TruCluster
Showing results for 
Search instead for 
Do you mean 

Network Interface not working after migration TruCluster 5.1.B

ygg
Occasional Visitor

Network Interface not working after migration TruCluster 5.1.B

I have a cluster ( TruCluster 5.1B ) that consists of three ES40. Each one has three network interfaces. Two of then are used for netrain. IP address of "nr0" interface is used by the cluster within a corporative network ( 10.x.x.x )
The third one is used for connecting to a different network (192.x.x.x). The connection is through a switch.
This last one interface, now, after migrating from Tru64 4.0G to 5.1B, doesn't work. The configuration of both networks ( 10.x.x.x and 192.x.x.x ) hasn't change at all.
Ethernet cards seem to be ok.
gated daemon is running
The machines don't see any other machine of the cluster through the third interface.
¿ Any idea about what could be producing this problem
5 REPLIES
Honored Contributor

Re: Network Interface not working after migration TruCluster 5.1.B


Just guessing..... with the upgrade the name of the interface changed from ee2 to ee3 (or other), to make it work again you need to change in /etc/rc.config the relation between NETDEV_n and ee? .

Show us the "hwmgr view hierarchy" and "grep NETDEV_ /etc/rc.config"

__ Johan.

_JB_
ygg
Occasional Visitor

Re: Network Interface not working after migration TruCluster 5.1.B

Hi,
No, the name of the interface hasnt't changed.

I'll send you more information:
# ifconfig -a
ics0: flags=1100063
inet 10.0.0.1 netmask ffffff00 broadcast 10.0.0.255 ipmtu 7000

lo0: flags=100c89





inet 127.0.0.1 netmask ff000000 ipmtu 4096

nr0: flags=c63
NetRAIN Attached Interfaces: ( tu0 tu1 ) Active Interface: ( tu0 )
inet 10.235.115.14 netmask ffffffc0 broadcast 10.235.115.63 ipmtu 1500

sl0: flags=10

tu0: flags=4000c63
NetRAIN Virtual Interface: nr0
NetRAIN Attached Interfaces: ( tu0 tu1 ) Active Interface: ( tu0 )

tu1: flags=4000c63
NetRAIN Virtual Interface: nr0
NetRAIN Attached Interfaces: ( tu0 tu1 ) Active Interface: ( tu0 )

tu2: flags=c63
inet 192.168.5.31 netmask ffffff00 broadcast 192.168.5.255 ipmtu 1500

tun0: flags=80


HWID: hardware hierarchy (!)warning (X)critical (-)inactive (see -status)
-------------------------------------------------------------------------------
1: platform AlphaServer ES40
2: cpu CPU0
3: cpu CPU1
7: bus pci1
8: connection pci1slot1
20: scsi_adapter itpsa0
21: scsi_bus scsi0
75: disk bus-0-targ-0-lun-0 dsk0
10: connection pci1slot2
22: scsi_adapter isp0
23: scsi_bus scsi1
79: tape bus-1-targ-5-lun-0 tape0
12: connection pci1slot3
24: fibrechannel_adapter emx0
25: scsi_bus scsi2
97: disk IDENTIFIER=8 dsk1
98: disk IDENTIFIER=7 dsk2
99: disk IDENTIFIER=10 dsk3
100: disk IDENTIFIER=9 dsk4
101: disk IDENTIFIER=11 dsk5
102: disk IDENTIFIER=12 dsk6
103: disk IDENTIFIER=15 dsk7
104: disk IDENTIFIER=16 dsk8
105: disk IDENTIFIER=17 dsk9
106: control_port bus-2-targ-0-lun-0 scp0
14: connection pci1slot4
80: cluster_interconnect mchan0
81: legacy_driver Legacy-driver-(mchan0)
16: connection pci1slot5
26: network tu0
18: connection pci1slot6
27: network tu1
28: bus pci0
29: connection pci0slot1
43: graphics_controller comet0
31: connection pci0slot2
82: cluster_interconnect mchan1
83: legacy_driver Legacy-driver-(mchan1)
33: connection pci0slot3
44: X network tu2
35: connection pci0slot4
45: fibrechannel_adapter emx2
46: scsi_bus scsi3
97: disk IDENTIFIER=8 dsk1
98: disk IDENTIFIER=7 dsk 99: disk IDENTIFIER=10 dsk3
100: disk IDENTIFIER=9 dsk4
101: disk IDENTIFIER=11 dsk5
102: disk IDENTIFIER=12 dsk6
103: disk IDENTIFIER=15 dsk7
104: disk IDENTIFIER=16 dsk8
105: disk IDENTIFIER=17 dsk9
106: control_port bus-2-targ-0-lun-0 scp0
37: connection pci0slot7
47: bus isa0
48: connection isa0slot0
49: keyboard keyboard0
50: pointer mouse0
51: connection isa0slot2
52: serial_port tty00
53: connection isa0slot3
54: serial_port tty01
55: connection isa0slot4
56: parallel_port lp0
57: connection isa0slot5
58: fdi_controller fdi0
59: disk fdi0-unit-0 floppy0
39: connection pci0slot15
60: ide_adapter ata0
61: scsi_bus scsi4
76: disk bus-4-targ-0-lun-0 cdrom0
62: scsi_bus scsi5
41: connection pci0slot19
63: bus usb0
64: sensor systhermal-cpu0
65: sensor systhermal-cpu1
66: sensor systhermal-pci_zone-1
67: sensor systhermal-pci_zone-2
68: sensor systhermal-pci_zone-3
69: sensor sysfan-pci_zone-1/2
70: sensor sysfan-power_supply-3/4
71: sensor sysfan-cpu_memory-5/6
72: sensor syspower-ps-0
73: sensor syspower-ps-1
74: sensor syspower-ps-2



# grep NETDEV_ /etc/rc.config
# NETDEV_n - network device name for network devices currently
# for example, NETDEV_0="ln0"
NETDEV_4=
NETDEV_5=
NETDEV_6=
NETDEV_7=
export NETDEV_0 NETDEV_1 NETDEV_2 NETDEV_3 NETDEV_4 NETDEV_5 NETDEV_6 NETDEV_7
NETDEV_1="ics0"
export NETDEV_1
NETDEV_2="tu2"
export NETDEV_2
NETDEV_0="nr0"
export NETDEV_0

Thanks.


Honored Contributor

Re: Network Interface not working after migration TruCluster 5.1.B


Did you remark the "X"=critical that hwmgr put in the output for tu2 ?
The interface card seems to have a problem.

__ Johan .

_JB_
Honored Contributor

Re: Network Interface not working after migration TruCluster 5.1.B

change the interconnect ip-adress to a 172. range (privat range). Using only privat networks is not a really good idea. 4.0x is not equal to 5.1x cluster configuration. Be sure you read and understand the Trucluster v5 installation guide and configured the cluster for use within private network ranges....
Help() { FirstReadManual(urgently); Go_to_it;; }
ygg
Occasional Visitor

Re: Network Interface not working after migration TruCluster 5.1.B

Finally was a problem with a switch
//Add this to "OnDomLoad" event