3.8. Configuring Physical Components with CLI
This section provides information to configure cards, adapter cards, and ports.
Topics in this section include:
3.9. 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.
3.9.1. 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.
3.9.2. 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.
- SONET/SDH
- SONET/SDH can be used only when configuring an OC-3 or OC-12 SONET path on an appropriate adapter card.
- Configure a network port or channel to participate in the service provider transport or infrastructure network.
To configure a SONET path, see Configuring SONET/SDH Port Parameters. - Channelized
- Channelized ports can be configured on the following adapter cards and modules:
- 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 / 1-port OC12/STM4 Adapter card
- 8-port Voice & Teleprotection card (access mode only)
- 8-port C37.94 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)
- 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.
3.9.3. Maximizing Bandwidth Use
After ports are preprovisioned, multilink bundles (MLPPP) or IMA groups can be configured to increase the bandwidth available between two nodes.
The following cards, modules, and platforms support multilink bundles:
- 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 / 1-port OC12/STM4 Adapter card
- T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on 7705 SAR-H)
- T1/E1 ports on the 7705 SAR-A
- T1/E1 ports on the 7705 SAR-M
- T1/E1 ports on the 7705 SAR-X
The following cards, modules, and platforms support IMA groups:
- 2-port OC3/STM1 Channelized Adapter card
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
- T1/E1 ports on the 7705 SAR-M
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 Channelized Ports.
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. |
3.9.4. Using Partial Bandwidth
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.
The following cards and platforms support fractional T1/E1 on a PPP channel group (encapsulation type ppp-auto), or all timeslots on T1/E1 ports, in network mode:
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
- T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on 7705 SAR-H)
- T1/E1 ports on the 7705 SAR-A
- T1/E1 ports on the 7705 SAR-M
- T1/E1 ports on the 7705 SAR-X
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.
3.10. Basic Configuration
The basic 7705 SAR 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, 16-port T1/E1 ASAP Adapter card, 32-port T1/E1 ASAP Adapter card, 10-port 1GigE/1-port 10GigE X-Adapter card, 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card, and Integrated Services card)
- identify specific port to configure
The following example displays some card and port configurations on the 7705 SAR-8 Shelf V2.
| 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). |
3.11. Common Configuration Tasks
The following basic system tasks are performed, as required:
3.11.1. Configuring Cards and Adapter Cards
This section contains the following topics:
3.11.1.1. 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
- 32-port T1/E1 ASAP Adapter card
The mda-mode command is 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 (x10-1gb-sfp or x1-10gb-sf+).
The mda-mode command is used on the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card to configure the card for either 4-port OC3/STM1 mode or 1-port OC12/STM4 mode (p4-oc3 or p1-oc12).
The mda-mode command is used on the Integrated Services card to configure the card for a SCADA application: (mddb, pcm, or vcb).
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 Shelf V2.
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.
3.11.1.2. 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 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.
3.11.1.3. 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 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.
3.11.1.4. 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.
3.11.1.5. 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 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.
3.11.1.6. 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
- 32-port T1/E1 ASAP Adapter card
- 7705 SAR-M (variants with T1/E1 ports)
- 7705 SAR-X
- 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 cards support differential clocking mode only:
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card (DS1/E1 channels)
- 4-port DS3/E3 Adapter card (clear channel DS3/E3 ports and DS1/E1 channels on channelized DS3 ports (E3 ports cannot be channelized)); differential clocking mode on DS1/E1 channels is supported only on the first three ports of the card
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.
3.11.1.7. 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 Shelf V2 or 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 Shelf V2 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 Shelf V2 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 Shelf V2 or 7705 SAR-18 chassis.
3.11.1.8. 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.
3.11.1.9. 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 Shelf V2), alarm connector (for the 7705 SAR-M, 7705 SAR-Wx, 7705 SAR-H, 7705 SAR-Hc, and 7705 SAR-X), 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.
3.11.1.10. Displaying Adapter Card Information
After performing the adapter card configuration, you can use the config>card 1 and the info commands to display the information on the 7705 SAR-8 Shelf V2.
Use the config>card 1 and the info detail commands to display the adapter card detailed configuration information on the 7705 SAR-8 Shelf V2.
3.11.2. Configuring Ports
This section provides the CLI syntax and examples to configure the following:
3.11.2.1. 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 or working port must be shut down in the config>port port-id context 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 or bidirectional mode on:
- 2-port OC3/STM1 Channelized Adapter cards for TDM CES (Cpipes) and TDM CESoETH with MEF 8 with DS3/DS1/E1/DS0 channels
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter cards for MLPPP access ports or TDM CES (Cpipes) and TDM CESoETH (MEF 8) access ports with DS1/E1 channels, or on a network port configured for POS
- 4-port OC3/STM1 Clear Channel Adapter cards network side (configured for POS operation).
SC-APS with TDM access is supported on DS3, DS1, E1, and DS0 (64 kb/s) channels.
MC-APS is supported in bidirectional mode on:
- 2-port OC3/STM1 Channelized Adapter cards for TDM CES (Cpipes) and TDM CESoETH with MEF 8 with DS3/DS1/E1/DS0 channels
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter cards for MLPPP access ports or CES (Cpipes) and TDM CESoETH (MEF 8) access ports with DS1/E1 channels.
MC-APS with TDM access is supported on DS3, DS1, E1, and DS0 (64 kb/s) channels. TDM SAP-to-SAP with MC-APS is not supported.
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.
For SC-APS and MC-APS with MEF 8 services where the remote device performs source MAC validation, the MAC address of the channel group in each of the redundant interfaces may be configured to the same MAC address using the mac CLI command.
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.
The following CLI syntax shows examples of typical configurations of SC-APS and MC-APS on MC-MLPPP access ports on a 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card.
SC-APS node:
MC-APS working node:
MC-APS protection node:
Pseudowire redundancy node:
3.11.2.2. Configuring LCR Parameters
LCR has the following configuration rules.
- The working and protection adapter cards in an LCR group must be configured with the same setting for the mda-mode command. In addition, the clock-mode for each card must be set to dcr-acr before the adapter card can be added to an LCR group.
- In an SC-LCR group, both the working and protection adapter cards are configured with the same LCR group ID on the same node. The working and protection adapter cards must be the same type.
- In an MC-LCR group, the working and protection adapter cards are configured on separate nodes. Users must ensure that the working and protection adapter cards are the same type.
- A working adapter card must be created first in an LCR group. Then a protection adapter card can be added to or removed from an LCR group at any time.
- The protection adapter card must be removed from the configuration before the working adapter card is removed.
- A protection adapter card or working adapter card must be shut down in the config>card>mda mda-slot context before being removed from an LCR group.
- A channel cannot be configured on a T1/E1 port before its associated adapter card is added to an LCR group.
- A working adapter card cannot be removed from an LCR group until the associated T1/E1 channel is removed.
- When adapter cards are added to an LCR group, all channel-level configurations are available only on the associated LCR ports and configuration on the physical member ports is blocked.
LCR is supported on the following cards on the 7705 SAR-8 Shelf V2 and the 7705 SAR-18:
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
To create an SC-LCR group, it is mandatory to configure a group ID and the working and protection adapter cards. Use the following CLI syntax to configure SC-LCR.
The following CLI syntax shows an example of configuring SC-LCR.
Use the info command to display SC-LCR configuration information.
To create an MC-LCR group, it is mandatory to configure the LCR ID, the working adapter card and neighbor address, and protection adapter card and neighbor address. Use the following CLI syntax to configure LCR parameters for an MC-LCR group.
The following CLI syntax shows an example of configuring a working adapter card on a node in an MC-LCR group.
To complete the MC-LCR configuration, log on to the protection node, configure an LCR group with the same LCR ID as the working adapter card, and configure the protection adapter card and the neighbor address. An IP link establishes a multi-chassis protocol (MCP) link between the two nodes.
The following CLI syntax shows an example of configuring a protection adapter card on a node in an MC-LCR group.
Use the info command to display MC-LCR configuration information.
3.11.2.3. Configuring a Microwave Link
A microwave link can be configured on a 7705 SAR-8 Shelf V2 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 Shelf V2; the MPR-e radios are in standalone mode.
3.11.2.4. Configuring Ethernet Port Parameters
Use the following CLI syntax to configure Ethernet network and access port parameters. For more information on the dot1x command, see Configuring 802.1x Authentication Port Parameters. For more information on the mac-auth and mac-auth-wait commands, see Configuring MAC Authentication Port Parameters.
When an Ethernet port is configured in WAN mode (xgig wan command), users can change certain SONET/SDH parameters to reflect the SONET/SDH requirements for the port. For more information, see Configuring SONET/SDH Parameters on an Ethernet XGIG WAN Port.
3.11.2.4.1. 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.
3.11.2.4.2. 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.
3.11.2.4.3. 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.
3.11.2.4.4. 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.
3.11.2.4.5. Configuring MAC Authentication Port Parameters
The 7705 SAR supports a fallback MAC authentication mechanism for client devices (for example, PCs and STBs) on an Ethernet network that do not support 802.1x EAP.
MAC authentication provides protection against unauthorized access by forcing the device connected to the 7705 SAR to have its MAC address authenticated by a RADIUS server before it is able to transmit packets through the 7705 SAR.
Use the following CLI syntax to configure MAC authentication for an Ethernet port:
The following CLI syntax shows an example of configuring MAC authentication for an Ethernet port:
Use the info detail command to display port configuration information.
3.11.2.5. Configuring SONET/SDH Port Parameters
When configuring a SONET/SDH port, users configure both SONET/SDH and TDM aspects of a channel. The CLI uses the sonet-sdh-index variable to identify a channel in order to match SONET/SDH parameters with TDM parameters for the channel. Configuring TDM on a SONET/SDH port is similar to configuring it on a TDM port. See Configuring Channelized Ports for additional information.
This section shows the CLI syntax for the following adapter cards and provides examples for configuring SONET/SDH access and network ports:
- 4-port OC3/STM1 Clear Channel Adapter card
- 2-port OC3/STM1 Channelized Adapter card
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
4-port OC3/STM1 Clear Channel Adapter Card
Use the following CLI syntax to configure SONET/SDH port parameters on a 4-port OC3/STM1 Clear Channel Adapter card. On the 4-port OC3/STM1 Clear Channel Adapter card, the sonet-sdh-index variable in the path command is optional and defaults to sts3, which cannot be changed.
2-port OC3/STM1 Channelized Adapter Card and 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card
Use the following CLI syntax to configure SONET/SDH port parameters on a 2-port OC3/STM1 Channelized Adapter card or a 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card. The sonet-sdh-index values are different for each of these adapter cards (see SONET/SDH for more information). The syntax includes the TDM port parameters.
3.11.2.5.1. Configuring a SONET/SDH Access Port
This section provides examples of configuring a SONET/SDH access port on the following adapter cards:
- 4-port OC3/STM1 Clear Channel Adapter Card
- 2-port OC3/STM1 Channelized Adapter Card
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card
4-port OC3/STM1 Clear Channel Adapter Card
Use the following CLI syntax to configure a SONET/SDH access port on a 4-port OC3/STM1 Clear Channel Adapter card. The default setting for the mode command is access.
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 port info command to display SONET/SDH port configuration information.
2-port OC3/STM1 Channelized Adapter Card
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.
4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card
Use the following CLI syntax to configure a SONET/SDH access port on a 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card.
The following CLI syntax shows an example of configuring a SONET/SDH access port on a 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card (4-port mode).
The following display shows the configuration when the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card is in 4-port mode. Use the config port info command to display SONET/SDH port information.
The following display shows the configuration when the 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card is in 1-port mode. Use the config port info command to display SONET/SDH port information.
3.11.2.5.2. Configuring a SONET/SDH Network Port
This section provides examples of configuring a SONET/SDH network port on the following adapter cards:
- 4-port OC3/STM1 Clear Channel Adapter card
- 2-port OC3/STM1 Channelized Adapter card
3.11.2.5.2.1. 4-port OC3/STM1 Clear Channel Adapter Card
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 port info command to display SONET/SDH port information for the configured port.
3.11.2.5.2.2. 2-port OC3/STM1 Channelized Adapter Card
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 DS1 network port on a 2-port OC3/STM1 Channelized Adapter card. Configuring a SONET/SDH DS3 port is similar but without a channel group.
Use the config port info command to display SONET/SDH port information for the configured port.
3.11.2.5.3. Configuring the SONET/SDH Port group and path Commands
The group and path commands in the config>port>sonet-sdh context both use the sonet-sdh-index variable. However, the sonet-sdh-index format for each command is different. The full commands are as follows:
- group sonet-sdh-index payload {tu3 | vt2 | vt15}
- path [sonet-sdh-index]
The group command is only available on SONET/SDH adapter cards that support STS-3 channelization (that is, path sts3 or path sts3-1 commands). The payload is tug-index for the STS-3 path. The group command is available with SDH framing when an STS-3 path is configured with a payload of tug3. The payload of the group determines the next path layer.
The path [sonet-sdh-index] command is available on all SONET/SDH adapter cards. The sonet-sdh-index variable is optional for the 4-port OC3/STM1 Clear Channel Adapter card because the card defaults to sts3 and no further channelization is possible.
The 7705 SAR SONET/SDH implementation has options for clear channel OC3 and OC12.
The 2-port OC3/STM1 Channelized Adapter card supports DS3/DS1/E1 channelization (not E3), as well as n × DS0 channelization.
The 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card supports DS1/E1 channelization but not DS3/E3 and not n × DS0 channelization. In addition, DS1/E1 channels cannot be in DS3/E3 channels. To configure clear channel OC3 and clear channel OC12 on this adapter card, use the config card 1 mda slot mda-mode command to configure either 4-port OC3 mode (mda-mode p4-oc3) or 1-port OC12 mode (mda-mode p1-oc12).
Use the following CLI syntax to configure the basic channelized OC3/STM1 parameters:
The following CLI syntax shows an example of configuring the basic channelized OC3/STM1 parameters.
Use the info command to display configuration information.
3.11.2.5.4. Configuring SONET/SDH Parameters on an Ethernet XGIG WAN Port
When an Ethernet port is configured in WAN mode (xgig wan command), you can change certain SONET/SDH parameters to reflect the SONET/SDH requirements for the port.
The following CLI output shows an example of a SONET/SDH configuration for a WAN PHY Ethernet port.
3.11.2.6. SONET/SDH Channelized Port Configuration Examples
This section contains information on the following topics:
| Note: The following sections show examples of OC3 configurations. Similar examples for OC12 configurations would require an extra level in the sonet-sdh-index. See Table 22 in SONET/SDH Channelized Port ID for port syntax examples. |
3.11.2.6.1. OC3 Channelization using SONET and SDH
In SONET, the base signal is referred to as synchronous transport signal–level 1 (STS-1), which operates at 51.84 Mb/s. Higher-level signals are integer multiples of STS-1, for example, STS-3/OC3 = 3 x STS-1 = 155.52 Mb/s. The SDH equivalent of the SONET STS-1 and STS-3 frames are STM-0 and STM-1, respectively.
In addition to the STS-1 base format, SONET also defines synchronous formats at sub-STS-1 levels. The STS-1 payload can be subdivided into virtual tributaries (VTs) for SONET or virtual containers (VCs) for SDH. VTs and VCs are synchronous signals used to transport lower-speed transmissions. Two VTs are VT1.5 and VT2, where:
- VT1.5 = 1.728 Mb/s (enough to carry a T1)
- VT2 = 2.304 Mb/s (enough to carry an E1)
The SDH equivalents to VT1.5 and VT2 are VC11 and VC12, respectively.
| Note: The 7705 SAR CLI always uses the SONET command syntax and nomenclature, even when configuring an SDH port. For example, the same SONET CLI syntax and nomenclature would be used to configure both a VT1.5 and a VC11. The framing {sonet | sdh} command determines whether VTs or VCs are being configured. Use the show>port-tree command to display SONET/SDH containers. |
Figure 32 shows various possibilities for OC3 channelization using SONET and SDH framing. The VT1.5 and VT2 labels under the SDH STS1 path illustrate that SONET conventions are used for SDH configuration.
| Note: The 7705 SAR does not allow a payload of VT1.5 for VT2 paths. The payload for a VT1.5 path is ds1 and the payload for a VT2 path is vt2. |
Figure 32: OC3 Channelization using SONET and SDH
3.11.2.6.2. Configuring DS1/E1 on a Channelized OC3 Port with STS1 Path
This section provides several examples of configuring DS1/E1 channels and the use of the sonet-sdh-index parameter:
3.11.2.6.2.1. 1. DS1 (SONET Framing, STS1)
There are three STS1 paths per OC3. The following examples use sts1-1.
There are two ways to configure a DS1 channel on a SONET framed port (see Figure 32, SONET framing branch):
3.11.2.6.2.1.1. 1.1 STS1 with channelized DS3 payload
To configure a DS1 on an STS1 with a channelized DS3 payload:
- Create the STS1 path and set the payload to DS3.
- Create the channelized DS3 on the STS1 path.
- Create the DS1 on the DS3.
Use the info command to display configuration information.
Notes:
- the CLI identifier for the path command is sts1-stsNum, where:
- stsNum is the STS number, which can be 1, 2, or 3
- the CLI identifier for the TDM ds3 command is ds3Num, where:
- ds3Num is equal to stsNum
In the example above, DS3 is configured on sts1-1, hence the numbering ds3 1. If sts1-2 or sts1-3 was configured instead of sts1-1, the corresponding DS3 configuration would be ds3 2 or ds3 3, respectively. - the CLI identifier for the TDM ds1 command is ds3Num.ds1Num, where:
- ds1Num is the DS1 number. Because a DS3 can carry 28 T1s, ds1Num can be between 1 and 28.
3.11.2.6.2.1.2. 1.2 STS1 with VT1.5 payload
To configure a DS1 on an STS1 with a VT1.5 payload:
- Create the STS1 path and set the payload to VT1.5.
- Create the VT1.5 path on the STS1 path.
- Create the DS1 on the VT1.5 path.
| Note: There is one DS1 per VT1.5 path. |
Use the info command to display configuration information. The example below creates two VT1.5 paths, each with its own DS1.
Notes:
- the CLI identifier for the VT1.5 path command is vt15-stsNum.vtGroupNum.vtNum, where:
- vt15- is a keyword
- stsNum is the STS1 number, which can be 1, 2, or 3
- vtGroupNum is the VT group number. An STS1 frame contains seven VT groups, so vtGroupNum can be from 1 to 7
- vtNum is the VT1.5 number. A VT group can hold four VT1.5 paths, so vtNum can be from 1 to 4
- the CLI identifier for the TDM ds1 command is similar to the path command, namely, stsNum.vtGroupNum.ds1Num, where:
- ds1Num is equal to vtNum
3.11.2.6.2.2. 2. E1 (SONET Framing, STS1)
A DS3 can be configured to carry an E1 payload (see Figure 32, SONET framing branch).
To configure an E1 on an STS1 with a DS3 payload:
- Create the STS1 path and set the payload to DS3.
- Create the TDM DS3 with channelized E1.
- Create the TDM E1.
Use the info command to display configuration information. In the example below, which applies only to the 2-port OC3/STM1 Channelized Adapter card, DS3 1 carries two E1 channels.
Notes:
- the CLI identifier for the path command is sts1-stsNum, where:
- stsNum is between 1 and 3
- the CLI identifier for the TDM ds3 command is ds3Num, where:
- ds3Num is equal to stsNum
In the example above, DS3 is configured on sts1-1, hence the command ds3 1. If sts1-2 or sts1-3 was configured instead of sts1-1, the corresponding ds3 configuration would be ds3 2 or ds3 3, respectively. - the CLI identifier for the TDM e1 command is ds3Num.e1Num, where:
- e1Num is between 1 and 21 because a DS3 can carry 21 E1s
3.11.2.6.3. Configuring DS1/E1 on a Channelized OC3 Port with STM Path
A SONET framed port—as well as an SDH framed port—can be divided into three STS1 paths. Each SONET port can be subdivided further into lower-speed virtual tributaries (VTs). Similarly, each SDH port can be subdivided into lower-speed virtual containers (VCs). As stated in OC3 Channelization using SONET and SDH, the CLI uses SONET STS1/VT configuration conventions to configure SDH VC paths.
The following examples illustrate the use of SONET CLI terminology to configure SDH paths. See the STS1 branch under SDH framing in Figure 32.
3.11.2.6.3.1. 1. DS1 (SDH Framing, STS1)
There are two ways to configure a DS1 channel on an SDH-framed port with STS1 paths:
3.11.2.6.3.1.1. 1.1 STS1 with channelized DS3 payload
To configure a DS1 on an STS1 with a channelized DS3 payload:
- Create the STS1 path and set the payload to DS3.
- Create the TDM DS3 with channelized DS1.
- Create the TDM DS1.
Use the info command to display configuration information.
Notes:
- the CLI identifier for the path command is sts1-stsNum:
- where stsNum is between 1 and 3
- the CLI identifier for the TDM ds3 command is ds3Num, where:
- ds3Num is equal to stsNum
In the example above, DS3 is configured on sts1-1, hence the command ds3 1. If sts1-2 or sts1-3 was configured instead of sts1-1, the corresponding ds3 configuration would be ds3 2 or ds3 3, respectively. - the CLI identifier for the TDM ds1 command is ds3Num.ds1Num, where:
- ds1Num is between 1 and 28 because a DS3 can carry 28 T1s
3.11.2.6.3.1.2. 1.2 STS1 with VT1.5 payload
To configure a DS1 on an STS1 with a VT1.5 payload:
- Create the STS1 path and set the payload to VT1.5.
- Create the VT1.5 path and set the payload to DS1.
- Create the corresponding TDM DS1.
| Note: There is one DS1 per VT1.5 path. |
Use the info command to display configuration information. This example creates two VT1.5 payloads, each having a corresponding DS1 channel.
Notes:
- the CLI identifier for the VT1.5 path command is vt15-stsNum.vtGroupNum.vtNum
- vt15- is a keyword
- stsNum is the STS1 number, which can be 1, 2, or 3
- vtGroupNum is the VT group number. An STS1 frame contains seven VT groups, so vtGroupNum can be from 1 to 7
- vtNum is the VT1.5 number. A VT group can hold four VT1.5 paths, so vtNum can be from 1 to 4
- the CLI identifier for the TDM ds1 command is similar to the path command, namely, stsNum.vtGroupNum.ds1Num, where:
- ds1Num is equal to vtNum
3.11.2.6.3.2. 2. E1 (SDH Framing, STS1)
There are two ways to configure an E1 channel on an SDH-framed port with STS1 paths (see the STS1 branch under SDH framing in Figure 32):
3.11.2.6.3.2.1. 2.1 STS1 with channelized DS3 payload
To configure an E1 on an STS1 with a DS3 payload:
- Create the STS1 path with SDH framing and set the payload to DS3.
- Create a TDM DS3 with a channelized E1.
- Create the corresponding E1.
Use the info command to display configuration information. In the example below, DS3 1 carries two E1 channels.
Notes:
- the CLI identifier for the path command is sts1-stsNum, where:
- stsNum is between 1 and 3
- the CLI identifier for the TDM ds3 command is ds3Num, where:
- ds3Num is equal to stsNum
In the example above, DS3 is configured on sts1-1, hence the command ds3 1. If sts1-2 or sts1-3 was configured instead of sts1-1, the corresponding ds3 configuration would be ds3 2 or ds3 3, respectively. - the CLI identifier for the TDM e1 command is ds3Num.e1Num, where:
- e1Num is between 1 and 21 because a DS3 can carry 21 E1s
3.11.2.6.3.2.2. 2.2 STS1 with VT2 payload
To configure an E1 on an STS1 with a VT2 payload:
- Create the STS1 path and set the payload to VT2.
- Create the VT2 path and set the payload to E1.
- Create the corresponding TDM E1.
| Note: There is one E1 per VT2 path. |
Use the info command to display configuration information.
Notes:
- the CLI identifier for the VT2 path command is vt2-stsNum.vtGroupNum.vtNum, where:
- vt2- is a keyword
- stsNum is the STS1 number, which can be 1, 2, or 3
- vtGroupNum is the VT group number. An STS1 frame contains seven VT groups, so vtGroupNum can be from 1 to 7
- vtNum is the VT2 number. A VT group can hold three VT2 paths, so vtNum can be from 1 to 3
- the CLI identifier for the TDM e1 command is similar to the path command, namely, stsNum.vtGroupNum.e1Num, where:
- e1Num is equal to vtNum
3.11.2.6.4. Configuring DS1/E1 on a Channelized OC3 Port with STS3 Path
Unique to an SDH framed port is the ability to configure a single STS3 path instead of three STS1 paths. When as STS3 path is configured, the VTs are configured using tributary units (TUs). One or more TUs can be combined into a tributary unit group (TUG) (see the STS3 branch in Figure 32).
When an STS3 path is configured on an SDH port, the three TUGs in the following configuration are created by default. Each TUG can be considered the equivalent of an STS1 path.
This section provides information on the following topics:
3.11.2.6.4.1. 1. DS1 (SDH Framing, STS3)
There are two ways to configure a DS1 on an SDH framed port with an STS3 path:
3.11.2.6.4.1.1. 1.1 STS3 / TUG with VT1.5 payload
To configure a DS1 on an STS3 / TUG with a VT1.5 payload:
- Configure an STS3 path on the port.
- Configure one of the three TUGs for a VT1.5 payload.
- Create a VT1.5 path with a DS1 payload on the STS3 path / TUG.
- Create a DS1 on the VT1.5 path.
Use the info command to display configuration information.
Notes:
- the CLI identifier for the VT1.5 path is vt15-tugNum.vtGroupNum.vtNum, where:
- vt15- is a keyword
- tugNum is the TUG number, which can be 1, 2, or 3
- vtGroupNum is the VT group number. A TUG3 contains seven VT groups, so vtGroupNum can be from 1 to 7
- vtNum is the VT1.5 number. A VT group can hold four VT1.5 paths, so vtNum can be from 1 to 4
- the CLI identifier for the TDM ds1 command is similar to that of the path command, namely, tugNum.vtGroupNum.ds1Num, where:
- ds1Num is equal to vtNum
3.11.2.6.4.1.2. 1.2 STS3 / TUG with TU3 payload
To configure a DS1 on an STS3 / TUG with a TU3 payload:
- Configure an STS3 path on the port.
- Create a TU3 path with the default payload.
- Create the TDM DS3 with channelized DS1.
- Create the TDM DS1.
Use the info command to display configuration information.
Notes:
- The CLI identifier for the TDM ds1 command is similar to that of the path command, namely, tugNum.vtGroupNum.ds1Num, where:
- ds1Num is equal to vtNum
3.11.2.6.4.2. 2. E1 (SDH Framing, STS3)
To configure an E1 on an SDH framed port with an STS3 path:
- Configure an STS3 path on the port.
- Configure one of the three TUGs for a VT2 payload.
- Create a VT2 path with an E1 payload on the STS3 path / TUG.
- Create an E1 on the VT2 path.
Use the info command to display configuration information.
Notes:
- the CLI identifier for the VT2 path command is vt2-tugNum.vtGroupNum.vtNum, where:
- tugNum is the TUG number, which can be 1, 2, or 3
- vtGroupNum is the VT group number. A TUG3 contains seven VT groups, so vtGroupNum can be from 1 to 7
- vtNum is the VT2 number. A VT group can hold three VT2 paths, so vtNum can be from 1 to 3
- the CLI identifier for the TDM e1 command is similar to the path command, namely, tugNum.vtGroupNum.e1Num, where:
- e1Num is equal to vtNum
3.11.2.6.5. Configuring a SONET/SDH Port with Multiple DS1s in an MLPPP Bundle
Figure 33 illustrates the setup to configure port 1/2/2 on 7705 SAR_118 as a SONET/SDH port with three DS1s on a channelized OC3/STM1 adapter card using SDH or SONET framing, and to configure the three DS1s for use in an MLPPP bundle on the network side.
This section provides information on the following topics:
Figure 33: Configuring SONET/SDH Network Port
3.11.2.6.5.1. Configuring the Network Port
- Configure the DS1s.The following CLI syntax shows an example of configuring three DS1s on a channelized OC3/STM1 adapter card using SDH framing. The framing must match on both ends.If SONET framing is needed, use the CLI syntax after this SDH syntax.CLI Syntax:configure port 1/2/2config>port# description "to-SAR119"config>port# sonet-sdhconfig>port>sonet-sdh# framing sdhconfig>port>sonet-sdh# path sts3 no shutdownconfig>port>sonet-sdh# group tug3-1 payload vt15config>port>sonet-sdh# path vt15-1.1.1config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# path vt15-1.1.2config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# path vt15-1.1.3config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# exitconfig>port# tdmconfig>port>tdm# ds1 1.1.1config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# ds1 1.1.2config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# ds1 1.1.3config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# exitconfig>port# exit*A:SAR118#The following CLI syntax shows the configuration of the same example using SONET framing. The framing must match on both ends.CLI Syntax:configure port 1/2/2config>port# description "to-SAR119"config>port# sonet-sdhconfig>port>sonet-sdh# framing sonetconfig>port>sonet-sdh# path sts1-1config>port>sonet-sdh>path# payload vt15config>port>sonet-sdh>path# exitconfig>port>sonet-sdh# path vt15-1.1.1config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# path vt15-1.1.2config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# path vt15-1.1.3config>port>sonet-sdh>path# no shutdownconfig>port>sonet-sdh>path# exitconfig>port>sonet-sdh# exitconfig>port# tdmconfig>port>tdm# ds1 1.1.1config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# ds1 1.1.2config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# ds1 1.1.3config>port>tdm>ds1# channel-group 1config>port>tdm>ds1>channel-group# mode networkconfig>port>tdm>ds1>channel-group# encap-type ppp-autoconfig>port>tdm>ds1>channel-group# no shutdownconfig>port>tdm>ds1>channel-group# exitconfig>port>tdm>ds1# no shutdownconfig>port>tdm>ds1# exitconfig>port>tdm# exitconfig>port# exit
- Create an MLPPP bundle using the three DS1s.CLI Syntax:configure port bundle-ppp-1/2.1config>port# multilink-bundleconfig>port>ml-bundle# member 1/2/2.1.1.1.1config>port>ml-bundle# member 1/2/2.1.1.2.1config>port>ml-bundle# member 1/2/2.1.1.3.1config>port>ml-bundle# exitconfig>port# no shutdownconfig>port# exit
- Repeat the same configurations on 7705 SAR_119 port 1/2/2.
3.11.2.6.5.2. Verifying the Configured Network Ports
3.11.2.6.5.3. Verifying the Available Channelization
Use the port-tree command to confirm the current channelization of the OC3 channel.
Until port 1/2/1 is configured, the default STS3 is subdivided into three STS1s, each having a payload type of DS3.
When port 1/2/1 path sts1-1 has been provisioned (indicated in the following output by an “*” in line 574652478), all the available VT1.5 paths under sts1-1 on port 1/2/1 are created and listed. In this case, all seven VT groups (VTGs) are listed, each containing four VT1.5 paths. The remaining two STS1s (sts1-2 and sts1-3) still have DS3 payloads.
| Note: The same show>port-tree display is used for both SONET and SDH. The SONET nomenclature is used to show both SONET and SDH hierarchies. |
The following configure command provisions sts1-1 with VT1.5 paths, which appear in the port-tree command that follows.
3.11.2.7. 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.
3.11.2.8. Configuring Codirectional G.703 Ports
Use the following CLI syntax to configure a codirectional G.703 port on an 8-port Voice & Teleprotection card.
The following CLI syntax shows an example of configuring a codirectional G.703 port on an 8-port Voice & Teleprotection card.
3.11.2.9. Configuring Teleprotection Ports
Use the following CLI syntax to configure a teleprotection port on an 8-port Voice & Teleprotection card or 8-port C37.94 Teleprotection card.
The following CLI syntax shows an example of configuring a teleprotection port on an 8-port Voice & Teleprotection card or an 8-port C37.94 Teleprotection card.
3.11.2.10. Configuring TDM PPP
Use the following CLI syntax to configure PPP parameters for TDM DS3/E3 ports or DS3 channels.
3.11.2.11. Configuring Channelized Ports
Channelized ports are supported on the following cards and modules:
- 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 / 1-port OC12/STM4 Adapter card
- 4-port DS3/E3 Adapter card
- 8-port Voice & Teleprotection card
- 8-port C37.94 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
3.11.2.11.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 Shelf V2.
Use the show mda detail command to show detailed information for the channelized adapter cards shown in the previous example.
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 / 1-port OC12/STM4 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, RS-530, 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.
On the 8-port Voice & Teleprotection card, a single DS0 channel group and its parameters are configured in the codirectional, FXO, FXS, or TPIF context and up to 12 timeslots can be assigned in the TPIF context.
On the 8-port C37.94 Teleprotection card, a single DS0 channel group and its parameters are configured in the TPIF context and up to 12 timeslots can be assigned in 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.
3.11.2.12. 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.
The following cards and platforms support fractional T1/E1 on a PPP channel group (encapsulation type ppp-auto), or all timeslots on T1/E1 ports, in network mode:
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
- T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on 7705 SAR-H)
- T1/E1 ports on the 7705 SAR-A
- T1/E1 ports on the 7705 SAR-M
- T1/E1 ports on the 7705 SAR-X
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:
3.11.2.13. 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 ft 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 ft on a T1 port.
Use the config port info command to display port configuration information.
3.11.2.14. Configuring DS1 or E1 SSM
Use the following CLI syntax to configure Synchronization Status Messaging (SSM) for DS1 or E1 TDM ports.
| Note:
|
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.
3.11.2.15. 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 Shelf V2 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).
3.11.2.15.1. 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.
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.
3.11.2.16. Configuring Multilink PPP Bundles
The following cards, modules, and platforms support multilink bundles:
- T1/E1 ports on the 7705 SAR-A
- T1/E1 ports on the 7705 SAR-M
- T1/E1 ports on the 7705 SAR-XThe following must have all member links of an MLPPP bundle configured on the same card or module:
- 16-port T1/E1 ASAP Adapter card
- 32-port T1/E1 ASAP Adapter card
- T1/E1 ports on the 4-port T1/E1 and RS-232 Combination module (on 7705 SAR-H)
The following must have all member links of an MLPPP bundle configured on the same card or module, and on the same port:- 2-port OC3/STM1 Channelized Adapter card
- 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
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 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.
3.11.2.17. 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 fragments 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 port info command to display port configuration information.
3.11.2.18. Configuring LAG Parameters
Observe the following general rules and conditions when configuring LAGs.
- All ports (links) in a LAG must share the same characteristics (speed, duplex, hold-timer, and so on). The port characteristics are inherited from the primary port.
- 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 with the same encapsulation value.
- LAG is supported on Ethernet access, network, and hybrid ports.
- On access ports, the links must be distributed over two different adapter cards or different MDAs on the 7705 SAR-X, in order to minimize the effect of an adapter card failure on the LAG.
- On network ports, the links can be on the same platform or adapter card/module or distributed over multiple components.
- A LAG can be in active/active mode or in active/standby mode for access, network, or hybrid mode. Active/standby mode is a subset of active/active mode if subgroups are enabled.
- By default, LACP is disabled. 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.
Note: LACP cannot be configured for static LAG. For more information on static LAG, see Static LAG (Active/Standby LAG Operation without LACP).
- Each link in a LAG must be a member of a subgroup. On access, network or hybrid ports, a LAG can have a maximum of four subgroups and a subgroup can have links up to the maximum number supported on the LAG. LAG is active/active if there is only one sub-group. LAG is active/standby if there is more than one subgroup.
- The port with the highest priority is the primary port. If multiple 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.
- 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 Mixed-Generation Hardware 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. Therefore, 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.
Additional general rules for LAG configuration are as follows.
- Most port features (port commands) can only be configured on the primary member port. The configuration, or any change to the configuration, is automatically propagated to any remaining ports within the same LAG. Operators cannot modify the configurations on non-primary ports.
- When adding the first port member to a LAG group, its port configuration becomes the configuration of the LAG group.
- Once a LAG group has been created, new ports can be added to the LAG group only if their port configurations match with the LAG group configurations inherited from the group’s existing primary port. A newly added port may become the primary port or a non-primary port, depending on the setting of the LAG selection criteria, priorities, and so on.
- Not all configurations follow the conventions above. Some exceptions include the commands loopback (internal or line), cfm-loopback, mac, lldp, dot1x, and efm-oam.
- At boot-up, port configuration is applied before LAG configuration is applied. Therefore, configuration values are allowed or prohibited for both a standalone port and a port attached to a LAG group; otherwise, a database restore or exec command will fail. For example, if the scheduler mode profile command option is supported on a Gen-2 port that is the primary member of a LAG, operators are allowed to change scheduler-mode on other member links, including Gen-1 and Gen-3 ports. If the scheduler mode profile command option is blocked for a standalone Gen-2 port, then after issuing an admin>save command followed by a reboot command, the node will fail to reload the database file.
The following CLI syntax shows an example of configuring LAG parameters:
The following example displays a LAG configuration:
3.11.2.19. 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, 2-port OC3/STM1 Channelized Adapter cards, and T1/E1 ports on the 7705 SAR-M. The groups aggregate E1 or DS1 ATM channels into a single logical ATM interface.
3.11.2.19.1. Configuring IMA Groups
Use the following CLI syntax to configure IMA group parameters.
3.11.2.19.2. 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 the ifindexes 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
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:
3.11.2.19.3. 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.
3.11.2.20. 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 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:
3.11.2.21. 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 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 serial ports
Frame relay ports can be configured in access mode to support:
- Fpipes on:
- 16-port T1/E1 ASAP Adapter card 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 serial ports
- Ipipes on:
- 16-port T1/E1 ASAP Adapter card 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 serial 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 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.
3.11.2.22. Configuring TDM and SDI Ports for HDLC Encapsulation
HDLC service can be configured on the following ports:
- 16-port T1/E1 ASAP Adapter card 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 or 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:
3.11.2.23. 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 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 or 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:
3.11.2.24. Configuring GNSS Receiver Port Parameters
Use the following CLI syntax to configure GNSS receiver port parameters.
3.11.2.25. Configuring Serial Ports for Raw Socket Transport
Use the following CLI syntax to configure raw socket parameters on an RS-232 serial port.
| Note: Raw sockets are only supported on RS-232 serial ports. |
3.11.3. 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 scada info command to display the new SCADA bridge configuration information:
3.12. Service Management Tasks
This section describes the following service management tasks:
3.12.1. Changing a Provisioned Adapter Card Type
To change an adapter card type already provisioned for a specific slot, you must shut down any existing port configurations on the card, delete the adapter card configuration, and provision the new adapter card.
Use the following CLI syntax to change an adapter card type:
The following CLI syntax shows an example of modifying an adapter card.
3.12.2. Deleting an Adapter Card
To delete an adapter card provisioned for a specific slot, you must shut down any existing port configurations on the card and delete the adapter card configuration.
Use the following CLI syntax to delete an adapter card provisioned for a specific slot.
The following CLI syntax shows an example of deleting an adapter card.