cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
18595
Views
15
Helpful
1
Replies

GigabitEthernet2/0/1 is down, line protocol is down (monitoring)

LAAsm2012b
Beginner
Beginner

Csico switch 3750, when connect a device to this port, the light on the switch is green, but the device doesn't get IP, and doesn see it belongs to any VLAN in sh vlan.

sh int g2/0/1 got:

GigabitEthernet2/0/1 is down, line protocol is down (monitoring)

  Hardware is Gigabit Ethernet, address is x.x..x (bia x.x.x)

  MTU 5000 bytes, BW 100000 Kbit, DLY 100 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX

  input flow-control is off, output flow-control is unsupported

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input never, output 00:34:41, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 209

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     0 packets input, 0 bytes, 0 no buffer

     Received 0 broadcasts (0 multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 0 multicast, 0 pause input

     0 input packets with dribble condition detected

     39158 packets output, 13651510 bytes, 0 underruns

     0 output errors, 0 collisions, 1 interface resets

     0 babbles, 0 late collision, 0 deferred

     0 lost carrier, 0 no carrier, 0 PAUSE output

     0 output buffer failures, 0 output buffers swapped out

   

can anyone pls tell me how to fix this? thx.

1 Accepted Solution

Accepted Solutions

Peter Paluch
Hall of Fame Cisco Employee Hall of Fame Cisco Employee
Hall of Fame Cisco Employee

Hello,

According to the output, the port is a part of a monitor session (a SPAN session) as a destination port. Look for "monitor session" commands in your configuration that refer to the port, and if you do not need this monitoring session, you may remove it from your configuration. That will make the port work normally again.

Best regards,
Peter

View solution in original post

1 Reply 1

Peter Paluch
Hall of Fame Cisco Employee Hall of Fame Cisco Employee
Hall of Fame Cisco Employee

Hello,

According to the output, the port is a part of a monitor session (a SPAN session) as a destination port. Look for "monitor session" commands in your configuration that refer to the port, and if you do not need this monitoring session, you may remove it from your configuration. That will make the port work normally again.

Best regards,
Peter

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers