Configuring Channelized SONET/SDH

Feature History for Configuring Channelized SONET/SDH

Support for the following SPA was introduced on the Cisco ASR 9000 Series Router:

Cisco 2-Port Channelized OC-12/DS0 SPA

Release 4.0.0

Support for the following SPA was introduced on the Cisco ASR 9000 Series Router:

Cisco 1-Port Channelized OC-48/STM-16 SPA

Support for SDH, E3, E1, and POS channelization was added for the Cisco 2-Port Channelized OC-12/DS0 and Cisco 1-Port Channelized
OC-48/STM-16 SPAs.

Release 4.0.1

Support for the following SPA was introduced on the Cisco ASR 9000 Series Router:

Cisco 1-Port Channelized OC-3/STM-1 SPA

Prerequisites for Configuring Channelized SONET/SDH

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include
the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact
your AAA administrator for assistance.

Before configuring Channelized SONET/SDH, be sure that the following tasks and conditions are met:

You have at least one of the following SPAs installed in your chassis:

Cisco 1-Port Channelized OC-3/STM-1 SPA

Cisco 2-Port Channelized OC-12c/DS0 SPA

Cisco 1-Port Channelized OC-48/STM-16 SPA

You should know how to apply and specify the SONET controller name and interface-path-id with the generalized notation rack/slot/module/port. The SONET controller name and interface-path-id are required with the controller sonet command.

Information About
Configuring Channelized SONET/SDH

To configure Channelized SONET/SDH, you must understand these
concepts:

A channelized SONET interface is a composite of STS streams,
which are maintained as independent frames with unique payload pointers. The
frames are multiplexed before transmission.

When a line is channelized, it is logically divided into smaller
bandwidth channels called
paths. These paths carry the SONET payload. The sum of the
bandwidth on all paths cannot exceed the line bandwidth.

When a line is not channelized, it is called
clear channel, and the full bandwidth of the line is
dedicated to a single channel that carries broadband services.

An STS stream can be channelized into the following types of
channels:

T3/E3

VT1.5 mapped T1

Packet over SONET/SDH (POS) (OC12 and OC48 only)

The T3/E3 channels can be channelized further into T1s, and the
T1s can be channelized into time slots (DS0s), except on the 1-Port
Channelized OC-48/STM-16 SPA, which does not support T1 or DS0s.

Channelizing a SONET line consists of two primary processes:

Configuring the controller

Configuring the interface into channelized paths

You configure the controller first by setting the mode of the
STS path. The mode can be set to T3, or VT1.5-mapped T1, or POS, depending on
your hardware support.

Note

POS is supported only on the STS-3c and STS-12c paths on the
Cisco 1-Port Channelized OC-12/DS0 SPA and on the STS-3c, STS-12c, and STS-48c
paths on the Cisco 1-Port Channelized OC-48/STM-16 SPA.

When the mode is specified, the respective controller is
created, and the remainder of the configuration is applied on that controller.
For example, mode T3 creates a T3 controller. The T3 controller can then be
configured to a serial channel, or it can be further channelized to carry T1s,
and those T1s can be configured to serial interfaces.

Depending on the support for
your installed SPA, each STS path can be independently configured into T3s,
E3s, or VTGs, and so on.

This figure shows an example
of three STS paths for a SONET controller. However, the 2-Port Channelized
OC-12/DS0 SPA supports up to 12 STS paths, and the 1-Port Channelized
OC-48/STM-16 SPA supports up to 48 STS paths, but the 1-Port Channelized
OC-48/STM-16 SPA does not support VTGs.

Figure 1. SONET Controller STS
Paths

This figure shows an example of some SONET controller
configuration combinations.

Note

The 1-Port Channelized
OC-48/STM-16 SPA on the Cisco ASR 9000 Series Router does not support VTGs.

VTG paths are only supported
on the Cisco 1-Port Channelized OC-3/STM-1 SPA and Cisco 2-Port Channelized
OC-12c/DS0 SPA on the Cisco ASR 9000 Series Router.

Figure 3. SONET VTG Channelized Paths

Channelized SDH
Overview

Synchronous Digital Hierarchy
(SDH) is the international equivalent of SONET.

Channelized SDH is supported
on the following SPAs:

Cisco 1-Port Channelized OC-48/STM-16 SPA

Cisco 1-Port Channelized OC-3/STM-1 SPA

Cisco 2-Port Channelized OC-12/DS0 SPA

