|
|
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 an entry in the ATM E.164 translation table, use the e164 address ATM E.164 translation table configuration command.
e164 address e164-address nsap-address nsap-address
e164-address | Specifies the E.164 address for an entry in the ATM E.164 translation table. The address consists of 7 to 15 decimal digits. See the ITU-T Recommendation E.164 for details on the syntax and semantics of native E.164 addresses. |
nsap-address | Specifies the NSAP-encoded ATM end-system address for an entry in the ATM E.164 translation table. The address is specified as 40 hexadecimal digits. |
ATM E.164 translation table configuration
Each entry in the ATM E.164 translation table specifies a one-to-one correspondence between a native E.164 address and an NSAP-encoded ATM end system-address. Refer to the
atm e164 translation command for more information and usage guidelines about the ATM E.164 translation feature.
The e164 address command is a subcommand of the atm e164 translation-table global configuration command.
The following example shows setting an entry in the ATM E.164 translation table.
Switch# configure terminal Switch(config)# atm e164 translation-table Switch(config-atm-e164)# e164 address 1112222 nsap-address 11.111122223333444455556666.112233445566.11
To configure the PNNI peer group leader election, use the election PNNI node configuration command. To set the election parameters to their defaults, use the no form of this command.
election [leadership-priority number] [override-unanimity-timer secs] [pgl-init-timer secs]
number | Peer group leadership priority that this node should advertise, in the range of 0 to 205. The default is 0. |
override-unanimity-timer | Specifies the amount of time, in seconds, a node will wait to be declared the preferred PGL by unanimous agreement among its peers. This timer is used to prevent nodes from waiting forever for unanimity. The default is 30 seconds. |
pgl-init-timer | Specifies the amount of time, in seconds, allowed to initialize the PGL before starting the election process. This timer is used to ensure that every node casts a vote only after waiting for topology information to propagate across the group. The default is 15 seconds. |
reelection-timer | Specifies the amount of time, in seconds, to wait before the reelection process is restarted after connectivity to the PGL is lost. This timer is used to delay each node in the peer group from voting for the PGL upon loss of connectivity until the nodes in the peer group have received updated topology information. The default is 15 seconds. |
secs | The number of seconds for each timer, in the range of 1 to 120. |
See "Syntax Description."
PNNI node configuration
The node with the highest configured leadership priority in the peer group is normally elected to become the peer group leader. The timers are defined in the PNNI PGL election state machine.
The following example shows how to enter PNNI node configuration mode and specify a node.
Switch# configure terminal Switch(config)# atm router pnni Switch(config-atm-router)# node 1 Switch(config-pnni-node)#
The following example specifies the peer group leadership priority for this node using the
default timers.
Switch(config-pnni-node)# election leadership-priority 1
Before you can use a serial port for Frame Relay, use the encapsulation frame-relay interface configuration command to enable encapsulation on the Frame Relay interface. To disable configuration, use the no form of this command.
encapsulation frame-relay ietf
ietf | Sets the encapsulation method to comply with the IETF standard RFC 1490. |
None
Interface configuration
To correctly support Frame Relay-to-ATM service interworking connections that use translation mode, the Frame Relay interface on the adjacent router must also be configured with IETF encapsulation.
The following example configures a serial interface for Frame Relay encapsulation type IETF.
Switch# configure terminal Switch(config)# interface serial 11/0/0:1 Switch(config-if)# encapsulation frame-relay ietf
show ima interface (Catalyst 8510 MSR and LightStream 1010)
To erase flash or configuration memory, use one of the erase privileged EXEC commands.
The erase startup-config command replaces the write erase command.
flash | Erases internal Flash memory. |
startup-config | Erases the startup configuration in memory. |
Privileged EXEC
When you use the erase startup-config command, the switch erases or deletes the configuration pointed to by the config_file environment variable. The config_file environment variable specifies the configuration file used for initialization. If the config_file environment variable specifies a Flash memory device and configuration filename, the switch deletes the configuration file. That is, the switch marks the file as "deleted."
If you attempt to erase the configuration file specified by the config_file or BOOTLDR environment variables, the system prompts you to confirm the deletion. Also, if you attempt to erase the last valid system image specified in the BOOT environment variable, the system prompts you to confirm the deletion.
The following example deletes the startup configuration file.
Switch# erase startup-config
bert (Catalyst 8510 MSR and LightStream 1010)
cd
dialer-list list
show bootflash:
show startup-config
undelete
To specify a node to exclude from all segments of a partially specified ATM PNNI explicit path,
use the exclude-node PNNI explicit path configuration command.
name-string | Name of the PNNI node to be excluded from all segments of the ATM PNNI explicit path. |
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, specified as a hexadecimal port ID. |
None
PNNI explicit-path configuration
Unlike other explicit-path entries, exclude-node entries do not need to appear in any order.
They apply to all segments on the path.
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.
Normally, aggregation tokens are used in place of port IDs for nodes that are higher level LGNs. However, 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)# segment-target dallas_4Switch(cfg-pnni-expl-path)#segment-target 40:72:47.009181000000106000000000Switch(cfg-pnni-expl-path)#exclude-node st_louis_2
atm pnni explicit-path
next-node
segment-target
show atm pnni explicit-paths
Posted: Thu Feb 17 16:42:14 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.