We have a BladeCenter which has a internal switch IGESM (version 12.1(22)EA6a).
the IGESM internal side connects some blade servers.
IGESM external side connects a distribution server.
bladeserver <--> bladeswitch <--> distribution server
when bootup, the bladeserver need to get it's IP(via DHCP) and image from the distribution server.
Now the problem is as soon as the bladeserver get the IP address, the line protocol on the bladeswitch is flapping and then the port was error-disabled as link flap.
My question is why the line protocol is flapping? (AS I know, after the line protocol had been negotiated between bladeserver and bladeswitch, the status would be stable.) Please give me some tips about it.
Here is the logging message:
Apr 13 15:28:29.198 CHN: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to down
Apr 13 15:28:35.430 CHN: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to up
Apr 13 15:28:38.222 CHN: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to down
Apr 13 15:28:41.322 CHN: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, changed state to up
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...