10-12-2014 11:38 PM
Dear All,
We have Total 7 SG300 switches for Desktop access dual-homed to Pair of 3560-x switches for Data access in branch environment.
All 7 switches have identical configuration, hardware version and were commissioned at the same time.
However only three of them keep on crashing or restarting intermittently without any time correlation with each other.
But the issue occurs only during working hours
Error on all of the switches before crashing :-
SYSLOG-F-OSFATAL: FATAL ERROR: tExcTask: ABORT DATA exception ***** FATAL ERROR ***** SW Version : 1.2.7.76 Version Date: 19-Jul-2012 Version Time: 17:54:43 Instruction 0x18 Exception vector 0x10 Program state register 0x80000092
Information level message on all of the switches after crashing :-
INIT-I-Startup: Cold Startup
10-12-2014 11:49 PM
Hi,
Try to upgrade the firmware of the switch over console.Still issue exists .Kindly raise the TAC ticket to get replacement of the switch.
Firmware link:
http://software.cisco.com/download/release.html?mdfid=283019669&flowid=18907&softwareid=282463181&release=1.4.0.88&relind=AVAILABLE&rellifecycle=&reltype=latest
Cisco TAC contact details:
http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
10-13-2014 12:18 AM
Dear V K Moorthy,
Could you explain how to upgrade SG300 firmware over console, because i could only find below three methods.
10-13-2014 01:52 AM
10-13-2014 06:34 AM
Is it possible to upgrade both the boot code and the firmware through this method?
10-13-2014 07:43 PM
No only we can upgrade the firmware.
10-13-2014 11:19 PM
Hey,
Post upgrading one of the affected switch, new issue is being observed.
If both the two links are connected to upstream pair of 3560 switches, a layer 2 loop is found to be occurring with multiple mac flap notifications and traffic utilization shooting to 400 Mbps from normal 1 Mbps.the loop is rectified after one of the link to 3560 switches is disconnected.
The loop is observed even if no other host is connected to the switch except these two uplinks
The configuration which was working fine before upgrade, is now causing this issue post upgrade.
10-13-2014 11:33 PM
Which is the root-bridge in your network:3560 or SG 300 .Kindly share the network topology of your network.
10-13-2014 11:47 PM
Root Bridge port channel
[3560 1]---------------------------[3560 2]
| |
| |
| |
|------------[SG300]-----------|
As you can see for all of our Sg300 Root bridge id is same as bridge id.
and port on secondary 3560 usually goes to block mode, but in case of upgraded Sg300 the port on 3560-2 switch remains in forwarding mode only.
10-14-2014 12:12 AM
Kindly share the STP priority values for switch 3560-1 and 3560-2
10-14-2014 12:29 AM
Below is configuration for port 32 connected to working SG300.
Affected SG300 is connected to port 33 and has identical configuration
3560-1
Port 32 (GigabitEthernet0/33) of VLAN0031 is designated forwarding
Port path cost 4, Port priority 128, Port Identifier 128.32.
Designated root has priority 4127,
Designated bridge has priority 4127,
Designated port id is 128.32, designated path cost 0
3560-2
Port 32 (GigabitEthernet0/33) of VLAN0031 is alternate blocking
Port path cost 4, Port priority 128, Port Identifier 128.31.
Designated root has priority 4127,
Designated bridge has priority 4127,
Designated port id is 128.31, designated path cost 0
10-14-2014 02:08 AM
Hi,
Kindly take the configuration backup from SG300 switch.Reset the switch to factory default and upload the configuration back.After that you have same issue.Kindly raise the TAC ticket to cisco support team.
Support center contact details:
--------------------------------------http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
10-14-2014 07:56 AM
Nothing seems to work , same issue exists even after factory reset,
It seems the switch is filtering BPDUs as port facing SG300 of 3560-2 shows 0 BPDUs received.
10-15-2014 12:24 AM
Hi,
Can you try to change on catalyst PVST+ to classic STP and on SG300 RSTP to classic STP?
Those two are running different STP versions and simply do not understand each other BPDU messages.
Aleksandra
02-25-2019 01:24 PM
Hello. I know, it's an old post but I just wanted to mention for anyone else out there. The small business switches SF/SG only do STP for vlan 1 when using RSTP. They only consider other vlans when you switch over to MST which is the only way to get full vlan STP coverage when creating loops between them and Catalysts.
It's likely that your SG did not receive superior BPDUs from the 3560s and so proclaimed itself root bridge and then it blocked one of the root ports coming from same 3560s.
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