This post is more than 5 years old
11 Posts
0
38336
Cluster nodes cant ping each other
Hi,
I have recently put one of our old clusters back online, its a poweredge 1855. I'm working on 5 nodes, and it has a PowerConnect 5316M on the back. The 5316M has only 1 cable connecting it to the uplink switch.
Each blade has 2 NIC's. One of them is a normal production NIC, with a normal IP on our range. All blades can ping each other on this address, and they all have internet.
The other NIC is what I'm going to use for live migration, or cluster heartbeat or something ..either way, it has a different range with no gateway (172.50.1.x)
Now, 3 of the blades can all ping eachother, but not the other 2. And the 2 that cant ping, can ping eachother. So it looks like 2 are on the same VLAN, and the other 3 are on the same VLAN.
The problem i have, is the switch shows them all on the default VLAN ..and one thing i cant work out ..is if the servers all have 2 NICs, but there are only 10 internal switch ports? ..so how can i set either NIC on a different VLAN?
The switch config is here:
console# show run
spanning-tree mode mstp
spanning-tree mst configuration
instance 1 add vlan 1,15,900
instance 2 add vlan 2-3
name PDSNetherlands1
revision 900
exit
spanning-tree mst 1 priority 57344
spanning-tree mst 2 priority 57344
interface port-channel 1
description 'LACPGROUP-M5316M-SW2'
exit
interface port-channel 1
switchport mode general
exit
vlan database
vlan 2-3,15,238,328-329,501,638,900
exit
interface port-channel 1
switchport general allowed vlan add 15
exit
interface port-channel 1
switchport general allowed vlan add 900
exit
interface vlan 2
name "PDS Internet"
exit
interface vlan 3
name "PDS Wireless"
exit
interface vlan 15
name "PDS ServerInfrastructure"
exit
interface vlan 238
name "SHELL GI-Desktops"
exit
interface vlan 328
name "SHELL Unix-Desktops"
exit
interface vlan 329
name "SHELL Windows-Servers"
exit
interface vlan 501
name "SHELL Linux-Desktops"
exit
interface vlan 638
name "SHELL IP-Telephony"
exit
interface vlan 900
name "PDS Workstations"
exit
interface range ethernet g(11-16)
channel-group 1 mode auto
exit
interface vlan 1
ip address 10.254.254.253 255.0.0.0
exit
ip default-gateway 10.0.0.1
logging 10.0.1.56 severity debugging facility local0
username admin password 5ebe2294ecd0e0f08eab7690d2a6ee69 level 15 encrypted
username admin_jon password ea4462b55746d29a4a0fc44c3db06b95 level 15 encrypt
ed
username administrator password 22d4734b069e91ceebdf297701005b28 level 15 enc
rypted
snmp-server community private rw
sntp client poll timer 60
sntp unicast client enable
sntp anycast client enable
sntp broadcast client enable
sntp server 64.90.182.55 poll
console#
Any help would be appreciated, I cannot complete the cluster validation wizard until i can crack this ..
Kind Regards,
Jon
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
1
April 17th, 2013 08:00
This document does a good job of showing how the Interconnections work.
www.dell.com/.../ps3q05-20050163-Brundridge-OE.pdf
I/O module 1 will go to port 1 and I/O module 2 will go to port 2 of the LOM.
So it may be worth checking which ports are being used by the server. If 3 are on port 1 and then the other 2 are on port 2, try and get all the 172.50.1.x addresses assigned to port 2 for example.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
April 16th, 2013 12:00
Do we have just the one 5316 installed in slot 1, or are there other devices plugged into slots 2,3,4 on the back of the chassis ?
Which slots on the front of the chassis are the blade servers installed in, are these the only servers?
We can run the following show command on the interfaces to check and make sure they are all in VLAN 1 still.
#show interfaces switchport ethernet 1/g1
With that information we should be able to look into things a little more.
Thanks.
JonPDS
11 Posts
0
April 17th, 2013 07:00
Hi Daniel,
Thanks for the reply. Here is more information:
We have 2 x 5316 installed in the back of the chassis. Each of them now has a single cable in external port 14 connecting it to our core switches, these are just on VLAN 1.
The servers that I'm currently working on are installed in slots 5,6,7,8 and 9 in the front of the chassis.
Slots 1,2,3 also contain servers, but I'm not too concerned about those right now. Slot 4 is just empty.
When I run the above command, the result is the same for all internal ports ...VLAN 1, Access mode, Gvrp Status: disabled ...no forbidden VLAN's.
I just cannot see any different in the ports, but 6 and 7 can still only see eachother.
One thing i'm confused about ...if there are 2 modular switches in the back, with a total of 12 external ports (to connect to various external networks) ..and they have a total of 20 internal ports ...how do i know which interface on which server is connected to which internal port?
All of the blades have 2 NIC's, but i dont have a way to tell which internal port they go into?
Thanks so far!
cheers,
Jon
JonPDS
11 Posts
0
April 18th, 2013 04:00
Hi Daniel,
Thanks for that link, I had a read through it. I can understand what you're saying about NIC 1 going to module 1 and NIC 2 going to module 2 ..that makes sense now.
All the servers are using the same NICs for the same type off network ...NIC 1 on all blades is the 10.x.x.x production NICs ..all of them can see the rest of the network. Then the secondary card is the 172.x.x.x range ...but this is only working for 3 nodes. ...all the 172.x.x.x addresses are on port 2.
The switches look largely unconfigured ...that is all the ports are on VLAN 1.
So does this mean for blade 1, NIC 1 goes to port 1 on I/O module 1 ...and blade 1 NIC 2 goes to port 1 on I/O module 2?
Sorry for the confusion but I'm not sure why two of the 172's cant ping the rest?
Cheers,
Jon
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
April 18th, 2013 08:00
Jon, thanks for keeping us updated, that is great news to hear!
Cheers
JonPDS
11 Posts
0
April 18th, 2013 08:00
Hi,
this is fixed now. Indeed it was the internal ports on the Switch-2 which were configured for a different VLAN. The CLI didnt show this, and the normal VLAN membership GUI wouldnt let me change them ...the VLAN port settings would let me change the VLAN tho. .
all are talking now ..thanks for your help
Regards,
Jon