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

Violation Rate Alarm Time Clear Rate Alarm Time Clear

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

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

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

4) Los .0001% 10 min 3 min .01% 30 sec 10 sec

5) Fer .01% 10 min 3 min .1% 200 sec 10 sec

6) CRC .01% 10 min 3 min .1% 200 sec 10 sec

7) Oom .001% 10 min 3 min .1% 30 sec 10 sec

8) Ais16 .0001% 10 min 3 min .01% 30 sec 10 sec




This Command: clrphyslnalm 10.1





Continue?





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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

9) Pkoof .01% 10 min 3 min .1% 200 sec 10 sec

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

11) Badclk .1% 10 min 3 min 1% 50 sec 10 sec

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

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

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

15) Pccpd .001% 5 min 3 min .1% 60 sec 10 sec

16) Bdapd .001% 5 min 3 min .1% 60 sec 10 sec





This Command: clrphyslnalm 10.1




Continue?

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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

17) Bdbpd .001% 5 min 3 min .1% 60 sec 10 sec

18) Lcv 10E-5 10 min 3 min 10E-3 30 sec 10 sec

19) Pcvl 10E-7 10 min 3 min 10E-3 30 sec 10 sec

20) Pcvp 10E-7 10 min 3 min 10E-3 30 sec 10 sec

21) Bcv 10E-7 10 min 3 min 10E-3 30 sec 10 sec

22) Rxvpd 1% 5 min 3 min 4% 60 sec 10 sec

23) Rxtspd .01% 5 min 3 min .1% 60 sec 10 sec

24) Rxbdapd .001% 5 min 3 min .1% 60 sec 10 sec




This Command: clrphyslnalm 10.1




Continue?




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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

25) Rxbdbpd .001% 5 min 3 min .1% 60 sec 10 sec

26) Rxntspd .01% 5 min 3 min .1% 60 sec 10 sec

27) Rxhppd .001% 5 min 3 min .1% 60 sec 10 sec

28) Atmhec .1% 10 min 3 min 1% 120 sec 10 sec

29) FSyncErr .01% 10 min 3 min .1% 200 sec 10 sec

30) Rxspdm .01% 4 min 2 min .001% 30 sec 5 sec

31) CGWpktds .01% 5 min 3 min 1% 60 sec 10 sec

32) CGWcelld .01% 5 min 3 min 1% 60 sec 10 sec




This Command: clrphyslnalm 10.1




Continue?

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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

33) Txntscds .001% 5 min 3 min .1% 60 sec 10 sec

34) Txhpcdsc .001% 5 min 3 min .1% 60 sec 10 sec

35) Txvcdscd .1% 5 min 3 min .0001% 60 sec 10 sec

36) Txtscdsc .01% 5 min 3 min .1% 60 sec 10 sec

37) Txbdacds .001% 5 min 3 min .1% 60 sec 10 sec

38) Txbdbcds .001% 5 min 3 min .1% 60 sec 10 sec

39) Txcbrcds .001% 5 min 3 min .1% 60 sec 10 sec

40) Txabrcds .001% 5 min 3 min .1% 60 sec 10 sec




This Command: clrphyslnalm 10.1

Continue?




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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

41) Txvbrcds .001% 5 min 3 min .1% 60 sec 10 sec

42) TxGwFPds .01% 5 min 3 min 1% 60 sec 10 sec

43) RxGwCLds .01% 5 min 3 min 1% 60 sec 10 sec




This Command: clrphyslnalm 10.1




Enter Type:

clrphyslnerrs (clear UXM physical line errors)

Clears the errors associated with a UXM physical 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 clrphyslnerrs command can clear only those alarms that the collection of statistical data has caused. Alarms caused by a network failure cannot be cleared by clrphyslnerrs.

Syntax

clrphyslnerrs [<line_number>]

Parameters

Parameter	Description
[<line_number>]	Specifies the physical line.The format is either slot (for a single-trunk card) or slot.port.

Attributes

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

Related Commands

dspphyslnerrs, prtphyslnerrs

Example

Clear UXM physical line error counts from line on port 3 of slot 11. In response to the prompt, enter "y" to reset all circuit line error counts to "0."

clrphyslnerrs 11.3

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

Line Alarm Configuration

Minor Major

Violation Rate Alarm Time Clear Rate Alarm Time Clear

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

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

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

4) Los .0001% 10 min 3 min .01% 30 sec 10 sec

5) Fer .01% 10 min 3 min .1% 200 sec 10 sec

6) CRC .01% 10 min 3 min .1% 200 sec 10 sec

7) Oom .001% 10 min 3 min .1% 30 sec 10 sec

8) Ais16 .0001% 10 min 3 min .01% 30 sec 10 sec

This Command: clrphyslnalm 10.1

clrportstats (clear port statistics)

Clears the statistics for any port card. This includes the data byte count in the transmit and receive directions and error counts associated with the port. Statistical accumulation then resumes for that port.

The clrportstats command clears statistics for a virtual port if a virtual port is specified.

Syntax

clrportstats <slot>.<port | *>[.<vport>]

Parameters

Parameter	Description
slot.port	Specifies the slot and port number of the trunk to add.
<port | *>	Specifies the port or asterisk for all ports.
[.<vport>]	Specifies the virtual port

Attributes

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

Related Commands

dspportstats

Example

Clear the port statistics for port 1 on an FRP card in slot 9. Type "y" to confirm.

clrportstats 9.1

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

Port Statistics for 9.1 Cleared: Apr. 13 2000 15:32

Port Speed: 256 kbps Collection Time: 11 day(s) 19:22:09 Corrupted: YES

Bytes Average (kbps) Util (%) Frames

From Port: 0 0 0 0

To Port: 0 0 0 0

Frame Errors LMI Receive Protocol Stats Misc Statistics

Invalid CRC 0 Status Enq Rcvd 0 Avg Tx Port Q 0

Invalid Alignment 0 Status Xmit 0 FECN Frames 0

Invalid Frm Length 0 Asynch Xmit 0 Ratio (%) 0

Invalid Frm Format 0 Seq # Mismatches 0 BECN Frames 0

Unknown DLCIs 0 Timeouts 0 Ratio (%) 0

Last Unknown DLCI 0 Invalid Req 0 Rsrc Overflow 0

Sig Protocol: None DE Frms Dropd 0

This Command: clrportstats 9.1

OK to clear port statistics (y/n)?

Example

Clear the port statistics for port 11.1 for the BXM card. Type "y" to confirm.

clrportstats 11.1

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 13 2000 10:24 GMT




Port Statistics for 11.1 Cleared: Dec. 13 2000 10:00

Port Speed: 353208 cps Collection Time: 0 day(s) 00:21:59 Corrupted: NO




Cells CLP (EFCI)

Rx Port: 0 0 --

Tx Port: 248 0 --





Unkn Addr (UA): 248 Rx OAM Cells : 0 Rx Clp 0 Cells: 0

Rx Clp 0 Dscd : 0 Rx Clp 1 Dscd : 0 Tx Clp 0 Cells: 248

Tx OAM Cells : 248 Rx RM Count : 0 Tx RM Count : 0

Lst Unk VpiVci: 0.0




UA sums across ports in port group.





This Command: clrportstats 11.1





OK to clear port statistics (y/n)?

clrrtrcnf (clear router configuration file)

Clears the IOS configuration file stored in the NPM RAM buffer. This buffer must be cleared before a new save/restore configuration file, a new firmware image, or a new IOS configuration file can be stored in the NPM RAM buffer. This is because the NPM RAM buffer can be used only by one application at a time.

The clrrtrcnf command supports the URM Remote Router Configuration feature introduced in Release 9.3.30. This feature allows you to start up or restart the URM embedded IOS router with an IOS configuration file that is downloaded from a TFTP server. For additional information on the URM and Remote Router Configuration feature see the cnfrtr command description.

Syntax

clrrtrcnf

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
SuperUser	Yes	Yes	IGX	Yes	Yes	Yes	NO

Related Commands

burnrtrcnf, cnfrtr, cnfrtrcnfmastip, dspcnf, dsprtr, dsprtrcnfdnld, dsprtrslot

Example

Clear the IOS configuration file from the NPM RAM buffer. The clrrtrcnf command prompts you to confirm the clear procedure before it executes.

clrrtrcnf

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:33 GMT




















This Command: clrrtrcnf





Router configuration file will be deleted from NPM, Continue (y/n)?

clrscrn (clear terminal screen)

Clears the terminal screen.

Syntax

clrscrn

Attributes

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

Related Commands

redscrn, prtscrn

clrslotalms (clear slot alarms)

Clears the alarm messages associated with the alarms displayed for the Display Slot Alarms command. Alarm messages are cleared for the specified slot only. These counters should be cleared before beginning any monitoring session. This command prompts the user with an "OK to Clear?" message before actually clearing the counters.

Use dspslotalms to observe the slot alarms. Refer to the dspslotalms command for a description of the counters cleared by the clrslotalms command.

Syntax

clrslotalms <slot>

Parameters

Parameter	Description
<slot>	Specifies the number of the shelf slot in the BPX node.

Attributes

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

Related Commands

dspslotalms

Example

Clear alarm on slot 3.

clrslotalms 3

clrsloterrs (clear slot errors)

Clears the counters for the error counts displayed for the Display Slot Errors command. Counters are cleared for the specified slot only. These counters should be cleared before beginning any monitoring session. This command prompts the user with an "OK to Clear?" message before actually clearing the counters.

Use dspsloterrs to observe the slot errors. Refer to the dspsloterrs command for a description of the counters cleared by the clrsloterrs command.

Syntax

clrsloterrs <slot number | *>

Parameters

Parameter	Description
<slot number | *>	Specifies the shelf slot in the node or an asterisk for all shelf slots.

Attributes

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

Related Commands

dspsloterrs

Example

Clear the slot errors in slot 3.

clrsloterrs 3

clrtrkalm (clear trunk alarm)

Clears statistical alarms associated with either a physical or virtual trunk. Note that if a virtual trunk is specified for a command that configures information related to the physical port, then the physical port information is configured for all virtual trunks. This means that using clrtrkalm clears parameters on a logical trunk basis, but any changes automatically affect all trunks on the port when you change a physical option. Any changes you make to a virtual trunk on a port affect all virtual trunks on that port.

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

The clrtrkalm 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.

---

Note A virtual trunk also has trunk port alarms that are shared with all the other virtual trunks on that port. You clear and set these alarms together for all the virtual trunks sharing the same port.

---

Alarms for the BXM and UXM card types are cleared and displayed differently.

Syntax

clrtrkalm <trunk number> <failure type>

Parameters

Parameter	Description
<trunk number>	Specifies the trunk. Note that for virtual trunks, no virtual trunk parameter is required—just slot.port. The format is either slot (for a single-trunk card) or slot.port.
<failure type>	Specifies the type of alarm to clear.

Attributes

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

Related Commands

dsptrks, dsptrkerrs

Example

Display trunk alarm configuration.

clrtrkalm 4.2

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

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:38 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

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

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

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

4) Los .0001% 10 min 3 min .01% 30 sec 10 sec

5) Fer .01% 10 min 3 min .1% 200 sec 10 sec

6) CRC .01% 10 min 3 min .1% 200 sec 10 sec

7) Oom .001% 10 min 3 min .1% 30 sec 10 sec

8) Ais16 .0001% 10 min 3 min .01% 30 sec 10 sec





This Command: clrtrkalm 4.2





Continue? y




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

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:34 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

9) Pkoof .01% 10 min 3 min .1% 200 sec 10 sec

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

11) Badclk .1% 10 min 3 min 1% 50 sec 10 sec

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

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

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

15) Pccpd .001% 5 min 3 min .1% 60 sec 10 sec

16) Bdapd .001% 5 min 3 min .1% 60 sec 10 sec





This Command: clrtrkalm 4.2





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:34 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

17) Bdbpd .001% 5 min 3 min .1% 60 sec 10 sec

18) Lcv 10E-5 10 min 3 min 10E-3 30 sec 10 sec

19) Pcvl 10E-7 10 min 3 min 10E-3 30 sec 10 sec

20) Pcvp 10E-7 10 min 3 min 10E-3 30 sec 10 sec

21) Bcv 10E-7 10 min 3 min 10E-3 30 sec 10 sec

22) Rxvpd 1% 5 min 3 min 4% 60 sec 10 sec

23) Rxtspd .01% 5 min 3 min .1% 60 sec 10 sec

24) Rxbdapd .001% 5 min 3 min .1% 60 sec 10 sec





This Command: clrtrkalm 4.2





Continue? y




------------------------------------SCREEN 4-----------------------------------

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:34 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

25) Rxbdbpd .001% 5 min 3 min .1% 60 sec 10 sec

26) Rxntspd .01% 5 min 3 min .1% 60 sec 10 sec

27) Rxhppd .001% 5 min 3 min .1% 60 sec 10 sec

28) Atmhec .1% 10 min 3 min 1% 120 sec 10 sec

29) FSyncErr .01% 10 min 3 min .1% 200 sec 10 sec

30) Rxspdm .01% 4 min 2 min .001% 30 sec 5 sec

31) CGWpktds .01% 5 min 3 min 1% 60 sec 10 sec

32) CGWcelld .01% 5 min 3 min 1% 60 sec 10 sec





This Command: clrtrkalm 4.2





Continue? y




------------------------------------SCREEN 5-----------------------------------

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:35 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

33) Txntscds .001% 5 min 3 min .1% 60 sec 10 sec

34) Txhpcdsc .001% 5 min 3 min .1% 60 sec 10 sec

35) Txvcdscd .1% 5 min 3 min .0001% 60 sec 10 sec

36) Txtscdsc .01% 5 min 3 min .1% 60 sec 10 sec

37) Txbdacds .001% 5 min 3 min .1% 60 sec 10 sec

38) Txbdbcds .001% 5 min 3 min .1% 60 sec 10 sec

39) Txcbrcds .001% 5 min 3 min .1% 60 sec 10 sec

40) Txabrcds .001% 5 min 3 min .1% 60 sec 10 sec





This Command: clrtrkalm 4.2





Continue? y




------------------------------------SCREEN 6-----------------------------------

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 10:35 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

41) Txvbrcds .001% 5 min 3 min .1% 60 sec 10 sec

42) TxGwFPds .01% 5 min 3 min 1% 60 sec 10 sec

43) RxGwCLds .01% 5 min 3 min 1% 60 sec 10 sec

44) CGWfrmab .01% 5 min 3 min 1% 60 sec 10 sec





This Command: clrtrkalm 4.2





Enter Type:

Example

Clear alarms on trunk 4.2

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

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 11:09 GMT





Last Command: clrtrkalm 4.2 4




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

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 11:05 GMT




TRK Type Current Line Alarm Status Other End

4.2 OC3 Clear - OK sw180/5.1

4.4 OC3 Clear - OK sw53/11.2

14 T1/24 Clear - OK sw180/8





Last Command: dsptrks

clrtrkerrs (clear trunk errors)

Clears the statistical error counters at the node for the specified physical or virtual trunk. You should do this before you begin any monitoring session and periodically thereafter to determine exactly when a trunk problem begins. Use dsptrkerrs to observe errors without clearing counters.

Syntax

clrtrkerrs <trunk_number | *>

Parameters

Parameter	Description
<trunk_number | *>	Specifies the trunk counter to clear or asterisk for all trunks.

Attributes

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

Related Commands

dsptrkerrs, prttrkerrs

Example

Clear all trunk errors.

clrtkerrs *

pubsbpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 19:37 PST




Total Errors




Code Rx Cell Out of Loss of Frame HCS Tx Cell Cell Cell

TRK Errors Dropped Frames Signal BitErrs Errors Dropped Errors Oofs

1.1 0 0 0 0 - 0 0 - -

1.2 0 0 0 0 - 0 0 - -









This Command: clrtrkerrs *





Clears errors on all trunks. Continue (y/n)?

clrtrkstats (clear trunk statistics)

Clears the node counters used for the Display Trunk Statistics. Counters are cleared for a physical or virtual trunk. You should clear these counters before beginning any monitoring session. This is similar to the clrtrkerrs command for errors. This command prompts you with an "OK to Clear?" message before actually clearing the counters.

Use dsptrkstats to observe the trunk statistics. See the dsptrkstats command for a description of the counters cleared by the clrtrkstats command.

Syntax

clrtrkstats <trunk number>

Parameters

Parameter	Description
trunk number	Specifies the trunk. Note that, for virtual trunks, no virtual trunk parameter is required—just slot.port. The format is either slot (for a single-trunk card) or slot.port.

Attributes

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

Related Commands

dsptrkstats

Example

Clear the statistics on trunk 4.4.

clrtrkstats

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 11:17 GMT




Trunk 4.4 Clear - OK

Collection Time: 0 day(s) 00:00:00 Clrd: 12/11/00 16:18:00

Type Count

QBIN: NTS Cells Tx to line 0

QBIN: Tx NTS Cells Received 0

QBIN: Tx NTS Cells Discarded 0

QBIN: Hi-Pri Cells Tx to line 0

QBIN: Tx Hi-Pri Cells Received 0

QBIN: Tx Hi-Pri Cells Discarded 0

QBIN: Voice Cells Tx to line 0

QBIN: Tx Voice Cells Received 0

QBIN: Tx Voice Cells Discarded 0

QBIN: TimeStamped Cells Tx to ln 0

QBIN: Tx TS Cells Received 0

QBIN: Tx TS Cells Discarded 0




This Command: clrtrkstats 4.4





OK to clear (y/n)?

cnfabrparm (configure assigned bit rate queue parameters)

Configures parameters for the Assigned Bit Rate (ABR) queue on all ports on the selected UXM.

You can toggle the Egress/Ingress Congestion Information control and/or the ABR RM cell Explicit Rate stamping parameters on and off. All ports on the UXM in the selected slot are dynamically reconfigured according to the new parameters.

Syntax

cnfabrparm <slot> <CI_control> <ER_control>

Parameters

Parameter	Description
<slot>	Specifies the slot number of the UXM card.
<CI_control>	Enables or disables Egress/Ingress Congestion Information control.
<ER_control>	Enables or disables ABR RM cell Explicit Rate stamping.

Attributes

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

Related Commands

cnfportq, dspportq, cnfport, dspport

Example

Configure assigned bit rate queue parameters for slot 5.

cnfabrparm 5

sw205 TN SuperUser IGX 8420 9.3 Apr. 13 2000 04:50 GMT

ABR Configuration for UXM in slot 5

CI Control : N

Egress ER Stamping : N




This Command: cnfabrparm 5

cnfapsln (configure APS line parameters)

Configure SONET APS Line Redundancy according to industry standards. The IGX platform supports ATM trunk redundancy; the BPX supports SONET APS line redundancy. APS line redundancy provides a standards-based solution to line redundancy.

---

Note For the Annex A protocol, you cannot set both the Bidirectional and Nonrevertive options—they are invalid combinations. For the Annex B protocol option, the default is Bidirectional and Nonrevertive.

---

Syntax

cnfapsln <slot.port> <SFBER> < SDBER> <Revertive_mode> <WTR> <Direction>

Parameters

Parameter	Description	Range/Options
slot.port	Slot and port of the line you want to configure.	-
SFBER (Signal Fail Bit Error Rate)	Signal Fail Bit Error Rate threshold at which point an APS switch occurs.	Default: 3 Range: 3-12
SDBER (Signal Detect Bit Error Rate)	Signal Detect Bit Error Rate for line degradation.	Default 5 Range: 5-12
Revertive mode	Revert to Working line after Wait to Restore interval expires. You must enter the number 0 or 1. This applies only to automatic switches. Revertive switching does not take place as a result of user-initiated switching. For Annex A, the default is non-revertive. For Annex B, the default is non-revertive. For Annex B, you are not allowed to change to unidirectional or revertive mode.	Default: 1 Range: 0-1 0 = revertive 1 = non-revertive
WTR (Wait to Restore)	Wait to restore interval. After a switch from a Working to a Protection line, this is the interval in minutes to wait before attempting to switch back to the Working line. This is not applicable if the Revertive Mode option is set to N (non-revertive).	Default: 5 Range: 1-12 minutes
Direction	Direction of switching. Unidirectional is switching in only one direction. With Bidirectional, after one side switches, then the other side also switches. For Annex A, the default is unidirectional. For Annex B, default is bidirectional. For Annex B, you are not allowed to change to unidirectional or revertive mode.	Default: 0 (unidirectional) Range: 0-1, where 0 is unidirectional and 1 is bidirectional.

Attributes

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

Related Commands

addapsln, delapsln, cnfapsln, dspapsln, dsplog, dspalms, switchapsln

Example

Configures APS line parameters.

cnfapsln 1.1

alexa TRM genre BPX 8620 9.3 Apr. 13 2000 16:15 PDT




APS Configuration parameters for Working, Protection lines 1.1, 1.2




APS Protocol: 1+1




Signal Fail BER threshold (10 to the -n): 3

Signal Detect BER threshold (10 to the -n): 5

Revertive Switching: Yes

Wait to Restore Timer: 5 minutes

Uni/Bi Directional Switching: Unidirectional




Command: cnfapsln 1.1

Example

Configures APS line parameters.

cnfapsln 1.1

colossus TN StrataCom BPX 8600 9.3 Apr. 13 2000 16:08 PDT




APS Configuration parameters for Working, Protection lines 1.1, 1.2




APS Protocol: 1+1




Signal Fail BER threshold (10 to the -n): 3

Signal Detect BER threshold (10 to the -n): 5

Revertive Switching: Yes

Wait to Restore Timer: 5 minutes

Uni/Bi Directional Switching: Unidirectional




Command: cnfapsln 1.1

Example

Configures APS line parameters for APS 1:1 line redundancy

cnfapsln 6.3

colossus TN StrataCom BPX 8600 9.3 Apr. 13 2000 16:08 PDT




APS Configuration parameters for Working, Protection lines 6.3, 6.4




APS Protocol: 1+1




Channels Halved for APS operation: Yes

APS Standard for Card: GR-253




Signal Fail BER Threshold (10 to the -n): 3

Signal Detect BER Threshold (10 to the -n): 5

Uni/Bi Directional Switching: Bidirectional

Revertive Switching: Yes

Wait to Restore Timer: 5 minute(s)





Command: cnfapsln 6.3

cnfasm (configure ASM card)

Sets configurable parameters associated with the BPX Alarm and Status Monitor card in slot 15. Because this card always resides in slot 15, entering the slot number is unnecessary. Robust alarms are generated for these alarm conditions:

•Power supply, temperature, fan, and DC-voltage level alarms. (Some of these conditions already generate Robust Alarms on the IGX.)

•Connection AIS alarm

•Bus failure

•External clock source failure

•Multiple invalid login attempts on a user port (potential security threat)

•Excessive CPU and memory usage on switch processor card

These alarm conditions above appear in the maintenance log or in the node command line interface commands (dspasm), and are not also reported as SNMP trap to the customer NMS. (Such traps are generated by the Cisco WAN Manager RTM proxy upon receiving Robust Alarms from a switch.)

In Release 9.2 and above, robust alarms are generated by the BPX when power and temperature alarm conditions are detected by the ASM card. The ASM card monitors and reports events involving:

•Power supplies

•Cabinet temperature

•Cooling fan speed

•DC-voltage level

You configure and control the reporting of these events by using the cnfasm command, where you can enable or disable each alarm. For power supply failure/removal events, you can also specify the alarm class (that is, Major vs. Minor).

A robust alarm is generated by these events:

•The IGX platform when a DC-voltage out-of-range condition occurs.

•All switch platforms (IGX, BPX) when:

–An Alarm Indicator Signal (AIS) condition is detected on a PVC. The alarm now has an NNI Status field that previously appeared in the Connection NNI Alarm message.

–A bus failure or failure cleared event occurs. (In releases previous to Release 9.2, such events are reported through maintenance log messages.)

–An external clock source failure or failure cleared event occurs.

–The number of successive invalid login attempts on a user port exceeds the current threshold setting on the switch. You set the threshold by using the cnfsysparm command.)

–The processor card CPU utilization of the IDLE process falls below a fixed threshold. The purpose of the alarm is to indicate the possible degradation of service caused by processor load reaching an abnormally high level.

Syntax

cnfasm

Attributes

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

Related Commands

dspasm

Example

Configure parameters for the ASM card

cnfasm

D1.jea TRM SuperUser BPX 8600 9.3 Apr. 13 2000 12:25 GMT

[1] Cabinet temp threshold: 50 C [4] Polling interval (msec): 10000

[2] Power A deviation: 6 V [5] Fan threshold (RPM): 2000

[3] Power B deviation: 6 V

ALM ALM

[6] ACO button - [14] BPX card slot -

[7] History button - [15] PSU A failure Y

[8] Cabinet temp Y [16] PSU A removed Y

[9] Power A volt Y [17] PSU B failure Y

[10] Power B volt Y [18] PSU B removed Y

[11] Fan 1 RPM Y

[12] Fan 2 RPM Y

[13] Fan 3 RPM Y

This Command: cnfasm

Which parameter do you wish to change:

cnfatmcls (configure class template)

Use cnfatmcls to modify the ten Cisco-supplied class templates for ATM connection configuration. (The addcon command can take a class as an input.)

When you enter the number of the class to configure, the display shows the current value of each parameter in the class. For each item in the class, a prompt appears for changing or keeping the current value.

You can use cnfatmcls and cnfcls to configure the rt-VBR ATM connection class. You can use dspatmcls and dspcls to display the connection parameters for the rt-VBR and nrt-VBR connection classes.

The rt-VBR connections are configured per class 3 service parameters, and nrt-VBR connections are configured per class 2 service parameters. You can change these class parameters by using the cnfcls/cnfatmcls commands, or you can enter the parameters individually for each connection by specifying yes to the extended parameters prompt of the addcon command.

---

Note For a new node running software Release 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes. Therefore, it won't have the rt-VBR connection class 3. However, you can configure the connection classes to desired service and parameters by using the cnfcls/cnfatmcls commands. For nrt-VBR connections in a new node, running Release 9.2.20, a number of connection classes are preconfigured, including 2, 4, 5, and 6.

---

Syntax

cnfatmcls <class number> [optional parameters]

Parameters

Parameter	Description
class	Specifies the class to configure. Range: 1-10
optional parameters	Individual parameters are specific to the type of connection (rt-VBR, nrt-VBR, CBR, UBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, ATFXFST). Each is prompted one at a time. Refer to the dspcls command to see the parameters in each of the classes.

Attributes

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

Related Commands

addcon, cnfatmcls, dspatmcls, cnfcls, dspcls

Example

Configure ATM connection class 10. The command line interface (CLI) displays the current settings and requests the class type (see System Response 1). After you enter a class type, the CLI prompts you to specify each parameter for the selected class type (ABRSTD as System Response 2 shows).

cnfatmcls 10

sw60 TN SuperUser BPX 8620 9.3 Date/Time Not Set

ATM Connection Classes

Class: 10 Type: CBR

PCR(0+1) % Util CDVT(0+1) Policing

4000/4000 100/100 10000/10000 4

Description: "Default CBR 4000"




This Command: cnfatmcls 10




Enter class type (rt-VBR, nrt-VBR, UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, ATFXFST):





sw60 TN SuperUser BPX 8620 9.3 Date/Time Not Set

ATM Connection Classes

Class: 10 Type: ABRSTD

PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC

4000/4000 100/100 4000/4000 10000/10000 n

Description: "Default CBR 4000"




This Command: cnfatmcls 10 abrstd * * * * *




Do you want this change (y/n)?

Example

Configure ATM connection class 3 for rt-VBR class type connection parameters. The command line interface (CLI) displays the current settings and requests the class type.

cnfatmcls 3

sw60 TN SuperUser BPX 8620 9.3 Date/Time Not Set

ATM Connection Classes

Class: 3 Type: rt-VBR

PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR

2000/2000 100/100 10000/10000 n 2000/2000




MBS Policing

1000/1000 3

Description: "Default rt-VBR 2000"





This Command: cnfatmcls 3

Enter class type (rt-VBR, nrt-VBR, UBR, CBR, ATFST, ATFR, ABRSTD, ABRFST, ATFT, ATFX, ATFTFST, ATFXFST):

cnfbmpparm (configure priority bumping)

Configures priority bumping parameters.

Priority bumping requires a number of configuration parameters saved in the BRAM and sent to the Standby Processor card. The parameters consist of a feature activation flag, a bundle size, and a set of seven CoS bands (0-7), implicitly defining eight CoS bands. Unlike Automatic Routing Management capabilities, which include a number of different operational flavors, priority bumping is strictly a CoS-based (or, more accurately, band-based) algorithm. Each band is defined by the low-end CoS value within the band. Band 0 (implicitly defined) is the most important one, whereas Band 7 is the least important. Each connection within a band is equally important, despite the fact that it might be tagged with a different CoS. Note that Band 0 is not bumpable.

A minimum of two bands are required to be defined for the priority bumping feature to work. A network with only one band is equivalent to having the priority bumping feature disabled.

The entire network must be upgraded to 9.3.0 in order for the priority bumping feature to be operational.

Use these steps to set up priority bumping:

---

Step 1 For a BPX switch, a license must be purchased for each BPX node on the network using the cnfswfunc 6 e command (see the first Example). The Cisco System Engineer enters the password to purchase priority bumping license. The license is granted immediately with the correct password.

Step 2 Before you enable priority bumping, ensure that a minimum of two bands exist by using the dspbmpparm command.

---

Caution If less than two bands exist, the BCC aborts.

---

The following sample output shows that two bands do not exist:

XXX TN Cisco BPX 8620 9.3.0     Feb. 22 2006 12:12 GMT




Priority Bumping Enabled [ NO]

Priority Bumping Bundle [ 0]

Priority Bumping Bands:

Band 0 (non-bumpable) [ 0-15]






Priority Bumping Active on this node [ NO]

Number of bumpable Bands [ 0]




Last Command: dspbmpparm




If a minimum of two bands do not exist, use the cnfbmpparm command to create the bands. The following sample output shows the default values for the bumping bands:

XXX TN Cisco BPX 8620 9.3.0    Feb. 22 2006 12:10 GMT

1 Priority Bumping Enabled [ NO]

2 Priority Bumping Bundle [ 50] (D)

3 Priority Bumping Bands:

Band 1 [ 2] (D)

Band 2 [ 4] (D)

Band 3 [ 6] (D)

Band 4 [ 8] (D)

Band 5 [ 10] (D)

Band 6 [ 12] (D)

Band 7 [ 14] (D)





Last Command: cnfbmpparm 3 2 4 6 8 10 12 14

Step 3 From either an IGX switch or a BPX switch, enable priority bumping from any node on the network using the cnfbmpparm command.

Parameter changes made at one node are propagated to the rest of the network, then updated both to the BRAM and Standby Processor card.

The default configuration when priority bumping is enabled is shown below:

Band	0	1	2	3	4	5	6	7
CoS	0/1	2/3	4/5	6/7	8/9	10/11	12/13	14/15

Step 4 To test priority bumping (optional) you can create an environment to "stress" bandwidth resources and see how the feature works. For example:

1. Delete a trunk.

2. Physically remove a cable to a connection.

3. Add connections to create limited bandwidth resources on a trunk.

You then can use the dspcons command to view connection routing.

Step 5 To display the CoS-based loads, use the dspload command. Information about the CoS-based loads within each band helps you determine where to add connections in a priority bumping environment. The loads are displayed for a trunk. The total capacity is shown at the bottom of the display, and the load for each Band is displayed at the top. Any connection that is added to a band could bump and utilize bandwidth resources for the band that follows it; for example, adding a connection to Band 5 can bump connections in Band 6 and Band 7, allowing connections in Band 5 to utilize the bandwidth from those bands.

---

Limitations

•Priority bumping does not support a situation when VPC CONIDs (or any resources other than bandwidth and LCN) are in short supply.

•Priority bumping can only be activated when all nodes are upgraded to Release 9.3.0 switch software, or higher.

•In a 9.3 network, there can be some nodes (BPX only) that do not purchase the priority bumping feature. Consequently, they are not capable of participating in the priority bumping operations. These nodes are not chosen during route selection unless the trunks leading to or from the nodes have sufficient network resources.

•The maximum number of low priority connections that can be bumped in each attempt to route a high priority connection is 1023.

•The maximum number of connections that can be bundled in a routing attempt is 50.

Syntax

cnfbmpparm [1 [<enable>|<disable>] ]

[2 <bundle> ]

[3 <b1> <b2> [<b3> [<b4> [<b5> [<b6> [<b7>]]]]]]

Parameters

Parameter	Values	Description
Priority Bumping Enabled	ON or OFF Default OFF	This flag specifies whether the priority bumping feature is activated on the node.
Priority Bumping Bundle	Range: 1-50 Default 10	The number of connections that can be selected in a priority bumping routing request.
Bumping Band 1	Range: 1-50 Default 2	The lowest value in the second most important CoS band. Connections with a CoS value below Bumping Band 1 are implicitly grouped as the most important band, Band 0. Connections in Band 0 can bump those in other bands, but cannot be bumped. Connections in Band 1 can bump those in bands 2-7, and can only be bumped by those in Band 0.
Bumping Band 2	Range: 1-15 Default 4	The lowest value in the third most important CoS band. Connections in this band can bump those in bands 3-7, and can be bumped by those in bands 0-1. Bumping Band 2 cannot be less than Bumping Band 1. If they are equal, the band definition ends.
Bumping Band 3	Range: 1-15 Default 6	The lowest value in the fourth most important CoS band. Connections in this band can bump those in bands 4-7, and can be bumped by those in bands 0-2. Bumping Band 3 cannot be less than Bumping Band 2. If they are equal, the band definition ends.
Bumping Band 4	Range: 1-15 Default 8	The lowest value in the fifth most important CoS band. Connections in this band can bump those in bands 5-7, and can be bumped by those in bands 0-3. Bumping Band 4 cannot be less than Bumping Band 3. If they are equal, the band definition ends.
Bumping Band 5	Range: 1-15 Default 10	The lowest value in the sixth most important CoS band. Connections in this band can bump those in bands 6-7, and can be bumped by those in bands 0-4. Bumping Band 5 cannot be less than Bumping Band 4. If they are equal, the band definition ends.
Bumping Band 6	Range: 1-15 Default 12	The lowest value in the seventh most important CoS band. Connections in this band can only bump those in Band 7, and can be bumped by those in bands 0-5. Bumping Band 6 cannot be less than Bumping Band 5. If they are equal, the band definition ends.
Bumping Band 7	Range: 1-15 Default 14	The lowest value in the least important CoS band. Connections in this band cannot bump, but can be bumped by those in bands 0-6. Bumping Band 7 cannot be less than Bumping Band 6.

Attributes

Privilege	Jobs	Log	Node	Card Type and Memory Requirement	Lock
1-2	No	No	IGX or BPX	NPM-32 NPM-64 BCC-64.	Yes

Related Commands

dspbmpparm, dspbmpstats

Example

Purchase priority bumping on a BPX using the cnfswfunc command, option 6

cnfswfunc 6 e

---------------------------------------------




bpx1 TN StrataCom BPX 8620 9.3.0K Jan. 26 2000 14:16 PST




Index Status Function




1 Enabled Configuration Save/Restore

2 Enabled ForeSight

3 Enabled Multiple VTs (6 sessions enabled)

4 Enabled Virtual Trunks

5 Enabled ABR standard with VSVD

6 Enabled Priority Bumping




Last Command: cnfswfunc 6 e

Example

CoS-based loads.

igxaf1 TN StrataCom IGX 8420 9.3 the.0F Jan. 10 2000 15:33 PST




Configured Trunk Loading: TRK igxaf1 16.4--10.1 bpx2

Band: CoS Xmt-c Rcv-c

B1 : 1- 1 191 191 Conid In Use+Avail 256

B2 : 2- 2 288 288

B3 : 3- 3 1036 1036 VPC conids: 0/256

B4 : 4- 4 216 216

B5 : 5- 5 216 216 Trunk type is Terrestrial

B6 : 6-13 900 900 Trunk supports cell routing

B7 :14-15 300 300 Trunk does not use ZCS

Total In Use 3147 3147 Trunk end supports all gateway types

Reserved 400 400 Gateway conns: 28/200

Available 75 75 Traffic: V TS NTS FR FST CBR NRT-VBR ABR

Total Capacity 3622 3622 RT-VBR

Lcn/GwLcn bmap, oe: 7F/5F,7F/00

Example

Default Setup, Eight CoS Bands.

The default configuration is priority bumping disabled. However, when the feature is simply enabled (without changing the other banding parameters), the network would operate with eight CoS bands.

Band	0	1	2	3	4	5	6	7
CoS	0/1	2/3	4/5	6/7	8/9	10/11	12/13	14/15

Example

Refined Granularity of CoS Banding.

A sample PB_Band configuration of 1, 2, 3, 4, 5, 11 and 13 provides a better granularity of CoS banding at the more important end of the spectrum.

Band	0	1	2	3	4	5	6	7
CoS	0	1	2	3	4	5-10	11/12	13-15

Another sample PB_Band configuration of 3, 5, 8, 12, 13, 14 and 15 provides a better granularity of CoS banding at the less important end of the spectrum.

Band	0	1	2	3	4	5	6	7
CoS	0-2	3/4	5-7	8-11	12	13	14	15

Example

Reduced CoS Banding, Better Operational Performance.

A sample PB_Band configuration of 1, 2, 8, 9, 9, 9 and 9 provides a reduced CoS banding, thus allowing better routing performance (with fewer iterations through the bands).

Band	0	1	2	3	4
CoS	0	1	2-7	8	9-15

This screen illustrates how the bands are configured, then displayed.

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

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 13 2000 10:03 GMT




1 Priority Bumping Enabled [ YES]

2 Priority Bumping Bundle [ 50] (D)

3 Priority Bumping Bands:

Band 1 [ 1] (D)

Band 2 [ 2] (D)

Band 3 [ 8] (D)

Band 4 [ 9] (D)

Band 5 [ 9] (D)

Band 6 [ 9] (D)

Band 7 [ 9] (D)





Last Command: cnfbmpparm 3 1 2 8 9 9




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

sw53 TN Cisco BPX 8620 9.3.m0 Dec. 13 2000 10:00 GMT




Priority Bumping Enabled [ YES]

Priority Bumping Bundle [ 50]

Priority Bumping Bands:

Band 0 (non-bumpable) [ 0- 0]

Band 1 [ 1- 1]

Band 2 [ 2- 7]

Band 3 [ 8- 8]

Band 4 [ 9-15]





Priority Bumping Active on this node [ NO]

Number of bumpable Bands [ 0]





Last Command: dspbmpparm

Example

Minimum CoS Banding.

Another sample PB_Band configuration of 1, 1, 1, 1, 1, 1 and 1 provides a minimum CoS banding of only two bands).

Band	0	1
CoS	0	1-15

cnfbpnv (set backplane type to new)

Use the command cnfbpnv to configure the backplane, if the backplane is so enabled. This operation is necessary in some instances to program the NOVRAM.

Issue the dspbpnv command to see the NOVRAM setting. For some operations, it is necessary to verify the NOVRAM in order to ensure feature compatibility. For example, in order for the BPX 8600 to operate at 19.2 Gbps with the BCC-4V, it must have the NOVRAM Word #2 set to 0001 (which indicates that the backplane version is new). If it instead has the NOVRAM Word#2 set to 0000 (indicating that the backplane version is old) the switch cannot run with a 19.2 Gbps peak throughput. If you visually verify that the backplane is a 19.2 Gbps backplane (see note below), but the backplane NOVRAM Word #2 has not been set to 0001, then issue the cnfbpnv command to program the NOVRAM.

---

Step 1 Enter cnfbpnv, and the response is:

Are you sure this is a new backplane (y/n)

Enter y

Step 2 Use the command dspbpnv to confirm the change. It should display:

Word #2 =0001

---

---

Note The 19.2 backplane can be visually identified by the small white card slot fuses at the bottom rear of the backplane. These fuses are approximately 1/4 inch high and1/8 inch wide. The 9.6 Gbps backplane does not have these fuses. If the BPX switch is a late model, then a 19.2 Gbps backplane is installed.

---

Syntax

cnfbpnv

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
Super User	No	No	BPX	No	OK	Yes	No

Related Commands

dspbpnv

cnfbus (configure active bus)

Use the dspbuses command to display the current bus configuration when configuring the buses with the cnfbus command. It should only be necessary to use this command when a problem is suspected with the currently active System Bus. As a safeguard against bus failure, each node is equipped with redundant System Buses, Bus A and Bus B. Either bus can be configured as the active bus and the remaining bus is reserved as standby.

Syntax

cnfbus <a | b | t | l>

Parameters

Parameter	Description
a	Select Bus A as the active bus.
b	Select Bus B as the active bus.
t	Toggles between buses. It changes the standby bus to the active bus and the active bus to the standby bus.
l	Toggles between buses and lanes. It changes the standby bus to the active bus and the standby lane to the active lane and the active bus to the standby bus and the active lane to the standby lane.

Attributes

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

Related Commands

dspbuses

Example

Configure the system bus to toggle.

cnfbus t

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 19:42 GMT




Bus Info




Bus Bandwidth usage in Fastpackets/second (Snapshot)




Allocated = 20000 ( 2%)




Available = 1148000 (98%)





-----------

Bus A: Standby - OK

Bus B: Active - OK





Last Command: cnfbus t





Next Command:

cnfbusbw (configure UXM card bus bandwidth)

Configures the amount of bandwidth allocated on the bus for a specified UXM card. The default amount of bus bandwidth allocated depends on the connection type you are adding; 77 Mbps (1/2 OC-3 rate) of bus bandwidth is allocated to an OC-3 port card when the first line is upped. For the T3/E3 line, 44/34 Mbps (T3/E3 rate) is allocated as default bus bandwidth. For a T1/E1 line, the amount of bandwidth allocated will be enough for all T1/E1 lines supported on the card.

After the default bus bandwidth is allocated, the system will not allocate any more bus bandwidth to the card when you activate more lines, so you must manually allocate the bus bandwidth to the card using the cnfbusbw command. All ports on the UXM in the selected slot are dynamically reconfigured according to the new parameters.

Syntax

cnfbusbw <slot> <bw>

Parameters

Parameter	Description
<slot>	Specifies the slot number of the UXM.
<bw>	Specifies the amount of bandwidth to be allocated in UBUs, which the system converts to either FastPackets per second or cells per second. The maximum rate you can set is 288,000 cells per second, which is 235 UBUs. Each UBU is the equivalent of 4000 cells per second.

Display Fields

Display	Description
Minimum Required Bandwidth	Minimum bandwidth in FastPackets per second and cells per second required for all connections currently configured on this card. This is calculated by UXM firmware as connections are added.
Maximum Port Bandwidth	Total bandwidth of all active trunks/ports on this card in FastPackets per second, cells per second and UBUs.
Average Bandwidth and Peak Used Bandwidth	Statistics counters maintained by UXM firmware. These statistic counters display FastPackets per second, cells per second, and UBUs. Use this information when calculating the amount of bus bandwidth to be allocated. These counters are cleared when the UXM card is reset.
Last Updated time	Shows the time when the counters were last updated. This will be the current time if you answered yes to the Get updated bandwidth info from card (Y/N)? prompt or entered the command with the u parameter.
Allocated Bandwidth	The bandwidth allocated for this card using the cnfbusbw command. Allocated bandwidth is specified in UBU units and converted to either FastPackets per second or cells per second by the system.

Attributes

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

Related Commands

dspbusbw (a standard user command)

Example

Configure the bandwidth on the UXM card in slot 3 of the IGX.

cnfbusbw 3

sw108 VT Cisco IGX 8420 9.3.p8 Dec. 13 2000 11:47 GMT




Bus Bandwidth Usage for UXM card in slot 3 Last Updated on 12/13/00 11:45:46




FPkts/sec Cells/sec UBUs

Minimum Reqd Bandwidth: 0 19549 5

Average Used Bandwidth: 0 0 0

Peak Used Bandwidth: 0 2 1

Maximum Port Bandwidth: - 1059624 265




Allocated Bandwidth: 1

(Cell Only): - 4000

(Cell+Fpkt): 2000 3000

(Fpkts / 2 + Cells) <= 4000





Reserved Bandwidth: - 4000 1




Last Command: cnfbusbw 3

cnfcassw (configure CAS switching)

Configures a UVM to convert channel associated signaling (CAS) and dual-tone multi-frequency (DTMF) tones to common channel signaling (CCS) call control messages. This conversion is necessary for voice networks in which a Voice Network Switch (VNS) uses SVCs to route calls from a CAS-based PBX through a WAN. Model B or later firmware on the UVM is necessary.

Before you can execute cnfcassw:

•The line to which you apply cnfcassw must be up.

•If any connections exist on the line, you cannot change the cnfcassw parameters. However, you can execute the command to see the current parameters in the cnfcassw display.

•You cannot configure a line for both CAS-switching and pass-through.

•With CAS-switching on a UVM that has Y-cable redundancy, the call state of each connection is lost in the event of a switch-over.

Syntax

cnfcassw <line> <mode> <CCS type> <CAS type> <conn type> <country code>
<interdigit timeout> <tone level> <DTMF duration> <idle pattern> <parameters 6-18>

---

Note For the initial implementation of CAS switching, you should specify only port 1 for the line parameter (where line has the format slot.port) and select "PBX-end" for mode.

---

Parameters

Parameter	Description	Default
line	Specifies the line in the format slot.port. The line must be up before you can execute cnfcassw.
mode	Possible entries are "p" for PBX-end, "s" for server-end, or "o" for off. The applications are as follows: •PBX-end applies to a UVM connected to a PBX. Specify PBX-end mode if you plan to add the signaling channel (using addcon) at the UVM connected to the PBX (rather than the CVM or UVM connected to the VNS). •Server-end applies to a UVM connected to the VNS. Specify Server if you plan to add the signaling channel (using addcon) at the UVM connected to the VNS (rather than the PBX). •Off means the UVM is not in CAS-switching mode.	off
CCS type	Range: 1-4. A 1 selects Q.SIG.	1
CAS type	Range: 1-32. A 1 specifies AB signaling for 2-wire E&M line.	1
conn type	Specifies the type of voice connection. Range: a32 and a24.	a32
country code	Range: 0-0xFF. For example, 0 is the U.S. country code.	0
interdigit timeout	Range: 0-0xFF, where each hexadecimal value you enter is a multiplier of 50 millisecond increments.	05, which results in 250 ms.
tone level	Specifies the dB level of the DTMF below 0 dBm. Range: 0-0xFF	00 for 0 dB
DTMF duration	Specifies the DTMF on/off duration. Range: 0-0xFF, and the value you enter is multiplied by 5 millisecond increments.	0C, which results in 60 ms on then 60 ms off.
idle pattern	Specifies the data pattern for the data channel. Range: 0-0xFF	7F for T1, 54 for E1 line
parms 6-19	Parameters 6-18 are reserved for future use.	00

Attributes

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

Related Commands

dspln, dsplncnf

Example

Configure port 1 of the UVM in slot 5 to support CAS switching.

cnfcassw 5.1

sw175 TN SuperUser IGX 8420 9.3 Apr. 13 2000 06:11 PST

Line 5.1 CAS Switching Parameters

=> CASSW mode [OFF] Parm 11 [00] (H)

CCS Type [ 1] (D) Parm 12 [00] (H)

CAS Type [ 1] (D) Parm 13 [00] (H)

Conn Type [a32 ] Parm 14 [00] (H)

Country code [00] (H) Parm 15 [00] (H)

Interdigit TO [05] (H) Parm 16 [00] (H)

Tone level [00] (H) Parm 17 [00] (H)

DTMF duration [0C] (H) Parm 18 [00] (H)

Idle pattern [54] (H)

Parm 6 [00] (H)

Parm 7 [00] (H)

Parm 8 [00] (H)

Parm 9 [00] (H)

Parm 10 [00] (H)

This Command: cnfcassw 5.1




Enter mode: Pbx/Server/Off (o):




cnfcdparm (configure card parameters)

Configures card level functionality, including the level of channel statistics, the selection of VC merge, and support for O.151 OAM cell format, a non-standard format still used by some service providers instead of the standard I.610 OAM cell format.

This command supports the multilevel channel statistics feature, which lets you configure and display additional levels of statistics on a BXM or UXM card.

Configuration of the channel statistic level is a slot-based parameter. For example, if slot 5 is configured to support level 3 channel statistics, all connections on the card in slot 5 will be set to level 3 statistics.

The multilevel channel statistics feature is supported on the BPX and IGX platforms, for BXM and UXM cards. (Refer to release notes for card firmware release requirements.) The multilevel channel statistics feature requires switch software to collect, display, and propagate to Cisco WAN Manager the various statistics types. The channel statistic types vary in number and type based upon the level of support provided by the BXM and UXM cards. For additional information see the "Multilevel Channel Statistics Support" section.

Apart from the cnfcdparm command that you use to configure the channel statistic level on the BXM/UXM cards, you use the following commands to configure and display BXM and UXM card statistics:

•Summary Statistics Commands: dspchstats, clrchstats

•Interval Statistics Commands: dspchstathist, dspchstatcnf, cnfchanstats (statistics information collected by these commands is sent to Cisco WAN Manager)

Syntax

cnfcdparm <slot> <index> <value>

Parameters

Parameter	Description
<slot>	Specifies the slot.
<index> and <value>	Index values are 1, 2, or 3; 1 = Channel Statistics. If 1 is entered for <index>, the values are one of the statistics levels: 0, 1, 2, 3. For a description of all four channel statistics levels, see the BPX 8600 Installation and Configuration Manual, Release 9.3.30, Chapter 5 BXM Card Sets: T3/E3, 155, and 622.
<index> and <value>	Index values are 1, 2, or 3; 2 = VC Merge. If 2 is entered for <index>, the values are: E = Enable VC Merge feature D = Disable VC Merge feature Enable or disable Virtual Circuit (VC) merge. VC merge improves the scalability of MPLS networks and allows multiple incoming VCs to be merged into a single outgoing VC, which is called merged VC. VC Merge is responsible for processing any incoming VSI messages from the MPLS controller and identifies the merging request. In the BPX 8600 series switch, VC Merge is implemented as part of the output buffering for ATM interfaces. The VC Merge feature requires the enhanced BXM (BXM-E) cards. Tag switching is supported. Only frame-based connections are implemented.The key to VC Merge is to switch cells from the merging Label Virtual Circuit (LVC) to the merged LVC that points to the destination, while preserving AAL5 framing. Several AAL5 frames can arrive on different VCs and are merged onto a single VC without interleaving the frames. If VC Merge is not supported on the card, N/A is displayed. Errors encountered after executing this parameter may generate the following error messages: •Could not send request to card. The request to enable or disable VC Merge cannot be sent to the BXM-E card. •Card rejected cmd.The BXM-E card rejects the request to enable or disable VC Merge. •No response from card. The BXM-E card did not respond to the request to enable or disable VC Merge.
<index> and <value>	Index values are 1, 2, or 3; 3 = O.151 OAM cell format If 3 is entered for <index>, the values are: E = Enable O.151 OAM cell format D = Disable O.151 OAM cell format Support for O.151 OAM is on a per card basis. If O.151 OAM is enabled on the card: •The card is then able to support both I.610 and O.151 formats at the same time. •You can then use the command tstconseg with O.151 OAM cells or I.610 cells running on all connections provisioned on that card. Note The user cannot execute the command addyred if O.151 OAM is enabled on the primary card and the secondary card does not support the feature.

Attributes

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

Related Commands

cnfchstats, dspchstats, tstpingoam, tstconseg

Example (BPX)

Configure channel statistics level 1 on slot 11 in the BPX.

cnfcdparm 1 3 E

sw252 TN Cisco BPX 8620 9.3.30 Aug. 21 2001 18:21 PST




Card Parameters




1 Channel Statistics Level ......................................... 1

2 VC Merge State ......................................... N/A

3 O.151 OAM Format ......................................... E




Last Command: cnfcdparm 1 3 E




O.151 OAM cell format enabled on this card.

Next Command:

Example (BPX)

Enable VC Merge on slot 5.




m2 TN Cisco BPX 8620 9.3.a0 May 7 2001 21:37 GMT




Card Parameters




1 Channel Statistics Level ......................................... 1

2 VC Merge State ......................................... E





Last Command: cnfcdparm 5 2 e





VC Merge enabled on this card.

Example (BPX)

Error message when VC Merge is selected by not supported (note N/A beside VC Merge State). cnfcdparm 2 E

hugh TN Cisco BPX 8620 9.3.3o May 21 2001 09:39 PST




Card Parameters




1 Channel Statistics Level ......................................... 1

2 VC Merge State ......................................... N/A





VC Merge not supported by card

This Command: cnfcdparm 2 E

Multilevel Channel Statistics Support

The number of statistics available are based upon the statistics level programmed on the BXM or UXM card. Table 3-16 lists the channel statistics available on the BXM and UXM cards. The four different levels supported are shown, along with the statistics field description as it appears on the related statistics screens (dspchstats, cnfcdparm, clrchstats, dspchstathist, dspchstatcnf, cnfchanstats).

Table 3-16 Channel Statistics Available on BXM

Level 0	Level 1	Level 2	Level 3
No Stats	RX Cells from port	All level 1	All Level 2
	RX EOFs from port	TX EFCI 1 to Port	RX EFCI 1 from Port
	RX cells to NW	RX CLP0 to NW	RX EFCI 0 from Port
	RX CPL1 from port	RX CLP1 to NW	TX EFCI 0 from NW
	RX cells Non-cmplt	TX EFCI 0 to Port	TX EFCI 1 from NW
	RX CLP0 Non-cmplt	RX EFCI 0 to NW
	RX CLP1 Non-cmpl	RX EFCI 1 to NW	OAM from Port
	Ingress VC Q depth	TX EOFs to Port	RM Cells from Port
	TX cells from NW		RM From NW
	TX CLP1 to Port	RX EOF CNG DSC	OAM From NW
	TX Cells to Port		RM Cells to Port
	RX CLP0 Cng Dscd		Rx EFCI 0 Cng Dsc
	RX CLP1 Cng Dscd		Rx EFCI 1 Cng Dsc
	RX CLP0 from Port		Rx OAM Cng Dsc
	TX CLP0 Cells to Port		Rx RM Cng Dsc
	TX CLP0 from NW		Rx FRM to NW
	TX CLP1 from NW		Rx BRM/Fst to NW
	Ingress VSVD ACR		Tx EFCI 0 Cng Dsc
	Egress VSVD ACR		Tx EFCI 1 Cng Dsc
	Egress VC Q Depth		Tx RM Cng Dsc
			Tx OAM Cng Dsc
	*TX CLP 0 Dscd
	*TX CLP 1 Dscd
	*TX CLP0+1 Dscd
	*RX CLP0+1 from prt
	*OAM State
	* indicates summary stats only

However, the cnfcdparm command will not allow you to change the statistics level if the card is active. The switch software detects the current channel statistics level available on the UXM or BXM card. Also, switch software performs these card mismatch verification:

•When a card is inserted, if the channel statistic level decreases from the entry in the logical card database, the card will mismatch.

•When a card is inserted, if the channel statistic level increases from the entry in the logical card database, the card will not mismatch. The logical card database will NOT be updated with the increased channel statistic level value, and you will have available only the number of statistics described on the primary card.

•During the Y-cable mismatch verification, if the secondary card has a smaller channel statistic level, then the primary card (logical card) and the secondary card will mismatch. During the Y-cable mismatch verification, if the channel statistic level is larger on the secondary card, the card will not mismatch. The Y-cable will continue to operate based on the number of statistics available on the primary/logical card.

cnfcdpparm (configure CVM card parameters)

Configures CVM parameters for Modem Detection (MDM), certain reserved debug parameters, and In Frame and Out of Frame (I Frm and O Frm) thresholds for DS0A-type T1 applications. (See the cnfln description for information on assigning % Fast Modem on a per-channel basis.) All CVMs in the node are dynamically reconfigured according to the new parameters. When you enter the command, the system prompts for a parameter number.

Syntax

cnfcdpparm <parameter number> <new value>

Parameters

Parameter	Description
<parameter number>	Specifies the number of the parameter to change. (See Table 3-17.)
<new value>	Specifies the new value for the parameter.

Attributes

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

Related Commands

cnfchts, dchst, cnfecparm

---

Caution You should consult the Cisco TAC before changing any of these parameter.

---

Table 3-17 cnfcdpparm—Parameters and Descriptions 

No.	Parameter	Description	Default1
1	MDM Low Power Threshold	Power level for Modem Detect high-range threshold.	3160 (H)
2	MDM Stationary Coefficient	Indicates how rapidly the power level is changing to not be detected as modem.	14 (H)
3	MDM ZCR High Freq Threshold	Defines upper frequency value for 2100 Hz tone used in V.25 modem detection.	5A (H)
4	MDM ZCR Low Freq Threshold	Defines lower frequency value for 2100 Hz tone used in V.25 modem detection.	56 (H)
5	MDM Detect Failure Count	Defines number of failures above which fast modem is not declared.	4 (H)
6	MDM Detect Window Min.	Number of 5.25-milliseconds windows used in modem tests.	39 (H)
7	MDM Detect Silence Max.	Amount of time a channel stays in a modem-detected state. The parameter equals the value you enter times 84 milliseconds. Default=1008 milliseconds.	C (H)
8	MDM Pkt Header	Changes packet type from voice to non-time-stamped for modems.	6 (D)
9	Null Timing Pkt Header	Gives a higher priority to the specified number of voice packets to decrease delay for spurts of talking.	4 (D)
10	Debug Parameter A	A reserved engineering debug parameter. This parameter does not actually go to the card.	0 (H)
11	Debug Parameter B	A reserved engineering debug parameter. This parameter does not actually go to the card.	0 (H)
12	I Frm 2.4 Threshold(msecs)	Specifies In Frame threshold for DS0 2.4 Kbps overhead data channel.	500 (D)
13	O Frm 2.4 Threshold (msecs)	Specifies Out of Frame threshold for DS0 2.4 Kbps overhead data channel.	500 (D)
14	I Frm 4.8 Threshold (msecs)	Same as 19 for DS0 4.8 Kbps channel.	500 (D)
15	O Frm 4.8 Threshold(msecs)	Same as 20 for DS0 4.8 Kbps channel.	500 (D)
16	I Frm 9.6 Threshold(msecs)	Same as 19 for DS0 9.6 Kbps channel.	500 (D)
17	O Frm 9.6 Threshold (msecs)	Same as 20 for DS0 9.6 Kbps channel.	500 (D)

1 Enter value in either decimal (D) or hexadecimal (H). 1 Example 1 cnfcdpparm 1 pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 18:06 PDT 1 1 MDM Low Pwr Thrsh [3160] (H) 15 0 Frm 4.8 Thrsh (msecs) [ 500] (D) 1 2 MDM Stationary Coef. [ 14] (H) 16 I Frm 9.6 Thrsh (msecs) [ 500] (D) 1 3 MDM ZCR High Frq Thrsh [ 5A] (H) 17 O Frm 9.6 Thrsh (msecs) [ 500] (D) 1 4 MDM ZCR Low Frq Thrsh [ 56] (H) 1 5 MDM Detect Failure Cnt [ 4] (H) 1 6 MDM Detect Window Min. [ 39] (H) 1 7 MDM Detect Silence Max. [ 24] (H) 1 8 MDM Pkt Header [ 6] (D) 1 9 Null Timing Pkt Header [ 4] (D) 1 10 Debug Parm A [ 0] (H) 1 11 Debug Parm B [ 0] (H) 1 12 I Frm 2.4 Thrsh (msecs) [ 500] (D) 1 13 O Frm 2.4 Thrsh (msecs) [ 500] (D) 1 14 I Frm 4.8 Thrsh (msecs) [ 500] (D) 1 1 This Command: cnfcdpparm 1 1 Which parameter do you wish to change:

cnfcftst (configure communication fail test pattern)

The communication fail test pattern is used to periodically test for failure of nodes to communicate with each other. This test pattern is also used to recover from communication fail conditions.

A communication fail is defined as a loss of controller communication over one or more trunks to a particular node. A communication fail differs from a communication break condition in that the node may be reachable over other paths. The communication fail test is used to test the failed trunk for proper controller traffic.

Use cnfcftst to configure the communication fail test pattern byte by byte. It defaults to a pattern of 4 bytes of 1s followed by 4 bytes of 0s. Varying the length of the test pattern makes the communications test more or less rigorous. Changing the characters determines the pattern sensitivity for strings of less than 14 bytes.

The dspcftst command displays the current communication test pattern. The parameters used for declaring and clearing communication fails are set by the cnfnodeparm command.

Syntax

cnfcftst

Attributes

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

Related Commands

dspcftst

Example

Configure Communication Fail Test Pattern.

cnfcftst

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 21:17 GMT




Comm Fail Test Pattern




==> Byte 0: FF Byte 12: 00 Byte 24: FF Byte 36: 00 Byte 48: FF

Byte 1: FF Byte 13: 00 Byte 25: FF Byte 37: 00 Byte 49: FF

Byte 2: FF Byte 14: 00 Byte 26: FF Byte 38: 00 Byte 50: FF

Byte 3: FF Byte 15: 00 Byte 27: FF Byte 39: 00 Byte 51: FF

Byte 4: 00 Byte 16: FF Byte 28: 00 Byte 40: FF Byte 52: 00

Byte 5: 00 Byte 17: FF Byte 29: 00 Byte 41: FF Byte 53: 00

Byte 6: 00 Byte 18: FF Byte 30: 00 Byte 42: FF Byte 54: 00

Byte 7: 00 Byte 19: FF Byte 31: 00 Byte 43: FF Byte 55: 00

Byte 8: FF Byte 20: 00 Byte 32: FF Byte 44: 00 Byte 56: FF

Byte 9: FF Byte 21: 00 Byte 33: FF Byte 45: 00 Byte 57: FF

Byte 10: FF Byte 22: 00 Byte 34: FF Byte 46: 00 Byte 58: FF

Byte 11: FF Byte 23: 00 Byte 35: FF Byte 47: 00 Byte 59: FF




This Command: cnfcftst

Enter Byte 0:

cnfchadv (configure channel adaptive voice)

Enables the adaptive voice (ADV) feature for individual channels. ADV must also be enabled at each node that terminates the connection. The channel-specific cnfchadv has no effect at nodes that do not support ADV enabled.

If the ADV feature is enabled for a channel with a "c" or "v" connections, VAD is automatically disabled on that channel when trunk bandwidth is available and enabled when trunk bandwidth is needed. If the Adaptive Voice feature is not enabled for a channel with a "c" or "v" connections, VAD is always turned on for that channel. In order for a voice ("c" or "v") connection to use ADV, both ends must have ADV enabled by the cnfchadv command.

Syntax

cnfchadv <channel> <e | d>

Parameters

Parameter	Description
<channel>	Specifies the channel or range of channels over which you specify Adaptive Voice.
e	Enables ADV (default)s
d	Disables ADV

Attributes

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

Related Commands

dspchcnf

Example

Enable Adaptive Voice for channel 13.1.

cnfchadv 13.1

sw150 TN Cisco IGX 8420 9.3.2T Dec. 20 2000 00:36 PST




% Adaptive Gain (dB) Dial Interface OnHk Cond

Channels Util Voice Fax In Out Type Type A B C D Crit

13.1-24 60 Enabled - 0 0 Inband Unconfig ? ? - - a







Last Command: cnfchadv 13.1

cnfchdfm (configure channel DFM)

Enables or disables Data Frame Multiplexing (DFM) for individual channels and sets the DFM parameters for the channels. The default state when the DFM feature is activated on a card is enabled. Because DFM is a purchased option, the Cisco Technical Assistance Center (TAC) must activate on the applicable nodes before you use the cnfchdfm command.

The DFM feature must be both installed and enabled. The DFM feature must be installed through software control at each node terminating the connection. If DFM is not installed for a pertinent node in the network, the cnfchdfm command has no effect at that node. Furthermore, you must use cnfchdfm at both ends of the connection to enable DFM.

Syntax

cnfchdfm <channel(s)> <7 | 8 | 16> [e | d]

Parameters

Parameter	Description
channel	Specifies the channel or range of channels.
7 | 8 | 16	Specifies the pattern length in bits for the DFM algorithm. Default: 8 bits
e | d	Optionally enables or disables DFM. Note that DFM works at rates no higher than 128 Kbps. Default: e

Attributes

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

Related Commands

dspchcnf

Example

Set the DFM pattern length to 8 bits for data channel 5.1.

cnfchdfm 5.1 8

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

Maximum EIA % DFM Pattern DFM

Channels Update Rate Util Length Status

5.1 15 100 8 Enabled

5.2-4 2 100 8 Enabled




Last Command: cnfchdfm 5.1 8

Next Command:

cnfchdl (configure dial type for channels)

Configures the dial type for a channel or set of channels. The dial type may be inband, pulse, or user-configured. The user-configured option allows non-default timing values to be used. The parameters associated with the cnfchdl command are timing constants used to ensure that signaling pulses are not distorted in time by transmission through the network.

•Dial type determines the signaling message timing for a connection. Dial type is ignored for DS0 data connections.

•When you add an inband or pulse dial type to a channel, the channel configuration screen appears, showing the designated dial types for each channel.

•When you add a user-configured dial type, a more detailed screen appears, showing the dial type as well as the signaling delay, minimum wink, interdigit times, and playout delay.

If you select inband, the node assumes that the A and B bits are not used for loop-disconnect dialing. Therefore, any change in signaling bit status goes in a packet to the far end of the connection.

If you select pulse, the transmitting node waits (normally 72 ms) after an A or B bit transition for another transition to arrive. If a transition arrives, the new transition goes into the same signaling packet that is sent to the far end of the connection. This step increases the delay of the signaling transition across the network but decreases the amount of trunk bandwidth used for signaling.

If the default timings are not correct for the network, you must configure the options. The dialing type should be set correctly. If a connection-designated pulse is used for inband signaling, a greater than necessary delay across the network results. If a connection-designated inband is used for pulse signaling, the relative timing of signaling transitions may be lost and so distort the pulses.

Syntax

cnfchdl <channel(s)> <dial_type> [<sig_delay> <min_wink> <int_dig_time>
<playout delay>]

Parameter

Parameter	Description
channel	Specifies the channel or range of channels over which to configure dial type.
dial type	Specifies the dial type to assign. The three possible dial types are: i = inband p = pulse u = user-configured Inband is the default dial type. If you designate "u" for a user-configured dial type, you are prompted, as applicable, from among the following: sig delay, min wink, interdigit time, and playout delay.
signaling delay	Specifies the signaling delay for the user-configured dial type. Range: 12-96 ms. Your entry is rounded to the closest multiple of 1.5 ms.
minimum wink	Specifies the minimum wink to assign to the user-configured dial type. Range: 3-765 ms. Your entry is rounded down to the nearest multiple of 3 ms. This parameter does not apply to CDP, UVM, or CVM channels.
interdigit time	Specifies the interdigit time for the user-configured dial type. Range: 3-765 ms. Your entry is rounded down to the nearest multiple of 3 ms. This parameter does not apply to CDP, UVM, or CVM channels.
playout delay	Specifies the signaling delay assign to the user-configured dial type. Range: 12-96 ms. Your entry is rounded to the closest multiple of 1.5 ms.

Attributes

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

Related Commands

dspchcnf, dspchdlcnf

Example

Configure the dial type of channel 14.1 to pulse.

cnfchdl 14.1 p

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

% Adaptive Gain (dB) Dial OnHk Cond

Channels Util Voice In Out Type Interface Type A B C D Crit.

14.1 40 Enabled 0 - Pulse Unconfig ? ? - - a

14.2-24 40 Enabled 0 - Inband Unconfig ? ? - - a




Last Command: cnfchdl 14.1 p

Next Command:

cnfchec (configure channel echo canceller)

Configures the echo canceller and other channel parameters associated with a voice channel. (You cannot configure CAS and data channels using cnfchec.) The CDP/CVM and UVM have slightly different parameters. Unavailable parameters appear on the screen as a dashed line, so no prompts for these unavailable options appear.

Syntax

For CDP/CVM:
cnfchec <chan> <ec> <erl> <td> <convergence> <nlp>

For UVM:
cnfchec <chan> <ec> <td> <nlp> <bkgd_filter>

Parameters

Parameter	Description
channel	Specifies the channel or range of channels. For a CDP or CVM, "channel" has the format slot.channel(s). For a UVM, "channel" has the format slot.line.channels(s).
echo canceller	Enable or disable the echo canceller. An "e" enables. A "d" disables.
echo return loss	Sets the echo return loss as high/low). An "h" specifies high. An "l" specifies low.
tone disabler	Enables or disables the tone disabler. An "e" enables. A "d" disables.
convergence	Enables or disables convergence. An "e" enables. A "d" disables. Except for test purposes, the normal state for convergence is enabled.
nonlinear processing	Enables or disables nonlinear processing. An "e" enables. A "d" disables.
bkgd_filter	Enables or disables the background filter.

Attributes

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

Related Commands

dspchec

Example

Enable and configure the Echo Canceller in channel 7.1 with high echo loss tone disabled, convergence enabled, and non-linear processing enabled. In this example, the card is either a CDP or CVM because the channel is specified with slot.channel rather than slot.line.channel.

cnfchec 7.1 e h e e e

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




Echo Echo Return Tone Conver- Non-Linear Voice

Channels Cancel Loss (.1 dBs) Disabler gence Processing Tmplt

7.1 Enabled High 60 Enabled Enabled Enabled USA

7.2-31 Disabled High 60 Enabled Enabled Enabled USA







Last Command: cnfchec 7.1 e h e e e





Next Command:

Example

Enable the echo canceller in channel 10.1.1. In this example, the card is a UVM because the channel is specified with slot.line.channel. Note the available parameters differ slightly from a CDP/CVM.

cnfchec 10.1.1

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:21 PST




Echo Echo Return Tone Conver- Non-Linear Voice Bkgrnd

Channels Cancel Loss(.1 dBs) Disabler gence Processing Tmplt Filter

10.1.1-24 Disabled - Enabled - Enabled - Enabled

10.2.1-24 Disabled - Enabled - Enabled - Enabled









This Command: cnfchec 10.1.1





Enable or Disable Echo Cancel (e/d)? [d]:

cnfcheia (configure EIA update rate for channels)

Sets the sampling rate for the updating EIA control leads. You can set this rate from 0 (no sampling) to packet-generation rate for the EIA leads associated with the channel.

At 20 updates/second, the control leads are polled for changes every 50 msec. Therefore, changes occurring more rapidly than that might not be detected. If there is no change in EIA lead status, no packet is sent. A minimum of one update per second is sent if the maximum update rate chosen is from 1 to 20.

If the connection is configured in such a way that an implied isochronous clock is detected, the update rate is always 20 per second in the same direction as that of the clock signal. For 1.544 Mbps data connections, this defaults to 0. This does not affect EIA sampling rates of fast EIA or embedded EIA leads.

Syntax

cnfcheia <channel> <update_rate>

Parameters

Parameter	Description
<channel>	Specifies the channel or range of channels over which to configure the EIA update rate.
<update_rate>	Specifies the maximum EIA update rate in updates per second.

Attributes

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

Related Commands

dspchcnf

Example 1

Set the EIA update rate to 15 sec. for data channel 5.1.

cnfcheia 5.1 15

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

Maximum EIA % DFM Pattern DFM

Channels Update Rate Util Length Status

5.1 15 100 8 Enabled





Last Command: cnfcheia 5.1 15

Next Command:

cnfchfax (configure FAX modem detection for channels)

Configures a channel on a UVM for either FAX detection or FAX relay. If you enable FAX detection, the UVM suspends voice compression when it detects a FAX or modem tone on the channel. For the duration of the FAX, transmission takes place at 64 Kbps.

FAX relay is a mechanism for compression the FAX transmission rate across a network to 9.6 Kbps.

To view the current configuration, use the dspchcnf command.

Syntax

cnfchfax <slot.line> <channel> <e | d>

Parameters

Parameter	Description
<slot.line>	Specifies the line of the UVM.
<channel>	Specifies the DS0 or range of DS0s.
<e | d>	Enable or disable FAX detection.

Attributes

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

Related Command

dspchcnf

Example

Configure channels 1-24 on line 1 of the UVM in slot 7 to have FAX modem detection.

cnfchfax 7.1.1

sw109 VT Cisco IGX 8420 9.3 Apr. 13 2000 19:10 PST

% Adaptive Gain (dB) Dial Interface OnHk Cond

Channels Util Voice Fax In Out Type Type A B C D Crit

7.1.1-24 40 Enabled Disabled 0 0 Inband 2W E&M 0 X - - a

7.2.1-24 40 Enabled Disabled 0 0 Inband Unconfig ? ? - - a




Last Command: cnfchfax 7.1.1

Next Command:

cnfchgn (configure gain insertion for channels)

Configures the amount of gain inserted by the IGX node for a given circuit line channel or range of channels. Gain can be configured between +6 dB and -8 dB. The input gain is inserted at the receive side of a voice card and is therefore applied before the signal is packetized by the card. The output gain is inserted at the transmit side of a voice card and is applied after the signal has been depacketized by the card. Gain is meaningless for channels that carry data.

Syntax

cnfchgn <channel(s)> <input_gain> <output_gain>

Parameters

Parameter	Description
channel	Specifies the channel or range of channels.
input_gain	Specifies the gain, in decibels, to assign to the channel. Range: -8 dB-+6 dB.
output_gain	Specifies the gain, in decibels, to assign to the channel. Range: -8 dB -+6 dB.

Attributes

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

Related Commands

dspchcnf

Example

Configure input gain of -4 dB and an output gain of +2 dB for channel 1 of circuit line 1.

cnfchgn 14.1 -4 2

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

% Adaptive Gain (dB) Dial OnHk Cond

Channels Util Voice In Out Type Interface Type A B C D Crit.

14.1 40 Enabled -4 -2 User Unconfig ? ? - - a

14.2-24 40 Enabled 0 -2 Inband Unconfig ? ? - - a




Last Command: cnfchgn 14.1 -4 2

Next Command:

cnfchpri (configure Frame Relay channel priority)

Sets the channel priority for a Frame Relay connection. The Channel Priority feature permits some Frame Relay connections to receive a higher priority within a port queue than other Frame Relay traffic on a per-connection basis. The default priority is low. You can configure Frame Relay LMI ports to communicate the priority to a router. You must change the priority on both ends of a connection.

---

Note Note that data of high-priority (hi-pri) connections is sent to the CPE (customer premises equipment) ahead of data from low priority (low-pri) connections. Note that this parameter has nothing to do with how the connection is routed through the network, but affects only how data is sent to the CPE.

---

Syntax

cnfchpri <slot.port.DLCI.> <h | l>

Parameters

Parameter	Description
<slot.port.DLCI.>	Specifies the channel or range of channels. The format is slot.port.DLCI.
<h | l>	The priority: h = high; l = low.

Attributes

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

Related Commands

dspchcnf

Example

Configure a high priority for Frame Relay connection 9.1.100.

cnfchpri 9.1.100 h

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

Conn: 9.1.100 gamma 8.1.200 fr

MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST

9.6/9.6 9.6/9.6 5/5 256/256 10/10 65535/65535 9.6/9.6 n

% Util: 100/100

Owner: LOCAL Restriction: NONE CoS: 0 Status: OK

Group: NONE Priority: H TestRTD: 0 msec

Path: alpha 14--13beta 15--15gamma

Pref: Not Configured

alpha 9.1.100 gamma 8.1.200

FRP: OK FRP: OK

FRI: OK FRI: OK

Last Command: cnfchpri 9.1.100 h

Next Command:




cnfchstats (configure channel statistics collection)

Enables statistics collection for various channel parameters. The cnfchstats command is sometimes referred to as an "interval statistics" command—the statistics information collected is propagated to Cisco WAN Manager.

To configure the channel statistics level on the BXM and UXM card, use the cnfcdparm command. This command lets you configure a specific card slot to support additional levels of statistics (levels 2 and 3) that were supported in releases previous to Release 9.2 (level 1). See the cnfcdparm command for more information.

This debug command enables statistics collecting for channel parameters. Table 3-18 lists the statistics by type. Not all statistic types are available for all connections. Only valid statistics are displayed for you to select; inapplicable statistics appear in gray. If you are unsure of the size parameter to specify, select four bytes per sample.

The dspchstatcnf command displays the channel statistics configuration. Statistics are collected by and displayed on the Cisco WAN Manager workstation. Cisco WAN Manager allows statistics collection to be customized. You can disable a Cisco WAN Manager-enabled channel statistic by specifying the optional node name of the workstation as the last parameter on the command line.

Syntax

cnfchstats <channel> <stat> <interval> <e | d> [<samples> <size> <peaks>] [nodename]

Parameters

Parameter	Description
<channel>	Specifies the channel (connection) to configure.
<stat>	Specifies the type of statistic to enable/disable. (See Table 3-18.)
<interval>	Specifies the time interval of each sample (1-255 minutes).
<e|d>	Enables/disables a statistic. E to enable; D to disable a statistic.
[samples]	Specifies the number of sample to collect (1-255).
[size]	Specifies the number of bytes per data sample (1, 2 or 4).
[peaks]	Enables/disables the collection of one-minute peaks. Y to enable; N to disable.
[nodename]	Specifies the name of the node to which the Cisco WAN Manager terminal connects.

Attributes

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

Related Commands

dspchstatcnf, cnfdparm, dspchstathist, cnfchanstats

Example

cnfchstats 9.2.1.100

sw199 TN SuperUser IGX 8420 9.3 Apr. 13 2000 09:28 PDT

Channel Statistic Types

46) Cells Received from Port 60) Average Tx Vcq Depth in Cells

47) EOF Cells Received from Port 61) Bkwd Severely Errored Cell Blocks

48) Cells Transmitted to Network 62) Bkwd Lost Cell Count

49) Cells Received from Network 63) Bkwd Misinserted Cell Count

50) Cells Received with CLP=1 64) Bkwd Bipolar Violation Count

51) Non-Compliant Cells Received 65) Fwd Severely Errored Cell Blocks

52) Average Rx VCq Depth in Cells 66) Fwd Lost Cell Count

53) Cells Transmitted with EFCI=1 67) Fwd Misinserted Cell Count

54) Cells Transmitted to Port 68) Fwd Bipolar Violation Count

56) Cells Received with CLP=0 69) Good Pdu's Received by the Sar

57) Cells Transmitted with EFCI=0 70) Good Pdu's Transmitted by the Sar

58) Ingress Vsvd Allowed Cell Rate 71) Rx pdu's discarded by the Sar

59) Egress Vsvd Allowed Cell Rate 72) Tx pdu's discarded by the Sar





sw199 TN SuperUser IGX 8420 9.3 Apr. 13 2000 09:28 PDT

Channel Statistic Types

73) Invalid CRC32 pdu rx by the sar

74) Invalid Length pdu rx by the sar

75) Shrt-Lgth Fail detected by the sar

76) Lng-Lgth Fail detected by the sar




This Command: cnfchstats 9.2.1.100

Statistic Type:




Table 3-18 Channel Statistics 

Statistic Number	Statistic Type
1	Frames Received
2	Receive Frames Discarded
3	Frames Transmitted
4	Transmit Frames Discarded
5	Packets Received
6	Receive Packets Discarded
7	Packets Transmitted
8	Projected Packets Transmitted
9	Supervisory Packets Transmitted
10	Bytes Received
11	Receive Bytes Discarded
12	Bytes Transmitted
13	Transmit Bytes Discarded
14	Seconds V.25 Modem On
15	Seconds DSI Enabled
16	Seconds Off-Hook
17	Seconds In Service
18	Frames Transmitted with FECN
19	Frames Transmitted with BECN
20	Supervisory Packets Received
21	Minutes Congested
22	DE Frames Received
23	DE Frames Transmitted
24	DE Frames Dropped
25	DE Bytes Received
26	Frames Received in Excess of CIR
27	Bytes Received in Excess of CIR
28	Frames Transmitted in Excess of CIR
29	Bytes Transmitted in Excess of CIR
32	Rx Frames Discarded—Deroute/Down
33	Rx Bytes Discarded—Deroute/Down
34	Rx Frames Discarded—VC Queue Overflow
35	Rx Bytes Discarded—VC Queue Overflow
36	Tx Frames Discarded—Queue Overflow
37	Tx Bytes Discarded—Queue Overflow
38	Tx Frames Discarded—Ingress CRC
39	Tx Bytes Discarded—Ingress CRC
40	Tx Frames Discarded—Trunk Discard
41	Tx Bytes Discarded—Trunk Discard
42	TX Frames During Ingress LMI Fail
43	TX Bytes During Ingress LMI Fail
44	Unkn Prot Frms Dscd at Ingress
45	Unkn Prot Frms Dscd at Egress
46	Cells Received from Port
47	EOF Cells Received from Por
48	Cells Transmitted to Network
49	Cells Received from Network
50	Cells Received with CLP=1
51	Non-Compliant Cells Received
52	Average Rx VCq Depth in Cells
53	Cells Transmitted with EFCI=1
54	Cells Transmitted to Port
56	Cells Received with CLP=0
57	Cells Transmitted with EFCI=0
58	Ingress Vsvd Allowed Cell Rate
59	Egress Vsvd Allowed Cell Rate
60	Average Tx Vcq Depth in Cells
61	Bkwd Severely Errored Cell Blocks
62	Bkwd Lost Cell Count
63	Bkwd Misinserted Cell Count
64	Bkwd Bipolar Violation Count
65	Fwd Severely Errored Cell Blocks
66	Fwd Lost Cell Count
67	Fwd Misinserted Cell Count
68	Fwd Bipolar Violation Count
69	Good pdus Received by the SAR
70	Good pdus Transmitted by the SAR
71	Rx pdus discarded by the SAR
72	Tx pdus discarded by the SAR
73	Invalid CRC32 pdu rx by the SAR
74	Invalid Length pdu rx by the SAR
75	Invalid Length pdu rx by the SAR
76	Lng-Lgth Fail detected by the SAR

cnfchts (configure channel timestamp)

Configures a pre-aging parameter for data channels. Applicable cards are the SDP, LPD, LDM, and HDM. Applicable traffic is time-stamped data.

This command configures the pre-age parameter for data channels. The pre-age parameter specifies the initial age of a time-stamped packet. With a non-zero pre-age, the packet has less time to wait at the destination before it reaches the Max Time-Stamped Packet Age and is taken out of the ingress queue. (Data channels with the greater pre-age value are processed sooner.) However, if the pre-age value is too high because of queuing delays in the network, packets could be discarded because they appear too old at the destination.

The value you enter for pre-age should be a multiple of 250 microseconds (otherwise, the system rounds the value down to the nearest multiple of 250 microseconds). The default value is 0. Acceptable values are in the range 0 to the Max Time Stamped Packet Age (set by the cnfsysparm command). After you change a time-stamp, the connection should be rerouted or restarted for the new value to take effect.

---

Note You can see the value for pre-age in the screen display for the dspchcnf command. If dspchcnf is entered at a user-privilege level below SuperUser level, the pre-age parameter does not appear in the dspchcnf output.

---

Syntax

cnfchts <channel> <pre-age>

Parameters

Parameter	Description
<channel>	Specifies the data channel.
<pre-age>	Specifies a value in 250-microsecond increments to go in the age field in the header of a time-stamped packet.

Attributes

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

Related Commands

cnfcdpparm

Example

cnfchts 3.1 1000

pubsipx1 TN SuperUser IGX 8420 9.3 Apr. 13 2000 03:50 GMT

Maximum EIA % DFM Pattern DFM PreAge

Channels Update Rate Util Length Status (usec)

3.1 2 100 8 Enabled 1000

3.2-4 2 100 8 Enabled 0





Last Command: cnfchts 3.1 1000

Next Command:

cnfchutl (configure channel utilization)

Informs the system software of the expected utilization rate of connections with traffic-dependent compression algorithms (voice connections with VAD, data connections with DFM, Frame Relay connections). The software load model then takes the user-specified rate of the connection and modifies it by using the percent of utilization you specify with cnfchutl. The resulting rate is used in calculations for loading trunks. The load model uses these figures instead of calculated estimates from real traffic patterns.

For the full benefits of the compression algorithms to be used, the default utilizations should be modified after traffic studies have been performed. Traffic studies of Frame Relay connections should be used to determine optimum utilization settings. When calculating loads in a network, the load allocated to a connection is:

channel utilization x full load for the connection type

For example, with a channel utilization of 50percent and a full load of 480 packets per second, the load allocated to a connection is:

0.50 x 480 pps = 240 pps

For voice connections with VAD turned off, the bandwidth allocated is always the maximum bandwidth for the connection type. In other words, the utilization, although configurable, is ignored for a voice channel without VAD and a data channel without DFM.

If you use cnfchutl to increase the utilization of a connection, the system verifies that the additional bandwidth is available on the connection's current route. If the bandwidth is not available, the system attempts to reroute the connection. If no other route is found, the connection is failed.

If you use cnfchutl to decrease the utilization of a connection, the system makes the bandwidth available to other connections that require a route. The screen displayed by the cnfchutl command depends upon whether a data channel, voice channel, or Frame Relay channel is specified.

Syntax

cnfchutl <channel> <%_util>

Parameters

Parameter	Description
channel	Specifies the channel for configuring utilization. The channel can be in voice, data, Frame Relay. The format for channel depends on the technology: •Voice connection: slot.channel •Data connection: slot.port •Frame Relay connection: slot.port.DLCI •Access device connection: slot.port.device_ID
percent utilization	Specifies the percentage of utilization of the channel. Range: 0-100 Default value (data or Frame Relay): 100% Default value (voice): 40%

Attributes

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

Related Commands

dspchcnf

Example

Set utilization on data channel 5.1 at 40%.

cnfchutl 5.1 40

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

Maximum EIA % DFM Pattern DFM

Channels Update Rate Util Length Status

5.1 15 40 8 Enabled

5.2-4 2 100 8 Enabled




Last Command: cnfchutl 5.1 40

Next Command:

Example

Set utilization on voice channel 14.1 at 55%.

cnfchutl 14.1 55

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

% Adaptive Gain (dB) Dial OnHk Cond

Channels Util Voice In Out Type Interface Type A B C D Crit.

14.1 55 Enabled -4 - User Unconfig ? ? - - a

14.2-24 40 Enabled 0 - Inband Unconfig ? ? - - a




Last Command: cnfchutl 14.1 55

Next Command:




Example

Set utilization on Frame Relay channel 8.1.100 at 60%.

cnfchutl 8.1.100 60

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

Frame Relay Channel Configuration Port: 8.1




From Minimum Peak AvgFrame Cmax VC Q ECN Q % Util 8.1.100 9.6 * 70 10 65535 65535 60 8.1.301 9.6 * 70 10 65535 65535 100




Last Command: cnfchutl 8.1.100 60

Next Command:




cnfcldir (configure control lead direction)

Sets the control lead direction for pins 11 and 23 on the EIA/TIA-232 data channels of an SDP or HDM card set. This allows the control leads to carry "backward" channels. Pins 11 and 23 on an EIA/TIA-232 interface are bidirectional. The signals on these pins can have various names, such as SI, SF, CH, CI, and QM. To display control lead information about pins 11 and 23, use the dspbob command. Use the cnfict command to configure the behavior of all output leads.

Syntax

cnfcldir <channel> <lead> <direction>

Parameters

Parameter	Description
<channel>	Specifies the EIA/TIA-232 data channel whose control lead direction to configure.
<lead>	Specifies the pin number of the control lead. Range: 11 and 23
<direction>	Specifies the direction of the control lead signal. Valid control lead directions are: Input = The control lead acts as an input to the IGX node (default). Output = The control lead acts as an output from the IGX node.

Attributes

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

Related Commands

cnfict, dspbob, dspict

Example

Configure lead number 11 of channel 3.1 to be an input. The screen example shows the display after the system has accepted the input as valid.

cnfcldir 3.1 11 input

pubsigx1 TN SuperUser IGX 8420 9.3 Apr. 13 2000 00:30 GMT




Port: 3.1

Interface: V35 DCE

Clocking: Normal




Inputs from User Equipment Outputs to User Equipment

Lead Pin Lead Pin Lead Pin Lead Pin

RTS C CTS D

DTR H DSR E

TxD P/S DCD F

TT U/W RI J

TM K

RxD R/T

RxC V/X

TxC Y/a





Last Command: cnfcldir 3.1 11 input





Next Command:




cnfclksrc (configure network clock source)

Specifies a network-wide clock source. The clocking scheme ensures that all nodes in the network automatically synchronize to the nearest, most stable clock available. After you specify a clock source, the location and type of the network clock source goes out to all nodes in the network. This synchronization remains in effect despite line failures, power outages, controller card switchovers, line repairs, and the joining of subnetworks and all other network topology changes. Each node in the network maintains a list of the available clock sources for the network.

A clock source can be:

•a line (L)

•a trunk (T)

•an external source (E)

The clock type can be:

•primary (P)

•secondary (S)

•tertiary (T)

To remove a clock source, enter its type as "r" at the end of the cnfclksrc command line.

Designation of the clock type depends on the stratum (or stability) of the clock source. In a large network, for example, you could designate all stratum 2 clocks as "primary," all stratum 3 clocks as "secondary," and all stratum 4 clocks as "tertiary." The network regards all primary clocks as equal in the network clocking hierarchy, regards all secondary clocks as equal, and regards all tertiary clocks as equal. Each node synchronizes to the highest stratum clock source that is available. If multiple, equal clock sources are available, the node synchronizes to the source that is physically the closest. If none of the sources is available, the network synchronizes to the internal oscillator of one of the nodes in the network.

When you are planning clock sources, consider these points:

•The dspclksrcs command displays all clock sources in a network. The dspcurclk command displays the clock source that a specific node is currently using and the path between the source and the local node.

•To avoid unnecessary clock disruptions, configure all primary clock sources for the network first.

•A line must be upped and not in an alarm before you can configure it as a network clock source.

•Before you define a trunk as a clock source, use cnftrk to specify that the trunk does not pass synchronization.

Syntax

cnfclksrc <line type> <line number> <source type> [freq]

Parameters

Parameter	Description
line type	Specifies whether the clock source is a trunk (T), line (L), or external (E).
line number	For a line (L) clock source, this specifies the back slot location of the source. For a trunk (T) clock source, this specifies the slot.port. For external clock sources (E), this specifies either front card slot 1 or 2, as long as either slot has a card. This external source designation applies to IGX and BPX nodes.
source type	Specifies where the clock fits in the hierarchy: P = primary; S = secondary; and T = tertiary. To remove the clock source configuration for the current type and line, enter an "r."
freq	Specifies the frequency of the clock source. An entry is necessary only if the line type is an external line. The supported frequencies are 1.544 MHz and 2.048 MHz. Enter a "1" for 1.544 MHz or a "2" for 2.048 MHz.

Attributes

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

Related Commands

dspclksrcs, dspcurclk

Example

Configure trunk 10.1 as a primary clock. The network clock sources screen shows that trunk 10.1 has been configured as a primary clock source for the network.

cnfclksrc T 10.1 P

sw152 TN Cisco IGX 8420 9.3.b1 Mar. 16 2001 15:03 GMT




Network Clock Sources




Primary

sw245 Line 10.2 sw213 Trunk 9.5 sw213 Trunk 14.2

sw152 Line 10.4 sw152 Trunk 10.1




Secondary

sw152 Trunk 16.3




Tertiary

None







Last Command: cnfclksrc T 10.1 P

cnfclnparm (configure circuit line parameter)

Configures the alarm integration time for circuit lines originating on a UVM, CDP, or CVM and for T1/E1 Frame Relay circuits originating on an FRP, FRM, or UFM.

This command configures the circuit line alarm integration times for RED and YELLOW circuit line alarms. These integration times are specified in milliseconds and should be set to correspond to the local carrier's alarm integration times. Carrier integration times are typically 800 to 1500 ms. for RED Alarm and 1500 to 3000 ms. for YELLOW Alarm. The allowable range for these parameters are 60 to 3,932,100 ms.

Syntax

cnfclnparm <line>

Parameters

Parameter	Description
<line>	Specifies the circuit line to configure.

Attributes

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

Related Commands

cnfclnsigparm, dchst

Example

cnfclnparm 11

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




CLN 11 Parameters

1 Red Alarm - In/Out [ 1000 / 2000] (Dec)

2 Yel Alarm - In/Out [ 1000 / 2000] (Dec)







This Command: cnfclnparm 11





Which parameter do you wish to change:




cnfclnsigparm (configure circuit line signaling parameters)

Configures signaling parameters for a UVM or CVM.

The CVM & UVM Heartbeat parameter (option 1) is the rate, in seconds, at which the card sends a signaling (ABCD bits) state update to the other end of the connection, even when there is no change in the state of the signaling bits. This is done because signaling packets are time-stamped data packets, and there is a small chance that a signaling packet might be discarded somewhere in the network. This mechanism is a recovery mechanism to ensure that on-hook and off-hook notifications are not lost.

Increasing this interval will probably have no impact as long as none of the normal signaling time-stamped data packets are discarded in the network.

Syntax

cnfclnsigparm <parameter number> <parameter value>

Parameters

Parameter	Description
<parameter number>	Specifies the parameter number of the signaling parameter to change.
<parameter value>	Specifies the new value to enter.

Attributes

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

Related Commands

cnfclnparm, dspsig

Example

cnfclnsigparm

sw219 TRM SuperUser IGX 8420 9.3 Apr. 13 2000 08:12 GMT

1 CVM & UVM Heartbeat [ 2] (sec)

2 CVM & UVM Sig. Polling Rate [ 10] (sec)

3 CVM & UVM Default Inband Sig Delay [ 96] (msec)

4 CVM & UVM Default Inband Playout Delay [ 200] (msec)

5 CVM & UVM Default Pulse Sig Delay [ 96] (msec)

6 CVM & UVM Default Pulse Playout Delay [ 200] (msec)

7 CVM & Number of Packet Slices [ 1]

8 CVM & UVM Packet Rate [ 200] (pkt/sec)

9 CVM & UVM Condition E1 CCS Lines? [ NO]

10 CVM & UVM Default Inband Min. Wink [ 140] (msec)

11 CVM & UVM Default Pulse Min. Wink [ 140] (msec)

12 CVM & UVM Condition T1 Lines? [ YES] (yes/no)

Last Command: cnfclnsigparm

Which parameter do you wish to change:





Table 3-19 Display Fields 

No.	Parameter	Description	Range
1	Heartbeat	The current state of the signaling is periodically transmitted to the far end even if no signaling transitions are detected. This interval is determined by the value of "heartbeat." The CVM & UVM Heartbeat parameter (option 1) is the rate, in seconds, at which the card sends a signaling (ABCD bits) state update to the other end of the connection, even when there is no change in the state of the signaling bits. This is done because signaling packets are time-stamped data packets, and there is a small chance that a signaling packet might be discarded somewhere in the network. This recovery mechanism ensures that on-hook and off-hook notifications are not lost. Increasing this interval will probably have no impact as long as none of the normal signaling time-stamped data packets are being discarded in the network.	2-30 sec.
2	Signal Polling Rate	How often the control card polls the UVM/CVM for the status of the signaling. This parameter is used to update displays and statistics.	2-60 sec.
3	Default Inband Signal Delay	The transmit buffer timer value set after a valid signaling transition for in-band signaling arrives. After timeout, a signaling packet is sent.	30-96 msec.
4	Default Inband Playout Delay	The receive buffer timer that "ages" an incoming, time-stamped packet. When the age of the packet reaches the time-stamp value, it moves on to depacketization and then to the user equipment. This parameter is used to even out the delay between signaling packets and voice packets.	0-200 msec.
5	Default Pulse Signal Delay	Same as number 3 but applied to pulse signaling.	30-96 msec.
6	Default Pulse Playout Delay	Same as number 4 but applied to pulse signaling.	100-200 msec.
8	Packet Rate	Reserves trunk bandwidth for carrying UVM/CVM signaling.	0-1000 packets/sec.
9	Condition CCS Lines	If you specify "yes" for this parameter, the card applies signaling conditioning during an alarm to all channels on E1 CCS circuit lines to notify marked for Common Channel Signaling to notify PBX of a line failure.	YES or NO
10	Inband Min. Wink	Same as 6 for in-band signaling.	120-300 msec.
11	Pulse Min. Wink	For UVM/CVM connections only, this parameter controls both wink and inter-digit intervals for signaling that arrives over the NPM signaling channel from a far end UVM/CVM.	120-300 msec.
12	Condition T1 Lines?	If you specify "yes" for this parameter, the card applies signaling conditioning during an alarm to all channels on T1 circuit lines to notify PBX of a line failure.	YES or NO

cnfcls (configure class template)

Modify the ten Cisco-supplied class templates for connection configuration. (The addcon command can take a class as an input.)

When you enter the number of the class to configure, the display shows the current value of each parameter in the class. For each item in the class, a prompt appears for changing or keeping the current value.

You can use cnfatmcls and cnfcls to configure the rt-VBR ATM connection class. You can use dspatmcls and dspcls to display the connection parameters for the rt-VBR and nrt-VBR connection classes.

The rt-VBR connections are configured per class 3 service parameters, and nrt-VBR connections are configured per class 2 service parameters. You can change these class parameters by using the cnfcls or cnfatmcls commands, or the parameters can be entered individually for each connection by specifying yes to the extended parameters prompt of the addcon command.

---

Note For a new node running software Release 9.2.20 or later, the rt-VBR connection class number is 3. An upgraded node will retain existing connection classes. Therefore, it cannot have the rt-VBR connection class 3. However, you can configure the connection classes to desired service and parameters by using the cnfcls/cnfatmcls commands. For nrt-VBR connections in a new node, a number of connection classes are pre-configured, including 2, 4, 5, and 6.

---

Syntax

cnfcls <class number> [optional parameters]

Parameters

Parameter	Description
class number	Specifies the class to configure. Range: 1-10
optional parameters	Individual parameters are specific to the type of connection (CBR, rt-VBR, nrt-VBR, ABR, ATFR). Each is prompted one at a time. Refer to the dspcls command to see the parameters in each of the classes.

Attributes

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

Related Commands

addcon, dspcls, cnfatmcls, dspatmcls

Example

Configure connection class 10. The command line interface (CLI) displays the current settings and requests the class type. After you enter a class type, the CLI prompts you to specify each parameter for the selected class type (ABRSTD in the second screen display).

cnfcls 10

sw60 TN SuperUser BPX 8620 9.3 Date/Time Not Set

ATM Connection Classes

Class: 10 Type: CBR

PCR(0+1) % Util CDVT(0+1) Policing

4000/4000 100/100 10000/10000 4

Description: "Default CBR 4000"




This Command: cnfcls 10




Enter class type (VBR, CBR, UBR, ABRSTD, ABRFST, ATFR):




_______________________________________________________




sw60 TN SuperUser BPX 8620 9.3 Date/Time Not Set

ATM Connection Classes

Class: 10 Type: ABRSTD

PCR(0+1) % Util MCR CDVT(0+1) AAL5 FBTC

4000/4000 100/100 4000/4000 10000/10000 n

Description: "Default CBR 4000"




This Command: cnfcls 10 abrstd * * * * *




Do you want this change (y/n)?




This screen is an example of a cnfcls/cnfatmcls command and response:

pubsbpx1 TN silves:1 BPX 8620 9.3 Apr. 13 2000 10:42 PDT

ATM Connection Classes

Class: 2 Type: nrt-VBR

PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR

1000/1000 100/100 10000/10000 n 1000/1000

MBS Policing

1000/1000 3

Description: "Default nrt-VBR 1000 "




This Command: cnfcls atm 2

Enter class type (rt-VBR, nrt-VBR, CBR, UBR, ABRSTD, ABRFST, ATFR, ATFST, ATFT,

ATFTFST, ATFX, ATFXFST):

cnfcmb (configure combined timeout parameters)

Configures the time the node waits for a second packet to become available for placing in an ATM cell. Use the cnfcmb command to control the time that the node waits for individual traffic types.

Syntax

cnfcmb <parameter> <value>

Parameters

Parameter	Description
<parameter>	Specifies the number of the parameter to change.
<value>	Specifies the value of the parameter to change. When you enter a value for a parameter, switch software multiplies the value by 125 microseconds to derive the timeout.

Parameter Values

Parameter	Description	Default
1	Timeout for Voice (multiplied by 125 microseconds)	2
2	Timeout for Time-Stamped Traffic (multiplied by 125 microseconds)	2
3	Timeout for High Priority Traffic (multiplied by 125 microseconds)	0
4	Timeout for Non-Time-Stamped Traffic (multiplied by 125 microseconds)	2
5	Timeout for Bursty Data 1 Traffic (multiplied by 125 microseconds)	255
6	Timeout for Bursty Data 2 Traffic (multiplied by 125 microseconds)	255

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
service	Yes	No	IGX			Yes

Related Commands

dspchcnf

Example

Change the timeout for voice packets from the default of 2 * 125 microseconds to 1 * 125 microseconds.

cnfcmb 1 1

pubsigx1 TN SuperUser IGX 32 9.3 Apr. 13 2000 23:38 PDT

System-Wide Combine Timeout Parameters

1 Packet Combining Timeout for Voice (125 usec *)...................... 2

2 Packet Combining Timeout for Time Stamped Traffic (125 usec *)....... 2

3 Packet Combining Timeout for High Priority Traffic (125 usec *)...... 0

4 Packet Combining Timeout for Non Time Stamped Traffic (125 usec *)... 2

5 Packet Combining Timeout for Bursty Data 1 Traffic (125 usec *)...... 255

6 Packet Combining Timeout for Bursty Data 2 Traffic (125 usec *)...... 255




This Command: cnfcmb

Which parameter do you wish to change: 1 1




cnfcmparm (configure connection management parameters)

Configure various connection management parameters for the node. This command configures parameters (see Table 3-20 for parameter values) that affect Adaptive Voice, Rerouting, and Courtesy Up/Down. These parameters are used only at the local node.

The cnfcmparm command is used to enable cost-based route selection and the use of delay as the trunk cost. By default, delay is enabled. This worst-case delay for each connection type is calculated from the configured voice and non-time-stamped trunk queue depths.

For delay sensitive connections on the IGX (voice and non-time-stamped), the worst-case trunk delay can be used as the per-trunk cost.

For delay sensitive connections on the BPX (ATM CBR), end-to-end delay is not used as a routing constraint in Automatic Routing Management.

Syntax

cnfcmparm <parameter> <value>

Parameters

Parameter	Description
<parameter>	Specifies the number of the parameter to change. See Display Fields below.
<value>	Specifies the new parameter value to enter.

Table 3-20 Parameter Values 

No.	Parameter	Description	Range	Default
8	Maximum Routing Bundle	For rerouting, the maximum number of connections allowed in a routing request. For derouting, the maximum number of connections chosen using the CoS-based criterion. The value of this parameter should be set to less than that of parameter 21. A larger value provides a faster rerouting/derouting time. A smaller value provides better load balancing.	1-250	90
9	Reroute Timer	The number of seconds since the last reroute to wait before attempting another reroute of the same connection. After a connection has been successfully routed, it does not get rerouted again (especially for a connection that has previously experienced a failure at its preferred route) until this amount of time has elapsed. The time delay permits the preferred route to stabilize its operational status before a working connection with a preferred route is returned to the preferred route. A zero timer means the request is re-attempted immediately.	0-900 seconds	0 seconds
10	Timer Reset on Line Fail	This boolean specifies that the reroute timer in parameter 9 can be ignored if the current route actually fails (instead of attempting a rerouting of working connections on non-preferred routes).	y=yes n=no	y
11	Max Down/Up Per Pass	The maximum number of connections allowed to be upped or downed per pass. A larger value provides a faster completion of state update notifications, at the expense of potentially flooding the network. A smaller value provides better control of network traffic, but at the expense of prolonged state update notifications.	0-255	50
12	Down/Up Timer	The amount of time to wait before the next pass of upping/downing connections. A larger value provides slower-paced state update notifications, thus allowing time for the node to process other requests. A smaller value provides faster-paced state update notifications.	1000-65535 msecs	30000 msecs
13	Maximum Route Errors per Cycle	The maximum number of failed rerouting attempts allowed for a connection. Once this threshold has been reached, the connection is removed from the reroute group (see parameters 25, 26, and 27) and placed in a block waiting for the next cycle. (See also parameters 14 and 15.) A larger value provides a more resilient rerouting attempt. A smaller value allows a faster declaration of rerouting failure.	0-65535 failures	BPX: 50 IGX: 200
14	Maximum Time Between Routing Cycles	All connections that have waited for this amount of time are allowed to be returned into the reroute group. The expiration of this timer starts off another cycle of rerouting attempts. (See also parameters 13 and 15.) A larger value provides more time for the network topology to settle before re-attempting a connection reroute. A smaller value allows more frequent reroute attempts.	1-8 minutes	5 minutes
15	Maximum Routing Error Cycles	The maximum number of cycles of rerouting attempts. Once this threshold has been reached, the connection is declared failed. You must use the rrtcon command to reroute the failed connection. (See also parameters 13 and 14.) Alternatively, the failed connection is rerouted when the BCC becomes active (for example, due to card reset or switchcc). A larger value provides a more resilient rerouting attempt. A smaller value allows a faster declaration of rerouting failure.	0-255 cycles	BPX: 10 IGX: 1
16	Routing pause timer	The amount of time to wait before the next rerouting attempt. Do not wait when set to 0. A larger value provides a slower-paced rerouting attempt, taking advantage of possible network topology updates. A smaller value allows for a faster-paced rerouting attempt that does not depend on the changing network topology.	0-65535 msecs	0
17	Max. messages sent per update	The maximum number of CMUPDATE messages that may be sent into the network without acknowledgment. This parameter permits the transmitting node to throttle the networking traffic to prevent jamming. A larger value allows the broadcasting to complete faster, at the risk of jamming the network. A smaller value slows down the broadcasting without flooding the network, but at the expense of more broadcasting iterations.	0-223 decimal	10
18	Send SVC urgent msgs	IGX only. This parameter enables an IGX node to inform each via node to remove an SVC connection during deletion. When disabled, the via nodes are not immediately informed through an update message. This causes the trunk loading occupied by a deleted SVC to remain unavailable until the update message is received by the via node.	y=yes n=no	BPX: n IGX: y
19	Max SVC Retry	IGX only. The maximum number of failed routing attempts before the SVC connection is declared failed. If the routing attempt fails due to a reason other than being "blocked," the connection is immediately declared failed. A blocked attempt means that the routing state machine on the via/slave node is already processing a route request, or is locked by some other state machines. A larger value provides a more resilient SVC rerouting attempt. A smaller value allows a faster declaration of rerouting failure.	0-30 decimal	0
20	Wait for TBL updates	After routing all connections based on CoS, wait roughly this amount of time before the routing of other connections in need of rerouting (for example, those failed connections due to lack of critical internal resources). This delay allows the topology to settle after the CoS-based rerouting phase. This wait period should typically be one or two seconds longer than the time specified by the Fast Interval parameter (default 5 seconds) of the cnftlparm command.	0-65000 decimal	70 (x100 msecs)
21	Max derouting bundle	The maximum number of connections chosen based on load, that can be derouted concurrently. The value of this parameter should be set to greater than that of parameter 8. The actual number of connections concurrently derouted can reach the sum of this parameter and of parameter 8. A larger value provides a faster rerouting/derouting time. A smaller value provides better load balancing.	0-16000 decimal	500
22	Enable cost-based routing	This boolean specifies whether the cost-based routing algorithm should be used in preference to the hop-based routing algorithm. Yes means enable cost-based routing. Cost-based routing allows the network operation to better tune the network utilization based on the least cost. Hop-based routing is a simpler algorithm that selects a path strictly based on the least number of hops.	y=yes n=no	n
23	Enable route cache usage	This boolean specifies whether the most recent successfully used routes are to be placed in cache in order to avoid performing route selection. Yes enables route cache usage. The cache route can be either a cost-based route or a hop-based route.	y=yes n=no	n
24	Use delay for routing	This boolean specifies whether queuing delay is considered in the cost-based routing algorithm. Yes means use delay for routing. The parameter only applies to voice and non-timestamped connection types.	y=yes n=no	n
25	# of reroute groups used	Specifies the number of reroute groups allowed for the node. Each reroute group is categorized based on the load requirement for each connection. The node reroutes connections with the highest load units first and proceeds with successively decreasing load unit ranges. A larger value provides more groups at the cost of more iterations stepping through the reroute groups during rerouting. A smaller value provides a faster completion of the iterations.	1-200 groups	50
26	Starting size of RR groups	The first reroute group is defined to consist of connections with load units at or below this parameter value. During rerouting, connections from this reroute group are considered last. Connections with load units above this value but at or below the sum of this value and that of the next parameter (increment between RR groups) are placed in the second reroute group. A larger value provides a bigger range of bandwidth for the first reroute groups. A smaller value provides a more refined range of bandwidth included in the first reroute group.	0-96000 cell load units (CLUs)	0 CLUs
27	Increment between RR groups	Each of the remaining reroute groups is defined to consist of connections with load units higher than the previous reroute group, but at or below the sum of the previous reroute group threshold and this parameter value. The last reroute group can accommodate any load units above the second-last reroute group threshold. (See parameter 26 for a definition of the first reroute group.) A larger value provides a bigger range of bandwidth for each of a smaller number of reroute groups. A smaller value provides a smaller range of bandwidth for each of a larger number of reroute groups.	1-96000 cell load units (CLUs)	100 CLUs
28	CM updates app timeout	Configures a second timeout for CM updates. This avoids CM-update overloads after rebuilds in large networks with fully loaded nodes. The timeout value is specified in 10-second increments. This parameter is relevant to the following CM updates: •Exist •Non-exist •Pref route •BW •State Switch software sends all of the above updates in the form of a bitmap of LCON indexes. When an update is sent, switch software marks a timeout of 150 seconds. It also marks a "pending bitmap" that contains all the LCON indexes for update messages that have been sent. If the node does not receive a response for any of the updates within the 150 second timeout, the updates are sent again. However, if the node receives a networking acknowledgment for the CM update message, or a response for some of the LCONs (also a bitmap), a second timeout of *10 seconds (the value configured for this parameter) is marked. Also, the bits for which a timeout has been received are cleared in the pending bitmap. If this second timeout expires, all the updates are sent again to the remote node, including the updates for which responses have been received.	1 to 15 (10 to 150 seconds)	5 (50 seconds)
29	Route concurrency level	Specifies the number of concurrent routes available on the BPX or IGX node. A value of 1 disables concurrent routing, and the node uses sequential routing. The values 2 through 8 indicate the total number of concurrent routes available on the node. When the value is changed, all reroute statistics are retained. The Concurrent Routing feature can be enabled only if the entire network is running Release 9.3.30 or above.

Attributes

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

Related Commands

dsprrst, cnftlparm

Example

The example shows the two screens required to display all cnfcmparm parameters.

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

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 15 2001 06:05 PST




1 Normalization Interval [ 2] (D)

2 Max Number To Normalize [ 5] (D)

3 Normalization Logging [ No]

4 Settling Interval [ 4] (D)

5 Minimum Open Space [ 1000] (D)

6 Normalization Priority [ Load]

7 Load Sample Period [ 4] (D)

8 Maximum Routing Bundle [ 90] (D)

9 Reroute Timer [ 3] (secs)

10 Reset Timer on Line Fail [ Yes]

11 Max Down/Up Per Pass [ 50] (D)

12 Down/Up Timer [30000] (msecs)

13 Max Route Errs per cycle [ 200] (D)

14 Time between Rrt cycles [ 5] (mins)

15 Max. Rrt Err cycles [ 1] (D)




This Command: cnfcmparm





Continue?

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

sws5 TN Cisco IGX 8420 9.3.a4 Mar. 15 2001 06:06 PST




16 Routing pause timer [ 0] (msecs)

17 Max msgs sent per update [ 10] (D)

18 Send SVC urgent msg [ Yes]

19 Max SVC Retry [ 0] (D)

20 Wait for TBL Updates [ 70] (100 msecs)

21 Max Derouting Bndl (0=all)[ 500] (D)

22 Enable Cost-Based Routing [ No]

23 Enable Route Cache Usage [ No]

24 Use Delay for Routing [ No]

25 # of reroute groups used [ 50] (D)

26 Starting size of RR grps [ 0] (CLU)

27 Increment between RR grps [ 100] (CLU)

28 CM updates app timeout [ 5] (10 secs)

29 Route concurrency level [ 1] (D)





This Command: cnfcmparm





Enter parameter index:

cnfcon (configure connection)

If the connection type includes ForeSight (ABR enabled), the results of the last test round-trip delay command (tstdelay) appear. Note that this is not the current RTD but the result of the last test that ran. Connection priority—high or low—is displayed for standard Frame Relay connections and ForeSight connections. Several checks are done on the parameters that specify bandwidth to assist users in efficient use of network bandwidth.

These messages describe the performance evaluation:

•Error: Min cannot exceed peak

•Warning: Min exceeds this port's speed.

•Warning: Sum of mins exceeds port's speed.

•Warning: Peak exceeds this port's speed.

Warning messages are informational only, so the related operation continues. If an error message appears, the operation does not continue.

Syntax

cnfcon <slot.port [dlci | vpi.vci]> [bandwidth parameters]

Parameters

Parameter	Description
<slot.port [dlci | vpi.vci]>	Specifies the connection to configure. This command configures one connection at a time.
[bandwidth parameters]	Optional. Refer to the addcon command for descriptions and connection types.

Attributes

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

Related Commands

addcon, dspcon

Example

Configure ASI connection 11.1.1.15.

cnfcon 11.1.1.15

bpx01 TN Cisco BPX 8620 9.3.2V Jan. 19 2001 07:53 PST




Conn: 11.1.1.15 bpx02 11.2.21.15 nrt-vbr Status:OK

PCR(0+1) % Util CDVT(0+1) AAL5 FBTC SCR

50/50 100/100 250000/250000 n 50/50




MBS Policing VC Qdepth CLP Hi CLP Lo

1000/1000 3 1280/1280 80/80 35/35




Trunk Cell Routing Restrict: Y







Last Command: cnfcon 11.1.1.15

cnfcond (configure conditioning template)

Creates a conditioning template that specifies the bit patterns to be transmitted for each of the T1 and E1 timeslots and their A, B, C, and D signaling bits while the channel is in the failed state. Its purpose is to prevent the signaling bits from returning to the idle (on-hook) bit pattern during a channel failure and to force a known bit pattern (usually busy). If a connection fails and the template has been specified as the conditioning template for the failed connection, the data parameter in the template is transmitted in the channels timeslot, and the A, B, C, and D bits are processed according to the specified parameters.

A two-character sequence in the ID parameter field identifies the template. The Data Pattern field displays the pattern transmitted in the channels timeslot. The Signaling Pattern field displays the pattern transmitted in the channel's A, B, C, and D signaling bit positions. Each of the A, B, C, and D signaling bits are specified independently and may be held high or low or toggled to the on-hook condition for a short time then off-hook (the name of this latter action is a wink). You can control the timing of the bit-toggling by specifying the duration of winks in increments of 50 ms.

A typical failure response is for the node to:

1. Transmit idle characters in the channel's timeslot

2. Signal off-hook for a period of 2 seconds

3. Return permanently to the on-hook condition

Syntax

cnfcond <id> <data> <A bit> <B bit> <C bit> <D bit>

Parameters

Parameter	Description
id	Specifies the identifier of conditioning template. The identifier may be any two character combination of lowercase letters (a-z) and numeric digits (0-9).
data	Specifies an eight-bit binary string to use instead of the voice in the event the channel fails.
A bit B bit C bit D bit	Specifies the signaling sequence to be transmitted for these bits in the event of a channel failure. You can independently set each of these parameters. Each element in the sequence is expressed as a 1 or 0 (to indicate the logic state of the line) followed by a number in parenthesis to indicate the duration that the state remains on the channel. The duration number is expressed in 50 ms intervals. If you do not enter a duration value, the state remains the same indefinitely. For example, if <B> is set to 1(40); upon a channel failure, the B bit remains in the 1 state for 2 seconds (40 x 50 ms=2 seconds). For another example, <C> set to 0 would cause the C bit to be held permanently at 0 during a failed channel condition because no duration value is present. Note that you can specify a sequence of states by entering several states separated by slash symbols. The maximum number of states in a sequence is 5. For example, you could set <A> to 1(40)/0(20)/1 to vary the duration of the 0 and 1 states.

Attributes

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

Related Commands

cnfvchtp, dspchcnf, dspcond

Example

Configure the conditioning template.

cnfcond lm 01010100 0(40)/1 1 1 1

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

Conditioning criterion lm:

Data Pattern

01010100 - E1/T1

Signaling Pattern

A 0(40)/1

B 1

C 1

D 1

Last Command: cnfcond lm 01010100 0(40)/1 1 1 1

Next Command:

cnfcos (configure CoS)

Determines the priority for rerouting a connection. You determine the priority by specifying a delay before the network reroutes one or more failed connections. The CoS applies to:

•A single connection

•A range of connections

•A connection group

When connections have failed (typically due to a trunk failure), the network reroutes them according to priorities that are set primarily by the class of service (CoS). The value of CoS is the number of seconds the network waits before it begins to reroute the connection, so the CoS determines the rerouting order for connections owned by a node. The range of possible CoS values is 0-15.

The number of connections in a network has an effect on the increment between CoS values you should use. For larger numbers of connections, you should allow more time to reroute the connections in a class. To facilitate the greater time required to reroute larger numbers of connections, use a larger increment between CoS values. In a larger network, for example, you could specify CoS values that are 3 seconds apart (such as 0, 3, 6, 9, 12, and so on, for example). For a network with less traffic, assign CoS values in increments of 1 or 2. This strategy ensures that all connections of a given CoS reroute before the connections with the next CoS start to reroute.

Syntax

cnfcos <group | channel> <cos>

Parameters

Parameter	Description
<group | channel>	Specifies the voice, data, Frame Relay, or FastPAD voice/data channel(s), where channel is one of the following: •Voice connections: slot.channel •Serial data connections: slot.port •Frame Relay connections: slot.port.DLCI
<cos>	Specifies the class of service number to assign to the channel, range of channels, or connection group. Range: 0-15 seconds The rerouting priority is inversely proportional to the CoS (a low CoS values means a high routing priority).

Related Commands

dspcons

Attributes

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

Example

Set the CoS for channel 5.1 to 0.

cnfcos 5.1 0

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.2.400 beta 19.2.302 Ok fr 0 L

14.1 gamma 15.1 Ok v 0 L




Last Command: cnfcos 5.1 0

Next Command:




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

Reassign the VPI and start_VCI for the control channels between the VSI controller and the UXM slaves. The required input parameters are:

•a controller ID

•a new VPI

•a new start_VCI

The command will delete all existing control channels to release the old VPI and start_VCI and then reprogram the control channels with the new VPI and start_VCI.

During the process of channel deprogramming and reprogramming, communication between the controller and slaves will be disrupted.

Syntax

cnfctrlr <controller_id> <VPI> <start_VCI>

Parameters

Parameter	Description
<controller_id>	The controller identifier (1-16)
<VPI>	The VPI for control channel UNI ports: 0-255 NNI ports: 0-4095
<start_VCI>	The starting VCI for the control channel 16-slot IGX: 40-65521 32-slot IGX: 40-65505

Attributes

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

Example

Configure controller 3 with a new VPI (5) and a new start_VCI (100).

cnfctrlr 3 5 100

Description

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




VSI Controller Information




CtrlrId PartId ControlVC Intfc Type CtrlrIP

VPI VCIRange

3 2 0 100-70 12.1 MPLS 0.0.0.0






Last Command: cnfctrlr 3 5 40




Controller VPI.VCI reconfigured successfully!

Next Command:

cnfdate (configure date and time)

Sets the date and time for the entire network. The node broadcasts the specified date and time to every node in the network. The time displayed at each node is consistent with the time zone where the node resides. (See the cnftmzn description.) For the first-time configuration of the date and time in a network, cnfdate requires all the parameters except for second. The default for second is 0. If a date and time already exist in the network, the defaults are the existing values at the moment you enter the cnfdate command. Note that changes to date and time alter the time-stamps on WAN Manager statistics.

Syntax

cnfdate <year> <month> <day> <hour> <minute> [second]

Parameters

Parameter	Description
year	Specifies the year.
month	Specifies the month. Range: 1-12
day	Specifies the day. Range (depending on the month): 1-31
hour	Specifies the hours. Range: 0-23 For example, enter 6 AM as 6 and 6 PM as 18.
minute	Specifies the minute of the hour. Range: 0-59; Default: 0
second	Specifies the seconds. Range: 0-59; Default: 0

Attributes

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

Related Commands

cnftime, cnftmzn

Example

Set the time to 1:54:11 PM, December 16, 1997. The system prompts:
"Warning: Changing time of day affects StrataView statistics time-stamps.

Continue?"
Enter "y" to continue or "n" to abort." Upon a "y" response, the system further prompts with: "Hit RETURN to change clock, DEL to abort."

cnfdate 1997 12 16 13 54 11




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

YourID 1

Sarah 5




Last Command: cnfdate 1997 12 16 13 54 11

Warning: Changing time of day affects StrataView statistics timestamps

Continue?




cnfdch (configure voice connection for idle code suppression)

Configure a super-rate data connection that has idle code suppression (ICS) enabled or disabled, before adding a connection. The ICS information in the cnfdch screen is identical to that of dspchcnf.

The idle code suppression feature provides a way to stop FastPacket generation on an Nx64 super-rate PVC connection when the connected PBX has terminated a video call and there are no video calls in progress. It enables the UVM and CVM to detect the on-hook condition of video conferencing calls. No video traffic will be generated when a video call has terminated. Traffic on the data network is therefore reduced.

During the on-hook phase, FastPacket generation ceases, resulting in more trunk bandwidth becoming available. All connections that use ForeSight can use this unused bandwidth, resulting in higher information rate.

Because there are multiple channels involved in an Nx64 data connection, the idle code suppression configuration of the first channel in the Nx64 channel will be used for the entire connection bandwidth.

Configuration must be done for each endpoint of a connection. When the state of an ICS connection changes, no network message is sent to the other end. You can choose to configure the other end if ICS is supported on the other end also. To maximize the benefit of the idle code suppression feature, you should enable ICS on both endpoints of the connection.

If some of the specified channels do not yet have any connection attached, those channels will be initialized to a data type channel.

To interwork with HDM/LDM/SDP/LDP cards, idle code suppression on UVM/CVM/CDP channel will be turned off for any super-rate connection that also terminates on HDM/LDM/SDP/LDP.

All super-rate data connections will have their ICS state set to "disabled" state unless they have been specifically configured with the cnfdch command to be enabled, or through Cisco WAN Manager (or another SNMP manager application).

Use the cnfdchl command to configure a channel before you add a connection. The configuration remains the same when connections are removed and added again. This configuration will be removed when the associated line is deactivated.

The cnfdch command is available for level 2 users and above; that is, you must have at least privilege level 2 or above to use this command.

The cnfdch command is blocked if one or more specified channels is carrying a voice connection (including t-type).

The cnfdch command prompts you to enable or disable idle code suppression:

Enable or Disable Idle Code Suppression (e/d)?[d]:

Syntax

cnfdch <channel><ch_ics_state>

Parameters

Parameter	Description
channel	slot.line.channel for UVM or line.channel for CVM/CDP. A channel range is allowed.
ch_ics_state	Channel idle code suppression state: d for disabled; e for enabled.

Attributes

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

Related Commands

dspchcnf, dspcons

How Idle Code Suppression Works

When a video call terminates, the PBX generates the appropriate line idle code (for example, 0x7f for mu-law). Per ITU H.221 video coding scheme, no byte will be repeated on one DS0 for more than
80 times. In the case of BONDING protocol, the maximum is 256 (32 msec). The firmware can distinguish a video call and an idle channel carrying idle code. Idle code suppression is not programmable. Any byte that repeats for more than 32 msec in all DS0s in a super-rate connection will be suppressed.

Switch software determines idle code suppression capability on a card based on firmware model and revision number (for example, it considers that the CVM card supports idle code suppression starting with model B revision E firmware).

The idle code suppression feature for the UVM and CVM cards on the IGX detects the idle (on-hook) state of a video call, which uses an Nx64K data connection, and suppresses packet transmission during this idle condition. The UVM or CVM at the far end plays out the idle code during this time. You disable or enable and display the status of idle code suppression on a per-connection basis through the switch software CLI cnfdch and dspchcnf commands.

The UVM and CVM card firmware identifies an on-hook or idle condition by detecting repetition of idle codes. These codes can be present in the regular video traffic also (that is, in H.221 or BONDING frames). The code must repeat a certain number of times before it can be concluded that the call is on-hook. It is not necessary to look for specific idle codes. Any byte-code repeating beyond the threshold (about 32 ms) indicates idle channels. The firmware monitors byte repetition on each Nx64 connection for which this feature is enabled. On detecting repetition beyond the specified threshold, FastPacket generation for such a connection would cease. This results in the remote side of the connection to under-run. In this condition, it would transmit the previously transmitted byte on each DS0 for the connection. The UVM/CVM continues to monitor DS0s for the connection to detect a change in data received. Any change would indicate an off-hook condition, after which FastPacket transmission would resume.

The idle code suppression feature consists of IGX switch software Release 9.2, and requires UVM model E firmware and CVM/CDP model B revision E firmware. The new UVM/CVM/CDP firmware ensures that idle code suppression can interoperate with UVM/CVM/CDP cards that do not have idle code suppression capability. Such a configuration means that FastPacket generation stops in one direction while the other end continues to generate FastPackets. This behaves exactly the same as enabling idle code suppression on one side but not on the other side.

All back card types supported by UVM/CVM/CDP support idle code suppression.

Interface with Cisco WAN Manager and Other Network Management Systems

The SNMP agent interface on the IGX provides the following operations: Get/Set of MIB information of the desired state of idle code suppression (enabled/disabled).

If a request fails, a General Error is returned to Cisco WAN Manager. An error string is logged in the switch software error table. Cisco WAN Manager can then optionally obtain the error string from switch software. Examples of error messages are "Card in slot does not support Idle Code Suppression" and "E1 CAS and Voice Channels - Not Configured".

Inserting/Removing Cards (Idle Code Suppression Mismatch)

Given an active non-Y-redundant UVM/CVM/CDP card without ICS support, upgrades to a card with ICS are allowed. However, you cannot downgrade a card with ICS capability to a card that does not support ICS (see Table 3-21).

Given a pair of cards in a Y-redundancy configuration, whether any of them is active or not, they must have the same ICS capability (see Table 3-22).

Table 3-21 Active Line That is Not in Y-Redundant Pair

ICS Support		Comment
Old Card	New Card
NO	NO	OK—same card
NO	YES	OK
YES	NO	mismatch
YES	YES	OK—same card

Table 3-22 Card is Configured for Y-Redundancy

ICS Support		Comment
Old Card	New Card
NO	NO	OK
NO	YES	OK but ICS is not available until both cards support ICS
YES	NO	Mismatch if both cards support ICS before
YES	YES	OK

Y-Redundancy

To ensure that cards with the same ICS capability be allowed to be a Y-redundancy pair, addyred blocks cards that have different idle code suppression capability (see Table 3-23).

Table 3-23 Addyred Blocked Cards

ICS Support		Comment
Primary Card	Secondary Card
NO	NO	OK
NO	YES	addyred blocked
YES	NO	addyred blocked
YES	YES	OK

Upgrading and Downgrading the Idle Code Suppression Feature

Given an active non-Y-redundant UVM/CVM/CDP card (see Table 3-24) without idle code suppression support, an upgrade to a card with ICS support is allowed. Downgrading a card with ICS capability to a card without ICS capability is not allowed.

Upgrading the ICS feature to a Y-redundancy pair (see Table 3-25) that does not support the ICS feature is not allowed. The Y-redundancy pair must be deleted first to upgrade the feature. After both cards complete the ICS upgrade, the cards can be added as a Y-redundancy pair.

Table 3-24 Active Line that is Not in Y-Redundant Pair

ICS Support		Comment
Old Card	New Card
NO	NO	OK—same card
NO	YES	mismatch
YES	NO	mismatch
YES	YES	OK—same card

Table 3-25 Card is Configured for Y-Redundancy

ICS Support		Comment
Old Card	New Card
NO	NO	OK
NO	YES	OK but ICS is not available until both cards support ICS
YES	NO	Mismatch if both cards support ICS before
YES	YES	OK

Limitations with Idle Code Suppression

T-type connections are not supported. On a VNS controlled network, t-type SVCs are used for video calls. VNS does not support Nx64 super-rate connections.

This feature is intended to work with video codecs that implement H.222 or BONDING protocol only.

Example

Display configuration values for channels 9.1.3 through 9.1.5.

cnfdch 9.1.3—5

sw176 TRM StrataCom IGX 8420 9.3 Apr. 13 2000 17:28 PST




Maximum EIA % DFM Pattern DFM Idle Code PreAge

From 9.1.3 Update Rate Util Length Status Suppr (usec)

9.1.3-5 - - - - Disabled 0





This Command: cnfdch 9.1.3-5

cnfdchtp (configure data channel interface type)

Configures a CDP, CVM, or LDP or LDM DDS port interface type to OCU or DSU. When configuring DDS operations, this command returns an error if executed on a slot with an EIA/TIA-232 back card. It forces a back card slot from EIA/TIA-232 mode to DDS mode if a back card is not installed and there are no connections. Any Y-cable association is deleted in this case. The clocking tracks the DDS port interface type. OCU type interfaces are configured as looped, and DSU type interfaces are configured as normal. The default interface is DSU.

When configuring CDP, CVM, LDP, or LDM operation, this command configures DCE types as normal clocking and DTE types as looped clocking. The default type is DCE. For T1 lines, DS0A on T1 unassigned signaling is configurable. When a connection is not present, voice channels are converted to data channels.

Syntax

cnfdchtp <channel> <interface type> [unassigned signaling]

Parameters

Parameter	Description
<channel>	Specifies the channel to configure in the format <slot>. <port>.
<interface type>	Specifies the interface type to configure. An LDP or LDM DDS port can be configured as DSU or OCU (enter ds or oc). A CDP or CVM port can be configured as DCE or DTE (enter dce or dte).
[unassigned signaling]	Optionally specifies an optional parameter for T1 lines to indicate DS0A or T1 unassigned signaling. Enter d for DS0A or t for T1.

Attributes

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

Example

Configure DDS channel 31.1 as OCU.

cnfdchtp 31.1 oc

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 17:30 MST

Data Channel: 31.1

Interface: DDS-4 OCU Config

Clocking: Looped

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

DSR ON CTS ON

DCD ON

Last Command: cnfdchtp 31.1 oc

Next Command:

Example

Configure channel 22.1 as DCE with T1 unassigned signaling.

cnfdchtp 22.1 dce

beta TRM YourID:1 IGX 32 9.3 Apr. 13 2000 17:30 MST

Data Channel: 22.1

Interface: Missing DDS0A DCE Configuration

Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

DSR ON CTS ON

DCD ON




Last Command: cnfdchtp 22.1 dce t

Next Command:




cnfdclk (configure data channel clocking type)

The clock configuration of each channel of a connection determines how the clock will be propagated through the network, and how external equipment should be synchronized.

If clocking is not set correctly, there might be no synchronization, and the connection would operate in a plesiochronous mode. Each data port can be configured independently to act as either DCE or DTE by adjusting the jumper (SDI card) or changing the adapter cable (LDI card) on the data interface card. The effect of the clocking type designated depends on whether each data port is configured as DTE or DCE.

Syntax

cnfdclk <channel> <normal | split | looped>

Parameters

Parameter	Description
<channel>	Specifies the channel to configure in the format <slot>. <port>.
<normal | split | looped>	Specifies the clocking type to assign to the channel. Valid clocking types are: •n for Normal •s for Split •l for Looped for an SDP or HDM (fewer options for an LDP or LDM)

Attributes

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

These data clocking configurations are possible with the cnfdclk command:

DCE-Configured Data Port: Normal Clocking

When the data port is configured as DCE, selecting a clocking type of n (for normal) results in clocking as illustrated in Figure 3-11. The IGX node, acting as DCE, provides both the transmit and receive data clocks to the user equipment.

Figure 3-11 Normal Clocking on a DCE

DCE-Configured Data Port: Split Clocking

When the data port is configured as DCE, selecting a clocking type of s (for split) results in clocking as illustrated in Figure 3-12. In split clocking, TT may be generated independently of RxC. The maximum data rate for split clocking is 112 Kbps.

Figure 3-12 Split Clocking on a DCE

DCE-Configured Data Port: Looped Clocking

When the data port is configured as DCE, selecting a clocking type of l (for looped) results in clocking as illustrated in Figure 3-13. The Terminal Timing signal, called TT or XTC, is simply RxC looped back from the user equipment. In this configuration, it is important that the two clocks (RxC and TT) be frequency locked. This clocking configuration is supported for all data rates.

Figure 3-13 Looped Clocking on a DCE

DTE-Configured Data Port: Normal Clocking

When the data port is configured as DTE, selecting a clocking type of n (for normal) results in clocking as illustrated in Figure 3-14. The IGX, acting as DTE, receives both the transmit and receive data clocks from the user equipment. When the user equipment is not referenced to the network clock, the maximum data rate for this configuration is 112 Kbps. The two clocks must be frequency-locked for proper operation.

Figure 3-14 Normal Clocking on a DTE

DTE-Configured Data Port: Split Clocking

When the data port is configured as DTE, selecting a clocking type of s (for split) results in the clocking as illustrated in Figure 3-15. When the user equipment is not referenced to the network clock, the maximum data rate for this configuration is 112 Kbps. The two clocks must be frequency-locked for proper operation.

Figure 3-15 Split Clocking on a DTE

DTE Configured Data Port: Looped Clocking

If you specify clocking type of l (looped) when the data port is in DTE mode, the result is the clocking arrangement shown in Figure 3-16. The RxC clock signal is the TT(XTC) signal looped back to the IGX node by the user equipment. The network supports this clocking configuration for all data rates. The restrictions to the data clocking schemes are:

•Except for special cases, isochronous clocking is limited to data rates of 112 Kbps or less. For higher data rates, all clocks must be frequency-locked to the network.

•For any port there must be only one isochronous clock in a direction. Any situation where user equipment provides two clock signals that are not locked is subject to slippage.

•Slippage may also occur in any situation where there are opposing user clocks for a single direction of data.

Figure 3-16 Looped Clocking on a DTE

Example

Configure the clocking for channel 5.1 to normal.

cnfdclk 5.1 n

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

Data Channel: 5.1

Interface: V35 DCE

Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

RI(J) OFF DSR (E) ON

CTS(D) ON TN (K) OFF

DCD(F) ON

Last Command: cnfdclk 5.1 n

Next Command:




cnfdiagparm (configure diagnostic test parameters)

Sets various diagnostic test parameters for the nodes. These parameters affect the three IGX and BPX automatic diagnostic tests. Use this command to set test parameters on the internal system clock.

Syntax

cnfdiagparm

Display Parameters

No.	Parameter *	Description	Default *
1	VDP Test Frequency This parameter is OBSOLETE.	Interval between VDP background tests (in seconds).	50
2	LDP tstport delay	Seconds delayed before test data is sent.	10
3	System clock drift (8.192 MHz)	Range of allowable drift of system clock.	±480
4	UEC-B's PLL railing (8.192 MHz) This parameter is OBSOLETE.	Range of UEC-B's phase lock loop rail.	± 2720
5	NPM PLL Min. (8.192 MHz)	Lower limit of controller card's PLL.	- 92000
6	NPM PLL Max. (8.192 MHz)	Upper limit of controller card's PLL.	+ 508000
7	Clock Test Window	Number of samples that make up a window.	10
8	Clock Test Max Error in Window	Errors within window before fault isolation.	4
9	Clock Test Isolation Window	Window size during fault isolation.	10
10	Clock Fault Max. Error in Window	Errors allowed during fault isolation.	3
11	Clock Test Frequency	Interval between clock tests.	200 ms.
12	Clock Test Switch Delay	Delay clock testing after any clock transfers to allow settling.	3000 ms.
13	Card Reset Threshold		255
14	Card Reset Increment		0
* Clock Test parameters—Frequencies are in Hz, offset from 8.192 MHz

Attributes

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

Related Commands

cnftstparm

---

Note Parameters 1 and 4 are obsolete.

---

Example

cnfdiagparm

sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 01:39 GMT

1. Vdp Test Frequency (seconds) [50]

2. LDP tstport delay [10]

3. System clock drift (8.192 MHz) +- [480]

4. UEC-B's PLL railing (8.192 MHz) +- [2720]

5. PCC's PLL minimum (8.192 MHz) - [92000]

6. PCC's PLL maximum (8.192 Mhz) + [508000]

7. Clock Test Window [10]

8. Clock Test Max Error in Window [4]

9. Clock Fault Isolation Window [10]

10. Clock Fault Max Error in Window [3]

11. Clock Test Frequency (msec) [200]

12. Clock Test Switch Delay (msec) [2000]

13. Card Reset Threshold [60]

14. Card Reset Increment [10]

Last Command: cnfdiagparm

Next Command:

cnfdlparm (configure download parameters)

Sets various software and firmware downloader parameters that affect the SW/FW download protocol. It is primarily a debug command, included only to accommodate the possibility that some future software or firmware revision may need to be adjusted for optimizing the downloading process.

---

Caution You should not change downloader parameters except under specific direction from the Technical Assistance Center (TAC).

---

When you enter cnfdlparm, the system displays an indexed list of parameters.

Syntax

cnfdlparm

Attributes

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

Display Fields

No.	Parameter	Description	Range	Default
1	Rmt Blk Freq	For downloads to a remote node, Rmt Blk Freq is the time between blocks.	1-9999999 msecs	100 msecs
2	Rmt Blk Size	For downloads to a remote node, Rmt Blk Size is the number of bytes in each block.	1-7C0 hex	400 hex
3	Lcl Blk Freq	For downloads to the other processor in the same (local) node, Lcl Blk Freq is the time (in msecs) between blocks.	1-9999999 msecs	100 msecs
4	Lcl Blk Size	For downloads to the other processor in the same (local) node, Lcl Blk Size is the number of bytes in each block.	1-7C0 hex	400 hex
5	Image Req Freq	The time between requests for a description of an image. When a node seeks a new software image from other nodes, it first sends requests for a full description of the image residing on a node to determine if that node has the correct image. The requesting node sends its request one node at a time. Image Req Freq is the time between the last request and the request to another node. (This parameter is not a frequency but rather a time period.)	1-9999999 msecs	10000 msecs
6	Dnld Req Freq	After a node seeking a new software image has found a node with the correct image, it requests a download of the image. If the node with the correct image is not available to send the image, the requesting node waits a period of time before it again requests the image. Dnld Req Freq is the period of time the requesting node waits before it again requests the image. (This parameter is not a frequency but rather a time period.)	1-9999999 msecs	10000 msecs
7	Session Timeout	The time a receiving node waits for a block transfer to resume. If a block transfer stops after downloading begins, the Session Timeout is the time the receiving node waits to resume before it gives up and requests the download again.	1-9999999 msecs	30000 msecs
8	Request Hop Limit	Limit on the number of hops the local node can go to request a download. (The number of hops is the number of trunks that are crossed for one node to communicate with another node.) Request Hop Limit=1 means the request can go to only an immediate neighbor.	1-9999999	1
9	Crc Throttle Freq	The number of CRC calculations per second. Crc Throttle Freq lets you reduce the number of calculations so the node does not use processor time for CRC calculations.	1-9999999	5000
10	Crc Block Size	Number of bytes that a CRC calculation covers. The default is intentionally the same as Rmt Blk Size and Lcl Blk Size.	1-7C0 hex bytes	400 hex
11	Rev Change Wait	The time to wait before the node actually loads the software for loadrev or runrev execution.	0-99999 msecs	0
12	CCs Switch Wait	A wait period before the node actually switches control cards during switchcc execution. During normal operation, you should have no reason to increase CCs Switch Wait.	1-9999999 msecs	1000 msecs
13	Lcl Response TO (Time Out)	On a local node, a processor that is downloading to another processor must receive an acknowledgment from the receiving processor for each block that correctly arrived. If the sending processor does not receive an acknowledgment by the time Lcl Response TO (Time Out) has elapsed, the downloading processor sends the block again.	1-9999999 msecs	5000
14	Rmt Response TO (Time Out)	When one node downloads to another node, the sending node must receive an acknowledgment for each block correctly received. If the sending node receives no acknowledgment by the time Rmt Response TO (Time Out) has elapsed, the sending node sends the block again.	1-9999999 msecs	30000
15	FW Dnld Block TO (Time Out)	The wait period that a controller card waits for an acknowledgment from a receiving card that it correctly received a block.	1-9999999 msecs	50 msecs
16	FW Dnld Msgs/Block	Number of Cbus messages per CRC block CRC check on the payload of the FW download message.	1-9999999 msecs	4
17	Flash Write TO	During flash memory programming, Flash Write TO (Time Out) is the time to wait for an acknowledgment that a write cycle finished before timing out.	1-9999999 msecs	16000 msecs
18	Flash Erase TO	During a flash memory erasure, Flash Erase TO (Time Out) is the time to wait for an acknowledgment that the erase cycle finished before timing out.	1-9999999 msecs	100
19	Erase Verify TO	Erase Verify TO (Time Out) is the time to wait for an acknowledgment of the completion of the second (or "true") verification of the erasure before timing out. The Erase Verify TO parameter is useful only if write/erase performance characteristics of a flash memory device change.	1-9999999 msecs	16000 msecs
20	Standby Flash TO	During flash memory programming, Standby Flash TO (Time Out) is the time to wait for an acknowledgment that the standby flash is available before timing out.	1-9999999 msecs	300 msecs
21	Lcl Flash Init TO	During flash memory programming, Lcl (local) Flash Init TO (Time Out) is the time to wait for an acknowledgment that a initialization of local flash memory finished before timing out.	1-9999999 msecs	1000
22	Flsh Write Blk Sz	Number of bytes per write cycle.	1-10000 hex	10000 hex
23	Flsh Verify Blk Sz	Second (or "true") verification of the block write. The Flsh Verify Blk Sz parameter is useful only if performance characteristics of a flash memory device change.	1-10000 hex	400 hex
24	Chips Per Write/Erase	Number of bytes per write/erase cycle	1, 2, or 4	1

Example

cnfdlparm

pubsbpx1 VT SuperUser BPX 8620 9.3 Apr. 13 2000 23:18 GMT




1 Rmt Blk Freq (msec) [ 100] 16 FW Dnld Msgs/Block(dec) [ 4]

2 Rmt Blk Size (hex) [ 400] 17 Flash Write TO(msec) [ 16000]

3 Lcl Blk Freq (msec) [ 100] 18 Flash Erase TO(msec) [ 100]

4 Lcl Blk Size (hex) [ 400] 19 Erase Verify TO(msec) [ 16000]

5 Image Req Freq (msec) [ 10000] 20 Standby Flash TO(sec) [ 300]

6 Dnld Req Freq (msec) [ 10000] 21 Lcl Flash Init TO(msec) [ 1000]

7 Session Timeout (msec) [ 30000] 22 Flsh Write Blk Sz (hex) [ 10000]

8 Request Hop Limit (dec) [ 1] 23 Flsh Verfy Blk Sz (hex) [ 400]

9 Crc Throttle Freq (dec) [ 5000] 24 Chips Per Write/Erase [ 1]

10 Crc Block Size (hex) [ 400]

11 Rev Change Wait(dec) [ 0]

12 CCs Switch Wait(dec) [ 1000]

13 Lcl Response TO(msec) [ 5000]

14 Rmt Response TO(msec) [ 20000]

15 FW Dnld Block TO(msec) [ 50]




This Command: cnfdlparm





Which parameter do you wish to change:

cnfecparm (configure echo canceller parameters)

Configures the CDP or CVM integrated echo canceller (IEC) parameters for specified voice circuit line.

The cnfecparm command configures IEC parameters associated with all voice channels for the specified circuit line. Setting these parameters allows you to optimize the IEC performance.

The dspecparm command description lists the defaults and provides a sample display. Also, refer to the cnfchec command.

Syntax

cnfecparm <line> <parameter number> <parameter value>

Parameters

Parameter	Description
<line>	Specifies the circuit line to configure.
<parameter number>	Specifies the number of the parameter to change.
<parameter value>	Specifies the new value to enter for the parameter.

Parameter Values

Index	Parameter	Description	Options
1	Echo Return Loss High	Maximum ERL required for echo canceller to converge on speech (value X 0.1 dB).	0-99 dB
2	Echo Return Loss Low	Minimum ERL required for echo canceller to converge on speech (value X 0.1 dB).	0-99 dB
3	Tone Disabler Type	Selection of protocol to enable tone disabler.	G.164, G.165
4	Non-Linear Processing	Selects type of post-canceller signal.	Center Clipper, Multiplying
5	NLP Threshold	Threshold below which non-linear processing is enabled (value X 0.1 dB).	0-99 dB
6	Noise Injection	Determines if noise will be injected when NLP is active.	Enable, Disable
7	Voice Template	Selection of template to use; normal voice levels or high voice levels.	USA—normal UK—high-level

Attributes

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

Related Commands

cnfchec, dspecparm

Example

Show integrated echo canceller (IEC) parameters for slot 13:

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 12:41 PST




IEC Slot 13 Parameters

1 IEC Echo Return Loss High (.1 dBs) [ 60] (D)

2 IEC Echo Return Loss Low (.1 dBs) [ 30] (D)

3 IEC Tone Disabler Type [ G.164]

4 IEC Non-Linear Processing [Center Clipper]

5 IEC Non-Linear Processing Threshold [ 18] (D)

6 IEC Noise Injection [ Enabled]

7 IEC Voice Template [ USA]





This Command: cnfecparm 13

cnffrcls (configure Frame Relay class)

Configures a system-wide Frame Relay connection class. Be aware of these factors:

•You should configure network-wide classes only when all nodes are reachable.

•Beware of conflicting values with existing, joined networks.

•Changing a class does not affect any existing connections. An altered Frame Relay class affects only connections that are added using the changed class.

Syntax

cnffrcls <class_num> [<BW params>] [<description>]

Parameters

Parameter	Description
<class_num>	Specifies network-wide Frame Relay connection class to be configured.
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 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
description	Any text string up to 25 characters terminated by a <RET>. This is used to provide the user with a descriptive identifier for the class.

Attributes

Privilege	Jobs	Log	Node	Lock
1-2	Yes	Yes	IGX	Yes

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

Related Commands

addcon, dspfrcls

Example

Configure Frame Relay class #1 to operate with ForeSight. The list of * parameters leaves those parameters unchanged, and "y" enables ForeSight. Because the utilization and description parameters have not been entered, any existing values for these parameters remain in effect.

cnffrcls 1 *

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

Frame Relay Connection Classes

# MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST

.6/9.6 9.6/9.6 65535/65535 128/128 10/10 65535/65535 9.6/9.6 y

% Util: 100/100 Description: "Default 9.6"

2 19.2/19.2 19.2/19.2 65535/65535 */* 10/10 65535/65535 19.2/19.2 n

% Util: 100/100 Description: "Default 19.2"

3 16/16 16/16 65535/65535 */* 10/10 65535/65535 16/16 n

% Util: 100/100 Description: "Default 16"

4 32/32 32/32 65535/65535 */* 10/10 65535/65535 32/32 n

% Util: 100/100 Description: "Default 32"

5 56/56 56/56 65535/65535 */* 10/10 65535/65535 56/56 n

% Util: 100/100 Description: "Default 56"

Last Command: cnffrcls 1 * * * * * * * y




Continue (y): y




_____________________________




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

Frame Relay Connection Classes

# MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR FST

6 64/64 64/64 65535/65535 */* 10/10 65535/65535 64/64 n

% Util: 100/100 Description: "Default 64"

7 128/128 128/128 65535/65535 */* 10/10 65535/65535 128/128 n

% Util: 100/100 Description: "Default 128"

8 192/192 192/192 65535/65535 */* 10/10 65535/65535 192/192 n

% Util: 100/100 Description: "Default 192"

9 256/256 256/256 65535/65535 */* 10/10 65535/65535 256/256 n

% Util: 100/100 Description: "Default 256"

10 512/512 512/512 65535/65535 */* 10/10 65535/65535 512/512 n

% Util: 100/100 Description: "Default 512"




Last Command: cnffrcls 1 * * * * * * * y




Next Command:

cnffrcon (configure Frame Relay connection)

Configures bandwidth parameters or enables ForeSight for an individual Frame Relay connection. Because you normally specify bandwidth parameters through the Frame Relay class or by the option of overriding bandwidth parameters through specific arguments for addcon, it is more common to use cnffrcon where you need to customize a single connection's bandwidth parameters.

Be sure the MIR you specify is appropriate. If the MIR is too high, bandwidth is wasted. If it is too low, the connection may drop data. The statistics reports are the best source of information to help you determine the appropriate MIR.

The PIR usually is set to the port speed. You can specify a lower PIR if other constraints on the data generation rate exist. If the PIR you specify is too low, frames are dropped. If it is too high, bandwidth may be wasted unless the network has ForeSight.

The Cmax, VC Q, and ECN Q values should be changed only by knowledgeable users and when tuning data is available to support the determination of appropriate values. These values affect system buffering resources, so any change from the defaults requires caution. Refer to the Cisco WAN Switching System Overview for more details on connection parameters.

If the connection type has ForeSight (FST = y), the result of the last test round-trip delay command (Test RTD) is displayed. Note that this is not the current RTD but the result of the last, user-specified test. High or low connection priority is displayed for both standard Frame Relay connections and ForeSight connections.

The node checks the bandwidth parameters to promote efficient use of network bandwidth. These messages reflect the checks on bandwidth usage:

•Error: Min cannot exceed peak

•Warning: Min exceeds this port's speed.

•Warning: Sum of mins exceeds port's speed.

•Warning: Peak exceeds this port's speed.

Warning messages are informational and do not indicate that the command is failing to execute. Error messages indicate the command is not executing.

When you specify the frp_bw parameters, enter all changes (or unchanged values indicated by an asterisk) on the line. You must specify either a change or a place-holder (*) up to at least the last changed value (after which place-holders are unnecessary). Decide on any changes before starting this command. The parameters section of this command description lists frp_bw parameters.

Syntax

cnffrcon <channel> [bandwidth_parameters]

Parameters

Parameter	Description
<channel>	Specifies the channel to configure connection parameters. The command configures connection information for one channel at a time. You cannot specify a set of channels. The channel has this format: slot.port.DLCI
[bandwidth_parameters]	Optionally specifies the bandwidth parameters in these format: MIR/MIR, CIR/CIR, VC_Q/VC_Q, PIR/PIR, Cmax/Cmax ECNQ_thresh/ECNQ_thresh, QIR/QIR, FST, %utl/%utl A slash indicates you can specify a value for each direction. FST is either ForeSight enable (y) or disable (n). An "*" is a placeholder for a parameter you do not change.

Attributes

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

Related Commands

addcon, dspcon

Example

Configure Frame Relay connection 14.3.4.

cnffrcon 14.3.4

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 12:49 PST




Conn: 14.3.4 igxr02 27.3.4 fr Status:OK

MIR CIR VC Q Depth PIR Cmax ECN QThresh QIR

64/64 64/64 65535/65535 64/64 100/100 65535/65535 64/64




Owner: LOCAL Restriction: NONE CoS: 0 FST: n % Util: 25/25

Pri: L Test-RTD: 0 msec

Path: igxr03 19.1--12.3igxr02

Pref: Not Configured






igxr03 UFM: OK igxr02 UFM: OK

Line 14.3 : OK Line 27.3 : OK






This Command: cnffrcon 14.3.4

cnffrcport (configure Frame Relay port)

Configures the port speed and percent of utilization on the concentrated link of a Port Concentrator Shelf (PCS). This is not a standard command. Primarily, you would use cnffrcport to adjust the rate on the concentrated link due to some unusual system configuration.

Because this command applies to the FRC interface (the concentrated link) rather than the user port for the CPE, the port number and the range of speeds is the same as that of the FRP or FRM card. Thus, the port numbers are 1-4 with rates varying from 56 Kbps through 2 Mbps. During port configuration, a prompt for each parameter appears. To keep the current value of the parameter, press the Return key without typing anything.

Syntax

cnffrcport <slot.port> <speed>< utilization>

Frame Relay

Parameter	Description
<slot.port>	Specifies the card slot and port number. Because the port number is that of the concentrated link rather than the user port number, the range is 1-4 (not 1-44).
<speed>	Specifies the port clock speed for a 2.0 Mbps FRP-2 or FRM-2. The display shows the configured speed as Configured Clock and the actual speed as Measured Rx Clock. The available speeds are: 1 port (selected speeds, 56-2048 Kbps) 2 ports (selected speeds, 56-1024 Kbps) 3 ports (selected speeds, 56-672 Kbps) 4 ports (selected speeds, 56-512 Kbps)
< utilization>	Specifies the percent of utilization of the concentrated link.

Attributes

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

Related Commands

upfrport, dnfrport, dspfrport, dspcd

Example

Reconfigure PCS port 6.1 to have a speed of 512 Kbps and a concentrated link utilization of 88 percent. Note that executing dspcd for this slot would show a port count of 44, which indicates that the card set supports a PCS. The Configured Clock of 512 Kbps by itself does not indicate a PCS because a standard FRP-2 or FRM-2 also supports this rate.

cnffrcport 6.1 512 88

minnow TN SuperUser IGX 8410 9.3 Apr. 13 2000 10:16 PST




Physical Port: 6.1 [INACTIVE]

Interface: FRI-X21 DCE Configured Clock: 512 Kbps

Clocking: Normal Measured Rx Clock: 0 Kbps

Min Flags / Frames 1

Port ID 1022

Port Queue Depth 65535 OAM Pkt Threshold 3 pkts

ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec

DE Threshold 100 % N391 Full Status Poll 6 cyl

Signaling Protocol None EFCI Mapping Enabled No

Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec

T392 Polling Verif Timer 15 IDE to DE Mapping Yes

N392 Error Threshold 3 Interface Control Template

N393 Monitored Events Count 4 Lead I

Communicate Priority No State ON

Upper/Lower RNR Thresh 75%/ 25% Concentrated Link Util 88%




Last Command: cnffrcport 6.1 512 88





Next Command:




cnffstparm (configure ForeSight node parameters)

Configures the Optimized Bandwidth Management (formerly called ForeSight) parameters for Frame Relay ports.

This command has an effect only if the Frame Relay Optimized Bandwidth Management option is enabled. The parameter values set by this command apply to all Frame Relay connections enabled with Optimized Bandwidth Management. These parameters must be configured on each node in the network that has Optimized Bandwidth Management connections. (The cnffrcon command enables Optimized Bandwidth Management on a connection.)

Syntax

cnffstparm

No line or port number need be entered.

Parameters

Number	Parameter	Description	Default
1	FRP Increase Rate	If free bandwidth is available, the rate at which FRP increases transmission (as a percentage of MIR).	10%
2	FRP Decrease Rate	If free bandwidth becomes unavailable, the rate at which FRP decreases transmission (as a percentage of current rate).	93%
3	FRP Fast Decrease Rate	If a cell is dropped or the TxQ is full, the rate at which FRP decreases transmission (as a percentage of current rate).	50%
4	RTD Measurement Time	The polling interval for measuring round-trip delay on each Frame Relay PVC.	5 sec.
5	Default RTD	The default RTD the connection uses before RTD is measured.	100 ms.
6	Minimum RTD	Min. value used for RTD in FR calculation regardless of measured RTD.	40 ms.
7	Maximum RTD	Max. value used for RTD in FR calculation regardless of measured RTD.	250 ms.
8	FECN for congested mins	When this percentage of packets received have the FECN bit set, a congested minutes field in the dspfrport command is indicated.	50%
9	QIR Time-out	Time before the allowable transmit rate is reset to QIR.	10 secs.
10	Max Test Delay Retries	Maximum number of delay test retries after a timeout.	2

Attributes

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

Related Commands

cnffrcon

Example

cnffstparm

sw66 TN SuperUser BPX 15 9.3 Apr. 13 2000 23:50 GMT

1 FST Increase Rate [ 10] (%)

2 FST Decrease Rate [ 93] (%)

3 FST Fast Decrease Rate [ 50] (%)

4 RTD Measurement Time [ 5] (secs)

5 Default RTD [ 100] (msecs)

6 Minimum RTD [ 40] (msecs)

7 Maximum RTD [ 250] (msecs)

8 FECN for congested mins [ 50] (%)

9 QIR Time-out [ 244] (secs)

10 Max TstDelay Retries [ 2] (dec)




Last Command: cnffstparm

Next Command:




cnffunc (configure system functions)

Enables or disables a specified node function.

Syntax

cnffunc <function_index> <e | d>

Each function has an index number. By entering the command, the index parameter, and the letter "e" or "d," the function is either enabled or disabled.

Function Index Parameters

Index	Function	Description	Default
1	Automatic CLN/TRK Loopback Test on Local/Remote Alarms	A remote-end loopback is automatically set up on a failed line or trunk. Used to check the integrity of the back card alarm circuitry.	enabled
2	FDP Loopback button	For an IGX node, enables loopback button on SDP or HDM card faceplate. (Disable it to prevent accidental operation by contact.)	enabled
3	User Command Logging	All commands entered by the user is entered in the system log when enabled. When disabled, system log does not become so large but there is no audit trail of operator commands kept.	enabled
4	Automatic Card Reset on Hardware Error	The controller card (BCC or NPM) issues a hardware reset to a card when firmware detects an error during normal operation. This allows the node to return a card to service after a firmware error.	enabled
5	TXR Model D Download	(Not used)	enabled
6	Card Error Record Wraparound	Allows the log entry for each card error to wrap for long entries. When disabled, only first ten failures are logged.	enabled
7	Card Test After Failure	Indicates card function self-tests and background test should continue to be executed after a card has been declared as failing these tests.	disabled
8	Download from Remote WAN Manager NMS	Allows a node to download software images from a WAN Manager not directly connected to the node.	disabled
9	Logging of connection events in local event log	All connection event messages are entered in the system log when enabled. When disabled, system log does not become so large but there is no audit trail of connection events kept.	disabled
10	Logging of connection events in WAN Manager event log	All connection event messages are entered in the WAN Manager event log when enabled. When disabled, WAN Manager event log does not become so large but there is no audit trail of connection events kept.	disabled
11	Force Download From a Specific IP address	Forces the node to only download software images from a WAN Manager with the specified IP address.	disabled
12	Logging of SVC connection events	All SVC connection event messages are entered in the local event log when enabled. When disabled, local event log does not become so large but there is no audit trail of SVC connection events kept.	disabled
13	CDP WinkStart Signaling	Toggles WinkStart signaling on the CDP.	disabled
14	Logging of Bus Diagnostic Events in local event log	All Bus Diagnostic event messages are entered in the local event log when enabled. When disabled, local event log does not become so large but there is no audit trail of Bus Diagnostic events kept.	enabled
15	Automatic Card Reset after Burnfw for CBI Cards	While the network is running Release 9.1, use the cnffunc command option 15 to disable the Automatic Card Reset after Burnfw for CBI cards option. (By default, this option is enabled.) You need to perform this step so that you can burn the UXM firmware revision on the flash and delay execution of the new firmware revision until the card is reset with the resetcd command. After the UXM at both ends of the trunk are burned with the new firmware revision, you can reset the UXM cards at the same time so that the new ATM Forum-Compliant protocol is invoked at both ends of the trunk at the same time. It is important that you perform this step, because a node potentially may be not be reached if this is an IMA trunk, and it is the only trunk connected to that remote node. Also note that if an IMA trunk is not used within the Release 9.1 network, then you do not need to perform this step. Then upgrade all UXM cards in the Release 9.1 network with UXM firmware model B.	Enabled/ Disabled [Default: Enabled]

Attributes

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

Upgrading from Release 9.1 to Release 9.2 When IMA Trunks Exist

When IMA trunks exist in a Release 9.1 network, and you are upgrading from Release 9.1 to 9.2, ensure that the following steps have been performed:

•While the network is running Release 9.1, use the cnffunc command option 15 to disable the Automatic Card Reset after Burnfw for CBI cards option. (Note that this option is enabled by default.) This step is required so that you can burn UXM firmware revision on the flash and delay execution with this new firmware revision, then later reset the card by using the resetcd command. After the UXM at both ends of the trunks is burned with the new firmware revision, you can reset the UXM cards at the same time so that the new ATM Forum-Compliant protocol is invoked at both ends at the same time. If this step is not followed, some nodes may not be reachable if this is an IMA trunk, and it is the only trunk connected to that remote node. Note that if an IMA trunk is not used within the 9.1 network, then you do not need to perform this step.

•Upgrade all UXM cards in the Release 9.1 network with UXM firmware model B.

You are now ready to upgrade the switch software from Release 9.1 to 9.2.

Example (IGX)

Enables automatic card testing after a card failure has been detected.

cnffunc 15 e

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

sw180 TN Cisco IGX 8420 9.3.2J Oct. 25 2000 12:20 GMT




Index Status Function




1 Enabled Automatic CLN/PLN Loopback Test on Local/Remote Alarms

2 Enabled FDP Loopback button

3 Enabled User Command Logging

4 Enabled Automatic Card Reset on Hardware Error

5 Enabled TXR Model D Download

6 Enabled Card Error Record Wraparound

7 Disabled Card Test After Failure

8 Disabled Download From Remote CWM

9 Disabled Logging of conn events in local event log

10 Disabled Logging of conn events in CWM event log

11 Disabled Logging SVC Connection Events

12 Disabled Force Download From a Specific IP address

13 Disabled CDP WinkStart Signaling




This Command: cnffunc




Continue?




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

sw180 TN Cisco IGX 8420 9.3.2J Oct. 25 2000 12:22 GMT




Index Status Function




14 Enabled Logging of Bus Diagnostic Events in local event log

15 Enabled Automatic Card Reset after Burnfw for CBI cards

16 Enabled Logging of router state events in CWM event log






Last Command: cnffunc 15 e

Example (BPX)

cnffunc 1 e

sw53 TN Cisco BPX 8620 9.3.2J Oct. 25 2000 12:18 GMT




Index Status Function




1 Enabled Automatic TRK Loopback Test on Local/Remote Alarms

2 Enabled User Command Logging

3 Disabled Automatic Card Reset on Hardware Error

4 Enabled Card Error Record Wraparound

5 Disabled Card Test After Failure

6 Disabled Download From Remote Cisco StrataView Plus

7 Disabled Logging of conn events in local event log

8 Disabled Logging of conn events in Cisco StrataView Plus event log

9 Disabled Force Download From a Specific IP address





Last Command: cnffunc 1 e

cnffwswinit (configure FW/SW download initiator IP address)

Specifies the IP address of the machine used to initiate a firmware or software download. With Release 9.3.30 and higher, the cnffwswinit command is also used to specify the IP address of the network server used to initiate the configuration save and restore operation using a TFTP Start file or SNMP interface.

This is a safety measure to prevent downloads from being started anywhere in the network. You must have access to a node, and use the cnffwswinit command to set the IP address before a download will be accepted from that address.

Syntax

cnffwswinit <IP address>

Parameters

Parameter	Description
<IP address>	Specifies the IP address of the network server that initiates a firmware/software download or a configuration save/restore operation.

Attributes

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

Related Commands

dsppwd, adduser, deluser, dspusers

Example

Configure the IP address of the network server that will initiate the firmware download to the network nodes.

cnffwswinit 172.29.52.17

cnfict (configure interface control template)

Sets the interface control template signals. The signals that can be set by using cnfict depend on the type of back card used and whether the hardware is configured for DCE or DTE. On an IGX node, the applicable front cards are the LDM, HDM, FRM, and CVM (for data). Each data channel has a default interface control template for its active, conditioned, and looped near and far states. Use the cnfict command is used to individually configure each interface control lead in each template.

When Y-cable redundancy is in effect, the control template configuration for the data channels terminating at the primary slot is also applied to the data channels of the secondary slot. Any configuration information for the secondary slot is ignored.

---

Note The cnfict command is not valid for V.11 and X.21 interfaces. For FRP V.35 and Port Concentrator V.35 and V.28 interfaces, only the active template is usable, and you can configure the leads to On or Off.

---

Syntax

cnfict <port> <template> <output> <source>

Parameters

Parameter	Description
port	Specifies the data channel or Frame Relay port whose interface control template is to be configured. Entered as <slot.port>. On an IGX node, the applicable cards are the LDM, HDM, FRM, and CVM.
template	Specifies which interface control template to configure for the channel and has the format <a | c | l | n | f>. Valid entries are listed below. The only valid template for a Frame Relay port, X.21 or V.35, is the ACTIVE template. Also, all the output leads have steady state values and do not follow local or remote inputs
	Entry	Template	Description
	a	Active	The active control template is in effect while the data channel is active (normal operation) i.e., when the connection is routed and not failed.
	Entry	Template	Description
	c	Conditioned	The conditioned control template is in effect when conditioning is applied to the data channel. The conditioned template is used when the network detects that it cannot maintain the connection because of card failures or lack of bandwidth (the connection failed).
	l	Looped	The looped template is in effect when the data channel is being looped back in either direction. The looped template is used when addloclp or addrmtlp has been used to loop the connection within the network.
	n	Near loopback	The near template is in effect when running a tstport n command or an addextlp n command on a port. The port is configured such that the external near modem is placed in a loopback.
	f	Far loopback	The far template is in effect when running a tstport f command or an addextlp f command on a port. The port is configured such that the external far-end modem is placed in a loopback.
output	Specifies the output lead. Refer to the Configurable Lead information in the command description for abbreviations. Configurable output leads vary with the type of data interface (EIA/TIA-232, V.35, X.21, or EIA/TIA -449).
source	Specifies how the lead is to be configured and has the format <on | off |local | remote> <input> [delay]. Valid source choices follow:
	Source Options
	on	The output lead is asserted.
	off	The output lead is inhibited.
	l	Local. Indicates that the output follows a local lead.
	r	Remote. Indicates that the output follows a remote lead.
	input	Specifies the name of the local or remote input lead that the output lead follows.
	delay	Specifies the time in milliseconds that separates the off to on lead transitions. Delay is valid only when the output lead is CTS and the input lead is local RTS. On to Off lead transitions are not subject to this delay.

Attributes

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

Related Commands

addextlp, dspict, tstport

Configurable Lead Names and Functions

Table 3-26 shows the configurable leads and the equivalence between EIA/TIA-232C, EIA/TIA-232D, EIA/TIA-449, V.35, and X.21 interfaces. The leads are configurable for each type of data interface supported by the IGX node. An IGX treats leads impartially for non-interleaved connections.

The entries under the IGX Name column indicate the abbreviations to use when specifying input or output leads on the command line. A node treats leads impartially for non-interleaved connections. Any signal received on an EIA pin at one end may be transmitted to any pin at the other end, up to the maximum of 12 EIA leads on any interface type. For interleaved EIA connections, refer to the Fast EIA column. The column shows which leads are carried in the interleaved bytes of the data packets. All remaining leads are carried in standard control lead packets.

Table 3-26 Configurable Lead Names and Functions 

Configurable Leads
Source	IGX Name	EIA/TIA- 232C	EIA/TIA- 232D	EIA/TIA- 449	V.35	X.21	Fast EIA	Function
DTE	RTS	CA	CA	RS	C		F4	Request to Send
DCE	CTS	CB	CB	CS	D		F4	Clear to Send
DCE	DSR	CC	CC	DM	E		F3	Data Set Ready
DCE	DCD	CF	CF	RR	F		F7	Data Carrier Detect (RLSD)
DCE	QM	QM	QM					Equalizer Mode
DTE	pin 11	11	11					Sometimes used for Data
DCE	SDCD	SCF	SCF					Secondary Data Carrier Detect
DCE	SCTS	SCB	SCB					Secondary Clear to Send
DTE	STxD	SBA	SBA				F5	Secondary Transmit Data
DTE	NS			NS			F7	New Sync
DCE	SRxD	SBB	SBB				F5	Secondary Receive Data
DCE	DCR	DCR						Divided Receiver Clock
DTE	RL		RL	RL			F6	Remote Loopback
DTE	SRTS	SCA	SCA					Secondary Request to Send
DTE	DTR	CD	CD	TR	H		F3	Data Terminal Ready
DCE	SQ	CG	CG	SQ				Signal Quality Detect
DCE	RI	CE	CE	IC	J**			Ring Indicator
DTE	SF	CH	CH	SF				Signal Rate Select (to DCE)
DCE	SI	CI	CI	SI				Signaling Rate Select. (to DTE)
DTE	BSY	BSY		IS			F1	Busy (In Service)
DCE	SB		TST	SB			F1	Test Indicator
DTE	LL			LL			F2	Local Loopback
DCE	TM			TM	K1		F6	Test Mode
DTE	SS			SS				Select Standby
DTE	C					C		Control
DCE	I					I		Indicator

1 Applicable to SDP cards only.

Note that pins 11 and 23 on an EIA/TIA-232 port are bidirectional, and their default direction is input. See the cnfcldir command for information on changing the direction of these pins. The cpyict command can be used to copy an interface control template from one data channel to another. You can then edit it by using the cnfict command. The dspbob command displays the state of leads at specified intervals.

Example

Configure the conditioned interface control template for channel 31.1 to SB on (DDS).

cnfict 31.1 c SB on

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

Data Channel: 31.1

Interface: DDS-4 OCU Config

Clocking: Looped

Interface Control Template for Connection while CONDITIONED

Lead Output Value Lead Output Value

SB ON RI OFF

DSR OFF CTS ON

DCD OFF




Last Command: cnfict 31.1 c sb on




Next Command:

Example

Configure the active interface control template for channel 25.1 to CTS-on (EIA/TIA-232). CTS-on means that when the port is active, the CTS lead is asserted.

cnfict 25.1 a cts on

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 17:36 MST

Data Channel: 25.1

Interface: EIA/TIA-232 DCE

Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

RI OFF DSR ON

CTS ON SRxD ON

DCR OFF DCD ON

SCTS ON SDCD ON

SQ ON




Last Command: cnfict 25.1 a cts on

Next Command:

Example

Configure the active interface control template for channel 5.1 to CTS on (V.35).

cnfict 5.1 active CTS on

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

Data Channel: 5.1

Interface: V35 DCE

Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

RI (J) OFF DSR (E) ON

CTS (D) ON TM (K) OFF

DCD (F) ON

Last Command: cnfict 5.1 a cts on




Next Command:

Example

Configure the active interface control template to have RTS-on. This means that when the port is active. the RTS lead is asserted.

cnfict 9.1 a rts on




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

Port: 9.1 [ACTIVE ]

Interface: FRI-V35 DTE Configured Clock: 256 Kbps

Clocking: Normal Measured Rx Clock: 0 Kbps

Port ID 7

Port Queue Depth 65535 OAM Pkt Threshold 3 pkts

ECN Queue Threshold 65535 T391 Link Intg Timer 6 sec

DE Threshold 100 % N391 Full Status Poll 10 cyl

Signaling Protocol None ForeSight (CLLM) No

Asynchronous Status No CLLM Status Tx Timer 0 msec

T392 Polling Verif Timer 15 Interface Control Template

N392 Error Threshold 3 Lead State

N393 Monitored Events Count 4 RTS ON

Communicate Priority No DTR ON

Upper/Lower RNR Thresh 75%/ 25%

Min Flags / Frames 1

Last Command: cnfict 9.1 a rts on




Next Command:

Example

Configure the near interface control template for 31.1, to DSR on (DDS trunk).

cnfict 31.1 n dsr on

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 17:38 MST

Data Channel: 31.1

Interface: DDS-4 OCU Config

Clocking: Looped

Interface Control Template for Connection while NEAR EXT LOOPED

Lead Output Value Lead Output Value

DSR ON CTS ON

DCD ON




Last Command: cnfict 31.1 near dsr on

Next Command:

cnflan (configure LAN)

Configures node communication parameters, to enable the node to communicate with a Cisco WAN Manager terminal over an Ethernet LAN using TCP/IP protocol. The parameters all contain address information about the Ethernet TCP/IP network that connects the Cisco WAN Manager station to an IGX or BPX node. The values must conform to those of the network. The network administrator can supply the parameters.

With Release 9.3.30, the cnflan command supports the first phase of the Automatic Routing Management to PNNI migration. When the XLMI protocol and the LMI Neighbor Discovery feature are enabled (using the advertise interface information parameter from the cnfport command) and the LAN IP is the selected Management IP address, the new LAN IP address is sent to the BXM card whenever the LAN IP address is changed. The cnfnodeparm command is used to select the Management IP address.

Syntax

cnflan <IP_Address> <IP_Subnet_Mask> <Maximum LAN Transmit Unit> <TCP Service Port>

Parameters

Parameter	Description
<IPAdd>	Specifies the Internet address of the node used in the TCP/IP protocol.
<IP subnet mask>	Specifies a 32-bit mask that contains information about the bit lengths of the subnet ID and host ID address fields. The format of this field uses 1s for the subnet ID field and 0s for the host ID address field as defined in the TCP/IP protocol. Default: 255 255 255.0. This mask denotes both subnet ID and host ID fields as 8-bit fields.
<Max. LAN Transmit Unit>	BPX nodes only: typical length is 1500 bytes.
<TCPServicePort>	Specifies the node's service point used by the transmission control protocol (TCP).
<GatewayIPAddr>	Specifies the Internet gateway address.

Attributes

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

Related Commands

upln, dnln, cnfln

Example

Configure node parameters to communicate with Cisco WAN manager.

cnflan

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 12:51 PST




Active IP Address: 172.29.10.238

IP Subnet Mask: 255.255.255.0

IP Service Port: 5120

Default Gateway IP Address: 172.29.10.1

Maximum LAN Transmit Unit: 1500

Ethernet Address: 00.C0.43.00.EC.BA




Type State

LAN READY

TCP UNAVAIL

UDP READY

Telnet READY

TFTP READY

TimeHdlr READY

SNMP READY




This Command: cnflan





Enter IP Address:

cnfleadmon (monitor LDM/HDM data port leads)

Monitors the IGX node's LDM/HDM ports for failures. You can set each of the twelve control lead types to be monitored by firmware on the LDM/HDM card. The monitor reports only lead state changes; no event is reported if the lead remains up from one poll to the next.

You can also set the interval value that determines how frequently the firmware will check the card's serial port leads. To turn off the feature, set the interval value to zero.

Syntax

cnfleadmon <index> <interval>

Parameters

Parameter	Description
<index>	Index number of the serial data port leads. Values 1 through 12. When you enter a different lead index number, an arrow moves to highlight the current monitoring data on that lead.
<interval>	The timer value in seconds. This determines how frequently the firmware on the LDM/HDM card will check the specified lead. Values: 5 through 255 seconds Default = 0 Enter 0 to turn off the feature.

Attributes

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

Related Commands

dsplogcd, dspcd, addjobtrig

Example

Tells the LDM/HDM card firmware to monitor data port lead number 4, every 5 seconds.

cnfleadmon 4 5

sw180 TN Cisco IGX 8420 9.3.r5 Dec. 20 2000 13:34 GMT




| LDM | HDM/SDI-RS232 | HDM/SDI-RS449 | HDM/SDI-V35 |

index | DCE : DTE | DCE : DTE | DCE : DTE | DCE : DTE |

1 : :TST/25 IS/28 :SB/36 :

2 : LL/18 :RI/22 LL/10 :IC/15 :RI/J

3 DTR/20 :DSR/6 DTR/20 :DSR/6 TR/12&30 :DM/11&29 DTR/H :DSR/E

===> 4 RTS/4 :CTS/5 RTS/4 :CTS/5 RS/7&25 :CS/9&27 RTS/C :CTS/D

5 : STxD/14 :SRxD/16 : :

6 : RL/21 : RL/14 :TM/18 :TM/K

7 :DCD/8 :DCD/8 NS/34 :RR/13&31 :DCD/F

8 : SRTS/19 :SCTS/13 : :

9 : :SDCD/12 : :

10 : SF/23 :SI/23 SF/16 :SI/2 :

11 : : :SQ/33 :

12 : ***/11 :QM/11 SS/32 : :

Sampling interval for HDM or LDM control lead shown above ...... 5 seconds




Last Command: cnfleadmon 4 5

cnfln (configure line)

Configures a line to be compatible with the device to which it connects. The cnfln command applies to voice, data, Frame Relay, ATM (including IMA lines). The cnfcln command is an alias for cnfln.

Because of the variety of line types and characteristics, separate parameters sections are included in this command description to define the parameters for specific line types. The system automatically presents the correct options on the command line for each line type. If a parameter is not applicable to a card type, the system displays the parameter in half-tone or the parameter value field with dashed lines.

---

Note In Release 9.3.20 and higher, the cnfln command is not used to configure the VC Shaping parameter on IGX ATM ports. You must use the cnfport command to configure VC Shaping. This change applies to all ATM ports in the IGX, that is, ports on the UXM and URM. Refer to the cnfport command for more information specific to ATM port configuration.

---

Syntax

cnfln <line> <parameters>

Syntax for IMA

cnfln <slot>.<primary link>

Parameters (IGX Voice, Data, Frame Relay Lines)

The following graphic illustrates the loop clock parameter, described in the parameter table that follows.

Figure 3-17 Loop Clock Illustration

Parameter	Description	Default
slot or slot.line	Specifies the line. If the back card has one line connector and cable, enter the slot number. If the card has more than one physical line, include a line number. If the card is a UVM, however, enter just the slot number.
loop clock	Enables the transmit and receive control leads to use the same clock. Format for the parameter is Y or N.	N
line framing	Configures T1 line framing to be D4 or ESF. Note that UFM-C series is ESF only. With Release 9.3.0, changing the line framing for BXM-T3 cards from PLCP to HEC no longer automatically changes the port's bandwidth to the new maximum. It merely raises the upper limit for the port's bandwidth. After changing the framing, you must use cnfport to increase the port's bandwidth.	D4 (ESF on UFM/FRM)
line coding	Configures T1 and E1 coding:
	T1:ZCS B8ZS AMI	ZCS B8ZS for FRM/UFM/UXM
	E1:HDB3 ZCS	HDB3
line CRC on	Enables CRC-4 detection for E1 lines. Use either Y or N.	N
E1 recv impedance	A parameter, in the range 1-7. 1 is 75 ohm impedance, unbalanced 2 is 75 ohm impedance, unbalanced 3 is 20 ohm impedance, balanced 4 is 0-133 ft impedance, ABAM cable 5 is 133-266 ft impedance, ABAM cable 6 is 266-399 ft impedance, ABAM cable 7 is 399-533 ft, ABAM cable	1
signaling	E1: Common channel signaling (CCS) or ABCD signaling bits with channel associated signaling (CAS)	CAS
	T1: Common channel signaling (CCS), ABCD or ABAB (with ESF line framing) or AB (with D4 line framing).	AB
encoding	A-law mu-law	depends on the back card
cable type/length	A parameter, in the range 1-8. 1 = voice circuit: 0-220 ft MAT cable, Frame Relay circuit: CSU Network Interface 2 = voice circuit: 220-440 ft MAT cable, Frame Relay circuit: 0-133 ft ABAM cable 3 = voice circuit: 440-655 ft MAT cable, Frame Relay circuit: 133-266 ft ABAM cable 4 = voice circuit: 0-133 ft ABAM cable, Frame Relay circuit: 266-399 ft ABAM cable 5 = voice circuit: 133-266 ft ABAM cable, Frame Relay circuit: 399-533 ft ABAM cable 6 = voice circuit: 266-399 ft ABAM cable, Frame Relay circuit: 533-655 ft ABAM cable 7 = voice circuit: 399-533 ft, Frame Relay circuit: not used 8 = voice circuit: 533-655 ft, Frame Relay circuit: not used	4
56 Kbps bit stuffing	most significant bit (msb) least significant bit (lsb)	msb
pct fast modem	Expected percentage of fast modem connections on the line. High speed modems preclude the use of ADPCM. Consequently, channel load requirements increase over that required for a voice channel. Range: 0-100	20

Parameters (BPX ATM Line)

Parameter	Description
line number	Specifies the ATM line to configure.
line options	Specifies the ATM line options:
	Parameter	Description	Options	Default
	Loop clock	Enable loop clocking.	Yes/No	No
	Idle Code	Hex data placed in unused payload of cells.	0 - FF (hex)	7F
	Cable Type/Length	Length and type of cable used for trunk.	1 = 0 - 225 2 = >225	1
	HCS Masking	Use a non-zero starting value for the HCS calculation to ensure a non-zero HCS. This is used to aid in the cell delineation algorithm.	Yes | No	Yes
	Payload Scramble	Whether or not to scramble (randomize) the cell payload data. Note: for E3, this must always be set to Yes.	Yes | No	No

Parameters (IGX ATM UXM Line)

Parameter	Description
slot.line	Specifies which line on which slot to configure.
line options	Specifies the ATM line options:
	Parameter	Description	Options	Default
	Loop clock	Enable loop clocking	Yes/No	No
	Idle Code	Hex data placed in unused payload of cells.	0 - FF (hex)	7F
	HCS Masking	Use a non-zero starting value for the HCS calculation to ensure a non-zero HCS. This is used to aid in the cell delineation algorithm.	Yes | No	Yes
	Payload Scramble	Whether or not to scramble (randomize) the cell payload data. Note: for E3, this must always be set to Yes.	Yes | No	Yes
	Frame Scramble	Whether or not to scramble (randomize) the frame data. Note: for E3, this must always be set to Yes.	Yes | No	No
	Cell Framing	Choose the cell framing format. Select either STS-3C (SONET) or STM-1 (SDH).	STS-3C | STM-1 PLCP HEC	STS-3C for OC-3 PLCP for T3 HEC for E3
	Line CRC	Enables E1 CRC-4 protection on E1 multiframed lines.	Yes | No	Yes

Parameters (IGX IMA UXM Lines)

Parameter	Description
slot.line	Specifies which line on which slot to configure.
Line DSO-Map	Line DSO mapping.
IMA Group Members	Specifies the line numbers of the individual links composing the IMA group.
Retained Links	The minimum number of links in the IMA group that must be active in order for the IMA line to operate. For an IMA line, you can add or delete links in an IMA group, or specify the number of retained links for an IMA configuration. If the number of links fails and falls below the retained link number specified, the IMA line fails. By default, the number of retained links is the same as the number of lines grouped together when the IMA group is created. For example, the command "upln 3.1-4" results in 4 lines in an IMA group with 4 retained links. If one link fails, the IMA line fails. Using the cnfln command, you can change the Retained Links parameter to a lesser number, for example, 3. Therefore, if one of the lines fails, the IMA line remains active.
IMA Protocol Option	Specify one of the following: Enable-to enable the IMA protocol on a line Disable-to disable the IMA protocol on a line Note: Changing the protocol option on an active line results in port failure. The user should always make sure that the IMA line is configured the same as the CPE.
IMA Max. Diff. Dly.	Specify a value. Range: 0-200 msec. Default: 200 msec. Defines the maximum time that one T1 or E1 link can be delayed with respect to another T1 or E1 link in the IMA line or trunk bundle. If the delay becomes too great, the proper reassembly of IMA frames will not occur, causing traffic errors. There is limited storage capacity in this buffer, therefore this parameter establishes the maximum differential delay which will be tolerated. Accurately specifying the delay results in optimum performance due to reduced buffer time; overspecifying the delay results in poor performance due to unnecessary cell waits in the buffer. Refer to Figure 3-18.
IMA Clock Mode:	The clock mode is Common Transmit Clock (CTC).
Loop Clock	Enables the transmit and receive control leads to use the same clock. Specify Yes or No. Default: No.
Line Coding	Configures T1 and E1 coding. Default values per line type are: E1-HDB3 T1-ZCS T1-(UFM T1), B8ZS J1-HDB3 E3-HDB3 T3-B8ZS OC3-N/A Possible line coding values for each line type are: E1-HDB3- not configurable T1-ZCS, B8ZS, AMI J1-HDB3- not configurable E3-HDB3-not configurable T3-B8ZS-not configurable OC3-N/A
Line CRC	Enables CRC-4 detection for E1 lines. Use either Y or N. This parameter defaults to "Y" when the line is upped.
Line recv impedance	For E1, a parameter in the range 1-7. 1 is 75 ohm impedance, unbalanced 2 is 75 ohm impedance, unbalanced 3 is 20 ohm impedance, balanced 4 is 0-133 ft impedance, ABAM cable 5 is 133-266 ft impedance, ABAM cable 6 is 266-399 ft impedance, ABAM cable 7 is 399-533 ft, ABAM cable
Idle Code	Hex data placed in unused payload of cells Range: 0 - FF (hex) Default: 7F
HCS Masking	Masking of cell header checksum to disable error checking. Specify either Yes or No. Default: Yes.
Payload Scramble	Whether or not to scramble (randomize) the cell payload data. Specify either Yes or No. Default: No Note: for E3, this must always be set to Yes.

Figure 3-18 illustrates the parameter IMA Max. Diff. Dly., described in the parameter table above.

Figure 3-18 IMA Max. Diff. Delay

Attributes

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

Related Commands

dspln, dsplncnf, dsptsmap, dnln, upport, dspport, dspports

Example

Configure voice line for a UVM.

cnfln 11.1 N D4 ZCS U-LAW AB 4 msb 20 N

poego TN Cisco IGX 8420 9.3.u4 May 10 2001 1231 PST




LN 11.1 Config T1/24 UVM slot11

Loop clock No

Line framing D4

Line coding ZCS

Line encoding u-LAW

Line T1 signalling AB

Line cable type ABAM

Line length 0-133 ft.

Line 56KBS Bit Pos msb

Line pct fast modem 20

Line cnfg External

Line cnf slot.line --

Line CAS-Switching --

Line SVC-Caching Off




Last Command cnfln 11.1 N D4 ZCS U-LAW AB 4 msb 20 N

Example

Configure a Frame Relay T1 line for the following option: no loop clock.

cnfln 15 N ESF 4

sw150 TN Cisco IGX 8420 9.3.2T Dec. 19 2000 22:50 PST




LN 15 Config T1/24 FRM slot:15

Loop clock: No

Line framing: ESF

Line coding: B8ZS

Line cable type: ABAM

Line length: 266-399 ft.






Last Command: cnfln 15 N ESF 4




Example

Configure ASI port 5.1.

cnfln 5.1

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 13:24 PST




LN 5.1 Config T3 [96000 cps] ASI-T3 slot: 5

Loop clock: No Idle code: 7F hex




Line framing: --

coding: --




recv impedance: --

E1 signaling: --

encoding: -- cable type:

T1 signaling: -- length: 0-225 ft.

HCS Masking: Yes

Payload Scramble: No

56KBS Bit Pos: -- Frame Scramble: --

pct fast modem: -- Cell Framing: --




Last Command: cnfln 5.1

Example

Configure the UXM-E1 IMA line.

cnfln 5.1 1-15,17-31 1-8 6 200 N 54 Y Y N

sw225 TN StrataCom IGX 8420 9.3.l3 Feb. 2 2000 10:14 GMT




LN 5.1(8) Config E1/238 UXM slot:10

Line DS-0 map: 1-15,17-31

IMA Group Member(s): 1-8

Retained links: 6

IMA Protocol Option: Enabled

IMA Max. Diff. Dly: 200 msec.

IMA Clock Mode: CTC

Loop clock: No

Line coding: HDB3

Line CRC: Yes

Line recv impedance: 75 ohm

Idle code: 54 hex

HCS Masking: Yes

Payload Scramble: Yes




This Command: cnfln 5.1 1-15,17-31 1-8 6 200 N 54 Y Y N

Example

Configure an E1/30 line on the CVM card in slot 12. Disable the CRC line check.

cnfln 12

sw219 TN Cisco IGX 8420 9.3.3c Mar. 16 2001 10:10 GMT




LN 12 Config E1/30 CVM slot:12

Loop clock: No

Line framing: On

Line coding: HDB3

Line CRC: No

Line recv impedance: 75 ohm + gnd

Line E1/J1 signal: CAS

Line encoding: A-LAW

Line 56KBS Bit Pos: msb

Line pct fast modem: 20

Line SVC-Caching: Off








Last Command: cnfln 12

Example (BPX)

cnfln 6.3

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 13:26 PST




LN 6.3 Config OC3 [353208cps] BXM slot: 6

Loop clock: 0 Idle code: 7F hex




Line framing: --

coding: --




recv impedance: --

E1 signaling: --

encoding: -- cable type: --

T1 signaling: -- length: --

HCS Masking: Yes

Payload Scramble: Yes

56KBS Bit Pos: -- Frame Scramble: Yes

pct fast modem: -- Cell Framing: STS-3C




Last Command: cnfln 6.3

Example (IGX)

Configure line 5.3 on a UXM in an IGX node.

cnfln 5.3 N 7F Y Y Y

sw180 TN Cisco IGX 8420 9.3.2a July 20 2000 15:35 GMT




LN 5.3 Config OC3 UXM slot:5

Loop clock: No

Line framing: STS-3C

Idle code: 7F hex

HCS Masking: Yes

Payload Scramble: Yes

Frame Scramble: Yes




Last Command:cnfln 5.3 N 7F Y Y Y

cnflnalm (configure line alarm)

Sets the trunk and line alarm values for failures that are statistical in nature. Statistical alarms are declared by the switch software when cards supporting these trunks or lines report too many errors. The switch declares an alarm if the detected error rate equals the cnflnalm parameter error rate for the period of time designated by the alarm time parameter. Error rates that exceed the specified error rate cause an alarm in a proportionately shorter period of time. An alarm is cleared when the error rate remains below the rate specified by error rate for a period of time designated by the clear time.

You can configure the thresholds for alarms caused by the collection of statistics but not for the alarms caused by a network failure. For example, you can configure the threshold for an alarm caused by a collection of bipolar errors, but you cannot configure an alarm caused by a card failure.

Six parameters exist for each failure type—three for minor alarms and three for major alarms. When configuring any item for a minor or major alarm, you must enter a value. You can enter a new value or enter the current value.

The tables show for each failure type, the alarm classes, the possible error rate options, and default alarm times and clear times.

Syntax

cnflnalm <fail_type> <alarm_class> <rate> <alarm_time> <clear_time>

Parameters

Parameter	Description
Failure type	Specifies the failure type. The list that follows gives the number for each failure type. (Items with an asterisk pertain to ATM only.) 1. Bpv—Bipolar violations 2. Fs—Frame slip 3. oof—Out of frame 4. Vpd—Voice packets dropped (TX) 5. Tspd—Time-stamped packets dropped (TX) 6. Ntspd—Non-time-stamped packets dropped 7. Pkterr—Packet error 8. Los—Loss of signal 9. Fer—Frame error 10. CRC—Cyclic Redundancy Check 11. Pkoof—Packet out of frame 12. Oom—Out of multiframe 13. Ais16—Alarm information signal—E1/E3 Only 14. Bdapd—Bursty data A packets dropped 15. Bdbpd—Bursty data B packets dropped 16. Badclk—Bad clock 17. Pccpd—PCC packets dropped 18. * Lcv—Line code violations 19. * Pcv1—P-bit parity code violations 20. * Pcvp—C-bit parity code violations 21. * Bcv—PLCP BIP-8 code violations 22. * Rxvpd—Receive voice packets dropped 23. * Rxtspd—Receive time stamped packets dropped 24. * Rxntspd—Receive non-time-stamped packets dropped 25. * Rxbdapd—Receive bursty data A packets dropped 26. * Rxbdbpd—Receive bursty data B packets dropped 27. * Rxhppd—Receive high-priority packets dropped
Failure type (continued)	28. * Atmhec—Cell header HEC errors 29. * Plcpoof—PLCP out of frame 30. * 30—Rxspdm: Receive spacer packets dropped
alarm class	Specifies the class of alarm to be configured for the specified alarm type. Valid alarm classes are: •Minor alarm •Major alarm
rates	Specifies the error rate at which the error must occur before an alarm is declared. The choices for error rates vary depending on the failure type and the alarm class. The choices are called out as Error Rate Options. The default error rates are indicated. With the exception of a Vpd (voice packets dropped) failure, you enter the number corresponding to the error rate. For Vpd (voice packets dropped) failures, you enter a percentage for the dropped packet rate in the range 1%-10%.
alarm time	Specifies the time that a condition must exceed a threshold before an alarm is declared. Range (minor alarms): 3-10 minutes Range (major alarms): 10-250 seconds
clear time	Specifies the time that the condition must exceed the selected threshold before the alarm is cleared. Range (minor alarms,): 3-10 minutes Range (major alarms): 10-250 seconds

Parameters (Error Rate Options)

Error Rate Options
Option	Alarm Class	Error Rate
A	1 - minor	1 - 1% 2 -.1% 3 -.01% 4 -.001% 5 -.0001%
	2 - major	1 - 1% 2 -.1% 3 -.01%
B	1 - minor	1 - 10E-4 2 - 10E-5 3 - 10E-6 4 - 10E-7 5 - 10E-8
	2 - major	1 - 10E-2 2 - 10E-3 3 - 10E-4 4 - 10E-5 5 - 10E-6

Parameters (Failure Type)

Failure Type	Alarm Class	Error Rate Options *	Alarm Time	Clear Time
1-Bpv	1-minor 2-major	Option B Default = 4 Default = 2	10 Minutes 10 Seconds	3 Minutes 10 Seconds
2-Fs	1-minor 2-major	Option A Default = 3 Default = 2	10 Minutes 10 Seconds	3 Minutes 10 Seconds
3-Oof	1-minor	1: 1% 2: 0.1% 3: 0.01% 4: 0.001% 5: 0.0001% (Def.)	10 Minutes	3 Minutes
	2-major	1: 1% 2: 0.1% 3: 0.01% (Def.) 4: 0.001%	10 Seconds	10 Seconds
4- Vpd	1-minor 2-major	Any dropped packet rate from 1% to 10%	5 Minutes 60 Seconds	3 Minutes 10 Seconds
5- Tspd	1-minor 2-major	Option A Default = 3 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
6-Ntspd	1-minor 2-major	Option A Default = 3 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
7- Pkterr	1-minor 2-major	Any error count from 1-10,000	10 Minutes 125 Seconds	3 Minutes 10 Seconds
8-Los	1-minor 2-major	Option A Default = 5 Default = 3	10 Minutes 10 Seconds	3 Minutes 10 Seconds
9- Fer	1-minor 2-major	Option A Default = 3 Default = 2	10 Minutes 200 Seconds	3 Minutes 10 Seconds
10- CRC	1-minor 2-major	Option A Default = 3 Default = 2	10 Minutes 200 Seconds	3 Minutes 10 Seconds
11-Pkoof	1-minor 2-major	Option A Default = 3 Default = 2	10 Minutes 200 Seconds	3 Minutes 10 Seconds
12- Oom	1-minor 2-major	Option A Default = 4 Default = 2	10 Minutes 10 Seconds	3 Minutes 10 Seconds
13- Ais16	1-minor 2-major	Option A Default = 5 Default = 3	10 Minutes 10 Seconds	3 Minutes 10 Seconds
14-Bdapd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
15- Bdbpd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
16-Badclk	1-minor 2-major	Option A Default = 2 Default = 1	10 Minutes 50 Seconds	3 Minutes 10 Seconds
17-Pccpd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
18-Lcv	1-minor 2-major	Option B Default = 3 Default = 1	10 Minutes 10 Seconds	3 Minutes 10 Seconds
19-Pcv1	1-minor 2-major	Option B Default = 3 Default = 1	10 Minutes 10 Seconds	3 Minutes 10 Seconds
20-Pcvp	1-minor 2-major	Option B Default = 3 Default = 1	10 Minutes 10 Seconds	3 Minutes 10 Seconds
21-Bcv	1-minor 2-major	Option B Default = 3 Default = 1	10 Minutes 10 Seconds	3 Minutes 10 Seconds
22-Rxvpd	1-minor 2-major	1-10% Default =1% 1-10% Default = 4%	5 Minutes 60 Seconds	3 Minutes 10 Seconds
23-Rxtspd	1-minor 2-major	Option A Default = 3 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
24-Rxbdapd	1-minor 2-major	Option A Default = 3 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
25-Rxbdbpd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
26-Rxntspd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
27-Rxhppd	1-minor 2-major	Option A Default = 4 Default = 2	5 Minutes 60 Seconds	3 Minutes 10 Seconds
28-Atmhec	1-minor 2-major	Option A Default = 4 Default = 2	10 Minute 120 Seconds	3 Minutes 10 Seconds
29-Plcpoof	1-minor 2-major	Option A Default = 4 Default = 2	10 Minutes 200 Seconds	3 Minutes 10 Seconds
30-Rxspdm	1-minor 2-major	Option A Default = 4 Default = 2	4 Minutes 10 Seconds	2 Minutes 5 Seconds

Attributes

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

Related Commands

clrnalm, clrtrkalm, dspclnerrs, dsplnalmcnf, dsptrkerrs

Example

Display current alarm types.

cnflnalm

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 13 2000 12:54 GMT




Line Alarm Types




1) Bpv 13) Tsdp 25) Rxbdbpd 37) Txbdacdscd

2) Fs 14) Ntsdp 26) Rxntspd 38) Txbdbcdscd

3) Oof 15) Pccpd 27) Rxhppd 39) Txcbrcdscd

4) Los 16) Bdapd 28) Atmhec 40) Txabrcdscd

5) Fer 17) Bdbpd 29) FSyncErr 41) Txvbrcdscd

6) CRC 18) Lcv 30) Rxspdm 42) TxGwFPdscd

7) Oom 19) Pcvl 31) CGWpktdscd 43) RxGwCLdscd

8) Ais16 20) Pcvp 32) CGWcelldscd 44) CGWfrmabrt

9) Pkoof 21) Bcv 33) Txntscdscd

10) Pkterr 22) Rxvpd 34) Txhpcdscd

11) Badclk 23) Rxtspd 35) Txvcdscd

12) Vpd 24) Rxbdapd 36) Txtscdscd




This Command: cnflnalm




Enter Type:

Example

Set Alarm Type 27, the Minor alarm time threshold, to 4 minutes. In this example, the cnflnalm command is followed by the alarm type (27), the alarm minor or major (1 for minor, 2 for major), the current rate (which is the default of 0.001%, (which is a 4), the new value for Alarm Time of 4 minutes (which is a "4" entry), and the existing Alarm Clear time of "3."

cnflnalm 27 1 4 4 3

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 13 2000 13:01 GMT




Line Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

25) Rxbdbpd .001% 5 min 3 min .1% 60 sec 10 sec

26) Rxntspd .01% 5 min 3 min .1% 60 sec 10 sec

27) Rxhppd .001% 4 min 3 min .1% 60 sec 10 sec

28) Atmhec .1% 10 min 3 min 1% 120 sec 10 sec

29) FSyncErr .01% 10 min 3 min .1% 200 sec 10 sec

30) Rxspdm .01% 4 min 2 min .001% 30 sec 5 sec

31) CGWpktds .01% 5 min 3 min 1% 60 sec 10 sec

32) CGWcelld .01% 5 min 3 min 1% 60 sec 10 sec




Last Command: cnflnalm 27 1 4 4 3

cnflnparm (configure ATM line card parameters)

Configures several parameters for ATM lines originating on the BPX or IGX nodes. The cnflnparm command is quite similar to the cnfln command.

This command configures the circuit line alarm integration times in milliseconds for Red and Yellow circuit line alarms. You should set them to correspond to the local carrier's alarm integration times. The cnflnparm range for each of these parameters is 60-3932100 ms. Carrier integration times are typically 800 ms-1500 ms for Red Alarm and 1500-3000 ms for Yellow Alarm.

You can also set the queue depth for the two queues associated with the ASI-0 card, the constant bit rate (CBR) queue and the Variable Bit Rate (VBR) queue. The queue depths may be increased to
16,000 bytes per queue.

Syntax

cnflnparm <slot.port> <option 1-4>

Parameters

Parameter	Description
<slot.port>	Specifies the line to configure.
<option >	Specifies the parameter to configure.

Attributes

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

Related Commands

upln, dnln, cnfln

Example

cnflnparm 5.1

sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 01:54 GMT

LN 5.1 Parameters

1 Red Alarm - In/Out [ 2500 / 15000] (Dec)

2 Yel Alarm - In/Out [ 2500 / 15000] (Dec)

This Command: cnflnparm 5.1

Which parameter do you wish to change: Which parameter do you wish to change:

cnflnpass (configure line pass-through)

Configures a pair of ports so that unprocessed channels go from a primary UVM to a secondary UVM. The cnflnpass command primarily applies to channels that use LDCELP or G.729 CACELP (although pass-through is possible on any type of connection except t-type or td-type). For a description of pass-through, refer to the UVM description in the Cisco IGX Reference.

To return ports to the non-passing configuration, execute cnflnpass with a 0 as the second argument.

Syntax

To configure pass-through, enter:
cnflnpass <primary line> <secondary line>

To remove pass-through from the primary and secondary lines, enter:
cnflnpass <primary line> 0

Parameters

Parameter	Description
<primary line>	Specifies the channels that the primary card supports. The format is slot.port.
<secondary line>	Specifies the channels that the secondary card supports. The format is slot.port.

Attributes

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

Related Commands

dsplncnf

Example

Configure line 13.1 to pass any unsupported channels to line 12.1.

cnflnpass 13.1 12.1

Upon successful execution of the command, the screen displays the slot and line of the passing channel on the right. The screen also shows other characteristics of the line.

sw176 TN IGX 8420 9.3 Apr. 13 2000 00:18 GMT

LN 13.1

E1/30 UVM slot: 13

Loop clock: No

Line framing: On cnfg: Passing

coding: HDB3 slot.line: 12.1

CRC: No

recv impedance: 75 ohm + gnd

E1/J1 signaling: CAS

encoding: A-LAW

T1 signaling: --

cable type: --

length: --

56KBS Bit Pos: msb

pct fast modem: 20

Last Command: cnflnpass 13.1 12.1

Next Command:





Note that, when you remove pass-through by entering a 0 for the secondary line, the screen also still line characteristics but with dashed lines in the column for the secondary (or passing) line.

cnflnsigparm (configure line signaling parameters)

Configures the line signaling parameters associated with a line for the CVM and UVM voice cards.

The CVM and UVM Heartbeat parameter (option 1) is the rate, in seconds, at which the card sends a signaling (ABCD bits) state update to the other end of the connection, even when there is no change in the state of the signaling bits. This is done because signaling packets are time-stamped data packets, and there is a small chance that a signaling packet might be discarded somewhere in the network. This recovery mechanism ensures that on-hook and off-hook notifications are not lost. Increasing this interval will probably have no impact as long as none of the normal signaling time-stamped data packets are being discarded in the network.

In Release 9.2 and higher, the CVM and UVM cards are supported. The CIP and CDP cards are not supported.

Syntax

cnflnsigparm <parameter number> <parameter value>

Parameters

Parameter	Description
<parameter number>	Specifies the number of the parameter to change.
<parameter value>	Specifies the new value to enter.

Parameter Values

No.	Parameter	Description	Range
1	Heartbeat	The current state of the signaling is periodically transmitted to the far end even if no signaling transitions are detected. This interval is determined by the value of the "heartbeat." The CVM & UVM Heartbeat parameter (option 1) is the rate, in seconds, at which the card sends a signaling (ABCD bits) state update to the other end of the connection, even when there is no change in the state of the signaling bits. This is done because signaling packets are time-stamped data packets, and there is a small chance that a signaling packet might be discarded somewhere in the network. This recovery mechanism ensures that on-hook and off-hook notifications are not lost. Increasing this interval will probably have no impact as long as none of the normal signaling TS data packets are being discarded in the network.	2-30 sec.
2	Signal Polling Rate	How often the control card polls the UVM/CVM for the status of the signaling. This parameter is used to update displays and statistics.	2-60 sec.
3	Default Inband Signal Delay	The transmit buffer timer value set after a valid signaling transition for in-band signaling arrives. After timeout, a signaling packet is sent.	30-96 msec.
4	Default Inband Playout Delay	The receive buffer timer that "ages" an incoming, time-stamped packet. When the age of the packet reaches the timestamp value, it moves on to depacketization and then to the user equipment. This parameter is used to even out the delay between signaling packets and voice packets.	0-200 msec.
5	Default Pulse Signal Delay	Same as number 3 but applied to pulse signaling.	30-96 msec.
6	Default Pulse Playout Delay	Same as number 4 but applied to pulse signaling.	100-200 msec.
7	CVM Number of Packet Slices		1
8	Packet Rate	Reserves trunk bandwidth for carrying UVM/CVM signaling.	0-1000 packets/sec.
9	Condition CCS Lines	If you specify yes for this parameter, the card applies signaling conditioning during an alarm to all channels on T1 circuit lines to notify PBX of a line failure.	YES or NO
10	Inband Min. Wink	Same as 6 for in-band signaling.	120-300 msec.
11	Pulse Min. Wink	For UVM/CVM connections only, this parameter controls both wink and inter-digit intervals for signaling that arrives over the NPM signaling channel from a far end UVM/CVM.	120-300 msec.
12	Condition T1 Lines?	If you specify yes for this parameter, the card applies signaling conditioning during an alarm to all channels on T1 circuit lines to notify PBX of a line failure.	YES or NO

Attributes

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

Related Commands

cnflnparm, cnflnstats, dsplnstatcnf, dsplnstathist, upln, dnln, cnfln

Example

Configure line signaling for CVM and UVM voice cards.

cnflnsigparm

cc2 LAN SuperUser IGX 32 9.3 Apr. 13 2000 11:16 PST




1 CVM & UVM Heartbeat [ 2] (sec)

2 CVM & UVM Sig. Polling Rate [ 10] (sec)

3 CVM & UVM Default Inband Sig Delay [ 96] (msec)

4 CVM & UVM Default Inband Playout Delay [ 200] (msec)

5 CVM & UVM Default Pulse Sig Delay [ 96] (msec)

6 CVM & UVM Default Pulse Playout Delay [ 200] (msec)

7 UVM Number of Packet Slices [ 1]

8 CVM & UVM Packet Rate [ 200] (pkt/sec)

9 CVM & UVM Condition T1 CCS Lines or T1 Lines? [ YES]

10 UVM Default Inband Min. Wink [ 140] (msec)

11 UVM Default Pulse Min. Wink [ 140] (msec)

12 CVM & UVM Condition T1 Lines? [ YES] (yes/no)






This Command: cnflnsigparm





Which parameter do you wish to change




cnflnstats (configure line statistics collection)

Configures statistics collection for a line. Primarily, cnflnstats is a debug tool (older alias: cnfclnstats). It lets you customize statistics collected on each line. Table 3-26 lists the statistics for FastPacket-based cards with T1 or E1 lines. For other available parameters, refer to the actual screens on a node. The examples show available statistics for a UXM port and an ASI-155 port.

Not all statistic types are available for all lines. Valid statistics appear in full brightness while unavailable types appear dimmed.

Bipolar violations are not generally accumulated on E1 trunk and circuit lines. They are accumulated only on T1 lines connected to Frame Relay ports.

Syntax

cnflnstats <line> <stat> <interval> <e | d> [<samples> <size> <peaks>]

Parameters

Parameter	Description
<line>	Specifies the port to configure.
<stat>	Specifies the type of statistic to enable/disable.
<interval>	Specifies the time interval of each sample. Range: 1-255 minutes
<e|d>	Enables/disables a statistic. Range: E to enable, D to disable.
[samples]	Specifies the number of samples to collect. Range: 1-255
[size]	Specifies the number of bytes per data sample. Range: 1, 2, or 4
[peaks]	Enables the collection of one minute peaks. Range: Y to enable, N to disable.

Statistics for FastPacket Cards

Statistic Index Number	Statistic	Line Type
1	Bipolar Violations	E1 and T1
2	Frame Slips	E1 and T1
3	Out of Frames	E1 and T1
4	Loss of Signal	E1 and T1
5	Frame Bit Errors	E1 only
6	CRC Errors	E1 only
7	Out of Multi-Frames	E1 only
8	All Ones in Timeslot 16	E1 only

Attributes

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

Related Commands

dsplnstatcnf, dsplnstathist

Example (FastPacket)

cc2 LAN SuperUser IGX 8430 9.3 Apr. 13 2000 11:20 PST




Line Statistic Types




1) Bipolar Violations

2) Frames Slips

3) Out of Frames

4) Losses of Signal

5) Frames Bit Errors

6) CRC Errors

7) Out of Multi-Frames

8) All Ones in Timeslot 16







Last Command: cnflnstats 15 6 255 e





Next Command:




Example (UXM Port)

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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 13 2000 13:35 GMT




Line Statistic Types




1) Bipolar Violations 37) Severely Err Secs - Path

3) Out of Frames 38) Severely Err Frame Secs

4) Losses of Signal 40) Unavail. Seconds

5) Frames Bit Errors 41) BIP-8 Code Violations

6) CRC Errors 42) Cell Framing Errored Seconds

29) Line Code Violations 43) Cell Framing Sev. Err Secs.

30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs

31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.

32) Line Parity Errors 62) Total Cells Tx to line

33) Errored Seconds - Line 69) Total Cells Rx from line

34) Severely Err Secs - Line 98) Frame Sync Errors

35) Path Parity Errors 141) FEBE Counts

36) Errored Secs - Path 143) Cell Framing FEBE Err Secs




This Command: cnflnstats 4.1





Continue? y




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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 13 2000 13:36 GMT




Line Statistic Types




144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.

151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.

152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.




This Command: cnflnstats 4.1





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 13 2000 13:36 GMT




Line Statistic Types




215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count

216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count

217) HCS Uncorrectable Error

218) HCS Correctable Error

219) INVMUX: line violations

220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.




This Command: cnflnstats 4.1





Statistic Type:

Example (BXM-155)

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

sw53 VT Cisco BPX 8620 9.3.m0 Dec. 13 2000 13:52 GMT




Line Statistic Types




1) Loss of Frames 39) Path FEBE

2) Loss of Signal 40) Section BIP8 Err. Secs.

19) HCS Errors 41) Line BIP24 Err. Secs.

28) YEL Transitions 42) Line FEBE Err. Secs.

30) Alarm Indication Signal 43) Path BIP8 Err. Secs.

31) Loss of Cell Delineation 44) Path FEBE Err. Secs.

32) Loss of Pointer 45) Section BIP8 Severely Err. Secs.

33) OC3 Path AIS 46) Section Sev. Err. Framing Secs.

34) OC3 Path YEL 47) Line BIP24 Severely Err. Secs.

35) Section BIP8 48) Line FEBE Severely Err. Secs.

36) Line BIP24 49) Path BIP8 Severely Err. Secs.

37) Line FEBE

38) Path BIP8




This Command: cnflnstats 11.1





Continue? y




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

sw53 VT Cisco BPX 8620 9.3.m0 Dec. 13 2000 13:53 GMT




Line Statistic Types




50) Path FEBE Severely Err. Secs.

51) Line Unavailable Secs.

52) Line Farend Unavailable Secs.

53) Path Unavailable Secs.

54) Path Farend Unavailable Secs.

55) HCS Correctable Error

56) HCS Correctable Error Err. Secs






This Command: cnflnstats 11.1





Statistic Type:




The table below provides BXM object names and some line statistics descriptions for the BXM card. Note that the object name given is, in most cases, the same as the screen field name when the cnflnstats screen is displayed.

---

Note Where interface type is not specified it is implied to be of generic nature, and is good for all BXM interfaces (T3, E3, OC-3, OC-12).

---

Line Statistics Descriptions (BXM Card)

Object ID	Object Name	Range	Description
01	Message Tag	Byte 0-3: Tag ID Byte 4-7: IP Address	Identifier and source IP address sent with CommBus message. Both will be copied into the response, if any is to be sent.
02	Line Number	1 - 12	Identifies the target line number. If multiple line numbers are sent during the operation, then each line number object terminates the configuration for the string of objects for the previous line number.
03	Statistical Subset	Byte 0: Subset # 0: All stats 1-4: Subset # Byte 1-n: List of Stat Objects in subset	The set operator configures the subset template. The get operator uses the subset number to build a response. It ignores the "byte 1-n" string.
04	Statistics Auto-Reset Option	0: Disabled 1: Enabled	Statistics will be automatically reset after sent to the BCC in an Event Message if the Auto-Reset option is enabled. After the instance of an enable or disable command, the condition will persist until another Auto-Reset command is encountered. Note reset is on a line basis.
05	Total Cells Transmitted	0 - 232-1	Total cells transmitted at the physical layer interface.
06	Total Cells Received	0 - 232-1	Total cells received at the physical layer interface.
07	RESERVED
08	LOS	0 - 232-1	Number of instances of LOS.
09	LOF	0 - 232-1	Number of instances of LOF.
0A	Line AIS	0 - 232-1	Number of instances of AIS.
0B	Line RDI (YEL)	0 - 232-1	Number of instances of Yellow Alarm detection.
0C	T3/E3 LCV	0 - 232-1	T3/E3 Line Code Violation Count.
0D	T3 PCV	0 - 232-1	T3 P-Bit Code Violations (Line) Count.
0E	T3 CCV	0 - 232-1	T3 C-Bit Code Violations (Path) Count.
0F	T3 FEBE	0 - 232-1	Far End Block Error.
10	T3/E3 FERR	0 - 232-1	Framing Errors Count.
11	T3/E3 LES	0 - 232-1	Line Errored Seconds Count. Incremented for each second there was at least one LCV.
12	T3 PES	0 - 232-1	T3 P-bit Errored Seconds Count. Incremented for each second there was at least one PES.
13	T3 CES	0 - 232-1	T3 C-bit Errored Seconds Count. Incremented for each second there was at least one CES.
14	T3/E3 LSES	0 - 232-1	Line Severely Errored Seconds Count. Incremented for each second there were 44 or more LCVs.
15	T3 PSES	0 - 232-1	T3 P-bit Severely Errored Seconds Count. Incremented for each second there were 44 or more P-bit Errors.
16	T3 CSES	0 - 232-1	T3 C-bit Severely Errored Seconds Count. Incremented for each second there were 44 or more C-bit Errors.
17	T3/E3 SEFS	0 - 232-1	T3/E3 Severely Errored Framing Seconds Count incremented for each second there was one or more Severely Errored Framing Errors (OOF).
18	T3/E3 UAS	0 - 232-1	Unavailable Seconds. Count starts from the onset of LOS, LOF, or AIS.
19	T3 PLCP LOF	0 - 232-1	PLCP Loss of Frame. Number of times Loss of Frame was detected by the PLCP.
1A	T3 PLCP YEL	0 - 232-1	PLCP Yellow Alarm count.
1B	T3/E3 PLCP BIP-8	0 - 232-1	PLCP/G.832 BIP-8 Errors. Incremented each BIP-8 Error was detected by PLCP.
1C	T3/E3 PLCP FEBE	0 - 232-1	T3/E3 PLCP/G.832 Far End Block Errors.
1D	T3 PLCP FOE	0 - 232-1	T3 PLCP Framing Octet Errors
1E	T3/E3 PLCP BIP-8 ES	0 - 232-1	T3/E3 PLCP/G.832 BIP-8 Errored Seconds. Incremented each second at least one PLCP BIP-8 Error was detected.
1F	T3/E3 PLCP FEBE ES	0 - 232-1	T3/E3 PLCP/G.832 FEBE Errored Seconds. Incremented each second at least one PLCP FEBE was detected.
20	T3/E3 PLCP BIP-8 SES	0 - 232-1	T3/E3 PLCP/G.832 BIP-8 Severely Errored Seconds. Incremented each second there were at least 5 BIP-8 Errors.
21	T3/E3 PLCP FEBE SES	0 - 232-1	T3/E3 PLCP/G.832 FEBE Severely Errored Seconds. Incremented each second there were at least 5 FEBE Errors.
22	T3 PLCP SEFS	0 - 232-1	T3 Severely Errored Framing Seconds.Incremented each second there was at least one SEF event. (PLCP OOF).
23	T3 PLCP UAS	0 - 232-1	T3 PLCP Unavailable Seconds. Count starts at the onset of LOS, LOF, AIS, or PLCP LOF.
24	RESERVED
25	HCS uncorrectable errors	0 - 232-1	Number of instances of Loss of Cell Delineation.
26	RESERVED
27	LOC	0 - 232-1	Number of instances of Loss of Cell Delineation.
28	OC-3 LOP	0 - 232-1	Number of instances of Loss of Pointer.
29	OC-3 Path AIS	0 - 232-1	Number of instances of Path AIS.
2A	OC-3 Path RDI (YEL)	0 - 232-1	Number of instances of Path Yellow.
2B	OC-3 Section BIP-8 Errors	0 - 232-1	Number of instances of Section BIP-8 Errors.
2C	OC-3 Line BIP-24	0 - 232-1	Number of instances of Line BIP-24 Errors.
2D	OC-3 Line FEBE	0 - 232-1	Number of instances of Line Far-End Blocking Errors.
2E	OC-3 Path BIP-8	0 - 232-1	Number of instances of Path BIP-8 Errors.
2F	OC-3 Path FEBE	0 - 232-1	Number of instances of Path Far-End Blocking Errors.
30	OC-3 Section BIP-8 ES	0 - 232-1	Number of seconds that had at least one instance of Section BIP-8 Errors.
31	OC-3 Line BIP-24 ES	0 - 232-1	Number of seconds that had at least one instance of Line BIP-24 Errors.
32	OC-3 Line FEBE ES	0 - 232-1	Number of seconds that had at least one instance of Line Far-End Blocking Errors.
33	OC-3 Path BIP-8 ES	0 - 232-1	Number of seconds that had at least one instance of Path BIP-8 Errors.
34	OC-3 Path FEBE ES	0 - 232-1	Number of seconds that had at least one instance of Path Far-End Blocking Errors.
35	OC-3 Section BIP-8 SES	0 - 232-1	Number of seconds that had at least 2500/8800 (OC-3/OC-12) instances of Section BIP-8 Errors.
36	OC-3 Section SEFS	0 - 232-1	Number of seconds that had at least 2500/8800 (OC-3/OC-12) instances of OOF.
37	OC-3 Line BIP-24 SES	0 - 232-1	Number of seconds that had at least 2500/10000 (OC-3/OC-12) instances of Line BIP-24 Errors.
38	OC-3 Line FEBE SES	0 - 232-1	Number of seconds that had at least 2500/10000 (OC-3/OC-12) instances of Line Far-End Blocking Errors.
39	OC-3 Path BIP-8 SES	0 - 232-1	Number of seconds that had at least 2400 instances of Path BIP-8 Errors.
3A	OC-3 Path FEBE SES	0 - 232-1	Number of seconds that had at least 2400 instances of Path Far-End Blocking Errors.
3B	OC-3 Line UAS	0 - 232-1	Number of seconds that the line was unavailable, in LOS, LOF, AIS, or after the occurrence of 10 contiguous Line SESs.
3C	OC-3 Line Far End UAS	0 - 232-1	Number of seconds that the line experienced at least 10 contiguous Line FEBE SESs.
3D	OC-3 Path UAS	0 - 232-1	Number of seconds that the line was unavailable, in LOP, Path AIS, or after the occurrence of 10 contiguous Path SESs.
3E	OC-3 Path Far End UAS	0 - 232-1	Number of seconds that the line experienced at least 10 contiguous Path FEBE SESs.
3F	HCS correctable errors	0 - 232-1	Number of instances of Loss of Cell Delineation.
40 -41	RESERVED

cnfmode (configure mode)

Selects a mode of the card for a UFM-U back card. The mode of a card is combination of maximum port speeds and for specific port numbers. Table 3-27 lists the maximum port speeds and active ports for each mode. The cnfmode command lets you select 1 of 27 modes for either a UFI-12V.35 back card or a UFI-12X.21 back card. For a UFI-4HSSI back card, three modes are available.

To specify the actual speed of an individual port, use the command cnfport. The IGX documentation describes the application of the modes and the sequence of execution of these commands.

---

Note The cnfmode and cnfufmumode commands are the same command.

---

Syntax

cnfmode <port> <mode>

Parameters

Parameter	Description
slot	Specifies the slot of the UFM-U card.
mode	Specifies the mode of the UFM-U card set. The range for V.35 and X.21 ports is 1-27. The range for HSSI ports is 1-3. You may have to delete connections and down one or more ports before you execute cnfmode. To determine if you must delete connection or for a detailed description of the modes of a UFM-U, see the Cisco IGX 8400 Series Reference.

Attributes

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

Related Commands

cnfport, dspmode, dspmodes

Example

Configure the UFM-U card set in slot 13 to have mode 4. Note that the display shows which ports are active for each mode number but does not show the current mode of the UFM-U. To see the current mode of the UFM-U, use dspmode.

cnfmode 13 4

w180 TN SuperUser IGX 16 9.3 Apr. 13 2000 01:25 GMT

UFMU MODES AND PORT AVAILABILITY BITMAP

Mode[ 1]:111111111111 Mode[ 2]:101010101010 Mode[ 3]:100010001000

Mode[ 4]:101011111111 Mode[ 5]:100011111111 Mode[ 6]:101010101111

Mode[ 7]:100010101111 Mode[ 8]:100010001111 Mode[ 9]:100010101010

Mode[10]:100010001010 Mode[11]:111110101111 Mode[12]:111111111010

Mode[13]:111110001111 Mode[14]:111111111000 Mode[15]:101011111010

Mode[16]:111110101010 Mode[17]:101010001111 Mode[18]:101011111000

Mode[19]:111110101000 Mode[20]:111110001010 Mode[21]:100011111010

Mode[22]:100011111000 Mode[23]:111110001000 Mode[24]:101010001010

Mode[25]:101010101000 Mode[26]:100010101000 Mode[27]:101010001000

This Command: cnfmode 13

Enter The New UFMU Mode [1]: 4





Table 3-27 Card Modes for Unchannelized Back Cards 

	V.35 and X.21 Ports			HSSI Ports
	Group A	Group B	Group C	A	B
Mode	1 2 3 4	5 6 7 8	9 10 11 12	1 2	3 4
1	3 3 3 3	3 3 3 3	3 3 3 3	8 8	8 8
2	8 - 8 -	8 - 8 -	8 - 8 -	16 -	16 -
3	10 - - -	10 - - -	10 - - -	16 -	- -
4	8 - 8 -	3 3 3 3	3 3 3 3
5	10 - - -	3 3 3 3	3 3 3 3
6	8 - 8 -	8 - 8 -	3 3 3 3
7	10 - - -	8 - 8 -	3 3 3 3
8	10 - - -	10 - - -	3 3 3 3
9	10 - - -	8 - 8 -	8 - 8 -
10	10 - - -	10 - - -	8 - 8 -
11	3 3 3 3	8 - 8 -	3 3 3 3
12	3 3 3 3	3 3 3 3	8 - 8 -
13	3 3 3 3	10 - - -	3 3 3 3
14	3 3 3 3	3 3 3 3	10 - - -
15	8 - 8 -	3 3 3 3	8 - 8 -
16	3 3 3 3	8 - 8 -	8 - 8 -
17	8 - 8 -	10 - - -	3 3 3 3
18	8 - 8 -	3 3 3 3	10 - - -
19	3 3 3 3	8 - 8 -	10 - - -
20	3 3 3 3	10 - - -	8 - 8 -
21	10 - - -	3 3 3 3	8 - 8 -
22	10 - - -	3 3 3 3	10 - - -
23	3 3 3 3	10 - - -	10 - - -
24	8 - 8 -	10 - - -	8 - 8 -
25	8 - 8 -	8 - 8 -	10 - - -
26	10 - - -	8 - 8 -	10 - - -
27	8 - 8 -	10 - - -	10 - - -

cnfmxbutil (configure muxbus utilization)

Configures the Muxbus or cell bus utilization factor for each FRP or FRM, respectively.

Use the cnfmxbutil command to configure the Muxbus or cell bus utilization factor for each FRP or FRM in the node on a slot-by-slot basis. (System software automatically allocates a certain amount of bandwidth for each FRP or FRM in a node. Since the maximum data rate for an FRP or FRM is 2 Mbps, this bandwidth is also the maximum amount of the bus reserved for an FRP or FRM.)

In many applications, each of the four FRP or FRM ports is configured for a large number of 56 or
64 Kbps connections. System software totals the bandwidth required for all the connections, multiplies the total by 121% to reserve extra bandwidth for overhead, then subtracts this amount from the total available bus bandwidth.

However, statistically full utilization is not often required on ports with a large number of connections, so the reserved bus bandwidth may be further reduced. In a node with a T3 or E3 ATM trunk card, much of the bus bandwidth may be assigned to the ATM trunk, so you should exercise caution when allocating the remaining bus bandwidth.

Syntax

cnfmxbutil <slot number> <percentage>

Parameters

Parameter	Description
<slot number>	Specifies the slot number of the associated FRP card.
<percentage>	Specifies the percent of Muxbus or cell bus bandwidth to allocate.

Attributes

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

Example

Configure Muxbus Utilization. The screen displays "N/A" for a slot where no FRP or FRM exists. Once the slot is selected, the system displays the message "Enter Utilization Factor." The range is 1-250%. The default is 121%. The extra 21% for the default is for the overhead for encapsulating the Frame Relay frame into the FastPackets or ATM cells.

cnfmxbutil

gamma Cisco WAN Manager SuperUser IGX 8420 Rev: 9.3 Apr. 13 2000 14:27 PDT




Slot 1: N/A Slot 9: N/A Slot 17: 121% Slot 25: N/A

Slot 2: N/A Slot 10: N/A Slot 18: 121% Slot 26: N/A

Slot 3: N/A Slot 11: N/A Slot 19: N/A Slot 27: N/A

Slot 4: N/A Slot 12: N/A Slot 20: N/A Slot 28: N/A

Slot 5: N/A Slot 13: N/A Slot 21: N/A Slot 29: N/A

Slot 6: N/A Slot 14: N/A Slot 22: N/A Slot 30: N/A

Slot 7: N/A Slot 15: N/A Slot 23: N/A Slot 31: N/A

Slot 8: N/A Slot 16: N/A Slot 24: N/A Slot 32: N/A





This Command: cnfmxbutil




Enter Slot:

cnfname (configure node name)

Specifies the name by which a node is known within the network. It may be changed at any time. The new node name is automatically distributed to the other nodes in the network.

Node names are case sensitive. For example, an upper-case "A" is not considered to be the same as a lower-case "a". Duplicate names are not allowed in the same network.

Node names may be configured from within a job sequence. If the node name is changed and the corresponding name in the job is not changed, the job will not function properly.

In these situations, the cnfname command cannot be executed:

•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 channel connection in the network with the addcon or delcon commands.

•There is an unreachable node in the network.

•The name chosen is already being used for another node in the network.

Syntax

cnfname <nodename>

Attributes

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

Related Commands

cnfterm, cnfprt, and window

Example

The name changes to "alpha." The network topology screen displays indicating the new name. See the dspnw description for more information on the network topology screen.

cnfname alpha




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

NodeName Alarm Packet Line Packet Line Packet Line

alpha 10- 7/beta 14- 13/beta

beta MAJOR 7- 10/alpha 9- 10/gamma 13- 14/alpha

15- 15/gamma 20- 11/gamma

gamma MAJOR 10- 9/beta 11- 20/beta 15- 15/beta





Last Command: cnfname alpha





Next Command:

cnfnodeparm (configure node parameter)

Sets a variety of general parameters for a node in the network.

The defaults for the network parameters are selected by Cisco engineering to operate under normal conditions. With few exceptions, you should change them only with the guidance of the Cisco TAC.

With the first 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 topology information between the adjacent BXM and AXSM over the AR-PNNI link. With Release 9.3.30, use the cnfnodeparm BPX parameter option 56 to configure the XLMI Management IP address as LAN IP or Network IP address. Whenever the choice of Management IP address is changed, the new Management IP address is sent to the BXM.

With Release 9.3.30, use the cnflan and cnfnwip commands to configure IP addresses. Use the cnfport command to enable XLMI protocol and the LMI Neighbor Discovery feature (using the advertise interface information parameter). Use the dspnebdisc command to display the AXSM's neighbor information discovered by the BPX via the LMI Neighbor Discovery procedure.

Syntax

cnfnodeparm

Attributes

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

Parameters (BPX)

Index	Parameter	Description	Default
1	Update Initial Delay (sec.)	This delay, multiplied times the number of nodes in the network, is the delay before conditional updates are transmitted to the network after a BCC switchover.	5000 seconds
2	Update Per-Node Delay (ms.)	Delay between transmission of conditional updates to nodes.	30000 msecs
3	Comm. Break Test Delay (ms.)	Interval between tests for communication breaks on any node.	3000 msecs
4	Comm. Break Test Offset	Factor between number of communication test failures and successful tests to declare a node in communication break condition.	10 (D)
5	Network Time-out Period	The time a node waits for a response to a communication test transmission before it declares a failure. Four failures allowed.	1700 (D)
6	Network Inter-p Period	The time a node waits for a response to a communication test transmission on inter-domain connections before it declares a failure. The maximum number of failures is four.	4000 (D)
7	NW Sliding Window Size	Controls the number of BCC messages that can be transmitted simultaneously. Defines number of "no acknowledgments outstanding" on a controller before NACKS declared.	1 (D)
8	Num. Normal Time-outs	Number of normal network retransmissions allowed before issuing a communication break condition (for intra-domain connections).	7 (D)
9	Num. Inter-p Time-outs	Number of normal network retransmissions allowed before issuing a communication break condition (for inter-domain connections).	3 (D)
10	Num. Satellite Time-outs	Number of satellite network retransmissions allowed before issuing a communication break.	6 (D)
11	Number of Blind Time-outs	Maximum number of communication fail time-outs and retransmissions performed when using the blind channel. "Blind" refers to the message being sent across the trunk without knowing what node is on the other end of the trunk. The Comm Fail test uses this blind channel.	4 (D)
12	Number of CB Msg Time-outs	Number of communication break time-outs and retransmissions before declaring a communication break (CB) condition. One successful acknowledgment clears CB.	2 (D)
13	Comm. Fail Interval (ms.)	Minimum time allocated for communication fail testing of all trunks terminating on the current node.	10,000 (D)
14	Comm. Fail Multiplier	Number of Comm. Fail Intervals to skip for good lines.	3 (D)
15	CC Redundancy Configured	Yes indicates a redundant controller card is required to prevent an alarm.	Y
16	Stats Memory (x 100 KB)	The amount of controller memory to allocate to statistics collection.	132 (D)
17	Standby Update Timer	Determines how often to send update messages to a standby controller.	10 (D)
18	Stby Updts Per Pass	Number of messages that can be sent to standby card for each update interval.	50 (D)
19	Gateway ID Timer	An inter-domain rerouting timer. How often to look for junction nodes for new route.	30 (D)
20	GLCON Alloc Timer	Another inter-domain rerouting timer controlling the gateway LCON function.	30 (D)
21	Comm Fail Delay	Number of seconds before starting to detect communication failures after a controller switchover.	60 (D)
22	Nw. Hdlr Timer (msec)	Network handler timer determines how long to wait to send messages to or receive messages from a remote node.	50 (D)
23	SAR CC Transmit Rate	Transmit data rate for BCC traffic to standby BCC (Kbps).	560 (D)
24	SAR High Transmit Rate	Transmit data rate for BCC traffic to other BCC nodes (Kbps).	280 (D)
25	SAR Low Transmit Rate	Transmit data rate for BCC traffic to ICC nodes (Kbps).	56 (D)
26	SAR VRAM Cngestn Limit	The threshold for BCC traffic receive queue congestion that causes cell discards.	7680 (D)
27	SAR VRAM Cell Discard	BCC traffic receive queue discard amount in cells.	256 (D)
28	ASM Card Cnfged	Yes indicates an Alarm/Status Monitor card is required or an alarm will be generated.	Y
29	TFTP Grant Delay (sec)	The number of seconds the node waits before resending a TFTP request after a TFTP error has occurred. This field is display-only; you set the value in Cisco WAN Manager.	1
30	TFTP ACK Timeout (sec)	The number of seconds the node waits for an acknowledgment of a TFTP request before it declares the request as timed out. This field is display-only; you set the value in Cisco WAN Manager.	10
31	TFTP Write Retries	The number of times the node retries a TFTP operation (not just writes) after a failed attempt. This field is display-only; you set the value in Cisco WAN Manager.	3
32	SNMP Event logging	Enables maintenance logging of global SNMP messages. These SNMP events are not errors but any GET, SET, and so on. Output goes to a printer connected to the node's auxiliary port or a terminal server (accessible via Telnet). Without a connected output device, the parameter is meaningless.	y=yes
33	Job Lock Timeout	Range: 1-1000 seconds Default: 0 (disables this parameter)	60
34	Max Via LCONs	The maximum number of "via" connections a via node can support. The default is the maximum for the node and should remain the default under normal operating conditions.	50000
35	Max Blind Segment Size	The maximum size of each segment of a blind message. (The full message may be longer than the segment, especially in a large network.) A blind message is a message the local node sends to the far end node when you execute addtrk. If the trunk has many errors, smaller message segments increase the possibility of a successful addtrk. Under normal conditions, this parameter should remain the default.	3570
36	Max XmtMemBlks Per NIB	Maximum number of memory blocks available for messages that are awaiting transmission. Under normal conditions, this parameter should remain the default.	3000
37	Max Mem on Stby Q (%)	Maximum number of update messages that can reside in queues awaiting transmission to the standby processor. This percentage is used to determine when to flush the standby message queue when the percentage is reached. Only rare circumstances could provide a reason to change this parameter, so do not change it without first consulting the TAC.	33 (D)
38	Stat Config Proc Cnt	Stat Config Proc Cnt is the number of statistics that will be enabled before pausing and allowing other processes to run. The default value of 1000 specifies that 1000 statistics should be enabled. But the count is checked only once for every object, so if the number of objects exceeds the count there will be one statistic enabled for each object. For example, if there are 1000 connections and the default count is set, one statistic will be enabled for each connection before pausing. If there are 2000 connections, one statistic will be enabled for each connection, then the number of statistics enabled (2000) will be compared to the count (1000). Since the number enabled exceeds the count, the enabling of statistics will pause.	1000 (where count is between 1 and 100000)
39	Stat Config Proc Delay	Specifies the amount of time in milliseconds (ms) that statistics processing pauses between enabling passes. On a heavily loaded switch, you may increase this number to reduce the load when enabling statistics, but the enabling process takes longer. The total (approximate) amount of time to process a statistics-enable request is calculated as shown below: total_time = (num_of_stats / count_per_pass) * delay_per_pass where num_of_stats is the sum of all statistics for this switch (conns * conn stats + lines * line stats + ...) count_per_pass is described above delay_per_pass is described above Using an example of a switch with 1000 connections (10 statistics per connection), three trunks (10 statistics per trunk), 10 ports (10 statistics per port), and the default settings (count = 1000, delay = 2000 msec) yields the following: total_time = ([(1000 * 10) + (3 * 10) + (10 * 10)] / 1000 * 2000 = (10130 / 1000) * 2000 = 11 * 2000 = 22000 msec = 22 seconds	2000 (where delay is between 50 and 60000 ms)
40	Enable Degraded Mode	Enables or disables the rebuild-prevention feature on the node. Enabling this parameter causes a graceful switchover of the active controller card without having to do a rebuild. User connections and user traffic are maintained even when bugs or system overload would cause repeated aborts. Remaining updates are completed as fast as possible without affecting existing connections. If this parameter is disabled and an abort occurs during the update of the standby processor, the node rebuilds. On the BPX, the active/standby/fail lights on the active card flash at the same time indicating the node is in degraded mode.	No (disabled)
41	Trk Cell Rtng Restrict	Specifies whether connections can be routed using cell-based trunks only. The Trk Cell Rtng Restrict parameter lets you specify a default for an option to the addcon command; that is, you can specify what the addcon parameter "Trunk cell routing restricted" prompts the user as a default, for example: "Trunk cell routing restricted? y/n [y]" or "Trunk cell routing restricted? y/n [n]". If "n" is specified, then FastPacket-based routing is used.	[Yes is default] Yes/No
42	Enable Feeder Alert	When degraded mode is entered, this parameter is set to yes, then a message is sent to the MGX 8220 interface shelves to update the nodes' status so that connections will not fail. This parameter works in conjunction with degraded mode parameters (for example, Auto Switch on Degrade). If Enable Feeder Alert is disabled (the default) or, due to network congestion, the messages cannot be exchanged between the hub and the feeder to disable LMI, manual intervention can still be achieved by using the addfdrlp and delfdrlp commands on the BPX. (Note that addfdrlp and delfdrlp commands are service-level commands and can be used only by Cisco personnel.)	[No is default] Yes/No
43	Reroute on Comm Failure	Default value is False. If there is communication failure, the node will not send the topology update message to the other nodes. If the value is set to True, the node will send out a line change message and the remote nodes (master/slave) will deroute/condition the connections. Also, connections are always rerouted on a Virtual Trunk regardless of whether reroute on path fail is enabled or not. You would sometimes use this parameter in conjunction with the A-bit Notifications on LMI/ILMI Interface feature (which you enable with the cnfnodeparm SuperUser command). For information about the A-bit Notifications feature, see the <CommandItalic>Cisco WAN Switch Command Reference.	True/False
44	Auto Switch on Degrade	When degraded mode is entered, the standby card is updated and ready. If the default is enabled (yes) then the card switchover happens automatically. If this parameter is set to yes, when degraded mode is entered, then the standby card is ready, and the card switchover happens automatically.	[Yes is default] Yes/No
45	Max Degraded Aborts	Use this parameter to determine the maximum frequency with which degraded mode aborts can occur before some other action is taken. In other words, they will be used to threshold degraded mode aborts. Another action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. For example, using the default values of 100 for Max Hitless Rebuild Count, and 1000 hours Hitless Counter Reset Time, a maximum of 100 hitless rebuilds can occur within a 1000 hour period before it is determined that degraded mode should be entered. For each hitless rebuild that occurs, if 1000 hours pass without the maximum hitless rebuild count having been exceeded, then that hitless rebuild will have aged beyond the point where it is still considered for thresholding purposes.	100 is default (range is 0-100 or 255 (infinite)
46	Max Hitless Rebuild Count	Use this parameter to determine the maximum frequency with which hitless rebuilds can occur before some other action is taken. In other words, they will be used to threshold hitless rebuilds. Another action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. For example, using the default values of 100 for Max Hitless Rebuild Count, 1000 hours Hitless Counter Reset Time, a maximum of 100 hitless rebuilds can occur within a 1000 hour period before it is determined that degraded mode should be entered. For each hitless rebuild that occurs, if 1000 hours pass without the maximum hitless rebuild count having been exceeded, then that hitless rebuild will have aged beyond the point where it is still considered for thresholding purposes. If the maximum hitless rebuild counts is set to "255" for "infinite," then an unlimited number of hitless rebuilds can occur without the thresholding mechanism triggering a full rebuild or a change to degraded mode. In this case, the configurable hitless counter reset time will be ignored, no full rebuilds will be automatically performed. This allows you to determine when the best time is to manually perform a full rebuild, probably during a period of low traffic. At the other extreme, if the maximum hitless rebuild is set to zero, then no hitless rebuilds will be attempted. This disables the feature. When the configurable parameters Max Hitless Rebuild Count and Hitless Counter Reset Time are reconfigured, then the statistical counters for hitless rebuilds will be reset. The Max Hitless Rebuild Count and Hitless Counter Reset Time are stored in BRAM.	100 (range is 0-100 or 255 (infinite)
47	Hitless Counter Reset Time	Use this parameter to determine the maximum frequency with which hitless rebuilds may occur before some other action is taken. In other words, they will be used to threshold hitless rebuilds. Some other action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. For example, using the default values of 100 for Max Hitless Rebuild Count, 1000 hours Hitless Counter Reset Time, a maximum of 100 hitless rebuilds may occur within a 1000 hour period before it is determined that degraded mode should be entered. For each hitless rebuild that occurs, if 1000 hours pass without the maximum hitless rebuild count having been exceeded, then that hitless rebuild will have aged beyond the point where it is still considered for thresholding purposes.	1000 hours (range is 1-1000)
48	Send A-bit Early	Specifies whether A-bit is sent on deroute. The default is set to no initially. If you issue this command again, the prompt then shows the previously provisioned value. Use the Send A-bit Early parameter (option 48) to enable or disable the A-bit Notifications feature. (The default is N which means the A-bit Notifications feature is disabled.) If the Send A-bit Early parameter is set to N, then the settings for parameter 49 (A-bit Timer Multiplier M) and parameter 50 (A-bit Timer Granularity N) are ignored and have no effect. After you enable the Send A-bit Early parameter by setting it to yes, you can set the A-bit Timer Granularity N and A-bit Timer Multiplier M parameters. The Send A-bit Early parameter works in conjunction with the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. You must set the Send A-bit Early parameter to yes to enable it, then you can set the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. Note that a pre-Release 9.1.07 node or Release 9.1.07 node with the Release 9.1.07 cnfnodeparm Send A-bit immediately parameter turned off behaves the same way as a Release 9.2 node with the Early A-bit Notifications on ILMI/LMI Interface using Configurable Timer feature disabled. A 9.1.07 node with the cnfnodeparm Send A-bit immediately parameter turned on behaves the same as a Release 9.2 node with the Send A-bit Early (option 48 in cnfnodeparm) set to yes and the A-bit Timer Multiplier M (option 49 in cnfnodeparm) set to 0. The different A-bit behavior in Release 9.2 is completely local to the node and is applicable to the master and slave ends of connections when the connections are derouted. When only one of the nodes connected by a connection has the Send A-bit Early enabled (set to Y), the timing in which that the A-bit notification feature is sent at one end of the connection may be drastically different from the other end of the connection. Thus, it is recommended that the Send A-bit Early parameter be configured the same on all nodes. For more information on the Send A-bit Notification on ILMI/LMI using Configurable Timer feature, refer to the BPX 8600 Series Installation and Configuration manual.	[N is default] (Y/N)
49	A-bit Timer Multiplier M	The A-bit Timer Multiplier M and A-bit Timer Granularity N parameters are used in conjunction with the Send A-bit Early parameter. You must set the Send A-bit Early parameter to yes to enable it, then you can set A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. You can set the A-bit Timer Multiplier M option from 0 to 100. The default value is 0. When you execute the cnfnodeparm command, the prompt shows the previously configured value, or the default value if no upgrade or no configuration on these values was done previously. A value X is the time to wait before A-bit = 0 is sent out if the connection is in a derouted state. A connection derouted at a time period between 0 and N will send out A-bit = 0 at a time between X and X + N, if the connection continues to be in a derouted state. In cases where there are many A-bit status changes to report to the CPE, the last A-bit updates may be delayed much longer because A-bit updates process about 47 connections per second. To make a compromise between performance and the granularity of timers, A-bit Timer Multiplier N can be configured to be from 3 to 255 seconds. The bigger the value of N, the better the system performance will be. The value of X is M * N (A-bit Timer Multiplier M * A-bit Timer Granularity N values). To compromise between performance and the granularity of timers, N can be configured to be from 3 to 255 seconds; the bigger the value of N, the better the system performance will be. The value of X (M * N) is set such that M can be configured to be from 0 to 100. The default value for N is 3 seconds. The default value for M is 0, meaning A-bit = 0 sent out on deroute. It is recommended that the value of X (value of A-bit Timer Multiplier M * value of A-bit Timer Granularity N) be set such that when a trunk fails, the connections are given sufficient time to reroute successfully, avoiding the need to send out A-bit = 0. If the value of X is set to be smaller than the normal time to reroute connections when a trunk fails, the time to complete rerouting them may take longer. This can happen for line cards and feeder trunks that have LMI/ILMI protocol runs on those cards, such as BXM on BPX and Frame Relay cards on IGX. Note that it takes time for those cards to process A-bit status information for each connection coming from controller card through CommBus messages. Note that a pre-Release 9.1.07 node or a 9.1.07 node with the Send A-bit Early parameter turned off behaves the same way as a Release 9.2 node with the Release 9.2 Early A-bit Notifications feature disabled. A 9.1.07 node with the Send A-bit Early parameter turned on behaves the same way as a Release 9.2 node with the Send A-bit Early parameter set to on, and the A-bit Timer Multiplier M parameter set to 0. To follow the general Release 9.2 interoperability, it is recommended that the A-bit Notifications feature not be used when the standby control processor is in a locked state.	[Default is 0] (D)
50	A-bit Timer Granularity N	You can set the A-bit Timer Granularity N option from 3 to 255 seconds. The default value is 3 seconds. You use the A-bit Timer Granularity N and A-bit Timer Multiplier M parameters in conjunction with the Send A-bit Early parameter to configure the Early A-bit Notifications on LMI/ILMI Interface using Configurable Timer feature in Release 9.2 and beyond. (The Send A-bit Early parameter must be enabled before you can set the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters.) The Early A-bit Notifications feature lets the user specify the timer interval to wait before A-bit = 0 is sent out if a connection fails to reroute and is in the derouted state too long. No precise timer is kept for each connection. Instead, all connections derouted during a certain time period go to the same bucket. This time period is N, which defines the granularity of the timers, and is specified by the A-bit Timer Granularity N parameter. Also, the value X is the time to wait before A-bit = 0 is sent out if the connection is in a derouted state. A connection that is derouted at a time period between 0 and N will send out A-bit = 0 at a time between X and X + N if the connection continues to be in a derouted state. In cases where there are many A-bit status changes to report to the CPE, the last A-bit updates may be delayed much longer because A-bit updates process about 47 connections per second. To compromise between performance and the granularity of timers, you can configure the N value (A-bit Timer Granularity N) to be from 3 to 255 seconds. The bigger the value of N, the better the system performance will be. The value of X should be M * N, where M can be configured to be from 0 to 100. The default value for N (specified by the A-bit Timer Multiplier N parameter) is 3 seconds. The default value for M is 0, meaning that A-bit = 0 is sent out on deroute. It is recommended that the value of X (A-bit Timer Multiplier M value * A-bit Timer Granularity N value) be set such that when a trunk fails, the connections are given sufficient time to reroute successfully, avoiding the need to send out A-bit = 0.	[Default is 3 seconds]
51	FBTC with PPD Policing	If you have installed a BXM card with the Routing Control Monitoring and Policing (RCMP) chip, which supports PPD on policing, you may enable this feature by setting this parameter to Y. Older BXM cards do not support PPD on policing. After enabling this parameter, a warning appears: "Warning: Must switchyred or reset PPDPolic BXM line cards after change." Note that these operations are not supported in remote NMS stations. Next you must choose one of two options by entering either Y or N: Y = BXM FBTC on thresholds and PPD policing. This option is supported only on BXM cards with the new version of the RCMP chip that provides this functionality. N = BXM FBTC on thresholds. Provides FBTC on CLP thresholds only. Although it is not recommended to use both an older BXM card and a BXM card that supports PPD on policing on a Y-redundant pair, you can do so. The severity of the feature mismatch is minor because FBTC can still function based on the CLP thresholds on the BXM card that does not support PPD on policing. This parameter is a one-time installation task; it should not be frequently changed.	[N is default] (Y/N)
52	CommBrk Hop Weight	In order to do concentric Comm Break clearing, nodes are ordered by hop count as well as by the time they have been waiting for the Comm Break test. This ensures that the running of route op if no topology change was detected does not change the order of testing. Also, distant nodes are guaranteed to be tested after a finite time regardless of how many nodes go in and out of Comm Break. The function used is: h * w - s Where h is the number of hops a node is away, s is the number of second since it is in Comm Break (and not in path fail), w is the CommBrk Hop Weight.	[25 is the default] (D)
53	CB Fail Penalty Hops	A node that fails a Comm Break test is entered into the list mentioned in the previous description of CommBrk Hop Weight, plus a penalty. The penalty is at least p * w, where p (by default 2) is configurable as the CB Fail Penalty Hops parameter. This means the node gets another chance after p rings have been tested. In the old way the node did not get another chance after all nodes had been tested.	[2 is the default] (D)
54	Auto BXM Upgrade	Used for legacy BXM to BXM-E upgrades. If the parameter is set to Y, SWSW upgrades the logical database as soon as both legacy BXMs are replaced by BXM-Es in yred case, or the active legacy BXM is replaced by a BXM-E in non-yred case. Set this parameter to N if you want to manually upgrade. Refer to the BPX 8600 Installation and Configuration Guide, 9.3.0 Release, for upgrade scenarios and procedures.	[Y default is yes] (Y/N)
55	LCN reprgrm batch cnt	Specifies the number of LCN(s) to be reprogrammed in a batch before giving up CPU. This is typically used for dynamic partitioning.	[100 is the default] (D)
56	Download LAN IP or Network IP Address	Specifies whether to use the configured LAN IP or network IP address as the management IP address used in the ILMI Neighbor Discovery procedure. The management IP address is part of the neighbor information exchanged between the BPX and an attached ATM device, such as CISCO ATM routers or switches, when the ILMI Neighbor Discovery feature is enabled. The management IP address allows a network management system to access the BPX and the attached device. Use the cnflan command to configure the LAN IP address. Use the cnfnwip command to configure the network IP address. Use the cnfport command to enable the ILMI protocol and Advertise Interface Information parameter. Use the dspnebdisc command to display the neighbor information discovered by the Neighbor Discovery feature.	[Nw is default] (Lan/Nw)
57	IP Relay Gateway Node Number	Specifies the node number of the node that is to serve as an IP Relay Gateway to a TFTP network server used to save and restore node configuration files. The default value for this parameter is zero to indicate no node. The network server must be reachable through the LAN from the configured IP Relay Gateway. The IP Relay Gateway node must be configured separately on each node in the network. The configured gateway can be the same on all nodes if a dingle IP relay gateway is used for all nodes. Multiple gateways and/or multiple network servers can be used to decrease bottlenecks and the time required to back up the entire network.	0 (default) (range of node numbers is 1-223)
* Enter value in either decimal (D) or hexadecimal (H).

Parameters (IGX)

Index	Parameter	Description	Default
1	Update Initial Delay (sec.)	Specifies a factor for generating a delay before conditional updates are transmitted to the network after a controller card switchover. The Update Initial Delay is multiplied by the number of nodes in the network.	5000 (D)
2	Update Per-Node Delay (ms.)	Specifies the delay between transmission of conditional updates to the nodes.	30000 (D)
3	Comm. Break Test Delay (ms.)	Normal interval between tests for communication break on any node.	30000 (D)
4	Comm. Break Test Offset	Factor between number of communication test failures and test successes to declare a node in communication break condition.	10 (D)
5	Network Time-out Period	Number of milliseconds to wait for a response to a communication test transmission before declaring a failure. The maximum is four failures.	1700 (D)
6	Network Inter-p Period	In inter-domain connections, Network Inter-p Period is the number of milliseconds to wait for a response to a communication test transmission before declaring a failure. The maximum is four failures.	4000 (D)
7	Network Sliding Window Size	Controls the number of control card messages that the node can simultaneously transmit to the network. This parameter defines the number of "no acknowledgments outstanding" on a controller before NACKS is declared.	1 (D)
8	Number of Normal Time-outs	For intra-domain connections: Number of Normal Time-outs is the maximum number of normal network retransmissions before the node signals a communication break.	7 (D)
9	Number of Inter-p Time-outs	For inter-domain connections: Number of Inter-p Time-outs is the maximum number of normal network retransmissions before the node signals a communication break.	3 (D)
10	Number of Satellite Time-outs	Maximum number of satellite network retransmissions before the node signals a communication break.	6 (D)
11	Number of Blind Time-outs	Maximum number of communication fail time-outs and retransmissions performed when using the blind channel. "Blind" refers to the message being sent across the trunk without knowing what node is on the other end of the trunk. The Comm Fail test uses this blind channel, however, the Comm Fail application has a non-configurable limit of three comm failures before declaring Comm Fail. For example, the network handler task will attempt to deliver the Comm Fail request message four times before reporting a failure back to the Comm Fail application, which will retry twice more (each with four retries on the blind channel) before declaring Comm Fail. The Number of Blind Time-outs parameter is the number of communication fail time-outs and retransmissions performed when using the blind channel.	4 (D)
12	Number of CB Msg Timeouts	Number of communication break time-outs and retransmissions before the node declares a communication break condition (CB). One successful acknowledgment clears the CB condition.	2 (D)
13	Comm. Fail Interval (ms.)	Minimum time allocated for communication fail testing of all trunks terminating on the local node.	10,000 (D)
14	Comm. Fail Multiplier	Number of Comm. Fail Intervals to skip for good lines.	3 (D)
15	Temperature Threshold (ЧC.)	Temperature in the enclosure that causes an over-temperature alarm to go to the controller card.	50 (D)
16	Redundancy Configured	A y indicates a redundant controller card is required. The absence of a redundant controller card generates an alarm.	Y
17	MT3 Pass Through Delay	The parameter is OBSOLETE.
18	Network Packet TX Rate	Rate for transmitting control card packets to the network. The range is a series of discreet values: 100 200 333 500 1000 1100 1200 1333 1500 2000. The units of measure are packets per second (pps). The purpose of this parameter is to prevent the control card from flooding the trunk with packets.	500 pps
19	TFTP Memory (x 10 KB)	Specifies the amount of controller memory to allocate for statistics collection.	76 (D)
20	Standby Update Timer	Specifies how often to send update messages to standby controller.	10 (D)
21	Stby Updts Per Pass	Number of messages that can be sent to the standby card for each update interval.	30 (D)
22	Gateway ID Timer	An inter-domain rerouting timer. How often to look for junction nodes for new route.	30 (D)
23	GLCON Alloc Timer	Another inter-domain rerouting timer controlling the gateway LCON function.	30 (D)
24	Comm Fail Delay	Number of seconds before starting to detect communication failures after a controller switch over.	60 (D)
25	Nw Hdlr Timer (msec)	Network handler timer determines how long to wait to send messages to or receive messages from a remote node.	50 (D)
26	CBUS Delay	Specifies the minimum number of milliseconds the NPM must wait before it places the next command on the CBUS.	20 (D)
27	SNMP Event Logging	Enables maintenance logging of global SNMP messages. These SNMP events are not errors but any GET, SET, and so on. Output goes to a printer connected to the node's auxiliary port or a terminal server (accessible via Telnet). Without a connected output device, the parameter is meaningless.	y=yes
28	TFTP Grant Delay (sec)	The number of seconds the node waits before resending a TFTP request after a TFTP error has occurred. This field is display-only; you set the value in Cisco WAN Manager.	1
29	TFTTP ACK Time-out (sec)	The number of seconds the node waits for an acknowledgment of a TFTP request before it declares the request as timed out. This field is display-only; you set the value in Cisco WAN Manager.	10
30	TFTP Write Retires	The number of times the node retries a TFTP operation (not just writes) after a failed attempt. This field is display-only: you set the value in Cisco WAN Manager.	3
31	FRP/FRM Link Status Alarm	Determines whether a signaling failure on an FRP or FRM port causes a major alarm. This parameter applies to any port configured as an NNI.	y=yes
32	Job Lock Time-out	The range is 1-1000 seconds. The default of 0 disables this parameter.	0
33	Max Via LCONs	The maximum number of "via" connections a node can support. (A via connection does not terminate on the node but merely passes through.) This maximum is configurable, but you cannot lower the number below the current limit on the node. The default is the current maximum and should remain unchanged for normal operating conditions.	On an IGX node: 20000 On a BPX node: 50000
34	Max Blind Segment Size	The maximum size of each segment of a blind message. (The full message may be longer than the segment, especially in a large network.) A blind message is a message the local node sends to the far end node when you execute addtrk. If the trunk has many errors, smaller message segments increase the possibility of a successful addtrk. Under normal conditions, this parameter should remain the default.	3570
35	Max XmtMemBlks Per NIB	Maximum number of memory blocks available for messages that are awaiting transmission. Under normal conditions, this parameter should remain the default.	3000
36	Max Mem Stby Update Q Size	Maximum number of update messages that can reside in queues awaiting transmission to the standby processor. This percentage is used to determine when to flush the standby message queue when the percentage is reached. Only rare circumstances could provide a reason to change this parameter, so do not change it without first consulting the TAC.	5000
37	Trk Cell Rtng Restrict	Specifies whether or not trunks on a UXM on an IGX node can route only cell traffic. The Trk Cell Rtng Restrict parameter lets you specify a default for an option to the addcon command; that is, you can specify what the addcon parameter "Trunk cell routing restricted" prompts the user as a default, for example: "Trunk cell routing restricted? y/n [y]" or "Trunk cell routing restricted? y/n [n]." If "n" is specified, then FastPacket-based routing is used. When adding or configuring ATM connections, this prompt will display for all connections (for example, CBR, ABR, UBR, and so on) except for real-time VBR (rt-VBR) connections because rt-VBR connections should not be routed over FastPacket trunks.	Yes/No
38	Stat Config Proc Cnt	Stat Config Proc Cnt is the number of statistics that will be enabled before pausing and allowing other processes to run. The default value of 1000 specifies that 1000 statistics should be enabled. But the count is checked only once for every object, so if the number of objects exceeds the count there will be one statistic enabled for each object. For example, if there are 1000 connections and the default count is set, one statistic will be enabled for each connection before pausing. If there are 2000 connections, one statistic will be enabled for each connection, then the number of statistics enabled (2000) will be compared to the count (1000). Since the number enabled exceeds the count, the enabling of statistics will pause.	1000 (where count is between 1 and 100000)
39	Stat Config Proc Delay	Specifies the amount of time in milliseconds (ms) that statistics processing pauses between enabling passes. On a heavily loaded switch, you may increase this number to reduce the load when enabling statistics, but the enabling process takes longer. The total (approximate) amount of time to process a statistics-enable request is calculated as shown below: total_time = (num_of_stats / count_per_pass) * delay_per_pass where num_of_stats is the sum of all statistics for this switch (conns * conn stats + lines * line stats + ...) count_per_pass is described above delay_per_pass is described above Using an example of a switch with 1000 connections (10 statistics per connection), three trunks (10 statistics per trunk), 10 ports (10 statistics per port), and the default settings (count = 1000, delay = 2000 msec) yields the following: total_time = ([(1000 * 10) + (3 * 10) + (10 * 10)] / 1000 * 2000 = (10130 / 1000) * 2000 = 11 * 2000 = 22000 msec = 22 seconds	2000 (where delay is between 50 and 60000 ms)
40	Enable Degraded Mode	Enables or disables the rebuild-prevention feature on the node. Enabling this parameter causes a graceful switchover of the active controller card without having to do a rebuild. User connections and user traffic are maintained even when bugs or system overload would cause repeated aborts. Remaining updates are completed as fast as possible without affecting existing connections. If this parameter is disabled and an abort occurs during the update of the standby processor, the node rebuilds. Note that on the IGX, the active/standby/fail lights on the active card do not flash (as they do on the BPX node to indicate that the node is in degraded mode). If enabled, an abort condition will transition the node into degraded mode rather than rebuilding the node. You can disable this parameter (it is enabled by default) so that an abort will result in a rebuild. After degraded has been entered, a minimal set of functionality is available. (See the "High Priority Login" section for more information.) Disabled functions include provisioning and routing, network communications, event logging, and LAN access. However, connections continue to pass traffic. Once in degraded mode, a configurable parameter indicates whether to switch to the standby once it's ready. If Enable Degraded Mode is enabled (Y), an abort condition will transition the node into degraded mode rather than rebuilding the node. You can disable this parameter so that an abort will result in a node rebuild.	Y (enabled)
41	Enable Feeder Alert	When degraded mode is entered, this parameter is set to yes, then a message is sent to the MGX 8220 interface shelves to update the nodes' status so that connections will not fail. This parameter works in conjunction with degraded mode parameters (for example, Auto Switch on Degrade). If Enable Feeder Alert is disabled (the default) or, due to network congestion, the messages cannot be exchanged between the hub and the feeder to disable LMI, manual intervention can still be achieved by using the addfdrlp and delfdrlp commands on the BPX. (Note that addfdrlp and delfdrlp commands are service-level commands and can be used only by Cisco personnel.)	[No is default] Yes/No
42	Trk Cell Rtng Restrict	Specifies whether connections can be routed using cell-based trunks only. The Trk Cell Rtng Restrict parameter lets you specify a default for an option to the addcon command; that is, you can specify what the addcon parameter "Trunk cell routing restricted" prompts the user as a default, for example: "Trunk cell routing restricted? y/n [y]" or "Trunk cell routing restricted? y/n [n]". If "n" is specified, then FastPacket-based routing is used.	Yes/No
43	Enable Reroute on Comm Fail	Default value is False. If there is communication failure, the node will not send the topology update message to the other nodes. If the value is set to True, the node will send out a line change message and the remote nodes (master/slave) will deroute/condition the connections. You would sometimes use this parameter in conjunction with the A-bit Notifications on LMI/ILMI Interface feature (which you enable with the cnfnodeparm SuperUser command). See the A-bit Notifications feature description in the Cisco WAN Switching Command Reference.	[F] (T/F)
44	Auto Switch on Degrade	When degraded mode is entered, the standby card is updated and ready. If the default is enabled (yes) then the card switchover happens automatically. If this parameter is set to yes, when degraded mode is entered, then the standby card is ready, and the card switchover happens automatically. After a node has entered degraded mode (see Enable Degraded Mode parameter), this parameter indicates whether to switch to the standby card once it is ready. The default setting is to enable switching. You can set this parameter to disable switching if you want to allow further time to diagnose the problem rather than switching to the other processor, or to stop switching due to repeated aborts.	[Yes is default] Yes/No
45	Max Degraded Aborts	Use this parameter to determine the maximum frequency with which degraded mode aborts can occur before some other action is taken. In other words, they will be used to threshold degraded mode aborts. Another action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. This parameter indicates the maximum number of aborts while in the degraded state. In the case where the processor continues to reset while in degraded mode, each reset will result in the processor staying in degraded mode unless this threshold has been reached, in which case the next reset will cause a full rebuild of the node. The desired result is to avoid infinite aborts while in degraded mode, which would essentially lock the node indefinitely. You can set Max Degraded Aborts to its maximum value (255) to indicate that the processor will be allowed to abort indefinitely without going through a full rebuild. This approach can be used to avoid a full rebuild (which will impact the user plane) until an appropriate time is reached when it may be reset or replaced.	100 is default (range is 0-100 or 255 (infinite)
46	Max Hitless Rebuild Count	Use this parameter to determine the maximum frequency with which hitless rebuilds can occur before some other action is taken. In other words, they will be used to threshold hitless rebuilds. Another action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. For example, using the default values of 100 for Max Hitless Rebuild Count and 1000 hours Hitless Counter Reset Time, a maximum of 100 hitless rebuilds can occur within a 1000 hour period before it is determined that degraded mode should be entered. For each hitless rebuild that occurs, if 1000 hours pass without the maximum hitless rebuild count having been exceeded, then that hitless rebuild will have aged beyond the point where it is still considered for thresholding purposes. If the maximum hitless rebuild count is set to "255" for "infinite," then an unlimited number of hitless rebuilds can occur without the thresholding mechanism triggering a full rebuild or a change to degraded mode. In this case, the configurable hitless counter reset time will be ignored, no full rebuilds will be automatically performed. This allows you to determine when the best time is to manually perform a full rebuild, probably during a period of low traffic. At the other extreme, if the maximum hitless rebuild is set to zero, then no hitless rebuilds will be attempted. This disables the feature. When the configurable parameters Max Hitless Rebuild Count and Hitless Counter Reset Time are reconfigured, then the statistical counters for hitless rebuilds will be reset. The Max Hitless Rebuild Count and Hitless Counter Reset Time are stored in BRAM.	100 (range is 0-100 or 255 (infinite)
47	Hitless Counter Reset Time	Use this parameter to determine the maximum frequency with which hitless rebuilds can occur before some other action is taken. In other words, they will be used to threshold hitless rebuilds. Another action could be a full rebuild, or it could be entering degraded mode. The allowable configurable range is shown in the Default column to the right. For example, using the default values of 100 for Max Hitless Rebuild Count and 1000 hours Hitless Counter Reset Time, a maximum of 100 hitless rebuilds can occur within a 1000 hour period before it is determined that degraded mode should be entered. For each hitless rebuild that occurs, if 1000 hours pass without the maximum hitless rebuild count having been exceeded, then that hitless rebuild will have aged beyond the point where it is still considered for thresholding purposes. If the maximum hitless rebuild count is set to "255" for "infinite", then an unlimited number of hitless rebuilds can occur without the thresholding mechanism triggering a full rebuild or a change to degraded mode. In this case, the configurable hitless counter reset time will be ignored, no full rebuilds will be automatically performed. This allows you to determine when the best time is to manually perform a full rebuild, probably during a period of low traffic. At the other extreme, if the maximum hitless rebuild is set to zero, then no hitless rebuilds will be attempted. This disables the feature. When the configurable parameters Max Hitless Rebuild Count and Hitless Counter Reset Time are reconfigured, then the statistical counters for hitless rebuilds will be reset. The Max Hitless Rebuild Count and Hitless Counter Reset Time are new in Release 9.2, and will be stored in BRAM.	1000 hours (range is 1-1000)
48	Send A-bit Early	Specifies whether A-bit is sent on deroute. The default is set to no initially. If you issue this command again, the prompt then shows the previously provisioned value. Use the Send A-bit Early parameter (option 48) to enable or disable the A-bit Notifications feature. (The default is N, which means the A-bit Notifications feature is disabled.) If the Send A-bit Early parameter is set to N, then the settings for parameter 49 (A-bit Timer Multiplier M) and parameter 50 (A-bit Timer Granularity N) are ignored and have no effect. After you enable the Send A-bit Early parameter by setting it to yes, you can set the A-bit Timer Granularity N and A-bit Timer Multiplier M parameters. The Send A-bit Early parameter works on conjunction with the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. You must set the Send A-bit Early parameter to yes to enable it, then you can set the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. The different A-bit behavior in Release 9.2 and higher is completely local to the node and is applicable to the master and slave ends of connections when the connections are derouted. When only one of the nodes connected by a connection has the Send A-bit Early enabled (set to Y), the timing in which that the A-bit notification feature is sent at one end of the connection may be drastically different from the other end of the connection. Thus, it is recommended that the Send A-bit Early parameter be configured the same on all nodes. For more information on the Send A-bit Notification on ILMI/LMI using Configurable Timer feature, refer to the BPX 8600 Series Installation and Configuration Manual.	[N is default] (Y/N)
49	A-bit Timer Multiplier M	The A-bit Timer Multiplier M and A-bit Timer Granularity N parameters are used in conjunction with the Send A-bit Early parameter. You must set the Send A-bit Early parameter to yes to enable it, then you can set A-bit Timer Multiplier M and A-bit Timer Granularity N parameters. You can set the A-bit Timer Multiplier M option from 0 to 100. The default value is 0. When you execute the cnfnodeparm command, the prompt shows the previously configured value, or the default value if no upgrade or no configuration on these values was done previously. A value X is the time to wait before A-bit = 0 is sent out if the connection is in a derouted state. A connection derouted at a time period between 0 and N will send out A-bit = 0 at a time between X and X + N, if the connection continues to be in a derouted state. In cases where there are many A-bit status changes to report to the CPE, the last A-bit updates may be delayed much longer because A-bit updates process about 47 connections per second. To make a compromise between performance and the granularity of timers, A-bit Timer Multiplier N can be configured to be from 3 to 255 seconds. The bigger the value of N, the better the system performance will be. The value of X is M * N (A-bit Timer Multiplier M * A-bit Timer Granularity N values). To compromise between performance and the granularity of timers, N can be configured to be from 3 to 255 seconds; the bigger the value of N, the better the system performance will be. The value of X (M * N) is set such that M can be configured to be from 0 to 100. The default value for N is 3 seconds. The default value for M is 0, meaning A-bit = 0 sent out on deroute. It is recommended that the value of X (value of A-bit Timer Multiplier M * value of A-bit Timer Granularity N) be set such that when a trunk fails, the connections are given sufficient time to reroute successfully, avoiding the need to send out A-bit = 0. If the value of X is set to be smaller than the normal time to reroute connections when a trunk fails, the time to complete rerouting them may take longer. This can happen for line cards and feeder trunks that have LMI/ILMI protocol runs on those cards, such as BXM on BPX and Frame Relay cards on IGX. Note that it takes time for those cards to process A-bit status information for each connection coming from controller card through Comm Bus messages. To follow the general Release 9.2 interoperability, it is recommended that the A-bit Notifications feature not be used when the standby control processor is in a locked state.	[Default is 0] (D)
50	A-bit Timer Granularity N	You can set the A-bit Timer Granularity N option from 3 to 255 seconds. The default value is 3 seconds. You use the A-bit Timer Granularity N and A-bit Timer Multiplier M parameters in conjunction with the Send A-bit Early parameter to configure the Early A-bit Notifications on LMI/ILMI Interface using Configurable Timer feature in Release 9.2 and beyond. (The Send A-bit Early parameter must be enabled before you can set the A-bit Timer Multiplier M and A-bit Timer Granularity N parameters.) The Early A-bit Notifications feature lets the user specify the timer interval to wait before A-bit = 0 is sent out if a connection fails to reroute and is in the derouted state too long. No precise timer is kept for each connection. Instead, all connections derouted during a certain time period go to the same bucket. This time period is N, which defines the granularity of the timers, and is specified by the A-bit Timer Granularity N parameter. Also, the value X is the time to wait before A-bit = 0 is sent out if the connection is in a derouted state. A connection that is derouted at a time period between 0 and N will send out A-bit = 0 at a time between X and X + N if the connection continues to be in a derouted state. In cases where there are many A-bit status changes to report to the CPE, the last A-bit updates may be delayed much longer because A-bit updates process about 47 connections per second. To compromise between performance and the granularity of timers, you can configure the N value (A-bit Timer Granularity N) to be from 3 to 255 seconds. The bigger the value of N, the better the system performance will be. The value of X should be M * N, where M can be configured to be from 0 to 100. The default value for N (specified by the A-bit Timer Multiplier N parameter) is 3 seconds. The default value for M is 0, meaning that A-bit = 0 is sent out on deroute. It is recommended that the value of X (A-bit Timer Multiplier M value * A-bit Timer Granularity N value) be set such that when a trunk fails, the connections are given sufficient time to reroute successfully, avoiding the need to send out A-bit = 0.	[Default is 3 seconds]
51	CommBrk Hop Weight	In order to do concentric Comm Break clearing, nodes are ordered by hop count as well as by the time they have been waiting for the Comm Break test. This ensures that the running of route op if no topology change was detected does not change the order of testing. Also, distant nodes are guaranteed to be tested after a finite time regardless of how many nodes go in and out of Comm Break. The function used is: h * w - s Where h is the number of hops a node is away, s is the number of second since it is in Comm Break (and not in path fail), w is the CommBrk Hop Weight.	[25 is the default] (D)
52	CB Fail Penalty Hops	A node that fails a Comm Break test is entered into the list mentioned in the previous description of CommBrk Hop Weight, plus a penalty. The penalty is at least p * w, where p (by default 2) is configurable as the CB Fail Penalty Hops parameter. This means the node gets another chance after p rings have been tested. In the old way the node did not get another chance after all nodes had been tested.	[2 is the default] (D)
53	Download LAN IP or Network IP Address	Specifies whether to use the configured LAN IP or network IP address as the management IP address used in the ILMI Neighbor Discovery procedure. The management IP address is part of the neighbor information exchanged between the IGX and an attached ATM device, such as CISCO ATM routers or switches, when the ILMI Neighbor Discovery feature is enabled. The management IP address allows a network management system to access the IGX and the attached device. Use the cnflan command to configure the LAN IP address. Use the cnfnwip command to configure the network IP address. Use the cnfport command to enable the ILMI protocol and the Advertise Interface Information parameter. Use the dspnebdisc command to display the neighbor information discover by the Neighbor Discovery feature.	[Lan is the default] (Lan/Nw)
54	IP Relay Gateway Node Number	Specifies the node number of the node that is to serve as an IP Relay Gateway to a TFTP network server used to save and restore node configuration files. The default value for this parameter is zero to indicate no node. The network server must be reachable through the LAN from the configured IP Relay Gateway. The IP Relay Gateway node must be configured separately on each node in the network. The configured gateway can be the same on all nodes if a single network server is used for all TFTP configuration backups. Multiple gateways and/or multiple network servers can be used to decrease bottlenecks and the time required to back up the entire network.	0 (default) (range of node numbers is 1-223)
* Enter value in either decimal (D) or hexadecimal (H).

Example (BPX)

cnfnodeparm

bpx1 TN Cisco BPX 8620 9.3.30 Mar. 19 2000 10:47 GMT




1 Update Initial Delay [ 5000] (D) 16 Stats Memory (x 100KB) [ 132] (D)

2 Update Per-Node Delay [30000] (D) 17 Standby Update Timer [ 10] (D)

3 Comm-Break Test Delay [30000] (D) 18 Stby Updts Per Pass [ 150] (D)

4 Comm-Break Test Offset [ 10] (D) 19 Gateway ID Timer [ 30] (D)

5 Network Timeout Period [ 1700] (D) 20 GLCON Alloc Timer [ 30] (D)

6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [ 60] (D)

7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [ 25] (D)

8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [ 560] (D)

9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [ 280] (D)

10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [ 56] (D)

11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [ 7680] (D)

12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [ 256] (D)

13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [ Y] (Y/N)

14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [ 1] (D)

15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [ 10] (D)




This Command: cnfnodeparm





Continue?




bpx1 TN Cisco BPX 8620 9.3.30 Mar. 19 2000 10:47 GMT




31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [ 100] (D)

32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D)

33 Job Lock Timeout [ 60] (D) 48 Send Abit early [ N] (Y/N)

34 Max Via LCONs [50000] (D) 49 Abit Tmr Multiplier M [ 0] (D)

35 Max Blind Segment Size [ 3570] (D) 50 Abit Tmr Granularity N [ 3] (D)

36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [ N] (Y/N)

37 Max Mem on Stby Q (%) [ 33] (D) 52 CommBrk Hop Weight [ 25] (D)

38 Stat Config Proc Cnt [ 1000] (D) 53 CB Fail Penalty Hops [ 2] (D)

39 Stat Config Proc Delay [ 2000] (D) 54 Auto BXM upgrade [ Y] (Y/N)

40 Enable Degraded Mode [ Y] (Y/N) 55 LCN reprgrm batch cnt [ 100] (D)

41 Trk Cell Rtng Restrict [ Y] (Y/N) 56 Dnld LanIP or NwIP [ Nw](Lan/Nw)

42 Enable Feeder Alert [ N] (Y/N) 57 IP Relay gateway node [ 0] (D)

43 Reroute on Comm Fail [ N] (Y/N)

44 Auto Switch on Degrade [ Y] (Y/N)

45 Max Degraded Aborts [ 100] (D)




This Command: cnfnodeparm

Example (IGX)

cnfnodeparm

sw76 TN Cisco IGX 8420 9.3.30 Mar. 19 2000 12:45 GMT




1 Update Initial Delay [ 5000] (D) 16 CC Redundancy Cnfged [ Y] (Y/N)

2 Update Per-Node Delay [30000] (D) 17 MT3 Pass Through Relay [ Y] (Y/N)

3 Comm-Break Test Delay [30000] (D) 18 Nw Pkt Tx Rate (pps) [ 500] (D)

4 Comm-Break Test Offset [ 10] (D) 19 TFTP Memory (x 10KB) [ 210] (D)

5 Network Timeout Period [ 1700] (D) 20 Standby Update Timer [ 10] (D)

6 Network Inter-p Period [ 4000] (D) 21 Stby Updts Per Pass [ 50] (D)

7 NW Sliding Window Size [ 1] (D) 22 Gateway ID Timer [ 30] (D)

8 Num Normal Timeouts [ 7] (D) 23 GLCON Alloc Timer [ 30] (D)

9 Num Inter-p Timeouts [ 3] (D) 24 Comm Fail Delay [ 60] (D)

10 Num Satellite Timeouts [ 6] (D) 25 Nw Hdlr Timer (msec) [ 25] (D)

11 Num Blind Timeouts [ 4] (D) 26 CBUS Delay (msec) [ 20] (D)

12 Num CB Msg Timeouts [ 2] (D) 27 SNMP Event logging [ Y] (Y/N)

13 Comm Fail Interval [10000] (D) 28 TFTP Grant Delay (sec) [ 1] (D)

14 Comm Fail Multiplier [ 3] (D) 29 TFTP ACK Timeout (sec) [ 10] (D)

15 Temperature Threshold [ 50] (D) 30 TFTP Write Retries [ 3] (D)




This Command: cnfnodeparm





Continue?





sw76 TN Cisco IGX 8420 9.3.30 Mar. 19 2000 12:45 GMT




31 FRP Link Status Alarm [ Y] (Y/N) 46 Modem polling timer [ 1] (D)

32 Job Lock Timeout [ 0] (D) 47 Verify CBA for non-FRP [ N] (Y/N)

33 Max Via LCONs [20000] (D) 48 Send Abit early [ N] (Y/N)

34 Max Blind Segment Size [ 3570] (D) 49 Abit Tmr Multiplier M [ 0] (D)

35 Max XmtMemBlks per NIB [ 3000] (D) 50 Abit Tmr Granularity N [ 3] (D)

36 Max Mem on Stby Q (%) [ 33] (D) 51 CommBrk Hop Weight [ 25] (D)

37 Trk Cell Rtng Restrict [ Y] (Y/N) 52 CB Fail Penalty Hops [ 2] (D)

38 Stat Config Proc Cnt [ 1000] (D) 53 Dnld LanIP or NwIP [ Lan](Lan/Nw)

39 Stat Config Proc Delay [ 2000] (D) 54 IP Relay gateway node [ 0] (D)

40 Enable Degraded Mode [ Y] (Y/N)

41 Enable Rrt on Comm Fail[ N] (Y/N)

42 Auto Switch on Degrade [ Y] (Y/N)

43 Max Degraded Aborts [ 100] (D)

44 Max Htls Rebuild Count [ 100] (D)

45 Htls Counter Reset Time[ 1000] (D)




This Command: cnfnodeparm





Enter parameter index:

cnfnwip (configure network IP address)

Configures an IP address and subnet mask for the node. The network IP address and subnet mask support statistics collection for Cisco WAN Manager. The cnfnwip command defines the IP address the system uses to pass messages between Cisco WAN Manager and the node. The Statistics Master process in Cisco WAN Manager Network collects statistics. The Statistics Manager requests and receives statistics using TFTP Get and Put messages. These TFTP messages pass between the node and the Statistics Master using IP Relay. (See the cnfstatmast description for details on setting the Statistics Master address.)

The cnfnwip command supports the first phase of the Automatic Routing Management to PNNI migration. When the XLMI protocol and LMI Neighbor Discovery feature are enabled and the network IP is the selected Management IP address, the new network IP address is sent to the BXM card whenever the network IP address is changed.

Syntax

cnfnwip <IPAddr> <IPSubnetMask>

Parameters

Parameter	Description
<IPAddr>	IP address of the node: the format is nnn.nnn.nnn.nnn, where nnn can be 1-255
<IPSubnetMask>	subnet mask: the format is nnn.nnn.nnn.nnn

Attributes

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

Example

cnfnwip 199.35.96.217 255.255.255.0

where:

199.35.96.217 is the IP address, and 255.255.255.0 is the subnet mask.




axiom TN Bootzilla IGX 32 9.3 Apr. 13 2000 18:25 GMT




Active Network IP Address: 169.134.90.106

Active Network IP Subnet Mask: 255.255.255.0







Last Command: cnfnwip 169.134.90.106 255.255.255.0

cnfoamseg (configure connection OAM segment status)

Configures the segment status of an Extended PVC (XPVC) segment in a hybrid Automatic Routing Management-PNNI network. Using cnfoamseg for PVC is only applicable for ENNI/EUNI ports. To change the connection segment type for PVCs terminating on ENNI/EUNI ports has no impact to end-to-end OAM cells, such as AIS.

With Release 9.3.30, the BPX 8600 supports an XPVC that spans over an AR-PNNI, or AR-PNNI-AR, hybrid network. The Cisco WAN Manager (CWM) is used to add, modify, and delete XPVCs (using the SNMP Service Agent proxy along with provided CWM-XPVC-CLI scripting capability). The CWM is also used to display XPVC connection details and monitor XPVC status.

The AR BXM and PNNI AXSM interface cards allow Enhanced UNI (EUNI) and Enhanced NNI (ENNI) port types that support XPVC segments. XPVC segments terminating on EUNI/ENNI ports are automatically programmed as "non-segment" endpoints. Non-segment endpoints do not loop back OAM segment loopback cells. With non-segment endpoints, OAM loopback cells are passed through to the adjacent network. Consequently, the CWM test procedures, such as test delay, cannot identify a faulty XPVC segment. When end-to-end XPVC testing fails, the faulty AR or PNNI network and faulty XPVC segment must be identified.

You use the cnfoamseg command to change the segment status of an XPVC segment from "non-segment" to "segment". When the XPVC segment status is "segment", OAM segment loopback cells are looped back at the terminating EUNI/ENNI endpoint. This allows CWM test procedures to be executed on each XPVC segment to isolate a fault. The command cnfoamseg does have SNMP support.

The CWM is notified when the XPVC segment status is changed. The XPVC segment status is persistent. The status is retained for node rebuild and card reset. The secondary BXM card in a Y-redundant pair retains the segment status.

Use the CWM interface to determine fault isolation instead of trying to do this from the CLI. After a fault has been isolated, use the cnfoamseg command to reset the XPVC segment status as "non-segment" for normal operation in the AR-PNNI hybrid network. Use the dspoamseg command to display the current segment status of an XPVC segment.

Syntax

cnfoamseg <connection_channel> <segment_flag>

Parameters

Parameter	Description
connection channel	Specifies the XPVC segment channel to be configured. Channel is specified in the following format: slot.port.vpi.vci
segment flag	Specifies the segment status of the XPVC segment. The values are Y/N. The default is N. •Y - selects the segment status of "segment" •N - selects the segment status of "non-segment"

Attributes

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

Related Commands

dspoamseg

Example

Change the segment status of XPVC segment channel 9.1.10.500 from "non-segment" to "segment". Verify that the segment status is changed using the dspoamseg command.

cnfoamseg 9.1.10.500

bpx1 TN Cisco BPX 8620 9.3 Feb. 7 2001 16:46 GMT




Connection segment status




The Connection is : Non-Segment















This Command: cnfoamseg 9.1.10.500




Segment(Y/N): y




-----------------------------------------------------------------------------------

bpx1 TN Cisco BPX 8620 9.3 Feb. 7 2001 16:40 GMT




Connection segment status




The Connection is : Segment















Last Command: dspoamseg 9.1.10.500




cnfphyslnstats (configure physical line statistics)

Configures parameters for circuit line statistics collection on a UXM card. This is a debug command that applies to physical lines on a UXM card using Inverse Multiplexing Over ATM (IMA)—a logical trunk or logical line configuration. It primarily applies to debugging and not standard network operation.

Use the cnfphyslnstats command to customize statistics collection on each physical line. To see the statistics available for each type of interface, refer to the actual screens for each interface, as in the subsequent examples.

Since Release 9.2, for virtual trunking, physical line statistics apply to each physical port. In the case of IMA trunks, the physical line statistics are tallied separately for each T1 port.

IMA physical line alarms are a special case. Each IMA trunk or line has a configurable number of retained links. If the number of non-alarmed lines is less than the number of retained links, the logical trunks on the IMA trunk or line are placed into major alarm.

For example, consider IMA virtual trunks 4.5-8.2 and 4.5-8.7, with the number of retained links on 4.5-8 configured to 2. If 4.5 and 4.6 go into LOS (loss of signal), physical line alarms are generated for these two physical lines. The logical trunks 4.5-8.2 do not go into alarm because the two retained links are still healthy. In this situation, the bandwidth on the logical trunks is adjusted downward to prevent cell drops, and the connections on those trunks are rerouted. If a third line goes into alarm, the logical trunks are then failed.

IMA Physical Line Statistics

The cnfphyslnstats command lets you configure the following additional physical line statistics (which support the ATM Forum-compliant Version 1.0 IMA protocol). A summary and description of these statistics follows in Table 3-28.

Table 3-28 cnfphyslnstats IMA Physical Line Statistics 

Statistics Object	Definition
IV-IMA	ICP Violations: count of errored, invalid or missing ICP cells during non-SES-IMA or non-UAS-IMA conditions.
Near End Severely Errored Seconds (SES-IMA)	Count of one-second intervals containing Š 30% of the ICP cells counted as IV-IMAs (see note 1), or one or more link defects (e.g., LOS, OOF/LOF, AIS or LCD), LIF, LODS defects during non-UAS-IMA condition.
Far End Severely Errored Seconds (SES-IMA-FE)	Count of one-second intervals containing one or more RDI-IMA defects during non-UAS-IMA-FE condition.
Near End Unavailable Seconds (UAS-IMA)	Unavailable seconds: unavailability begins at the onset of 10 contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA.
Far End Unavailable Seconds (UAS-IMA-FE)	Unavailable seconds at FE: unavailability begins at the onset of 10 contiguous SES-IMA-FE and ends at the onset of 10 contiguous seconds with no SES-IMA-FE.
Near End Tx Unusable Seconds (Tx-UUS-IMA)	Tx Unusable seconds: count of Tx Unusable seconds at the NE LSM.
Near End Rx Unusable Seconds (Rx-UUS-IMA)	Rx Unusable seconds: count of Rx Unusable seconds at the NE LSM.
Far End Tx Unusable Seconds (Tx-UUS-IMA-FE)	Tx Unusable seconds at FE: count of seconds with Tx Unusable indications from the FE LSM.
Far End Rx Unusable Seconds (Rx-UUS-IMA-FE)	Rx Unusable seconds at FE: count of seconds with Rx Unusable indications from the FE LSM.
Near End Tx No. of Failures (Tx-FC)	Count of NE Tx link failure alarm conditions.
Near End Rx No. of Failures (Rx-FC)	Count of NE Rx link failure alarm conditions.

Syntax

cnfphyslnstats <port> <line> <stat> <interval> <e|d> [<samples> <size> <peaks>]

Parameters

Parameter	Description
<port>	Specifies the port with the physical line to configure.
<line>	Specifies the physical line to configure.
<stat>	Specifies the type of statistic to enable/disable.
<interval>	Specifies the time interval of each sample. Range: 1-255 minutes
<e|d>	Enables/disables a statistic. E to enable; D to disable.
[samples]	Specifies the number of samples to collect. Range: 1-255

Attributes

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

Related Commands

dspphyslnstats, dspphyslnstathist

Example (IMA)

cnfphyslnstats 7.1

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

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 14:19 PST




Line Statistic Types




1) Bipolar Violations 37) Severely Err Secs - Path

3) Out of Frames 38) Severely Err Frame Secs

4) Losses of Signal 40) Unavail. Seconds

5) Frames Bit Errors 41) BIP-8 Code Violations

6) CRC Errors 42) Cell Framing Errored Seconds

29) Line Code Violations 43) Cell Framing Sev. Err Secs.

30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs

31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.

32) Line Parity Errors 62) Total Cells Tx to line

33) Errored Seconds - Line 69) Total Cells Rx from line

34) Severely Err Secs - Line 98) Frame Sync Errors

35) Path Parity Errors 141) FEBE Counts

36) Errored Secs - Path 143) Cell Framing FEBE Err Secs




This Command: cnfphyslnstats 7.1




Continue?

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

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 14:19 PST




Line Statistic Types




144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.

151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.

152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.




This Command: cnfphyslnstats 7.1




Continue?

------------------------------------SCREEN 3-----------------------------------

igxr03 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 14:20 PST




Line Statistic Types




215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count

216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count

217) HCS Uncorrectable Error

218) HCS Correctable Error

219) INVMUX: line violations

220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.




This Command: cnfphyslnstats 7.1





Statistic Type:




Example (OC-3)

cnfphyslnstats 14.2

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

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:31 PST




Line Statistic Types




1) Bipolar Violations 37) Severely Err Secs - Path

3) Out of Frames 38) Severely Err Frame Secs

4) Losses of Signal 40) Unavail. Seconds

5) Frames Bit Errors 41) BIP-8 Code Violations

6) CRC Errors 42) Cell Framing Errored Seconds

29) Line Code Violations 43) Cell Framing Sev. Err Secs.

30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs

31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.

32) Line Parity Errors 62) Total Cells Tx to line

33) Errored Seconds - Line 69) Total Cells Rx from line

34) Severely Err Secs - Line 98) Frame Sync Errors

35) Path Parity Errors 141) FEBE Counts

36) Errored Secs - Path 143) Cell Framing FEBE Err Secs




This Command: cnfphyslnstats 14.2





Continue? y




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

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:31 PST




Line Statistic Types




144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.

151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.

152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.




This Command: cnfphyslnstats 14.2





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:32 PST




Line Statistic Types




215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count

216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count

217) HCS Uncorrectable Error

218) HCS Correctable Error

219) INVMUX: line violations

220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.




This Command: cnfphyslnstats 14.2





Statistic Type:

Example (UXM T3/636 Trunk)

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

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:39 PST




Line Statistic Types




1) Bipolar Violations 37) Severely Err Secs - Path

3) Out of Frames 38) Severely Err Frame Secs

4) Losses of Signal 40) Unavail. Seconds

5) Frames Bit Errors 41) BIP-8 Code Violations

6) CRC Errors 42) Cell Framing Errored Seconds

29) Line Code Violations 43) Cell Framing Sev. Err Secs.

30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs

31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.

32) Line Parity Errors 62) Total Cells Tx to line

33) Errored Seconds - Line 69) Total Cells Rx from line

34) Severely Err Secs - Line 98) Frame Sync Errors

35) Path Parity Errors 141) FEBE Counts

36) Errored Secs - Path 143) Cell Framing FEBE Err Secs




This Command: cnfphyslnstats 8.1





Continue? y




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

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:41 PST




Line Statistic Types




144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.

151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.

152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.




This Command: cnfphyslnstats 8.1





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw150 TN Cisco IGX 8420 9.3.2Q Dec. 13 2000 14:42 PST




Line Statistic Types




215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count

216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count

217) HCS Uncorrectable Error

218) HCS Correctable Error

219) INVMUX: line violations

220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.




This Command: cnfphyslnstats 8.1





Statistic Type:




Example (UXM E3/530 Trunk)

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

sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 07:41 PST




Line Statistic Types




3) Out of Frames 42) Cell Framing Errored Seconds

4) Losses of Signal 43) Cell Framing Sev. Err Secs.

5) Frames Bit Errors 44) Cell Framing Sec. Err Frame Secs

6) CRC Errors 45) Cell Framing Unavail. Secs.

29) Line Code Violations 62) Total Cells Tx to line

30) Line Errored Seconds 69) Total Cells Rx from line

31) Line Severely Err Secs 98) Frame Sync Errors

32) Line Parity Errors 143) Cell Framing FEBE Err Secs

33) Errored Seconds - Line 144) Cell Framing FEBE Sev. Err. Secs.

34) Severely Err Secs - Line 151) Yellow Alarm Transition Count

38) Severely Err Frame Secs 152) Cell Framing Yel Transitions

40) Unavail. Seconds 153) AIS Transition Count

41) BIP-8 Code Violations 193) Loss of Cell Delineation




This Command: cnfphyslnstats 3.1





Continue? y




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

sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 07:41 PST




Line Statistic Types




194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.

202) Section BIP8 Err. Secs. 215) Path Unavailable Secs.

203) Line BIP24 Err. Secs. 216) Path Farend Unavailable Secs.

204) Line FEBE Err. Secs. 217) HCS Uncorrectable Error

205) Path BIP8 Err. Secs. 218) HCS Correctable Error

206) Path FEBE Err. Secs. 219) INVMUX: line violations




This Command: cnfphyslnstats 3.1





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw150 TN Cisco IGX 8420 9.3.2R Dec. 14 2000 07:42 PST




Line Statistic Types




220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.

228) INVMUX: Tx Failure Count

229) INVMUX: Rx Failure Count







This Command: cnfphyslnstats 3.1





Statistic Type:

Example (T1)

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

igxr02 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:37 PST




Line Statistic Types




1) Bipolar Violations 37) Severely Err Secs - Path

3) Out of Frames 38) Severely Err Frame Secs

4) Losses of Signal 40) Unavail. Seconds

5) Frames Bit Errors 41) BIP-8 Code Violations

6) CRC Errors 42) Cell Framing Errored Seconds

29) Line Code Violations 43) Cell Framing Sev. Err Secs.

30) Line Errored Seconds 44) Cell Framing Sec. Err Frame Secs

31) Line Severely Err Secs 45) Cell Framing Unavail. Secs.

32) Line Parity Errors 62) Total Cells Tx to line

33) Errored Seconds - Line 69) Total Cells Rx from line

34) Severely Err Secs - Line 98) Frame Sync Errors

35) Path Parity Errors 141) FEBE Counts

36) Errored Secs - Path 143) Cell Framing FEBE Err Secs




This Command: cnfphyslnstats 31.8




Continue?

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

igxr02 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:36 PST




Line Statistic Types




144) Cell Framing FEBE Sev. Err. Secs. 202) Section BIP8 Err. Secs.

151) Yellow Alarm Transition Count 203) Line BIP24 Err. Secs.

152) Cell Framing Yel Transitions 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

198) Line BIP24 211) Path BIP8 Severely Err. Secs.

199) Line FEBE 212) Path FEBE Severely Err. Secs.

200) Path BIP8 213) Line Unavailable Secs.

201) Path FEBE 214) Line Farend Unavailable Secs.




This Command: cnfphyslnstats 31.8




Continue?

------------------------------------SCREEN 3-----------------------------------

igxr02 VT Cisco IGX 8430 9.3.2V Jan. 18 2001 13:38 PST




Line Statistic Types




215) Path Unavailable Secs. 228) INVMUX: Tx Failure Count

216) Path Farend Unavailable Secs. 229) INVMUX: Rx Failure Count

217) HCS Uncorrectable Error

218) HCS Correctable Error

219) INVMUX: line violations

220) INVMUX: Severely Err. Secs.

221) INVMUX: Farend Sev. Err. Secs.

222) INVMUX: Unavailable Secs.

223) INVMUX: Farend Unavail Secs.

224) INVMUX: Tx Unusable Seconds

225) INVMUX: Rx Unusable Seconds

226) INVMUX: Farend Tx Unusable Secs.

227) INVMUX: Farend Rx Unusable Secs.




This Command: cnfphyslnstats 31.8





Statistic Type:

Example (E1)




sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:07 PST

Line Statistic Types

3) Out of Frames 198) Line BIP24

4) Losses of Signal 199) Line FEBE

5) Frames Bit Errors 200) Path BIP8

6) CRC Errors 201) Path FEBE

62) Total Cells Tx to line 202) Section BIP8 Err. Secs.

69) Total Cells Rx from line 203) Line BIP24 Err. Secs.

151) Yellow Alarm Transition Count 204) Line FEBE Err. Secs.

153) AIS Transition Count 205) Path BIP8 Err. Secs.

193) Loss of Cell Delineation 206) Path FEBE Err. Secs.

194) Loss of Pointer 207) Section BIP8 Severely Err. Secs.

195) OC-3 Path AIS 208) Section Sev. Err. Framing Secs.

196) OC-3 Path YEL 209) Line BIP24 Severely Err. Secs.

197) Section BIP8 210) Line FEBE Severely Err. Secs.

This Command: cnfphyslnstats 11.4

Continue? y






sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:07 PST

Line Statistic Types

211) Path BIP8 Severely Err. Secs.

212) Path FEBE Severely Err. Secs.

213) Line Unavailable Secs.

214) Line Farend Unavailable Secs.

215) Path Unavailable Secs.

216) Path Farend Unavailable Secs.

217) HCS Uncorrectable Error

218) HCS Correctable Error

This Command: cnfphyslnstats 11.4

cnfport (configure Frame Relay port)

Configures the parameters of a Frame Relay port. The cnfport command applies to the UFM/UFI, FRP/FRI, FRM/FRI, and FRM-2/FRP-2. (Note that a command also exists for the concentrated link between the PCS and FRM-2 or FRP-2: cnffrcport.)

During port configuration, a prompt for each parameter appears. To keep the current value of the parameter, press the Return key without typing any characters. When a parameter is not configurable for an application, the parameter appears shaded or with dashed lines.

Starting with Release 9.3.10, the ELMI (Enhanced Local Management Interface) Neighbor Discovery feature is supported on ports on the UFM. This feature serves the same purpose as the ILMI Neighbor Discovery feature. For additional information see the "ELMI Neighbor Discovery for UFM" section.

You can mix the data rate for each of the ports if the total for all ports does not exceed the maximum composite data rate that the card set supports. Table 3-29 shows the supported data rates for individual T1 and E1 lines.

Table 3-29 T1 and E1 Data Rates 

Data Rates at 56 Kbps Increments				Data Rates at 64 Kbps Increments
56	112	168	224	64	128	192	256
280	336	392	448	320	384	448	512
504	560	616	672	576	640	704	768
728	784	840	896	832	896	960	1024
952	1008	1064	1120	1088	1152	1216	1280
1176	1232	1288	1344	1344	1408	1472	1536
1400	1456	1512	1568	1600	1664	1728	1792
1624	1680	1736	1792	1856	1920	1984	2048

Table 3-30 shows the available data rates on a single, PCS user-port. For the FRP-2 and FRM-2 cards, the maximum composite data rate over the 44 logical user-ports is 1.792 Mbps.

Table 3-30 PCS Data Rates 

Data Rates in Kbps
9.6	14.4	16	19.2	32	38.4	48	56
64	112	128	168	192	224	256	280
320	336	384

For a PCS, some additional rules for assigning data rates to the 44 ports apply:

•No single user-port should have a speed greater than 384 Kbps.

•The total for each group of 11 ports should not exceed 448Kbps. The software allows higher rates, but the system may drop data if user-equipment passes data above the aggregate total of 448 Kbps.

•The port numbers for the 11-port groups are 1-11, 12-22, 23-33, and 34-44.

Syntax (basic format)

cnfport <slot.port>[.<vport>] [<parameters>]

Syntax (T1/E1 ports on UFM-C)

cnfport <slot.port> <line.DS0_range> <port queue depth> <ecn queue threshold>
<de threshold> <signaling protocol> [protocol parameters]

Syntax (unchannelized ports on UFM-U)

cnfport <slot.port> <port type> <port queue depth> <ecn queue threshold>
<de threshold> <signaling protocol> [protocol parameters]

Syntax (T1/E1 ports on FRM or FRP)

cnfport <slot.port> <port queue depth> <ecn queue threshold> <de threshold>
<signaling protocol> [protocol parameters]

Syntax (all other ports—for an FRM or FRP)

cnfport <slot.port> <speed> <port queue depth> <clocking> <de_threshold> <min-flags-bet-frames> <ECN q_threshold> <port ID> <signaling protocol y/n>
[protocol parameters]

---

Note Some parameters are mandatory for T1/E1 lines and optional for other line types. For additional information on signaling protocol see the "Signaling Protocol Timers" section.

---

Parameters

Parameter	Description
slot.port	Specifies the logical port on the FRP, FRM, or UFM-U in the format slot.port. For a T1/E1 line on an FRM or FRP, port is a logical number. For a UFM-C, the range for port is 1-250. (See the description of slot.port line in the Cisco IGX 8400 Series Reference manual.) For a Port Concentrator Shelf, port is to the logical port in the range 1-44.
port type (for a UFM-U) For port type on a PCS, see next box.	Specifies whether a port on a UFM-U is DCE or DTE. The prompt appears if the system detects a UFM-U. The default is DCE. For an FRM or FRP, "port Type" is display-only because jumper blocks on the back cards set the mode. When you use cnfport in a job, the "Enter mode (line or port)" prompt follows slot.port. Note that this mode is the interface type of the Frame Relay port rather than the mode of the UFM-U. Valid entries are HSSI, V35, X21, PORT (PORT is generically unchannelized), or LINE (LINE indicates T1 or E1). If the front card is a UFM-U, a subsequent prompt asks you to specify DCE or DTE.
port type (for a PCS) (For port type on a UFM-U, see preceding box.)	Port type for a PCS tells switch software whether the port is V.35, V.11 or V.28. Port type for a PCS does not actually configure the port: to configure the port, you must install the appropriate card in the PCS. See the port type description for the UFM-U for information on cnfport in a job.
interface type	Specifies an interface type for a Port Concentrator Shelf (PCS). This parameter appears if switch software detects a PCS. It applies to the user interface display only and not the PCS itself because system software does not detect the interface type within the PCS. To change the user-interface type, you must change a card in the PCS.
slot.port line	Specifies the UFM-C slot, port, and line number, where port can be 1-250, and line can be 1-8. Note that the maximum number of T1/E1 lines per node is 32. This maximum could be, for example, spread over 4 UFM-8C card sets that utilize all 8 lines on each back card.
speed	Specifies a port clock speed in Kbps for a 2.0 Mbps UFM, FRP, or FRM. The configured speed appears under the Configured Clock heading. The actual clock rate appears under the Measured Rx Clock heading. Note that this option does not apply to T1/E1 lines because these line types use 64 or 56 Kbps timeslots. The range of speeds according to the number of active ports is: •1 port (selected speeds, 56-2048 Kbps) •2 ports (selected speeds, 56-1024 Kbps) •3 ports (selected speeds, 56-672 Kbps) •4 ports (selected speeds, 56-512 Kbps) Refer to the table at the beginning of this command description for the available clock rates for all port combinations.
clocking	Specifies the port's clock type for HSSI, V.35, and X.21 lines. Clocking does not apply to T1, E1, or Port Concentrator lines. The clock is either normal or looped. Four combinations of clocking are available for the V.35 ports. Two combinations of clocking are available for HSSI and X.21. Note that the clock and data direction in DCE mode is the opposite of the direction for DTE mode. The possibilities are: •FRP, FRM, or UFM-U port is DCE with normal clocking (HSSI, V.35, X.21). •FRP, FRM, or UFM-U port is DCE with looped clocking (V.35 only). •FRP, FRM, or UFM-U port is DTE with normal clocking (HSSI, V.35, X.21). •FRP, FRM, or UFM-U port is DTE with looped clocking (V.35 only). For a description of looped and normal clocking, refer to the appropriate configuration guide.
port ID	Specifies the DLCI associated with the port (0-1024) {0}. A node uses this number when you add bundled connections. Otherwise, port ID can be used as a network destination number in global addressing. The port ID does not apply to T1, E1, or PCS ports.
port queue depth	Specifies the maximum bytes in the transmission queue at the UFM, FRP, or FRM port. Range: 0-65535 bytes Default: 65535 bytes
ecn queue threshold	Specifies the threshold at which the system begins to generate explicit congestion notification (BECN and FECN bits) for the port. Range: 0-65535 bytes Default: 65535 bytes
signaling protocol	Specifies the LMI operation mode. The first time you execute cnfport on a port, the command line interface displays the following options for this parameter: "none, Strata LMI, a (for Annex A), and d (for Annex D)." If you enter "a" or "d," the subsequent prompt asks if the interface is NNI. For the initial port specification and subsequent port specifications for a particular port, you can also use a single digit from the LMI definition list that follows. The total industry standard range is 0-255, but Cisco WAN Switching nodes recognize only the following (the default is internally recognized as LMI=2): LMI = 0 LMI is disabled at this port. LMI = 1 Cisco LMI and the asynchronous update process is enabled at this port. Greenwich Mean Time is also enabled. LMI = 2 LMI is disabled at this port. LMI = 3 Cisco LMI is enabled at this port, but asynchronous update process is disabled. LMI = 4 The port configuration is UNI using CCITT Q.933 Annex A parameters. LMI = 5 The port configuration is UNI using ANSI T1.617 Annex D parameters. LMI = 6 The port configuration is NNI using CCITT Q.933 Annex A parameters. LMI = 7 The port configuration is NNI using ANSI T1.617 Annex D parameters. For any Frame Relay card set that has a maximum frame length of 4510 bytes, the use and type of a signaling protocol results in a limit on the possible number of connections per port (the port here is either physical or logical). The maximum number of connections per port for each protocol is as follows: For Annex A: 899 For Annex D: 899 For Strata LMI: 562 Neither addcon nor cnfport prevents you from adding more than the maximum number of connections on a port. (You might, for example, use cnfport to specify an LMI when too many connections for that particular LMI already exist.) If the number of connections is exceeded for a particular LMI, the 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 also subsequently leads to A-bit failures in other segments of the connection path.
de threshold	Specifies the port queue depth above which the system discards frames with a set Discard Eligibility (DE) bit. Range: 0-100 percent Default: 100 percent A threshold of 100 percent disables DE for the port because a queue cannot contain more than 100 percent of its capacity.
asynchronous status	Specifies whether the node should send unsolicited LMI update messages when they appear or wait for the user-device to poll. Enter y (yes) or n (no).
polling verify timer	Specifies a Link Integrity Verification Timer heartbeat (keep-alive) period. Set the timer to 5 secs. more than the setting in the user equipment. Range: 5-30 Default: 15
error threshold	Specifies the number of failures in the monitored events that cause the keep-alive process to report an alarm. A threshold of 0 reverts to 1. A threshold greater than 10 reverts to 10. Theoretical range: 0-255 Valid range: 1-10
monitored events count	Specifies the number of monitored events for the keep-alive process. A port communication-fail condition is cleared after this number of successful polling cycles. A value of 0 reverts to 1, and a value more than 10 reverts to 10. Theoretical range: 0-255 Valid range: 1-10
communicate priority	Specifies whether the system should communicate the SNA priority of the connections to the user-device on the port. Enter y (yes) or n (no). (SNA priority is either H or L.)
upper/lower RNR threshold	Specifies the receiver not ready (RNR) thresholds. The upper threshold is the number of receiver not ready indications from the user equipment before an alarm is generated for this port. The lower RNR threshold is the number of indications from the user equipment before an alarm is cleared. Range: 1-255 Default (upper RNR threshold): 75 Default (lower RNR threshold): 25
EFCI mapping enabled	Directs the system to map the ForeSight congestion bit (which is set in the FastPackets by a trunk card) to the FECN and BECN bits on the affected PVC.
CLLM Enabled	Specifies whether the system should use CLLM over the port.
min. flags/frame	Specifies the minimum number of flags between frames when the direction of transmission is from the node to the user-equipment. Any value greater than 0 is valid on the UFM, FRP or FRM. Range (Port Concentrator Shelf): 1-16 Default: 1
OAM Packet threshold	Specifies how many OAM FastPackets must arrive from a remote NNI port before the local port generates "A-bit = 0" in the signaling protocol message to the locally attached device. A 0 disables this function. The OAM FastPacket threshold setting applies to UNI and NNI ports. The following two paragraphs provide a more detailed explanation of the A-bit and OAM FastPacket threshold usage. Range: 0-15 packets Default: 3 packets On any Frame Relay port (UNI or NNI) that is using a signaling protocol (Cisco LMI, Annex A, or Annex D), the FRP or FRM provides a Status message to the attached equipment in response to a Status Enquiry message or as an Asynchronous Update. These Status messages contain details about every PVC configured on the port. In particular, the PVC Active bit (the A-bit) represents whether a PVC is active (A-bit=1) or out of service (A-bit = 0). If the other end of the connection PVC on a UNI port, the only conditions that can cause the local Frame Relay card to send an A-bit=0 are: •The PVC is down (intentionally taken out of service) •The PVC has failed for any reason (such as a hardware failure, trunk failure with no ability to reroute, and so on) If the other end of the PVC terminates on an NNI port, one additional condition can cause the local UFM, FRP, or FRM to send an A-bit=0 to the local device: if the remote NNI port on the card receives an A-bit=0 from the remote network over the remote NNI, then the local card can propagate an A-bit=0 out the local port. The mechanism by which the remote card notifies the local card of the A-bit=0 coming from the remote network is OAM FastPackets. The local node sends one OAM FastPacket every 5 seconds for as long as the A-bit coming from the remote network is 0.
T391 link integrity timer	Specifies the interval after which the system sends Status Enquiry messages across the NNI port. Both networks do not need to have the same T391 value. Range: 5-30 seconds Default: 6 seconds On a Frame Relay NNI port, the Link Integrity Timer (T391) specifies how often the UFM, FRP, or FRM generates a Status Enquiry message to the attached network using the selected NNI signaling protocol (Annex A or Annex D). The card should receive a Status message for every Status Enquiry message it transmits. If the Frame Relay card receives either no responses or invalid responses, a Port Communication Failure results (and causes a minor alarm). Using the default values for N392 Error Threshold and N393 Monitored Events Count in an example: an error occurs when no response (or a bad response) arrives for 3 out of the last 4 Status Enquiry messages. Default (392 Error Threshold): 3 Default (N393 Monitored Events Count): 4
N392 error threshold	Specifies the number of bad or undelivered responses to Status Enquiry messages that can occur before the system records a Port Communication Failure. See the description of the link integrity timer parameter for example usage. Range: 1-10 Default: 3
N393 monitored events count	Specifies the number of Status Enquiry messages in a period wherein the system waits for responses to the enquiries. See the description of the link integrity timer parameter for example usage. Range: 1-10 Default: 4
N391 full status polling cycle	Specifies the interval at which the system sends the Full Status Report request for all PVCs across the NNI port. The Full Status reports the status of all the connections across the NNI. Range: 1-255 polling cycles Default: 10 cycles
card type	Specifies the card type when you enter the cnfport command in a job. This parameter is not available except when you specify cnfport in a job by using the addjob command. During the job specification, you enter the card type just after the slot.port during the command specification phase of addjob. Valid card types are "V.35," "X.21," "port," and "line," where "line" indicates a T1 or E1 line.
CLLM status Tx Timer	Specifies an interval for the system to send ForeSight congestion messages across the NNI. Both networks must be Cisco WAN Switching networks. Used in conjunction with the CCLM Enabled parameter. Range: 40 ms-350 ms Default: 100 ms
IDE to DE mapping	Specifies whether the destination system should map the internal DE bit (IDE) status in the FastPacket or ATM cell to the Frame Relay DE bit at the destination. Enter y (yes) or n (no). If you specify the non-standard case of CIR=0 with either addcon or cnffrcls, you must first enable IDE to DE mapping. Refer to the appropriate configuration guide for important information on setting CIR=0.
interface control template	Specifies the control leads (signal names of the wires in the port connector) and the state (whether the signal is on or off) for V.35 and X.21 physical Frame Relay ports. This template is not a configurable parameter; there is no individual prompt for it. When the parameter Interface is configured to DCE or DTE, the Interface Control Template will change. A different hardware connector pin-out with some different signal leads are used for DCE than is used for DTE. Some leads that may be displayed are: CTS-Clear To Send. Circuit in the EIA/TIA-232 specification that is activated when DCE is ready to accept data from a DTE. DSR-data set ready. EIA/TIA-232 interface circuit that is activated when DCE is powered up and ready for use. DCD-Data Carrier Detect. Signal that indicates whether an interface is active. Some interface types that may be displayed are: DCE-Data circuit-terminating equipment (ITU-T expansion). Devices and connections of a communications network that comprise the network end of the user-to-network interface. The DCE provides a physical connection to the network, forwards traffic, and provides a clocking signal used to synchronize data transmission between DCE and DTE devices. DTE-data terminal equipment. Device at the user end of a user-network interface that serves as a data source, destination, or both. DTE connects to a data network through a DCE device and typically uses clocking signals generated by the DCE.
channel speed	Specifies the bandwidth available to a logical port. The speed is 64 Kbps times the number of DS0s you specify with the channel range parameter.
line number	The number of the line, which in this context is the physical network communications channel on a backcard.
channel range	Specifies the DS0s for the T1 or E1 logical port. The value can be 1 or a contiguous combination in the range 1-24 for T1 or 1-31 for E1. For example, 7-12 indicates 6 DS0s for the port, starting with DS0 7. Before you use this command, specify the valid channel range with the addfrport command.

Attributes

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

Related Commands

upport, dnport, dspport, dspports, delport, addport

Example (IGX)

Configure UFM-C port 8.1.

cnfport 8.1 65535 65535 100 c y 15 3 4 y 75 25 3 y y 100 y 1

sw176 TN Cisco IGX 8420 9.3.a5 Apr. 27 2001 09:31 PDT




Port: 8.1 [ACTIVE ]

Interface: T1D Configured Clock: 320 Kbps

Clocking: None Measured Rx Clock: None




Port ID - Min Flags / Frames 1

Port Queue Depth 65535 OAM Pkt Threshold 3 pkts

ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec

DE Threshold 100 % N391 Full Status Poll 6 cyl

Signalling Protocol Cisco LMI EFCI Mapping Enabled Yes

Asynchronous Status Yes CLLM Enabled/Tx Timer Yes/100 msec

T392 Polling Verif Timer 15 IDE to DE Mapping Yes

N392 Error Threshold 3 Channel Speed 64

N393 Monitored Events Count 4 Line Number 1

Communicate Priority Yes Channel Range 1-5

Upper/Lower RNR Thresh 75%/ 25%

Last Command: cnfport 8.1 65535 65535 100 c y 15 3 4 y 75 25 3 y y 100 y 1

Example

Configure a UFM-U card.

cnfport 9.1DCE 256 NORMAL 0 65535 65535 100 n N N Y 1

sw108 TN Cisco IGX 8420 9.3.u2 May 23 2001 15:27 GMT




Port: 9.1 [ACTIVE ]

Interface: V35 DCE Configured Clock: 256 Kbps

Clocking: Normal Measured Rx Clock: 256 Kbps




Port ID 0 Min Flags / Frames 1

Port Queue Depth 65535 OAM Pkt Threshold 3 pkts

ECN Queue Threshold 65535 T391 Link Intg Timer 10 sec

DE Threshold 100 % N391 Full Status Poll 6 cyl

Signalling Protocol None EFCI Mapping Enabled No

Asynchronous Status No CLLM Enabled/Tx Timer No/ 0 msec

T392 Polling Verif Timer 15 IDE to DE Mapping Yes

N392 Error Threshold 3 Interface Control Template

N393 Monitored Events Count 4 Lead CTS DSR DCD

Communicate Priority No State ON ON ON




Last Command: cnfport 9.1 DCE 256 NORMAL 0 65535 65535 100 n N N Y 1

ELMI Neighbor Discovery for UFM

Starting with Release 9.3.10, Enhanced Local Management Interface (ELMI) provides a protocol to monitor the status of permanent virtual connections between two Cisco communication devices. Through ELMI for example, the network management system (NMS) becomes aware of the existing connectivity between an IGX 8400 switch and a Cisco IOS router running ATM or Frame Relay.

The enhanced version of ELMI on IOS is called ELMI-AR (Address Resolution). Note that, since IGX switches mainly are connected to routers that run IOS, you must implement the same protocol on IOS, too.

The ELMI protocol enhancements for the UFM serves the same purpose as the ILMI enhancements for the UXM, and implements similar mechanisms to enable Neighbor Discovery. While ILMI Neighbor Discovery works with ATM links, ELMI Neighbor Discovery works with Frame Relay links. ELMI Neighbor Discovery is a Cisco standard, while ILMI is based on the standard ILMI protocol.

Use parameter option 53 from the cnfnodeparm command to configure the ILMI Management IP address. The Management IP address is used by the NMS application to access the IGX or the ATM device. Depending upon your network set up, you can configure the IGX to send either the LAN IP address or Network IP address as part of the neighbor information exchange with the attached ATM device. Enter 0 for LAN IP address, or 1 for Network IP address. The IGX switch default is the network IP address.

Once the parameter is set in cnfnodeparm, enable Neighbor Discovery using the cnfport command. Set the Advertise Interface parameter to "Yes" to enable the feature.

Signaling Protocol Timers

This section introduces the implementation of two signaling timers and related parameters you can specify through the cnfport command.

Periodically, devices use signaling to request the status of other, connected devices or networks. The signaling can be a simple confirmation of the other device's existence or more detailed information, such as the DLCIs, bandwidth, and state of all PVCs. The signaling described here occurs between:

•The user-equipment and a Frame Relay port across the user-to-network interface (UNI)

•Frame Relay ports in the network across the network-to-network interface (NNI)

Periodically, Frame Relay ports within the network transmit a Status Enquiry and wait for a Status response. These exchanges occur across the UNI and the NNI. At the UNI, the user-equipment periodically sends a series of Status Enquiries and awaits a Status response for each enquiry. At the NNI of any network, a Frame Relay port can generate Status Enquiries and, at alternate times, receive Status Enquiries. In this way, the signaling between networks mirror each other. ( Figure 3-19 shows the three possible exchanges.) The timers for Status Enquiry and Status Response and other, related parameters are the:

•Link integrity timer—the time period between each Status Enquiry that either the user-equipment or a Frame Relay port in the network generates

•Polling verification timer—a time period in which a Frame Relay port waits for a Status Response to a Status Enquiry that the port generated

•Error threshold—the number of missing or erroneous events that triggers a Port Communication Failure

•Monitored events count—the number of events in a polling cycle

•Full status polling cycle—a polling cycle in which the port that has sent the Status Enquiry waits for detailed status information

In the preceding list, an event is either a Status Enquiry or a Status Response. The meaning of the event depends on whether the link integrity timer or the polling verification timer is waiting for the event. The link integrity timer waits for Status Responses. The polling verification timer waits for Status Enquiries.

Most Status Enquiries contain only a sequence number. After sending these simple Status Enquiries, the polling device checks for the sequence number. Periodically, a full status polling cycle takes place, in which the polling device waits for all applicable information, such as the status of all connections that cross the NNI. For signaling across the UNI, the Frame Relay Forum has recommended a full status polling cycle at every sixth polling cycle. The Frame Relay Forum has not recommended a frequency for the NNI. The cnfport command lets you select a frequency in the range of once every 1-10 polling cycles.

The Frame Relay port or user-device counts a user-specified number of errors out of a user-specified number of attempts before it signals a Port Communication Failure. These parameters are the error threshold and the monitored events count, respectively. The defaults for these parameters are 3 and 4, respectively. To use the defaults in an example: if 3 out of 4 events are either missing or erroneous within the specified time period, the port signals a Port Communication Failure (a minor alarm).

An event has a user-specified amount of time to arrive. The allowed time period for the arrival of a valid event is the number of seconds you assign to a timer. If an enquiry or response is missing or bad within the timer value, the event is failed. Again, using all default values in an example: if the polling verification timer is 15 seconds and no Status Enquiry arrives within that time, the port records a missing Status Enquiry. If no Status Enquiry arrives during the next two 15-second periods, the port signals a Port Communication Failure. In the UNI example in the figure, the third Status Enquiry does not arrive. Note that each time a Status Enquiry arrives, the polling verification timer restarts counting at 0 seconds rather than waiting until the specified number of seconds has elapsed.

Whether the port is on a UNI or NNI, the polling verification timer setting must be longer than the link integrity timer. (Refer to the cnfport parameters table for values.) You cannot set the link integrity timer for the user-equipment with cnfport. Usually, the link integrity timer on user-equipment is 10 seconds, which you can verify by executing dspportstats and counting the number of seconds between statistical updates. On the NNI, you can set both timers (they use either Annex A or Annex D).

Figure 3-19 Signaling Protocol Timing

The data rates available with the 1 Mbps FRI are shown in Table 3-31.

Table 3-31 Data Rates for the 1-Mbps FRI 

Port Data Rates in Kbps for 1Mbps FRI
1024	512	256	128
896	448	224	112
768	384	192	64
672	336	168	56

The rules for assigning data rates to the four ports when using the 1 Mbps FRI are:

•If you assign a data rate of 672 Kbps or higher on any port, you cannot use any other port.

•If you assign a data rate of between 384 Kbps and 512 Kbps to any port, you can specify a second port with an available data rate of 512 Kbps or less.

•If you assign a data rate of 336 Kbps to any port, you can specify two other ports for any available data rates of 336 Kbps or less.

If the data rate of any port does not exceed 256 Kbps, you can specify all four ports with any available data rates of 256 Kbps or less.

cnfport (configure ATM port)

Configures the parameters of an ATM port on the IGX or BPX. The command is used to:

•configure an ATM port on the UXM in the IGX.

•configure the internal ATM port on the Universal Router Module (URM) in the IGX.

•configure an ATM port on the ASI and BXM cards in the BPX.

During port configuration, a prompt for each parameter appears. To keep the current value of the parameter, press the Return key without typing any characters. When a parameter is not configurable for an application, the parameter appears shaded or with dashed lines.

For additional information see the "Traffic Shaping on the UXM and URM" section, the "Traffic Shaping on the BXM" section, and the "Virtual Ports" section.

The cnfport command supports the Universal Router Module (URM) on the IGX 8400. The URM provides IOS-based voice support and basic routing functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router. The external interface type of the URM ATM port is defined as internal. The internal interface is a logical internal ATM port. The internal ATM port speed is equivalent to an OC-3 port. The default port configuration is the same as the default configuration for a UXM port. The port type is UNI with no protocol. The port cannot be configured as NNI, and the protocol cannot be configured as LMI, as the embedded router does not support the LMI protocol. Switch software reserves the VPI.VCI pair 0.1023 for the internal IPC mechanism used for UXM to router communication.

In Release 9.3.30, the cnfport command supports phase one of the Automatic Routing Management to PNNI migration. You use the cnfport command to set the BXM port type as Enhanced UNI (EUNI) or Enhanced NNI (ENNI) and to enable the Extended LMI (XLMI) protocol and LMI Neighbor Discovery feature (using the advertise interface information parameter). This port configuration is required to support the Extended PVC (XPVC) segment that links the BPX to the adjacent MGX in the hybrid AR-PNNI, or AR-PNNI-AR, network. See the "Automatic Routing Management to PNNI Migration" section for more information.

Parameters

Parameter	Description
slot.port[.vport]	Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI, UXM, or URM cards.
port type	Specifies whether the cell header format is NNI, UNI, EUNI, or ENNI. UNI is the default. NNI cannot be configured on the URM embedded UXM port. Specifies the ATM cell header format. Values are: •UNI (default value) •NNI Additional values to support Automatic Routing Management-PNNI links in a hybrid network, BPX only: •Extended UNI (EUNI) •Extended NNI (ENNI) With EUNI/ENNI port types, all new connections are programmed as "non-segment". These non-segment connections do not terminate OAM segment loopback cells. EUNI/ENNI port configuration is allowed only when the XLMI protocol is enabled on the BXM port. EUNI/ENNI port types cannot be configured on ports with existing connections. Only the following combinations are supported: •UNI to EUNI •NNI to ENNI ENNI/EUNI is also support for the BXM-E. If the port type is UNI and the port type required is ENNI, you must first provision the port as NNI, then as ENNI. Note Release 9.3.30 Switch Software disables FCES and Policing on the PVC endpoint, which is terminating on the XLMI link.
metro data cell header	Specifies whether the metro data cell header type is used (ASI-T3 cards only).
VPI Range	BPX only: VPI Range is configurable on Virtual Ports and defaults to 0-255/4095 for Physical Ports (based on UNI/NNI type). The VPI Range cannot overlap with any other VPI Range on the physical interface. The range for EUNI port types is the same as for UNI (0-255). The range for ENNI port types is the same as for NNI (0-4095).
Bandwidth	BPX only: Bandwidth is configurable on all ports. For Virtual Ports, this parameter specifies the maximum bandwidth available for a Virtual Port. Each port has this parameter configurable. Connections within the Virtual Port may overbook the bandwidth if CAC Override is enabled, but the actual throughput will never be allowed to exceed the Virtual Port bandwidth. Note Changing the line framing for BXM-T3 cards from PLCP to HEC no longer automatically changes the port's bandwidth to the new maximum. It merely raises the upper limit for the port's bandwidth. After changing the framing, you must use cnfport to increase the port's bandwidth, and cnfrsrc to increase the port's Automatic Routing Management bandwidth (PVC Max Bandwidth).
CAC Reserve	BPX only: CAC Reserve is configurable on all ports, but only valid if CAC Override is disabled. This parameter specifies the amount of Automatic Routing Management Port Bandwidth not available for booking by connections if CAC Override is disabled. If CAC Override is enabled, overbooking is permitted. The purpose of this parameter is to reserve some bandwidth to handle bursts of traffic without cell discards.
shift h | n	Specifies whether a one-byte shift on the HCF field of the cell header occurs. Changing the HCF field for a physical port will affect all virtual ports supported on the physical port. The choice of H (shift) or N (no shift) depends on whether the ATM cloud includes non-Cisco WAN Switching nodes and whether virtual trunking is in operation: •You typically select H (the default, or shift on) if the cloud includes non-Cisco WAN Switching nodes or if only a physical trunk is configured for the ASI port. •You typically select N (shift off) if virtual trunks are configured and the ATM cloud consists of Cisco WAN Switching nodes only. For BPX or IGX ports performing virtual trunking within an ATM cloud to external Cisco equipment, ports should be configured to shift on (that is, shift H) for BNI cards; BXM ports should typically be configured to shift off (shift N). Note For UXM cards, you cannot configure the Shift parameter—the Shift setting is always N, or shift off. For example, if the public ATM cloud consists of BPX nodes, the access points to the cloud might be ASI ATM UNI ports. Because the cells transmitted to the ASI trunk interface are coming from a Cisco device, for example, a BNI card, the 16 VCI bits have already been left-shifted by four (4) bits and contain 12 bits of VCI information and four (4) bits of ForeSight information. Therefore, the ASI cards at either end of the cloud should be configured to not shift (that is, shift off). In this case, you would configure shift N on the ASI port. If the ATM cloud consists of non-Cisco nodes, then the 12 VCI bits + 4 ForeSight bits in the cells coming from the BNI card in the BPX are then passed through untouched as 16 VCI bits. Because it is a non-Cisco network, the ForeSight bits are ignored. Make sure that you set the HCF field correctly for your network configuration before you add connections. For example, if you are acting as a service provider, and one of your customers wants to configure virtual trunking through the network, if your ports have been previously configured with the incorrect HCF shift field setting, you may need to go back and delete all the connections from each port, configure the port, and add the connections again. Below are guidelines on how to set the Shift parameter when using BNI virtual trunking through a cloud of Cisco equipment using BXMs, and a cloud using ASIs and BNIs. Also shown is how to set the Shift parameter when using either BXM or UXM virtual trunking through a cloud of Cisco equipment (BXM cards), and a cloud of ASIs and BNIs.
%util	Enables/disables percent utilization. This parameter supports ATM VBR/ABR fairness for ASI terminated connections and applies to only VBR and ABR connections. To change the %util status of a port, no connections can be currently terminating on the port. Therefore, if connections terminate on the port, they must be deleted before cnfport execution then re-added after execution of cnfport. The port queue bandwidth with %util feature disabled is: •For ABR connections Port Queue BW = sum (MCR) •For VBR connections Port Queue BW = sum (PCR) •For CBR connections Port Queue BW = sum (PCR) When the %util feature is enabled, the port queue bandwidth is calculated for ABR and VBR connections as follows: for ABR connections, the port queue bandwidth is the sum of a percentage of the MCRs for the connections terminating on the port; for VBR connections, the port queue bandwidth is the sum of a percentage of the PCRs for connections terminating on the port. The feature is not applied to CBR connections. In summary, the port queue bandwidth with feature %util enabled is: •For ABR connections Port Queue BW = sum (MCR * %util) •For VBR connections Port Queue BW = sum (PCR * %util) •For CBR connections Port Queue BW = sum (PCR) For virtual ports, parameter can be set to Enable or Disable and is only pertinent to the specific virtual port.
CAC Override	Controls the allocation of bandwidth on a port. If enabled, connections are allowed to be added to a port even if the bandwidth requirements exceed the port capacity. If disabled, the bandwidth requirements of all connections on the port will not exceed the port capacity.
protocol	Specifies the use of either an LMI protocol, an ILMI protocol, an IXLMI protocol (BXM only) or no specified protocol. No specified protocol is the default. LMI cannot be configured on the URM. When the protocol is enabled on a virtual port, ILMI processing is done only on the BXM card. You cannot configure the protocol to run on the controller card (BCC) with virtual ports. The ILMI configuration performed on one virtual port applies to all virtual ports on the same physical interface. The ILMI Neighbor Discovery feature on a BXM interface with virtual ports is supported on BPX but not yet supported by CWM. Note The cnfport command prevents disabling ILMI protocol on a port interface if a VSI ILMI session is active on a VSI partition of the port interface. Values for protocol are one of the following: N-(NONE) L-(LMI) I-(ILMI) XL-(XLMI) The default LMI/XLMI parameters are: •VPI for LMI/XLMI connection: 0 (3 if the protocol is XLMI) •VCI for LMI/XLMI connection: 31 •LMI Polling Enable?: N •LMI Status Enquiry Timer (T393): 10 seconds •LMI Update Status Timer (T394): 10 seconds •LMI Polling Timer (T396): 10 seconds •LMI Status Enquiry Retry (N394): 5 •LMI Update Status Retry (N395): 5 Note In order to enable the migration topology discovery feature, set: •Protocol to XL •VPI to 3 •VCI to 31 •Polling to Yes •Protocol on the Card to Yes •Advertise Interface Information to Yes
protocol (cont.)	The default ILMI parameters are: •VPI for ILMI connection: 0 •VCI for ILMI connection: 16 •ILMI Address Registration Enable?: N •ILMI Polling Enable?: N •ILMI Trap Enable?: N •ILMI T491 Polling Interval: 30 seconds •ILMI N491 Error Threshold: 3 •ILMI N492 Event Threshold: 4 Note An IMA configuration will display the same protocol values as shown above.
Protocol by Card	For the BPX, defines the card that runs the LMI/ILMI protocol. The LMI/ILMI protocol can run on either the interface card (BXM) or the controller card. Values are Y/N. The default is N. •Y - selects the interface card to run the LMI/ILMI protocol •N - selects the controller card to run the LMI/ILMI protocol This parameter is supported on BXM interfaces configured with virtual ports. The setting of this parameter on one virtual port applies to all virtual ports on the same physical interface. This parameter is automatically defaulted to Y when the XLMI protocol is selected. The XLMI protocol runs only on the BXM interface card. Note For a BXM interface configured with virtual ports, the ILMI protocol runs only on the card. The protocol is blocked from running on the BCC.
Protocol run on the card	For the IGX, defines the card that runs the ILMI protocol. This must be set to Y for XLMI provisioning support. The ILMI protocol can run on the interface card (UXM and URM) or the controller card. Values are Y/N. The default is Y. •Y - selects the interface card to run the ILMI protocol •N - selects the controller card to run the ILMI protocol This parameter is applicable only when the ILMI protocol is selected and the card supports the LMI/ILMI protocol. Note For the URM, the ILMI protocol runs only on the card. The protocol is blocked from running on the NPM.
Advertise Interface Information	The advertise interface information parameter defines whether the interface is authorized to advertise its interface information. Values are Y/N. The default is Y. •Y - the switch sends its topology information (such as, the switch management IP address and Interface Name) to its neighbor. •N - the switch does NOT send its topology information to its neighbor. Instead, the switch sends 0.0.0.0 as the management IP address and a NULL string as Interface Name to the neighbor The user is prompted for this parameter when Protocol is ILMI or XLMI, Protocol by Card (BPX) or Protocol run on the card (IGX) is set to Y, and the interface card supports the Neighbor Discovery feature. The setting of this parameter does not affect the incoming neighbor's topology information. If the neighbor sends its topology information to the switch, the switch processes and stores the information. The neighbor's topology information is displayed using the dspnebdisc command. Note The ILMI Neighbor Discover feature on a BXM interface with virtual ports is supported on the BPX but not yet supported on CWM.
ILMI Reset Flag	BXM only. This indicates whether the ILMI session is to be reset when a PNNI controller is added. The default is Yes.
VC Shaping	IGX ports only. Specify one of the following: Yes—Applies egress traffic shaping to each VC. No—Does not apply egress traffic shaping to each VC. In previous releases the cnfln command was used to enable or disable VC shaping on ATM ports in the IGX. The cnfport command is now used to configure VC shaping. This change applies to all ATM ports in the IGX, i.e., UXM and URM ports. Refer to Traffic Shaping on the UXM and URM and Traffic Shaping on the BXM for more information about this topic.
F4-F5 Mapping	BXM only. Enables/disables the F4 to F5 Mapping feature. Values are "Y" to enable, "N" to disable. The default value is "N". You can enable the feature only when the number of required F4-F5 channels are available. The cnfport and dspport commands display the number of F4-F5 channels on the port. If F4-F5 mapping is enabled, the field "F4-F5 Used Channels" is displayed. If F4-F5 mapping is disabled, the field "F4-F5 Reqd Chans" is displayed. F4-F5 mapping can not be enabled on ports which have VCCs provisioned with a VCI value of less than 33.

Attributes

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

Related Commands

upport, dnport, dspport, dspports, delport, addport

Example

(BPX) config port 1.6 of a BXM.

cnfport 1.6 353208 UNI H Y L 0 31 Y 10 10 10 5 5 N 0 N Y

hugh TN Cisco BPX 8620 9.3.30 Aug. 13 2001 12:49 PDT




Port: 1.6 [FAILED ] Bandwidth/AR BW: 353208/353208

Interface: LM-BXM CAC Override: Enabled

VPI Range: 0 - 255 CAC Reserve: 0

Type: UNI %Util Use: Disabled

Shift: SHIFT ON HCF (Normal Operation)

SIG Queue Depth: 640 Port Load: 0 %

F4-F5 Mapping: Yes F4-F5 Used Chans: 1

Protocol: LMI Protocol by Card: Yes

VPI.VCI: 0.31

LMI Polling Enabled: Y

T393 Status Enquiry Timer: 10

T394 Update Status Timer: 10

T396 Polling Timer: 10

N394 Max Status Enquiry Retry: 5

N395 Max Update Status Retry: 5

Last Command: cnfport 1.6 353208 UNI H Y L 0 31 Y 10 10 10 5 5 N 0 N Y





Next Command:

Example

(BPX) Configure BXM port 2.3 to support an Extended PVC (XPVC) segment in a hybrid AR-PNNI network. The configuration is carried out in two steps:

•First Step: Configure BXM port 2.3 for the Extended LMI (XLMI) protocol and enable the LMI Neighbor Discovery feature.

•Second Step: Configure the Enhanced UNI (EUNI) port type.

cnfport 1.1 353208 UNI H N XL 3 31 Y 10 10 10 5 5 N 0 N Y Y

sw252 TRM Cisco BPX 8620 9.3.e6 Aug. 23 2001 15:20 PST




Port: 1.1 [ACTIVE ] Bandwidth/AR BW: 353208/353208

Interface: LM-BXM CAC Override: Enabled

VPI Range: 0 - 255 CAC Reserve: 0

Type: UNI %Util Use: Disabled

Shift: SHIFT ON HCF (Normal Operation)

SIG Queue Depth: 640 Port Load: 0 %

F4-F5 Mapping: No F4-F5 Reqd Chans: 0

Protocol: X-LMI Protocol by Card: Yes

VPI.VCI: 3.31 Advertise Intf Info: Yes

LMI Polling Enabled: Y

T393 Status Enquiry Timer: 10

T394 Update Status Timer: 10

T396 Polling Timer: 10

N394 Max Status Enquiry Retry: 5

N395 Max Update Status Retry: 5

Last Command: cnfport 1.1 353208 UNI H N XL 3 31 Y 10 10 10 5 5 N 0 N Y Y






cnfport 1.1 353208 EUNI H N XL 3 31 Y 10 10 10 5 5 N 0 N Y Y

sw252 TRM Cisco BPX 8620 9.3.e6 Aug. 23 2001 15:20 PST




Port: 1.1 [ACTIVE ] Bandwidth/AR BW: 353208/353208

Interface: LM-BXM CAC Override: Enabled

VPI Range: 0 - 255 CAC Reserve: 0

Type: E-UNI %Util Use: Disabled

Shift: SHIFT ON HCF (Normal Operation)

SIG Queue Depth: 640 Port Load: 0 %

F4-F5 Mapping: No F4-F5 Reqd Chans: 0

Protocol: X-LMI Protocol by Card: Yes

VPI.VCI: 3.31 Advertise Intf Info: Yes

LMI Polling Enabled: Y

T393 Status Enquiry Timer: 10

T394 Update Status Timer: 10

T396 Polling Timer: 10

N394 Max Status Enquiry Retry: 5

N395 Max Update Status Retry: 5

Last Command: cnfport 1.1 353208 EUNI H N XL 3 31 Y 10 10 10 5 5 N 0 N Y Y





Next Command:

Example

(IGX) Configure port 25.1 of a URM.

cnfport 25.1 N i 10 16 y y 30 3 4 y y 200 0 Y y y

bolger TN Cisco IGX 8430 9.3.3o May 15 2001 19:34 PST




Port: 25.1 [ACTIVE ]

Interface: INTERNAL CAC Override: Disabled

Type: UNI %Util Use: Enabled

Speed: 353208 (cps) GW LCNs: 200

SIG Queue Depth: 640 Reserved BW: 0 (cps)

Alloc Bandwidth: 353208 (cps) VC Shaping: Enabled

Protocol: ILMI Protocol run on the card: Yes

VPI.VCI: 10.16 Advertise Intf Info: Yes

ILMI Polling Enabled Y

Trap Enabled Y

T491 Polling Interval 30

N491 Error Threshold 3

N492 Event Threshold 4




Last Command: cnfport 25.1 N i 10 16 y y 30 3 4 y y 200 0 Y y y

Example

(IGX) Configure IMA port 8.1 of a UXM.

cnfport 8.1 Y I 10 16 Y Y 30 3 4 Y Y 200 0 Y Y Y

bolger TN Cisco IGX 8430 9.3.3o May 15 2001 19:35 PST

Port: 8.1 [ACTIVE ]

IMA Port Grp: 1-2

Interface: E1-IMA CAC Override: Disabled

Type: NNI %Util Use: Enabled

Speed: 8905 (cps) GW LCNs: 200

SIG Queue Depth: 640 Reserved BW: 0 (cps)

Alloc Bandwidth: 8905 (cps) VC Shaping: Enabled

Protocol: ILMI Protocol run on the card: Yes

VPI.VCI: 10.16 Advertise Intf Info: Yes

ILMI Polling Enabled Y

Trap Enabled Y

T491 Polling Interval 30

N491 Error Threshold 3

N492 Event Threshold 4




Last Command: cnfport 8.1 Y I 10 16 Y Y 30 3 4 Y Y 200 0 Y Y Y

Automatic Routing Management to PNNI Migration

With Release 9.3.30, you use the cnfport command to provision a BXM port to support the XPVC segment that links the Automatic Routing Management BPX's BXM to the adjacent PNNI MGX's AXSM in the hybrid AR-PNNI network.

EUNI/ENNI Port Types

Release 9.3.30 introduces two new BXM port types: Enhanced UNI (EUNI) and Enhanced NNI (ENNI). With EUNI/ENNI ports types, all new XPVC connections added to the port are programmed as "non-segment". Non-segment connections to NOT terminate OAM segment loopback cells. This allows the OAM cells to start from an edge of the AR-PNNI network and traverse through multiple XPVC segments for end-to-end connection testing. Note that in the AR-PNNI hybrid network, UNI/NNI connections continue to be programmed as segment. Segment connections terminate OAM segment loopback cells.

The EUNI/ENNI port type configuration is required on each junction of the AR-PNNI, or AR-PNNI-AR, network and on both sides of each XPVC segment. Both the AR BXM and the PNNI AXSM port must be either EUNI or ENNI.

The cnfport command allows EUNI/ENNI port type configuration only when the XLMI protocol is enabled on the BXM port. EUNI/ENNI port types are only allowed on BXM ports with no existing connections. If the port has existing connections, cnfport blocks selection of the EUNI/ENNI port type.

The cnfport command only supports the following port type configuration combinations:

•UNI to EUNI

•NNI to ENNI

If the port type is UNI (the default port type) and the required port type is ENNI, you must first configure the port as NNI, then as ENNI. The CLI prompt specifies the combinations allowed.

The VPI range and default for the EUNI port type is the same as for the UNI port type (0-255). The VPI range and default for the ENNI port type is the same as for the NNI port type (0-4095). VSI partition and virtual ports are not supported on EUNI/ENNI port types.

XLMI Protocol and LMI Neighbor Discovery

Release 9.3.30 introduces a new BXM protocol: Extended LMI (XLMI). The XLMI protocol supports LMI Neighbor Discovery and XPVC status update in the hybrid AR-PNNI network. XLMI is only supported over an AR-PNNI link, and it only runs on the BXM interface card.

The XLMI protocol cannot be enabled if there are existing connections on the BXM port. To enable the XLMI protocol, select the "XL" value for the Protocol parameter. When the XLMI protocol is enabled, cnfport sets the default values for the following parameters:

•Protocol by Card: Y. The XLMI protocol cannot run on the BCC controller card.

•Control VC: VPI = 3/VCI = 31. This configuration is required for XLMI.

•LMI Polling Enabled: N. (Although the default is N, set this parameter to Y for the LMI Neighbor Discovery feature)

•T393 Status Enquiry Timer: 10 seconds

•T394 Update Status Timer: 10 seconds

•T396 Polling Timer: 10 seconds

•N394 Max Status Enquiry Retry: 5 seconds

•N395 Max Update Status Retry: 5 seconds

The XLMI protocol cannot be enabled or disabled if there are existing connections on the port. On ports with no connections, a warning is displayed when XLMI is disabled, and you are asked to confirm the action. If the disable is confirmed, the neighbor AXSM's information, if any, is deleted from the port and the CWM is notified.

To enable the LMI Neighbor Discovery feature, set LMI Polling to "Y" and the Advertise Interface Information parameter to "Y." When LMI Neighbor Discovery is enabled, the BXM in the Automatic Routing Management network and the AXSM in the PNNI network exchange topology information. This information includes IP address and Interface Name. The BXM reports the AXSM's neighbor information to the BCC, and the BCC reports it to the CWM.

Use parameter option 56 from the cnfnodeparm SuperUser command to configure the Management IP address to be sent to the AXSM as part of the neighbor information exchange with the AXSM. You can configure the BPX to send either the LAN IP address or Network IP address. Enter 0 for LAN IP address, or 1 for Network IP address. The default is the network IP address.

When the Advertise Interface Information is set to "N," the BXM does not send topology information to the AXSM. However, the setting of this parameter does not affect the neighbor's information. If the neighbor's information is available, the BPX reports it to the CWM. When an LMI session is downed, the BXM resets the neighbor's information to default values. The neighbor's IP address is set to NULL and the Interface Name is set to NULL string.

With Release 9.3.30, the cnfport command performs feature mismatch verification when BXM cards are replaced. If the replacement card does not support the LMI Neighbor Discovery feature, mismatch is declared under the following conditions.

1. For stand-alone BXM card replacement, mismatch is declared if the original BXM card supports LMI Neighbor Discovery and at least one port is configured for LMI Neighbor Discovery.

2. For card replacement in a Y-redundant BXM pair, mismatch is declared if the original card pair supports LMI Neighbor Discovery and at least one port is configured for LMI Neighbor Discovery.

ILMI Neighbor Discovery

The ILMI Neighbor Discovery feature is supported on ports (not virtual ports) on both the UXM and BXM cards. This feature enables a network management system, such as Cisco WAN Manager or CiscoWorks 2000, to discover other attached ATM devices, such as Cisco ATM routers or switches. The attached devices also must support ILMI Neighbor Discovery for this feature to work.

The ILMI Neighbor Discover feature on a BXM interface with virtual ports is supported on the BPX but not yet supported on CWM.

When the Advertise Interface Information parameter is enabled on a port, the BPX or IGX and the attached ATM device exchange their management IP addresses and other interface information using the ILMI protocol. The exchanged information consists of the following:

•atmfMyIfName: physical interface name

•atmfMyIfIdentifier: Interface identifier

•atmfMyIpNmAddress: Management IP Address, either the LAN IP or network IP.

•atmfMySysIdentifier: System Identifier, a 6-byte string read from the BPX NOVRAM, or if not available, the default value is "000001"

Use parameter option 56 (BPX) or 53 (IGX) from the cnfnodeparm SuperUser command to configure the ILMI Management IP address. The Management IP address is used by the network management system (NMS) to access the BPX, IGX, or attached ATM device. Depending upon your network set up, you can configure the BPX or IGX to send either the LAN IP address or Network IP address as part of the neighbor information exchange with the attached ATM device. Enter 0 for LAN IP address, or 1 for Network IP address. The default is the network IP address for the BPX or and LAN IP address for the IGX.

While the method for configuring ILMI Neighbor Discovery is the same for the BXM and the UXM, it works a little bit differently for the URM. The URM card has two parts: an embedded router and an embedded UXM port. The router runs Cisco IOS and must have its IP address configured with the router IOS command line interface accessible via an IOS console port located on the backcard of the URM card. Configure the router protocol to ILMI. The UXM port on the URM card must be configured with the IGX command line interface. Set the protocol to ILMI and enable the Neighbor Discovery feature. With this configuration, the Management IP address of the embedded router is reported to the URM embedded UXM via ILMI.

Once the parameter is set in cnfnodeparm, enable the Neighbor Discovery feature using the Advertise Interface Information parameter from the cnfport command. Set the parameters that follow, depending upon the switch.

Options that must be set for a BXM port are shown in Table 3-32.

Table 3-32 cnfport—BXM Parameters to Set for ILMI Neighbor Discovery 

Parameters	Value
Protocol	ILMI
Protocol by Card	Yes
Advertise Interface Information	Yes
ILMI Polling Enabled	Yes

Options that must be set for a UXM port are shown in Table 3-33.

Table 3-33 cnfport—UXM Parameters to Set for ILMI Neighbor Discovery

Parameters	Value
Protocol	ILMI
Protocol Run On The Card	Yes
Advertise Interface Information	Yes
ILMI Polling Enabled	Yes

"Protocol run on the card" or "Protocol By Card" is prompted only when the protocol is ILMI and the card supports ILMI on the card. The "Advertise Interface Information" parameter is prompted only when "Protocol run on the card" or "Protocol By Card" is set to Yes.

The switch always processes the neighbor's management IP address and IfName.Use the dspnebdisc command to display all the neighbor's information discovered by the BPX or the IGX via the ILMI Neighbor Discovery procedure.

The cnfport command, in addition to other configuration commands, performs mismatch verification on the BXM and UXM cards. For example, the cnfport command verifies that the Y-cabled redundant cards both have LMI/ILMI configured.

Refer to "Feature Mismatching" in the BPX 8600 Series Installation and Configuration. The Feature Mismatching capability will not mismatch cards unless the actual feature has been enabled on the card. This allows for a graceful card migration from an older release.

Traffic Shaping on the UXM and URM

The UXM and URM cards support the VC traffic shaping feature. VC traffic shaping shapes each connection by scheduling cells using the WFQ (Weighted Fair Queueing) technique to ensure conformance to the service provider's requirements. In general, traffic shaping provides a tight control on each connection's CDV in order to meet carrier requirements. The feature also prevents domination of bandwidth resources by any one connection.

On the UXM and URM, traffic shaping is configured on a per port basis. Once the traffic shaping parameter is turned on, all connections added afterward will have traffic shaping on. Refer to the Cisco WAN Switch Software Release 9.2 release notes for additional information on traffic shaping.

Traffic Shaping on the BXM

Traffic shaping lets you choose whether to have VC scheduling performed to your CBR, VBR, UBR, or ABRSTD with VSVD and without FCES traffic streams. You can configure the traffic shaping (which involves weighted fair queuing) option on each BXM interface. In release 9.3.05 onward, traffic shaping is enabled/disabled per QoS by using the cnfportq command.

Traffic shaping, and all traffic pertaining to the QoS for this release, is performed on a per-port basis. When a particular QoS is enabled, all traffic exiting the port is subject to the VC scheduling based on the appropriate service parameters you provision. When a particular port is configured to perform traffic shaping, all ATM cells, regardless of class of service, pass through the VC queues before leaving the card. When a traffic class is not configured for traffic shaping, its connections circumvent the VC queues and are scheduled by the Qbins.

No connections should exist on the port before changing the port traffic shaping parameter. If there are existing connections when the port traffic shaping parameter is toggled, then these connections will not be updated unless the card is reset, connections are rerouted, a switchcc occurs, or you modify the connection parameters. Also, traffic shaping is not enabled on a VSVD endpoint if an external segment has been enabled.

Redundant cards must either both support traffic shaping, or neither support traffic shaping. In the non-redundant case, traffic shaping is configurable regardless of whether the BXM card in the target slot supports traffic shaping. If the card does not support traffic shaping, then a BXM card that does support traffic shaping can be inserted later and the traffic shaping configuration will take effect. System software will not perform mismatch checking on the traffic shaping capabilities of the BXM.

The traffic shaping rate parameters are in Table 3-34. The MCR is the minimum cell rate for the connection. This is the lowest rate that the connection will be scheduled from the VC queue into the Qbin. The PCR is the peak cell rate, or the highest rate at which the connection will be scheduled from the VC queue into the Qbin.

Table 3-34 cnfport—Traffic Shaping Rates 

Service Type	MCR	PCR
CBR	PCR	PCR
VBR	SCR1 %Util	PCR
UBR	0	PCR
ABR	MCR %Util	PCR

1 Indicates that the system software issues a warning that traffic shaping is not supported on that specific BXM.

---

Note Traffic shaping does not generate any alarms. There is no mismatch checking for BXMs that support traffic shaping, so if you insert a BXM card with firmware that does not support it, then the traffic shaping functionality will not exist.

---

---

Note Cells can be momentarily received out of order when you reconfigure connections between traffic shaping and non-traffic shaping. This is a limitation of the hardware for which there is no workaround.

---

Configuring Traffic Shaping

Traffic shaping involves passing ATM traffic through the ATM interface at a VC queue, scheduled rate. With the introduction of traffic shaping, the customer will have the option to perform VC scheduling to his/her ABR, CBR, VBR, and UBR traffic streams. Traffic shaping is performed by the BXM hardware.

Traffic shaping will be performed on a per-port, per-CoS basis.

No connections should exist on the port before you change the port traffic-shaping parameter. If there are existing connections when you toggle the port traffic-shaping parameter, then these connections will not be updated unless you reset the card (by using the resetcd command), connections are rerouted, a switchcc occurs, or you modify the connection parameters. Also, it should be noted that traffic shaping is not enabled on a VSVD endpoint if external segment has been enabled.

Use cnfportq to configure traffic shaping parameters.

Firmware Functionality (BXM)

The BXM firmware supports a new CommBus parameter to enable/disable traffic shaping. When you add a connection, the BXM firmware checks its database to see if traffic shaping is enabled for the port that the connection is to be mapped to. If traffic shaping is enabled, the BXM firmware sets up the ASIC hardware to perform the weighted fair queuing. In the background, the BXM firmware runs a rate-based algorithm.

Existing functionality, such as VC queuing, is used by the traffic shaping feature.

In this release, the BXM firmware supports a new CommBus (CBUS) parameter to enable/disable traffic shaping. When a connection is added, the BXM firmware checks its database to see if traffic shaping is enabled for the port that the connection is to be mapped to. If traffic shaping is enabled for the traffic class on the port, the BXM firmware sets up the ASIC hardware to perform the weighted fair queuing. In the background, the BXM firmware runs a rate-based algorithm similar to what is done today for explicit rate stamping (ERS). The only other interface change includes an egress SCR parameter in the channel (0x52) message.

The algorithm executed by the firmware involves the BXM firmware polling the cell arrival and transmit counters of the Qbins approximately every 15 msec. During this time, the firmware determines the congestion ratio:

rc = rp * out/in

where rp is the previous value of rc, "out" is the number of cells leaving the Qbin, and "in" is the number of cells arriving into the Qbin. Note that if the ratio of out/in is less than 1, then the Qbin is experiencing congestion. The BXM firmware takes the resulting "rc" and divides this value into the sum of all of the PCRs for the Qbin and uses this result as the congestion factor to be programmed into the hardware (SABRE).

Performance of Traffic Shaping

The weighted fair queuing (WFQ) algorithm for traffic shaping runs the same algorithm as the explicit rate stamping (ERS). This processing consumes 12 percent of the bandwidth. Because the algorithm runs once (even if both ERS and WFQ are enabled), traffic shaping will not increase the worst-case demand for BXM processor time.

Errors and Alarm Handling

No alarms will be generated regarding the traffic-shaping feature. As previously mentioned, there is no mismatch checking for BXMs that do not support the feature, so if you insert a BXM with firmware that does not support the feature, then the traffic shaping functionality will not be supported on that card.

It should be noted that cells can be momentarily received out of order when connections are reconfigured between traffic shaping and non-traffic shaping. This is a limitation of the hardware for which there is no workaround.

Virtual Ports

Virtual ports ( Figure 3-20) are logical interfaces like virtual trunks, trunks, and ports. (A maximum of 31 logical entities are available on a BXM card.)

Virtual ports is an optional feature that must be configured by Cisco on the BPX.

Figure 3-20 Virtual Ports

One or more virtual ports may function on a single port connected to CPE devices, directly or through an ATM cloud. Although virtual ports, like ports, can connect directly to CPEs, they are generally used to connect indirectly.

Traffic shaping has previously been supported on ports and on connections. Virtual ports on BPX switches provide hierarchical traffic shaping, which means both virtual port traffic shaping and connection traffic shaping.

A virtual port may carry multiple PVCs or PVPs. VI traffic shaping capability is provided per virtual port. Additionally, connection traffic shaping is available on a QoS basis. While virtual port shaping is always ON, you can turn connection traffic shaping ON or OFF by using the cnfportq command.

Each virtual port supports all Automatic Routing Management (AutoRoute) traffic types that are currently supported by ports.

To set the maximum bandwidth available for use on that virtual port, use the Bandwidth parameter of the command cnfport (see Figure 3-21). This parameter is similar to the Bandwidth parameter used for ports. However, while the Bandwidth parameter is configurable on a virtual port, on a port, this parameter is not configurable; it is automatically set to the line speed.

You can configure a virtual port's bandwidth to the full port bandwidth or a subset thereof. However, the bandwidth sum of all virtual ports on a port cannot exceed the port's total bandwidth.

Figure 3-21 Port Bandwidth

Requirements

Virtual ports are available on the BXM card for the BPX. This feature is included in BPX Switch Software 9.3.10. and is independent of firmware. Virtual ports are not supported on ASI card connections.

On the BPX, this feature requires:

•BCC 3-64 or BCC 4-128 controller card

•BXM card

Depending on the interface type, UNI or NNI, the maximum number of PVPs will be 255 or 4095 respectively. The maximum number of VCIs is 65535.

Port Bandwidth and Line Speed

Figure 3-22 shows the types of bandwidth that make up the port's total bandwidth as configured by cnfport.

Figure 3-22 Port Bandwidth and Line Speed

Total Port Bandwidth

The total port bandwidth is the bandwidth of the port. It is configured by the cnfport command. Its units are cells per second. If there are multiple ports on a line (physical interface), then the sum of the "Total Port Bandwidths" on that line is limited to be less than or equal to the line speed.

For BXM T3 lines the line speed is based on the framing, PLCP or HEC, and can be reconfigured using the cnfln command.

Automatic Routing Management Bandwidth

The Automatic Routing Management Bandwidth is the bandwidth that can be used by Automatic Routing Management connections. It is user configured via the cnfrsrc command. Its units are cells per second. It can never be larger than the total port bandwidth.

VSI Bandwidth

The VSI bandwidth is the bandwidth that is currently used by the VSI partitions. It is a calculated value based on the VSI min-BW and max-BW values. Its units are in cells per second. It is "configurable by the user" when the min-BW and max-BW values are modified via the cnfrsrc command. When being configured, the min-BW and max- BW parameters cannot be set so that they would consume more than Total Port Bandwidth-Automatic Routing Management Bandwidth.

Unused Bandwidth

The unused bandwidth is whatever is left over. This occurs if some of the non-Automatic Routing Management bandwidth is unused by VSI.

Limitations

The BXM card has 31 Virtual Interfaces (VIs). These VIs can be used for Virtual Ports, Virtual Trunks, Physical Ports or Physical Trunks.

•The maximum number of interfaces (Virtual/Physical Port/Trunk) per BXM is equal to the maximum number of VIs. Therefore, a maximum of 31 (BXM) Virtual Ports are supported per card. The maximum number of Virtual Ports is 31 (BXM), but the number of available Virtual Ports can be lower based on the number of other interface types in use.

•A maximum of 254 ports (physical or virtual), are supported on the BPX node with the BCC 4-128 controller. A maximum of 144 Virtual Ports will be supported on a BPX node running the BCC 3-64 controller. Virtual Ports are not supported on controllers lower than BCC 3-64 (BPX). The maximum Virtual Ports available will be reduced by the number of Physical Ports on the system.

•Some port parameters are physical, and therefore when they are changed on one Virtual Port, they will change the same parameter on all other Virtual Ports that reside on the same Physical Port. Others apply only to the Virtual Port. A description of all the parameters is listed in Table 2-65.

•The total number of connection channels per card is shared by all interfaces on the card. The number of channels used by all the interfaces on a card cannot exceed the total number of channels on the card. The number of channels on a given interface is further limited by the port group to which it belongs.

•The number of port groups limits the number of channels that may be used on an interface. For example, consider an 8-port BXM card with two port groups and a total of n channels. Each port group may access a pool of n/2 channels. Each port may only access the channels in its port group, so each interface is limited to a maximum of n/2 channels.

•The total bandwidth per Physical Port is shared by all the Virtual Ports on that Physical Port. The bandwidth sum of all the Virtual Ports on the Physical Port cannot exceed the bandwidth of the Physical Port.

•Queue depth per port is shared by all the logical (Physical/Virtual Port/Trunk) interfaces on the card. The queues are dynamic, which allows oversubscription of the available queue space. The sum of all the configured queue depths may be larger than the available queue space on the card.

a. T1 (UXM card only) 3,622 cells/second

b. T3 (PLCP mode) (BXM) 96,000 cells/second

c. T3 (HEC/Direct mapping mode) (BXM) 104,000 cells/second

d. E3 (BXM) 80,000 cells/second

e. OC3 (BXM) 353,208 cells/second

f. OC12 (BXM) 1,412,830 cells/second

•Virtual Port traffic shaping is always ON, connection shaping is configurable per QoS.

cnfportq (configure port queue parameters)

Configures queue parameters for a port on an ASI or BXM card on the BPX, or a UXM card on the IGX. Pressing the Return key keeps the current value for the parameter.

You can use cnfportq to configure Qbin values separately for rt-VBR and nrt-VBR connection types on ports. (To configure the Qbin values for rt-VBR and nrt-VBR classes of service on trunks, use cnftrkparm.) The rt-VBR and nrt-VBR connections use different queues on a port: these are the rt-VBR and nrt-VBR queues, respectively.

For information on configuring trunk queues used by rt-VBR and nrt-VBR connections, see the cnftrkparm command.

The VBR class of service type can be either rt-VBR or nrt-VBR, depending on the way the corresponding port (service) queues (both ingress and egress) are configured. For the nrt-VBR class of service type in this release, the corresponding service queues are large enough to provide efficient bandwidth sharing with other non-real-time service types. The service queues for both rt-VBR and nrt-VBR service types can be configured on a node-by-node basis.

In Release 9.3.0, you can enable connection shaping for BXM queues. (See Hierarchical. Traffic Shaping on the BXM Card.)

Syntax

cnfportq <slot.port>[<.vport>] [<params>]

Parameters (ASI)

Parameter	Description
slot.port[.vport]	Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards.
nni/uni	Specifies whether the cell header format is NNI or UNI. Default: UNI
cbr queue parms	Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others.
nrt-vbr queue parms	Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others.
rt-vbr queue parms	Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others.
ubr/abr queue parms	Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 24000 for depth and 0 to 100% for all others.

Parameters (UXM)

Parameter	Description
slot.port[.vport]	Specifies the card slot, physical, and optional virtual port number (BXM only). At this time, virtual ports are not available for ASI or UXM cards.
nni/uni	Specifies whether the cell header format is NNI or UNI. UNI is the default.
cbr queue parms	Specifies the CBR queue parameters of depth, cbr-hi, cbr-lo, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others.
nrt-vbr queue parms	Specifies the nrt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others.
rt-vbr queue parms	Specifies the rt-VBR queue parameters of depth, vbr-hi, vbr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others.
ubr/abr queue parms	Specifies the ABR queue parameters of depth, abr-hi, abr-low, and efci. The ranges are 0 to 97250 for depth and 0 to 100% for all others. UBR traffic shares this queue with the ABR traffic.

The total queue size of the UXM card is 97250 cells.

Parameters (BXM)

Parameter	Description
slot.port[.vport]	Specifies the card slot, physical port, and optional virtual port (BXM card only). The optional vport identifier must be between 1-31 inclusive.
VC traffic shaping, connection shaping	Weighted fair queuing (WFQ) can be enabled on a per QoS/Qbin basis. This field is only configurable for BXM cards that support VC shaping. As of Release 9.3.0, VC shaping for BXM cards is no longer enabled on a per line bases. It is now done on a per Qbin/QoS basis. Enable/disable connection shaping within a virtual port. This feature is based on QoS. For example, all CBR connections can have traffic shaping, but all ABR connections may have traffic shaping disabled. The default setting is disabled.

Attributes

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

Related Commands

upport, dnport, dspportq

Example (BPX)

Configure the port queue for port 6.3 on a BXM card.

cnfportq 6.3

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 08:59 PST




Port: 6.3 [ACTIVE ]

Interface: LM-BXM

Type: UNI

AR Bandwidth: 353208 (cps)

QUEUE DEPTH CLP HI CLP LO EFCI VC SHAPE

/EPD

CBR 600 80% 60% 60% DISABLED

rt-VBR 5000 80% 60% 60% DISABLED

nrt-VBR 5000 80% 60% 60% DISABLED

UBR/ABR 20000 80% 60% 20% DISABLED





Last Command: cnfportq 6.3

Example (IGX)

Configure the port queue for port 5.3 on a UXM card.

cnfportq 5.3

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 08:29 GMT




Port: 5.3 [ACTIVE ]

Interface: OC3

Type: UNI

Speed: 353208 (cps) Alloc Bandwidth: 353208 (cps)




CBR Queue Depth: 600 rt-VBR Queue Depth: 5000

CBR Queue CLP High Threshold: 80% rt-VBR Queue CLP High Threshold: 80%

CBR Queue CLP Low Threshold: 60% rt-VBR Queue CLP Low Threshold: 60%

CBR Queue EFCI Threshold: 60% rt-VBR Queue EFCI Threshold: 60%

nrt-VBR Queue Depth: 5000 ABR Queue Depth: 20000

nrt-VBR Queue CLP High Threshold: 80% ABR Queue CLP High Threshold: 80%

nrt-VBR Queue CLP Low Threshold: 60% ABR Queue CLP Low Threshold: 60%

nrt-VBR Queue EFCI Threshold: 60% ABR Queue EFCI Threshold: 20%






Last Command: cnfportq 5.3

cnfportstats (configure port statistics collection)

Configures parameters for statistics collection on ports. The primary purpose of this command is debugging. Table 3-35 lists the configurable statistics for a Frame Relay port. For port statistics in general, refer to the actual cnfportstats screens on a node. Not all statistic types are applied to all ports.

Qbin statistics are Cells Served, Cells Discarded, and Cells Received.

Here is a summary of all Qbin statistics collected by the BPX and IGX:

•UXM and BXM Qbins 1-9 on Automatic Routing Management trunks.

•BXM Qbins 0-3, 9 on Automatic Routing Management ports.

•UXM Qbins 2,3, 7-9 on Automatic Routing Management ports.

•UXM and BXM Qbins 10-15 on VSI ports and trunks.

All other Qbins are unused, and the switch does not provide statistics for them. Starting in switch software release 9.3.10, the switch provides the collection of Qbin Cells Discarded statistics via SNMP for the above mentioned Qbins.

Syntax

cnfportstats <port> <stat> <interval> <e|d> [<samples> <size> <peaks>]

Parameters

Parameter	Description
<port>	Specifies the port to configure.
<stat>	Specifies the type of statistic to enable/disable.
<interval>	Specifies the time interval of each sample. Range:1-255 minutes
<e|d>	Enables/disables a statistic. E to enable; D to disable.
[samples]	Specifies the number of samples to collect. Range: 1-255
[size]	Specifies the number of bytes per data sample. Range: 1, 2 or 4
[peaks]	Enables the collection of one minute peaks. Y to enable; N to disable.

Table 3-35 Configurable Statistics for a Frame Relay Port 

Type	Statistic
1-4	Total frames and bytes transmitted and received.
5-6	Frames transmitted with FECN and BECN set.
7-10	Frames received with problems: CRC errors, invalid format, frame alignment errors, wrong length frames.
11	Number of direct memory access (DMA) overruns on a Frame Relay port that are probably due to excessive user-data input.
12-17	LMI counts on UNI ports. These include status inquiries, status transmit and update requests, invalid inquiries, and LMI link time-outs.
18	Frames received with DLCIs in error.
19	Frames dropped with DE bit set.
20-24	LMI counts on NNI ports: status inquiries, status receive and update requests, LMI link time-outs, keep-alive sequence errors.
25-26	Frame and byte count totals for Consolidated Link Layer Message (CLLM) frames that transmit Optimized Bandwidth Management messages.

Attributes

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

Related Commands

cnftrkstats, dsportstathist, dsporterrs, dsptrkstathist, cnfstatparm, dspphyslnstats, dspphyslnstathist

Example (UXM on IGX)

cnfportstats 5.3

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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 07:57 GMT




Port Statistic Types




34) PORT: Unknwn VPI/VCI cnt 48) PORT: # of cells rcvd

35) VI: Cells rcvd w/CLP=1 49) PORT: # of cells xmt

36) VI: OAM cells received 51) INVMUX: HEC cell errors

37) VI: Cells tx w/CLP=1 52) INVMUX: LCP cell errors

39) VI: Cells received w/CLP=0 53) INVMUX: Cell Hunt Count

40) VI: Cells discarded w/CLP=0 54) INVMUX: Bandwidth Change Count

41) VI: Cells discarded w/CLP=1 55) ILMI: Get Req PDUs rcvd

42) VI: Cells transmitted w/CLP=0 56) ILMI: GetNxt Req PDUS rx

43) VI: OAM cells transmitted 57) ILMI: GetNxt Req PDUS xmt

44) VI: RM cells received 58) ILMI: Set Req PDUs rcvd

45) VI: RM cells transmitted 59) ILMI: Trap PDUs rcvd

46) VI: Cells transmitted 60) ILMI: Get Rsp PDUs rcvd

47) VI: Cells received 61) ILMI: Get Req PDUs xmt




This Command: cnfportstats 5.3





Continue? y




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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 07:57 GMT




Port Statistic Types




62) ILMI: Get Rsp PDUs xmt 75) LMI: Invalid LMI PDU length rcvd

63) ILMI: Set Req PDUs xmt 76) LMI: Unknown LMI PDUs rcvd

64) ILMI: Trap PDUs xmt 77) LMI: Invalid LMI IE rcvd

65) ILMI: Unknwn PDUs rcvd 78) LMI: Invalid Transaction IDs

66) LMI: Status messages xmt 79) INVMUX: Unavailable Seconds

67) LMI: Updt Status msgs xmt 80) INVMUX: Near End Fail Count

68) LMI: Status Ack msgs xmt 81) INVMUX: Last Proto Fail Code

69) LMI: Status Enq msgs rcvd 82) INVMUX: Slowest Link

70) LMI: Status Enq msgs xmt 86) Q2 Cells Tx

71) LMI: Status msgs rcvd 87) Tx Q2 CDscd

72) LMI: Updt Status msg rcvd 88) Egr CRx Q2

73) LMI: Status Ack msg rcvd 89) Q3 Cells Tx

74) LMI: Invalid LMI PDUs rcvd 90) Tx Q3 CDscd




This Command: cnfportstats 5.3





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 07:58 GMT




Port Statistic Types




91) Egr CRx Q3 113) Q11 Cells Tx

101) Q7 Cells Tx 114) Tx Q11 CDscd

102) Tx Q7 CDscd 115) Egr CRx Q11

103) Egr CRx Q7 116) Q12 Cells Tx

104) Q8 Cells Tx 117) Tx Q12 CDscd

105) Tx Q8 CDscd 118) Egr CRx Q12

106) Egr CRx Q8 119) Q13 Cells Tx

107) Q9 Cells Tx 120) Tx Q13 CDscd

108) Tx Q9 CDscd 121) Egr CRx Q13

109) Egr CRx Q9 122) Q14 Cells Tx

110) Q10 Cells Tx 123) Tx Q14 CDscd

111) Tx Q10 CDscd 124) Egr CRx Q14

112) Egr CRx Q10 125) Q15 Cells Tx




This Command: cnfportstats 5.3





Continue? y




------------------------------------SCREEN 4-----------------------------------

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 07:59 GMT




Port Statistic Types




126) Tx Q15 CDscd

127) Egr CRx Q15








This Command: cnfportstats 5.3





Statistic Type:

Example (BXM on BPX) Node

cnfportstats 6.3

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

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 08:14 PST




Port Statistic Types




1) Unknown VPI/VCI count 24) Get Request PDUs transmitted

8) Number of cells received 25) Get Response PDUs transmitted

9) Number of cells rcvd w/CLP set 26) Trap PDUs transmitted

12) Number of cells xmitted 27) Unknown ILMI PDUs Received

13) OAM cells received count 28) Status messages transmitted

15) Number of cells xmitted w/CLP set 29) Update Status messages transmitted

18) Get Request PDUs received 30) Status Acknowledge msgs transmitted

19) Get Next Request PDUS received 31) Status Enquiry messages received

20) Get Next Request PDUS transmitted 32) Status Enquiry mesgs transmitted

21) Set Request PDUs received 33) Status messages received

22) Trap PDUs received 34) Update Status messages received

23) Get Response PDUs received 35) Status Acknowledge messages received





This Command: cnfportstats 6.3





Continue? y




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

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 08:15 PST




Port Statistic Types




36) Invalid LMI PDUs received received 48) Last unknown VPI/VCI pair

37) Invalid LMI PDU length received 49) Tx Cells Served on Qbin 0

38) Unknown LMI PDUs received 50) Tx Cells Discarded on Qbin 0

39) Invalid LMI IE received 51) Tx Cells Received on Qbin 0

40) Invalid Transaction IDs 52) Tx Cells Served on Qbin 1

41) Number of cells rcvd w/clp 0 53) Tx Cells Discarded on Qbin 1

42) Number of cells dscd w/clp 0 54) Tx Cells Received on Qbin 1

43) Number of cells dscd w/clp set 55) Tx Cells Served on Qbin 2

44) Number of cells tx w/clp 0 56) Tx Cells Discarded on Qbin 2

45) Tx OAM cell count 57) Tx Cells Received on Qbin 2

46) Rx RM cell count 58) Tx Cells Served on Qbin 3

47) Tx RM cell count 59) Tx Cells Discarded on Qbin 3





This Command: cnfportstats 6.3





Continue? y




------------------------------------SCREEN 3-----------------------------------

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 08:16 PST




Port Statistic Types




60) Tx Cells Received on Qbin 3 87) Tx Cells Received on Qbin 12

76) Tx Cells Served on Qbin 9 88) Tx Cells Served on Qbin 13

77) Tx Cells Discarded on Qbin 9 89) Tx Cells Discarded on Qbin 13

78) Tx Cells Received on Qbin 9 90) Tx Cells Received on Qbin 13

79) Tx Cells Served on Qbin 10 91) Tx Cells Served on Qbin 14

80) Tx Cells Discarded on Qbin 10 92) Tx Cells Discarded on Qbin 14

81) Tx Cells Received on Qbin 10 93) Tx Cells Received on Qbin 14

82) Tx Cells Served on Qbin 11 94) Tx Cells Served on Qbin 15

83) Tx Cells Discarded on Qbin 11 95) Tx Cells Discarded on Qbin 15

84) Tx Cells Received on Qbin 11 96) Tx Cells Received on Qbin 15

85) Tx Cells Served on Qbin 12

86) Tx Cells Discarded on Qbin 12





This Command: cnfportstats 6.3





Statistic Type:

cnfpref (configured preferred route for connections)

Specifies the preferred route for a connection or range of connections. Enter cnfpref only at a node that is an end point of the connection. This command applies only to connections that exist within a domain. Do not attempt to execute cnfpref on connections that exist between domains.

The preferred route for a connection is used when possible. If the preferred route is different from the existing route, the connection automatically moves to the preferred route whenever network conditions allow (for example, when trunks are out of alarm and sufficient bandwidth exists).

Syntax

cnfpref <channel | *> <route + | -> [d]

Parameters

Parameter	Description
<channel | *>	Specifies the channel or range of channels for preferred route configuration. The channel specifier has one of the following formats: •Voice connection: slot.channel •Data connection: slot.port •Frame Relay connection: slot.port.DLCI A "*" specifies all locally owned connections and applies only to the "+" and "-".
<route + | ->	Designates the preferred route for the connection(s) to take through the network. The route is designated by one or more "trunk/node name" pairs. At a given node alpha, for example, entering a route of "12/delta 6/epsilon", would route the connection from alpha to delta via delta's trunk 12. The connection would then go from delta to epsilon via epsilon's trunk 6. A "+" causes the connection's current route to become the preferred route. A "-" removes the connection's preferred route designation.
[d]	Specifies directed routing. If the preferred route is not available, the connection is failed.

Attributes

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

Related Commands

dsprts

Example

Select the preferred route for channel 14.1 to be through beta trunk 13 to beta then to gamma trunk 15. For gamma, the "d" in the command specifies that the route is directed.

cnfpref 14.1 13/beta 15/gamma d

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

From 14.1 Route

14.1

alpha 14--13beta 15--15gamma

Pref:(D) alpha 14--13beta 15--15gamma





Last Command: cnfpref 14.1 13/beta 15/gamma d

Next Command:




Example

Remove the preferred route for channel 6.4.

cnfpref 6.4 -

Example

Designate the current routing of all locally owned connections to be the preferred routing. Using a "-" instead of a "+" in the command would remove the preferred routing designation of all locally owned connections.

cnfpref * +

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

Chan/Grp Route

5.1

alpha 10-- 7beta

Pref: alpha 10-- 7beta

9.1.100

alpha 14--13beta 15--15gamma

Pref: alpha 14--13beta 15--15gamma

9.1.200

alpha 10-- 7beta 15--15gamma

Pref: alpha 10-- 7beta 15--15gamma

9.2.400

alpha 10-- 7beta

Pref: alpha 10-- 7beta

Last Command: cnfpref * +

Next Command:

cnfprt (configure printing functions)

Configures the printing function. To obtain local or remote printing at a node, a printer must connect to the AUX PORT. Also, the configuration must include the correct baud rate and printer type for the port. Use the cnfterm and cnftermfunc commands to do this.

The cnfprt and cnftermfunc commands interact. If the auxiliary port on the node is configured for either an External Device Window or the Network Management Log, a "local" printing configuration automatically changes to "no printing." Printing is not possible because the auxiliary port is being used for another purpose.

Establishing a virtual terminal connection with a node does not affect the printing location established for the node that initiates the virtual terminal connection. For example, if node alpha is configured so that all alpha information goes to a printer at node beta and if alpha establishes a virtual terminal connection with node gamma, the results of print commands entered on the alpha keyboard still print at beta. Furthermore, this occurs regardless of the printing location configured for node gamma.

Syntax

cnfprt <mode> <remote node name>

Parameters

Parameter	Description
mode	Specifies the printing mode. Enter: "L" for local printing "R" for remote printing "n" for no printing
remote node name	Specifies the remote node whose printer is used for print commands issued by a user who is physically logged on to this node. This option is valid only when remote printing has been selected. A remote node is one within the domain, but not the node where the command is entered.

Attributes

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

Related Commands

cnfterm, dsptermfunc

Example

Change the configured printing.

cnfprt

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

Printing Mode

Remote Printing at beta

Local Printing

No Printing




This Command: cnfprt

Select Local (l), Remote (r), or None (n):




cnfpwd (configure password)

Changes the password associated with a User ID. To change a password, you must log into the node with the User ID whose password you want to change. Passwords are case-sensitive.

In a structured network, each domain requires you to have a password. In each domain, your password and associated privilege level can be the same as or different from those in the other domains. For each domain, you can change the password at any node within the domain, including a junction node.

Syntax

cnfpwd <old password> <new password>

Parameters

Parameter	Description
<old password>	Specifies the old password.
<new password>	Specifies the new password. Passwords must have 6-15 characters. Only letters, numbers, "_", and "-" are allowed in a password. Spaces are not allowed.

Attributes

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

Related Commands

dsppwd, adduser, deluser, dspusers

Example

Change your password.

cnfpwd

cnfqbin (configure Qbin)

Configure the Qbin (class of service buffers) on a selected UXM or BXM port, physical trunk, or virtual trunk. The cnfqbin command prompts you whether "template" should be used for Qbin parameters.

As an option, you can accept the default values from the interface service class template. For example, you can type in Yes when prompted whether the interface service class template (SCT) should be used, and the command will use the Qbin values from the Qbin templates. You will not be allowed to enter values for any Qbin parameter in this case. If you do not choose the template option, you can enter desired values.

When a VSI interface is activated, the default template (MPLS1) is assigned to an interface. The corresponding Qbin template is copied into the card Qbin data structure for that interface. When you want to change this, by giving new values using the cnfQbin command, the Qbin is now user configured as opposed to template configured. This information is displayed on the dspQbin screen. It indicates whether the values in the Qbin are from the template assigned to the interface OR the values have been changed to user-defined values.

There are 16 Qbins (numbered 0 through 15) per interface. Only Qbins 10-15 are used by VSI and they are the only VSI Qbins you can configure.

To fine tune traffic delay, use the cnfqbin command to adjust the thresholds for the traffic arriving in the VSI Qbins for a given interface.

If you use the cnfqbin command to set an existing Qbin to disabled, the egress of the connection traffic to the network is disabled. Re-enable the Qbin to restore the egress traffic.

---

Note Cell delay variation (CDV) is based on the Qbin depths and the transmission speed of the virtual switch interface. The default Qbin depths are specified in the service class templates (SCTs). You can configure the Qbin depths by using the cnfqbin command.
Cell tolerance delay (CTD), which is the fixed delay, is based on a fixed value, and is not configurable.

---

Syntax

cnfqbin <slot number>.<port number>.<vtrk>

Parameters (UXM)

Parameter	Description
slot.port.vtrk	Specifies the UXM card slot, port, and virtual trunk number.
Qbin ID	Specifies the ID number of the Qbin available for use by the LSC (MPLS Controller) for VSI. Range: 10-15
Enable Qbin	Answer yes or no to enable your Qbin configuration.
Qbin Discard Threshold	Specifies the Qbin depth in units of cells.
CLP Low Threshold	Specifies the threshold in percentage for CLP low. Range: 0-100
CLP High Threshold	Specifies the threshold in percentage for CLP high. Range: 0-100
EFCI threshold	Specifies the threshold in percentage for EFCI. Range: 0-100

Parameters (BXM)

Parameter	Description
slot.port	Specifies the BXM card slot and port number.
Qbin ID	Specifies the ID number of the Qbin available for use by VSI controller. Range: 10-15
Enable Qbin	Answer yes or no to enable your Qbin configuration.
Minimum Bandwidth	Specifies the minimum bandwidth in cells per second available for the Qbin. Range: 0-352207 Default: 0
Qbin Discard Threshold	Specifies the Qbin depth in units of cells.
CLP Low Threshold	Specifies the threshold in percentage for CLP low. Range: 0-100
CLP High Threshold	Specifies the threshold in percentage for CLP high. Range: 0-100
EFCI threshold	Specifies the threshold in percentage for EFCI. Range: 0-100
Template	Specifies that the interface service class template should be used to configure the Qbin parameters. Thus the cnfqbin command will use the card's Qbin values from the Qbin template. If you do not choose the template option, you can enter your preferred values for the Qbin parameters.

Attributes

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

Related Commands

dspqbin, dspqbint

Example (UXM)

Configure Qbin 10 for UXM port 3.1 on the IGX.

cnfqbin 3.1 10

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:30 PST




Qbin Database 3.1 on UXM Qbin 10 (Configured by MPLS1 Template)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 65536 c9.3.10ells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%






This Command: cnfqbin 3.1 10





'E' to Enable, 'D' to Disable [E]:

Example (UXM)

Configure the Qbin 10 for port 3.1. Change the Discard Threshold from 65535 to 64000 and change Low EDP Threshold from 95% to 90%.

•E to Enable, D to Disable [E]: E

•Use default values from template?: N

•Qbin Discard threshold [65535]: 64000

•Low EPD threshold [95] (%): 90

•High CLP threshold [100] (%):

•EFCI threshold [100] (%)




cnfqbin 3.1 10

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:36 PST




Qbin Database 3.1 on UXM Qbin 10 (Configured by User)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 64000 cells

EPD Threshold: 90%

High CLP Threshold: 100%

EFCI Threshold: 100%






Last Command: cnfqbin 3.1 10 E N 64000 90 100 100





Next Command:




Minor Alarm

Example

You can also set the previous parameters for Qbin 15:

cnfqbin 3.1 15 E N 64000 90 100 100

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:39 PST




Qbin Database 3.1 on UXM Qbin 15 (Configured by User)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 64000 cells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%






Last Command: cnfqbin 3.1 15 E N 64000 95 100 100





Next Command:




Example (BXM)

Configure the parameters of Qbin 10 on BXM OC-3 port 4.1.

cnfqbin 14.1 10

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 17:01 GMT




Qbin Database 4.1 on BXM Qbin 10 (Configured by MPLS1 Template)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 105920 cells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%





This Command: cnfqbin 4.1 10





'E' to Enable, 'D' to Disable [E]:

Example (BXM)

Configure Qbin 11 for BXM OC-3 trunk 4.2. Change the Qbin Discard threshold from 105920 to 100000 cells.

•E to Enable, D to Disable [E]: E

•Use default values from template?: N

•Qbin Discard threshold [105920]: 100000

•Low EPD threshold [95] (%)

•High CLP threshold [100] (%):

•EFCI threshold [100] (%):

cnfqbin 4.2 11

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 17:10 GMT




Qbin Database 4.2 on BXM Qbin 11 (Configured by User)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 100000 cells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%




Last Command: cnfqbin 4.2 11 E N 100000 95 100 100

Example (BXM)

You can also set the previous parameters for Qbin 15:

cnfqbin 4.2 15 E N 100000 95 100 100

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 17:16 GMT




Qbin Database 4.2 on BXM Qbin 15 (Configured by User)

(EPD Enabled on this Qbin)




Qbin State: Enabled

Discard Threshold: 100000 cells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%




Last Command: cnfqbin 4.2 15 E N 100000 95 100 100





Next Command:

Qbin Dependencies

The available Qbin parameters are shown in Table 3-36. Notice that the Qbins available for VSI are restricted to Qbins 10-15 for that interface.

There are 9 Qbin templates. Each Qbin template is associated with one corresponding service class template. For Qbin default settings, see Table 3-37.

Only MPLS1 (template 1) may be used with IGX.

Table 3-36 Available Qbin Parameters 

Template Object Name	Template Units	Template Range/Values
Qbin Number	enumeration	0-15 (10-15 valid for VSI)
Max Qbin Threshold	msec	1-2000000
Qbin CLP High Threshold	% of max Qbin threshold	0-100
Qbin CLP Low Threshold	% of max Qbin threshold	0-100
EFCI Threshold	% of max Qbin threshold	0-100
Discard Selection	enumeration	1: CLP Hysteresis 2: Frame Discard
Weighted Fair Queueing	enable/disable	0: Disable 1: Enable

Table 3-37 lists cnfqbin parameters with possible values and ranges.

.

Table 3-37 Qbin Default Settings 

Qbin	Max Qbin Threshold (usec)	CLP High	CLP Low/EPD	EFCI	Discard Selection
LABEL Template 1
10 (Null, Signaling, Tag0,4)	300,000	100%	95%	100%	EPD
11 (Tag1,5)	300,000	100%	95%	100%	EPD
12 (Tag2,6)	300,000	100%	95%	100%	EPD
13 (Default, Tag3,7)	300,000	100%	95%	100%	EPD
14 (Tag Abr)	300,000	100%	95%	6%	EPD
15 (Tag unused)	300,000	100%	95%	100%	EPD
PNNI Templates 2 (with policing) and 3
10 (Null, CBR)	4200	80%	60%	100%	CLP
11 (VbrRt)	53000	80%	60%	100%	EPD
12 (VbrNrt, Signaling)	53000	80%	60%	100%	EPD
13 (Default, Ubr)	105000	80%	60%	100%	EPD
14 (Abr)	105000	80%	60%	20%	EPD
15 (Unused)	105000	80%	60%	100%	EPD
Full Support for ATMF and reduced support for Tag CoS without Tag-Abr Templates 4 (with policing) and 5
10 (Tag 0,4,1,5, Default, UBR, Tag-Abr*)	300,000	100%	95%	100%	EPD
11 (VbrRt)	53000	80%	60%	100%	EPD
12 (VbrNrt, Signaling)	53000	80%	60%	100%	EPD
13 (Tag 2,6,3,7)	300,000	100%	95%	100%	EPD
14 (Abr)	105000	80%	60%	20%	EPD
15 (Cbr)	4200	80%	60%	100%	CLP
Full Support for Tag ABR and ATMF without Tag CoS Templates 6 (with policing) and 7
10 (Tag 0,4,1,5,2,6,3,7 Default, UBR)	300,000	100%	95%	100%	EPD
11 (VbrRt)	53000	80%	60%	100%	EPD
12 (VbrNrt, Signaling)	53000	80%	60%	100%	EPD
13 (Tag-Abr)	300,000	100%	95%	6%	EPD
14 (Abr)	105000	80%	60%	20%	EPD
15 (Cbr)	4200	80%	60%	100%	CLP
Full Support for Tag CoS and reduced support for ATMF Templates 8 (with policing) and 9
10 (Cbr, Vbr-rt)	4200	80%	60%	100%	CLP
11 (Vbr-nrt, Abr, Signaling)	53000	80%	60%	20%	EPD
12 (Ubr, Tag 0,4)	300,000	100%	95%	100%	EPD
13 (Tag 1, 5, Tag-Abr)	300,000	100%	95%	6%	EPD
14 (Tag 2,6)	300,000	100%	95%	100%	EPD
15 (Tag 3, 7)	300,000	100%	95%	100%	EPD

cnfrcvsig (configure receive signaling)

Configures the receive signaling bits for a voice channel. Channel signaling bit options are:

•t (transparent)

•0

•1

•I (invert)

If signaling is set to "not used" (-) by using cnfchtp, the following condition is maintained: A=1, B=1, C=0, D=1.

Syntax

cnfrcvsig <channel(s)> <[A/]Conv> <[B/]Conv> <[C/]Conv> <[D/]Conv>

Parameters

Parameter	Description
channel	Specifies the channel or range of channels to receive signaling.
A/	Optionally specifies the conversion applied to the A bit. <Conv> can be one of: 1:bit is asserted. 0:bit is inhibited. T:bit is passed transparently. I:bit is inverted.
B/	Optionally specifies the conversion applied to the B bit.
C/	Optionally specifies the conversion applied to the C bit.
D/	Optionally specifies the conversion applies to the D bit.

Attributes

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

Related Commands

cnfxmtsig, dspsigqual

Example

Configure channel 8.1 signaling to transparent for the A-bit, inhibited for the B-bit, inverted for the C-bit and D-bits.

cnfrcvsig 8.1 A/T B/0 C/I D/I

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

Signaling Qualifiers

From 8.1 TXA-bit TXB-bit TXC-bit TXD-bit RXA-bit RXB-bit RXC-bit RXD-bit

8.1 T T T T T 0 I I

8.2-31 T T T T T T T T




Last Command: cnfrcvsig 8.1 A/T B/0 C/I D/I

Next Command:




cnfrobparm (configure robust alarms parameters)

Sets parameters associated with the Robust Alarms feature. Robust Alarms is a protocol for node-to-Network Management System (NMS) communications. When a node has statistics or alarm information for the NMS, it requires a confirmation from the NMS that the database has been updated.

In Release 9.2 and higher, there are robust alarms for certain alarm conditions that appear in the maintenance log or in the node user interface but are not also reported as SNMP traps to the customer NMS. (Such traps are generated by the Cisco WAN Manager RTM proxy upon receiving Robust Alarms from a switch.) Robust Alarm messages are generated by the following alarm conditions:

•Power supply, temperature, fan, and DC voltage level alarms

•Connection AIS alarm

•Bus failure

•External clock source failure

•Multiple invalid login attempts on a user port

•Excessive CPU and memory usage on switch processor card

The BPX and the IGX generate power supply, temperature, and fan alarms.

Syntax

cnfrobparm <index> <value>

Parameters

Parameter	Description
<index>	Specifies the parameter to configure.
<value>	Specifies new value to be entered for the parameter.

Parameter Values

No.	Parameter	Description	Default
1	Robust State wakeup timer	The Robust State machine becomes active after the specified time period has elapsed. If this timer value increases, the state machine operates less often and places less load on the controller card. Units of measure are seconds.	10 seconds
2	Robust update timer	Once a message has gone to the NMS, another message does not go until this timer expires. Units of measure are seconds.	10 seconds
3	Robust acknowledgment time-out	An acknowledgment must be returned by the NMS within this time period or it is assumed the communications link is down. Units of measure are seconds.	600 seconds
4	Robust acknowledgment reset timeout	After a downed link has been repaired, the next message goes out after this time period has elapsed. The purpose of this time period is to let the link settle after the repair. Units of measure are seconds.	60 seconds

Attributes

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

Example (IGX)

cnfrobparm

a34 TRM SuperUser IGX 8420 9.3 Apr. 13 2000 15:02 PDT

Robust Parameters

1 Robust State wakeup timer (sec) .................................. 10

2 Robust update timer (sec) ........................................ 10

3 Robust acknowledge timeout (sec) .................................600

4 Robust acknowledge reset timeout (sec) ...........................60




This Command: cnfrobparm

Which parameter do you wish to change:

cnfrrcpu (configure CPU-based reroute throttling level parameters)

When the CPU utilization exceeds the defined threshold, routing is suspended. Throttling thresholds can be independently set for master, via, and slave routing. In addition, a hysteresis mechanism is provided to prevent excessing oscillation, using the parameter <resume_diff>).

---

Note Throttling is based on the CPU utilization of the TRNS task and all tasks with the same or higher priority. Hence, activity of low-priority tasks such as FAIL or SNMP will not cause routing to be throttled.

---

Syntax

cnfrrcpu <m_cpu> <v_cpu> <s_cpu> <resume_diff>

Parameters

Parameter	Description
<m_cpu>	Specifies the % CPU utilization above which master routing will be suppressed. Range: 0-100 Default: 0
<v_cpu>	Specifies the% CPU utilization (TRNS+higher) above which via routing will be suppressed. Range: 0-100 Default: 0
<s_cpu>	Specifies the % CPU utilization (TRNS+higher) above which slave routing will be suppressed. Range: 0-100 Default: 0
<resume_diff>	Specifies the difference between suppression threshold and resume threshold; once routing (of any type) is suppressed, routing will not resume until the CPU utilization (TRNS+higher) drops below (threshold-resume diff)% Range: 0-to (MIN{m_cpu, v_cpu, s_cpu} - 25) Default: 0

Attributes

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

Example (IGX)

sws5 TRM Cisco IGX 8420 9.3.f5 Aug. 24 2001 0746 GMT




Master CPU Throttle Level (% CPU) 80

Via CPU Throttle Level (% CPU) 100

Slave CPU Throttle Level (% CPU) 100

CPU Resume Difference (% CPU) 10




NOTE %CPU refers to CPU utilization by TRNS and higher-priority tasks

cnfrsrc (configure resource)

Use the cnfrsrc command to partition resources for:

•Automatic Routing Management PVCs

•VSI-MPLS (Multiprotocol Label Switching)

•VSI-PNNI (Private Network to Network Interface)

If you want to configure resources for a VSI-MPLS controller or PNNI SVCs, refer to the subsequent BPX- and IGX-specific command definitions.

Up to two controllers of the same type can be attached to a node and assigned the same partition to provide controller redundancy on that partition. A different set of controllers can be attached to the node and be assigned a different partition to provide controller redundancy on this second partition.

You can configure a virtual trunk to be dedicated to VSI or to Automatic Routing Management. You cannot configure a virtual trunk for both VSI and Automatic Routing Management.

This command supports physical trunks and virtual trunks. After VSI has been enabled, the virtual trunk becomes a "dedicated" VSI virtual trunk. If the trunk has already been added or if the VPI value has not been configured, switch software will prevent you from configuring the VPI value.

The switch software:

•Allows start VPI = 0 for a VSI partition on a port interface, or feeder trunk interface.

•Prevents a second VSI partition from being enabled on a port interface if the first VSI partition uses a start VPI = 0.

•In release 9.2.30 and release 9.3.0, prevents a VSI partition from being disabled on a trunk interface if a PNNI controller is attached to the trunk interface controlling partition being disabled. This restriction has been removed starting with Release 9.3.05) going forward.

Configurable Resources

You can use cnfrsrc to configure these resources:

•Template number (new field in Release 9.2)

•Maximum PVC LCNs

•Maximum PVC Bandwidth

•Configure PVC VIP ranges (Y/N)

•Start of PVC VPI range 1

•End of PVC VPI range 1

•Start of PVC VPI range 2

•End of PVC VPI range 2

•Start of PVC VPI range 3

•End of PVC VPI range 3

•Start of PVC VPI range 4

•End of PVC VPI range 4

•Configure Partition (Y/N)

•Partition ID

•Enable Partition (Enable/Disable)

•Minimum VSI LCNs

•Maximum VSI LCNs

•Start VSI VPI

•End VSI VPI - Warning message will tell you that the end VSI VPI is equal to the start VSI VPI for virtual trunks

•Minimum VSI Bandwidth

•Maximum VSI Bandwidth

The resources that you can configure are the number of connection IDs (conids) and the trunk bandwidth. You use the cnfrsrc command to configure the cell rate and number of connections on a BXM card only. (You cannot use the cnfrsrc command on the IGX.)

You configure all port and trunk attributes by using cnftrk, cnftrkparm, or cnfrsrc. When you change a physical port attribute, you are notified that all the logical (physical and virtual) trunks on the port are affected.

When using cnfrsrc to configure partition resources for Automatic Routing Management PVCs, you are prompted whether you want to configure VSI options. Enter "n" for No. You will not be prompted to enter any VSI options.

Use the cnfrsrc command to configure conids (lcns) and bandwidth. The conid capacity indicates the number of connection channels on the trunk port which are usable by the virtual trunk.

This number cannot be greater than the total number of connection channels on the card. The maximum number of channels is additionally limited by the number of VCI bits in the UNI cell header. For a virtual trunk, the number is divided by the maximum number of virtual trunks on the port to determine the default. Use the cnfsrc command to configure this value on the BPX. Table 3-38 lists the number of connection IDs for virtual trunks on various cards.

Table 3-38 Maximum Connection IDs (LCNs)

Port Type	Maximum Conids	Default
BXM/UXM	1-(number of channels on the card)	256
BNI T3/E3	1-1771	256
BNI OC-3	1-15867 (3837 max/vtrk	256

Syntax

cnfrsrc <slot>.<port> <.vport> <maxpvclcns> <maxpvcbw> <partition> <e|d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

Parameters

Parameter	Description
slot.port.vtrk	Specifies the BXM card slot and port number and virtual trunk.
Maximum PVC LCNs	The maximum number of LCNs allocated for Automatic Routing Management PVCs for this port. The range depends upon the card type; (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC) 256 is the default. The default is 256 only if 256 are available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. For trunks, there are additional LCNs allocated for Automatic Routing Management that are not configurable. You can use the dspcd <slot> command to display the maximum number of LCNs you can configure using the cnfrsrc command for the given port. For trunks, configurable LCNs represent the LCNs remaining after the BCC has subtracted the networking LCNs needed. A trunk has 270 networking LCNs, or channels. You can use the dspcd command to display VSI channels also. For a port card, a larger number is shown, as compared with a trunk card. This is because a trunk uses 270 networking LCNs, as compared with a port card, which uses no networking LCNs. You can use dspcd to display VSI channels also. Setting this field to "0" would disable Automatic Routing Management PVCs on the specified port. Note You must specify a value greater than 0 for the Maximum PVC LCNs, Maximum PVC Bandwidth, and Maximum VSI LCNs parameters. Otherwise, you will not be able to create any Automatic Routing Management connections on a BXM card. Also, if these parameters do not have values greater than 0, you will be unable to change the connection channel amount when you configure the BXM trunk by using cnftrk. Logical Interface (slot.port [.vtrk] for trunks and slot.port for lines). The bandwidth is logical interface based. Default: the line rate of this interface.
Maximum PVC Bandwidth	Specifies the maximum bandwidth of the port allocated for Automatic Routing Management use depends upon the card type; (1-11771 for the BNI T/E3 and 1-15867 for the BNI OC); 256 is the default. The default is 256 only if 256 is available. If other ports and trunks on the card have been configured to use LCNs such that there are only 100 remaining, then the default value for the newly added port would be 100. In this instance trunk upping would be blocked indicating that there are not enough LCNs to support the trunk. You can configure the Maximum PVC Bandwidth value for ports, but not for trunks. Note You must specify a value greater than 0 for the Maximum PVC LCNs, Maximum PVC Bandwidth, and Maximum VSI LCNs parameters. Otherwise, you will not be able to create any Automatic Routing Management PVCs on the BXM card. Note Changing the line framing for BXM-T3 cards from PLCP to HEC no longer automatically changes the port's bandwidth to the new maximum. It merely raises the upper limit for the port's bandwidth. After changing the framing, you must use cnfport to increase the port's bandwidth, and cnfrsrc to increase the port's Automatic Routing Management bandwidth (PVC Max Bandwidth). You can define the PVC VPI ranges for Automatic Routing Management connections by using the cnfrsrc command. However, overlapping of the PVC and VSI VPI ranges are allowed only on a physical port or feeder trunk interface. When configuring the overlapping ranges, you will receive a warning of "Warning - VPI overlaps with AR range x". The command will be stopped if you answer y and will proceed if you answers n. The cnfrsrc screen contains a warning message: Note that the "*" next to the VPI fields indicate the overlapping PVC (Automatic Routing Management and VSI VPI ranges).
Configure PVC VCI Range	You will be prompted when configuring a port or feeder trunk only. Answer Yes or No to begin configuring the PVC VPI range. Enter Y if you are migrating PVCs on this interface to PNNI SPVCs, otherwise answer N. If you enter Y, you will be prompted for the four PVC VPI ranges.
Start of PVC VPI range x	You can define 4 VPI ranges. ALl the existing PVCs have to be using a VPI in one of the defined PVC VIP ranges.
End of PVC VPI range x	Together with Start of PVC VPI range, it defines a VPI range for PVCs.
Configure Partition	Answer yes or no to begin configuring resources for the partition. To configure Automatic Routing Management PVCs, enter n for No. You will not be prompted to enter VSI options to configure VSI partition resources. However, if you want to configure VSI options, enter y for yes, and you will be prompted to configure partition resources for VSI. (Refer to the command cnfrsrc (configure VSI resources for IGX) and cnfrsrc (configuring VSI resources for BPX) for more information on VSI-related options
Partition ID	Specifies the ID number of the partition. In previous releases, use 1. In release 9.1, use 1 for the partition ID. Default: 0 Range: 1 - 3
Enable Partition	Answer yes or no to enable your configured partition.
Minimum VSI LCNs	The minimum number of LCNs guaranteed for this partition. Range is from 0 to card limit: 0 is the default. The VSI controller guarantees at least this many connection endpoints in the partition, provided there are sufficient free LCNs in the common pool to satisfy the request at the time the partition is added. When a new partition is added or the value is increased, it may be that existing connections have depleted the common pool so that there are not enough free LCNs to satisfy the request. The BXM gives priority to the request when LCNs are freed. The net effect is that the partition may not receive all the guaranteed LCNs (min LCNs) until other LCNs are returned to the common pool. You can increase this value dynamically when there are enough unallocated LCNs in the port group to satisfy the increase. You may not decrease the value dynamically. All partitions in the same port group must be deleted first and reconfigured in order to reduce this value. To avoid this deficit condition, which could occur with maximum LCN usage by a partition or partitions, it is recommended that all partitions be configured ahead of time before adding connections. Also, it is recommended that all partitions be configured before adding a VSI controller by using the addshelf command.
Maximum VSI LCNs	The total number of LCNs the partition is allowed for setting up connections. The min LCNs is included in this calculation. If max LCNs equals min LCNs, then the max LCNs are guaranteed for this partition. Otherwise, (max - min) LCNs are allocated from the common pool on a FIFO basis. If the common pool is exhausted, new connection setup requests will be rejected for the partition, even though the maximum LCNs has not been reached. You may increase this value dynamically when there are enough unallocated LCNs in the port group to satisfy the increase. You may not decrease the value dynamically. All partitions in the same port group must be deleted first and reconfigured in order to reduce this value. Different types of BXM cards support different maximum values. If you enter a value greater than the allowed maximum, a message is displayed with the allowable maximum value. Note You must specify a value greater than 0 for the Maximum VSI LCNs, Maximum PVC Channels, and Maximum PVC Bandwidth parameters. Otherwise, you will not be able to add any connections on a BXM card.
Start VSI VPI	By default the LSC (for example, the 6400, 7200 or 7500 series router) will use either a starting VSI VPI of 1 or 2 for MPLS, whichever is available. If both are available, a starting VSI VPI of 1 is used. The VPI range should be 2-15 on a BPX  8620 VSI. The VSI range for MPLS on the BPX 8620 is configured as a VSI partition, usually VSI partition number 1. VSI VPI 1 is reserved for Automatic Routing Management PVCs. (This restriction applies only to trunks, not to ports. For a port, you can use any VPI value.) For a port UNI, the VPI range is 1 to 255. For a port NNI, the range is 1 to 4095. For trunks that do not have Automatic Routing Management configured, the VPI ranges are the same as for ports. The VSI partition for MPLS should start at VPI 2. If VPI 2 is not to be used, you can use the MPLS VPI interface configuration on the LSC to override the defaults. For trunks with Automatic Routing Management configured, the range is 2 to 4095. Always set to 2 for trunks. For ports in port mode it should be set to "1". By default the LSC (for example, 6400, 7200 or 7500 series router) will use either a starting VSI VPI of 1 or 2 for label switching, whichever is available. Default: 1
End VSI VPI	Two VPIs are sufficient, although it may be advisable to reserve a larger range of VPIs for later expansion, for example, VPIs 2-15. Range: <Start VSI VPI > value to 4095.
Minimum VSI Bandwidth	The minimum port bandwidth that can be used by this partition in cells per second. Range: 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207. Default: 0
Maximum VSI Bandwidth	The maximum port bandwidth that can be used by this partition. This value is used for VSI Qbin bandwidth scaling. Range: 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207. Default: 0

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	Hipri
1-6	No	No	BPX (BXM cards only)			No

Related Commands

dsprsrc

Example

Configure resource for port 9.1, to use Automatic Routing Management PVCs.

cnfrsrc 9.1 256 9600 N N

sw215 TN Cisco BPX 8620 9.3.f9 May 31 2000 15:29 GMT




Port : 9.1

Full Port Bandwidth: 96000

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 96000

(CAC Reserve: 0)




PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Disabled Disabled Disabled

VSI LCNS (min/max): 0 /0 0 /0 0 /0

VSI VPI (start/end): 0 /0 0 /0 0 /0

VSI BW (min/max): 0 /0 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 9.1 256 96000 N N





Next Command:

Example

Configure the resource of a virtual port 9.6.1 on the BXM card in slot 9 with a maximum of 256 PVC LCNS and a bandwidth of 3096.

cnfrsrc 9.6.1 256 3096

w215 TN Cisco BPX 8620 9.3.f9 May 31 2000 15:28 GMT

Port : 9.6.1

Full Port Bandwidth: 3096

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 3096

(CAC Reserve: 0)

PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1

Partition : 1 2 3

Partition State : Disabled Disabled Disabled

VSI LCNS (min/max): 0 /0 0 /0 0 /0

VSI VPI (start/end): 0 /0 0 /0 0 /0

VSI BW (min/max): 0 /0 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR

Last Command: cnfrsrc 9.6.1 256 3096




Next Command:

cnfrsrc (configure VSI resources for IGX)

Configures resources on ports, physical trunks, and virtual trunks.

This command supports both physical trunks and virtual trunks. After VSI has been enabled, the virtual trunk becomes a "dedicated" VSI virtual trunk.

The switch software will prevent you from configuring VSI:

•if the virtual trunk has already been added; or

•if the VPI value has not been configured.

You can configure a virtual trunk to be dedicated to VSI or to Automatic Routing Management. You cannot configure a virtual trunk for both VSI and Automatic Routing Management.

Syntax

cnfrsrc <slot.port.vtrk>

or

cnfrsrc <slot>.<port>.<vtrk> <maxpvclcns> <maxpvcbw> <partition> <e/d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

Parameters

Parameter	Description
slot.port.vtrk	Specifies the UXM card slot and port number and virtual trunk.
Maximum PVC LCNs	The maximum number of LCNs allocated for Automatic Routing Management PVCs for this port. Range: 1-8000 Default: 256 You can use the dspcd <slot> command to display the maximum number of LCNs you can configure using the cnfrsrc command for the given port. For trunks, configurable LCNs represent the LCNs remaining after the NPM card has subtracted the networking LCNs needed. A trunk has 270 networking LCNs, or channels. By default, when a port or trunk is upped, in addition to the 256 PVC LCNs, 200 Gateway LCNs are allocated for that port/trunk. The Gateway LCNs are used for non-UXM to UXM connections (like Frame Relay or ATFR). When PVC LCNs are reduced using the cnfrsrc command, the Gateway LCNs are also reduced so that it is always less than the PVC LCNs. However, when PVC LCNs are increased, the Gateway LCNs are not increased. Use the command dspchuse to display the channel usage for all ports, trunks, and virtual trunks of a given slot. Setting this field to "0" would disable Automatic Routing Management PVCs on the specified port. Note You must specify a value greater than 0 for the Maximum PVC LCNs and Maximum PVC Bandwidth. Otherwise, you will not be able to create any Automatic Routing Management connections on that UXM port or trunk.
Maximum PVC Bandwidth	Specifies the maximum bandwidth of the port allocated for Automatic Routing Management use. You can configure the maximum PVC Bandwidth value for ports, but not for trunks. Range: 0-352207 Default: The bandwidth is based on the logical interface (slot.port). The default value for this object is the line rate of this interface. Card Type | Bandwidth -------------------------------------------------- UXM E3 | 80000 UXM T3 | 96000 UXM OC-3             | 353208 UXM E1                 |       4528 UXM T1                 |       3622 You must specify a value greater than 0 for the maximum PVC LCNs and maximum PVC Bandwidth. Otherwise, you will not be able to create Automatic Routing Management PVCs on the UXM port or trunk. This parameter is not prompted and is not configurable for trunks and virtual trunks.
Edit VSI Parms?	To configure AR PVCs or AR bandwidth only, enter n for No. You will not be prompted to enter VSI options to configure VSI partition resources. However, if you want to configure VSI options, enter y for yes, and you will be prompted to configure partition resources for VSI.
Partition ID	Specifies the ID number of the partition. Range: 1-3
Enable Partition	Answer e to enable or d to disable your configured partition.
Minimum VSI LCNs	The minimum number of LCNs guaranteed for this partition. Range: 0-8000 Default: 0 If there are not enough LCNs on the slot to guarantee this minimum number, the switch software will prompt you with the number of available LCNs. You can increase this value dynamically when there are enough unallocated LCNs on the slot to satisfy the increase.
Maximum VSI LCNs	The total number of LCNs the partition is allowed for setting up connections. You may increase or decrease this value dynamically when there are enough unallocated LCNs on the slot to satisfy the change. Note that you must specify a value greater than 0 for the maximum VSI LCNs. Otherwise, you will not be able to add any VSI connections on that partition.
Start VSI VPI	VSI connections on this partition start from this VPI. Range: Port UNI: 0-255 Port NNI: 0-4095 Trunk with Automatic Routing Management configured: 2-4095 Trunk with NNI and no Automatic Routing Management configured: 1-4095 Trunk with UNI: 2-255 If the specified VPI is used by Automatic Routing Management connections or the control channel of the VSI controller, a warning will appear and then a prompt for the Start VSI VPI.
End VSI VPI	VSI connections on this partition can use VPIs up to this VPI. The End VSI VPI should be equal to or greater than the Start VSI VPI.
Minimum VSI Bandwidth	The minimum port bandwidth that can be used by this partition in cells per second. Range: 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207. Default: 0
Maximum VSI Bandwidth	The maximum port bandwidth that can be used by this partition. Range: 0 to <Maximum Line Rate>. For example, the OC-3 line rate is 352207. Default: 0

Attributes

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

Related Commands

dsprsrc

Increasing the Number of VSI LCNs Guaranteed for a VSI Partition

You can increase the number of LCNs guaranteed for a given VSI partition by increasing the Minimum VSI LCNs of the desired partition.

If the new number does not cause the total VSI LCNs to be increased (that is, if your want to increase the minimum VSI LCNs at the expense of the common pool), the request will be denied if there isn't enough free VSI LCNs in the common pool. The UXM card cannot find enough free VSI LCNs to give to the specified partition. More AR LCNs must be made available to VSI for the request to succeed. The cnfrsrc will display a message: Resource not available, maximum available LCN(s) is 50. 100 more LCN needed. This indicates the number of AR LCNs that should be made available to the VSI.

cnfrsrc 12.1 256 20000 y 1 e 900 1500 300 400 4000 6000

Decreasing the VSI LCNs

You can decrease the VSI LCN range in order to make more LCNs available to AR:

•If the formula result used to compute the number of VSI LCNs, was obtained by using the Minimum VSI LCNs, then you can decrease the VSI LCN range by decreasing the Minimum VSI LCNs of any VSI partition.

•If the formula result was obtained by using the Maximum VSI LCNs, then you can decrease the VSI LCN range by decreasing the Maximum VSI LCNs of the VSI partition whose max was used to get the result of the formula.

In some cases, decreasing the VSI LCN range will fail because there are not enough free VSI LCNs to give to AR. The cnfrsrc command will display a failure message giving the number of VSI channels that can be made available to AR (There are only 100 free VSI channels). You can then re-execute the cnfrsrc requesting a smaller number of VSI LCNs to be given to AR.

If you must give more VSI LCNs to AR than what is currently free, go to the VSI master and delete or re-route the necessary number of VSI connections to free up the required VSI LCNs by executing the proper commands on the VSI master. You can then reattempt the cnfrsrc command.

Sometimes the LCNs that were freed by the VSI master are reused prior to reexecuting the cnfrsrc command. You can delete more connections on the VSI master than what is required. Or you can freeze the VSI master so that it does not add any new VSI connections until the cnfrsrc command is reexecuted.

cnfrsrc 12.1 256 20000 y 1 e 900 1500 300 400 4000 6000

Expanding the VSI VPI Range

You can expand the VSI VPI range by changing the parameters Start VSI VPI and End VSI VPI. The command cnfrsrc checks whether the new VPI range overlaps with:

•AR connections; or

•a VPI is used by VSI controllers; or

•a VPI used by another partition.

Shrinking the VSI VPI Range

You can shrink the VSI VPI range by increasing the parameter Start VSI VPI and/or by decreasing the the parameter End VSI VPI. This works only if no VSI connections use the old VPI range. For example, if there is a VSI connection and VPI 10; and if the current VSI VPI range is [5,11], then the VSI VPI range cannot be shrunk to [5,9].

Increasing VSI Bandwidth

You can increase the bandwidth of VSI by increasing the Minimum VSI Bandwidth and/or Maximum VSI Bandwidth of the appropriate VSI partition. Increasing the bandwidth of VSI may cause AR connections on a trunk to be re-routed in order to free the necessary bandwidth for VSI. You will see a warning (Warning - increasing Max VSI Bandwidth will reroute all conns on this trunk). The command will proceed only if you choose to proceed.

cnfrsrc 12.1 256 20000 y 1 e 900 1500 300 400 4000 6000

Decreasing VSI Bandwidth

You can decrease VSI bandwidth of VSI by reducing the values of Minimum VSI Bandwidth and/or Maximum VSI Bandwidth. This works only if the VSI connections are not using the existing bandwidth.

Example

Changing the PVC max lcn and PVC max bandwidth for a port.

cnfrsrc 4.1 1000 300000 N

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 10:52 PST




Line : 4.1

Maximum PVC LCNS: 1000 Maximum PVC Bandwidth: 300000






State

Partition 1: D

Partition 2: D

Partition 3: D





Last Command: cnfrsrc 4.1 1000 300000 N




Cnfrsrc successful.

Next Command:

Example

Changing the PVC max lcn and PVC max bandwidth for a port.

cnfrsrc 5.1 2000 N

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 10:53 PST




Trunk : 5.1

Maximum PVC LCNS: 2000 Maximum PVC Bandwidth: 3528

(Statistical Reserve: 1000)





State

Partition 1: D

Partition 2: D

Partition 3: D





Last Command: cnfrsrc 5.1 2000 N




Max PVC lcn maybe adjusted to be consistent with the other end.

Next Command:

Example

Enable a partition on a port.

cnfrsrc 4.1 1000 300000 y 1 e 100 200 20 30 1000 50000

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:05 PST




Line : 4.1

Maximum PVC LCNS: 1000 Maximum PVC Bandwidth: 300000






State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW

Partition 1: E 100 200 20 30 1000 50000

Partition 2: D

Partition 3: D





Last Command: cnfrsrc 4.1 1000 300000 y 1 e 100 200 20 30 1000 50000




Cnfrsrc successful.

Next Command:

Example

Enabling a partition on a trunk.

cnfrsrc 5.1 2000 y 2 e 500 2000 55 60 1000 2000

sw188 TRM Cisco IGX 8420 9.3.1c Aug. 17 2000 11:06 PST




Trunk : 5.1

Maximum PVC LCNS: 2000 Maximum PVC Bandwidth: 1528

(Statistical Reserve: 1000)





State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW

Partition 1: D

Partition 2: E 500 2000 55 60 1000 2000

Partition 3: D






Last Command: cnfrsrc 5.1 2000 y 2 e 500 2000 55 60 1000 2000




Cnfrsrc successful.

Next Command:

Example

Configure resources on card slot 4, port 2.

cnfrsrc 4.2 256 96000 N

sw180 TN Cisco IGX 8420 9.3.r3 Dec. 19 2000 13:51 GMT




Line : 4.2

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 96000






State

Partition 1: D

Partition 2: D

Partition 3: D






Last Command: cnfrsrc 4.2 256 96000 N

Example

Configure resources on port 2 on the UXM card in slot 4.

cnfrsrc 4.2 256 3096 N

sw180 TN Cisco IGX 8420 9.3.r3 Dec. 19 2000 13:48 GMT




Line : 4.2

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 3096






State

Partition 1: D

Partition 2: D

Partition 3: D






Last Command: cnfrsrc 4.2 256 3096 N




Cnfrsrc successful.

cnfrsrc (configuring VSI resources for BPX)

Configures resources on ports, physical trunks and virtual trunks. You can partition resources for Automatic Routing Management PVCs, VSI-MPLS (Multiprotocol Label Switching), including VC Merge, or PNNI.

This command supports both physical trunks and virtual trunks. After VSI has been enabled, the virtual trunk becomes a "dedicated" VSI virtual trunk.

The switch software will prevent you from configuring VSI:

•If the virtual trunk has already been added; or

•If the VPI value has not been configured

You can configure a virtual trunk to be dedicated to VSI or to Automatic Routing Management. You cannot configure a virtual trunk for both VSI and Automatic Routing Management.

The switch software prevents a VSI partition from being disabled on a trunk interface if a PNNI controller is attached to the trunk interface controlling partition being disabled.

It is possible to have PVCs terminating on the Label Switch Controller itself. This example reserves approximately 10 Mbps (26000 cells per sec) for PVCs, and allows up to 256 PVCs on the switch port connected to the LSC.

Syntax

cnfrsrc <slot.port.vtrk>

or on physical trunks:
cnfrsrc <slot>.<port>.<vtrk> <maxpvclcns> <maxpvcbw> <y|n> <partition> <e|d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

or on feeder trunks/ports:
cnfrsrc <slot>.<port>.<vtrk> <maxpvclcns> <maxpvcbw><y|n> [<pvcstartvpi1> <pvcendvpi1> <pvcstartvpi2><pvcendvpi2><pvcstartvpi3><pvcendvpi3><pvcstartvpi4><pvcendvpi4>]<y|n> <partition> <e|d> <minvsilcns> <maxvsilcns> <vsistartvpi> <vsiendvpi><vsiminbw> <vsimaxbw>

or, for VC merge:

cnfrsrc <port number> <maxpvclcns> <maxpvcbw> <partition ID {e|d}> By default, the LSC uses either a starting VSI VPI of 1 or 2 for label switching, whichever is available. If both are available, a starting VSI VPI of 1 is used. The VPI range should be 2-3 on a BPX VSI connected to a 6400, 7200 or 7500 AIP. If VPI 2 is not to be used, you can use the label switching VPI interface configuration command on the LSC to override the defaults.

<vsistartvpi> <vsiendvpi> <vsiminbw> <vsimaxbw>

Parameters

The table lists the cnfrsrc parameters used for configuring resources for VSI partitions (an MPLS controller, for example).

Object Name	Range/Values	Default	Description
VSI partition	1-3	None	Identifies the partition.
Partition state	0 = Disable Partition 1 = Enable Partition	0	For Partition state = 1, the VSI parameters are mandatory.
Enable Partition	e or d	Enable Partition	Answer e to enable or d to disable your configured partition.
Min VSI LCNs	0 to port_group/card limit	None	Minimum LCNs (conns) guaranteed for this partition. If the parameter for VC merge is set to "e," the feature is enabled by filling at least 1023 VSI channels on any interface on the card. The maximum and minimum logical connections (LCNs) determine the maximum number of virtual connections (VCs) that can be supported on the interface. The number of VCs required on the interface is controller dependent.
Max VSI LCNs	1 to port_group/card limit	None	Maximum LCNs permitted on this partition. The maximum and minimum logical connections (LCNs) determine the maximum number of virtual connections (VCs) that can be supported on the interface. The number of VCs required on the interface is controller dependent.
Edit VSI parms	<y|n>		y= prompt for VSI parameters. n = no prompt for VSI parameters.
Start VSI VPI	1-4095	None	Partition Start VPI. By default, the LSC will use either a starting VSI VPI of 1 or 2 for label switching, whichever is available. If both are available, a starting VSI VPI of 1 is used. The VPI range should be 2-3 on a BPX VSI connected to a 6400, 7200 or 7500 AIP. If VPI 2 is not to be used, you can use the label switching VPI interface configuration command on the LSC to override the defaults.
End VSI VPI	1-4095	None	Partition End VPI. VSI connections on this partition can use VPIs up to this VPI. The end VSI VPI should be equal to or greater than the Start VSI VPI.
Min VSI Bw	0-Line Rate	None	Minimum Partition bandwidth.
Max VSI Bw	0-Line Rate	None	Maximum Partition bandwidth.

Attributes

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

Related Commands

dsprsrc

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.

Resource Partitioning

The VSIs must partition the resources between competing controllers: Automatic Routing Management, MPLS, and PNNI, for example. Different types of controllers can share a node's resources. For example, Automatic Routing Management, and MPLS, or Automatic Routing Management and PNNI (SVCs), but not PNNI and MPLS, can share resources.

Up to three partitions are supported and any three may be of a single type. The user interface will block the activation of partitions with ID higher than 1 if the card does not support multiple partitions.

The resources that you need to configure for a partition are shown in Table 3-39 for a partition designated ifci, which stands for interface controller 1, in this example.

The three parameters that must be distributed are:

•number of logical connections (LCNs)

•bandwidth (BW)

•virtual path identifiers (VPI)

Table 3-39 ifci—VSI Parameter Ranges

ifci parameters	Min	Max
LCNs	0 to port_group/card limit	1 to port_group/card limit
BW	0-Line Rate	0-Line Rate
VPI	1-4095	1-4095

When you add a trunk, the entire bandwidth is allocated to Automatic Routing Management (formerly known as AutoRoute). To change the allocation to provide resources for a VSI, use the cnfrsrc command on the BPX switch.

Figure 3-23 Graphical View of Resource Partitioning, Automatic Routing Management, and VSI

Partition Information Sent to Cisco WAN Manager

When the partition information is configured for the first time or any parameters are changed, Cisco WAN Manager is updated through a robust message.

•pvc_vpi_start_1:
This field represents start VPI range for range 1.

•pvc_vpi_end_1:
This field represents the ending VPI range for range 1.

•pvc_vpi_start_2:
This field represents start VPI range for range 2.

•pvc_vpi_end_2:
This field represents the ending VPI range for range 2.

•pvc_vpi_start_3:
This field represents start VPI range for range 3.

•pvc_vpi_end_3:
This field represents the ending VPI range for range 3.

•pvc_vpi_start_4:
This field represents start VPI range for range 4.

•pvc_vpi_end_4:
This field represents the ending VPI range for range 4.

•vsi_min_channels:
This field represents the minimum guaranteed channels available for a given port.

•vsi_max_bw:
This field represents the maximum bandwidth available, but not guaranteed, for a port.

Partitioning

On each interface (port or trunk) on the BXM cards used for PNNI/MPLS controllers, two sets of resources must be divided up between traditional PVC connections and switching connections. The traditional PVC connections are configured directly on the BPX platform, and switching connections are set up by the controllers using the VSI. These resources are partitioned on each interface:

• Bandwidth

• Logical Connections

•VPI

As with all ATM switches, the BPX switch supports up to a specified number of connections. On the BPX switch, the number of connections supported depends on the number of port/trunk cards installed. On each interface, space for connections is divided up between traditional BPX switch permanent virtual circuit (PVC) connections, Label Switching VCs (LVCs), and PNNI Switching VCs (SVC).

Soft and Dynamic Partitioning

Release 9.3.10 introduces Soft Partitioning and Dynamic Partitioning in order to support the smooth introduction of another VSI controller into a BPX network already configured with an existing VSI controller, easier tuning of switch resources, and the migration of Automatic Routing Management to PNNI.

Soft Partitioning provides resource guarantees for LCNs and bandwidth per partition and a pool of resources available to all partitions in addition to the guaranteed resources. Dynamic Partitioning provides the ability to rather easily increase the allocation of a resource to a partition.

You define and manage the number of LCNs assigned to a given VSI partition by modifying the "Minimum VSI LCNs" and "Maximum VSI LCNs" fields of the cnfrsrc CLI command.

To give more LCNs from Automatic Routing Management to VSI, change the Min LCNs or Max LCNs to cause BPX software to produce a bigger number. To increase the LCNs reserved to a VSI partition, increase the "Minimum VSI LCNs" or "Maximum VSI LCNs" fields of the appropriate VSI partition. The VSI LCN boundary is moved into Automatic Routing Management if there are enough free Automatic Routing Management LCNs to fulfill the request.

If there are not enough free LCNs in the Automatic Routing Management (AR) space, the cnfrsrc command does not fulfill a request to increase the VSI LCN space. In such a case, the cnfrsrc command displays a failure message showing the number of currently free AR LCNs. You can reissue the cnfrsrc command specifying a smaller increase to the VSI partition. If that is not acceptable, you must first delete and reroute the necessary number of AR connections. Then you can attempt cnfrsrc again.

Moving the VSI LCN boundary into the Automatic Routing Management space might step over LCNs that are currently allocated. BPX software reprogram the necessary channels so that new channels out of the lower AR LCN space are picked instead. Before starting the process of reprogramming the necessary number of AR connections, the cnfrsrc command displays a warning message and waits for your permission to proceed. The warning message shows the number of Automatic Routing Management (AR) connections that will be re-programmed. After reprogramming the necessary channels the LCN boundary is moved into the Automatic Routing Management space.

---

Note You can migrate Automatic Routing Management (AutoRoute) connections only if the VPI range of the recipient VSI partition is adjacent to Automatic Routing Management. To migrate Automatic Routing Management connections to a non-adjacent VSI partition requires different VPIs within the recipient VPI boundary.

---

Information about this feature also can be found in the BPX Installation and Configuration Manual, Release 9.3.10, Configuring BXM Virtual Switch Interface.

VSI Partitioning

VSI partitioning requires the following commands and procedures:

Defining the PVC VPI Range

You can define the PVC VPI ranges by filling the VSI fields described in the previous section. In the following sample system response of the cnfrsrc command, note that the * next to the VPI fields denote that the PVC and VSI VPI space overlap. You are prompted if the overlapping VSI partition is an MPLS partition. If it is, then the command will be abort because overlapping VPI ranges between Automatic Routing Management and MPLS is not supported.

Configuring the PVC VPI ranges requires the BXM card to have VSI level 3 support. An error message is displayed if you want to configured the PVC VPI ranges but the VSI level on the card is lower than 3.

Increasing the VSI LCN Range

You can increase the number of LCNs reserved for VSI by increasing the Minimum VSI LCNs and/or Maximum VSI LCNs of the appropriate VSI partition. Increasing the VSI LCN space may cause a number of AR connections to be reprogrammed. You will see a warning: "Channel conflict, max LCN w/o reprog = 5. LCN(s) to reprogram = 20." The command will proceed only if you so choose.

Increasing the Number of LCNs Guaranteed for a VSI Partition

You can increase the number of LCNs guaranteed for a given VSI partition by increasing the Minimum VSI LCNs of the desired partition. If the new number does not cause the total VSI LCNs to be increased (that is, if you want to increase the Minimum VSI LCNs at the expense of the common pool), the request will be denied if there isn't enough free VSI LCNs in the common pool. The BXM card cannot find enough free VSI LCNs to give to the specified partition. More AR LCNs must be made available to VSI for the request to succeed. The cnfrsrc will display a message: "Resource not available, maximum available LCN(s) is 50. 100 more LCN needed." This indicates the number of AR LCNs that should be made available to the VSI.

Increasing VSI Bandwidth

You can increase the bandwidth of VSI by increasing the Minimum VSI Bandwidth or Maximum VSI Bandwidth of the appropriate VSI partition.

---

Note Increasing VSI bandwidth may trigger a rerouting of all connections on that trunk.

---

Disabling Connection Admission Control (CAC) on a Port

To oversubscribe the AR bandwidth on a given port, make sure that the CAC feature is disabled on the port. Use the cnfport command for this purpose; the CAC Override field should specify "Enabled".

cnfport <slot.port>[.vtrk] <options for E1 | T1 | E3 | T3 | OC-3 | OC-12 | E2 | HSSI | SR >

Oversubscribing AR Bandwidth on a Port

To oversubscribe the AR bandwidth on a given port, make sure that the CAC feature is disabled on the port. Refer to Disabling Connection Admission Control (CAC) on a Port for more details.

Use the cnfrsrc command to decrease the bandwidth allocated for AR and give it to the VSI partition that is going to receive the AR connections. The cnfrsrc command contains 4 fields that specify information about the bandwidth:

•Maximum PVC Bandwidth
Specifies the maximum bandwidth that can be used by AR.

•Statistical Reserve
Applicable only to trunks. It specifies the bandwidth that should be set aside for node to node communications.

•Minimum VSI Bandwidth

•Maximum VSI Bandwidth

The cnfrsrc command verifies that the sum of the Maximum PVC Bandwidth, Statistical Reserve, and the VSI bandwidth of all VSI partitions on the port does not exceed the port speed.

You can decrease the AR bandwidth by decreasing the Maximum PVC Bandwidth field. To increase the VSI bandwidth:

•If the total bandwidth allocated for VSI was obtained by adding the Minimum VSI Bandwidth of all the VSI partitions on the port, you can give more bandwidth to VSI by increasing the Minimum VSI Bandwidth of a given partition.

•If the total bandwidth allocated for VSI was obtained by using the Maximum VSI Bandwidth of a given partition, you can give more bandwidth to VSI by increasing the Maximum VSI Bandwidth field of the partition that was used to compute the VSI bandwidth.

In the example below you can see that all of the AR bandwidth on the port was given to VSI. Note the * next the Maximum PVC Bandwidth shows that the AR bandwidth is oversubscribed.

Example

Configure the VSI partition1 for port 4.1 without defining PVC VPI ranges.

cnfrsrc 12.5 256 26000 N Y 1 e 512 16384 2 15 26000 100000

n4 TN SuperUser BPX 8620 9.3.10     Apr. 4 2000    16:40 PST

Port : 4.1

Full Port Bandwidth: 353208

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 26000

(CAC Reserve: 0)




PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Enabled Disabled Disabled

VSI LCNS (min/max): 512 /7000 0 /0 0 /0

VSI VPI (start/end): 2/15 0 /0 0 /0

VSI BW (min/max): 26000 /100000 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 12.5 256 26000 N Y 1 e 512 7000 2 15 26000 100000




Next Command:

Example

Configure the VSI partition1 for port 4.1, defining overlapping PVC VPI ranges. The overlapping VPI ranges are indicated by an asterisk * next to the range values.

cnfrsrc 12.5 256 26000 Y 0 255 -1 -1 -1 -1 -1 -1 Y 1 e 512 16384 2 15 26000 100000

n4 TN SuperUser BPX 8620 9.3.10     Apr. 4 2000    16:40 PST

Port : 4.1

Full Port Bandwidth: 353208

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 26000

(CAC Reserve: 0)




PVC VPI RANGE [1]: 0 */255 * PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Enabled Disabled Disabled

VSI LCNS (min/max): 512 /7000 0 /0 0 /0

VSI VPI (start/end): 2 */15 * 0 /0 0 /0

VSI BW (min/max): 26000 /100000 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 12.5 256 26000 Y 0 255 -1 -1 -1 -1 -1 -1 Y 1 e 512 7000 2 15 26000 100000




Next Command:

Example

Configure the VSI partition1 for trunk 12.5. You are not prompted for "configure PVC VPI ranges".

cnfrsrc 12.5 256 26000 Y 1 e 512 16384 2 15 26000 100000

n4 TN SuperUser BPX 8620 9.3.10     Apr. 4 2000    16:40 PST

Trunk: 4.1

Full Port Bandwidth: 353208

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 26000

(CAC Reserve: 1000)




PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Enabled Disabled Disabled

VSI LCNS (min/max): 512 /7000 0 /0 0 /0

VSI VPI (start/end): 2 /15 0 /0 0 /0

VSI BW (min/max): 26000 /100000 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 12.5 256 352207 Y 1 e 512 7000 2 15 26000 100000




Example

Enable VC merge on the partition on slot 1.

cnfrsrc 12.1 256 91000 y 1 E 200 200 10 10 0 0

m2 TN Cisco BPX 8620 9.3.a0 May 8 2001 17:40 GMT




Trunk : 12.1

Full Port Bandwidth: 96000

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 91000

(Statistical Reserve: 5000)




PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Enabled Disabled Disabled

VSI LCNS (min/max): 200 /200 0 /0 0 /0

VSI VPI (start/end): 10 /10 0 /0 0 /0

VSI BW (min/max): 0 /0 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 12.1 256 91000 y 1 E 200 200 10 10 0 0

Example

Disable VC merge by disabling the last partition on a slot.

cnfrsrc 12.1 256 91000 y 1 d




m2 TN Cisco BPX 8620 9.3.a0 May 8 2001 18:06 GMT




Trunk : 12.1

Full Port Bandwidth: 96000

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 91000

(Statistical Reserve: 5000)




PVC VPI RANGE [1]: -1 /-1 PVC VPI RANGE [2]: -1 /-1

PVC VPI RANGE [3]: -1 /-1 PVC VPI RANGE [4]: -1 /-1




Partition : 1 2 3

Partition State : Disabled Disabled Disabled

VSI LCNS (min/max): 200 /200 0 /0 0 /0

VSI VPI (start/end): 10 /10 0 /0 0 /0

VSI BW (min/max): 0 /0 0 /0 0 /0

VSI ILMI Config: CLR CLR CLR




Last Command: cnfrsrc 12.1 256 91000 y 1 d

cnfrtcost (display connection loading)

Configures the cost cap for a connection when cost-based routing is configured.

A maximum allowable cost value (cost cap) is used during route determination to prevent selection of a route that exceeds an acceptable cost. For routing based on delay, the cost cap is the acceptable end-to-end delay for the connection type. This cap is configured network-wide per delay-sensitive connection type.

For routing based on trunk cost, the cost cap is the acceptable end-to-end cost. This cap is configured per connection. The default cost cap is 100, which is derived from the maximum hops per route (10) and default cost per trunk (10). The cost cap can be changed at any time. If the cost cap is decreased below the current route cost, the connection is not automatically rerouted. A manual reroute is required to route the connection to fit under the new cost cap. This gives you more control over the connection reroute outage.

---

Note The cnfrtcost is valid only at the node where the connection was added.

---

Syntax

cnfrtcost <connection> <max cost>

Parameters

Parameter	Description
<connection>	Indicates the connection endpoint (that is, slot.port.vpi.vci)
<max cost>	Indicates the maximum allowable route cost. Range: 1-100

Attributes

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

Related Commands

dspcon, cnfpref, dsprtcache

Example

After configuring the cost cap for a connection, you can check to see the configured value with the dspcon command, as is shown in the System Response example. This is the dspcon response for 9.2.5.100 with the additional fields of Max Cost (40) and Route Cost (1). For a route optimized on trunk delay, the cost labels are updated to indicate delay: Max Cost becomes Max Delay and Route Cost becomes Route Delay.

cnfrtcost 9.2.5.100 40 1

sw203 TN StrataCom BPX 8620 9.3 Apr. 13 2000 18:18 GMT

Conn: 9.2.5.100 sw242 14.2.5.100 cbr Status:OK

PCR(0+1) % util CDVT(0+1) Policing

50/50 100/100 10000/10000 4/4

Owner: LOCAL Restriction: NONE CoS: 0

TestRTD: 0 msec Trunk Cell Routing Restrict: Y Max Cost: 40 Route Cost: 1

Path: sw203 3.1.1-- 2.1.1sw242

Pref: Not Configured

sw203 ASI-T3 : OK sw242 ASI-OC-3 : OK

Line 9.2 : OK Line 14.2 : OK

OAM Cell RX: Clear NNI : OK

NNI : OK

Last Command: dspcon 9.2.5.100

Next Command:




cnfrtr (configure router configuration parameters)

Configures the parameters for the Universal Router Module (URM) embedded IOS-based router on a specified router slot. Configurable router parameters include the IOS configuration file source and the router serial port function. The cnfrtr command can be invoked on a logically active or standby slot. For additional information on the URM and a complete listing of the CLI commands that support the embedded IOS-based router, see the "Universal Router Module" section on page 2-23.

Upon start-up, reset or restart, the embedded router must load an IOS configuration file. Use the cnfrtr command to specify the source, or location, of the IOS configuration file that the router is to use. Starting with Release 9.3.30, there are three IOS configuration file sources. These sources are:

•The NPM BRAM, which stores a default blank, or basic, IOS configuration file. This is the default IOS configuration file source.

•The embedded router NOVRAM, which stores the router's running IOS configuration file.

•The URM Admin flash, which stores an IOS configuration file that is downloaded from a TFTP server. This file location is supported only with the Release 9.3.30 or higher.

By default, the URM is configured to load the basic IOS configuration file from the NPM. The NPM BRAM can be configured as the IOS configuration file source for the embedded router when the URM is installed or replaced.

With Release 9.3.20, the initial configuration on the router must be done manually using the IOS CLI. With the Release 9.3.30 Remote Router Configuration feature, however, the URM Admin flash can store an IOS configuration file that is downloaded from a TFTP server. This downloaded file can be used to start up the router with an initial configuration, eliminating the need for console access to the embedded router. See the "URM Remote Router Configuration Feature" section for additional information.

During normal operations, the running IOS configuration file is stored in the embedded router NOVRAM. The running IOS configuration file is required for the router to resume normal operation in the event of a card reset or restart. The router NOVRAM can be configured as the IOS configuration file source for the embedded router during normal operations.

Syntax

cnfrtr <router_slot> <IOS_configuration> <serial_port_function>

Parameters

Parameter	Description
router slot	Specifies the virtual shelf slot to support the URM embedded router. Range: 1-32 Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains an IGX card without an embedded router. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.
IOS configuration	Specifies the location, or source, of the IOS configuration file the embedded router is to use at start-up, reset, or restart. Default: NPM (n) n = NPM. This configuration specifies that the default blank, or basic, IOS configuration file is loaded from the NPM BRAM. This configuration file can be used when the URM is installed or replaced. r = Router BRAM. This configuration specifies that the IOS configuration file is loaded from the embedded router BRAM. This configuration is required for the router to resume normal operation in the event of a card restart or rebuild. a = Admin flash. This configuration specifies that the IOS configuration file is loaded from the URM Admin flash. Starting with Release 9.3.30, an IOS configuration file can be downloaded from a TFTP server and stored in the URM Admin flash. This file can be used for initial router configuration at the time of router start-up.
serial port function	Specifies the function of the router serial port. Default: CON 1 = CON (console). This configuration specifies that the router serial port functions as a console external interface. 2 = AUX (auxiliary). This configuration specifies that the router serial port functions as an auxiliary external interface. This configuration is typically used for monitoring purposes.

Attributes

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

Related Commands

burnrtrcnf, clrrtrcnf, cnfrtr, cnfrtrcnfmastip, cnfrtrparm, dspalms, dspcnf, dsprtr, dsprtrcnfdnld, dsprtrslot, dsprtrslots, rstrtr

Example

Configure parameters for the URM embedded router on router slot 10. Select the URM Admin flash as the IOS configuration file source. Select console as the serial port function.

cnfrtr 6

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 05:26 GMT




Configuration for Router Slot 10: Snapshot

IOS Configuration: from card's Admin Flash

Router Serial Port: CON
















Last Command: cnfrtr 10 a 1

URM Remote Router Configuration Feature

Starting with Release 9.3.30, the URM supports the Remote Router Configuration feature. This feature allows you to start up or restart the URM embedded IOS router with an IOS configuration file that is downloaded from a TFTP server. The process of passing the IOS configuration file to the URM embedded router is similar to the process of downloading firmware images to cards. The steps in the transfer process, and the IGX CLI commands utilized, are summarized below.

•Clear the NPM RAM buffer of firmware images, save/restore configuration files, and any previous IOS configuration files. Use the dspcnf command to display the configuration save/restore status of the network nodes and identify nodes reserved for firmware images or IOS configuration files. Use the getfwrev <cardtype>0.0 to clear firmware images. Use the savecnf clear command to clear save/restore configuration files. Use the clrrtrcnf command to clear IOS configuration files.

•Create a directory and the IOS configuration file on the TFTP server from which the file is to be transferred. Use the cnfrtrcnfmastip command to specify the IP address of the authorized TFTP server.

•Send a TFTP Start file (through TFTP put) to the IGX node to initiate transfer of the IOS configuration file to the NPM RAM buffer. The interface for transferring the IOS configuration file is the same interface used to transfer firmware images. Use the dsprtrcnfdnld command to monitor the progress of the file transfer.

•Copy (or burn) the IOS configuration file from the NPM RAM buffer to the URM Admin flash. Use the burnrtrcnf command to copy the configuration file. Use the dsprtrcnfdnld command to monitor the progress of the copy activity.

•Use the cnfrtr command to configure the URM Admin flash as the source of the IOS configuration file stored in the URM Admin flash. With this configuration, the router uses the configuration file stored in the URM Admin flash at start up and upon reset or restart.

The interface for transferring the IOS configuration file is the same as the interface for transferring firmware images by TFTP. A Start file is sent to the node through TFTP put. The Start file contains the information to start the IOS configuration file download. Upon receipt of the Start file, the IGX node drives the process of transferring the IOS configuration file from the TFTP server to the NPM RAM buffer. The RAM buffer used is the same buffer used to store firmware images and node configuration save/restore files.

The name of the TFTP Start file for the IOS configuration file is always dnld.rtr. The Start file format is described below.

TFTP_REQUEST

•IP: <IP_address>. Specifies the IP address of the TFTP server storing the IOS configuration file.

•Path Name: <pathname>. Specifies the path name to the IOS configuration file stored on the TFTP server.

•File Name: <filename>. Specifies the name of the IOS configuration file stored on the TFTP server.

cnfrtrcnfmastip (configure router configuration download initiator TFTP server IP)

Configures the IP address of the authorized TFTP client which could initiate the TFTP start file transfer. This command ensures that only an authorized client initiates the transfer of the IOS configuration file.

The cnfrtrcnfmastip command supports the URM Remote Router Configuration feature introduced in Release 9.3.30. This feature allows you to start up or restart the URM embedded IOS router with an IOS configuration file that is downloaded from a TFTP server. For additional information on the URM and Remote Router Configuration feature see the cnfrtr command description.

Syntax

cnfrtrcnfmastip <IP_address>

Parameters

Parameter	Description
IP address	IP address of the authorized TFTP client which initiates transfer of the IOS configuration file. The cnfrtrcnfmastip command modifies the same IP address as the cnffwswinit command. These two commands can be used interchangeably.

Attributes

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

Related Commands

burnrtrcnf, clrrtrcnf, cnfrtr, dspcnf, dsprtr, dsprtrcnfdnld, dsprtrslot

Example

cnfrtrcnfmastip

sw175 TN Cisco IGX 8420 9.3.q6 Mar. 9 2000 07:45 GMT










Last Command: cnfrtrcnfmastip 172.29.10.43

cnfrtrparm (configure router service parameters)

Configures service parameters for the embedded router in the Universal Router Module (URM) introduced on the IGX 8400 in Release 9.3.20. The URM provides IOS-based voice support and basic routing functions. It consists of an embedded UXM with one internal ATM port and an embedded IOS-based router.

Syntax

cnfrtrparm <router_slot> <index> <action>

Parameters

Parameter	Description
router slot	Specifies the virtual shelf slot to support the URM embedded router. Range: 1-32 Switch software manages the embedded router in the URM as if the router resides on a slot in a virtual shelf (of routers). Each slot in the IGX shelf has a corresponding router slot in the virtual shelf. A router slot is considered empty when the equivalent IGX slot is empty or contains an IGX card without an embedded router. If the IGX slot contains a URM card, the router slot is reported as hosting an IOS router.
rommon action	Specifies what action ROMMON is to take when the URM embedded router boots up. Range: 1, 2, 3, or 4 Default: 1, load IOS. 1. IOS: if this parameter is set to IOS, the router loads the IOS image from the Flash. 2. BootHelper: if this parameter is set to BootHelper, the router loads BootHelper from the Flash protected area. 3. Rommon-CLI: if this parameter is set to Rommon-CLI, the router enters ROM monitor or maintenance mode. When the router is in this state, you can enter ROM monitor commands from the console port to manually load a system image. 4. Cnfg-register: if this parameter is set to cnfg-register, the router performs the action that was configured in the router's Configuration Register Boot Field.
reset router on IOS IPC failure	Specifies whether the router IOS is reset in the event of an IOS IPC failure. Range: Y to enable or N to disable. Default: Y, enable.
bootflash write enable	Enables write to router BootFlash. Range: Y to enable or N to disable. Default: N, disable.

Attributes

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

Related Commands

cnfrtr, dsprtr, dsprtrslot, dsprtrslots, dspalms, rstrtr

Example: Configure Rommon Action

Configure the Rommon Action parameter by using the cnfrtrparm command.




sw180 TN Cisco IGX 8420 9.3.2J Nov. 7 2000 07:18 GMT




1 Rommon Action [ load IOS ]

2 Reset Router on IOS IPC Failure [ No ]

3 BootFlash Write Enable [ Yes ]





This Command: cnfrtrparm 15 1





load (1)IOS, (2)BootHelper, (3)Rommon-CLI (4)Cnfg-register:

Example: Configure Reset Router Parameter

Configure the Reset Router on IOS IPC Failure parameter by using the cnfrtrparm command.

sw180 TN Cisco IGX 8420 9.3.2J Nov. 7 2000 07:19 GMT




1 Rommon Action [ load IOS ]

2 Reset Router on IOS IPC Failure [ No ]

3 BootFlash Write Enable [ Yes ]





This Command: cnfrtrparm 15 2





Reset IOS on IPC failure ?




Example: Configure Reset Router Parameter

Configure the BootFlash Write Enable parameter by using the cnfrtrparm command.

sw180 TN Cisco IGX 8420 9.3.2J Nov. 7 2000 07:20 GMT




1 Rommon Action [ load IOS ]

2 Reset Router on IOS IPC Failure [ No ]

3 BootFlash Write Enable [ Yes ]





This Command: cnfrtrparm 15 3





Enable write to router BootFlash?




cnfslotalm (configure slot alarm parameters)

Configure the alarm parameters for the various card types. Upon command entry, the system displays a screen with a choice of eight card-alarm types. It then displays "Enter Type" and waits for a number in the range 1-12. Upon entry of the alarm type, the system displays the error rates of the selected type.

Syntax

cnfslotalm <fail_type> <alarm_class> <rate> <alarm_time> <clear_time>

Parameters

Parameter	Description
<fail_type>	Error type
<alarm_class>	Either major or minor
<rate>	Error frequency
<alarm_time>	Duration of prescribed error frequency required to declare an alarm.
<clear_time>	The alarm will clear after this amount of time if the alarm threshold is no longer met

Attributes

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

Related Commands

dspslotalmcnf, dspslotalms

Example

Configure the alarm parameters.

cnfslotalm 10

pubsbpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 19:43 PST




Slot Alarm Types




1) Standby PRBS Errors 11) Poll Clk Errors

2) Rx Invalid Port Errs 12) CK 192 Errors

3) PollA Parity Errors

4) PollB Parity Errors

5) Bad Grant Errors

6) Tx Bip 16 Errors

7) Rx Bip 16 Errors

8) Bframe parity Errors

9) SIU phase Errors

10) Rx FIFO Sync Errors




This Command: cnfslotalm





Enter Type:




The screen display after selecting alarm type 10:

pubsbpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 19:47 PST




Slot Alarm Configuration




Minor Major




Violation Rate Alarm Time Clear Rate Alarm Time Clear

1) SPRBS .1% 10 min 3 min 1% 100 sec 100 sec

2) InvP .1% 10 min 3 min 1% 100 sec 100 sec

3) PollA .1% 10 min 3 min 1% 100 sec 100 sec

4) PollB .1% 10 min 3 min 1% 100 sec 100 sec

5) BGE .1% 10 min 3 min 1% 100 sec 100 sec

6) TBip .1% 10 min 3 min 1% 100 sec 100 sec

7) RBip .1% 10 min 3 min 1% 100 sec 100 sec

8) Bfrm .1% 10 min 3 min 1% 100 sec 100 sec

9) SIU .1% 10 min 3 min 1% 100 sec 100 sec

10) RFifo .1% 10 min 3 min 1% 100 sec 100 sec




Last Command: cnfslotalm 10





Next Command:

cnfslotstats (configure slot statistics collection)

Configures the statistics for a card slot. This command is primarily a troubleshooting tool for use when hardware errors are experienced that might not be detected by the individual care self-test routines. An associated display command (dspsloterrs) is available for all users.

This command sets the collection interval for each of the BPX node slot statistics. The default is for no statistics to be collected. The collection interval range is 1 minute-255 minutes (4 1/4 hours).

You must enter the statistic type (1-9) to set the collection interval. When you enter the command, the system responds with the following prompt:

Collection Interval (1-255 minutes): __




Table 3-40 lists the statistics associated with each slot in the BPX node.

Syntax

cnfslotstats <port> <stat> <interval> <e|d> [<samples> <size> <peaks>]

Parameters

Parameter	Description
<port>	Specifies the port to configure.
<stat>	Specifies the type of statistic to enable/disable.
<interval>	Specifies the time interval of each sample (1-255 minutes).
<e|d>	Enables/disables a statistic. E to enable; D to disable.
[samples]	Specifies the number of samples to collect (1-255).
[size]	Specifies the number of bytes per data sample (1, 2 or 4).
[peaks]	Enables the collection of one minute peaks. Y to enable; N to disable.

Attributes

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

Related Commands

dspsloterrs

Table 3-40 Statistics Associated with Each Slot in a BPX Node  

Error	Description
Standby Bus Errors	Indicates a background test over the standby bus produced an error.
Rx Invalid Port Errors	Indicates port number was out of the range 1-3.
Polling Bus A Errors	Parity error occurred on this polling bus.
Polling Bus B Errors	Parity error occurred on this polling bus.
Bad Grant Errors	Error indicates arbiter did not issue a grant to send data before a time-out.
Tx BIP-16 Errors	Data frame transmitted had a checksum error.
Rx BIP-16 Errors	Data frame received with a checksum error.
Bframe parity errors	Errors detected in the BPX frame on the StrataBus or in a memory operation.
SIU Phase Errors	Serial Interface Unit on the card did not detect the frame synch properly.
Rx FIFO Sync Errors	First-In-First-Out buffer synchronization errors.
Poll Clk Errors	Polling clock errors.
CK 192 Errors	Clock 192 errors.
Monarch Specific Errors	Errors that occur on only the BXM.

Example

cnfslotstats 8

sw81 TN SuperUser BPX 15 9.3 Apr. 13 2000 15:42 PST




Card Statistics Types




1) Standby PRBS Errors

2) Rx Invalid Port Errs

3) PollA Parity Errors

4) PollB Parity Errors

5) Bad Grant Errors

6) Tx Bip 16 Errors

7) Rx Bip 16 Errors

8) Bframe parity Errors

9) SIU phase Errors

10) Rx FIFO Sync Errors

11) Poll Clk Errors

12) CK 192 Errors

13) Monarch Specific Errors




This Command: cnfslotstats 8

cnfsnmp (configure SNMP parameters)

Configures the SNMP GET and SET community strings.

Syntax

cnfsnmp <GET community string> <SET community string>

Parameters

Parameter	Description
get community string	Specifies the GET community string.
set community string	Specifies the SET community string.

Attributes

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

Related Commands

dspsnmp, dspsnmpstats

Example

Configure the SNMP GET and SET community string parameters.

cnfsnmp

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 09:06 GMT




Get Community String: audit

Set Community String: private

Trap Community String: private




SNMP Set Request Queue Size: 110

SNMP Queued Request Timeout (secs): 21600

SNMP Trap Event Queue Size: 100







Last Command: cnfsnmp

cnfstatmast (configure statistics master SV+ address)

Configures an IP address for the Statistics Master process in WAN Manager. The cnfstatmast command defines the IP address for routing the messages to and from the Statistics Master in WAN Manager.

The Statistics Master process requests and receives network statistics by using TFTP Get and Put messages. These TFTP messages pass between the node and the Statistics Master over IP Relay. See the cnfnwip description for details on setting a node address.

Syntax

cnfstatmast <IP Address>

Parameters

Parameter	Description
<IP Address>	Specifies the IP address for the Statistics Master. IP addresses have 32-bits. The format of an IP address is x.x.x.x, where x is a value in the range 1-255.

Attributes

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

Related Commands

cnfnwip, dspnwip

Example

Configure 199.35.96.217 as the IP address for the Statistics Master.

cnfstatmast 199.35.96.217

cnfstatparms (configure TFPT statistics parameters)

Configures collection of TFTP statistics for the BPX and IGX. This is primarily a Debug command.

Syntax

cnfstatparms <retry> <timeout> <bucket interval> <file interval> <peak> <option>

Parameters

Parameter	Description
<retry>	Number of times TFTP should try again when a TFTP error (such as timeout) occurs. Range: 0-5
<timeout>	TFTP acknowledgement timeout. Range: 0-100 seconds
<bucket interval>	Length of the bucket interval. Valid values: 5, 10, 15, 30, 60 minutes
<file interval>	Length of the file interval. Valid values: 15, 30, 60 minutes. Must be a multiple of Bucket Interval.
<peak>	Enable peak statistics. Values: T(rue) | F(alse)
<option>	Enable all statistics or individually selected ones. Values: 1 (All), 2 (User Defined) Depending on the value entered here, you are prompted for more questions.

Related Commands

dspstatparms, dsptrkerrshist

Attributes

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

Example (UXM on the IGX)

cnfstatparms 5 5 5 15 1 2

sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Available Statistic Object Types:




1: Connections

2: Service Interfaces

3: Trunks

4: Ports

5: Physical Lines

.: Quit







This Command: cnfstatparms 5 5 5 15 1 2

Enter Object Type (numeric value): 3




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Available Object Sub-types:




1: Narrow Band

2:

3: BPX 8600 ATM

4: IGX 8400 ATM

.: Quit






This Command: cnfstatparms 5 5 5 15 1 2





Enter Object Sub Type (numeric value): 4

Enter Peak Value (secs): 300




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Virtual Interface Statistic Types




1) QBIN: Voice Cells Tx to line 14) QBIN: Tx BData A Cells Discarded

2) QBIN: TimeStamped Cells Tx to ln 15) QBIN: Tx BData B Cells Discarded

3) QBIN: NTS Cells Tx to line 16) QBIN: Tx CBR Cells Discarded

4) QBIN: Hi-Pri Cells Tx to line 17) QBIN: Tx ABR Cells Discarded

5) QBIN: BData A Cells Tx to line 18) QBIN: Tx nrt-VBR Cells Discarded

6) QBIN: BData B Cells Tx to line 19) QBIN: Tx NTS Cells Received

7) QBIN: Tx CBR Cells Served 20) QBIN: Tx Hi-Pri Cells Received

8) QBIN: Tx nrt-VBR Cells Served 21) QBIN: Tx Voice Cells Received

9) QBIN: Tx ABR Cells Served 22) QBIN: Tx TS Cells Received

10) QBIN: Tx NTS Cells Discarded 23) QBIN: Tx BData A Cells Received

11) QBIN: Tx Hi-Pri Cells Discarded 24) QBIN: Tx BData B Cells Received

12) QBIN: Tx Voice Cells Discarded 25) QBIN: Tx CBR Cells Received

13) QBIN: Tx TS Cells Discarded 26) QBIN: Tx ABR Cells Received




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Virtual Interface Statistic Types




27) QBIN: Tx nrt-VBR Cells Received 40) CGW: Packets Rx From Network

28) VI: Cells rcvd w/CLP=1 41) CGW: Cells Tx to Line

29) VI: OAM cells received 42) CGW: NIW Frms Relayed to Line

30) VI: Cells tx w/CLP=1 43) CGW: SIW Frms Relayed to Line

31) VI: Cells received w/CLP=0 44) CGW: Aborted Frames Tx to Line

32) VI: Cells discarded w/CLP=0 45) CGW: Dscd Pkts

33) VI: Cells discarded w/CLP=1 46) CGW: 0-Length Frms Rx from Network

34) VI: Cells transmitted w/CLP=0 47) CGW: Bd CRC16 Frms Rx from Network

35) VI: OAM cells transmitted 48) CGW: Bd Lngth Frms Rx from Network

36) VI: RM cells received 49) CGW: OAM RTD Cells Tx

37) VI: RM cells transmitted 50) CF: Egress Packet Sequence Errs

38) VI: Cells transmitted 51) CF: Egress Bad HEC from cellbus

39) VI: Cells received 52) CF: Egress Packets from cellbus




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Virtual Interface Statistic Types




53) CF: Egress Cells Tx to Line 66) CF: Ingress Cells from Line

54) CGW: Packets Tx to Network 67) IE: Egress Packets to Extract Buf

55) CGW: Cells Rx from Line 68) IE: Egress Cells injected

56) CGW: NIW Frms Relayed from Line 69) IE: Egress Packets Extract Buf full

57) CGW: SIW Frms Relayed from Line 70) IE: Ingress Cells to Extract Buf

58) CGW: Abrt Frms 71) IE: Ingress Packets injected

59) CGW: Dscd Cells 72) IE: Ingress Cells Extract Buf full

60) CGW: 0-Lngth Frms Rx from Line 73) QBIN: Tx Q10 Cells Served

61) CGW: Bd CRC32 Frms Rx from Line 74) QBIN: Tx Q10 Cells Discarded

62) CGW: Bd Lngth Frms Rx from Line 75) QBIN: Tx Q10 Cells Received

63) CGW: OAM RTD Cells Rx 76) QBIN: Tx Q11 Cells Served

64) CGW: OAM Invalid OAM Cells Rx 77) QBIN: Tx Q11 Cells Discarded

65) CF: Ingress Packets to cellbus 78) QBIN: Tx Q11 Cells Received




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Virtual Interface Statistic Types




79) QBIN: Tx Q12 Cells Served

80) QBIN: Tx Q12 Cells Discarded

81) QBIN: Tx Q12 Cells Received

82) QBIN: Tx Q13 Cells Served

83) QBIN: Tx Q13 Cells Discarded

84) QBIN: Tx Q13 Cells Received

85) QBIN: Tx Q14 Cells Served

86) QBIN: Tx Q14 Cells Discarded

87) QBIN: Tx Q14 Cells Received

88) QBIN: Tx Q15 Cells Served

89) QBIN: Tx Q15 Cells Discarded

90) QBIN: Tx Q15 Cells Received





This Command: cnfstatparms 5 5 5 15 1 2





Enter Statistic Type ('.' to quit):




=============================================================================

*** cnfstatparms for IGX UXM Port Statistics

=============================================================================






sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Available Statistic Object Types:




1: Connections

2: Service Interfaces

3: Trunks

4: Ports

5: Physical Lines

.: Quit






This Command: cnfstatparms 5 5 5 15 1 2





Enter Object Type (numeric value): 4




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Available Object Sub-types:




1: Frame Relay Ports

2: ATM Ports

3:

.: Quit













This Command: cnfstatparms 5 5 5 15 1 2





Enter Object Sub Type (numeric value): 2

Enter Peak Value (secs): 300




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Port Statistic Types




1) Frames Received 14) LMI UNI Status Update Count

2) Frames Transmitted 15) LMI Invalid Status Enquiries

3) Bytes Received 16) LMI UNI Link Timeout Errors

4) Bytes Transmitted 17) LMI UNI Keepalive Sequence Errors

5) Frames Transmitted with FECN 18) Receive Frames Undefined DLCI Count

6) Frames Transmitted with BECN 19) DE Frames Dropped

7) Receive Frame CRC Errors 20) LMI NNI Status Enquiries

8) Invalid Format Receive Frames 21) LMI NNI Status Receive Count

9) Receive Frame Alignment Errors 22) LMI NNI Status Update Count

10) Illegal Length Receive Frames 23) LMI NNI Keepalive Sequence Errors

11) Number of DMA Overruns 24) LMI NNI Link Timeout Errors

12) LMI UNI Status Enquiries 25) CLLM Frames Transmitted

13) LMI UNI Status Transmit Count 26) CLLM Bytes Transmitted




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Port Statistic Types




27) CLLM Frames Received 40) VI: Cells discarded w/CLP=0

28) CLLM Bytes Received 41) VI: Cells discarded w/CLP=1

29) CLLM Failures 42) VI: Cells transmitted w/CLP=0

30) Tx Frames Discarded - Queue Overflow43) VI: OAM cells transmitted

31) Tx Bytes Discarded - Queue Overflow 44) VI: RM cells received

32) Tx Frames while Ingress LMI Failure 45) VI: RM cells transmitted

33) Tx Bytes while Ingress LMI Failure 46) VI: Cells transmitted

34) PORT: Unknwn VPI/VCI cnt 47) VI: Cells received

35) VI: Cells rcvd w/CLP=1 48) PORT: # of cells rcvd

36) VI: OAM cells received 49) PORT: # of cells xmt

37) VI: Cells tx w/CLP=1 50) INVMUX: maximum diff delay

38) PORT: Last unknown VPI/VCI pair 51) INVMUX: HEC cell errors

39) VI: Cells received w/CLP=0 52) INVMUX: LCP cell errors




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Port Statistic Types




53) INVMUX: Cell Hunt Count 66) LMI: Status messages xmt

54) INVMUX: Bandwidth Change Count 67) LMI: Updt Status msgs xmt

55) ILMI: Get Req PDUs rcvd 68) LMI: Status Ack msgs xmt

56) ILMI: GetNxt Req PDUS rx 69) LMI: Status Enq msgs rcvd

57) ILMI: GetNxt Req PDUS xmt 70) LMI: Status Enq msgs xmt

58) ILMI: Set Req PDUs rcvd 71) LMI: Status msgs rcvd

59) ILMI: Trap PDUs rcvd 72) LMI: Updt Status msg rcvd

60) ILMI: Get Rsp PDUs rcvd 73) LMI: Status Ack msg rcvd

61) ILMI: Get Req PDUs xmt 74) LMI: Invalid LMI PDUs rcvd

62) ILMI: Get Rsp PDUs xmt 75) LMI: Invalid LMI PDU length rcvd

63) ILMI: Set Req PDUs xmt 76) LMI: Unknown LMI PDUs rcvd

64) ILMI: Trap PDUs xmt 77) LMI: Invalid LMI IE rcvd

65) ILMI: Unknwn PDUs rcvd 78) LMI: Invalid Transaction IDs




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Port Statistic Types




79) INVMUX: Unavailable Seconds 92)

80) INVMUX: Near End Fail Count 93)

81) INVMUX: Last Proto Fail Code 94)

82) INVMUX: Slowest Link 95)

83) 96)

84) 97)

85) 98)

86) Q2 Cells Tx 99)

87) Tx Q2 CDscd 100)

88) Egr CRx Q2 101) Q7 Cells Tx

89) Q3 Cells Tx 102) Tx Q7 CDscd

90) Tx Q3 CDscd 103) Egr CRx Q7

91) Egr CRx Q3 104) Q8 Cells Tx




This Command: cnfstatparms 5 5 5 15 1 2





Continue?




sw144 TN Cisco IGX 8420 9.3.1x Date/Time Not Set




Port Statistic Types




105) Tx Q8 CDscd 118) Egr CRx Q12

106) Egr CRx Q8 119) Q13 Cells Tx

107) Q9 Cells Tx 120) Tx Q13 CDscd

108) Tx Q9 CDscd 121) Egr CRx Q13

109) Egr CRx Q9 122) Q14 Cells Tx

110) Q10 Cells Tx 123) Tx Q14 CDscd

111) Tx Q10 CDscd 124) Egr CRx Q14

112) Egr CRx Q10 125) Q15 Cells Tx

113) Q11 Cells Tx 126) Tx Q15 CDscd

114) Tx Q11 CDscd 127) Egr CRx Q15

115) Egr CRx Q11

116) Q12 Cells Tx

117) Tx Q12 CDscd




This Command: cnfstatparms 5 5 5 15 1 2





Enter Statistic Type ('.' to quit):




Example (BXM on the BPX)

cnfstatparms 5 5 5 15 1 2

rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:37

GMT




Available Statistic Object Types:




1: Connections

2: Service Interfaces

3: Trunks

4: Ports

5: Physical Lines

.: Quit




This Command: cnfstatparms 5 5 5 15 1 2




Enter Object Type (numeric value): 3




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:37

GMT




Available Object Sub-types:




1: Narrow Band

2:

3: BPX 8600 ATM

4: IGX 8400 ATM

.: Quit




This Command: cnfstatparms 5 5 5 15 1 2




Enter Object Sub Type (numeric value): 3




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:38

GMT




Virtual Interface Statistic Types




1) Tx Voice Overflow Drpd Cells 14) Tx Bdata B CLP Drpd Cells

2) Tx TS Overflow Drpd Cells 15) Tx Voice CLP Drpd Cells

3) Tx NTS Overflow Drpd Cells 16) Tx TS CLP Drpd Cells

4) Tx Hi-Pri Overflow Drpd Cells 17) Tx NTS CLP Drpd Cells

5) Tx BData A Overflow Drpd Cells 18) Tx Hi-Pri CLP Drpd Cells

6) Tx BData B Overflow Drpd Cells 19) Tx CBR Cells Served

7) Tx Voice Cells Served 20) Tx VBR Cells Served

8) Tx TS Cells Served 21) Tx ABR Cells Served

9) Tx NTS Cells Served 22) Tx CBR CLP Drpd Cells

10) Tx Hi-Pri Cells Served 23) Tx nrt-VBR CLP Drpd Cells

11) Tx BData A Cells Served 24) Tx ABR CLP Drpd Cells

12) Tx BData B Cells Served 25) Tx CBR Overflow Drpd Cells

13) Tx Bdata A CLP Drpd Cells 26) Tx nrt-VBR Overflow Drpd Cells




This Command: cnfstatparms 5 5 5 15 1 2




Continue? y




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:38

GMT




Virtual Interface Statistic Types




27) Tx ABR Overflow Drpd Cells 40) Egress TS Cells Rx

28) Tx NTS Cells Discarded 41) Egress BData A Cells Rx

29) Tx Hi-Pri Cells Discarded 42) Egress BData B Cells Rx

30) Tx Voice Cells Discarded 43) Egress CBR Cells Rx

31) Tx TS Cells Discarded 44) Egress ABR Cells Rx

32) Tx BData A Cells Discarded 45) Egress VBR Cells Rx

33) Tx BData B Cells Discarded 46) Total Cells Tx from port

34) Tx CBR Cells Discarded 47) Cells RX with CLP0

35) Tx ABR Cells Discarded 48) Cells Rx with CLP1

36) Tx VBR Cells Discarded 49) Cells RX Discard with CLP0

37) Egress NTS Cells Rx 50) Cells RX Discard with CLP1

38) Egress Hi-Pri Cells Rx 51) Cells TX with CLP0

39) Egress Voice Cells Rx 52) Cells TX with CLP1




This Command: cnfstatparms 5 5 5 15 1 2




Continue? y




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:38

GMT




Virtual Interface Statistic Types




53) BXM: Total Cells RX 66) Egress Q12 Cells Rx

54) Ingress OAM Cell Count 67) Tx Q13 Cells Served

55) Egress OAM Cell Count 68) Tx Q13 Cells Discarded

56) Ingress RM cell count 69) Egress Q13 Cells Rx

57) Egress RM cell count 70) Tx Q14 Cells Served

58) Tx Q10 Cells Served 71) Tx Q14 Cells Discarded

59) Tx Q10 Cells Discarded 72) Egress Q14 Cells Rx

60) Egress Q10 Cells Rx 73) Tx Q15 Cells Served

61) Tx Q11 Cells Served 74) Tx Q15 Cells Discarded

62) Tx Q11 Cells Discarded 75) Egress Q15 Cells Rx

63) Egress Q11 Cells Rx

64) Tx Q12 Cells Served

65) Tx Q12 Cells Discarded




This Command: cnfstatparms 5 5 5 15 1 2 3 3 60




Enter Statistic Type ('.' to quit):




===============================================================================

*** cnfstatparms for BPX BXM Port Statistics




================================================================================




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:41

GMT




Available Statistic Object Types:




1: Connections

2: Service Interfaces

3: Trunks

4: Ports

5: Physical Lines

.: Quit




This Command: cnfstatparms 5 5 5 15 1 2




Enter Object Type (numeric value): 4




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:41

GMT




Available Object Sub-types:




1: Frame Relay Ports

2: ASI

3: FTC

.: Quit




This Command: cnfstatparms 5 5 5 15 1 2




Enter Object Sub Type (numeric value): 2




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:42

GMT




Port Statistic Types




1) Unknown VPI/VCI count 13) OAM cells received count

2) Cell buff overflow (ingress) 14) Tx payload err cnt BIP-16 err

3) Non-zero GFC count 15) Number of cells xmitted w/CLP

set

4) ISU discard count 16) Number of cells xmitted w/EFCI

set

5) ISU free list empty count 17) Tx header err discard

6) Receive AIS cell count 18) Get Request PDUs received

7) Receive FERF cell count 19) Get Next Request PDUS received

8) Number of cells received 20) Get Next Request PDUS

transmitted

9) Number of cells rcvd w/CLP set 21) Set Request PDUs received

10) Number of cells rcvd w/EFCI set 22) Trap PDUs received

11) Number of BCM cells rcvd 23) Get Response PDUs received

12) Number of cells xmitted 24) Get Request PDUs transmitted




This Command: cnfstatparms 5 5 5 15 1 2




Continue?




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:42

GMT




Port Statistic Types




25) Get Response PDUs transmitted 37) Invalid LMI PDU length received

26) Trap PDUs transmitted 38) Unknown LMI PDUs received

27) Unknown ILMI PDUs Received 39) Invalid LMI IE received

28) Status messages transmitted 40) Invalid Transaction IDs

29) Update Status messages transmitted 41) Number of cells rcvd w/clp 0

30) Status Acknowledge msgs transmitted 42) Number of cells dscd w/clp 0

31) Status Enquiry messages received 43) Number of cells dscd w/clp set

32) Status Enquiry mesgs transmitted 44) Number of cells tx w/clp 0

33) Status messages received 45) Tx OAM cell count

34) Update Status messages received 46) Rx RM cell count

35) Status Acknowledge messages received47) Tx RM cell count

36) Invalid LMI PDUs received received 48) Last unknown VPI/VCI pair




This Command: cnfstatparms 5 5 5 15 1 2




Continue?




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:42

GMT




Port Statistic Types




49) Tx Cells Served on Qbin 0 61)

50) Tx Cells Discarded on Qbin 0 62)

51) Tx Cells Received on Qbin 0 63)

52) Tx Cells Served on Qbin 1 64)

53) Tx Cells Discarded on Qbin 1 65)

54) Tx Cells Received on Qbin 1 66)

55) Tx Cells Served on Qbin 2 67)

56) Tx Cells Discarded on Qbin 2 68)

57) Tx Cells Received on Qbin 2 69)

58) Tx Cells Served on Qbin 3 70)

59) Tx Cells Discarded on Qbin 3 71)

60) Tx Cells Received on Qbin 3 72)




This Command: cnfstatparms 5 5 5 15 1 2




Continue?




rogue TN Cisco BPX 8620 9.3.1Z July 14 2000 11:43

GMT




Port Statistic Types




73) 85) Tx Cells Served on Qbin 12

74) 86) Tx Cells Discarded on Qbin 12

75) 87) Tx Cells Received on Qbin 12

76) Tx Cells Served on Qbin 9 88) Tx Cells Served on Qbin 13

77) Tx Cells Discarded on Qbin 9 89) Tx Cells Discarded on Qbin 13

78) Tx Cells Received on Qbin 9 90) Tx Cells Received on Qbin 13

79) Tx Cells Served on Qbin 10 91) Tx Cells Served on Qbin 14

80) Tx Cells Discarded on Qbin 10 92) Tx Cells Discarded on Qbin 14

81) Tx Cells Received on Qbin 10 93) Tx Cells Received on Qbin 14

82) Tx Cells Served on Qbin 11 94) Tx Cells Served on Qbin 15

83) Tx Cells Discarded on Qbin 11 95) Tx Cells Discarded on Qbin 15

84) Tx Cells Received on Qbin 11 96) Tx Cells Received on Qbin 15




This Command: cnfstatparms 5 5 5 15 1 2




Enter Statistic Type ('.' to quit):





cnfsysparm (configure system parameters)

Configures various system (or network) parameters. Network-wide parameters are configurable only when all nodes in the network are reachable. The parameters you specify with this command apply throughout the network regardless from which node you execute the command. Take special note of the consequences of how you resolve conflicting values when networks are joined.

You can select each parameter by its index number. The "System Parameters" subsection describes each parameter by index number. The "Parameter Values" table lists the defaults and ranges for each parameter.

---

Warning Using cnfsysparm requires caution because network rerouting or loss of data may result from changes in system parameters. If necessary, consult with the TAC before you use cnfsysparm.

---

Syntax

cnfsysparm <index> <value>

Parameters

Parameter	Description
<index>	Specifies a numerical value that refers to the specific parameter to be changed. Index numbers and descriptions of the system-wide parameters are in the table that precedes the command summary.
<value>	Specifies a numerical value that applies to the selected parameter. See "Parameter Values" table.

System Parameters

The configurable system parameters are listed by index number:

1: Maximum Time-Stamped Packet Age is the maximum age a time-stamped packet can have before the switch discards it. If networks are joined and the Maximum Time-Stamped Packet Age in the networks differ from each other, the lower value becomes the maximum.

2: Fail Connections On Communication Break determines whether connections are conditioned if the node at the other end of the connection becomes unreachable. If networks with different settings are joined, the resolution is to enable this parameter for the new network.

3-7: Maximum Network Delay for various types of compressed voice and high-speed data connections using LDM/HDM on an IGX node. When the total queueing delay on a route exceeds this value, connection traffic cannot use the route. The units of measure are milliseconds. When networks with different values are joined, the lower value becomes the Maximum Network Delay.

8-12: Maximum Network Delay for compressed voice and high-speed data connections. When the total queueing delay on a route exceeds the specified number of milliseconds, a connection traffic cannot use the route. When networks with different values are joined, the higher value becomes the Maximum Network Delay. Applicable cards are the UVM, CDP, or CVM.

In Release 9.1, when cost-based routing is configured, the delay cost cap is the maximum allowable end-to-end delay for the connection type. Use parameters 3 through 12 to configure this delay network-wide for all delay-sensitive connections.

•13: Enable Discard Eligibility (DE) bit for Frame Relay connections. Frames received with DE set have been sent on connections where the PIR has been exceeded and are eligible to be discarded. Enabling DE automatically enables CLP. CLP is disabled when Discard Eligibility is turned off except on the bursty data B queue when ForeSight is enabled.

•14: Use Frame Relay Standard Parameters Bc and Be allows you to substitute the Frame Relay Forum standard Bc for VC Q depth and Be for PIR when you configure Frame Relay ports and connections. (The affected commands are cnfport, addcon for Frame Relay, and cnfcon.) Screen displays for Frame Relay ports and connections reflect the choice for this parameter. Note that if you change this parameter, a network-wide reset to the default values takes place for all Frame Relay classes, and the terminal displays a warning that the reset occurred.

•Obsolete: 15-20: Maximum Local Delay for Interdomain UVM, CDP, or CVM to UVM, CDP, or CVM connections is similar to parameters 8-12 described above. These parameters specify the maximum delay at the local domain in a structured network. These delays can be set only on a domain-by-domain basis (not end-to-end).

•21: FastPAD Jitter Buffer Size is the size of the buffer for neutralizing jitter in connections that terminate on a FastPAD. The units of measurement are milliseconds.

•22: Number of Consecutive Invalid Login Attempts to Cause Major Alarm specifies the number of failed login attempts that causes a major alarm. The default of 0 means that failed login attempts do not cause an alarm. If the threshold is set to 0, the Too Many Invalid Login Attempts service-affecting alarm is disabled and no alarm will be generated.

•23: Enable Connection Deroute Delay is an enable that causes the network to wait a period of time before rerouting connections because of an error on a trunk. With Enable Connection Deroute Delay enabled, the network does not immediately reroute connections when statistical errors are occurring or when a trunk momentarily moves into a failure state then returns to normal operation. This feature is relevant when rerouting the connections is more of a disruption than the errors caused by the intermittant trunk.

•24: Frame Relay VCs Polling Rate is the period between the start of polling cycles for both ATM and Frame Relay virtual connections. The possible values are 5, 10, and 15 seconds. As the number of connections in a network grows, greater intervals between cycles may be appropriate. The suggested intervals for the numbers of connections are:

–5 minute polling for up to 4000 connections

–10 minute polling for up to 8000 connections

–15 minute polling beyond 8000 connections.

•25: Port Polling Rate is the time between the start of polling cycles for interval statistics. The possible values are 5, 10, and 15 minutes. (To specify the particular statistics, use the statistics manager in WAN Manager.) As the number of connections in a network grows, greater intervals between cycles may be appropriate. The suggested intervals for the numbers of connections are:

–5 minutes for up to 300 connections

–10 minutes for up to 500 connections

–15 minutes for more than 500 connections.

•26: Num of Nodes doing Simultaneous TFTP Cnfg Save/Restore is the total number of nodes that can perform TFTP configuration data transfers simultaneously. The value must be the same on all nodes in the network. This parameter indicates the maximum number of simultaneous sessions. However, the actual number of simultaneous sessions can be less than this number, depending on the node numbering configuration in the network. When networks with different values of this parameter are joined, the resolution is to take the lower number. Range is 1 to 15 nodes. Default value is four nodes.

Parameter Values

System Parameters
Index	System-Wide Parameter	Default	Range
1	Max Time Stamped Packet Age (in milliseconds).	32	1-60
2	Fail Connections On Communication Break.	No	y or n
3	Max Network Delay for "v" connections (in milliseconds).	14	1-255
4	Max Network Delay for "c" connections (in milliseconds).	27	1-64
5	Max Network Delay for "d" connections (in milliseconds).	14	1-255
6	Max Network Delay for "a" connections (in milliseconds).	27	1-255
7	Max Network Delay for High-Speed Data connections (in milliseconds).	40	1-255
8	Max Network Delay for CDP or CVM to CDP or CVM "v" connections (in milliseconds).	64	1-255
9	Max Network Delay for CDP or CVM to CDP or CVM "c" connections (in milliseconds).	64	1-64
10	Max Network Delay for CDP or CVM to CDP or CVM "t & p" connections (in milliseconds).	64	1-255
11	Max Network Delay for CDP or CVM to CDP or CVM "a" connections (in milliseconds).	64	1-255
12	Max Network Delay for CDP or CVM to CDP or CVM High-Speed Data connections (in milliseconds).	64	1-255
13	Enable Discard Eligibility (DE).	No	y or n
14	Use Frame Relay standard parameters Bc and Be.	No	y or n
15	Obsolete: Max Local Delay for Interdom CDP to CDP "v" connections.	27	1-255
16	Obsolete: Max Local Delay for Interdom CDP to CDP "c" connections.	27	1-64
17	Obsolete: Max Local Delay for Interdom CDP to CDP "t & p" connections.	27	1-255
18	Obsolete: Max Local Delay for Interdom CDP to CDP "a" connections.	27	1-255
19	Obsolete: Max Local Delay for Interdom CDP to CDP High-Speed Data connections.	27	1-255
20	Obsolete: Max Local Delay for Interdom High-Speed Data connections (in milliseconds).	28	1-255
21	FastPAD Dejitter Buffer Depth (in milliseconds).	15	0-255
22	Number of Consecutive Invalid Login Attempts to Cause Major Alarm.	0	3-9
23	Enable Connection Deroute Delay.	Yes	y or n
24	Frame Relay VCs Polling Rate is the number of minutes between polling cycles for both ATM and Frame Relay virtual connections in the network.	5	5, 10, or 15
25	Port Polling Rate is the number of minutes between polling cycles for interval statistics gathered for all ports in the network. As the number of connections in a network grows, greater intervals between cycles may be appropriate. The suggested intervals for the numbers of connections are: •5 minutes for up to 300 connections •10 minutes for up to 500 connections •15 minutes for more than 500 connections.	5	5, 10, or 15
26	Number of Nodes Doing Simultaneous Configuration Save/Restore	4	1-15

Attributes

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

Example

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

bpx1 TN Cisco BPX 8620 9.3.39 Mar. 19 2000 10:52 GMT




System-Wide Parameters




1 Max Time Stamped Packet Age (msec) ................................ 32

2 Allow CPU Starvation of Fail Handler .............................. Yes

3 Max Network Delay for 'v' connections (msec)....................... 15

4 Max Network Delay for 'c' connections (msec)....................... 28

5 Max Network Delay for 't' & 'p' connections (msec)................. 15

6 Max Network Delay for 'a' connections (msec)....................... 28

7 Max Network Delay for High Speed Data connections (msec)........... 32

8 Max Network Delay for CDP-CDP 'v' connections (msec)............... 64

9 Max Network Delay for CDP-CDP 'c' connections (msec)............... 64

10 Max Network Delay for CDP-CDP 't' & 'p' connections (msec)......... 64

11 Max Network Delay for CDP-CDP 'a' connections (msec)............... 64




This Command: cnfsysparm




Continue?

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

bpx1 TN Cisco BPX 8620 9.3.39 Mar. 19 2000 10:52 GMT




System-Wide Parameters




12 Max Network Delay for CDP-CDP High Speed Data connections (msec)... 64

13 Enable Discard Eligibility......................................... No

14 Use Frame Relay Standard Parameters Bc and Be...................... No

15 Max Local Delay for Interdom CDP-CDP 'v' conns (msec).............. 28

16 Max Local Delay for Interdom CDP-CDP 'c' conns (msec).............. 28

17 Max Local Delay for Interdom CDP-CDP 't' & 'p' conns (msec)........ 28

18 Max Local Delay for Interdom CDP-CDP 'a' conns (msec).............. 28

19 Max Local Delay for Interdom CDP-CDP High Speed Data conns (msec).. 28

20 Max Local Delay for Interdom High Speed Data conns (msec).......... 29

21 FastPAD Jitter Buffer Size (msec)................................. 20

22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm . 5




This Command: cnfsysparm




Continue?

------------------------------------SCREEN 3-----------------------------------

bpx1 TN Cisco BPX 8620 9.3.39 Mar. 19 2000 10:53 GMT

System-Wide Parameters




23 Enable Connection Deroute Delay feature............................ Yes

24 Interval Statistics polling rate for ATM VCs....................... 15

25 Interval Statistics polling rate for ports on IPX/IGX 8400 nodes... 15

26 Num of Nodes doing Simultaneous TFTP Cnfg Save/Restore............. 15





This Command: cnfsysparm

cnftcpparm (configure TCP parameters)

Configures the TCP parameter. This command specifies the number of times per second that the BCC checks the IP addresses for attention requests.

Syntax

cnftcpparm <network ip throttle>

Parameters

Parameter	Description
<network ip throttle>	Specifies the number of times that the BCC card polls the LAN for attention requests.

Attributes

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

Related Commands

dsptcpparm

Example

cnftcpparm

sw81 TN SuperUser BPX 15 9.3 Apr. 13 2000 15:46 PST




NWIP Bandwidth Throttle (Kbytes/sec): 32







This Command: cnftcpparm





Enter NWIP Bandwidth Throttle (Kbytes/sec):

cnfterm (configure terminal port)

Configures data transmission parameters for the control and auxiliary ports. The IGX and BPX nodes support two EIA/TIA-232 serial ports on the upper bus expansion card. The top port is called the Control Terminal port. The lower port is called the Auxiliary Port (AUX).

Parameters can vary with the equipment connected to the port. The control port may connect to a control terminal, a direct-dial modem, or an external EIA/TIA-232 device. The auxiliary port may connect to either a printer or an external EIA/TIA-232 device. After you have set the data transmission parameters for a port, use the SuperUser command cnftermfunc to specify the equipment attached to the port. The configuration parameters must match the equipment physically attached to the port.

Syntax

cnfterm <a | c> <baud> <parity> <data_bits> <stop_bits> <output flow control> <input flow control>
<CTS flow control> <y | n>

Parameters

Parameter	Description
a | c	Specifies the port to be configured, where "a" means auxiliary port, and "c" means control port.
baud rate	Specifies the baud rate. The rates are 1200, 2400, 4800, 9600, and 19200 bps.
parity	Specifies parity checking for character transmission to and from the port. Valid parity choices are "E" for even parity, "O" for odd parity, and "N" for no parity.
data bits	Specifies the number of bits to be sent for each transmitted character and the number of bits to be expected for each received character. A "7" indicates 7 bits for each character. An "8" indicates 8 bits for each character.
stop bits	Specifies the number of stop bits to be sent with each transmitted character and the number of stop bits to be expected with each received character. A "1" indicates one stop bit with each character; a "2" indicates two stop bits with each character.
output flow control	Specifies the output flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control.
input flow control	Specifies input flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control.
cts flow control	Configures cts flow control. An "X" specifies XON/XOFF flow control; an "N" specifies no flow control. This parameter should be turned off if working with modems on a BPX node.
y | n	Specifies whether the node requires DTR to be asserted to allow or maintain a Login. A "Y" causes the node to require the presence of DTR before allowing a login. A "N" causes the node to ignore DTR.

Attributes

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

Related Commands

cnfterm, cnfprt, window

Example

Configure an auxiliary control port.

cnfterm

lpha TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 11:58 PST

Control port Auxiliary port

Baud Rate: 1200 Baud Rate: 9600

Parity: None Parity: None

Number of Data Bits: 8 Number of Data Bits: 8

Number of Stop Bits: 1 Number of Stop Bits: 1

Output flow control: XON/XOFF Output flow control: XON/XOFF

Input flow control: XON/XOFF Input flow control: XON/XOFF

Use DTR signal: Yes DTR signal: Yes

This Command: cnfterm

Select Control port (c) or Auxiliary port (a):

cnftermfunc (configure terminal port functions)

Configures port functions for the IGX or BPX control and auxiliary ports. The IGX nodes support two EIA/TIA-232 asynchronous serial ports on the SCC and SCM, respectively. The BPX node supports two EIA/TIA-232 asynchronous serial ports on the BCC. In all cases, the top port is the Control Terminal port, and the lower port is the Aux Port. The Control Terminal port can connect to a control terminal, Cisco WAN Manager, a direct dial-in modem, or any external EIA/TIA-232 device. The Aux Port can connect to a printer, an auto-dial modem to call a control center, or an external EIA/TIA-232 device.

The interface specified for the port must match the equipment physically attached to the port. The baud rate and other data transmission parameters for the port are set with the cnfterm command. If either port is configured as an external device window, enter the window command to begin a session with the external device.

If the auxiliary port is configured as an auto-dial modem, designate a network ID and a phone number. Configuring the auxiliary port for an auto-dial modem enables the following to occur: When a change in alarm status happens anywhere in the network, the auto-dial modem attached to the auxiliary port dials the specified phone number. If the call goes to the TAC, the alarm is logged under the specified network ID. With this log, Cisco engineers are automatically notified of any problems that occur in the network.

Syntax

cnftermfunc <a | c> <index> [escape_string | (Network_ID_string)] [dial_string]

Parameters

Parameter	Description
<a | c>	Specifies port. a specifies that the auxiliary port will be configured. c specifies that the control port will be configured.
<index>	Control port: 1. VT100/Cisco WAN Manager 2. VT100 3. External device window Auxiliary port: 1. Okidata 184 printer 2. Okidata 184 printer with LOG 3. VT100 4. Alarm Message Collector 5. External Device Window 6. Autodial Modem
escape string	Specifies a string of 1 to 8 characters used to terminate a session with an external device. This parameter is valid only for "External Device Window" interfaces. Default: quit
network id string	Specifies a string of 1-12 characters used to identify the network during an auto-dial connection to the TAC. This parameter is valid only for "Autodial Modem" interfaces. Any alarm status change in the network is automatically logged at Cisco by using this network ID. Contact TAC for the ID to use.
dial string	Specifies the telephone number to be dialed when the network is reporting alarm status changes via the auto-dial modem. This parameter is valid only for "Autodial Modem" interfaces. The phone number can be up to 16 characters long and normally consists of digits and commas only. A comma is used to indicate that the auto-dial modem should pause two seconds before continuing to dial. For example, the number "9,4083700736" would cause the modem to dial a "9," pause two seconds, then dial the remaining digits. Contact Cisco TAC for the number.

Attributes

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

Related Commands

cnfterm, cnfprt, dsptermfunc

Example

Configure an IGX or BPX node control or auxiliary port.

cnftermfunc

Without an argument on the command line, the switch displays a list of parameters:

TN SuperUser IGX 8420 9.3 Apr. 13 2000 03:46 GMT

Control port Auxiliary port

1. VT100/StrataView 1. Okidata 182 Printer

2. VT100 2. Okidata 182 Printer with LOG

3. External Device Window 3. VT100

4. Alarm Message Collector

5. External Device Window

6. Autodial Modem




This Command: cnftermfunc

Select Control port (c) or Auxiliary port (a)

Example

Configure an auxiliary port. The port configuration screen appears with "Autodial Modem" highlighted to indicate that this interface has been chosen for the auxiliary port. When an alarm occurs on the network, the modem dials 18007674479 to reach the TAC. The alarm is logged on a Cisco computer under the name Intrepid.

cnftermfunc a 5 Intrepid 18007674479

cnftime (configure time)

Sets the time for the entire network. The time is broadcast to all nodes in the network. The time displayed at each node is adjusted for the node's time zone. (See the cnftmzn command for more about time zone.) This command can be executed only if the date for the network has already been configured using the cnfdate command. If hour, minute, or second is not entered, the current value is kept.

Syntax

cnftime <hour> <minute> <second>

Parameters

Parameter	Description
<hour>	Sets the time for the entire network. The time is broadcast to all nodes in the network. The time displayed at each node is adjusted for the node's time zone. (See the cnftmzn command for more information.) This command can only be executed if the date for the network has already been configured using the cnfdate command. If hour, minute, or second is not entered, the current value is kept.
<minute>	Specifies the current minute. Range: 0-59
<second>	Specifies the current second. Range: 0-59

Attributes

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

Related Commands

cnfdate, cnftmz

Example

Configure time to 7:31 in the evening. The system displays two warning prompts before it changes the time.

cnftime 19 31 00

pubsigx1 TN SuperUser IGX 8430 9.3 Apr. 13 2000 19:31 GMT





This Command: cnftime 19 31 00





Warning: Changing time of day affects StrataView statistics timestamps

Hit RETURN to change clock, DEL to abort




cnftlparm (configure trunk-based loading parameters)

Configures the trunk-based loading (TBL) parameters. Use the cnftlparm command to control the rate of update messages in conjunction with trunk-based loading.

---

Note Cisco Systems recommends that you leave all parameters at the default values. If you need to change a TBL parameter, first call TAC.

---

Syntax

cnftlparm <index>

Parameters

No.	Index	Description	Range	Default
1	Enable	Enables or disables automatic TBL update messages. Do not disable unless you first contact TAC.	Yes/No	Yes
2	Normal Interval	Specifies the time interval between checks to determine if the node should send out a TBL update signaling a non-critical change in the trunk load.	0-65000 (times 100 msecs)	150
3	Fast Interval	Specifies the time interval between checks to determine if the node should send out a TBL update signaling a critical change in the trunk load.	0-65000 (times 100 msecs)	50
4	Low Threshold	Algorithm parameters for complex update algorithm.	1-100%	50
5	High Threshold	Algorithm parameters for complex update algorithm.	1-100%	90
6	Min. Percent Chg, Mid 1	Algorithm parameters for complex update algorithm.	1-100%	10
7	Min. Percent Chg, Mid 2	Algorithm parameters for complex update algorithm.	1-100%	6
8	Min. Percent Chg, Mid 3	Algorithm parameters for complex update algorithm.	1-100%	3
9	Min. Percent Chg, Upper	Algorithm parameters for complex update algorithm.	1-100%	2
10	Background Updt Count	Specifies a periodic update. 0=update disabled. If Background Updt Count is greater than 0, switch software multiplies it by the value you specify for Normal Interval.	0-1000%	0
11	Update Algorithm	Selects the update algorithm. 0=default. 1=complex update algorithm.	0 or 1	0

Attributes

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

Related Commands

cnfcmparm

Example

cnftlparm

sw66 TN SuperUser BPX 15 9.3 Apr. 13 2000 22:31 GMT

1 Enable [ Yes]

2 Normal Interval [ 150] (100msecs)

3 Fast Interval [ 50] (100msecs)

4 Low Threshold [ 50] (D)

5 High Threshold [ 90] (D)

6 Min Percent Chg, Mid 1 [ 10] (D)

7 Min Percent Chg, Mid 2 [ 6] (D)

8 Min Percent Chg, Mid 3 [ 3] (D)

9 Min Percent Chg, Upper [ 2] (D)

10 Background Updt Count [ 0] (D)

11 Update Algorithm [ 0] (D)

This Command: cnftlparm

Enter parameter index:

cnftmzn (configure time zone)

Configures the time zone for the node. Configuring the time zone for a node ensures that the node's time is correct for the local area regardless of the node at which the network date and time are set. Once configured, the time zone for the node is saved in battery-backed memory. After a power failure, a node's date and time are restored if at least one other node in the network has the current time and date.

Syntax

cnftmzn <timezone | g+ | - hours>

Parameters

Parameter	Description
time zone	•gmt (or g)—Greenwich Mean Time •cst (or c)—Central Standard Time •est (or e)—Eastern Standard Time •mst (or m)—Mountain Standard Time •pst (or p—Pacific Standard Time •yst (or y)—Yukon Standard Time •cdt—Central Daylight Savings Time •edt—Eastern Daylight Savings Time •mdt—Mountain Daylight Savings Time •pdt—Pacific Daylight Savings Time •ydt—Yukon Daylight Savings Time
g+ | - hours	Specifies the difference in hours between local time and Greenwich Mean Time. Instead of entering the time zone, you can enter the hours from Greenwich Mean Time. For example, instead of entering pdt for Pacific Daylight Time, you could enter g-7, which is Greenwich Mean Time minus 7 hours. Range: -12 to +12 hours.

Attributes

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

Related Commands

cnfdate

Example

Configures the time zone to Pacific Standard Time.

cnftmzn pst

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




Last Command: cnftmzn pst

Next Command:




cnftrk (configure trunk)

Configures trunk parameters. The typical procedure to add a trunk to the network includes the following steps.

1. Use uptrk to "up" or activate the trunk with a default configuration.

2. Use cnftrk to configure trunk parameters. You must execute cnftrk at both ends of a trunk.

3. Use addtrk to add the trunk to the network.

For additional information on adding and configuring trunks, see the <CellCommandItalic>Cisco BPX Series Installation and Configuration guide and the Cisco IGX 8400 Installation and Configuration guide. Also see the "Physical and Virtual Trunk Configuration" section, the "IMA-Compliant Trunk Configuration" section, and the "Subrate and Fractional Trunk Configuration" section.

In the display for cnftrk, the current value for each parameter appears on screen. At the command line prompt for each parameter, the current or default value appears in parentheses and stays the same if you press Return without entering a new value. Configurable parameters depend on the trunk type. If a displayed parameter is not available for the current trunk type, its name displays at half-intensity, and the value field contains dashes.

If you specify cnftrk in a job, prompts appear for line format and line options when you create or edit the job by using addjob or editjob, respectively.

The cnftrk command configures a logical trunk (physical or virtual), so when you change a physical parameter, all trunks on the port (both physical and virtual) are affected. For example, if you change the line framing on a virtual trunk, all virtual trunks on the port are automatically updated to have the modified line framing.

The cnftrk command supports the CBR, ABR, and VBR (rt-VBR and nrt-VBR) traffic classes on both physical and virtual trunks.

You use cnftrk to configure the Transmit Trunk Rate for all BPX cards except the BXM. For BXM cards, you must use the cnfrsrc command to configure the Transmit Trunk Rate (trunk load). For IGX cards, you configure the Transmit Trunk Rate only after a trunk has been added.

You use the cnftrk command to assign a VPI value. You cannot configure the VPI value if the virtual trunk is already configured for VSI. If the VSI feature is enabled, and you execute cnftrk to decrease the transmit rate, you must confirm whether the Qbin configuration is set up correctly by using the cnfqbin command to change the value. The reason for this is that when the transmit rate is decreased, the Qbin depth will be automatically recalculated.

Starting with Release 9.3.30, you can configure an incremental cell delay variance (CDV) on BNI, BXM, UXM, and NTM trunks. For more information about the CDV, see the description of this parameter in parameter table in this section. In addition, you can configure BXM and UXM virtual trunks to recognize receipt of end-to-end F4 OAM AIS alarms from the ATM service provider. See the "Trunk AIS OAM Recognition" section for more detail.

Also starting with Release 9.3.30, the CRC-4 Protection feature allows you to enable/disable the CRC check on multiframed UXM E1 trunks. This feature applies to all types of UXM E1 trunks except unframed E1 trunks. The two ends of the UXM E1 trunk must be configured to work together. Mismatch of CRC-4 protection configuration between the two ends of the UXM E1 trunk, will result in Out of Frame alarms on the trunk. You use the cnftrk Line CRC parameter to enable/disable the CRC check.

Table 3-41 below shows the trunk parameters that you can configure using cnftrk. You can specify all physical options on virtual trunks. If you change a physical option on a virtual trunk, the change is propagated to all virtual trunks on the trunk port.

In the table, an X indicates that the parameter is configurable. An X* in the Virtual column indicates that the parameter is a physical parameter, and changing the value for one virtual trunk on the port will automatically cause all virtual trunks on the port to be updated with the same value.

Table 3-41 cnftrk—Parameters That are Configurable on Physical and Virtual Trunks 

Descriptions	BXM		UXM
	Physical	Virtual	Physical	Virtual
Transmit Trunk Rate (configurable using cnfrsrc)	X	X	X	X
Receive Trunk Rate	X	X	X	X
Pass Sync	X	X*	X	X*
Loop Clock	X	X*	X	X*
Statistical Reserve	X	X	X	X
Header Type NNI	X	X*	X	X*
Trunk VPI		X	X	X
Incremental CDV	X	X	X	X
F4 AIS Detection		X		X
Routing Cost	X	X	X	X
Virtual Trunk Type		X		X
Idle Code	X	X*	X	X*
Restrict PCC traffic	X	X	X	X
Link Type	X	X*	X	X*
Line Framing	X	X*	X	X*
Line Coding			X	X*
Line Cable type			X	X*
Line cable length	X	X*	X	X*
HCS Masking	X	X*	X	X*
Payload Scramble	X	X*	X	X*
Connection Channels	X	X	X	X
Gateway Channels			X	X
Valid Traffic classes	X	X	X	X
Frame Scramble	X	X*	X	X*
Deroute Delay Time	X	X	X	X
VC (Traffic) Shaping	X	X	X	X
Protocol by the Card	X	X	X	X
IMA Differential Delay			X	X
IMA Clock Mode			X	X
IMA Group member			X	X
Retained links			X	X
IMA Differential Delay			X	X

Syntax

cnftrk <slot.port>[.vtrk] <options for E1 | T1 | E3 | T3 | OC-3 | OC-12 | E2 | HSSI | SR >

Parameters

Trunk Option	Type	Description	Possible Entries	Default
slot.port [.vtrk]	All	The number of the trunk to configure.	Any valid slot and port. For cards with one port, use slot.	N/A
Trunk Identification (display only—not configurable)	All	Displays trunk number, trunk type and bandwidth supplied. The card type and slot number of the unit supporting the trunk is also displayed.	T3, E3, T1, E1, E2, fractional T1, fractional E1 subrate, ATM, NTC, NTM, OC-3, STM1, OC-12, STM4.	none
Clock Rate	ATM	This clock rate is required only for HSSI. Actual clock limits depend on the front card.	4 Mbps-50.84 Mbps
Transmit Trunk Rate (not configurable for BXM)	ATM	This indicates the trunk load and is configurable for all BPX cards except the BXM. You configure Transmit Trunk Rate on the BXM by using the cnfrsrc command. On IGX, Transmit Trunk Rate is configurable after a trunk has been added. Note The trunk load, which displays in brackets at the end of the first line on the cnftrk display, may vary from the Transmit Trunk Rate value. This is due to the way that cells are converted to DS0s, and vice versa, and the way the Rcv Trunk Rate determines the Transmit load at the other end of the trunk. The Transmit Trunk Rate in cells per second (cps) may not fit in the full DS0 and the resulting value may be truncated. The result is that the values displayed in Trunk load field and Transmit Trunk Rate fields may display different values.
Subrate interface	PKT	Subrate physical interface type.	X.21 | V.35	X.21
Subrate data rate	PKT	Subrate data rate in Kbps. Allows you to specify, in Kbps, the clock rate for the selected subrate interface. Acceptable values are any multiple of 64 Kbps up to a maximum of 1920 Kbps.	64 Kbps, 128 Kbps, 256 Kbps, 384 Kbps, 1.024Mbps, 1.536 Mbps, and 1.920Mbps	1920 Kbps
DS0 map	PKT	Specifies the DS0s to use for a fractional T1 or E1 bundle. Optional "a" = "use alternating channels" (for example, 20-30a means 20, 22, 24, and so on).	x - y[a]	0-31 (E1) 0-23 (T1)
Pass sync	All	Enables the trunk to pass a clock for network synchronization.	Yes | No	Yes for standard, no for virtual trunks
Loop Clock	All	Loop receive clock back to transmit.	Yes | No	No
Header Type	ATM	Selects the ATM cell header type: UNI, NNI, or STI. UNI is the default for virtual trunks but you may need to configure this parameter to NNI to match the header type of the VPC provided by the ATM cloud. In this release, this parameter is configurable for physical and virtual trunks. See the Cisco WAN Switching System Overview for a description.	UNI | NNI | STI	STI
Statistical Reserve	All	This trunk bandwidth is reserved for non-standard traffic, such as internode controller messages.	0-10666	The recommended stats reserve for T3/E3/OC3/OC12 is 1000 cps and 300 cps for T1/E1 virtual trunks.
Idle code	All	HEX code either in the payload space of an ATM idle cell or on an idle FastPacket trunk (idle packets do not exist)	0-FF (hex)	54 (E1) 7F (T1, ATM)
Gateway Type	ATM	Defines the type of addressing mode for this trunk. See Cisco WAN Switching System Overview for a description.	BPX-BPX (BAM) Cloud (CAM) Simple (SAM)	BAM
Connection Channels	ATM	The maximum number of connection channels per trunk. All virtual trunks on the port share this total. The number of connections added to the port cannot exceed the number of connection channels configured for the port. Number of connection channels, or LCNs, on the trunk port that are usable by the virtual trunk. This number cannot be greater than the total number of connection channels on the card. The maximum number of channels is additionally limited by the number of VCI bits in the UNI cell header. For a virtual trunk, divide this number by the maximum number of virtual trunks on the port to get the default.	BNI-T3/E3: max 1771 BNI-OC-3: max 15867 (3837 maximum/virtual trunk) BXM/UXM: 1-(number of channels allowable on card)	BNI-T3/E3: 1771 BNI-OC-3: 15867 For Virtual Trunks: BNI-T3/E3: 55 BNI-OC-3: 1442
Valid Traffic Classes	BXM UXM	BXM and UXM trunk valid traffic classes are: V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR	V = Voice TS = Time Stamped NTS = Non-Time Stamped FR = Frame Relay FST = ForeSight CBR = ATM constant bit rate RT-VBR = ATM real time (RT) VBR NRT-VBR = ATM non-real time (NRT) VBR N&RT-VBR = Both NRT-VBR and RT-VBR are chosen, screen display only, not prompted. ABR = ATM ABR	N/A
VPI Address	ATM	Virtual path address in ATM cell. The VPI configured for a virtual trunk must match the VPI for the VPC in the cloud. Valid VPC VPIs depend on the port type. Must be non-0 for a virtual trunk.	BXM/UXM (UNI)—1-255 BXM/UXM (NNI)—1-4095 BNI T3/E3—1-255 BNI OC-3—1-63	0
VCI Address	ATM	Virtual circuit address in ATM cell.	0-65,535	0
Restrict CC traffic (requires SuperUser privilege)	All	Restrict node controller messages from a trunk. Restricting CC traffic can cause serious problems. Contact the TAC through Cisco Customer Engineering before you change it.	Y | N	No
Link type	All	Terrestrial or Satellite link.Link Type applies to configuring a route so it can "avoid satellite."	T | S	T
Routing Cost	ATM	The administrative cost of a trunk for when cost-based routing is configured.	1-50	10 (upon trunk activation)
Line framing	PKT	T1 line framing	D4 | ESF	D4
Line coding	PKT	E1 line coding T1 line coding	HDB3 | AMI ZCS | B8ZS | AMI	HDB3 ZCS
Line CRC	PKT ATM	E1 CRC-4 Starting with Release 9.3.30, the CRC-4 Protection feature allows you to enable/disable the CRC check on all multiframed UXM E1 trunks. This feature applies to all types of UXM E1 trunks except unframed E1 trunks. The two ends of the UXM E1 trunk must be configured to work together. Mismatch of CRC-4 protection configuration between the two ends of the UXM E1 trunk, will result in Out of Frame alarms on the trunk.	Yes | No	Yes
Recv impedance	PKT	E1 receive impedance.	1 = 75W unbalanced 2 = 75W balanced 3 = 120W balanced	1
Cable type and cable length	PKT ATM	Length and type of cable used for trunk. Designates the software configurable line build-out to match the cable length from the IGX node to the DSX cross-connect. For BPX, the choices are 0-225 feet and over 225 feet. Cable type is not selectable for BPX. Not applicable to MMF or SMF.	1 = 0-220' MAT 2 = 220-440' MAT 3 = 440-655' MAT 4 = 0 -133' ABAM 5 = 133-266' ABAM 6 = 266-399' ABAM 7 = 399-533' ABAM 8 = 533-655' ABAM 0= 0-225 1= greater than 255	4 0
HCS Masking	ATM	Mask the ATM cell header checksum to disable error checking. HCS Masking applies to E3, OC-3, and OC-12 only.	Yes | No	Yes
Payload Scramble	ATM BNI	Scramble the cell payload.	Yes | No	Yes for BNI-E3 No for all others
End supp BData	PKT ATM	Indicates whether the far end of a trunk supports bursty, Frame Relay data.	Yes | No	No
End supp FST	PKT ATM	Indicates whether the far end of the trunk supports Optimized Bandwidth Management for Frame Relay.	Yes | No	No
IMA Differential Delay		Range: 0-200 milliseconds. Default: Differential delay of 200 msec. Because all physical links share the same line configuration, any changes made to this parameter and IMA Clock Mode parameter will be applied to all physical links of the specified IMA group. This parameter is configurable on virtual trunks that are on top of IMA ports.	0-200 msec	0-200 msec
IMA Clock Mode		Two clock mode options are available: Common Transmit Clock Source (CTC mode), and Independent Transmit Clock Source (ITC mode). CTC mode is the default. This parameter is configurable on virtual trunks that are on top of IMA ports.		CTC mode
IMA Group member		Lets you add or delete physical lines of an existing IMA group. You are prompted to enter the physical lines using the following format, for example: IMA Group member: 1,3,5,7 or IMA Group member: where 1,3,5,7 are physical lines that comprise the IMA group. IMA Group member is a set of physical lines comprising an IMA group. You can specify the group member as an expression consisting of the primary link followed by a "," (comma), or a hyphen (-), and additional physical links. You then use the following syntax to up a trunk when you specify an IMA group on a UXM trunk: uptrk slot.group_member.vtrk	primary link (slot.port)	No default
Retained links		Total number of physical links in the group must be greater than or equal to the number of retained links.
IMA Protocol Option		Lets you enable/disable the IMA Protocol on trunks that have only one physical line.	Enabled/Disabled	Default: IMA protocol disabled on these trunk types
Deroute Delay Time	All	Indicates how long in seconds the network will wait before rerouting connections on a failed trunk. This helps when a trunk momentarily moves into a failure state then returns to normal operation. This feature is relevant when rerouting the connections is more of a disruption than the errors caused by the intermittent trunk. Causes each node not to recognize the trunk as failed until this timer expires at the nodes used by the trunk. This indirectly affects the time that A-bit notifications are sent out because the connection deroute is also delayed.	0-600	0
Virtual Trunk Type	BNI, BXM, UXM	This choice usually comes from the carrier that provides the ATM cloud. This is the VPC type provided by the ATM cloud.	CBR, VBR, ABR	CBR
Virtual Trunk VPI	BNI, BXM, UXM	Virtual trunks must be configured to have a greater-than-0 VPI before connections are added by addcon. This value usually comes from the carrier that provides the ATM cloud. VPI configured for a virtual trunk matches VPI for VPC in the ATM cloud. Every cell transmitted to this trunk has this VPI value. Valid VPC VPIs depend on the port type.	1-255 for BXM/UXM (UNI) 1-4095 for BXM/UXM (NNI) 1-255 for BNI T3/E3 1-63 for BNI OC-3 (STM1)
Incremental CDV	BNI, BXM, UXM, NTM	Configures the incremental cell delay variance (CDV) on trunks. The value is specified in units of 125-usec increments. The magnitude of incremental CDV value can be up to 255 units of 125-usec (or, about 32 msec). The default value is zero.	0-255 units of 125-usec	0
F4 AIS Detection	BXM, UXM	Enables/disables the AIS OAM Recognition feature on virtual trunks. With this feature, UXM and BXM virtual trunks recognize receipt of end-to-end F4 OAM AIS alarms from the ATM service provider as virtual trunk path failure. Virtual trunks in a VP-tunnelling configuration (IGX) are not supported.	Yes | No	No

Attributes

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

Related Commands

addtrk, cnfrsrc, deltrk, dntrk, dsptrkcnf, uptrk

Physical and Virtual Trunk Configuration

Physical and virtual trunk configuration is similar. When you configure a port-level characteristic of a virtual trunk, all the virtual trunks on the port are modified with that characteristic. When the port characteristics of a trunk are modified, all characteristics related to that trunk port are updated.

Virtual trunks (see Table 3-43 for default statistical reserves) appear in the routing topology map as available trunks for routing. The existing physical trunk characteristics, such as bandwidth and satellite/terrestrial type, apply to virtual trunks. The routing algorithm must take into account special restrictions and conid assignments for a virtual trunk. For example, VPCs cannot be routed over a virtual trunk. Also, each virtual trunk has a configurable number of connection channels reserved from the card. The routing algorithm checks for adequate channel availability on a virtual trunk before selecting the trunk for the route.

The connection channel management scheme for the UXM and BXM cards is the same as in the previous release. The conids are selected on a per logical trunk basis. The associated LCNs are selected from a pool of LCNs for the entire card. Each virtual trunk can use the full range of acceptable conid values. The range consists of all the 16-bit values (1-65535), excluding the node numbers and blind addresses. A port uses the VPI to differentiate connections that have the same conid.

The number of channels per virtual trunk can be changed after the trunk has been added to the network. Decreasing the number of channels on an added virtual trunk causes connection reroutes where increasing the number of channels on an added virtual trunk will not cause connection reroutes.

Table 3-42 Default Statistical Reserves for Physical Trunks

	BNI	BXM	UXM
IMA-T1/E1	N/A	N/A	5000cps > T2, E2 1000 cps < T2, E2
T1/E1	N/A	N/A	1000 cps
T3/E3	5000 cps	5000 cps	5000 cps
OC3	5000 cps	5000 cps	5000 cps
OC12	N/A	5000 cps	N/A
T2 = 14490 cps (96 DS0s) E2 = 19900 cps N/A = not available

Table 3-43 Default Statistical Reserves for Virtual Trunks

	BNI	BXM	UXM
T1/E1	N/A	N/A	300 cps
T3/E3	1000 cps	1000 cps	1000 cps
OC3	1000 cps	1000 cps	1000 cps
OC12	N/A	1000 cps	N/A
N/A = not available

Trunk AIS OAM Recognition

With the Release 9.3.30 AIS OAM Recognition feature, virtual trunks recognize receipt of end-to-end F4 OAM AIS alarms from the ATM service provider. Prior to Release 9.3.30,virtual trunks recognized ILMI traps/responses as a source of Virtual trunk path failure.

The AIS OAM Recognition feature is provided on BPX BXM and IGX UXM cards only. Virtual trunks in a VP-tunnelling configuration (IGX) are not supported.

The absence or presence of ILMI support from the ATM service provider does not affect the functionality of detecting F4 OAM AIS. Similarly, absence or presence of AIS indication from the ATM cloud does not affect the functionality of ILMI.

The Virtual Trunk Path Fail states have been expanded to distinguish between failures due to ILMI and AIS. The trunk states now include:

•Clear state

•Virtual Trunk Path Fail state due to ILMI trap

•Virtual Trunk Path Fail state due to AIS

•Virtual Trunk Path Fail state due to both ILMI and AIS

You use the cnftrk F4 AIS Detection parameter to enable/disable the AIS OAM Recognition feature. You use the dsptrks command to display the state of all trunks on the node.

The AIS OAM Recognition feature provides a new entry point into the Virtual Trunk Path Failure alarm. Consequently, more connection rerouting may occur. You can use the cnftrk Trunk Deroute Delay timer to avoid excessive rerouting during brief outages.

Receive and Transmit Rates on Physical Trunks

The parameters RCV Trunk Rate and Transmit Trunk Rate apply to physical ATM trunks on an IGX node. On a BPX node, only Transmit Trunk Rate is available. These parameters let you configure lower rates than the maximum line rate for the trunk type. If you adjust a rate, you need to do this at both ends of the trunk. For example, if RCV Trunk Rate on an IGX is 40,000 packets per second (pps), Transmit Trunk Rate on the far end must be 20,000 cells per second (cps). The typical relationship between pps and cps is two FastPackets for each cell.

The default value for Transmit Trunk Rate is the maximum rate for the back card type. You can reduce this rate to any number of cells per second that is less than or equal to the physical port rate. If E3 or T2 is selected, the bandwidth is reduced from the T3 rate.

---

Note You can configure the Transmit Trunk Rate parameter, which indicates the trunk load, by using the cnfrsrc command on BXM cards. On both IGX and BPX nodes, the trunk load displays in cps (cells per second), and the value is displayed in brackets on the first line of the cnftrk display.

---

On the cnftrk screen, the Transmit Rate and Transmit Load are always displayed in cps (cells per second). (The Transmit Load displays in brackets above the Transmit Rate field, for example, TRK 13.1.1 Config T3 [2867 cps].) Because switch software performs an internal conversion from DS0s to cells for the receive rate, this receive rate dictates the transmit load at the other end of the trunk, and vice versa. Because the Transmit Load (in cps) may not fit into the full DS0, the resulting number that appears in the Transmit Load field (for example, [2867 cps], could be truncated. For example, if you were to change the Transmit Rate on a routing trunk from 96000 to 104268, cnftrk will prompt you to enter a Transmit Rate of 0-104268, and will accept 104268, but it may assign a value of 104150 instead of 104268. The Transmit Load would be the same, for example, 104150 cps, regardless of whether the user configured the Transmit Rate as 104268 or 104269 or 104270.

This shows how the transmit rate is calculated internally by switch software:

1 DS0 = 64000 bits/sec
or
DS0 = 8 bits x 8000 samples/sec = 64000 bits/sec
1 cell long unit = 424 bits/sec
therefore:
Number of cells per second (cps) = DS0 * 8000 / 53 bytes per ATM cell

For any user-provided Transmit Trunk Rate value in T1 cells per second (cps).

Rcv Trunk Rate = T1 x 53 /8000 (in DS0)

(This is the actual value used for everything and dictates the Transmit Trunk Load value at the other end of the trunk.)

The conversion occurs again at the other end:

T2 = R1 * 8000 / 53 (in cps)

The Transmit Load number displayed in brackets is the same, that is, 104150 cells per second, whether the user has given the Transmit Rate as 104268 or 104269 or 104270.

Receive and Transmit Rates on Virtual Trunks

The implementation of XMT Trunk Rate on a virtual trunk differs from the implementation on a physical trunk. On a physical trunk, XMT Trunk Rate limits the rate at which the back card physically generates cells. For a virtual trunk, XMT Trunk Rate does not limit the rate at which the back card generates cells: the line rate stays at the maximum for the line type. However, XMT Trunk Rate is the maximum transmission rate allowed on a virtual trunk.

The provider of the virtual trunk service assigns the value for XMT Trunk Rate. You must have this provider-assigned value for XMT Trunk Rate and enter it when you use cnftrk.

The total bandwidth of all the virtual trunks in one port cannot exceed the maximum bandwidth of the port. The trunk loading (load units) is maintained per virtual trunk, but the cumulative loading of all virtual trunks on a port is restricted by the transmit and receive rates for the port.

ILMI Neighbor Discovery on Virtual Trunks

Starting with Release 9.3.10, you can configure the ILMI protocol to run on the interface card (BXM and UXM) or on the controller card (BCC and NPM). The ILMI Neighbor Discovery feature is available for use on virtual trunks on the BXM card and UXM card. This feature enables a network management system (NMS), such as Cisco WAN Manager or CiscoWorks 2000, to discover other attached ATM devices, such as Cisco ATM routers or switches. The attached devices also must support ILMI Neighbor Discovery for this feature to work.

When ILMI Neighbor Discovery is enabled on a virtual trunk, the BPX or IGX and the attached ATM device exchange their management IP addresses and other interface information using the ILMI protocol. The exchanged information consists of the following:

•atmfMyIfName: physical interface name

•atmfMyIfIdentifier: Interface identifier

•atmfMyIpNmAddress: Management IP Address, either the LAN IP or network IP

•atmfMySysIdentifier: System Identifier, a 6-byte string read from the BPX NOVRAM, or if not available, the default value is "000001"

The management IP address is used by the NMS application to access the BPX, IGX, or the ATM device. The management IP address can be either the LAN IP address or network IP address configured for the BPX or IGX node. Use parameter option 56 (BXM) or 53 (UXM) from the cnfnodeparm SuperUser command to configure the ILMI management IP address. Enter 0 for LAN IP address, or 1 for network IP address. The default is the network IP address for the BPX and IGX.

Once the parameter is set in cnfnodeparm, you enable the ILMI Neighbor Discovery feature by using the cnftrk command. Use the parameter ILMI Run On The Card for the UXM, and Protocol By The Card for the BXM.

You use the dspnebdisc command to display all the neighbor's information discovered by the BPX or the IGX via the ILMI Neighbor Discovery procedure.

IMA-Compliant Trunk Configuration

The cnftrk command has a parameter that lets you add or delete physical lines of an existing IMA group (IMA Group member parameter). You are prompted to enter the physical lines. When you add or delete a physical link, these rules are enforced:

•You cannot delete primary links.

•The total number of physical links in the group must be greater than or equal to the number of retained links. You will be prompted to decrease the number of retained links, if necessary.

•The bandwidth of the deleted physical link will be subtracted from the trunk's Trunk Transmit Rate only. The trunk's Trunk Receive Rate is unaffected. If the Trunk Receive Rate needs to be dropped down, you will be prompted to do this first in a separate operation. You will be warned that connection reroutes may occur.

---

Note The above functional characteristics apply only to the UXM Firmware Model M, which supports the ATM Forum IMA-Compliant protocol. If a card has UXM Firmware Model A, which supports the Cisco Proprietary protocol, the IMA trunk functions as it did in Release 9.1. For example, you will not be able to add or delete physical links of an existing IMA group.

---

Primary Link—In an IMA group, you must select one of the physical links to be a primary link. This primary link number is used to refer to this IMA group or trunk. You can use cnftrk to add additional links to the group or delete existing links.

When deleting existing links from an IMA group, you cannot delete the primary link. You must first deactivate the trunk using deltrk, then use dntrk to remove the primary link.

Refer to 9.2 release notes for up-to-date feature support and system requirements.

Physical Lines Comprising an IMA Group

In Release 9.1, it was a requirement that the IMA group had to consist of consecutive physical lines. In this release, you can define an IMA trunk consisting of non-consecutive physical lines. In addition, you can change the group member by deleting a physical line from an existing IMA trunk.

Use the following syntax to specify an IMA group on a UXM trunk:

•uptrk slot.group_member.vtrk

where:

slot is the slot number

group_member is a set of physical lines composing an IMA group. You can specify the member in an expression consisting of the primary link followed by a, or - and additional physical links.

vtrk is the optional virtual trunk number. If at least one virtual trunk already exists on this port, you only have to specify the primary link as the group_member.

For example, 9.1-4 defines trunk 9.1 to consist of four physical links, that is, 1, 2, 3 and 4, where physical link 1 is the primary link. (This example is compatible with Release 9.1.)

For example, 9.1-3,5 defines trunk 9.1 to consist of four physical links, that is, 1, 2, 3 and 5 where physical link 1 is the primary link.

For example, 9.5-7,2-3 defines trunk 9.5 to consist of five physical links, that is, 2, 3, 5, 6 and 7 where physical link 5 is the primary link.

For example, 9.8,2,4,6 defines trunk 9.8 to consist of all even number of physical links where physical link 8 is the primary link.

Subrate and Fractional Trunk Configuration

For FastPacket trunks, which the NTC and NTM front cards support, you can configure the Subrate interface and Subrate data rate fields only if the back card is a BC-SR. The interface types for a subrate trunk are:

•V.11

•X.21

•V.35

•EIA/TIA-449

Set the data rate to match the subrate facility within the range 64 Kbps-1.920 Mbps.

The DS0 map is used to define fractional E1 and T1 trunks. It consists of a repeating set of specifications in the form:

<x[-y[a]]>
where
"x" and the optional "y" are DS0 numbers 0-23, and
the optional "a" indicates alternating.

The value of "y" must be greater than the value of "x." The values of both "x" and "y" cannot be less than 0 or greater than the maximum number of DS-0s for the line type. In the DS0 map for unframed E1, use 0-31. For framed E1, use 1-31. For 30 DS-0 E1, use 1-15, 17-31.

Example (BPX)

Configure a physical trunk.

cnftrk 1.1 353208 Y 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N 10 N Y N 0

hugh TN Cisco BPX 8620 9.3.3o May 16 2001 1602 PST




TRK 1.1 Config OC3 [353207cps] BXM slot 1

Transmit Rate 353208 VPC Conns disabled No

Protocol By The Card Yes Line framing STS-3C

VC Shaping No coding --

Hdr Type NNI Yes recv impedance --

Statistical Reserve 5000 cps cable type --

Idle code 7F hex length --

Connection Channels 256 Pass sync Yes

TrafficV,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock No

Restrict CC traffic No HCS Masking Yes

Link type Terrestrial Payload Scramble Yes

Routing Cost 10 Frame Scramble Yes

F4 AIS Detection No Vtrk Type / VPI -- / --

Incremental CDV 0

Deroute delay time 0 seconds

Last Command cnftrk 1.1 353208 Y 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR

N 10 N Y N 0

Example (BPX)

Configure a virtual trunk.

cnftrk 1.4.1 3000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 N 0 N N Y Y Y CBR 10 0

hugh TN Cisco BPX 8620 9.3.3o May 16 2001 1604 PST




TRK 1.4.1 Config OC3 [2867 cps] BXM slot 1

Transmit Rate 3000 VPC Conns disabled --

Protocol By The Card -- Line framing STS-3C

VC Shaping No coding --

Hdr Type NNI No recv impedance --

Statistical Reserve 1000 cps cable type --

Idle code 7F hex length --

Connection Channels 256 Pass sync No

TrafficV,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock No

Restrict CC traffic No HCS Masking Yes

Link type Terrestrial Payload Scramble Yes

Routing Cost 10 Frame Scramble Yes

F4 AIS Detection No Vtrk Type / VPI CBR / 10

Incremental CDV 0

Deroute delay time 0 seconds

Last Command cnftrk 1.4.1 3000 N 1000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR

N TERRESTRIAL 10 N 0 N N Y Y Y CBR 10 0




Example (BPX)

Configure a BNI trunk.

cnftrk 10.1 80000 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N TERRESTRIAL 10 0 Y N Y 0

hugh TN Cisco BPX 8620 9.3.3o May 16 2001 1605 PST




TRK 10.1 Config E3 [80000 cps] BNI-E3 slot 10

Transmit Rate 80000 VPC Conns disabled --

Protocol By The Card -- Line framing --

VC Shaping -- coding --

Hdr Type NNI -- recv impedance --

Statistical Reserve 5000 cps cable type

Idle code 7F hex length 0-225 ft.

Connection Channels 1771 Pass sync Yes

TrafficV,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock No

Restrict CC traffic No HCS Masking Yes

Link type Terrestrial Payload Scramble Yes

Routing Cost 10 Frame Scramble --

F4 AIS Detection -- Vtrk Type / VPI -- / --

Incremental CDV 0

Deroute delay time 0 seconds

Last Command cnftrk 10.1 80000 5000 7F V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR N

TERRESTRIAL 10 0 Y N Y 0

Example (IGX)

Configure a UXM physical trunk.

cnftrk 9.1 353207 Y N 5000 10 7F N 200 V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR 10 y N

bolger TN Cisco IGX 8430 9.3.3o May 16 2001 16:07 PST

TRK 9.1 Config OC3 [353207cps] UXM slot9

Transmit Trunk Rate 353208 cps Connection Channels 256

Rcv Trunk Rate 353207 cps Gateway Channels 200

Pass sync Yes TrafficV,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Loop clock No Incremental CDV 10

Statistical Reserve 5000 cps Frame Scramble Yes

Header Type NNI Deroute delay time 0 seconds

VPI Address 1 VC Shaping Yes

Routing Cost 10 VPC Conns disabled No

Idle code 7F hex F4 AIS Detection No

Restrict PCC traffic No

Link type Terrestrial

Line framing STS-3C

HCS Masking Yes

Payload Scramble Yes

Last Command cnftrk 9.1 353207 Y N 5000 10 7F N 200 V,TS,NTS,FR,FST,CBR,NRT-VBR

,ABR,RT-VBR 10 y N




Example (IGX)

Configure a UXM IMA trunk.

cnftrk 8.1 1-15,17-31 1-4 4 17962 17962 Y N 1000 NNI 1 10 54 N TERRESTRIAL Y Y Y 200 V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR 0 200 N N N

bolger TN Cisco IGX 8430 9.3.3o May 16 2001 1609 PST




TRK 8.1(4) Config E1/119 [17962 cps] UXM slot8

Line DS-0 map 1-15,17-31 Line coding HDB3

IMA Group Member(s) 1-4 Line CRC Yes

Retained links 4 Line recv impedance 120 ohm

Transmit Trunk Rate 17962 cps HCS Masking Yes

Rcv Trunk Rate 17962 cps Payload Scramble Yes

Pass sync Yes Connection Channels 256

Loop clock No Gateway Channels 200

Statistical Reserve 1000 cps TrafficV,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Header Type NNI Incremental CDV 0

VPI Address 1 IMA Protocol Option Enabled

Routing Cost 10 IMA Max. Diff. Dly 200 msec.

Idle code 54 hex IMA Clock Mode CTC

Restrict PCC traffic No Deroute delay time 0 seconds

Link type Terrestrial VC Shaping No

VPC Conns disabled No

F4 AIS Detection No

Last Command cnftrk 8.1 1-15,17-31 1-4 4 17962 17962 Y N 1000 NNI 1 10 54 N TER

RESTRIAL Y Y Y 200 V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR 0 200 N N N

---

Note The ATM Forum-compliant ATM Inverse Multiplexing standard does not support the IMA link autodisable option. Previous to Release 9.2, the IMA link auto disable parameter displayed for IMA links, but it does not display in Release 9.2 or higher. The IMA group member and IMA Differential delay parameters are configurable. The IMA Clock Mode parameter is fixed at CTC and is not configurable. Also, note that you can configure IMA trunk parameters on virtual trunks that are on top of IMA ports.

---




Example (IGX)

Configure a UXM virtual trunk.

cnftrk 18.3.5 3000 2867 N N 1000 N 10 7F N TERRESTRIAL PLCP 1 Y N200 V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR CBR 10 100 Y y Y

bolger TN Cisco IGX 8430 9.3.3o May 16 2001 1614 PST




TRK 18.3.5 Config T3/19 [2867 cps] UXM slot18

Transmit Trunk Rate 3000 cps Connection Channels 256

Rcv Trunk Rate 2867 cps Gateway Channels 200

Pass sync No TrafficV,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Loop clock No Vtrk Type / VPI CBR / 10

Statistical Reserve 1000 cps Incremental CDV 100

Header Type NNI Deroute delay time 0 seconds

Routing Cost 10 VC Shaping Yes

Idle code 7F hex ILMI run on the card Yes

Restrict PCC traffic No F4 AIS Detection Yes

Link type Terrestrial

Line framing PLCP

Line cable length 0-225 ft.

HCS Masking Yes

Payload Scramble No

Last Command cnftrk 18.3.5 3000 2867 N N 1000 N 10 7F N TERRESTRIAL PLCP 1 Y N

200 V,TS,NTS,FR,FST,CBR,NRT-VBR,ABR,RT-VBR CBR 10 100 Y y Y




cnftrkalm (configure trunk alarms)

Configures trunk alarm reporting. When trunks are upped and added to the network, alarm reporting automatically is enabled. The cnftrkalm command lets you disable alarms on a trunk. Disabling alarms may be useful, for example, for trunks that are connected to the node but not yet in service or if the node is experiencing occasional bursts of errors but is still operational.

When the alarms are enabled, they cause an alarm output from the DTI Group Alarm Connector (if present) and an alarm indication on the Cisco WAN Manager terminal.

A virtual trunk also has trunk port alarms that are shared with all the other virtual trunks on the port. These alarms are cleared and set together for all the virtual trunks sharing the same port.

Statistical alarms are provided on cell drops from each of the Advanced CoS Management queues. These alarms are maintained separately for virtual trunks on the same port.

On an IGX node, enabled alarms cause an output from the ARC or ARM card or an indication to Cisco WAN Manager.

Syntax

cnftrkalm <slot.port>[.vtrk] <e | d>

Parameters

Parameter	Description
<slot.port>	Specifies the trunk number.
[.vtrk]	Specifies the virtual trunk number. Optional.
<e | d>	Enables or disables the alarm.

Attributes

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

Related Commands

dspalms, dsptrks

Trunk Alarms

Table 3-44 shows physical and logical trunk alarms, with the alarm type, the physical interface type, and whether the alarm is a logical, statistical, or integrated alarm.

Table 3-44 Physical and Logical Trunk Alarms Supported on IGX and BPX 

Alarm Type	Physical					Logical	Statistical	Integrated
	T1	E1	T3	E3	SONET
LOS	X	X	X	X	X		X	X
OOF	X	X	X	X	X		X	X
AIS	X	X	X	X	X		X	X
YEL	X	X	X	X	X			X
PLCP OOF			X					X
LOC				X	X			X
LOP					X			X
PATH AIS					X			X
PATH YEL					X			X
PATH TRC					X			X
SEC TRC					X			X
ROOF	X	X						X
FER	X	X						X
AIS16	X	X					X	X
IMA	X	X						X
NTS Cells Dropped						X	X
TS Cells Dropped						X	X
Voice Cells Dropped						X	X
Bdata Cells Dropped						X	X
BdatB Cells Dropped						X	X
HP Cells Dropped						X	X
CBR Cells dropped						X	X
VBR Cells dropped						X	X
ABR Cells dropped						X	X

Statistical alarms are provided on cell drops from each of the Advanced CoS Management queues. These alarms are maintained separately for virtual trunks on the same port.

A virtual trunk also has trunk port alarms that are shared with all the other virtual trunks on the port. These alarms are cleared and set together for all the virtual trunks sharing the same port.

IMA physical line alarms are a special case. Each IMA trunk port has a configurable number of retained links. If the number of non-alarmed lines is less than the number of retained links, the logical trunks on the IMA trunk port are placed into major alarm.

For example, suppose there are IMA virtual trunks 4.5-8.2 and 4.5-8.7. Further, the number of retained links on 4.5-8 has been configured to 2. If 4.5 and 4.6 go into LOS, physical line alarms are generated for these 2 physical lines. The logical trunks 4.5-8.2 and 4.5-8.7 do not go into alarm because the two retained links are still healthy. In this situation, the bandwidth on the logical trunks is adjusted downwards to prevent cell drops, and the connections on those trunks are rerouted. If a third line goes into alarm, the logical trunks are then failed. See Table 3-45 for a list of physical and trunk alarms that are supported on IMA lines.

Table 3-45 Physical and Logical Alarms Supported on IMA Physical Lines 

Alarm Type	Physical					Logical	Statistical	Integrated
	T1	E1	T3	E3	SONET
LOS	X	X	X	X	X		X	X
OOF	X	X	X	X	X		X	X
AIS	X	X	X	X	X		X	X
YEL	X	X	X	X	X			X
PLCP OOF			X					X
LOC				X	X			X
LOP					X			X
PATH AIS					X			X
PATH YEL					X			X
PATH TRC					X			X
SEC TRC					X			X
ROOF	X	X						X
FER	X	X						X
AIS16	X	X					X	X
IMA	X	X						X
NTS Cells Dropped						X	X
TS Cells Dropped						X	X
Voice Cells Dropped						X	X
BDATA Cells Dropped						X	X
BDATB Cells Dropped						X	X
HP Cells Dropped						X	X
CBR Cells Dropped						X	X
VBR Cells Dropped						X	X
ABR Cells Dropped						X	X

Example

Disable trunk alarms on trunk 7.

cnftrkalm 7 d

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

PLN Type Current Line Alarm Status Other End

7 E1/32 Clear - Line OK alpha.10

9 T1/24 Clear - Line OK gamma.10

13 T1/24 Clear - Line OK alpha.14

15 T1/24 Clear - Line OK gamma.15

20 T3/3 Major - AIT Missing -




Last Command: cnftrkalm 7 d




Next Command:

Example

Enable the alarms after they have been disabled.

cnftrkalm 8 d

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 09:44 GMT




TRK Type Current Line Alarm Status Other End

8 T1/24 Clear - OK sw108/14






Last Command: cnftrkalm 8 d

Example

cnftrkalm 8 e

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 09:48 GMT




TRK Type Current Line Alarm Status Other End

8 T1/24 Clear - OK sw108/14






Last Command: cnftrkalm 8 e

cnftrkict (configure trunk interface control template)

Configures the output lines of an interface control template for a subrate trunk. Table 3-46 shows the configurable signals.

Table 3-46 Configurable Signals in an Interface Control Template

Interface Type	Output Signal	Inputs
X.21	C, I
V.35	RTS, DTR	CTS, DSR
MIL-188	IS, LL, RL, RS, SF, SS, TR	DM, CS

Syntax

cnftrkict <line> <output> <source>

Parameters

Parameter	Description
<line>	Specifies the trunk for the interface control template.
<output>	Specifies the output lead to be configured. Configurable output leads vary depending on the type of data interface used (X.21or V.35).
<source>	Specifies how the specified output lead is to be configured. The options are as follows: •On, which means the output lead is asserted. •Off, which means the output lead is inhibited. •l (lower case L) Output follows a local input lead. •Input, which specifies the name of the local input lead that the output lead follows. Input leads vary according to the type of data interface supported (X.21 or V.35).

Attributes

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

Related Commands

dsptrkict, prttrkict

Example

Configure output lead "c" as "on" in the interface control template for subrate trunk 9.

cnftrkict 9 c on

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

Packet Line: 9

Interface: X.21 DTE




Interface Control Template for Trunk Line




Lead Output Value Lead O Output Value

C /DTR ON





Last Command: cnftrkict 9 c on

Next Command:

cnftrkparm (configure trunk card parameters)

Sets specified trunk parameters for these front cards:

•UXM/UXM-E

•AIT

•NTC

•NTM

•BNI

•BXM/BXM-E

Use the cnftrkparm command to optimize a network for particular traffic mixes. Use this command to configure any of the trunk-specific parameters associated with a trunk card. It applies to either a FastPacket trunk or a ATM trunk.

For ATM trunks, cnftrkparm applies to both physical and virtual trunks. BXM and UXM virtual trunks have the same configuration parameters for queues as physical trunks.

The integrated alarm thresholds for major alarms and the gateway efficiency factor is the same for all virtual trunks on the port. Note that BNI VTs are supported by a single queue and do not support configuration of all the OptiClass queues on a single virtual trunk.

You can also use this command to reconfigure trunk queue depths to meet the CEPT requirement for a maximum end-to-end delay of 10 milliseconds. For this purpose, enter:

cnftrkparm <trunk number> <parameter index> <parameter value>

where:

trunk number specifies the trunk.
parameter index is 2 (which corresponds to the NTS queue).
parameter value is 7 (which is the maximum allowable queue depth).

When the system receives this command and a trunk number, it displays the configurable parameters with an index number for each. The parameters vary with the trunk type, as the subsequent figures and tables show.

Configuring Trunk Queues Used by Real-Time VBR and Non-Real-Time VBR Connections

Qbin values on both ports and trunks used by rt-VBR connections and nrt-VBR connections can be configured separately. (To configure Qbin values on ports, use cnfportq.)

The rt-VBR traffic type (or connection class) is supported on the IGX UXM and BPX BXM, ASI, and BNI cards. However, the rt-VBR class of service is not supported for MGX 8850 or MGX 8220 interface shelves.

A rt-VBR connection uses the rt-VBR queue on a trunk. It shares this queue with voice traffic. The rt-VBR and voice traffic shares the default or user-configured parameters for the rt-VBR queue. These parameters are queue depth, queue CLP high and CLP low thresholds, EFCI threshold, and queue priority.

A nrt-VBR connection uses the nrt-VBR queue on a trunk. The configurable parameters are queue depth, queue CLP high and CLP low thresholds, EFCI threshold, and queue priority.

You can configure the Qbin values separately for rt-VBR and nrt-VBR classes on trunks using the cnftrkparm command. For rt-VBR, the cnftrkparm command configures Q-depth rt-VBR and Max Age rt-VBR. For nrt-VBR, the cnftrkparm command configures Q-depth nrt-VBR, Low CLP nrt-VBR, and High CLP nrt-VBR.

For information on configuring port queues used by rt-VBR and nrt-VBR connections, see the cnfportq command.

Syntax

cnftrkparm <trk number> <parm index> <parm value>

Parameters

Parameter	Description
<trk number>	Specifies the trunk to configure. To specify a virtual trunk, use this format: slot.port.vtrk.
<parm index>	Specifies the parameter to change.
<parm value>	Specifies the value of the parameter.

Attributes

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

Related Commands

dsptrkstathist, dsptrkstatcnf

Physical and Virtual Parameters Configurable with cnftrkparm

All virtual trunks on a BNI card are supported by a single queue; therefore, you cannot configure all the Advanced CoS Management queues on a single virtual trunk.

The UXM and BXM share the same queueing architecture. The egress cell traffic out a port is queued in two stages. First they are queued per virtual interface (VI), each of which supports a virtual trunk. Within each virtual interface, the traffic is queued according to its normal Advanced CoS Management traffic type. In other words, voice, Time-Stamped, Non-Time-Stamped, High-Priority, BData, BDataB, CBR, rt-VBR, nrt-VBR, and ABR traffic is queued separately.

The overall queue depth of the virtual interface is the sum of all the queue depths for all the available queues. Since each virtual trunk occupies one virtual interface (VI), the overall queue depth available for the virtual trunk is that of its VI. You do not configure the virtual interface directly, however, you use the cnftrkparm command to configure the queues within the virtual trunk.

Although the traffic consists of Frame Relay in cells, the traffic can pass through a BPX node. Therefore, the Bursty Data queues exist in the BPX node.

BXM and UXM virtual trunks have all the configuration parameters for queues that physical trunks have. The integrated alarm thresholds for major alarms and the gateway efficiency factor is the same for all virtual trunks on the port. Note that BNI virtual trunks are supported by a single queue and do not support configuration of all the Advanced CoS Management (formerly OptiClass) queues on a single virtual trunk.

Table 3-47 provides a list of physical and virtual parameters that you can configure using cnftrkparm. X in the table indicates that the parameter is configurable. X* in the virtual trunk column indicates the parameter is a physical parameter, and changing the value for one virtual trunk on the port will automatically cause all virtual trunks on the port to be updated with the same value.

Table 3-47 cnftrkparm—Configurable Parameters for Physical and Virtual Trunks  

Description of cnftrkparm Parameters	BXM		UXM
	Physical	Virtual	Physical	Virtual
Queue Depth - rt-VBR	X	X	X	X
Queue Depth - NTS	X	X	X	X
Queue Depth - TS	X	X	X	X
Queue Depth - Bdata A	X	X	X	X
Queue Depth - Bdata B	X	X	X	X
Queue Depth - High Priority	X	X	X	X
Queue Depth - CBR	X	X	X	X
Queue Depth - nrt-VBR	X	X	X	X
Queue Depth - ABR	X	X	X	X
Max Age - rt-VBR	X	X	X	X
Red Alm - I/O	X	X*	X	X*
Yel Alm - I/O	X	X*	X	X*
Lo/Hi CLP and EFCN Bdata A	X	X	X	X
Lo/Hi CLP and EFCN Bdata B	X	X	X	X
Lo/Hi CLP for CBR	X	X	X	X
Lo/Hi CLP for VBR	X	X	X	X
Low/Hi CLP, and EFCN for ABR	X	X	X	X
EPD and EFCN for CBR and nrt-VBR			X	X
SVC Queue pool size	X	X
Gateway Efficiency			X	X*

Display Fields (IGX)

Index	Parameter	Description
1, 18	Yel/Red Alarm In/Out	Specifies a time period relating to when a trunk goes into a red or yellow alarm and after it comes out of the alarm state. The applicable type of alarm here stems from a physical line problem rather than from a statistical error. The purpose of this parameter is to prevent the switch from rerouting the connections after a very brief problem or from prematurely informing switch software that the trunk is back in service (after a failure). The implementation is •The "into" alarm value is the time the card waits after a local (red) or yellow (remote) problem occurs before the card alerts switch software of the problem. •The "out of" alarm value is the time the card waits after a local, physical problem is cleared before the card alerts switch software that the problem no longer exists.
2, 19	Rx/Tx Max. Age: - rt-VBR	Specifies a multiplier for 125-microsecond increments for the maximum age of rt-VBR (or voice) packets. For example, with the default of 20, the node discards rt-VBR (or voice) packets older than 2.5 seconds.
3, 20	Rx/Tx EFCN - BdataB	For packets or cells received from the trunk carrying Optimized Bandwidth Management Frame Relay, the node sets the FECN bit above this threshold.
4	Gateway Efficiency	Specifies an expected average number of FastPackets in each cell arriving from a trunk. The purpose of this parameter is to help switch software regulate bandwidth usage the cell bus in an IGX node. The range is 1.0-3.0. (This parameter does not apply to the BXM card.)
5	EFCN - Rx Space	Same as 3, 20 except that FECN - Rx Space sets the threshold in the Rx space queues in the AIT card. Rx space queues face toward the IGX node.
6, 7	Low-High CLP-Rx Space	Same as 8, 9 except this threshold is for setting CLP in receive spacer queues for data to send to the local node.
8, 9	Rx High CLP (Bdata A/BdataB)	Frame Relay cells/packets received from trunk with CLP bit set above this high threshold will be dropped and will continue to be dropped until the low threshold is crossed. Separate queues for Optimized Bandwidth Management and non-Optimized Bandwidth Management data. Given in terms of percent of queue depth.
10, 11	Rx Low CLP (Bdata A/BdataB)	Same as for 8, 9 except sets low threshold.
12-17	Receive Queue Depth (rt-VBR, NTS, TS, BData A, BData B, High Pri.)	Reserves RAM in the trunk card for each of the receive queues in terms of the number of packets.
25, 26	Tx High CLP	Same as 8, 9 except this is threshold for setting CLP in transmit queues for data to be output to the next link.
27, 28	Tx Low CLP	Same as for 25, 26 except sets low threshold.
29-34	Transmit Queue Depth	Reserves RAM in the trunk card for each of the transmit queues in terms of the number of packets.

Example (IGX)

cnftrkparm 13

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 15:58 PST




PLN 13 Parameters:

1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 22] 32 BDataA [ 301]

13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 114] 33 BDataB [ 301]

14 TS [ N/A] 17 HighPri[ N/A] 31 TS [2616] 34 HighPri[ 100]




Last Command: cnftrkparm 13





Next Command:




---

Note For parameter 12, the system displays: "Warning—don't change Voice Q size, use Max Voice Age."

---

Display Fields (BPX)

Index	Parameter	Description
1	Q Depth - rt-VBR	Specifies the queue depth in cells for rt-VBR and voice traffic. This parameter relates to item 7, Max Age - rt-VBR: if you increase the value for Max Age - rt-VBR, the node increases the size of the rt-VBR (or voice) Packet Queue because more voice packets can accumulate due to a greater age. In Release 9.2, for BXM trunks, the rt-VBR and voice service types share the same queue (the rt-VBR queue). Similarly, for BXM trunks, rt-VBR and voice traffic share the default or user-configured voice Qbin values.
2	Q Depth - Non-TS	Specifies the queue depth in cells for non-time-stamped traffic.
3	Q Depth - TS	Specifies the queue depth in cells for time-stamped traffic.
4	Q Depth - BData A	Specifies the depth in cells for the bursty data A queue.
5	Q Depth - BData B	Specifies the depth in cells for the bursty data B queue.
6	Q Depth - High Pri	Specifies the queue depth in cells for high priority traffic.
7	Max Age - rt-VBR	Specifies a multiplier for 125-microsecond increments for the maximum age of rt-VBR (or voice) packets. For example, with the default of 20 microseconds, the node discards rt-VBR (or voice) packets older than 2.5 seconds. This value is the same as the default queue delay. The Max Age - rt-VBR (or voice) Qbin threshold can be calculated as follows: (20 * (125 microseconds) * num_ds0s/53 cells + 2) for any trunk. This parameter relates to item 1, Q Depth - rt-VBR: if you increase the value for Max Age - rt-VBR, the node increases the size of the Voice (or rt-VBR) Packet Queue because more rt-VBR (or voice) packets can accumulate due to a greater age.
8	Red Alm - I/O (Dec)	Specifies a time period relating to when a trunk goes into red alarm and after it comes out of the alarm state. The applicable type of alarm here stems from a physical line problem rather than from a statistical error. The purpose of this parameter is to prevent the switch from rerouting the connections after a very brief problem or from prematurely informing switch software that the trunk is back in service (after a failure). The implementation is: •The "into" alarm value is the time the card waits after a local, physical problem occurs before the card alerts switch software of the problem. •The "out of" alarm value is the time the card waits after a local, physical problem is cleared before the card alerts switch software that the problem no longer exists.
9	Yel Alm - I/O (Dec)	Specifies a time period relating to when a trunk goes into yellow alarm and after it comes out of the alarm state. The applicable type of alarm here stems from a physical line problem rather than from a statistical error. The purpose of this parameter is to prevent the switch from rerouting the connections after a very brief problem or from prematurely informing switch software that the trunk is back in service (after a failure). The implementation is: •The "into" alarm value is the time the card waits after a remote, physical problem occurs before the card alerts local switch software of the problem. •The "out of" alarm value is the time the card waits after a remote, physical problem is cleared before the card alerts local switch software that the problem no longer exists.
10	Low CLP - BData A	Specifies a percent of the Bursty Data A queue. When the number of cells in the queue falls below this percentage, the switch stops discarding cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1.
11	High CLP - BData A	Specifies a percent of the Bursty Data A queue. When the number of cells in the queue reaches this percentage, the switch begins to discard cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1 regardless of the cell count in the queue.
12	Low CLP - BData B	Specifies a percent of the Bursty Data B queue. When the number of cells in the queue falls below this percentage, the switch stops discarding cells with CLP=1.
13	High CLP - BData B	Specifies a percent of the Bursty Data B queue. When the number of cells in the queue reaches this percentage, the switch begins to discard cells with CLP=1.
14	EFCN - BData B	Specifies the number of cells in the Bursty Data B queue that causes the switch to send congestion notification to the destination node. The default is low in relation to the default queue depth so that notification begins to go out as soon as congestion begins.
15	Q Depth - CBR	Specifies the depth of the queue dedicated to CBR traffic.
16	Q Depth - nrt-VBR	Specifies the depth of the queue dedicated to nrt-VBR traffic.
17	Q Depth - ABR	Specifies the depth of the queue dedicated to ABR traffic.
18	Low CLP - CBR	Specifies a percent of the CBR queue. When the number of cells in the queue falls below this percentage, the node stops discarding cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1 regardless of the cell count in the queue. The reason the default is 100% is that, with CBR, congestion is not an expected condition.
19	High CLP - CBR	Specifies a percent of the CBR queue. When the number of cells in the queue reaches this percentage, the node begins to discard cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1 regardless of the cell count in the queue. The reason the default is 100% is that, with CBR, congestion is not an expected condition.
20	Low CLP - nrt-VBR	Specifies a percent of the nrt-VBR queue. When the number of cells in the queue falls below this percentage, the node stops discarding cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1 regardless of the cell count in the queue. The reason the default is 100% is that, with VBR, congestion is not an expected condition.
21	High CLP - nrt-VBR	Specifies a percent of the nrt-VBR queue. When the number of cells in the queue reaches this percentage, the node begins to discard cells with CLP=1. The default of 100% disables the function, which causes the switch to discard all cells with CLP=1 regardless of the cell count in the queue. The reason the default is 100% is that, with VBR, congestion is not an expected condition.
22	Low CLP - ABR	Specifies a percent of the ABR queue. When the number of cells in the queue falls below this percentage, the node stops discarding cells with CLP=1.
23	High CLP - ABR	Specifies a percent of the ABR queue. When the number of cells in the queue reaches this percentage, the node begins to discard cells with CLP=1.
24	EFCN - ABR	Specifies the number of cells in the ABR queue that causes the switch to send congestion notification to the destination node. The default is low in relation to the default queue depth so that notification begins to go out as soon as congestion begins.
25	SVC Queue Pool Depth	Specifies the collective size of the queue depth for all SVC connections.

Example (BPX)

cnftrkparm 1.1

pubsbpx1 TN SuperUser BPX 8620 9.3 Apr. 13 2000 09:37 GMT

TRK 1.1 Parameters

1 Q Depth - rt-VBR [ 242] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 9070] (Dec)

4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000] 22 Low CLP - ABR [ 25] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000] 23 High CLP - ABR [ 75] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (Dec)

11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 144] (Dec)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 1.1

Which parameter do you wish to change:




Example (BXM OC-12 Trunk)




sw97 TRM SuperUser BPX 8620 9.3 Apr. 13 2000 13:14 GMT

TRK 13.1 Parameters

Trunk Type: NNI

1 Q Depth - rt-VBR [ 3000] (Dec) 15 Q Depth - CBR [ 1200] (Dec)

2 Q Depth - Non-TS [ 3000] (Dec) 16 Q Depth - rt-VBR [ 10000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 30000] (Dec)

4 Q Depth - BData A [ 20000] (Dec) 18 Low CLP - CBR [ 100] (%)

5 Q Depth - BData B [ 20000] (Dec) 19 High CLP - CBR [ 100] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - rtVBR [ 100] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - rt-VBR [ 100] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000] 22 Low CLP - ABR [ 25] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000] 23 High CLP - ABR [ 75] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (Dec)

11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 144] (Dec)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

Last Command: cnftrkparm 13.1

Next Command:




---

Note In Release 9.2.20 and higher, rt-VBR and voice connections both use the voice Qbin on the trunk. Similarly, rt-VBR and voice traffic both share the default or user-configured voice Qbin values for the trunk—Queue depth, CLP High/Low Threshold, EFCI Threshold, and Queue priority.

---

Example (BPX Virtual Trunk)

cnftrkparm 1.1.1

sw97 TN SuperUser BPX 15 9.3 Apr. 13 2000 10:11 GMT




TRK 1.1.1 Parameters

8 Red Alm - I/O (Dec) [ 2500 / 10000]

9 Yel Alm - I/O (Dec) [ 2500 / 10000]

15 Q Depth - CBR [ 2678] (Dec)

18 Low CLP - CBR [ 100] (%)

19 High CLP - CBR [ 100] (%)






This Command: cnftrkparm 1.1.1





Which parameter do you wish to change:

Example (IGX OC-3 Trunk)

cnftrkparm 6.3

sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:25 PST

TRK 6.3 Parameters:

1 Yel Alm-In/Out (D) [ 2500/ 10000] 18 Red Alm-In/Out (D) [ 2500/ 10000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ 100] 10 BDataA [ 100] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ 75] 11 BdataB [ 25] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 1952] 15 BDataA [10000] 29 rt-VBR [ 1952] 32 BDataA [10000]

13 Non TS [ 2925] 16 BDataB [10000] 30 Non TS [ 2924] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 6.3




sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:26 PST

TRK 6.3 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (D) Tx EFCN (D)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR [ 5000] 39 rt-VBR [ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 30] 48 ABR [ 30]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

41 CBR [ 100] 44 CBR [ 100] 49 CBR [ 100] 52 CBR [ 100]

42 nrt-VBR [ 100] 45 nrt-VBR 100] 50 nrt-VBR [ 100] 53 VBR [ 100]

43 ABR [ 75] 46 ABR [ 25] 51 ABR [ 75] 54 ABR [ 25]




This Command: cnftrkparm 6.3




Example (IGX) T3 or E3 Trunk




sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:25 PST

TRK 8.1 Parameters:

1 Yel Alm-In/Out (D) [ 2500/ 10000] 18 Red Alm-In/Out (D) [ 2500/ 10000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ 100] 10 BDataA [ 100] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ 75] 11 BdataB [ 25] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 242] 15 BDataA [ 8000] 29 rt-VBR [ 242] 32 BDataA [ 8000]

13 Non TS [ 360] 16 BDataB [ 8000] 30 Non TS [ 360] 33 BDataB [8000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 8.1

sw228 TN SuperUser IGX 8420 9.3 Apr. 13 2000 18:26 PST

TRK 8.1 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (D) Tx EFCN (D)

35 CBR [ 400] 38 CBR [ 400]

36 nrt-VBR [ 5000] 39 VBR [ 5000]

37 ABR [10000] 40 ABR [10000] 47 ABR [ 30] 48 ABR [ 30]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

41 CBR [ 100] 44 CBR [ 100] 49 CBR [ 100] 52 CBR [ 100]

42 nrt-VBR [ 100] 45 nrt-VBR [ 100] 50 nrt-VBR [ 100] 53 nrt-VBR [ 100]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]




Example (BXM Trunk)

cnftrkparm 2.4

pubsbpx1 TN silves:1 BPX 8620 9.3 Apr. 13 2000 10:50 PDT






TRK 2.4 Parameters

1 Q Depth - rt-VBR [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [20000] (Dec)

4 Q Depth - BData A [10000] (Dec) 18 Low CLP - CBR [ 60] (%)

5 Q Depth - BData B [10000] (Dec) 19 High CLP - CBR [ 80] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)

8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)

11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 2.4




cnftrkstats (configure trunk statistics collection)

Configures collection of Qbin statistics for a selected trunk.

You can enable collection of Qbin statistics collected by the BPX and IGX. Qbin statistics are Cells Served, Cells Discarded, and Cells Received.

•UXM and BXM Qbins 1-9 on Automatic Routing Management trunks.

•BXM qbins 0-3, 9 on Automatic Routing Management ports.

•UXM qbins 2,3, 7-9 on Automatic Routing Management ports.

•UXM and BXM Qbins 10-15 on VSI ports and trunks.

All other Qbins are unused, and the switch does not provide statistics for them. Also starting in switch software release 9.3.10, the switch provides the collection of Qbin Cells Discarded statistics via SNMP for the above mentioned Qbins.

The cnftrkstats command is primarily a debug command. It configures the collection of statistics for a physical or virtual trunk. After displaying all statistic types for the trunk, the system prompts for "statistic type." Enter the index number associated with the statistic.

Not all types of statistics are available for all lines. Unavailable selections appear in half-tone. Table 3-48 lists the types of statistics that are configurable for FastPacket T1 trunks and ATM T3 trunks. The subsequent figures show the screens associated with T1 packet trunks and T3 ATM trunks.

Table 3-48 Statistics Configurable for FastPacket T1 trunks and ATM T3 Trunks 

Categories of Statistics Types	Categories of Statistics Types
Line faults	Line errors and errored seconds
Frame Slips and Loss	Path errors
Transmit packets dropped	Cell framing errors
Packets transmitted for various packet types	EFCN packets transmitted to bus
Packets dropped for various packet types	Queue Service Engine (QSE) cells transmitted
Bursty data CLP packets and cells dropped	Spacer packets transmitted and dropped for each of the 16 queues
Errored seconds	The number of seconds in which errors occurred

Syntax

cnftrkstats <line> <stat> <interval> <e | d> [<samples> <size> <peaks>]

Parameter

Parameter	Description
<line>	Specifies the trunk to configure.
<stat>	Specifies the type of statistic to enable/disable.
<interval>	Specifies the time interval of each sample. Range:1-255 minutes
<e | d>	Enables/disables a statistic. E to enable; D to disable.
[samples]	Specifies the number of samples to collect (1-255).
[size]	Specifies the number of bytes per data sample (1, 2 or 4).
[peaks]	Enables/disables collection of 10-second peaks. Y enables; N disables.

Attributes

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

Related Commands

dsptrkstatcnf, dsptrkstathist

Example (ATM on IGX's AIT Card)

These screens pertain to an ATM trunk (AIT card) on an IGX node. Other trunk types and cards have other parameters. To see the list of these, enter the command and continue from page to page without entering an index number.




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:45 PST




Line Statistic Types

3) Out of Frames 22) BDA Packets Transmitted

4) Losses of Signal 23) BDB Packets Transmitted

10) Packet CRC Errors 24) Total Packets Transmitted

12) Tx Voice Packets Dropped 25) BDA CLP Packets Dropped

13) Tx TS Packets Dropped 26) BDB CLP Packets Dropped

14) Tx NTS Packets Dropped 27) BDA EFCN Pkts Transmitted

15) Tx CC Packets Dropped 28) BDB EFCN Pkts Transmitted

16) Tx BDA Packets Dropped 29) Line Code Violations

17) Tx BDB Packets Dropped 30) Line Errored Seconds

18) Voice Packets Transmitted 31) Line Severely Err Secs

19) TS Packets Transmitted 32) Line Parity Errors

20) NTS Packets Transmitted 33) Errored Seconds - Line

21) CC Packets Transmitted 34) Severely Err Secs - Line




This Command: cnftrkstats 11





Continue?

___________________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:46 PST




Line Statistic Types

35) Path Parity Errors 48) Tx nrt-VBR Cells Drpd

36) Errored Secs - Path 49) Tx TimeStamped Cells Drpd

37) Severely Err Secs - Path 50) Tx NTS Cells Dropped

38) Severely Err Frame Secs 51) Tx Hi-Pri Cells Drpd

39) AIS Signal Seconds 52) Tx BData A Cells Drpd

40) Unavail. Seconds 53) Tx BData B Cells Drpd

41) BIP-8 Code Violations 54) Voice Cells Tx to line

42) Cell Framing Errored Seconds 55) TimeStamped Cells Tx to ln

43) Cell Framing Sev. Err Secs. 56) NTS Cells Tx to line

44) Cell Framing Sec. Err Frame Secs 57) Hi-Pri Cells Tx to line

45) Cell Framing Unavail. Secs. 58) BData A Cells Tx to line

46) ATM Cell Header HEC Errs 59) BData B Cells Tx to line

47) Pkts. Rx from Muxbus 60) Half Full cells Tx to ln




This Command: cnftrkstats 11





Continue?

______________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:47 PST




Line Statistic Types

61) Full cells Tx to ln 74) Rx Hi-pri Pkts Dropped

62) Total Cells Tx to line 75) Rx BDA Pkts Dropped

63) Tx Bdata A CLP Cells Drpd 76) Rx BDB Pkts Dropped

64) Tx Bdata B CLP Cells Drpd 77) Voice pkts Tx to Muxbus

65) Bdata A EFCN Cells Tx ln 78) TS pkts Tx to Muxbus

66) Bdata B EFCN Cells Tx ln 79) NTS pkts Tx to Muxbus

67) Half Full Cells Rx from ln 80) Hi-pri pkts Tx to Muxbus

68) Full Cells Rx from line 81) Bdata A pkts Tx to Muxbus

69) Total Cells Rx from line 82) Bdata B pkts Tx to Muxbus

70) Total pkts Rx from line 83) Rx Bdata A CLP pkts drpd

71) Rx Voice Pkts Dropped 84) Rx Bdata B CLP pkts drpd

72) Rx TS Pkts Dropped 85) Bdata A EFCN Pkts Tx muxbus

73) Rx NTS Pkts Dropped 86) Bdata B EFCN Pkts Tx muxbus




This Command: cnftrkstats 11





Continue?




__________________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:48 PST




Line Statistic Types

87) Total Pkts Tx to muxbus 100) Rx Spacer 2 Pkts dropped

88) Rx voice cells drpd 101) Rx Spacer 3 Pkts dropped

89) Rx TimeStamped Cells drpd 102) Rx Spacer 4 Pkts dropped

90) Rx NTS Cells dropped 103) Rx Spacer 5 Pkts dropped

91) Rx Hi-pri Cells dropped 104) Rx Spacer 6 Pkts dropped

92) Rx Bdata A Cells dropped 105) Rx Spacer 7 Pkts dropped

93) Rx Bdata B Cells dropped 106) Rx Spacer 8 Pkts dropped

94) Rx Bdata A CLP cells drpd 107) Rx Spacer 9 Pkts dropped

95) Rx Bdata B CLP cells drpd 108) Rx Spacer 10 Pkts dropped

96) Rx Spacer CLP Pkts drpd 109) Rx Spacer 11 Pkts dropped

97) Spacer EFCN Pkts Tx to Muxbus 110) Rx Spacer 12 Pkts dropped

98) Frame Sync Errors 111) Rx Spacer 13 Pkts dropped

99) Rx Spacer 1 Pkts dropped 112) Rx Spacer 14 Pkts dropped




This Command: cnftrkstats 11




___________________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:49 PST




Line Statistic Types

113) Rx Spacer 15 Pkts dropped 126) Spacer 10 Pkts Tx to Muxbus

114) Rx Spacer 16 Pkts dropped 127) Spacer 11 Pkts Tx to Muxbus

115) Rx Spacer Pkts drpd 128) Spacer 12 Pkts Tx to Muxbus

116) Spacer 0 Pkts Tx to Muxbus 129) Spacer 13 Pkts Tx to Muxbus

117) Spacer 1 Pkts Tx to Muxbus 130) Spacer 14 Pkts Tx to Muxbus

118) Spacer 2 Pkts Tx to Muxbus 131) Spacer 15 Pkts Tx to Muxbus

119) Spacer 3 Pkts Tx to Muxbus 132) Spacer 16 Pkts Tx to Muxbus

120) Spacer 4 Pkts Tx to Muxbus 133) Rx Voice QSE Cells Tx

121) Spacer 5 Pkts Tx to Muxbus 134) Rx Time Stamped QSE Cells Tx

122) Spacer 6 Pkts Tx to Muxbus 135) Rx NTS QSE Cells Tx

123) Spacer 7 Pkts Tx to Muxbus 136) Rx Hi Priority QSE Cells Tx

124) Spacer 8 Pkts Tx to Muxbus 137) Rx BData A QSE Cells Tx

125) Spacer 9 Pkts Tx to Muxbus 138) Rx Bdata B QSE Cells Tx




This Command: cnftrkstats 11

__________________________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 15:02 PST




Line Statistic Types

139) Rx BData A EFCN QSE Cells Tx 152) Cell Framing Yel Transitions

140) Rx BData B EFCN QSE Cells Tx 153) AIS Transition Count

141) FEBE Counts 161) CGW Packets Rx From IGX Net

142) FERR Counts (M or F bit) 162) CGW Cells Tx to Line

143) Cell Framing FEBE Err Secs 163) CGW Frms Relayed to Line

144) Cell Framing FEBE Sev. Err. Secs. 164) CGW Aborted Frames Tx to Line

145) Cell Framing FEBE Counts 165) CGW Dscd Pkts From Abted Frms

146) Cell Framing FE Counts 166) CGW 0-Lngth Frms Rx from Line

147) ATM CRC Errored Seconds 167) CGW Packets Tx to IGX Net

148) ATM CRC Severely Err. Secs. 168) CGW Cells Rx from Line

149) Bdata A CLP Packets Tx to Line 169) CGW Frms Relayed from Line

150) Bdata B CLP Packets Tx to Line 170) CGW Aborted Frms Rx From Line

151) Yellow Alarm Transition Count 171) CGW Dscd Cells From Abted Frms




This Command: cnftrkstats 11

________________________________________________________________




sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 14:51 PST




Line Statistic Types

172) CGW Bd CRC32 Frms Rx from Line 185) OAM Valid OAM Cells Rx

173) CGW Bd Lngth Frms Rx from Line 186) OAM Loopback Cells Rx

174) CGW Bd CRC16 Frms Rx from IGX 187) OAM AIS Cells Rx

175) CGW Bd Length Frms Rx from IGX 188) OAM FERF Cells Rx

176) CGW 0-Length Frms Rx from IGX 189) OAM RTD Cells Rx

177) OAM Valid OAM Cells Tx 190) OAM RA Cells Rx

178) OAM Loopback Cells Tx 191) OAM Invalid OAM Cells Rx

179) OAM AIS Cells Tx 192) OAM CC Cells Rx

180) OAM FERF Cells Tx

181) OAM RTD Cells Tx

182) OAM RA Cells Tx

183) OAM Invalid Supv Packets Rx

184) OAM CC Cells Tx




This Command: cnftrkstats 11




Example (T1/24 Trunk on IGX)

cnftrkstats 8

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 10:12 GMT




Line Statistic Types




1) Bipolar Violations 18) Voice Packets Transmitted

3) Out of Frames 19) TS Packets Transmitted

4) Losses of Signal 20) NTS Packets Transmitted

5) Frames Bit Errors 21) CC Packets Transmitted

6) CRC Errors 22) BDA Packets Transmitted

9) Packet Out of Frames 23) BDB Packets Transmitted

10) Packet CRC Errors 24) Total Packets Transmitted

12) Tx Voice Pkts Dropped 25) BDA CLP Packets Dropped

13) Tx TS Packets Dropped 26) BDB CLP Packets Dropped

14) Tx NTS Packets Dropped 27) BDA EFCN Pkts Transmitted

15) Tx CC Packets Dropped 28) BDB EFCN Pkts Transmitted

16) Tx BDA Packets Dropped 149) Bdata A CLP Packets Tx to Line

17) Tx BDB Packets Dropped 150) Bdata B CLP Packets Tx to Line




This Command: cnftrkstats 8





Statistic Type:

Example (UXM OC-3 Trunk on IGX)

cnftrkstats 5.1

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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 10:20 GMT




Virtual Interface Statistic Types




1) QBIN: Voice Cells Tx to line 14) QBIN: Tx BData A Cells Discarded

2) QBIN: TimeStamped Cells Tx to ln 15) QBIN: Tx BData B Cells Discarded

3) QBIN: NTS Cells Tx to line 16) QBIN: Tx CBR Cells Discarded

4) QBIN: Hi-Pri Cells Tx to line 17) QBIN: Tx ABR Cells Discarded

5) QBIN: BData A Cells Tx to line 18) QBIN: Tx nrt-VBR Cells Discarded

6) QBIN: BData B Cells Tx to line 19) QBIN: Tx NTS Cells Received

7) QBIN: Tx CBR Cells Served 20) QBIN: Tx Hi-Pri Cells Received

8) QBIN: Tx nrt-VBR Cells Served 21) QBIN: Tx Voice Cells Received

9) QBIN: Tx ABR Cells Served 22) QBIN: Tx TS Cells Received

10) QBIN: Tx NTS Cells Discarded 23) QBIN: Tx BData A Cells Received

11) QBIN: Tx Hi-Pri Cells Discarded 24) QBIN: Tx BData B Cells Received

12) QBIN: Tx Voice Cells Discarded 25) QBIN: Tx CBR Cells Received

13) QBIN: Tx TS Cells Discarded 26) QBIN: Tx ABR Cells Received




This Command: cnftrkstats 5.1




Continue? y




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

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 10:21 GMT




Virtual Interface Statistic Types




27) QBIN: Tx nrt-VBR Cells Received 40) CGW: Packets Rx From Network

28) VI: Cells rcvd w/CLP=1 41) CGW: Cells Tx to Line

29) VI: OAM cells received 42) CGW: NIW Frms Relayed to Line

30) VI: Cells tx w/CLP=1 43) CGW: SIW Frms Relayed to Line

31) VI: Cells received w/CLP=0 44) CGW: Aborted Frames Tx to Line

32) VI: Cells discarded w/CLP=0 45) CGW: Dscd Pkts

33) VI: Cells discarded w/CLP=1 46) CGW: 0-Length Frms Rx from Network

34) VI: Cells transmitted w/CLP=0 47) CGW: Bd CRC16 Frms Rx from Network

35) VI: OAM cells transmitted 48) CGW: Bd Lngth Frms Rx from Network

36) VI: RM cells received 49) CGW: OAM RTD Cells Tx

37) VI: RM cells transmitted 54) CGW: Packets Tx to Network

38) VI: Cells transmitted 55) CGW: Cells Rx from Line

39) VI: Cells received 56) CGW: NIW Frms Relayed from Line




This Command: cnftrkstats 5.1




Continue? y




------------------------------------SCREEN 3-----------------------------------

sw180 TN Cisco IGX 8420 9.3.p7 Dec. 14 2000 10:22 GMT




Virtual Interface Statistic Types




57) CGW: SIW Frms Relayed from Line 78) QBIN: Tx Q11 Cells Received

58) CGW: Abrt Frms 79) QBIN: Tx Q12 Cells Served

59) CGW: Dscd Cells 80) QBIN: Tx Q12 Cells Discarded

60) CGW: 0-Lngth Frms Rx from Line 81) QBIN: Tx Q12 Cells Received

61) CGW: Bd CRC32 Frms Rx from Line 82) QBIN: Tx Q13 Cells Served

62) CGW: Bd Lngth Frms Rx from Line 83) QBIN: Tx Q13 Cells Discarded

63) CGW: OAM RTD Cells Rx 84) QBIN: Tx Q13 Cells Received

64) CGW: OAM Invalid OAM Cells Rx 85) QBIN: Tx Q14 Cells Served

73) QBIN: Tx Q10 Cells Served 86) QBIN: Tx Q14 Cells Discarded

74) QBIN: Tx Q10 Cells Discarded 87) QBIN: Tx Q14 Cells Received

75) QBIN: Tx Q10 Cells Received 88) QBIN: Tx Q15 Cells Served

76) QBIN: Tx Q11 Cells Served 89) QBIN: Tx Q15 Cells Discarded

77) QBIN: Tx Q11 Cells Discarded 90) QBIN: Tx Q15 Cells Received




This Command: cnftrkstats 5.1




Statistic Type:

Example (BXM OC-12 Trunk on BPX)

cnftrkstats 11.2

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

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 10:48 PST




Virtual Interface Statistic Types




7) Tx Voice Cells Served 32) Tx BData A Cells Discarded

8) Tx TS Cells Served 33) Tx BData B Cells Discarded

9) Tx NTS Cells Served 34) Tx CBR Cells Discarded

10) Tx Hi-Pri Cells Served 35) Tx ABR Cells Discarded

11) Tx BData A Cells Served 36) Tx VBR Cells Discarded

12) Tx BData B Cells Served 37) Egress NTS Cells Rx

19) Tx CBR Cells Served 38) Egress Hi-Pri Cells Rx

20) Tx VBR Cells Served 39) Egress Voice Cells Rx

21) Tx ABR Cells Served 40) Egress TS Cells Rx

28) Tx NTS Cells Discarded 41) Egress BData A Cells Rx

29) Tx Hi-Pri Cells Discarded 42) Egress BData B Cells Rx

30) Tx Voice Cells Discarded 43) Egress CBR Cells Rx

31) Tx TS Cells Discarded 44) Egress ABR Cells Rx




This Command: cnftrkstats 11.2




Continue? y




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

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 10:49 PST




Virtual Interface Statistic Types




45) Egress VBR Cells Rx 58) Tx Q10 Cells Served

46) Total Cells Tx from port 59) Tx Q10 Cells Discarded

47) Cells RX with CLP0 60) Egress Q10 Cells Rx

48) Cells Rx with CLP1 61) Tx Q11 Cells Served

49) Cells RX Discard with CLP0 62) Tx Q11 Cells Discarded

50) Cells RX Discard with CLP1 63) Egress Q11 Cells Rx

51) Cells TX with CLP0 64) Tx Q12 Cells Served

52) Cells TX with CLP1 65) Tx Q12 Cells Discarded

53) BXM: Total Cells RX 66) Egress Q12 Cells Rx

54) Ingress OAM Cell Count 67) Tx Q13 Cells Served

55) Egress OAM Cell Count 68) Tx Q13 Cells Discarded

56) Ingress RM cell count 69) Egress Q13 Cells Rx

57) Egress RM cell count 70) Tx Q14 Cells Served




This Command: cnftrkstats 11.2




Continue? y




------------------------------------SCREEN 3-----------------------------------

sw167 TN Cisco BPX 8620 9.3.2R Dec. 14 2000 10:49 PST




Virtual Interface Statistic Types




71) Tx Q14 Cells Discarded

72) Egress Q14 Cells Rx

73) Tx Q15 Cells Served

74) Tx Q15 Cells Discarded

75) Egress Q15 Cells Rx




This Command: cnftrkstats 11.2




Statistic Type:

cnftstparm (configure card test parameters)

Sets parameters for the internal diagnostic self-tests that you can perform for each card type in the node.

Upon receiving this command, the system displays a two-page screen illustrating each of the various card types equipped in the node along with their self-test parameters.

Each card has two tests run on standby cards:

•Diagnostic self-test
The self-test affects the normal operation of the card.

•Background test
The background test can execute while the card is carrying traffic.

Only background tests are executed on active cards.

Here are the configurable test parameters for each card type:

•Frequency for Test Execution (sec)

•Enable/Disable Self-Test (e or d)

•Self-Test Failure Increment

•Self-Test Failure Threshold

•Time-out For Self Test (sec)

•Enable/Disable Background Test (e or d)

•Background Test Failure Increment

•Background Test Failure Threshold

Universal Router Module

With Release 9.3.20, the IGX 8400 supports the Universal Router Module (URM). The URM provides IOS-based voice support and basic routing functions. The URM is a combination of a URM front card and a 2FE2V back card. The URM hardware consists of an embedded UXM that provides the ATM interface to the IGX network and an embedded IOS-based router. The embedded UXM is based on UXM-E hardware. It is logically a one-port UXM without physical interfaces and provides functionality similar to the UXM/UXM-E modules in the IGX.

The URM supports card self-test and background test. Use the cnftstparm command to enable, disable, or configure the self-test and background test on the URM. The tests apply only to the embedded UXM side of the card.

Syntax

cnftstparm <tp> <freq> <s_e> <s_inc> <s_thr> <s_to> <b_e> <b_inc> <b_thr>

Parameters

Parameter	Description
<tp>	Specifies the card type.
<freq>	Specifies the time between the completion of one test and the start of the next (in seconds; default is card-dependent). Range: 1 - 65535 seconds Default for BCC card: 1600 seconds Recommended value for the BCC card: 1600 seconds
<s_e>	Enables/disables the card self-test. E to enable; D to disable.
<s_inc>	Specifies the threshold counter increment for self-test failures. Counter for each card-type: each failure increments. Default:100
<s_thr>	Specifies the failure threshold for self-tests. Default: 300
<s_to>	Specifies time to wait for a self-test response (in seconds). How long to wait for a response depends on the card. The recommended value for the self-test time-out value on the BCC card is 800 seconds. The value on the standby controller card will be maintained even if the active timeout value is less than 800, which prevents the self-test timeout value from changing during a switchover (after a switchcc command is run). For example, if you change the self-test time-out value to 900 on the standby controller card, and then do a switchcc, the self-test time-out value on the new active controller card will remain 900.
<b_e>	Enables/disables the card background test. E to enable; D to disable. Available tests depend on the card; some are not enabled.
<b_inc>	Specifies the threshold counter increment for background test failures.
<b_thr>	Specifies the failure threshold for background tests.

Attributes

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

Related Commands

cnfdiagparm, dspcderrs, prtcderrs, tststats

Example (BPX)

Here is the first page of the cnftstparm display for a BPX node.

sw45 TN SuperUser BPX 15 9.3 Apr. 13 2000 16:04 PDT

Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -

Type Freq Enable Inc Thresh Timeout Enable Inc Thresh

---- ----- -------- ------- ------- ------- -------- ------- -------

BCC 1600 Enabled 100 300 800 N/A 100 300

ASM 300 Disabled 100 300 60 N/A 100 300

BNI-T3 300 Enabled 100 300 150 N/A 100 300

BNI-E3 300 Enabled 100 300 150 N/A 100 300

ASI-E3 900 Enabled 100 300 800 Enabled 100 300

ASI-T3 900 Enabled 100 300 800 Enabled 100 300

ASI-155 900 Enabled 100 300 800 Enabled 100 300

BNI-155 300 Enabled 100 300 150 N/A 100 300

BXM 2000 Disabled 100 300 1800 Enabled 100 300




Last Command: cnftstparm

Next Command:

Example (IGX with a URM)

Here is the cnftstparm display for an IGX node and the configuration of a Universal Router Module (URM).

sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:23 GMT




Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -

Type Freq Enable Inc Thresh Timeout Enable Inc Thresh

---- ----- -------- ------- ------- ------- -------- ------- -------

PSM 300 Enabled 100 300 31 N/A 100 300

HDM 300 Enabled 100 300 80 Enabled 100 300

LDM 300 Enabled 100 300 80 Enabled 100 300

NTM 300 Enabled 100 300 31 N/A 100 300

FRM 300 Enabled 100 300 80 Enabled 100 300

MT3 300 Enabled 100 300 50 N/A 100 300

CVM 300 Enabled 100 300 300 N/A 100 300

NPM 180 Enabled 100 300 120 N/A 100 300

ARM 300 Enabled 100 300 60 N/A 100 300

BTM 300 Enabled 100 300 120 N/A 100 300

BTM 300 Enabled 100 300 80 Disabled 100 300

UFM 300 Enabled 100 300 80 Enabled 100 300

This Command:cnftstparm




Continue? y




--------- Screen 2 ----------




sw190 TRM Cisco IGX 8420 9.3.2l Oct. 10 2000 04:24 GMT




Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -

Type Freq Enable Inc Thresh Timeout Enable Inc Thresh

---- ----- -------- ------- ------- ------- -------- ------- -------

UFMU 300 Enabled 100 300 80 Enabled 100 300

ALM 300 Enabled 100 300 120 N/A 100 300

UVM 300 Disabled 100 300 60 N/A 100 300

UXM 300 Enabled 100 300 800 Enabled 100 300

URM 300 Enabled 100 300 800 Enabled 100 300




Last Command:cnftstparm URM 300 E 100 300 800 E 100 300




Enter the card type at the prompt to begin modifying the test parameter.

cnfuiparm (configure user interface parameters)

Sets control terminal user interface parameters. Use cnfuiparm to set user interface parameters for the control terminal on the local node.

It may be necessary to change these parameters in special circumstances, such as when you need to observe a screen for a long period of time or when modem password protection makes logging in difficult.

Syntax

cnfuiparm <parameter number> <value>

Parameters

Parameter	Description
<parameter number>	Specifies the index number of the parameter to set.
<value>	Specifies the new parameter value to enter.

Parameter Values

No.	Parameter	Description	Default*
1	Logout Time	Idle time before a local user is logged out (0=never).	20 minutes
2	VT Logout Time	Idle time before a virtual terminal user is logged out.	4 minutes
3	Prompt Time	Idle time before a parameter prompt times out.	2 minutes
4	Command Time	Idle time before a continuous command times out.	3 minutes
5	UID Privilege Level	Privilege level of User ID allowed to use control terminal. The default is 6, the lowest user level.	6
6	Input Char Echo	If enabled, characters are echoed as you type them.	enabled
7	Screen Update Time	Time between screen updates.	2 seconds

Attributes

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

Related Commands

cnfnodeparm, dsptsmap

Example (IGX)

cnfuiparm

sw197 TN SuperUser IGX 8420 9.3 Apr. 13 2000 04:01 GMT

1. Logout Time ........... 999 minutes

2. VT Logout Time ........ 4 minutes

3. Prompt Time ........... 60 seconds

4. Command Time .......... 3 minutes

5. UID Privilege Level ... 6

6. Input Character Echo .. Enabled

7. Screen Update Time .... 10 seconds




This Command: cnfuiparm

Enter parameter index:

cnfuvmchparm (configure channel parameters on a UVM)

Configures default parameters for a channel or range of channels on a UVM. The parameters are:

•Voice codec unit (VCU) level

•PCM interface unit (PIU) level

•VAD threshold

•Modem threshold

Syntax

cnfuvmchparm <channel> <value>

Parameters

Parameter	Description
<channel>	Specifies the channel or range of channels.
<value>	VCU is the Voice codec unit. The value for this parameter is a noise level placed in a voice packet that is added in case a voice packet is dropped. The value you can enter is a multiplier for the base noise level of -10 dB. Range: 1-15 (multiplied by -10 dB). For example, if you enter 6, the level of noise placed in a replacement packet is -60 dB. PIU is the PCM interface unit. The PIU performs a resampling and injects noise in case of lost packets. Range: 1-15 (which is a multiplier for -10 dB). For example, if you enter 6, the level of noise placed in a replacement packet is -60 dB. VAD is the Voice Activity Detection threshold. If the decibel level falls below the specified limit, no packets are transmitted. Range: 0-65535 and is a multiplier of -1 dB, but typical values are around 30-40. Modem threshold is a threshold for modem tone detection. Below this threshold, the tone is ignored (or "not detected"). Range: 0-255 and is a multiplier of -1 dB, but typical values are around 30-40. The other values appear as numbered columns. These are placeholders reserved for future development.

Attributes

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

Example

Configure the parameters for channels 1-23 on port 1 of the UVM in slot 7.

cnfuvmchparm 7.1.1

sw109 VT SuperUser IGX 8420 9.3 Apr. 13 2000 17:25 PST

From Parameter:

VCU PIU VAD mdm

7.1.1 lvl lvl thld thld 5 6 7 8 9 10 11

7.1.1-23 6 6 40 40 0 0 0 0 0 0 0

7.2.1-23 6 6 40 40 0 0 0 0 0 0 0






This Command: cnfuvmchparm 7.1.





Enter VCU Noise Level/-10dB [0-15]:

cnfvchparm (configure voice channel parameter)

Modifies CVM or CVM voice channel parameters for:

•Voice Activity Detection (VAD)

•Background noise injection

•VF channel loss

•Echo suppression

•Modem detection

Different versions of firmware for the CVM present different ways of specifying the level of background noise you can select to cover awkward periods of silence at the ends of voice connections. For cards with Model A firmware, you specify the actual level in dBm (deciBels) or dBrnC0. For Model A cards, you can specify the noise levels with a granularity of 0.1 dBm or dBrnC0. For cards with Model B firmware, you enter a number that maps to a noise level.

After you enter cnfvchparm, the system displays "Enter channel(s)." After you enter the parameters, the system requests confirmation by displaying "Reconfigure active CDP channels? (y/n)."

Without the cnfvchparm command, the other ways to reconfigure channels are

•By switching cards

•By deleting then re-adding connections

Syntax

cnfvchparm <channel> <parameters>

Parameters

Parameter	Description
<channel>	Specifies the voice channel numbers to configure.
<parameters>	Specifies values for the voice parameters.

VF Channel Parameters

Parameter	Description	Default
Sample delay for VAD connections	Adds processing to speech information to prevent front-end clipping due to speech detector latency. One increment is 125 micro seconds. Here are some sample delay values: 01 ------- 0.125 msec. 50 ------- 10 msec. A8 ------- 21 msec.	A8 (H)
Sample delay for non-VAD connections	Same for non-VAD circuits.	01 (H)
Background Noise	Sets the level of background noise the far-end card adds to the connection while it receives no voice packets. For Model A firmware, specify levels in actual decibels in 0.1 dB increments. Injected noise levels for Model B firmware: 00 -------- Dynamically set noise level to match the noise detected at the other end. Requires Model B firmware on the CDP or CVM. 0 --------- 0 dBrnC0 or -90 dBm 1 --------- 18 dBrnC0 or -70 dBm 2 --------- 21 dBrnC0 or -67 dBm 3 --------- 23 dBrnC0 or -65 dBm 4 --------- 25 dBrnC0 or -63 dBm 5 --------- 27 dBrnC0 or -61 dBm 6 --------- 30 dBrnC0 or -58 dBm 7 --------- 49 dBrnC0 or -39 dBm	2 (H)
High Pass Filter mode	Enables/disables high-pass filter to assist in VAD and modem detect.	enabled
Floating Priority mode	When enabled, sets higher priority for modem detection on "c" and "v" channels. Effectively changes the trunk queue for the channel.	enabled
V.25 modem detect mode	Enables/disables V.25 modem-detect mode. The default is enabled with "detect-64K," which specifies that a 2100 Hz tone indicates the presence of V.25-type modem. The options with V.25 modem detect are "disable," "32" for 32K upgrade, and "64" for 64K upgrade. Enter "32" for fax transmission at 32 Kbps FAX Optimized ADPCM. Use the default "64" for fax transmission at 64 Kbps PCM.	enabled
32K	Auto-upgrade line to 32 Kbps ADPCM when a 32K modem is detected.	disabled
64K	Automatically upgrade line to 64 Kbps clear channel PCM when a high-speed modem is detected.	enabled

Attributes

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

Related Commands

cnfcvmparm, dspchan

Example (Model A)

The screen display illustrates cnfvchparm applied to a Model A CDP. The display for Model A cards shows the decibel level of the injected noise.

sw110 TN SuperUser IGX 8420 9.3 Apr. 13 2000 17:43 PDT




CDP Models All None All

UVM Models All None All

Sample Delay Bkgnd Echo Suppression V.25 Xmit

From 14.1 VAD Non-VAD Noise HPF Float Function Loss Detect Delay

14.1-15 A8 01 67 ON ON ON ON 64K 5

14.17-24 A8 01 67 ON ON ON ON 64K 5







This Command: cnfvchparm 14.1-6 A8 1 67 e e e e





V.25 Modem detect, 'd' - disable, '32' - 32K upgrade, '64' - 64K upgrade:

Example (Model B)

The screen displays in the example illustrates cnfvchparm applied to a Model B CDP. The display for the Model B shows the number that corresponds to a decibel (or dBrnC0) level of background noise.

sw83 TN SuperUser IGX 8420 9.3 Apr. 13 2000 17:01 PST

CDP Models All None All

Sample Delay Bkgnd Echo Suppression V.25 Xmit

From 11.1 VAD Non-VAD Noise HPF Float Function Loss Detect Delay

11.1-15 A8 01 2 ON ON ON ON ON 5

11.17-31 A8 01 2 ON ON ON ON ON 5







This Command: cnfvchparm





Next Command:

cnfvchtp (configure interface type for voice channels)

Configures an interface signaling type for a voice channel. Most standard signaling types are maintained by the node, but you may build a custom template.

If you enter the cnfvchtp command without a specific interface number, the system will present you with a list of valid interface types and their associated on-hook and conditioning information.

To assign an interface type (and its associated on-hook and conditioning information) to the channel or set of channels, enter the number of the desired interface type. Type "1" requires user configuration. Interface type is ignored for "d" type connections.

Syntax

cnfvchtp <channel> <type> [<A> <B> <C> <D> <cond_code>]

Parameters

Parameter	Description
channel	Specifies the channel or range of channels for the interface type configuration. For a CVM or CDP, the format is slot.channel[-channel]. For a UVM, the format for channel is slot.line.channel[-channel].
interface type	Specifies the number of the interface type to assign to the channel or range of channels. These types are listed in the table "Interface Types" below. The on-hook column has A-bits on the left and B-bits on the right. The conditioning column has different types of conditioning specified. If you designate interface type number 1 to indicate a user-configured interface type, the system prompts for: on-hook A, on-hook B, on-hook C (if applicable), on-hook D (if applicable), conditioning A, conditioning B, conditioning C (if applicable), conditioning D (if applicable), and conditioning template information. When the IGX receives A-bit, B-bit, C-bit, and D-bits corresponding to the on-hook values, that channel is known to be on-hook. If the A-bit, B-bit, C-bit, and D-bits do not correspond to the on-hook values, that channel is known be off-hook
on-hook A	A-bit value for the on-hook state of a channel or set of channels.
on-hook B	B-bit value for the on-hook state of a channel or set of channels.
on-hook C	C-bit value for the on-hook state of a channel or set of channels.
on-hook D	D-bit value for the on-hook state of a channel or set of channels. Possible values: 1 + high 0 = low X= don't care ? = don't know - = not used
conditioning template	One of many predefined or user-defined conditioning templates in the range of 00000000 to 11111111. (See dspcond and cnfcond commands.) Each interface type, except for option 1, has a predetermined conditioning template associated with it. These represent the A-bit, B-bit, C-bit, D-bit values as well as the substitute PCM voice sample sent to the attached equipment in case the voice connection fails for any reason.

Interface Types

Interface Number	Interface Type	On-hook	Conditioning
1	User Config
2	Unconfig	? ? - -	a
3	No Sig	? ? ? ?	a
4	Force Sig	? ? - -	a
5	2W E&M	0 X - -	a
6	4W E&M	0 X - -	a
7	FXO	11 - -	b
8	FXS G/S	01 - -	c
9	FXS L/S	0 X - -	d
10	DPO	0 X - -	a
11	DPT	0 X - -	a
12	RPO	0 X - -	a
13	RPT	0 X - -	a
14	SDPO	0 X - -	a
15	DX	0 X - -	a
16	ETO	? ? - -	e
17	PLAR	? ? - -	d
18	PLR	0 X - -	a
19	RD	? ? - -	a
20	R1 (SOCOTEL)	0 - - -	e
21	SSDC5A	1 1 0 1	f
22	R2 (backward)	1 1 - -	e
23	R2 (forward)	1 0 - -	d

Attributes

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

Related Commands

cnfchgn, cnfchdl, dspchcnf

Example

Configure the interface type for channel 13.1-24.

cnfvchtp 13.1-24

sw150 TN Cisco IGX 8420 9.3.2T Dec. 19 2000 23:48 PST




No Intf. Type OnHk Cond No Intf. Type OnHk Cond

1 User Config 13 RPT 0 X - - a

2 Unconfig ? ? - - a 14 SDPO 0 X - - a

3 No Sig ? ? ? ? a 15 DX 0 X - - a

4 Force Sig ? ? - - a 16 ETO ? ? - - e

5 2W E&M 0 X - - a 17 PLAR ? ? - - d

6 4W E&M 0 X - - a 18 PLR 0 X - - a

7 FXO 1 1 - - b 19 RD ? ? - - a

8 FXS G/S 0 1 - - c 20 R1 (SOCOTEL) 0 - - - e

9 FXS L/S 0 X - - d 21 SSDC5A 1 1 0 1 f

10 DPO 0 X - - a 22 R2 (backward) 1 1 - - e

11 DPT 0 X - - a 23 R2 (forward) 1 0 - - d

12 RPO 0 X - - a






Last Command: cnfvchtp 13.1

Example

Configure a user configurable interface type for channel 15.1 to 15.8. The channel configuration screen shows that channels 5-8 of circuit line 15 now has a user-configured interface type with an A-bit on-hook value of X, a B-bit on-hook value of X, an C-bit on-hook value of not used, D-bit on-hook value of not used, and conditioning template b.

cnfvchtp 15.5-8 1 X X - - b

cnfvsiif (assign a service class template to an interface)

Assign a service class templates (SCT) to an interface.

Use the dspvsiif command to display a service class template assigned to an interface, as well as display a summary of the resources allocated to the VSI partition on a given interface.

A default service template is assigned to a logical interface (VI) when you up the interface by using upport and uptrk.

For example:

•uptrk 1.1

•uptrk 1.1.1 (virtual trunk)

•upln 1.1 and upport 1.1

This default template (MPLS1) has the identifier of 1. You can change the service template from service template 1 to another service template by using the cnfvsiif command. The dspvsiif command allows you to display the template associated with the interface. For example:

•cnfvsiif 1.1 2

•cnfvsiif 1.1.1 2

•dspvsiif 1.1

•dspvsiif 1.1.1

---

Note Only MPLS1 (template 1) may be used with IGX.

---

Syntax

cnfvsiif <slot.port.vtrk> <tmplt_id>

Parameters

Parameter	Description
<slot.port.vtrk>	Specifies the card slot and port number and virtual trunk.
<tmplt_id>	Specifies the ID number of the service class template to be assigned.

Attributes

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

Related Commands

cnfrsrc, dsprsrc, cnfqbin, dspqbin

Example (IGX)

Assign service class template 2 to port interface 3.1. You will see a warning if partition 3 is active.

cnfvsiif 3.1 1

bently TN Cisco IGX 8430 9.3.10 Aug. 3 2000 13:49 PST




Port: 3.1




service class template ID: 2





State MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW

Partition 1: D

Partition 2: D

Partition 3: E 100 200 100 200 10000 10000






Last Command: cnfvsiif 3.1 2




Interface has active VSI partition(s): changing SCT will be service affecting

Next Command:

Example (BPX)

Assign service class template 2 to port interface 4.1.

cnfvsiif 4.1 2

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 17:58 GMT




Port: 4.1




service class template ID: 2




VSI Partitions :

channels bw vpi

Part E/D min max min max start end ilmi

1 D 0 0 0 0 0 0 D

2 D 0 0 0 0 0 0 D

3 D 0 0 0 0 0 0 D





Last Command: cnfvsiif 4.1 2





Next Command:

cnfvsipart (configure VSI ILMI on VSI partition)

Enable or disable VSI ILMI support.

You may enable VSI ILMI on only one VSI partition on the interface.

Starting with Release 9.3, this command is used only on a trunk interface. To enable VSI ILMI on the port interface, use the cnfport command to enable ILMI and Protocol By Card.

Syntax

cnfvsipart <slot.port.[vtrk]> <part_id> <enable_option>

Parameters

Parameter	Description
<slot.port.[vtrk]>	Slot, port (and virtual port if applicable) of the interface.
<part_id>	Partition ID corresponding to the VSI partition.
<enable_option>	This parameter indicates whether to enable or disable VSI ILMI functionality. Valid values: •Y enables the VSI ILMI session. •N disables the VSI ILMI session.

Attributes

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

Related Commands

cnfrsrc, dspvsipartcnf, cnfport, cnftrk

Example

Enable VSI ILMI on BXM trunk 4.2, VSI partition 1.

cnfvsipart 4.2 1 Y

sw143 TRM Cisco BPX 8620 9.3.10 Aug. 2 2000 18:20 GMT





Trunk: 4.2 Partn: 1 ILMI: E LCN: 543 Topo: BPX NW IP





Last Command: cnfvsipart 4.2 1 Y





Next Command:

cnfxmtsig (configure transmit signaling)

Allows the node to pass A, B, C, and D channel signaling bits through unchanged, or to invert, or hold them at a given value for a CDP or CVM line. It affects signaling bits in the transmit direction (to the PBX or channel bank) in an E1 system. The command configures the transmit signaling. Channel signaling bit options are T (transparent), 0, 1, or I (invert). If signaling is set to "not used" (-) by cnfchtp, the following is maintained: A=1, B=1, C=0, D=1.

Syntax

cnfxmtsig <channel(s)> <[A/]Conv> <[B/]Conv> <[C/]Conv> <[D/]Conv>

Parameters

Parameter	Description
channel	Specifies the channel or range of channels to receive signaling.
A/	Specifies the conversion applied to the A-bit. <Conv> can be one of: 1 = bit is asserted. 0 = bit is inhibited. T = bit is passed transparently. I = bit is inverted.
B/	Specifies the conversion applied to the B-bit.
C/	Specifies the conversion applied to the C-bit.
D/	Specifies the conversion applies to the D-bit.

Attributes

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

Related Commands

cnfrcvsig, dspsigqual

Example

Configure the transmit signaling for channel 8.1 to inverted for the A-bit, inhibited for the B-bit, asserted for the C-bit and transparent for the D-bit.

cnfxmtsig 8.1 a/I b/0 c/1 d/t

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

signaling Qualifiers

From 8.1 TXA-bit TXB-bit TXC-bit TXD-bit RXA-bit RXB-bit RXC-bit RXD-bit

8.1 1 0 1 T T 0 I I

8.2-31 T T T T T T T T




Last Command: cnfxmtsig 8.1 a/I b/O c/1 d/t

Next Command:




compactrsrc (compact resources)

This command is used to compact the Automatic Routing Management CBAs on a particular slot. It deprograms all the connections (cross-connects) terminated on that card and reprograms them with new CBA values. You can use this command if you need to free up some CBAs to use them for VSI. The command affects all the connections that have been programmed.

Syntax

compactrsrc ar

Parameters

Parameter	Description
ar	Select Automatic Routing Management (AutoRoute)

Attributes

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

Example

Compacts CBA resources used by Automatic Routing Management connections.

compactrsrc ar

sw100 TRM StrataCom IGX 8420 9.3.10   July 16 2000   12:18 PST





WARNING - ALL AUTO ROUTE CONNECTIONS WILL BE RE-PROGRAMMED.




THIS WILL CAUSE DROPPING OF CELLS IN ALL PVCs.






This Command: compactrsrc ar




OK to continue (y/n)?

cpyict (copy interface control templates)

Copies all control template information associated with a given channel: the active template information, the conditioned template information, and the looped template information for near and far ends.

Once copied, you can edit the control template information by using the cnfict command. See the cnfict command for more information about the interface control templates.

On an IGX node, the applicable front cards are the LDM, HDM, FRM, and CVM (for data).

Syntax

cpyict <source_port> <destination_port>

Parameters

Parameter	Description
<source_port>	Specifies the data channel or Frame Relay port of the interface control template information to copy.
<destination_port>	Specifies the data channel or Frame Relay port that will receive the copied control template information.

Attributes

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

Related Commands

cnfict, dspict

Example

Copy the interface control template for data channel 25.1 to channel 25.2.

cpyict 25.1 25.2

beta TRM YourID:1 IGX 8430 9.3 Apr. 13 2000 17:40 MST

Data Channel: 25.2

Interface: EIA/TIA 232 DCE

Clocking: Normal

Interface Control Template for Connection while ACTIVE

Lead Output Value Lead Output Value

RI OFF DSR ON

CTS ON SRxD ON

DCR OFF DCD ON

SCTS ON SDCD ON

SQ ON




Last Command: cpyict 25.1 25.2

Next Command:

cpytrkict (copy trunk interface control template)

Copies the interface control template of one trunk to another trunk. Once copied, the control information can be edited by using the cnftrkict command. See the cnftrkict description for more information on configuring the trunk interface control templates.

Syntax

cpytrkict <source_trunk> <destination_trunk>

Parameters

Parameter	Description
<source_trunk>	Specifies the trunk number of the interface control template information to be copied.
<destination_trunk>	Specifies the trunk number to which the interface control template information is copied.

Attributes

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

Related Commands

cnftrkict, dsptrkict

Example

Copy the interface control template for trunk 9 to trunk 11.

cpytrkict 9 11

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

Packet Line: 9

Interface: X.21 DTE




Interface Control Template for Trunk Line




Lead Output Value Lead Output Value

C/DTR ON





Last Command: cpytrkict 9 11




Enter destination line number: