-> bridge msti 3 priority 12288
Even though the above command is accepted in the 1x1 mode, the new priority value does not take effect until the switch mode is changed to flat mode. Note that explicit commands using the cist and msti keywords are required to define an MSTP configuration. Implicit commands are only allowed for defining STP or RSTP configurations.

page 2-10

Implicit commands resemble previously implemented Spanning Tree commands, but apply to the appropriate instance based on the current mode and protocol that is active on the switch. For example, if the 1x1 mode is active, the instance number specified with the following command implies a VLAN ID:
-> bridge 255 priority 16384
If the flat mode is active, the single flat mode instance is implied and thus configured by the command. Since the flat mode instance is implied in this case, there is no need to specify an instance number. For example, the following command configures the protocol for the flat mode instance:
-> bridge protocol mstp
Similar to previous releases, it is possible to configure the flat mode instance by specifying 1 for the instance number (e.g., bridge 1 protocol rstp). However, this is only available when the switch is already running in the flat mode and STP or RSTP is the active protocol. Note. When a snapshot is taken of the switch configuration, the explicit form of all Spanning Tree commands is captured. For example, if the priority of MSTI 2 was changed from the default value to a priority of 16384, then bridge msti 2 priority 16384 is the command captured to reflect this in the snapshot file. In addition, explicit commands are captured for both flat and 1x1 mode configurations. For more information about Spanning Tree configuration commands as they apply to all supported protocols (STP, RSTP, and MSTP), see Chapter 7, Configuring Spanning Tree Parameters.
Understanding Spanning Tree Modes
The switch can operate in one of two Spanning Tree modes: flat and 1x1. The flat mode provides a Common Spanning Tree (CST) instance that applies across all VLANs by default. This mode supports the use of the STP (802.1D), RSTP (802.1w), and MSTP. MSTP allows the mapping of one or more VLANs to a single Spanning Tree instance. The 1x1 mode is an Alcatel-Lucent proprietary implementation that automatically calculates a separate Spanning Tree instance for each VLAN configured on the switch. This mode only supports the use of the STP and RSTP protocols. Although MSTP is not supported in the 1x1 mode, it is possible to define an MSTP configuration in this mode using explicit Spanning Tree commands. See Using Spanning Tree Configuration Commands on page 2-10 for more information about explicit commands. By default, a switch is running in the 1x1 mode and using the 802.1D protocol when it is first turned on. See Chapter 7, Configuring Spanning Tree Parameters, for more information about Spanning Tree modes.

-> port-security 3/6-12 4/6-12 5/6-12 enable
2 Set the total number of learned MAC addresses allowed on the same ports to 25 using the following
-> port-security 3/6-12 4/6-12 5/6-12 maximum 25
3 Configure the amount of time in which source learning is allowed on all LPS ports to 30 minutes using

the following command:

-> port-security shutdown 30
4 Select shutdown for the LPS violation mode using the following command:
-> port-security 3/6-12 4/6-12 5/6-12 violation shutdown
Note. Optional. To verify LPS port configurations, use the port-security learn-trap-threshold command. For example:
-> show port-security Port: 1/30 Operation Mode Max Bridged MAC allowed Max Filtered MAC allowed Low End of MAC Range High End of MAC Range Violation Setting
: DISABLED, : 1, : 5, : 00:00:00:00:00:00, : ff:ff:ff:ff:ff:ff, : RESTRICT,
MAC VLAN MAC TYPE -------------------+------+------------------00:20:95:00:fa:5c 1 STATIC
To verify the new source learning time limit value, use the show port-security shutdown command. For example:
-> show port-security shutdown LPS Shutdown Config = 2 min Convert-to-static = DISABLE Remaining Learning Window = 110 sec

page 3-3

Learned Port Security Overview
Learned Port Security (LPS) provides a mechanism for controlling network device access on one or more switch ports. Configurable LPS parameters allow the user to restrict the source learning of host MAC addresses to:
A specific amount of time in which the switch allows source learning to occur on all LPS ports. A maximum number of learned MAC addresses allowed on the port. A list of configured authorized source MAC addresses allowed on the port.
Additional LPS functionality allows the user to specify how the LPS port handles unauthorized traffic. The following two options are available for this purpose:
Block only traffic that violates LPS port restrictions; authorized traffic is forwarded on the port. Disable the LPS port when unauthorized traffic is received; all traffic is stopped and a port reset is
required to return the port to normal operation. LPS functionality is supported on the following Ethernet and Gigabit Ethernet port types:

Number of 1x1 Spanning Tree instances supported Number of Multiple Spanning Tree Instances (MSTI) supported Number of Ring Rapid Spanning Tree rings supported CLI Command Prefix Recognition
Parameter Description Spanning Tree operating mode Spanning Tree protocol BPDU switching status Priority value for the Spanning Tree instance Command bridge mode bridge protocol bridge bpdu-switching bridge priority Default 1x1 (a separate Spanning Tree instance for each VLAN) RSTP (802.1w) Disabled seconds 20 seconds
Hello time interval between each bridge hello time BPDU transmission Maximum aging time allowed for Spanning Tree information learned from the network Spanning Tree port state transition time Automatic VLAN Containment bridge max age

page 7-3

Parameter Description

Command

Default disabled
Capability of 1X1 mode to inter- bridge mode 1x1 pvst+ operate with Ciscos PVST+ mode.
Parameter Description Spanning Tree port administrative state Spanning Tree port priority value Spanning Tree port path cost Path cost mode Command bridge slot/port bridge slot/port priority bridge slot/port path cost bridge path cost mode Default Enabled (cost is based on port speed) Auto (16-bit in 1x1 mode and STP or RSTP flat mode, 32-bit in MSTP flat mode) Dynamic (Spanning Tree Algorithm determines port state) auto
Port state management mode Type of port connection

bridge slot/port mode

Type of BPDU to be used on a port when bridge port pvst+ the 1X1 mode is configured to interoperate with Ciscos PVST+ mode.
Multiple Spanning Tree (MST) Region Defaults
Although the following parameter values are specific to MSTP, they are configurable regardless of which mode (flat or 1x1) or protocol is active on the switch. Parameter Description The MST region name The revision level for the MST region The maximum number of hops authorized for the region The number of Multiple Spanning Tree Instances (MSTI) The VLAN to MSTI mapping Command bridge mst region name bridge mst region revision level bridge mst region max hops bridge msti bridge msti vlan Default blank 1 (flat mode instance) All VLANs are mapped to the Common Internal Spanning Tree (CIST) instance

page 7-4

Ring Rapid Spanning Tree Defaults
The following parameter value is specific to RRSTP and is only configurable when the flat mode is active on the switch. Parameter Description Ring status Command bridge rrstp ring Default Disabled

page 7-5

Spanning Tree Overview
Alcatel-Lucent switches support the use of the 802.1D Spanning Tree Algorithm and Protocol (STP), the 802.1w Rapid Spanning Tree Algorithm and Protocol (RSTP), the 802.1Q 2005 Multiple Spanning Tree Protocol (MSTP), and the Ring Rapid Spanning Tree Protocol (RRSTP). RSTP expedites topology changes by allowing blocked ports to transition directly into a forwarding state, bypassing listening and learning states. This provides rapid reconfiguration of the Spanning Tree in the event of a network path or device failure. The 802.1w standard is an amendment to the 802.1D document, thus RSTP is based on STP. Regardless of which one of these two protocols a switch or VLAN is running, it can successfully interoperate with other switches or VLANs. 802.1Q 2005 is a new version of MSTP that combines the 802.1D 2004 and 802.1S protocols. This implementation of 802.1Q 2005 also includes improvements to edge port configuration and provides administrative control to restrict port role assignment and the propagation of topology change information through bridge ports. MSTP is an enhancement to the 802.1Q Common Spanning Tree (CST), which is provided when an Alcatel-Lucent switch is running in the flat Spanning Tree operating mode. The flat mode applies a single spanning tree instance across all VLAN port connections on a switch. MSTP allows the configuration of Multiple Spanning Tree Instances (MSTIs) in addition to the CST instance. Each MSTI is mapped to a set of VLANs. As a result, flat mode can now support the forwarding of VLAN traffic over separate data paths. RRSTP is faster than MSTP. It is used in a ring topology where bridges are connected in a point to point manner. This protocol identifies the bridge hosting the alternate (ALT) port in lesser convergence time. This ALT port is changed to the forwarding state immediately without altering the MSTP state to enable the data path. The RRSTP frame travels from the point of failure to the bridge hosting the ALT port in both the directions. The MAC addresses matching the ports in the ring are flushed to make the data path convergence much faster than normal MSTP. This section provides a Spanning Tree overview based on RSTP operation and terminology. Although MSTP is based on RSTP, see Chapter 2, Using 802.1Q 2005 Multiple Spanning Tree, for specific information about configuring MSTP. For more information about using RRSTP, see Using RRSTP on page 7-39.

connection these ports provides is redundant (backup) and has a higher path cost value than the 2/3 to 3/8 connection between the same two switches. As a result, a network loop is avoided.
The port 3/2 connection on Switch B to port 3/10 on Switch C is also in a discarding (blocking) state,
as the connection these ports provides has a higher path cost to root Switch D than the path between Switch B and Switch A. As a result, a network loop is avoided.

page 7-11

Spanning Tree Operating Modes
The switch can operate in one of two Spanning Tree modes: flat and 1x1. Both modes apply to the entire switch and determine whether a single Spanning Tree instance is applied across multiple VLANs (flat mode) or a single instance is applied to each VLAN (1x1 mode). By default, a switch is running in the 1x1 mode when it is first turned on. Use the bridge mode command to select the flat or 1x1 Spanning Tree mode.The switch operates in one mode or the other, however, it is not necessary to reboot the switch when changing modes. To determine which mode the switch is operating in, use the bridge rrstp ring vlan-tag command. For more information about this command, see the OmniSwitch CLI Reference Guide.
Using Flat Spanning Tree Mode
Before selecting the flat Spanning Tree mode, consider the following:
If STP (802.1D) is the active protocol, then there is one Spanning Tree instance for the entire switch;
port states are determined across VLANs. If MSTP (802.1s) is the active protocol, then multiple instances up to a total of 17 are allowed. Port states, however, are still determined across VLANs.
Multiple connections between switches are considered redundant paths even if they are associated with

different VLANs.

Spanning Tree parameters are configured for the single flat mode instance. For example, if Spanning
Tree is disabled on VLAN 1, then it is disabled for all VLANs. Disabling STP on any other VLAN, however, only exclude ports associated with that VLAN from the Spanning Tree Algorithm.
Fixed (untagged) and 802.1Q tagged ports are supported in each VLAN. BPDU, however, are always

untagged.

When the Spanning Tree mode is changed from 1x1 to flat, ports still retain their VLAN associations
but are now part of a single Spanning Tree instance that spans across all VLANs. As a result, a path that was forwarding traffic in the 1x1 mode may transition to a blocking state after the mode is changed to flat. To change the Spanning Tree operating mode to flat, enter the following command:
The following diagram shows a flat mode switch with STP (802.1D) as the active protocol. All ports, regardless of their default VLAN configuration or tagged VLAN assignments, are considered part of one Spanning Tree instance. To see an example of a flat mode switch with MSTP (802.1s) as the active protocol, see Chapter 2, Using 802.1Q 2005 Multiple Spanning Tree.

page 7-27

