Table of Contents

E 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.

e164 address

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

Syntax Description

Command Modes

ATM E.164 translation table configuration

Command History

Usage Guidelines

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.

Examples

The following example shows setting an entry in the ATM E.164 translation table.

election

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]
[relection-timer secs]

no election [leadership-priority] [override-unanimity-timer] [pgl-init-timer]
[reelection-timer]

Syntax Description

Defaults

See "Syntax Description."

Command Modes

PNNI node configuration

Command History

Usage Guidelines

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.

Examples

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

The following example specifies the peer group leadership priority for this node using the default timers.

Related Commands

encapsulation frame-relay

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

no encapsulation frame-relay ietf

Syntax Description

Defaults

None

Command Modes

Interface configuration

Command History

Usage Guidelines

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.

Examples

The following example configures a serial interface for Frame Relay encapsulation type IETF.

Related Commands

epc port-reload

To indicate whether a stuck port should be shut down, or reset and reloaded, use the epc port-reload interface configuration command. To restore the default, use the no form of this command.

epc port-reload

no epc port-reload

Syntax Description

This command has no arguments or keywords.

Defaults

Shutdown mode.

Command Modes

Interface configuration

Command History

Usage Guidelines

The epc port-reload command is used in conjunction with the epc portstuck-wait command for the configuration of stuck port detection and recovery. The epc port-reload command enables automatic resetting and reloading of the Ethernet interface module microcode after detecting a port stuck failure.

The epc portstuck-wait command specifies the delay before signalling a port stuck failure (from the time the failure is detected). The default is 180 seconds. The valid range is 0 to 1200 seconds inclusive. A value of 0 sconds causes a port stuck failure to not be detected.

Together, these two commands provide a mechanism to troubleshoot and recover from port stuck failures. The port-stuck detection mechanism detects a stuck port, and prints a message indicating which port is stuck. The mechanism checks for responses sent by the port to the CPU requests. When the port stops responding to the messages sent by the CPU within a certain time (measured in seconds and configured by the user), it is identified as stuck. If it is only a port stuck failure, the port is isolated from the other functional ports, and Cisco IOS is informed that the line is down/down.

Then, depending on the configuration option for reset of the stuck port, the following action will be taken:

If the switch router is not configured to reset the port upon detecting a port stuck failure, the port will be isolated, thus preserving the integrity of the switch router.

If the switch router is configured to reset the port upon detection of a port stuck failure, the switch router will isolate the port from the rest of the functioning ports, and reset the port. This might affect up to three other ports in the case of Fast Ethernet 10/100 modules.

Note   If you configure the switch router as described in the nondefault behavior after a port stuck failure is detected, the switch router will not reset the Ethernet ports. The Ethernet interface must be configured to reset before the port stuck failure occurs. Also, the default behavior is to not reset the port if a port stuck failure is detected. If the Ethernet interface is not configured to reset when a port stuck failure is detected, schedule the switch router for downtime to remove and reinsert the module.

The following example puts the port in reload mode:

The following example restores the default (shutdown mode):

This command is NOVRAM writeable, and can be verified using the show running-config command.

Related Commands

epc portstuck-wait

To specify the amount of time before signalling a port stuck failure from the time of detection, use the epc portstuck-wait interface configuration command. To restore the default value, use the no form of this command.

epc portstuck-wait [value]

no epc portstuc-wait

Syntax Description

Defaults

Default is 180 seconds (3 minutes).

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is used to configure the amount of time that the port-stuck detection mechanism will wait after the port has stopped responding to the CPU requests, and prior to actually declaring the port to be stuck. The valid range is from 0 to 1200 seconds (20 minutes), with the default value at
180 seconds (3 minutes). A port can be declared stuck only after there is no response to any of the requests made by the CPU within this pre-configured period of time

Caution   Due to the nature of microcode architecture, do not configure low values for the wait time in the epc portstuck-wait command.The default value of 180 seconds has been carefully chosen, allowing for the hello intervals of protocols such as HSRP, EIGRP, OSPF. Configuring a low value might lead to incorrectly detecting temporary port stuck failures as real port stuck failures, and could likely cause temporary connectivity loss. It is highly recommended to keep this value at least at 60 seconds. Lower values are provided to allow for some specific network designs when you can absolutely rule out temporary port stuck failure scenarios, and also as a debugging aid. For most networks, 180 seconds should work very well.

Examples

The following example configures the portstuck-wait time to 240 seconds:

The following example restores the portstuck-wait time to the default of 180 seconds:

Related Commands

epc xpif-ip-per-pack-all

To enable ip per packet load sharing for IP packets on interfaces that have configured IP packet load sharing, enter the epc xpif-ip-per-pack-all global configuration command. To disable ip per packet load sharing, enter the no epc xpif-ip-per-pack-all command.

epc xpif-ip-per-pack-all

no epc xpif-ip-per-pack-all

Syntax Description

None

Defaults

The no epc xpif-ip-per-pack-all setting behavior is enabled by default.

When the no epc xpif-ip-per-pack-all behavior is active, all traffic flows will be forwarded to their destinations without being load balanced unless configured otherwise (for instance, TCP traffic can be configured to per packet load share on an interface by entering the ip load-sharing per-packet interface configuration command and not enabling the epc xpif-ip-per-pack-all command).

Command Modes

Global Configuration

Command History

Usage Guidelines

This command enables per-packet load sharing on the router for all IP traffic for all packet traversing interfaces configured using the ip load-sharing per-packet command. Load sharing is the concept that allows a device to distribute the outgoing and incoming traffic among multiple best paths to a particular destination. Per packet load sharing is configured per interface using the ip load-sharing per-packet command in interface configuration mode. In per packet load sharing, each packet is distributed among multiple best paths to the destination.

The epc xpif-ip-per-pack-all command is required to enable IP per packet load sharing on a device and to active the ip load-sharing per-packet interface configurations for all IP traffic.

When this command is not enabled, traffic flows will be forwarded to their destinations unless configured otherwise (for instance, TCP traffic can be configured to per packet load share on an interface by entering the ip load-sharing per-packet interface configuration command and not enabling the epc xpif-ip-per-pack-all command).

This command is only available for Gigabit Ethernet line cards.

This command can only be used with switches equipped with Enhanced ATM Router Modules. This command cannot be used with switches equipped with standard ATM Router Modules.

Per packet load balancing should not be configured on MPLS-enabled interfaces.

Examples

The following example enables per packet load sharing on the interfaces that have ip load-sharing per-packet enabled:.

Related Commands

erase

To erase flash or configuration memory, use one of the erase privileged EXEC commands.
The erase startup-config command replaces the write erase command.

erase {flash | startup-config}

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

When you use the erase startup-config command, the switch router 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 router deletes the configuration file. That is, the switch router 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.

Examples

The following example deletes the startup configuration file.

Related Commands

exclude-node

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.

exclude-node {name-string | node-id | node-id-prefix} [port hex-port-id | agg-token
hex-agg-token-id]

Syntax Description

Defaults

None

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 exclude-node path entry.

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

Note   To display the node IDs that correspond to named nodes in a network, use either the show atm pnni identifiers 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 hex-port-ids for a node, use either the show atm pnni identifiers command with the port keyword, or the show atm pnni topology command with the node and hex-port-id keywords.

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.

Examples

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

Related Commands