Cisco Transport Manager ML Provisioning Methodology, 5.0 [Cisco Transport Manager]

Table Of Contents

Cisco Transport Manager Release 5.0 ML Provisioning Methodology

Contents

Introduction

Overview

CLI Configuration Details

Base Card Configuration

RPR Base Card Configuration

Point-to-Point Base Card Configuration

Enabling and Disabling Ethernet Ports (Administrative State/Link Control)

Port Enable

Port Disable

Creating Service Connections

Using the QoS Policy Template

1. Class Map Configuration

Configuring CIR/PIR Class Map

Configuring BEST EFFORT Class Map

Configuring ADVANCED Class Map

2. QoS Profile Configuration

CIR/PIR QoS Profile

BEST EFFORT QoS Profile

ADVANCED QoS Profile

Bandwidth Data Service Provisioning

3. Interface Configuration

Adding UNI QinQ Access

Removing UNI QinQ Access

Adding UNI dot1Q Access

Removing UNI dot1Q Access

Adding UNI Untagged Access

Adding NNI dot1Q Access

Removing NNI dot1Q Access

Obtaining Documentation, Obtaining Support, and Security Guidelines

Cisco Transport Manager Release 5.0 ML Provisioning Methodology

This document describes the methodology that Cisco Transport Manager (CTM) Release 5.0 uses to provision ML-series cards.

Contents

This document describes the following topics:

•Introduction

•Overview

•CLI Configuration Details

•Base Card Configuration

•Enabling and Disabling Ethernet Ports (Administrative State/Link Control)

•Creating Service Connections

•Using the QoS Policy Template

•Obtaining Documentation, Obtaining Support, and Security Guidelines

Introduction

CTM is an advanced management system that provides functionality at the element and network management levels for Cisco network elements (NEs) and devices. CTM supports fault, configuration, performance, and security management functional areas. CTM also serves as a foundation for integration into a larger overall operations support system (OSS) environment by providing northbound gateway interfaces to higher layer management systems.

CTM supports data service provisioning over the ML-series cards. Data service provisioning consists of first provisioning the Layer 2 topology using optical circuits and then provisioning Layer 2 service on top of the Layer 2 topology.

The scope of this application note is to provide the set of Cisco IOS commands issued by CTM during the Layer 2 topology and Layer 2 service provisioning. The syntax used for the commands needs to be respected for services provisioned directly using Cisco IOS so that the provisioned services are recognized by CTM.

Overview

Layer 2 topology can be a point-to-point optical circuit, Resilient Packet Ring (RPR) consisting of a chain of optical circuits, or hub and spoke, consisting of multiple optical circuits connected in a hub-and-spoke fashion. Hub-and-spoke topologies are supported as multiple point-to-point topologies.

For a point-to-point topology, the following card combinations are supported:

•ML-1000-2/ML-100T-12 to ML-1000-2/ML-100T-12 card

•ML-1000-2/ML-100T-8/ML-100T-12 to OC-N/STM-N card

•ML-1000-2/ML-100T-12 to G-series card

•ML-1000-2/ML-100T-12 to E-Series (15327 only)

•ML-1000-2/ML-100T-12 to ML-100T-8/CE-100T-8 card

•ML-100T-8 to ML-100T-8/CE-100T-8 card

When deployed as hub-and-spoke, the ML-series can be placed at the spoke locations, with the G-series providing an extension of the traffic to a Cisco 7600, which forms the hub of the architecture. This arrangement provides a cost-effective way to interface to the Cisco 7600. Alternatively the ML-series can be deployed at both the hub and the spoke sites.

When deployed as RPR, all sites contain ML-series (ML-1000-2, ML-100T-12, or ML-100T-8). A minimum of two ML-series cards is required to configure an RPR.

CTM provisions ML-series cards by opening a session to each card. Before this can be done, each ML-series card must be provisioned and have a password configuration that allows CTM to log in. For this purpose, a barebone file is provided on the CTM server disk (Disk 1).

Note Refer to Cisco Transport Manager Release 5.0 User Guide for additional information.

A different file is provided for the following cards:

•ONS 15310 ML (barebone15310CLI_Security.txt)

