If you are running spanning tree, you might want to turn on udld aggressive mode in case of any gbics causing you some grief.
----- Original Message ----- From: "sam sneed" To: Sent: Monday, November 19, 2001 8:09 AM Subject: Re: spanning tree failure [7:26710] > To get an idea of the network topology, you can got to > http://www.v-man.net/vlan.gif > the switch i rebooted to solve problem was the bottom one. > > > ""sam sneed"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > I came into work this morning to find a segment of the network was down. > It > > was the segment connected to a 3548 switch. I suspecteda bridging loop but > > cannot verify. Does anyone know if there would be any "clues" i could look > > for? A power cycle fixed the problem but cleared the logs as well. Here > are > > the logs from a neighboring switch. Does anyone know how to interpret > these? > > > > 1y6w: %RTD-1-LINK_FLAP: GigabitEthernet0/2 link down/up 10 times per min > > 1y6w: %RTD-1-LINK_FLAP: GigabitEthernet0/2 link down/up 8 times per min > > 1y6w: %RTD-1-LINK_FLAP: GigabitEthernet0/2 link down/up 6 times per min > > 1y6w: %GIGASTACK-1-NO_LOOP_DETECT: The link neighbor of link 1 of > Gigastack > > GBIC in Gi0/2 did not respond to the loop detection request. If loop > > topology is deployed, make sure all switches in the stack are running the > > latest software. > > > > 1y6w: %GIGASTACK-1-NO_LOOP_DETECT: The link neighbor of link 2 of > Gigastack > > GBIC in Gi0/2 did not respond to the loop detection request. If loop > > topology is deployed, make sure all switches in the stack are running the > > latest software. > > > > Thanks alot. > > > > sam sneed Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=26720&t=26710 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
