|
|
This appendix describes the commands and tasks specific to your Cisco 6400, for both the NRP and the NSP. The tasks are presented only in the context of using a particular command; it does not describe how the tasks interrelate, nor does it provide comprehensive configuration examples.
Additional commands used to configure the NRP are detailed in the Release 12.0 Cisco IOS Configuration publications; additional commands used to configure the NSP are detailed in the ATM Switch Router Command Reference. All documents and guides are available at Cisco Connection Online (CCO) or on CD-ROM.
Figure A-1 explains the fields of a typical command reference page.
To specify the virtual template to use for cloning new virtual-access interfaces when an incoming tunnel connection is requested from a specific peer, use the accept dialin VPDN group command. To disable authentication and virtual template cloning, use the no form of this command.
accept dialin [l2f | l2tp | any | pppoe] virtual-template number [remote remote-peer-name]
no accept dialin [l2f | l2tp | any | pppoe] virtual-template number [remote remote-peer-name]
l2f | l2tp | any | pppoe | (Optional) Indicates which protocol to use for a dial-in tunnel. · l2f---Layer 2 Forwarding protocol. · l2tp---Layer 2 Tunnel Protocol. · any---VPDN will use autodetect to select either L2F or L2TP. Does not apply to PPPoE. · pppoe---Point-to-Point Protocol over Ethernet. |
virtual-template number | The virtual template interface from which the new virtual-access interface is cloned. |
remote remote-peer-name | (Optional) Case-sensitive name that the remote peer will use for identification and tunnel authentication. Does not apply to PPPoE. |
Disabled
VPDN group mode
This command replaces the vpdn incoming command used in Cisco IOS Release 11.3. The user interface will automatically be upgraded when you reload the router with a 12.0 T image.
When used with L2F or L2TP, the router replies to a dial-in layer 2 tunnel open request from the specified peer. When the access server accepts the request, it uses the specified virtual template to clone new virtual-access interfaces.
When used with PPPoE, the accept dialin command enables the router to accept incoming PPPoE discovery packets from clients and establish PPPoE sessions with them. After the PPPoE discovery stage completes, PPPoE uses the specified virtual template to clone new virtual-access interfaces. If a pre-cloned virtual-access interface is available in PPPoE private list, PPPoE would use that virtual-access interface to establish a PPP session with the client.
The following example allows the access server to accept a PPPoE dial-in tunnel. A virtual-access interface will be cloned from virtual-template 1:
accept dialin pppoe virtual-template 1
If you use the accept dialin command with the pppoe and virtual-template keywords and omit the remote-peer-name argument, you automatically enable a default PPPoE VPDN group, which allows all tunnels to share the same tunnel attributes:
vpdn-group 1 ! Default PPPoE VPDN group accept dialin pppoe virtual-template 1
vpdn incoming
To clear all of the APS priority requests created by the aps signal-degrade, aps lockout, aps force, and aps manual commands, use the aps clear EXEC command.
aps clear atm slot/subslot/port
slot/subslot/port | Specifies the ATM interface for which you want all APS priority requests cleared. |
None
EXEC configuration
This command applies to the Cisco 6400 NSP only.
The aps clear EXEC command allows you to remove all of the APS priority requests on the named ATM interface.
In the following example, all of the current APS priority requests on ATM 2/0/1 are cleared.
Switch# aps clear atm 2/0/1
aps force
aps lockout
aps manual
To force an interface to switch to the alternate port within a redundant pair, use the aps force EXEC command.
aps force atm slot/subslot/port from [protection | working]
slot/subslot/port | Specifies the interface you want to affect. |
from protection | Specifies that you want to switch from the protection port to the working port. |
from working | Specifies that you want to switch from the working port to the protection port. |
None
EXEC mode
This command applies to the Cisco 6400 NSP only.
Force is a defined APS request priority level. The request succeeds if no higher priority request (lockout is the only higher priority request) is posted. The aps force command does not persist over a system restart. The port type named in the command indicates the member of the redundant port pair that you want to switch away from.
For more information about APS priority requests, see the Telcordia GR-253-CORE specification.
The following example shows the ATM 1/1/1 interface being forced to switch from the working port to the protection port within the defined redundant pair.
Switch# aps force atm 1/1/1 from working
aps clear
aps lockout
aps manual
To lock out the protection port within a redundant pair, use the aps lockout EXEC command.
aps lockout atm slot/subslot/port
slot/subslot/port | Specifies the interface you want to affect. |
None
EXEC mode
This command applies to the Cisco 6400 NSP only.
Lockout is defined as the highest APS request priority level. The aps lockout command does not persist over a system restart. When the protection port is locked out, only the working port is used for the specified interface.
For more information about APS priority requests, see the Telcordia GR-253-CORE specification.
In the following example, the ATM 1/1/1 interface is forced to use the working port within the defined redundant pair.
Switch# aps lockout atm 1/1/1
To post an APS request that switches an interface to the alternate port within a redundant pair, use the aps manual EXEC command.
aps manual atm slot/subslot/port from [protection | working]
slot/subslot/port | Specifies the interface you want to affect. |
from protection | Specifies that you want to switch from the protection port to the working port. |
from working | Specifies that you want to switch from the working port to the protection port. |
None
EXEC mode
This command applies to the Cisco 6400 NSP only.
Manual is a defined APS request priority level. The request succeeds if no higher priority request is posted. The aps manual command does not persist over a system restart. The port type named in the command indicates the member of the redundant port pair that you want to switch away from.
Table A-1 lists the priority requests, relevant to the Cisco 6400, that are higher than manual.
| Priority | Priority request |
|---|---|
1 | Lockout of protection |
2 | Forced switch |
3 | SF - Low priority |
4 | SD - Low priority |
5 | Manual switch |
For a complete list of priority requests, see Table 5.3 of the Telcordia GR-253-CORE specification.
In the following example, the ATM 1/1/1 interface is switched from the working port to the protection port within the defined redundant pair, provided that no higher priority request is posted.
Switch# aps manual atm 1/1/1 from working
To set the APS operational mode on a Cisco 6400 for a pair of redundant ports, use the aps mode interface command. To remove the APS operational mode, use the no associate command.
aps mode {linear 1+1 nonreverting unidirectional}
linear 1+1 nonreverting unidirectional | Specifies that the APS operation between the two redundant ports for the interface is linear, 1+1, nonreverting, and unidirectional. |
On
Interface configuration
This command applies to the Cisco 6400 NSP only.
The linear 1+1 nonreverting unidirectional mode is the only APS mode currently supported on the Cisco 6400.
There is only one logical interface for a pair of redundant ports. The APS configuration commands are accepted only on an interface that represents a redundant pair of ports. If the redundancy between ports is removed through use of the no associate command, two interface configuration sections are created, but the APS configuration commands are removed from both.
The aps mode must be set before the other aps commands can be entered.
In the following example, the ATM interface 1/0/0 is configured for linear APS operation.
Switch(config)# interface atm 1/0/0 Switch(config-if)# aps mode linear 1+1 nonreverting unidirectional
To set the bit-error-rate threshold for signal degrade APS priority posting, use the aps signal-degrade interface configuration command. To remove the BER threshold, use the no form of this command.
aps signal-degrade BER threshold value
BER threshold | Specifies the name of the priority request for which you are setting a threshold. |
value | Specifies the value of the threshold, which is 10-x, where x is 5, 6, 7, 8, or 9. |
None
Interface configuration
This command applies to the Cisco 6400 NSP only.
For a complete list of priority requests, see Table 5.3 of the Telcordia GR-253-CORE specification.
In the following example, the BER threshold for the ATM 1/0/1 interface is set to 9.
Switch(config)# interface atm 1/0/1 Switch(config-if)# aps signal-degrade BER threshold 9
aps signal-fail
aps mode
show aps
show controllers
To set the bit-error-rate threshold for signal fail APS priority posting, use the aps signal-fail interface configuration command. To restore the default BER threshold, use the no form of this command.
aps signal-fail BER threshold value
BER threshold | Specifies the name of the priority request for which you are setting a threshold. |
value | Specifies the value of the threshold, which is 10-x, where x is 3, 4, or 5. |
The default BER threshold is 10-3.
Interface configuration
This command applies to the Cisco 6400 NSP only.
For a complete list of priority requests, see Table 5.3 of the Telcordia GR-253-CORE specification.
In the following example, the BER threshold for the ATM 1/0/1 interface is set to 5.
Switch(config)# interface atm 1/0/1 Switch(config-if)# aps signal-fail BER threshold 5
aps signal-degrade
aps mode
show aps
show controllers
To list the contents of a UNIX-style tar archive or to extract its contents, use the archive tar privileged EXEC command.
archive tar /table URL
/table | Lists the contents of the tar archive. |
URL | Specifies the location of the tar archive you want to list. |
/xtract | Extracts the contents of the source tar archive to the destination given. |
source | Specifies the source of the tar file you want to extract. |
destination | Specifies the destination of the tar file you want to extract. Usually installed from Flash disk on the NSP. |
None
Privileged EXEC
This command applies to the Cisco 6400 NSP only.
This command is mostly used to unpack updated Web Console pages. The Cisco 6400 is shipped with current Web Console HTML pages, however, from time to time you might want to download new or updated pages. The new pages will be stored in a tar archive that you must unpack with the archive tar command before viewing.
The following example shows how to extract files on the TFTP server named boothost and install them on the disk located in slot 0 on the NSP:
Switch# archive tar /xtract tftp://boothost/6400/c6400s-html.tar disk0:
To group two slots or two subslots for redundant operation, use the associate redundancy subcommand. To remove the redundancy, use the no form of this command.
associate {slot | slot/subslot} [slot | slot/subslot ] [slot | slot/subslot ]
slot | Specifies that redundancy is set between two slots. |
subslot | Specifies that redundancy is set between two subslots. |
slot/subslot | Specifies the slot and subslot number for the first member of a redundant pair. You do not need to specify the second member of the pair because only adjacent devices can be configured as redundant. |
No redundancy
Redundancy configuration
This command can be entered only from the Cisco 6400 NSP.
The associate command must be entered in redundancy configuration mode. Redundant pairs consist of the odd-numbered slot and the following even-numbered slot. For example, slots 1 and 2 can be configured as a redundant pair but slots 2 and 3 cannot be configured as a redundant pair. The same applies to redundant subslots. For example, subslots 7/1 and 8/1 can form a redundant pair.
When you use the associate command for two slots, it implies that the related subslots are also associated and behave in a redundant manner.
In the following example, Cisco 6400 slots 1 and 2 are configured for redundant operation. You need only specify the first member of a redundant pair.
Switch(config)# redundancy Switch(config-r)# associate slot 1
To configure an interface to use ATM routed bridging, use the atm route-bridge interface configuration command.
atm route-bridge protocol
protocol | Protocol to be route-bridged. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(5)DC | This command was first introduced. |
The following example configures ATM routed bridging on an interface:
Router(config)# interface atm 4/0.100 point-to-point Router(config-if)# ip address 172.69.5.9 255.255.255.0 Router(config-if)# pvc 0/32 Router(config-if)# atm route-bridged ip
To automatically synchronize the configuration between the Cisco 6400 primary and secondary redundant NSPs and NRPs, use the auto-sync redundancy subcommand. To disable automatic synchronization between redundant NSPs or NRPs, use the no form of this command.
auto-sync {startup-config | bootvar | config-register | standard}
startup-config | Specifies that the startup configuration be synchronized between the two redundant NSPs. |
bootvar | Specifies that the boot variables be synchronized between the two redundant NSPs. Boot variables are ROMMON environment variables used to control the booting process. |
config-register | Specifies that the configuration register be synchronized between the two redundant NSPs. The configuration register, stored in NVRAM, contains startup time parameters for the system. |
standard | Specifies that all objects be synchronized between the two redundant NSPs. In this case, all objects are the startup configuration, the bootvar, and the configuration register. |
No synchronization for individual objects. Standard is the default when auto-synchronization is enabled.
Main-cpu redundancy configuration
To ensure that the configurations are identical between redundant NSPs or NRPs, you must use the auto-sync command. Otherwise, when operation changes from the primary to the secondary device, the operation of the switch or router might change if the configurations differ from one member of the redundant pair to the other.
The following example shows how to configure automatic synchronization of the startup configuration between redundant NSPs.
Switch# redundancy Switch(config-r)# main-cpu Switch(config-r-mc)# auto-sync startup-config
To set the current port snooping configuration and actual register values for the highest ATM interface, use the atm snoop interface atm interface configuration command.
atm snoop interface atm monitored-port [direction dir]
monitored-port | Slot, subslot, and port number for the ATM interface to be monitored. The port can be any port except the NSP ATM 0/0/0 port or the test port. |
dir | Specified as receive or transmit and determines the direction of the cell traffic to monitor. |
Receive
Interface configuration on the snoop test port.
The atm snoop interface atm subcommand applies only if the previously specified port is the highest system port residing on card 8 and subcard 1 (which has been shut down). If these conditions are met, the subcommand enables the snoop test port. Cells transmitted from the snoop test port are copies of cells transmitted to or from the monitored port. Transmissions in only one direction are captured.
When a port is in snoop mode, any prior permanent virtual connections to the snoop test port remain in the down state.
The port number of the test port depends on the card type.
The following example shows how to configure the highest port in the snoop mode to monitor port card 1, subcard 0, and port 1 in the transmit direction starting from the configuration mode.
Switch(config)# interface atm 8/1/1 Switch(config-if)# shutdown Switch(config-if)# atm snoop interface atm 1/0/1 direction transmit Switch(config-if)# no shutdown
show atm snoop
To clear the external alarm relays or the device memory for the requested alarm level or source reported on a Cisco 6400, use the clear facility-alarm EXEC command.
clear facility-alarm [major | minor | critical] [source {sec-cpu | pem {0 | 1} |
major | Specifies that all major alarms be cleared. |
minor | Specifies that all minor alarms be cleared. |
critical | Specifies that all critical alarms be cleared. |
source | Specifies the source of an alarm. |
sec-cpu | Specifies the source of the alarm you want to clear as the secondary CPU. There is no other way to clear an alarm on this device. |
pem | Specifies the source of the alarm you want to clear as one of the redundant power modules, either 0 or 1. There is no other way to clear an alarm on this device. |
cardtype slot/subslot | Specifies the source of the alarm you want to clear as the device installed in the specified slot or subslot. There is no other way to clear an alarm on this device. |
If no operator is specified, all external alarms are cleared.
EXEC
The clear facility-alarm command clears all of the specified external alarm indications. The alarm condition is still posted and can be seen by use of the show facility-alarm status command, and the LEDs are still illuminated. To clear the alarm status, you must remove the alarm condition at its source by specifying an alarm source with this command. When a source is specified, the memory of the specified device is cleared, thereby clearing the source of the alarm.
In the following example, only the minor alarms are cleared.
Switch> clear facility-alarm minor
facility-alarm
show facility-alarm status
To enter explicit threshold temperatures for minor and major alarms, use the facility-alarm global configuration command. To disable the alarm for the minor or major temperature threshold, use the no form of this command.
facility-alarm [intake-temperature | core-temperature] [minor {°C}] [major {°C}]
intake-temperature | Specifies the minor and major temperature thresholds for the reading at the intake airflow. |
core-temperature | Specifies the minor and major temperature thresholds for the reading at the core of the chassis. |
minor | Specifies the temperature threshold for the minor alarm in degrees Celsius. If no value is specified, the threshold is reset to the default value. |
major | Specifies the temperature threshold for the major alarm in degrees Celsius. If no value is specified, the threshold is reset to the default value. |
Disabled
Global configuration
The Cisco 6400 environmental monitoring hardware includes a digital thermometer that measures the intake airflow temperature at the hottest section of the chassis. The minor, major, and critical temperature defaults are empirically determined values that vary depending on the number and type of cards installed in the chassis. The facility-alarm command allows you to override the empirically determined default values. The no form of this command allows you to disable alarms for the selected alarm type.
Critical alarms cannot be disabled and the threshold cannot be changed. These alarms are defined as those that are triggered just before the system powers itself off.
In the following example, a setting is selected for the chassis core temperature at which a major alarm will be triggered.
Switch(config)# facility-alarm core-temperature major 105
clear facility-alarm
show facility-alarm status
To reset a device installed in a slot or subslot on a Cisco 6400, use the hw-module command. To remove an indefinite reset on a slot or subslot, use the no hw-module shutdown configuration command.
hw-module {slot | slot/subslot | main-cpu | sec-cpu | nsp {A | B}} reset [hold | release]
slot/subslot | Specifies the number of the slot or subslot that identifies the device that will be reset. |
reset | Specifies that the slot or subslot should be reset. |
main-cpu | Specifies that the main CPU should be reset. Allows you to reset the main CPU regardless of the CPU you are currently logged into. |
sec-cpu | Specifies that the secondary CPU should be reset. Allows you to reset the secondary CPU regardless of the CPU you are currently logged into. |
hold | Specifies that the slot or subslot should be held in reset indefinitely. This option is only available in the service internal mode. |
release | Specifies that the slot or subslot should be released from the reset state. This option is only available in the service internal mode. |
shutdown | When used with the no form, the shutdown option releases the reset state. |
Disabled
EXEC or global configuration
This command applies to the Cisco 6400 NSP only.
When entered from the EXEC, this command causes an immediate reset of the device installed in the specified slot, subslot, or CPU. When a port is reset, all of the input/output hardware associated with the port is reset. If a slot is reset, both of the cards installed in the associated subslots are reset. This operation is different from resetting an IOS interface by means of the shutdown command. Typically, the hw-module command results in the card rebooting. If the card is the primary member of a redundant pair, the current secondary card might become the primary.
The reset hold option keeps the specified card in reset indefinitely. To release a card from the hold state, use the reset release form of the EXEC command.
When entered from the configuration mode, this command holds the slot or subslot in reset at system boot time. To release the card from the reset state, use the no hw-module shutdown command.
The no shutdown form of this command releases the slot or subslot from the reset state, whether the slot was held in reset by a configuration command at boot time or by an EXEC command.
In the following example, one of the NSP cards is reset.
Switch# hw-module nsp A
To configure an interface type and enter interface configuration mode, use the interface global configuration command.
interface type slot/subslot/portTo configure a subinterface, use the interface global configuration command.
interface type slot/subslot/port.vpt#
type | Type of interface to be configured. Refer to Table A-2 for a list of keywords. |
number | Integer used to identify the interface. |
slot | Interface slot number. The numbers are assigned at the factory at the time of installation or when the card is added to a system. The number can be displayed with the show interface command. The slots are numbered from left to right. |
subslot | Backplane subslot number. The value can be 0 or 1. |
port | Port number of the interface. |
.vpt | Virtual path tunnel number for subinterface on physical ATM ports. |
.subinterface | Subinterface number in the range 1 to 4,294,967,293. The number that precedes the period (.) must match the subinterface number. |
multipoint | Specifies a multipoint subinterface. This option applies only to the interface ATM 0/0/0. |
point-to-point | Specifies a point-to-point subinterface. The default is multipoint. This option applies only to the interface ATM 0/0/0. |
Global configuration
For information or output for the NRP interface atm command, refer to the Cisco IOS 12.0 Wide-Area Networking Command Reference.
| Keyword | Interface Type |
|---|---|
async | Auxiliary port line used as an asynchronous interface. |
atm | ATM interface. |
bvi | Bridge-group virtual interface. |
dialer | Dialer interface. |
ethernet | Ethernet IEEE 802.3 interface. |
group-async | Master asynchronous interface. |
lex | Lex interface. |
loopback | Software-only loopback interface that emulates an interface that is always running. It is a virtual interface supported on all platforms. The interface number is the number of the loopback interface you want to create or configure. There is no limit on the number of loopback interfaces you can create. |
null | Null interface. |
tunnel | Tunnel interface, used to declare a TSP tunnel interface. The tunnel interface number is in the range 0 to 65535. |
virtual-template | Virtual template interface. |
virtual-tokenring | Virtual Token Ring interface. |
vlan | Catalyst 5000 VLAN interface. |
The following example shows the start of the ATM interface on slot 1, subslot 0, and port 1 configuration using the interface global configuration command:
Switch(config)# interface atm 1/0/1 Switch(config-if)#
In the following example, a VP tunnel is created with VPI 50 on slot 1, subslot 0, and port 1. The subinterface configuration mode is entered for the VP tunnel, through use of the interface global configuration command:
Switch(config)# interface atm 1/0/1 Switch(config-if)# atm pvp 50 Switch(config-if)# interface atm 1/0/1.50 Switch(config-subif)#
In the following example, configuration is begun on the NRP interface ATM 0/0/0, through use of the interface global configuration command:
Router(config)# interface atm 0/0/0 Router(config-if)#
In the following example, the interface global configuration command is used to create a point-to-point subinterface on the NRP ATM 0/0/0 interface and enter the subinterface configuration mode:
Router(config)# interface atm 0/0/0.1 point-to-point Router(config-subif)#
In the following example, configuration of the BVI 1 interface on the NSP is begun through use of the interface global configuration command:
Switch(config)# interface bvi 1 Switch(config-if)#
show interface
To set a primary or secondary IP address for an interface or to use DHCP to set the interface address, use the ip address interface configuration command. To remove an IP address or disable IP processing, use the no form of this command.
ip address [ip-address mask [secondary] | negotiated]
ip-address | IP address. |
mask | Mask for the associated IP subnet. |
secondary | Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address. |
negotiated | Specifies the use of DHCP to obtain the IP address, subnet mask, and default route. |
Negotiated.
Interface configuration
The negotiated (default) option for this command allows the system to act as a DHCP client and automatically set the IP address, subnet mask, and default route for the specified interface. On the NSP, this command applies only to the Ethernet 0/0/0 and ATM 0/0/0 interfaces.
You can disable IP processing on a particular interface by removing its IP address with the no ip address command. If the switch detects another host using one of its IP addresses, it prints an error message on the console.
The optional keyword secondary allows you to specify an unlimited number of secondary addresses. Secondary addresses are treated like primary addresses, except the system never generates datagrams other than routing updates using the secondary source addresses. IP broadcasts and ARP requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
In the following example, 172.31.1.27 is the primary address and 192.168.7.17 and 192.168.8.17 are secondary addresses for Ethernet interface 0/0/0:
Switch(config)# interface ethernet 0/0/0 Switch(config-if)# ip address 172.31.1.27 255.255.255.0 Switch(config-if)# ip address 192.168.7.17 255.255.255.0 secondary Switch(config-if)# ip address 192.168.8.17 255.255.255.0 secondary
show interface
To switch to the main-cpu submode of the redundancy mode, use the main-cpu redundancy command.
main-cpuThis command has no arguments or keywords.
Redundancy
After you enter the main-cpu submode, you can use the auto-sync command to synchronize the configuration between the primary and secondary route processors based on the primary configuration. In addition, you can use all of the redundancy commands that are applicable to the main CPU.
The following example shows how to switch to the main-cpu submode of redundancy mode.
Switch(config)# redundancy Switch(config-r)# main-cpu Switch(config-r-mc)#
aps mode
auto-sync
redundancy
show redundancy
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.
network-clock-select [priority {atm slot/subslot/port | system} | revertive]
priority | Specifies a priority between 1 and 4. |
atm | Specifies the type of interface. |
slot/subslot/port | Specifies the card, subcard, and port number of the ATM interface. |
system | The free running clock provided by the NSP is the source for all network derived ports. |
revertive | Specifies that if a higher priority clock source fails, the next priority clock is used until the first clock source comes back on line. |
System clock
Global configuration
This command applies to all ATM interfaces on the Cisco 6400 NSP. If the no network-clock-select revertive command is used, the clock source does not return to the original source after it has switched to a lower priority clock source, even if the original clock source comes back on line.
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 to configure ATM 1/1/0 to use the network-derived clock source.
Switch# configure terminal Switch(config)# network-clock-select 2 atm 3/0/1 Switch(config)# interface atm 1/1/0 Switch(config)# clock source network-derived end
 | Caution Configure a network clock source before a port uses it as the clock source. Otherwise, by default, the system clock (NSP-resident local oscillator) is used, and the transmit clock is configured as network-derived. |
show network-clocks
To limit the number of PPPoE sessions that can originate from a single MAC address, use the pppoe limit per-mac command.
pppoe limit per-mac number
number | The maximum number of PPPoE sessions for a single MAC address. |
100
Global configuration
The following example places a limit of 5 PPPoE sessions per MAC address:
Router(config)#pppoe limit per-mac 5
pppoe limit per-vc
To limit the number of PPPoE sessions that can be established on a VC, use the pppoe limit per-vc command.
pppoe limit per-vc number
number | The maximum number of PPPoE sessions for a VC. |
100
Global configuration
The following example places a limit of 50 PPPoE sessions per VC:
Router(config)#pppoe limit per-vc 50
pppoe limit per-mac
To select the NAS port format used for RADIUS accounting features, use the radius-server attribute nas-port format global configuration command. To restore the default NAS port format, use the no form of this command.
[no] radius-server attribute nas-port format format
format | Choose one of the following keywords: a---Standard NAS port format. b---Extended NAS port format. c---Shelf-slot NAS port format. d---ATM VC extended NAS port format. |
Standard NAS port format.
EXEC
| Release | Modification |
|---|---|
11.3(7)T | This command was first introduced. |
11.3(9)DB | The d format was added. |
The radius-server attribute nas-port format command configures RADIUS to change the size and format of the NAS port attribute field (RADIUS IETF Attribute 5).
In the following example, a RADIUS server is identified, and the NAS port field is set to ATM VC extended format:
Router# radius-server host 172.31.5.96 auth-port 1645 acct-port 1646 Router# radius-server attribute nas-port format d
raduis-server host non-standard
To configure two full-height slots, two half-height slots, or the main CPU for redundant operation, use the redundancy global configuration command. The redundancy command starts a configuration submode, where the redundant configuration is specified.
redundancyNone
Disabled
Global configuration
The redundancy command starts a configuration submode for setting slot and subslot redundancy. The exact redundancy implementation between a pair of redundant entities is a property of the objects actually installed in the chassis.
Only adjacent (odd and even) slot pairs can be configured for redundancy. When a slot is configured for redundancy, both of the subslots, if there are any, are automatically configured for redundancy. When subslots are configured for redundancy, all ports on the two subslots are redundant.
The following example shows how to configure the two Cisco 6400 NRPs installed in slots 1 and 2 for redundant operation:
Switch(config)# redundancy Switch(config-r)# associate slot 1
aps mode
main-cpu
redundancy force-failover
show redundancy
To force the current primary and secondary devices in a redundant pair to change roles, use the redundancy force-failover EXEC command.
redundancy force-failover {slot | slot/subslot | slot/subslot | main-cpu}
slot/subslot/ | Specifies the slot or subslot for one member of a redundant pair, where the primary/secondary relationship between the two entities is reversed. |
main-cpu | Specifies that the primary/secondary relationship between the two available NSPs be reversed. |
Disabled
EXEC
The redundancy force-failover command can be used to force a change in the primary/secondary relationship required for software and hardware upgrade situations. This command has no effect on interfaces that are running in SONET linear 1+1 nonreverting unidirectional APS mode. To reverse the roles of two redundant ports, use the aps force command.
This command does not generate an alarm (as a hardware reset would).
In the following example, the primary/secondary relationship is reversed between the router card in slot 2 and its redundant partner. The other slot in the redundant pair is not specified in this command. You can use the show redundancy command to view the configured redundant pairs.
Switch# redundancy force-failover slot 2
To display the SONET APS configuration for each redundant interface, use the show aps command.
show apsEXEC
This command displays the APS status of all cards configured for APS mode linear 1+1 nonreverting unidirectional operation. The output is closely associated with the generation of K1/K2 bytes transmitted from the redundant interface.
The following is sample output from the show aps EXEC command.
Switch# show aps
ATM7/0/0: APS Lin NR Uni, Failure channel: Protection
Active Channel: CHANNEL7/0/0, Channel stat: Good
Port stat (w,p): (Good, Good)
ATM7/0/1: APS Lin NR Uni, Failure channel: Protection
Active Channel: CHANNEL7/0/1, Channel stat: Good
Port stat (w,p): (Good, Good)
Table A-3 describes the fields shown in the display.
| Field | Description |
|---|---|
APS | This interface is operating in APS mode. (Default configuration.) |
Lin | This interface is operating in linear mode. (Default configuration.) |
NR | This interface is operating in nonreverting mode. (Default configuration.) |
Uni | This interface is operating in unidirectional mode. (Default configuration.) |
Failure channel: | The name of the failure channel specified by the b5-b8 field of the K1 byte used in APS operation. Options can be Protection or Working. |
Active channel: | The number of the active channel specified as the physical channel in use. These values correspond to the physical slot/subslot/port used within the chassis. |
Channel stat: | The status of the active channel specified by the b1-b4 field of the K1 byte used in APS operation. |
Port stat: | The status of the individual physical working (w) and protection (p) channels. |
To view the PPP over ATM characteristics of a VC, use the show atm pvc ppp EXEC command.
show atm pvc pppThis command has no arguments or keywords.
This command applies only to the Cisco 6400 NRP.
EXEC
The following is sample output of the show atm pvc ppp command:
Router# show atm pvc ppp
VCD /
ATM Int. Name VPI VCI Type VCSt VA VASt IP Addr
0/0/0 1 0 33 PVC UP 1 DOWN 10.123.1.1
0/0/0 foo 0 34 PVC UP 2 DOWN 10.123.1.1
To show the current major and minor alarms and the thresholds for all user-configurable alarms on a Cisco 6400, use the show alarm status command.
show facility-alarm statusThis command has no keywords or arguments.
Global configuration
The show facility-alarm status command displays all of the current major and minor alarms and the user-configurable alarm thresholds for temperature. The Cisco 6400 has physical connections to a highly visible alarm display within the Central Office. After an alarm condition is indicated (by LEDs or bells), the show facility-alarm status command can be used to determine the cause of the alarm.
The following is an example of the output from the show facility-alarm status command.
Switch# show facility-alarm status Thresholds: Intake minor 40 major 50 Core minor 55 major 53 SOURCE:Network Clock TYPE:Network clock source, priority level 2 down SEVERITY:Minor ACO:Normal SOURCE:NSP EHSA TYPE:Secondary failure SEVERITY:Minor ACO:Normal SOURCE:ATM2/0/1 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal SOURCE:ATM6/0/1 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal SOURCE:ATM7/0/1 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal SOURCE:ATM6/1/0 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal SOURCE:ATM6/1/1 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal SOURCE:ATM7/1/1 TYPE:Sonet major line failure SEVERITY:Major ACO:Normal
To display the hardware configuration of the Cisco 6400 NRP, use the show nrp EXEC command.
show nrpThis command has no keywords or arguments.
EXEC
The following is sample output from the show nrp command:
Switch# show nrp
Router installed in slot 2
Network IO Interrupt Throttling:
throttle count=0, timer count=0
active=0, configured=0
netint usec=4000, netint mask usec=200
NRP CPU ID EEPROM:
Hardware revision 2.12 Board revision UNKNOWN (0xAF
Serial number 4294967295 Part number 255-65535-255
Test history 0xFF RMA number 255-255-255
EEPROM format version 0
EEPROM contents (hex):
0x00: 00 E3 02 0C FF FF FF FF FF FF FF FF FF FF FF FF
0x10: FF FF FF FF FF FF FF FF FF FF FF 78 FF FF FF FF
To show which slots, subslots, ports, and CPUs are defined as being redundant on the Cisco 6400, use the show redundancy command.
show redundancy [slot/subslot]This command has no keywords or arguments.
EXEC
This command displays a redundancy configuration table showing each object in a redundant pair and indicating which object is currently the master. Chassis redundancy is displayed if no slot or subslot is specified. If a slot or subslot is specified, the redundancy configuration for only that slot is displayed.
The following is sample output from the show redundancy command on the NSP:
Switch# show redundancy Preferred main-cpu : B NSP A : Primary NSP B : Secondary
The following is sample output from the show redundancy command on the NRP:
Router# show redundancy Primary NRP in slot 2, system configured non redundant User EHSA configuration (by CLI config): slave-console = off keepalive = on config-sync modes: standard = on start-up = on boot-var = on config-reg = on NSP EHSA configuration (via pam-mbox): redundancy = off preferred (slot 2) = yes Debug EHSA Information: NRP specific information: Backplane resets = 0 NSP mastership changes = 0 print_pambox_config_buff: pmb_configG values: valid = 1 magic = 0xEBDDBE1 (expected 0xEBDDBE1) nmacaddrs = 1 run_redundant = 0x0 preferred_master = 0x1 macaddr[0][0] = 0010.7b79.af93 macaddr[1][0] = 0000.0000.0000 EHSA pins: peer present = 0 peer state = SANTA_EHSA_SECONDARY crash status: this-nrp=NO_CRASH(1) peer-nrp=NO_CRASH(1) EHSA related MAC addresses: peer bpe mac-addr = 0010.7b79.af97 my bpe mac-addr = 0010.7b79.af93
To control which tags are advertised and to which nodes they are advertised, use the tag-switching advertise-local-tags global configuration command. To disable advertisement of tags, use the no form of this command.
tag-switching advertise-local-tags [for access-list-num [to access-list-num] ]for access-list-num | Specifies an access list of prefixes that should be advertised. |
to access-list-num | Specifies an IP access list of TDP peer prefixes that should receive advertisements. |
For all tags and to all peers
Global configuration
Multiple tag-switching advertise-local-tags commands can be used. When multiple commands are entered, their effect is combined to determine an overall specification of how locally allocated tags are advertised.
In the following example, the router is configured to advertise all locally assigned tags to all TDP neighbors. The assumption is that before the command is entered the default of no tag advertisement is in effect.
Switch(config)# tag-switching advertise-local-tags
In the following example, the router is configured to advertise tags for networks 10.101.0.0 and 10.221.0.0 to all TDP neighbors. The assumption is that before the commands are entered the default of no tag advertisement is in effect.
Switch(config)# access-list 1 permit 10.101.0.0 0.0.255.255 Switch(config)# access-list 4 permit 10.221.0.0 0.0.255.255 Switch(config)# tag-switching advertise-local-tags for 1 Switch(config)# tag-switching advertise-local-tags for 4
In the following example, the router is configured to advertise all tags to all TDP neighbors except neighbor 10.101.0.8. The assumption is that before the commands are entered the default of no tag advertisement is in effect.
Switch(config)# access-list 1 permit any Switch(config)# access-list 2 deny 10.101.0.8 Switch(config)# tag-switching advertise-local-tags Switch(config)# tag-switching advertise-local-tags for 1 to 2
To specify the number of virtual-access interfaces to be created and cloned from a specific virtual template, use the virtual-template pre-clone global configuration command.
virtual-template template-number pre-clone number
virtual-template template-number | The virtual template interface from which the new virtual-access interfaces are created. |
pre-clone number | The number of virtual-access interfaces created. |
None
Global configuration
This command applies to PPPoE only.
The number of pre-cloned virtual-access interfaces should be set to the number of expected PPPoE sessions.
The following example creates 1200 pre-cloned virtual-access interfaces on virtual template 1:
Router(config)# virtual-template 1 pre-clone 1200
Posted: Mon Nov 15 12:41:41 PST 1999
Copyright 1989-1999©Cisco Systems Inc.