Table Of Contents
cnfabr
Configure ABR—PXM1E
In general, the cnfabr command configures the VS/VD-specific parameters for an existing ABR connection. The connection must be of service type ABR (in the addcon command, service type=10).
Note
In the current release, the PXM1E UNI/NNI back card does not support VS/VD. The only ABR parameters that the PXM1E supports are MCR and PCR.
Note
Syntax
cnfabr <ifNum> <vpi <vci> -icr <Initial cell rate>] -adtf <ACR decr. factor>] -rdf <Rate decr. factor>] -rif <Rate incr. factor>] -nrm <Cells per fwd RM>] -trm <Time between fwd RMs>] -cdf <cutoff decrease factor>] -frtt <fix round trip delay>] -tbe <transient buffer exposure>] -intvsvd <internal vsvd config>] -extvsvd <external vsvd config>]
Syntax Description
Related Commands
addcon, cnfabrtparmdft, dspabrtparmdft, cnfintfvsvd
Attributes
cnfabrtparmdft
Configure ABR Traffic Parameter Defaults—PXM45, PXM1E
The cnfabrtparmdft command lets you configure default, ABR-specific parameters for all ABR SPVCs on a PNNI port. These parameters apply to SPVCs only.
Note
When you add an ABR connection, the controller provides the default ABR traffic parameters before the connection is committed. The default ABR traffic parameters are used in the SETUP message at the source when an SPVC with ABR service is set up. (Note also that you can change VS/VD-specific parameters for an individual ABR connection by using the cnfabr command on the AXSM-E.)
Syntax
cnfabrtparmdft <portid> [-rif RIF-value] [-rdf RDF-value] [-tbe TBE-value] [-nrm NRM-value] [-trm TRM-value] [-adtf ADTF-value] [-cdf CDF-value] [-fsd FSD-value]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-rif
Keyword that specifies the Rate Increase Factor (RIF). This is the factor by which to increase the Allowed Cell Rate (ACR). RIF is a power of 2 in the range 1/32768 to 1.
Default: 7
-rdf
Keyword that specifies the Rate Decrease Factor (RDF). This is the factor by which to decrease the Allowed Cell Rate (ACR). RDF is a power of 2 in the range 1/32768 to 1.
Default: 4
-tbe
Keyword that specifies the Transient Buffer Exposure (TBE). This is the negotiated number of cells that the network would like to limit the source to sending during startup periods, before the first RM-cell returns. The range is 0-16,777,215 cells.
Default: 1048320
-nrm
Keyword that specifies the maximum number of cells that the source can send for each forward RM-cell. Nrm is a power of 2 in the range 2-256.
Default: 5
-trm
Keyword that specifies the maximum number of milliseconds for one RM-cell to travel from source to endpoint. The range is 100 x 2-7 to 100 x 20 milliseconds.
Default: 8
-adtf
Keyword that specifies the ACR Decrease Time Factor (ADTF). This is the time permitted to decrease the cell rate from the RM-cell rate to the Allowed Cell Rate (ACR) for normal traffic. The range is 1 to 1023 milliseconds.
Default: 50
-cdf
Keyword that specifies the Cutoff Decrease Factor (CDF). This controls the decrease in Allowed Cell Rate (ACR) associated with Missing RM-cell count (CRM). CDF can be either or the following:
•
•
CRM limits the number of forward RM-cells that may be sent in the absence of received backward RM-cells. CRM is an integer. Its size is implementation-specific.
Default: 7
-fsd
Keyword that specifies the Fixed-source-delay.
Default: 0
Related Commands
addcon, cnfabr, dspabrtparmdft, cnfintfvsvd
Attributes
cnfaddrreg
Configure Address Registration—PXM45, PXM1E
This command lets you enable or disable ILMI address registration for a port. Before you can run cnfaddrreg, the following must have occurred:
1.
2.
The cnfaddrreg command can also enable (or disable) the address registration for backward compatibility.
The peer must support address registration table and procedure, so you must confirm that address registration is enabled on all three places.
Syntax
cnfaddrreg <portid> [{yes | no}]
Syntax Description
In addition to typing a port ID, you must also type either "yes" pr "no."
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
yes
Enable ILMI address registration on the port. The default is "yes" (enabled).
no
Disable ILMI address registration on the port.
Related Commands
None
Attributes
Example
Disable ILMI address registration on port 4:1.1:11.
Geneva.7.PXM45.a > cnfaddrreg 4:1.1:11 nocnfainihopcount
Configure AINI Hop Count—PXM45, PXM1E
The cnfainihopcount command lets you determine the maximum number of AINI links that a call can traverse. The specification applies to any call originating on the local node, and the area to which the setting applies is the entire network. With cnfainihopcount, you can:
•
•
Note
Syntax
cnfainihopcount [-hopcntgen {enable | disable}] [-maxhops <value>]
Syntax Description
Related Commands
dspainihopcount
Attributes
Example
Enable AINI hop counting and specify a maximum of 20 hops. No response appears unless an error occurs, so follow up by displaying the configuration.
8850_NY.8.PXM.a > cnfainihopcount -hopcntgen enable -maxhops 208850_NY.8.PXM.a > dspainihopcountAINI Hop Counter Generation: enableMax AINI Hops: 208850_NY.8.PXM.a >cnfalm
Configure Alarm—PXM45, PXM1E
Configures statistical alarm thresholds for a line. The configurable items for SONET and PLCP are defined in RFC 2258. The configurable items for DS3 and E3 are defined in RFC 2496. The items that constitute a configuration are:
•
•
•
•
•
•
A keyword identifies the alarm criteria. Each keyword identifies the tested layer (line, and so on), the type of threshold (errored seconds, and so on), and the test period of 15 minutes or 24 hours. For example, -lnes15 indicates the number of errored seconds on the line layer during any 15 minute period. See the Syntax Description for a list and definitions of all keywords.
Note
Syntax
Due to the variety of line types and formats for line identifiers, the information is presented as generic syntax information and details for specific line types.
The required parameters are as follows:
•
•
•
Other parameters are optional and must be preceded by the keyword that identifies the type of parameter.
Generic Syntax Description
The generic syntax is.
cnfalm <line type> <X.line> <alarm severity> <thresholds>
The meaning of the generic syntax appears in the following list. Refer to subsequent lists for the descriptions of alarm severities and thresholds for each line type.
Thresholds for SONET Section
Thresholds for SONET Line
Thresholds for SONET Path
Thresholds for DS3
Thresholds for E3
Thresholds for PLCP
Related Commands
dspalmcnf
Attributes
Example
Configure the following thresholds for triggering a major line-level alarm on line 9 in bay 2:
•
•
•
•
•
•
•
node4.7.PXM1E.a > cnfalm -sonetline 2.9 -lnsev 2 -lnes15 60 -lnes24 600 -lnses15 3 -lnses24 7 -lncv15 75 -lncv24 750 -lnuas15 10 -lnuas24 10Check the configuration by running dspalmcnf for the line number and line type in this example.
node4.7.PXM1E.a > dspalmcnf -sonetline 2.9LineNum: 2.9Line Stat Alarm Severity: No Alarm15min Threshold 24hr ThresholdLine ESs : 60 600Line SESs: 3 7Line CVs : 75 750Line UASs: 10 10cnfapsln
Configure APS Line—PXM1E
Configures the APS parameters for a line (working line). Use the cnfapsln command after you add the line. See the description for the addapsln command for a detailed explanation of adding Automatic Protection Switching (APS).
Syntax
Note
Note
cnfapsln -w <working line> -sf <SignalFaultBER> -sd <SignalDegradeBER> -wtr <Wait To Restore> -dr <direction> -rv <revertive> -proto <protocol>
Syntax Description
Related Commands
addapsln, delapsln, dspapsln, dspapslns, switchapsln, dspapsbkplane, dspbecnt
Attributes
Example
cnfapsln -w 1.1.1 -sf 3 -sd 5 -wtr 5 -dr 2 -rv 1cnfatmimagrp
Configure ATM IMA Group—PXM1E
The cnfatmimagrp command lets you enable or disable payload scrambling for an IMA group. The default is enabled.
Syntax
cnfatmimagrp -grp <group> -sps <PayloadScramble>
Syntax Description
Related Commands
dspatmimagrp
Attributes
Example
Disable payload scrambling in IMA group 2.
PXM1E.7.PXM.a > cnfatmimagrp 2.2cnfatmln
Configure ATM Line—PXM1E
The cnfatmln command lets you configure the ATM layer cell header for a line.
You must configure the ATM layer cell header for a line before you activate the line using upln or before you add a logical port to the line using addport.
Syntax
cnfatmln -ln <bay.line> -sps <PayloadScramble> -nch <cellhdr> -ncp <NullCell payload>
-hcs <hcs>Syntax Description
Related Commands
dspatmln
Attributes
Example
For line 1 disable payload scrambling and specify a null cell header.
MGX8850.7.PXM1E.a > cnfatmln -ln 2.1 -sps 2 -nch ab12ababFor line 1, enable payload scrambling and specify null cell headers.
MGX8850.1.PXM1E.a > cnfatmln -ln 2.1 -sps 1 -nch 1a1a1a1a -ncp aaFor line 1, disable payload scrambling and specify a null cell header.
MGX8850.1.9.PXM1E.a > cnfatmln -ln 2.1 -sps 2 -nch ab12ababcnfautocnf
Configure Auto Configuration—PXM45, PXM1E
The cnfautocnf command enables or disables ILMI auto configuration for a port. To use this command, the port must be added but administratively down (via dnpnnport).
With auto-configuration enabled, the ILMI slave side starts ILMI auto configuration to negotiate the ATM layer parameters with its peer while ports come up. With auto-configuration disabled, the ILMI slave does not start ATM layer parameter-negotiation while ports come up. Instead, the ILMI slave uses the local configuration parameters. The default state for auto-configuration is enabled.
Syntax
cnfautocnf <portid> [yes | no]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
yes | no
Enable of disable ILMI automatic configuration on the port by typing "yes" or "no."
Default: yes
Attributes
Examples
Enable ILMI auto-configuration on port 7:2.1:11.
Geneva.7.PXM1E.a > cnfautocnf 7:2.1:1 yescnfbert
Configure Bit Error Rate Testing—PXM45, PXM1E
The cnfbert command lets you configure, start, or stop a bit error rate test (BERT) on a legacy service module. This BERT requires a Service Resource Module (SRM-3T3/C or SRME). The SRME does not support all patterns or all loopbacks on all service module lines, so use the dspbertcap command to see the capability for a specific service module.
Note
One BERT session at a time can run in a bay. If you attempt to configure a session while one is running, the controller blocks the second test.
Note
Syntax
cnfbert -cbif <LSMNum> -pat <bertPattern> -lpbk <loopback> -sbe <singleBitErr>
-cir <dropIteration> -en <enable>Syntax Description
The mandatory parameters are -cbif <LSMNum> -pat <bertPattern> -lpbk <loopback> -en <enable>. Also, you can terminate the BERT session by either using the delbert command or using the cnfbert mandatory parameters and specifying the enable as -en 6.
Related Commands
dspbert, delbert, dspbertcap
Attributes
Example
Configure a BERT session, as follows (after using the dspbertcap command, as needed), then display the test after about a half hour by using the dspbert command:
•
•
•
•
•
•
JANUS1.7.PXM.a > dspbertcap 25.1 1Pattern List:-------------1: allZeros, 2: allOnes, 3: altOneZero,4: doubleAltOnesZeros 6: oneIn8, 8: threeIn24,18: twoE9MinusOne, 20: twoE11MinusOne 21: twoE15MinusOne,24: twoE20MinusOne, 25: twoE20MinusOneQRSS 28: twoE23MinusOneDevice to loop options supported:---------------------------------FarEnd Loopback: All listed patterns supported12: lineInband, 13: lineLoopbackESF18: smartJackInband -Supported only on SRMELocal Loopback: All listed patterns supported14: localLoopbackNo Loopback: All listed patterns supported15: noLoopbackCodeUse cnfbert and delbert cli to configure and delete bertJANUS1.7.PXM.a > cnfbert -cbif 25.1.0 -pat 1 -lpbk 14 -en 4Successfully configured.JANUS1.7.PXM.a > dspbert 1Start Date : 05/07/2002Current Date : 05/07/2002Start Time : 15:41:11Current Time : 16:15:00Physical Slot Number : 25Logical Slot Number : 25Line Number : 1 (Line test)Device To Loop : Local LoopbackBERT Pattern : All Zeroes PatternError Inject Count : 0Bit Count : 3107466159Bit Count Received : 3107466159Bit Error Count : 0Bit Error Rate (BER) : 0BERT is in sync.
cnfcbclk
Configure Cellbus Clock—PXM45, PXM1E
The cnfcbclk command lets you specify whether a Cellbus runs at the default of 21 MHz or the double-speed rate of 42 MHz. Not every Cellbus (and the card slots it supports) can receive the double-speed clock, so use the dspcbclk to see whether a particular Cellbus can run at 42 MHz. The application of dspcbclk and cnfcbclk is the clocking for the Route Processor Module (RPM). The RPM runs much more efficiently at 42 Mhz.
The backplane has 8 Cellbuses: 6 Cellbuses support 2 card slots and can support 21 MHz or 42 MHz clocking. Two of the Cellbuses (CB4 and CB8) support 6 cards slots and can receive only the 21 MHz clock. See the dspcbclk output in the Example section.
Note
Syntax
cnfcbclk <cellBus> <clockRate>
Syntax Description
cellBus
Specifies the Cellbus. Enter a string in the range CB1-CB8. The string is not case-sensitive.
clockRate
Specifies a clock rate of 21 MHz or 42 MHz. Enter either "21" or "42."
Related Commands
dspcbclk
Attributes
Example
To determine which slots can run at a higher rate, display the current Cellbus clock configuration. The display shows that all Cellbuses currently have the default speed of 21 Mhz.
pop20two.8.PXM.a > dspcbclkCellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 21 1, 2 21, 42CB2 21 3, 4 21, 42CB3 21 5, 6 21, 42CB4 21 17 - 22 21CB5 21 9, 10 21, 42CB6 21 11, 12 21, 42CB7 21 13, 14 21, 42CB8 21 25 - 30 21Configure a double-speed clock for Cellbus 5, then check the configuration.
pop20two.8.PXM.a > cnfcbclk cb5 42pop20two.8.PXM.a > dspcbclkCellBus Rate (MHz) Slots Allowable Rates (MHz)----------------------------------------------------------CB1 21 1, 2 21, 42CB2 21 3, 4 21, 42CB3 21 5, 6 21, 42CB4 21 17 - 22 21CB5 42 9, 10 21, 42CB6 21 11, 12 21, 42CB7 21 13, 14 21, 42CB8 21 25 - 30 21
cnfcdmode
Configure Card Mode—PXM1E
The cnfcdmode command lets you specify the mode of the lower-speed lines on the PXM1E UNI/NNI back card. (It does not apply to the OC3c/SDH or higher speed lines.)
Note
On the combination back card (FRU-8T3E3-4OC3), you can specify whether all lower-bandwidth lines operate as one of the following:
•
•
On the T1/E1 back card (RBBN-16-T1E1), you can specify whether all lower-bandwidth lines operate as one of the following:
•
•
Note
Syntax
cnfcdmode <mode>
Syntax Description
mode
The mode is a number in the range 1-4.
•
•
•
•
Related Commands
dsplns, dspcd, dspcds
Attributes
cnfcdstat
Configure Card Statistics—PXM1E
The cnfcdstat command lets you configure the TFTP bucket statistics for the entire UNI/NNI back card. Parts of the configuration control the bucket interval and the collection interval. These parameters affect the generation of the files that contain statistics and that are transferred to the Cisco WAN Manager (CWM) via FTP.
The card statistics level (stats level) cannot be set if a configuration exists on the lines, such as logical ports. You must set the stats level before you can add any logical ports. However, you can set the bucket interval and the collection interval after you have added logical ports.
Enabling statistics effects performance. Statistical counters use up bandwidth, which reduces the amount of bandwidth available for connections. The PXM1E provides statistical alarms to help control the amount of bandwidth used for statistics.
Statistical alarms are different than integrated alarms. An integrated alarm indicates a persistent traffic loss at either the local end, such as the LOS and LOF alarms, or at the remote end, such as the RDI alarm.
A statistical alarm indicates that a statistical counter has exceeded the threshold for alarm indication. For instance, the Severely Errored Seconds (SES) counter might exceed the corresponding 15-minute threshold. For this condition, a statistical alarm is raised, which indicates a degraded performance that is not due to persistent traffic loss.
Statistical alarms are based on fixed statistics collection intervals. There are two types of fixed statistics collection intervals:
•
•
The start of an interval is aligned to the time of day. For instance, 11:15, 11:30, 11:45, etc. At the end of the interval, the corresponding statistical alarms are cleared. An alarm is raised again if a counter exceeds the threshold during the new interval.
Types of Card Statistics
The types of card statistics that are reported, and at which levels, are shown in the following tables.
Syntax
cnfcdstat -i <bucket interval> -ci <collection interval> -sl <stats level> -ed <1 | 2>
Syntax Description
Related Commands
dspcdstatcnf
Attributes
Example
PXM1E_SJ.7.PXM.a > cnfcdstat -i ten -ci one -sl 1 -ed enablecnfcdvtdft
Configure Cell Delay Variation Tolerance Default—PXM45, PXM1E
For all connections of a particular service type on a PNNI logical port, cnfcdvtdft configures the default number of microseconds for the cell delay variation tolerance (CDVT). The direction is ingress. The new configuration applies to new incoming calls but not existing calls. You can execute cnfcdvtdft whether the port is in the provisioning state (prior to addport on the service module) or administratively up.
Syntax
cnfcdvtdft <portid> <service_category> [microseconds]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
service_category
Service type: cbr, rtvbr, nrtvbr, ubr, or abr.
micro seconds
The number of microseconds for CDVT.
Range: 0-2147483647
Default: 250,000
Related Commands
dspcdvtdft
Attributes
Examples
Specify a CDVT of 125000 microseconds for ABR connections on port 4:1.1:11. Check the results by executing dspcdvtdft for the port.
Geneva.7.PXM.a > cnfcdvtdft 4:1.1:11 abr 125000Geneva.7.PXM.a > dspcdvtdft 4:1.1:11cbr: rt-vbr: nrt-vbr: ubr: abr:CDVT: 250000 250000 250000 250000 125000Geneva.7.PXM.a >
cnfcli
Configure CLI—PXM45. PXM1E
The cnfcli command is the CLI portion of a feature that lets you modify the user privilege (or access) level of one or more commands. The other portions of the feature involve text file creation on a workstation and transferring that file to the switch. For a significant number of commands, you cannot modify the privilege. A list of these commands appears in the section, "Restrictions."
The cnfcli command converts an ASCII text file containing privilege changes to a binary file and applies it to the commands whose privilege you have changed. The ASCII file is created on a workstation by using "vi" or any other text editor. Subsequently, you FTP the file to a TEMP directory on the node.
On the active PXM, the cnfcli command can do one of the following tasks according to the parameters:
•
•
•
Note
Feature Details
The following list describes details for this feature.
•
•
•
•
•
•
•
•
•
•
–
–
–
Restrictions
This section lists the restrictions on the use of the cnfcli command.
•
•
•
•
•
The following list shows the commands whose privilege you cannot change.
ASCII File Format
You can use any text editor to create the ASCII file. The format is one command followed by the group access level name on a line, as the following indicates:
<command name><space(s)><group access level name><carriage return>
<command name><space(s)><group access level name><carriage return>
...
<command name><space(s)><group access level name><carriage return>
The requirements and characteristics of the ASCII file are as follows:
•
•
•
•
•
•
•
Activating This Feature
The steps for using this feature are as follows:
1.
2.
3.
cnfcli accesslevel install C:/TMP/filename.txtThe following events occur:
•
•
•
•
•
4.
•
•
cnfcli accesslevel display
•
File Locations
The binary file resides in a directory named F:/CLI/CNF/ after the installation finishes. If you do not create a binary file through the cnfcli command, no file resides in this directory.
Errors and Failure Conditions
This section lists possible errors, failures, and solutions.
•
•
•
•
•
•
Syntax
With a single iteration of the cnfcli command, you can either install the file with modified privilege levels or direct the switch to revert to the default privilege levels. The possible sequences of this command and its parameters are as follows:
cnfcli <accesslevel> <install> [full path file name]
cnfcli <accesslevel> <default>
Syntax Description
Related Commands
ftp, dspcli
Attributes
Example
This example consists of the following tasks:
1.
2.
3.
4.
5.
6.
7.
clicnf.txt***********************cnfsct SERVICE_GP adfjafkdcnfserialif SERVICE_GPcnfsig SERVICE_GPcnfsigdiag SERVICE_GPcnfsnmp SERVICE_GPcnfsntpcnfsntprmtsvr SERVICE_GPcnfspvcprfx SERVICE_GPcnfspvcres icnfsrmclksrc ;cnfsscop SERVICE_GPcnfstatsmgr SERVICE_GPcnfsvcoverride SERVICE_GPcnftmzn SERVICE_GPaddapsln SERVICE_GPaddchanloop SERVICE_GPaddcon SERVICE_GPaddfdr SERVICE_GPaddlmi SERVICE_GPaddlnloop SERVICE_GPaddpart SERVICE_GPaddport SERVICE_GPaddrscprtn SERVICE_GParpFlush SERVICE_GParpShow SERVICE_GPbootChange SERVICE_GPbye SERVICE_GPcc SERVICE_GP***************************FTP the file to C:/TMP, for example, then use that whole path name with the cnfcli command.
jeff.8.PXM.a > cnfcli accesslevel install C:/TMP/clicnf.txtReading input file C:/TMP/clicnf.txt...Total of 35 lines in file:- 24 commands accepted- 5 commands found not allowed- 6 commands with invalid access level name- 0 comment linesConverting input file to binary file...doneWriting binary file to disk...doneUpdating command access levels for this slot...doneSend request to slot 7 to install...doneSend request to slot 2 to install...doneSend request to slot 6 to install...doneSend request to slot 9 to install...doneSend request to slot 10 to install...donejeff.8.PXM.a > dspcli accesslevelCommand Name Current Default-----------------------------------------------------------addapsln SERVICE_GP GROUP1addlnloop SERVICE_GP GROUP1arpFlush SERVICE_GP SUPER_GParpShow SERVICE_GP ANYUSERcnfsct SERVICE_GP GROUP1cnfserialif SERVICE_GP SUPER_GPcnfsig SERVICE_GP GROUP1cnfsntprmtsvr SERVICE_GP GROUP1cnfspvcprfx SERVICE_GP SUPER_GPcnfsscop SERVICE_GP GROUP1cnfsvcoverride SERVICE_GP SUPER_GPcnftmzn SERVICE_GP SUPER_GP12 command access levels changed.jeff.8.PXM.a > cc 2(session redirected)jeff.2.AXSM.a > dspcli accesslevelCommand Name Current Default-----------------------------------------------------------addapsln SERVICE_GP GROUP1addcon SERVICE_GP GROUP1addfdr SERVICE_GP GROUP1addlmi SERVICE_GP GROUP1addlnloop SERVICE_GP GROUP1addpart SERVICE_GP GROUP1addport SERVICE_GP GROUP1addrscprtn SERVICE_GP GROUP1arpFlush SERVICE_GP SUPER_GParpShow SERVICE_GP ANYUSER10 command access levels changed.jeff.2.AXSM.a > cc 8(session redirected)jeff.8.PXM.a > cnfcli accesslevel uninstallUninstall command access levels for this slot...doneSend request to slot 7 to uninstall...doneSend request to slot 2 to uninstall...doneSend request to slot 6 to uninstall...doneSend request to slot 9 to uninstall...doneSend request to slot 10 to uninstall...donejeff.8.PXM.a > cc 2(session redirected)jeff.2.AXSM.a > dspcli accesslevelCommand Name Current Default-----------------------------------------------------------0 command access levels changed.
cnfclkparms
Configure Clock Parameters—PXM45, PXM1E
The cnfclkparms command lets you configure the signal type and cable type for E1 BITS sources. The configuration applies to both (upper and lower) lines. This command applies to manual clock distribution but not Network Clock Distribution Protocol (NCDP—see cnfncdp description).
Note
Syntax
cnfclkparms <signal type> <cable type>
Syntax Description
Related Commands
None
Attributes
Example
Set the cable type to coaxial then check it.
Unknown.8.PXM.a > cnfclkparms 1 2Unknown.8.PXM.a > dspclkparmsBITS Cable Type: CoaxialBITS Signal Type: Data Modecnfclksrc
Configure Clock Source—PXM45, PXM1E
The cnfclksrc command lets you configure a primary or secondary clock source for the node. This command supports the manual clock distribution mode—where the mechanism for propagating a primary clock throughout the network must be configured at each switch. To enable the automatic clock distribution provided by the Network Clock Distribution Protocol (NCDP), use the cnfncdp command.
A clock source can be:
•
•
•
Clock Operation
When a switch first powers up, the internal oscillator on the PXM provides the clock to the node. Thereafter, you can configure the clock sources at each node according to a well-designed plan for network synchronization.
A typical configuration for a network starts with a Building Integrated Timing System (BITS) clock source of stratum 3 or higher on one of the switches. Therefore, the node with the BITS clock becomes the master clock source for the network. The active clock drives the clock line on the backplane, and each service module takes its clock from this line. Thereafter, the clock goes out through every line to other switches in the network. At the other switches, you can configure one of the lines to be the primary or secondary clock source for that switch.
(For a description of line-level looped timing, refer to the cnfln description. With looped timing, a clock arrives on a line and is redirected to become the transmit clock for only that line.)
Prerequisites to Clock Configuration
Whether it uses BITS or an NNI line for a clock source, the node first must have a network controller. See the addcontroller description. For an NNI-sourced clock, the additional prerequisites are:
•
•
•
Database Updates and Clock Configuration
If the node has a redundant PXM, it automatically receives changes you make to the clock configuration as well as automated clock changes that occur under node management. For example, if you delete a clock source (delclksrc), the standby card automatically implements this configuration change. Also, any switch from primary to secondary source is recorded by the standby PXM.
Syntax
The syntax for cnfclksrc depends on the clock source.
For the external BITS clock:
cnfclksrc <priority> <portid>
portid has the format [shelf.]slot.port -bits e1 | t1 [-revertive <enable | disable>]
For AXSM-sourced clock (note the positions of the periods and colons):
cnfclksrc <priority> <portid>
portid has the format [shelf.]slot:subslot.port:subport or slot.port on a PXM1E
Syntax Description
priority
The priority of the clock source is either primary or secondary. The default is primary.
portid for BITS
•
•
•
•
MGX 8830 chassis) and a port number of 35 or 36 because you have identified a BITS clock source. Type the string "-bits" followed by a space then either "e1" or "t1." See "Usage Guidelines" for details.•
portid on service module or PXM1E UNI or NNI
•
•
•
•
•
•
•
•
•
Usage Guidelines for cnfclksrc
The following sections contain relevant information for cnfclksrc and details about its parameters.
Specifying Primary and Secondary Clock Sources
Before using the cnfclksrc command, note the following:
•
•
•
•
•
•
•
•
Changing the Priority of a Clock Source
To change the priority of a clock source, the command sequence depends on the priority of the sources:
•
To change from one primary source to another primary source, you need to execute only cnfclksrc To change the priority of a clock source, the command sequence depends on the priority of the sources:
•
•
Responses to Clock Failures
If the current clock is the primary or secondary source and that source fails, the clock circuitry goes into holdover mode. Holdover is a standards-based response to a failed clock. In holdover, the UI-S3 card maintains the clock based on the clock signal's parameters as recorded in hardware. Even for a stratum 1 source, the UI-S3 card maintains the frequency and stability of the failed clock source for up to 24 hours. If the source does not return to use in 24 hours, the node switches to the internal oscillator.
Configuring a BITS Clock
You can configure a node to obtain its primary and secondary clocks from a BITS device connected to the PXM-UI S3. The PXM-UI S3 can support stratum levels 1-3 and has two connectors to receive these highly stable clocks from an external device. If the primary and secondary clocks are externally-sourced, they must be the same rate. For example, you cannot specify a T1 for primary and an E1 for secondary.
Note
You can enable a revertive mode for the primary BITS clock. The revertive function on the PXM applies when the primary clock source fails. A failure is a loss of the primary clock source after the node has locked to that clock source. If a primary clock recovers from a failure and revertive mode is enabled, the node automatically reverts to the primary source. The restored primary clock must be available for 12 seconds before it again becomes the active clock source.
If the primary clock source fails and revertive mode is disabled, you must re-configure the primary source after the failure has been corrected.
To change the mode from revertive to non-revertive, use cnfclksrc. Follow the portID and priority with "-revertive disable."
Note
Related Commands
dspclksrcs, delclksrc, dspclkalms, cnfclkparms
Attributes
Examples
Configure the E1 clock at the upper connector of the PXM-UI S3 as the primary source. Configure subport (logical port) 10 on the line of the AXSM-1-2488 in slot 3 as the secondary. For the secondary source on the AXSM, note the locations of the periods and colons. Upon successful execution, the system displays a confirmation message.
pinnacle.7.PXM.a> cnfclksrc primary 7.35 -bits e1Clock Manager has been successfully executed.pinnacle.7.PXM.a> cnfclksrc secondary 3:1.1:10Clock Manager has been successfully executed.Configure a primary network clock to revert to the highest priority E1 clock source after recuperation from a failure. Upon successful execution, the system displays a confirmation message.
pinnacle.7.PXM.a> cnfclksrc primary 7.36 -bits e1 -revertive enableClock Manager has been successfully executed.cnfcmdabbr
Configure Command Abbreviation—PXM45, PXM1E
The cnfcmdabbr command lets you specify whether the CLI requires the entire name of a command or accepts the first unique string of characters that identifies a command. For example, "loa" is enough to identify loadrev if command abbreviation is enabled. (The string "lo" is not enough to identify a particular command because of the logout command.)
Syntax
cnfcmdabbr <flag>
Syntax Description
flag
A Boolean expression to enable or disable command abbreviation: enter "on" to enable or "off" to disable command abbreviation.
Related Commands
dspcmdabbr
Attributes
Example
Enable command abbreviation, then check its status by executing dspcmdabbr.
excel.1.3.PXM.a > cnfcmdabbr onCommand Abbreviation feature being enabledpop20one.7.PXM.a > dspcmdabbrCommand Abbreviation feature currently enabledTest the functionality of command abbreviation by entering "loa" (for loadrev) without parameters.
pop20one.7.PXM.a > loaERR: Syntax: loadrev <slot> <revision>revision - revision number. E.g.,2.0(1)2.0(1.255)2.0(0)I or 2.0(0)A2.0(0)P1 or 2.0(0)P2cnfcon
Configure Connection—PXM1E
The cnfcon command lets you modify the bandwidth, policing, and routing parameters of an existing endpoint. On the PXM1E, this command applies to only an SPVC or an SPVP with an endpoint that exists on the UNI/NNI back card.The command parameters consist of:
•
•
•
After you specify the mandatory connection identifier, all other parameters are optional.
Usage Guidelines for the cnfcon Command
The following sections discuss the application of certain cnfcon parameters.
Note
Traffic Parameters
Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both the forward and reverse directions. Be sure that the value entered as "local" on one end is equal to the value entered as "remote" on the other end. For example, the lpcr on the slave endpoint should be same as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If you modify traffic parameters after creating an SPVC, you just modify them at either the master endpoint or the slave endpoint.
Traffic parameters such as CDV, CTD are entered at both the master and slave endpoints for both the forward and reverse directions. However, the values of these parameters entered at the slave end are ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master end only.
Routing Parameters
Routing parameter, such as maximum route cost (-mc maxcost) or the routing priority (-rtngprio routingPriority) need to be entered at the master endpoint only. The values of the parameters entered at the slave end are ignored during call setup.
You can assign a priority at the master end of an SPVC or SPVP. The PNNI controller routes higher priority connections before lower priority connections. The user-configurable range for a connection is, in descending order of priority, 1-15. The default is 8. See cnfpri-routing for a detailed description of the Priority Routing feature. Also, the cnfpri-routing command lets you configure groups of bandwidth so that the order of routing also reflects the bandwidth requirements of the connection.
If you use the cnfcon command to modify only the routing priority of a connection, PNNI does not immediately re-route the connection. Nevertheless, if you run dspcon for such a changed connection at the master endpoint, it immediately shows the changed priority even before PNNI re-routes the connection. You can also use the dsppncon command to see the priority of the SVC portion that is associated with master and slave endpoints. Note that the dsppncon command shows the new priority only after PNNI re-routes the connection.
Frame Discard
The current release supports two types of frame discard for VCCs carrying AAL5 cells. These frame discard mechanisms are policing-based and congestion-based. Policing-based discard depends on the -frame option in the addcon or cnfcon command (specified only at the master end). Congestion-based policing for all cell streams is governed by settings in the current port SCT. The two types of frame discard are independent of each other and may or may not coexist.
When policing-based frame discard is enabled, the policer discards all cells of an AAL5 frame that follow a non-compliant cell. Specific actions for PCR and SCR non-compliance are detailed in the section, "Policer Settings and Consequences."
When congestion based frame discard is enabled by the current port-level SCT, if the arriving cells exceed an EPD threshold, the whole frame is discarded.
The table below shows the action applied to a connection according to the frame discard setting. The following information clarifies the table contents:
•
–
–
•
–
–
Restrictions
Frame discard applies to connections that use ATM AAL5 adaptation (ITU-T I.363.5). Although enabling frame discard on an AAL5 cell stream is not mandatory, it helps improve the useful throughput on a VC by discarding complete frames during times of congestion on the switch. Without frame discard enabled on an AA5 cell stream, corrupted AAL5 frames (containing dropped cells) can reach upper layers and trigger numerous re-sends. Conversely, enabling frame discard on other (non-AAL5) types of cell streams can bring uncertain results. In a worst case, total discard of end-to-end traffic of a non-AAL5 stream can occur in either direction.
The hardware does not support frame-based discard on VPCs. Only VCCs support frame-based discard.
Note
Policer Settings and Consequences
This section describes two types of conformance tests that occur when you enable frame discard through this frame discard parameter. The tests are PCR and SCR conformance tests.
The PCR conformance test is performed using GCRA1 in exactly the same manner as normal cell policing. For this test, the Action should be set to discard. If the PCR conformance test is deemed to be non-compliant, the action will be to discard of the cells in the current frame. In other words, a "partial packet action" can be taken when cells in the current frame fail this conformance test. The PCR conformance test implements a partial packet discard (PPD). The policer does a complete frame discard if the first cell of the packet was discarded as a result of PCR failure
The SCR conformance test is performed using GCRA2, although it differs slightly from the normal cell policing.The SCR conformance test is performed only at the start of a frame. If the first cell of a frame is a conforming CLP=0 cell, then all remaining cells will be as if they are conforming to the SCR conformance test. The SCR conformance test can be programmed to tag non-conforming CLP=0 cells. If the first cell of a frame is a non-conforming CLP=0, then that cell and all other cells in that frame (including the EOM) will be tagged. In other words, the tagged action taken by this conformance test is determined at frame boundaries only. If the SCR conformance test is programmed to discard, the policer can discard at any point in the frame and is not restricted by frame boundaries.
Local-Only Parameters
The parameters CDVT, stats enable, cc enable (specified using -cdvt, -stat, -cc) are significant only at the endpoint where you enter them. Therefore, they can be different at each end of the connection.
Syntax
cnfcon <ifNum> <vpi> <vci>
[-lpcr <local to remote PCR>] [-rpcr <remote to local PCR>] [-lscr <local to remote SCR>] [-rscr <remote to local SCR>] [-lmbs <local to remote MBS>] [-rmbs <remote to local MBS>] [-lcdv <local to remote maxCDV>] [-rcdv <remote to local maxCDV>] [-lctd <local to remote maxCTD>] [-rctd <remote to local maxCTD>] [-lmcr <local to remote MCR>] [-rmcr <remote to local MCR>] [-cdvt <local CDVT>] [-cc <OAM CC Cnfg>] [-stat <Stats Cnfg>] [-frame <frame discard>] [-mc <Max Cost>] [-segep <OAM segment endpoint>]
[-lputil <local -> remote PUtil>] [-rputil <remote -> local PUtil>] [-rtngprio <routingPriority>]Syntax Description
Note
ifNum
The logical interface (or port) number. This ifNum corresponds to the ifNum added through the addport command. The range is 1-31.
Note
vpi
Virtual path identifier value in the range 0-255 (UNI) or 0-4095 (NNI or VNNI). For VNNI, specify one VPI per port.
vci
Virtual connection identifier (VCI):
•
•
service type
Type a number in the range 1-12 to specify one of the following service types:
•
•
•
•
•
•
•
•
•
•
•
•
mastership
Value to specify the endpoint as master or slave:
•
•
-slave
Keyword for the slave-end identifier, an item you enter at the master end. This keyword is mandatory when you are adding a master endpoint (mastership=m or 1).
-lpcr
Local peak cell rate (PCR). Specifies the PCR from a local endpoint to a remote endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-rpcr
Remote peak cell rate (PCR). Specifies the PCR from a remote endpoint to a local endpoint (3-5651328 cells per second). PCR is the maximum cell rate for the connection at any time.
-lscr
Local sustained cell rate (SCR). Specifies the SCR from a local endpoint to a remote endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-rscr
Remote sustained cell rate (SCR). Specifies the SCR from a remote endpoint to a local endpoint (3-5651328 cells per second). SCR is the maximum cell rate that a connection can sustain for long periods.
-lmbs
Local maximum burst size (MBS). Specifies the MBS from a local endpoint to a remote endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-rmbs
Remote maximum burst size (MBS). Specifies the MBS from a remote endpoint to a local endpoint (1-5000000 cells). MBS is the maximum number of cells that can burst at the PCR and still be compliant.
-cdvt
Local cell delay variation tolerance (CDVT). Specifies the CDVT from a local endpoint to a remote endpoint (1-5000000 microseconds). Cell Delay Variation Tolerance controls the time scale over which the PCR is policed.
Note that no remote CDVT is necessary.
-lcdv
The local cell delay variation (CDV) parameter specifies the peak to peak CDV from the local endpoint to the remote endpoint. The range is 1-16777215 microseconds.
To revert to the default value for this parameter, type "-1."
-rcdv
The remote cell delay variation (CDV) parameter specifies the peak to peak CDV from the remote endpoint to the local endpoint. The range is 1-16777215 microseconds.
To revert to the default value for this parameter, type "-1."
-lctd
Local cell transfer delay (CTD). This parameter specifies the CTD from a local endpoint to a remote endpoint. The range is 0-65535 microseconds.
To revert to the default value for this parameter, type "-1."
-rctd
Remote cell transfer delay (CTD). This parameter specifies the CTD from the remote endpoint to the local endpoint. The range is 0-65535 microseconds.
To revert to the default value for this parameter, type "-1."
-cc
Operations, administration, and maintenance continuity check (OAM CC): enter 1 to enable or 0 to disable.
To provision continuity checking, enable this function at both ends of the connection, otherwise a connection alarm results. (As you create a connection with this parameter, the connection goes into alarm until both ends of the connection are added.)
Default: 0 (disabled)
-stat
Statistics collection: enter 1 to enable or 0 to disable. The default is 0.
The Cisco WAN Manager tool collects statistics for a connection if you enable it here. Statistics collection is disabled for all connections by default. Statistics collection has an impact (which may not be significant) on the real-time response, especially for SVCs (which can be affected even though you do not add SVCs). Therefore, you should enable statistics collection for only the subset of connections that really warrants such a feature.
-frame
This option lets you enable or disable frame-based policing and discard for the VCC (no VPCs). See the section, "Frame Discard," for important details on frame discard.
Note
Possible values:
•
•
Default: 0 (disabled)
-mc
Maximum cost (maxcost): a value that creates a priority for the connection route. The switch can select a route if the cost does not exceed maxcost. The range for maxcost is 0-4294967295. If you do not specify maxcost, the connection has the highest routing priority by default. Therefore, the maxcost parameter lets you lower the routing priority of a connection. Note the following effects of values in the maxcost range:
•
•
•
Although maxcost applies to an individual connection, routing costs substantially depend on a cost-per-link that you specify at every PNNI logical port in the network. The applicable PNNI command is cnfpnni-intf.
The cost of a route is as follows:
routing cost=sum of all costs-per-link
where:
•
•
The cost-per-link applies to all connections of a particular service type on a port. For example, the cost-per-link is the same for all VBR.1 connections that PNNI controls on a port, and this cost can differ from all UBR.1 connections on the same port. Alternatively, you can use cnfpnni-intf to make the cost-per-link the same for all service types.
To illustrate by examining a four-link route:
1.
2.
3.
The route is usable because the cost of 50240 is less than the maxcost of 100000.
Default: 4294967295 The default makes maxcost meaningless for the connection, so PNNI does not use it as a routing metric.
Note
-lputil
Local Percentage Utilization: Range 1-100. The default is 100.
-rputil
Remote Percentage Utilization: Range 1-100. The default is 100.
-rtngprio
You can modify the priority of this connection. The descending range of priorities is 1-15. The default is 8. See the cnfpri-routing description for details on this feature.
Related Commands
addcon, delcon, dspcon, dspcons, dspconstats
Attributes
Example
Enable OAM CC in the connection with a VPI and VCI of 10 40 on interface 1.
MGX8850.7.PXM1E.a > cnfcon 1 10 40 -cc 1Configuration successfulAssign a routing priority of 3 to the connection with a VPI and VCI of 102 and 102, respectively, on interface number 1. Check the result by using the dspcon command.
M8850_LA.7.PXM1E.a > cnfcon 1 102 102 -rtngprio 3Configuration successfulM8850_LA.7.PXM1E.a > dspcon 3:1.1:1 102 102Port Vpi Vci Owner State Persistency----------------------------------------------------------------------------Local 3:1.1:1 102.102 MASTER FAIL PersistentAddress: 47.00918100000100001a531c2a.000001031801.00Node name: M8850_LARemote Routed 102.102 SLAVE -- PersistentAddress: 47.00918100000200036b5e30cd.000001011802.00Node name:-------------------- Provisioning Parameters --------------------Connection Type: VCC Cast Type: Point-to-PointService Category: CBR Conformance: CBR.1Bearer Class: BCOB-XLast Fail Cause: unallocated (unassigned) number Attempts: 20055Continuity Check: Disabled Frame Discard: DisabledL-Utils: 100 R-Utils: 100 Max Cost: -1 Routing Cost: 0OAM Segment Ep: EnabledPriority: 3cnfconpref
Configure Preferred Route for a Connection—PXM45, PXM1E, PXM1
The cnfconpref commands lets you associate a preferred route with an SPVC or SPVP. A connection can have only one preferred route. If a connection already has a preferred route associated with it, you can replace that route with a new one. See the addpref description for more details on preferred routes.
The preferred route must already exist for you to associate it with a connection. The steps can be two or possibly all three of the following:
1.
2.
3.
Note
Syntax
cnfconpref <portid> <vpi> <vci> <rteID> [-assoc {set | clr}] [-direct {set | clr}]
[-onPrefRte {yes | no}]Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vpi
VPI of the connection.
Range: 0-255 on a UNI, 0-4095 on an NNI
Default: none
vci
VCI of the connection. If the VCI is 0, the connection is an SPVP.
Range: 1-65535
Default: none
rteID
The route identifier.
Range: 1-5000
Default: none
-assoc
The -assoc option either associates (-assoc set) or disassociates (-assoc clr) the specified route to the specified connection. If you type -assoc set to associate a route, the command entry must include the route ID. If you disassociate the route by typing -assoc clr, the route ID is unnecessary. Because set is the default, if you type a route ID but do not include -assoc set, the protocol interprets the command as an attempt to associate the specified route to the specified connection.
Possible entries: set or clr (for clear)
Default: set
-direct
Change the directed route status. A directed route means the preferred route associated with the connection is the only route the connection can take. If the preferred route is not available, the connection is failed. Type -direct yes to make the route identified by rteID a directed route for the associated connection. The connection is identified by portid vpi vci.
Possible entries: yes or no
Default: no
-onPrefRte
This parameter lets you inform the node that the connection is routed on its associated, preferred route. The purpose is to prevent rerouting of the connection during grooming.
Possible entries: yes or no
Default: no
Usage Guidelines
Before associating a preferred route to an SPVC, consider the following
•
•
•
Related Commands
addpref, modpref, delpref, dsppref, dspprefs, dsptopondlist
Attributes
cnfconsegep
Configure Connection Segment Endpoint—PXM45, PXM1E
The cnfconsegep command lets you configure a segment endpoint for an SVC or SVP on a via node. Its purpose is to support a particular troubleshooting scheme. After you create an endpoint, you can use the tstdelay command and specify the endpoint created with the cnfconsegep command. The Example section shows how to use tstdelay and conntrace in conjunction with the cnfconsegep command.
You can specify more than one endpoint as long as each one complies with the requirements of the cnfconsegep command, as follows:
•
•
•
In Figure 2-5, an SPVC has endpoints at UNI1 and UNI2. You can use cnfconsegep to configure segment endpoints at NNI2, NNI3, NNI4, and NNI5. You cannot configure segment endpoints at UNI1, UNI2, NNI1, and NNI6. After you configure any of these endpoints, you could verify the electrical integrity by using the tstdelay command from UNI1 or UNI2 to each of NNI2, NNI3, NNI4, or NNI5. After you finish troubleshooting, remove all segment endpoints by using delconsegep for each endpoint.
Figure 2-5 Configurable Endpoints for the cnfconsegep Command
Syntax
cnfconsegep <portid> <vpi> [vci]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
vpi
VPI of the connection.
vci
VCI of the connection.
Related Commands
cnfoamsegep, dspoamsegep, delconsegep, dspconsegep
Attributes
Example
This example shows how the cnfconsegep, conntrace, and tstdelay commands can work to show a point of failure.
•
•
•
•
•
•
In this network, the following have also been established:
•
•
•
Check the connection path by using the conntrace command then displaying the trace results with the dspconntracebuffer command. Note that the dspconntracebuffer command does not use keywords. As expected, it traverses the direct link (PhysPortId=9:1.2:2 as shown in the output display), as follows:
tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66tokyo.8.PXM.a > dspconntracebuffer 9:1.8:8 66 66Result:SUCCESS Reason: N/InterfaceId:9:1.8:8Originating Interface VPI : 66Originating Interface VCI : 66Originating Interface Call Ref : 1NodeId EgressPort VPI VCI CallRef56:160:47.00918100000000107b65f448.00107b65f448.01 17373186 0 35 1 PhysPortId=9:1.2:256:160:47.00918100000000309409f3bb.00309409f3bb.01 0Terminating Interface VPI : 66Terminating Interface VCI : 66Terminating Interface Call Ref : 1To continue this example, the following tasks are performed:
1.
2.
3.
tokyo.8.PXM.a > dnpnport 9:1.2:2tokyo.8.PXM.a > conntrace 9:1.8:8 -vpi 66 -vci 66Result:SUCCESS Reason: N/AInterfaceId:9:1.8:8Originating Interface VPI : 66Originating Interface VCI : 66Originating Interface Call Ref : 2NodeId EgressPort VPI VCI CallRef56:160:47.00918100000000107b65f448.00107b65f448.01 17373185 0 36 2 PhysPortId=9:1.1:156:160:47.00918100000000309409f3b8.00309409f3b8.01 17373187 0 41 1 PhysPortId=9:1.3:356:160:47.00918100000000309409f3bb.00309409f3bb.01 0Terminating Interface VPI : 66Terminating Interface VCI : 66Terminating Interface Call Ref : 2tokyo.8.PXM.a > uppnport 9:1.2:2Configure a connection segment endpoint by using the following values on node "fiorano:"
•
•
fiorano.7.PXM.a > cnfconsegep 9:1.1:1 0 36PortId: 0.9:1.1:1 Vpi: 0 Vci: 36The connection is configured as a segment end point.On the CLI of the AXSM in slot 9, use the tstdelay command to measure the required time for sending OAM cells to the far-end and back. From the PNNI physical port ID 9:1.8:8, you know to cc to slot 9 and specify ifNum 8. (Note that Cisco does not recommend using the tstdelay command for acquiring an accurate measurement of the round trip delay. Its function is better suited to confirming the existence of the connection path.)
tokyo.9.AXSM.a > tstdelay 8 66 66tstdelay is in progress ..Connection Id Test Type Direction Result Round Trip Delay============= ========= ========= ======= ================08.0066.00066: OAM Lpbk ingress Success 128 microsecDelete the configuration of the segment endpoint then measure the round trip delay.
fiorano.7.PXM.a > delconsegep 9:1.1:1 0 36PortId: 0.9:1.1:1 Vpi: 0 Vci: 36The connection is configured as NOT a segment end point.tokyo.9.AXSM.a > tstdelay 8 66 66tstdelay is in progress ..Connection Id Test Type Direction Result Round Trip Delay============= ========= ========= ======= ================08.0066.00066: OAM Lpbk ingress Success 194 microsec
Note that the round trip delay is significantly longer (194 microseconds compared to 128 microseconds in the first instance). If the OAM cells did not return to the near end, the segment where traffic was being lost would have been identified.
Also note that the configuration of segment endpoints can occur on many via nodes.
cnfdate
Configure Date—PXM45, PXM1E
Configure the system date. The system does not return a message unless an error occurred. To see the date, use the dspdate command.
Note
Syntax
cnfdate <mm/dd/yyyy>
Syntax Description
mm/dd/yyyy
•
•
•
Related Commands
dspdate
Attributes
Example
Set date to June 26, 2000.
excel.7.PXM.a > cnfdate 06/26/2000cnfdiag
Configure Diagnostics—PXM45, PXM1E
Enables the online or offline diagnostics. The cnfdiag command also configures the time settings for the start time and coverage for running the offline diagnostics. When you enter cnfdiag with no parameters, it displays the current configuration and status of the diagnostics.
The cnfdiagall command is the same as cnfdiag except that it configures all slots on the card at once.
Note
The Purpose of the Diagnostics
These diagnostics were implemented to test and validate the communication paths on the PXM and the AXSMs before and during operation. The diagnostics are always scheduled from the PXM controller card whether they run on the PXM or a service module.
For backward compatibility, the current switches have two buses on the backplane:
•
•
Because of the difference between bus speeds on the backplane, the Reliability Availability Serviceability (RAS) requirements demand that diagnostics periodically run on the communications paths. Therefore, diagnostics should periodically run on both active and standby cards—especially on standby cards. Frequent testing of standby cards through diagnostics helps to ensure that when an active card fails, the standby card is ready to assume the active card state immediately.
Online Diagnostics
Online diagnostics are nondestructive tests (that do not interfere with live traffic) and run on either an active card or a standby card. The MGX 8950, MGX 8850, and MGX 8830 switches support various online diagnostics tests. The sections that follow describe the tests that run on a PXM45, PXM1E, and the AXSMs.
PXM45 Online Diagnostics
Active State
When you enable online diagnostics on an active PXM45, the following test runs:
•
Standby State
When you enable online diagnostics on a standby PXM45, the following tests run:
•
•
PXM1E On-line Diagnostics
For on-line diagnostics, either an active or a standby PXM1E can run a loopback test. Cells originate on the Atlas, loop at the QE1210, then terminate at the Atlas.
AXSM Online Diagnostics
Active State
When you enable online diagnostics for an active AXSM card, the following test runs:
•
Standby State
When you enable online diagnostics on a standby AXSM card, the following tests run:
•
•
•
Offline Diagnostics
Offline diagnostics are destructive (interfere with traffic) and therefore run only on standby cards.
Offline diagnostics are scheduled by using the offline start (offStart) and offline day-of-week (offDow) parameters. The coverage (offCover) parameter specifies the length of time that the diagnostics run.
Note
The offline diagnostics that can be enabled and scheduled depend on the circuitry. The sections that follow list the offline diagnostic by card.
PXM45 Offline Diagnostics
The PXM45 runs the following off-line diagnostics:
1.
•
•
•
•
2.
•
•
•
•
•
•
3.
•
•
•
•
•
•
4.
•
5.
•
•
•
PXM1E Off-line Diagnostics
The PXM1E runs off-line diagnostics in the following areas:
1.
2.
3.
AXSM Offline Diagnostics
1.
2.
3.
4.
5.
6.
7.
8.
Syntax
cnfdiag <slot> <onEnb> <offEnb> [<offCover> <offStart> <offDow>]
Syntax Description
Related Commands
cnfdiagall, dspdiagcnf, abortofflinediag
Attributes
Example
cnfdiag 7 enable disable light 22:30 -M-W-F-cnfdiagall
Configure Diagnostics All—PXM45, PXM1E
This command enables and configures online or offline diagnostics for all card slots. (This command is the same as cnfdiag except that it effects all slots instead of just one.)
When you enter this command with no parameters, it displays the current configuration and status of the diagnostics.
Note
Note
Syntax
cnfdiagall <onEnb> <offEnb> [<offCover> <offStart> <offDow>]
Syntax Description
Related Commands
cnfdiag, dspdiagcnf
Attributes
Example
cnfdiagall enable disable light 22:30 -M-W-F-cnfe164justify
Configure E.164 Justification—PXM45, PXM1E
Specifies whether the E.164 AESAs with the E.164 AFI are converted to the left or right-justified encoding format. For PNNI to search the address correctly, all nodes in the PNNI network must use the same justification.
Syntax
cnfe164justify left | right
Syntax Description
left or right
Justification of E164 addresses. Type the entire word "left" or "right."
Default: left
Related Commands
dspsvcparm
Attributes
Examples
Configure right-hand justification for the E.164 AESAs.
Geneva.7.PXM.a > cnfe164justify right
cnfenhiisp
Configure Enhanced IISP—PXM45, PXM1E
The cnfenhiisp command enables or disables the enhanced IISP feature on the port. This command applies to only IISP ports. When you change the operational state of enhanced IISP, the change does not affect existing calls.
The items that enhanced IISP include are:
•
•
•
•
Syntax
cnfenhiisp <portid> {yes | no}
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
yes | no
Enter "yes" to enable enhanced IISP or "no" to disable enhanced IISP.
Default: no
Related Commands
dspenhiisp
Attributes
Examples
Enable enhanced IISP on port 11:2.1:1.
Geneva.7.PXM.a > cnfenhiisp 11:2.1:1 yes
cnfetherif
Configure Ethernet Interface—PXM45, PXM1E (init state only)
The cnfetherif command lets you configure an Ethernet interface while the PXM is in the init state. The dspetherif command displays the configuration. Both of these commands are available only when the PXM is in the init state.
Syntax
cnfetherif <ip_address> [ net_mask ]
ip_address
The IP address has the format a.b.c.d. See the Example section.
net_mask
The optional net mask has the format a.b.c.d. See Example for a typical netmask.
Syntax Description
This command has no parameters.
Related Commands
dspetherif
Attributes
Example
Configure an init-state Ethernet interface to have Ethernet address 177.19.21.66 and a netmask of 255.255.0.0. Display the new Ethernet interface.
scott.8.PXM.if > cnfetherif 177.19.21.66 255.255.0.0scott.8.PXM.if > dspetherifscott System Rev:03.00 Sep. 20, 2002 12:49:26 PSTMGX8850 Node Alarm:MINORETHERNET IP INTERFACE CONFIGURATION--------------------------------------------------------------------lnPci (unit number 0):Flags:(0x63) UP BROADCAST ARP RUNNINGType:ETHERNET_CSMACDInternet address:177.19.21.66Broadcast address:177.19.21.255Netmask 0xffff0000 Subnetmask 0xffffff00Ethernet address is 00:30:94:09:f3:abMetric is 0Maximum Transfer Unit size is 1500342500 packets received; 281994 packets sent60401 multicast packets received282 multicast packets sent0 input errors; 0 output errors0 collisions; 0 droppedDISK IP address:177.19.21.66cnffltset
Configure Filter Set—PXM45, PXM1E
Use cnffltset to modify an existing filter set. This command can:
•
•
After a filter is modified for a specific port, associate the filter to that port by using cnf-pnportacc.
Syntax
cnffltset <name> [-address atm-address -length address-length [-plan {nsap | e164}] [-list {calling | called}]] [-index number] [-accessMode {permit | deny}]
Syntax Description
Related Commands
addfltset, delfltset, dspfltset
Attributes
cnfilmi
Configure ILMI—PXM1E
Configures the card-level interim local management interface (ILMI) for the PXM1E UNI/NNI back card (for the VSI slave side). Activating the card-level ILMI through cnfilmi requires a pre-existing logical port (see addport) and resource partition (see addrscprtn or addpart). No response appears unless an error occurs.
Note
Syntax
cnfilmi <ifNum> -id <partitionID> -ilmi <ilmiEnable> -vpi <vpi> -vci <vci> -trap <ilmiTrapEnable> -s <keepAliveInt> -t <pollingIntervalT491> -k <pollInctFact>
Syntax Description
Related Commands
dspilmi, dspilmis, dspilmicnt, clrilmicnt, dnilmi, upilmi
Attributes
Examples
Unknown.7.PXM1E.a > cnfilmi 1 1 -ilmi 1 -vpi 40 -vci 99 -s 10 -t 10 -k
cnfilmienable
Configure ILMI Enable—PXM45, PXM1E
Enables ILMI on a PNNI port. Prior to cnfilmienable, the port must be administratively down. Use the dnpnport command to down the port and uppnport to up it.
Syntax
cnfilmienable <portid> [yes | no]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
yes or
noType "yes" to enable ILMI or "no" to disable ILMI on the specified PNNI port.
Default: disabled
Related Commands
dnpnport, uppnport, dsppnilmi
Attributes
Examples
Enable ILMI on a PNNI port 4:1.1:11. First, disable the port by using dnpnport.
Geneva.1.PXM.a > dspilmi 4:1.1:11INFO: No ilmi address registeredGeneva.7.PXM.a > dnpnport 4:1.1:11Geneva.7.PXM.a > cnfilmienable 4:1.1:1Geneva.7.PXM.a > uppnport 4:1.1:11Geneva.7.PXM.a >
cnfilmiproto
Configure ILMI Protocol—PXM45, PXM1E
The cnfilmiproto command lets you configure how PNNI reacts to ILMI events that occur on the VSI slave (a service module). Use the dsppnilmi command to confirm changes to the configuration.
Syntax
cnfilmiproto <portid> [-securelink {yes | no}] [-attachmentpoint {yes | no] [-modlocalattrstd {yes | no]
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
-securelink
Sets the flag securelink to make PNNI release the call if it loses connection to the ILMI slave.
no: do not enable the ILMI Secure link protocol.
yes: disable the ILMI Secure link protocol.Default: yes
-attachmentpoint
Sets the flag attachmentpoint to make PNNI release the call if the slave ILMI session sees changes in peer information, such as the system name or system ID.
no: do not enable the detection of loss of attachmentpoint protocol.
yes: Enable the detection of loss of attachmentpoint.Default: yes
-modlocalattrstd
Sets the flag modlocalattrstd to make PNNI release the call if the slave ILMI sees ATM layer (partition resource) changes, such as the VPI or VCI.
no: disable the ILMI standard procedure for modification of local ATM param.
yes: enable the ILMI standard procedure for modification of local ATM param.Default: yes
Related Commands
dsppnilmi
Attributes
Example
Jose.7.PXM.a > cnfilmiproto 11:2.1.1 -securelink no -attachmentpoint no -modlocalattrstd yescnfimagrp
Configure IMA Group—PXM1E
This command modifies one or more attributes of an IMA group. Modifying any IMA attribute causes the IMA group to restart. See the addimagrp and addimaport descriptions for details on IMA groups.
Syntax
cnfimagrp <-grp group> [-ver <version>] [-txm <minLinks>] [-txid <txImaId>] [-txfl <txFrameLen>] [-dd <diffDelayMax>] [-uptim <groupUpTime>] [-dntim <groupDownTime>]
Syntax Description
Related Commands
addimagrp, delimagrp, dspimagrp, dspimagrps, rstimagrp, dspimalnk
Attributes
Example
For IMA group 16, specify a differential delay of 200 milliseconds.
MGX8850.7.PXM1E.a > cnfimagrp -grp 2.16 -dd 200cnfimalnktst
Configure IMA Link Test—PXM1E
The cnfimalnktst command lets you specify a pattern test to confirm the integrity of an individual link. To start and end the test, use the startimalnktst and stopimalnktst commands, respectively.
The test pattern is a number in the range 0-254. A 0 causes the system to select a number for the pattern. If the transmitted number is the same as the number that arrives at the receiving end of the link, the link is valid. If the test pattern is different or does not arrive at all, the link is invalid.
Note
Syntax
cnfimalnktst <-grp group> <-lnk link> <-pat test Pattern>
Syntax Description
Related Commands
startimalnktst, stopimalnktst
Attributes
Example
For group 1 and link 1, specify a test pattern of 77.
MGX8850.7.PXM1E.a> cnfimalnktst -grp 2.1 -lnk 2.1 -pat 77cnfintfcongth
Configure Interface Congestion Threshold—PXM45, PXM1E
The cnfintfcongth command lets you configure congestion thresholds for a logical port. The thresholds apply to incoming calls and status enquiries. When the upper congestion limit is reached, the port may block incoming calls and adjust the pace of status enquiries.
You must specify at least one keyword.
Syntax
cnfintfcongth <portid> [-setuphi {setuphival [-unackedstatenqlo {unackedstatenqloval} ]
[ -unackedstatenqhi {unackedstatenqloval} ]Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For details, see the section, "PNNI Format," in "Introduction."
-setuphi
The number of connection set-up messages per second. Above this number, the condition of set-up messages on the interface is congested.
Range: 1-260 calls per second
Default: 180-unackedStatEnqLo
The number of status enquires yet to be acknowledged by peer-to-peer interface. Below this value, the congestion condition for status enquiries at the interface level is dropped.
Range: 1-500 messages
Default: 40-unackedStatEnqHi
The number of status enquires yet to be acknowledged by peer-to-peer interface. The interface is considered to be congested with status enquiries when this thresholds is reached.
Range: 1-500 messages
Default: 100
Related Commands
dspintfcongth, dspnodalcongth
Attributes
Example
Configure a congestion threshold of 200 for set-up messages on 6:1.1:1. Check the results by using the dspintfcongth command.
M8850_NY.7.PXM.a > cnfintfcongth 6:1.1:1 -setuphi 200M8850_NY.7.PXM.a > dspintfcongth 6:1.1:1Congestion Thresholds for port : 6:1.1:1Parameter Value unit--------- ----- ----setuphi 100 cpsunackedStatEnqLo 40 messagesunackedStatEnqHi 200 messagesM8850_NY.7.PXM.a >cnfintfvsvd
Configure Interface for VS/VD—PXM45, PXM1E
The cnfintfvsvd command lets you enable internal or external virtual source/virtual destination (VS/VD) on a PNNI port. If VS/VD is disabled on a port, you can enable VS/VD for individual ABR connections by using the cnfabr command. As described in Syntax Description, the cnfintfvsvd command also lets the service class template determine whether VS/VD is enabled.
Note
Before using the cnfintfvsvd command, note the following.
•
•
•
Syntax
cnfintfvsvd <portid> [-internal {off | on | unspecified}] [-external {off| on | unspecified}]L
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
internal
Indicates the internal loop for VS/VD. The choices are as follows:
off: at the port level, VS/VD service for ABR connections is disabled. Therefore, for an ABR connection to have VS/VD support, you must use the cnfabr command to enable it.
on: at the port level, VS/VD service for ABR connections is enabled. Therefore, all ABR connections on the port have VS/VD support. If you do not want a particular ABR connection to have VS/VD, use the cnfabr command to disable it for that connection.
unspecified: the port defaults to the VS/VD capability that the port-level SCT specifies.
Default: unspecified
external
Indicates the external loop for VS/VD. The choices are as follows:
off: at the port level, VS/VD service for ABR connections is disabled. Therefore, for an ABR connection to have VS/VD support, you must use the cnfabr command to enable it.
on: at the port level, VS/VD service for ABR connections is enabled. Therefore, all ABR connections on the port have VS/VD support. If you do not want a particular ABR connection to have VS/VD, use the cnfabr command to disable it for that connection.
unspecified: the port defaults to the VS/VD capability that the port-level SCT specifies.
Default: unspecified
Related Commands
dsppnport, cnfabr
Attributes
Example
This example starts with the assumption that port 5:1.1:1 is administratively down and is configured for an interface type other than UNI 4.0. Do the following:
Step 1
Step 2
Step 3
Step 4
M8850_NY.7.PXM.a > cnfpnportsig 5:1.1:1 -univer uni40M8850_NY.7.PXM.a > cnfintfvsvd 5:1.1:1 -internal on -external onM8850_NY.7.PXM.a > uppnport 5:1.1:1M8850_NY.7.PXM.a > dsppnport 5:1.1:1Port: 5:1.1:1 Logical ID: 17111041IF status: down Admin Status: upVSVD Internal Loop: onVSVD External Loop: onUCSM: enableAuto-config: enable Addrs-reg: enableIF-side: network IF-type: uniUniType: private Version: uni4.0PassAlongCapab: n/aInput filter: 0 Output filter: 0minSvccVpi: 0 maxSvccVpi: 255minSvccVci: 35 maxSvccVci: 65535minSvpcVpi: 1 maxSvpcVpi: 255#SpvcCfg: #SpvcActive: #SpvpCfg: #SpvpActive:p2p : 0 0 0 0p2mp: 0 0 0 0#Svcc: #Svpc: Total:p2p : 0 0 0p2mp: 0 0 0Total: 0M8850_NY.7.PXM.a >cnflink
Configure Link—PXM45, PXM1E
The cnflink command lets you change the framing for a T1 tributary. The command applies to the Service Resource Module-Enhanced (SRME). The upln and cnfln commands that you use on the PXM result in a line framing for all tributaries. For an individual link, you can configure the framing by using the cnflink command.
Note
Syntax
cnflink <SrmStartLinkIf> <FramingType>
Syntax Description
Related Commands
addlink, dellink, dsplink, dspslotlink
Attributes
Example
cnfln
Configure Line—PXM1E
On a PXM, the cnfln command lets you configure a line on the UNI/NNI (network interface) back card of a PXM1E or a Service Resource Module (SRME or SRM-3T3/C). (The UNI/NNI back card is also known as the uplink card or uplink bay.)
Note
Note the following before you use the cnfln command on a PXM:
•
•
•
•
(If the switch is already powered on and the SRMs installed, you can pull the back card from the primary SRM and, if present, the back card from the secondary SRM. If the cards are out of the backplane and power is off, just install the front cards. An SRM with no back card appears in card displays as "SRM_NO-BC.)Generic Syntax
This section introduces general information about the syntax. The syntax varies according to the line type, so each line type has its own description.
Your entries for line type and slot number determine the option list for cnfln on a PXM. The options for line type depend on whether the line is SONET, SDH, T3, E3, T1, or E1. The slot indicates to the controller whether the card is an SRM or the PXM1E NNI/UNI back card. The generic syntax follows:
cnfln -<lineType> slot.line <optionList>
If you enter only the line type, slot number, and line number, the Help feature displays appropriate syntax with option list. In the sections that follow, the Syntax and Syntax Description heading shows the line type.
To help you enter the correct line type and to locate the SRMs, use some of the high-level commands. To see all cards in the switch, use the dspcds command. The display shows where and what type of SRMs are present. To see the type of PXM1E back card, use the dspcd command on the PXM1E CLI. To see the types for all lines, use the dsplns command.
Syntax for PXM1E SONET or SDH Line
cnfln -sonet <X.line> -slt <LineType> -clk <clockSource>
Syntax Description for PXM1E SONET or SDH Line
Syntax for PXM1E T3 Line
cnfln -ds3 <X.line> -lt <LineType> -len <LineLength> -oof <OOFCriteria> -cb <A>
-clk <clockSource> -rfeac <RcvFEACValidation>Syntax Description for PXM1E T3 Line
Syntax for PXM1E E3 Line
cnfln -e3 <X.line> -len <LineLength> -clk <clockSource>
Syntax for PXM1E DS1 Line
Syntax for PXM1E E1 Line
Syntax for SRME Line
cnfln -sonet <slot.line> -slt <LineType> -clk <clockSource> -lpb <loopback> -sfs <FrameScramble> -rdiv <RDI-V Type> -rdip <RDI-P Type> -tt <Tributary Type> -tm <TributaryMappingType>
-tf <TributaryFramingType> -st <SignallingTranportMode> -tg <TributaryGroupingType>Syntax Description for SRME Line
If you are planning bulk distribution to T1 lines in Japan, specify a SDH (STM1) line type (see the -slt parameter). For bulk distribution to E1 lines, you must also specify the SDH line type.
Syntax for SRM-3T3
cnfln -ds3 <X.line> -lt <LineType> -len <LineLength> -oof <OOFCriteria> -cb <A>
-rfeac <RcvFEACValidation> -clk <clockSource>Syntax Description for SRM-3T3/C
Related Commands
upln, dnln, dspln, dsplns, cnfcdmode
Attributes
Example PXM1E T3 Line
Configure T3 line 2.4 to have ds3cbitadm coding, be 10 meters, oof=2, clock local, and rfeac=2.
MGX8850.7.PXM1E.a > cnfln -ds3 2.4 -lt 1 -len 10 -oof 2 -cb 1 -clk 2 -rfeac 1Examples for SRME
Check the tributary mapping on the SRME SONET line in slot 15 and change it to byte-synchronous if the current configuration is asynchronous.
Unknown.7.PXM.a > dspln -sonet 15.1Line Number : 15.1Admin Status : UpLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable RDI-V Type : one bitXmt Clock source : loopTiming RDI-P Type : one bitLine Type : sonetSts3 VT Type : vt15/vc11Medium Type(SONET/SDH) : SONET VT Mapping Type : asynchronousMedium Time Elapsed : 11985 VT Framing Type : N/AMedium Valid Intervals : 13 VT Signalling Mode : N/AMedium Line Type : ShortSMF VT Grouping Type : N/AThe VT Mapping Type field shows asynchronous, so configure the line for byte-synchronous. The command is rejected because of existing links. List the links then delete them.
Unknown.7.PXM.a > cnfln -sonet 15.1 -tm 2ERROR: There are links on the line, remove links firstUnknown.7.PXM.a > dsplink 15.1Line Num VtNum RowStatus TargetSlot TargetSlotLine FramingType======== ====== ========== ========== ============== ===========1 1 Add 11 1 Not Appl1 2 Add 11 2 Not ApplUnknown.7.PXM.a > delslotlink 11 0Proceed with configuring the line for byte-synchronous tributary mapping and check the configuration. Note that Framing Type and Signaling Mode take on the default values now that the tributary mapping has become byte-synchronous.
Unknown.7.PXM.a > cnfln -sonet 15.1 -tm 2Unknown.7.PXM.a > dspln -sonet 15.1Line Number : 15.1Admin Status : UpLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable RDI-V Type : one bitXmt Clock source : loopTiming RDI-P Type : one bitLine Type : sonetSts3 VT Type : vt15/vc11Medium Type(SONET/SDH) : SONET VT Mapping Type : byteSynchronsMedium Time Elapsed : 12034 VT Framing Type : ESFMedium Valid Intervals : 13 VT Signalling Mode : Transfer ModeMedium Line Type : ShortSMF VT Grouping Type : N/AConfigure the line on the SRME in slot 15 for a SDH line type. Check the configuration and note the default values for SDH.
Unknown.7.PXM.a > cnfln -sonet 15.1 -slt 2Unknown.7.PXM.a > dspln -sonet 15.1Line Number : 15.1Admin Status : UpLoopback : NoLoop APS enabled : DisableFrame Scrambling : Enable RDI-V Type : one bitXmt Clock source : loopTiming RDI-P Type : one bitLine Type : sonetStm1 VT Type : vt15/vc11Medium Type(SONET/SDH) : SDH VT Mapping Type : byteSynchronsMedium Time Elapsed : 12099 VT Framing Type : ESFMedium Valid Intervals : 13 VT Signalling Mode : Transfer ModeMedium Line Type : ShortSMF VT Grouping Type : Au3cnfloginmsg
Configure Login Message—PXM45, PXM1E
The cnfloginmsg command lets you create a message that appears when any user logs into the switch.
Syntax
cnfloginmsg
Syntax Description
The interface prompts for a login message. The maximum length is 500 characters. The interface also instructs you to terminate message creation by putting a period on a line with no other characters on that line. See Example.
Related Commands
dsploginmsg, clrloginmsg
Attributes
Example
Create a login message that says, "Call system administrator before using this switch." Complete the message by typing a period on a line. Check the message by using the dsploginmsg command.
M8950_DC.7.PXM.a > cnfloginmsgEnter new Login Message (Less than 500 characters)To complete message enter a line with only a "."Call system administrator before using this switch.Following message will be displayed when user logs in:Call system administrator before using this switchConfirm entry of new message Y/N:(N) yStoring changed Login messageM8950_DC.7.PXM.a > dsploginmsgCall system administrator before using this switchcnfmbsdft
Configure Maximum Burst Size Default—PXM45, PXM1E
Configures the default maximum burst size (MBS) for SPVCs on a port. The applicable service types are real-time and non real-time variable bit rate (rt-VBR and nrt-VBR).
The most likely connection type for which you would use cnfmbsdft is SVC. You can also rely on the value set with this command as a default for SPVCs if you do not specify an MBS through addcon for each SPVC of service type VBR.
The new configuration applies to new incoming calls, not existing calls. You can use cnfmbsdft whether the port is active or in the provisioning state.
Syntax
cnfmbsdft <portid> <service_category> [num-of-cell]:
Syntax Description
portid
The format of the PNNI physical port identifier can vary, as follows:
•
•
–
–
•
For more details, see the section, "PNNI Format," in "Introduction."
service_category
ATM 4.0 service category—either rt-VBR or nrt-VBR.
num-of-cell
The units of measure for MBS are cells.
Range: 0-2147483647 cells
Default: set by the platform to 1024 cells.
Related Commands
dspmbsdft
Attributes
Examples
Configure a default MBS of 10000 cells for nrt-VBR.
cnfmbsdft 11:2.1:1 nrtvbr 10000
cnfname
Configure Name—PXM45, PXM1E
The case-sensitive node name must begin with a letter. It can include:
•
•
•
After you enter the name, the system prompts for confirmation. To see the name, use dspcds (or many of the other node-level display commands): the node name is the first item in the display.
Note
Syntax
cnfname <node name>
Syntax Description
Related Commands
None
Attributes
Example
Configure the node name to be "MGX8850." The system requests you to confirm the name. The CLI prompt returns with the new name. In this example, however, the name as it appears in the prompt is truncated to eight characters because of space limitations for information displayed in the prompt.
NODENAME.7.PXM.a > cnfname MGX8850This node name will be changed to MGX8850. Please ConfirmDo you want to proceed (Yes/No)?MGX8850.7.PXM.a >cnfncdp
Configure NCDP—PXM45, PXM1E
The cnfncdp command lets you change the clock distribution mode at the switch level. The choices are manual mode and Network Clock Distribution Protocol (NCDP). At every switch that you plan to use NCDP, you must enable it through the cnfncdp command. (See Syntax and Syntax Description for the optional parameters.) A switch can use only one distribution mode, and the default mode is manual. The unused mode is disabled. Normally, if you enter a command that applies to the mode that is disabled, the controller rejects the command. Although the two modes are mutually exclusive, the configuration for each mode is saved. If you return a switch to its previous distribution mode, the previous configuration is operational.
Note
For manual clock distribution, use cnfclksrc and related commands to modify, view, or delete clock sources. If you upgrade from Release 2.1 to Release 3 or later software, the switch comes up in manual clock distribution mode and has the previous configuration for manual distribution.
Note
The manual and NCDP modes require some configuration at each switch. Regardless of the mode, a switch can synchronize to any of the following:
•
•
•
If you select NCDP, the optional cnfncdp parameters let you configure as needed the following values:
•
•
•
•
Note
NCDP synchronizes each switch to a single root (or master) clock reference. When you first enable NCDP on more than one switch, it automatically selects the oscillator on one of the switches to be the root of a network clock spanning tree. (On the other hand, if you have pre-configured an external source, NCDP becomes enabled with that source.) When you further configure clock source priorities and a possible BITS device, NCDP again identifies the best source according to your parameter entries.
With each change in NCDP clock state—such as node reset or introduction of a BITS device—it uses the values in the following hierarchy to select a root.
1.
2.
3.
4.
After NCDP determines the default root clock source, it identifies that root to every node in the network.
NCDP ensures that all nodes have a record of the entire spanning clock tree. Thus, each node has a record of the node with the root (or "best") clock source and gets its root source from that node. The maximum number of hops to that master clock node is configurable.
The default clock source under NCDP—a free-running, internal oscillator—is sufficient for a small network. However, the concept of the "best" clock source actually becomes meaningful when you connect a BITS clock or define clocking domains.
Note
To create clocking domains or to configure a BITS clock, NCDP provides the following commands:
•
•
•
–
–
–
Syntax
cnfncdp [ -distributionMode {ncdp | manual] [-maxNetworkDiameter hopcount]
[-hello milliseconds] [-holdtime milliseconds] [-topoChangeTimer milliseconds]Syntax Description
If the distribution mode is manual, only the -distributionMode parameter is meaningful. If you enable NCDP, all other parameters become meaningful.
Related Commands
cnfncdpclksrc, cnfncdpport, delncdpclksrc, dspncdp, dspncdpclksrc, dspncdpclksrcs, dspncdpport, dspncdpports
Attributes
Example
Configure the current switch to be in NCDP mode and set the maximum network diameter to 50.
M8850_LA.8.PXM.a > cnfncdp -distributionMode 1 -maxNetworkDiameter 50cnfncdpclksrc
Configure NCDP Clock Source—PXM45, PXM1E
The cnfncdpclksrc command lets you configure clock sources so that NCDP selects the clock source you want to serve as the best (or root or master) source. The primary use of this command is for specifying external clock sources. To do so, you indicate a high priority and stratum level for the external source. NCDP uses these values to determine the best clock source in the network and build the spanning clock tree. An external source can be a Building Integrated Timing Source (BITS) device connected to a PXM or—much less commonly—a UNI port somewhere on the switch.
Note
External Clock Sources
Even with external sources, you do not need to use the cnfncdpclksrc command at each node (although you must enable NCDP at each node by using the cnfncdp command). You can specify a small number of external sources and, if desired, one or two internal sources as backup for unlikely failure scenarios and leave it to NCDP to utilize the priorities as needed. If every configured source were to fail—leaving all internal oscillators in the network with the same priority—NCDP would use the ATM address of each node as a tie-breaker to select and propagate a root clock.
Internal Clock Sources
You can direct NCDP to select the internal oscillator of a particular node as the root for the following reasons:
•
•
NCDP chooses a node as the best source whether or not you assign a priority to an internal clock. NCDP uses its usual hierarchy of values in the following list to pick a node as the root. In the case of an internal source, the pertinent values are priority and nodal ATM address, as the annotations in the list state:
1.
2.
