Re: Gbic link between 2 3524xl stp problem

kitch · ‎09-17-2003

Hello, I need some help with this:

Small network, 2 3524xl switches linked by 1 gbic(copper) adapter on each switch, single vlan (1) , simple configuration.

about 10 days ago the network started to give many problems, after many tests (hardware is ok) I saw that connecting switches together using fastethernet ports (instead of the gbic ports) worked great (but at 100mbps).

But using the gbic ports the link goes up and down continuosly each 5 minutes more or less. gbic ports leds also go amber/green.

show spanning-tree says that the link changes between learning and forwarding all the time.

Please any ideas are welcome!

debug all says this:

00:25:36: start_timer id mismatch satellite dm 2 state 1 id 53ABBC exp id 53A93C

00:25:36: start_timer id mismatch satellite dm 2 state 1 id 53B5FC exp id 53AABC

00:25:36: CPU Interface 0 storage notify failed on queue 1

00:25:36: port = 0, old = 0, new = 0

00:25:36: co_status: Event EVENT_STP_STATE_CHANGE port 35 to 0

00:25:36: Ethernet Controller STP change: port 35 learning -> forwarding

00:25:36: Ethernet Controller STP change: port 35 learning -> forwarding vlan

1

00:25:36: CGMP SHIM: got topology change

00:25:36: ST: GigabitEthernet0/2 vlan 1 -> forwarding

00:25:37: start_timer id mismatch satellite dm 0 state 1 id 53A93C exp id 53AC3C

00:25:37: start_timer id mismatch satellite dm 0 state 1 id 53AC3C exp id 53AAFC

00:25:37: start_timer id mismatch satellite dm 0 state 1 id 53A97C exp id 53AB7C

00:25:37: start_timer id mismatch satellite dm 0 state 1 id 53AA7C exp id 53B1FC

00:25:37: start_timer id mismatch satellite dm 0 state 1 id 53AAFC exp id 53A83C

00:25:37: IP: s=10.164.99.90 (VLAN1), d=10.164.99.255, len 217, rcvd 1

00:25:37: UDP: rcvd src=10.164.99.90(138), dst=10.164.99.255(138), length=197

00:25:37: IP: s=10.164.99.90 (VLAN1), d=10.164.99.255, len 217, dispose udp.nopo

rt

00:25:37: IP: s=10.164.99.5 (VLAN1), d=10.164.99.255, len 219, rcvd 1

00:25:37: UDP: rcvd src=10.164.99.5(138), dst=10.164.99.255(138), length=199

00:25:37: IP: s=10.164.99.5 (VLAN1), d=10.164.99.255, len 219, dispose udp.nopor

t

00:25:37: Add address 0010.8376.adeb, on port Gi0/2 vlan 1

00:25:38: SNMP: HC Timer 68F79C fired

00:25:38: SNMP: HC Timer 68F79C rearmed, delay = 20000

00:25:38: CPU Interface 0 storage notify failed on queue 1

00:25:38: start_timer id mismatch satellite dm 0 state 1 id 53AABC exp id 53AA3C

00:25:38: start_timer id mismatch satellite dm 0 state 1 id 53AA3C exp id 53AEBC

00:25:38: start_timer id mismatch satellite dm 0 state 1 id 53A9FC exp id 53ABBC

00:25:38: IP: s=10.164.99.90 (VLAN1), d=10.164.99.255, len 217, rcvd 1

00:25:38: UDP: rcvd src=10.164.99.90(138), dst=10.164.99.255(138), length=197

00:25:38: IP: s=10.164.99.90 (VLAN1), d=10.164.99.255, len 217, dispose udp.nopo

rt

00:25:38: IP: s=10.164.99.5 (VLAN1), d=10.164.99.255, len 219, rcvd 1

00:25:38: UDP: rcvd src=10.164.99.5(138), dst=10.164.99.255(138), length=199

00:25:38: IP: s=10.164.99.5 (VLAN1), d=10.164.99.255, len 219, dispose udp.nopor

t

00:25:38: IP: s=10.164.99.61 (VLAN1), d=10.164.99.255, len 239, rcvd 1

00:25:38: UDP: rcvd src=10.164.99.61(138), dst=10.164.99.255(138), length=219

00:25:39: IP: s=10.164.99.61 (VLAN1), d=10.164.99.255, len 239, dispose udp.nopo

rt

00:25:39: start_timer id mismatch satellite dm 0 state 1 id 53ABFC exp id 53ABBC

00:25:39: start_timer id mismatch satellite dm 0 state 1 id 53ABBC exp id 53AEBC

00:25:39: start_timer id mismatch satellite dm 0 state 1 id 53AB7C exp id 53AA3C

00:25:39: IP: s=10.164.99.90 (VLAN1), d=10.164.99.255, len 217, rcvd 1

00:25:39: UDP: rcvd src=10.164.99.90(138), dst=10.164.99.255(138), length=197

jdw28 · ‎09-17-2003

you probably have a bad GBIC or Gigabit port. Use Etherchannel if you want to stick with FE ports but with fast connections.

-Jim

milan.kulik · ‎09-18-2003

I've also had a problem with copper GBIC in 3524 in the past. It was working fine a week and went down then. After switch reset it worked again for some time and failed again.

I decided not to use copper GBICs finally.

Regards,

Milan

cminch · ‎09-18-2003

Hi,

Do you have UDLD enabled? This might also work.

regards,

Corey

kitch · ‎09-18-2003

Thanks all for your answers,

seems that the GBIC adapter comes down and up without apparent reason.

Already tried:

-Change ports and GBIC adapters, hardware seems ok

-Switchport mode trunk on both gbic ports (single vlan, that wouldn't be necessary please correct me if I'm wrong)

-enable UDLD on both Gigabit ports

I think I'll configure a etherchannel and ask management to buy new switches!!

Thanks

Fernando