Ingress option when configuring SPAN/RSPAN

From: Filyurin, Yan (yan.filyurin@eds.com)
Date: Tue Jul 10 2007 - 14:56:27 ART


Hello Group Study. I was wondering if you could help me understand or
point me to another thread that explains and it deals with SPAN and
RSPAN configuration. All seems well understood except the ingress
option that can be configured when configuring span destination.
From what I understand destination port becomes a pure egress port that
sends captured traffic to network analyzer, but in certain cases either
when the analyzer is using that interface both for management and
monitoring or it is an IDS that needs to react to what it seems traffic
has to come back from it. And I am not sure I understand all the
options. So I was wondering if someone could help me understand them.

For example it is possible to configure dotq vlan vlan_id, which would
imply that traffic from the analyzer would arrive with 802.1q tag and
that vlan_id would be part of the tag. In case of untagged vlan vlan_id
that traffic would come untagged and the switch would treat as it would
be traffic on the access port. And then there is also ISL option where
it would arrive ISL encapsulated. Yet how come you can't specify ISL
vlan in that case? Besides that, am I understanding the other options
correctly?

Thank you



This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART