- Cisco Community
- Technology and Support
- Small Business Support Community
- Switches - Small Business
- Hello,I am not quite sure
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SG500XG-8F8T
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2014 07:10 AM
Hello,
I have two SG500XG-8F8T's in a stack config. I am using the 10G copper ports 1/2/1 and 1/2/2 to connect to a VNXe SPA eth10 and SPB eth10 respectivley. I have ports 2/2/1 and /2/2/2 connnect to SPA eth 11 and SPB eth11 repectively. The ports carry 2 VLAN's. When working with the technician from EMC, they are seeing alot Rapid STP traffic. Below is the log. Any ideas on what and why this is happening
root@spa:/cores/service>tcpdump -i eth11
tcpdump: WARNING: eth11: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth11, link-type EN10MB (Ethernet), capture size 96 bytes
15:18:06.181200 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge -id 8000.0c:68:03:9f:d6:44.8070, length 43
15:18:08.181036 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge -id 8000.0c:68:03:9f:d6:44.8070, length 43
15:18:10.181073 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge -id 8000.0c:68:03:9f:d6:44.8070, length 43
15:18:10.212709 00:18:73:e1:b5:ae (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown ) SNAP Unnumbered, ui, Flags [Command], length 46
15:18:10.212822 00:18:73:e1:b5:ad (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown ) SNAP Unnumbered, ui, Flags [Command], length 46
15:18:12.181010 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:14.180949 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
/bin/grep: network.conf: No such file or directory
/bin/grep: network.conf: No such file or directory
15:18:1 4.280133 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknow n), length 298
15:18:16.180878 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:16.533082 IP 192.168.21.61.19867 > 192.168.21.101.iscsi-target: S 1751040484:1751040484(0) win 65535 <mss 8960,nop,wscale 9,sackOK,timestamp 470556 0>
15:18:16.533296 IP 192.168.21.61.19867 > 192.168.21.101.iscsi-target: . ack 88320002 win 524 <nop,nop,times tamp 470556 1294>
15:18:18.180821 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:20.180762 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:22.180700 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:24.180629 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:26.180563 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:26.279752 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknown), length 298
15:18:27.879676 0c:68:03:9f:d7:ae (oui Unknown) > 01:80:c2:00:00:0e (oui Unknown), ethertype Unknown (0x88c c), length 62:
0x0000: 0207 040c 6803 9fd6 4404 0805 7465 322f ....h...D...te2/
0x0010: 322f 3206 0200 780a 0753 4735 3030 2d42 2/2...x..SG500-B
0x0020: 0e04 0014 0014 fe06 0080 c201 0001 0000 ................
15:18:28.180503 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:29.800290 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:18:30.180443 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:30.739715 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:18:32.180379 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:32.659708 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:18:34.180311 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:36.180257 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:36.419532 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:18:38.180189 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:38.279372 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknown), length 298
15:18:40.180130 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:40.208690 00:18:73:e1:b5:ae (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown) SNAP Unnumbered, ui, Flag s [Command], length 46
15:18:40.209304 00:18:73:e1:b5:ad (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown) SNAP Unnumbered, ui, Flag s [Command], length 46
15:18:42.180063 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:44.180002 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:44.180817 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:18:46.179937 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:46.545338 CDPv2, ttl: 180s, Device-ID '0c68039fd644'[|cdp]
15:18:48.179873 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:50.179804 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:50.278994 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknown), length 298
15:18:52.179750 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:52.218986 IP 192.168.20.1 > 224.0.0.1: ICMP router advertisement lifetime 30:00 1: {192.168.20.1 0}, length 16
15:18:54.179679 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:56.179617 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:57.878727 0c:68:03:9f:d7:ae (oui Unknown) > 01:80:c2:00:00:0e (oui Unknown), ethertype Unknown (0x88c c), length 62:
0x0000: 0207 040c 6803 9fd6 4404 0805 7465 322f ....h...D...te2/
0x0010: 322f 3206 0200 780a 0753 4735 3030 2d42 2/2...x..SG500-B
0x0020: 0e04 0014 0014 fe06 0080 c201 0001 0000 ................
15:18:58.179554 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:18:58.938855 IP6 fe80::e68:3ff:fe9f:d644.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 inf-req
15:19:00.179496 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:19:02.179432 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44. 8070, length 43
15:19:02.278620 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknown), length 298
15:19:04.179366 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
15:19:06.179302 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
/bin/grep: network.conf: No such file or directory
/bin/grep: network.conf: No such file or directory
15:19:08.179244 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
15:19:10.179185 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
15:19:10.277949 00:18:73:e1:b5:ae (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown) SNAP Unnumbered, ui, Flags [Command], length 46
15:19:10.278148 00:18:73:e1:b5:ad (oui Unknown) > 01:00:0c:cc:cc:cc (oui Unknown) SNAP Unnumbered, ui, Flags [Command], length 46
15:19:12.179111 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
15:19:14.179049 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
15:19:14.278241 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:68:03:9f:d6:44 (oui Unknown), length 298
15:19:16.178987 STP 802.1w, Rapid STP, Flags [Learn, Forward, Agreement], bridge-id 8000.0c:68:03:9f:d6:44.8070, length 43
oka
- Labels:
-
Small Business Switches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2014 01:45 PM
Hello,
The reason you are seeing so much RSTP traffic is because that is it's default behavior. RSTP sends out information every 2 seconds, which matches up with the time stamps on your trace here.
Sources used: Understanding RSTP (802.1w)
This is part of the standard of how RSTP functions. What exactly is the issue you are having?
You do have the option of using normal STP, or disabling it entirely, but chances are these normal messages are not the cause of your problem.
Hope that helps and thank you for choosing Cisco,
Christopher Ebert - Advanced Network Support Engineer
Cisco Small Business Support Center
*please rate helpful posts*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2014 02:44 PM
Hello,
The EMC tech is asking me a few questions that I am unsure on how to answer.
The issue we are having is: The EMC SAN has two SP's when and SP fails(basically we reboot it) the other SP takes over this happens in about 40 seconds which is acceptable for my VMware hosts. The problem we are seeing is when the SP that was rebooted comes back online, it sometimes takes up to 4 minutes for the orginal iSCSI paths to reinstate casuing timeouts on the host. The EMC tech thinks this could be network related, but I am not so sure. His comments are below in bold.
Hi Joe,
That’s good to know about RSTP. Did you ask if you should maybe should use FAST RTO instead. Also have they looked at your switch configs and given any suggestions to them?
Also have you done any further testing with RSTP disabled?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2014 02:59 PM
Hello,
I am not quite sure what Fast RTO is, I'm assuming something like Fast Retransmission Timeout? The only thing I could find on that related to EIGRP, so I don't think it has much to do with what is happening here. Either way your options for spanning tree are STP, RSTP, or disabling it. You can also try setting the port those SPs connect to as Edge ports, that will making them spanning tree portfast ports, however with RSTP your ports should already be coming up in less then 5 seconds, so I'm not sure that will resolve anything.
I am happy to take a look at your switches configuration if you would like, but I am with you, I don't think this is a network related issue. The failover between SPs (which I'm guessing stands for Storage Processor) sounds like an issue on the EMC side of things. I am not trying to push anything back over to them, but I have dealt with several EMC SAN setups on our switches, and there wasn't much to be changed on ours when it came to SP failover.
-----
Christopher Ebert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2014 06:50 AM
Thanks for your reply. I would appreciate you looking at my switch configs. SP does stand for storage processor. Let me know when you are available. Can you please email itops@cerus.com instead of rchew@cerus.com when you are available to work on this.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2014 11:26 AM
Have you tried placing the ports connected to the SP's and VMWare hosts into Portfast/Edge mode so they transition directly to forwarding instead of first going through listening and learning?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2014 01:13 PM
I just did this and same result. It appears the links come up just fine. Again, I don't think its a networking issue. Do you want me to paste my config in?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2014 01:18 PM
I think the RSTP stuff may be a red herring and you should focus on devising a way to rule out the switches. Maybe you can make all connections to a single switch for testing purposes and the re-test and see if the trouble still occurs?
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