Configuring Physical Components with CLI
This section provides information to configure cards, adapter cards, and ports.
Topics in this section include:
Preprovisioning Guidelines
The 7705 SAR platforms each have two ports on the chassis to connect terminals for management access: a console port for a terminal connection and a management port for a Telnet connection.
The console port is used to configure parameters locally through a direct connection from a system console. The management port is used to configure parameters remotely through a connection to a remote workstation, using Telnet or SSH to open a secure shell connection.
For more information about management connections, refer to the appropriate chassis installation guide, in the section on router management connections.
Predefining Entities
In order to initialize an adapter card, the IOM type and adapter card type must match the preprovisioned parameters. In this context, preprovisioning means to configure the entity type (IOM type, adapter card type, port, and interface) that is planned for an adapter card. Preprovisioned entities can be installed but not enabled, or the slots can be configured but remain empty until populated. Provisioning means that the preprovisioned entity is installed and enabled.
You can preprovision ports and interfaces after the IOM is activated (card slot and card type are designated) and adapter card types are specified.
Preprovisioning a Port or SCADA Bridge
Before a port or SCADA bridge can be configured, the adapter card slot must be preprovisioned with an allowed adapter card type (for a SCADA bridge, the only type allowed is isc, for the Integrated Services card).
Preprovisioning recommendations (for ports only) include:
- Ethernet
- Configure an access port for customer-facing traffic on which services are configured.
- Configure a network port for uplink traffic.An encapsulation type must be specified in order to distinguish services on the access port. Encapsulation types must also be specified for network ports. By default, the encapsulation type for Ethernet ports in network mode is null.
- Channelized
- Channelized ports can be configured on the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, 2-port OC3/STM1 Channelized Adapter card, 4-port OC3/STM1 Channelized Adapter card, 8-port Voice & Teleprotection card (access mode only), 8-port FXO Adapter card (access mode only), 6-port FXS Adapter card (access mode only), 4-port DS3/E3 Adapter card (DS3 ports only), 12-port Serial Data Interface card (access mode only), 6-port E&M Adapter card (access mode only) and 4-port T1/E1 and RS-232 Combination module.
- Configure an access port for customer-facing traffic on which services are configured.
- Configure a network port for uplink traffic.An encapsulation type must be specified in order to distinguish services on the access port or channel. For network mode, the encapsulation type is set to ppp-auto and cannot be changed.
Maximizing Bandwidth Use
For the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and 2-port OC3/STM1 Channelized Adapter cards, after ports are preprovisioned, multilink bundles (MLPPP) or IMA groups can be configured to increase the bandwidth available between two nodes.
All physical links or channels in a bundle or group combine to form one logical connection. A bundle or group also provides redundancy in case one or more links that participate in the bundle fail. For command syntax, see Configuring Multilink PPP Bundles. To configure channelized ports for TDM, see Configuring SONET/SDH Port Parameters.
For 12-port Serial Data Interface cards and the RS-232 ports on the 4-port T1/E1 and RS-232 Combination module, some or all of a port bandwidth can be dedicated to a channel by aggregating a number of DS0s into a single bundle. Serial data transmission rates below the rate of a single DS0, that is, less than 64 kb/s, are achieved using the High Capacity Multiplexing (HCM) proprietary protocol. These rates are known as subrates, and are supported only when operating in RS-232 mode or X.21 mode.
 | Note:
A DS0 channel operating at a rate less than 64 kb/s still uses a full 64 kb/s timeslot. |
Using Partial Bandwidth
The 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, and the T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module support fractional T1/E1 on a PPP channel group in network mode. Fractional T1/E1 allows one or more DS0 channels to be bundled together (up to the maximum bandwidth of the network link), allowing the customer to use only that portion of the link that is needed. This means that the PPP service can use a selected number of timeslots (octets) in the network T1 or E1 link, thus reducing the amount of T1 or E1 bandwidth that must be leased or purchased from the attached carrier. This leads to multiplexing efficiencies in the transport network.
Only one channel group can be configured per port. When the channel group is configured for ppp-auto encapsulation and network mode, all timeslots (channels) are automatically allocated to the channel group. The user can then configure the number of timeslots needed. Timeslots not selected cannot be used.
Basic Configuration
The basic 7705 SAR OS interface configuration must include the following tasks:
- identify chassis slot (step in activating the IOM)
- specify card type (step in activating the IOM)
- identify adapter card (MDA) slot
- specify adapter card type (mda-type) (must be an allowed adapter card type)
- specify adapter card mode (mda-mode) (supported on the 4-port DS3/E3 Adapter card, the 16-port T1/E1 ASAP Adapter card version 2, the 32-port T1/E1 ASAP Adapter card, and the 10-port 1GigE/1-port 10GigE X-Adapter card)
- identify specific port to configure
The following example displays some card and port configurations on the 7705 SAR-8.
| Note:
The 7705 SAR-18 displays similar output with the exception being that the MDA number goes from 1 to 12 and from X1 to X4 (for XMDA cards). |
Common Configuration Tasks
The following basic system tasks are performed, as required.
Configuring Cards and Adapter Cards
This section contains the following topics:
Configuring Cards
Card configurations must include a chassis slot designation. A slot must be preconfigured with the type of card and adapter cards that are allowed to be provisioned.
The mda-mode command is used on the following adapter cards to configure the appropriate encapsulation methods (cem-atm-ppp or cem-fr-hdlc-ppp) that are required to support pseudowire services:
- 4-port DS3/E3 Adapter card
- 16-port T1/E1 ASAP Adapter card, version 2
- 32-port T1/E1 ASAP Adapter card
The mda-mode command is also used on the 10-port 1GigE/1-port 10GigE X-Adapter card to configure the card for either 10-port 1GigE mode or 1-port 10GigE mode.
The following CLI syntax shows an example of configuring a chassis slot and card (to activate the IOM) and adapter cards on the 7705 SAR-8.
The following CLI syntax shows an example of configuring a chassis slot and card (to activate the IOM) and adapter cards on the 7705 SAR-18.
Configuring Adapter Card Network Queue QoS Policies
Network queue QoS policies can optionally be applied to adapter cards. Network queue policies define the ingress network queuing at the adapter card node level. Network queue policy parameters are configured in the config>qos context. For more information on network queue policies, refer to the 7705 SAR OS Quality of Service Guide, “Network Queue QoS Policies”.
Queue policies do not apply to the Auxiliary Alarm card.
Use the following CLI syntax to configure network queue policies on an adapter card.
Configuring Ring Adapter Card or Module Network and Network Queue QoS Policies
Network and network queue QoS policies can optionally be applied to a ring adapter card or module, such as the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module.
Network policies define ring type network policies to a ring adapter card, where a ring type is a network-policy-type.
Network queue policies define the add/drop port network queuing at the adapter card node level.
Network and network queue policy parameters are configured in the config>qos context. For more information on network queue policies, refer to the 7705 SAR OS Quality of Service Guide, “Network QoS Policies” and “Network Queue QoS Policies”.
Use the following CLI syntax to configure network and network queue policies on an adapter card.
Configuring Adapter Card Fabric Statistics
The collection of fabric statistics can be enabled on an adapter card to report about the fabric traffic flow and potential discards.
Fabric statistics do not apply to the Auxiliary Alarm card.
Use the following syntax to configure fabric statistics on an adapter card.
Configuring Adapter Card Fabric Profile
Ingress fabric profiles can be configured on an adapter card, in either a network or access context, to allow network ingress to fabric shapers to be user-configurable at rates that provide up to 1 Gb/s switching throughput from the adapter card towards the fabric. For more information on fabric profiles, refer to the 7705 SAR OS Quality of Service Guide, “QoS Fabric Profiles”.
Fabric profiles do not apply to the Auxiliary Alarm card.
Use the following CLI syntax to assign a fabric profile on an adapter card.
Configuring Adapter Card Clock Mode
Clocking mode is defined at the adapter card level. There are three clocking modes available: differential, adaptive, and dcr-acr, which is a mixture of both differential and adaptive. The dcr-acr option enables differential and adaptive clocking on different ports of the same card or chassis. Differential and dcr-acr clocking modes also support a configurable timestamp frequency. In order to carry differential clock recover information, the RTP header must be enabled on the SAP.
The following chassis, cards, and modules support all clocking modes:
- 16-port T1/E1 ASAP Adapter card, version 2
- 32-port T1/E1 ASAP Adapter card
- 7705 SAR-M (variants with T1/E1 ports)
- 7705 SAR-A (variant with T1/E1 ports)
- T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module
When the timestamp frequency is configured for differential or dcr-acr mode on a 4-port T1/E1 and RS-232 Combination module, the configured value will take effect on both modules installed in the 7705 SAR-H.
The following chassis and cards support adaptive clocking mode only:
- 16-port T1/E1 ASAP Adapter card, version 1
- 7705 SAR-F (T1/E1 ports)
The following cards support differential clocking mode only:
- 4-port OC3/STM1 Channelized Adapter card (T1/E1 channels)
- 4-port DS3/E3 Adapter card (T1/E1 channels on DS3 ports; E3 ports cannot be channelized)
Use the following CLI syntax to configure adaptive clocking mode.
Use the following CLI syntax to configure differential clocking mode or a combination of differential and adaptive clocking modes with a timestamp frequency.
Configuring Adapter Card Voice Attributes
Use the following CLI syntax to assign the type of companding law and signaling to be used on a 6-port E&M Adapter card installed in a 7705 SAR-8 and 7705 SAR-18 chassis.
Use the following CLI syntax to assign the type of companding law to be used on the FXO and FXS ports on an 8-port Voice & Teleprotection card installed in a 7705 SAR-8 or 7705 SAR-18 chassis.
Use the following CLI syntax to assign the type of companding law to be used on the FXO ports on an 8-port FXO Adapter card installed in a 7705 SAR-8 or 7705 SAR-18 chassis.
Use the following CLI syntax to assign the type of companding law to be used on the FXS ports on a 6-port FXS Adapter card installed in a 7705 SAR-8 or 7705 SAR-18 chassis.
Configuring Ring Adapter Card or Module Parameters
Use the following CLI syntax to configure the adapter card or module parameters on the 2-port 10GigE (Ethernet) Adapter card or 2-port 10GigE (Ethernet) module.
After configuring the adapter card or module, you can use the config>card>mda>ring>info detail command to display the information on the ring adapter card or module.
Configuring Auxiliary Alarm Card, Chassis, and Ethernet Port External Alarm Parameters
Use the following CLI syntax to configure the external alarm parameters for the Auxiliary Alarm card, 7705 SAR Ethernet ports (supported on all platforms with Ethernet ports), and for the four alarm inputs on the fan module (for the 7705 SAR-8), alarm connector (for the 7705 SAR-F, 7705 SAR-M (all variants), 7705 SAR-Wx (all variants), 7705 SAR-H, and 7705 SAR-Hc), and alarm module (for the 7705 SAR-18).
The output commands apply to the Auxiliary Alarm card only. The debounce and normally commands do not apply to external alarm parameters configured on an Ethernet port.
The following CLI syntax shows an example of configuring custom alarms on Ethernet ports.
Use the show external-alarms input command to display Ethernet port alarm input information.
Displaying Adapter Card Information
After performing the adapter card configuration, you can use the config info command to display the information on the 7705 SAR-8.
Use the config info detail command to display the adapter card detailed configuration information on the 7705 SAR-8.
Configuring Ports
This section provides the CLI syntax and examples to configure the following:
Configuring APS Port Parameters
APS has the following configuration rules.
- A working port must be added first. Then a protection port can be added or removed at any time.
- The protection port must be removed from the configuration before the working port is removed.
- A protection port must be shut down before being removed from an APS group.
- A path cannot be configured on a port before the port is added to an APS group.
- A working port cannot be removed from an APS group until the APS port path is removed.
- When ports are added to an APS group, all path-level configurations are available only at the APS port level and configuration on the physical member ports is blocked.
- When a port is a protection circuit of an APS group, the configuration options available in the config>port port-id>sonet-sdh context are not allowed for that port unless they are in the following exception list:
- clock-source
- [no] loopback
- [no] report-alarm
- section-trace
- [no] threshold
SC-APS is supported in unidirectional and bidirectional mode on the 2-port OC3/STM1 Channelized Adapter card for TDM CES (Cpipes) and TDM CESoETH with MEF 8, on the 4-port OC3/STM1 Channelized Adapter card with Cpipes, and on the 4-port OC3/STM1 Clear Channel Adapter card when configured for POS. MC-APS is supported in bidirectional mode on the 2-port OC3/STM1 Channelized Adapter card for TDM CES (Cpipes) and TDM CESoETH with MEF 8, and on the 4-port OC3/STM1 Channelized Adapter card with Cpipes.
APS can be configured in SC-APS mode with both working and protection circuits on the same node, or in MC-APS mode with the working and protection circuits configured on separate nodes.
Use the following CLI syntax to configure APS port parameters for an SC-APS group.
The following CLI syntax shows an example of configuring ports for SC-APS. The only mandatory configuration required to create an SC-APS group is to configure the working and protection circuit.
Use the config port info command to display port configuration information.
Use the following CLI syntax to configure APS port parameters for an MC-APS group.
The following CLI syntax shows an example of configuring an MC-APS working circuit on a node. The only mandatory configuration required to create an MC-APS group is to configure the working and protection circuit, and the neighbor address.
To complete the MC-APS configuration, log on to the protection node, configure an APS group with the same APS ID as the working group, and configure the protection circuit. The MC-APS signaling path is established automatically when APS groups with matching IDs are both configured.
The following CLI syntax shows an example of configuring an MC-APS protection circuit on a node.
Use the config port info command to display port configuration information.
SC-APS and MC-APS on the 2-port OC3/STM1 Channelized Adapter card (access side) normally support only TDM CES (Cpipes). SC-APS and MC-APS support Epipes with TDM SAPs when the MEF 8 service is used. The following CLI syntax shows an example of TDM CESoETH with MEF 8 for APS.
Configuring a Microwave Link
A microwave link can be configured on a 7705 SAR-8 or 7705 SAR-18 in order to support a microwave connection from ports 1 through 4 on a Packet Microwave Adapter card to an MPR-e radio that may be configured in standalone mode or Single Network Element (Single NE) mode.
Use the following CLI syntax to configure a microwave link (in the example, the MPR-e radios are configured in standalone mode):
The following CLI syntax shows an example of configuring a microwave link on the 7705 SAR-8; the MPR-e radios are in standalone mode.
Configuring Ethernet Port Parameters
Use the following CLI syntax to configure Ethernet network and access port parameters. For more information on the dot1x parameter see Configuring 802.1x Authentication Port Parameters.
Configuring an Ethernet Network Port
A network port is network facing and participates in the service provider transport or infrastructure network processes.
Use the following basic CLI syntax to configure Ethernet network mode port parameters.
The following CLI syntax shows an example of configuring an Ethernet port for network mode.
Use the config port info command to display port configuration information.
Configuring an Ethernet Access Port
Services are configured on access ports used for customer-facing traffic. If a Service Access Point (SAP) is to be configured on a port, it must be configured for access mode.
When a port is configured for access mode, the appropriate encapsulation type can be specified to distinguish the services on the port. Once a port has been configured for access mode, multiple services may be configured on the port.
Use the following basic CLI syntax to configure Ethernet access mode port parameters
The following CLI syntax shows an example of configuring an Ethernet port for access mode.
Use the config port info command to display port configuration information.
Configuring a Hybrid Ethernet Port
A hybrid Ethernet port allows the combination of network and access modes of operation on a per-VLAN basis and must be configured for either dot1q or qinq encapsulation.
A hybrid mode port must use dot1q encapsulation to be configured as a network IP interface. Attempting to specify a qinq-encapsulated hybrid port as the port of a network interface is blocked.
Once a port has been configured for hybrid mode, multiple services may be configured on the port.
Use the following basic CLI syntax to configure hybrid mode port parameters.
The following CLI syntax shows an example of configuring a hybrid port for access mode.
Use the config port info command to display port configuration information.
Configuring 802.1x Authentication Port Parameters
The 7705 SAR supports network access control of client devices (for example, PCs and STBs) on an Ethernet network using the IEEE 802.1x standard. 802.1x is a standard for authenticating customer devices before they can access the network. Authentication is performed using Extensible Authentication Protocol (EAP) over LAN (EAPOL).
802.1x provides protection against unauthorized access by forcing the device connected to the 7705 SAR to go through an authentication phase before it is able to send any non-EAP packets. Only EAPOL frames can be exchanged between the aggregation device (authenticator; for example, the 7705 SAR) and the customer device (supplicant) until authentication is successfully completed.
Use the following CLI syntax to configure an 802.1x Ethernet port:
The following CLI syntax shows an example of configuring an 802.1x Ethernet port:
Use the config port info command to display port configuration information.
Configuring DSL Module Port Parameters
Use the following CLI syntax to configure DSL module port parameters.
Configuring a DSL Module Network Port
A network port is network-facing and participates in the service provider transport or infrastructure network processes.
Use the following CLI syntax to configure DSL module network port parameters.
The following CLI syntax shows an example of configuring a DSL module port for network mode.
Use the config port info command to display port configuration information.
Configuring a DSL Module Access Port
Services are configured on access ports used for customer-facing traffic. If a Service Access Point (SAP) is to be configured on a port, it must be configured for access mode.
When a port is configured for access mode, the appropriate encapsulation type can be specified to distinguish the services on the port. Once a port has been configured for access mode, multiple services may be configured on the port.
QinQ encapsulation type is supported on the DSL block on the 7705 SAR-Wx. However, it is not supported on the DSL Module on the 7705 SAR-M.
Use the following CLI syntax to configure a DSL module port for access mode.
The following CLI syntax shows an example of configuring a DSL port for access mode.
Use the config port info command to display port configuration information.
Configuring SONET/SDH Port Parameters
Use the following CLI syntax to configure SONET/SDH port parameters on a 4-port OC3/STM1 Clear Channel Adapter card.
Use the following CLI syntax to configure SONET/SDH port parameters on a 2-port OC3/STM1 Channelized Adapter card.
Configuring a SONET/SDH Access Port
Use the following CLI syntax to configure a SONET/SDH access port on a 4-port OC3/STM1 Clear Channel Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH access port on a 4-port OC3/STM1 Clear Channel Adapter card.
Use the config info command to display SONET/SDH port configuration information.
Use the following CLI syntax to configure a SONET/SDH access port on a 2-port OC3/STM1 Channelized Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH access port on a 2-port OC3/STM1 Channelized Adapter card.
Use the following CLI syntax to configure a SONET/SDH access port on a 4-port OC3/STM1 Channelized Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH access port on a 4-port OC3/STM1 Channelized Adapter card.
Use the config info command to display SONET/SDH port information.
Configuring a SONET/SDH Network Port
Use the following CLI syntax to configure a SONET/SDH network port on a 4-port OC3/STM1 Clear Channel Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH network port on a 4-port OC3/STM1 Clear Channel Adapter card.
Use the config info command to display SONET/SDH port information for the configured port.
Use the following CLI syntax to configure a SONET/SDH network port on a 2-port OC3/STM1 Channelized Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH network port on a 2-port OC3/STM1 Channelized Adapter card.
Use the config info command to display SONET/SDH port information for the configured port.
Configuring Voice Ports
Use the following CLI syntax to configure an analog voice port on a 6-port E&M Adapter card.
The following CLI syntax shows an example of configuring an analog voice port on a 6-port E&M Adapter card. The default values are used for the commands that are not shown in the example.
Use the following CLI syntax to configure an analog voice port on an 8-port Voice & Teleprotection card.
The following CLI syntax shows an example of configuring an analog voice port on an 8-port Voice & Teleprotection card. The default values are used for the commands that are not shown in the example.
Use the following CLI syntax to configure an analog voice port on an 8-port FXO Adapter card.
The following CLI syntax shows an example of configuring an analog voice port on an 8-port FXO Adapter card. The default values are used for the commands that are not shown in the example.
Use the following CLI syntax to configure an analog voice port on a 6-port FXS Adapter card.
The following CLI syntax shows an example of configuring an analog voice port on a 6-port FXS Adapter card.
Configuring Teleprotection Ports
Use the following CLI syntax to configure a teleprotection port on an 8-port Voice & Teleprotection card.
The following CLI syntax shows an example of configuring a teleprotection port on an 8-port Voice & Teleprotection card. The default values are used for the commands that are not shown in the example.
Configuring TDM PPP
Use the following CLI syntax to configure PPP parameters for TDM DS3/E3 ports.
Configuring Channelized Ports
Channelized ports are supported on the following cards and module:
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
- 12-port Serial Data Interface card
- 6-port E&M Adapter card
- 2-port OC3/STM1 Channelized Adapter card
- 4-port OC3/STM1 Channelized Adapter card
- 4-port DS3/E3 Adapter card
- 8-port Voice & Teleprotection card
- 4-port T1/E1 and RS-232 Combination module
- 8-port FXO Adapter card
- 6-port FXS Adapter card
| Note:
Ethernet ports cannot be channelized. |
When configuring channelized ports, the port ID is specified in different ways depending on the TDM type and level of channelization, as follows:
- N × DS0 in DS1 port.channel-group, where channel-group is 1 to 24
- N × DS0 in E1 port.channel-group, where channel-group is 1 to 32
- N × DS1 in DS3 port.DS1 port.channel-group, where channel-group is 1 to 24
- N × E1 in E3 port.E1 port.channel-group, where channel-group is 1 to 32
- 1 × DS0 in V.35, RS-232, or X.21 port.channel-group, where channel-group is 1
- 1 × DS0 in E&M, FXO, or FXS port.channel-group, where channel-group is 1
- 1 × DS0 in codirectional port.channel-group, where channel-group is 1
- N × DS0 in TPIF port.channel-group, where channel-group is 1
Verifying the Adapter Card Type
To ensure that you have a channel-capable adapter card, verify the adapter card you are configuring by using the show mda command.
In the following example, mda 1, mda 3, mda 4, and mda 6 show channelized adapter cards on the 7705 SAR-8.
Use the show mda detail command to show detailed information for the channelized adapter cards shown in the previous sample.
On the 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, 2-port OC3/STM1 Channelized Adapter card, 4-port DS3/E3 Adapter card, and T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module, DS0 channel groups and their parameters are configured in the DS1 or E1 context. For a DS1 channel group, up to 24 timeslots can be assigned (numbered 1 to 24). For an E1 channel group, up to 31 timeslots can be assigned (numbered 2 to 32). For ATM, all timeslots are auto-configured when a channel group gets created. The 4-port OC3/STM1 Channelized Adapter card supports channelization at the DS1/E1 level only.
On the 6-port E&M Adapter card, a single DS0 channel group and its parameters are configured in the E&M context. On the 12-port Serial Data Interface card and RS-232 ports of the 4-port T1/E1 and RS-232 Combination module, DS0 channel groups and their parameters are configured in the V.35, RS-232, or X.21 context. For RS-232, a single timeslot is auto-configured when a channel group is created. For V.35 and X.21, the number of timeslots auto-configured when a channel group is created depends on the interface speed. For the 8-port Voice & Teleprotection card, a single DS0 channel group and its parameters are configured in the codirectional, FXO or FXS context and up to 12 timeslots can be assigned for the TPIF context.
| Note:
|
The following is an example of an E1 channel group configuration.
The following is an example of an RS-232 channel group configuration.
The following is an example of an E&M channel group configuration.
The following is an example of an FXO channel group configuration:
The following is an example of an FXS channel group configuration:
Services can now be applied to the configured channelized ports.
Configuring Fractional T1/E1 Ports for PPP Encapsulation
A T1 or E1 port can be configured to provide a subrate PPP service. That is, by using a channel group, the PPP service can be assigned to a subset of the timeslots that are available on the T1 or E1 port. Only one channel group can be configured per port for subrate PPP.
To configure PPP for use over a subrate (or fractional) T1/E1 port on a 16-port T1/E1 ASAP Adapter card,32-port T1/E1 ASAP Adapter card, or 4-port T1/E1 and RS-232 Combination module, you must first configure a channel group, then set the port to network mode and encapsulation type ppp-auto. The node then automatically allocates all 24 T1 or 31 E1 channels (timeslots) to the channel group.
You must then change the value of the timeslot configuration to specify the number of timeslots you want to use. Any timeslots not selected cannot be used.
Use the following CLI syntax to configure a T1/E1 port for fractional T1/E1.
First, configure the port:
Use the config port info command to display port configuration information:
Next, change the value of the timeslots configuration (currently, all timeslots are allocated to this channel group):
Use the config port info command to display the new port configuration information:
Configuring T1 Line Buildout
Telcordia GR-499 requirements indicate that a T1/E1 transmitter will typically support an LBO adjustment in order to maintain an equivalent interconnect distance of approximately 655 feet over the full range of cable lengths up to 655 ft (200 m).
Use the following CLI syntax to configure LBO functions for T1 (DS1) ports. The LBO function is implemented using the length command. To change the length of the port, you must first shut down the port and then configure the length. This command applies to T1 ports only.
The following CLI syntax shows an example of configuring a length of 266 feet on a T1 port.
Use the config port info command to display port configuration information.
Configuring TDM E1 SSM
Use the following CLI syntax to configure Synchronization Status Messaging (SSM) for E1 TDM ports:
The following CLI syntax shows an example of configuring SSM on an E1 port.
Use the config port info command to display port configuration information.
Configuring ATM Interface Parameters
ATM interface parameters can be configured for SONET/SDH ports in access mode, TDM ports or channels supporting ATM encapsulation, and IMA multilink bundles. The parameters allow users to configure characteristics of an ATM interface. The 7705 SAR-8 and 7705 SAR-18 support configuration of the following ATM interface parameters:
- cell-format — allows the user to select the ATM cell format to be used on a given interface: UNI or NNI (NNI is not supported on SONET/SDH interfaces)
- min-vp-vpi — allows the user to set the minimum allowable virtual path identifier (VPI) value that can be used on the ATM interface for a VPC
- mapping — allows the user to configure ATM cell mapping for DS3 clear channels. Since E3 ports only support G.751 framing with direct cell mapping, ATM mapping is hard-coded for direct mapping for an E3 port (you will get an error message if you try to change the value).
ATM Interface Commands
Use the following CLI syntax to configure basic ATM interface parameters for SONET/SDH ports.
Use the following CLI syntax to configure basic ATM interface parameters for TDM DS3/E3 ports. (In the E3 ATM interface example, the mapping command is shown for reference only; it does not appear in the CLI.)
Use the following CLI syntax to configure basic ATM interface parameters for TDM DS1/E1 channels.
Use the following CLI syntax to configure basic ATM interface parameters for IMA multilink bundles.
Configuring Multilink PPP Bundles
Multilink PPP bundles can be created on a 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, 2-port OC3/STM1 Channelized Adapter card, 4-port OC3/STM1 Channelized Adapter card, and 4-port T1/E1 and RS-232 Combination module.
Multilink bundling is based on a link control protocol (LCP) option negotiation that permits a system to indicate to its peer that it is capable of combining multiple physical links into a bundle. Each bundle represents a single connection between two routers. The bundles aggregate channelized ports to define the bandwidth between the routers over the DS1 links.
Multilink bundling operations are modeled after a virtual PPP link-layer entity where packets received over different physical link-layer entities are identified as belonging to a separate PPP network protocol (the Multilink Protocol, or MP) and recombined and sequenced according to information present in a multilink fragmentation header. All packets received over links identified as belonging to the multilink arrangement are presented to the same network-layer protocol processing machine, whether they have multilink headers or not.
When you configure multilink bundles, consider the following guidelines.
- A multilink bundle configuration should include at least 2 ports.
- Multilink bundles can only be aggregated on a single adapter card.
- All member links of an MLPPP group must reside on the same T1/E1 ASAP card or the same port on a 2-port OC3/STM1 Channelized Adapter card, 4-port OC3/STM1 Channelized Adapter card, or 4-port T1/E1 and RS-232 Combination module, and be of the same type (either E1 or DS1).
- When you configure a channel group on the network side with ppp-auto encapsulation, the system automatically allocates all timeslots to the channel group.
- When you configure a channel group on the access side with IPCP encapsulation, the system does not automatically allocate all timeslots to the channel group. In order to use the port or channel group as a member in an MLPPP or MC-MLPPP, you must manually allocate all the timeslots to the channel group before adding it to the bundle.
Configuring MC-MLPPP
When you configure MC-MLPPP on a port, consider the following guidelines:
- MC-MLPPP can be enabled on every MLPPP bundle
- MC-MLPPP must be enabled before links are added
- links inside an MC-MLPPP bundle must be configured for access mode and IPCP encapsulation type. All links must be from the same adapter card and all timeslots must be allocated to a single channel group.
- a single fragment size for all classes is supported
- prefix elision is not supported, as per RFC 2686. The prefix elision (compressing common header bytes) option advises the router that, in each of the given classes, the implementation expects to receive only packets with a certain prefix; this prefix is not to be sent as part of the information in the fragment(s) of this class.
Use the following CLI syntax to configure MC-MLPPP.
The following CLI syntax shows an example of configuring MC-MLPPP.
Use the config info command to display port configuration information.
Configuring LAG Parameters
Observe the following general rules and conditions when configuring LAGs.
- A maximum of 16 LAGs, 2 ports (links) each, can be configured on a 7705 SAR.
- Both ports of a given LAG must share the same characteristics (speed, duplex, hold-timer, and so on). The port characteristics are inherited from the primary port.
- Both ports of a given LAG must be distributed over two different adapter cards to minimize the impact of an adapter card failure on the LAG.
- LAG is supported only on Ethernet access ports.
- Only active/standby operation is supported.
- By default, LACP is disabled and must be set before a LAG can be used. LACP operates in two modes: passive and active. If the mode on the CE end is passive, the LACP mode on the 7705 SAR end must be active.
- Autonegotiation must be disabled or set to limited mode for ports in a LAG in order to guarantee a specific port speed.
- Ports in a LAG must be configured as full duplex.
- Ports in a LAG must be configured for the same encapsulation value.
- Each port in a LAG must be a member of a subgroup. A subgroup can only have one port member.
- The port with the highest priority is the primary port. If both ports have the same priority, the port with the lowest port ID becomes the primary port.
- A port on standby can be replaced while the active port in the LAG is operational.
- The show commands display physical port statistics on a port-by-port basis. Statistics for the entire LAG can also be displayed.
- When one port is on a first- or second-generation Ethernet adapter card and the other port is on a third-generation Ethernet adapter card, mix-and-match traffic management occurs. The LAG SAP uses a generic QoS configuration where scheduler-mode, agg-rate, and cir-rate are configured for the SAP, but only those applicable parameters needed by the active adapter card are used to set the QoS values of the active port. See LAG Support on the 6-port Ethernet 10Gbps Adapter Card for details. See Table 2 for a list of adapter card generations.
- The primary port configuration settings are applied to both the primary and secondary LAG ports. Thus, in order to support unshaped SAPs when the primary port is a Gen-3-based port and the secondary port is a Gen-2-based port, configuring the unshaped-sap-cir on the Gen-3-based port is allowed, even though it does not apply to the Gen-3-based port. This is because unshaped-sap-cir is needed by the (secondary) Gen-2-based port when it becomes the active port. The full command is config>port>ethernet>access>egress> unshaped-sap-cir cir-rate.
- When a LAG contains a port on a first-generation Ethernet adapter card, the scheduler mode can only be 4-priority.
| Note:
LACP cannot be configured for static LAG. For more information on static LAG, see Static LAG (Active/Standby LAG Operation without LACP). |
The following CLI syntax shows an example of configuring LAG parameters:
The following example displays a LAG configuration:
Configuring Multilink ATM Inverse Multiplexing (IMA) Groups
IMA groups are supported on channelized 16-port T1/E1 ASAP Adapter cards, 32-port T1/E1 ASAP Adapter cards, and 2-port OC3/STM1 Channelized Adapter cards. The groups aggregate E1 or DS1 ATM channels into a single logical ATM interface.
Configuring IMA Groups
Use the following CLI syntax to configure IMA group parameters.
Configuration Notes for IMA Groups
An IMA group has common interface characteristics (for example, configuration that applies to a logical ATM interface either configured via the IMA group context or taken from the primary link). The following list details the common IMA group interface characteristics:
- ATM interface characteristics (under the ATM menu context)
- interface mode type (only access is supported)
Member links inherit these common characteristics from the IMA group that they are part of and as long as they are part of the IMA group.
The primary link is the member that has the lowest ifindex. When a member is added or deleted, the primary member may be changed based on ifindicies of all member links.
Once a path becomes part of an IMA group logical link, the path ceases to exist as a physical ATM path interface. This means that:
- ATM interface characteristics enforced over the link are those of a group. When a link is removed from an IMA group, the link's ATM characteristics are reset to ATM interface defaults.
- no services can be configured on the member link itself
After the primary member has been added, each additional member added to the group will only be accepted if it matches the configuration of the IMA group.
ATM interface characteristics are not part of this verification as they are overwritten or reset to defaults when a link is added to or removed from an IMA group.
When a member is assigned to an IMA group, the member is automatically assigned an IMA link ID. IMA link IDs range from 0 to 16 and stay constant as long as the router does not reboot.
When configuring IMA groups, consider the following guidelines.
- All IMA links in an IMA group must belong to the same T1/E1 Adapter card or the same physical OC3 port.
- IMA bundles can only be aggregated on a single adapter card.
- On the 2-port OC3/STM1 Channelized Adapter card, the red differential delay is configurable from 2 to 50 ms and is accurate within 1 ms. On the 16-port T1/E1 ASAP Adapter card and 32-port T1/E1 ASAP Adapter card, the red differential delay is configurable from 2 to 75 ms and is accurate within 1 ms.
- If no member links are configured on an IMA group, the speed of an E1 channel will be used to compute the maximum IMA group bandwidth that may be allocated to shaped services.
- When adding member links to an IMA group, the clock-source of the E1 or DS1 link must be set to node-timed.
The following example illustrates creation of an IMA group with three group members residing on a channelized 16-port T1/E1 ASAP Adapter card in slot 1/3/1:
IMA Test Procedure
Use the following CLI syntax to perform an IMA test pattern procedure on a member link of an IMA group.
An operator can deploy IMA test procedures to verify operations of an IMA group and its member links. The following is a list of key points about the test pattern procedure.
- The test procedure is performed as defined by the IMA specification version 1.1. That is, a test pattern is sent over the specified link and is expected to be looped back over all the links in the group. ICP cells are used to perform the test.
- The test procedure is not traffic-affecting; that is, data traffic will not be affected by the ongoing test.
- There can only be a single test executed per IMA group at any given time.
- The IMA member link must exist in the specified group for the command to be accepted.
- The test pattern procedure must be shut down before a new test-link value or test pattern is accepted.
- The current IMA group test pattern configuration and result of a given IMA test can be seen by executing a show command for the IMA group. A test-link result can have three values:
- Disabled: the test-link is currently not running
- Operating: the test pattern procedure is no shutdown and there are currently no failed links for this running test-pattern procedure
- Link-Failed: one or more links have failed the test-pattern procedure. Execute a show port <slot/mda/port> ima-link command to see the failed link and received pattern value.
- Deleting a member link that is the same as the specified test-link, to stay in compliance with key point 4, will result in the test-link value being reset to default.IMA test procedure configurations are not saved when the admin save command is executed.
Configuring SDI Ports for IPCP Encapsulation
V.35 and X.21 ports on the 12-port Serial Data Interface card can be configured for IPCP encapsulation to support PPP SAPs for Ipipes. See the 7705 SAR OS Services Guide for more information about IP interworking VLL (Ipipe) services.
Use the following CLI syntax to configure IPCP parameters for V.35 serial ports. X.21 ports that are configured for super-rate speeds are also supported. The encap-type must be set to ipcp.
Use the config port info detail command to display port configuration information:
Configuring TDM and SDI Ports for Frame Relay Encapsulation
Frame relay service can be configured on the following ports:
- 16-port T1/E1 ASAP Adapter card, version 2, on DS1 or E1 ports
- 32-port T1/E1 ASAP Adapter card on DS1 or E1 ports
- 4-port DS3/E3 Adapter card on clear channel DS3 or E3 ports, or on DS3 ports channelized to DS1 or E1 down to DS0
- 12-port Serial Data Interface card on V.35 and X.21 ports
Frame relay ports can be configured in access mode to support:
- Fpipes on:
- 16-port T1/E1 ASAP Adapter card, version 2, on DS1 or E1 ports
- 32-port T1/E1 ASAP Adapter card on DS1 or E1 ports
- 4-port DS3/E3 Adapter card on clear channel DS3 or E3 ports, or on DS3 ports channelized to DS1 or E1 down to DS0
- 12-port Serial Data Interface card on V.35 or X.21 ports
- Ipipes on:
- 16-port T1/E1 ASAP Adapter card, version 2, on DS1 or E1 ports
- 32-port T1/E1 ASAP Adapter card on DS1 or E1 ports
- 4-port DS3/E3 Adapter card on clear channel DS3 or E3 ports only
- 12-port Serial Data Interface card on V.35 or X.21 ports
The encap-type must be set to frame-relay. The settings for the frame relay port can be modified by using the parameters under the frame-relay command hierarchy as shown in the following examples. The settings apply to frame relay ports used for Fpipe SAPs and interworking Ipipe SAPs. See the 7705 SAR OS Services Guide for more information about frame relay VLL (Fpipe) services and IP interworking VLL (Ipipe) services.
Use the following CLI syntax to configure a frame relay access port on a 16-port T1/E1 ASAP Adapter card or a 32-port T1/E1 ASAP Adapter card.
Use the config port info detail command to display port configuration information:
Use the following CLI syntax to configure frame relay parameters for TDM DS3/E3 ports.
Use the following CLI syntax to configure frame relay parameters for V.35 serial ports. X.21 ports at super-rate speeds are also supported.
Configuring TDM and SDI Ports for HDLC Encapsulation
HDLC service can be configured on the following ports:
- 16-port T1/E1 ASAP Adapter card, version 2, on clear channel or fractional DS1 or E1 ports
- 32-port T1/E1 ASAP Adapter card on clear channel or fractional DS1 or E1 ports
- 12-port Serial Data Interface card on V.35 serial ports and X.21 serial ports (at super-rate speeds only)
HDLC ports can be configured in access mode to support Hpipes on the above cards. The encap-type must be set to hdlc.
| Note:
HDLC encapsulation can be used on a port to transmit cHDLC frames into an Hpipe. |
Use the following CLI syntax to configure a T1/E1 port for HDLC.
HDLC ports cannot be configured if the mode is set to network.
Use the config port info command to display the new port configuration information:
Use the following CLI syntax to configure an X.21 serial port (super-rate speed) on a 12-port Serial Data Interface card for HDLC. The syntax for a V.35 serial port is similar.
Use the config port info command to display the new port configuration information:
Configuring TDM and SDI Ports for Cisco HDLC Encapsulation
Cisco HDLC (cHDLC) service can be configured on the following ports:
- 16-port T1/E1 ASAP Adapter card, version 2, on clear channel or fractional DS1 or E1 ports
- 32-port T1/E1 ASAP Adapter card on clear channel or fractional DS1 or E1 ports
- 12-port Serial Data Interface card on V.35 serial ports and X.21 serial ports (at super-rate speeds)
Cisco HDLC ports can be configured in access mode to support Ipipes on the above cards. The encap-type must be set to cisco-hdlc.
| Note:
Cisco HDLC encapsulation cannot be used to transmit HDLC frames into an Ipipe. |
Use the following CLI syntax to configure a T1/E1 port for cHDLC.
Cisco HDLC ports cannot be configured if the mode is set to network.
Use the config port info command to display the new port configuration information:
Use the following CLI syntax to configure an X.21 serial port (at super-rate speeds) on a 12-port Serial Data Interface card for cHDLC. The syntax for a V.35 serial port is similar.
Use the config port info command to display the new port configuration information:
Configuring GPS RF Port Parameters
Use the following CLI syntax to configure GPS RF port parameters.
Configuring SCADA Bridge Parameters
Use the following CLI commands to configure SCADA bridge parameters on an Integrated Services card.
The following CLI syntax shows an example of configuring SCADA bridge parameters on an Integrated Services card.
Use the config info command to display the new SCADA bridge configuration information:
Service Management Tasks
This section discusses basic procedures of the following service management tasks:
Modifying or Deleting an Adapter Card
To change an adapter card type already provisioned for a specific slot/card, you must first shut down the slot/MDA/port configuration and then delete the adapter card from the configuration.
Use the following CLI syntax to modify an adapter card.
The following CLI syntax shows an example of modifying an adapter card.
Deleting a Card
To delete a CSM or adapter card provisioned for a specific slot, you must shut down existing port configurations and shut down and remove all adapter card configurations.
Use the following CLI syntax to delete a card provisioned for a specific slot.
The following CLI syntax shows an example of deleting a card.
Deleting Port Parameters
Use the following CLI syntax to delete a port provisioned for a specific adapter card.
The following CLI syntax shows an example of deleting a port.