The following is a summary of Spanning Tree port configuration commands. For more information about these commands, see the OmniSwitch CLI Reference Guide. Commands bridge slot/port Type Implicit Used for. Configuring the port Spanning Tree status for a VLAN instance when the 1x1 mode is active or the single Spanning Tree instance when the flat mode is active. Configuring the port Spanning Tree status for the single flat mode instance. Configuring the port Spanning Tree status for a VLAN instance. Configuring the port priority value for a VLAN instance when the 1x1 mode is active or the single Spanning Tree instance when the flat mode is active. Configuring the port priority value for the single flat mode instance. Configuring the port priority value for a Multiple Spanning Tree Instance (MSTI). Configuring the port priority value for a VLAN instance. Configuring the port path cost value for a VLAN instance when the 1x1 mode is active or the single Spanning Tree instance when the flat mode is active. Configuring the port path cost value for the single flat mode instance. Configuring the port path cost value for a Multiple Spanning Tree Instance (MSTI). Configuring the port path cost value for a VLAN instance. Configuring the port Spanning Tree mode (dynamic or manual) for a VLAN instance when the 1x1 mode is active or the single Spanning Tree instance when the flat mode is active. Configuring the port Spanning Tree mode (dynamic or manual) for the single flat mode instance. Configuring the port Spanning Tree mode (dynamic or manual) for a VLAN instance. Configuring the port connection type for a VLAN instance when the 1x1 mode is active or the single Spanning Tree instance when the flat mode is active. Configuring the port connection type for the single flat mode instance. Configuring the port connection type for a VLAN instance.
bridge cist slot/port bridge 1x1 slot/port bridge slot/port priority
bridge cist slot/port priority bridge msti slot/port priority bridge 1x1 slot/port priority bridge slot/port path cost
Explicit Explicit Explicit Implicit
bridge cist slot/port path cost bridge msti slot/port path cost bridge 1x1 slot/port path cost bridge slot/port mode
Explicit Explicit Explicit Explicit
bridge cist slot/port mode bridge 1x1 slot/port mode bridge slot/port connection
Implicit Explicit Explicit
bridge cist slot/port connection bridge 1x1 slot/port connection

Implicit Explicit

page 7-28

Commands

Used for. Configures the connection type for a port or an aggregate of ports for the flat mode Common and Internal Spanning Tree (CIST). Configures the connection type for a port or an aggregate of ports for a 1x1 mode VLAN instance. Configures a port or an aggregate of ports for the flat mode Common and Internal Spanning Tree (CIST) as an edge port, automatically. Configures a port or an aggregate of ports for the 1x1 mode VLAN instance as an edge port, automatically. Configures the restricted role status for a port or an aggregate of ports for the flat mode Common and Internal Spanning Tree (CIST) as a restricted role port. Configures a port or an aggregate of ports for the 1x1 mode VLAN instance as a restricted role port. Configures a port or an aggregate of ports for the flat mode Common and Internal Spanning Tree (CIST) to support the restricted TCN capability. Configures a port or an aggregate of ports for the 1x1 mode VLAN instance to support the restricted TCN capability. Limits the transmission of BPDU through a given port for the flat mode Common and Internal Spanning Tree (CIST). Limits the transmission of BPDU through a given port for the 1x1 mode VLAN instance. Configures the type of BPDU to be used on a port when PVST+ mode is enabled.

page 8-3

Customer Domain Provider Domain Operator Domain Operator Domain Operator Domain

Access Network

Core Network
Customer Network Maintenance End Point Maintenance Intermediate Point

Customer Network

CFM Monitoring Domains
Ethernet OAM Connectivity Fault Management consists of four types of messages that help in monitoring and debugging Ethernet networks. These messages are described below:
Continuity Check Messages (CCMs)These are multicast messages exchanged periodically between
MEPs. They allow MEPs to detect loss of service connectivity amongst themselves and discover other MEPs within a domain. These messages also enable MIPs to discover MEPs.
Linktrace Messages(LTMs)These messages are transmitted by a MEP to trace the path to a destina-
tion MEP. They are requested by an administrator.
Loopback Messages (LBMs)These messages are transmitted by a MEP to a specified MIP or MEP.
They are requested by an administrator.
Alarm Indication Signal (AIS) MessagesThese messages send alerts to other devices in the network
to notify a fault in the network. Note. AIS messages are not supported in this release.

page 8-4

