Table Of Contents

Alphabetical List of Commands addad through cpytrkict

. (a period) (display command history)

addalmslot (add alarm card set)

addapsln/delapsln (add/delete SONET APS line)

addcon (add a data channel connection)

addcon (add channel voice connections)

addcon (add a Frame Relay connection)

addcon (add an ATM connection)

PCR Values and Traffic Policing

addctrlr (add a VSI controller to an IGX node)

addctrlr (add VSI capabilities to an AAL5 feeder interface (BPX))

addextlp (add external loop)

addjob (add a job)

addjobtrig (add job trigger)

addlnloclp (add local loopback to line)

addlnlocrmtlp (add local-remote loopback to BPX line)

addloclp (add local loopback to connections on a port)

addlocrmtlp (add local-remote loopback in a tiered network)

addport (add ATM or Frame Relay port)

addrmtlp (add remote loopback to connections)

addshelf (add interface shelf or controller to a routing node or hub)

addtrk (add a trunk between nodes)

addtrkred (add trunk redundancy)

adduser (add a user)

addyred (add Y-cable redundancy)

Feature Mismatching

APS 1+1 Environment (Redundant Back Cards with Front Card Redundancy)

burnfwrev (burn firmware image into cards)

burnrtrcnf (burn router configuration file)

bye (end user session)

chklm (check node loading model)

clrcderrs (clear detailed card errors)

clrchstats (clear channel statistics)

clrclkalm (clear alarm clock)

clrcnf (clear configuration memory)

clreventq (clear event queues from the fail handler)

clrfrcportstats (clear FRC/FRM port statistics)

clrlnalm (clear circuit line alarm)

clrlnerrs (clear line errors)

clrlog (clear event log)

clrmsgalm (clear message alarm)

clrphyslnalm (clear physical line alarm)

clrphyslnerrs (clear UXM physical line errors)

clrportstats (clear port statistics)

clrrtrcnf (clear router configuration file)

clrscrn (clear terminal screen)

clrslotalms (clear slot alarms)

clrsloterrs (clear slot errors)

clrtrkalm (clear trunk alarm)

clrtrkerrs (clear trunk errors)

clrtrkstats (clear trunk statistics)

cnfabrparm (configure assigned bit rate queue parameters)

cnfapsln (configure APS line parameters)

cnfasm (configure ASM card)

cnfatmcls (configure class template)

cnfbmpparm (configure priority bumping)

cnfbpnv (set backplane type to new)

cnfbus (configure active bus)

cnfbusbw (configure UXM card bus bandwidth)

cnfcassw (configure CAS switching)

cnfcdparm (configure card parameters)

Multilevel Channel Statistics Support

cnfcdpparm (configure CVM card parameters)

cnfcftst (configure communication fail test pattern)

cnfchadv (configure channel adaptive voice)

cnfchdfm (configure channel DFM)

cnfchdl (configure dial type for channels)

cnfchec (configure channel echo canceller)

cnfcheia (configure EIA update rate for channels)

cnfchfax (configure FAX modem detection for channels)

cnfchgn (configure gain insertion for channels)

cnfchpri (configure Frame Relay channel priority)

cnfchstats (configure channel statistics collection)

cnfchts (configure channel timestamp)

cnfchutl (configure channel utilization)

cnfcldir (configure control lead direction)

cnfclksrc (configure network clock source)

cnfclnparm (configure circuit line parameter)

cnfclnsigparm (configure circuit line signaling parameters)

cnfcls (configure class template)

cnfcmb (configure combined timeout parameters)

cnfcmparm (configure connection management parameters)

cnfcon (configure connection)

cnfcond (configure conditioning template)

cnfcos (configure CoS)

cnfctrlr (configure controller with new VPI and start_VCI for control channels)

cnfdate (configure date and time)

cnfdch (configure voice connection for idle code suppression)

cnfdchtp (configure data channel interface type)

cnfdclk (configure data channel clocking type)

cnfdiagparm (configure diagnostic test parameters)

cnfdlparm (configure download parameters)

cnfecparm (configure echo canceller parameters)

cnffrcls (configure Frame Relay class)

cnffrcon (configure Frame Relay connection)

cnffrcport (configure Frame Relay port)

cnffstparm (configure ForeSight node parameters)

cnffunc (configure system functions)

cnffwswinit (configure FW/SW download initiator IP address)

cnfict (configure interface control template)

cnflan (configure LAN)

cnfleadmon (monitor LDM/HDM data port leads)

cnfln (configure line)

cnflnalm (configure line alarm)

cnflnparm (configure ATM line card parameters)

cnflnpass (configure line pass-through)

cnflnsigparm (configure line signaling parameters)

cnflnstats (configure line statistics collection)

cnfmode (configure mode)

cnfmxbutil (configure muxbus utilization)

cnfname (configure node name)

cnfnodeparm (configure node parameter)

cnfnwip (configure network IP address)

cnfoamseg (configure connection OAM segment status)

cnfphyslnstats (configure physical line statistics)

cnfport (configure Frame Relay port)

ELMI Neighbor Discovery for UFM

Signaling Protocol Timers

cnfport (configure ATM port)

Automatic Routing Management to PNNI Migration

Traffic Shaping on the UXM and URM

Traffic Shaping on the BXM

Virtual Ports

cnfportq (configure port queue parameters)

cnfportstats (configure port statistics collection)

cnfpref (configured preferred route for connections)

cnfprt (configure printing functions)

cnfpwd (configure password)

cnfqbin (configure Qbin)

cnfrcvsig (configure receive signaling)

cnfrobparm (configure robust alarms parameters)

cnfrrcpu (configure CPU-based reroute throttling level parameters)

cnfrsrc (configure resource)

cnfrsrc (configure VSI resources for IGX)

cnfrsrc (configuring VSI resources for BPX)

cnfrtcost (display connection loading)

cnfrtr (configure router configuration parameters)

URM Remote Router Configuration Feature

cnfrtrcnfmastip (configure router configuration download initiator TFTP server IP)

cnfrtrparm (configure router service parameters)

cnfslotalm (configure slot alarm parameters)

cnfslotstats (configure slot statistics collection)

cnfsnmp (configure SNMP parameters)

cnfstatmast (configure statistics master SV+ address)

cnfstatparms (configure TFPT statistics parameters)

cnfsysparm (configure system parameters)

cnftcpparm (configure TCP parameters)

cnfterm (configure terminal port)

cnftermfunc (configure terminal port functions)

cnftime (configure time)

cnftlparm (configure trunk-based loading parameters)

cnftmzn (configure time zone)

cnftrk (configure trunk)

Physical and Virtual Trunk Configuration

IMA-Compliant Trunk Configuration

Subrate and Fractional Trunk Configuration

cnftrkalm (configure trunk alarms)

cnftrkict (configure trunk interface control template)

cnftrkparm (configure trunk card parameters)

cnftrkstats (configure trunk statistics collection)

cnftstparm (configure card test parameters)

cnfuiparm (configure user interface parameters)

cnfuvmchparm (configure channel parameters on a UVM)

cnfvchparm (configure voice channel parameter)

cnfvchtp (configure interface type for voice channels)

cnfvsiif (assign a service class template to an interface)

cnfvsipart (configure VSI ILMI on VSI partition)

cnfxmtsig (configure transmit signaling)

compactrsrc (compact resources)

cpyict (copy interface control templates)

cpytrkict (copy trunk interface control template)

Alphabetical List of Commands addad through cpytrkict

---

. (a period) (display command history)

Displays the twelve (12) most recently used commands. To reuse one of these commands, enter the associated number. The command appears on the command entry line, where you can edit or re-execute a command.

To edit the command line: backspace through the command's arguments and type in a new value or backspace without typing a new value to restart the command at the cursor position.

Syntax

.            (A period)

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-6	No	No	BPX, IGX			No

Example

Display the command history.

.           (A period)

sw180          TN    Cisco           IGX 8420  9.3.g0    Oct. 20 2000 09:26 GMT

Command history

12: addyred 4

11: dspcds

10: dspcd 6

 9: dspcd 9

 8: addyred 6 9

 7: dsptrks

 6: addshelf 5.1

 5: upcd

 4: upcd 6

 3: dspcds

 2: dncd 9

 1: upcd 9

Last Command: upcd 9

Next Command: 

addalmslot (add alarm card set)

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.

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.

Syntax

addalmslot <slot number>

Parameter

Parameter	Description
<slot number>	Specifies the slot number of the alarm card set.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-4	No	Yes	BPX, IGX			Yes

Related Commands

delalmslot, dspalms

Example

Enable alarm reporting from slot 16 in a node. (The system then displays alarm status.)

addalmslot 16

beta           TRM   YourID:1        IGX 8430    9.3      Apr. 13 2000 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:      

addapsln/delapsln (add/delete SONET APS line)

Add a SONET APS (Automatic Protection Switching) line. The addapsln and delapsln command lets you add SONET APS (Automatic Protection Switching) for BXM OC-3 or OC-12 lines.

SONET APS is a standard that describes the switching of SONET lines from the active line to a standby line to provide hardware line redundancy. The SONET APS feature applies only to BXM OC-3 and OC-12 cards in this release.

When adding a new APS line pair, you must specify the desired APS protocol. The delapsln command deletes APS for the lines.

When the addapsln command executes, the switch software:

•Verifies that the slot.port arguments support APS

•Verifies that the appropriate back card is installed

•Verifies that the protection port is not already active

•If card redundancy is already configured for the two-slot case (APS 1+1), verifies that the primary card is the same type as the working line card.

Before the addapsln command has been executed, there is no working or protection line. The addapsln command defines which line is the working line and which line is the protection line. (For APS 1+1 Annex B, the active line is called the "primary section," and the standby line is called the "secondary section," which provides protection for the primary section.)

Feature Mismatching to Verify APS (Automatic Protection Switching) Support

The addapsln command, in addition to other configuration commands, performs mismatch verification on the BXM and UXM cards. For example, the addapsln command verifies whether the cards both have APS support configured. Refer to the BPX 8600 Series Installation and Configuration Manual.

Whenever you activate a feature by configuring it with CLI commands, switch software performs a verification to ensure that the hardware and firmware support the feature. For example, if you are attempting to add APS on a specific line (by using addapsln), and the BXM card does not support this feature, a warning message is displayed and the addition is not completed.

The Feature Mismatching capability does not mismatch cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Syntax

addapsln <slot.port1> < slot.port2> <protocol>

You must enter the slot.port pair and the protocol option. If you do not enter the protocol option, a menu lists the options.

Parameters

Parameter	Description
slot.port1	The desired working line number
slot.port2	The desired protection line number
protocol	1: 1+1 2: 1:1 3: 1+1 Annex B 4: 1+1, ignore K1K2 bytes

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1	No	Yes	BPX			Yes

Related Commands

delapsln, cnfapsln, dspapsln, dsplog, dspalms

Example

Add an APS redundant pair, with Working line on slot 11, port 1; Protection line on slot 12, port 1; with "1" specifying APS 1+1 protocol.

addapsln 11.1 12.1 1

sw119          TRM   StrataCom       BPX 8620  9.3.10    Date/Time Not Set

Work/Protect Actv Active Line      Standby Line     Current APS     Last User

(Work1/Work2)Line Alarm Status     Alarm Status     Alarm Status    Switch Req

11.1 12.1    NONE Deactivated      APS Deactivated  APS Deactivated Clear

Last Command: addapsln 11.1 12.1 1

addcon (add a data channel connection)

Establishes data channel connections between nodes in a network.

After you add a connection by using the addcon command, the node automatically routes the connection. The node where you execute addcon is the "owner" of the added connections. The concept of ownership is important because you must enter information about automatic rerouting and preferred routing at the node that owns the connection. See the cnfpref and cnfcos commands for more information on automatic rerouting. Before the node adds the connection, the proposed connection appears on the screen with a prompt for you to confirm the addition.

When applied to data connections, the addcon command adds a synchronous data connection to the network. You can add synchronous data connections to any node slot equipped with either an LDM or HDM in an IGX node. Before you add a connection, determine the desired data rate. To find the data rates that individual cards support, refer to the card descriptions in the Cisco IGX 8400 Series Reference manual.

When connecting sets of data channels, you do not have to specify the full channel set for the local end of the connection. You have to designate only the first channel in the range. For example, to add connects 27.1-4 at local node alpha to channels 9.1-4 at beta, you can enter:

addcon 27.1-4 beta 9.1

If Y-cable redundancy has been specified, you can add data connections at only primary card slots (not at the secondary card slots). See the addyred definition for more information. Standard Data Rates Table 3-1 through Table 3-9 follow, listing data rates. The following notations appear with some data rates:

•*	Must be used with 8/8 or 8/8I coding.
•/n	Specifies a partially filled packet type: the /n allows partial packets to be sent and so avoid the delay incurred by waiting to build a full packet.
•f	Entered after the data rate, an f specifies fast EIA (interleaved EIA) for the connection.
•t	Indicates "transparent" (CDP or CVM subrate DS0A): if you include the t-option, the IGX node does not check for supervisory or control information.

Table 3-1 Data Connection Load Table with Normal EIA and No DFM 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
1.2	43	28	38	32
1.8	65	28	57	32
2.4	35	70	30	80
3.2	46	70	40	80
3.6	52	70	45	80
4.8	35	140	30	160
6.4	46	140	40	160
7.2	52	140	45	160
8	58	140	50	160
9.6	69	140	60	160
12	86	140	75	160
12.8	92	140	80	160
14.4	103	140	90	160
16	115	140	100	160
16.8	120	140	105	160
19.2	138	140	120	160
24	172	140	150	160
28.8	206	140	180	160
32	229	140	200	160
38.4	275	140	240	160
48	343	140	300	160
56	381	147	334	160
57.6	392	147	360	160
54	436	147	381	168
72	490	147	429	168
76.8	523	147	458	168
84	572	147	500	168
96	654	147	572	168
112	762	147	667	168
115.2	784	147	686	168
128	871	147	762	168
144	980	147	858	168
168	1143	147	1000	168
192	1307	147	1143	168
224	1524	147	1334	168
230.4	1568	147	1372	168
256	1742	147	1524	168
288	1960	147	1715	168
336	2286	147	2000	168
384	2613	147	2286	168
448	3048	147	2667	168
512	3483	147	3048	168
672	4572	147	4000	168
768	5225	147	4572	168
772	5252	147	4596	168
896	6096	147	5334	168
1024	6966	147	6096	168
1152	7837	147	6858	168
1344			8000	168
Unshaded connections generate time-stamped data packets. Shaded connections generate non-time-stamped data packets.

Table 3-2 Data Connection Load Table with Interleaved EIA 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
1.2f	35	35	30	40
1.8f	52	35	45	40
2.4f	35	70	30	80
3.2f	46	70	40	80
3.6f	52	70	45	80
4.8f	69	70	60	80
6.4f	92	70	80	80
7.2f	103	70	90	80
8f	115	70	100	80
9.6f	138	70	120	80
12f	172	70	150	80
12.8f	183	70	160	80
14.4f	206	70	180	80
16f	229	70	200	80
16.8f	240	70	210	80
19.2f	275	70	240	80
24f	343	70	300	80
28.8f	412	70	360	80
32f	458	70	400	80
38.4f	549	70	480	80
48f	686	70	600	80
56f	800	70	700	80
57.6f	823	70	720	80
54f	915	70	800	80
72f	1029	70	900	80
76.8f	1098	70	960	80
84f	1200	70	1050	80
96f	1372	70	1200	80
112f	1600	70	1400	80
115.2f	1646	70	1440	80
128f	1829	70	1600	80
144f	2058	70	1800	80
168f	2400	70	2100	80
192f	2743	70	2400	80
224f	3200	70	2800	80
230.4f	3292	70	2880	80
256f	3658	70	3200	80
288f	4115	70	3600	80
336f	4800	70	4200	80
384f	5486	70	4800	80
448f	6400	70	5600	80
512f	7315	70	6400	80
1.2f	35	35	30	40
1.8f	52	35	45	40
2.4f	35	70	30	80
3.2f	46	70	40	80
3.6f	52	70	45	80
4.8f	69	70	60	80
6.4f	92	70	80	80
DFM is not available on interleaved EIA connections.

Table 3-3 Data Connection Load Table with Partially Filled Packets and No DFM 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
2.4/4	86	28	75	32
3.2/4	115	28	100	32
3.6/4	129	28	113	32
4.8/10	69	70	60	80
4.8/4	172	28	150	32
6.4/10	92	70	80	80
6.4/4	229	28	200	32
7.2/10	103	70	90	80
7.2/4	258	28	225	32
8/10	115	70	100	80
9.6/10	138	70	120	80
12/10	172	70	150	80
12.8/10	183	70	160	80
14.4/10	206	70	180	80
All of the above connections generate time-stamped data packets.

Table 3-4 Data Connection Load Table with Normal EIA and DFM 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
1.2	58	21	24	3
1.8	86	21	24	3
2.4	39	63	72	9
3.2	51	63	72	9
3.6	58	63	72	9
4.8	37	133	152	19
6.4	49	133	152	19
7.2	55	133	152	19
8	61	133	152	19
9.6	73	133	152	19
12	91	133	152	19
12.8	97	133	152	19
14.4	109	133	152	19
16	121	133	152	19
16.8	127	133	152	19
19.2	145	133	152	19
24	181	133	152	19
28.8	217	133	152	19
32	241	133	152	19
38.4	289	133	152	19
48	361	133	152	19
56	422	133	152	19
57.6	434	133	152	19
64	482	133	152	19
72	542	133	152	19
76.8	578	133	152	19
84	632	133	152	19
96	722	133	152	19
112	843	133	152	19
115.2	867	133	152	19
128	963	133	152	19

Table 3-5 Data Connection Load Table with Partially Filled Packets and DFM

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
2.4/4	115	21	100	24
3.2/4	153	21	134	24
3.6/4	172	21	150	24
4.8/10	77	63	67	72
4.8/4	229	21	200	24
6.4/10	102	63	89	72
6.4/4	305	21	267	24
7.2/10	115	63	100	72
7.2/4	343	21	300	24
8/10	127	63	112	72
9.6/10	153	63	134	72
12/10	191	63	167	72
12.8/10	204	63	178	72
14.4/10	229	63	200	72

Table 3-6 Data Connection Load Table with Partially Filled Packets and Interleaved EIA

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
1.2f/2	86	14	75	16
1.8f/2	129	14	113	16
2.4f/5	69	35	60	40
2.4f/2	172	14	150	16
3.2f/5	92	35	80	40
3.2f/2	229	14	200	16
3.6f/5	103	35	90	40
3.6f/2	258	14	225	16
4.8f/5	138	35	120	40
6.4f/5	183	35	160	40
7.2f/5	206	35	180	40
All of the above connections generate time-stamped data packets. DFM is not available on interleaved EIA connections.

Table 3-7 Sub-Rate Data Connection Load Table (HDM to HDM)

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
2.4t			35	80
4.8t			35	160
9.6t			70	160
56t			381	168
t			381	168
All sub-rate data connections use 8/8 coding. Unshaded connections generate time-stamped data packets. Shaded connections generate non-time-stamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections.

Table 3-8 Sub-Rate Data Connection Load Table (HDM to HDM) 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
2.4/4t			88	32
4.8/10t			70	80
4.8/4t			175	32
9.6/10t			140	80
All sub-rate data connections use 8/8 coding. All of the above connections generate time-stamped data packets. DFM is not available on sub-rate connections. Interleaved EIA is not available on sub-rate connections.

Table 3-9 Super-Rate Data Connection Load Table (LDM to HDM) 

Bit Rate (Kbps)	7/8 Coding		8/8 Coding
	Pkt/Sec	Bits/Pkt	Pkt/Sec	Bits/Pkt
1x56	381	147	334	168
2x56	762	147	667	168
3x56	1143	147	1000	168
4x56	1524	147	1334	168
5x56	1905	147	1667	168
6x56	2286	147	2000	168
7x56	2667	147	2334	168
8x56	3048	147	2667	168
1x64	436	147	381	168
2x64	871	147	871	168
3x64	1307	147	1307	168
4x64	1742	147	1143	168
5x64	2177	147	1524	168
6x64	2613	147	1905	168
7x64	3048	147	2286	168
8x64	2483	147	2667	168
All of the connections generate non-time-stamped data packets. DFM is not available on interleaved EIA connections.

In fast EIA signaling mode, an interleaved byte of EIA signaling information is associated with every byte of data in a packet. This format is appropriate for applications where EIA lead transitions must closely synchronize with user data. Fast EIA can apply to data rates up to 512 Kbps.

When FastPackets are built using the 7/8 coding format, each octet in the FastPacket payload consists of seven user data bits followed by a 1. This "bit-stuffing" allows these FastPackets to be safely carried on trunks that enforce ones density requirements by ensuring that each octet contain at least one 1 (such as IGX trunks configured for ZCS or AMI encoding). The user data may have any format and may contain any pattern, including all 0s. The single 1 inserted in the final bit position of each octet ensures that no more than seven consecutive 0s occur in a FastPacket. The 7/8 coding format is the safest mode to use when the data protocol is unknown and certain trunks in the network use ZCS or AMI.

When FastPackets are built using the 8/8 coding format, each octet in the FastPacket payload consists of eight user data bits. The 8/8 coding format is more efficient than the 7/8 format. However, the ones density requirement on trunks must be met by one of the following:

•Ensuring that the end-user equipment data protocol can never send more than seven consecutive 0s.

•Ensuring that the connection can never be carried on a trunk which uses ZCS ones density enforcement.

The vast majority of trunks today use intelligent ones density enforcement schemes, such as B8ZS, HDB3, B3ZS, or CMI. All such trunks can safely carry 8/8 data connections with no risk of data corruption. Data connections can be configured to NOT use ZCS trunks by specifying the optional "*Z" routing restriction.

When FastPackets are built using the 8/8I coding format, each octet in the FastPacket payload consists of eight inverted user data bits, i.e., each 0 is changed to a 1 and each 1 is changed to a 0. The bits are re-inverted at the far end of the connection. For such connections, the ones' density requirement on trunks must be met by one of the following:

•Ensuring that the end-user equipment data protocol can never send more than seven consecutive 1s.

•Ensuring that connection can never be carried on a trunk that uses ZCS ones density enforcement.

As with the 8/8 coding format, 8/8I connections can be safely carried on the vast majority of trunks today. However, the 8/8I format is primarily intended to provide the efficiency of 8/8 coding for any data which is HDLC or SDLC-based. HDLC/SDLC can never send more than six consecutive 1s, which, when inverted, automatically meets the ones density requirements of every possible trunk format.

If the data protocol requires an acknowledgment and is delay-sensitive, avoid routing the connection over a satellite line (*s for avoid). If 8/8 or 8/8I coding is the selected format, avoid trunks with zero code suppression (*z for avoid) because the zero code suppression could corrupt the last bit in the byte.

Syntax

addcon <local channel> <remote node> <remote channel> <type> <coding> [avoid]

Parameters

Parameter	Description
<local channel>	Specifies the local channel or set of channels in the format slot.port [-port]. (The brackets indicate you can specify a range of channels.)
<remote node>	Specifies the name of the node at the other end of the connection. For a DACS-type connection (where a channel on a node connects to a channel on the same node), use the local node name for remote node.
<remote channel>	Specifies the remote channel or set of channels in the format slot.port [-port]. (The brackets indicate you can specify a range of channels.)
<type>	Specifies the data connection bit rate, EIA control lead mode, and in some cases, the number of data bytes in a data packet. Refer to the Standard Data Connection rates for allowable bit rates.
<coding>	Specifies the data coding format for data transmissions. Valid formats: •7/87 = bits of user data plus a 1 inserted in the final bit position of each data byte in a data packet. This is the default coding. •7/8e = used with LDP or LDM application. •8/88 = bits of user data for each data byte in a data packet. •8/8I8 = bits of user data for each data byte in a packet. The data is inverted
[avoid]	Optionally specifies the type of trunk for the connection to avoid. The default is no avoidance. The choices are: •s - avoid satellite trunks. •t - avoid terrestrial trunks. •z - avoid trunks using zero code suppression techniques that modify any bit position to prevent long strings of 0s.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	IGX			Yes

Related Commands

delcon, dncon, dspcon, dspcons, upcon

Example

Add a low speed data connection of 56 Kbps at 6.1. The connections are highlighted on the screen. A prompt appears asking you to confirm these connections. Respond "y" for yes to add the connection. The connections screen then appears showing that data channel 11.1 on node pubsigx2 is connected to channel 6.1 on node pubsigx1. The 56 under the type category indicates that the data rate for the channel is 56 Kbps.

addcon 6.1 pubsigx2 11.1 56

pubsigx1       TN    SuperUser       IGX 8420    9.3    Apr. 13 2000  06:23 PDT

 From           Remote      Remote

 6.1            NodeName    Channel         State  Type      Compress  Code CoS

 6.1            pubsigx2    11.1            Ok     56                  7/8  0

Last Command: addcon 6.1 pubsigx2 11.1 56

Next Command:

Example

For a CDP super-rate connection, add a 256 Kbps (4x64) connection from an SDP at node alpha to the CDP at node beta. Data rates come from the Standard Data Rate Connections in the preceding pages.

addcon 5.1 beta 6.1-4 4x64

The elements on the command line consist of:

addcon slot.port remote nodename slot.start channel at far-end channel rate

Example

For CDP to CDP or CVM to CVM, add a 256 Kbps (4x64) data connection from a CDP (or CVM) at node alpha to the CDP (or CVM) at node beta. The syntax for this example requires that the start and end channel are entered for both ends of the connection and that the data rate is specified to be the same at both ends.

addcon 5.4-7 beta 6.1-4 4x64

The channel numbers can be different on each end if they are contiguous.

addcon	slot.start channel -end channel	remote nodename
	slot.start channel -end channel	rate

addcon (add channel voice connections)

Establishes the channel connections between nodes in the network. You can add voice connections to any slot that has a CDP, UVM, or CVM. Before you add a connection, determine its compression type.

If you plan for a port on a UVM to carry more than 16 channels with LDCELP or the G.729 version of CACELP, you must have a second, connected UVM and configure the resultant pair of UVMs for passthrough operation. If you attempt to add more than 16 LDCELP or G.729 channels, the system reports any excess connections as being failed connections after addcon execution finishes. Furthermore, if you execute dspcon, the status display for the excess connections shows "ConnRJ" (connection rejected). Refer to the cnflnpass description in this chapter and the UVM description in the Cisco IGX Reference for a description of passthrough.

After you have established passthrough for a pair of UVM card sets, the system does not allow duplication of channel numbers when you add connections. For example, if you add 7.1.1-16, the node does not allow you to add 8.1.1-8 if you have linked the UVMs by using cnflnpass. Instead, you would add 8.1.17-24.

A UVM with Model B or higher firmware supports CAS switching. Before you can add connections in a network with CAS switching, you must configure the UVM for this feature by using the cnfcassw command. Note that, for CAS switching, you use addcon to add the signaling channels at the near and far end in the format slot.port.24 on a T1 line and slot.port.16 on an E1 line. Also, the connection type for these signaling channels is "t." If you specify D-channel compression, the connection type is "td." See the description of cnfcassw in the "Setting Up Lines" chapter or, for a more detailed description, the manual titled Cisco VNS (Voice Network Switching) Installation and Operation.

When adding a range of channels, you do not have to specify the full channel set at the near-end. You may specify only the first channel in the set. For example, to connect channels 13.1-10 at alpha to channels 12.5-14 at beta, you could enter "addcon 13.1-10 beta 12.5." In this example, channel 13.1 is connected to channel 12.5, and channel 13.2 is connected to channel 12.6, and so on.

Connections are added with a default class of service (CoS). The value of CoS is the number of seconds that the node waits before it reroutes the connection after a failure. The CoS applies to various types of connections other than voice.

Table 3-10 and Table 3-11 describe what you enter for the type parameter for each rate and compression variable.

Table 3-10 Types of CDP and CVM Operation

Rate	VAD	No VAD	Comment
64 Kbps	v	p	None.
32 Kbps	c32	a32	None.
32 Kbps for FAX	c32d	a32d	Specifies 32 Kbps specially optimized for FAX; c32d incorporates Voice Activity Detection (VAD).
24 Kbps ADPCM	c24	a24	None.
16 Kbps no ZCS	c16z	a16z	For non-ZCS only.
16 Kbps	c16	a16	ZCS is permissible; c16 and a16 use non-standard compression algorithms.

Table 3-11 Types of UVM Operation 

Rate	VAD	No VAD	Comment
64 Kbps	v	p, t	Pass-through does not accept t-type connections.
32 Kbps	c32	a32	None.
24 Kbps ADPCM	c24	a24	None.
16 Kbps no ZCS	l16V	l16	For non-ZCS only.
8 Kbps	g729r8v g729ar8v	g7298 g729ar8	The UVM supports two forms of CACELP. Both versions can support VAD (or no VAD). The "a" indicates G.729A. The other version is G.729.

Table 3-12 Types of UVM Connections

Connection	Description
p	A p-connection carries 64 Kbps PCM voice and supports A-law or micro-law encoding and conversion, gain adjustment, and signaling.
t	A t-connection carries 64 Kbps clear channel data traffic.
td	A td-connection carries compressed, 16 Kbps signaling between an IGX node and VNS unit.
v	A v-connection is the same as "p" (above) but with VAD.
a32 a24	Specifies ADPCM only. You can specify 32 Kbps or 24 Kbps.
c32 c24	Specifies both ADPCM and VAD. You can specify 32 Kbps or 24 Kbps.
l16	LDCELP compression of voice to 16 Kbps.
l16v	LDCELP compression of voice to 16 Kbps with VAD.
g729r8	CACELP voice compression at 8 Kbps according to G.729. This type also supports automatic FAX and modem upgrade.
g729r8v	CACELP voice compression at 8 Kbps with VAD according to G.729.
g729ar8	CACELP voice compression at 8 Kbps according to G.729A.
g729ar8v	CACELP voice compression at 8 Kbps with VAD according to G.729A.

The difference between a PCM (p) connection and a transparent (t) or transparent D-compression (td) connection is that the D4 frame signaling bits are identified and processed as signaling information with PCM connections. PCM connections permit gain adjustment to be applied to the connection. Transparent connections treat all bits, including signaling bits, as data bits and disables any gain adjustment conversion that you may have specified.

The number in the type field indicates the ADPCM rates in Kbps. The "z" suffix indicates that 00 code level is used. Type a16 or c16 uses only 01, 10, and 11 binary codes to avoid long strings of zeros. Type a16z and c16z connections use the 00 code and are automatically configured to avoid ZCS lines (*Z).

Syntax

addcon <local channel> <remote node> <remote channel> <type> [avoid]

Parameters

Parameter	Description
local channel	Specifies the local channel or set of channels to add. Right-angle brackets indicate a range of channels. Channel specification on a UVM has one more parameter than the specification on a CDP or CVM: For a CDP or CVM, the format for channel specification is slot.chan[-chan]. For a UVM, the format for channel specification is slot.line.chan[-chan]. Refer to the Cisco IGX Reference for a description of the UVM's lines. Note that, if you are using CAS switching with Model B firmware, line must be 1.
remote node	Specifies the name of the node at the other end of the connection. For a DAX connection (where channels on a node are connected to channels on the same node), use the local node name.
remote channel	Specifies the remote channel or set of channels to connect. Brackets indicate that a range of channels can be specified. Channel specification on a UVM has one more parameter than the specification on a CDP or CVM. For a CDP or CVM, the format for channel specification is slot.chan[-chan]. For UVM, the format for channel specification is slot.line.chan[-chan].
type	Specifies the voice connection type. Refer to Table 3-9 or Table 3-10 for voice connection types and compression. For connections to an access device such as the Cisco 3810, type can be one of the following: 24 Kbps or 32 Kbps ADPCM, LDCELP, or CACELP.
avoid	Specifies the type of trunk for the connection to avoid. Optional Default: no avoidance. The choices are: •s - avoid satellite trunks. •t - avoid terrestrial trunks. •z - avoid trunks using zero code suppression techniques that modify any bit position to prevent long strings of zeros.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	IGX			Yes

Related Commands

delcon, dncon, dspcon, dspcons, cnfcos

Example

Add a v- type voice connection. This command connects channel 7.2 on node alpha to channel 8.2 on node beta. A prompt asks you to confirm the proposed connections.

Connection type is "v," class of service (CoS) is "2," compression is VAD, and ownership is local. For an explanation of CoS, see the cnfcos description. Because you are entering the addcon command at node alpha, the node alpha is the owner of the connection.

addcon 7.2 beta 8.2 v

alpha          TRM   YourID:1        IGX 16    9.3    Apr. 13 2000 09:37 PST 

 Local      Remote      Remote 		 		 								 			 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	 	Route       

 Channel    NodeName    Channel    State  Type    Compression Avoid CoS

 7.2	        beta	        8.2        	Ok	     v	       VAD         	L     	2

Last Command: addcon 7.2 beta 8.2 v                                          

Next Command: 

addcon (add a Frame Relay connection)

After you add a connection, the system automatically routes the connection. The node on which you execute addcon is the owner of the connection. The concept of ownership is important because you must specify automatic rerouting and preferred routing information at the node that owns the connection. See the cnfpref and cnfcos descriptions for information on automatic rerouting. Before it actually adds the connection, the system displays the parameters you have specified and prompts you to confirm them.

---

Note For cards with Y-cable redundancy specified, you can add connections to only primary cards.

---

Each Frame Relay connection (and associated user device) has a local identification in the form of a unique DLCI. The total range for DLCIs is 1-1023. Typically, DLCIs 16-1007 are available for local and remote channels. According to ANSI standards, DLCIs 1-15 and 1008-1022 are reserved. DLCI 1023 is reserved for LMI signaling.

Only a UFM could come close to using all DLCIs. The maximum number of connections on a UFM is 1000. The maximum number of Frame Relay connections on an FRC or FRM is 252.

If a user device can automatically determine the network configuration by using the LMI, you do not need to specify the DLCIs in the network to the device. If a device cannot interrogate the network to determine the DLCIs in the network, you must specify the network DLCIs to the user device.

As the following sections describe, you can generally differentiate Frame Relay connections as normal, bundled, grouped, and frame forwarding. In particular, a Frame Relay connection can also terminate at a Frame Relay endpoint or an ATM endpoint if the endpoints have firmware to support this arrangement. A connection that terminates at Frame Relay and ATM endpoints uses service interworking (SIW).

Service Interworking

Frame Relay connections that terminate at ATM endpoints require service interworking (SIW) support. At the Frame Relay end, service interworking is one of the optional parameters. The line cards on which you can add service interworking connections are:

•the UFM on an IGX node

•ASI on a BPX node

•FRSM in an MGX 8220 shelf.

The Frame Relay endpoint has an identifier in the format slot.port.DLCI.

For SIW connections, the ATM endpoint identifier has the format slot.port.vpi.VCI.

---

Note You cannot group or bundle SIW connections with non-SIW connections.

---

Adding connections to a virtual port for a BXM card does not require the virtual port number. The slot, port, and VPI map to the supporting virtual port. In addition, Vc QDepth is configurable for all connection types.

Bundled Connections

A normal connection is a single PVC. A Frame Relay PVC can terminate at either a Frame Relay endpoint or an ATM endpoint.

Connection bundling creates a full mesh of connections between two groups of Frame Relay ports by executing addcon command only once. When you add a bundle between two groups of ports, you create a connection between each port of one group of ports and each port of the other group of ports. Each group of Frame Relay ports can include up to four ports. Consequently, the maximum number of connections in a bundle is 16 (resulting from a full mesh of connections between two groups of four ports each).

Note that a Port Concentrator Shelf does not support bundling.

Characteristics of connection bundling are:

•The number of ports used at each end of the bundle does not have to be the same.

•All of the ports used in a group must be on the same card.

•Only the FRP Model D and the FRM Model D support connection bundles. The UFM does not support connection bundling.

•All of the ports used for a bundle must be contiguous. For example, a bundle on a card may not consist of only ports 1, 3, and 4.

•The syntax for specifying a group of ports for a connection bundle is slot.port[xport].

