5.The SP Switch Router Adapter card is connected to the SP Switch and configured. Check with SDRGetObjects switch_responds on the CWS and use Eunfence if needed.
The following tasks are performed on the respective SP nodes:
1. On the nodes in SP21, the following route needs to be set:
route add -net 192.168.13 -netmask 255.255.255.0 -mtu 65280 10.50.1.2
2. On the nodes in SP2, the following route needs to be set:
route add
Hint: You must not use SMIT to set the routes and put them into the ODM. The SP Switch is not working when these routes are set, at boot time. Therefore, they are put onto another, already available network interface, for example the control Ethernet, and this is definitely not what you expect 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.
3. Check for correct routing entries on all nodes in SP21:
root@sp21en0:/ dsh netstat |
|
|
|
| ||
sp21n01: 192.168.13/24 | 192.168.14.4 | UG | 5 | 717959 | css0 65280 | - |
sp21n05: 192.168.13/24 | 192.168.14.4 | UG | 2 | 172837 | css0 65280 | - |
sp21n06: 192.168.13/24 | 192.168.14.4 | UG | 0 | 0 | css0 65280 | - |
sp21n07: 192.168.13/24 | 192.168.14.4 | UG | 2 | 141374 | css0 65280 | - |
sp21n08: 192.168.13/24 | 192.168.14.4 | UG | 0 | 0 | css0 65280 | - |
sp21n09: 192.168.13/24 | 192.168.14.4 | UG | 2 | 78305 | css0 65280 | - |
sp21n10: 192.168.13/24 | 192.168.14.4 | UG | 0 | 0 | css0 65280 | - |
sp21n11: 192.168.13/24 | 192.168.14.4 | UG | 0 | 202459 | css0 65280 | - |
sp21n13: 192.168.13/24 | 192.168.14.4 | UG | 5 | 543370 | css0 65280 | - |
sp21n15: 192.168.13/24 | 192.168.14.4 | UG | 1 | 384799 | css0 65280 | - |
root@sp21en0:/ |
|
|
|
|
|
|