•ONS 15454 ML base microcode (barebone15454CLI_Security.txt)

•ONS 15454 ML enhanced microcode (barebone15454CLI_Enhanced_Security.txt)

Reset the ML card after loading the barebone file and wait for five minutes before provisioning topologies and services. The login and password are reported in the Control Panel window. You create other profiles on ML cards by using the IOS Users table (available under Administration > CTC-based NEs > IOS Users Table).

After entering command-line interface (CLI) commands through the Telnet session, CTM issues a write or copy start run command to write the Cisco IOS configuration file to the Timing Communications and Control (TCC) flash. When the Cisco IOS configuration file is written to the TCC flash (by CTM or by another user), CTM is notified. To verify that CTM has been notified, issue the write command after any CLI change.

CTM provides a graphical user interface (GUI) wizard to facilitate provisioning of L2 topologies and related L1 circuits. Refer to the "Provisioning Data Services" section of Chapter 8, "Provisioning Services" in Cisco Transport Manager Release 5.0 User Guide. Create an RPR or point-to-point topology involving some of the ML cards in the network. Based on the L2 topology circuit type and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each ML card in the RPR ring.

The Create L2 Service wizard guides you through the VLAN creation. There is no CLI to create a circuit VLAN. An RPR supports from 1 to 4095 VLANs, and these VLANs are enabled at all times. All that is required is to configure the endpoint to connect a ring VLAN to an Ethernet port (or port VLAN). Only ML devices are supported on an RPR.

Point-to-point topology is supported for ML-ML, ML-G1000, and ML-OC cards. Point-to-point topology creation is similar to RPR creation in that based on the L2 topology circuit type and size that you specify, CTM creates related L1 circuits and installs a base card configuration on each ML card in the point-to-point topology.

CLI Configuration Details

Note the following CLI conventions:

•Notes are reported within brackets ( [ ] ). For example:

[notes]

•Optional commands or parameters are reported within brackets ( [ ] ). For example:

[match any]

•Configurable parameters are reported within left and right angle brackets (< >). For example:

<parameter>

•Multiple parameters or commands are enclosed within braces ( { } ) and separated by a vertical bar ( | ). For example:

{parameter_1 | parameter_2 | parameter_3}

Base Card Configuration

The base card configuration is a set of commands entered during the L2 topology creation. The parameters used are defined in the L2 Topology Bandwidth pane (Figure 1) of the Create L2 Topology wizard.

Figure 1 Create Layer 2 Topology Wizard

RPR Base Card Configuration

For creation of an RPR topology, the base card configuration must be applied to all ML cards involved in the RPR. The ring is not functional and is reported as L2 Not Ready until the base card configuration is applied to all cards. You can select an L2 Not Ready RPR in the L2 Topology table and enable the L2 service provisioning by choosing Configuration > Enable L2 Service.

Caution When the state is reported as L2 Not Ready the base card configuration is missing. Performing the CTM operation Configuration > Enable L2 Service will apply the base configuration to the card. This operation is traffic affecting if the service has already been provisioned on the card.

CTM defines the unique card number within the ring. The actual range is 1 to 251 in any order. Refer to the NE hardware documentation for the number of ML cards allowed per RPR.
class-map match-any SP_MANAGEMENT
match cos <SP Management Class of Service>
class-map match-any AVVID_VOICE_VIDEO
match cos <Low Latency Queue Class of Service>
class-map match-any AVVID_CONTROL
match cos <AVVID Control Class of Service>
class-map match-any CIR
match cos <Committed Rate Class of Service>
class-map match-all BEST_EFFORT
match any
Policy-map POLICY_QOS_OUT
class SP_MANAGEMENT 
bandwidth percent <SP Management (%)>
class AVVID_VOICE_VIDEO
Priority 8 [Fixed value not configurable]
class AVVID_CONTROL
bandwidth percent <AVVID Control (%)>
class CIR
bandwidth percent <Committed Rate (%)>
class BEST_EFFORT
Bandwidth percent <Default Best Effort (%)>
Cos commit <CoS Commit> 
No ip routing
Vlan dot1q tag native 
L2protocol-tunnel cos 2 [Fixed Value] 
interface SPR1
Spr station-id <Card#> [Valid Range is 1..254. It is not Spr node <Card#>]
[The following commands are not issued by CTM, these are default ML settings]
no ip address
no keep alive
hold-queue 150 in
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]
no ip route-cache
interface POS0
Spr-intf-id 1
Service-policy output POLICY_QOS_OUT
[The following commands are not issued by CTM, these are default ML settings]
No ip address
No ip route-cache
Crc 32
interface POS1
Spr-intf-id 1
Service-policy output POLICY_QOS_OUT
[The following commands are not issued by CTM, these are default ML settings]
No ip address
No ip route-cache
Crc 32
Point-to-Point Base Card Configuration

