Operating instructions

170 Cisco Systems Intelligent Gigabit Ethernet Switch Module
Step 3.1.4:
Configure RSPAN on
port g0/19 on CIGESM1
.
RSPAN can be configured several
ways to capture traffic from a
single port, multiple ports, or even
VLANs. This step does not
discuss all of the possibilities, butit
gives one specific example: to
capture all traffic to and from port
g0/1 such that it can be captured
and viewed from a sniffer attached
to 6500-1, port g2/2. Port g0/19
on the Cisco Systems IGESM is
used as the reflector port for this
example. The necessary
commands for the 6500-1 are
shown in Table 7-15 on page 165.
Important: We do not
recommend that you use RSPAN
on a Cisco Systems IGESM
running Release 12.1(14)AY. This
release has an issue with RSPAN
that could disrupt network
communications. For more
information about this issue, see
Appendix A, “Hints and tips” on
page 227.
Create the RSPAN VLAN and set it to
support RSPAN:
vlan 500
remote-span
Configure the port to be monitored
(g0/1 in this case), as well as the port
performing the function of the
reflector-port (g0/19):
monitor session 1 source interface
g0/1
monitor session 1 destination
remote vlan 500 reflector-port
g0/19
The two monitor commands listed
above should be each on their own,
single line.
Important: A remote VLAN used by
RSPAN must not be used by on any
other access ports on the Cisco
Systems IGESM or be defined as the
management VLAN on the Cisco
Systems IGESM. Review the rules for
setting up RSPAN mentioned at the
beginning of this topology example.
CMS does not support configuring
RSPAN at this time. Use the CLI to
configure RSPAN.
Step 3.1.5:
Configure 802.1Q
trunking to BladeServer1 and add
allowed VLANs
.
int g0/1
switchport trunk allowed vlan
2,10,15
Note that the VLAN numbers might be
wrapped in this document; they should
be on the same line as the command.
This allows VLANs 2, 10, and 15 to
reach BladeServer1’s first NIC.
1. In the top menu bar, click VLAN →
VLAN.
2. Click port Gi0/1.
3. Click Modify.
4. In the Trunk-Allowed VLAN field,
enter 2,10,15.
5. Click OK.
6. Click Apply or OK.
Important: As noted in step 3.1.3, a
limitation in the current version of CMS
exists where it will always include
VLANs 1 and 1001 through 1005. This
can cause a mismatch with the setting
on the blade server side and result in
the trunk not working as expected. The
only solution at this time is to go into the
CLI and run the switchport trunk
allowed vlan command with the
desired settings, as shown in the CLI
section for this step.
Description and comments Actions via IOS CLI for CIGEMS1 Actions via CMS for CIGEMS1