When you create a connection bundle with addcon, you do not explicitly specify the required DLCI at each endpoint of each connection. Instead, the DLCIs are automatically assigned using global addressing with the Port IDs, which have been previously assigned to the ports. Consequently, you must first assign a Port ID (other than 0) to every port to which you plan to assign a connection bundle. Use cnfport to assign a Port ID or dspport to see an existing Port ID.

For example, the command

addcon 6.1x3 alpha 7.2x3 1

defines a single connection bundle between a local group of 3 ports (ports 1, 2, and 3 on card 6) and a remote group of 2 ports (ports 2 and 3 on card 7). The resulting connection bundle consists of these six connections:

local node slot 6.port 1 to node alpha slot 7.port 2

local node slot 6.port 1 to node alpha slot 7.port 3

local node slot 6.port 2 to node alpha slot 7.port 2

local node slot 6.port 2 to node alpha slot 7.port 3

local node slot 6.port 3 to node alpha slot 7.port 2

local node slot 6.port 3 to node alpha slot 7.port 3

Each connection in the bundle is assigned the parameters of the same Frame Relay class (class 1, in the example above). Notice that no DLCIs were specified for the six connections. The DLCIs are automatically assigned using the Port IDs of the ports.

As an example, assume that the following Port IDs had been previously assigned for the five ports.

port 6.1Port ID = 22

port 6.1Port ID = 534

port 6.3Port ID = 487

port 7.2Port ID = 92

port 7.3Port ID = 796

As a result of the addcon command, the six connections that you create are automatically assigned DLCIs using global addressing as follows.

6.1.92 - 7.2.22

6.1.796 - 7.3.22

6.2.92 - 7.2.534

6.2.796 - 7.3.534

6.3.92 - 7.2.487

6.3.796 - 7.3.487

The dspcons display shows the entire bundle as a single item. Therefore, you cannot see the automatically assigned DLCIs on the dspcons screen. (The automatically assigned DLCIs in the preceding list appear in italics.) To see the DLCIs, use dspcon, as in the following example:

dspcon 6.1x3 alpha 7.2x3

The preceding shows one screen for the whole bundle then an additional screen for each connection in the bundle. The assigned DLCIs appear in these individual connection display screens.

---

Note If you request help for addcon at the command line prompt, the Help line shows type as a parameter. However, when you are using addcon for a Frame Relay connection, the type shown in the help display is actually the Frame Relay class shown on the preceding syntax line As stated, you can optionally override any or all of the bandwidth parameters and ForeSight-enable in the Frame Relay class by typing the parameters that appear as frp_bw and avoid in the Help display.

Note also that you do not enter the coding parameter shown on the Help line.

---

Frame Forwarding Connections

A non-Frame Relay data connection (such as HDLC or SDLC) that is routed through Frame Relay cards can bypass a router or take advantage of DFM at higher data rates. The format slot.port.* identifies a frame forwarding connection. For example:

addcon 11.2.* alpha 12.3.* 2

The "*" indicates to the node that a DLCI is meaningless.

Maximum Connections Per Port with Signaling Protocols

For any Frame Relay card set that has a maximum frame length of 4510 bytes, the use and type of signaling protocol you may have (optionally) specified with the cnfport command results in a limit on the possible number of connections per physical or logical port. The maximum number of connections per port for each protocol is:

•For Annex A: 899

•For Annex D: 899

•For StrataLMI: 562

The addcon command does not prevent you from adding more than the maximum number connections on a port. If the number of connections is exceeded, the particular LMI does not work on the port, the full status messages that result are discarded, and LMI timeouts occur on the port. A port failure results and subsequently leads to A-bit failures in segments of the connection path.

Syntax

addcon <local_channel> <remote_node> <remote_channel> [con_type] <frame_relay_class | [individual parameters]> [route_avoid]

Parameters

Parameter	Description
local channel	Specifies the local channel to connect in the format: slot.port.DLCI | x port | .* Range for FRP port: 1-24 Range for FRM port: 1-31 Range for UFM-C port: 1-250 (For connections on a UFM-C, line is not necessary because of the port-to-line mapping through addport). Range for UFM-U (V.35 or X.21) port: 1-12 Range for UFM-U (HSSI) port: 1-4 Range for DLCI: 16-1007
remote node	Specifies the name of the remote node at the other end of the connection.
remote channel	Specifies the connection at the far end. For Frame Relay termination points, use: slot.port.DLCI | x port | .* If the far end is an ATM termination (as in interworking), use: slot.port.vpi.vci Range vpi: 0-255 Range vci: 1-4095 One exception to these ranges is an interface shelf (which uses Annex G signaling) in a tiered network: •For an MGX 8220 shelf, VPI range: 1-1015 VCI range: 1-65535 •For an MGX 8850 shelf, when adding a connection with a UNI interface to a BPX routing node, VPI range: 1-4095 VCI range: 1-65535 For an MGX 8850 shelf, when adding a connection with an NNI interface to a BPX routing node, VPI range: 1-4095 VCI range: 1-65535 •For an IGX/AF shelf, Range (VPI and VCI): 1-255 You do not need to specify the virtual port (if one has been activated for this channel) on a BXM card. The slot, port, and VPI will automatically map to the correct virtual port.
Frame Relay class	Specifies a Frame Relay class. Entering a Frame Relay class is a shortcut for specifying bandwidth parameters. You must enter a Frame Relay class, but then you can modify any of the bandwidth parameters specified by the class. To do so, do not press Return after you type the class number but continue typing either a value for the parameter or a * to keep the current value. The system does not display the parameters, but the description of the frp_bw parameters in the "Optional Parameters" table that follows shows the order and ranges of the parameters you can specify.
con_type	Optionally specifies the type of ATM-to-Frame Relay service interworking. (If the connection is Frame Relay-to-Frame Relay, the network selects any necessary interworking.) The possible con_type entries are atft and atfx. To specify service interworking in transparent mode, type atft. To specify service interworking in translation mode, type atfx. In translation mode, a standard set of encapsulation protocols are translated. If system software does not recognize an encapsulation protocol for an atfx connection, it generates one of two Frame Relay endpoint statistics: rcvFramesDscdUnknownProtocol or xmtFramesDscdUnknownProtocol.
frp_bw	Optionally specifies individual bandwidth parameters. The parameter name "frp_bw" is the label for the bandwidth parameters described here. The slash (/) between the repeated parameter name shows that you can specify a value for each direction. (FST is the exception.) Two parameters can be either the (default) Cisco versions or the Frame Relay Forum standard parameters. To switch between Cisco and Frame Relay Forum, use the cnfsysparm command. Note that all parameters you select with cnfsysparm are network-wide and not confined to the current connection addition. The switchable parameters are: •Cisco Parameters Standard Parameters •PIR (peak information rate) Be (excess burst) •VC_Q (VC queue depth) Bc (committed burst) When you are using the Cisco parameter set, the names and order of specification are: MIR/MIR, CIR/CIR, VC_Q/VC_Q, PIR/PIR, Cmax/Cmax ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl When you are using the parameters with the two Frame Relay Forum versions, the names and order of specification are: MIR/MIR, CIR/CIR, Bc/Bc, Be/Be, Cmax/Cmax, ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl For the definition of each parameter and important information on setting CIR=0, refer to the appropriate installation and configuration guide.
avoid	Optionally specifies the type of trunk or route to avoid for the connection. The default is no avoidance. To specify an avoid value, type it after the Frame Relay class or—if you override the Frame Relay class—after the frp_bw values. Be sure to include the asterisk (*). The avoid parameters are: *s = Avoid satellite trunks. *t = Avoid terrestrial trunks. *z = Avoid trunks using zero-code suppression techniques that modify any bit position to prevent long strings of zeros.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	IGX, (BPX service internetworking)			Yes

Related Commands

delcon, dncon, dspcon, dspcons, upcon

Example (local addressing)

Execute these commands at node Alpha to configure the network shown in Figure 3-1.

addcon 6.1.100 beta 6.2.200 3

addcon 6.1 101 delta 4.1.102 2

addcon 4.1.100 beta 6.2.101 4

addcon 4.1.200 gamma 5.1.300 1

Figure 3-1 Local Addressing Example

Example

Add a connection between the user-device at alpha port 9.1 and the user-device at gamma port 8.1. The user-device at alpha refers to the connection using local DLCI 200. The user-device at gamma refers to this connection using local DLCI 300. The DLCIs have only local significance, so a DLCI must apply to only one connection.

addcon 9.1.200 gamma 8.1.300 1

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 10:12 PST 

Local      		Remote	     Remote		                                        Route   

Channel    		NodeName   Channel    	State   	Type  Compression   Code   Avoid	    CoS	   O 

 5.1		       beta		       25.1       Ok		      256	                 7/8			             0	     L 

 9.1.100   gamma      8.1.200	    Ok      	fr				                  0	                     L 

 9.1.200   gamma	      8.1.300	    Ok	      fr                  				0                     	L 

 9.2.400		   beta	       19.2.302	   Ok	      fr                  				0                     	L 

 14.1      		gamma      15.1	       Ok	      v                   				0                     	L 

Last Command: addcon 9.1.200 gamma 8.1.300 1                                    

Next Command: 

Example

Add another connection at local port 9.1. A DLCI of 100 is used at the local node. A DLCI of 300 can be used at both beta gamma because the DLCIs have only local significance.

addcon 9.1.100 beta 6.2.300 2

Example (global addressing)

The network to configure in this example is shown in Figure 3-2.

addcon 6.1.80 beta 9.2.79 2
addcon 6.1.81 gamma 4.1.79 1
addcon 4.1.80 beta 6.2.81 5

Figure 3-2 Global Addressing Example

Example (bundle connections)

Add a bundle of connections between Frame Relay ports 8.1-3 on node gamma and 19.2-4 on node alpha. For this bundle, the network routes traffic between gamma port 8.2 and alpha port 19.2.

addcon 8.1x3 alpha 19.2x4 1

pubsigx3       VT    SuperUser       IGX 8410     9.3 Apr. 13 2000  19:41 GMT

 Local          Remote      Remote

 Channel        NodeName    Channel         State  Type      Compress  Code CoS

     8.1x3      alpha      19.2x4     Ok     fr

This Command: addcon 8.1x3 alpha 19.2x4 1

Add these connections (y/n)?

Example (frame forwarding)

Add a frame forwarding connection between the local node's port 8.2 and 19.2 on node alpha.

addcon 8.2.* alpha 19.2.* 1

Locals       Remote      Remote                                        Route  

Channel      NodeName    Channel   State    Type   Compression  Code   Avoid  CoS   O 

6.1          beta        25.2       Ok      256                 7/8           0     R 

8.1.200      alpha       9.1.100    Ok      fr                                0     R 

8.2.300      beta        19.1.101   Ok      fr                                0     R 

15.1         alpha       14.1       Ok      v                                 0     R 

This Command: addcon 8.2.* alpha 19.2.* 1                                        

Add these connections (y/n)?      

Example (modifying bandwidth)

Parameters specified by Frame Relay class 7 for this connection are modified by substituting 30 for Cmax in both directions, enabling ForeSight, and reducing percent utilization from 100 percent to 80 percent.

addcon 8.3.101 beta 19.3.201 7 * * * * 30/30 * * Y 80/80

gamma          TRM   YourID:1        IGX 8410    9.3   Apr. 13 2000 12:10 CST 

 Local      Remote      Remote                                     Route       

 Channel    NodeName    Channel    State  Type   Compression  Code Avoid CoS O 

 6.1        beta        25.2        Ok     256                 7/8         0  R 

 8.1.200    alpha       9.1.100     Ok     fr                              0  R 

 8.2.300    beta        19.1.101    Ok     fr                              0  R 

 15.1       alpha       14.1        Ok     v                               0  R 

Last Command: dspcons                           

Next Command: addcon 8.3.101 beta 19.3.201 7 * * * * 30/30 * * Y 80/80 

addcon (add an ATM connection)

Establishes an ATM connection between the current node another node in the network. ATM connections are added to UNI or NNI ports on ASI or BXM interface cards in a BPX node and UXM or URM interface cards in an IGX node. Before a connection is added, you are prompted to confirm the connection addition. After addcon executes, the system software automatically routes the connection.

The addcon command for ATM adds any one of the following types of ATM connections:

•Constant Bit Rate (CBR)

•Variable Bit Rate (VBR)—rt-VBR and nrt-VBR

•Frame Relay-to-ATM interworking connection (ATFR)

•Frame Relay-to-ATM interworking with ForeSight (ATFST) connection

•Available Bit Rate according to ATM Forum standards (ABRSTD)

•Available Bit Rate with ForeSight (ABRFST)

•Frame Relay-to-ATM transparent Service Interworking (ATFT)

•Frame Relay-to-ATM transparent Service Interworking with Foresight (ATFTFST)

•Frame Relay-to-ATM translational Service Interworking (ATFX)

•Frame Relay-to-ATM translational Service Interworking with Foresight (ATFXFST)

•Unspecified Bit Rate (UBR)

Frame Relay-to-ATM Interworking enables Frame Relay traffic to be connected across high-speed ATM trunks using ATM standard Network and Service Interworking. Two types of Frame Relay-to-ATM interworking are supported, Network Interworking and Service Interworking.

You can add connections to a virtual port on a BXM card. When adding a connection to a virtual port, the virtual port number is not required. The slot, port, and VPI will map to the supporting virtual port. In addition, Vc QDepth is configurable for all connection types.

The node on which addcon executes is the "owner" of the connection. Automatic rerouting and preferred routing information is entered on the node that owns the connection. See the cnfpref and cnfcos descriptions for details on automatic rerouting.

If addcon is attempted on a port with F4-F5 mapping enabled, and there are no channels left for F4-F5 mapping, the following message is displayed: "No channel left for F4-F5 mapping on this portgroup." If channel unavailability occurs at the remote end, the following message is displayed: "No channel left for F4-F5 mapping on this portgroup at the remote end."

For detailed descriptions of the connection types, traffic classes, policing, and ATM-related topics, refer to the Cisco BPX 8600 Series Installation and Configuration guide or the ATM Forum specifications.

Syntax

addcon <local_channel> <remote_node> <remote_channel> [connection_class] [individual parameters]

Parameters

The addcon parameter prompts depend on the connection type. The following two tables define the parameters and list the defaults and ranges for each parameter.

The notation (0), (1), or (0+1) appears for some parameters. This refers to the state of the Cell Loss Priority (CLP) bit. The usage of the CLP bit is in the traffic policing schemes: (0+1) means cells with CLP=0 or 1; (0) means cells with CLP=0; (1) means cells with CLP=1. The CLP bit is used in different contexts. For example, CDVT (0+1) refers to Cell Delay Variation Tolerance (CDVT) for cells with CLP=0 or 1.

Parameter	Description
local channel	Specifies the local slot, port, virtual path identifier (VPI), and virtual connection identifier (VCI) for the connection. The format is slot.port.vpi.vci. You do not need to specify the virtual port (if one has been activated for this channel). The slot, port, and VPI will automatically map to the correct virtual port. The VPI range for a UNI connection is 1-255. The VPI range for an NNI connection is 1-4095. When adding an MGX 8850 interface shelf with a UNI interface to a BPX routing node, the VPI range is 1-255. The VCI range is 1-65535. When adding an MGX 8850 interface shelf with an NNI interface to a BPX routing node, the VPI range is 1-255. The VCI range is 1-65535. When adding an SES (Service Expansion Shelf) to an IGX 8400 routing node, for VCC addressing, the VPI range is 1-255. The VCI range is 1-65535. For VPC addressing, when adding an SES interface shelf to an IGX 8400 routing hub with a UNI interface, the VPI range is 1-255. The VCI range is 1-65535. For VPC addressing, when adding an SES shelf to an IGX 8400 routing with an NNI interface, the VPI range is 1-4095. The VCI range is 1-65535. Note that when adding an SES to an IGX 8400 routing node, the VPI/VCI configured on the IGX 8400 routing hub should match the VPI/VCI configured on the SES interface shelf endpoint address. When adding a VP tunnelling DAX connection to an IGX UXM card, either end of the connection can be the VPI or VCI side. This connection type can be any of the ATM connection types supported by UXM virtual trunks, for example, ABR, CBR, UBR, and VBR. The VCI range is 1-65535. The VCI can be an asterisk (*) to indicate the connection is a virtual path connection (so the VCI has no meaning within the network). Note The VCI cannot be less than 33, if F4-F5 mapping is enabled on the port.
remote node name	Specifies the name of the node at the other (or remote) end of the connection.
remote channel	Specifies the remote node's slot, port, VPI, and VCI for this connection. The format is slot.port.vpi.vci. The VPI and VCI ranges are: The VPI range for a UNI connection is 1-255. The VPI range for an NNI connection is 1-4095. The range for a VCI is 1-65535. The VCI can be an asterisk (*) to indicate the connection is a virtual path (the VCI does not provide a distinction within the network). Note The VCI cannot be less than 33, if F4-F5 mapping is enabled on the port. You do not need to specify the virtual port (if one has been activated for this channel). The slot, port, and VPI will automatically map to the correct virtual port.
connection class/ traffic type	Specifies one of the following traffic types—VBR (rt-VBR or nrt-VBR), UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, or ATFXFST; or connection classes—for example, for rt-VBR, connection class 3 for a new node running Release 9.2.20. The subsequent displayed parameters depend on the connection type you choose. To see the parameters associated with each connection type, refer to the appropriate flow diagrams in the Cisco BPX 8600 Series Installation and Configuration guide. Instead of entering a class of service, you can choose a class number. The class number represents a preconfigured template for a connection type. The class serves as an alternative to specifying each parameter for a connection type. For example, class 4 for nrt-VBR, and class 3 for rt-VBR. To specify a connection class, enter a digit in the range 1-10. To see the parameter values for a class, use the dspcls/dspatmcls commands. To customize any class template, use the cnfcls/cnfatmcls commands. Note For a new node running 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes and will not have the rt-VBR connection class 3. However, you can configure the connection classes to whatever service and parameters you want by using the cnfcls/cnfatmcls commands. Note For VP tunnelling DAX connections, a VP tunnelling connection type is represented by CBRVP, ABRSTVP, ABRFSTVP, and so on. The letters VP are appended to the connection class or connection type, to indicate that it is a VP tunnelling connection. This connection type must be the same as the VCC connection type provisioned within the public ATM cloud.
PCR	Peak Cell Rate: the cell rate that the source cannot exceed.
%Util	Specifies the percentage of bandwidth utilization.
MCR	Minimum Cell Rate: the committed, minimum cell rate for a connection in a network.
CDVT	Cell Delay Variation Tolerance: controls policing tolerance for cells which are early or late relative to the PCR.
FBTC (AAL5 Frame-based Traffic Control)	Enables the possibility of discarding the whole frame, not just one non-compliant cell. This is used to set the Early Packet Discard bit at every node along a connection. With the ASI, FBTC means packet discard on both policing and queueing. With the BXM, FBTC means packet discard on queueing only.
VSVD	Virtual Source Virtual Destination.
Flow Control External Segments	Enables Cisco WAN switches to perform flow control on external segments (on the CPE, for example) in addition to the Cisco WAN Switching segments.
SCR	Sustainable Cell Rate: the long-term limit on the rate that a connection can sustain.
MBS	Maximum Burst Size: the maximum number of cells that can burst at the PCR and still be compliant. MBS is used to determine the Burst Tolerance (BT), which controls the time period over which the SCR is policed.
Policing	Selects the type of policing to be applied to this connection. Possible values are 1-5. See Table 3-15 for details about each of the five policing modes.
VC QDepth	The depth of the queue VC QDepth. As of Release 9.3, VC QDepth can be configured for all connections, not just ABR connections.
CLP Hi	Cell Loss Priority Hi threshold (% of VC QDepth). When the high threshold is exceeded, the node discards cells with CLP=1 until the number of cells in the queue drops below the level specified by CLP Lo/EPD. As of Release 9.3, CLP Hi can now be configured for all connections, not just ABR connections.
CLP Lo/EPD	Cell Loss Priority Low threshold (% of VC QDepth)/Early Packet Discard. When the number of cells in the queue drops below the level specified by CLP Lo/EPD, the node stops discarding cells with CLP=1. If the card is a BXM and AAL5 FBTC=yes, the percent of VC QMax equals the value of EPD. Frame-based Traffic Control (FBTC) is FGCRA for AAL5. For an ASI card, the percent of VC QMax is CLP Lo regardless of the FBTC setting. As of Release 9.3, CLP Lo/EPD can now be configured for all connections, not just ABR connections.
EFCI	Explicit Forward Congestion Indication threshold (% of VC QDepth).
ICR	Initial Cell Rate: the rate at which a source initially transmits after an idle period.
IBS	Initial Burst Size: the maximum burst size a source can initially transmit after an idle period. IBS applies only to BXM cards.
ADTF	The Allowed-Cell-Rate Decrease Factor. Time permitted between sending RM cells before the rate is decreased to ICR. (In previous software releases, ADTF was ICR TO—Initial Cell Rate Time Out.)
Trm	An upper bound on the time between forward RM-cells for an active source: an RM cell must be sent at least every Trm milliseconds. (In previous software releases, Trm was Min. Adjust.)
RIF	Rate Increase Factor: controls the amount by which the cell transmission rate may increase upon receipt of an RM cell. (In previous software releases, RIF was Rate Up.)
RDF	Rate Decrease Factor: controls the amount decrease in cell transmission rate when an RM cell arrives. (In previous software releases, RDF was Rate Down.)
Nrm	Nrm. Maximum number of cells a source may send for each forward RM cell: an RM cell must be sent for every Nrm-1 data cells.
FRTT	Fixed Round Trip Time: the sum of the fixed and propagation delays from the source to a destination and back.
TBE	Transient Buffer Exposure The negotiated number of cells that the network would like to limit the source to sending during start-up periods, before the first RM-cell returns.

