From: Spyros Kranis (skranis@algosystems.gr)
Date: Fri Jul 15 2005 - 16:43:29 GMT-3
Omer,
Please mention the following:
SW1(config)#monitor session 1 destination remote vlan 888
% Incomplete command.
SW1(config)#monitor session 1 destination remote vlan 888 ?
reflector-port Remote SPAN reflector port
SW1(config)#monitor session 1 destination remote vlan 888
Regards
Skra
-----Original Message-----
From: Ben-Shalom, Omer [mailto:omer.ben-shalom@intel.com]
Sent: Friday, July 15, 2005 10:07 PM
To: Scott Morris; Spyros Kranis; Amit Jain; ccielab@groupstudy.com
Subject: RE: Monitor session - reflector port
The question is looking for RSPAN, RSPAN uses a dedicated VLAN (say 999) to
move all the traffic to the remote monitor/sniffer
On one switch you set your monitor source as usual but the monitor
destination is the VLAN
monitor sess 1 source interface fa0/1
monitor sess 1 destination remote vlan 999
On the other switch the monitor source is the VLAN and the destination is as
usual.
monitor sess 1 source remote vlan 999
monitor sess 1 destination interface fa0/22
Hope this helps.
Thanks,
Omer.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott Morris
Sent: Thursday, July 14, 2005 6:17 PM
To: 'Spyros Kranis'; 'Amit Jain'; ccielab@groupstudy.com
Subject: RE: Monitor session - reflector port
Whenever you choose a reflector port, you are borrowing the ASICs for the
monitoring process. That pretty well kills the line for normal usage. So
picking a trunk would not be a good idea!
Typically you choose a port that is unused (Cisco's recommendation) or that
belongs to someone you don't like (my addition!). ;)
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Spyros Kranis
Sent: Thursday, July 14, 2005 11:04 AM
To: 'Amit Jain'; ccielab@groupstudy.com
Subject: RE: Monitor session - reflector port
Amit,
Of course you can configure it as a reflector port . Cisco states do NOT.
The switch accepts it!
But the show interface command will inform you that the line is up protocol
is down (monitoring).
In your lab maybe you have multiple trunks between the switches so the
traffic would go from the other trunks , not the one configured to be a
reflector port.
TIA
skra
-----Original Message-----
From: Amit Jain [mailto:netsteps@rediffmail.com]
Sent: Thursday, July 14, 2005 6:00 PM
To: Spyros Kranis; ccielab@groupstudy.com
Subject: Re: Monitor session - reflector port
I guess you can configure a reflector port to be a trunk port. I did the
scenario today and config was taken in by switches but not tested this using
sniffer in real lab.
Amit
----- Original Message -----
From: "Spyros Kranis" <skranis@algosystems.gr>
To: <ccielab@groupstudy.com>
Sent: Wednesday, July 13, 2005 3:05 PM
Subject: Monitor session - reflector port
> Hi group,
> I have both switches SW1 - SW2 that are connected through ONLY port FA0/24
> that is configured as trunk to each other.
> At lab 44 of ipexp states:
>
> The IT department has a request to analyze all the traffic on SW1 Port
F0/1.
> The network analyzer is connected to port F0/22 on SW2, Configure the
> switches to accommodate this request.
>
> If I configure the monitor command on SW1 with the reflector port to be
the
> fa0/24 (the only trunk port)the port will be put in up down. Cisco states
> that the reflector port cannot be a trunk port.
>
> So what can we do in this situation?
> Do we have to configure a reflector port to be another port not the trunk?
>
> At the real lab exam, Maybe a question to the proctor regarding this
issue?
>
> Any thoughts?
>
> TIA
>
> Skra
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:30 GMT-3