06-18-2015 07:59 AM - edited 03-08-2019 12:36 AM
Hi all,
I have configured some 6509 ports in SPAN mode with an active monitor session. In particular I have configured one port on a catalyst and another port on another catalyst in order to sniff the traffic passing through this domain (composed by the two 6k).
On both catalysts, doing the "sh int gix/x" on the SPAN ports, the "GigabitEthernet1/29 is up, line protocol is down (monitoring)" message appears.
By contrast when I do "sh int status" on the first catalyst the SPAN port is in the monitoring status whereas on the second catalyst doing the "sh int status" the SPAN port is in "not connected" status.
This port's led is green, the cable is not broken so I would like to know if this second SPAN port is working properly also if the "sh int status" shows the "not connected status".
Hoping to have been clear I thank you in advance.
Silvio
Solved! Go to Solution.
06-18-2015 10:43 AM
Edit: bug below references 6000 switch.
CSCee77136
Same trouble description as SCSed18022 but references 6000 switch and sup engine.
*************************************************************************************************
Hi silvio1989,
Sounds identical to bug CSCed18022. Its referencing a 4000 switch and not a 6500 switch. I'll look for a similar bug related to a 6500 switch. See below.
Hope this helps,
Please rate helpful posts.
Thanks,
06-18-2015 08:45 AM
Hello silvio1989,
Rspan is needed to span traffic from one switch to another switch.
See link below.
Hope this helps,
Please rate helpful posts.
Thanks.
06-18-2015 09:00 AM
Hi Charles,
I have always configured SPAN in this way:
monitor session 5 source vlan 1040 , 1064 , 1123 , 1143 , 1163
monitor session 5 destination interface Gi1/29
with
interface GigabitEthernet1/29
description Sonda Shark
no ip address
no snmp trap link-status
switchport
switchport mode access
no cdp enable
end
I have encountered this issue in the sh int status just this time... The strange thing is that if I do sh int gi1/29 I see "5 minute output rate 40378000 bits/sec, 3346 packets/sec" so I reckon that it is spanning traffic.
But why the port is in not connected status!? :O
06-18-2015 10:13 AM
Are you saying, with sh int gi1/29 -- it says "monitoring"
sh int status ---> not connected ...
is this your questions.
Please post the output also here for better understanding.
06-19-2015 01:03 AM
Hi!
Exactely! This is the issue!
Here there are the output:
#sh int gi1/29
GigabitEthernet1/29 is up, line protocol is down (monitoring)
Hardware is C6k 1000Mb 802.3, address is 0011.9336.9c44 (bia 0011.9336.9c44)
Description: Sonda Shark
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 2/255, rxload 1/255
Encapsulation ARPA, loopback not set
Full-duplex, 1000Mb/s
input flow-control is off, output flow-control is on
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters 6y30w
Input queue: 0/2000/12/0 (size/max/drops/flushes); Total output drops: 4
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 8212000 bits/sec, 714 packets/sec
3129242757 packets input, 839789764257 bytes, 0 no buffer
Received 13 broadcasts, 0 runts, 0 giants, 0 throttles
12 input errors, 2 CRC, 0 frame, 1195 overrun, 0 ignored
0 input packets with dribble condition detected
6867195564 packets output, 2541371809115 bytes, 0 underruns
4 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
#sh int status | i Gi1/29
Gi1/29 Sonda Shark notconnect 1 a-full a-1000/10/100/1000BaseT
I have tried to shut/no shut the port, I changed the speed and the duplex but nothing happened.
06-18-2015 10:43 AM
Edit: bug below references 6000 switch.
CSCee77136
Same trouble description as SCSed18022 but references 6000 switch and sup engine.
*************************************************************************************************
Hi silvio1989,
Sounds identical to bug CSCed18022. Its referencing a 4000 switch and not a 6500 switch. I'll look for a similar bug related to a 6500 switch. See below.
Hope this helps,
Please rate helpful posts.
Thanks,
06-19-2015 01:07 AM
Hi,
I hope so.. but how can I justify this behaviour if there is nothing officially related to this bug on CISCO 600 series !?
06-19-2015 03:23 AM
Ah ok! I had not seen the first two lines of your answer.. so... the case is closed! :D Thank you very much!
06-19-2015 03:30 AM
Your welcome.
10-19-2017 03:48 PM
Hi All,
Will SNMP trap work on SPAN destination port?
Regards,
Godwin. S
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: