Ok, if you've seen my other recent thread, ignore it.
Whenever I create a SPAN session on the Cisco 1812, when I set the destination port for a SPAN session, the destination port always shows all egress traffic on all ports (the tx of all the ports.) Even when I tell it specifically to not show the tx of a port it continues to do so.
For example:
monitor session 1 destination interface fa 2
And I get all TX traffic from all ports.
If I do something like:
monitor session 1 source interface fa 7 rx
The destination port continues to monitor tx traffic as well, and simply begins to monitor RX traffic as well.
Then:
no monitor session 1 source interface fa 7
It stops monitoring RX traffic on that port, but continues to monitor TX traffic.
I can't find any documentation that states why (or if) it works like this. Is it a limitation on the 1812 router that doesn't give me an error message when I try to stop monitoring TX traffic? Or is something wrong with the IOS?
Whenever I create a SPAN session on the Cisco 1812, when I set the destination port for a SPAN session, the destination port always shows all egress traffic on all ports (the tx of all the ports.) Even when I tell it specifically to not show the tx of a port it continues to do so.
For example:
monitor session 1 destination interface fa 2
And I get all TX traffic from all ports.
If I do something like:
monitor session 1 source interface fa 7 rx
The destination port continues to monitor tx traffic as well, and simply begins to monitor RX traffic as well.
Then:
no monitor session 1 source interface fa 7
It stops monitoring RX traffic on that port, but continues to monitor TX traffic.
I can't find any documentation that states why (or if) it works like this. Is it a limitation on the 1812 router that doesn't give me an error message when I try to stop monitoring TX traffic? Or is something wrong with the IOS?