MIP CCM Database Support
Per section 19.4 of the IEEE 802.1ag 5.2 draft standard, an MHF may optionally maintain a MIP CCM database as it is not required for conformance to this standard. A MIP CCM database, if present, maintains the information received from the MEPs in the MD and can be used by the Linktrace Protocol. This implementation of Ethernet OAM does not support the optional MIP CCM database. As per section 19.4.4 of the IEEE 802.1ag 5.2 draft standard, LTM is forwarded on the basis of the source learning filtering database. Because the MIP CCM database is not supported in this release, MIPs will not forward LTM on blocked egress ports.

page 8-5

Quick Steps for Configuring Ethernet OAM
The following steps provide a quick tutorial on how to configure Ethernet OAM. Each step describes a specific operation and provides the CLI command syntax for performing that operation.

RIP Forced Hold-Down Interval ip rip force-holddowntimer

page 20-2

Quick Steps for Configuring RIP Routing
To forward packets to a device on a different VLAN, you must create a router port on each VLAN. To route packets by using RIP, you must enable RIP and create a RIP interface on the router port. The following steps show you how to enable RIP routing between VLANs from scratch. If active VLANs and router ports have already been created on the switch, go to Step 7.
5 Configure an IP interface to enable IP routing on a VLAN by using the ip interface. For example:
6 Configure an IP interface to enable IP routing on a VLAN by using the ip interface. For example:
7 Load RIP into the switch memory by using the ip load rip command. For example:

-> ip load rip

8 Enable RIP on the switch by using the ip rip status command. For example:
-> ip rip status enable
9 Create a RIP interface on VLAN 1 by using the ip rip interface command. For example:
-> ip rip interface vlan-1
10 Enable the RIP interface by using the ip rip interface status command. For example:
-> ip rip interface vlan-1 status enable
11 Create an RIP interface on VLAN 2 by using the ip rip interface command. For example:
-> ip rip interface vlan-2
Note. For more information on VLANs and router ports, see Chapter 4, Configuring VLANs.

page 20-3

RIP Overview
In switching, traffic may be transmitted from one media type to another within the same VLAN. Switching happens at Layer 2, the link layer; routing happens at Layer 3, the network layer. In IP routing, traffic can be transmitted across VLANs. When IP routing is enabled, the switch uses routing protocols to build routing tables that keep track of stations in the network and decide the best path for forwarding data. When the switch receives a packet to be routed, it strips off the MAC header and examines the IP header. It looks up the source/destination address in the routing table, and then adds the appropriate MAC address to the packet. Calculating routing tables and stripping/adding MAC headers to packets is performed by switch software. IP is associated with several Layer 3 routing protocols. RIP is built into the base code loaded onto the switch. Others are part of Alcatel-Lucents optional Advanced Routing Software. IP supports the following IP routing protocols:
RIPAn IGP that defines how routers exchange information. RIP makes routing decisions by using a
least-cost path method. RIPv1 and RIPv2 services allow the switch to learn routing information from neighboring RIP routers. For more information and instructions for configuring RIP, see RIP Routing on page 20-6.

-> policy rule rule5 log interval 1500
Note that setting the log interval time to 0 specifies to log as often as possible.

Deleting Rules

To remove a policy rule, use the no form of the command.
-> no policy rule rule1
The rule will be deleted after the next qos apply.
Verifying Policy Configuration
To view information about policy rules, conditions, and actions configured on the switch, use the following commands: show policy condition Displays information about all pending and applied policy conditions or a particular policy condition configured on the switch. Use the applied keyword to display information about applied conditions only. Displays information about all pending and applied policy actions or a particular policy action configured on the switch. Use the applied keyword to display information about applied actions only. Displays information about all pending and applied policy rules or a particular policy rule. Use the applied keyword to display information about applied rules only. Displays applied policy rules that are active (enabled) on the switch.

show policy rule

show active policy rule
When the command is used to show output for all pending and applied policy configuration, the following characters may appear in the display: character + definition Indicates that the policy rule has been modified or has been created since the last qos apply. Indicates the policy object is pending deletion.

