|
|
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 specify that the configuration server ATM address is computed by the ATM switch router automatic method, use the lane auto-config-atm-address interface configuration command.
To remove the previously assigned ATM address, use the no form of this command.
config | Specifies the configuration server's ATM address. |
No specific ATM address is set.
Interface configuration
This command only applies to the route processor interface ATM 0.
When the config keyword is not present, this command causes the LANE server and LANE client on the subinterface to use the automatically assigned ATM address for the configuration server.
When the config keyword is present, this command assigns the automatically generated ATM address to the configuration server (LECS) configured on the interface. Multiple commands that assign ATM addresses to the LANE configuration server can be issued on the same interface to assign different ATM addresses to the configuration server. These commands include
lane auto-config-atm-address, lane config-atm-address, and llane fixed-config-atm-address.
The following example associates the LANE configuration server with the database named network1, and specifies that the configuration server's ATM address is assigned by the
automatic method.
Switch# configure terminal Switch(config)# interface atm 0 Switch(config-if)# lane database network1 Switch(config-if)# name eng server-atm-address 39.0000014155551211.0800.AA00.1001.02 Switch(config-if)# name mkt server-atm-address 39.0000014155551211.0800.AA00.4001.01 Switch(config-if)# lane config database network1 Switch(config-if)# lane config auto-config-atm-address
lane config-atm-address
lane database
llane fixed-config-atm-address
To specify an ATM address---and override the automatic ATM address assignment---for the broadcast-and-unknown server on the specified subinterface, use the lane bus-atm-address interface configuration command. To remove the ATM address previously specified for the broadcast-and-unknown server on the specified subinterface and thus revert to the automatic
address assignment, use the no form of this command.
atm-address-template | ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, ESI bytes, or selector byte of the automatically assigned ATM address. |
Automatic ATM address assignment
Interface configuration
This command only applies to the route processor interface.
This command gives the client the ATM address of the broadcast-and-unknown server. The client will use this address rather than sending LE_ARP requests for the broadcast address.
When applied to a selected interface but with a different ATM address than used previously,
this command replaces the broadcast-and-unknown server's ATM address.
ATM Addresses. A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address):
Address Templates. LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character, and an ellipsis (...) to match any number of leading or trailing characters.
The values of the digits that are replaced by wildcards come from the automatic ATM assignment method.
In LANE, a prefix template explicitly matches the prefix, but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the Selector field corresponds to the specific subinterface of the interface.
The following example uses an ESI template to specify the part of the ATM address corresponding to the interface; the remaining values in the ATM address come from automatic assignment.
Switch(config-if)# lane bus-atm-address ...0800.200C.1001.**
The following example uses a prefix template to specify the part of the ATM address corresponding to the switch; the remaining values in the ATM address come from automatic assignment.
Switch# configure terminal Switch(config)# interface atm 0 Switch(config-if)# lane bus-atm-address 45.000014155551212f.00.00...
To activate a LANE client on the specified subinterface, use the lane client interface configuration command. To remove a previously activated LANE client on the subinterface, use the no form of this command.
lane client {ethernet | tokenring} [elan-name]
ethernet | Identifies the type of emulated LAN attached to this subinterface as Ethernet. |
tokenring | Identifies the type of emulated LAN attached to this subinterface as Token Ring. |
elan-name | Name of the emulated LAN. This argument is optional because the client obtains its emulated LAN name from the configuration server. Maximum length is 32 characters. |
No LANE clients are enabled on the interface.
Interface configuration
This command only applies to the route processor interface.
If a lane client command has already been entered on the subinterface for a different emulated LAN, the client initiates termination procedures for that emulated LAN and joins the new emulated LAN.
If you do not provide an elan-name value, the client contacts the server to find which emulated LAN to join. If you do provide an emulated LAN name, the client consults the configuration server to ensure that no conflicting bindings exist.
The following example shows how to enable a Token Ring LANE client on a subinterface.
Switch(config)# interface atm 0.1 Switch(config-subif)# lane client tokenring
lane client-atm-address
To specify an ATM address---and override the automatic ATM address assignment---for the LANE client on the specified subinterface, use the lane client-atm-address interface configuration command. To remove the ATM address previously specified for the LANE client on the specified subinterface and revert to the automatic address assignment, use the no form of this command.
lane client-atm-address atm-address-template
atm-address-template | ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, ESI bytes, or selector byte of the automatically assigned ATM address. |
Automatic ATM address assignment
Interface configuration
This command only applies to the route processor interface.
Use of this command on a selected subinterface, but with a different ATM address than used previously, replaces the LANE client's ATM address.
ATM Addresses. A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address):
Address Templates. LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character, and an ellipsis (...) to match any number of leading or trailing characters. The wildcard characters come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix, but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the ATM switch router implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the Selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method for automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Router Products Configuration Guide.
The following example uses an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment.
Switch# configure terminal Switch(config)# interface atm 0 Switch(config-if)# lane client-atm-address ...0800.200C.1001.**
The following example uses a prefix template to specify the part of the ATM address corresponding to the switch; the remaining parts of the ATM address come from automatic assignment.
Switch(config)# interface atm 0 Switch(config-if)# lane client-atm-address 47.000014155551212f.00.00...
To specify a configuration server's ATM address explicitly, use the lane config-atm-address interface configuration command. To remove an assigned ATM address, use the no form of
this command.
atm-address-template | ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, ESI bytes, or selector byte of the automatically assigned ATM address. |
config | Used to specify the configuration server ATM address. |
No specific ATM address or method is set.
Interface configuration
This command only applies to the route processor interface.
If the config keyword is not present, this command causes the LANE server and LANE client on the subinterface to use the specified ATM address for the configuration server.
When the config keyword is present, this command adds an ATM address to the configuration server configured on the interface. A LANE configuration server can listen on multiple ATM addresses. Multiple commands that assign ATM addresses to the LANE configuration server can be issued on the same interface to assign different ATM addresses to the LANE configuration server.
ATM Addresses. A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address) and consists of the following:
Address Templates. LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the ATM address prefix, but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the Cisco implementation of LANE, the prefix corresponds to the switch prefix, the ESI corresponds to a function of ATM interface's MAC address, and the Selector field corresponds
to the specific subinterface of the interface.
For a discussion of the Cisco method of automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter in the Cisco IOS Switching Services Configuration Guide.
lane auto-config-atm-address
lane config database
lane database
llane fixed-config-atm-address
To associate a named configuration table (database) with the configuration server on the selected ATM interface, use the lane config database interface configuration command. To remove the association between a named database and the configuration server on the specified interface, use the no form of this command.
lane config database database-name
database-name | Name of the LANE database. |
No configuration server is defined, and no database name is provided.
Interface configuration
This command only applies to the route processor interface.
This command is not available on a subinterface, because only one LANE configuration server can exist per interface.
The named database must exist before the lane config database command is entered. Refer to the lane database command for more information.
Multiple lane config database commands cannot be entered multiple times on the same interface. You must delete an existing association by using the no form of this command before you create a new association on the specified interface.
To activate a LANE configuration server you need to use the lane config database command and one of the following commands:
lane auto-config-atm-address
lane config-atm-address
lane database
llane fixed-config-atm-address
To specify that the fixed-configuration server ATM address assigned by the ATM Forum is used, use the lane fixed-config-atm-address interface configuration command. To specify that the fixed ATM address is not used, use the no form of this command.
lane [config] fixed-config-atm-address
config | Specifies the configuration server ATM address. |
No specific ATM address or method is set.
Interface configuration
This command only applies to the route processor interface.
When the config keyword is not present, this command causes the LANE server and LANE client on the subinterface to use that ATM address, rather than the ATM address provided by the ILMI,
to locate the configuration server.
When you use this command with the config keyword, and the LECS is a master, the master monitors on the fixed address. If you enter this command when a server is not a master, the server monitors on this address when it becomes a master. If you do not enter this command, the LECS does not monitor on the fixed address.
Multiple commands that assign ATM addresses to the LECS can be issued on the same interface in order to assign different ATM addresses to the LECS. Commands that assign ATM addresses to the LECS include lane auto-config-atm-address, lane config-atm-address, and
llane fixed-config-atm-address. The lane config database command and at least one command that assigns an ATM address to the LECS are required to activate an LECS.
lane auto-config-atm-address
lane config-atm-address
To add a static entry to the LE_ARP table of the LANE client configured on the specified subinterface, use the lane le-arp interface configuration command. To remove a static entry
from the LE_ARP table of the LANE client on the specified subinterface, use the no form of
this command.
mac-address | MAC address to bind to the specified ATM address. |
atm-address | ATM address. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
No static address bindings are provided.
Interface configuration
This command only applies to the route processor interface.
This command only adds or removes a static entry binding a MAC address or next-hop route descriptor (for Token Ring) to an ATM address. It does not add or remove dynamic entries. Removing the static entry for a specified ATM address from an LE_ARP table does not release
the data-direct VCC established to that ATM address. However, clearing a static entry clears any fast-cache entries that were created from the MAC address-to-ATM address binding.
Static LE_ARP entries are not aged and are not removed automatically.
To remove dynamic entries from the LE_ARP table of the LANE client on the specified subinterface, use the clear lane le-arp command.
The following example shows how to add a static entry to the LE_ARP table on the route processor main ATM interface 0.
Switch# configure terminalSwitch(config)#interface atm 0Switch(config-if)#lane le-arp 0800.aa00.0101 47.000014155551212f.00.00.0800.200C.1001.01
clear lane le-arp
To specify an ATM address---and override the automatic ATM address assignment---for the LANE server on the specified subinterface, use the lane server-atm-address interface configuration command. To remove the ATM address previously specified for the LANE server on the specified subinterface and revert to the automatic address assignment, use the no form of this command.
lane server-atm-address atm-address-template
atm-address-template | ATM address or a template in which wildcard characters are replaced by any nibble or group of nibbles of the prefix bytes, ESI bytes, or selector byte of the automatically assigned ATM address. |
The LANE client finds the LANE server by consulting the configuration server.
Interface configuration
This command only applies to the route processor interface.
This command also instructs the LANE client configured on this subinterface to reach the LANE server by using the specified ATM address instead of the ATM address provided by the configuration server.
When used on a selected subinterface, but with a different ATM address than was used previously, this command replaces the LANE server's ATM address.
ATM Addresses. A LANE ATM address has the same syntax as an NSAP (but it is not a network-level address):
Address Templates. LANE ATM address templates can use two types of wildcards:
an asterisk (*) to match any single character, and an ellipsis (...) to match any number of leading
or trailing characters. The values of characters replaced by wildcards come from automatic ATM address assignment.
In LANE, a prefix template explicitly matches the prefix, but uses wildcards for the ESI and
selector fields. An ESI template explicitly matches the ESI field, but uses wildcards for the prefix and selector.
In the LightStream 1010 ATM switch implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the Selector field corresponds to the specific subinterface of the interface.
For a discussion of the Cisco method for automatically assigning ATM addresses, refer to the "Configuring LAN Emulation" chapter of the Router Products Configuration Guide.
The following example uses an ESI template to specify the part of the ATM address corresponding to the interface; the remaining parts of the ATM address come from automatic assignment.
Switch# configure terminal Switch(config)# interface atm 0 Switch(config-if)# lane server-atm-address ...0800.200C.1001.**
The following example uses a prefix template to specify the part of the ATM address corresponding to the switch; the remaining parts of the ATM address come from automatic assignment.
Switch(config)# interface atm 0 Switch(config-if)# lane server-atm-address 45.000014155551212f.00.00...
To enable a LANE server and a broadcast-and-unknown server on the specified subinterface, use the lane server-bus interface configuration command. To disable a LANE server and broadcast-and-unknown server on the specified subinterface, use the no form of this command.
lane server-bus {ethernet | tokenring} elan-name
ethernet | Identifies the type of emulated LAN attached to this subinterface as Ethernet. |
tokenring | Identifies the type of emulated LAN attached to this subinterface as Token Ring. |
elan-name | Name of the emulated LAN. Maximum length is 32 characters. |
No LAN type and emulated LAN name are provided.
Interface configuration
The LANE server and the broadcast-and-unknown server are located on the same switch.
If a lane server-bus command was entered on the subinterface for a different emulated LAN,
the server initiates termination procedures with all clients and comes up as the server for the
new emulated LAN.
Use of the no form of this command removes a previously configured LANE server and broadcast-and-unknown server on the subinterface.
The following example enables a LANE server and broadcast-and unknown server for a
Token Ring ELAN.
Switch# configure terminal Switch(config)# interface atm 0.1 Switch(config-subif)# lane server-bus tokenring
lane server-atm-address
To set the line build-out to various lengths, use the lbo interface configuration command.
To restore the default, use the no form of this command.
For the channelized DS3 port adapter the syntax is:
lbo [short | long]For the channelized E1 and T1 port adapter the syntax is:
lbo [0_110 | 110_220 | 220_330 | 330_440 | 440_550 | 550_660 | gt_600]For the T1 IMA port adapter the syntax is:
lbo {{long {gain26 | gain36} {-15db | -22.5db | -7.5db | 0db}} | {short {133ft | 266ft |For the E1 IMA port adapter the syntax is:
lbo {{long gain43 {120db | 75db}} | {short gain12 22db}}
short | Cable length under 225 feet. |
long | Cable length over 225 feet. |
short | Sets the line build-out up to 255 feet. |
long | Sets the line build-out over 255 feet. |
0_110 | Cable length is 0 to 100 feet. |
110_220 | Cable length is 110 to 220 feet. |
220_330 | Cable length is 220 to 330 feet. |
330_440 | Cable length is 330 to 440 feet. |
440_550 | Cable length is 440 to 550 feet. |
550_660 | Cable length is 550 to 660 feet. |
gt_600 | Cable length is over 600 feet. |
gain26 | 26db gain. |
gain36 | 36db gain. |
-15db | -15 db pulse. |
-22.5db | -22.5 db pulse. |
-7.5db | -7.5 db pulse. |
0db | 0 db pulse. |
133ft | Cable length is 0 to 133 feet. |
266ft | Cable length is 134 to 266 feet. |
399ft | Cable length is 267 to 399 feet. |
533ft | Cable length is 400 to 533 feet. |
655ft | Cable length is 534 to 655 feet. |
gain43 | 43 db gain. |
120db | 120 db gain. |
75db | 75 db gain. |
gain12 | 12 db gain. |
22db | 22 db gain. |
For DS3 interfaces: short
For T1 and E1 interfaces: 110_220
For T1 IMA interfaces: short 133
For E1 IMA interfaces: short gain 12 22db
Interface configuration
The lbo command applies on T1, E1, T1 IMA, E1 IMA, and DS3 interfaces.
The following example illustrates how to set the line build-out for an E1 port adapter to l10.
Switch# configure terminal
Switch(config)# interface atm 3/1/0
Switch(config-if)# lbo 110
show controllers
To select the linecode type for the T1 or E1 line, use the linecode interface configuration command. To revert to the default, use the no form of this command.
linecode {ami | b8zs | hdb3}
ami | Specifies AMI as the linecode type. Valid for T1 or E1 interfaces. |
b8zs | Specifies B8ZS as the linecode type. Valid for T1 interfaces only. |
hdb3 | Specifies HDB3 as the linecode type. Valid for E1 interfaces only. |
For T1 lines: b8zs
For E1 lines: hdb3
Interface configuration
Use this command in configurations where the switch or access server must communicate with
T1 fractional data lines.
The T1 service provider determines which linecode type, either ami or b8zs, is required for your
T1 circuit.
The E1 service provider determines which linecode type, either ami or hdb3, is required for your E1 circuit.
The following example specifies AMI as the linecode type.
Switch# configure terminal Switch(config)# interface atm 3/0/0 Switch(config-if)# lihnecode ami
show controllers
To change the length of time for which data is used to compute load statistics, use the load-interval interface configuration command. To revert to the default setting, use the no form of this command.
load-interval seconds
seconds | Length of time for which data is used to compute load statistics; a value that is a multiple of 30, and between 30 and 600 (30, 60, 90, 120, and so on). |
300 seconds (or 5 minutes)
Interface configuration
This command only applies to the interfaces on the route processor card: Ethernet 0 or ATM 0.
To load computations to be more reactive to short bursts of traffic rather than to those averaged
over 5-minute periods, shorten the length of time over which load averages are computed.
If the load interval is set to 30 seconds, new data is used for load calculations over a 30-second period. This data is used to compute load statistics, including input rate in bits and packets per second, output rate in bits and packets per second, load, and reliability.
Load data is gathered every 5 seconds on the switch. This data is used for a weighted average calculation in which more recent load data has more weight in the computation than older load data. If the load interval is set to 30 seconds, the average is computed for the last 30 seconds of load data.
The load-interval command enables you to change the default interval of 5 minutes to a shorter or longer period of time. If you change it to a shorter period of time, the input and output statistics that are displayed when you use the show interfaces command are more current and are based on instantaneous data, rather than reflecting an average load over a longer period of time.
This command is often used for dial backup purposes to increase or decrease the likelihood of a backup interface being implemented, but it can be used on any interface.
In the following example, the default 5-minute average is set to a 30-second average. A burst in traffic that does not trigger a dial backup for an interface configured with the default 5-minute interval might trigger a dial backup for this interface that is set for a shorter, 30-second interval.
Switch# configure terminal Switch(config)# interface atm 0 Switch(config-if)# load-interval 30
Configure logging for interface link-status event, use the logging event link-status interface configuration command. To disable logging, use the no form of this command.
logging event link-statusThis command has no arguments or keywords.
Disabled
Interface Configuration
The following example shows how to enable logging link-status events on serial interface 11/0/0:1.
Switch# configure terminal Switch(config)# interface serial 11/0/0:1 Switch(config-if)# logging event link-status
show logging
To enable a loopback on the physical device associated with a port, use the loopback interface configuration command. To remove the loop, use the no form of this command.
loopback looptype
looptype | Specifies the loopback type as one of the following: · diagnostic---Transmit data is looped to receive data at the PHY layer. · diagnostic-path---Transmit payload is sent to the receive path overhead processor. · line---Receive signal is looped to transmit at the PHY device. · cell---Cells received by PHY are sent out through the transmit cell in the first-in-first-out order. · payload---Received payload stream is looped through the transmit stream. · pif---Transmit is looped to receive before the cells enter the PHY device. |
No loopback
Interface configuration
The cell and payload loopbacks are only available on DS1/E1 and DS3/E3 interfaces. The diagnostic-path loopback is only available for the OC-12 interface to loop the payload.
The show ima interface (Catalyst 8510 MSR and LightStream 1010) EXEC command is
used to show interfaces currently in loopback operation. To isolate problems in the field, use the diagnostic or line options.
The following example shows how to configure diagnostic loopback on the ATM 3/1/0 line.
Switch# configure terminal Switch(config)# interface atm 3/1/0 Switch(config-if)# loopback diagnostic
show controllers
show ima interface
To enable controller loopback for the channelized DS3 (CDS3) and channelized E1 (CE1)
Frame Relay port adapters, use the loopback controller configuration command. To disable loopback, use the no form of this command.
For the CDS3 Frame Relay port adapter, use the following syntax:
loopback {diagnostic | line | dual | pif}For the CE1 Frame Relay port adapter, use the following syntax:
loopback {diagnostic | line}
diagnostic | The transmit frames are looped back to the switch at the Frame Relay port adapter, as receive frames. |
line | The frames that are received by the ports on the Frame Relay port adapter in the |
dual | This option is similar to a combination of the line and diagnostic loopback options. This option is not available for the CE1 Frame Relay port adapter. |
pif | The cells being sent to the Frame Relay port adapter are looped back towards the switch This option is not available for the CE1 Frame Relay port adapter. |
No loopback
Controller configuration
Use this command for testing, diagnostics, and troubleshooting.
The following example configures the E1 interface to line loopback mode.
Switch# configure terminal Switch(config)# controller e1 11/0/0 Switch(config-controlle)# loopback line
To enable a loopback on the physical device associated with a port, use the loopback interface configuration command. To remove the loop, use the no form of this command.
loopback looptype
looptype | Specifies the loopback type as one of the following: · diagnostic---Transmit data is looped to receive data at the PHY layer. · diagnostic-path---Transmit payload is sent to the receive path overhead processor. · line---Receive signal is looped to transmit at the PHY device. · cell---Cells received by PHY are sent out through the transmit cell in · payload---Received payload stream is looped through the transmit stream. · pif---Transmit is looped to receive before the cells enter the PHY device. |
No loopback
Interface configuration
The cell and payload loopbacks are only available on DS1/E1 and DS3/E3 interfaces. The diagnostic-path loopback is only available for the OC-12 interface to loop the payload.
To show interfaces currently in loopback operation, use the show ima interface (Catalyst 8510 MSR and LightStream 1010) EXEC command. To isolate problems in the field, use the diagnostic or line options.
The following example shows how to configure diagnostic loopback on the ATM 3/1/0 line.
Switch# configure terminal Switch(config)# interface atm 3/1/0 Switch(config-if)# loopback diagnostic
show controllers
show ima interface
Posted: Mon May 8 18:36:41 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.