Table 3-13 addcon—Parameter Defaults and Ranges 

Parameter with Default Settings	UXM and BXM T1/E1, T3/E3, OC-3, and OC-12 RANGE	ASI Range
PCR(0+1)[50/50]	50-max. T1/E1 cells/sec 50-max. T3/E3 cells/sec 50-max. OC-3 cells/sec 50-max. OC-12 cells/sec	T3: MCR-96000 E3: MCR-80000 OC-3 (STM1): 0-353200 Limited to MCR-5333 cells/sec for ATFR connections.
%Util [100/100] for UBR [1/1]	0-100%	1-100%
MCR [50/50]	cells/sec 6-max. of T3/E3/OC-3/OC-12	T3: 0-96000 cells/sec E3: 0-80000 cells/sec
AAL5 Frame-Based Traffic Control: for rt/nrt-VBR [disable] for ABR/UBR [enable] for Path connection [disable]	enable/disable With the BXM card, FBTC means packet discard on queueing only.	enable/disable With the ASI card, FBTC means packet discard on both policing and queueing.
CDVT(0+1): for CBR [10000/10000], others [250000/250000]	0-5,000,000 microsecs.	T3/E3 1-250,000 usecs. OC-3/STM1: 0-10000 usecs.
ForeSight [disable]	0 = disable 1 = enable	0 = disable 1 = enable
VSVD [disable]	enable/disable	enable/disable
Flow Control External Segment [disable]	enable/disable	enable/disable
Default Extended Parameters [enable]	enable/disable	enable/disable
CLP Setting [enable]	enable/disable	enable/disable
SCR [50/50]	c50-max. T1/E1 cells/sec 50-max. T3/E3 cells/sec 50-max. OC-3 cells/sec 50-max. OC-12 cells/sec	T3: MCR-96000:T3 E3: MCR-80000: E3 OC-3/STM1: 0-353200 Limited to MCR-5333 cells/sec for ATFR connections.
MBS [1000/1000]	1-5,000,000 cells	T3/E3: 1-24000 cells OC-3 (STM1): 10-1000 cells
Policing [3] For CBR: [4]	1 = VBR.1 2 = VBR.2 3 = VBR.3 4 = PCR policing only 5 = off	1 = VBR.1 2 = VBR.2 3 = VBR.3 4 = PCR policing only 5 = off
ICR: max [MCR, PCR/10]	MCR - PCR cells/sec	MCR - PCR cells/sec
ADTF [1000]	62-8000 msecs.	1000-255000 msecs.
Trm [100]	ABRSTD: 1-100 msecs. ABRFST: 3-255 msecs.	20-250 msecs.
VC QDepth [16000/16000] For ATFR/ATFST [1366/1366]	0-61440 cells	Applies to T3/E3 only ABR: 1-64000 cells ATFR: 1-1366 cells
CLP Hi [80/80]	1-100%	1-100%
CLP Lo/EPD [35/35]	1-100%	1-100%
EFCI [30/30] For ATFR/ATFST [100/100]	1-100%	1-100%
RIF: For ForeSight: = max [PCR/128, 10] For ABRSTD [128]	If ForeSight, then in absolute (0-PCR) If ABR, then 2n (1-32768)	If ForeSight, then in absolute (0-PCR) If ABR, then 2n (1-32768)
RDF: For ForeSight [93] For ABRSTD [16]	IF ForeSight, then % (0%-100%) If ABR, then 2n (1-32768)	If ForeSight, then % (0%-100%) If ABR, then 2n (1-32768)
Nrm[32]-BXM only	2-256 cells	not applicable
FRTT[0]-BXM only	0-16700 msec	not applicable
TBE[1,048,320]-BXM only	0-1,048,320 cells different maximum range from TM spec. but limited by firmware for CRM (4095 only) where CRM=TBE/Nrm	not applicable
IBS [0/0]	0-24000 cells	T3/E3 ABR: 0-24000 cells ATFR: 1-107 cells OC-3: 0-999 cells
Trunk Cell Routing Restriction (y/n) [y]	yes or no For rt-VBR connections, this prompt will not display.	yes or no For rt-VBR connections, this prompt will not display.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX, IGX			Yes

Related Commands

delcon, dspcons

Example

Add a standard ABR connection with VSVD and no Default Extended Parameters (which then require user input for SCR, MBS, and so on).

addcon 9.1.100.100 pubsbpx2 9.1.102.102

pubsbpx1       TN    SuperUser       BPX 15    9.3 Apr. 13 2000 05:22 GMT 

 From            Remote      Remote                             Route

 9.1.100.100     NodeName    Channel         State  Type        Avoid CoS O

 9.1.100.100     pubsbpx2 	9.1.102.102     Ok     abrstd

 9.1.102.102     pubsbpx2 	9.1.100.100     Ok     abrstd

This Command: addcon 9.1.100.100 pubsbpx2 9.1.102.102 abr * * * * e e * d * * 1

* * * * * * * * *

Add these connections (y/n)? 

Example

Add a virtual path connection (VPC) to virtual circuit connection (VCC) between ports 1 and 2. (This is called a VP tunnelling connection.)

addcon 5.2.10.* pubsigx1p 5.1.1.100 CBR ...

pubsigx1       TN    SuperUser     IGX 8400    9.3   Apr. 13 2000 05:22 GMT 

 From          Remote        Remote                            Route

               NodeName      Channel       State   Type        Avoid CoS O

 5.2.10.*      pubsigx2      5.1.1.100     Ok      abrstvp

 5.1.1.100     pubsigx2 	     5.2.10.*    s  Ok      abrstvp

This Command: addcon 5.2.10.* pubsigx1p 5.1.1.100 CBR ...

Add these connections (y/n)? 

PCR Values and Traffic Policing

The following three tables provide additional information on PCR values and traffic policing. Table 3-14 defines the minimum PCR values with policing for each card type. Table 3-15 provides traffic policing definitions for each connection type.

Table 3-14 Minimum PCR Values with Policing Enabled 

Card Name	Card Types	Minimum PCR Values with Policing
IGX-UXM	T1/E1	6 cps
IGX-UXM	T3/E3	12 cps
IGX-UXM	OC-3/STM-1	50 cps
BPX-BXM	T3/E3	12 cps
BPX-BXM	OC-3/STM-1	50 cps
BPX-BXM	OC-12/STM-4	50 cps
Note The policing accuracy is always within one percent. The maximum PCR policing values are the same as the line rate.

Table 3-15 Traffic Policing Definitions 

Connection Type	ATM Forum TM spec. 4.0 conformance definition	PCR Flow (1st leaky bucket)	CLP tagging (for PCR flow)	SCR Flow (2nd leaky bucket)	CLP tagging (for SCR flow)
CBR	CBR.1 when policing set to 4 (PCR policing only)	CLP(0+1)	no	off	n/a
CBR	when policing set to 5 (off)	off	n/a	off	n/a
UBR	UBR.1 when CLP setting = no	CLP(0+1)	no	off	n/a
UBR	UBR.2 when CLP setting = yes	CLP(0+1)	no	CLP(0)	yes
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTFST, ATFX, ATFXFST	VBR.1 when policing set to 1	CLP(0+1)	no	CLP(0+1)	no
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTFST, ATFX, ATFXFST	VBR.2 when policing set to 2	CLP(0+1)	no	CLP(0)	no
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTFST, ATFX, ATFXFST	VBR.3 when policing set to 3	CLP(0+1)	no	CLP(0)	yes
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTFST, ATFX, ATFXFST	when policing set to 4	CLP(0+1)	no	off	n/a
rt/nrt-VBR, ABR, ATFR, ATFST, ATFT, ATFTFST, ATFX, ATFXFST	when policing set to 5 (off)	off	n/a	off	n/a
Note 1: - For UBR.2, SCR = 0 Note 2: CLP = Cell Lost Priority CLP(0) means cells that have CLP = 0 CLP(1) means cells that have CLP = 1 CLP(0+1) means both types of cells: CLP = 0 & CLP = 1 CLP(0) has higher priority than CLP(1) CLP tagging means to change CLP = 0 to CLP = 1, where CLP= 1 cells have lower priority

addctrlr (add a VSI controller to an IGX node)

Add VSI controller to a UXM line interface. Use the addctrlr command to add an VSI controller to UXM line interface on an IGX node. You can connect a VSI controller to an IGX node by physically connecting a cable from the controller to the UXM line interface.

You cannot connect a VSI controller to these interfaces:

•trunk

•virtual trunk

•feeder trunk

•IMA ports

The maximum number of controllers that can be added to an IGX is three, although the valid controller ID range is 1 to 16.

Syntax

addctrlr < slot.port> <controller id> <partition id> <control_vpi> <start_vci>

Parameters

Parameter	Description
<slot.port>	Slot and port numbers corresponding to the line or port to which a controller is attached.
<controller id>	Controller ID corresponding to the MPLS controller. Range: 1-16
<partition id>	Partition ID of the VSI partition controlled by the MPLS controller. Range: 1-3
<control_vpi>	VPI of the VSI control channels used for communication between the VSI master residing on the MPLS controller and VSI slaves residing on the UXM cards. For a 16-slot IGX there are a total of 14 such channels. For a 32-slot IGX there are a total of 30 such channels. For a line interface with NNI header type: Range: 0-4095 For a line interface with UNI header type Range: 0-255 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 UXM card in slot 3). The last VSI control channel corresponding to communication with the VSI slave on slot 16 or 32 (depending on the number of slots in the particular IGX model) will use the VCI value of (<start_vci> + number of slots on the IGX - 2). Range for 16-slot IGX: 40-65521 Range for 32-slot IGX: 40-65505 Default value: 40

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1	No	Yes	BPX, IGX	Yes	Yes	Yes	Yes

Related Commands

delctrlr, dspctrlrs

Example

Add controller to port 1 on slot 12, partition ID of 2 and controller ID of 3.

addctrlr 12.1 3 2 0 40

arnold         TN    Cisco           IGX 8430  9.3.10    Aug. 16 2000 17:04 PST 

                   VSI Controller Information

CtrlrId   PartId     ControlVC            Intfc    Type     CtrlrIP

                    VPI    VCIRange

   3         2       0      40-70          12.1     MPLS     0.0.0.0

Last Command: addctrlr 12.1 3 2 0 40

Controller added successfully!

Next Command: 

addctrlr (add VSI capabilities to an AAL5 feeder interface (BPX))

Adds VSI capabilities to a trunk interface to which a feeder of type AAL5 is attached. Use the addctrlr command to connect a Private Network-to-Network Interface (PNNI) controller. PNNI controller software resides on the Service Expansion Shelf (SES) hardware.

To add a PNNI controller to a BPX node:

---

Step 1 Run the command addshelf with shelf type set to X to add an AAL5 feeder. This ensures that Annex G protocol runs between the BPX and the SES.

Step 2 Run the addctrlr command to set up the VSI control channels from the PNNI SES controller to the VSI slave processes running on the BXM cards to ensure full VSI functionality for the PNNI controller. Execute the addctrlr command on an existing AAL5 interface shelf.

---

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. For example, if a PNNI controller controlling partition 1 were added to a 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 adding VSI controller capabilities to an AAL5 interface shelf (or feeder), the switch software prompts you for the specifics of the VSI controller:

•controller ID of the PNNI controller

•partition ID of the VSI partitions controlled by the PNNI controller

•VPI used for the VSI control channels set up by the PNNI controller

•start_VCI value for the VSI control channels set up by the PNNI controller

The PNNI controller controls 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.

Example: 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, start_VCI values <0, 40>. The VSI control channels to other slots would use the VPI, start_VCI values of <0, 40+slot-1>, where "slot" corresponds to the slot number of the BXM card.

---

Caution For feeder trunk interfaces, the addctrlr command will fail if the Automatic Routing Management connections terminating on the feeder interface use the same VPI start_VCI as those specified for the VSI control channels. You must delete the connections before proceeding if connections with VPI and start_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.

Syntax

addctrlr < slot.port> <controller id> <partition id> <control_vpi> <start_vci>

Parameters

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: Range: 0-4095 For a trunk interface with UNI header type: Range: 0-255 Default: 0 Note For a PNNI controller, do not modify control_vpi and start_vci.
<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). Range: 33-65521 Default: 40 Note For a PNNI controller, do not modify control_vpi and start_vci.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1	No	Yes	BPX, IGX	Yes	Yes	Yes	Yes

Related Commands

addshelf, delctrlr, dspctrlrs

Example

Add controller to port 4 on slot 10, partition ID of 2, and controller ID of 3.

addctrlr 10.4 3 2 0 40

night           TN   StrataCom     BPX 8600   9.3.10 Aug. 1 2000 14:31 GMT  

		BPX 8620 VSI controller information

Ctrl Id 	Part Id 	Control_VC 	Trunk 	Ctrlr Type 	Intfc 

		VPI  VCIRange

	1	1 	0 	40-54 	10.3 	VSI 	VSI

	2 	2 	0 	40-54 	11.1 	VSI 	VSI

Warning partition already in use do you want to add redundant controller                                                                         

Last Command: addctrlr 10.4 3 2 0 40 

Next Command:      

Example

Adds a controller, such a PNNI controller, to a BPX interface shelf.

addctrlr 10.3 3 1 0 40

night           TN   StrataCom     BPX 8600   9.3.10 Aug. 1 2000 14:31 GMT  

		BPX 8620 VSI controller information

Ctrl Id 	Part Id 	Control_VC 	Trunk 	Ctrlr Type 	Intfc 

		VPI  VCIRange

	1	1 	0 	40-54 	10.3 	VSI 	VSI

	2 	2 	0 	40-54 	11.1 	VSI 	VSI

Warning partition already in use do you want to add redundant controller                                                                         

Last Command: addctrlr 10.3 3 1 0 40 

Next Command:      

addextlp (add external loop)

Places an external device in loopback mode. The addextlp command applies to existing connections on an SDP, HDM, LDP, or LDM. A near loopback causes the NEAR EIA template to be applied. A far loopback causes the FAR EIA template to be applied to the data port. The loopback remains in place until removed by the dellp command.

The dspcons command shows which connections are in loopback mode. Specifying an "n" after the channel indicates a near loopback, and an "f" indicates a far loopback. Because addextlp takes the specified connections out of service, use it only when a service disruption is tolerable.

Syntax

addextlp <channel> < n | f >

Parameters

Parameter	Description
channel	Specifies the channel to loopback in the format slot.port.
n | f	Specifies whether the loopback is near or far. An "n" specifies near; an "f" specifies far. For a non-DDS port, the near or far modem is placed in loopback, if it supports this function. For a DDS port, the external DDS device is placed in CSU loopback. Local channels must be configured as OCU in order to place them in external loopback.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	IGX			Yes