page 30-38

character # For example:
definition Indicates that the policy object differs between the pending/applied objects.
-> show policy rule Policy my_rule {L2/3}: +my_rule5 {L2/3}: mac1 {L2/3}:
From Prec Enab Act cli 0Yes Yes No cond5 -> action2 cli 0Yes No cond2 -> pri2 cli 0Yes No dmac1 -> pri2 No
Refl Log Trap Save No Yes Yes
The above display indicates that my_rule is inactive and is not used to classify traffic on the switch (the Inact field displays Yes). The rule my_rule5 has been configured since the last qos apply command was entered, as indicated by the plus (+) sign. The rule will not be used to classify traffic until the next qos apply. Only mac1 is actively being used on the switch to classify traffic. To display only policy rules that are active (enabled and applied) on the switch, use the show active policy rule command. For example:
-> show active policy rule Policy mac1 {L2/3}: From Prec Enab Act Refl Log Trap Save Matches cli 0 Yes Yes No No Yes Yes 0 dmac1 -> pri2
In this example, the rule my_rule does not display because it is inactive. Rules are inactive if they are administratively disabled through the policy rule command, or if the rule cannot be enforced by the current hardware. Although my_rule5 is administratively active, it is still pending and not yet applied to the configuration. Only mac1 is displayed here because it is active on the switch. See the OmniSwitch CLI Reference Guide for more information about the output of these commands.

-> policy network group netgroup2 10.10.5.1 10.10.5.2
In the next example, a policy network group called netgroup3 is created with two IPv4 addresses. The first address also specifies a mask.
-> policy network group netgroup3 173.21.4.39 mask 255.255.255.0 10.10.5.3
In this example, the 173.201.4.39 address is subnetted, so that any address in the subnet will be included in the network group. For the second address, 10.10.5.3, a mask is not specified; the address is assumed to be a host address. The network group may then be associated with a condition through the policy condition command. The network group must be specified as a source network group or destination network group. In this example, netgroup3 is configured for condition c4 as source network group:
-> policy condition c4 source network group netgroup3

page 30-43

To remove addresses from a network group, use no and the relevant address(es). For example:
-> policy network group netgroup3 no 173.21.4.39
This command deletes the 173.21.4.39 address from netgroup3 after the next qos apply. To remove a network group from the configuration, use the no form of the policy network group command with the relevant network group name. The network group must not be associated with any policy condition or action. For example:
-> no policy network group netgroup3
If the network group is not currently associated with any condition or action, the network group netgroup3 is deleted from the configuration after the next qos apply. If a condition or an action is using netgroup3, the switch will display an error message similar to the following:
ERROR: netgroup3 is being used by condition 'c4'
In this case, remove the network group from the condition first, then enter the no form of the policy network group command. For example:
-> policy condition c4 no source network group -> no policy network group netgroup3
The policy condition command removes the network group from the condition. (See Creating Policy Conditions on page 30-33 for more information about configuring policy conditions.) The network group will be deleted at the next qos apply.

In this example, the specified ports for pgroup2 span across two slots. As a result, the maximum bandwidth limit specified by the policy action is increased to 20K for all of the ports. The bandwidth limit is increased by multiplying the number of slots by the specified bandwidth value.

page 30-49

Verifying Condition Group Configuration
To display information about condition groups, use the following show commands: show policy network group Displays information about all pending and applied policy network groups or a particular network group. Use the applied keyword to display information about applied groups only. Displays information about all pending and applied policy services or a particular policy service configured on the switch. Use the applied keyword to display information about applied services only. Displays information about all pending and applied policy service groups or a particular service group. Use the applied keyword to display information about applied groups only. Displays information about all pending and applied MAC groups or a particular policy MAC group configured on the switch. Use the applied keyword to display information about applied groups only. Displays information about all pending and applied policy port groups or a particular port group. Use the applied keyword to display information about applied groups only.

show policy service

show policy service group

show policy mac group

show policy port group
See the OmniSwitch CLI Reference Guide for more information about the syntax and output for these commands. When the command is used to show output for all pending and applied condition groups, the following characters may appear in the display: character + # definition Indicates that the policy rule has been modified or has been created since the last qos apply. Indicates the policy object is pending deletion. Indicates that the policy object differs between the pending/applied objects.
In the example shown here, netgroup1 is a new network group that has not yet been applied to the configuration.
-> show policy network group Group Name: From Switch blt Entries 4.0.1.166 10.0.1.166 143.209.92.166 192.85.3.1 143.209.92.0/255.255.255.0 172.28.5.0/255/255/255.0
When the qos apply command is entered, the plus sign (+) will be removed from netgroup1 in the display. See Applying the Configuration on page 30-54 for more information about the qos apply command.

page 30-50

Using Map Groups
Map groups are used to map 802.1p, ToS, or DSCP values to different values. The following mapping scenarios are supported:
802.1p to 802.1p, based on Layer 2, Layer 3, and Layer 4 parameters and source/destination slot/port.

You can modify the IGMP query response interval from 1 to 65535 in tenths of seconds by entering ip multicast query-response-interval followed by the new value. For example, to set the IGMP query response interval to 6000 tenths-of-seconds you would enter:
-> ip multicast query-response-interval 6000
You can also modify the IGMP query response interval on the specified VLAN by entering:
-> ip multicast vlan 3 query-response-interval 6000

page 32-15

Restoring the IGMP Query Response Interval
To restore the IGMP query response interval to its default (i.e., 100 tenths-of-seconds) value on the system if no VLAN is specified, use the ip multicast query-response-interval command by entering:
-> ip multicast query-response-interval 0
-> ip multicast query-response-interval
To restore the IGMP query response interval to its default value. You can also restore the IGMP query response interval on the specified VLAN by entering:
-> ip multicast van 2 query-response-interval 0
-> ip multicast vlan 2 query-response-interval
To restore the IGMP query response interval to its default value.
Modifying the IGMP Router Timeout
The default IGMP router timeout (i.e., expiry time of IP multicast routers) is 90 seconds. The following subsections describe how to configure a user-specified router timeout value and how to restore it with the ip multicast router-timeout command.
Configuring the IGMP Router Timeout
You can modify the IGMP router timeout from 1 to 65535 seconds by entering ip multicast router-timeout followed by the new value. For example, to set the IGMP router timeout to 360 seconds on the system if no VLAN is specified, you would enter:
-> ip multicast router-timeout 360
You can also modify the IGMP router timeout on the specified VLAN by entering:
-> ip multicast vlan 2 router-timeout 360
Restoring the IGMP Router Timeout
To restore the IGMP router timeout to its default (i.e., 90 seconds) value on the system if no VLAN is specified, use the ip multicast router-timeout command by entering:

show ip slb cluster server show ip slb probes
The show ip slb, show ip slb servers, and show ip slb clusters commands provide a global view of switch-wide SLB parameters. These commands are particularly helpful in fine-tuning configurations. For example, if you wanted to get a quick look at the status of all SLB clusters you would use the show ip slb clusters command as shown below:
-> show ip slb clusters Admin Operational # % Cluster Name VIP/COND Status Status Srv Avail ----------------+----------------+--------+-------------------+-----+--------WorldWideWeb 128.241.130.204 Enabled In Service Intranet c1 Enabled In Service FileTransfer 128.241.130.206 Enabled Out of Service 2 50
In the example above, two SLB clusters (WorldWideWeb and Intranet) are administratively enabled and are in service (i.e., at least one physical server is operational in the cluster). The third SLB cluster (FileTransfer) is administratively enabled but is out of service (i.e.,no physical servers are operational in the cluster). The show ip slb cluster command provides detailed configuration information and statistics for individual SLB clusters. To use the show ip slb cluster command, enter the command followed by the name of the SLB cluster, as shown below:
-> show ip slb cluster WorldWideWeb
A statistics parameter is available with both the show ip slb clusters and show ip slb cluster commands to provide a packet count of traffic that was qualified and sent to a QoS policy condition cluster. To use this parameter, enter either of these commands with their required parameters and optionally specify the statistics parameter, as shown below:
-> show ip slb clusters statistics -> show ip slb cluster Intranet statistics
Note. See page 34-4 and page 34-5 for samples of the show ip slb cluster command output.

