-
Cisco IOS Wide-Area Networking Command Reference, Release 12.3 T
-
Introduction
-
Wide-Area Networking Commands: A through B
-
Wide-Area Networking Commands: C
-
Wide-Area Networking Commands: D through E
-
Wide-Area Networking Commands: frame-relay adaptive-shaping through frame-relay lmi-type
-
Wide-Area Networking Commands: frame-relay local-dlci through fr-atm connect dlci
-
Wide-Area Networking Commands: H through L
-
Wide-Area Networking Commands: M through R \r\n
-
Wide-Area Networking Commands: scrambling cell-payload through show dxi pvc
-
Wide-Area Networking Commands: show frame-relay through show vc-group
-
Wide-Area Networking Commands: show x25 through svc
-
Wide-Area Networking Commands: T through x25 nvc
-
Wide-Area Networking Commands: x25 ops through xot access-group
-
Table Of Contents
user unidentified traffic permit
threshold de
To configure the threshold at which discard eligible (DE)-marked packets will be discarded from switched permanent virtual circuits (PVCs) on the output interface, use the threshold de command in Frame Relay congestion management configuration mode. To remove the threshold configuration, use the no form of this command.
threshold de percentage
no threshold de percentage
Syntax Description
percentage
Threshold at which DE-marked packets will be discarded, specified as a percentage of maximum queue size.
Defaults
100%
Command Modes
Frame Relay congestion management configuration
Command History
Usage Guidelines
You must enable Frame Relay congestion management on the interface before congestion management parameters will be effective. To enable Frame Relay congestion management and to enter Frame Relay congestion management configuration mode, use the frame-relay congestion-management interface command.
You must enable Frame Relay switching, using the frame-relay switching global command, before the threshold de command will be effective on switched PVCs.
Examples
The following example shows how to configure a DE threshold of 40% on serial interface 1.
interface serial1encapsulation frame-relayframe-relay congestion-managementthreshold de 40Related Commands
threshold ecn
To configure the threshold at which ECN bits will be set on packets in switched PVCs on the output interface, use the threshold ecn Frame Relay congestion management configuration command. To remove the threshold configuration, use the no form of this command.
threshold ecn {bc | be} percentage
no threshold ecn {bc | be} percentage
Syntax Description
Defaults
100%
Command Modes
Frame Relay congestion management
Command History
Usage Guidelines
You must enable Frame Relay congestion management on the interface before congestion management parameters will be effective. To enable Frame Relay congestion management and to enter Frame Relay congestion management configuration mode, use the frame-relay congestion-management interface command.
You must enable Frame Relay switching, using the frame-relay switching global command, before the threshold ecn command will be effective on switched PVCs.
You can configure separate queue thresholds for committed and excess traffic.
Configure the Be ECN threshold so that it is greater than or equal to zero and less than or equal to the Bc ECN threshold. Configure the Bc ECN threshold so that it is less than or equal to 100.
Examples
The following example shows how to configure a Be threshold of 0 and a Bc threshold of 20% on serial interface 1.
interface serial1encapsulation frame-relayframe-relay congestion-managementthreshold ecn be 0threshold ecn bc 20Related Commands
timeout setup
To configure the amount of time allowed to set up a control channel with a remote provider edge (PE) router at the other end of a Layer 2 pseudowire, use the timeout setup command in L2TP class configuration mode. To disable the configured value, use the no form of this command.
timeout setup seconds
no timeout setup seconds
Syntax Description
seconds
The number of seconds allowed to set up a Layer 2 control channel. The valid values range from 60 to 6000. The default value is 300 seconds.
Defaults
seconds: 300
Command Modes
L2TP class configuration
Command History
12.0(23)S
This command was introduced.
12.3(2)T
This command was integrated into Cisco IOS Release 12.3(2)T.
Usage Guidelines
Use this command to configure the amount of time that can be spent attempting to establish a control channel.
Examples
The following example sets a timeout period of 200 seconds to establish a control channel with a remote peer in Layer 2 pseudowires that have been configured with the L2TP class named "l2tp-class1":
Router(config)# l2tp-class l2tp-class1Router(config-l2tp-class)# timeout setup 200Related Commands
l2tp-class
Creates a template of L2TP control plane configuration settings that can be inherited by different pseudowire classes and enters L2TP class configuration mode.
timeouts (SSG-radius-proxy)
To enter SSG-radius-proxy-timers configuration mode, use the timeouts command in SSG-radius-proxy configuration mode. To restore all timeouts, use the no form of this command.
timeouts
no timeouts
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
SSG-radius-proxy configuration
Command History
12.2(15)B
This command was introduced.
12.3(4)T
This command was integrated into Cisco IOS Release 12.3(4)T.
Usage Guidelines
Use this command to enter SSG-radius-proxy-timeouts configuration mode to configure SSG RADIUS proxy handoff, idle, IP address, and Mobile Station ID (MSID) timeouts.
Examples
The following example shows how to enter SSG-radius-proxy-timeouts mode:
ssg radius-proxytimeoutsubr
To configure unspecified bit rate (UBR) quality of service (QoS) and specify the output peak cell rate (PCR) for an ATM permanent virtual circuit (PVC), PVC range, switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle member, use the ubr command in the appropriate command mode. To remove the UBR parameter, use the no form of this command.
ubr output-pcr [input-pcr]
no ubr output-pcr [input-pcr]
Syntax Description
output-pcr
The output PCR in kbps.
input-pcr
(Optional for SVCs only) The input peak cell rate (PCR) in kilobits per second. If this value is omitted, the input-pcr will equal the output-pcr.
Defaults
UBR QoS at the maximum line rate of the physical interface.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Command History
Usage Guidelines
To configure ATM SVCs with an output PCR and an input PCR that differ from each other, you must expressly configure an output value and an input value using the output-pcr and input-pcr arguments, respectively.
Configure QoS parameters using the ubr, ubr+, or vbr-nrt command. The last command you enter will apply to the PVC or SVC you are configuring.
If the ubr command is not explicitly configured on an ATM PVC, SVC, or VC bundle member, the VC inherits the following default configuration (listed in order of next highest precedence):
•
Configuration of any QoS command (ubr, ubr+, or vbr-nrt) in a VC class assigned to the PVC or SVC itself.
•
•
•
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command. This command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use this command in bundle-vc configuration mode, first enter the bundle command to specify the bundle, then enter bundle configuration mode. Then enter the pvc-bundle configuration command to add the VC to the bundle as a member of it and enter bundle-vc configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next highest precedence):
•
•
•
Examples
The following example specifies the output-pcr argument for an ATM PVC to be 100,000 kbps:
pvc 1/32ubr 100000The following example specifies the output-pcr and input-pcr arguments for an ATM SVC to be 10,000 kbps and 9,000 kbps, respectively:
svc lion nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05ubr 10000 9000Related Commands
ubr+
To configure unspecified bit rate (UBR) quality of service (QoS) and specify the output peak cell rate and output minimum guaranteed cell rate for an ATM permanent virtual circuit (PVC), PVC range, switched virtual circuit (SVC), virtual circuit (VC) class, or VC bundle member, use the ubr+ command in the appropriate command mode. To remove the UBR+ parameters, use the no form of this command.
ubr+ output-pcr output-mcr [input-pcr] [input-mcr]
no ubr+ output-pcr output-mcr [input-pcr] [input-mcr]
Syntax Description
Defaults
UBR QoS at the maximum line rate of the physical interface.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Command History
Usage Guidelines
To configure ATM SVCs with an output PCR and an input PCR that differ from each other, you must expressly configure an output value and an input value using the output-pcr, output-mcr, input-pcr, and input-mcr arguments, respectively.
Configure QoS parameters using the ubr, ubr+, or vbr-nrt command. The last command you enter will apply to the PVC or SVC that you are configuring.
If the ubr+ command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
•
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command before you enter the ubr+ command. This command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use this command in bundle-vc configuration mode, first enter the bundle command to specify the bundle the VC member belongs to, then enter bundle configuration mode. Then enter the pvc-bundle bundle configuration command to add the VC to the bundle as a member of it.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of next highest precedence):
•
•
•
Examples
The following example specifies the output-pcr argument for an ATM PVC to be 100,000 kbps and the output-mcr to be 3000 kbps:
pvc 1/32ubr+ 100000 3000The following example specifies the output-pcr, output-mcr, input-pcr, and input-mcr arguments for an ATM SVC to be 10,000 kbps, 3000 kbps, 9000 kbps, and 1000 kbps, respectively:
svc lion nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05ubr+ 10000 3000 9000 1000Related Commands
user suspect maximum
To specify the maximum number of Service Selection Gateway (SSG) transparent autologon suspect (SP) users that can be added to the suspect user list, use the user suspect maximum command in transparent auto-logon configuration mode. To remove the specification, use the no form of this command.
user suspect maximum value
no user suspect maximum value
Syntax Description
value
Maximum number of suspect users that can be added to the SP list. Valid range is from 10 to 5000. The default is 5000.
Defaults
The default maximum number of suspect users that can be added to the suspect user list is 5000.
Command Modes
Transparent auto-logon configuration
Command History
Usage Guidelines
An SSG transparent autologon suspect user is a user whose authentication, authorization, and accounting (AAA) authorization resulted in an access reject.
If the number of suspect users exceeds the maximum value configured, SSG sends a syslog message and does not add any further users to the SP list.
Examples
The following example specifies that the maximum number of suspect users that can be added to the SP list is 200:
Router(config-login-transparent)# user suspect maximum 200Related Commands
user suspect timeout
To specify the maximum length of time for which a Service Selection Gateway (SSG) transparent autologon suspect (SP) user remains in the suspect user list, use the user suspect timeout command in transparent auto-logon configuration mode. To return to the default length of time, use the no form of this command.
user suspect timeout timeout
no user suspect timeout timeout
Syntax Description
timeout
Maximum length of time (in minutes) that a suspect user remains in the suspect user list. Range is from 1 to 34560. Default is 60 minutes.
Defaults
60 minutes
Command Modes
Transparent auto-logon configuration
Command History
Usage Guidelines
If a packet is received for a user who is marked as an SP user, packets to or from this user are dropped or TCP-redirected until the timeout value is reached. When the timeout value is reached, any new traffic received by SSG from the user triggers the transparent logon procedure.
Examples
The following example specifies that a suspect user will remain in the suspect user list for 30 minutes:
Router(config-login-transparent)# user suspect timeout 30Related Commands
user unidentified timeout
To specify the maximum length of time for which a Service Selection Gateway (SSG) transparent autologon unidentified user remains marked as no response (NR), use the user unidentified timeout command in transparent auto-logon configuration mode. To return to the default timeout value (10 minutes), use the no form of this command.
user unidentified timeout timeout
no user unidentified timeout timeout
Syntax Description
Defaults
10 minutes
Command Modes
Transparent auto-logon
Command History
Usage Guidelines
An unidentified user is marked NR if there is no response from the authentication, authorization, and accounting (AAA) server to an authorization request and the authorization request times out.
If a packet is received for a user who is marked as an NR user, packets to or from this user are dropped or TCP-redirected until the timeout value is reached. When the timeout value is reached, any new traffic received by SSG from the user triggers the transparent logon procedure.
Examples
The following example sets the user unidentified timeout to 5 minutes:
Router(config-login-transparent)# user unidentified timeout 5Related Commands
user unidentified traffic permit
To specify that packets received from a Service Selection Gateway (SSG) transparent autologon user whose authorization request has timed out will be forwarded or received, use the user unidentified traffic permit command in transparent auto-logon configuration mode. To return to the default (packets dropped if user authorization has timed out), use the no form of this command.
user unidentified traffic permit
no user unidentified traffic permit
Syntax Description
This command has no arguments or keywords.
Defaults
Packets received from a user whose authorization request has timed out are dropped.
Command Modes
Transparent auto-logon configuration
Command History
Usage Guidelines
Configuring this command allows traffic flow for NR users toward the service network.
Examples
The following example specifies that packets received from a user whose authorization request has timed out will be forwarded or received:
Router(config-login-transparent)# user unidentified traffic permitRelated Commands
vbr-nrt
To configure the variable bit rate-nonreal time (VBR-NRT) quality of service (QoS) and specify output peak cell rate (PCR), output sustainable cell rate, and output maximum burst cell size for an ATM permanent virtual circuit (PVC), PVC range, switched virtual circuit (SVC), VC class, or VC bundle member, use the vbr-nrt command in the appropriate command mode. To remove the VBR-NRT parameters, use the no form of this command.
vbr-nrt output-pcr output-scr output-mbs [input-pcr] [input-scr] [input-mbs]
no vbr-nrt output-pcr output-scr output-mbs [input-pcr] [input-scr] [input-mbs]
Syntax Description
Defaults
UBR QoS at the maximum line rate of the physical interface.
Command Modes
Interface-ATM-VC configuration (for an ATM PVC or SVC)
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
PVC range configuration (for an ATM PVC range)
PVC-in-range configuration (for an individual PVC within a PVC range)
Command History
Usage Guidelines
Configure QoS parameters using the ubr, ubr+, or vbr-nrt command. The last command you enter will apply to the PVC or SVC you are configuring.
If the vbr-nrt command is not explicitly configured on an ATM PVC or SVC, the VC inherits the following default configuration (listed in order of precedence):
•
•
•
•
To use this command in VC-class configuration mode, enter the vc-class atm global configuration command before you enter the vbr-nrt command. This command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use this command in bundle-vc configuration mode, first enter the pvc-bundle configuration command to add the VC to the bundle as a member of it, then and enter bundle-vc configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance rules (listed in order of precedence):
•
•
•
Examples
The following example specifies the output-pcr argument for an ATM PVC to be 100,000 kbps, the output-scr argument to be 50,000 kbps, and the output-mbs to be 64:
pvc 1/32vbr-nrt 100000 50000 64The following example specifies the VBR-NRT output and input parameters for an ATM SVC:
svc lion nsap 47.0091.81.000000.0040.0B0A.2501.ABC1.3333.3333.05vbr-nrt 10000 5000 32 20000 10000 64Related Commands
vc-class atm
To create a virtual circuit (VC) class for an ATM permanent virtual circuit (PVC), switched virtual circuit (SVC), or ATM interface and enter vc-class configuration mode, use the vc-class atm global configuration command. To remove a VC class, use the no form of this command.
vc-class atm name
no vc-class atm name
Syntax Description
Defaults
No VC class is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
If an SVC command (for example, the idle-timeout or oam-svc command) is applied on a PVC, the command is ignored. This is also true if a PVC command is applied to an SVC.
Examples
The following example creates a VC class named "pvc-qos":
vc-class atm pvc-qosvc-group
To assign multiple Frame Relay data-link connection identifiers (DLCIs) to a virtual circuit (VC) group for Frame Relay-to-ATM Network Interworking (FRF.5), use the vc-group command in global configuration mode. To disable the VC group assignments, use the no form of this command.
vc-group group-name
no vc-group group-name
The vc-group command requires the use of the following command in VC-group configuration mode to provide a map between Frame Relay DLCIs and Frame Relay-SSCS DLCIs:
FR-interface-name FR-DLCI [FR-SSCS-DLCI]
Syntax Description
The following syntax description applies to the VC-group entries:
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
This command specifies the Frame Relay DLCIs in the VC group and maps them to the Frame Relay-SSCS DLCIs. If the optional FR-SSCS DLCI value is not specified, its value is the same as the Frame Relay DLCI.
Examples
The following example shows how to configure an FRF.5 many-to-one connection. The vc-group command maps Frame Relay DLCI 16, 17, 18, and 19 to a VC group named "friends":
Router(config)# vc-group friendsRouter(config-vc-group)# serial0 16 16Router(config-vc-group)# serial0 17 17Router(config-vc-group)# serial0 18 18Router(config-vc-group)# serial0 19 19Related Commands
virtual-template (BBA group)
To configure a PPPoE profile with a virtual template to be used for cloning virtual access interfaces, use the virtual-template command in BBA group configuration mode. To remove the virtual template from a PPPoE profile, use the no form of this command.
virtual-template template-number
no virtual-template template-number
Syntax Description
template-number
Identifying number of the virtual template that will be used to clone virtual-access interfaces.
Defaults
A virtual template is not specified.
Command Modes
BBA group configuration
Command History
Usage Guidelines
Each PPPoE profile can clone virtual-access interfaces using only one virtual template. If you enter a second virtual-template command in a PPPoE profile, it will replace the first virtual-template command.
You can configure different PPPoE profiles to use different virtual templates. You can also configure multiple PPPoE profiles to use the same virtual template.
Examples
The following example shows the configuration of two PPPoE profiles:
bba-group pppoe vpn1virtual-template 1sessions per-vc limit 2sessions per-mac limit 1!bba-group pppoe vpn2virtual-template 2sessions per-vc limit 2sessions per-mac limit 1!Related Commands
virtual-template pre-clone
To specify the number of virtual-access interfaces to be created and cloned from a specific virtual template, use the virtual-template pre-clone command in global configuration mode. To disable precloning, use the no form of this command.
virtual-template template-number pre-clone number
no virtual-template template-number pre-clone number
Syntax Description
template-number
The number of the virtual template interfaces from which the new virtual-access interfaces are created.
number
The number of virtual-access interfaces to be created.
Defaults
Precloning is disabled.
Command Modes
Global configuration
Command History
12.0(3)DC
This command was introduced on the Cisco 6400 node route processor.
12.2(4)T
This command was integrated into Cisco IOS Release 12.2(4)T.
Usage Guidelines
The number of precloned virtual-access interfaces should be set to the number of expected PPPoA and PPPoE sessions.
The precloned virtual-access interfaces will be attached to the PVC upon receipt of the first PPP packet from the client on the PVC. The virtual-access interface will be detached from the PVC upon termination of the PPP session.
When a PPP session is terminated, the virtual-access interface will remain in the router and will be reused. When precloning is disabled, any virtual-access interfaces that were already precloned but have not yet been used will remain in the router for future use.
Examples
The following example shows how to create 1200 precloned virtual-access interfaces on virtual template 1:
virtual-template 1 pre-clone 1200Related Commands
vlan-id dot1q
To enable IEEE 802.1Q VLAN encapsulation for a specific VLAN on an Ethernet interface, use the vlan-id dot1q command in interface configuration mode. To disable 802.1Q encapsulation for a specific VLAN, use the no form of this command.
vlan-id dot1q vlan-id
no vlan-id dot1q vlan-id
Syntax Description
Defaults
IEEE 802.1Q VLAN encapsulation is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows you to enable IEEE 802.1Q VLAN encapsulation for a specific VLAN on an Ethernet interface without associating the VLAN with a subinterface. Configuring 802.1Q VLANs on the main interface without using up subinterfaces increases the number of VLANs that can be configured on a router to 4000 VLANs per interface.
You can configure a VLAN on a main interface and at the same time configure VLANs on subinterfaces of the same interface. However, you cannot configure a specific VLAN on the main interface and on a subinterface at the same time. To configure PPPoE over 802.1Q VLAN support on a subinterface, use the encapsulation dot1q and pppoe enable commands in subinterface configuration mode.
It is not possible to shut down traffic for individual VLANs that are configured on the main interface.
Examples
The following example shows how to configure PPPoE over an 802.1Q VLAN on Fast Ethernet interface 0/0.
interface fastethernet 0/0no ip addressno ip mroute-cacheduplex halfvlan-id dot1q 20pppoe enable group PPPOEexit-vlan-configThe following example configures Ethernet interface 0 to bridge packets using VLAN ID 100 and assigns the interface to bridge group 1:
interface ethernet 0vlan-id dot1q 100description bridged vlan 100bridge-group 1bridge-group 1Related Commands
vlan-range dot1q
To enable IEEE 802.1Q VLAN encapsulation for a range of VLANs on an Ethernet interface, use the vlan-range dot1q command in interface configuration mode. To disable 802.1Q encapsulation for a range of VLANs, use the no form of this command.
vlan-range dot1q start-vlan-id end-vlan-id [native]
no vlan-range dot1q start-vlan-id end-vlan-id
Syntax Description
Defaults
IEEE 802.1Q VLAN encapsulation is not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command allows you to enable IEEE 802.1Q VLAN encapsulation for a range of VLANs on an Ethernet interface without associating each VLAN with a subinterface. Configuring an 802.1Q VLAN range on the main interface without using up subinterfaces increases the number of VLANs that can be configured on a router to 4000 VLANs per interface.
You can configure a VLAN range on a main interface and at the same time configure VLANs outside the range on subinterfaces of the same interface. However, you cannot configure a specific VLAN on the main interface and on a subinterface at the same time. To configure PPPoE over 802.1Q VLAN support on a subinterface, use the encapsulation dot1q and pppoe enable commands in subinterface configuration mode.
It is not possible to shut down traffic for individual VLANs that are configured on the main interface.
To bridge both tagged and untagged packets, regardless of their VLAN ID, you do not need to create a VLAN ID range.
Examples
The following example shows how to configure PPPoE over a range of 802.1Q VLANs on Fast Ethernet interface 0/0.
interface fastethernet 0/0no ip addressno ip mroute-cacheduplex halfvlan-range dot1q 20 30pppoe enable group PPPOEexit-vlan-configThe following example configures Ethernet interface 0 to bridge untagged (native) packets using a range of VLAN IDs from 1 to 500 and assigns the interface to bridge group 1:
interface ethernet 0vlan-range dot1q 1 500 nativedescription 1 to 500bridge-group 1bridge-group 1Related Commands
vpn service
To configure a static domain name, use the vpn service command in ATM VC or VC class configuration mode. To remove a static domain name, use the no form of this command.
vpn service domain-name
no vpn service domain-name
Syntax Description
Defaults
No default behavior or values
Command Modes
ATM VC configuration
ATM VC class configurationCommand History
12.1(1)DC1
This command was introduced on the Cisco 6400 NRP.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
Use the vpn service command in a permanent virtual circuit (PVC) or a PVC range configuration so that PPP over ATM (PPPoA) sessions in those PVCs will be forwarded according to the domain name supplied, without starting PPP.
Examples
In the following partial example, virtual private dialup network (VPDN) group 1 is selected for PPPoA session forwarding based on the domain name domain.com:
vpdn-group 1request-dialinprotocol l2tpdomain abc.cominitiate-to ip 10.1.1.1 priority 1...interface ATM1/0.1 multipointpvc 101protocol ppp virtual-template 1vpn service domain.comx25 accept-reverse
To configure the Cisco IOS software to accept all reverse-charge calls, use the x25 accept-reverse command in interface or X.25 profile configuration mode. To disable this facility, use the no form of this command.
x25 accept-reverse
no x25 accept-reverse
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
X.25 profile configurationCommand History
Usage Guidelines
This command causes the interface to accept reverse-charge calls by default. You can also configure this behavior for each peer with the x25 map interface configuration command.
Examples
The following example sets acceptance of reverse-charge calls:
interface serial 0x25 accept-reverseRelated Commands
x25 address
To set the X.121 address of a particular network interface, use the x25 address command in interface or X.25 profile configuration mode.
x25 address x121-address
Syntax Description
Defaults
Defense Data Network (DDN) and Blacker Front End (BFE) encapsulations have a default interface address generated from the interface IP address. For proper DDN or BFE operation, this generated X.121 address must not be changed. Standard X.25 encapsulations do not have a default.
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
When you are connecting to a public data network (PDN), the PDN administrator will assign the X.121 address to be used. Other applications (for example, a private X.25 service), may assign arbitrary X.121 addresses as required by the network and service design. X.25 interfaces that engage in X.25 switching only do not need to assign an X.121 address.
Examples
The following example sets the X.121 address for the interface:
interface serial 0encapsulation x25x25 address 00000123005The address must match that assigned by the X.25 network service provider.
x25 alias
To configure an interface alias address that will allow this interface to accept calls with other destination addresses, use the x25 alias command in interface or X.25 profile configuration mode.
x25 alias {destination-pattern | x121-address-pattern} [cud cud-pattern]
Syntax Description
Defaults
No alias is configured.
Command Modes
Interface configuration
X.25 profile configurationCommand History
11.2
This command was introduced. It replaces the functionality that was provided by the alias keyword of the x25 route command.
Usage Guidelines
Encapsulation, packet assembler/disassembler (PAD), and Qualified Logical Link Control (QLLC) calls are normally accepted when the destination address is that of the interface (or the zero-length address). Those calls will also be accepted when the destination address matches a configured alias.
Examples
An X.25 call may be addressed to the receiving interface; calls addressed to the receiving interface are eligible for acceptance as a datagram encapsulation, PAD or QLLC connection, and may not be routed. In the following example, serial interface 0 is configured with a native address of 0000123 and a destination alias for any address that starts with 1111123. That is, serial interface 0 can accept its own calls and calls for any destination that starts with 1111123.
interface serial 0encapsulation x25x25 address 0000123x25 alias ^1111123.*x25 bfe-decision
This command is no longer supported.
x25 bfe-emergency
This command is no longer supported.
x25 default
To set a default protocol that Cisco IOS software will assume applies to incoming calls with unknown or missing protocol identifier in the call user data (CUD), use the x25 default interface configuration command. To remove the default protocol specified, use the no form of this command.
x25 default protocol
no x25 default protocol
Syntax Description
Defaults
No default protocol is specified.
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command specifies the protocol assumed by the Cisco IOS software for incoming calls with unknown or missing protocol identifier in the call user data (CUD). If you do not use the x25 default interface configuration command, the software clears any incoming calls with unrecognized CUD.
Examples
The following example establishes IP as the default protocol for X.25 calls:
interface serial 0x25 default ipRelated Commands
x25 facility
To force facilities on a per-call basis for calls originated by the router (switched calls are not affected), use the x25 facilitycommand in interface or X.25 profile configuration mode. To disable a facility, use the no form of this command.
x25 facility option
no x25 facility option
Syntax Description
option
Set of user facilities options. See Table 68 for a list of supported facilities and their values.
Defaults
No facility is sent.
Command Modes
Interface configuration
X.25 profile configurationCommand History
Usage Guidelines
Table 68 lists the set of x25 facility command user facilities options.
Examples
The following example specifies a transit delay value in an X.25 configuration:
interface serial 0x25 facility transit-delay 24000The following example sets an ROA name and then sends the list via the X.25 user facilities:
x25 roa green_list 23 35 36interface serial 0x25 facility roa green_listRelated Commands
x25 fail-over
To configure a secondary interface and set the number of seconds for which a primary interface must be up before the secondary interface resets, use the x25 fail-over command in the appropriate configuration mode. To prevent the secondary interface from resetting, use the no form of this command.
x25 fail-over seconds interface type number [dlci | mac-address]
no x25 fail-over seconds interface type number [dlci | mac-address]
Syntax Description
Defaults
No default behavior or values
Command Modes
Interface configuration
X.25 profile configurationCommand History
Usage Guidelines
The x25 fail-over command can be configured on a primary X.25 interface or an X.25 profile only.
Examples
In the following example, X.25 failover is configured on a network that is also configured for Annex G. If data-link connection identifier (DLCI) 13 or DLCI 14 on serial interface 1/0 goes down, dialer interface 1 will serve as the secondary interface. After DLCI 13 or 14 comes back up and remains up for 20 seconds, dialer interface 1 will reset, sending all calls back to the primary interface.
interface serial1/0encapsulation frame-relayframe-relay interface-dlci 13x25-profile frame1exitframe-relay interface-dlci 14x25-profile frame1 dteexit!interface dialer1encapsulation x25exitx25 route ^1234 interface serial1/0 dlci 13x25 route ^1234 interface serial1/0 dlci 14x25 route ^1234 interface dialer1!x25 profile frame1x25 fail-over 20 interface dialer1exit!Related Commands
show x25 context
Displays information about X.25 links.
x25 profile
Configures an X.25 profile without specifying any hardware-specific information.
x25 hic
To set the highest incoming-only virtual circuit (VC) number, use the x25 hic interface configuration command.
x25 hic circuit-number
Syntax Description
Defaults
0
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command is applicable only if you have the X.25 switch configured for an incoming-only VC range. Incoming is from the perspective of the X.25 data terminal equipment (DTE). If you do not want any outgoing calls from your DTE, configure both ends to disable the two-way range (set the values of x25 ltc and x25 htc to 0) and configure an incoming-only range. Any incoming-only range must come before (that is, must be numerically less than) any two-way range. Any two-way range must come before any outgoing-only range.
Examples
The following example sets a valid incoming-only VC range of 1 to 5:
interface serial 0x25 lic 1x25 hic 5Related Commands
x25 hoc
To set the highest outgoing-only virtual circuit (VC) number, use the x25 hoc interface configuration command.
x25 hoc circuit-number
Syntax Description
Defaults
0
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is applicable only if you have the X.25 switch configured for an outgoing-only VC range. Outgoing is from the perspective of the X.25 data terminal equipment (DTE). If you do not want any incoming calls on your DTE, disable the two-way range (set the values of x25 ltc and x25 htc to 0) and configure an outgoing-only range. Any outgoing-only range must come after (that is, be numerically greater than) any other range.
Examples
The following example sets a valid outgoing-only VC range of 2000 to 2005:
interface serial 0x25 loc 2000x25 hoc 2005Related Commands
x25 hold-queue
To set the maximum number of packets to hold until a virtual circuit (VC) is able to send, use the x25 hold-queue interface configuration command. To remove this command from the configuration file and restore the default value, use the no form of this command without an argument.
x25 hold-queue packets
no x25 hold-queue [packets]
Syntax Description
packets
Number of packets. A hold queue value of 0 allows an unlimited number of packets in the hold queue.
Defaults
10 packets
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
If you set the queue-size argument to 0 when using the no x25 hold-queue command, there will be no hold queue limit. While this setting will prevent drops until the router runs out of memory, it is only rarely appropriate. A VC hold queue value is determined when it is created; changing this parameter will not affect the hold queue limits of the existing virtual circuits.
Examples
The following example sets the X.25 hold queue to hold 25 packets:
interface serial 0x25 hold-queue 25Related Commands
x25 hold-vc-timer
To start the timer that prevents additional calls to a destination for a given period of time (thus preventing overruns on some X.25 switches caused by Call Request packets), use the x25 hold-vc-timer interface configuration command. To restore the default value for the timer, use the no form of this command.
x25 hold-vc-timer minutes
no x25 hold-vc-timer
Syntax Description
minutes
Number of minutes that calls to a previously failed destination will be prevented. Incoming calls are still accepted.
Defaults
0 minutes
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
Only Call Requests that the router originates are held down; routed X.25 Call Requests are not affected by this parameter.
Upon receiving a Clear Request for an outstanding Call Request, the X.25 support code immediately tries another Call Request if it has more traffic to send, and this action might cause overrun problems.
Examples
The following example sets this timer to 3 minutes:
interface serial 0x25 hold-vc-timer 3x25 host
To define a static host name-to-address mapping, use the x25 host global configuration command. To remove the host name, use the no form of the command.
x25 host name x121-address [cud call-user-data]
no x25 host name
Syntax Description
name
Host name.
x121-address
The X.121 address.
cud call-user-data
(Optional) Sets the Call User Data (CUD) field in the X.25 Call Request packet.
Defaults
No static host name-to-address mapping is defined.
Command Modes
Global configuration
Command History
Usage Guidelines
This command permits you to map an X.121 address to an easily recognizable name. You can later use this host name instead of the X.121 address when you issue the translate command for X.25.
Examples
The following example specifies a static address mapping:
x25 host Willard 4085551212The following example removes a static address mapping:
no x25 host WillardThe following example specifies static address mapping from the X.121 address 12345678 to the host name "ocean". It then uses the name "ocean" in the translate command in place of the X.121 address when translating from the X.25 host to the PPP host with address 10.0.0.2.
x25 host ocean 12345678translate x25 ocean ppp 10.0.0.2 routingRelated Commands
x25 htc
To set the highest two-way virtual circuit (VC) number, use the x25 htc interface configuration command.
x25 htc circuit-number
Syntax Description
Defaults
1024 for X.25 network service interfaces; 4095 for CMNS network service interfaces.
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command is applicable if the X.25 switch is configured for a two-way VC range. Any two-way VC range must come after (that is, be numerically larger than) any incoming-only range, and must come before any outgoing-only range.
Examples
The following example sets a valid two-way VC range of 5 to 25:
interface serial 0x25 ltc 5x25 htc 25Related Commands
cmns enable
Enables the CMNS on a nonserial interface.
x25 ltc
Sets the lowest two-way VC number.
x25 hunt-group
To create and maintain a hunt group, use the x25 hunt-group global configuration command. To delete this hunt group, use the no form of this command.
x25 hunt-group name {rotary | vc-count}
no x25 hunt-group name
Syntax Description
name
Name you assign to the particular hunt group.
rotary
Each call steps to the next interface.
vc-count
Each call is placed on the interface with most available logical channels.
Command Modes
Global configuration
Command History
Usage Guidelines
Only one load-balancing distribution method can be selected for a hunt group, although one interface can participate in one or more hunt groups.
The rotary distribution method sends every call to the next available interface regardless of line speed and the number of available VCs on that interface.
The vc-count distribution method sends calls to the interface with the largest number of available logical channels. This method ensures a good load balance when you have lines of equal speed. If the line speeds are unequal, the vc-count method will favor the line with the higher speed. In cases where interfaces have the same line speed, the call is sent to the interface that is defined earliest in the hunt group.
To distribute calls equally among interfaces regardless of line speed, configure each interface with the same number of VCs.
With the vc-count distribution method, if a hunt group does not contain an operational interface, the call will be forwarded to the next route if one was specified. If a session is terminated on an interface within the hunt group, that interface now has more available VCs and it will be chosen next.
Examples
X.25 Load Balancing Using VC-Count Distribution Method Example
In the following example, the vc-count distribution method is used on a hunt group that contains two serial interfaces that have different numbers of VCs. Assuming no sessions are being terminated at this time, the first 450 calls will be sent to Serial1, and subsequent calls will alternate between Serial0 and Serial1 until the interfaces are full.
interface serial0description 56k link supporting 50 virtual circuitsx25 htc 50!interface serial1description T1 line supporting 500 virtual circuitsx25 htc 500!x25 hunt-group hg-vc vc-countinterface serial0interface serial1!Hunt Group Configuration Example
The following example shows the creation of hunt group "HG1" with serial interfaces 1 and 2 and two specific XOT target IP addresses (172.17.125.54 and 172.17.125.34). Hunt group "HG1" is configured to use rotary distribution method. The example also shows the creation of hunt group "HG2" with serial interfaces 0 and 3. Hunt group "HG2" will use vc-count distribution method.
x25 hunt-group HG1 rotaryinterface serial 1interface serial 2xot 172.17.125.54xot 172.17.125.34exitx25 hunt-group HG2 vc-countinterface serial 0interface serial 3Related Commands
show x25 hunt-group
Displays X.25 hunt groups, detailed interface statistics, and distribution methods.
x25 idle
To define the period of inactivity after which the router can clear a switched virtual circuit (SVC), use the x25 idle interface configuration command.
x25 idle minutes
Syntax Description
Defaults
0 (the SVC is kept open indefinitely)
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
Calls originated and terminated by the router are cleared; packet assembler/disassembler (PAD) and switched virtual circuits are not affected. To clear one or all virtual circuits at once, use the clear x25 privileged EXEC command.
Examples
The following example sets a 5-minute wait period before an idle circuit is cleared:
interface serial 2x25 idle 5Related Commands
x25 ip-precedence
To enable the Cisco IOS software to use the IP precedence value when it opens a new virtual circuit (VC), use the x25 ip-precedence interface configuration command. To cause the Cisco IOS software to ignore the precedence value when opening VCs, use the no form of this command.
x25 ip-precedence
no x25 ip-precedence
Syntax Description
This command has no arguments or keywords.
Defaults
The router opens one VC for all types of service.
Command Modes
Interface configuration
Command History
Usage Guidelines
This feature is useful only for Defense Data Network (DDN) or Blacker Front End (BFE) encapsulations because only these methods have an IP precedence facility defined to allow the source and destination devices to both use the VC for traffic of the given IP priority.
Verify that your host does not send nonstandard data in the IP type of service (TOS) field because it can cause multiple wasteful virtual circuits to be created.
Four VCs may be opened based on IP precedence to encapsulate routine, priority, immediate, and all higher precedences.
The x25 map nvc limit or the default x25 nvc limit still applies.
Examples
The following example allows new IP encapsulation VCs based on the IP precedence:
interface serial 3x25 ip-precedencex25 ips
To set the interface default maximum input packet size to match that of the network, use the x25 ips interface configuration command.
x25 ips bytes
Syntax Description
bytes
Byte count. It can be one of the following values: 16, 32, 64, 128, 256, 512, 1024, 2048, or 4096.
Defaults
128 bytes
Command Modes
Interface configuration
Command History
Usage Guidelines
X.25 network connections have a default maximum input packet size set by the network administrator. Larger packet sizes require less overhead processing. To send a packet larger than the X.25 packet size over an X.25 virtual circuit, the Cisco IOS software must break the packet into two or more X.25 packets with the more data bit (M-bit) set. The receiving device collects all packets with the M-bit set and reassembles the original packet.
Note
Examples
The following example sets the default maximum packet sizes to 512:
interface serial 1x25 ips 512x25 ops 512Related Commands
x25 lic
To set the lowest incoming-only virtual circuit (VC) number, use the x25 lic interface configuration command.
x25 lic circuit-number
Syntax Description
Defaults
0
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command is applicable only if you have the X.25 switch configured for an incoming-only VC range. Incoming is from the perspective of the X.25 DTE device. If you do not want any outgoing calls on your DTE device, disable the two-way range (set the values of x25 ltc and x25 htc to 0).
The following example sets a valid incoming-only VC range of 1 to 5, and sets the lowest two-way VC number:
interface serial 0x25 lic 1x25 hic 5x25 ltc 6Related Commands
x25 linkrestart
To force X.25 Level 3 (packet level) to restart when Level 2 (Link Access Procedure, Balanced [LAPB], the link level) resets, use the x25 linkrestart interface configuration command. To disable this function, use the no form of this command.
x25 linkrestart
no x25 linkrestart
Syntax Description
This command has no arguments or keywords.
Defaults
Forcing packet-level restarts is the default and is necessary for networks that expect this behavior.
Command Modes
Interface configuration
X.25 profile configuration
Command History
Examples
The following example disables the link-level restart:
interface serial 3no x25 linkrestartx25 loc
To set the lowest outgoing-only virtual circuit (VC) number, use the x25 loc interface configuration command.
x25 loc circuit-number
Syntax Description
Defaults
0
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command is applicable only if you have the X.25 switch configured for an outgoing-only VC range. Outgoing is from the perspective of the X.25 DTE device. If you do not want any incoming calls from your DTE device, configure the values of x25 loc and x25 hoc and set the values of x25 ltc and x25 htc to 0.
Examples
The following example sets a valid outgoing-only virtual circuit range of 2000 to 2005:
interface serial 0x25 loc 2000x25 hoc 2005Related Commands
x25 ltc
To set the lowest two-way virtual circuit (VC) number, use the x25 ltc interface configuration command.
x25 ltc circuit-number
Syntax Description
Defaults
1
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
This command is applicable if you have the X.25 switch configured for a two-way virtual circuit range. Any two-way virtual circuit range must come after (that is, be numerically larger than) any incoming-only range, and must come before any outgoing-only range.
Examples
The following example sets a valid two-way virtual circuit range of 5 to 25:
interface serial 0x25 ltc 5x25 htc 25Related Commands
x25 map
To set up the LAN protocols-to-remote host mapping, use the x25 map command in interface configuration or X.25 profile configuration mode. To retract a prior mapping, use the no form of this command.
x25 map protocol address [protocol2 address2 [...[protocol9 address9]]] x121-address [option]
no x25 map protocol address x121-address
Syntax Description
Defaults
No LAN protocol-to-remote host mapping is set up.
Command Modes
Interface configuration
X.25 profile configurationCommand History
Usage Guidelines
Because no defined protocol can dynamically determine LAN protocol-to-remote host mappings, you must enter all the information for each host with which the router may exchange X.25 encapsulation traffic.
Two methods are available to encapsulate traffic: Cisco's long-available encapsulation method and the Internet Engineering Task Force (IETF) standard method (defined in RFC 1356); the latter allows hosts to exchange several protocols over a single virtual circuit. Cisco's encapsulation method is the default (for backward compatibility) unless the interface configuration command specifies the ietf keyword.
When you configure multiprotocol maps, you can specify a maximum of nine protocol and address pairs in an x25 map command. However, you can specify a protocol only once. For example, you can specify the IP protocol and an IP address, but you cannot specify another IP address. If the compressedtcp and ip keywords are both specified, the same IP address must be used.
Bridging is supported only if you are using Cisco's traditional encapsulation method. For correct operation, bridging maps must specify the broadcast option.
Since most datagram routing protocols rely on broadcasts or multicasts to send routing information to their neighbors, the broadcast keyword is needed to run such routing protocols over X.25.
Encapsulation maps might also specify that traffic between the two hosts should be compressed, thus increasing the effective bandwidth between them at the expense of memory and computation time. Because each compression virtual circuit requires memory and computation resources, compression must be used with care and monitored to maintain acceptable resource usage and overall performance.
Open Shortest Path First (OSPF) Protocol treats a nonbroadcast, multiaccess network such as X.25 in much the same way as it treats a broadcast network by requiring the selection of a designated router. In previous releases, this required manual assignment in the OSPF configuration using the neighbor router configuration command. When the x25 map command is included in the configuration with the broadcast, and the ip ospf network command (with the broadcast keyword) is configured, there is no need to configure any neighbors manually. OSPF will now run over the X.25 network as a broadcast network. (Refer to the ip ospf network interface configuration command for more detail.)
Note
You can modify the options of an x25 map command by restating the complete set of protocols and addresses specified for the map, followed by the desired options. To delete a map command, you must also specify the complete set of protocols and addresses; the options can be omitted when deleting a map.
Once defined, a map's protocols and addresses cannot be changed. This requirement exists because the Cisco IOS software cannot determine whether you want to add to, delete from, or modify an existing map's protocol and address specification, or simply mistyped the command. To change a map's protocol and address specification, you must delete it and create a new map.
A given protocol-address pair cannot be used in more than one map on the same interface.
Table 69 lists the protocols supported by X.25.
Table 69 Protocols Supported by X.25
appletalk
AppleTalk
bridge
Bridging1
clns
ISO Connectionless Network Service
compressedtcp
TCP/IP header compression
decnet
DECnet
ip
IP
ipx
Novell IPX
pad
PAD links2
qllc
System Network Architecture (SNA) encapsulation in X.253
1 Bridging traffic is supported only for Cisco's traditional encapsulation method, so a bridge map cannot specify other protocols.
2 Packet assembler/disassembler (PAD) maps are used to configure session and protocol translation access, therefore, this protocol is not available for multiprotocol encapsulation.
3 Qualified Logical Link Control (QLLC) is not available for multiprotocol encapsulation.
Note
Table 70 lists the map options supported by X.25 using the x25 map command.
Examples
The following example maps IP address 172.20.2.5 to X.121 address 000000010300. The broadcast keyword directs any broadcasts sent through this interface to the specified X.121 address.
interface serial 0x25 map ip 171.20.2.5 000000010300 broadcastThe following example specifies an ROA name to be used for originating connections:
x25 roa green_list 23 35 36interface serial 0x25 map ip 172.20.170.26 10 roa green_listThe following example specifies an NUID facility to send on calls originated for the address map:
interface serial 0x25 map ip 172.20.174.32 2 nudata "Network User ID 35"Strings can be quoted, but quotation marks are not required unless embedded blanks are present.
Related Commands
x25 map bridge
To configure an Internet-to-X.121 address mapping for bridging of packets in X.25 frames, use the x25 map bridge command in interface configuration mode. To disable the Internet-to-X.121 address mapping, use the no form of this command.
x25 map bridge x121-address broadcast [option]
Syntax Description
Defaults
No bridging over X.25 is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
The X.25 bridging software uses the same spanning-tree algorithm as the other bridging functions, but allows packets to be encapsulated in X.25 frames and transmitted across X.25 media. This command specifies IP-to-X.121 address mapping and maintains a table of both the Ethernet and X.121 addresses.
Table 71 lists x25 map bridge options.
Examples
The following example configures transparent bridging over X.25 between two Cisco routers using a maximum of six virtual circuits:
interface serial 1x25 map bridge 000000010300 broadcast nvc 6Related Commands
x25 map
Sets up the LAN protocols-to-remote host mapping.
x25 address
Sets the X.121 address of a particular network interface.
x25 map cmns
The x25 map cmns command is replaced by the enhanced x25 route command. See the description of the x25 route command in this chapter for more information.
x25 map compressedtcp
To map compressed TCP traffic to an X.121 address, use the x25 map compressedtcp interface configuration command. To delete a TCP/IP header compression map for the link, use the no form of this command.
x25 map compressedtcp ip-address [protocol2 address2 [...[protocol9 address9]]]
x121-address [option]no x25 map compressedtcp address [protocol2 address2 [...[protocol9 address9]]]
x121-addressSyntax Description
Defaults
No mapping is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Cisco supports RFC 1144 TCP/IP header compression (THC) on serial lines using HDLC and X.25 encapsulation. THC encapsulation is only slightly different from other encapsulation traffic, but these differences are worth noting. The implementation of compressed TCP over X.25 uses one virtual circuit to pass the compressed packets. Any IP traffic (including standard TCP) is separate from TCH traffic; it is carried over separate IP encapsulation virtual circuits or identified separately in a multiprotocol virtual circuit.
Note
The nvc map option cannot be used for TCP/IP header compression, because only one virtual circuit can carry compressed TCP/IP header traffic to a given host.
Examples
The following example establishes a map for TCP/IP header compression on serial interface 4:
interface serial 4ip tcp header-compressionx25 map compressedtcp 172.20.2.5 000000010300Related Commands
x25 map pad
To configure an X.121 address mapping for packet assembler/disassembler (PAD) access over X.25, use the x25 map pad interface configuration command.
x25 map pad x121-address [option]
Syntax Description
x121-address
X.121 address of the interface.
option
(Optional) Services that can be added to this map—the same options as the x25 map command; see Table 69 earlier in this chapter.
Defaults
No specific options are used for PAD access.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use a PAD map to configure optional X.25 facility use for PAD access. When used with the x25 pad-access interface configuration command, the x25 map pad command restricts incoming PAD access to those statically mapped hosts.
Examples
The following example configures an X.25 interface to restrict incoming PAD access to the single mapped host. This example requires that both incoming and outgoing PAD access use the network user identification (NUID) user authentication.
interface serial 1x25 pad-accessx25 map pad 000000010300 nuid johndoe secretRelated Commands
x25 map
Sets up the LAN protocols-to-remote host mapping.
x25 pad-access
Causes the PAD software to accept PAD connections only from statically mapped X.25 hosts.
x25 map rbp local
To configure a router to establish X.25 circuits in response to incoming TCP connections on a specified TCP port, and to use record boundary preservation (RBP) to transfer data between the TCP session and the corresponding X.25 circuit, use the x25 map rbp local command in interface configuration mode. To delete the map, use the no form of this command.
x25 map rbp x121-address [cud string] local port port [cug group-number] [packetsize in-size out-size] [recordsize size] [reverse] [roa name] [throughput in out] [transit-delay milliseconds] [windowsize in-size out-size]
no x25 map rbp x121-address [cud string] local port port
Syntax Description
Defaults
No SVC is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
RBP enables X.25 hosts to exchange data with TCP/IP hosts via TCP sessions while maintaining X.25 packet boundaries.
When the x25 map rbp local command is configured, the router will listen for a request for a TCP connection to the specified TCP port. When the connection request is accepted, the router will then attempt to place an X.25 call on the interface on which the command was configured, using the X.25 address of the interface as the calling address, the X.121 address specified in the command as the destination address, and the call user data specified in the command. If the call is not successfully completed, the TCP connection will be closed.
The number of connections that may be established to the TCP port is limited only by router resources (such as memory, processor utilization, and available X.25 circuits).
When connections that will be established by the TCP/IP host are configured, the local TCP port number must be unique, with the exception that the same TCP port number may be configured once on each of multiple X.25 interfaces that will not be active simultaneously; this includes the case in which one X.25 interface is configured as a backup interface for another X.25 interface.
No information from the TCP connection is included in the X.25 Call packet sent to the X.25 host.
Examples
interface Serial1/0encapsulation x25 dcex25 address 13133x25 map rbp 12131 local port 9999Related Commands
x25 map rbp remote
To configure a router to establish TCP sessions in response to incoming X.25 calls, and to use record boundary preservation (RBP) to transfer data between the X.25 circuit and the corresponding TCP session, use the x25 map rbp remote command in interface configuration mode. To delete the map, use the no form of this command.
x25 map rbp x121-address [cud string] remote host ip-address port port [accept-reverse] [recordsize size] [source-interface interface]
no x25 map rbp x121-address [cud string] remote host port port
Syntax Description
Defaults
No SVC is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
RBP enables X.25 hosts to exchange data with TCP/IP hosts via TCP sessions while maintaining X.25 packet boundaries.
The router will accept an incoming X.25 call if the source address and call user data in the call request match the values configured in the x25 map rbp remote command. If the cud parameter is specified in the command, the call user data in the incoming call must match the configured value exactly. If the cud parameter is not specified in the command, the call user data must not conflict with any protocol ID recognized by the router, but it is otherwise ignored.
If an incoming call requests reverse charging, and the accept-reverse option is not specified in the matching map, the call will be refused.
If the incoming call is accepted, the router will attempt to open a TCP connection to a configured IP address and TCP port using a dynamically assigned local TCP port number. If the TCP connection cannot be opened, the X.25 call will be cleared.
The number of X.25 calls that may be accepted is limited only by router resources.
No information from the X.25 call packet is provided to the TCP/IP host.
Examples
interface Serial1/0encapsulation x25 dcex25 address 12030x25 map rbp 12132 remote host 10.0.0.1 port 9999Related Commands
x25 modulo
To set the window modulus, use the x25 modulo interface configuration command.
x25 modulo modulus
Syntax Description
modulus
Either 8 or 128. The value of the modulo parameter must agree with that of the device on the other end of the X.25 link.
Defaults
8
Command Modes
Interface configuration
Command History
Usage Guidelines
X.25 supports flow control with a sliding window sequence count. The window counter restarts at zero upon reaching the upper limit, which is called the window modulus. Modulo 128 operation is also referred to as extended packet sequence numbering, which allows larger packet windows.
Examples
The following example sets the window modulus to 128:
interface serial 0x25 modulo 128Related Commands
x25 nvc
To specify the maximum number of virtual circuits (VCs) that a protocol can have open simultaneously to one host, use the x25 nvc interface configuration command. To increase throughput across networks, you can establish up to eight virtual circuits to a host and protocol.
x25 nvc count
Syntax Description
Defaults
1
Command Modes
Interface configuration
X.25 profile configuration
Command History
Usage Guidelines
When the windows and output queues of all existing connections to a host are full, a new virtual circuit will be opened to the designated circuit count. If a new connection cannot be opened, the data is dropped.
Note
Examples
The following example sets the default maximum number of VCs that each map can have open simultaneously to 4:
interface serial 0x25 nvc 4