For a point-to-point topology involved in at least one ML card, the other card can be ML, OC, or G1000. The point-to-point base card configuration must be applied only on the ML card(s) involved in the topology.

Note CTM does not enable spanning tree. Therefore, verify that there are no Layer 2 loops formed by bridged connections outside the ML network. Layer 2 loops in a network without spanning tree enabled might cause network instability.

Note If a G1000 card is one endpoint in the point-to-point topology, a Network-to-Network Interface (NNI) connection is assumed. That is, the class of service (CoS) coming into the G1000 is trusted (not overwritten).
class-map match-any SP_MANAGEMENT
match cos <SP Management Class of Service> 
class-map match-any AVVID_VOICE_VIDEO
match cos <Low Latency Queue Class of Service>
class-map match-any AVVID_CONTROL
match cos <AVVID Control Class of Service>
class-map match-any CIR
match cos <Committed Rate Class of Service> 
class-map match-all BEST_EFFORT
match any
Policy-map POLICY_QOS_OUT
class SP_MANAGEMENT
bandwidth percent <SP Management (%)>
class AVVID_VOICE_VIDEO
Priority 8 [Fixed value not configurable]
class AVVID_CONTROL
bandwidth percent <AVVID Control (%)>
class CIR
bandwidth percent <Committed Rate (%)>
class BEST_EFFORT
Bandwidth percent <Default Best Effort (%)>
cos commit <CoS Commit>
No ip routing
vlan dot1q tag native
l2protocol-tunnel cos 2 [Fixed Value]
[The following commands are not issued by CTM, these are default ML settings]
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]
no ip route-cache
interface POS0
service-policy output POLICY_QOS_OUT
Crc {16|32} [Crc 16 between ML and E-Series, otherwise is Crc 32]
[The following commands are not issued by CTM, these are default ML settings]
No ip address
No ip route-cache
interface POS1
service-policy output POLICY_QOS_OUT
Crc {16|32} [Crc 16 between ML and E-Series, otherwise is Crc 32]
[The following commands are not issued by CTM, these are default ML settings]
No ip address
No ip route-cache
Enabling and Disabling Ethernet Ports (Administrative State/Link Control)

CTM provides the ability to enable or disable an Ethernet port at any time (see Figure 2). This activity is independent of other port provisioning. CTM automatically disables a port when the last connection is removed.

Figure 2 Modify Layer 2 Service Drops Wizard

Port Enable
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]
No shutdown
Port Disable
Interface {FastEthernetN|GigabitEthernetM} [N=0..11 and M=0,1]
shutdown
Creating Service Connections

CTM provides an L2 service provisioning wizard to facilitate provisioning of VLANs over a defined L2 topology. You can define each Ethernet port as UNI (user interface) or NNI. VLANs on an Ethernet port are referred to as port VLANs. VLANs on Packet Over SONET (POS) and Shared Packet Ring (SPR) ports (and their connected circuits) are referred to as service provider VLANs (or circuit VLANs).

You cannot mix NNI and UNI connections on the same port. CTM supports the following types of service configurations:

•UNI QinQ Access (User VLAN and Protocol transparency)—Cannot be combined with other connection types on the same port.

•UNI dot1q Access—Select an unused port VLAN from 1 to 4095. It can be combined with untagged connections on the same port. Each port VLAN can be used for only one connection.

•UNI Untagged Access—Configure as Dot1q Access with port VLAN 1.

