From: Jason Morris (mcnever@gmail.com)
Date: Sun Jan 11 2009 - 22:28:21 ARST
ok, i'm having some issues with the 'ingress' portion of the monitor
it would appear. I've done this 100 times in real life and now i
can't seem to get it to work in a lab. am i missing something or does
ingress work differently on the 3560 or what? thoughts?
150.100.220.7 is connected to f0/7 of this switch.
see the output below
Cat-2(config)#do sho run | i monitor
monitor session 1 source interface Fa0/15
monitor session 1 destination interface Fa0/7 ingress untagged vlan 567
Cat-2(config)#do sho run int f0/7
Building configuration...
Current configuration : 85 bytes
!
interface FastEthernet0/7
switchport access vlan 567
switchport mode access
end
Cat-2(config)#do sho run int vlan 567
Building configuration...
Current configuration : 68 bytes
!
interface Vlan567
ip address 150.100.220.12 255.255.255.240
end
Cat-2(config)#do ping 150.100.220.7 repeat 15
Type escape sequence to abort.
Sending 15, 100-byte ICMP Echos to 150.100.220.7, timeout is 2 seconds:
...............
Success rate is 0 percent (0/15)
Cat-2(config)#no monitor session 1 destination int f0/7
Cat-2(config)#do ping 150.100.220.7 repeat 15
Type escape sequence to abort.
Sending 15, 100-byte ICMP Echos to 150.100.220.7, timeout is 2 seconds:
..........!!!!!
Success rate is 33 percent (5/15), round-trip min/avg/max = 1/2/8 ms
Cat-2(config)#
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:43:37 ARST