06-11-2015 01:30 AM - edited 03-08-2019 12:30 AM
Hello
We have a simple setup with 2x cisco WS-C4948-10GE (san-sw3 and san-sw4) connecting NFS storage (appliance1) and iSCSI storage (appliance2) to 6 vmware esx hosts with 1 link on each switch (see attachment for network diagram). These two switches are connected to each other through a 6x1gbit port-channel and have one interface each for management and vtp data.
This setup has been working fine for a while (6+ months) but a few days ago when we removed a VLAN from both switches on the trunk connecting appliance1 (nfs storage). This VLAN was only used for LDAP authenticating users on a network share no longer used.
When this VLAN was removed we lost connection to all NFS storage on the esx hosts, randomly the hosts connected again but quickly got disconnected. I was able to browse datastores for a while and some times single hosts seemed to work (but awful slow). This reminded me of MTU issues that I have seen before on esx hosts however, we did not touch any MTU settings and MTU seems to be configured properly (on esx hosts, on switches and on appliances). Whats even more weird is that we did not lose iSCSI connections, these seem to have been functioning all the time.
In addition I was able to ping appliance1 from all esx hosts with MTU of 1500. When I tried to ping with MTU 9000 some hosts worked, later on I was able to ping from all hosts with MTU 9000 but connectivity was not restored.
To resolve the issue I shutdown the nfs storage ports (appliance1) and portchannel on switch2 (san-sw4), leaving one link between switches (trunk on GigabitEthernet1/46) still up.
I have attached our switch configuration as it was when the issue was live (ie no shutdown ports). I would very much appreciate any suggestions to what actually happened and/or solutions.
Many thanks
/Daniel
06-11-2015 02:03 AM
Could the issue be related to a loop because we had both port-channel and a single link trunk up at the same time? Would any loop prevention mechanism not kick in? Would this not mean unresponsive switches (switches was responsive and no usual traffic was detected, though I did lose switch2 (san-sw4) 2 times during a 7 hour period but it recovered)? And why would appliance2 still be available?
06-11-2015 05:41 AM
Do you have the logs from both switches during the outage ?
06-11-2015 05:46 AM
Unfortunately our logging configuration was very sparse and I could see nothing out of the ordinary in 'sh logging' (I did check during outage). If there is any other logging or buffer I don't know about please advice.
Thanks.
06-11-2015 06:29 AM
I see syslog setup did anything go to that ? if it was layer 2 stp calculations that caused it you would need to use command below to track the suspect ports , without real time debugs/logs would be very difficult to suggest exactly what happened
sh spanning-tree de | i ieee|from|is exec|occur
06-11-2015 06:39 AM
Unfortunately the syslog server was down at the time of event. :(
What would be your best guess at the cause? Similar events have happened before (but resolved itself after a while) and I'm trying to establish if it could be related to both PortChannel and single link trunk being up at the same time.
The single link trunk was supposed to be shutdown but this configuration has been missed out.
06-11-2015 07:16 AM
i would say stp at some level guessing , use that command above once there have been no major changes you should be able to identify where when changes occurred
06-11-2015 08:17 AM
Here is the command;
san-sw3#sh spanning-tree de | i ieee|from|is exec|occur
VLAN0001 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0020 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0024 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0025 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0026 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0027 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0028 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0054 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0104 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0140 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0200 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0201 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0202 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0301 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0302 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0303 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0304 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0306 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0307 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0308 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0310 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0311 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0312 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0314 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0315 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0316 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0401 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0501 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0502 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0503 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0504 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0505 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0506 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0507 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0508 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0509 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0510 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0511 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0512 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0513 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0514 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0515 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0520 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0521 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0522 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0523 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 8 last change occurred 1d18h ago
from Port-channel1
VLAN0524 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0525 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 8 last change occurred 1d18h ago
from Port-channel1
VLAN0526 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0527 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0528 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0529 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0530 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 2 last change occurred 1d15h ago
from Port-channel1
VLAN0531 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0532 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0533 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0534 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0535 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0536 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 0 last change occurred 1d14h ago
VLAN0537 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 2 last change occurred 1d15h ago
from Port-channel1
VLAN0538 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 2 last change occurred 1d15h ago
from Port-channel1
VLAN0539 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 2 last change occurred 1d15h ago
from Port-channel1
VLAN0540 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 2 last change occurred 1d15h ago
from Port-channel1
VLAN0541 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0542 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0543 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0544 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0545 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0546 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0547 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0548 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0549 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0550 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0551 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0552 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0553 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0554 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0580 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0581 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0596 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0597 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0598 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0599 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0610 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0611 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0612 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0613 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0710 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0711 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0712 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 16 last change occurred 1d17h ago
from GigabitEthernet1/33
VLAN0713 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0714 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0715 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0716 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0717 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0718 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0719 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0720 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0721 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0722 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 26 last change occurred 1d15h ago
from TenGigabitEthernet1/50
VLAN0723 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0724 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0800 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0801 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 12 last change occurred 1d18h ago
from GigabitEthernet1/48
VLAN0802 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 11 last change occurred 1d18h ago
from GigabitEthernet1/48
VLAN0803 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0805 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 11 last change occurred 1d18h ago
from GigabitEthernet1/48
VLAN0811 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0812 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0813 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 21 last change occurred 1d15h ago
from TenGigabitEthernet1/50
VLAN0814 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 21 last change occurred 1d15h ago
from TenGigabitEthernet1/50
VLAN0815 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 23 last change occurred 1d15h ago
from TenGigabitEthernet1/50
VLAN0900 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0902 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0903 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0998 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN0999 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 6 last change occurred 1d18h ago
from Port-channel1
VLAN1000 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 11 last change occurred 1d15h ago
Is 23 changes anything to be concerned about? But yeah, there has been some topology changes.
06-11-2015 08:17 AM
From the other switch I can see at most 35 changes;
VLAN1000 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 35 last change occurred 1d15h ago
from GigabitEthernet1/48
06-12-2015 12:18 AM
To use that command you start at the core and follow the port so just jump across to the port-channel neighbor run it again see what interface it shows for all the changes then use cdp for that interface and follow it to the next switch and so on , its a way of tracking faults at layer 2 it will eventually bring you to a destination of where the chnages may have started but doing it after the time will be more difficult so it may not be full proof but its something to go on , is that around the time the fault occurred ? you dont want to be chasing the ports if there have been changes since as it only records the last current topology changes , its just a stripped down spanning-tree detail output thats easier to read
06-12-2015 12:24 AM
Correct, the time is just after the incident was resolved by shutting ports. What even more confuses me is that I see "last change occurred 1d15h ago from TenGigabitEthernet1/50". These ports, TenGigabitEthernet1/50 and TenGigabitEthernet1/49 are not connected to any switch, just the nfs-server.
Why would these ports trigger a change in STP?
06-12-2015 01:02 AM
You need to look at what vlan(s) are associated with the port if your using pvst as a change somewhere on that vlan at layer 2 could put the ports into an stp calculation , saying that they should be set to portfast if connected to a server and bpduguard to avoid that happening with servers keep them as edge ports in stp
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide