Cisco RPM-XF Specifications Page 74

  • Download
  • Add to my manuals
  • Print
  • Page
    / 688
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 73
2-18
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 2 Preparing AXSM Lines for Communication
General AXSM Provisioning Procedures
Channelizing a Line
The channelization feature allows you to create a simple or complex combination of paths for each line
on your AXSM-XG back card. The simplest approach assigns the same bandwidth to each path. A more
complex approach creates different path widths within the same SONET/SDH/T3 line. Depending on the
type of line being channelized and the channelization scheme used, different types of paths are created.
Note The CLI shows SONET naming conventions in place of their equivalent SDH terms. For example, the
display for SDH AU paths shows “STS”, the display for VC/TU paths shows “VT”.
Because paths support both ATM and DS3 payloads, you need to specify which payload type will travel
over each path, and you may want to configure additional options for DS3 paths. Table 2-8 shows the
channel payloads that are supported by each interface type.
You can assign ATM service to any level path down to DS3. The ATM service is carried on an STS-3
down to nxDS3 (IMA), where n is the number of configured DS3s. See the Adding ATM Ports” section
on page 3-27 to configure ATM service to a DS3 line.
Keep the following in mind when configuring paths on a channelized line:
You can not configure channelization on a line that is already carrying active paths. Before you can
configure a previously channelized line, you must bring down all previously configured paths on that
line with the dnpath command.
You can not configure a channelized line to be in clear channel mode if it is carrying active paths.
Before you can configure a channelized line to be clear channel, you must bring down all previously
configured paths on that line with the dnpath command.
The sum of the bandwidths on the provisioned physical interfaces can not exceed the total bandwidth
of the physical line (OC3 or DS3).
A single STS-1 or AU-3 can carry one E3 or one DS3 (T3).
All tributaries within an AU-3 (or TUG-3 within AU-4) must be the same size: either VC-11/TU-11
or VC-12/TU-12.
A single TUG-3 in an AU-4 can carry 21E1s, 28 T1s, one E3, or one T3.
A single AU-4 can carry 84 T1s, 63 E1s, 3 T3s, or 3 E3s.
You can not map channelized DS3 lines or paths into VC3/TU-3s, TUG-3s, or AU-4s.
A single STS-1 will carry one E3 or one T3.
After a line is channelized, all the paths are initially down. To use a channel:
Enter the uppath command to bring up the paths you want to configure.
Then enter the cnfpath command to configure them. The cnfpath command parameters are
different, depending on the type of path you are configuring. Take care to only use the
parameters that are valid for the path type you are configuring.
Table 2-9 describes the possible cnfpath command parameters for all path types.
Table 2-8 Channlized Interface Mapping
Path/Interface Type Possible Channel Payloads
STS-1
DS3
ATM
Page view 73
1 ... 73 74 75 ... 688

Comments to this Manuals

No comments