beautypg.com

Span and rspan session limits, Default span and rspan configuration, Configuring span – IBM 12.1(22)EA6 User Manual

Page 339: Span configuration guidelines

background image

18-7

Cisco Systems Intelligent Gigabit Ethernet Switch Modules for the IBM BladeCenter, Software Configuration Guide

24R9746

Chapter 18 Configuring SPAN and RSPAN

Configuring SPAN

SPAN and RSPAN Session Limits

You can configure (and store in NVRAM) one local SPAN session or multiple RSPAN sessions on a
switch. The number of active sessions and combinations are subject to these restrictions:

SPAN or RSPAN source (rx, tx, both): 1 active session limit. (SPAN and RSPAN are mutually
exclusive on a source switch).

RSPAN source sessions have one destination per session with an RSPAN VLAN associated for that
session.

Each RSPAN destination session has one or more destination interfaces for each RSPAN VLAN that
they support.

RSPAN destination sessions are limited to two, or one if a local SPAN or a source RSPAN session
is configured on the same switch.

Default SPAN and RSPAN Configuration

Table 18-1

shows the default SPAN and RSPAN configuration.

Configuring SPAN

This section describes how to configure SPAN on your switch. It contains this configuration
information:

SPAN Configuration Guidelines, page 18-7

Creating a SPAN Session and Specifying Ports to Monitor, page 18-8

Creating a SPAN Session and Enabling Ingress Traffic, page 18-9

Removing Ports from a SPAN Session, page 18-11

SPAN Configuration Guidelines

Follow these guidelines when configuring SPAN:

SPAN sessions can coexist with RSPAN sessions within the limits described in the

“SPAN and

RSPAN Session Limits” section on page 18-7

.

The destination port cannot be a source port; a source port cannot be a destination port.

You can have only one destination port per SPAN session. You cannot have two SPAN sessions
using the same destination port.

Table 18-1

Default SPAN and RSPAN Configuration

Feature

Default Setting

SPAN state

Disabled.

Source port traffic to monitor

Both received and sent traffic (both).

Encapsulation type (destination port)

Native form (no encapsulation type header).

Ingress forwarding (destination port)

Disabled.