•NNI dot1q Access—Select an unused port VLAN from 1 to 4095. It can be combined with untagged connections on the same port. Each port VLAN can be used for only one connection.

The circuit VLAN range is 1 to 4095. On an RPR, all valid circuit VLANs can be used; however, due to limited bridge-group resources, each ML card can access only 255 circuit VLANs. Due to limited card-level bridge-group resources, only 255 circuit VLANs can be used on a point-to-point circuit.

Note VLAN ID 1 is reserved for untagged VLANs.

Using the QoS Policy Template

The following information must be user-configured in the L2 service provisioning and QoS profile wizards:

•Port (FastEthernetM [FEM] or GigabitEthernetN [GIGEN] with M=0..11 and N=0,1)

•Service connection type (UNI QinQ, UNI dot1Q, UNI untagged, or NNI dot1Q)

•Quality of Service (QoS) parameters (selection of the QoS profile name defined in the QoS profile)

CTM assigns an unused bridge group (BG) to the card. The range is 1 to 255.

Table 1 lists the configuration information for a Best Effort QoS profile. You can select the predefined profile and customize it, or create a new customized profile by using the Advanced option.

Table 1 Configuration Settings for the Best Effort QoS Profile

QoS Template Name

Best_Effort

QoS Template Type

Best Effort

QoS Policy

Setting

Match Any

True

Match IP

False

IP Precedence Value

N/A

Match CoS

False

CoS Value

N/A

Match DSCP

False

DSCP Value

N/A

AND

N/A

CIR Type

N/A

Committed Rate

N/A

Committed Burst

N/A

Committed CoS Marking

Mark CoS

QoS Policy

Setting

Committed CoS Value

0

Excess Traffic

Allow

Peak Rate

N/A

Peak Burst

N/A

Excess CoS Marking/Value

0

Violations

N/A

Violate CoS

N/A

Best Effort Type

Line Rate

Max Rate

96 kbps

Max Burst

8000 bytes

Table 2 lists the configuration information for the committed information rate/peak information rate (CIR/PIR) QoS profile. You can select the predefined profile and customize it, or create a new customized profile by using the Advanced option.

Note When you select the CIR/PIR profile and want to modify it, in order to set the CIR type to Rate_Limited, CIR=PIR, and CIR Burst=PIR Burst, you must first configure your own advanced service.

Table 2 Configuration Settings for the CIR/PIR QoS Profile

QoS Template Name

CIR_PIR

QoS Template Type

Advanced

QoS Policy

Setting

Match Any

True

Match IP

False

IP Precedence Value

N/A

Match CoS

False

CoS Value

N/A

Match DSCP

False

DSCP Value

N/A

AND

N/A

CIR Type

Rate_Limited

Committed Rate

96 kbps

Committed Burst

8000 bps

Committed CoS Marking

Mark CoS

QoS Policy

Setting

Committed CoS Value

2

Excess Traffic

Allow

Peak Rate

96 kbps

Peak Burst

8000 bps

Excess CoS Marking/Value

2

Violations

Allow

Violate CoS

2

Best Effort Type

N/A

Max Rate

N/A

Max Burst

N/A

CTM allows you to define a QoS policy template starting from the above predefined policies, customizing them within the following predefined ranges:

•CIR_PIR

–CIR: 96,000 to 800,000,000 bits per second.

–Max CIR Burst: 8000 to 64000 bytes.

–PIR: 96,000 to 800,000,000 bits per second. Cannot be less than CIR.

–Max PIR Burst: 8000 to 64000 bytes. Cannot be less than Max CIR Burst.

–Traffic matching criteria is match-all.

–Only one policer is allowed.

•Best_Effort

–Line Rate: CIR is 96000 bits per second and CIR Burst is 8000 bytes.

–Rate Limited: User configures the CIR and CIR Burst.

–Traffic matching criteria is match-all.

–Only one policer is allowed.

Users can create their own advanced QoS policy. The user can input the customized QoS configuration based on the following parameters:

•Traffic matching criteria.

•CoS: Range is 0 to 7.

•DSCP: Range is 0 to 63.

