We have had a number of issues lately on our DWDM circuit and every time the circuit goes down we need to physically reset the gbic (Slide in and out) to enable the link to recover. In most instances it is only a blip on the DWDM however, this manual intervention is the only way to fully restore service.
Is there a certain configuration that is required on these types of interfaces to stop this.
I have attached the suspects port config for your opinion.
GigabitEthernet4/14 is up, line protocol is up (connected)
Hardware is C6k 1000Mb 802.3, address is 000a.f397.70ca (bia 000a.
Description:
Internet address is
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:08, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 126000 bits/sec, 39 packets/sec
5 minute output rate 1591000 bits/sec, 391 packets/sec
L2 Switched: ucast: 8150099153 pkt, 7257955078921 bytes - mcast: 1
121077872 bytes
L3 in Switched: ucast: 6436465962 pkt, 377125300975 bytes - mcast:
bytes mcast
L3 out Switched: ucast: 12878567404 pkt, 16658544727649 bytes
6437698001 packets input, 529212122856 bytes, 0 no buffer
Received 1216621 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
12879792036 packets output, 16894005760681 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
