- A through B
- C
- debounce-time rai through dialer rotor
- dialer string through group-range
- interface bri through isdn busy
- isdn call interface through isdn send-alerting
- isdn sending-complete through loopback remote (controller)
- map-class dialer through modem inout
- modem cts-alarm
- peer default ip address through ppp iphc max-header
- ppp iphc max-period through ppp multilink slippage
- ppp pap wait through rotary-group
- script activation through show dial-shelf
- show dial-shelf split through show nbf cache
- show nbf sessions through show tech-support spe
- show tgrm through x25 map ppp
- ppp pap wait
- ppp pfc local
- ppp pfc remote
- ppp quality
- ppp reliable-link
- ppp timeout aaa
- ppp timeout authentication
- ppp timeout idle
- ppp timeout idle (template)
- ppp timeout multilink link add
- ppp timeout multilink link remove
- ppp timeout multilink lost-fragment
- ppp timeout ncp
- ppp timeout retry
- pri-group timeslots
- profile incoming
- range
- rcapi number
- rcapi server
- red undancy
- reload components
- resource
- resource-pool
- resource-pool aaa accounting ppp
- resource-pool aaa protocol
- resource-pool call treatment
- resource-pool call treatment discriminator
- resource-pool group resource
- resource-pool profile customer
- resource-pool profile discriminator
- resource-pool profile service
- resource-pool profile vpdn
- retry keepalive
- rotary
- rotary-group
ppp pap wait
To configure the router to delay the Password Authentication Protocol (PAP) authentication until after the peer has authenticated itself to the router, use the ppp pap wait command in interface configuration mode. To allow the router to immediately send out its PAP request once the authentication phase starts, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is used only when the call direction is call-in. The ppp pap wait command specifies that the router will not authenticate to a peer requesting PAP authentication until the peer has authenticated itself to the router. The no form of this command specifies that the router will immediately send out its PAP request once the authentication phase starts.
Examples
The following example specifies ISDN BRI number 0. The method of encapsulation on the interface is PPP. The following example disables the default, meaning that the router will immediately send out its PAP request once the authentication phase starts.
Related Commands
ppp pfc local
To configure protocol field compression (PFC) in configuration requests, use the ppp pfc local command in interface configuration mode. To return the router to the default for PCF handling, use the no form of this command.
ppp pfc local { forbid | request }
Syntax Description
The PFC option is not sent in outbound configuration requests, and requests from a peer to add the PFC option are not accepted. |
|
The PFC option is included in outbound configuration requests. |
Command Default
PFC handling is automatically selected based on the type of link. For asynchronous links, the router responds as if the request keyword were selected and the router includes the PFC option in outbound configuration requests. For synchronous links, the router responds as if the forbid keyword were selected and the PFC option is not sent out in outbound configuration requests and requests from a peer to add the PFC option are not accepted.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(15)B. |
Usage Guidelines
When PFC is negotiated during PPP negotiation, Cisco routers may compress the PPP protocol field from two bytes to one byte. The ppp pfc local command configures how a router handles PFC in its outbound configuration request and allows PFC to be disabled during PPP negotiation, thus allowing the HDLC framing and the protocol field to remain uncompressed.
Prior to the introduction of the ppp pfc local command, negotiation and use of PFC was entirely dependent upon the link type (synchronous or asynchronous) and was not under the independent control of a system administrator, and this is still the default. The ppp pfc local command allows the system administrator to control when PPP negotiates the HDLC address and PFC options during initial LCP negotiations, and how the results of the PPP negotiation are applied.
Note
Using PFC can result in minor gains in effective bandwidth because they reduce the amount of framing overhead for each packet. However, using PFC changes the alignment of the network data in the frame, which in turn can impair the switching efficiency of the packets both at the local and remote ends of the connection. For these reasons, it is generally recommended that PFC not be enabled without carefully considering the potential results.
Examples
The following example shows how to configure a router to exclude the PFC option from its outbound configuration requests:
Related Commands
|
|
|
|---|---|
Configures the PFC option in configuration requests received from a remote peer. |
ppp pfc remote
To configure how the protocol field compression (PFC) option in configuration requests is received from a remote peer, use the ppp pfc remote command in interface configuration mode. To return to the default for PFC handling, use the no form of this command.
ppp pfc remote { apply | ignore | reject }
Syntax Description
PFC options are accepted and PFC may be performed on frames sent to the remote peer. |
|
PFC options are accepted, but PFC is not performed on frames sent to the remote peer. |
|
Command Default
PFC handling is automatically selected based on the type of link, as follows: For asynchronous links, the router responds as if the apply keyword were selected and the router accepts PFC options received from a remote peer and PFC may be performed on frames sent to the remote peer. For synchronous links, the router responds as if the ignore keyword were selected and PFC options are accepted but PFC is not performed on frames sent to the remote peer.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(15)B. |
Usage Guidelines
When PFC is negotiated during PPP negotiation, Cisco routers may compress the PPP protocol field from two bytes to one byte. The ppp pfc remote command allows PFC to be disabled during PPP negotiation, thus allowing the HDLC framing and the protocol field to remain uncompressed.
Prior to the introduction of the ppp pfc remote command, negotiation and use of PFC was entirely dependent upon the link type (synchronous or asynchronous) and was not under the independent control of a system administrator, and this is still the default. The ppp pfc remote command allows the system administrator to control when PPP negotiates the HDLC address and PFC options during initial LCP negotiations, and how the results of the PPP negotiation are applied.
Note Using PFC can result in minor gains in effective bandwidth because they reduce the amount of framing overhead for each packet. However, using PFC changes the alignment of the network data in the frame, which in turn can impair the switching efficiency of the packets both at the local and remote ends of the connection. For these reasons, it is generally recommended that PFC not be enabled without carefully considering the potential results.
Examples
The following example shows how to configure a router to explicitly reject PFC options from a remote peer:
Related Commands
|
|
|
|---|---|
Configures the ACFC option in configuration requests received from a remote peer. |
|
ppp quality
To enable Link Quality Monitoring (LQM) on a serial interface, use the ppp quality command in interface configuration mode. To disable LQM, use the no form of this command.
Syntax Description
Specifies the link quality threshold. Range is from 1 to 100. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The percentages are calculated for both incoming and outgoing directions. The outgoing quality is calculated by comparing the total number of packets and bytes sent to the total number of packets and bytes received by the destination node. The incoming quality is calculated by comparing the total number of packets and bytes received to the total number of packets and bytes sent by the destination node.
If the link quality percentage is not maintained, the link is deemed to be of poor quality and is taken down. LQM implements a time lag so that the link does not bounce up and down.
Examples
The following example enables LQM on serial interface 2:
Related Commands
|
|
|
|---|---|
ppp reliable-link
To enable Link Access Procedure, Balanced (LAPB) Numbered Mode negotiation for a reliable serial link, use the ppp reliable-link command in interface configuration mode. To disable negotiation for a PPP reliable link on a specified interface, use the no form of the command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Enabling LAPB Numbered Mode negotiation as a means of providing a reliable link does not guarantee that all connections through the specified interface will in fact use a reliable link. It guarantees only that the router will attempt to negotiate reliable link on this interface.
PPP reliable link can be used with PPP compression over the link, but it does not require PPP compression.
PPP reliable link does not work with Multilink PPP.
You can use the show interface command to determine whether LAPB has been established on the link. You can troubleshoot PPP reliable link by using the debug lapb command and the debug ppp negotiations, debug ppp errors, and debug ppp packets commands.
Examples
The following example enables PPP reliable link and predictor compression on BRI interface 0:
Related Commands
ppp timeout aaa
To support the idle direction for the timeout value set by authentication, authorization, and accounting (AAA), use the ppp timeout aaa command in interface configuration mode. To remove this setting, use the no form of this command.
no ppp timeout aaa [ inbound ]
Syntax Description
(Optional) Specifies that the AAA server can set the PPP idle timeout parameters only for inbound traffic. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to reset the idle timer based on inbound traffic only set by AAA, and to support the idle direction for the timeout value set by AAA.
Examples
The following example uses a virtual template to set the idle timer by AAA only when inbound traffic is detected:
Related Commands
|
|
|
|---|---|
ppp timeout authentication
To set the PPP authentication timeout value, use the ppp timeout authentication command in interface configuration mode. To restore the default value, use the no form of this command.
ppp timeout authentication seconds
Syntax Description
Maximum time, in seconds, to wait for a response to an authentication packet. Valid seconds are from 0 to 255 seconds. The default is 10 seconds. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
Usage Guidelines
To keep an L2TP network server (LNS) from timing out a PPP authentication process, we recommend that you configure the PPP authentication timeout to 100 seconds.
Examples
The following example changes the time to wait for a response to an authentication packet to 15 seconds:
Related Commands
|
|
|
|---|---|
ppp timeout idle
To set the PPP timeout idle parameter, use the ppp timeout idle command in interface configuration mode. To reset the timeout value, use the no form of this command.
Syntax Description
Line idle time, in seconds, allowed before disconnecting the line. Acceptable range is platform dependent. |
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
This command was modified. The command name was changed to ppp timeout idle. |
Usage Guidelines
The ppp timeout idle command is used mainly on dialup interfaces and other temporary circuits to control how long the connection can be idle before it is terminated. All user traffic will reset the idle timer; however, nonnetwork traffic such as PPP control packets will not reset the timer. Also note that the dialer subsystem supports an alternate idle link detection mechanism that can be used instead of or with this PPP idle link detection mechanism.
The ppp timeout idle command name replaces the name ppp idle-timeout. The CLI will accept the ppp timeout idle name in Cisco IOS Release 12.2 and later releases.
Examples
The following example shows how to set the idle timer to 15 seconds:
Related Commands
ppp timeout idle (template)
To set PPP idle timeout parameters on a virtual template interface, use the ppp timeout idle command in interface configuration mode. To reset the time value, use the no form of this command.
Syntax Description
Line idle time, in seconds, allowed before disconnecting the line. |
Command Default
Command Modes
Command History
Usage Guidelines
This version of the ppp timeout idle command is used on virtual template interfaces to control how long the connection can be idle before it is terminated.
Examples
The following example sets the PPP idle timeout to 45 seconds in virtual template interface 1:
Related Commands
ppp timeout multilink link add
To limit the amount of time for which Multilink PPP (MLP) waits for a call to be established, use the ppp timeout multilink link add command in interface configuration mode. To remove the value, use the no form of this command.
ppp timeout multilink link add seconds
no ppp timeout multilink link add
Syntax Description
Wait period, in seconds, in the range from 1 to 65535 seconds. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When MLP needs to increase the bandwidth of a bundle, it attempts to bring up an additional link by requesting that the dialer system place a call to the peer system, or if the Bandwidth Allocation Protocol (BAP) is used, the call may also be done by requesting that the peer system make the call. BAP can be used to either make the call or request that the peer system make the call, depending upon the configuration. The time value specified with the ppp timeout multilink link add command determines how long MLP waits for that call to be established. If a new link does not join the bundle within the specified time, it is assumed that the call failed, and the call is attempted again.
If there are not enough links to carry the load, and the call succeeds in less than the time specified with the ppp timeout multilink link add command, MLP can immediately request another link. The time value specified with the ppp timeout multilink link add command prevents flooding the dialer system with call requests because not enough time was provided for prior requests to finish.
If the ppp timeout multilink link add command is not configured but the dialer wait-for-carrier-time command is, MLP will use the time value set with the dialer wait-for-carrier-time command. If neither command is configured, MLP uses a default value of 30 seconds.
This command is used with dynamic bandwidth (dial-on-demand) bundles.
Examples
The following example sets the call timeout period to 45 seconds:
Related Commands
ppp timeout multilink link remove
To set a timer that determines how long Multilink PPP (MLP) waits to drop a link when traffic load goes below the configured load threshold, use the ppp timeout multilink link remove command in interface configuration mode. To remove the value, use the no form of this command.
ppp timeout multilink link remove seconds
no ppp timeout multilink link remove
Syntax Description
Threshold wait period, in seconds, in the range from 1 to 65535 seconds. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When traffic load goes below the threshold set with the ppp multilink load-threshold command, MLP waits for the time set with the ppp timeout multilink link remove command and, if the load still remains below that threshold, drops the link to reduce bandwidth.
MLP will reduce bandwidth but never remove the last link in a bundle. The complete severing of a connection is controlled by the idle timer value specified in the dialer idle-timeout command; however, the idle timer has no effect on when MLP will drop excess links in a bundle.
If the ppp timeout multilink link remove command is not configured but the dialer wait-for-carrier-time command is, MLP will use the time value set with the dialer wait-for-carrier-time command. If neither command is configured, MLP uses a default value of 30 seconds.
This command is used with dynamic bandwidth (dial-on-demand) bundles.
Examples
The following example sets the low traffic load threshold wait period to 45 seconds:
Related Commands
|
|
|
|---|---|
Specifies the length of time the interface waits for a carrier. |
|
Limits the amount of time for which MLP waits for a call to be established. |
ppp timeout multilink lost-fragment
To set a timer that determines how long Multilink PPP waits for an expected fragment to arrive before declaring it lost, use the ppp timeout multilink lost-fragment command in interface configuration mode. To reset the default value, use the no form of this command.
ppp timeout multilink lost-fragment seconds [ milliseconds ]
no ppp timeout multilink lost-fragment
Syntax Description
Command Default
Command Modes
Command History
Examples
The following example sets a 5-second wait period for receiving expected fragments before declaring the fragments lost:
The following example sets a 300-millisecond wait period for receiving expected fragments before declaring the fragments lost:
The following example configures a wait period of 500 milliseconds (1/2 second):
Related Commands
|
|
|
|---|---|
Sets an advisory flag that indicates that the serial interface may receive packets in a different order than a peer system sent them. |
ppp timeout ncp
To set a time limit for the successful negotiation of at least one network layer protocol after a PPP connection is established, use the ppp timeout ncp command in interface configuration mode. To reset the default condition, use the no form of this command.
Syntax Description
Maximum time, in seconds, PPP should wait for negotiation of a network layer protocol. If no network protocol is negotiated in the given time, the connection is disconnected. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was changed to ppp timeout ncp. The ppp negotiation-timeout command was accepted by the command line interpreter through Cisco IOS Release 12.2. |
Usage Guidelines
The ppp timeout ncp command protects against the establishment of links that are physically up and carrying traffic at the link level, but are unusable for carrying data traffic due to failure to negotiate the capability to transport any network level data. This command is particularly useful for dialed connections, where it is usually undesirable to leave a telephone circuit active when it cannot carry network traffic.
Examples
The following example sets the Network Control Protocol (NCP) timer to 8 seconds:
Related Commands
|
|
|
|---|---|
Sets the interval for closing user connections on a specific line or port. |
|
ppp timeout retry
To set the maximum waiting period for a response during PPP negotiation, use the ppp timeout retry command in interface configuration mode. To reset the time value to the default settings, use the no form of this command.
ppp timeout retry seconds [ milliseconds ]
Syntax Description
Command Default
The default value waiting period for a response during PPP negotiation is 2 seconds.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(33)SRD. The milliseconds argument was added. |
Usage Guidelines
The ppp timeout retry command is useful for setting a maximum amount of time PPP should wait for a response to any control packet it sends.
Examples
The following example sets the retry timer to 100 seconds and 200 ms:
Related Commands
|
|
|
|---|---|
pri-group timeslots
To specify an ISDN PRI group on a channelized T1 or E1 controller, and to release the ISDN PRI signaling time slot, use the pri-group timeslots command in controller configuration mode. To remove or change the ISDN PRI configuration, use the no form of this command.
pri-group timeslots timeslot-range [ nfas_d { backup nfas_int number nfas_group number | none nfas_int number nfas_group number [ service mgcp ] | primary nfas_int number nfas_group number [ iua as-name | rlm-group number | service mgcp ]} | service mgcp ]
no pri-group timeslots timeslot-range [ nfas_d { backup nfas_int number nfas_group number | none nfas_int number nfas_group number [ service mgcp ] | primary nfas_int number nfas_group number [ iua as-name | rlm-group number | service mgcp ]} | service mgcp ]
Syntax Description
Command Default
No ISDN PRI group is configured. The switch type is automatically set to the National ISDN switch type (primary-ni keyword) when the pri-group timeslots command is configured with the rlm-group subkeyword.
Command Modes
Command History
Usage Guidelines
The pri-group command supports the use of DS0 time slots for Signaling System 7 (SS7) links, and therefore the coexistence of SS7 links and PRI voice and data bearer channels on the same T1 or E1 span. In these configurations, the command applies to voice applications.
In SS7-enabled Voice over IP (VoIP) configurations when an RLM group is configured, High-Level Data Link Control (HDLC) resources allocated for ISDN signaling on a digital subscriber line (DSL) interface are released and the signaling slot is converted to a bearer channel (B24). The D channel will be running on IP. The chosen D-channel time slot can still be used as a B channel by using the isdn rlm-group interface configuration command to configure the NFAS groups.
NFAS allows a single D channel to control multiple PRI interfaces. Use of a single D channel to control multiple PRI interfaces frees one B channel on each interface to carry other traffic. A backup D channel can also be configured for use when the primary NFAS D channel fails. When a backup D channel is configured, any hard system failure causes a switchover to the backup D channel and currently connected calls remain connected.
NFAS is supported only with a channelized T1 controller and, as a result, must be ISDN PRI capable. Once the channelized T1 controllers are configured for ISDN PRI, only the NFAS primary D channel must be configured; its configuration is distributed to all members of the associated NFAS group. Any configuration changes made to the primary D channel will be propagated to all NFAS group members. The primary D channel interface is the only interface shown after the configuration is written to memory.
The channelized T1 controllers on the router must also be configured for ISDN. The router must connect to either an AT&T 4ESS, Northern Telecom DMS-100 or DMS-250, or National ISDN switch type.
The ISDN switch must be provisioned for NFAS. The primary and backup D channels should be configured on separate T1 controllers. The primary, backup, and B-channel members on the respective controllers should be the same configuration as that configured on the router and ISDN switch. The interface ID assigned to the controllers must match that of the ISDN switch.
You can disable a specified channel or an entire PRI interface, thereby taking it out of service or placing it into one of the other states that is passed in to the switch using the isdn service interface configuration command.
In the event that a controller belonging to an NFAS group is shut down, all active calls on the controller that is shut down will be cleared (regardless of whether the controller is set to primary, backup, or none), and one of the following events will occur:
- If the controller that is shut down is configured as the primary and no backup is configured, all active calls on the group are cleared.
- If the controller that is shut down is configured as the primary, and the active (In service) D channel is the primary and a backup is configured, then the active D channel changes to the backup controller.
- If the controller that is shut down is configured as the primary, and the active D channel is the backup, then the active D channel remains as backup controller.
- If the controller that is shut down is configured as the backup, and the active D channel is the backup, then the active D channel changes to the primary controller.
The expected behavior in NFAS when an ISDN D channel (serial interface) is shut down is that ISDN Layer 2 should go down but keep ISDN Layer 1 up, and that the entire interface will go down after the amount of seconds specified for timer T309.
Note The active D channel changeover between primary and backup controllers happens only when one of the link fails and not when the link comes up. The T309 timer is triggered when the changeover takes place.
Examples
The following example configures T1 controller 1/0 for PRI and for the NFAS primary D channel. This primary D channel controls all the B channels in NFAS group 1.
The following example specifies ISDN PRI on T1 slot 1, port 0, and configures voice and data bearer capability on time slots 2 through 6:
The following example configures a standard ISDN PRI interface:
The following example configures a dedicated T1 link for SS7-enabled VoIP:
The following example configures a shared T1 link for SS7-enabled VoIP. The rlm-group 0 portion of the pri-group timeslots command releases the ISDN PRI signaling channel.
Related Commands
profile incoming
To define a template formed by directives guiding the Call Service Module (CSM) to process the digit sequence for a signaling class, use the profile incoming command in global configuration mode.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Arrange the directive special characters in the order necessary to process the digit sequence for your signaling class.
Examples
The following example enables the profile incoming command:
Related Commands
|
|
|
Defines a signaling class with a template formed by directives guiding the CSM to process the digit sequence. |
range
To associate a range of modems or other physical resources with a resource group, use the range command in resource group configuration mode. To remove a range of modems or other physical resources, use the no form of this command.
range { limit number | port slot [ slot ]}
no range { limit number | port slot [ slot ]}
Cisco AS5200 and AS5300 Series Routers
range { limit number | port slot / port [ slot / port ]}
no range { limit number | port slot / port [ slot / port ]}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the range resource group configuration command to associate a range of modems or other physical resources with a resource group.
Specify the range for port-based resources by using the resource’s physical location. Do not identify non-port-based resource ranges by using a location. Rather, specify the size of the resource group with a single integer limit.
Specify noncontiguous ranges by using multiple range port commands within the same resource group. Do not configure the same ports in more than one resource group and do not overlap multiple port ranges.
For resources that are not pooled and have a one-to-one correspondence between DS0s, B channels, and HDLC framers, use the range limit number command. Circuit-switched data calls and V.120 calls use these kinds of resources.
Note Do not put heterogeneous resources in the same group. Do not put MICA modems in the same group as Microcom modems. Do not put modems and HDLC controllers in the same resource group.
Do not configure “port” and “limit” parameters in the same resource group.
Examples
The following example shows the range limit set for 48 simultaneous connections being supported by the resource group:
range limit 48
The following example shows the ports set for modem 1 ranging from port 0 to port 47:
range port 1/0 1/47
rcapi number
To enable the Cisco 800 series router to distinguish between incoming CAPI calls and incoming non-CAPI calls such as POTS, PPP, and X.25, use the rcapi number command in global configuration mode. To release the specified directory number from the RCAPI interface, use the no form of this command.
rcapi number directory-number [ : subaddress ]
Syntax Description
(Optional) Subaddress of the router preceded by a colon (:). |
Command Default
Command Modes
Command History
|
|
|
|---|---|
The commands rcapi number and no rcapi number were introduced on the Cisco 800 series router. |
Usage Guidelines
The rcapi number command allows the Cisco 800 series router to reserve directory numbers exclusively for incoming calls.
The directory-number argument is the number assigned by the ISDN provider for the PC on which RCAPI is configured. The directory number should not be set to any other interfaces such as POTS and DOV. This command works only with the Net3 switch type.
Examples
The following example sets the router to recognize an ISDN number rather than a subaddress:
Related Commands
|
|
|
|---|---|
Enables the RCAPI server on the 800 series router and, optionally, sets the TCP port number. |
|
Display statistics and details about RCAPI server operation. |
rcapi server
To enable the RCAPI server on the 800 series router or to set the TCP port number, use the rcapi server command in global configuration mode. To disable the RCAPI server on the 800 series router, use the no form of this command.
Syntax Description
Command Default
If the router is configured for basic Net3 IDSN switch type, by default RCAPI is enabled, and the port number is set to 2578.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command works only with the Net3 switch type. The same port number must be configured on both the router and client PC.
Examples
The following example set the TCP port number to 2000:
Related Commands
redundancy
To enter redundancy configuration mode, use the redundancy command in global configuration mode.
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
Use the redundancy command to enter redundancy configuration mode, where you can define aspects of redundancy such as shelf redundancy for the Cisco AS5800 universal access server.
Before configuring line card redundancy, install the Y-cables. Before deconfiguring redundancy, remove the Y-cables.
The following restrictions apply to line card redundancy on the Cisco 10000 series router:
- Port-level redundancy is not supported.
- Redundant cards must occupy the two subslots within the same physical line card slot.
- The line card that will act as the primary line card must be the first line card configured, and it must occupy subslot 1.
From redundancy configuration mode, you can enter the main CPU submode to manually synchronize the configurations that are used by the two supervisor engines.
From the main CPU submode, you can use the auto-sync command to use all of the redundancy commands that are applicable to the main CPU.
To select the type of redundancy mode, use the mode command.
Nonstop forwarding (NSF) with stateful switchover (SSO) redundancy mode supports IPv4. NSF with SSO redundancy mode does not support IPv6, Internetwork Packet Exchange (IPX), and Multiprotocol Label Switching (MPLS).
After you enter redundancy configuration mode, you can use the interchassis command to specify the redundancy group number and enter interchassis redundancy mode. In the interchassis redundancy configuration mode, you can do the following:
- Specify a backbone interface for the redundancy group using the backbone command.
- Exit from interchassis configuration mode using the exit command.
- Specify the IP address of the remote redundancy group member using the member ip command.
- Specify the Multichassis LACP (mLACP) node ID, system MAC address, and system priority using the node-id, system-mac, and system-priority commands.
- Define the peer monitoring method using the monitor command.
Cisco uBR10012 Universal Broadband Router
After you enter redundancy configuration mode, you can use the main-cpu command to enter main-CPU redundancy configuration mode, which allows you to specify which files are synchronized between the active and standby Performance Routing Engine (PRE) modules.
At the redundancy configuration mode, you can do the following:
- Set a command to its default mode using the default command.
- Exit from a redundancy configuration using the exit command.
- Enter the line card group redundancy configuration using the linecard-group command.
- Enter main-CPU redundancy configuration mode using the main-cpu command, which allows you to specify which files are synchronized between the active and standby Supervisor cards.
- Configure the redundancy mode for the chassis using the mode command.
- Enforce a redundancy policy using the policy command.
Examples
The following example shows how to enable redundancy mode:
The following example shows how to assign the configured router shelf to the redundancy pair designated as 25. This command must be issued on both router shelves in the redundant router-shelf pair:
The following example shows how to configure two 4-port channelized T3 half eight line cards that are installed in line card slot 2 for one-to-one redundancy:
The following example shows how to enter the main CPU submode:
Router(config)# redundancy
Router(config-r)# main-cpu
Router(config-r-mc)#
Cisco uBR10012 Universal Broadband Router
The following example shows how to enter redundancy configuration mode and display the commands that are available in that mode on the Cisco uBR10012 router:
The following example shows how to enter redundancy configuration mode and displays its associated commands on the Cisco RFGW-10 chassis:
The following example shows how to enter redundancy configuration mode and its associated commands in the interchassis mode:
Related Commands
reload components
To request that the dial shelf controller (DSC) (or DSCs in a redundant configuration) be reloaded at the same time as a reload on the Router Shelf on the Cisco AS5800, use the reload components command in EXEC mode. To cancel a reload, use the reload components cancel command.
reload components { all | description-line | at hh : mm | in [hhh : ]mmm }
Syntax Description
Command History
|
|
|
|---|---|
Command Modes
Usage Guidelines
On the Cisco AS5800 only, to request that the DSC (or DSCs in a redundant configuration) be reloaded at the same time as a reload on the Router Shelf, use the reload components all command.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This prevents the system from dropping to the ROM monitor and thereby taking the system out of remote user control.
If you modify your configuration file, the system prompts you to save the configuration. During a save operation, the system asks you if you want to proceed with the save if the CONFIG_FILE environment variable points to a startup configuration file that no longer exists. If you say “yes” in this situation, the system goes to setup mode upon reload.
When you schedule a reload to occur at a later time, it must take place within approximately 24 days.
The at keyword can only be used if the system clock has be set on the router (either through Network Time Protocol (NTP), the hardware calendar, or manually). The time is relative to the configured time zone on the router. To schedule reloads across several routers to occur simultaneously, the time on each router must be synchronized with NTP.
To display information about a scheduled reload, use the show reload command.
Examples
The following example reloads all components on a Cisco AS5800:
Related Commands
|
|
|
|---|---|
resource
To assign resources and supported call-types to a customer profile, use the resource command in customer profile configuration mode. To disable this function, use the no form of this command.
resource name { digital | speech | v110 | v120 } [ service name ]
no resource name { digital | speech | v110 | v120 } [ service name ]
Syntax Description
Command Default
No resources are assigned to the customer profile by default.
Command Modes
Customer profile configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource customer profile configuration command to assign resources and supported call-types to a customer profile. This command specifies a group of physical resources to be used in answering an incoming call of a particular type for a particular customer profile. For example, calls started by analog modems are reciprocated with the speech keyword.
Examples
The following example shows a physical resource group called “modem1”. Forty-eight integrated modems are then assigned to modem1, which is linked to the customer profile called “customer1_isp”:
Related Commands
|
|
|
|---|---|
resource-pool
To enable or disable resource pool management, use the resource-pool command in global configuration mode.
resource-pool { enable | disable }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool global configuration command to enable and disable the resource pool management feature.
Examples
The following example shows how to enable RPM:
resource-pool aaa accounting ppp
To include enhanced start/stop resource manager records to authorization, authentication, and accounting (AAA) accounting, use the resource-pool aaa accounting ppp command in global configuration mode. To disable this feature, use the no form of this command.
resource-pool aaa accounting ppp
no resource-pool aaa accounting ppp
Syntax Description
Command Default
Disabled. The default of the resource-pool enable command is to not enable these new accounting records.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool aaa accounting ppp global configuration command to include enhanced start/stop resource manager records to AAA accounting. The resource-pool aaa accounting ppp command adds new resource pool management fields to the AAA accounting start/stop records. The new attributes in the start records are also in the stop records—in addition to those new attributes added exclusively for the stop records.
If you have configured your regular AAA accounting, this command directs additional information from the resource manager into your accounting records.
Note If you configure only this command and do not configure AAA accounting, nothing happens. The default functionality for the resource-pool enable command does not include this functionality.
Table 1 shows the new fields that have been added to the start and stop records.
|
|
|
|---|---|
| Customer-profile-active-sessions |
|
This list of newly supported start and stop fields is not exhaustive. Cisco reserves the right to enhance this list of records at any time. Use the
show accounting command to see the contents of each active session.
Note Cisco recommends that you thoroughly understand how these new start/stop records affect your current accounting structure before you enter this command.
Examples
The following example shows the new AAA accounting start/stop records inserted into an existing AAA accounting infrastructure:
Related Commands
|
|
|
|---|---|
Allows display of the active accountable events on the network and helps collect information in the event of a data loss on the accounting server. |
resource-pool aaa protocol
To specify which protocol to use for resource management, use the resource-pool aaa protocol command in global configuration mode. To disable this feature and go to local, use the no form of this command.
resource-pool aaa protocol { local | group name }
Syntax Description
Use an external authorization, authentication, and accounting (AAA) server group. The Resource Pool Management Server (RPMS) is defined in a AAA server group. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool aaa protocol global configuration command to specify which protocol to use for resource management. The AAA server group is most useful when you want to have multiple RPMSs configured as a fall-back mechanism.
Examples
The following example shows how to specify local authorization protocol:
resource-pool call treatment
To set up the signal sent back to the telco switch in response to incoming calls, use the resource-pool call treatment command in global configuration mode. To disable this function, use the no form of this command.
resource-pool call treatment { profile { busy | no-answer } | resource { busy | channel-not-available }}
no resource-pool call treatment { profile { busy | no-answer } | resource { busy | channel-not-available }}
Syntax Description
Answers the call, then sends a busy signal when profile authorization or resource allocation fails. |
|
Sends channel not available (CNA) code when resource allocation fails. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool call treatment global configuration command to set up the signal sent back to the telco switch in response to incoming calls.
Examples
The following example configures the device to answer the call and send a busy signal when profile authorization or resource allocation fails:
resource-pool call treatment discriminator
To modify the signal (ISDN cause code) sent to the switch when a discriminator rejects a call, enter the resource-pool call treatment discriminator command in global configuration mode. To disable this function, use the no form of this command.
resource-pool call treatment discriminator { busy | no-answer | channel-not-available }
no resource-pool call treatment discriminator { busy | no-answer | channel-not-available }
Syntax Description
Answers the call, then sends a busy signal when profile authorization or resource allocation fails. |
|
Sends channel not available (CNA) code when resource allocation fails. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool call treatment discriminator global configuration command to set up the signal sent back to the telco switch in response to incoming calls.
Examples
Use the following command to answer the call, but send a busy signal to the switch when profile authorization or resource allocation fails:
Use the following command to prevent the call from being answered when profile authorization fails and the discriminator rejects a call:
resource-pool group resource
To create a resource group for resource management, use the resource-pool group resource command in global configuration mode. To remove a resource group from the running configuration, use the no form of this command.
resource-pool group resource name
no resource-pool group resource name
Syntax Description
Name for the group of physical resources inside the access server. This name can have up to 23 characters. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool group resource global configuration command to create a resource group for resource management. When calls come into the access server, they are allocated physical resources as specified within resource groups and customer profiles.
See the range command for more information.
If some physical resources are not included in any resource groups, then these remaining resources are not used and are considered to be part of the default resource group. These resources can be used in certain cases to answer calls before profile allocation occurs, but the resources are not used other than in the connection phase.
Note For standalone network access server environments, configure resource groups before using them in customer profiles. For external RPMS environments, configure resource groups on the network access server before defining them on external RPMS servers.
When enabling RPM for SS7 signaling, like resources in the network access server (NAS) must be in a single group:
- All modems must be in one group.
- All High-Level Data Link Control (HDLC) controllers must be in a different group.
- All V.110 ASICs must be put into another group.
- All V.120 resources must be in a separate group.
All resource group types must have the same number of resources and that number must equal the number of interface channels available from the public network switch. This grouping scheme prevents the CNA signal from being sent to the signaling point. For SS7 signaling, Microcom and MICA technologies modems must be in the same group. If SS7 signaling is not used, Cisco recommends assigning Microcom and MICA modems to separate groups to avoid introducing errors in RPM statistics.
Examples
The following example shows the configuration options within a resource group:
Related Commands
|
|
|
|---|---|
Associates a range of modems or other physical resources with a resource group. |
resource-pool profile customer
To create a customer profile and to enter customer profile configuration mode, use the resource-pool profile customer command in global configuration mode. To delete a customer profile from the running configuration, use the no form of this command.
resource-pool profile customer name
no resource-pool profile customer name
Syntax Description
Customer profile name. This name can have up to 23 characters. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Support for this command was integerated into Cisco IOS Release 12.0(5)T. |
Usage Guidelines
Use the resource-pool profile customer command to create a customer profile and enter customer profile configuration mode.
VPDN groups can be associated with a customer profile by issuing the vpdn group command in customer profile configuration mode.
A VPDN profile can be associated with a customer profile by issuing the vpdn profile command in customer profile configuration mode.
VPDN session limits for the VPDN groups associated with a customer profile can be configured in customer profile configuration mode using the limit base-size command.
Examples
The following example shows how to create two VPDN groups, configure the VPDN groups under a VPDN profile named profile1, then associate the VPDN profile with a customer profile named customer12:
Related Commands
resource-pool profile discriminator
To create a call discrimination profile and assign it a name, use the resource-pool profile discriminator command in global configuration mode. To remove a call discrimination profile from the running configuration, use the no form of this command.
resource-pool profile discriminator name
no resource-pool profile discriminator name
Syntax Description
Name of the call discrimination profile created. This name can have up to 23 characters. You can add a calling line ID (CLID) or DNIS group to the discriminator profile created. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was enhanced to add CLID groups and dialed number identification service (DNIS) groups to a discriminator. |
Usage Guidelines
Discriminator profiles enable you to process calls differently based on the call type and DNIS or CLID combination. Use the resource-pool profile discriminator command to create a call discrimination profile, and then use the clid group command to add a CLID group to a discriminator.
To create a call discrimination profile, you must specify both the call type and CLID group. Once a CLID group is associated with a call type in a discriminator, it cannot be used in any other discriminator.
Examples
The following example shows a call discriminator named clid1 created and configured to block digital calls from the CLID group named clid3:
Related Commands
|
|
|
|---|---|
resource-pool profile service
To set up the service profile configuration, use the resource-pool profile service command in global configuration mode. To disable this function, use the no form of this command.
resource-pool profile service name
no resource-pool profile service name
Syntax Description
Service profile name. This name can have up to 23 characters. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the resource-pool profile service global configuration command to set up the service profile configuration.
Examples
The following example shows the creation of a service profile called user1:
resource-pool profile vpdn
To create a virtual private dialup network (VPDN) profile and to enter VPDN profile configuration mode, use the resource-pool profile vpdn command in global configuration mode. To disable this function, use the no form of this command.
resource-pool profile vpdn name
no resource-pool profile vpdn name
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Support for this command was integerated into Cisco IOS Release 12.0(5)T. |
Usage Guidelines
Use the resource-pool profile vpdn command to create a VPDN profile and enter VPDN profile configuration mode, or to enter VPDN profile configuration mode for a VPDN profile that already exists.
VPDN groups can be associated with a VPDN profile using the vpdn group command in VPDN profile configuration mode. A VPDN profile will count VPDN sessions across all associated VPDN groups.
VPDN session limits for the VPDN groups associated with a VPDN profile can be configured in VPDN profile configuration mode using the limit base-size command.
Examples
The following example createss the VPDN groups named l2tp and l2f, and associates both VPDN groups with the VPDN profile named profile32:
Related Commands
retry keepalive
To enable Redundant Link Manager (RLM) keepalive retries, use the retry keepalive command in RLM configuration mode. To disable this function, use the no form of this command.
retry keepalive number-of-times
no retry keepalive number-of-times
Syntax Description
Number of keepalive failures allowed before the link is declared down, from |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
RLM allows keepalive failures in consecutive certain amounts of time configured using the command line interface (CLI) before it declares the link is down.
Examples
The following example sets RLM keepalive retries to 88:
Related Commands
rotary
To define a group of lines consisting of one or more virtual terminal lines or one auxiliary port line, use the rotary command in line configuration mode. To remove a group of lines from a rotary group, use the no form of this command.
rotary group [ queued [ by-role ]] [ round-robin ]
no rotary group [ queued [ by-role ]] [ round-robin ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Connections to a rotary group can take advantage of the following features:
- Clear To Send (CTS)—If a line in a rotary group is configured to require CTS, the Cisco IOS software ignores that line when CTS from the attached device is low. This feature enables the software to avoid inactive host ports automatically. To enable this feature, use the modem bad line configuration command.
- EIA/TIA-232 handshaking—Rotary groups are often associated with large terminal switches that require an EIA/TIA-232 handshake before forming a connection. In this case, use the modem callout line configuration command to configure the lines in the group. If the EIA/TIA-232 handshake fails on a line, the Cisco IOS software steps to the next free line in the rotary group and restarts the negotiation.
- Access control—You can use access lists for groups of virtual terminal lines.
- Session timeout—Use the session-timeout line configuration command to set an interval for a line so that if no activity occurs on a remotely initiated connection for that interval, the Cisco IOS software closes the connection. The software assumes that the host has crashed or is otherwise inaccessible.
Typically, rotary groups are used on devices with multiple modem connections to allow connection to the next free line in a hunt group. In the event that there are no free asynchronous ports, the queued keyword enables outgoing connection requests to be queued until a port becomes available. Periodic messages are sent to users to update them on the status of their connection request.
For a nonqueued connection request, the remote host must specify a particular TCP port on the router to connect to a rotary group with connections to an individual line. The available services are the same, but the TCP port numbers are different. Table 2 lists the services and port numbers for both rotary groups and individual lines.
|
|
|
Individual Lines |
|---|---|---|
For example, if Telnet protocols are required, the remote host connects to the TCP port numbered 3000 (decimal) plus the rotary group number. If the rotary group identifier is 13, the corresponding TCP port is 3013.
If a raw TCP stream is required, the port is 5000 (decimal) plus the rotary group number. If rotary group 5 includes a raw TCP (printer) line, the user connects to port 5005 and is connected to one of the raw printers in the group.
If Telnet binary mode is required, the port is 7000 (decimal) plus the rotary group number.
The by-role keyword enables priority users to bypass the queue and access the first available line.
Note Priority users must have the privilege level of administrator(PRIV_ROOT) to take advantage of this option.
The round-robin selection algorithm enabled by the round-robin keyword improves the utilization of tty ports. When looking for the next available port, the default linear hunting algorithm will not roll over to the next port if the first port it finds is bad. This failure to roll over to the next port results in an inequitable utilization of the tty ports on a router. The round-robin hunting algorithm will roll over bad ports instead of retrying them.
Note The round-robin option must be configured for all the lines in a rotary group.
Examples
The following example establishes a rotary group consisting of virtual terminal lines 2 through 4 and defines a password on those lines. By using Telnet to connect to TCP port 3001, the user gets the next free line in the rotary group. The user need not remember the range of line numbers associated with the password.
The following example enables asynchronous rotary line queueing:
The following example enables asynchronous rotary line queueing using the round-robin algorithm:
Related Commands
rotary-group
To assign a request-dialout virtual private dialup network (VPDN) subgroup to a dialer rotary group, use the rotary-group command in request-dialout configuration mode. To remove the request-dialout VPDN subgroup from the dialer rotary group, use the no form of this command.
no rotary-group [ group-number ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If the dialer pool or dialer rotary group that the VPDN group is in contains physical interfaces, the physical interfaces will be used before the VPDN group.
You must first enable the protocol l2tp command on the request-dialout VPDN subgroup before you can enable the rotary-group command. Removing the protocol l2tp command will remove the rotary-group command from the request-dialout subgroup.
You can only configure one dialer profile pool (using the pool-member command) or dialer rotary group (using the rotary-group command). If you attempt to configure a second dialer resource, you will replace the first dialer resource in the configuration.
Examples
The following example configures VPDN group 1 to request Layer 2 Tunnel Protocol (L2TP) dial-out to IP address 172.16.4.6 using dialer profile pool 1 and identifying itself using the local name router32.
Related Commands
|
|
|
|---|---|
Enables an LNS to request VPDN dial-out calls by using L2TP. |
Feedback