Related Commands

dellp, dspcons

Example

Place the device connected to channel 5.1 in near loopback.

addextlp 5.1 n

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 12:53 PST 

 Local      Remote      Remote                                      Route       

 Channel    NodeName    Channel    State  Type    Compression  Code Avoid CoS O 

 N5.1       beta        25.1       Ok     256                  7/8         0  L 

 9.1.100    gamma       8.1.200    Ok     fr                               0  L 

 9.2.400    beta        19.2.302   Ok     fr                               0  L 

 14.1       gamma       15.1       Ok     v                                0  L 

Last Command: addextlp 5.1 n                                                    

Next Command:   

addjob (add a job)

Creates a job or command script. When you create a new job by using addjob, your privilege level becomes the privilege level of the job itself. When adding commands to the job, you cannot add a command that requires a privilege higher than your privilege level. Furthermore, you must have a privilege level at least as high as the job to run the job (with runjob, for example).

The system does not check the validity of the command with respect to the current state of the network or for relationships to other commands in the job. To ensure that it works as expected, try running the job with runjob.

Syntax

addjob [description] [execution time, execution interval] <commands>

Parameters

Parameter	Description
command	Specifies the syntax for a command to include in the job. The number of commands that can be included in a job is limited only by available memory. Not all commands can be included in a job. A job cannot contain commands that are above your privilege level. For example, if you have privilege level 3, your job cannot include the addtrk command because this command requires privilege level 1.
failure reaction	Specifies the desired reaction to the failure of a command in the job. Each command in the job must have a failure reaction. The failure reaction is specified in the following format <c | a | rc | ra> <number of repetitions>. In this format: c specifies that the job continues running. a specifies that the job must abort. rc specifies that the command should retry for the specified number of times and continue running the job even if the command fails during the retries. ra specifies that the command should retry for the specified number of times and abort the job if the command always fails during the retries.
job description	A user-specified description of the job. This description can be up to 16 characters, including spaces.
execution time	Specifies the date and time to run the job. Without an execution time, the job can begin running only by the runjob command. Execution time is specified in the following format. (The seconds parameter is optional.) year (four digits) month (two digits) day hour (0-23) minute [seconds]
execution interval	Specifies an interval between job repetitions. The three possible execution intervals are: d (days) h (hours) m (minutes) The interval range is 1 minute to 45 days. If you do not specify an execution interval, the job runs once at execution time. If you specify an execution interval (d, h, or m), you must also specify the number of units in the interval.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-6	No	Yes	BPX, IGX			Yes

Related Commands

deljob, dspjob, dspjobs, editjob, prtjob, runjob, stopjob

Example

The system response is a series of prompts requesting details of the job. The system requests a job description (or name), an execution time for the job, a unit for the interval at which the job is to run (hours, for example), the number of units in the interval, the commands to execute, and what to do with the result.

addjob

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 14:15 PST 

                                  Job 1   test                                  

Last Execution Results: None                     Status: Idle                   

Next Execution Time: 08/17/97 20:20:30           Interval: 1 days               

 1: prtlog                                                                      

   - Failure Reaction: Repeat 2 Times and Abort        Exec. Results: None      

Last Command: addjob                                                            

Next Command:      

In this example, a new job is being created. The job number is "1." The job description (or name) is "test." The job is scheduled to run on August 17, at 2:20:30 PM and every day thereafter at the same time. The command in the job is prtlog. If this command fails when the job runs, it tries twice again and aborts if unsuccessful.

The "Enter Cmd" prompt at the bottom of the screen indicates you can enter the next command for the job. To exit addjob, press Return without entering a command.

addjobtrig (add job trigger)

Configures a job to run if a failure or repair occurs on a trunk (narrowband or broadband), a line (voice, data, Frame Relay, ATM, narrowband, broadband), or a T3 (DS3). You can also use addjobtrig to allocate or release bandwidth from other connections. This bandwidth decision depends on whether the EIA lead status is "up" or "down." For example, a job can be triggered to run if the RTS lead of an HDM/LDM port changes state. If the FRM you are using is an FRM-T1 or E1, it qualifies as a line and can be used as a job trigger.

A line failure is any alarm condition that takes the trunk or line out of service. Such a condition is always a major alarm. However, not all major alarms cause the trunk or line to be considered failed. Those that are considered failed are the ones that appear on the dsptrks or dsplns screens with a color associated with it, such as "Major—Local All Ones" or "Major—Remove Packet Out of Frame (Yel)". Specifically excluded are all the statistical alarms, some of which may be major.

A line repair is the opposite of a line failure. A repair of a line occurs when the alarms on the line are removed.

The lead type on HDM/LDM is based on the configuration from cnfleadmon. The display shows: "Front Card Supports Lead State Trap".

Syntax

addjobtrig <job_number> <line_type> <line_specifier> <fail/repair>

Parameters

Parameter	Description
job number	Specifies the number of the job to trigger.
line type	Specifies the type of line. A "p" indicates any type of trunk (TRK). A "c" indicates any type of circuit line. (A "d" indicates a DS3 line. Do not specify the "d" option; this represents an obsolete card—the MT3.)
line specifier	Specifies the slot number for trunks and lines. Use the standard nomenclature to designate trunks and lines. For example, depending on the card type (single-line or multi-line), specify either <slot.port>, or just <slot>.
fail/repair	Specifies whether the trigger occurs on the failure or repair of a line. If the card is an SDP, LDP, HDM, or LDM, the fail and repair triggers occur only on the transitions of RTS (regardless of whether the port is DCE or DTE). If you select fail, the trigger is the transition of RTS from on to off. If you select repair, the trigger is the transition of RTS from off to on. To enable triggering on leads other than RTS, use the cnfict command.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	No	BPX, IGX			Yes

Related Commands

addjob, dspjob, dspjobs

Examples

addjobtrig	1 p 14 f	trigger job 1 when TRK 14 fails
addjobtrig	3 c 15 r	trigger job 3 when CLN 15 repairs
addjobtrig	2 p 14 r	trigger job 2 when TRK 14 repairs
addjobtrig	3 d 27 E f	trigger job 3 when DS3 27 E (East) fails

Example

Trigger job 1 whenever a repair of line 14 occurs.

addjobtrig 1 c 14 r

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 14:22 PST 

Job   Description       Next Execution      Status     Interval    Access Group 

1     test              08/17/97 11:00:00   Idle       1 days      Group 1      

      Trigger 1 -  CLN 14         REPAIR                                        

Last Command: addjobtrig 1 c 14 r                                               

Next Command:        

addlnloclp (add local loopback to line)

Establishes a local-remote loopback on a trunk or port card in a BPX. Applicable cards are the ASI, BNI, BME, and BXM.

While a line loop is present, software suspends the card self-test and the line diagnostic test that normally run when a line goes into alarm. Suspending these tests prevents background test loops from interfering with the user-specified loop.

Line loops are set for a line on the local node, so you cannot specify a remote node, and no network messaging is supported for setting a line loop of any type on a remote node.

Line loop status is displayed on the dsplns screen for an ASI, BME, or a BXM in port mode and the dsptrks screen for a BNI, BME, or a BXM in trunk mode. Line loop status is not displayed for connections (dspcons) affected by a line loop. Instead, a warning is printed if the line has connection traffic travelling on it, and an event is logged when a line loop is set or cleared. A line loop on a trunk generates Comm Fail, causing connections to fail and be rerouted.

For both of the dsplns and dsptrks screens, the "[" character appears before the back card type in the "Type" column to indicate that the line local loopback is active.

The line loop state is not saved in BRAM or on a rebuild but is preserved on a switchover. After a rebuild, a line's loop state is cleared.

Exercise caution when you set up loops on a BNI, BME, or BXM trunk because looping an added BNI/BXM/BME trunk causes Comm Failure and connection rerouting. BNI/BXM/BME addlnlocrmtlp is not supported because of a lack of useful purpose, and Cisco recommends that you use addlnloclp only when the trunk is upped but not added. On the other hand, the system does not prevent you from looping an added BNI/BXM/BME trunk port.

Syntax

addlnloclp <slot.port>

Parameters

Parameter	Description
slot.port	Specifies the port.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX			Yes

Related Commands

dellnlp, dsptrks, dsplns, addlnlocrmtlp

Example

The dsplns display appears with the connection highlighted and a prompt for confirmation.

addlnloclp 11.8

sw53           VT    Cisco           BPX 8620  9.3.m0    Dec. 14 2000 12:33 GMT

Line      Type     Current Line Alarm Status

11.1      OC3      Clear - OK

11.8     ]OC3      Clear - OK

Last Command: addlnloclp 11.8 

addlnlocrmtlp (add local-remote loopback to BPX line)

Establishes a local-remote loopback on a trunk or port card in a BPX. Applicable cards are the ASI, BNI, and BXM/BME.

While a line loop is present, software suspends the card self-test and the line diagnostic test that normally run when a line goes into alarm. Suspending these tests prevents background test loops from interfering with the user-specified loop.

Line loops are set for a line on the local node, so you cannot specify a remote node, and no network messaging is supported for setting a line loop of any type on a remote node.

Line loop status is displayed on the dsplns screen for an ASI or a BXM/BME in port mode and the dsptrks screen for a BNI or a BXM/BME in trunk mode. Line loop status is not displayed for connections (dspcons) affected by a line loop. Instead, a warning is printed if the line has connection traffic travelling on it, and an event is logged when a line loop is set or cleared. A line loop on a trunk generates Comm Fail, causing connections to fail and be rerouted.

For both of the dsplns and dsptrks screens, the "[" character appears before the back card type in the "Type" column to indicate that the line local-remote loopback is active.

The line loop state is not saved in BRAM or on a rebuild but is preserved on a switchover. After a rebuild, a line's loop state is cleared.

Exercise caution when you set up loops on a BNI or BXM/BME trunk because looping an added BNI/BXM/BME trunk causes Comm Failure and connection rerouting. BNI/BXM/BME addlnlocrmtlp is not supported because of a lack of useful purpose, and Cisco recommends that you use addlnloclp only when the trunk is upped but not added. On the other hand, the system does not prevent you from looping an added BNI/BXM/BME trunk port.

In this release, you can use the addloclp and addlocrmtlp commands to enable a two-segment connection at the hub node port endpoint in a network of IGX hubs and MGX 8800 interface shelves. The addloclp and addlocrmtlp commands are blocked at the interface shelf trunk endpoint. The addrmtlp command is not supported at either endpoint of the connection. You can use the dellp command to remove the local (or local remote) loopbacks that have been added; however, you cannot use the dellp command at the trunk endpoint of the connection—it will be blocked. Loops of any kind are not supported for the middle segment of a three-segment connection.

Syntax

addlnlocrmtlp <slot.port>

Parameters

Parameter	Description
slot.port	The port on the local node.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX			Yes

Related Commands

dsptrks, dsplns, dellnlp, addlnloclp

Example

The dsptrks screen appears with the loopback highlighted by the "[" character.

addlnlocrmtlp 10.1

pubsbpx1       TN    SuperUser       BPX 8620    9.3 Apr. 13 2000 01:27 GMT 

TRK     Type   Current Line Alarm Status               Other End

 1.1    T3     Clear - OK                              pubsaxi1(AXIS)

 1.3    T3     Clear - OK                              pubsipx1/8

 4.1    OC-3    Clear - OK                              -

10.1   [OC-3    Clear - OK                              -

Last Command: addlnlocrmtlp 10.1

Next Command: 

addloclp (add local loopback to connections on a port)

Places these types of channels in local loopback mode:

•Voice

•Data

•Frame Relay port

•Frame Relay connection

•ATM connection

•Access device port

For voice connections, addloclp creates a signal path from a channel or group of channels on an incoming line then back out to the line. External test equipment can test the integrity of the path at the T1 DS0 level. Figure 3-3 shows a local loopback on a voice channel.

Figure 3-3 Local Loopback on a Voice Channel

For data connections, addloclp creates a signal path from the incoming data port or set of ports back to these same port(s) through the local CDP/CVM, SDP/HDM, or LDP/LDM. External test equipment can then test the integrity of the path. Figure 3-4 illustrates a local loopback on a data connection.

Figure 3-4 Local Loopback on a Data Connection

A local loopback can simultaneously exist at both ends of a connection. However, a local loopback and a remote loopback cannot co-exist on a connection. (See the addrmtlp description for more information.)

Before executing a loopback, the IGX node performs signal and code conditioning to remove the connection from service. The loopback remains in place until removed by the dellp command. Only existing connections can be looped back.

Use the dspcons command to see which connections are looped back. A flashing right parenthesis ")" or left parenthesis "("is used in the connections display to indicate a loopback. The direction and location of the parenthesis depends on whether the loopback is local or remote and which end of the connection was used to establish the loopback.

A local loopback initiated from the local end of the connection looks like this in the connections display:

Local Channel	Remote Node	Remote Channel
12.1	alpha	15.1

A local loopback initiated from the remote end of the connection looks like this:

Local Channel	Remote Node	Remote Channel
12.1	alpha	15.1

In Frame Relay connection loopback mode (DLCI included in command), all packets from the far-end of the connection are dropped. The far-end system software is informed of the loopback. In port loopback mode (port specified without a DLCI), all packets for this port are dropped and each opposite end is informed of the loopback mode.

Use the format slot.port in port mode to loop just the port. The data is looped directly in the FRI back card, so no data reaches the muxbus or cellbus. Use the format slot.port.DLCI in connection (channel) mode to loop a specific channel. Note that this can affect up to 252 connections (channels) in port loopback mode.

Because the addloclp command causes the connection(s) to be removed from service, you should use loopbacks only when a service disruption can be tolerated. You establish remote loopbacks with the addrmtlp command. You remove local and remote loopbacks with the dellp command. You can also initiate loopbacks for data channels by pressing a button on the front of the associated data card.

Frame Relay Local Loops with Port Concentrator

When a Frame Relay port or connection is located on a Port Concentrator instead of directly on an FRP or FRM card, the data test path is different. When just the <port> parameter is used, incoming data is looped back out on the Port Concentrator port, as shown in Figure 3-5.

Figure 3-5 Local Loop on Port Concentrator

This loop disrupts all Frame Relay connections on the port that is under test.

When you specify a connection with <port.dlci> parameters, the connection is looped back at the FRM-2 or FRP-2 interface with the IGX card bus, as shown in Figure 3-6.

Figure 3-6 Local Loop on FRM-2 or FRP-2

As shown, this test verifies the operation of all components from the Port Concentrator to the IGX interface with the FRP-2 or FRM-2 card.

This tests interrupts only the specified connection on the Port Concentrator port.

In this release, the addloclp and addlocrmtlp commands support the two-segment connection at the hub node port endpoint in a network of IGX hubs and SES interface shelves. The addloclp and addlocrmtlp commands are blocked at the interface shelf trunk endpoint. The addrmtlp command is not supported at either endpoint of the connection. You can use the dellp command to remove the local (or local remote) loopbacks that have been added; however, you cannot use the dellp command at the trunk endpoint of the connection—it will be blocked. Loops of any kind are not supported for the middle segment of a three-segment connection.

Syntax

addloclp channel

Parameters (Voice)

Parameter	Description
slot	Specifies the slot number of the card containing the port to loop at the local node.
channel (s)	Specifies the channel or set of channels to loop at the local node.
port	Where applicable for the connection type, specifies the port.

Parameters (Data)

Parameter	Description
slot	Specifies the slot number of the card containing the port to loop at the local node.
port	Specifies the local port to loop at the local node.

Parameters (Frame Relay Connection)

Parameter	Description
slot	Specifies the slot number of the FRP card containing the port to loop at the local node.
port	Specifies the local port to loop at the local node.
DLCI	Specifies the Data Link Connection Identifier (DLCI) number of the channel to loop at the local node.

Parameters (ATM Connection)

Parameter	Description
slot	Specifies the slot number of the ATM card containing the port to loop at the local node.
port	Specifies the local port to loop at the local node.
VPI/VCI	VPI range: 0-7 VCI range: 1-255 An asterisk (*) indicates a virtual path.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX, IGX			Yes

Related Commands

addrmtlp, dellp, dspcons, dspfrport

Example

The connections screen appears with connection 14.1 highlighted. The system prompts you to confirm the loopback. To confirm it, enter y.

addloclp 14.1

Next Command:       

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 11:03 PST 

 Local      Remote      Remote                                      Route       

 Channel    NodeName    Channel    State  Type    Compression  Code Avoid CoS O 

 5.1        beta       )25.1       Ok     256                  7/8         0  L 

 9.1.100    gamma       8.1.200    Ok     fr                               0  L 

 9.1.200    gamma       8.1.300    Ok     fr                               0  L 

 9.2.400    beta        19.2.302   Ok     fr(Grp)                          0  L 

 14.1      )gamma       15.1       Ok     v                                0  L 

Last Command: addloclp 14.1                                                     

Next Command:        

addlocrmtlp (add local-remote loopback in a tiered network)

Adds support of a local-remote loopback for testing multisegment connections in a tiered network. The effect is to instruct the remote node to set up a remote loopback.

You must execute the addlocrmtlp command before using tstcon and tstdelay for multisegment connections. For interface shelves, you can execute addlocrmtlp on either the interface shelf (after you telnet to it).

After testing is complete, remove the local-remote loop by executing dellp. A parenthesis on the screen shows the loop's endpoint.

The addloclp and addlocrmtlp commands support a two-segment connection at the hub node port endpoint in a network of IGX hubs and SES interface shelves. The addloclp and addlocrmtlp commands are blocked at the interface shelf trunk endpoint. The addrmtlp command is not supported at either endpoint of the connection.

You can use the dellp command to remove the local (or local remote) loopbacks that have been added; however, you cannot use the dellp command at the trunk endpoint of the connection—it will be blocked. Loops of any kind are not supported for the middle segment of a three-segment connection.

Syntax

addlocrmtlp <channel(s)>

Parameters

Parameter	Description
channels(s)	The connection endpoint on the local node.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX, IGX			Yes

Related Commands

tstcon, tstdelay, dellp, dspcons, dspfrport

Example

The connections screen appears with the connection highlighted and prompts you to confirm.

addlocrmtlp 5.1.3.100