•IP Precedence: Range is 0 to 7.

•CoS transmit values for CIR/PIR.

•Exceed action and Violate action and their CoS transmit values.

•Up to 8 QoS classes can be configured.

The following information must be user-configured in the L2 service provisioning and QoS profile wizards:

•Port (FastEthernetM [FEM] or GigabitEthernetN [GIGEN] with M=0..11 and N=0,1)

•Service connection type (UNI QinQ, UNI dot1Q, UNI untagged, or NNI dot1Q)

•QoS parameters (selection of the QoS profile name defined in the QoS profile)

CTM assigns an unused BG to the card. The range is 1 to 255.

Note The CLI commands in this section are written for services defined on the RPR topology. For services defined on point-to-point circuits, replace int spr 1 with int pos 0 or int pos 1, depending on which POS will carry the service. The bridge x protocol command is never issued. Spanning tree is not enabled for RPR or point-to-point circuits. The L2protocol-tunnel all command is expanded to three separate lines when saved by the Cisco IOS.

For each selected service drop, the configuration is done in three steps:

1. Class map configuration (not required for NNI-configured ports).

2. Policy map configuration (through QoS profiles; not required for NNI-configured ports).

3. Interface configuration (through the Create L2 Service wizard).

The following sections describe the commands entered for each step.

1. Class Map Configuration

Configuring CIR/PIR Class Map
[Class Map Configuration for CIRPIR]
Class-map match-all CLASS_BG<BG>_CIRPIR
match bridge-group <BG>
Configuring BEST EFFORT Class Map
[Class Map Configuration for BESTEFFORT]
Class-map match-all CLASS_BG<BG>_BESTEFFORT
match bridge-group <BG>
Configuring ADVANCED Class Map

Figure 3 shows an example of how to create an advanced QoS profile.

Figure 3 Create QoS Profile Wizard—ADVANCED Class Map Configuration
[Class Map Configuration for ADVANCED]
class-map match-all CLASS_BG<BG>_ADVANCED_<Service Drop Port>_N [N number of Policer will 
be configured on the <Service Drop Port>=0,1 for GigaEthernet and <Service Drop 
Port>=0..11 for FastEthernet.]
match bridge-group <BG>
[match ip dscp <Match DSCP>]
[if Match DSCP has been selected - Valid Range is 0-63]
[match ip precedence <Match IP Precedence>]
[if Match IP Precedence has been selected - Valid Range is 0-7]
[match cos <Match CoS>]
[if Match CoS has been selected - Valid Range is 0-7]
2. QoS Profile Configuration

CIR/PIR QoS Profile

Figure 4 shows an example of how to create a CIR/PIR QoS profile.

Figure 4 Create QoS Profile Wizard—CIR/PIR
[Policy Map Configuration command for CIR/PIR QoS Profile]
Policy-map POLICY_{GIGE|FE}<port>_IN
Class CLASS_BG<BG>_CIRPIR
[1. Case Line Rate selection]
Police 96000 8000 conform-action set-cos-transmit 2 exceed-action set-cos-transmit 2
[2. Case Rate Limited selection Excess Traffic Discarded]
Police <Committed Rate> <Committed Burst Size> conform-action set-cos-transmit 1 
exceed-action drop
[3. Case Rate Limited selection Excess Traffic Allowed]
Police <Committed Rate> <Committed Burst Size> <Peak Burst> pir <Peak Rate> 
conform-action set-cos-transmit 2 exceed-action set-cos-transmit 1 violate-action drop
BEST EFFORT QoS Profile

Figure 5 shows an example of how to create a BEST EFFORT QoS profile.

Figure 5 Create QoS Profile Wizard—BEST EFFORT
[Policy Map Configuration for BESTEFFORT QoS Profile]
Policy-map POLICY_{GIGE|FE}<port>_IN 
Class CLASS_BG<BG>_BESTEFFORT
[1. Case Line Rate selection] 
Police 96000 8000 conform-action set-cos-transmit 0 exceed-action set-cos-transmit 0 
[2. Case Rate Limited selection] 
Police <Max Rate> <Max Burst> conform-action set-cos-transmit 0 exceed-action drop
ADVANCED QoS Profile

