- 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
- dialer pppoe-client-vlan-cos
- dialer string
- dialer string (dialer profiles)
- dialer string (legacy DDR)
- dialer string trunkgroup
- dialer voice-call
- dialer vpdn
- dialer wait-for-carrier-time (interface)
- dialer wait-for-carrier-time (map-class)
- dialer wait-for-line-protocol
- dialer watch-di sable
- dialer watch-group
- dialer wa tch-list
- dialer watch-list delay
- dialer-group
- dialer-group (template)
- dialer-list protocol (Dial)
- dial-peer cor custom
- dial-peer cor list
- dial-shelf split backplane-ds0
- dial-shelf split slots
- dial-shelf split slots none
- dial-shelf split slots remove
- dial-tdm-clock
- disconnect
- dnis group
- ds0 busyout (channel)
- ds0 busyout-threshold
- ds0-group (controller e1)
- encap-sequence
- encapsulation cpp
- failover group-number
- firmware filename
- firmware location
- firmware upgrade
- flowcontrol
- group-range
dialer pppoe-client-vlan-cos
To mark PPP and PPPoE control packets explicitly, use the dialer pppoe-client-vlan-cos command in the dialer interface configuration mode. To unmark PPP and PPPoE control packets specified for the dialer interface, use the no form of this command.
dialer pppoe-client-vlan-cos cos-val
no dialer pppoe-client-vlan-cos cos-val
Syntax Description
cos value of control packets. The cos-val can range from 0 to 7. |
Command Default
Command Modes
Dialer Interface Configuration
Command History
|
|
|
|---|---|
This command was integrated into Cisco Release 15.4(03)M6.2 and supports fly cos settings for control packets. |
Usage Guidelines
This command has to be configured under the dialer interface configuration, which will allow marking of the control packets with the defined COS value.
Configuring this command on a per-dialer basis would result in marking of control packets on a per-dialer basis.
This command will be effective during the absence of PPPOE associated interface service cos policy. Service policy will have higher precedence than this command.
Examples
In this example cos-value is set to 4. The following example shows how to configure COS marking of control packets for PPPoEoD.
Here none of the service policy is associated with e0.1. Dialer service policy settings will be applied for data packets. Hence by default, PPP/PPPOE control packets will be marked with ‘0’. If we need specific control packet settings, “dialer pppoe-client-vlan-cos” command can be configured. In this case it is configured with value 4. So control packets will be marked with 4.
dialer string
To specify the string (telephone number) to be called for interfaces calling a single site, use the dialer string command in interface configuration mode. To delete the dialer string specified for the interface, use the no form of this command.
dialer string dial-string [ : isdn-subaddress ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To use this command on an asynchronous interface, you must define a modem chat script for the associated line by using the script dialer command. A script must be used to implement dialing.
Dialers configured as in-band pass the string to the external dialing device. Specify one dialer string command per interface.
To specify multiple strings, use the dialer map command. In general, you include a dialer string or dialer map command if you intend to use a specific interface to initiate a dial-on-demand routing (DDR) call.
Note
If a dialer string command is specified without a dialer-group command with access lists defined, dialing is never initiated. If the debug dialer command is enabled, an error message is displayed indicating that dialing never will occur.
The string of characters specified for the dial-string argument is the default number used under the following conditions:
- A dialer map command is not included in the interface configuration.
- The next hop address specified in a packet is not included in any of the dialer map interface configuration commands recorded—assuming that the destination address passes any access lists specified for DDR with the dialer-list command.
On synchronous interfaces, depending on the type of modem you are using, International Telecommunication Union Telecommunication (ITU-T) Standardization Sector V.25 bis options might be supported as dial-string parameters of the dialer string command. Supported options are listed in Table 1 . The functions of the parameters are nation specific, and they may have different implementations in your country. These options apply only if you have enabled DDR with the dialer in-band command. Refer to the operation manual for your modem for a list of supported options.
Note The ITU-T carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT).
|
|
|
|---|---|
Tone. Dialing to be continued in Dual Tone Multifrequency (DTMF) mode. |
|
Examples
The following example specifies a dial-on-demand routing (DDR) telephone number to be tone-dialed on interface async 1 using the dialer string command:
Related Commands
dialer string (dialer profiles)
To specify the string (telephone number) to be used when placing a call from an interface, use the dialer string command in interface configuration mode. To delete the telephone number specified for the interface, use the no form of this command.
dialer string dial-string [ class class-name ]
Syntax Description
(Optional) Dialer map class associated with this telephone number. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When you use dialer profiles for DDR, use the dialer string class form of this command to define a map class for a specific dialer profile.
Dialer profiles make it unnecessary to use dialer maps to configure DDR.
Note If a dialer string command is specified without a dialer-group command with access lists defined, dialing is never initiated. If the debug dialer command is enabled, an error message is displayed indicating that dialing never will occur.
Examples
The following example specifies that the dial string 4155550134 be used in calls to destinations defined by the map class myclass:
Related Commands
dialer string (legacy DDR)
To specify the destination string (telephone number) to be called for interfaces calling a single site, use the dialer string command in interface configuration mode. To delete the dialer string specified for the interface, use the no form of this command.
dialer string dial-string [ : isdn-subaddress ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To use this command on an asynchronous interface, you must define a modem chat script for the associated line by using the script dialer command. A script must be used to implement dialing.
Dialers configured as in-band pass the string to the external dialing device. Specify one dialer string command per interface.
In general, you include a dialer string command if you intend to use a specific interface to initiate a dial-on-demand routing (DDR) call.
Note If a dialer string command is specified without a dialer-group command with access lists defined, dialing is never initiated. If the debug dialer command is enabled, an error message is displayed indicating that dialing never will occur.
The string of characters specified for the dial-stri ng argument is the default number used under the following conditions:
- A dialer map command is not included in the interface configuration.
- The next hop address specified in a packet is not included in any of the dialer map command in interface configuration modes recorded—assuming that the destination address passes any access lists specified for DDR with the dialer-list command.
On synchronous interfaces, depending on the type of modem you are using, International Telecommunication Union Telecommunication (ITU-T) Standardization Sector V.25 bis options might be supported as dial-string parameters of the dialer string command. Supported options are listed in Table 1 . The functions of the parameters are nation specific, and they may have different implementations in your country. These options apply only if you have enabled DDR with the dialer in-band command. Refer to the operation manual for your modem for a list of supported options.
Note The ITU-T carries out the functions of the former Consultative Committee for International Telegraph and Telephone (CCITT).
Examples
The following example specifies a DDR telephone number to be tone-dialed on asynchronous interface 1 using the dialer string command:
Related Commands
dialer string trunkgroup
To specify a dial-out telephone number and dial-out trunk group name for a static configuration on a network access server (NAS), use the dialer string trunkgoup command in interface configuration mode. To delete the static, dial-out trunk group configuration, use the no form of this command.
dialer string dial-string trunkgroup trunkgroup-label
no dialer string dial-string trunkgroup trunkgroup-label
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A dialer string command, in general, enables a specific interface for initiating a dial-on-demand routing (DDR) call.
The dialer string trunkgroup command enables use of a dial-out trunk group, which directs an outbound synchronous or asynchronous call to be initiated by DDR on a specific channel of an ISDN circuit. The channel (also called a digital service 0 or DS0 link), is a member of a defined dial-out trunk group. Individual DS0s from various signaling circuits can be aggregated into a dial-out trunk group.
The dial-out trunk group configured by the dialer string trunkgroup command must be part of a static configuration on an NAS. See the “Related Commands” section for commands that allow other nonstatic configurations of dial-out trunk groups.
Examples
The following example enables use of dial-out trunk group TG1 on dialer interface 0 as part of a static NAS configuration:
Related Commands
dialer voice-call
To configure the dialer map class for a Network Specific Facilities (NSF) dialing plan to support outgoing voice calls, use the dialer voice-call command in map-class dialer configuration mode.
Syntax Description
Command Default
Command Modes
Map-class dialer configuration
Command History
|
|
|
|---|---|
Examples
The following partial example defines a dialer map class to support the SDN dialing plan and to support outgoing voice calls. For a more complete example using all the related commands, see the map-class dialer command.
Related Commands
dialer vpdn
To enable a dialer profile or dial-on-demand routing (DDR) dialer to use Layer 2 Tunnel Protocol (L2TP) dialout, use the dialer vpdn command in interface configuration mode. To disable L2TP dialout on a dialer profile or DDR dialer, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The dialer vpdn command must be configured on the LNSs dialer interface to enable L2TP dialout. This command enables the dialer to place a VPDN call.
Examples
The following example shows how to configure the dialer interface and VPDN group on an LNS for L2TP dialout:
Related Commands
|
|
|
|---|---|
Allows a dialer to access the AAA server for dialing information. |
|
Enables an LNS to request VPDN dial-out calls by using L2TP. |
dialer wait-for-carrier-time (interface)
To specify the length of time the interface waits for a carrier, use the dialer wait-for-carrier-time command in interface configuration mode. To reset the carrier wait time value to the default, use the no form of this command.
dialer wait-for-carrier-time seconds
no dialer wait-for-carrier-time
Syntax Description
Number of seconds that the interface waits for the carrier to come up when a call is placed. Acceptable values are positive, nonzero integers. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
On asynchronous interfaces, the dialer wait-for-carrier-time command sets the total time allowed for the chat script to run.
If a carrier signal is not detected in this amount of time, the interface is disabled until the enable timeout occurs (configured with the dialer enable-timeout command).
Examples
The following example specifies a carrier wait time of 45 seconds on asynchronous interface 1:
Related Commands
|
|
|
|---|---|
Sets the length of time an interface stays down after a call has completed or failed and before the interface is available to dial again. |
dialer wait-for-carrier-time (map-class)
To specify the length of time to wait for a carrier when dialing out to the dial string associated with a specified map class, use the dialer wait-for-carrier-time command in map-class dialer configuration mode. To reset the carrier wait time value to the default, use the no form of this command.
dialer wait-for-carrier-time seconds
no dialer wait-for-carrier-time
Syntax Description
Number of seconds that the interface waits for the carrier to come up when a call is placed. Acceptable values are positive, nonzero integers. The default is 30 seconds. |
Command Default
Command Modes
Map-class dialer configuration
Command History
|
|
|
|---|---|
Usage Guidelines
You can define different dialer map classes with different wait-for-carrier times to suit the different types of lines and interfaces. For example, you must define a longer wait time for a map class used by serial interfaces than for one used by ISDN interfaces.
Examples
The following example specifies a carrier wait time of 20 seconds for the class “Eng” on interface Dialer2:
dialer wait-for-line-protocol
To set a maximum time the dialer will wait for a line protocol after establishing a physical connection before considering the call unsuccessful, use the dialer wait-for-line-protocol command in interface configuration mode. To disable this function, use the no form of this command.
dialer wait-for-line-protocol wait-time
no dialer wait-for-line-protocol
Syntax Description
Time, in seconds, that the dialer will wait for the line protocol to come up after the physical layer connection has been established. The time can range from 1 to 2147483 seconds. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is supported only with encapsulation PPP.
By default the Cisco IOS software considers a dial-out attempt successful if a connection is established to the physical layer (Layer 1 of the Open System Interconnection reference model). The dialer wait-for-line-protocol command can be used to configure a router to wait a specific amount of time for a line protocol to come up once a physical layer connection has been established. If the call is dropped before the timer has elapsed, the call will be considered a failure. Redial will be triggered if the redial options have been configured with the dialer redial interface configuration command. The dialer failure statistics for the physical interface will be updated, which may influence the selection of a physical dialer for the next dial attempt. The physical dialer selection algorithm may be customized using the dialer rotor interface configuration command.
Note This command is not useful in conjunction with Cisco High-Level Data Link Control (HDLC) encapsulation. Cisco HDLC encapsulation is the default line protocol and will always come up regardless of line conditions.
Examples
The following example configures the dialer to wait 10 seconds for a line protocol after making a physical connection:
Related Commands
dialer watch-disable
Note Effective with Cisco IOS Release 12.3(11)T, this command is replaced by the dialer watch-list delay command. See the dialer watch-list delay command page for more information.
To set a delay time to the backup interface, use the dialer watch-disable command in interface configuration mode. To disable this feature, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was replaced by the dialer watch-list delay command. |
Usage Guidelines
This command is used to add a delay time to the backup interface. The delay time delays the time it takes for the backup interface to disconnect after the primary interface recovers.
Examples
The following example forces a 6-second delay to the backup interface once the primary interface recovers:
Related Commands
|
|
|
|---|---|
Displays general diagnostic information for ISDN BRI interfaces configured for DDR. |
dialer watch-group
To enable dial-on-demand routing (DDR) backup on an interface using Dialer Watch, configure the interface using the dialer watch-group command in interface configuration mode. To disable this feature, use the no form of this command.
dialer watch-group group-number
no dialer watch-group group-number
Syntax Description
Group number assigned that will point to a globally defined list of IP addresses to watch. The valid range is 1 to 255. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the dialer watch-group command on the secondary interface you want to enable DDR backup.
The dialer watch group number points to a globally defined list (the dialer watch-list command) that contains the IP addresses to be watched. If you use the dialer watch-group command you must also use the dialer watch-list command.
You must configure the standard commands required to enable the router to perform DDR in addition to the Dialer Watch commands. Refer to the Cisco IOS Dial Technologies Configuration Guide and the Cisco IOS Dial Technologies Command Reference for additional information.
The dialer watch-group and dialer watch-list commands can be added in any order.
Examples
The following example configures BRI interface 0 as the backup interface:
interface bri0
ip address 10.1.1.2 255.255.255.0
encapsulation ppp
dialer watch-group 1
Related Commands
|
|
|
|---|---|
Adds the list of IP addresses to be monitored for Dialer Watch. |
dialer watch-list
To specify a list of watched routes of IPv4 or IPv6 addresses, to specify IPv4 or IPv6 address and VPN routing and forwarding (VRF) instance pairs to be monitored by dialer watch, or to configure the router to dial the backup link if the primary link fails during the initial startup, use the dialer watch-list command in global configuration mode. To disable the list of watched routes or to disable the dialer watch to monitor IPv4 or IPv6 addresses and VFR pairs, use the no form of this command.
dialer watch-list group-number {[ ip ip-address ip-address-mask | ipv6 ipv6-address ipv6-address-mask ] [ vrf vrf-name ] | delay route-check initial seconds }
no dialer watch-list group-number {[ ip ip-address ip-address-mask | ipv6 ipv6-address ipv6-address-mask ] [ vrf vrf-name ] | delay route-check initial seconds }
Syntax Description
Command Default
The specified list of IPv4 or IPv6 addresses, the IPv4 or IPv6 address and the VRF instance pairs are not monitored. The router is not configured to dial the backup link when the primary link fails during the initial startup.
Command Modes
Command History
Usage Guidelines
Use the dialer watch-list command to specify a list of all IP addresses or networks that you want to monitor. The software does not limit the number of IP addresses or IPv6 addresses that can be added to a watch group.
Use the dialer watch-list command with the dialer watch-group command to monitor the IP or IPv6 addresses and VRF pairs. The group-number value specified using the dialer watch-list command must match the group number set in the dialer watch-group command in interface configuration mode. For example, if you use dialer watch-group 1, you must use dialer watch-list 1.
The dialer watch-list and dialer watch-group commands can be used in any order.
Address matching is exact; therefore, you must apply the specific IP or IPv6 address and mask range for the networks that you want to monitor. Use the show ip route and show ipv6 route commands to verify that the IPv4 and IPv6 routes you are watching exist in the routing table.
The route configured for the dialer watch-list command must exactly match the route in the routing table. This matching includes verifying that the network and the masks are identical.
You must configure the standard commands required to enable the router to perform dial-on-demand routing (DDR) in addition to configuring the dialer watch commands. See the Dial Technologies Configuration Guide and the Dial Technologies Command Reference for additional information.
Enabling the delay route-check initial keywords enables the router to check whether the primary route is up after the initial startup of the router is complete and the timer has expired. If this command is not configured, the dialer watch mechanism is triggered only when the primary route is removed from the routing table. If the primary link fails to come up during initial startup of the router, the route is never added to the routing table and hence cannot be watched. Therefore, use of the delay route-check initial keywords enables the dialer watch to dial the backup link in the event of a primary link failure during the initial startup of the router.
Use the vrf vrf-name keyword and argument to configure the corresponding VRF table to be used to detect when the watched route for the VRF has gone down. A VRF is a per-VPN routing information repository that defines the VPN membership of a customer site attached to a network access server. A VRF consists of an IP routing table, a derived Cisco Express Forwarding (formerly known as CEF) table, a set of interfaces that use the forwarding table, and a set of rules and routing protocol parameters that control the information that is included in the routing table. A separate set of routing and Cisco Express Forwarding tables is maintained for each VPN customer.
Note that the VRF might have overlapping address space, as explained below:
- At the provider edge (PE) router, each customer edge (CE) router will have a corresponding VRF associated with it.
- If two CE routers use the same address space, the corresponding VRFs at the PE router will have the overlapping address space.
- When using the vrf vrf-name keyword and argument, configure the watched route as an IPv4 or an IPv6 address-VRF name pair, where the IP address is the watched IP address and the VRF name is the routing and forwarding instance to which the IP address belongs.
Configuring the dialer watch with only the IP address does not ensure that the correct CE route will be dialed when a watched route goes down. Configuring the dialer watch with an IP address and VRF name pair ensures that the VRF table corresponding to the routing and forwarding instance to which the IP address belongs is found and the correct CE is dialed.
You can define a watch route that watches the same IP address, but belongs to a different VRF, in a single watch list.
Examples
The following example shows how to specify a pair of watched routes in a legacy dialer configuration. In this configuration, watch lists 1 and 2 are watching the same IP address, but belong to different VRFs.
The following example shows how to specify a pair of watched routes in a dialer rotary group configuration. In this configuration, watch lists 1 and 2 watch the same IP address, but belong to different VRFs.
The following example shows how to specify a pair of watched routes in a dialer profile configuration. In this configuration, watch lists 1 and 2 watch the same IP address, but belong to different VRFs.
The following example shows how to list IP addresses to be watched and form a group of networks to be monitored:
The following example shows how to list IPv6 addresses to be watched and form a group of IPv6 networks to be monitored:
The following command output shows how to ensure that a device checks that the primary route is up after initial startup of the device is complete:
Related Commands
dialer watch-list delay
To configure the router to delay before connecting or disconnecting a secondary link for a route monitored by Dialer Watch, use the dialer watch-list delay command in global configuration mode. To disable these delays, use the no form of this command.
dialer watch-list group-number delay { connect connect-time | disconnect disconnect-time }
no dialer watch-list group-number delay { connect connect-time | disconnect disconnect-time }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to configure a delay before connecting or disconnecting a secondary link for a route monitored by Dialer Watch. This command will not work unless dial-on-demand routing (DDR) is configured and Dialer Watch has been enabled.
Examples
The following example configures the router to wait 10 seconds before verifying that the primary link is still down and dialing a secondary link:
dialer watch-list 1 ip 10.1.1.0 255.255.255.0
dialer watch-list 1 delay connect 10
The following example configures the router to wait 10 seconds to disconnect a secondary link once the primary link has been reestablished:
dialer watch-list 1 ip 10.1.1.0 255.255.255.0
dialer watch-list 1 delay disconnect 10
Related Commands
|
|
|
|---|---|
Adds the list of IP addresses to be monitored for Dialer Watch. |
dialer-group
To control access by configuring an interface to belong to a specific dialing group, use the dialer-group command in interface configuration mode. To remove an interface from the specified dialer access group, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
An interface can be associated with a single dialer access group only; multiple dialer-group assignment is not allowed. A second dialer access group assignment will override the first. A dialer access group is defined with the dialer-group command. The dialer-list command associates an access list with a dialer access group.
Packets that match the dialer group specified trigger a connection request.
Examples
The following example specifies dialer access group number 1.
The destination address of the packet is evaluated against the access list specified in the associated dialer-list command. If it passes, either a call is initiated (if no connection has already been established) or the idle timer is reset (if a call is currently connected).
Related Commands
|
|
|
|---|---|
Defines a DDR dialer list to control dialing by protocol or by a combination of protocol and an access list. |
dialer-group (template)
To control access by configuring a virtual access interface to belong to a specific dialing group, use the dialer-group command in template configuration mode. To remove an interface from the specified dialer access group, use the no form of this command.
dialer-group dialer-list-number
Syntax Description
Number of the dialer access group to which the specific interface belongs. This access group is defined with the dialer-list command. Acceptable values are positive numbers from 1 to 128. |
Command Default
Command Modes
Command History
Usage Guidelines
An interface can be associated with only a single dialer access group; multiple dialer-group assignment is not allowed. A second dialer access group assignment will override the first. A dialer access group is defined with the dialer-group template configuration command. The dialer-list command associates an access list with a dialer access group. For Cisco IOS Release 12.2(4)T, the number of dialer groups that can be configured was increased from 10 to 128.
Packets that match the dialer group specified trigger a connection request.
Examples
The following example specifies dialer access group number 1. The destination address of the packet is evaluated against the access list specified in the associated dialer-list command. If it passes, either a call is initiated (if no connection has already been established) or the idle timer is reset (if a call is currently connected).
Related Commands
|
|
|
|---|---|
Defines a dialer list to control dialing by protocol or by a combination of protocol and an access list. |
dialer-list protocol (Dial)
To define a dial-on-demand routing (DDR) dialer list for dialing by protocol or by a combination of a protocol and a previously defined access list, use the dialer-list protocol command in global configuration mode. To delete a dialer list, use the no form of this command.
dialer-list dialer-group protocol protocol-name { permit | deny | list access-list-number | access-group }
no dialer-list dialer-group [ protocol protocol-name [ list access-list-number | access-group ]]
Syntax Description
Number of a dialer access group identified in any dialer-group interface or template configuration command. Up to 128 dialer groups can be configured. |
|
One of the following protocol keywords: appletalk, bridge, clns, clns_es, clns_is, decnet, decnet_router-L1, decnet_router-L2, decnet_node, ip, ipx, or ipv6. |
|
Specifies that an access list will be used for defining a granularity finer than an entire protocol. |
|
Access list numbers specified in any DECnet, IP, or Novell IPX standard or extended access lists, including Novell IPX extended service access point (SAP) access lists and bridging types. See Table 2 for the supported access list types and numbers. |
|
Filter list name used in the clns filter-set and clns access-group commands. |
Command Default
Command Modes
Command History
Usage Guidelines
The various no forms of this command have the following effects:
- The no dialer-list dialer-group command deletes all lists configured for the specified dialer access group, regardless of the keyword previously used ( permit, deny, protocol, or list).
- The no dialer-list dialer-group protocol protocol-name command deletes all lists configured for the specified dialer access group and protocol protocol-name.
- The no dialer-list dialer-group protocol protocol-name list access-list-number command deletes the specified list.
The dialer-list protocol command permits or denies access to an entire protocol.
The dialer-list protocol command with the optional list keyword provides finer permission granularity and also supports protocols that were not previously supported. This command also applies protocol access lists to dialer access groups to control dialing using DDR. The dialer access groups are defined with the dialer-group command.
Table 2 lists the access list types and numbers that the dialer-list protocol command supports. The table does not include International Organization for Standardization Connectionless Network Service (ISO CLNS) because that protocol uses filter names instead of predefined access list numbers.
|
|
|
|---|---|
Examples
Dialing occurs when an interesting packet (one that matches access list specifications) needs to be output on an interface. Using the standard access list method, packets can be classified as interesting or uninteresting. The following example classifies all other IP packets as interesting and permits them to initiate calls:
Then the following command places list 101 into dialer access group 1:
In the following example, DECnet access lists allow any DECnet packets with source area 10 and destination area 20 to trigger calls:
Then the following command places access list 301 into dialer access group 1:
In the following example, a CLNS filter is defined and then the filter is placed in dialer access group 1:
The following example configures an IPv6 access list named list2 and places the access list in dialer access group 1:
Related Commands
dial-peer cor custom
To specify that named class of restrictions (COR) apply to dial peers, use the dial-peer cor custom command in global configuration mode.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must use the dial-peer cor custom command and the name command to define the names of capabilities before you can specify COR rules and apply them to specific dial peers.
Examples of possible names might include the following: call1900, call527, call9, and call911.
Note You can define a maximum of 64 COR names.
Examples
The following example defines two COR names:
Related Commands
|
|
|
|---|---|
dial-peer cor list
To define a class of restrictions (COR) list name, use the dial-peer cor list command in global configuration mode. To remove a previously defined COR list name, use the no form of this command.
no dial-peer cor list list-name
Syntax Description
List name that is applied to incoming or outgoing calls to specific numbers or exchanges. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
A COR list defines a capability set that is used in the COR checking between incoming and outgoing dial peers.
Examples
The following example adds two members to the COR list named list1:
Related Commands
|
|
|
|---|---|
dial-shelf split backplane-ds0
To connect two router shelves to a dial shelf, use the dial-shelf split backplane-ds0 command in global configuration mode. To remove the connection, use the no form of this command.
dial-shelf split backplane-ds0 { predefined-option | userdefined option }
no dial-shelf split backplane-ds0
Syntax Description
Predefined backplane DS0 pairs. See Table 3 for a list of these options. |
|
Number of backplane DS0 interfaces used by the router shelf that you define, in the range 128 to 2048. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The options for this command come in pairs and vary according to the desired configuration. You will need to log in to each router shelf and separately configure the routers for the intended load. In most circumstances, it is recommended that the predefined options remain selected. These options are designed to be matched pairs, as seen in Table 3 . You can select the userdefined keyword and define your own split, if needed. Table 3 lists the predefined options.
|
|
|
|
|
||||
|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
||
|
|
|
||||||
|
|
|
||||||
|
|
|
||||||
|
|
|
||||||
51 |
|
|
|||||
|
|
|
||||||
|
1.This option is used to revert to the default for an environment that uses six E1 lines. |
The dial-shelf split slot command must be defined for the dial-shelf split backplane-ds0 command to be active.
Even if your system is already using a split dial shelf configuration, configuring one router shelf to handle two T3 trunks and the other router to handle the third trunk requires you to take the entire access server out of service. Busyout all connections before attempting to reconfigure. The configuration must be changed to set up one pool of TDM resources that can be used by either DMM cards or UPC and a second pool of two streams that contains TDM resources that can be used only by UPCs.
You may have more trunk capacity than 2048 calls. It is your decision how to provision the trunks so the backplane capacity is not exceeded. If more calls come in than backplane DS0 capacity for that half of the split, the call will be rejected and an error message printed for each call. This cannot be detected while a new configuration is being built because the router cannot tell which T1 trunks are provisioned and which are not. The user may want some trunks in hot standby.
The DMM, HMM, and VoIP cards can use only 1792 DS0 of the available 2048 backplane DS0. The UPC and trunk cards can use the full 2048 backplane DS0.
The show tdm splitbackplane command shows the resources in two groups, the first 1792 accessible to all cards, and the remaining 256 accessible only to UPC and trunk cards.
Examples
The following example shows how to configure two router shelves. Refer to Table 3 to interpret the options specified.
Configure router shelf 1 to run two CT3 interfaces with channel-associated signaling (CAS) and the ability to answer 1344 calls:
Configure router shelf 2 to run one CT3 interface with CAS on the second router shelf and the ability to answer 672 calls:
The total calls configured for the system are 2036 (1344 plus 672).
Related Commands
|
|
|
|---|---|
Displays modem and PRI channel assignments with streams and channels on the modem side as assigned to the unit and channels on the PRI side of the TDM assignment. |
dial-shelf split slots
To configure split dial shelves, use the dial-shelf split slots command in global configuration mode. To change the router shelf to normal mode, if a router is in split mode and the other router shelf has already relinquished control of all dial shelf slots or is switched off, use the no form of this command.
dial-shelf split slots slot-numbers
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You allocate the slots in the dial shelf between the two router shelves to achieve the desired configuration. The two router shelves are both configured to run in split mode by means of the dial-shelf split slots command. While a router is in split mode, additional slots can be added to the set that the router owns by re-entering the dial-shelf split slots command listing the new slots. The effect of entering two or more dial-shelf split slots commands with different slot numbers is cumulative.
Slots must be explicitly removed from the list of router-owned slots with the dial-shelf split slots remove command.
A single router can also be configured in split mode, but with no slots owned, by using the dial-shelf split slots none command.
When you configure a Cisco AS5800 system to operate in split mode, it is the same as having two Cisco AS5800 systems with each having a separate set of feature boards assigned to its router; they just happen to be sharing a single dial shelf. Modem pooling, for example, is the same as if you had two separate Cisco AS5800 systems. Router shelf 1 has a modem pool that consists of all the modem cards that reside in slots owned by router shelf 1. The same situation applies to router shelf 2.
Examples
The following example would configure the router shelf to own slots 0 through 2 and 6 through 8.
In this example, the other router shelf could be configured to own the other slots: 3, 4, 5, 9, 10, and 11.
Related Commands
|
|
|
|---|---|
Configures the router in dial shelf split mode but with no slots owned. |
|
dial-shelf split slots none
To configure the router in dial shelf split mode but with no slots owned, use the dial-shelf split slots none command in global configuration mode.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The dial-shelf split slots none command is useful for configuring a single router in split mode, but with no slots owned.
Examples
The following example changes dial shelf slot ownership. The router will no longer have ownership of any dial shelf slots.
Related Commands
|
|
|
|---|---|
dial-shelf split slots remove
To remove slots configured in split mode, use the dial-shelf split slots remove command in global configuration mode.
dial-shelf split slots remove slot-numbers
Syntax Description
List of the dial shelf slot numbers to be removed,separated by spaces, in the range 0 to 11. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
To move a slot from the control of one router shelf to the others, the router releasing the slot should be modified first by entering the dial-shelf split slots remove command, specifying the slot numbers to be released. The released slots can then be added to the slot set of the other router by re-entering the dial-shelf split slots command including the new slot numbers.
The router shelf that is losing the slot frees any resources and clears any state associated with the card in the slot it is relinquishing. The dial shelf controller (DSC) reconfigures its hub to ignore traffic from that slot, and if there is a card in the slot it will be reset. This ensures that the card frees up any TDM resource it might be using and allows it to restart under control of the router shelf that is subsequently configured to own the slot.
Examples
The following example removes dial shelf slot 8 from the list of owned dial shelf slots:
Related Commands
|
|
|
|---|---|
Configures the router in dial shelf split mode but with no slots owned. |
dial-tdm-clock
To configure the clock source and priority of the clock source used by the time-division multiplexing (TDM) bus on the dial shelf of the Cisco AS5800, use the dial-tdm-clock command in global configuration mode. To return the clock source and priority to the default values, use the no form of this command.
dial-tdm-clock priority number { external { e1 | t1 } [ 120ohm ] | freerun | trunk-slot slot port port } [ line { 0 | 1 }]
no dial-tdm-clock priority number { external { e1 | t1 } [ 120ohm ] | freerun | trunk-slot slot port port } [ line { 0 | 1 }]
Syntax Description
Command Default
If no clock sources are specified, the software selects the first available good clock source on a trunk port.
Command Modes
Command History
Usage Guidelines
The TDM bus in the backplane on the dial shelf must be synchronized to the T1/E1 clocks on the trunk cards. The DSC card on the dial shelf provides hardware logic to accept multiple clock sources as input and use one of them as the primary source to generate a stable, PPL synchronized output clock. The input clock can be any of the following sources:
- Trunk port in slots 0 through 5 (up to 12 can be selected (two per slot)
- An external T1 or E1 clock source fed directly through a connector on the DSC card
- A free running clock from an oscillator in the clocking hardware on the DSC card
The clock commands are listed in the configuration file with the highest priority listed first.
If the current primary clock source is good, specifying another clock source of higher priority does not cause the clock source to switch to the higher priority clock source. The new higher priority clock source is used as a backup clock source. This prevents switching of the clock source as you enter multiple dial-tdm-clock priority configuration commands in random order. Also, it is important not to disturb the existing clock source as long as it is good. To force the new higher priority clock source to take over from a currently good primary clock source, configure the new clock source and use the no dial-tdm-clock priority command to remove the current primary clock source.
To display the current primary and backup clocks along with their priorities, use the show dial-shelf clocks EXEC command.
Examples
In the following example, an external clock source is set at priority 1 and the trunk card in slot 4, port 1 is set at priority 5:
Related Commands
|
|
|
|---|---|
Displays information about the dial shelf, including clocking information. |
disconnect
To disconnect a line, use the disconnect command in EXEC mode.
Syntax Description
(Optional) Number of the line or name of the active network connection to be disconnected. |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Do not disconnect a line to end a session. Instead, log off the host, so that the Cisco IOS software can clear the connection. Then end the session. If you cannot log out of an active session, disconnect the line.
Examples
In the following example, the user disconnects from the device Remote to return to the router:
Related Commands
|
|
|
|---|---|
dnis group
To include a group of Dialed Number Identification Service (DNIS) numbers in a customer profile, use the dnis group command in customer profile configuration mode. To remove a DNIS group from a customer profile, use the no form of this command.
dnis group { default | name dnis-group-name }
no dnis group { default | name dnis-group-name }
Syntax Description
Command Default
Command Modes
Customer profile configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Use the dnis group customer profile configuration command to include a group of DNIS numbers in a customer profile or discriminator.
Examples
The following example includes the DNIS group called customer1dnis in the customer1 customer profile:
Related Commands
|
|
|
|---|---|
ds0 busyout (channel)
To busyout one or more digital signal level 0s (DS0s), use the ds0 busyout command in controller configuration mode. To cancel busyout on a DS0, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.0, and supported the E1and DMM HMM (Double Modem Module [12] Hex Modem Module [6]). |
Usage Guidelines
Use the ds0 busyout command when you to busyout a one or more DS0s (channels). If there is an active call, the software waits until the call terminates by a disconnection; then the DS0 is busied out. First you must specify the T1 line (port) containing the 24 DS0s, using the controller T1 command.
To busyout all DS0s on a trunk card or all modems on a modem card, use the busyout privileged EXEC command.
To display the busyout information, use the show busyout privileged EXEC command.
Note The ds0 busyout command only applies to cas-group command configurations for channel-associated signaling. This command has no effect on pri-group command configurations.
Examples
In this example, the controller T1 is configured with cas-group (channel-associated signaling). The following example removes DS0s 1 through 10 from dialup services. These DS0s are assigned to the T1 port (line) in shelf 6, slot 0, port 0:
Related Commands
ds0 busyout-threshold
To define a threshold to maintain a balance between the number of DS0s and modems, use the ds0 busyout-threshold command in global configuration mode. To remove the threshold, use the no form of this command.
Cisco AS5300 and AS5800 Access Servers Only
ds0 busyout-threshold threshold-number
no ds0 busyout-threshold threshold-number
Note This command is the same as the modem busyout-threshold command for the Cisco AS5350 and AS5400 access servers.
Syntax Description
Number of modems that are free when the router should enforce the stipulation that the number of free DS0 lines is less than or equal to the number of modems. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was changed to ds0 busyout-threshold for the Cisco AS5300 and AS5800 access servers. |
Usage Guidelines
The ds0 busyout-threshold command functionality is also often termed autobusyout. This command applies to all DS0 lines coming into the router and counts all free modems in all pools.
The ds0 busyout-threshold command periodically checks to see if the number of free modems is less that the user specified threshold and if it is it ensures the number of free DS0 channels is less than or equal to the number of modems.
This command should only be used where excess calls to one router are forwarded by the exchange to an additional router on the same exchange group number.
Since the ds0 busyout-threshold command checks only periodically, the threshold should be greater than the number of calls the user expects to receive in 1 minute plus a safety margin. For example, if the user receives an average of 10 calls per minute, then a threshold of 20 would be advised. Very small thresholds should be avoided since they do not allow sufficient time for the exchange to respond to out-of-service notifications from the router, and callers may receive busy signals when free modems are all used.
The number of DS0 lines in normal operating conditions should be approximately equal to the number of modems (for example, within 30). If it is not, this will cause a lot of messaging traffic to the exchange and may cause active calls to be dropped. This is not a concern for short periods, that is, when modem cards are replaced.
On T3 controllers, any contained T1 controllers that are not in use should be undeclared to remove them from the autobusyout list.
Examples
The following example shows how you might configure the ds0 busyout-threshold command:
Related Commands
ds0-group (controller e1)
To define E1 channels for compressed voice calls and the channel-associated signaling (CAS) method by which the router connects to the PBX or PSTN, enter the ds0-group command in controller configuration mode. To remove the group and signaling setting, use the no form of this command.
ds0-group channel timeslots range type signal
no ds0-group channel timeslots range type signal
Syntax Description
Command Default
No channel-associated signaling is configured on the controller. All R2 signaling types have DNIS turned on by default.
Command Modes
Command History
Usage Guidelines
Use this command to configure support for incoming and outgoing call signals (such as on-hook and off-hook) on each E1 controller.
If you specify the time-slot range 1-31, the system software automatically uses the sixteenth time slot to transmit the channel-associated signaling.
The signaling you configure on the access server must match the signaling used by the central office. For example, if the central office switch is forwarding R2 analog signaling to a Cisco 2600 or 3600 series router, the E1 controller on the router must also be configured for R2 analog signaling (r2-analog).
All R2 signaling options have DNIS support turned on by default. If you enable the ani option, the collection of DNIS information is still performed. Specifying the ani option does not disable DNIS. DNIS is the number being called. ANI is the caller’s number. For example, if you are configuring router A to call router B, the DNIS number is router B and the ANI number is router A. ANI is very similar to Caller ID.
To customize the R2 signaling parameters, refer to the cas-custom controller configuration command. When you enable the ds0-group command, the cas-custom command is automatically set up to be polled for configuration information. However, unless you enable or turn on specific features with the ds0-custom command, the cas-custom feature has an empty set of signaling parameters.
DNIS is automatically collected for modem pools and R2 tone signaling. You do not need to specify the collection of DNIS information with the ds0-group command. However, if you are using non-R2 tone signaling, the system must be manually configured to collect DNIS information. For non-R2 CAS signaling, DNIS collection is done only for E&M-fgb.
Examples
In most cases, you will configure the same channel-associated signaling on each E1 controller. The following examples configure signaling and customized parameters on controller E1 2 using the ds0-group and cas-custom controller configuration commands.
The actual channel-associated signaling is configured on the sixteenth time slot, which is the reason why this time slot does not come up in the following output.
The following example shows all the supported E1 signaling types on a Cisco 2600 or 3600 series router.
Note Cisco IOS Releases later than 12.2 do not support the Single Attachment Station (SAS) CAS options of sas-loop-start and sas-ground-start.
R2 signaling parameters can be customized with the cas-custom controller configuration command:
encap-sequence
To assign an encapsulation sequence number to a priority class in a multiclass multilink PPP bundle, use the encap-sequence command in policy-map class configuration mode. To reset the default value, use the no form of this command.
encap-sequence [ sequence-id | none ]
Syntax Description
Command Default
Command Modes
Policy-map class configuration
Command History
|
|
|
|---|---|
This command was introduced and implemented on the Cisco 10000 series router for the PRE2. |
Usage Guidelines
The encap-sequence command allows you to assign sequence numbers to priority classes in a policy map for multiclass multilink PPP encapsulation. This command is only supported on the PRE2.
A class with a multiclass multilink PPP sequence number must have an associated queue action such as bandwidth and shape. The sequence number assigned to each priority class must be unique.
The default sequence number for class-default is 0 and it is not configurable.
If you do not assign a sequence number to a priority class, the priority queue packets use PPP encapsulation. Interleaving is allowed for priority traffic regardless of the encapsulated sequence number configuration.
Examples
The following example shows that class voice has the highest priority and that packets are not encapsulated with a sequence number for multiclass multilink PPP.
Related Commands
|
|
|
|---|---|
encapsulation cpp
Note Effective with Cisco IOS Release 12.3(4)T, the encapsulation cpp command is no longer available in Cisco IOS software.
To enable encapsulation for communication with routers or bridges using the Combinet Proprietary Protocol (CPP), use the encapsulation cpp command in interface configuration mode. To disable CPP encapsulation, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was removed and is no longer available in Cisco IOS software. |
Usage Guidelines
Use this command to communicate over an ISDN interface with Cisco 700 and 800 series (formerly Combinet) routers that do not support PPP but do support CPP.
Most Cisco routers support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
The Cisco 700 and 800 series routers support only IP, IPX, and bridging. For AppleTalk, these Cisco routers automatically perform half-bridging.
Examples
The following example configures BRI interface 0 to communicate with a router or bridge that does not support PPP:
The following example configures PRI serial interface 1/1:23 to communicate with a router or bridge that does not support PPP:
cpp authentication
Related Commands
failover group-number
To configure shelf redundancy for Cisco AS5800 universal access servers, use the failover group-number command in redundancy configuration mode. To disable redundancy, use the no form of this command.
failover group-number group-code
no failover group-number group-code
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T. |
Usage Guidelines
This command must be configured on both router shelves. The group-code argument is used by the system controller and must be the same for both router shelves forming the redundant pair.
For successful failover to occur, both router-shelf configurations must be synchronized. Configure each router shelf separately, as active and backup respectively, with the same configuration except for the IP address on egress interfaces.
Note Test the backup router shelf configuration before deployment in a production environment.
Examples
The following example assigns the configured router shelf to the redundancy pair designated as 25. These commands must be issued on both router shelves in the redundant router-shelf pair:
Related Commands
|
|
|
|---|---|
Displays current or historical status and related information and displays shelf-redundancy status. |
firmware filename
To use a different DSL firmware other than the embedded one, use the fi rmware filename command in controller configuration mode. To revert back to the embedded firmware, use the no form of this command.
firmware filename flash: firmware-filename
Syntax Description
Defaults
Command Modes
Configuration controller mode.
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example shows how to upgrade the firmware file.
Related Commands
|
|
|
|---|---|
Debugs the VDSL firmware download state, DSL line training progress, and VDSL interface status |
firmware location
To download firmware into the modems, use the firmware location command in Service Processing Element (SPE) configuration mode. To revert the router to the system embedded image default, use the no form of this command.
firmware location [ IFS ] filename
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
Use the firmware location SPE configuration command to download firmware into your modems. This command specifies the location of the firmware file and downloads the firmware in the range of SPEs specified, depending on the states configured by the firmware upgrade command. Use the firmware location command with the firmware upgrade command. The entire SPE is affected by the firmware location command.
The latest SPE firmware image can usually be retrieved from Cisco.com. You must first copy the SPE image from a TFTP server to Flash memory using the copy tftp flash command.
The firmware location command is a configuration command and must be saved into the system configuration using the write memory command; otherwise, at the next reboot downloading of the specified firmware will not occur.
The firmware location command was first supported in Cisco IOS Release 12.0(4)XI1. For earlier images, use the copy command. For the Cisco IOS Release 12.0(4)XI1 images, the copy flash modem command is disabled for MICA technologies modems and newer versions of the 56-kbps Microcom modems. The older V.34 Microcom modems still use the copy command for downloading in Cisco IOS Release 12.0(4)XI1 images.
Note This command should be used when traffic is low because the firmware location download will not begin until the modems have no active calls. Otherwise, use the firmware upgrade command to customize the scheduling of modem downloads for your needs.
You cannot use the firmware location command on SPEs that are in the Bad state.
Examples
The following example shows how to display all legal IFSs:
The following example shows how to enter the SPE configuration mode, set the range of SPEs, specify the firmware file location in Flash memory, download the file to the SPEs, and display a status report using the show spe EXEC command:
The following configuration example specifies a firmware file located in Flash memory:
The following configuration example shows how to download firmware that is not bundled with the Cisco IOS image:
The following configuration example shows how to download firmware that is bundled with the
Cisco IOS image:
Related Commands
|
|
|
Copies the SPE image from a TFTP server to the Flash memory. |
|
Performs download maintenance on SPEs that are marked for recovery. |
|
firmware upgrade
To modify the way in which the service processing element (SPE) will be downloaded, use the firmware upgrade command in SPE configuration mode. To revert to the default SPE firmware upgrade option, busyout, use the no form of this command.
firmware upgrade { busyout | recovery | reboot }
Cisco AS5350, Cisco AS5400, and Cisco AS5800
firmware upgrade [ busyout | download-maintenance | reboot ]
Syntax Description
Command Default
An upgrade occurs when all calls are terminated on the SPE (busyout).
For the Cisco AS5350, Cisco AS5400, and Cisco AS5800 there is no default.
Command Modes
Command History
Usage Guidelines
Three methods of upgrade are available: busyout, reboot, and download-maintenance or recovery.
The reboot keyword requests the Cisco access servers to upgrade SPE firmware at the next reboot.
The busyout keyword upgrades SPE firmware after waiting for all calls to be terminated on an SPE.
The download-maintenance or recovery keyword requests SPE firmware download during maintenance time.
Use this command in conjunction with the firmware location command and the spe download maintenance command.
The SPE firmware location command is designed to integrate all continuous ranges of SPEs containing the same firmware location. However, the firmware upgrade command does not affect the ranges of SPEs. As such, all SPEs within the ranges of SPEs must have the same firmware upgrade mode or the router uses the default upgrade mode to busyout state. If you want to upgrade a single SPE within an existing range of SPEs with a different upgrade mode than is currently configured, you must first change the upgrade mode for the entire range of SPEs and then change the firmware location for the specific SPE being upgraded. Furthermore, each time you merge ranges of SPEs due to configuration changes, verify that the configuration of the SPE firmware upgrade remains effective to what is desired.
Examples
The following example sets the SPEs and specifies the firmware upgrade to take place once all calls are terminated on the SPE:
If the busyout upgrade command is specified, or if no upgrade mode is specified, the SPE modems are set into a “pending download” state when you use the firmware location command on the specified SPE. The pending download state prevents any modem in that state to be allocated for new calls until the state is cleared. Modems with active calls remain active for their call durations, but enter the pending download state when they terminate. This pending download state can be cleared only when the SPE is finally downloaded. When all modems within the SPE are in the pending download state and no active calls remain on the SPE, the SPE is reloaded. The busyout option is the fastest way to upgrade modems on an active router but can severely impact the capacity of the router during the upgrade. The following example sets the default option for the firmware upgrade process:
If reboot upgrade is specified, the SPE modems are not reloaded to the new firmware location until the router is rebooted. The reboot upgrade option is useful for routers that need to have their SPE upgraded and that also will be rebooted for maintenance. When the new firmware is configured, the configuration takes effect after the reboot takes place. The following example sets the firmware upgrade reboot:
If recovery upgrade is specified, the SPE modems are reloaded based on the modem recovery algorithm. Only when no active calls exist on the SPE does the firmware download take place. Furthermore, at the time configured with the modem recovery maintenance command, the modem recovery maintenance process attempts, in a controller fashion, to reload the modems by busying out the modems for a window duration of time to make the download take place. Refer to the modem recovery documentation for more information. The recovery upgrade option upgrades modems on an active router with the least impact. Capacity is kept at a maximum. However, this option may take a few days for all modems to be reloaded to the new firmware location. The following example sets the system for a firmware upgrade recovery:
For the Cisco AS5350, Cisco AS5400, or Cisco AS5800, use the following syntax to set the system for a firmware upgrade recovery:
Related Commands
|
|
|
Specifies the scheduled modem maintenance recovery behavior. |
|
Performs download maintenance on SPEs that are marked for recovery. |
|
flowcontrol
To set the method of data flow control between the terminal or other serial device and the router, use the flowcontrol command in line configuration mode. To disable flow control, use the no form of this command.
flowcontrol { none | software [ lock ] [ in | out ] | hardware [ in | out ]}
no flowcontrol { none | software [ lock ] [ in | out ] | hardware [ in | out ]}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
Usage Guidelines
When software flow control is set, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them using the stop-character and start-character commands.
If a remote Telnet device requires software flow control, the remote system should not be able to turn it off. Using the lock option makes it possible to refuse “dangerous” Telnet negotiations if they are inappropriate.
Examples
The following example sets hardware flow control on line 7:
Related Commands
|
|
|
|---|---|
group-range
To create a list of member asynchronous interfaces (associated with a group interface), use the group-range command in interface configuration mode. To remove an interface from the member list, use the no form of this command.
group-range low-end-of-interfacerange high-end-of-interfacerange
Syntax Description
Beginning interface number to be made a member of the group interface. |
|
Ending interface number to be made a member of the group interface. |
|
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Using the group-range command, you create a group of asynchronous interfaces that are associated with a group asynchronous interface on the same device. This group interface is configured by using the interface group-async command. This one-to-many structure allows you to configure all associated member interfaces by entering one command on the group interface, rather than entering this command on each interface. You can customize the configuration on a specific interface by using the member command. Interface numbers can be removed from the interface group using the no group-range command.
Examples
The following example defines interfaces 2, 3, 4, 5, 6, and 7 as members of asynchronous group interface 0:
Feedback