RE: monitor session question (plus outputting to a trunk)

From: Danny.Andaluz@triaton-na.com
Date: Sat Jan 31 2004 - 03:10:01 GMT-3


Thanks, Mike.

Danny

-----Original Message-----
From: Mike Williams [mailto:ccie2be@swbell.net]
Sent: Friday, January 30, 2004 11:41 PM
To: Andaluz, Danilo, Triaton/NA; ccielab@groupstudy.com
Subject: RE: monitor session question (plus outputting to a trunk)

What you see is correct. When you set a span port destination, it should
show up/down (monitoring)...... On a few switches you could type a command
that would allow the monitoring device to also send traffic into the
switchport (therefore being "on the network" as normal while monitoring).
But all of our 3550s, Cat4000/4500, and Cat6500s show up/down (monitoring)
on all of our span ports.

I was just playing with that today trying to get our monitor session to
output dot1q tagged frames by setting the session destination to be a trunk
(unconditionally)...... Cisco says that outputting tagged (or ISL
encapsulated) frames is possible on the Cat6000/6500 starting with 12.1(13)E
and later, but we have 12.1(13)E9 on our 6500s (native) and whenever I setup
the output port as a trunk, as soon as I make it a span session destination,
trunking is disabled (as shown by "show int trunk mod <#>" (according to
all Cisco docs I read, this disabling of the trunking on a session
destination is normal for IOS prior to 12.1(13)E). Also can't find any
evidence that you can do this dot1q tagged spanning on the Cat4000/4500s
(running IOS, not CatOS).........

Mike W.

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Danny.Andaluz@triaton-na.com
Sent: Friday, January 30, 2004 5:55 PM
To: ccielab@groupstudy.com
Subject: monitor session question

Hey, Group.
 
I'm trying to setup a span port on my 3550. Here is my config:
 
monitor session 1 source interface Fa0/2
monitor session 1 destination interface Fa0/22

For some reason, the switch port shows up/down (monitoring). At first it
said up/up (monitoring) but then went down. Does this have anything to do
with the software I'm using to analyze traffic? I think I have the monitor
session configured according to the Doc CD.
 
 
CAT1#SH INT F0/22
FastEthernet0/22 is up, line protocol is down (monitoring)
  Hardware is Fast Ethernet, address is 000a.8a14.d777 (bia
000a.8a14.d777)
  MTU 1500 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)
  Full-duplex, 100Mb/s



This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:52 GMT-3