pubsbpx1       TN    SuperUser       BPX       9.3    Apr. 13 2000 14:41 PDT

 Local          Remote      Remote

 Channel        NodeName    Channel         State  Type      Compress  Code CoS

 5.1.3.100 (       pubsbpx3    7.1.2.49         Ok   aftr                       0

This Command: addlocrmtlp 5.1.3.100

Loopback these connections (y/n)?

addport (add ATM or Frame Relay port)

This command is required to add ports to the IGX and BPX. Use addport to:

•add an ATM port to the BPX (for example, ASI, BXM, physical, or virtual port).

•add the internal ATM port to the embedded UXM in the Universal Router Module (URM) (introduced in Release 9.3.20 on the IGX 8400).

•add a Frame Relay port to the IGX on a channelized FRP, FRM, or UFM card set. Only T1 or E1 lines carry channelized Frame Relay traffic, so the addport command does not apply to a Port Concentrator Shelf or front cards with a V.35, X.21, or HSSI interface.

•Only T1 or E1 lines carry channelized Frame Relay traffic, so the addport command does not apply to a Port Concentrator Shelf or front cards with a V.35, X.21, or HSSI interface.

•The addport command adds a logical Frame Relay port by using the slot number of the FRM and the DS0/timeslots that make up the logical port. On a UFM, the logical ports span the whole range of physical lines: you associate the logical ports to the lines as needed, then include the DS0s as the last field of the argument.

---

Note If you attempt to add a Frame Relay port on the UFM card set and the error message "Total number of ports and polling rate are not compatible, check cnfsysparm" is displayed, change the polling interval using the cnfsysparm command, option 25. Before changing the polling interval, run the command dspstatsinfo to see if the number of ports is less than 300, less than 500, or greater than 500. To make the ports and polling interval compatible, change the polling interval as follows: to 5 minutes if the number of ports is less than 300, to 10 minutes if the number of ports is less than 500, and to 15 minutes if the number of ports is less than 500.

---

The addport command is required before the ports can be activated (upport). The optional <vport> identifier indicates a virtual port. Only BXM cards support virtual ports.

For BPX only, since Release 9.3.0, upln no longer automatically configures a port. You must use the addport command to add the port before you can use the addcon command. You can verify that the line has been activated by using the dsplns command.

Syntax

addport <slot.port>[.<vport>]

For FRP or FRM card sets:
addfrport <slot.port> [DS0 channel] [56 | 64]

For UFM-C card sets:
addfrport <slot.port> <line.DS0_channel>

Parameters

Parameter	Description
slot.port[.vport]	Specifies the slot number of the card, the physical port, and the optional virtual port (BXM card only). Range (vport identifier): 1-31
slot.port (FRP or FRM series) slot.port line.DS0 channel (for UFM-C series)	Specifies the FRI T1 or E1 line number and the logical port number. For a UFM-U, specifies the physical slot and port. For an example of a T1 or E1: 8.12 is physical slot 8 and timeslot (or channel) 12. For the UFM card sets, this parameter specifies the slot and logical port, the physical line (the connector), and one or more contiguous DS0s. Range (logical ports): 1-250 Range (UFM-4C lines): 1-4 Range (UFM-8C lines): 1-8 Note the space between the port and line.
- chan	Optionally specifies that multiple DS0/timeslots should form one logical port. A "-" separates the starting and ending DS0s/timeslots). Timeslots must be contiguous. For example: addfrport 8.1-5. The system uses the lowest DS0/timeslot number as the logical port number and shows this in related displays.
rate	Optionally specifies the rate of a single, logical port. By default, a single logical port (or channel) is 64 Kbps. A single DS0 (timeslot) may be 56 Kbps or 64 Kbps. Default: 64 Kbps

Error/Warning Messages

Messages	Reason for Message
Slot is out of range	Line number not correct for T1/E1. You cannot add slots 0-31, that is, you cannot have a port at E1 speed. The maximum you can get is 31 slots (1984) using CCS (Common Channel signaling) because slot 0 is used for FAS, and so on.
Line must first be upped	Line is down.
Invalid channel range	Channel is out of the range 1-24 or 1-31 (16 is a reserved channel for E1).
Channel is busy	Channel is already assigned to a logical port.
You cannot use signaling channel 16" (E1)	CAS channel 16 included in logical port (E1). CCS permits the use of channel 16 but not in all countries.
Invalid rate	Entered rate is not 56 Kbps or 64 Kbps.
This rate is available for single channel only	Entered rate is 56 Kbps, but multiple channels specified.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX, IGX			Yes

Related Commands

delport, upport, dnport, dspports, dspport, cnfport

Example

Add port 3 to the BXM card in slot 11.

addport 11.3

sw53           TN    Cisco           BPX 8620  9.3.m0    Dec. 19 2000 12:43 GMT

Port configuration for ATM 11

From        VPI Min/Max     Bandwidth    Interface   State      Protocol  Type

11.3           0 /  255    353208 (cps)  LM-BXM      INACTIVE   NONE      UNI

Last Command: addport 11.3

256 PVCs allocated. Use 'cnfrsrc' to configure PVCs        

Example

Add the internal ATM port 11.1 on the Universal Router Module (URM) in an IGX node. The interface type is "INTERNAL". The default configuration is UNI with no protocol and is the same as the default configuration for a UXM port.

addport 11.1

sw190          TRM   Cisco           IGX 8420  9.3.e9    Oct. 6 2000  05:28 GMT 

Port configuration for ATM 11

Port   Chan        Speed      Interface       State       Protocol    Type

1      1        353208 (cps)  INTERNAL        INACTIVE    NONE        UNI

Last Command:addport 11.1

256 LCNs allocated. Use 'cnfrsrc' to configure LCNs

Next Command:

Example

Add a single Frame Relay port that occupies DS0s (timeslots) in the range 9-15. For a T1 line, this channel rate is 7 x 64 Kbps = 448 Kbps, as the screen example shows. The card is an FRP.

addport 21.9 -15

gamma          TRM   YourID:1        IGX 8410    9.3    Apr. 13 2000 17:28 CST 

Port configuration for FRP 21

From	   Chan	   Speed	    Interface	   State 
1	      9-15	    448	      FRI           T1	    INACTIVE

Last Command: addport 21.9-15

Next Command: 

addrmtlp (add remote loopback to connections)

The addrmtlp command places these types of channels in remote loopback mode:

•Voice

•Data

•Frame Relay port

•Frame Relay connection

•ATM connection

For voice connections, addrmtlp loops the information stream from the designated channel or group of channels on an incoming circuit line across the network and loops it back to the circuit line by way of the remote CDP or CVM. External test equipment can then test the integrity of the path at the T1 DS0 level. Figure 3-7 illustrates a remote loopback on a voice channel.

Figure 3-7 Remote Loopback on a Voice Channel

For data connections, addrmtlp transfers the information stream from the designated channels through the network and loops it back to the data port(s) through a remote SDP, HDM, LDM, or LDP. External test equipment can then test the integrity of the path. Figure 3-8 illustrates a data connection remote loopback.

Figure 3-8 Remote Loopback on a Data Connection

Prior to executing the loopback, the IGX node applies signaling template bit patterns to the A, B, C, and D signaling bits at the remote end to remove the connection from service. The loopback remains in place until removed by the dellp command. Only existing connections (those that have been entered with the add-on command) can be looped back. You cannot establish a remote loopback on a connection that is already looped back, either locally or remotely. (See the addloclp command for more information on local loopbacks.)

Use the dspcons command to see which connections are looped back. A flashing left parenthesis "("or right parenthesis ")" is used in the connections display to indicate a loopback. The direction and location of the parenthesis depends on whether the loopback is local or remote and which end of the connection was used to establish the loopback. A remote loopback initiated from the local end of the connection looks like this:

Local Channel	Remote Channel	Remote Node
3.2	alpha	12.1

A remote loopback initiated from the remote end of the connection looks like this:

Local Channel	Remote Node	Remote Channel
3.2	alpha	12.1

For remote loopback of Frame Relay connections, note that in remote loopback mode, if the transmit minimum bandwidth exceeds the receive minimum bandwidth, then loopback data may be dropped. For this reason, the connection speeds will be checked and the user will receive the following message if there is a problem:

Warning—Receiver's BW < Originator's BW-Data may be dropped

Because the addrmtlp command causes the connection to be removed from service, loopbacks should be used only when a service disruption can be tolerated. Local loopbacks are established with the addloclp command. Both local and remote loopbacks are removed by the dellp command. Loopbacks for data channels can also be initiated by pressing a push-button on the front of the associated data card.

Remote Loopbacks and the Port Concentrator Shelf

For Frame Relay remote loops, DLCI MUST be specified; entering only port number only generates an error message.

Unlike local loopbacks, remote loopbacks are not supported for Frame Relay ports; connections must be specified. Data incoming on the Frame Relay port is looped at the remote end FRM-2 or FRP-2 card, as shown in Figure 3-9.

Figure 3-9 Frame Relay Remote Loops

As shown, this test verifies the operation of IGX network components up to the interface with the remote-end FRM-2 or FRP-2. This test interrupts data traffic for only the connection specified by DLCI.

If a port concentrator is attached to the FRM-2 or FRP-2, the only difference in the loop is that the port specified to loop data is on the Port Concentrator, as shown in Figure 3-10.

Figure 3-10 Frame Relay Remote Loops with Port Concentrator

The addloclp and addlocrmtlp commands support the two-segment connection at the hub node port endpoint in a network of IGX hubs and SES interface shelves. The addloclp and addlocrmtlp commands are blocked at the interface shelf trunk endpoint. The addrmtlp command is not supported at either endpoint of the connection. You can use the dellp command to remove the local (or local remote) loopbacks that have been added; however, you cannot use the dellp command at the trunk endpoint of the connection—it will be blocked. Loops of any kind are not supported for the middle segment of a three-segment connection.

Syntax

addrmtlp (see parameter tables)

Parameters (Voice)

Parameter	Description
slot	Specifies the slot number of the card containing the port to loop at the local node.
channel (s)	Specifies the channel or set of channels to loop at the local node.
port	Where applicable for the connection type, specifies the port.

Parameters (Data)

Parameter	Description
slot	Specifies the slot number of the card containing the port to loop at the local node.
port	Specifies the local port to loop at the local node.

Parameters (Frame Relay)

Parameter	Description
slot	Specifies the slot number of the FRP card containing the port to loop at the local node.
port	Specifies the local port to loop at the local node.
DLCI	Specifies the Data Link Connection Identifier (DLCI) number of the channel to loop at the local node.

Parameters (ATM)

Parameter	Description
slot	Specifies the slot number of the card containing the port to loop at the local node.
channel (s)	Specifies the channel or set of channels to loop at the local node.
port	Where applicable for the connection type, specifies the port.
vpi.vci	Specifies VPI/VCI.

Related Commands

addloclp, dellp, dspcons

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-2	Yes	Yes	BPX, IGX			Yes

Related Commands

addloclp, dellp, dspcons

Example

The connections screen appears with connection 5.1 highlighted. The system prompts to confirm the loopback. To confirm it, enter y. A flashing parenthesis ")" appears in the "Remote Channel" column of the connection to indicate that the connection is looped back.

addrmtlp 5.1

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 12:57 PST 

 Local      Remote      Remote                                      Route       

 Channel    NodeName    Channel    State  Type    Compression  Code Avoid CoS O 

 5.1        beta       )25.1       Ok     256                  7/8         0  L 

 9.1.100    gamma       8.1.200    Ok     fr                               0  L 

 9.2.400    beta        19.2.302   Ok     fr                               0  L 

 14.1       gamma       15.1       Ok     v                                0  L 

Last Command: addrmtlp 5.1                                                      

Next Command:       

addshelf (add interface shelf or controller to a routing node or hub)

In a tiered network, adds an ATM link between:

•an IGX or BPX core switch shelf and an interface shelf; or

•a BXM card on a BPX node and a Label Switch Controller (LSC) such as a series 7200 or 7500 router; or

•a BXM card on a BPX node.

An MPLS controller is considered an interface shelf from the BPX's perspective.

The interface shelf can be one of these:

•An MGX 8220 shelf connected to a BPX node

•An MGX 8850 shelf connected to a BPX node

•An MPLS (Multiprotocol Label Switching) controller connected to a BPX node

•A Private Network to Network Interface (PNNI) Controller connected to a BPX node

•An IGX node connected to an IGX routing node that serves as a hub for the IGX/AF

•An SES (Service Expansion Shelf) connected to an IGX node

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 an UNI interface. The Annex G protocol is used in this release to pass connection status information between an IGX/BPX core switch shelf and an attached feeder.)

For example, the MGX 8850 interface shelf, or feeder, communicates over a UXM/UXM-E interface with the routing hub over Annex G LMI using AAL5 format.

---

Note Because tiered network capability is a paid option, personnel in the Cisco Technical Assistance Center (TAC) must Telnet to the unit and configure it as an interface shelf before you can execute addshelf.

---

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.

Use the commands addshelf and addctrlr to add an MPLS or PNNI controller to the BPX. Use the command addshelf with option "v" to add a VSI shelf. This is used mainly for MPLS controllers. Use the command addctrlr to add a controller to a shelf that has LMI capabilities.

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. Use addshelf with the "I" option at the IGX node to add the feeder trunk connecting it to an IGX feeder node.

Syntax

Interface shelf:

addshelf <slot.port> <shelf-type> [vpi] [vci]
addshelf <slot>.<primary link> <shelf type>

Label 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>

---

Note If you manage a tiered network through the command line interface, you can manage only Frame Relay interworking connections (ATFR) across the network. Three-segment connections for carrying serial data or voice between IGX/AFs is allowed, but you must manage them through Cisco WAN Manager.

---

Parameters

Parameter	Description
slot.port (trunk)	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.
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, 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 X for AAL5 for an SES (Service Expansion Shelf).
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 need to enter only the "v" or "vsi" option when configuring VSI options.
vpi vci	vpi,vci are optional when adding an interface shelf (feeder). (Specifies the vpi and vci (Annex G vpi and vci used). For the MGX 8220 only, Range vpi: 1-1015 Range vci: 1-65535
control VPI control VCI start	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). Choose <control_VPI> 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 Automatic Routing Management connection exists on (VPI.start_VCI to VPI.start_VCI+14). If any Automatic Routing Management connection exists on these VPI/VCI values, you are not allowed to use these VPI/VCI values. •This VPI is "reserved" for control VCs.
control partition	Specifies the control partition. You can typically leave this field blank when you add an MPLS 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.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-4	Yes	Yes	BPX switch with IGX interface shelves IGX switch with IGX shelves BPX switch with MGX 8220 interface shelf BPX with MGX 8850 interface shelf BPX switch for MPLS controller IGX switch for the Service Expansion Shelf (SES)	Yes	Yes	Yes	Yes

Related Commands

delshelf, dspnode, dsptrks

Release History

Previous to Release 9.2, WAN switching software supported the ability to configure the MGX 8220 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.

Release 9.2.20 supports:

•You can attach SES feeders to the routing network through an IGX 8400 routing hub using UXM/UXM-E and PXM trunks using UNI and NNI format. A routing hub can support up to four feeders.

•The LMI/Annex G signaling channel is used to communicate with the SES feeder through the SAR (Segmentation Assembly and Reassembly).

•UXM Feeder support provides voice, Frame Relay, and ATM data connections from feeder node to feeder node for a 2- or 3-segment network.

Signaling Channel Used by MGX 8850 and SES Interface Shelves Connecting to Routing Hubs

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.

Annex G is a bidirectional protocol used to monitor the status of connections across a UNI interface. This includes the real-time notification of the addition or deletion of connection segments and the ability to pass the availability (active state) or unavailability (inactive state) of the connections crossing this interface.

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 signaling channel to pass connection status information between itself and a BPX routing hub.

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.

addshelf Error Messages

Some of the possible error messages for the addshelf command:

•An MGX 8850 Interface Shelf already exists on this Hub

•Trunk is already added to the Network

•Trunk is in alarm

•An Interface Shelf already exists on this trunk

•Interface Shelf VPI out of range

•Interface Shelf VCI out of range

•No memory available for Interface Shelf allocation

•Communication failure during Shelf modification

•Shelf has been added

•Shelf has been deleted

•Communication breakdown

•Interface Shelf allocation failure

•Interface Shelf already has a network connection

•Interface Shelf name is not unique

•Interface Shelf IP address is not unique

•Interface Shelf modification failure

Example (Interface Shelf)

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):

addshelf 11.1 a

The sample display shows a partially executed command prompting you for the interface shelf type:

nmsbpx23       TN    SuperUser       BPX 8620    9.3.10    Apr. 4 2000   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 a 

Enter Interface Shelf Type:  I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)  

Next Command:

Example (MGX 8850 AAL5 Interface Shelf)

Add an MGX 8850 at trunk 4.8. After you add the MGX 8800 shelf, the screen displays a confirmation message and the name of the shelf.

To add the MGX 8850 (may be referred to on screen as AAL5), use this command:

addshelf 4.8 x

The system response shows that an MGX 8850 was added on trunk 4.8 as an AAL5 (ATM Adaptive Layer 5) type of interface shelf. (Adding an MGX 8850 interface shelf is similar to adding an MPLS controller interface shelf.)

pswbpx3       TN    SuperUser       BPX 8600    9.3.10    June 6 2000   13:28 PST

		BPX 8620 Interface Shelf Information

Trunk	Name	Type 	Part Id 	Ctrl Id 	Control_VC		Alarm

					VPI  VCIRange

4.8 		SIMFDR0 	AAL/5 	- 	- 	- 	- 	OK

This Command: addshelf 4.8 x 

Enter Interface Shelf Type:  I (IGX/AF), A (AXIS), P (APS), V (VSI), X (AAL5)  

Next Command:

Example (SES to an IGX)

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)

---

Note You can add an SES (Service Expansion Shelf) feeder only to an IGX routing node.

---

sw288       TN    SuperUser       IGX 8420    9.3   Apr. 13 2000 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 signaling protocol to communicate with an IGX routing hub, they all use the same interface shelf type of AAL5 (designated by the addshelf "X" option).

Adding a VSI Controller

The maximum number of controllers that can be attached to a given node is limited by the maximum number of feeders (16) that can be attached to a BPX hub. Therefore, the total number of feeders and controllers cannot exceed 16.

You add a VSI controller, such as an MPLS controller, to a switch by using the addshelf command with the vsi option. The vsi option of the addshelf command identifies VSI controllers and distinguishes them from interface shelves (feeders).

The VSI controllers are allocated a partition of the switch resources. VSI controllers manage their partition through the VSI interface. The controllers run the VSI master. The VSI master entity interacts with the VSI slave running on the BXMs through the VSI interface, to set up VSI connections using the resources in the partition assigned to the controller.

Two controllers that are intended to be used in a redundant configuration must specify the same partition when added to the node through the addshelf command.

When a controller is added to the node, switch software sets up the infrastructure so that the controllers can communicate with the slaves in the node. The VSI entities decide how and when to use these communication channels.

The controllers also require a communication channel between them. This channel could be in-band or out-of-band. When a controller is added to the switch, switch software sends controller information to the slaves. This information is advertised to all the controllers in the partition. The controllers may decide to use this information to set up an intermaster channel. Alternatively the controllers may use an out-of-band channel to communicate.

To add a controller to the node, use the addshelf command. You add a redundant controller in the normal way, except that it specifies a partition that may be already in use by another controller. The addshelf command allows for up to three controllers to manage the same partition.

One of the parameters that must be specified with the addshelf command when a VSI controller is added to the switch is the controller ID. This is a number between 1 and 32 that uniquely identifies the controller. Two different controllers must always have different controller IDs.

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 via the addshelf command, 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 specify the master-slave connections by using the <Control VPI> and <Control Start VCI> parameters. The default for these parameters is 0/0.

---

Note If you manage a tiered network through the command line interface, you can manage only Frame Relay interworking connections (ATFR) across the network. Three-segment connections for carrying serial data or voice between IGX/AFs is allowed, but you must manage them through WAN Manager.

---

Feature Mismatching to Verify VSI Support

The cnfrsrc and addshelf commands, in addition to other configuration commands, perform mismatch verification on the BXM and UXM cards. For example, the cnfrsrc and addshelf commands verify whether the cards both have VSI 2.0 support configured.

The Feature Mismatching capability does not check mismatched cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Example (Redundant VSI Controller)

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.

addshelf 11.1 vsi 1 2

night          TN    StrataCom       BPX 8600   9.3 Apr. 13 2000 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

Adding an MPLS Controller

For MPLS to carry traffic, you must first up the link to an MPLS controller (by using uptrk) at the BPX node. You can then add the link to the network (by using addshelf).

The link must be free of major alarms before you can add it with the addshelf command.

---

Note Once you up a port on the BXM in either trunk or port mode by using either the uptrk or upport commands, respectively, you can up only those ports in the same mode.

---

Example (MPLS Controller)

Add trunk 4.1 as a VSI-MPLS controller interface shelf with control ID set to 1, partition ID set to 1, 
control VC VPI set to 0, and control VC VCI start at 40. 

addshelf 4.1 vsi 1 1 0 40

nmsbpx23       TN    SuperUser       BPX 15    9.3.10    Aug. 1 2000 13:28 PST

		BPX 8620 Interface Shelf Information

Trunk	Name	Type 	Part Id 	Ctrl Id 	Control_VC		Alarm

					VPI  VCIRange

4.8 		SIMFDR0 	AAL/5 	- 	- 	- 	- 	OK

4.1		VSI	VSI	1	1	0	40-54	OK

This Command: addshelf 4.1 v 1 1 0 40

Next Command:

addtrk (add a trunk between nodes)

You must add a trunk to the network before it can carry traffic. You need only to execute addtrk at one of the nodes terminating the trunk. Before you add a trunk to the network, you must have activated (or "upped") the trunk at both ends by using uptrk.

A trunk must be free of major alarms before you can add it. If you use addtrk to join two networks that were previously separate, the local node verifies that all node names and node numbers in both networks are unique before it adds the trunk.

You cannot add a trunk while any of these conditions are true:

•Another node is attempting to change the network topology by adding or deleting a trunk.

•Another node is notifying all nodes that it has been renamed.

•Another node is currently adding or deleting a connection in the network with the addcon or delcon command.

•An unreachable node exists in the network.

•Connections are rerouting.

•The node names or the node numbers across the two networks are not unique. Use the command and optional parameter dspnds +n to see the node numbers.

---

Warning When using the addtrk command, exercise caution when adding a new node to a network or one network to another network. With these particular operations, the user IDs and passwords may be replaced by those in the other network. Consult Customer Service before performing these operations.

---

Adding a Virtual Trunk

You can add a trunk as a physical trunk or a virtual trunk. A virtual trunk is a way to connect Cisco nodes through a public ATM cloud. You can define virtual trunks on BNI, BXM and UXM cards.

(Note that even though nodes running Release 9.2 can interoperate with 9.1 or 8.5 nodes, if you are running a network with mixed releases, you cannot add UXM and BXM virtual trunks because the networking messages are incompatible due to the virtual trunk number and different cell format on virtual trunks. BNI cards use STI cell format, and BXM and UXM cards use NNI cell format.)

To designate a trunk as a virtual trunk, you use a virtual trunk number, which is used to differentiate the virtual trunks within a physical port. (Refer to the BPX 8600 Series Reference for more information on virtual trunking.)

For the BXM card, you can define a maximum of 32 virtual trunks within one port. Valid virtual trunk numbers are 1-31 per port. The number of virtual trunks available is limited by the number of virtual interfaces (VIs) available on the card. Each logical trunk (physical or virtual) consumes on VI.

For the UXM card, you can define a maximum of 16 virtual trunks within one port. Valid virtual trunk numbers are 1-15.

The addtrk command will be blocked for virtual trunks configured for VSI.

Syntax

addtrk <slot.port>[.vtrk]

Parameters

Parameter	Description
slot.port	Specifies the slot and port number of the trunk to add.
vtrk	Optionally specifies the virtual trunk number. Virtual trunking is supported on a BNI or BXM card on a BPX node, or a UXM card on an IGX node. The maximum number of virtual trunks per physical port: BNI card: 32 T3 or E3 line: 32 OC-3/STM1 line: 11 The maximum number of virtual trunks per port: BXM card: 32 UXM card:16

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1	Yes	Yes	BPX, IGX			Yes

Related Commands

deltrk, dsptrks, uptrk

Example

Add trunk 5.4 to node sw180.

addtrk 5.4

NOTE: update example to show: "Add trunk 5.4 to node sw180."

sw180          TN    Cisco           IGX 8420  9.3.r3    Dec. 19 2000 14:10 GMT

TRK         Type   Current Line Alarm Status               Other End

 5.4        OC3    Clear - OK                              -

 8          T1/24  Clear - OK                              sw108/14

Last Command: addtrk 5.4 

addtrkred (add trunk redundancy)

Configures trunk redundancy on an ATM trunk. The addtrkred command specifies a backup trunk to the primary trunk. Applicable line types are T3 and E3. The redundancy scheme requires two sets of ATM trunk cards and two standard T3 or E3 cables (not Y-cables). Note the following characteristics of trunk redundancy:

•Applicable card sets are the AIT connected to a BNI card set on a BPX node.

•Execute addtrkred on an IGX but not on the BPX side.

•Primary and backup card sets must be in adjacent slots.

•After a primary trunk failure clears, the traffic automatically returns to the primary card set.

•Trunk redundancy is not compatible with virtual trunking.

Syntax

addtrkred <primary trunk> <secondary trunk>

Parameters

Parameter	Description
primary trunk	Specifies the slot number of the primary trunk card set.
secondary trunk	Specifies the slot number of the secondary trunk card set as backup.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-4	No	Yes	BPX, IGX			Yes

Related Commands

deltrkred, dsptrkred

Example

Add bandwidth redundancy for the primary ATM trunk in slot 4 with backup from the ATM trunk in slot 5.

addtrkred 4 5

beta           TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000   15:15 MST 

ATM Line 	Backup ATM Line

   4           5 
	

Last Command: addtrkred 4 5

Next Command:       

adduser (add a user)

Adds a user to the network. The first time the new user ID is used for logon, a prompt asks the user to change from the default password to a new password which they enter using the cnfpwd command. Users with privilege levels 1 through 5 may add users with lower privilege levels. Because privilege level 6 has no user levels below it, level 6 cannot add any users.

Syntax

adduser <user_id> <privilege_level>

Parameters

Parameter	Description
<user_id>	Specifies the name of the user to add.
<privilege_level>	Specifies the privilege level to grant to the added user. Range: 1-6, where 1 is the highest level and 6 is the lowest.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	Yes	BPX, IGX			Yes

Related Commands

cnfpwd, deluser, dspusers

Example

Add a user sarah with privilege level 5.

adduser sarah 5

alpha          TRM   YourID:1        IGX 8410    9.3    Apr. 13 2000 13:48 PST 

YourID       1                                                                  

Sarah        5                                                                  

Last Command: adduser Sarah 5                                                   

Next Command:     

addyred (add Y-cable redundancy)

Enables card redundancy for cards on the BPX and IGX. The addyred command also enables SONET Automatic Protection Switching (APS) across two BXM OC-3 or OC-12 cards. Use the addyred command to specify the slots of the primary and secondary cards that form the redundant pair. Redundancy applies to the entire card, and not specific trunks or lines. (The addyred command performs the same function as the addcdred alias command.)

Redundant card sets must have these characteristics:

•The primary and secondary card sets must be identical.

•Secondary card sets must not currently be active.

•Neither the primary nor secondary card set may already be part of a redundant set.

•When configuring APS 1+1, the primary and secondary card sets must be in adjacent slots. (Note that this restriction applies only to the BPX chassis for APS 1+1 redundancy.) See the "APS 1+1 Environment (Redundant Back Cards with Front Card Redundancy)" section for additional information on APS 1+1.

In both 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 addyred command if the primary and secondary slots are empty. If one or both of the card slots is empty, the addyred command will fail.

You must use the addyred command to configure a VSI slave redundant card. When a standby slave card is first started (either by inserting the card into the slot, or issuing the addyred command from the CLI console), the active slave forwards all VSI messages received from the master VSI controller card to the standby slave VSI controller card.

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. 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. For descriptions of the jumper positions and cabling, see the Cisco IGX 8400 Series Installation and Configuration manual.

The addyred commands (addyred, delyred, dspyred, prtyred, switchyred) perform feature mismatch checking on both the primary and secondary cards. For information on feature mismatch checking, refer to the BPX 8600 Series Installation and Configuration Guide. Also see the "Feature Mismatching" section for detailed information.

With the second phase of the Automatic Routing Management to PNNI migration introduced in Release 9.3.30, the BXM interface card supports the Extended LMI (XLMI) protocol. This protocol enables the exchange of neighbor discovery information between the BXM and AXSM over the AR-PNNI link. You cannot activate XLMI/ENNI when there are existing connections. Also in this release, ILMI Neighbor Discovery feature is also available for virtual ports on the BXM card.

With Release 9.3.30, addyred is NOT allowed in the following instances:

•When the secondary BXM card does not support LMI Neighbor Discovery and the primary BXM card supports LMI Neighbor Discovery and at least one port is running the XLMI protocol.

•If one card in the Y-redundant BXM pair is replaced, mismatch is declared when the original card pair supports LMI Neighbor Discovery and at least one port is configured for LMI Neighbor Discovery.

•If O.151 OAM is enabled on the primary card (using cnfcdparm) and the secondary card does not support the feature.

---

Note In the hybrid AR-PNNI network, both the active and standby BXM cards receive messages for connections that are added or deleted. Both cards maintain identical connection database views. However, there is no XLMI redundancy, and only the active BXM card exchanges connection status information with the adjacent AXSM. At switchover, the new active BXM card initiates an exchange with the adjacent AXSM to synchronize the AXSM's connection database.

---

Syntax

addyred <primary slot> <secondary slot>

Parameters

Parameter	Description
<primary slot>	Specifies the slot number of the primary card set.
<secondary slot>	Specifies the slot number of the secondary card set.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-4	No	Yes	BPX, IGX	Yes	Yes	Yes	No

Related Commands

delyred, dspyred, prtyred, switchyred

Example (BPX)

Add Y-cable redundancy to the BPX BXM card sets in slots 2 and 12.

addyred 2 3

sw118          TN    Cisco           BPX 8620  9.3.c0    May  9 2001  1330 GMT 

     Slot Other Front   Back

Slot Type Slot  Card    Card 

2    Pri  3     BXM     LM-BXM

3    Sec  2     BXM     LM-BXM

This Command addyred 2 3

Example (IGX)

Add Y-cable redundancy to the IGX UXM/T3 card sets in slots 12 and 13.

addyred 12 13

arnold         TN    Cisco           IGX 8430  9.3.1p    Aug. 16 2000 17:27 PST 

     Slot Other Front  Back   Channel Configuration

Slot Type Slot  Card   Card     1    2    3    4    5    6    7    8  

12   Pri  13    UXM    T3       --   --   --   --   --   --   --   --

13   Sec  12    UXM    T3       --   --   --   --   --   --   --   --

Last Command: addyred 12 13

Next Command: 

Feature Mismatching

During addyred's mismatch checking, the following verifications are performed:

•A verification is performed to ensure that both the primary and secondary cards support features that are activated. For example, if the APS feature is configured on the primary card, and this feature is not available on the secondary card, you are blocked from using the addyred command. As another example, to ensure that cards with the Idle Code Suppression feature enabled on them are compatible, addyred blocks cards that have different idle code suppression capability.

•If the feature is not enabled, and the secondary card does not support similar feature sets, the (internal) logical database is updated to reflect this difference.

•Following a delyred command execution, the logical card's database is updated to reflect the primary card's capabilities.

With Release 9.3.10, addyred is NOT allowed if the BPX Neighbor Discovery Enable/Disable flag is set to ENABLED on any port on the primary card and the secondary card does not have the BPX Neighbor Discovery capability. An error message is displayed in this situation. The addyred is allowed if the BPX Neighbor Discovery Enable/Disable flag is NOT set to ENABLED on any port on the primary card. If the secondary card does not have the BPX Neighbor Discovery capability, the following events occur:

1. Mismatch is not declared.

2. Neighbor's information (Neighbor's IfName and Neighbor's IP Address) is deleted from all ports on the primary card.

3. BPX Neighbor Discovery Enable/Disable flags on all ports on the primary card are set to DISABLED (if previously set to ENABLED).

4. The logical card table(s) are updated to indicate that the BPX Neighbor Discovery feature is no longer supported.

5. CWM is notified via the Robust Port Update message.

Events 1 through 5 also occur in the following situations:

•A stand-alone BXM card with Neighbor Discovery capability and BPX Neighbor Discovery Enable/Disable flag set to either ENABLED or DISABLED on any port on the card is replaced with one that does not support the feature.

•One of the cards in a Y-redundant card pair (both cards with Neighbor Discovery capability and BPX Neighbor Discovery Enable/Disable flag set to either ENABLED or DISABLED on any port on the logical card) is replaced with one that does not support the feature.

Starting with Release 9.3.30, the BXM-E models DX and EX card slots can be configured to support 60K LCNs for VSI connections. For Y-cabled or APS 1+1 redundancy, the system checks the total physical channel number supported by each card in the pair. When addyred is executed, the lower value of the two cards becomes the attribute value for the logical card. If the logical card is configured to support 60K VSI LCN, mismatch is declared when a replacement card's attribute value of total physical channel number supported is not 60K-64.

APS 1+1 Environment (Redundant Back Cards with Front Card Redundancy)

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 back cards. The two redundant BXM back cards 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:

---

Note Using only one front card and two back cards is not a valid configuration when adding APS capability, and APS alarm capability is reduced when the standby card is not available. You must configure card redundancy before you can configure APS redundancy.

---

---

Note 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. 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.

---

burnfwrev (burn firmware image into cards)

Burns a firmware image into the memory of a specific card. Before you use burnfwrev, the firmware image must already reside in the controller card's memory. (Use getfwrev to load the image to the controller.)

A few seconds after you enter burnfwrev, the system displays a screen similar to the one in Figure 3-10, then the Burn Address column starts to indicate the addresses that are being "burned." When burnfwrev finishes, the status changes to "Complete."

After all cards at a node have been updated with burnfwrev, enter the following to clear the firmware image from the controller card's buffer area:

getfwrev 0.0 node_name

Use the dspfwrev command to display the firmware image status on the controller card at any time after burnfwrev has finished.

At the SuperUser level (0), you can use burnfwrev only to change the revision level of a card's firmware. If the firmware revision would result in a new model number for the card, only a user with a higher privilege level can burn the firmware image. In this case, you would have to call the TAC to execute the command.

Syntax

burnfwrev <image name> <slot number>

Parameters

Parameter	Description
<image name>	Specifies the name of the firmware image to burn. You should typically enter image names in all capital letters; also, image names are case-sensitive.
<slot number>	Specifies the shelf slot where the card to burn is located. Specifying slot 0 will burn all cards of the appropriate type at the local node.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
SuperUser	Yes	Yes	BPX, IGX			Yes

Related Commands

dspfwrev, getfwrev

Example

Burn Firmware Revision into Card

burnfwrev

gamma            TRM       SuperUser        Rev: 9.3 Apr. 13 2000  14:28 PDT 

Firmware        Size        Status                                              

F.D.A           256 K       Burning into slot 19 (6 lives)                      

File            Address     Length      CRC           Burn Address              

0               800000      10          E986E939                                

1               800800      410         22996DDA                                

2               801000      2D40        B212147F                                

3               805E60      480         85CB29EA                                

4               80A630      70          57A938AE                                

5               80A6B0      20          4B9E8DDC                                

6               810000      10000       338E45F6                                

7               820000      4400        95990113                                

8               835000      1810        875771B2                                

9               8368A0      15D0        4C597B97                                

This Command: burnfwrev                                                         

Continue?

burnrtrcnf (burn router configuration file)

Burns the IOS configuration file for the Universal Router Module (URM) embedded router from the NPM RAM buffer to the Admin flash of the URM card.

For information about the URM Remote Router Configuration feature introduced in Release 9.3.30, refer to URM Remote Router Configuration Feature on the IGX, page 2-3.

Syntax

burnrtrcnf <slot_number> <configuration_file_name>

Parameters