A Synchronous Transport
Module (STM) signal is the Synchronous Digital Hierarchy (SDH) equivalent of
the SONET STS, but the numbers are different for each bandwidth. In this guide,
the STM term refers to both path widths and optical line rates. The paths
within an STM signals are called administrative units (AUs).

A summary of the basic
terminology differences between SONET and SDH is as follows:

SONET STS is equivalent to SDH administrative unit (AU)

SONET VT is equivalent to SDH tributary unit (TU)

SDH basic building blocks are STM-1 (equivalent to STS-3) and
STM-0 (equivalent to STS-1)

An administrative unit (AU)
is the information structure that provides adaptation between the higher-order
path layer and the multiplex section layer. It consists of an information
payload (the higher-order virtual container) and an administrative unit
pointer, which indicates the offset of the payload frame start relative to the
multiplex section frame start.

An AU can be channelized into
tributary units (TUs) and tributary unit groups (TUGs).

An administrative unit 4
(AU-4) consists of three STM-1s or an STM-3.

An administrative unit 3
(AU-3) consists of one STM-1.

An administrative unit group
(AUG) consists of one or more administrative units occupying fixed, defined
positions in an STM payload.

Table 1. SONET and SDH Terminology Equivalencies

SONET Term

SDH Term

SONET

SDH

STS-3c

AU-4

STS-1

AU-3

VT

TU

SPE

VC

Section

Regenerator Section

Line

Multiplex Section

Path

Path

On the
Cisco ASR 9000 Series Router, the following levels of SDH channelization are
supported:

1-Port Channelized OC-3/STM-1 SPA

AU4 to TUG-3 to TUG-2 to VC-12 to E1 to NxDS0

AU4 to TUG-3 to VC-3 to DS3 (Clear Channel)

AU4 to TUG-3 to VC-3 to E3 (Clear Channel)

AU3 to TUG-2 to VC-11 to DS1 to NxDS0

2-Port Channelized OC-12/DS0 SPA

AU-4-4c (VC-4-4c)

AU-4 (VC-4)

AU-4 to TUG-3 to VC-3 to DS3

AU-4 to TUG-3 to VC-3 to E3

AU-4 to TUG-3 to TUG-2 to VC-11 to T1 to NxDS0

AU-4 to TUG-3 to TUG-2 to VC-12 to E1to NxDS0

AU-3 to VC-3 to DS3

AU-3 to TUG-2 to VC-11 to T1 to NxDS0

AU-3 to TUG-2 to VC-12 to E1to NxDS0

AU-3 to VC-3 to E3

AU-3 to VC-3 to DS3 to T1 to NxDS0

AU-3 to VC-3 to DS3 to E1 to NxDS0

1-Port Channelized OC-48/STM-16 SPA

DS3

E3

AU-3 (VC-3)

AU-4 (VC-4)

AU-4-4c (VC-4-4c)

AU-4-16c (VC-4-16c)

This figure shows an example of SDH AU-3 paths that can be
configured on certain supported SPAs.

Note

The 1-Port Channelized
OC-48/STM-16 SPA does not support further channelization of AU-3 paths into
T1s.

Figure 5. SDH AU3 Paths

This figure shows the SDH AU4 paths that can be configured on
supported SPAs.

Note

The 1-Port Channelized
OC-48/STM-16 SPA only supports channelization to the T3 or E3 level. Further
channelization of AU-4 paths is not supported.

Figure 6. SDH AU4 Paths

Default Configuration Values for Channelized SONET/SDH

This table describes the default configuration parameters that are present on the Channelized SONET/SDH.

Example:

Example:

RP/0/RSP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration eliminates the forced
administrative down on the interface, enabling it to move to an up or down
state (assuming that the parent SONET layer is not configured administratively
down).

Step 23

end or
commit

Example:

RP/0/0RSP0/CPU0:router(config-sonet)# end

or

RP/0/RSP0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command, the system prompts you to commit
changes:

Example:

Example:

