|
|
This chapter describes the commands that let you set up an IGX or BPX node. (You must set up each node before you build the network.) This chapter also describes how to:
Before you can add a node to the network, you need to assign a unique node name. All nodes initially have the default name NODENAME. The node name consists of one to eight printable characters (beginning with a letter), and cannot contain spaces. If you are naming the node after a city or place that contains more than eight characters, you will have to abbreviate the name to create a valid network node name. The name must be unique across the network. For example, to assign the node the name of alpha, enter:
cnfname alphaTo change a node name, do the following:
Step 1 Sign on to (or establish a virtual terminal connection with) the node whose name you want to change.
Step 2 Change the name of the node using the cnfname command.
The name of the node you are connected to changes to the new name. This new name will be distributed automatically to other nodes in the network.
Each node must have a time zone. To set the time zone for the node to Greenwich Mean Time, for example, enter:
cnftmzn GMTSince Release 7.0, "packet lines" have been referred to as trunks. Use the letters "trk" in all commands referring to packet lines. To remove a trunk from the network, do the following.
Step 1 Sign on to (or establish a virtual terminal connection with) the node.
Step 2 Delete all packet (trunk) lines attached to the node using the deltrk command. For example, to delete line 5, enter: deltrk 5.
An interface shelf is a non-routing device that drives ATM cells to and from a BPX or IGX routing hub in a tiered network. (An interface shelf is also sometimes referred to as a feeder shelf.) An interface shelf can be either an IGX or MGX 8850 node configured as an interface shelf, or an MGX 8220 interface shelf.
Because tiered network capability is a purchased option, for an IGX node to serve as an interface shelf, personnel in the Technical Assistance Center (TAC) must first configure it for that purpose. Furthermore, you must use the cnftrk command to configure an interface shelf to use STI cell headers and BPX Addressing Mode (BAM). Before you can add an MGX 8220 shelf to a tiered network, the shelf must be an available resource in the network. (For instructions on how to bring up an MGX 8220 shelf, see the MGX 8220 documentation.)
To add an interface shelf, use addshelf. See Figure 3-7 for an illustration of the command sequence for setting up an interface shelf. To delete a feeder shelf, use delshelf. To view conditions on a feeder trunk, use dspnode. (Note that addshelf and addtrk are mutually exclusive commands.
IGX/AF is the designation of an IGX node serving as an interface shelf. Display commands such as dspnw and dspnode display these designations. The dspnode command identifies the hub and feeder nodes and shows the alarm status. The designation for an MGX 8220 shelf serving as an interface shelf is AXIS. The designation for an MGX 8850 serving as an interface shelf is AAL5. The designation for an SES (Service Expansion Shelf) shelf serving as an interface shelf is also AAL5.
The following procedure applies when adding any supported feeder to an IGX routing node. To configure an SES (Service Expansion Shelf) as a feeder to an IGX 8400 routing hub:
You can set up port redundancy by installing two identical front and back card sets, connecting them with a Y-cable on each paired port, then specifying redundancy with the addyred command. Redundancy applies to the entire card and is not port or line-specific. The commands that apply to Y-cable redundancy are:
During normal operation, the primary set is "active" and carrying traffic, while the secondary set is in "standby." The primary set configuration is the configuration for both the primary and redundant set. If you reset the primary cards or the primary card set becomes inactive for another reason, the secondary card set becomes active.
IGX card sets can consist of the following:
BPX card sets may consist of the following:
The following requirements apply to redundant card sets:
Figure 3-1 illustrates the typical Y-cable connection of primary and secondary card sets. The single end of a Y-cable (or base of the "Y") goes to the user equipment. One of the two connectors at the split end goes to the primary back card, and the other connector goes to the secondary back card.
Switching to the standby card occurs only if the secondary card set is in a "Standby" or a "Standby-T" state (but not "Failed"). See the dspcds definition for information on these states.
On multiport card sets, each primary port is connected by a Y-cable to a secondary (redundant) port. Port 1 of the primary card set must be paired to port 1 of the secondary card set, and so on. Figure 3-2 illustrates the cabling for a multiport card set.
If the secondary card set becomes active, the primary card set goes into the standby state. For the primary card set to serve as a backup, it must be a complete set and not have failed status.
You can execute addyred even if the primary and secondary slots are empty. If cards reside in the primary and secondary slots, the system checks for card compatibility. Two types of incompatibility can occur: back card and jumper or cable. (On SDI, FRI, and FTI cards, jumpers determine whether a port is configured as DCE or DTE. On LDI cards, either a DCE or DTE adapter cable connects to the LDI port, as applicable).
If incompatibilities exist, the message "Y-Cable Conflict" appears on screen. Specific conflicts are listed in reverse video in the Y-Cable Redundancy screen. See the dspyred description for details. Redundancy on V.35 versions of the SDI and FRI cards requires special redundant jumpers. Always use the applicable Y-Cable Redundancy kit for a card.
Y-Cable redundancy is supported for both the UXM and BXM trunk cards at the edge of the ATM cloud.
If your system is configured to control an external device, such as a multiplexer, you can establish a window session to it from the control terminal. While in a window session, any characters you type at the control terminal go to the external device for processing. Any characters generated by the external device appear on the control terminal screen.
The Window to External Device (window) command establishes a window session. You can use this command only if the external device connects to the local node. You can, however, enter the window command during a virtual terminal session so that you have a window session with any external device in the network. To start a window session, use the Virtual Terminal (vt) command to access the node cabled to the device, then invoke the window command. Before starting a window session, you must have configured the port and the port function with cnfterm and cnftermfunc. In addition, you must know whether the external window device is cabled to a node's Control Terminal (EIA/TIA-232) port or Aux Port (EIA/TIA-232) port. The format for the window command is:
Enter an a if the external device is attached to the node's Aux Port or c if the device is attached to the node's Control Terminal port. The default for this parameter is Aux Port. To establish a window session with an external device attached to a node's Control Terminal port, enter:
The system responds by redrawing the terminal screen. You can now enter commands and send data to the external device as if you were locally connected to its Control Terminal port. While in the window session, only commands used to control the external device are recognized. IGX/BPX commands are not recognized. You might notice a slight transfer delay in transmission, due to the IGX/BPX bundling of characters before transmitting them. Transfers are delayed until the transfer buffer is filled, or until the keyboard has been inactive for over 50 milliseconds.
To end a window session, enter an escape sequence. Escape sequences are one to eight characters in length and are configured with the Configure Terminal Port Function (cnftermfunc) command. For example, if you have specified "signoff" as the escape sequence in the Configure Terminal Port Function, enter the following to end the window session:
The default escape sequence is:
If this escape sequence does not work and you do not know the configured escape sequence, leave the keyboard idle for four minutes. After four minutes, the system terminates the window session.
The sequences in Figure 3-3, Figure 3-4, Figure 3-5, Figure 3-6, and Figure 3-7 show the commands you execute to do the following node-related tasks:
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature provides a mechanism to send Abit = 0 status change over the LMI interface or send ILMI traps over the ILMI interface after the connections are derouted a certain amount of time. You can configure this time period by setting some cnfnodeparm parameters. This configurable time approach provides you with the flexibility to synchronize the operation of the primary network and backup utilities, such as dialed backup over the ISDN or PSTN network. This feature is supported on both the BPX and IGX platforms.
These brief definitions are relevant to the Early Abit Notifications on ILMI/LMI Interface using Configurable Timer feature:
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature allows Abit notifications to be sent over the LMI/ILMI interface if a connection cannot be rerouted after a user-specified time. Abit = 0 will not be sent if the connection is rerouted successfully during that time.
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature provides the user flexibility to configure the time when the node will start sending out Abit = 0 after a connection becomes derouted. This allows the CPE to take appropriate actions such as initiating the dialed backup process if the deroute process has not finished during a certain period of time.
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature is an enhancement to the Send Abit on Deroute feature provided in Release 9.1.07 for the BPX. To minimize the risk in deploying this feature, and to continue to support the Send Abit on Deroute feature, which was developed in Release 9.1.07 for BPX, the feature has the following guidelines:
1. You can enable this feature by using the cnfnodeparm command. You can specify that Abit Notification be sent either on deroute, or a user-configurable time after deroute. This feature can also be turned off. It is recommended that this feature be set the same on all nodes. Otherwise, the Abit behavior can be different on different nodes.
2. If this feature is turned off, switch software behaves the same as in previous releases. Existing functionality continues to function in a mixed release network (releases 8.4, 8.5, or 9.1 IGX or BPX network).
3. The Early Abit Notification on ILMI/LMI Using Configurable Timer feature is provided on both BPX and IGX platforms.
4. If the cnfnodeparm Abit Timer Multiplier M parameter is set to 0, then switch software behaves the same way as in Release 9.1.07 (which supported the Send Abit on Deroute feature).
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature is supported on IGX and BPX switch software. No new hardware or firmware is required on line cards or feeder trunk cards.
You can enable the Early Abit Notification on ILMI/LMI Using Configurable Timer feature on both IGX and BPX by using cnfnodeparm command parameters Send Abit Early, Abit Timer Multiplier M, and Abit Timer Granularity N.
A Release 9.2 IGX or BPX node using this feature is compatible with Release 8.4 and Release 8.5 nodes or Release 9.1 IGX and BPX nodes so that all existing connection related functions will continue to work. However, the timing in sending out the Abit notifications at both ends of connections may behave differently, depending on how this feature is configured.
The time to reroute connections varies depending on different parameters, such as the number of connections to reroute, reroute bundle size, and so on. It is important to notify the CPE if a connection is derouted and fails to transport user data after a specified time interval. However, it is desirable not to send out Abit = 0 and then Abit = 1 when a connection is derouted and rerouted quickly, because such notifications may trigger the CPE backup facilities, which is a costly process and may cause fluctuations in an otherwise stable system. The configurable time interval is a direct solution to these problems.
The Early Abit Notification on ILMI/LMI Using Configurable Timer feature allows you to specify the time interval after which to start sending out Abit = 0 if a connection fails to reroute and is in the derouted state too long. To avoid having an adverse performance impact on the system, no precise timer is kept for each connection. Instead, all connections derouted during a certain time period go to the same bucket.
This time period is referred to as N, which defines the granularity of the timers, and is specified by the value of the cnfnodeparm Abit Timer Granularity N parameter. Another parameter is the time to wait before Abit = 0 is sent out if the connection is in a derouted state. This parameter is called X. A connection that is derouted at a period of time between 0 and N will send out Abit = 0 at a time between X and X + N, if the connection continues to be in a derouted state. In cases where there are many Abit status changes to report to CPE, the last Abit updates may be delayed much longer because Abit updates process about 47 connections per second.
To make a compromise between performance and the granularity of timers, N can be configured to be from 3 to 255 seconds; the bigger the value of N, the better the system performance will be. The other parameter, X, is set to be M*N, where M can be configured to be from 0 to 100. The default value for N is 3sec. Default value for M (Abit Timer Multiplier M parameter) is 0, meaning Abit = 0 is sent out on deroute.
It is recommended that X (value of Abit Timer Multiplier M * the value of the Abit Timer Granularity N) be set such that when a trunk fails, the connections are given sufficient time to reroute successfully, avoiding the need to send out Abit = 0.
The change in the Abit behavior is completely local to the node and is applicable to the master and slave ends of connections when the connections are derouted. When only one of the nodes connected by a connection has this feature turned on, the timing in sending the Abit notification at one end of the connection may be drastically different from the other end. Therefore it is recommended that the Early Abit Notification on ILMI/LMI Using Configurable Timer feature be configured the same on all nodes. Also, because timers on nodes are not in sync, there is a slight time difference (3 seconds maximum) in sending Abit from the two ends of a connection, even if the cnfnodeparm parameter settings on the nodes are the same.
If the value of X (value of Abit Timer Multiplier M * value of Abit Timer Granularity N) is set to be smaller than the normal time to reroute connections when a trunk fails, the time it takes to finish rerouting them may take longer. This can happen for line cards and feeder trunks, which have the LMI/ILMI protocol running on those cards, such as BXM on BPX and Frame Relay cards on IGX. Note that it takes time for those cards to process the Abit status information for each connection coming from the controller card.
There is no impact on control processor switchover or trunk card redundancy switchover because connections are not rerouted.
In releases previous to Release 9.1.07, when connections are derouted, the CPE does not receive Abit notifications. In Release 9.1.07 on BPX, the Send Abit on Deroute feature was developed, which allowed the Abit = 0 to be sent immediately when a connection is derouted. (This was specified by the cnfnodeparm parameter Send Abit immediately parameter.) To further enhance the Send Abit on Deroute feature in Release 9.1.07, the Early Abit Notification on ILMI/LMI Using Configurable Timer feature has been implemented in Release 9.2 to allow the network administrator to configure the node as to when Abit = 0 is sent out if a connection is derouted and not rerouted quickly. This feature allows you to specify when Abit notifications will be sent at Frame Relay and ATM ports, and at feeder trunks in a tiered network architecture that supports the ILMI/LMI interface. In a tiered network, the Abit information is used by the feeder nodes such as MGX 8220 (AXIS) which then relays the Abit information to the CPE.
The status update messages are throttled at the rate of one message per second. Each message can be used to specify the conditioning information on a maximum of 47 connections. It may take on the order of minutes for the ILMI/LMI manager to process the Abit status when there is a large number of connections.
There are two factors in performance: system performance and reroute time. System performance is affected by the value of the time interval. In a network where connections are normally derouted and rerouted quickly before the bucket timer expires, the performance impact is very small. Only when the timer expires, then looping through all LCONs and sending update messages will take up some CPU time which is estimated to be smaller than 1 percent.
Reroute time is not affected if LMI/ILMI is running on the controller card. When the protocol is implemented on the line cards and feeder trunk cards, some additional Abit status communication between them and controller card may delay the reroute process.
Specifically, on the BPX, if the BXM runs LMI/ILMI, the BCC has to send Abit update to the card. These messages will be throttled. When this happens, we estimate the time to reroute all 12K connections increases no more than 5per cent.
For the IGX, enabling the Sending Abit Notification using Configurable Timer feature may impact performance if many connections end at Frame Relay cards. This is due to the restricted format of interface between NPM and Frame Relay cards.
Together with the CPE equipment that has dialed backup capability, this feature increases the availability of the services between the CPEs.
This feature is blocked until all nodes are running Release 9.2. A Release 9.2 node with or without this feature being turned on can interwork with other 8.4 or 8.5 nodes or Release 9.1 nodes with all existing connection management functionality.
Table 3-1 shows the command name and starting page for the description of each node command.
| Mnemonic | Description | Page |
|---|---|---|
addalmslot | Add an alarm slot | |
addcdred | Add card redundancy for SONET APS 1+1 across two BXM cards | |
addctrlr | Add a PNNI VSI controller to a BPX node through an AAL5 interface shelf | |
addshelf | Add a trunk between an IGX or BPX core switch shelf and an interface shelf | |
addyred | Add Y-cable redundancy | |
cnfasm | Configure ASM card | |
cnfdate | Configure date | |
cnffunc | Configure system function | |
cnfname | Configure node name | |
cnfprt | Configure printing functions | |
cnfterm | Configure terminal port | |
cnftime | Configure time | |
cnftmzn | Configure time zone | |
delalmslot | Delete alarm slot | |
delshelf | Delete a trunk between a IGX/BPX core switch shelf and interface shelf | |
delcdred | Delete Y-cable redundancy (disables card redundancy (for SONET Automatic Protection Switching feature) | |
delyred | Delete Y-cable redundancy | |
dspasm | Display ASM card configuration | |
dspcd | Display card | |
dspcds | Display cards | |
dsplancnf | Display LAN configuration | |
dspctrlrs | Display all PNNI VSI controllers on a BPX node |
|
dsplmistats | Display LMI Statistics | |
dspnds | Display nodes | |
dspnode | Display summary information about interface shelves | |
dsptermcnf | Display terminal configuration | |
dsptermfunc | Display terminal port configuration | |
dspprtcnf | Display print configuration | |
Display power | ||
dspcdred | Display Y-cable redundancy (displays card redundancy for SONET Automatic Protection Switching) | |
dspyred | Display Y-cable redundancy | |
prtcdred | Print card redundancy (prints Y cable redundancy for SONET Automatic Protection Switching) | |
prtyred | Print Y-cable redundancy | |
upcd | Up card | |
window | Window to external device |
Enables the MAJOR and MINOR alarm indicators on an Alarm Relay Card (ARC) or Alarm Relay Module (ARM) front card. It also configures the slot to provide external alarms from the Alarm Relay Interface (ARI) back card. You should use this command at each node equipped to provide external alarm indications to the customer alarm reporting system. The slot specified for the ARC or ARM may be any shelf slot, but is usually the slot farthest to the right.
Upon executing the command, the system places the alarm card set in the active state and displays the current alarm status.
Add alarm slot.
addalmslot <slot number>
delalmslot, dspalms
Privilege | 1-4 |
Jobs | NO |
Log | Yes |
Node | IGX |
Lock | Yes |
addalmslot 16
Enable alarm reporting from slot 16 in a node. (The system then displays alarm status.)
beta TRM YourID:1 IGX 8430 9.2 Aug. 3 1998 14:27 MST
Alarm summary (Configured alarm slots: 16)
Connections Failed: None
Groups Failed: None
PLN Alarms: 1 Major
CLN Alarms: None
Cards Failed: 1
Missing Cards: None
Remote Node Alarms: 1 Major
Remote Domain Alarms: None
Last Command: addalmslot 16
Next Command:
| Parameter | Description |
|---|---|
slot number | Specifies the slot number of the alarm card set. |
The addcdred is an alias for the addyred command (thus has identical functionality) which lets you enable card and line redundancy for the cards on the IGX and BPX. It lets you add card and line redundancy for APS 1+1 across two BXM OC-3 and OC-12 cards. You also use it before enabling APS 1:1 line redundancy. It works similarly to the addyred command.
Use the addcdred command to specify the slots of the primary and secondary (standby) cards that form the redundant pair.
When configuring APS 1+1 card and line redundancy, you must execute the addcdred command before using addapsln. Refer to the "APS 1+1 (Card and Line Redundancy)" section" for more information on setting up APS 1+1 card and line redundancy.
Redundant card sets must have the following characteristics:
In both the single and multiport card sets, if the secondary card set becomes active, the primary card set serves as its backup (assuming the primary card set is complete and not failed). You cannot use the addcdred command on empty card slots. If one or both of the card slots is empty, and you use the addcdred command, the command will fail.
If cards reside in the primary and secondary slots, the system checks for card compatibility. The following types of incompatibility can occur: back card and jumper or cable inconsistencies. Also, the addcdred command can fail because of firmware capabilities conflicts. For example, if one of the cards supports virtual trunking, and the other doesn't support virtual trunking, the addcdred command might fail. Refer to the Cisco BPX 8600 Series Installation and Configuration manual for more information on configuring SONET APS 1+1 card and line redundancy for BXM OC-3 and OC-12 cards.
The same numbered ports on adjacent BXM cards are used. A hardware, firmware, and software upgrade is required. (Firmware that supports APS 1+1 setup, and switch software Release 9.2 is required.)
The APS 1+1 feature requires two BXM front cards, an APS redundant frame assembly, and two redundant type BXM backcards. The two redundant BXM backcards are plugged into the APS redundant frame assembly. (Refer to the SONET APS Configuration chapter in the Cisco BPX 8600 Series Installation and Configuration guide for more information on APS hardware configuration.) The types of redundant back card and backplane sets required are:
The single backcards and mini-backplane can be ordered as spares. Their model numbers are:
If incompatibilities exist, the message "Y-Cable Conflict" appears on the screen. Specific conflicts are listed in reverse video on the dspcdred display. See the dspcdred description for more information.
In this release, to ensure that only cards with the Idle Code Suppression feature enabled on them are allowed to be a Y-redundancy pair, addcdred blocks cards that have different idle code suppression capability.
Add card redundancy for SONET Automatic Protection Switching (APS) across two OC-3 or OC-12 cards.
addcdred <primary slot> <secondary slot>
delcdred, dspcdred, prtcdred, switchcdred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | BPX |
Lock | Yes |
addcdred 2 3
Add redundant line on port 1 for BXM OC-3 card and APS backcards in slots 2 and 3 of the BPX.
beta TRM YourID:1 BPX 8620 9.2 Aug. 15 1997 14:27 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM
Last Command: addcdred 2 3
Next Command:
| Parameter | Description |
|---|---|
primary slot | Specifies the slot number of the primary card set. |
secondary slot | Specifies the slot number of the secondary card set. |
Adds VSI capabilities to a trunk interface to which a feeder of type AAL5 is attached. The addctrlr command is used only to connect a Private Network to Network Interface (PNNI) controller. PNNI is the software residing on the Service Expansion Shelf (SES) hardware
The addctrlr command is the second step in the adding of a PNNI controller to a BPX node.
The first step is to run the command addshelf with shelf type set to "X" to add a AAL5 feeder.
Then run the addctrlr command to set up the VSI control channels from the SES PNNI controller to the VSI slave processes running on the BXM cards to ensure full VSI functionality for the PNNI controller. You execute the addctrlr command on an existing AAL5 interface shelf.
Also note that you can add a PNNI controller to a Trunk interface only if the interface already has an active VSI partition corresponding to the partition that is controlled by the PNNI controller. Suppose a PNNI controller controlling the partition "1" were added to an trunk interface 12.1. Then it would be necessary that a VSI partition corresponding to partition "1" be active on the interface 12.1. Otherwise the addctrlr command would fail.
When you add VSI controller capabilities onto an AAL5 interface shelf (or feeder), the switch software prompts you for the specifics of the VSI controller:
Note that the addctrlr command does not prompt you for the controller name. The controller name is the same as the interface shelf, or feeder, name.
There could be 12 BXM cards on the BPX node and the PNNI controller would control VSI partitions on those BXM cards that support VSI capability. Hence a separate VSI control channel must be set up from the PNNI control to each BXM card that supports VSI. Suppose you specify a VPI value of 0 and start VCI value of 40 for the VSI control channels. Then the control channel corresponding to any BXM card on slot 1 would use VPI, VCI values <0, 40>. The VSI control channels to other slots would use the VPI, VCI values of <0, 40+slot-1>, where "slot" corresponds to the slot number of the BXM card.
The PNNI is the latest networking application controller that can control a BPX node's resources. PNNI runs on the MGX 8850 and SES platforms. The MGX 8850 connects to the BPX through an already-defined AAL5 interface shelf. The AAL5 interface shelf has Annex G capabilities. The PNNI can be configured as a VSI controller.
You use the addctrl and delctrlr commands to add and delete an MGX 8220 and MGX 8850 interface shelf configured with VSI controller capabilities. See the delctrlr command for information on deleting a PNNI (PNNI) controller from a BPX.
In this release, the addctrlr command can be used for controllers that require Annex G capabilities in the controller interface. In this release, the parameters "Control VPI" and "Control VCI start" have been added.
In this release you still use the same commands as in Release 9.1 to configure a VSI controller partition's resources: cnfrsrc, cnfqbin, dsprsrc, and dspqbin.
The management of resources on the VSI slaves requires that each slave in the node has a communication control VC to each of the controllers attached to the node. When a controller is added to the BCC, the BCC sets up the set of master-slave connections between the new controller port and each of the active slaves in the switch. The connections are set up using a well known vpi.vci. The value of the VPI is 0, and the value of the VCI is (40 + slot -1) where slot is the logical slot number of the slave, for ports, physical trunks, and feeder trunks case. For virtual trunks, the VPI used is the one configured in the command cnftrk and the vci used is (259 + slot -1).
The management of resources on the VSI slaves requires that each slave in the node has a communication control VC to each of the controllers attached to the node. When a controller is added to the BCC, the BCC sets up the set of master-slave connections between the new controller port and each of the active slaves in the switch.
You use addctrlr to set up the connections with the VPI/VCI. You enter the value of VPI; and the value of VCI is (value of VCI + slot -1) where slot is the logical slot number of the slave. The default values for these parameters are VPI=0 and VCI=40-53.
For feeder trunk interfaces, the addctrlr command will fail. You must delete the connections before proceeding if connections with VPI and VCI in the range exist in the range you specified.
The addition of a controller to a node will fail if there are not enough channels available to set up the control VCs in one or more of the BXM slaves.
The BCC also informs the slaves of the new controller through the VSI configuration CommBus message. The message include a list of controllers attached to the switch and their corresponding controller IDs.
Add VSI capabilities to a AAL5 feeder interface.
addctrlr < slot.port> <controller id> <partition id> <control_vpi> <start_vci>
| Parameter | Description |
|---|---|
<slot.port> | Slot and Port numbers corresponding to the feeder trunk |
<controller-id> | Controller ID corresponding to the PNNI controller. Values: 1-32 |
<partition-id> | Partition ID of the VSI partition controlled by the PNNI controller |
<control_vpi> | Starting VPI of the VSI control channels used for communication between the VSI master residing on the SES and VSI slaves residing on the BXM cards. There can be a total of 12 such channels one for each slave residing on each BXM card. For a trunk interface with NNI header type: For a trunk interface with UNI header type Default value: 0 |
<start_vci> | Starting VCI of the VSI control channels. This vci value is assigned to the first VSI control channel (between the VSI master and the VSI slave residing on the BXM card in slot 1). The last VSI control channel corresponding to communication with the VSI slave on slot 14 will use the vci value of (<start_vci>+14-1). The valid values are: 33 - 65521. Default value: 40 |
addshelf, delctrlr, dspctrlrs
Privilege | 1 |
Jobs | No |
Log | Yes |
Node | BPX |
Lock | Yes |
addctrlr 10.4 3 2 0 40
Add controller to port 4 on slot 10, partition ID of 2, and controller ID of 3.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl ID Ctrl IP State
10.3 PNNI VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Warning partition already in use do you want to add redundant controller
Last Command: addctrlr 10.4 3 2 0 40
Next Command:
Adds a controller, such a PNNI controller, to a BPX interface shelf.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Controllers Information
Trunk Name Type Part Id Ctrl ID Ctrl IP State
10.3 PNNI VSI 1 1 192.0.0.0 Enabled
11.1 VSI VSI 2 2 192.0.0.0 Disabled
Warning partition already in use do you want to add redundant controller
Last Command: addctrlr 10.3 3 1 0 40
Next Command:
Adds an ATM link between an IGX/BPX core switch shelf and an interface shelf such as an MGX 8220, MGX 8850, IGX shelf, or SES (Service Expansion Shelf) in a tiered network; or an ATM link between a BXM card on a BPX node and a Label Switch Controller (LSC) such as a series 7200 or 7500 router; or an ATM link between a BXM card on a BPX node and an Extended Services Processor. (An MPLS controller, a PNNI controller, or an Extended Services Processor controller is considered an interface shelf from the BPX's perspective.) The routing hub can be either a BPX or an IGX.
The interface shelf can be one of the following:
The signaling protocol that applies to the trunk on an interface shelf is Annex G. (Annex G is a bidirectional protocol defined in Recommendation Q.2931, used to monitor the status of connections across a UNI interface. The Annex G protocol is used in this release to pass connection status information between a IGX/BPX core switch shelf and an attached feeder.)
Each IGX/AF, MGX 8220, MGX 8850, or SES shelf has one trunk that connects to the BPX or IGX node serving as an access hub. A BPX routing hub can support up to 16 T3 trunks to the interface shelves, which can be IGX/AF, MGX 8220, or MGX 8850 interface shelves. An IGX hub can support up to four trunks to the interface shelves, which can be IGX/AF or SES (Service Expansion Shelf) shelves.
Before it can carry traffic, you must "up" the trunk on an interface shelf (using uptrk on both the interface shelf and the IGX/BPX core switch shelf) and "add" it to the network (using addshelf). Also, a trunk must be free of major alarms before you can add it with the addshelf command.
In this release, the commands addshelf and addctrlr are used to add a MPLS/PNNI controller to the BPX. The command addshelf with option "v" is used to add a VSI shelf. This is used mainly for MPLS controllers. The command addctrlr is used to add a controller to a shelf that has LMI capabilities.
In this release, you can use an IGX as a feeder node to connect via a UXM IMA trunk to an IGX or BPX router node using IMATM. You use addshelf with the I option at the IGX node to add the feeder trunk connecting it to an IGX feeder node.
Add an interface shelf (feeder) or a controller to a routing node or hub.
Interface shelf:
addshelf <slot.port> <shelf-type> [vpi] [vci]
addshelf <slot>.<primary link> <shelf type>
Tag switch controller:
addshelf <slot.port> <device-type> <control partition> <control ID>
VSI controller:
addshelf <trunk slot.port> v <ctrlr id> <part id> <control vpi> <control vci start> <redundant ctrlr warning>
delshelf, dspnode, dsptrks
Privilege | 1-4 |
Jobs | Yes |
Log | Yes |
Node | BPX switch with IGX interface shelves BPX switch with the MGX 8220 interface shelf BPX with the MGX 8850 interface shelf BPX switch for MPLS controller BPX switch for the Extended Services Processor (ESP) IGX switch for the Service Expansion Shelf (SES) |
Lock | Yes |
Interface shelf: addshelf 11.1 a 21 200
Label switch controller: addshelf 4.1 vsi 1 1
Interface shelf:
Add trunk 11.1 as an MGX 8220 interface shelf. After you add the shelf, the screen displays a confirmation message and the name of the shelf.
MPLS controller:
Add trunk 4.1 as a MPLS Controller interface shelf. After you add the MPLS controller, the screen displays a confirmation message and the name of the shelf:
An interface shelf can be one of the following:
| Parameter | Description |
|---|---|
slot.port (trunk) | slot.port Specifies the slot and port number of the trunk. |
shelf-type | I, A, P, V, X On a BPX node, shelf type specifies the type of interface shelf when you execute addshelf. The choices are I for IGX/AF, A for the MGX 8220, P for EPS (Extended Services Processor, a type of adjunct processor shelf), V for VSI, or X for the MGX 8800. In the case of BNI, only two options are available: I for IGX/AF, A for the MGX 8220. On an IGX node, shelf type specifies the type of interface shelf you can add. The choices are I for IGX/AF or X for AAL5 for an SES (Service Expansion Shelf). |
vpi vci | vpi, vci are optional when adding an interface shelf (feeder). |
Control VPI | The (VPI.VCI) of the 15 control VCs is (control_VPI.control_VCI_start) to (control_VPI.control_VCI_start+14).The control VC used for slot n (1<= n<=15) is (control_VPI.control_VCI_start + n -1). <control_VPI> should be chosen such that: ♦ if <control_VPI> = 0, <control_VCI_start> can be set to a value > 40. ♦ If any VSI partition exists on the interface, then control_VPI < start_VPI or control_VPI > end_VPI for all partitions on that interface. An error message is displayed if the control VPI falls into the VPI range belonging to a VSI partition. ♦ No AutoRoute connection exists on (VPI.start_VCI to VPI.start_VCI+14). If any AutoRoute connection exists on these VPI/VCI values, you are not allowed to use these VPI/VCI values. ♦ This VPI is "reserved" for control VCs.
|
Add an MGX 8220 at trunk 11.1 After you add the shelf, the screen displays a confirmation message and the name of the shelf. Add the MGX 8220 (may be referred to on screen as AXIS) as follows:
addshelf 11.1 a
The sample display shows a partially executed command prompting you for the interface shelf type:
nmsbpx23 TN SuperUser BPX 620 9.2 Apr. 4 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
1.3 AXIS240 AXIS OK
11.2 A242 AXIS OK
This Command: addshelf 11.1
Enter Interface Shelf Type: I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)
Next Command:
Add an MGX 8850 at trunk 4.1. After you add the MGX 8850 interface shelf, the screen displays a confirmation message and the name of the shelf. Add the MGX 8850 (may be referred to on-screen as AAL5) as follows:
addshelf 4.1 x
The sample display initially shows the output of a dsptrks command, then shows how an MGX 8850 was added on trunk 4.1 as an AAL5 type of interface shelf. (AAL5 is the ATM Adaptive Layer 5 protocol, which is an ATM standard interface that is used by the routing node or routing hub to communicate to the MGX 8850 and Service Expansion Shelf feeders.) Adding an MGX 8850 interface shelf or a Service Expansion Shelf is similar to adding an MPLS controller or a PNNI controller.
In releases previous to Release 9.2.10, for BTM E1/T3 feeder interface types, addshelf does not prompt you for the "Interface Shelf Type". In this release, addshelf will prompt you for the "Interface Shelf Type". (This is needed to distinguish which signalling protocol is used.) Because MGX 8220, MGX 8850 and SES use the same LMI signalling protocol, you will be prompted for the "Interface Shelf Type (A) AAL5".
sw288 TN SuperUser BPX 8620 9.2.j2 Dec. 10 1998 15:38 PST
TRK Type Current Line Alarm Status Other End
4.1 OC-12 Clear - OK -
11.2 T3 Clear - OK redhook/14
11.3 T3 Clear - OK sw113/16
This Command: addshelf 4.1
Enter Interface Shelf Type: I (IGX), A (AXIS), P (APS), V (VSI), X (AAL5)
BPX Interface Shelf Information
Trunk Name Type Part Id Ctrl Id Alarm
4.1 SIMFDR0 AAL5 - - OK
This Command: addshelf 4.1 x
Enter Interface Shelf Type: A (AXIS), P (APS), V (VSI), X (AAL5)
Shelf has been added
Next Command:
Add an SES interface shelf to an IGX 8400 (using a UXM or UXM-E interface). After you add the SES interface shelf, the screen displays a confirmation message and the name of the shelf. Add the SES (may be referred to on-screen as AAL5) as follows:
addshelf 6.1 X
Enter Interface Shelf Type: X (AAL5)
sw288 TN SuperUser IGX 8420 9.2.2I Dec. 10 1998 15:38 PST
TRK Type Type Alarm
9.1 ases1 AAL5 MIN
This Command: addshelf 4.1
Enter Interface Shelf Type: I (IGX), A (AXIS), P (APS), V (VSI), X (AAL5)
IGX Interface Shelf Information
Trunk Name Type Alarm
9.1 ses_fdr AAL5 MIN
This Command: addshelf 4.1 x
Enter Interface Shelf Type: A (AXIS), P (APS), V (VSI), X (AAL5)
Shelf has been added
Next Command:
The sample display shows that an SES was added on trunk 9.1 as an AAL5 type of interface shelf. (AAL5 is the ATM Adaptive Layer 5 protocol, which is an ATM standard interface that is used by the routing node or routing hub to communicate with the SES shelves.) Adding an IGX interface shelf is similar to adding an MPLS (Multiprotocol Label Switching) controller as an interface shelf.
The addshelf command will prompt for "Interface Shelf Type". Because the MGX 8220, MGX 8850 and the SES (Service Expansion Shelf) use the same Annex G LMI signalling protocol to communicate with an IGX routing hub, they all use the same interface shelf type of AAL5 (designated by the addshelf "X" option).
Previous to Release 9.2, WAN switching software supported the ability to configure an IGX 8400 as an interface shelf to the IGX 8400 hub over a BTM E1 and T3 interface. Also, the MGX 8220 (formerly called "AXIS") is supported as an interface shelf to the BPX. Release 9.1 introduced the ability for the MGX 8850 to serve as an interface shelf to a BPX routing hub. Release 9.2 introduced the ability for an SES (Service Expansion Shelf) to serve as an interface shelf to an IGX 8400 routing hub.
In Release 9.2.20, the following are supported:
An MGX 8220, an ESP (an Extended Services Processor controller, or Adjunct Processor Shelf), or an MGX 8850 can connect as interface shelves to a BPX routing node. An IGX interface shelf can connect to an IGX 8400 routing node over a UXM/UXM-E interface. Similarly, in Release 9.2.10, an SES can connect to an IGX routing hub over a UXM/UXM-E interface. However, you cannot do the following:
Previous to Release 9.2, the IGX 8400 interface shelf communicated with the IGX 8400 routing hub using a BTM E1 interface over the Annex G LMI with STI format. In Release 9.2, the SES interface shelf with a UXM/UXM-E interface communicates with the routing hub over an Annex G LMI interface by using AAL5 format.
An SES feeder uses the Annex G protocol to pass connection status information between itself and an IGX 8400 routing hub. Similarly, an MGX 8850 feeder uses the Annex G signalling channel to pass connection status information between itself and a BPX routing hub.
Previous to Release 9.2, IP relay was supported by encapsulating the IP data in a network message when interfacing with an IGX 8400 interface shelf. In this release, the SES interface shelf communicates with an IGX routing hub through ATM cells. Thus, IP data destined for an IGX 8400 is encapsulated in an AAL5 ATM cell format.
Some of the possible error messages for the addshelf command:
pswbpx3 TN SuperUser BPX 8600 9.1 June 6 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Part Id Ctrl Id Alarm
4.8 SIMFDR0 AAL5 - - OK
This Command: addshelf 4.8 x
Enter Interface Shelf Type: I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)
Next Command:
For label switching, before it can carry traffic, you need to "up" the link to a tag switch controller (using either uptrk or upport) at the BPX node. You can then "add" the link to the network (using addshelf). Also, the link must be free of major alarms before you can add it with the addshelf command.
| Parameter | Description |
|---|---|
slot.port | Specifies the BXM slot and port number of the trunk. (You can configure the port for either trunk (network) or port (service) mode. |
device-type | vsi, for "virtual switch interface", specifies a virtual interface to an ATM-LSR (Label Switch Router) controller such as a Cisco 7200 or 7500 series router. Note that the "v" option is not applicable when configuring Automatic Routing Management PVCs. You only need to enter the "v" or "vsi" option when configuring VSI options. |
control partition | Specifies the control partition. You can typically leave this field blank when you add an MPLS (formerly Tag Switching) controller to a BPX or MGX 8800 node. |
control ID | Control IDs must be in the range of 1 to 32, and you must set these identically on the VSI-MPLS Controller and in the addshelf command. A control ID of "1" is the default used by the MPLS Controller (formerly Tag Switch Controller). |
Add an LSC (Label Switch Controller) link to a BPX node by entering the addshelf command at the desired BXM port as follows:
addshelf 4.1 vsi 1 1
nmsbpx23 TN SuperUser BPX 15 9.2 Apr. 4 1998 13:28 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
5.1 j6c AXIS MIN
5.3 j5c IGX/AF MIN
4.1 VSI VSI OK
This Command: addshelf 4.1 v 1 1
Next Command:
addshelf 11.1 vsi 1 2
Add a redundant (more than one) VSI controller (as an interface shelf to a BPX node), on slot 11 on port 1, with a control partition of 1 and control ID of 2.
night TN StrataCom BPX 8600 9.2.00 Apr. 11 1998 14:31 GMT
BPX Interface Shelf Information
Trunk Name Type Part Id Ctrl Id Alarm
1.1 sww222 IGX/AF - - UNRCH
10.3 VSI VSI 1 1 OK
Warning partition already in use do you want to add redundant controller?
Last Command: addshelf 11.1 vsi 1 2
addshelf 4.1 vsi 1 1
Add a VSI controller to port 4.1, controlling partition 1
n4 TN SuperUser BPX 8620 9.2 Apr. 4 1998 16:42 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
3.1 j6c AXIS MIN
5.3 j5c IGX/AF MIN
4.1 VSI VSI OK
Last Command: addshelf 4.1 vsi 1 1
Next Command:
The addyred command performs the same function as the addcdred command. It enables card redundancy for cards on the IGX and BPX. Use the addyred command to specify the slots of the primary and secondary (standby) cards that form the redundant pair. Refer to the "Specifying Card Redundancy " section at the beginning of this chapter for a list of supported card sets.
Redundant card sets must have the following characteristics:
If cards reside in the primary and secondary slots, the system checks for card compatibility. Two types of incompatibility can occur: back card and jumper or cable inconsistencies. (On SDI, FRI, and FTI cards, jumpers determine whether a port is configured as DCE or DTE. On LDI cards, either a DCE or DTE adapter cable connects to the LDI port. For descriptions of the jumper positions and cabling, see the Cisco IGX 8400 Series Installation and Configuration manual.)
Note that the addyred command prevents invalid configurations when you try to configure the SONET APS feature. When SONET Automatic Protection Switching (APS) is configured, you will not be able to use the addyred or delyred commands on a card configured for APS 1:1 architecture. That is, you will not be able to execute the addyred command, then configure the APS 1:1 architecture. Similarly, you will not be able to configure APS 1:1, then execute the addyred command. You will be blocked from executing these commands at the command line interface.
If incompatibilities exist, the message "Y-Cable Conflict" appears on the screen. Specific conflicts are listed in reverse video in the dspyred display. See the dspyred description for more information.
To ensure that only cards with the Idle Code Suppression feature enabled on them are allowed to be a Y-redundancy pair, addyred blocks cards that have different idle code suppression capability.
The addyred commands (addyred, delyred, dspyred, prtyred, switchyred) will perform feature mismatch checking on both the primary and secondary cards. For information on feature mismatch checking, see "Feature Mismatching" section.
During addyred's mismatch checking, the following verifications are done:
Add Y-cable redundancy.
addyred <primary slot> <secondary slot>
delyred, dspyred, prtyred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
addyred 2 3
Add Y-cable redundancy to the BXM card sets in slots 2 and 3.
beta TRM YourID:1 BPX 8620 9.2 Aug. 15 1998 14:27 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM
Last Command: addyred 2 3
Next Command:
| Parameter | Description |
|---|---|
primary slot | Specifies the slot number of the primary card set. |
secondary slot | Specifies the slot number of the secondary card set. |
Lets you set various configurable parameters associated with the BPX Alarm and Status Monitor card in slot 15. Because this card always resides in slot 15, entering the slot number is unnecessary. In Release 9.2, robust alarms are generated for the following alarm conditions:
These alarm conditions above appear in the maintenance log or in the node command line interface commands (dspasm), are not also reported as SNMP trap to the customer NMS. (Such traps are generated by the Cisco WAN Manager RTM proxy upon receiving Robust Alarms from a switch.)
In Release 9.2, robust alarms are generated by the BPX when power and temperature alarm conditions are detected by the ASM card. The ASM card monitors and reports events involving:
You configure and control the reporting of these events through the cnfasm command, where you can enable or disable each alarm. For power supply failure/removal events, you can also specify the alarm class (that is, Major vs. Minor).
In Release 9.2, a robust alarm is generated by the IGX platform when a DC voltage out-of-range condition occurs.
A robust alarm is generated by all switch platforms (IGX, BPX) when an Alarm Indicator Signal (AIS) condition is detected on a PVC. The alarm now has an NNI Status field that previously appeared in the Connection NNI Alarm message.
A robust alarm is generated by all switch platforms (IGX, BPX) when a bus failure or failure cleared event occurs. (In releases previous to Release 9.2, such events are currently reported through maintenance log messages.)
A robust alarm is generated by all switch platforms when an external clock source failure or failure cleared event occurs.
A robust alarm is generated by all switch platforms when the number of successive invalid login attempts on a user port exceeds the current threshold setting on the switch. You set the threshold by using the cnfsysparm command.)
A robust alarm is generated by all switch platforms when the processor card CPU utilization of the IDLE process falls below a fixed threshold. The purpose of the alarm is to indicate the possible degradation of service caused by processor load reaching an abnormally high level.
Configure ASM (Alarm and Status Monitor) card
cnfasm
dspasm
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnfasm
Configure parameters for the ASM card.
D1.jea TRM SuperUser BPX 8600 9.2 Aug. 30 1998 12:25 GMT
[1] Cabinet temp threshold: 50 C [4] Polling interval (msec): 10000
[2] Power A deviation: 6 V [5] Fan threshold (RPM): 2000
[3] Power B deviation: 6 V
ALM ALM
[6] ACO button - [14] BPX card slot -
[7] History button - [15] PSU A failure Y
[8] Cabinet temp Y [16] PSU A removed Y
[9] Power A volt Y [17] PSU B failure Y
[10] Power B volt Y [18] PSU B removed Y
[11] Fan 1 RPM Y
[12] Fan 2 RPM Y
[13] Fan 3 RPM Y
This Command: cnfasm
Which parameter do you wish to change:
Sets the date and time for the entire network. The node broadcasts the specified date and time to every node in the network. The time displayed at each node is consistent with the time zone where the node resides. (See the cnftmzn description.) For the first-time configuration of the date and time in a network, cnfdate requires all the parameters except for second. The default for second is 0. If a date and time already exist in the network, the defaults are the existing values at the moment you enter the cnfdate command. Note that changes to date and time alter the timestamps on WAN Manager statistics.
Configure data and time
cnfdate <year> <month> <day> <hour> <minute> [second]
cnftime, cnftmzn
Privilege | 1 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnfdate 1997 12 16 13 54 11
Set the time to 1:54:11 in the afternoon, December 16 1997. The system prompts:
"Warning: Changing time of day affects StrataView statistics timestamps
Continue?"
Enter "y" to continue or "n" to abort." Upon a "y" response, the system further prompts with: "Hit RETURN to change clock, DEL to abort."
alpha TRM YourID:1 IGX 8420 9.2 Dec. 16 1998 13:54 PST
YourID 1
Sarah 5
Last Command: cnfdate 1997 12 16 13 54 11
Warning: Changing time of day affects StrataView statistics timestamps
Continue?
| Parameter | Description |
|---|---|
year | Specifies the year. |
month | Specifies the month. The range is 1-12. |
day | Specifies the day. The range depends on the month and can be 1-31. |
hour | Specifies the hours. The range is 0-23. For example, enter 6 AM as 6 and 6 PM as 18. |
minute | Specifies the minute of the hour. The range is 0-59. The default is 0. |
| Parameter | Description |
|---|---|
second | Specifies the seconds. The range is 0-59. The default is 0. |
Enables or disables a specified node function. Each function has an index number. By entering the command, the index parameter, and the letter "e" or "d," the function is either enabled or disabled.
When IMA trunks exist in a Release 9.1 network, and you are upgrading from Release 9.1 to 9.2, ensure that the following steps have been performed:
You are now ready to upgrade the switch software from Release 9.1 to 9.2.
Configure system functions
cnffunc <function_index> <e/d>
none
Privilege | 1-2 |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnffunc 7 e
Enables automatic card testing after a card failure has been detected.
sw199 TN StrataCom IGX 8420 9.2 Apr. 9 1998 18:14 GMT
Index Status Function
1 Enabled Automatic CLN/PLN Loopback Test on Local/Remote Alarms
2 Enabled FDP Loopback button
3 Enabled User Command Logging
4 Enabled Automatic Card Reset on Hardware Error
5 Enabled TXR Model D Download
6 Enabled Card Error Record Wraparound
7 Disabled Card Test After Failure
8 Disabled Download From Remote StrataView
9 Disabled Logging of conn events in local event log
10 Disabled Logging of conn events in SV+ event log
11 Disabled Logging SVC Connection Events
12 Disabled Force Download From a Specific IP address
13 Disabled CDP WinkStart Signalling
This Command: cnffunc
Continue? y
Index Status Function
14 Enabled Logging of Bus Diagnostic Events in local event log
This Command: cnffunc
Enter index:
| Index | Function | Description | Default |
|---|---|---|---|
1 | Automatic CLN/TRK Loopback Test on Local/Remote Alarms | A remote-end loopback is automatically set up on a failed line or trunk. Used to check the integrity of the back card alarm circuitry. | enabled |
2 | FDP Loopback button | For an IGX node, enables loopback button on SDP or HDM card faceplate. (Disable it to prevent accidental operation by contact.) | enabled |
3 | User Command Logging | All commands entered by the user is entered in the system log when enabled. When disabled, system log does not become so large but there is no audit trail of operator commands kept. | enabled |
4 | Automatic Card Reset on | The controller card (BCC, NPC, or NPM) issues a hardware reset to a card when firmware detects an error during normal operation. This allows the node to return a card to service after a firmware error. | enabled |
5 | TXR Model D Download | (Not used) | enabled |
6 | Card Error Record | Allows the log entry for each card error to wrap for long entries. When disabled, only first ten failures are logged. | enabled |
7 | Card Test After Failure | Indicates card function selftests and background test should continue to be executed after a card has been declared as failing these tests. | disabled |
8 | Download from Remote | Allows a node to download software images from a WAN Manager not directly connected to the node. | disabled |
9 | Logging of connection events in local event log | All connection event messages are entered in the system log when enabled. When disabled, system log does not become so large but there is no audit trail of connection events kept | disabled |
10 | Logging of connection events in WAN Manager event log | All connection event messages are entered in the WAN Manager event log when enabled. When disabled, WAN Manager event log does not become so large but there is no audit trail of connection events kept | disabled |
11 | Force Download From a Specific IP address | Forces the node to only download software images from a WAN Manager with the specified IP address. | disabled |
12 | Logging of SVC connection events | All SVC connection event messages are entered in the local event log when enabled. When disabled, local event log does not become so large but there is no audit trail of SVC connection events kept | disabled |
13 | CDP WinkStart Signalling | Toggles WinkStart signaling on the CDP. | disabled |
14 | Logging of Bus Diagnostic Events in local event log | All Bus Diagnostic event messages are entered in the local event log when enabled. When disabled, local event log does not become so large but there is no audit trail of Bus Diagnostic events kept | enabled |
15 | Automatic Card Reset after Burnfw for CBI Cards | While the network is running Release 9.1, use the cnffunc command option 15 to disable the Automatic Card Reset after Burnfw for CBI cards option. (By default, this option is enabled.) You need to perform this step so that you can burn the UXM firmware revision on the flash and delay execution of the new firmware revision until the card is reset with the resetcd command. After the UXM at both ends of the trunk are burned with the new firmware revision, you can reset the UXM cards at the same time so that the new ATM Forum Compliant protocol is invoked at both ends of the trunk at the same time. It is important that you perform this step, because a node potentially may be not be reached if this is an IMA trunk, and it is the only trunk connected to that remote node. Also note that if an IMA trunk is not used within the Release 9.1 network, then you do not need to perform this step. Then upgrade all UXM cards in the Release 9.1 network with UXM firmware model B. | Enabled/ |
Specifies the name by which a node is known within the network. It may be changed at any time. The new node name is automatically distributed to the other nodes in the network. Node names are case sensitive. For example, an upper-case "A" is not considered to be the same as a lower-case "a". Duplicate names are not allowed in the same network. Node names may be configured from within a job sequence. If the node name is changed and the corresponding name in the job is not changed, the job will not function properly. In the following situations, the cnfname command cannot be executed:
Configure node name
cnfname <nodename>
cnfterm, cnfprt, and window
Privilege | 1 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnfname alpha
The name changes to "alpha." The network topology screen displays indicating the new name. See the dspnw description for more information on the network topology screen.
alpha TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 12:02 PST
NodeName Alarm Packet Line Packet Line Packet Line
alpha 10- 7/beta 14- 13/beta
beta MAJOR 7- 10/alpha 9- 10/gamma 13- 14/alpha
15- 15/gamma 20- 11/gamma
gamma MAJOR 10- 9/beta 11- 20/beta 15- 15/beta
Last Command: cnfname alpha
Next Command:
Configures the printing function. To obtain local or remote printing at a node, a printer must connect to the AUX PORT. Also, the configuration must include the correct baud rate and printer type for the port. Use the cnfterm and cnftermfunc commands to do this.
The cnfprt and cnftermfunc commands interact. If the auxiliary port on the node is configured for either an External Device Window or the Network Management Log, a "local" printing configuration automatically changes to "no printing." Printing is not possible because the auxiliary port is being used for another purpose.
Establishing a virtual terminal connection with a node does not affect the printing location established for the node that initiates the virtual terminal connection. For example, if node alpha is configured so that all alpha information goes to a printer at node beta and if alpha establishes a virtual terminal connection with node gamma, the results of print commands entered on the alpha keyboard still print at beta. Furthermore, this occurs regardless of the printing location configured for node gamma.
Configure printing functions
cnfprt <mode> <remote node name>
cnfterm, dsptermfunc
Privilege | 1-6 |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnfprt
Change the configured printing.
alpha TRM YourID:1 IGX 8410 9.2 Aug. 15 1998 13:17 PST
Printing Mode
Remote Printing at beta
Local Printing
No Printing
This Command: cnfprt
Select Local (l), Remote (r), or None (n):
| Parameter | Description |
|---|---|
mode | Specifies the printing mode. Enter "L" for local printing, "R" for remote printing, and 'n' for no printing. |
remote node name | Specifies the remote node whose printer is used for print commands issued by a user who is physically logged on to this node. This option is valid only when remote printing has been selected. A remote node is one within the domain, but not the node where the command is entered. |
Configures data transmission parameters for the control and auxiliary ports. The IGX and BPX nodes support two EIA/TIA-232 serial ports on the upper bus expansion card. The top port is called the Control Terminal port. The lower port is called the Auxiliary Port (AUX). Parameters can vary with the equipment connected to the port. The control port may connect to a control terminal, a direct-dial modem, or an external EIA/TIA-232 device. The auxiliary port may connect to either a printer or an external EIA/TIA-232 device. After you have set the data transmission parameters for a port, use the superuser command cnftermfunc to specify the equipment attached to the port. The configuration parameters must match the equipment physically attached to the port.
Configure terminal port
cnfterm <a/c> <baud> <parity> <num_data_bits> <num_stop_bits>
cnfterm, cnfprt, window
Privilege | 1-6 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnfterm
Configure an auxiliary control port.
alpha TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 11:58 PST
Control port Auxiliary port
Baud Rate: 1200 Baud Rate: 9600
Parity: None Parity: None
Number of Data Bits: 8 Number of Data Bits: 8
Number of Stop Bits: 1 Number of Stop Bits: 1
Output flow control: XON/XOFF Output flow control: XON/XOFF
Input flow control: XON/XOFF Input flow control: XON/XOFF
Use DTR signal: Yes DTR signal: Yes
This Command: cnfterm
Select Control port (c) or Auxiliary port (a):
| Parameter | Description |
|---|---|
a/c | Specifies the port to be configured, where "a" means auxiliary port, and "c" means control port. |
baud rate | Specifies the baud rate. The rates are 1200, 2400, 4800, 9600, and 19200 bps. |
parity | Specifies parity checking for character transmission to and from the port. Valid parity choices are "E" for even parity, "O" for odd parity, and "N" for no parity. |
data bits | Specifies the number of bits to be sent for each transmitted character and the number of bits to be expected for each received character. A "7" indicates 7 bits for each character. An "8" indicates 8 bits for each character. |
stop bits | Specifies the number of stop bits to be sent with each transmitted character and the number of stop bits to be expected with each received character. A "1" indicates one stop bit with each character; a "2" indicates two stop bits with each character. |
output flow control | Specifies the output flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control. |
input flow control | Specifies input flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control. |
cts flow control | Configures cts flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control. This parameter should be turned off if working with modems on a BPX node. |
use DTR | Specifies whether the node requires DTR to be asserted to allow or maintain a Login. A "Y" causes the node to require the presence of DTR before allowing a login. A "N" causes the node to ignore DTR. |
Sets the time for the entire network. The time is broadcast to all nodes in the network. The time displayed at each node is adjusted for the node's time zone. (See the cnftmzn command for more information.) This command can only be executed if the date for the network has already been configured using the cnfdate command. If hour, minute, or second is not entered, the current value is kept.
Configure time
cnftime <hour> <minute> <second>
cnfdate, cnftmz
Privilege | 1 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnftime 19 31 00
Configure time to 7:31 in the evening. The system displays two warning prompts before it changes the time.
pubsigx1 TN SuperUser IGX 8430 9.2 Sep. 5 1998 19:31 GMT
This Command: cnftime 19 31 00
Warning: Changing time of day affects StrataView statistics timestamps
Hit RETURN to change clock, DEL to abort
| Parameter | Description |
|---|---|
hour | Sets the time for the entire network. The time is broadcast to all nodes in the network. The time displayed at each node is adjusted for the node's time zone. |
min | Specifies the current minute. The range is 0-59. |
sec | Specifies the current second. The range is 0-59. |
Configures the time zone for the node. Configuring the time zone for a node ensures that the node's time is correct for the local area regardless of the node at which the network date and time are set. Once configured, the time zone for the node is saved in battery-backed memory. After a power failure, a node's date and time are restored if at least one other node in the network has the current time and date.
Configure time zone
cnftmzn <timezone | g+/- hours>
cnfdate
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
cnftmzn pst
Configures the time zone to Pacific Standard Time.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 13:19 PST
Last Command: cnftmzn pst
Next Command:
| Parameter | Description |
|---|---|
time zone |
|
hours from Greenwich | Specifies the difference in hours between local time and Greenwich Mean Time. The range is from -12 to +12 hours. Instead of entering the time zone, you can enter the hours from Greenwich Mean Time. For example, instead of entering pdt for Pacific Daylight Time, you could enter g-7, which is Greenwich Mean Time minus 7 hours. |
Disables the ARC (IPX) or ARM (IGX) alarm indicators and ARI external alarms. See the addalmslot description for more information on ARC/ARM alarm relays and adding alarm slots.
Upon receiving the command, the system places the alarm card set in the standby state and displays the current alarm status.
Delete an alarm slot
delalm <slot number>
addalmslot, dspalms
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IGX |
Lock | Yes |
delalmslot 11
Disable the alarm indicators on the ARM card set in slot 11. (The system subsequently displays alarm status.)
pubsigx1 TN SuperUser IGX 8430 9.2 July 16 1998 02:09 GMT
Alarm summary (Configured alarm slots: None)
Connections Failed: None
Groups Failed: None
TRK Alarms: None
Line Alarms: None
Cards Failed: None
Missing Cards: None
Remote Node Alarms: 1 Minor
Remote Domain Alarms: None
Routing Network Alarms: None
Cabinet Fan(s) Failed
FastPAD Node Alarms: None
Last Command: delalmslot 11
Next Command:
| Parameter | Description | |
|---|---|---|
slot number | Specifies the slot number of the alarm card set to activate. |
|
The delcdred command disables card redundancy for the card set in the specified primary slot number. If the secondary card slot is being used as the active slot at the time you use the delcdred command, the system attempts to switch back to the primary slot. The substitution takes place only if the primary slot has a complete set of cards and the cards are in a Standby or a Standby-F state (not if they are Failed). See the dspcds description for information on card states.
When you issue the delcdred command, it always completes. If the primary card is incomplete, control will still be given to the primary card.
Because YRED (Y redundancy) could be considered a misnomer for the SONET APS two-slot case, the following new commands are new in Release 9.2 to support card redundancy:
See the addcdred and dspcdred commands for more information on card and line redundancy for SONET APS (Automatic Protection Switching) 1+1.
Delete redundant card
delcdred <primary slot>
addcdred, dspcdred, switchcdred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | BPX |
Lock | Yes |
delcdred 2
Delete card redundancy for slot 2.
Deletes an interface shelf from a tiered network. The identifier for an interface shelf is either the trunk number or the name of the shelf. Normally, you do not execute delshelf only at the BPX core switch shelf, but on the IGX/AF itself. The command delshelf has the single function of letting you turn off LMI if the trunk is not allowing communication. In contrast to the deltrk command, you can execute delshelf at any time if no connections terminate at the trunk.
In Release 9.2, when you use delshelf to remove an MGX 8850 interface shelf trunk from a BPX routing hub, or an SES interface shelf (or feeder) trunk from an IGX 8400 routing node, the Annex G signalling channel and IP relay programming for the MGX 8850 or SES interface shelf is removed.
Delete an interface shelf.
delshelf <trunk> | <shelf-name>
addshelf, dspnode
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
delshelf 4.1
Delete shelf trunk 4.1 on a BPX.
nmsbpx23 TN SuperUser BPX 8600 9.2 Aug. 16 1998 13:26 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
1.3 AXIS240 AXIS OK
11.2 A242 AXIS OK
Last Command: delshelf A241
Shelf has been deleted
Next Command:
| Parameter | Description |
|---|---|
trunk or shelf name | Specifies the slot and port number of the trunk or the name of the interface shelf. |
This command disables Y redundancy for the card set in the specified primary slot number. If the secondary card slot is being used as the active slot at the time you use the delyred command, the system attempts to switch back to the primary slot. The substitution takes place only if the primary slot has a complete set of cards and the cards are in a Standby or a Standby-F state (not if they are Failed). See the dspcds description for information on card states. See the addyred and dspyred commands for more information on Y-cable redundancy.
When you issue the delyred command, it always completes. If the primary card is incomplete, control will still be given to the primary card.
Delete Y-cable redundancy
delyred <primary slot>
addyred, dspyred, prtyred
Privilege | 1-4 |
Jobs | No |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
delyred 16
Disable Y-cable redundancy at slot 16.
Displays BPX node alarms that, when active, produce an external alarm output (relay closure). These alarms are associated with powering and cooling the node as well as a statistics count. For example, a minor alarm is generated when a fan speed drops below 2000 rpm. Since the single ASM card is always located in slot 15, you do not need to enter a card slot for this command. To configure the ASM alarms, use cnfasm (a superuser command).
Display ASM card
dspasm
cnfasm
Privilege | 1 |
Jobs | No |
Log | No |
Node | BPX |
Lock | Yes |
dspasm
Display the ASM card parameters.
D1.jea TRM SuperUser BPX 8620 9.2 Aug. 30 1998 12:24 GMT
ASM Status: Active ASM Alarms
Statistics count: 7 Fan #1 RPM out of range
Statistics timeouts: 0 Fan #2 RPM out of range
Cabinet temperature: 21 C Fan #3 RPM out of range
Power voltage A/B: 0.0 / 0.0 V
PSU Ins Type Rev SerNum Failure
A N N/A N/A N/A N/A
B N N/A N/A N/A N/A
FAN 1 2 3
0000 0000 0000 RPM
Last Command: dspasm
Next Command:
Displays the status, revision, and serial number of a card. If a back card is present, its type, revision, and serial number appear. The displayed information can vary with different card types.
The dspcd screen indicates whether the card supports IMA Compliance. If the card does not support IMA compliance, then the screen will not display any IMA support.
The dspcd command displays the SONET APS (Automatic Protection Switching) architecture supported on the card, slot # of redundant back card (if there is a redundant back card), and the reasons for the card's APS mismatch.
In this release, the dspcd screen indicates whether the front card supports the Lead State Trap for High/Low Speed Data Modules (HDM/LDM) on IGX.
If SONET APS is configured (which allows switching of SONET lines from the active line to a standby line to provide hardware line redundancy), the dspcd command displays the front and back card SONET APS attributes. For the front card, APS attributes are displayed if the front card supports one of the following:
For the back card, if the back card is a redundant back card, the slot number of the redundant backward is displayed. Also, the reasons for the card's APS mismatch are displayed also.
The dspcd command is a single-page display. (Note that the dsplogcd command shows all the ports and trunks on a given slot. The second page of the dsplogcd command shows each port and interface type corresponding to that slot.port.)
In support of feature mismatch checking in Release 9.2, the dspcd command provides mismatch information for the specified card.
Display card
dspcd <slot number>
dncd, dspcds, resetcd, upcd
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IGX, BPX |
Lock | No |
dspcd 6
The card is the trunk version of the ALM. The "B" next to Revision shows the card set is an ALM/B.
IGX8430 TN SuperUser IGX 8430 9.2 Oct. 12 1998 18:44 PST
Detailed Card Display for ALM in slot 6
Status: Active
Revision: B0310
Serial Number: 289417
Backplane Installed
Backcard Installed
Type: UAI-T3
Revision: HN
Serial Number: 242007
Last Command: dspcd 6
Next Command:
dspcd 5
Display information on the card in slot 5. The card is a UVM capable of CAS-switching.
wx175 TN SuperUser IGX 8420 9.2 Sep. 23 1998 22:31 PST
Detailed Card Display for UVM in slot 5
Status: Standby (Front Card Supports CAS-switching)
Revision: B0203
Serial Number: 336878
Integrated Echo Canceller
Channels: 31
Backplane Installed
Backcard Installed
Type: E1-2
Revision: AB
Serial Number: 336728
Last Command: dspcd 5
Next Command:
dspcd 7
Display information on the card in slot 7. The card is a UXM with an OC-3 back card.
sw224 TN SuperUser IGX 8430 9.2 Aug. 27 1998 16:01 GMT
Detailed Card Display for UXM in slot 7
Status: Standby
Revision: EXB
Serial Number: 190212
Backplane Installed
Backcard Installed
Type: OC-3
Revision: AH
Serial Number: 12345
Ports: 4
Line Mode: SMF
Last Command: dspcd 7
Next Cand:
dspcd 5
Display information on the card in slot 5. The card is a UXM with an E1 back card.
sw224 TN SuperUser IGX 16 9.0.n2 Aug. 27 1997 16:07 GMT
Detailed Card Display for UXM in slot 5
Status: Active (Front Card Supports SIW)
Revision: AAB (Front Card Supports Cell Forwarding)
Serial Number: 190208 (Front Card with GW installed)
Backplane Installed
Backcard Installed
Type: E1-IMA
Revision: EW
Serial Number: 23456
Ports: 8
Line Mode:
Last Command: dspcd 5
Next Command:
dspcd 5
Display information on the card in slot 11. The card is a 2-port BME card with an OC-12 back card.
sw60 TN SuperUser BPX 15 9.2 Feb. 5 1997 11:37 GMT
Status: Active
Revision: K0811
Serial Number: 324027
Queue Size: 228300
Support: 8129 Chns
2 Pts, OC-12
Backcard Installed
Type: LM-BXM
Revision: P02
Serial Number: 240255
Supports: 2 Pts, OC-12, SMF Md
Last Command: dspcd 11
dspcd 5
Display information on the card in slot 11. The card is a 2-port BME card with an OC-12 back card. Note that the second page of dspcd display shows each port and interface type corresponding to that card slot.
sw98 TN SuperUser BPX 8600 9.2.r3 Feb. 5 1998 11:37 GMT
Status: Active
Revision: CW07
Serial Number: abcdef
Fab Number: ----
Queue Size: 131000
Support: FST, 16256 Chns, 4 Ports OC-3
Backcard Installed
Type: LM-BXM
Revision: BA
Serial Number: 686687
Supports: 4 Pts, OC-3
Last Command: dspcd 11
sw98 TN SuperUser BPX 15 9.2.r3 Feb. 5 1998 11:37 GMT
Interface Details for BXM-OC-3 in slot 11
3.1: VSI only Trunk - (256 user chans)
3.2: Autoroute/VSI Trunk (512 user chans)
3.3: ATM Port (UNI/NNI) (2048 user chans)
3.4: Virtual Trunks (1..N)
Last Command: dspcd 11
dspcd 5
Display card for BXM-T3 in slot 5, which shows that VSI version 2 (VSI V2) is supported on the card.
sw58 TN StrataCom BPX 8600 9.2.00 June 25 1998 13:40 GMT
Detailed Card Display for BXM-T3 in slot 5
Status: Standby
Revision: ED04
Serial Number: 693903
Fab Number: 28-2218-02
Queue Size: 131000
Support: FST, 8 Pts,T3,VcS, VSI V2
Chnls:16320
PG[1]:1,2,3,4,5,6,7,8,
Backcard Installed
Type: LM-BXM
Revision: BA
Serial Number: 692993
Supports: 12 Pts, T3/E3
Last Command: dspcd 5
dspcd 4
Enter the dspcd command on card slot 4 (for example, to check the port group maximum that can be entered for the maxvsilcn parameter of the cnfrsrc command when configuring VSI resources). In this example, the maximum value for a port group is 7048.
n4 TN SuperUser BPX 8620 9.2 Apr. 4 1998 16:40 PST
Detailed Card Display for BXM-155 in slot 4
Status: Active
Revision: CD18
Serial Number: 693313
Fab Number: 28-2158-02
Queue Size: 228300
Support: FST, 4 Pts,OC-3,Vc
Chnls:16320,PG[1]:7048,PG[2]:7048
PG[1]:1,2,
PG[2]:3,4,
Backcard Installed
Type: LM-BXM
Revision: BA
Serial Number: 688284
Supports: 8 Pts, OC-3, MMF Md
Last Command: dspcd 4
Next Command:
dspcd 4
Enter the dspcd command on card slot 4 to show support for Partial Packet Discard (PPD) due to policing on the ingress direction. Only BXM cards with the RCMP (Routing Control Monitoring and Policing) chip support PPD on policing.
bpx04 TN StrataCom BPX 8620 9.2.30 Apr. 8 1999 12:00 GMT
Detailed Card Display for BXM-155 in slot 4
Status: Active
Revision: DD14 Backcard Installed
Serial Number: 772850 Type: LM-BXM
Fab Number: 28-2158-02 Revision: BB
Queue Size: 228300 Serial Number: 649646
Support: 4 Pts, OC-3, FST, VcShpSupp: 4 Pts,OC-3,SMF,RedSlot:NO
Support: VT, ChStLv 1, VSIlvl 2
Support: APS(FW)
Support: LMIver 1, ILMIver 1
Support: OAMLp, TrfcGen
Support: PPDPolic
#Ch:16320,PG[1]:8160,PG[2]:8160
PG[1]:1,2,
PG[2]:3,4,
#Sched_Ch:16384
Last Command: dspcd 12
Next Command:
Displays information for Y-cable pairings. A single slot can be specified, or all pairings are displayed when no slot is specified. Slot numbers appearing in high intensity indicate active card status. Front card, back card, and channel configuration conflicts appear in reverse video. A conflict occurs when the port interfaces are different for corresponding ports in a redundant slot pair. The output display contains the following information:
Remaining columns (Channel Configuration) describe the channel configurations when appropriate.
Display redundant cards.
dspcdred [slot]
addyred, delyred, prtyred
Privilege | 1-4 |
Jobs | No |
Log | No |
Node | BPX |
Lock | No |
dspyred
Display card redundancy for cards in slots 2 and 3.
beta TRM YourID:1 BPX 8620 9.2 Aug. 15 1997 14:27 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM
Last Command: dspcdred 2 3
Next Command:
Displays the cards in a shelf, front and back, with their type, revision, and status. For front and back card sets, the status field applies to the cards as a set. A letter "T" opposite a card indicates that it is running self-test. A letter "T" opposite a card indicates that it has failed a test. If lines or connections have been configured for a slot, but no suitable card is present, the display will list the missing cards at the top of the screen. If a special backplane is installed or if a card was previously installed, empty slots are identified as "reserved."
For a two-shelf node, the screen initially displays only the upper shelf with a "Continue?" prompt. Typing "y" to the prompt displays the cards in the lower shelf. The command dspcds followed by the letter "L" (for lower shelf) displays card status for just the lower shelf. For an IGX 8410 node, the card information appears in only the left column. The status and update messages are as follows:
♦ Active | Card in use, no failures detected. |
♦ Active—F | Card in use, failure(s) detected. |
♦ Active—T | Card active, background test in progress. |
♦ Active—F-T | Card active, minor failures detected, background test in progress. |
♦ Standby | Card idle, no failures. |
♦ Standby—F | Card idle, failure(s) detected. |
♦ Standby—T | Card idle, background test in progress. |
♦ Standby—F-T | Card idle, failure(s) detected, background test in progress. |
♦ Failed | Card failed. |
♦ Down | Card downed by user. |
♦ Down—F | Card downed, failure(s) detected. |
♦ Down—T | Card downed, failure(s) detected, background test in progress. |
♦ Mismatch | Mismatch between front card and back card. |
♦ Update * | Configuration RAM being updated from active control card. |
♦ Locked* | Old software version is being maintained in case it is needed. |
♦ Dnlding* | Downloading new system software from the active PCC adjacent node of from WAN Manager. |
♦ Dnldr* | Looking to adjacent nodes or WAN Manager for either software to load or other software needs you have not specifically requested. |
♦ Program | Occurs when new firmware is being burned on the card. |
In the preceding messages, an asterisk (*) means an additional status designation for BCC, NPC, or NPM cards. "F" flag in the card status indicates that a non-terminal failure was detected. Cards with an "F" status are activated only when necessary (for example, when no other card of that type is available). Cards with a "Failed" status are never activated.
The "reserved for" logic in Release 9.2 reserves the slot for a BXM if SONET APS (Automatic Protection Switching) has been configured on the slot.
To support the Hitless Rebuild feature in Release 9.2, after a switchover has occurred and the standby updates are about to begin, the dspcds command will show the standby processor card as missing temporarily. This is a result of the delay in performing the full rebuild on the standby processor, which is necessary as part of the hitless rebuild sequence.
Following any processor card switchover, the new standby will rebuild, preserving the critical databases needed for a hitless rebuild. When database updates can start, the standby will rebuild again doing a normal standby rebuild. If there is a failure on the new active card that causes it to switch back before updates can start, the card taking over will do a hitless rebuild. Under most conditions, the second switchover will not be necessary, and a full rebuild will be done on the standby processor. As this process begins, the standby card will briefly appear to be missing.
In support of the Hitless Rebuild feature, there is no change directly to the user command dspcds. However, after a switchover has occurred and the standby updates are about to begin, the dspcds command will show the standby processor card as missing temporarily. This is a result of the delay in performing the full rebuild on the standby processor, which is necessary as part of the hitless rebuild sequence.
Following any processor card switchover, the new standby will rebuild preserving the critical databases needed for a hitless rebuild. When database updates can start, the standby will rebuild again doing a normal standby rebuild. If there is a failure on the new active card that causes it to switch back before updates can start, the card taking over will do a hitless rebuild. Under most conditions, the second switchover will not be necessary, and a full rebuild will be done on the standby processor. As this process begins, the standby will briefly appear to be missing.
Display cards
dspcds [l]
dncd, dspcd, resetcd, upcd
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IGX, BPX |
Lock | No |
dspcds
Display status on all cards.
IGX8430 TN SuperUser IGX 8430 9.2 Oct. 12 1998 18:39 PST
FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPM A0205 Active-T 9 Empty universal backplane
2 Empty reserved for NPM 10 Empty universal backplane
3 FRM ESP FRI-T1 AC Active 11 ALM B0305UAI-T3 HN Active
4 Empty universal backplane 12 Empty
5 UXM AA09 E1-IMA EW Active 13 FRM EEV FRI-T1 AL Standby
6 ALM B0310UAI-T3 HN Active 14 BTM BFF BTM-T3 P02 Standby
7 UXM EX09 OC-3 AH Standby 15 NTM FHE T1 AL Standby
8 Empty universal backplane 16 CVM AFF T1 AK Active
Last Command: dspcds
Next Command:
dspcds l
Display status of cards on the lower shelf of an IPX 32 node (the option "l" means "lower").
beta TRM YourID:1 IPX 8430 9.2 Aug. 15 1998 14:37 MST
Missing Cards: 1 ATM, 1 T3
Front Card Back Card Front Card Back Card
Type Rev Type Rev Status Type Rev Type Rev Status
17 PCC HDB Standby 25 SDP BA RS232 AK Active-T
18 Empty 26 SDP BF RS232 AK Standby-F
19 FRP DFB FRI-V35 BC Active-F 27 Empty
20 ATM HM03 Empty Failed 28 Empty
21 Empty 29 Empty
22 CDP AAB Empty Unavail 30 Empty
23 Empty 31 Empty
24 Empty reserved for SDP 32 Empty
Last Command: dspcds l
Next Command:
dspcds
Display status of cards on a BPX 16 node. The 2 port BME card with OC-12 interface is in slot 11.
sw60 TN SuperUser BPX 15 9.2 Feb. 5 1997 11:36 GMT
Missing Cards: 1 BCC
FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 BNI-T3 CCF T3-3 BE Active 9 BNI-155 BDK MMF-2 CM Standby
2 Empty 10 Empty
3 ASI-T3 BJF T3-2 AA Standby 11 BME-622 K08 11LM-BXM P02AB Active
4 ASI-E3 BMJ E3-2 BE Standby 12 ASI-155 BDK MMF-2 AB Standby
5 BNI-E3 CMF E3-3 EY Standby 13 Empty
6 Empty 14 Empty
7 BCC BWF LMBCC AC Active 15 ASM ACA LMASM AC Active
8 Empty reserved for Card
Last Command: dspcds
Next Command:
| Parameter | Description |
|---|---|
l | Directs the system to display status of the cards on just the lower shelf of an |
Use the dspctrlrs command to display the VSI controllers, such as an PNNI SES controller, on a BPX node. The dspctrlrs command lists the controller id, the partition the controller uses, the trunk/interface a controller is attached to, the controller type (always a VSI controller), the interface type (AAL5, VSI (Label Switching), or MGX 8220 (formerly called AXIS) interface shelf, and the name of the controller/entity that the controller exists on (that is, node name, equipment name).
Displays all the VSI controllers on a node, such as a BPX node. Possible VSI controllers added to a node might be a PNNI ESP (Extended Services Processor) controller. (Note that you use addshelf and delshelf to add and delete a VSI controller such as a Label Switch Controller to a BPX node.)
You can also the dspnode command to display the VSI controllers on a BPX node.
Displays all VSI controllers, for example, such as PNNI SES, on a BPX node.
dspctrlrs <slot.port><controller name string><partition_id><controller_id>
addctrlr, cnfctrlr, delctrlr, dspnode
Privilege | 1 |
Jobs | Yes |
Log | Yes |
Node | BPX |
Lock | Yes |
dspctrlrs
Display VSI controllers on BPX node sw237.
sw237 TN StrataCom BPX 8620 9.2.a3 June 16 1999 05:04 PST
BPX 8620 VSI controller information
Ctrl Id Part Id Ctrl VC Trunk Ctrlr Type Intfc Type Name
VPI VCIRange
1 1 1 20 - 34 4.1 VSI VSI VSI
2 1 0 40 - 54 13.2 VSI AXIS SIMFDR0
Last Command: dspctrlrs
Displays the addresses and configuration for the LAN Ethernet. The configuration fields shows the type of network capability and it is ready or unavailable. The dsplancnf display contains the following address fields:
<IPAdd> | Specifies the Internet address of the node used in the TCP/IP protocol. |
<IP subnet mask> | Specifies a 32-bit mask that contains information about the bit lengths of the subnet ID and host ID address fields. The format of this field uses 1s for the subnet ID field and 0s for the host ID address field as defined in the TCP/IP protocol. The default value (in decimal notation) is 255 255 255.0. This mask denotes both subnet ID and host ID fields as 8-bit fields. |
<Max. LAN Transmit Unit> | BPX only: typical amount is 1500 bytes. |
<TCPServicePort> | Specifies the node's service point used by the transmission control protocol (TCP). |
<GatewayIPAddr> | Specifies the Internet gateway address |
Type | List of socket types (for example, TCP, UDP, and SNMP) that are open (in READY state) for communication between the node and the LAN. In the system response shown, the TCP socket is no longer used by switch software, indicated by the UNAVAIL state. The TimeHndlr (or Daytime) socket is related to TFTP. It lets an external node retrieve the day and time from the switch. The Tunneling socket is used for communication between a BPX and an INS (Intelligent Network Server). |
State | State of communication socket between the node and the LAN. READY indicates that the socket is open for communication between the node and the LAN. UNAVAIL indicates that the socket is not available for communication between the node and the LAN. |
Display LAN interface configuration
dsplancnf
cnflan (a superuser command)
Privilege | 1-5 |
Jobs | No |
Log | No |
Node | IGX, BPX |
Lock | No |
dsplancnf
Display the LAN configuration for the current node.
pubsbpx1 TN SuperUser BPX 8620 9.2 June 11 1998 13:23 GMT
Active IP Address: 204.179.31.104
IP Subnet Mask: 255.255.255.0
IP Service Port: 5120
Default Gateway IP Address: None
Maximum LAN Transmit Unit: 1500
Ethernet Address: 00.C0.43.00.21.F0
Type State Type State
LAN READY TUNL READY
TCP UNAVAIL
UDP READY
Telnet READY
TFTP READY
TimeHdlr READY
SNMP READY
Last Command: dsplancnf
Next Command:
Displays Annex G LMI statistics for the trunk that connects an IGX/AF interface shelf to the BPX core switch shelf. To execute this command from the access shelf itself, you must telnet to the IGX/AF. The dsplmistats command can provide information to help you analyze problems that may arise while you set up a tiered network.
Display Annex G LMI statistics
dsplmistats (parameters depend on the type of node)
none
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IGX/AF, BPX |
Lock | No |
dsplmistats
Display the LMI statistics for the trunk attached to the hub.
batman SuperUser IGX/AF 9.2 Nov. 30 1998 18:04 PST
Annex G LMI Statistics for slot:1 port:1
VPI.VCI: 0.0 Lmi enabled Lmi polling enabled
Invalid Pdu Rx: 0 Status Polling Timer (T396) : 10
Invalid Pdu Len Rx: 0 Status Enquiry Timer (T393) : 10
Unknown Pdu Type Rx: 0 Max Status Enquiry Retry (N394): 5
Unknown IE Type Rx: 0 Update Status Timer (T394) : 10
Bad Transaction Rx: 0 Max Update Status Retry (N395) : 5
Status Rx: 1384 Spc Polling Timer : 3
Status Enq Tx: 1384 Spc Retry Timer : 0
Status Enq Rx: 1384 Spc Retry Counter : 1
Status Tx: 1384 Node Status Retry Timer : 0
Status Ack Rx: 8 Node Status Retry Counter : 0
Update Status Tx: 8 Node Status Polling Timer : 2
Update Status Rx: 8
Status Ack Tx: 8
Last Command: dsplmistats
Next Command:
Displays the name, type, and alarm status of all nodes within the network of the node executing the command. The remote node alarm is provided. You can use the vt command to reach the remote node and obtain the alarm information.
If a node is in alarm, its name is highlighted and the alarm type (major/minor), is displayed. A major alarm will be a flashing word. A junction node is identified with "Yes" printed under the Jct column.
Display all nodes
dspnds [+n | -p | -d | domain]
dspnw
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | IGX, BPX |
Lock | No |
dspnds
Display the alarm status of all nodes within the network.
alpha TRM YourID:1 IGX 8420 9.2 Aug. 23 1998 09:42 PST
NodeName Alarm
alpha MAJOR
beta MAJOR
gamma MAJOR
Last Command: dspnds
Next Command:
| Parameter | Description |
|---|---|
+n | Specifies the node number. (Assigning a node number requires superuser privilege.) |
-p | Specifies that the display include the type of controller card in the node. The types are BCC, NPM, and so on. |
-d | Specifies that the display include the type of node for each named node. The type is either "IGX" or "BPX." |
Displays a summary of the interface shelves.
The dspnode command can isolate the shelf where an alarm has originated. For example, when you execute dspalms, the display indicates the number of shelves with alarms but does not identify the shelves. Therefore, execute dspnode on the IPX/BPX core switch shelf to determine which interface shelf generated the alarm.
The first example shows a screen display with dspnode executed on a BPX node. The second example shows a screen with dspnode executed on an IGX/AF. When executed on an IGX/AF, dspnode shows the name of the IGX/BPX core switch shelf and the trunk number. Note that to execute a command from an IGX/AF itself, you must either telnet to the shelf or use a control terminal attached to the shelf.
You can also use the dspnode command to display the VSI controllers on a BPX node. In this release, you can display the control_VPI and control_VCI_start of the particular controller, as shown in Example 6.
In Example 4, the dspnode screen shows loopbacks on feeders to a BPX node. The BPX no longer sends any status updates to the feeder yet it continues to acknowledge any feeder LMI messages received.
If the BPX cannot communicate LMI messages to its feeders, then the LMI status at the feeders must be maintained to keep the connections "active" to their external devices. If the BPX hub is flooded with network messages, then LMI/ILMI communication with its feeders may be interrupted. LMI normally runs a keep-alive between the hub and feeder. If the keep-alive fails, then the other end changes the status of all connections to "failed". If the outage is only due to a network message flood, then it is desirable to override this mechanism to keep the connection status as "active".
Display node
dspnode
addshelf, delshelf, dsptrks
Privilege | 1-6 |
Jobs | No |
Log | No |
Node | BPX, IGX, IGX/AF |
Lock | Yes |
dspnode
Display information about the interface shelves (executed on the IGX or BPX core switch shelf).
sw288 TN SuperUser BPX 8620 9.2.j2 Dec. 10 1998 15:09 GMT
BPX 8620 Interface Shelf Information
Trunk Name Type Part ID Ctrl ID Alarm
1.2 SW93AXIS AXIS UNRCH
1.3 SW77AXIS AXIS MAJ
3.1 sw92 TSC OK
5.8 SIMFDR0 AAL5 - - OK
Last Command: dspnode
Next Command:
dspnode
Display information about the interface shelves (feeders) attached to IGX core switch shelf (executed on an IGX 8420). In this case, an SES (Service Expansion Shelf) communicates with the IGX routing hub over the AAL5 protocol.
oo1 TN SuperUser IGX 8420 9.2.zR Dec. 10 1998 07:23 PDT
IGX Interface Shelf Information
Trunk Name Type Alarm
9.1 ases1 AAL5 OK
Last Command: dspnode
Next Command:
dspnode
Display information about the trunk to a BPX core switch shelf (executed on an BPX 8600).
BPX Interface Shelf Information
Trunk Name Type Part Id Ctrl Id Alarm
1.1 sww222 IGX/AF - - UNRCH
10.3 VSI VSI 1 1 OK
11.1 VSI VSI 1 2 OK
Last Command: dspnode
dspnode
Displays all interface shelves attached to the node. The resulting screens should show trunk 4.1 as type VSI.
n4 TN SuperUser BPX 8620 9.2 Apr. 4 1998 16:46 PST
BPX Interface Shelf Information
Trunk Name Type Alarm
3.1 j6c AXIS MIN
5.3 j5c IPX/AF MIN
4.1 VSI VSI OK
4.2 VSI VSI OK
4.3 VSI VSI OK
Last Command: dspnode
Next Command:
dspnode
Display information about the loopbacks on feeders to the BPX node.
sazu TN StrataCom BPX 8620 9.2 pr. 18 1998 11:11 GMT
BPX Interface Shelf Information
Trunk Name Type Alarm
10.2 sw157 IPX/AF MAJ (L)
Last Command: dspnode
Next Command:
Major Alarm
dspnode
Display information about the BPX 8620 interface shelf with this release enhancement that shows the controller's control_VPI and control_VCI_start.
------------------------------------------------------------------------
sw237 TN StrataCom BPX 8620 9.2.30 June 16 1999 05:06 PST
BPX 8620 Interface Shelf Information
Trunk Name Type Part Id Ctrl Id CntrlVC Alarm
VPI VCIRange
4.1 VSI VSI 1 1 1 20 - 34 OK
13.2 SIMFDR0 AXIS 1 2 0 40 - 54 OK
Last Command: dspnode
Displays the configuration for the control port and auxiliary port at a node. It includes all the asynchronous communications parameters that are specified by the cnfterm command.
Display terminal port configurations
dsptermcnf
cnfterm, cnftermfunc (a superuser command), dsptermfunc
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsptermcnf
Display the terminal port configuration data.
batman TN SuperUser BPX 8620 9.2 Aug. 26 1997 02:55 PST
Control port Auxiliary port
Baud Rate: 9600 Baud Rate: 9600
Parity: None Parity: None
Number of Data Bits: 8 Number of Data Bits: 8
Number of Stop Bits: 1 Number of Stop Bits: 1
Output flow control: XON/XOFF Output flow control: XON/XOFF
Input flow control: XON/XOFF Input flow control: XON/XOFF
CTS flow control: No CTS flow control: Yes
Use DTR signal: Yes Use DTR signal: Yes
Last Command: dsptermcnf
Next Command:
Displays the port functions configured by the cnftermfunc command.
Display terminal port functions
dsptermfunc
cnfterm, cnftermfunc, dsptermcnf
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsptermfunc
Display the terminal port configuration data. The highlighted or reverse video items are the currently selected options.
swstorm TN SuperUser BPX 8620 9.2 Aug. 23 1997 09:42 PST
Control port Auxiliary port
1. VT100/StrataView 1. Okidata 182 Printer
2. VT100 2. Okidata 182 Printer with LOG
3. VT100
4. Alarm Message Collector
5. External Device Window
6. Autodial Modem
Last Command: dsptermfunc
Next Command:
Displays printing configuration for the node. The three printing modes, 'remote', 'local' and 'no' are listed and the currently selected mode is highlighted. If remote printing is selected, the node name where the remote printer is located also appears. If the name of the node is flashing, the node is unreachable.
The dspprtcnf command displays the current print configuration for the network where the command is entered.
Remote mode indicates that the log for the node prints on the printer at the listed remote node. Local mode indicates that the log for the node prints on the node's printer. No printing mode indicates that the log for the node does not print.
Display print configuration
dspprtcnf
cnfprt
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dspprtcnf
Display the print configuration. The example does not show the highlighted field.
sw83 TN SuperUser IGX 8420 9.2 Aug. 22 1997 16:02 PST
Printing Mode
Remote Printing
Local Printing
No Printing
Last Command: dspprtcnf
Next Command:
Displays the current status of the power supply monitor, the current power supply configuration (which may consist of from one to four power supplies depending on node requirements), and the current cabinet temperature.
On the right side of the screen is displayed the internal cabinet temperature in degrees Centigrade and Fahrenheit. The temperature is displayed as a thermometer and the exact temperature appears at the top of the thermometer.
Display power supply status
dsppwr
dspcd, dspcds
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | IGX, BPX | No |
dsppwr
Display power supply status.
sw81 TN SuperUser BPX 8620 9.2 May 21 1997 13:13 PST
Power Status Cabinet Temperature
ASM Status: Active 22 71
Power voltage A/B: 0 / 49 V C 60 | | 140 F
e | | a
PSU Ins Type Rev SerNum Failure n 50 |--| 122 h
A N N/A N/A N/A N/A t | | r
B Y 240V 0C 29959 None i 40 | | 104 e
g | | n
Fan Status r 30 | | 86 h
a | | e
FAN 1 2 3 d 20 | | 68 i
3300 3360 3240 RPM e \Q--' t
Last Command: dsppwr
Next Command:
Displays information for Y-cable pairings. A single slot can be specified, or all pairings are displayed when no slot is specified. Slot numbers appearing in high intensity indicate active card status. Front card, back card, and channel configuration conflicts appear in reverse video. A conflict occurs when the port interfaces are different for corresponding ports in a redundant slot pair. The output display contains the following information:
Remaining columns (Channel Configuration) describe the channel configurations when appropriate.
Display Y-cable redundancy
dspyred [slot]
addyred, delyred, prtyred, switchyred
| Privilege | Jobs | Log | Node | Lock |
1-4 | No | No | IGX, BPX | No |
dspyred
Display Y-redundancy for all cards.
beta TRM YourID:1 IGX 8430 9.2 Aug. 15 1998 14:28 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
25 Pri 26 SDP RS232 DCE DCE DCE DCE
26 Sec 25 SDP RS232 DCE DCE DCE DCE
Last Command: dspyred
Next Command:
Prints the card redundancy configuration for a BXM card with an OC-3 or OC-3 interface. This command uses the same syntax and prints the same information as the dspyred command. See the dspcdred command for details on the format of the command output.
Print the card redundancy for all cards.
prtcdred <start slot>
addcdred, dspcdred, delcdred, prtcdred, switchcdred
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | Yes |
prtcdred
Print card redundancy for all cards (no starting slot entered).
beta TRM YourID:1 BPX 8620 9.2 Aug. 15 1997 14:27 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
2 Pri 3 BXM LM-BXM
3 Sec 2 BXM LM-BXM
Last Command: prtcdred 2
Next Command:
Prints the Y-cable redundancy configuration for an SDP, LDP, CDP, FRP, FTC, NTC or AIT card on an IPX node. On an IGX node, the cards are the HDM, LDM, CVM, FRM, FTM, NTM, BTM, ALM/B, UXM, UFM, and UVM. On a BPX node, the applicable cards are the BCC, ASI, and BNI. This command uses the same syntax and prints the same information as the dspyred command. See the dspyred command for details on the format of the command output.
Print the Y-cable redundancy
prtyred <start slot>
dspyred, addyred, delyred
| Privilege | Jobs | Log | Node | Lock |
1-6 | No | No | BPX | Yes |
prtyred
Print Y-redundancy for all cards (no starting slot entered).
beta TRM YourID:1 IGX 8420 9.2 Aug. 15 1998 14:28 MST
Slot Other Front Back Channel Configuration
Slot Type Slot Card Card 1 2 3 4 5 6 7 8
25 Pri 26 SDP RS232 DCE DCE DCE DCE
26 Sec 25 SDP RS232 DCE DCE DCE DCE
Last Command: prtyred
Next Command:
Switches active and redundant cards used for SONET APS (Automatic Protection Switching). The switchcdred command is the same as the switchyred command, and you can use it on any Y-cable redundancy card pair. You typically only would use the switchcdred command when you need to perform diagnostics or maintenance, and you need to remove and service the active card.
When there is a front card failure, front card downed, or the front card fails a self-test, the card switchover should happen automatically (that is, you should not need to execute the switchcdred command for the card switchover to happen.) An automatic switchover typically occurs when the switch software determines that the card is in a worse condition than the redundant pair (that is, a card is in a failed state due to a condition such as self-test, background test, fatal errors.) If a standby card is not available, the switchcdred command will not be executed.
Typically, when APS and card redundancy are implemented together, the term Y-redundancy actually refers to card redundancy because there is no Y cable connecting two backcards to one line. With SONET APS card redundancy, there is a primary and a secondary front card/back card pair. The redundant front card must be in Hot Standby state before a switchover can occur. When a front card failure is detected, the switchover should happen automatically (when card redundancy has been implemented). However, for the APS application, the active line is not switched if the line status is good. If the line has Loss of Signal (or other defects), it will be switched to the redundant line. (The line refers to the physical cable attached to the output of the back card.)
For APS 1+1, a front card can switch and become the standby card while its associated back card still has the active lines. The APS line will not switch during a card redundancy switch, unless the APS firmware detects that an APS switch is needed.
Following a switchcdred, or active card reset, the BXM card is sent a message from switch software to have it perform an APS switch to align itself with the last user switchapsln switch request. If the last user request is "clear", full automatic APS switching is in effect with the working line in the active state by default. When there is no last user request to switch to any particular line (that is, protection line), the working line becomes active.
Switch active card of a redundant pair of cards.
switchcdred
addcdred, delcdred, dspcdred, prtcdred
| Privilege | Jobs | Log | Node | Lock |
1-3 | Yes | No | BPX | Yes |
switchcdred
Change the active card to be the standby card.
No display produced.
The switchyred command is sometimes referred to as soft y-red switching (also known as the "graceful switching" feature. It lets you access the y-redundancy switching feature already in the system. Executing the switchyred command performs a graceful y-redundancy switch in that no cards need to be reset in the process of switching from the current active card to the current standby card. Thus, all the existing channel programming on both cards remain intact, and is ready to use in the case of a fault condition (where the newly active card is found to be faulty).
The customer typically diagnoses all standby equipment for all duplicated cards. To implement similar preventative maintenance procedures, this command lets you switch active and standby cards, without resetting either card. The customer intends to execute the switch once every two weeks. Should the standby card be found to be faulty, in the current scheme, during re-programming of the reset card, an outage is experienced. To do away with the outage period, the standby card is not to go through a rebuild forced by the resetting of the card. In the case of this feature, neither card is reset, however, programming is continued on both cards. This type of reprogramming will be to make sure all channels are programmed again on the same card. It is transparent to the user, since all the channels were never deleted; they are being reprogrammed as is the custom today in the case of a regular y-redundancy switch.
The switchyred command operates on the following BXM cards:
In addition, you can use the switchyred command on ASI cards and BNI cards. In any case where these cards are not supported, you will be blocked from executing the command at the command line interface. The switchyred command initiates the y-redundancy switch. It can also be initiated through a job. The switchyred command is available through the same access login as the addyred command.
The switchred command lets you switch between cards of a y-redundancy pair, avoiding any card resets or failures. The feature is needed to allow the customer fast failure recovery in the cases where the previously standby card is found to be at fault. The feature allows for the previously active card to maintain its configuration and availability, allowing you to switch to it, either through another soft y-redundancy switch request, or through the automated y-red switching (which executes upon card failure).
The graceful switching command (switchyred) is applicable to BXM, ASI cards, and BNI cards.
This command requires Release 9.1 software and beyond. The cards in question have to be programmed to be y-redundant. The states of the cards have to be Active (for the Primary card) and Standby (for the Secondary card) OR Standby (for the Primary card) and Active (for the Secondary card).
The purpose of a graceful switch is to switch from the current active card of a y-cable pair, to the current standby card of the pair, without deactivating, resetting, or re-programming either of the cards.
You initiate a graceful switch by issuing a switchyred command at the command line interface or through an SNMP script. The input to the command is the primary card's slot number. You can obtain this information through the dspyred command, which lists the Primary card of a yredundancy pair, and the secondary card of the y-red pair. See the example below.
| Slot | Card Type | Other Slot | Front Card | Back Card |
|---|---|---|---|---|
3 | Pri | 4 | BXM | LM-BXM |
4 | Sec | 3 | BXM | LM-BXM |
In the above example, a y-red has been configured using slots 3 and 4, where slot 3 is identified as the Primary card (Pri) of the pair. Using the example shown in switchyred Exampleswitchyred ExampleTable 3-20, the command line would look as follows:
Next Command: switchyred 3
The switchyred command displays errors on the screen if the slot used in the command line if the following conditions exist:
The command line issues a warning and prompts you to continue in case any channel programming is in progress. (Continuing at this stage introduces the risk of encountering continuity problems for a short period of time (until all remaining channels are programmed).
After you issue the command, the switch software starts the process of the graceful switch.
First, turn off the laser of the current active card (by sending it an Ox05 cbus message). In effect, stop running traffic on that card.
Next, activate and start running traffic on the current standby card, forcing it to be the new active card of the pair. This process also starts off the channel re-programming of the cards, and allows for the new standby card to be re-programmed.
All the steps required to complete the graceful y-redundancy switch are in Release 9.2, the main and possible only difference being that neither card is reset.
There are no backward compatibility issues related to the switchyred command in Release 9.1.
The switchyred feature introduces the concept of de-activating a card without a failed state being present, or deactivating the card, or the need to reprogram all the channels on the card.
The switchyred command kicks off the graceful switch process. After you issue the command, switch software checks for and reports the following error conditions:
If the y-redundancy pair (specified through the primary slot) contains cards in the incorrect state, a message is displayed onto the screen indicated the incorrect state of the cards. (valid states for the cards are:
You are prompted to continue if the following is true:
To choose to continue in this state implies that channels (connections) in the process of being programmed might not exist on the standby card after the graceful switching has completed, that is, the programming must be completed on both cards.
A message displays listing the cards being switched from, and the card being switched to, just before the graceful switching process begins.
After the switching process has been kicked off, the switch software does the following:
Event logging does not distinguish between a y-redundancy switch due to a failure (beyond logging the indication of the failure), and a y-redundancy switch due to the execution of the switchyred command.
Switch Y-redundant cards.
switchcdred
addyred, delyred, dspyred, prtyred, switchyred
| Privilege | Jobs | Log | Node | Lock |
1-3 | Yes | No | BPX | Yes |
switchcdred
Change the active card to standby card.
No display produced.
Activates a card you have downed with the dncd command. (If a slot contains a complete card set, both the front and back card are upped. After a card set is upped, it is available as a node resource. When you activate a card, it comes up in either the standby or active state. The initial state depends on whether the network is ready to use the card immediately.
Up card
upcd <slot>
dncd, dspcds
Privilege | 1- |
Jobs | Yes |
Log | Yes |
Node | IGX, BPX |
Lock | Yes |
upcd 10
Activate the card in slot 10. After you activate the NTC in slot 10, its status is "Standby."
pubsipx1 VT SuperUser IPX 16 9.1 Oct. 30 1997 21:15 GMT
FrontCard BackCard FrontCard BackCard
Type Rev Type Rev Status Type Rev Type Rev Status
1 NPC ABC Standby 9 Empty
2 NPC ABC Active 10 NTC ESC E1 P06 Standby-F
3 SDP CBC V35 AF Standby 11 Empty
4 Empty 12 Empty
5 FRP DFR FRI-V35 AA Active 13 CDP ABE T1 P06 Standby-T
6 LDP CC03 232-4 AC Standby 14 Empty
7 Empty universal backplane 15 NTC EC02 Empty Unavail
8 AIT BBF AIT-T3 AD Active 16 Empty
Last Command: upcd 10
Next Command:
| Parameter | Description |
|---|---|
slot | Specifies the card slot number of the card |
Provides an interface to an external device. To establish a session with an external device, first use the cnftermfunc command to designate the auxiliary port to serve as the external device window. To begin the session, enter the window command and specify the port. The control terminal screen subsequently clears, after which characters entered at the control terminal go to the external device and vice versa.
Because the IGX and BPX nodes "bundle" characters together before transmitting them, a slight transfer delay occurs. Transfers are delayed until the transfer buffer is filled or the keyboard is inactive for over 50 milliseconds. To end the session, enter the escape sequence designated with the cnftermfunc command. The default for the escape sequence is ^^ (SHIFT 66).
The window command can be executed over a virtual terminal connection. This makes it possible to control external devices from a single point in the network. Devices such as Channel Service Units (CSUs), routers, channel banks and other devices with RS-232 console ports can be accessed remotely with this feature.
Window to external device
window <a/c>
cnfterm, cnftermfunc
Privilege | 1-4 |
Jobs | No |
Log | No |
Node | IGX, BPX |
Lock | Yes |
window a
Connect to a local router attached to the auxiliary port. The following dialogue shows the prompts and example responses.
Protocol [ip]:
Target IP address: 192.9.202.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]::
Type escape sequence to abort. ^^
Sending 5, 100-byte ICMP Echoes to 192.9.202.1, timeout is 2 seconds:
.......
Success rate is 100 percent
left #
| Parameter | Description |
|---|---|
a | Specifies a window into external equipment attached to the node's auxiliary port. This is the default connection. |
c | Specifies a window into external equipment attached to the node's control port. |
Posted: Fri Nov 8 07:09:19 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.