Unsolved
This post is more than 5 years old
1 Message
0
781
March 14th, 2011 09:00
NAS IP Replication.
Hello Guys, I Have had challenges with network team on configuration of Ether Channel or LACP network configuration. NAS systems, each are Active-Standby configurations, deployed on the same networks, so no fire wall between to worry about, but the channel setup, network did the switch work, we can configure either ether channel or LACP on the NAS, how ever, once done, the NAS Data mover IP addresses respond to a ping, but can not ping anything. At this time, have the CGE0 & CGE1 setup as a FSN(Fail Safe Network) – CGE3 & 4 ports are suppose to be LACP, how ever, have not gotten and extra IP address to use to test that 2nd LACP, I ran a case through EMC, they can not find nor duplicate the issue in their labs, which takes us back to the network switch, how ever, network states is setup correctly. We have not gotten a 100% confirmation on what is to be replicated to the DR site, which is a matter of contention with in the client's camp.
Now, do I have any way to check if switch configuration is correct, like running a route trace to see where the packages are being dropped? Am I missing something on the configuration, or is there anything to take into account on this type of configs?
Thanks guys, you help will be much appreciated.
D.
No Events found!
DanJost
190 Posts
0
March 16th, 2011 11:00
What kind of switch is it? In Cisco IOS you can see the status of an LACP by using the following command:
show lacp 1 neighbor
...assuming you are using port channel 1...On the active data mover you'll get an output something like this:
switch#show lacp 1 neighbor
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 1 neighbors
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Gi1/0/1 FA 20 0060.1626.6370 8s 0x0 0x1027 0x100 0x3F
Gi2/0/1 FA 20 0060.1626.6370 4s 0x0 0x1027 0x200 0x3F
On the standby it'll look different because it isn't really "up"
switch#show lacp 2 neighbor
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 2 neighbors
Partner's information:
LACP port Admin Oper Port Port
Port Flags Priority Dev ID Age key Key Number State
Gi1/0/2 SP 0 0000.0000.0000 4294967s 0x0 0x0 0x0 0x0
Gi2/0/2 SP 0 0000.0000.0000 4294967s 0x0 0x0 0x0 0x0
Another view is to do a "show etherchannel 1 detail" - it'll tell you the etherchannel protocol and some other things that might be interesting. Again the passive DM will look different.
Because you can ping it and it can't ping "out", I would set up the channel again and try again. Unplug or disable one of the switch ports in the LACP port channel. If you are having port channel issues, it'll probably work on both ports when it's "buddy" is disconnected. Other things to check is to make sure there is a default route defined. If ping is your tool, I would start on the same subnet and VLAN with pings first at the default gateway and other devices and work your way out from there. Also, rule out the obvious such as client-side firewalls on the machine you are testing with. If you are doing dot1q VLAN trunking there are other things that you might have to deal with but you didn't mention anything about that.
Hope this helps...
Dan