RP/0/RSP0/CPU0:router (config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration
eliminates the forced administrative down on the interface, enabling it to move
to an up or down state (assuming that the parent SONET layer is not configured
administratively down).

Step 14

end or
commit

Example:

RP/0/RSP0/CPU0:router(config-sonet)# end

or

RP/0/RSP0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command,
the system prompts you to commit changes:

Example:

Example:

RP/0/RSP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration eliminates the forced
administrative down on the interface, enabling it to move to an up or down
state (assuming that the parent SONET layer is not configured administratively
down).

Step 15

end or
commit

Example:

RP/0/RSP0/CPU0:router(config-sonet)# end

or

RP/0/RSP0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command, the system prompts you to commit
changes:

Example:

Creates a protect channel for the APS group, where
0 designates a protect channel.

Note

The protect channel must be assigned before the active channel
can be assigned.

To configure APS where both
channels are on one router, use the
channel
local command for both the protect
and active channels. To configure APS using two different routers where
the active channel is on one router and the protect channel is on another
router, use the
channel
local command for either the protect or the active channel, but
use the
channel
remote command for the other channel.

Example:

Creates an active channel for the APS group, where
1 designates an active channel.

Note

The active channel must be assigned after the protect channel is
assigned.

To configure APS where both
channels are on one router, use the
channel
local command for both the
protect and active channels. To configure APS using two different routers
where the active channel is on one router and the protect channel is on another
router, use the
channel local command for either the protect or
the active channel, but use the
channel remote command for the other channel.

The
au command does not
specify the AU type. It specifies the number of the AU group for the AU type
that you want to configure. The range for the AU command varies based on
whether you are configuring AU-3 or AU-4.

Step 6

mode mode

Example:

RP/0/RSP0/CPU0:router(config-auPath)# mode c11-t1

Sets the mode of interface at the AU level. AU-3 paths can be
mapped to c11-t1 or c12-e1 on supported SPAs.

Step 7

root

Example:

RP/0/RSP0/CPU0:router(config-auPath)# root

Exits to global configuration mode.

Step 8

controller t1 interface-path-id

Example:

RP/0/RSP0/CPU0:router(config)# controller T1 0/1/1/0/0/0/0

Enters T1 controller configuration submode and specifies the T1
controller name and
interface-path-id with the
rack/slot/module/port/auNum/t1Num
notation.

Step 9

channel-group number

Example:

RP/0/RSP0/CPU0:router(config-t1)# channel-group 0

Sets the channel-group number to which time slots are assigned.
The range is from 1 to 28.

Example:

Example:

RP/0/RSP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration eliminates the forced
administrative down on the interface, enabling it to move to an up or down
state (assuming that the parent SONET layer is not configured administratively
down).

Step 19

end or
commit

Example:

RP/0/RSP0/CPU0:router(config-sonet)# end

or

RP/0/RSP0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command, the system prompts you to commit
changes:

The
au command does not specify the AU type. It
specifies the number of the AU group for the AU type that you want to
configure. The range for the AU command varies based on whether you are
configuring AU-3 or AU-4.

Step 6

mode t3

Step 7

or

Step 8

mode e3

Example:

RP/0/RSP0/CPU0:router(config-auPath)# mode t3

Sets the mode of interface at the AU level to T3 or E3.

Step 9

root

Example:

RP/0/RSP0/CPU0:router(config-auPath)# root

Exits to global configuration mode.

Step 10

controller {t3
| e3 }
interface-path-id

Example:

RP/0/RSP0/CPU0:router(config)# controller T3 0/1/1/0/0

Enters T3 or E3 controller configuration submode and specifies
the T3 or E3 controller name and
interface-path-id with the
rack/slot/module/port/auNum
notation.

Step 11

mode serial

Example:

RP/0/RSP0/CPU0:router(config-t3)# mode serial

Configures the mode of the port to be clear channel serial.

Step 12

show
configuration

Example:

RP/0/RSP0/CPU0:router(config-t3)# show configuration

Displays the contents of uncommitted configuration.

Step 13

root

Example:

RP/0/RSP0/CPU0:router(config-t3)# root

Exits to global configuration mode.

Step 14

interface serial interface-path-id

Example:

RP/0/RSP0/CPU0:router(config)# interface serial 0/1/1/0/0/0:0

Specifies the complete interface number with the
rack/slot/module/port/T3Num/T1num:instance
notation.

Example:

Example:

RP/0/RSP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration eliminates the forced
administrative down on the interface, enabling it to move to an up or down
state (assuming that the parent SONET layer is not configured administratively
down).

Step 18

end
or
commit

Example:

RP/0/RSP0/CPU0:router(config-sonet)# end

or

RP/0/RSP0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command, the system prompts you to commit
changes:

The
au command does not
specify the AU type. It specifies the number of the AU group for the AU type
that you want to configure. The range for the AU command varies based on
whether you are configuring AU-3 or AU-4.

Step 6

mode tug3

Example:

RP/0/0/CPU0:router(config-auPath)# mode tug3

Sets the mode of interface at the AU level. Currently only TUG3
is supported.

Step 7

width number

Example:

RP/0/0/CPU0:router(config-auPath)# width 3

Configures the number of the AU streams.

Step 8

tug3 number

Example:

RP/0/0/CPU0:router(config-auPath)#tug3 1

Specifies the Tributary Unit Group (TUG)
number and enters the config-tug3Path mode. The
range is 1 to 3.

Step 9

mode mode

Example:

RP/0/0/CPU0:router(config-tug3Path)# mode e3

Sets the mode of interface at the tug3 level. The modes are:

c11 —TUG-3 path carrying TU-11

c11-t1 —TUG-3 path carrying TU-11 to T1

c12 —TUG-3 path carrying TU-12

c12-e1 —TUG-3 path carrying TU-12 to E1

e3 —TUG-3 path carrying E3

t3 —TUG-3 path carrying T3

Note

The 1-Port Channelized
OC-48/STM-16 SPA only supports the
e3 and
t3 options.

Step 10

root

Example:

RP/0/0/CPU0:router(config-tug3Path)# root

Exits to global configuration mode.

Step 11

controller nameinstance

Example:

RP/0/0/CPU0:router(config)# controller e3 0/1/1/0/0/0

Enters controller configuration submode and specifies the
controller name and instance identifier with the
rack/slot/module/port/name/instance
notation. The controller names are:

e3 —TUG3 path carrying E3

t3 —TUG3 path carrying T3

e1 —channelized E1 port

Note

In this step, you can
create an E3 or T3 controller and add T1 channels under the T3 controller as
shown inStep 14, or you can create a channelized E1 port at this point.

E1 is not supported on the
1-Port Channelized OC-48/STM-16 SPA.

Step 12

mode mode

Example:

RP/0/0/CPU0:router(config-e3)#mode e1

Sets the mode of interface. The modes are:

e1 —Channelized into 21 E1s

serial —Clear Channel carrying HDLC-like payload

t1 —Channelized into 28 T1s

Note

T1 and E1 are not supported
on the 1-Port Channelized OC-48/STM-16 SPA.

Step 13

root

Example:

RP/0/0/CPU0:router(config-e3)# root

Exits to global configuration mode.

Step 14

controller nameinstance

Example:

RP/0/0/CPU0:router(config)# controller E1 0/1/1/0/0/0/0/0

Enters controller configuration submode and specifies the
controller name and instance identifier with the
rack/slot/module/port/name/instance1/instance2
notation. The controller names are:

Example:

Specifies time slots for the interface by number with the
num1:num2:num3:num4 notation, or by range with the
range1-range2 notation.

Step 19

show
configuration

Example:

RP/0/0/CPU0:router(config-e1-channel_group)# show configuration

Displays the contents of uncommitted configuration.

Step 20

root

Example:

RP/0/0/CPU0:router(config-e1-channel_group)# root

Exits to global configuration mode.

Step 21

interface serial interface-path-id

Example:

RP/0/0/CPU0:router(config)# interface serial 0/1/1/0/0/0:0

Specifies the complete interface number with the
rack/slot/module/port/T3Num/T1num:instance
notation.

Step 22

encapsulation {frame-relay |
hdlc |
ppp }

Example:

Router(config-if)# encapsulation frame-relay | hdlc | ppp

Specifies the encapsulation type with the one of the following
keywords:

frame-relay —Frame Relay network protocol

hdlc —High-level Data Link Control (HDLC)
synchronous protocol

ppp —Point-to-Point Protocol

Step 23

ipv4 ip-address mask

Example:

Router(config-if)# ip address 10.10.10.10 255.255.255.255

Assigns an IP address and subnet mask to the interface.

Step 24

no shutdown

Example:

RP/0/0/CPU0:router (config-if)# no shutdown

Removes the shutdown configuration.

Note

Removal of the shutdown configuration eliminates the forced
administrative down on the interface, enabling it to move to an up or down
state (assuming that the parent SONET layer is not configured administratively
down).

Step 25

end or
commit

Example:

RP/0/0/CPU0:router(config-sonet)# end

or

RP/0/0/CPU0:router(config-sonet)# commit

Saves configuration changes.

When you issue the
end command, the system prompts you to commit
changes: