1.The file /etc/gratm.conf needs the configuration statements for the port used:
Traffic_Shape name=bigg_speed_high_quality \ peak=622000 sustain=622000 burst=2048 qos=high
Interface ga010 traffic_shape=bigg_speed_high_quality
PVC ga010 0/132 proto=ip traffic_shape=bigg_speed_high_quality
2. The file /etc/grifconfig.conf has the following entries:
gt030 | 192.168.13.4 | 255.255.255.0 | - | mtu 65520 |
ga010 | 10.20.30.2 | 255.255.255.0 | - | mtu 9180 |
3.The file /etc/grroute.conf has the following line:
192.168.14.0 255.255.255.0 10.20.30.1
This sets the correct route to the other SP Switch network over the ATM
4.The SP Switch Router Adapter card is connected to the SP Switch and configured, too. Check with SDRGetObjects switch_responds on the CWS and use Eunfence if needed.
2.On the nodes in SP21 the following route needs to be set:
route add
192.168.14.4
3. On the nodes in SP2 the following route needs to be set:
route add
192.168.13.4
To avoid any pitfalls, set the MTU size explicitly to the size of the ATM adapter.
Hint: You must not use SMIT to set this route and put it into the ODM. The SP Switch is not operational at the time this route would be set during boot time. Therefore, this route would be put onto another, already available network interface, for example, the Control Ethernet, and this is definitely not what you want to happen.
Use a separate /etc/rc.routes shell script that is run only after an Estart or an Eunfence was issued, or use some other mechanisms to have this route set only after the css0 interfaces on the SP nodes are up and running.
Setup is done now, and every node in SP2 should now be able to ping every node in SP21 and vice versa.
4. Check for correct routing entries on all nodes in SP21:
Multiple RS/6000 SPs and Multiple GRFs 225
