[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Configuring Channelized IQ Interfaces

To enable channelized IQ interfaces, you must perform the following procedures:

Configuring a Clear Channel on a Channelized IQ Interface

A clear channel consolidates the entire bandwidth of a channelized interface into a single unpartitioned stream that looks like a standard interface. For example, a channelized OC12 IQ interface configured as a clear channel appears to have an OC12 SONET interface. To configure a clear channel on a channelized IQ interface, include the no-partition statement at the [edit interfaces cxx-fpc/pic/\port] hierarchy level. Include the interface-type option to set the channelized interface type. Once the interface is established, you can configure it the same way as a regular interface.

[edit]
interfaces {
coc12-1/1/0 {
no-partition interface-type so; # This creates a SONET OC12 interface:
}
so-1/1/0 {
unit 0 {
family inet {
address 10.245.1.1/30;
}
}
}
}

Configuring Single-Level Channels on a Channelized IQ Interface

You can subdivide a channelized interface directly into a set of large end channels. To configure part of a channelized IQ interface as a channel, include the partition statement at the [edit interfaces cxx-fpc/pic/port] hierarchy level. On a channelized OC12 IQ interface, use the oc-slice option to create slice sizes corresponding to the desired bandwidth. On a channelized E1 IQ interface, use the timeslots option to define NxDS0 channels or channel groups. On all channelized IQ interfaces, use the interface-type option to set the interface type (such as SONET OC3 or T3). Once the channel interfaces are established, you can configure them the same way as regular interfaces.

Note: One oc-slice in a channelized OC12 IQ interface partition is equivalent to one OC1/DS3-sized channel. If you add three slices together in sequence as a triplet, these pieces become an OC3-sized interface. However, you can configure triplets only with the following sequential slices: 1–3, 4–6, 7–9, 10–12.

[edit]
interfaces {
coc12-0/0/0 {
partition 1 oc-slice 1-3 interface-type so; # Creates an OC3 SONET
}
so-0/0/0:1 {
encapsulation ppp;
unit 0 {
family inet {
address 10.255.0.2/30;
}
}
}
}

Configuring Multilevel Channels on a Channelized IQ Interface

You can subdivide a channelized interface and then split these subchannelized interfaces into end channels. Creating small end channels might require multiple levels of channelization.

To configure a subdivided channelized interface within a partition of a channelized IQ interface, include the partition statement at the [edit interfaces cxx-fpc/pic/port] hierarchy level. On a channelized OC12 IQ interface, use the oc-slice option to create slice sizes corresponding to the desired bandwidth. On all channelized IQ interfaces, use the interface-type option to set the channelized interface type (such as channelized OC1).

On a channelized OC12 IQ interface, you can convert a subdivided channelized OC1 interface into a T3 or channelized T3 interface. To configure, include the no-partition statement at the [edit interfaces coc1-fpc/pic/port:channel] hierarchy level and set the interface-type to ct3. A ct3-fpc/pic/port:channel interface is the result. Such a conversion is known as M13 with C-bit parity mapping. T1 and DS0 channels created directly from a coc-1 interface use VT mapping.

To further split your channelized interfaces into even smaller channelized interfaces, use the partition and interface-type statements at the [edit interfaces cxx-fpc/pic/port:channel] hierarchy level. You can create channelized OC1, channelized T3, and channelized T1 interfaces, depending on the PIC type.

Finally, you configure these “channels of channels” as end channels. To configure end channels on a segmented channelized IQ interface, include the partition statement at the [edit interfaces cxx-fpc/pic/port:channel] hierarchy level. The number of channels in the hierarchy depends on how finely you partition the channelized IQ interface. Use the timeslots option to select NxDS0 level channels and the interface-type option to set the interface type (such as T1 or NxDS0). Once the resulting channels have been established, you can configure them as regular interfaces.

[edit]
interfaces {
coc12-0/0/0 {
partition 2 oc-slice 4 interface-type coc1; # Creates channelized OC1
partition 3 oc-slice 5 interface-type coc1; # interfaces: coc1-0/0/0:2,
partition 4 oc-slice 6 interface-type coc1; # :3, and :4.
}
coc1-0/0/0:2 {
no-partition interface-type t3; # Converts a channelized OC1 to
}
t3-0/0/0:2 {
encapsulation ppp;
unit 0 {
family inet {
address 10.255.0.6/30;
}
}
coc1-0/0/0:3 {
no-partition interface-type ct3; # Creates a channelized T3 interface:
}
ct3-0/0/0:3 {
partition 1-28 interface-type t1; # Creates 28 T1 interfaces:
}
coc1-0/0/0:4 {
partition 1 interface-type ct1; # Creates a channelized T1 interface:
}
ct1-0/0/0:4:1 {
partition 1 timeslots 1 interface-type ds; # Creates a 1xDS0 interface:
...# ds-0/0/0:4:1:1.
partition 24 timeslots 24 interface-type ds; # Creates a 1xDS0 interface:
}
t1-0/0/0:3:1 {
encapsulation ppp;
unit 0 {
family inet {
address 10.255.0.26/30;
}
}
}
...
}
ds-0/0/0:4:1:24 {
encapsulation ppp;
unit 0 {
family inet {
address 10.255.0.214/30;
}
}
}
}

A useful operational command you can use with all channelized IQ interfaces is the show interfaces interval command. It shows a summary of alarms, status indicators, and performance monitoring statistics in 15-minute increments over the past 24 hours. More detail on each of these indicators can be seen with the show interfaces extensive command:


user@router> show interfaces interval cstm1-0/0/0
Physical interface: cstm1-0/0/0, SNMP ifIndex: 32
  17:23-current:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  17:08-17:23:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  16:53-17:08:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  16:38-16:53:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  16:23-16:38:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  16:08-16:23:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  15:53-16:08:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  15:38-15:53:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  15:23-15:38:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  15:08-15:23:
    RS-ES: 33, RS-SES: 33, RS-SEFS: 32, MS-ES: 32, MS-SES: 32, MS-UAS: 4
  14:53-15:08:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  14:38-14:53:      
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  14:23-14:38:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  14:08-14:23:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  13:53-14:08:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  13:38-13:53:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  13:23-13:38:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  13:08-13:23:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  12:53-13:08:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  12:38-12:53:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  12:23-12:38:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  12:08-12:23:
    RS-ES: 0, RS-SES: 0, RS-SEFS: 0, MS-ES: 0, MS-SES: 0, MS-UAS: 0
  11:53-12:08:
    RS-ES: 11, RS-SES: 11, RS-SEFS: 11, MS-ES: 11, MS-SES: 11, MS-UAS: 1
  Interval Total:
    RS-ES: 44, RS-SES: 44, RS-SEFS: 43, MS-ES: 43, MS-SES: 43, MS-UAS: 5
[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]