Figure 6 shows an example of how to create an ADVANCED QoS profile.

Figure 6 Create QoS Profile Wizard—ADVANCED
[Policy Map Configuration for ADVANCED QoS Profile]
Policy-map POLICY_{GIGE|FE}<port>_IN 
Class CLASS_BG<BG>_ADVANCED_<Service Drop Port>_N 
[N number of Policer will be configured on the <Service Drop Port>=0,1 for 
GigaEthernet and <Service Drop Port>=0..11 for FastEthernet]
police <Committed Rate> <Committed Burst Size> [<Peak Rate> pir <Peak Burst>] 
conform-action {transmit|set-cos-transmit <Committed CoS Marking Value>} 
[exceed-action {drop|set-cos-transmit <Excess CoS Marking Value>}][violate-action 
{drop|set-cos-transmit <Violation CoS Marking Value>}]
[[<Peak Rate> pir <Peak Burst>] is applied only if Excess Traffic is Allowed] 
[exceed-action drop is applied only if Excess Traffic is Discarded]
[Trust option is never selectable for Excess Traffic or Violation tab, Mark CoS option 
is always used when the Excess or Violations is Allow]
[violation-action drop is applied only if Excess Traffic is Allowed and Violate 
Traffic is Discarded]
Bandwidth Data Service Provisioning

Check the Enable Bandwidth DSP check box (in the Control Panel > ONS NE Service pane for CTC-based NEs) to enable the bandwidth data service provisioning (DSP) check during L2 service provisioning. The bandwidth utilization report shows available and used bandwidth for each L2 topology. This report can be used during L2 service provisioning to verify whether the requested CIR is available on the topology. Based on the report, an error is returned if there is not enough bandwidth available for a drop port.

3. Interface Configuration

Adding UNI QinQ Access

Any port with mode dot1q-tunnel is a UNI QinQ Access connection. Figure 7 shows an example for adding UNI QinQ access using the Create Layer 2 Service wizard.

