Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Channelized OC48/STM16 IQE Interfaces (SDH Mode)

The Channelized OC48 IQE PIC configured for SDH mode creates a single channelized STM16 interface. You can configure the STM16 interface using the partition statement at the [edit interfaces cstm16-fpc/pic/port] hierarchy level to partition it into the following OC slices:

• 16 channelized AU-4 interfaces or a path layer with 4 STM4 or 16 STM1 interfaces.
• 16 channelized AU-4 interfaces, each partitioned to 3 clear channel E3 interfaces or 63 CE1 or E1 (ITU-T or KLM) interfaces. Combination of E1, CE1 and E3 are not supported in a single cau4.
• 16 channelized AU-4 interfaces, each partitioned to 63 CE1 (ITU-T or KLM) interfaces each partitioned to 31 NxDS0 interfaces

This section describes how to configure the following channelized OC48 IQE interfaces on a Channelized OC48 IQE PIC configured in SDH mode:

Configuring a Channelized OC48/STM16 IQE PIC for SDH Mode

To configure a Channelized OC48/STM16 IQE PIC to operate in SDH mode, include the framing sdh statement at the [edit chassis fpc fpc/pic/port] hierarchy level:

This configuration creates interface cstm16-0/2/0.

For more information, see the Junos OS Administration Library for Routing Devices.

Configuring Clear Channel STM1 and STM4 Interfaces

On a Channelized OC48/STM16 IQE PIC, you can partition the CSTM16 transport layer into 4 clear channel STM4 interfaces or 16 clear channel STM1 interfaces. Combinations of STM4 and STM1 are also permitted, but you must observe the OC-slice parameters.

This configuration creates interface so-fpc/pic/port.channel.

This configuration creates interface so-fpc/pic/port.channel.

Configuring Channelized AU-4 Interfaces

To configure a channelized AU-4 interface, include the partition, oc-slice, and interface-type statements at the [edit interfaces cstm16-fpc/pic/port:channel] hierarchy level, specifying the cau4 interface type:

This configuration creates interface cau4-fpc/pic/port:channel.

The partition number is the sublevel interface partition index. For SDH interfaces, the partition number is not correlated with bandwidth size. For channelized OC48/STM16 IQE interfaces, channelized STM16 interface can have from 1 through 16 partition numbers and channel numbering begins with 1 (:1).

The OC-slice range is the range of SONET/SDH slices. For SDH interfaces, the OC-slice range specifies the bandwidth size required for the interface type you are configuring. The interface type is the channelized interface type or data channel you are creating.

Example: Configuring Channelized AU-4 Interfaces

Configure channelized AU-4 interfaces:

Configuring E3 Interfaces

To configure E3 interfaces, include the partition and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the e3 interface type:

This configuration creates the interfaces e3-fpc/pic/port:channel.

Note: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQE interfaces. You can only apply CoS rules to the aggregate bit streams.

Note: Channelized OC48/STM16 IQE interfaces in M Series, MX Series, and T Series routers reserve channels 0-3 of each OC12 space for STS3C SONET channels. When you configure E3 or T3 channels in OC12 spaces on the described PICs, Junos OS allocates them starting from channel 4 because channels 0-3 are reserved for four STS3c SONET channels. Channel numbers are allocated sequentially in the following order: 4, 5, 6, 7, 8, 9, 11, 0, 1, 2, 3. Only after channels 4 through 11 of the OC12 space are exhausted (all 4 through 11 configured) for E3 or T3 channels will Junos OS then allocate channel 0-3 space for further E3 or T3 channels; thereby using up the 0-3 space previously reserved for four STS3c SONET channels. If a subsequent reconfiguration of this OC12 space occurs, where you try to replace channels 4-6 or 7-9 with an OC3 SONET channel; it fails because the channel 0-3 space is already occupied by the last E3 or T3 channels configured. This causes a failure in channel allocation and the Device Control Daemon (DCD) keeps retrying forever to configure the channel allocation on the interface. The only resolution is to reconfigure the last configured E3/T3 channels with OC3 channels, to free channels 0-3.

Example: Configuring E3 Interfaces

Configure E3 interfaces, using partition 1:

Configuring E1 or Channelized E1 Interfaces

To configure E1 or channelized E1 interfaces, include the partition and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the e1 or ce1 interface type:

This configuration creates the interfaces e1-fpc/pic/port:channel and ce1-fpc/pic/port:channel.

Note: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQE interfaces. You can only apply CoS rules to the aggregate bit streams.

Example: Configuring E1 and Channelized E1 Interfaces

Configure E1 or channelized E1 interfaces, using partition 3 and partition 4:

This configuration creates interfaces e1-0/2/0:1:3 and ce1-0/2/0:1:4.

Configuring NxDS0 IQE Interfaces

Configure channelized NxDS0 IQE interfaces on the channelized E1 IQE interface by including the partition, timeslots, and interface-type statements at the [edit interfaces ce1-fpc/pic/port:channel] hierarchy level, specifying the ds interface type:

This configuration creates the interface ds-fpc/pic/port:channel.

The time-slot range is from 1 through 31. You can designate any combination of time slots. To configure ranges, use hyphens. To configure discontinuous time slots, use commas. You can use a combination of ranges and discontinuous time slots, for example:

Example: Configuring NxDS0 IQE Interfaces

Configure channelized NxDS0 interfaces, using partition 4 and time slots 1 through 10:

This configuration creates interface ds0-0/2/0:1:2:3:4.

Configuring T3 or Channelized T3 Interfaces

To configure T3 or channelized T3 interfaces, include the partition and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the t3 or ct3 interface type:

This configuration creates the interfaces t3-fpc/pic/port:channel and t3-fpc/pic/port:channel.

Note: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ interfaces. You can only apply CoS rules to the aggregate bit streams.

Example: Configuring T3 or Channelized T3 Interfaces

Configure T3 and channelized T3 interfaces, using partition 1 and partition 2:

Configuring T1 or Channelized T1 Interfaces

To configure T1 or channelized T1 interfaces, include the partition and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the t1 or ct1 interface type:

This configuration creates the interfaces t1-fpc/pic/port:channel and t1-fpc/pic/port:channel.

Note: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ interfaces. You can only apply CoS rules to the aggregate bit streams.

Example: Configuring T1 or Channelized T1 Interfaces

Configure T1 and channelized T1 interfaces, using partition 1 and partition 2: