|
|
The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010. Where an entire command or certain attributes of a command have values specific to a particular switch, an exception is indicated by the following callouts:
To configure a name for a PNNI node, use the name node-level subcommand. To return to the default value, use the no form of this command.
name name
name | Specify the ASCII name for the PNNI node. |
The value assigned by the hostname command.
PNNI node command
The PNNI node name is distributed to all other nodes via PNNI flooding. This allows all PNNI nodes to use this node name in the following PNNI show commands:
This command only applies to PNNI nodes.
For more information, refer to the ATM Switch Router Software Configuration Guide.
The following example configures the node name to be eng_1.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)# name eng_1
hostname
show atm pnni local-node
To specify or replace the ring number of the emulated LAN in the configuration server's configuration database, use the name local-seg-id database configuration command. To remove the ring number from the database, use the no form of this command.
name elan-name local-seg-id seg-num
elan-name | Name of the emulated LAN. The maximum length of the name is 32 characters. |
seg-num | Segment number to be assigned to the emulated LAN. The number ranges from 1 to 4095. |
No emulated LAN name or segment number is provided.
Database configuration
This command is used for Token Ring LANE.
Refer to the lane database command for instructions on how to enter database configuration mode.
The same LANE ring number cannot be assigned to more than one emulated LAN.
The no form of this command deletes the relationships.
The following example specifies a ring number of 1024 for the emulated LAN red.
Switch# configure terminal Switch(config)# lane database eng_dbase Switch(lane-config-database)# name red local-seg-id 1024
delay
llane fixed-config-atm-address
To specify or replace the ATM address of the LANE server for the emulated LAN in the configuration server's configuration database, use the name server-atm-address global database configuration command. To remove it from the database, use the no form of this command.
name elan-name server-atm-address atm-address [restricted | un-restricted] [index n]
elan-name | Name of the emulated LAN. Maximum length is 32 characters. |
atm-address | LANE server's ATM address. |
restricted | un-restricted | Membership in the named emulated LAN is restricted to the LANE clients explicitly defined to the emulated LAN in the configuration server's database. |
index | Priority number. When specifying multiple LANE servers for fault tolerance, you can specify a priority for each server. The highest priority is 0. |
No emulated LAN name or server ATM address is provided.
Database configuration
Use the lane database command to enter database configuration mode.
Emulated LAN names must be unique within one named LANE configuration database.
Specifying an existing emulated LAN name with a new LANE server ATM address adds the LANE server ATM address for that emulated LAN for redundant server operation or simple LANE service replication. This command can be entered multiple times.
The no form of this command deletes the relationships.
The following example configures the example3 database with two restricted and one unrestricted emulated LANs. The clients that can be assigned to the eng and mkt emulated LANs are specified using the client-atm-address command. All other clients are assigned to the man emulated LAN.
Switch# configure terminal Switch(config)# lane database eng_dbase Switch(lane-config-database)# lane database example3 name eng server-atm-address 39.000001415555121101020304.0800.200c.1001.02 restricted name man server-atm-address 39.000001415555121101020304.0800.200c.1001.01 name mkt server-atm-address 39.000001415555121101020304.0800.200c.4001.01 restricted client-atm-address 39.000001415555121101020304.0800.200c.1000.02 name eng client-atm-address 39.0000001415555121101020304.0800.200c.2000.02 name eng client-atm-address 39.000001415555121101020304.0800.200c.3000.02 name mkt client-atm-address 39.000001415555121101020304.0800.200c.4000.01 name mkt default-name man
client-atm-address name
delay
lane database
To select the national bits for E1 IMA interfaces, use the national reserve interface configuration command. To restore the default, use the no form of this command.
national reserve international-bit sa4-bit sa5-bit sa6-bit sa7-bit sa8-bit
international-bit | Specifies the national reserve international bit, either 0 or 1. |
sa4-bit | Specifies the national reserve sa4 bit, either 0 or1. |
sa5-bit | Specifies the national reserve sa5 bit, either 0 or 1. |
sa6-bit | Specifies the national reserve sa6 bit, either 0 or 1. |
sa7-bit | Specifies the national reserve sa7 bit, either 0 or 1. |
sa8-bit | Specifies the national reserve sa8 bit, either 0 or 1. |
1 1 1 1 1 1
Interface configuration
To change the national reserve bit used by the controller, select 0 or 1 for each bit.
The following example sets the national reserve bits for ATM interface 0/0/0:
Switch(config)# interface atm 0/0/0
Switch(config-if)# national reserve 1 1 1 1 1 0
show controllers
To enable NCDP (Network Clock Distribution Protocol) and configure the network clocking hardware of the switch, use the ncdp command. To exit NCDP mode, use the no form of this command.
ncdp [max-diameter hops | revertive |
ncdp | Enables NCDP. |
max-diameter | Specifies the maximum network diameter for the protocol. |
hops | Specifies the maximum distance between any two nodes participating in the protocol, measured in hops. Values are 3 to 255. The default is 20. Each node must be configured with the same max-diameter value for the protocol to operate properly. |
revertive | Configures clock sources to be revertive. When clock sources are configured as revertive, a clock source that is selected and then fails is selected again once it becomes operational. When clock sources are non-revertive (the default), a failed clock source is prevented from being selected again. This nonrevertive behavior only applies to locally configured clock sources. |
source | Configures a clocking source for the given interface. See Table 13-1 for a list of keywords. |
timer | Specifies, in milliseconds, the hello time or hold time for the NCDP protocol. |
hello | Rate at which NCDP hello messages (configuration protocol data units) are sent. Specified in milliseconds. The default is 500. |
hold | Delay between transmission of hello messages. Specified in milliseconds. The default is 500. |
time_in_msec | Hello rate or hold delay time, in milliseconds. The range is 75-60000. |
Disabled
Global configuration
Use the NCDP protocol to configure network clocking hardware to distribute a clock signal through the node (for use by physical interfaces) and to distribute a clock signal between nodes on the network.
When NCDP is enabled, network clock sources are selected by the protocol. When NCDP is disabled, network clock sources are selected according to the definitions entered via the network-clock-select command.Table 13-1 describes the key words by source type.
| Keyword | Description |
|---|---|
priority | Specifies a network-wide priority for the clock source. The range is 1 to 255. |
interface-type | Specifies the interface type as atm or cbr. |
card/subcard/port | Card, subcard, and port number for the ATM interface. |
stratum | The level in the Bellcore stratum hierarchy. (See Bellcore GR-436-CORE and Bellcore |
bits | Displayed and accepted when the platform supports the building integrated timing system (BITS). bits is only displayed or accepted if the system is equipped with a telco module. |
system | Specifies the system clock as the clock source. |
The following example shows how to set the maximum network diameter (number of hops between nodes) to 11.
Switch# configure terminal Switch(config)# ncdp max-diameter 11
The following example shows how to configure clock sources, as follows:
Switch(config)# ncdp source 1 atm 0/0/0 2e Switch(config)# ncdp source 2 BITS 0 2e Switch(config)# ncdp source 3 cbr 0/0/0 3 Switch(config)# ncdp source 1 system
The following example shows how to configure the locally defined clock sources to be revertive.
Switch(config)# ncdp revertive
The following example shows how to configure the NCDP hello timer to 500 milliseconds.
Switch(config)# ncdp timer hello 500
debug ncdp
ncdp (interface)
show ncdp path root
show ncdp ports
show ncdp sources
show ncdp status
show ncdp timers
To enable NCDP and configure the network clocking hardware at the interface level, use the ncdp command. To exit NCDP mode, use the no form of this command.
ncdp [admin-weight weight | control-vc vpi vci]
ncdp | Enables NCDP for the interface. For all ATM NNI interfaces, NCDP is enabled by default. For all other interfaces, NCDP is disabled by default. |
admin-weight | Specifies the cost metric associated with the given port. The default is 10. |
weight | A strictly positive integer in the range 1 to 16777215. |
control-vc | Changes the control virtual circuit used to transport protocol messages between adjacent protocol entities on the given interface. |
vpi vci | Specifies the virtual path identifier and virtual channel identifier. |
Disabled
Interface configuration
Use the NCDP interface-level commands to enable or disable NCDP on the interface or to change interface-level parameters.
NCDP also allows you to enable or disable NCDP on a given port to specify the cost metric associated with a given port and to change the control virtual circuit used to transport protocol messages between adjacent protocol entities on the given interface.
The following example shows how to set a link cost of 75 for ATM interface 0/0/0:
Switch# configure terminal switch(config)# interface atm 0/0/0 switch(config-if)# ncdp admin-weight 75
The following example shows how to change the control virtual circuit used by the protocol to VPI=0, VCI=75.
switch(config)# interface atm 0/0/0 switch(config-if)# ncdp control-vc 0 75
debug ncdp
national reserve (Catalyst 8510 MSR and LightStream 1010)
show ncdp path root
show ncdp ports
show ncdp sources
show ncdp status
show ncdp timers
To allow the recovered clock to specify a particular port to provide network clocking, use the network-clock-select global configuration command. To disable this feature, use the no form of this command.
priority | Specifies the priority between 1 and 4. |
atm | ATM interface. |
cbr | Constant bit rate. |
card/subcard/port | Specifies the card, subcard, and port number of the ATM interface or CBR. |
system | The free running clock provided by the route processor, which is the source for all network derived ports. |
BITS | Selects a BITS port as the network clock source. (Catalyst 8540 MSR) |
E1 | Specifies an E1 interface. (Catalyst 8540 MSR) |
T1 | Specifies a T1 interface. (Catalyst 8540 MSR) |
revertive | Causes the clock to revert to a higher-priority clock if the current clock goes off line. |
System clock
Global configuration
This command applies to all interfaces except older versions of the DS3 interface. The system clock can be selected at any priority.
The following example shows how to configure ATM 3/0/1 as a network clock source of priority 2, and configure ATM 0/1/0 to use a network-derived clock source.
Switch# configure terminal Switch(config)# network-clock-select 2 atm 3/0/1 Switch(config)# interface atm 0/1/0 Switch(config)# clock source network-derived
The following example shows how to configure ATM 0/0/0 as a network clock source of priority 1, and revert to a higher-priority clock.
Switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# network-clock-select 1 atm 0/0/0 Switch(config)# network-clock-select revertive
 | Caution Configure a network clock-source before a port uses it as the clock source. Otherwise, by default, the system clock (route processor resident local oscillator) is used and the transmit clock is configured as network-derived. |
clock source (interface) (Catalyst 8510 MSR and LightStream 1010)
show network-clocks
To specify the next adjacent entry in a fully-specified ATM PNNI explicit path, use the next-node PNNI explicit-path configuration command.
next-node {name-string | node-id | node-id-prefix} [port hex-port-id | agg-token
name-string | Name of the PNNI node. |
node-id | Full 22-byte node-id for a PNNI node. |
node-id-prefix | The first 15 or more bytes of a node ID for a PNNI node. |
port hex-port-id | Specifies an exit port to exclude for a PNNI node. Should be specified as a hexadecimal port ID rather than as a port name. The default is to allow any valid exit port. |
agg-token hex-agg-token-id | Optionally specifies the exit aggregation token, which is used in place of the port ID for higher-level PNNI LGNs. The default is to allow any valid exit port. |
See "Syntax description."
PNNI explicit-path configuration
Node IDs can be entered with either the full 22-byte length address, or as a node ID prefix with a length of 15 bytes or more. To specify routes that include higher-level nodes (parent LGNs) for other peer groups, we recommend that you enter exactly 15 bytes so that the address remains valid in the event of a PGL update.
Node IDs appear in the following format:
dec: dec: 13-20 hex digits
Node names can be entered instead of node IDs. If names are used to identify higher-level LGNs, the resulting explicit paths are not guaranteed to remain valid if the PGL changes in the neighboring peer group. To prevent invalid paths, configure all parent LGNs (for all potential PGL nodes) with the same node name.
An exit port can be specified for any entry. The port should be specified as a hexadecimal port ID rather than as a port name. For excluded entries, only this port is excluded from the path.
Since the port ID could change if the following neighbor peer group changes PGL leaders, the aggregation token is used in place of the port ID for nodes with higher-level LGNs. The LGN aggregation token can only identify the port uniquely if the following entry is the next-node entry. Aggregation tokens are not allowed for excluded tokens.
The following example shows how to perform the following PNNI explicit path configuration tasks:
Switch# configure terminal Switch(config)# atm pnni explicit-path name boston_2.path1 Switch(cfg-pnni-expl-path)# next-node dallas_2 Switch(cfg-pnni-expl-path)# next-node dallas_4 port 80003004 Switch(cfg-pnni-expl-path)# next-node 40:72:47.009181000000106000000000
atm pnni explicit-path
exclude-node
segment-target
show atm pnni explicit-paths
To create, delete, enable, or disable PNNI nodes running on this switch and to specify or change the level of a node, use the node ATM router PNNI configuration command. PNNI node configuration mode is started when this command is entered. To remove a previously set node index, use the no form of this command.
node node_index level level_indicator [lowest] [peer-group-identifier] [pg_id | default]
node_index | Specifies the local node index, in the range of 1 to 8, used to identify a PNNI node. |
level_indicator | Specifies the PNNI level (position in the PNNI hierarchy), in the range of 1 to 104, at which the node exists. |
pg_id | Specifies a non-default peer group identifier for the peer group to which the node belongs. Enter the default keyword in place of an identifier to return from a non-default value to the default peer group identifier. |
lowest | Indicates that the node to be created is a lowest-level node (for example, the node runs over physical links and VPCs). If this is not present when a new node_index is specified, the new node becomes a logical group node that represents a PNNI peer group. A logical group node only becomes active when its child node is elected peer group leader. |
With the ATM switch router autoconfiguration capabilities, a lowest-level PNNI node with the node index 1 is automatically created and runs on all PNNI interfaces by default (including interfaces determined by ILMI to be PNNI interfaces, and on interfaces configured to run PNNI).
The default level is 56, the proper level for lowest-level nodes using autoconfigured Cisco ATM addresses in a single-level hierarchy.
ATM router PNNI configuration
The level of a node can only be modified when the node is disabled.
The enable and disable options can be used to reinitialize PNNI. For example, the node ID and peer group ID are recalculated based on the switch's first ATM address and the node level whenever a node is enabled.
For more information, refer to the ATM Switch Router Software Configuration Guide.
The following example shows how to enter PNNI node configuration mode.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)#
The following example shows how to create a lowest-level PNNI node with node index 1 at level 96 (assuming no node currently exists on this switch).
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 level 96 lowest Switch(config-pnni-node)#
atm address
atm router pnni
show atm pnni local-node
To specify the type of PNNI LGN representation, use the nodal-representation PNNI node configuration command.
nodal-representation {simple | complex [threshold threshold-value | radius-only]}
simple | Specifies the simple PNNI node representation, where an entire child peer group is represented as a single node. |
complex | Specifies the complex PNNI node representation. |
threshold threshold-value | Threshold percent for the generation of bypass or spoke exceptions. The threshold value ranges from 0 to 2147483647 percent. The default threshold is 60 percent. |
radius-only | Advertises radius metrics only with no bypass or spoke exceptions. |
simple
PNNI node configuration
Larger values for the threshold reduce the number of bypass and spoke exceptions advertised by PNNI. If a metric differs from the default metric and the (larger - smaller)/smaller ratio is greater than the threshold percentage, then an exception spoke, or bypass is advertised.
Lowest-level nodes are not allowed to have complex nodal representation.
The radius-only option suppresses all exceptions.
The following example shows how to specify nodal representation for radius only.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 2 Switch(config-pnni-node)# nodal-representation complex radius-only
show atm pnni aggregation link
show atm pnni aggregation node
show atm pnni local-node
Posted: Mon May 8 18:37:45 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.