Figure 7 Create Layer 2 Service Wizard—Adding UNI QinQ Access
[Interface Configuration]
Interface {GigabitEthernet<port>|FastEthernet<port>}
Description <QoSProfileName> 
[CTM will issue `L2protocol-tunnel all' command and the result will be the following 
set of commands]
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
Mode dot1q-tunnel
Bridge-group <BG>
Service-policy input POLICY_{GIGE|FE}<port>_IN
Service-policy output POLICY_QOS_OUT
[The following command in not issued by CTM, these are default ML settings] 
Bridge-group <BG> spanning-disable
Interface SPR1.<Service Provider VLAN>
Encapsulation dot1q <Service Provider VLAN>
Bridge-group <BG>
[The following command in not issued by CTM, these are default ML settings] 
Bridge-group <BG> spanning-disable
Removing UNI QinQ Access
[Note the reverse order of commands]
Interface SPR1.<Service Provider VLAN>
No Bridge-group <BG>
No Encap dot1q <Service Provider VLAN>
No Interface SPR1.<Service Provider VLAN> [Ignore warning message]
Interface {GigabitEthernet<port>|FastEthernet<port>}
No Bridge-group <BG> 
No Mode dot1q-tunnel 
No L2protocol-tunnel all
No description
No class-map CLASS_BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N} 
[Remove all the N number of Class Maps in case of Advanced QoS]
[When removing last connection from a port]
No Policy-map POLICY_{GIGE|FE}<port>_IN
No Service-policy output POLICY_QOS_OUT
Adding UNI dot1Q Access

Figure 8 shows an example for adding UNI dot1Q access using the Create Layer 2 Service wizard.

Figure 8 Create Layer 2 Service Wizard—Adding UNI dot 1Q Access

The port is recognized as UNI if service-policy input is entered on the port interface; otherwise, the port is recognized as NNI. Every subinterface is a dot1q connection. The classification of UNI versus NNI is based on the port-level parsing. A connection is untagged if encap dot1q 1 is entered. The multiple class map and QoS policer configurations for advanced QoS are similar to the QinQ Access example shown in Figure 8.
[Interface Configuration]
[First time only - First dot1q on this UNI port]
Interface {GigabitEthernet<port>|FastEthernet<port>}
Service-policy input POLICY_{GIGE|FE}<port>_IN
Service-policy output POLICY_QOS_OUT
Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>
Description <QoSProfileName>
Encapsulation dot1q <Port VLAN>
Bridge-group <BG>
[The following command in not issued by CTM, these are default ML settings] 
Bridge-group <BG> spanning-disable
Interface SPR1.<Service Provider VLAN>
Encapsulation dot1q <Service Provider VLAN>
Bridge-group <BG>
[The following command in not issued by CTM, these are default ML settings] 
Bridge-group <BG> spanning-disable
Removing UNI dot1Q Access
[Note the reverse order of commands]
Interface SPR1.<Service Provider VLAN>
No Bridge-group <BG>
No Encap dot1q <Service Provider VLAN>
No Interface SPR1.<Service Provider VLAN> [Ignore warning message]
Interface <port>.<Port VLAN>
No Bridge-group <BG>
No Encap dot1q <Port VLAN>
No description
No Interface <port>.<Port VLAN> [Ignore warning message]
Policy-map POLICY_{GIGE|FE}<port>_IN 
No Class BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N}
[Remove all the N number of Class Maps in case of Advanced QoS]
No class-map CLASS_BG<BG>_{CIRPIR|BESTEFFORT|ADVANCED_<Service Drop Port>_N}
[Remove all the N number of Class Maps in case of Advanced QoS]
[When removing last connection from a port]
No Policy-map POLICY_{GIGE|FE}<port>_IN
No Service-policy output POLICY_QOS_OUT
Adding UNI Untagged Access

UNI untagged access is similar to UNI dot1Q Access with Port VLAN ID = 1.

Adding NNI dot1Q Access
[Interface Configuration]
[First time only - First Connection on this port]
Interface {FastEthernet<port>|GigabitEthernet<port>}
Service-policy output POLICY_QOS_OUT
Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN>
Encap dot1q <Port VLAN>
Bridge-group <BG>
Interface spr 1.<Server Provider VLAN>
Encap dot1q <Server Provider VLAN>
Bridge-group <BG>
Removing NNI dot1Q Access
[Note the reverse order of commands]
Interface spr 1.<Server Provider VLAN>
No Bridge-group <BG>
No Encap dot1q <Server Provider VLAN>
No Interface spr 1.<Circuit VLAN> [Ignore warning message]
Interface <port>.<Port VLAN>
No Bridge-group <BG> 
No Encap dot1q <Port VLAN>
No Interface {FastEthernet<port>|GigabitEthernet<port>}.<Port VLAN> [Ignore warning 
message]
[When removing last connection from a port]
No Service-policy output POLICY_QOS_OUT
Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Copyright © 2005 Cisco Systems, Inc. All rights reserved.

Hierarchical Navigation

Cisco Transport Manager

Cisco Transport Manager ML Provisioning Methodology, 5.0

Downloads

Table Of Contents

Cisco Transport Manager Release 5.0 ML Provisioning Methodology

Contents

Introduction

Overview

CLI Configuration Details

Base Card Configuration

RPR Base Card Configuration

Point-to-Point Base Card Configuration

Enabling and Disabling Ethernet Ports (Administrative State/Link Control)

Port Enable

Port Disable

Creating Service Connections

Using the QoS Policy Template

1. Class Map Configuration

Configuring CIR/PIR Class Map

Configuring BEST EFFORT Class Map

Configuring ADVANCED Class Map

2. QoS Profile Configuration

CIR/PIR QoS Profile

BEST EFFORT QoS Profile

ADVANCED QoS Profile

Bandwidth Data Service Provisioning

3. Interface Configuration

Adding UNI QinQ Access

Removing UNI QinQ Access

Adding UNI dot1Q Access

Removing UNI dot1Q Access

Adding UNI Untagged Access

Adding NNI dot1Q Access

Removing NNI dot1Q Access

Obtaining Documentation, Obtaining Support, and Security Guidelines

Copyright © 2005 Cisco Systems, Inc. All rights reserved.