Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Cat4K6 problem

Intermittent communication problems on different port including one of the gbic uplinks (had to disable) on sup

CATOS 7.2(1)

1 WS-X4013

2 WS-X4148-RJ

3 WS-X4148-RJ

4 WS-X4148-RJ

5 WS-X4148-RJ

6 WS-X4232-GB-RJ

Every 10 mins logging the following:

2009 Jan 15 12:46:18 Eastern -05:00 %SYS-4-P2_WARN: 1/Astro(3/6) - consecutive m

anagement requests timed out.

2009 Jan 15 12:46:19 Eastern -05:00 %SYS-4-P2_WARN: 1/Astro(6/4) - consecutive m

anagement requests timed out.

2009 Jan 15 12:46:20 Eastern -05:00 %SYS-4-P2_WARN: 1/Astro(3/2) - consecutive m

anagement requests timed out.

2009 Jan 15 12:46:22 Eastern -05:00 %SYS-4-P2_WARN: 1/Astro(3/5) - consecutive m

anagement requests timed out.

Thank you


Re: Cat4K6 problem


The supervisor loosing communication with component on line card. Check this link..

Look for:

"%SYS-4-P2_WARN: 1/Astro(mod/port)" Section

Module might need replacement.



Hall of Fame Super Silver

Re: Cat4K6 problem


I agree here the result of error message decoder

3. %SYS-4-P2_WARN: 1/Astro(mod/port) The switch is generating %SYS-4-P2_WARN: 1/Astro(6/6)... messages.

This error message indicates that the Supervisor Engine has lost communication to a component on a line card. The Supervisor Engine keeps track of any timeouts that are associated with this communication.

Recommended Action: There are many possible causes associated with this condition. For more information on this error message and possible causes, refer to

Hope to help



Re: Cat4K6 problem

A lot of times this is caused when someone introduces a loop on the switch and ties up the supervisor so long that it can't talk to the linecards . Seeing its on more than 1 card I would suspect that . Check for loops . Do a show proc cpu , usually cpu will also be very high if this is happening and telnet access to switch will be slow . Doa show cdp nei and see if the switch sees "itself" on more than 1 port indicating a looped port . If you see this shutdown one of the ports which will break the loop and normalize the cpu . That being said it could still be a supervisor .