OSM Configuration Note, 12.2SR
Configuring the 4-Port Gigabit Ethernet WAN Optical Services Modules
Download this chapter
Configuring the 4-Port Gigabit Ethernet WAN Optical Services ModulesConfiguring the 4-Port Gigabit Ethernet WAN Optical Services Modules
Download the complete book
OSM Configuration Note, 12.2SR - Book-length PDF fileOSM Configuration Note, 12.2SR - Book-length PDF file (PDF - 4 MB)
give_us_feedback

Table Of Contents

Configuring 4-Port Gigabit Ethernet WAN Optical Services Modules

Supported Features

Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+

Gigabit Ethernet WAN Port Configuration

Basic Interface Configuration

Configuring Strict Priority Low Latency Queuing (LLQ) Support on the OSM-2+4GE-WAN+

Examples

Quality of Services


Configuring 4-Port Gigabit Ethernet WAN Optical Services Modules

This chapter provides an overview of the features supported on the 4-port Gigabit Ethernet WAN Optical Services Modules (OSM-2+4GE-WAN+ and OSM-4GE-WAN-GBIC) supported on Cisco 7600 series routers.

This chapter consists of these sections:

•Supported Features

•Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+

•Gigabit Ethernet WAN Port Configuration

•Quality of Services

Supported Features

The following Layer 3 features are supported on the Gigabit Ethernet WAN optical services modules (OSMs):

•Forwarding of distributed IP services

•Multiprotocol Label Switching (MPLS)

•Ethernet over Multiprotocol Label Switching (EoMPLS)

•Frame Relay over MPLS

•ATM cell relay over MPLS VC-Mode

•ATM AAL5 over MPLS

•IOS Modular QoS Command Line Interface (MQC) QoS

•Flow control

•802.1Q VLAN trunking

•Hot Standby Routing Protocol (HSRP)

•Jumbo frames

•Support for up to 32,000 MAC addresses per port

•Support for up to 32,000 simultaneous ACL entries

•Support for up to 32,000 simultaneous QoS entries

•SNMP I and II

•Four RMON groups per port: statistics, history, alarms, and events

•Online insertion and removal (OIR)

Note You should perform online insertion and removal (OIR) in a redandant route processor system only after the standby state reaches a terminal state of the configured High Availability mode.

•Inter-Switch Link (ISL)

Note The OSM-2+4GE-WAN+ module supports ISL on the Layer 2 Gigabit Ethernet LAN ports but does not support ISL on the Layer 3 Gigabit Ethernet WAN ports.

The Layer 2 Gigabit Ethernet ports on the OSMs are configured from the supervisor engine of the Cisco 7600 series router. For feature support and configuration information for the OSM Layer 2 Gigabit Ethernet ports, refer to the links in the "Layer 2 Software Features" section on page 1-4.

Saving your Configuration Before Upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+

When you upgrade from OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, the existing configuration will not be saved and applied to the new OSM-2+4GE-WAN+.

To save your configuration when upgrading from an OSM-4GE-WAN-GBIC to an OSM-2+4GE-WAN+, perform this task:

Step 1 Enter the write memory command before removing the OSM-4GE-WAN-GBIC.

Step 2 Install the new OSM-2+4GE-WAN+.

Step 3 Enter the copy startup-config running-config command.

Step 4 Enter the write memory command.

Warning The orientation of the GBIC in OSM-4GE-WAN-GBIC ports is reversed (upside down) from those of the LAN ports for OSM-2+4GE-WAN+.

Gigabit Ethernet WAN Port Configuration

The four Gigabit Ethernet WAN ports on the 4-port Gigabit Ethernet WAN OSMs are controlled by Cisco IOS software and support all standard Cisco IOS features. For configuration information for standard Cisco IOS features and routing protocols supported on the GE-WAN ports, refer to the appropriate Cisco IOS configuration guide and command reference publications at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/index.htm

Basic Interface Configuration

After you verify that the 4-port Gigabit Ethernet WAN OSM is installed correctly, use the configure command to configure the Gigabit Ethernet WAN interfaces.

The following procedure is for creating a basic configuration—enabling an interface and specifying IP routing. You might also need to enter other configuration subcommands, depending on the requirements for your system configuration.

Note Subinterfaces on the 4-port Gigabit Etherent WAN module cannot share HSRP group numbers. As a result, only 16 HSRP groups per Gigabit Ethernet WAN port are supported.

Note The MTU size you specify on a main Gigabit Ethernet WAN interface will also apply to all subinterfaces you configure on the main interface. It is not possible to specify an MTU size on a subinterface that is different from the MTU size specified for the main interface.

To configure the Gigabit Ethernet WAN interfaces, perform this task:

Step 1 Confirm that the system recognizes the module by entering the show version command: 

Router# show version

Step 2 Check the status of each port by entering the show interface command: 

Router# show interface

Step 3 Enter configuration mode and specify that the console terminal will be the source of the configuration subcommands: 

Router# configure terminal

Step 4 Enable IP routing by entering the ip routing command: 

Router(config)# ip routing

Step 5 At the prompt, specify the new interface to configure by entering the interface command, followed by the type (ge-wan) and slot/port number. The example that follows is for a Gigabit Ethernet WAN OSM in slot 3: 

Router(config)# interface ge-wan 3/0

Step 6 Assign an IP address and subnet mask to the interface with the ip address configuration subcommand, as in the following example: 

Router(config-if)# ip address 10.1.2.3 255.255.255.255

By default, a GE-WAN interface is configured for automatic negotiation of link parameters, such as duplex, speed, and flow control. To disable flow control and to force the interface for 1000/full-duplex mode, turn off automatic negotiation with the command: 

Router(config-if)# no negotiation auto

Note Changing the negotiation mode of an active interface flaps the interface by bringing it down and then back up, so as to implement the new negotiation mode. For this reason, we recommend changing the negotiation mode only when the interface is shutdown.

Tip Use the negotiation auto command to restore the default of automatic negotiation of link parameters.

Step 7 Change the shutdown state to up and enable the interface: 

Router(config-if)# no shutdown

The no shutdown command passes an enable command to the Gigabit Ethernet module. It also causes the module to configure itself based on the most recent configuration commands received by the module.

Step 8 Write the new configuration to memory: 

Router# copy running-config startup-config

When the configuration is stored, an OK message appears.

Configuring Strict Priority Low Latency Queuing (LLQ) Support on the OSM-2+4GE-WAN+

Starting with Cisco IOS Release 12.2(18)SXE, the Low Latency Queuing feature is changed for the OSM-2+4GE-WAN+ Optical Services Module. With this change, priority queue policing is supported on the module. Using Hiearchical Queuing Framework (HQF), the police command is combined with strict priority in a class on the OSM.

Note The priority percent % and priority kbps commands from previous releases are no longer supported.

If a second priority police class is included in the policy, police must be configured first.

To configure strict priority LLQ support, perform the following tasks, starting in global configuration mode:

 
Command or Action
Purpose

Step 1 

Router(config)# policy-map policy-name

Example:

Router(config)# policy-map policy11

Specifies the name of the policy map to be created or modified.

Step 2 

Router(config-pmap)# class class-name

Example:

Router(config)# class class204

Specifies the name of a predefined class included in the service policy.

Step 3 

Router(config-pmap-c)# priority

Example:Router(config)# priority

Configures the strict priority class.

Step 4 

Router(config-pmap-c)# police rate

Example:

Router(config-pmap-c) # police 1000000#

Sets the policing rate (in bps).

Examples

The following example shows a typical configuration and verification for the OSM-2+4GE-WAN+ OSM. 

!

 Policy Map child

   Class dscp-ef

     priority

    police cir 1000000 bc 31250 be 31250 conform-action transmit exceed-action drop

   Class dscp-af21

     bandwidth remaining 35 (%)

   Class dscp-af31

     bandwidth remaining 30 (%)

   Class class-default

     bandwidth remaining 25 (%)

!

 Policy Map parent

   Class vlan-2

     bandwidth 5000 (kbps)

     shape average 6000000 24000 24000

     service-policy child

!

interface ge-wan7/1

no ip address

negotiation auto

mls qos trust dscp

service-policy output parent

end

!

interface ge-wan7/1.2

encapsulation dot1Q 2

ip address 10.10.10.1 255.255.255.0

mls qos trust dscp

no cdp enable

end

The following show command verifies the configuration:

Router#show policy interface ge-wan7/1

GE-WAN7/1

Service-policy output: parent

Class-map: vlan-2 (match-all)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: vlan 2

Queueing

queue limit 1250 (packets)

(queue depth/total drops/no-buffer drops) 0/0/0

(pkts queued/bytes queued) 0/0

bandwidth 5000 kbps

shape (average) cir 6000000, bc 24000, be 24000

target shape rate 6000000

(shape parameter is rounded to 5952000 bps due to granularity)

Service-policy : child

Class-map: dscp-ef (match-all)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: ip dscp ef

Priority: b/w exceed drops: 0

police:

cir 1000000 bps, bc 31250 bytes

(Police cir is rounded to 983040 bps due to granularity)

Class-map: dscp-af21 (match-all)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: ip dscp af21

Queueing

queue limit 350 (packets)

(queue depth/total drops/no-buffer drops) 0/0/0

(pkts queued/bytes queued) 0/0

bandwidth remaining 35% (1400 kbps)

(bandwidth parameter is rounded to 1392 kbps due to granularity)

Class-map: dscp-af31 (match-all)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: ip dscp af31

Queueing

queue limit 300 (packets)

(queue depth/total drops/no-buffer drops) 0/0/0

(pkts queued/bytes queued) 0/0

bandwidth remaining 30% (1200 kbps)

(bandwidth parameter is rounded to 1196 kbps due to granularity)

Class-map: class-default (match-any)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: any

Queueing

queue limit 250 (packets)

(queue depth/total drops/no-buffer drops) 0/0/0

(pkts queued/bytes queued) 0/0

bandwidth remaining 25% (1000 kbps)

Class-map: class-default (match-any)

0 packets, 0 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: any

queue limit 248750 (packets)

(queue depth/total drops/no-buffer drops) 0/0/0 

      (pkts queued/bytes queued) 0/0

Router#

Quality of Services

The Gigabit Ethernet WAN modules support the following QoS implementations:

•Differentiated Services Code Point (DSCP) classification

•IP-precedence classification

•Class-based traffic shaping

•Class-based weighted fair queuing (CBWFQ)—Supported on the OSM-2+4GE-WAN+ only

•Low latency queuing (LLQ)—Supported on the OSM-2+4GE-WAN+ only

•Weighted Random Early Detection (WRED)—Supported on the OSM-2+4GE-WAN+ only

•Hierarchical traffic shaping for dot1q encapsulations—Supported for egress traffic on subinterfaces on the OSM-2+4GE-WAN+ only

•EoMPLS Support with CBWFQ, LLQ and WRED - CBWFQ, LLQ or WRED are applied to the EoMPLS uplink interface. Supported on the OSM-2+4GE-WAN+ only

For QoS configuration information and examples for the WAN OSM ports, see the "Configuring QoS on the OSMs" section on page 10-2.