Parameter	Description
slot number	Slot number of the URM card to which the IOS configuration file is to be burned.
configuration file name	Name of the IOS configuration file that is to be copied to the URM Admin flash. The IOS configuration file name can be a maximum of 32 characters. The maximum file size is 256K bytes. The file must be an ASCII text file. Compressed files cannot be interpreted by the IOS router.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
Super Group	Yes	Yes	IGX	Yes	Yes	Yes	No

Related Commands

clrrtrcnf, cnfrtr, cnfrtrcnfmastip, dspcnf, dsprtr, dsprtrcnfdnld, dsprtrslot

Example

Copy the IOS configurative file named 1234.c to the URM Admin flash.

burnrtrcnf

sw175          TN    Cisco           IGX 8420  9.3.30 Mar. 9 2000  05:31 GMT

Router Config filename         Status

1234.c                         Complete

Router Config fileSize         Bytes Dnld

256050

Last Command: burnrtrcnf 1234.c 

bye (end user session)

Ends a local or remote terminal connection. The local connection ends, and the initial sign-on prompt appears on the screen. With a local terminal connection, the bye command logs out the user. If a local terminal is inactive for a (default) period of 20 minutes, the connection is automatically broken. This is the equivalent of entering the bye command. With a remote terminal connection (vt), the bye command returns the terminal to the local node. After a (default) period of four minutes of inactivity, a remote terminal connection is automatically returned to a local connection. This is equivalent to entering the bye command.

Syntax

bye

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-6	Yes	No	BPX, IGX			Yes

Related Commands

vt

Example

bye

-----------------------------------SCREEN 1--------------------------------------

sw180          TN    Cisco           IGX 8420  9.3.g0    Oct. 20 2000 06:24 GMT

clrclnerrs         - Clear Circuit Line Errors

Can be included in Jobs.

Usage: clrclnerrs [<line_number>]

Last Command: help

Next Command: bye

-----------------------------------SCREEN 2--------------------------------------

sw180          TN    No User         IGX 8420  9.3.g0    Oct. 20 2000 06:26 GMT

Enter User ID:  

chklm (check node loading model)

Verify target node load models by issuing the chklm and dsplm commands. These commands compare sections of the current node's database with all other nodes in the network. These commands are useful before a software upgrade since ideally, the network should be alarm free at the time of the software upgrade. If this is not possible, at least the reason for all major alarms should be identified and noted, and then suitable reconfiguration should be made in order to remove the alarm.

Issue the chklm command on every node in the network sequentially. When complete, return to the first node and run the dsplm command.

Syntax

chklm

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
Super group	Yes	No	BPX, IGX	No	Yes	Yes	No

Related Commands

dsplm

Example

The command only returns a command prompt. See dsplm command for sample output.

clrcderrs (clear detailed card errors)

The clrcderrs command clears the history of card failures (errors) associated with the specified slot.

When you enter this command the system responds with Slot Number or *. After you enter the command, the system asks you to confirm that it is OK to clear this data.

Syntax

clrcderrs <slot number | *>

Parameters

Parameter	Description
<slot number | *>	Specifies the slot number to clear. A "*" can be entered to clear all cards.
<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 UXM card in slot 3). The last VSI control channel corresponding to communication with the VSI slave on slot 16 or 32 (depending on the number of slots in the particular IGX model) will use the VCI value of (<start_vci> + number of slots on the IGX - 2). Range 16-slot IGX: 40-65521 Range 32-slot IGX: 40-65505 Default: 40

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
SuperUser	Yes	Yes	BPX, IGX			Yes

Related Commands

dspcderrs, prtcderrs

Example

pubsigx1       TN    SuperUser       IGX 32    9.3       Apr. 13 2000  18:48 GMT

FRM in Slot 3  : 172240 Rev ESJ     Failures Cleared: Date/Time Not Set

----------------------------------- Records Cleared:  Date/Time Not Set

Self Test          Threshold Counter: 0          Threshold Limit: 300

Total Pass: 495           Total Fail: 0              Total Abort: 2

First Pass: Date/Time Not Set          Last Pass: Apr. 13 2000 19:36:48 GMT

First Fail:                            Last Fail:

Background Test    Threshold Counter: 0          Threshold Limit: 300

Total Pass: 29849         Total Fail: 0              Total Abort: 0

First Pass: Date/Time Not Set          Last Pass: Apr. 13 2000  18:46:34 GMT

First Fail:                            Last Fail:

Hardware Error     Total Events: 0     Threshold Counter: 0

First Event:                           Last Event:

This Command: clrcderrs 3

OK to clear (y/n)?

After replying "y" (yes) to the confirmation prompt, the screen appears:

pubsigx1       TN    SuperUser       IGX 32    9.3       Apr. 13 2000  18:55 GMT

FRM in Slot 3  : 172240 Rev ESJ     Failures Cleared: Date/Time Not Set

----------------------------------- Records Cleared:  Apr. 13 2000  18:55:02 GMT

Self Test          Threshold Counter: 0          Threshold Limit: 300

Total Pass: 0             Total Fail: 0              Total Abort: 0

First Pass:                            Last Pass:

First Fail:                            Last Fail:

Background Test    Threshold Counter: 0          Threshold Limit: 300

Total Pass: 0             Total Fail: 0              Total Abort: 0

First Pass:                            Last Pass:

First Fail:                            Last Fail:

Hardware Error     Total Events: 0     Threshold Counter: 0

First Event:                           Last Event:

Last Command: clrcderrs 3

clrchstats (clear channel statistics)

Clears the gathered statistics for either a specific channel or all channels, including Frame Relay channels. When you enter a specific channel number, the current channel statistics display appears, asking if you want to clear the display. If you enter "*" (all channels) for the channel specification, the display prompts you to confirm whether you want to clear all channel statistics. This is sometimes referred to as a summary statistics command.

The Multilevel Channel Statistics lets you configure and display additional levels of statistics beyond level 1 statistics (for example, levels 2 and 3), as supported by the Multilevel Channels Statistics feature. You use the cnfcdparm command to configure the channels statistics level on the BXM or UXM cards.

For example, if you configure slot 5 to support level 3 channel statistics, all connections on that particular card are set to provide level 3 statistics. Switch software collects, displays, and propagates to Cisco WAN Manager the various statistics types. The channel statistic type vary in number and type based on the level of support provided by the BXM and UXM cards. You use the dspchstats and clrchstats to display and clear the statistics.

Syntax

clrchstats <channel | *>

Parameters

Parameter	Description
channel	Specifies the channel whose statistics are cleared. Frame Relay format: slot.port.DLCI.
*	Specifies all channel statistics.

Attributes

Privilege	Jobs	Log	Node	Lock
1-5	Yes	Yes	IGX, BPX	Yes

Related Commands

dspchstats

Example

Clear channel statistics for 3.1.1 (BPX).

clrchstats 3.1.1

Example

Clear channel statistics for 3.1.1.

clrchstats 3.1.1

sw83           TN    SuperUser       IGX 8420    9.3       Apr. 13 2000 19:24 PST

Channel Statistics: 3.1.1         Cleared: Aug. 17 1997 08:10

MIR: 3.8 kbps           Collection Time: 6 day(s) 10:04:58      Corrupted: NO

                     Frames   Avg Size Avg    Util          Packets     Avg

                              (bytes)  (fps)  (%)                      (pps)

From Port:          1516586        198      2   35

To Network:         1516215        198      2   35         16678365        30

Discarded:              371        198      0    0

From Network:       1518665        197      2   35         16705146        30

To Port:            1518629        198      2   35

Discarded:               36        120      0    0              238         0

                   ECN Stats:  Avg Rx VC Q:             0    ForeSight RTD    40

Min-Pk bytes rcvd:      52470  FECN Frames:             0    FECN Ratio (%)    0

Minutes Congested:          0  BECN Frames:            16    BECN Ratio (%)    0

Frames rcvd in excess of CIR:       0  Bytes rcvd in excess of CIR:         0

Frames xmtd in excess of CIR:       0  Bytes xmtd in excess of CIR:         0

This Command: clrchstats 3.1.1

OK to clear (y/n)?

Example

Clear the statistics of channel 9.2.400.

clrchstats 9.2.400

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 13:24 PST 

Channel Statistics for 9.2.400    Cleared: Apr. 13 2000 13:23                   

MIR: 9.6 kbps           Collection Time: 0 day(s) 00:02:42      Corrupted: NO   

                     Frames   Avg Size Avg    Util          Packets     Avg     

                              (bytes)  (fps)  (%)                      (pps)    

From Port:                0          0      0    0                              

To Network:               0          0      0    0                0         0   

Discarded:                0          0      0    0                              

From Network:             0          0      0    0                0         0   

To Port:                  0          0      0    0                              

Discarded:                0          0      0    0                0         0   

                   ECN Stats:  Avg Rx VC Q:             0    ForeSight RTD    --

Min-Pk bytes rcvd:          0  FECN Frames:             0    FECN Ratio (%)    0

Minutes Congested:          0  BECN Frames:             0    BECN Ratio (%)    0

This Command: clrchstats 9.2.400                                                

OK to clear (y/n)?     

clrclkalm (clear alarm clock)

Clears the alarm status of a clock source, either circuit line or trunk, after a problem is cleared. Before the node can use the original clock source, you must clear the alarm with clrclkalm. The system displays no messages after execution.

The clock test runs continuously in a node, comparing the frequency of the node's clock source to a reference on the BCC/CC/control card. If a clock source is found to be outside preset frequency limits, it is declared defective and another clock source is selected. In order for the node to return to the original clock source, the alarm must be cleared by using the clrclkalm command. The alarm may be either a "Bad Clock Source" or "Bad Clock Path" alarm.

Syntax

clrclkalm <line type> <line number>

Parameters

Parameter	Description
<line type>	Specifies the type of line: "L" indicates a line. "T" indicates a trunk.
<line number>	Specifies the number of the line or trunk.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	Yes	BPX, IGX			Yes

Related Commands

cnfclksrc, dspclksrcs, dspclns, dspcurclk, dsptrks

clrcnf (clear configuration memory)

Clears the configuration memory at the current node and resets the node.

The clrcnf command erases most network configuration data. This configuration data includes connections, trunks, circuit lines, and so on, for the local node. You might need to use the clrcnf command when you upgrade the network with a new software release or when you move a node. A warning and a confirmation prompt appear before the command executes.

This command should be used only on a node that has not yet been placed in service or when the network configuration has been previously saved so it can be quickly reloaded. The configuration can be saved in one of several ways:

•On a Cisco WAN Manager terminal using the savecnf command. The node is then reloaded using the loadcnf command.

•On a standby controller card. Before entering the clrcnf command, remove the standby controller from its slot. The configuration data will be maintained in BRAM even though the power has been removed from the card.

---

Caution Use clrcnf with extreme caution. Typically, you should use clrcnf only if the Cisco TAC has instructed you to do so. This command can make the node unreachable to the network.

---

Syntax

clrcnf

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
SuperUser	No	No	BPX, IGX			Yes

Related Commands

loadcnf, runcnf, savecnf

clreventq (clear event queues from the fail handler)

Clears high-water marks for fail handler event queues.

Syntax

clreventq

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-6	No	Yes	BPX, IGX			Yes

Related Commands

dspeventq

Example

Clear the fail handler event queue.

clreventq

sw151          TN    SuperUser       IGX 16    9.3       Apr. 13 2000 19:18 GMT

  QUEUE                 LENGTH           THROTTLING

NUM NAMES          MAX   HIGH CURRENT      POINT

 1  Fail_Xid               26      1        7000

 2  Fail_ Q                25      0

 3  Mt_Sv_Q[0]      300     9      0         270

 4  sv_mt_bufq              9      0

This Command: clreventq

OK to clear HIGH counts(y/n)?

clrfrcportstats (clear FRC/FRM port statistics)

Clears port statistics for FRM-2 or FRP-2 physical ports connected to a Port Concentrator Shelf. To see the statistics that you clear with clrfrcportstats, execute dspfrcportstats. The controller card collects statistics from the FRM-2 or FRP-2 once per minute. Because clrfrcportstats clears statistics on the controller card, it might not clear statistics generated within the last minute.

Syntax

clrfrcportstats <slot.port | *>

Parameters

Parameter	Description
<slot.port | *>	Slot and port of the physical port. The range for port is 1-4. An asterisk (*) specifies all FRC-2/FRM-2 physical ports.

Related Commands

dspfrcportstats

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	Yes	Yes	BPX, IGX			Yes

clrlnalm (clear circuit line alarm)

Clears the alarms associated with a circuit line. Since the statistical alarms associated with a circuit line have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. This command allows these alarms to be cleared, allowing any new alarms to be quickly identified. The clrlnalm command can clear only alarms caused by the collection of statistical data. Alarms caused by a network failure cannot be cleared. For example, an alarm caused by a collection of bipolar errors can be cleared, but an alarm caused by a card failure cannot. (Same as alias clrclnalm.)

Syntax

<line_number> <fail_type>

Parameters

Parameter	Description
<line_number>	Specifies the number of the line.
<fail_type>	Specifies the type of alarm to clear.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	Yes	IGX			Yes

Related Commands

dsplns, dsplnerrs

Example

Clear the minor alarm caused by frame slips on circuit line 14.

clrlnalm 14 2

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 13:10 PST 

                             Line Alarm Configuration                           

                       Minor                               Major                

  Violation    Rate    Alarm Time  Clear         Rate    Alarm Time  Clear      

  1) Bpv        10E-7  10 min       3 min         10E-3   10 sec      10 sec    

  2) Fs          .01%  10 min       3 min           .1%   10 sec      10 sec    

  3) Oof       .0001%  10 min       3 min          .01%   10 sec      10 sec    

  4) Vpd           2%   5 min       3 min            5%   60 sec      10 sec    

  5) Tsdp        .01%   5 min       3 min           .1%   60 sec      10 sec    

  6) Ntsdp       .01%   5 min       3 min           .1%   60 sec      10 sec    

  7) Pkterr      .01%  10 min       3 min           .1%  125 sec      10 sec    

  8) Los       .0001%  10 min       3 min          .01%   10 sec      10 sec    

This Command: clrlnalm 14 2

Continue?     

clrlnerrs (clear line errors)

Clears the errors associated with a circuit line. Since the statistical alarms associated with a circuit line have associated integration times, they can keep a major or minor alarm active for some time after the cause has been rectified. This command allows these alarms to be cleared, allowing any new alarms to be quickly identified.

The clrlnerrs command can clear only those alarms that the collection of statistical data has caused. You cannot clear alarms caused by a network failure cannot be cleared by clrlnerrs.

Syntax

clrlnerrs [<line_number>]

Parameters

Parameter	Description
<line_number>	Specifies the number of the line.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	Yes	Yes	IGX			Yes

Related Commands

dsplnerrs, prtlnerrs

Example

Clear line error counts. In response to the prompt, enter "y" to reset all line error counts to "0."

clrlnerrs

alpha          TRM   YourID:1        IGX 8420    9.3    Apr. 13 2000 13:12 PST 

Total Errors                                                                    

From  Code    Frame   Out of  Loss of Frame   CRC     Out of                    

CLN   Errors  Slips   Frames  Signal  BitErrs Errors  MFrames AIS-16            

14          0       0       0       -       0       -       -       -           

Last Command: clrlnerrs                                                        

Next Command:    

clrlog (clear event log)

Clears the event log. When the log is cleared, one entry remains, "Info Log Cleared". Before the event log is cleared, a prompts asks you to confirm. See the dsplog command for more information on the event log.

Syntax

clrlog

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	Yes	Yes	IGX			Yes

Related Commands

dsplog

Example

Clear the event log. When the log is cleared, one entry remains, "Info Log Cleared." Enter "y" to confirm.

clrlog

sw151          TN    SuperUser       IGX 16    9.3       Apr. 13 2000 19:19 GMT

Most recent log entries (most recent at top)

Class  Description                                             Date     Time

Info   User SuperUser logged out (Local)                       09/12/96 18:18:57

Major  LN 5.6 Loss of Sig (RED)                                09/12/96 18:12:22

Info   User SuperUser logged out (Local)                       09/12/96 18:11:17

Info   Clock switch to oscillator of SCC                       09/12/96 18:10:46

Clear  LN 5.6 OK                                               09/12/96 18:05:11

Minor  LN 5.6 Out of Multi-Frames                              09/12/96 18:03:27

Info   Clock switch to LINE 5.6                                09/12/96 18:03:12

Clear  LN 5.6 OK                                               09/12/96 18:02:42

Info   Clock switch to oscillator of SCC                       09/12/96 17:59:24

Major  LN 5.6 Loss of Sig (RED)                                09/12/96 17:59:24

Info   Clock switch to LINE 5.6                                09/12/96 17:59:20

Clear  LN 5.6 OK                                               09/12/96 17:59:20

Major  LN 5.6 Loss of Sig (RED)                                09/12/96 17:58:51

This Command: clrlog

OK to clear (y/n)?

clrmsgalm (clear message alarm)

Clears the minor alarm due to an alarm message received at an alarm collection port.

Syntax

clrmsgalm

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	Yes	BPX, IGX			Yes

Related Commands

dspalms, dsplog

clrphyslnalm (clear physical line alarm)

Clears the specified statistical alarm associated with a physical line on a UXM card. The physical line statistical alarms include LOS, LOF, AIS, YEL, LOP, Path AIS, and Path YEL. You can display these alarms by using the dspphysln command. These alarms are shown as the physical line status, at the top of the display, when you run the dspphysln command.

Alarms caused by a network failure cannot be cleared. For example, an alarm caused by a collection of bipolar errors can be cleared, but an alarm caused by a card failure cannot.

Syntax

clrphyslnalm <line_number> <fail_type>

Parameters

Parameter	Description
<line_number>	Specifies the number of the physical line.The format is either slot (for a single-trunk card) or slot.port.
<fail_type>	Specifies the type of alarm to clear. If not specified, the system prompts with Enter Type:.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-5	No	Yes	IGX			Yes

Related Commands

dspphyslns, dspphyslnerrs

Example

Clear an alarm on physical line 10.1.

clrphyslnalm 10.1

sw199          TN    StrataCom       IGX 16    9.3    Apr. 13 2000  18:10 GMT

                             Line Alarm Configuration

                       Minor                               Major