page 34-35

The show ip slb cluster server command provides detailed configuration information and statistics for individual SLB servers. To use the show ip slb cluster server command, enter the command, the name of the SLB cluster that the server belongs to, server, and the IP address of the server. For example, to display statistics and parameters for a server with an IP address of 10.123.11.14 that belongs to an SLB cluster called Web_Server you would enter:
-> show ip slb cluster Web_Server server 10.123.11.14
A screen similar to the following will be displayed:
Cluster Web_Server VIP: 10.123.11.14 Server 10.123.11.4 MAC addr : 00:00:1f:40:53:6a, Slot number = 1, Port number = 4, Admin status : Enabled, Oper status : In Service, Availability time (%) = 95, Ping failures = 0, Last ping round trip time (milliseconds)= 20, Probe status = ,
In the example above, the server with an IP address of 10.123.11.4 is shown to be administratively enabled and in service (i.e., this server is being used for SLB cluster client connections). The show ip slb probes command provides both a global view of SLB probes and a detailed configuration information and statistics for individual probes. For example, to view the status of all probes enter show ip slb probes as shown below:

3 Optional. Configure optional parameters. For example, to create a file called monitor1 for port moni-
toring session 6 on port 2/3, enter:
-> port monitoring 6 source 2/3 file monitor1
Note. Optional. To verify the port monitoring configuration, enter show port mirroring status, followed by the port monitoring session ID number. The display is similar to the one shown below:
-> show port monitoring status Session Monitor Monitor Overwrite Operating Admin slot/port Direction Status Status ----------+----------+----------+--------------+----------+-------------------6. 2/ 3 Bidirectional ON ON ON
For more information about this command, see Port Monitoring on page 35-24 or the Port Mirroring and Monitoring Commands chapter in the OmniSwitch CLI Reference Guide.

page 35-6

sFlow Overview
The following sections detail the specifications, defaults, and quick set up steps for the sFlow feature. Detailed procedures are found in sFlow on page 35-29. Note. sFlow is only supported on the OmniSwitch 6850 and OmniSwitch 9000 for this release.

sFlow Specifications

RFCs Supported Sampling Agent IP Address 3176 - sFlow Management Information Base Sampling rate of one (1) counts all packets and 0 (zero) disables sampling. As it need to send a fixed IP address in the datagram, loopback0 IP address is used.

sFlow Defaults

The following table shows sFlow default values: sFlow Defaults Parameter Description Receiver Name Timeout Value IP Address Data File Size Version Number Destination Port Receiver Index Packet Sampling Rate Sampled Packet Size Receiver Index Interval Value CLI Command sflow receiver sflow receiver sflow receiver sflow receiver sflow receiver sflow receiver sflow sampler sflow sampler sflow sampler sflow poller sflow poller Default Value/Comments Empty 0 seconds 32 bit address (IPv4) 1400 Bytes 128 Bytes seconds

page 35-7

Quick Steps for Configuring sFlow
Follow the steps below to create a sFlow receiver session.
1 To create a sFlow receiver session, use the sflow receiver command by entering sflow
receiver, followed by the receiver index, name, and the address to be monitored. For example:
-> sflow receiver 1 name Golden address 198.206.181.3
2 Optional. Configure optional parameters. For example, to specify the timeout value 65535 for sFlow
receiver session on address 198.206.181.3, enter:
-> sflow receiver 1 name Golden address 198.206.181.3 timeout 65535
Note. Optional. To verify the sFlow receiver configuration, enter show sflow receiver, followed by the sFlow receiver index. The display is similar to the one shown below:
-> show sflow receiver Receiver 1 Name = Address = UDP Port = Timeout = Packet Size= DatagramVer=