[c-nsp] WS-C3750-48PS-E stackwise flap

[William]

Just looks like its the single cable from checking the syslogs for the
month, I'm going to swap out the offending cable and see if I can
replicate the issue in the lab with the 'faulty' cable.

Cheers,

On 19/09/2007, Jim McBurnett <jim at tgasolutions.com> wrote:
> I had a problem like that- and we replaced the cable.
> All was good afterwards.
> We put that cable on the lab stack, and the problem reoccurred..
> So I would replace the cable as a test- this kills the reset issue and a cable test with a single try.
> Then if it reoccurs, then we know it to be a stack port, or just place weirdness.
>
> At least the silver lining is that users don't know..
>
> Jim
>
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of William
> Sent: Wednesday, September 19, 2007 10:46 AM
> To: [c-nsp]
> Subject: [c-nsp] WS-C3750-48PS-E stackwise flap
>
> Hi,
>
> We have a pair of WS-C3750-48PS-E's in a standard stackwise configuration.
>
> Every so often on a daily basis we get the following msg in syslog:
>
> %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 2 has changed to state DOWN
> %STACKMGR-6-STACK_LINK_CHANGE: Stack Port 1 Switch 2 has changed to state UP
>
> At one point today it was happening every 2 minutes, then stopped and
> would appear a few hours later.
>
> We are running code 12.1(19)EA1c, which is abit dated but unable to
> spot any bugs that relate to this.
>
> Has anyone spotted this before? This is a remote site so I would like
> to leave the visual check/reseat of the cables last. More importantly
> no users are reporting an issue when these flaps happen.
>
> Thank you for your time.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>