Table of Contents

N Commands

The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. Where an entire command or certain attributes of a command have values specific to a particular switch or switch router, an exception is indicated by the following callouts:

Refer to Appendix D of this command reference for a detailed list of commands that have been removed, changed or replaced.

name

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

no name

Syntax Description

Defaults

The value assigned by the hostname command.

Command Modes

PNNI node command

Command History

Usage Guidelines

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.

Examples

The following example configures the node name to be eng_1.

Related Commands

name local-seg-id

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

no name elan-name local-seg-id seg-num

Syntax Description

Defaults

No emulated LAN name or segment number is provided.

Command Modes

Database configuration

Command History

Usage Guidelines

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.

Examples

The following example specifies a ring number of 1024 for the emulated LAN red.

Related Commands

name server-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] [preempt]

no name elan-name server-atm-address atm-address [restricted | un-restricted] [index n] [preempt]

Syntax Description

Defaults

No emulated LAN name or server ATM address is provided.

Command Modes

Database configuration

Command History

Usage Guidelines

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.

By default, when a higher-priority LES comes online, it does not preempt the current LES on the same emulated LAN. However, a higher-priority LES configured as preemptable does bump the current LES on the same emulated LAN when the LES comes online.

The no form of this command deletes the relationships.

Examples

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.

Related Commands

national reserve (Catalyst 8510 MSR and LightStream 1010)

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

no national reserve

Syntax Description

Defaults

1 1 1 1 1 1

Command Modes

Interface configuration

Command History

Usage Guidelines

To change the national reserve bit used by the controller, select 0 or 1 for each bit.

Note   This command applies only to E1 IMA.

Examples

The following example sets the national reserve bits for ATM interface 0/0/0:

Related Commands

ncdp (global)

To enable NCDP (Network Clock Distribution Protocol) and configure the network clocking hardware of the switch router, use the ncdp command. To exit NCDP mode, use the no form of this command.

ncdp [max-diameter hops | revertive | source priority {{{atm | cbr} card/subcard/port |
bits {0 | 1}} stratum | system} | timer {hello | hold} time_in_msec] [percentage]

no ncdp [max-diameter hops | revertive | source priority {{{atm | cbr} card/subcard/port |
bits {0 | 1}} stratum | system} | timer {hello | hold} time_in_msec] [percentage]

Syntax Description

Defaults

Disabled

Command Modes

Global configuration

Command History

Usage Guidelines

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 through the network-clock-select command. Table 13-1 describes the key words by source type.

Examples

The following example shows how to set the maximum network diameter (number of hops between nodes) to 11.

The following example shows how to configure clock sources, as follows:

The following example shows how to configure the locally defined clock sources to be revertive.

The following example shows how to configure the NCDP hello timer to 500 milliseconds.

Related Commands

ncdp (interface)

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]

no ncdp [admin-weight weight | control-vc vpi vci]

Syntax Description

Defaults

Enabled for all ATM NNI interfaces.

Disabled for all other interfaces.

Command Modes

Interface configuration

Command History

Usage Guidelines

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.

Examples

The following example shows how to set a link cost of 75 for ATM interface 0/0/0:

The following example shows how to change the control virtual circuit used by the protocol to
VPI=0, VCI=75.

Related Commands

network-clock-select

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.

Catalyst 8540 MSR

network-clock-select priority {{{atm | cbr} card/subcard/port} | system | BITS
{E1 | T1}}revertive

no network-clock-select priority {{{atm | cbr} card/subcard/port} | system | BITS
{E1 | T1}}revertive

Catalyst 8510 MSR and LightStream 1010

network-clock-select priority {{{atm | cbr} card/subcard/port} | system} revertive

no network-clock-select priority {{{atm | cbr} card/subcard/port} | system} revertive

Syntax Description

Defaults

System clock

Command Modes

Global configuration

Command History

Usage Guidelines

This command applies to all interfaces except older versions of the DS3 interface. The system clock can be selected at any priority.

Examples

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.

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.

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.

Related Commands

next-node

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 hex-agg-token-id]

Syntax Description

Defaults

See "Syntax Description."

Command Modes

PNNI explicit-path configuration

Command History

Usage Guidelines

Note   See the atm pnni explicit-path command for a description of how to edit or delete an existing next-node path entry.

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

Note   To display the node IDs that correspond to named nodes in a network, use either the show atm pnni identifier command or the show atm pnni topology command with the node keyword.

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.

Note   To display the corresponding hexadecimal port IDs for a node, use either the show atm pnni identifier command with the port keyword, or the show atm pnni topology command with the node and hex-port-id keywords.

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.

Note   Normally, the first next-node entry should specify an adjacent neighbor node. However, if an exit port needs to be specified for the local node, it can appear as entry index 1.

Examples

The following example shows how to perform the following PNNI explicit path configuration tasks:

Related Commands

node

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]
[enable | disable]

no node node_index

Syntax Description

Defaults

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.

Command Modes

ATM router PNNI configuration

Command History

Usage Guidelines

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 router'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.

Examples

The following example shows how to enter PNNI node configuration mode.

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 router).

Related Commands

node mobile

To create, delete, enable, or disable nodes running on the mobile switch, and to specify or change the level of a node, use the node ATM router PNNI configuration command. Also use this command to designate the highest node in this switch as a mobile logical group node.

node node_index mobile [default-peer-group-identifier mobile_pgid ] [highest-join-level join_level] [disable | enable]

no node node_index mobile [default-peer-group-identifier mobile_pgid ] [highest-join-level join_level]

Syntax Description