08-08-2002 05:35 AM - edited 03-02-2019 12:32 AM
We are seeing the following message on our switch , is this a hardware problem or should switch be reloaded . Can not find this message in any of the message guides that we have or online .
%SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
08-08-2002 08:57 AM
Might need more information to determine if this is a HW or network conjestion issue causing this. Here is some explanation.
This error message indicates the Supervisor has lost ESMP communication to
the Astro ASIC on 10/100 Line Cards. There are multiple possible causes
for this loss of communication:
1) Layer 2 Loop or Broadcast Storm that results in high traffic load that
causes loss of ESMP traffic. ESMP traffic takes the same interconnect path
as data traffic.
2) If the module number and Astro Reference are consistent and a layer 2
loop is not occuring, the problem is most likely a faulty SERDES component
on either the Supervisor or Line Card. A faulty SERDES component can cause
intermittent connectivity for ESMP traffic to the Astro resulting in
Timeouts.
3) If the module number and Astro reference in respect to the error message
is alternating modules and Astros, then the error message could be
indicating a Oscillator Failure. Generally, an Oscillator failure is
accompanied by both the Astro Timeout Error Message and BlockTXQueue and
BlockedGigaport Error Messages.
Hope this helps,
Don
08-09-2002 10:41 AM
Hello Don , this is some of the stuff we are seeing and also we are seeing a large amount of transmit errors across alot of the ports that are on the same vlan , this is a extended subnet of almost 800 users , yeah I know , not my choice . We have already reloaded the switch , it is running version 6.2.3 .
2002 Aug 09 16:30:31 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:01:af:07:96:96 is flapping between port 2/32 and port 2/25
2002 Aug 09 16:30:32 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:06:29:d0:fe:fe is flapping between port 2/32 and port 2/25
2002 Aug 09 16:30:32 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:d0:bc:f4:63:04 is flapping between port 2/27 and port 2/25
2002 Aug 09 16:30:38 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout occurred
2002 Aug 09 16:32:40 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:01:af:07:bd:17 is flapping between port 2/29 and port 2/32
2002 Aug 09 16:32:41 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:01:af:07:bd:26 is flapping between port 2/29 and port 2/32
2002 Aug 09 16:32:41 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:01:af:07:96:1f is flapping between port 2/29 and port 2/32
2002 Aug 09 16:33:22 UTC +00:00 %SYS-4-P2_WARN: 1/Blocked queue on gigaport 20, ( 1 : 0 )
2002 Aug 09 16:33:22 UTC +00:00 %SYS-4-P2_WARN: 1/Blocked queue (tx) on port 2/25
2002 Aug 09 16:33:49 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:d0:bc:f4:63:04 is flapping between port 2/32 and port 2/25
2002 Aug 09 16:33:50 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:06:29:77:4e:75 is flapping between port 2/32 and port 2/25
2002 Aug 09 16:33:52 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:01:af:07:96:a8 is flapping between port 2/32 and port 2/25
2002 Aug 09 16:33:52 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:06:29:95:0f:bf is flapping between port 2/32 and port 2/27
2002 Aug 09 16:35:32 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:d0:bc:f4:63:04 is flapping between port 2/25 and port 2/27
2002 Aug 09 16:35:33 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:a0:24:91:38:3b is flapping between port 2/25 and port 2/27
2002 Aug 09 16:35:33 UTC +00:00 %SYS-4-P2_WARN: 1/Host 00:06:29:f1:36:b2 is flapping between port 2/29 and port 2/32
2002 Aug 09 16:35:54 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout occurred
2002 Aug 09 16:46:03 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 16:56:10 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 17:06:19 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 17:16:27 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 17:22:21 UTC +00:00 %PAGP-5-PORTFROMSTP:Port 5/25 left bridge port 5/25
2002 Aug 09 17:22:27 UTC +00:00 %PAGP-5-PORTTOSTP:Port 5/25 joined bridge port 5/25
2002 Aug 09 17:26:36 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 17:36:44 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
2002 Aug 09 17:46:52 UTC +00:00 %SYS-4-P2_WARN: 1/Astro(2/4) - timeout is persisting
08-09-2002 10:59 AM
Glen,
The Astro referrence is not changing from 2/4 so you might have a bad linecard if you feel that you don't meet the other traffic related issues (Bcast Storm, Bridging Loops, etc). I notice you have a lot of hosts flapping between interfaces. What is causing this? If not HW related I would look closer into your STP design (assuming more switches here) and see if you are having issues there as well.
Hope this helps,
Don
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