Cisco IOS IBM Networking Command Reference

mac-address

To modify the default MAC address of an interface to some user-defined address, use the mac-address command in interface configuration mode. To return to the default MAC address on the interface, use the no form of this command.

mac-address ieee-address

no mac-address ieee-address

Syntax Description

Defaults

The interface uses a default MAC address that is derived from the base address stored in the electrically erasable programmable read-only memory (EEPROM).

Command Modes

Interface configuration

Usage Guidelines

Be sure that no other interface on the network is using the MAC address that you assign.

There is a known defect in earlier forms of this command when the Texas Instruments Token Ring MAC firmware is used. This implementation is used by Proteon, Apollo, and IBM RTs. A host using a MAC address whose first two bytes are zeros (such as a Cisco router) will not properly communicate with hosts using that form of this command of TI firmware.

There are two solutions. The first involves installing a static Routing Information Field (RIF) entry for every faulty node with which the router communicates. If there are many such nodes on the ring, this may not be practical. The second solution involves setting the MAC address of the Cisco Token Ring to a value that works around the problem.

This command forces the use of a different MAC address on the specified interface, thereby avoiding the Texas Instrument MAC firmware problem. It is up to the network administrator to ensure that no other host on the network is using that MAC address.

Examples

The following example sets the MAC layer address, where xx.xxxx is an appropriate second half of the MAC address to use:

interface tokenring 0

 mac-address 5000.5axx.xxxx

The following example changes the default MAC address on the interface to 1111.2222.3333:

Router# configure terminal

Router(config)# interface fastethernet 2/1/1

Router(config-if)# mac-address 1111.2222.3333

Related Commands

maximum-lus

To limit the number of logical unit (LU) control blocks that will be allocated for the TN3270 server, use the maximum-lus command in TN3270 server configuration mode. To restore the default value, use the no form of this command.

maximum-lus number

no maximum-lus

Syntax Description

Defaults

Because of the license structure, the default is 2100, which represents the limit of the lower-priced license (2000) plus a 5 percent buffer. If you configure a value greater than the default, a license reminder is displayed.

Command Modes

TN3270 server configuration

Command History

Usage Guidelines

The maximum-lus command is valid only on the virtual channel interface. Although the value may be varied at any time, reducing it below the current number of LU control blocks will not release those blocks until a physical unit (PU) is inactivated by Deactivate Physical Unit (DACTPU) or by using the no pu command.

If the number of LUs in use reaches 94 percent of the current setting, a warning message is displayed on the console. To prevent redundant messages, the threshold for generating such messages is raised for a period.

The TN3270 server attempts to allocate one LU control block for each LU activated by the hosts. In the case of dynamic definition of dependent LU (DDDLU) the control block is allocated when the client requests the LU, in anticipation of an activate logical unit (ACTLU) from the system services control points (SSCP) host.

By limiting the number of LU control blocks allocated, you can make sure enough memory is available to support other Cisco Mainframe Channel Connection (CMCC) functions. The control blocks themselves take about 1K bytes per LU. During session activity, a further 2K per LU may be needed for data. On a Channel Interface Processor (CIP), 32 MB of memory will support 4000 LUs. To support more than 4000 LUs, we recommend 64 MB of memory. On an XCPA, 8 MB of memory supports 1000 LUs.

Examples

The following example allows 5000 LU control blocks to be allocated:

maximum-lus 5000

Related Commands

max-llc2-rcvbuffs

To configure the number of receive DMA buffers that are used by the LLC2 stack on the CIP/XCPA, use the max-llc2-rcvbuffs internal adapter configuration command. Use the no form of this command to revert to the default setting.

max-llc2-rcvbuffs buffers

no max-llc2-rcvbuffs buffers

Syntax Description

Defaults

500 buffers

Command Modes

Virtual interface configuration

Command History

Examples

The following example configures the max-llc2-rcvbuffs for 750 buffers on Channel interface 4/2:

interface Channel4/2

 max-llc2-rcvbuffs 750

lan TokenRing 12

 source-bridge 16 1 500

 adapter 0 4000.cafe.0000

  llc2 Nw 31

  llc2 rnr-activated

 adapter 1 4000.cafe.0001

Related Commands

max-llc2-sessions

To specify the maximum number of Logical Link Control, type 2 (LLC2) sessions supported on the Cisco Mainframe Channel Connection (CMCC) adapter, use the max-llc2-sessions command in interface configuration mode. To restore the default value, use the no form of this command.

max-llc2-sessions number

no max-llc2-sessions number

Syntax Description

Defaults

The default number of sessions is 256.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command is configured on the virtual interface of a Channel Interface Processor (CIP), and the physical interface of a Channel Port Adapter (CPA). If you do not configure this parameter on the CMCC adapter, then the limit of LLC2 sessions is 256.

This command will fail if not enough memory is available on the CMCC adapter to support the specified number of LLC2 sessions.

Note A value of 0 sets the maximum number of LLC2 sessions to the default value of 256. In this case, the value does not appear in your configuration when you use the show run command.

Examples

The following example limits the maximum number of LLC2 sessions to 212:

max-llc2-sessions 212

multiring

To enable collection and use of Routing Information Field (RIF) information, use the multiring command in interface configuration mode. To disable the use of RIF information for the protocol specified, use the no form of this command.

multiring {protocol [all-routes | spanning] | all | other}

no multiring {protocol [all-routes | spanning] | all | other}

Syntax Description

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

Level 3 routers that use protocol-specific information (for example, Novell IPX or XNS headers) rather than MAC information to route datagrams also must be able to collect and use RIF information to ensure that they can send datagrams across a source-route bridge. The software default is to not collect and use RIF information for routed protocols. This allows operation with software that does not understand or properly use RIF information.

Note When you are configuring DLSw+ over FDDI, the multiring command supports only IP and IPX.

The multiring command allows for per-protocol specification of the interface's ability to append RIFs to routed protocols. When it is enabled for a protocol, the router will source packets that include information used by source-route bridges. This allows a router with Token Ring interfaces, for the protocol or protocols specified, to connect to a source-bridged Token Ring network. If a protocol is not specified for multiring, the router can route packets only to nodes directly connected to its local Token Ring.

Examples

The following example enables IP and Novell IPX bridging on a Token Ring interface. RIFs will be generated for IP frames, but not for the Novell IPX frames.

! commands that follow apply to interface token 0

interface tokenring 0

! enable the Token Ring interface for IP

 ip address 131.108.183.37 255.255.255.0

! generate RIFs for IP frames

 multiring ip

! enable the Token Ring interface for Novell IPX 

 novell network 33

Related Commands

name

To assign a name to the internal adapter, use the name command in internal adapter configuration mode. To remove the name assigned to an internal adapter, use the no form of this command.

name name

no name name

Syntax Description

Defaults

No default behavior or values

Command Modes

Internal adapter configuration

Command History

Examples

The following example assigns a name to an internal adapter interface:

name VTAM_B14

Related Commands

ncia

To stop or start a native client interface architecture (NCIA) server, use the ncia command in privileged EXEC mode.

ncia {start | stop}

Syntax Description

Command Modes

Privileged EXEC

Command History

Usage Guidelines

As soon as the NCIA server is configured, it begins running. If an NCIA server is configured and the configuration is stored in the NVRAM of the router, when the router boots up, the server is started automatically. Issuing the ncia start command when a server is already running causes the router to display the message:

NCIA server is running already!

There is not a no form for this command.

Examples

The following example stops an active NCIA server:

Router# ncia stop

Related Commands

ncia client

To configure a native client interface architecture (NCIA) client on a Cisco router, use the ncia client command in global configuration mode. To remove the configuration, use the no form of this command.

ncia client server-number client-ip-address virtual-mac-address [sna | all]

no ncia client server-number client-ip-address virtual-mac-address [sna | all]

Syntax Description

Defaults

No NCIA client is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

You must use the ncia server command to configure an NCIA server on the router before using the ncia client command to configure an NCIA client.

The purpose in configuring a client is so the NCIA server can connect outward to a client. When an end station on the LAN side tries to connect to a client, the end station sends an explorer. When the server receives this explorer, the server tries to match the MAC address in the client database. If it finds a match, the server then connects to that client. If the ability for the server to connect outward to clients is not needed, there is no reason to configure any clients.

Each client is assigned a MAC address from the pool created by the ncia server command. There are two exceptions to this guideline:

•A MAC address outside the pool created by the ncia server command can be defined in the ncia client command.

When a client configured with a MAC address outside the pool connects to the server, the client's configured MAC address is used, rather than allocating a new one from the pool.

•If a client has its own MAC address, it uses that address.

The MAC address is recognized during the "capability exchange" period when the client establishes a session with the NCIA server. Normally, it is not necessary to configure any client. The server accepts a connection from any unconfigured client. If the unconfigured client does not have its own MAC address, a MAC address from the pool will be assigned to it. If the unconfigured client has its own MAC address, that MAC address is used. If the client has its own MAC address and it is configured using the ncia client command, the two MAC addresses must match; otherwise, the connection will not be established.

If you do not specify the all keyword as the supported traffic type when you configure an NCIA client, the client only supports only SNA traffic.

Examples

The following example configures an NCIA client on a router:

ncia client 1 10.2.20.5 1111.2222.3333

Related Commands

ncia rsrb

To configure an remote source-route bridging (RSRB) ring to associate with an native client interface architecture (NCIA) server on a Cisco router, use the ncia rsrb command in global configuration mode. To remove the configuration, use the no form of this command.

ncia rsrb virtual-ring local-bridge local-ring ncia-bridge ncia-ring virtual-mac-address

no ncia rsrb

Syntax Description

Defaults

No RSRB ring is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

You must use the ncia server command to configure an NCIA server on the router before using the ncia rsrb command to configure an RSRB ring to associate with the server.

Examples

The following example configures a virtual ring to associate with an NCIA server on a Cisco router:

source-bridge ring-group 22

source-bridge ring-group 44

ncia rsrb 44 4 33 3 22 1111.1111.2222

Related Commands

ncia server

To configure an native client interface architecture (NCIA) server on a Cisco router, use the ncia server command in global configuration mode. To remove the configuration, use the no form of this command.

ncia server server-number server-ip-address server-virtual-mac-address virtual-mac-address virtual-mac-range [inbound-only] [keepalive seconds] [tcp_keepalive minutes]

no ncia server

Syntax Description

Defaults

No NCIA server is configured.

Command Modes

Global configuration

Command History

Usage Guidelines

Before configuring an NCIA server, you must use the dlsw local-peer command to configure a data-link switching plus (DLSw+) local peer on this router. Depending on your network design, you may need to use the ncia client command to configure an NCIA client on this router (optional), or use the ncia rsrb command to configure an remote source-route bridging (RSRB) ring to associate with this router (optional).

If you use the inbound-only keyword, there is no need to configure any NCIA clients (the server does not make out-going connections).

In a downstream physical unit (DSPU) configuration, before a client can establish a connection to a downstream physical unit (PU), such as a PC or workstation, the MAC address of the server (server-virtual-mac-address) must be defined at the PC or workstation as the destination MAC address. This MAC address appears as the server MAC address in the output of the show ncia circuits command.

Examples

The following example configures an NCIA server on a Cisco router:

ncia server 1 10.2.20.4 4000.3174.0001 4000.0000.0001 128 keepalive 0 tcp_keepalive 0

Related Commands

netbios access-list bytes

To define the offset and hexadecimal patterns with which to match byte offsets in NetBIOS packets, use the netbios access-list bytes command in global configuration mode. To remove an entire list or the entry specified with the pattern argument, use the no form of this command.

netbios access-list bytes name {permit | deny} offset pattern

no netbios access-list bytes name [permit | deny]

Syntax Description

Defaults

No offset or pattern is defined.

Command Modes

Global configuration

Command History

Usage Guidelines

For offset pattern matching, the byte pattern must be an even number of hexadecimal digits in length.

The byte pattern must be no more than 16 bytes (32 hexadecimal digits) in length.

As with all access lists, the NetBIOS access lists are scanned in order.

You can specify a wildcard character in the byte string indicating that the value of that byte does not matter in the comparison. This is done by specifying two asterisks (**) in place of digits for that byte. For example, the following command would match 0xabaacd, 0xab00cd, and so on:

netbios access-list bytes marketing permit 3 0xab**cd

Examples

The following example shows how to configure for offset pattern matching:

netbios access-list bytes marketing permit 3 0xabcd

In the following example, the byte pattern would not be accepted because it must be an even number of hexadecimal digits:

netbios access-list bytes marketing permit 3 0xabc 

In the following example, the byte pattern would not be permitted because the byte pattern is longer than 16 bytes in length:

netbios access-list bytes marketing permit 3 00112233445566778899aabbccddeeff00

The following example would match 0xabaacd, 0xab00cd, and so on:

netbios access-list bytes marketing permit 3 0xab**cd

The following example deletes the entire marketing NetBIOS access list named marketing:

no netbios access-list bytes marketing

The following example removes a single entry from the list:

no netbios access-list bytes marketing deny 3 0xab**cd

In the following example, the first line serves to deny all packets with a byte pattern starting in offset 3 of 0xab. However, this denial would also include the pattern 0xabcd because the entry permitting the pattern 0xabcd comes after the first entry:

netbios access-list bytes marketing deny 3 0xab

netbios access-list bytes marketing permit 3 0xabcd

Related Commands

netbios access-list host

To assign the name of the access list to a station or set of stations on the network, use the netbios access-list host command in global configuration mode. The NetBIOS station access list contains the station name to match, along with a permit or deny condition. To remove either an entire list or just a single entry from a list, depending upon the value given for pattern argument, use the no form of this command.

netbios access-list host name {permit | deny} pattern

no netbios access-list host name {permit | deny} pattern

Syntax Description

Defaults

No access list is assigned.

Command Modes

Global configuration

Command History

Usage Guidelines

Table 15 explains the pattern-matching characters that can be used.

Examples

The following example specifies a full station name to match:

netbios access-list host marketing permit ABCD

The following example specifies a prefix where the pattern matches any name beginning with the characters DEFG:

!The string DEFG itself is included in this condition.

netbios access-list host marketing deny DEFG*

The following example permits any station name with the letter W as the first character and the letter Y as the third character in the name. The second and fourth character in the name can be any character. This example would allow stations named WXYZ and WAYB; however, stations named WY and WXY would not be allowed because the question mark (?) must match specific characters in the name:

netbios access-list host marketing permit W?Y?

The following example illustrates how to combine wildcard characters. In this example the marketing list denies any name beginning with AC that is not at least three characters in length (the question mark [?] would match any third character). The string ACBD and ACB would match, but the string AC would not:

netbios access-list host marketing deny AC?

In the following example, a single entry in the marketing NetBIOS access list is removed:

no netbios access-list host marketing deny AC?*

In the following example, the entire marketing NetBIOS access list is removed:

no netbios access-list host marketing 

Related Commands

netbios enable-name-cache

To enable NetBIOS name caching, use the netbios enable-name-cache command in interface configuration mode. To disable the name-cache behavior, use the no form of this command.

netbios enable-name-cache

no netbios enable-name-cache

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

This command enables the NetBIOS name cache on the specified interface. By default the name cache is disabled for the interface. Proxy explorers must be enabled on any interface that is using the NetBIOS name cache.

Examples

The following example enables NetBIOS name caching for Token Ring interface 0:

interface tokenring 0

 source-bridge proxy-explorer

 netbios enable-name-cache

Related Commands

netbios input-access-filter bytes

To define a byte access list filter on incoming messages, use the netbios input-access-filter bytes command in interface configuration mode. The actual access filter byte offsets and patterns used are defined in one or more netbios-access-list bytes commands. To remove the entire access list, use the no form of this command with the appropriate name.

netbios input-access-filter bytes name

no netbios input-access-filter bytes name

Syntax Description

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Examples

The following example applies a previously defined filter named marketing to packets coming into Token Ring interface 1:

interface tokenring 1

 netbios input-access-filter bytes marketing 

Related Commands

netbios input-access-filter host

To define a station access list filter on incoming messages, use the netbios input-access-filter host command in interface configuration mode. To remove the entire access list, use the no form of this command with the appropriate argument.

netbios input-access-filter host name

no netbios input-access-filter host name

Syntax Description

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Usage Guidelines

The access lists of station names are defined in netbios access-list host commands.

Examples

The following example filters packets coming into Token Ring interface 1 using the NetBIOS access list named marketing:

interface tokenring 1

 netbios access-list host marketing permit W?Y?

 netbios input-access-filter host marketing

Related Commands

netbios name-cache

To define a static NetBIOS name cache entry, tying the server with the name netbios-name to the mac-address, and specifying that the server is accessible either locally through the interface-name specified, or remotely, through the ring-group group-number specified, use the netbios name-cache command in global configuration mode. To remove the entry, use the no form of this command.

netbios name-cache mac-address netbios-name {interface-name intetrface-number | ring-group group-number}

no netbios name-cache mac-address netbios-name

Syntax Description

Defaults

No entry is defined.

Command Modes

Global configuration

Command History

Usage Guidelines

To specify an entry in the static name cache, first specify a Routing Information Field (RIF) that leads to the server's MAC address. The Cisco IOS software displays an error message if it cannot find a static RIF entry for the server when the NetBIOS name-cache entry is attempted or if the server's type conflicts with that given for the static RIF entry.

Note The names are case sensitive; therefore "Cc" is not the same as "cC."

Examples

The following example indicates the syntax usage of this command if the NetBIOS server is accessed locally:

source-bridge ring-group 2

 rif 0220.3333.4444 00c8.042.0060 tokenring 0

 netbios name-cache 0220.3333.4444 DEF tokenring 0

The following example indicates the syntax usage of this command if the NetBIOS server is accessed remotely:

source-bridge ring-group 2 

 rif 0110.2222.3333 0630.021.0030 ring group 2

 netbios name-cache 0110.2222.3333 DEF ring-group 2

Related Commands

netbios name-cache name-len

To specify how many characters of the NetBIOS type name the name cache will validate, use the netbios name-cache name-len command in global configuration mode.

netbios name-cache name-len length

no netbios name-cache name-len length

Syntax Description

Defaults

15 characters

Command Modes

Global configuration

Command History

Examples

The following example specifies that the name cache will validate 16 characters of the NetBIOS type name:

netbios name-cache name-len 16

Related Commands

netbios name-cache proxy-datagram

To enable the Cisco IOS software to act as a proxy and send NetBIOS datagram type frames, use the netbios name-cache proxy-datagram command in global configuration mode. To return to the default value, use the no form of this command.

netbios name-cache proxy-datagram seconds

no netbios name-cache proxy-datagram seconds

Syntax Description

Defaults

There is no default time interval.

Command Modes

Global configuration

Command History

Examples

The following example specifies that the software will forward a NetBIOS datagram type frame in 20-second intervals:

netbios name-cache proxy-datagram 20

Related Commands

netbios name-cache query-timeout

To specify the "dead" time, in seconds, that starts when a host sends any ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame, use the netbios name-cache query-timeout command in global configuration mode. During this dead time, the Cisco IOS software drops any repeat, duplicate ADD_NAME_QUERY, ADD_GROUP_NAME, or STATUS_QUERY frame sent by the same host. This timeout is only effective at the time of the login negotiation process. To restore the default of 6 seconds, use the no form of this command.

netbios name-cache query-timeout seconds

no netbios name-cache query-timeout

Syntax Description

Defaults

6 seconds

Command Modes

Global configuration

Command History

Examples

The following example sets the timeout to 15 seconds:

netbios name-cache query-timeout 15

Related Commands

netbios name-cache recognized-timeout

To specify the "dead" time, in seconds, that starts when a host sends any FIND_NAME or NAME_RECOGNIZED frame, use the netbios name-cache recognized-timeout command in global configuration mode. During this dead time, the Cisco IOS software drops any repeat, duplicate FIND_NAME or NAME_RECOGNIZED frame sent by the same host. This timeout is effective only at the time of the login negotiation process. To restore the default of 6 seconds, use the no form of this command.

netbios name-cache recognized-timeout seconds

no netbios name-cache recognized-timeout

Syntax Description

Defaults

6 seconds

Command Modes

Global configuration

Command History

Examples

The following example sets the timeout to 15 seconds:

netbios name-cache recognized-timeout 15

Related Commands

netbios name-cache timeout

To enable NetBIOS name caching and to set the time that entries can remain in the NetBIOS name cache, use the netbios name-cache timeout command in global configuration mode. To restore the default of 15 minutes, use the no form of this command.

netbios name-cache timeout minutes

no netbios name-cache timeout minutes

Syntax Description

Defaults

15 minutes

Command Modes

Global configuration

Command History

Usage Guidelines

This command allows you to establish NetBIOS name caching. NetBIOS name-caching does not apply to static entries. Once the time expires, the entry will be deleted from the cache.

Examples

The following example sets the timeout to 10 minutes:

interface tokenring 0

 netbios name-cache timeout 10

Related Commands

netbios output-access-filter bytes

To define a byte access list filter on outgoing messages, use the netbios output-access-filter bytes command in interface configuration mode. To remove the entire access list, use the no form of this command.

netbios output-access-filter bytes name

no netbios output-access-filter bytes name

Syntax Description

Defaults

No access list is defined.

Command Modes

Interface configuration

Command History

Examples

The following example filters packets leaving Token Ring interface 1 using the NetBIOS access list named engineering:

interface tokenring 1

 netbios access-list bytes engineering permit 3 0xabcd 

 netbios output-access-filter bytes engineering

Related Commands

netbios output-access-filter host

To define a station access list filter on outgoing messages, use the netbios output-access-filter host command in interface configuration mode. To remove the entire access list, use the no form of this command.

netbios output-access-filter host name

no netbios output-access-filter host name

Syntax Description

Defaults

No access list filter is defined.

Command Modes

Interface configuration

Command History

Examples

The following example filters packets leaving Token Ring interface 1 using the NetBIOS access list named engineering:

interface tokenring 1

 netbios access-list host engineering permit W?Y?

 netbios output-access-filter host engineering

Related Commands

offload (backup)

To configure a backup group of offload devices, use the offload command in IP host backup configuration mode. To cancel the offload task on the Cisco Mainframe Channel Connection (CMCC) adapter, use the no form of this command.

offload device-address ip-address host-name device-name host-ip-link device-ip-link host-api-link device-api-link [broadcast]

no offload path device-address

Syntax Description

Defaults

No default behavior or values

Command Modes

IP host backup configuration

Command History

Usage Guidelines

Along with the path command, the offload backup command provides a quick way to configure an offload backup group.

Offload devices provide IP connectivity to a mainframe while offloading a large part of the TCP/IP processing to the CMCC adapter. Not every mainframe TCP/IP stack supports offload.

The offload command in IP host backup configuration mode uses the same underlying configuration parameters as the claw command in IP host backup configuration mode.

Examples

The following examples show two methods for entering the same IP host backup group information. The first group of commands is the long form, using the offload interface configuration command. The second group is the shortcut, using the path interface configuration command and an offload IP host backup configuration command.

Long form:

offload c000 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backup

offload c100 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backup

offload c200 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api backup

Shortcut form:

path c000 c100 c200

  offload 00 10.92.10.5 sysa router1 tcpip tcpip tcpip api

Related Commands

offload (primary)

To configure an offload device (read and write subchannel) for communication with a mainframe TCP/IP stack in offload mode and configure individual members of an offload backup group for the IP Host Backup feature, use the offload command in interface configuration mode. To cancel the offload task on the Cisco Mainframe Channel Connection (CMCC) adapter, use the no form of this command.

offload path device-address ip-address host-name device-name host-ip-link device-ip-link host-api-link device-api-link [broadcast] [backup]

no offload path device-address

Syntax Description

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Usage Guidelines

Offload devices provide IP connectivity to a mainframe while offloading a large part of the TCP/IP processing to the CMCC adapter. Not every mainframe TCP/IP stack supports offload.

The offload command uses the same underlying configuration parameters as does the claw command.

Examples

The following example shows how to enable IBM channel attach offload processing on a CMCC adapter's physical channel interface that is supporting a directly connected ESCON channel:

interface channel 3/0

ip address 10.92.0.1 255.255.255.0

offload 0100 00 10.92.0.21 CISCOVM EVAL TCPIP TCPIP TCPIP API

The following example shows how an IP host backup group is specified using the backup keyword:

interface Channel3/0

 no ip address

 no keepalive

 shutdown

 offload 0100 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup

 offload 0110 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup

 offload 0120 C0 10.30.1.2 TCPIP OS2TCP TCPIP TCPIP TCPIP API backup

 offload 0110 C2 10.30.1.3 TCPIP OS2TCP TCPIP TCPIP TCPIP API

Related Commands

offload alias

To assign a virtual IP address to a real IP address for an offload device on a Cisco Mainframe Channel Connection (CMCC) adapter, use the offload alias command in interface configuration mode. To remove the alias IP address, use the no form of this command.

offload alias real-ip alias-ip

no offload alias real-ip alias-ip

Syntax Description

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Usage Guidelines

Configure the offload alias command after you configure TCP/IP offload support on a CMCC adapter.

You can configure up to 8 different alias IP addresses for each real IP address of an offload device. You can assign the same alias IP address to multiple real IP addresses.

Examples

The following example configures TCP/IP offload support on a CMCC adapter for a host located at real IP address 10.10.21.3 with an alias IP address of 10.2.33.88:

interface channel 3/1

 offload E180 80 10.10.21.3 IPCLUST IPCLUST TCPIP TCPIP TCPIP API

 offload alias 10.10.21.3 10.2.33.88

path

To specify one or more data paths for the IP host backup, use the path command in interface configuration mode. To delete a single path, use the no form of this command.

path path

no path path

Syntax Description

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Usage Guidelines

Up to 16 values for the path argument can be specified in the path command.

The path command places the router in IP host backup configuration mode, where additional commands can be entered to define backup groups for Common Link Access for Workstations (CLAW) and offload connections.

Examples

The following examples show two methods for entering the same IP host backup group information. The first group is the long form, using the offload command in interface configuration mode. The second group of commands is the shortcut, using the path interface configuration command and an offload IP host backup configuration command.

Long form:

offload c000 00 198.92.10.5 sysa router1 tcpip tcpip backup

offload c100 00 198.92.10.5 sysa router1 tcpip tcpip backup

offload c200 00 198.92.10.5 sysa router1 tcpip tcpip backup

Shortcut form:

path c000 c100 c200

  offload 00 198.92.10.5 sysa router1 tcpip tcpip

Related Commands

ping sna

To initiate an Advanced Program-to-Program Communication (APPC) session with a named destination logical unit (LU) to run the APING transaction program to check network integrity and timing characteristics, use the ping sna command in privileged EXEC mode.

ping sna [-1] [-c consecutive-packets] [-i number-iterations] [-m mode] [-n] [-r] [-s size] [-t tpname] [-u userid -p password] destination

Syntax Description

Defaults

If -1 is not specified, the ping sna command will send the quantity of data represented by the -s size, -i number-iterations, and -c consecutive blocks options. It will be first sent in the direction from the ping sna requester to the receiver, then in the opposite direction.

If -c is not specified, consecutive data blocks per iteration defaults to 1.

If -i is not specified, number of iterations defaults to 2.

If -m is not specified, the mode defaults to #INTER.

If -s is not specified, the size of each block of data transferred defaults to 100 bytes.

If -t is not specified, the default transaction program name on the receiver is APINGD.

Command Modes

Privileged EXEC

Command History

Usage Guidelines

The ping sna command requires the destination to support the APING transaction program for the ping to succeed.

Examples

The following is an example of the ping sna command contact the destination NETA.CP001:

Router# ping sna NETA.CP001

Related Commands

pool

To define pool names for the TN3270 server and specify the number of screens and printers in each logical cluster, use the pool command in TN3270 server configuration mode. To remove a client IP pool, use the no form of this command.

pool poolname [cluster layout layout-spec-string]

no pool poolname

Syntax Description

Defaults

The default value for the layout-spec-string argument is 1a.

Command Modes

TN3270 server configuration

Command History

Usage Guidelines

The pool and allocate lu commands enable the TN3270 server to know the relationships between screen and printer LUs. These commands are an alternative to the logical unit (LU) nailing feature that allows clients to be nailed to LUs.

The pool command is configured in the TN3270 scope. The pool command provides the pool names and the definitions of the number of screens and printers in one logical cluster. Each pool statement must have a unique pool name.

The TN3270 server validates pool names when configuring a pool name and when processing the name received on a CONNECT request from the client. The TN3270 server rejects an invalid name and truncates the name received in the CONNECT request from the client to eight characters or at an invalid character (whichever comes first) when processing the CONNECT request.

When using a pool command to create a cluster, use a combination of the following values in the layout-spec-string argument:

s (screen)

p (printer)

a (any, or wildcard) (refers to a printer or a screen)

Examples

Use the following format to define the layout-spec-string argument, where the decimal-num argument is a decimal number from 1 to 255:

pool poolname cluster layout {decimal-nums}{decimal-nump}{decimal-numa}

The total sum of the numbers must be less than or equal to 255. No spaces are used between the entries in the layout-spec-string argument. The default is 1a, which defines one screen or one printer. A screen, printer, or a wildcard definition cannot be followed by a definition of the same type. A screen definition can be followed only by a printer or wildcard. Similarly, a printer definition can be followed only by a wildcard or a screen definition.

The following are examples of invalid layout-spec-string values, and the corresponding corrected specification:

•A layout-spec-string of 3s6s is invalid. The correct specification is 9s.

•A layout-spec-string of 3s6p7a8a is invalid. The correct specification is 3s6p15a.

•A layout-spec-string of 255s10p is invalid. Although the decimal number for any portion of the layout-spec-string can be from 1 to 255, the total number across all parameters cannot exceed 255. To correct this example, you can reduce the screens to 245 as 245s10p.

The combination of a screen, printer, and wildcard constitute a group. The layout-spec-string argument can support a maximum of four groups.

Consider the following example:

pool CISCO cluster layout 2s3p4a5s6a7s8p9s

There are four groups in this definition: 2s3p4a, 5s6a, 7s8p and 9s.

Pools must be defined before any pool references under the listen points are defined. Also, pools must be defined before they are referenced by other statements in the configuration. Failure to define the pool before it is referenced will cause the referencing configuration to be rejected.

Pools that are deleted (using the no form of the command) will cause all statements referencing the pool to be deleted.

The following criteria apply to the creation of pool names and local addresses:

•Pool and LU names must be unique; they cannot be identical.

•Local address ranges for pools must not overlap.

•Local address ranges for LU pools must not overlap with the existing client nailing configuration.

•Pool configurations made while LUs are in use do not affect the current LU configuration.

The following example uses the pool command to create two pools, pcpool and unixpool:

tn3270-server

 pool pcpool cluster layout 4s1p

 pool unixpool cluster layout 49s1p

listen-point 10.20.30.40

 client ip 10.10.10.2 pool pcpool

 pu PU1 91903315 dlur

  allocate lu 1 pool pcpool clusters 50

 pu PU2 91903345 dlur

  allocate lu 1 pool unixpool clusters 5

In this example, the pcpool contains a cluster of 4 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the pcpool contains a total of 50 clusters with each cluster containing 5 LUs. Note that the remaining 5 LUs automatically go to the generic pool.

The unixpool contains 49 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the unixpool contains a total of 5 clusters with each cluster containing 50 LUs. Again, note that the last 5 LUs automatically go to the generic pool.

Related Commands

ppp bcp tagged-frame

To enable the negotiation of IEEE 802.1Q-tagged packets over PPP links, use the ppp bcp tagged-frame command in interface configuration mode. To disable the negotiation of IEEE 802.1Q-tagged packets over PPP links, use the no form of this command.

ppp bcp tagged-frame

no ppp bcp tagged-frame

Syntax Description

This command has no arguments or keywords.

Defaults

The ppp bcp tagged-frame command is enabled by default.

Command Modes

Interface configuration

Command History

Usage Guidelines

This command provides flexibility in specifying which Bridge Control Protocol (BCP) options will be negotiated with the peer.

Examples

The following example configures Ethernet interface 0 to bridge packets using VLAN ID 100, and assigns the interface to bridge group 1:

interface serial 4/0

 ppp bcp tagged-frame

preferred-nnserver

To specify a preferred network node (NN) as server, use the preferred-nnserver command in Dependent Logical Unit Requestor (DLUR) configuration mode. To remove the preference, use the no form of this command.

preferred-nnserver name

no preferred-nnserver

Syntax Description

Defaults

No default behavior or values

Command Modes

DLUR configuration

Command History

Usage Guidelines

The preferred-nnserver command is valid only on the virtual channel interface. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing Advanced Peer-to-Peer Networking (APPN) products, including virtual telecommunications access method (VTAM), the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to 8 characters long; for example, RA12.NODM1PP. The portion of the name before the period is the network entity title (NET) ID and is shared between entities in the same logical network.

When no preferred server is specified, the Dependent Logical Unit Requestor (DLUR) will request NN server support from the first suitable node with which it makes contact. If refused, it will try the next one, and so on.

If a preferred server is specified, then DLUR will wait a short time to allow a link to the preferred server to materialize. If the preferred server is not found in that time, any suitable node can be used.

DLUR will not relinquish the current NN server merely because the preferred server becomes available.

Examples

The following example selects SYD.VMX as the preferred NN server:

preferred-nnserver SYD.VMX

Related Commands

priority-list protocol bstun

To establish block serial tunnel (BSTUN) queueing priorities based on the BSTUN header, use the priority-list protocol bstun command in global configuration mode. To revert to normal priorities, use the no form of this command.

priority-list list-number protocol bstun queue [gt | lt packetsize] [address bstun-group bsc-addr]

no priority-list list-number protocol bstun queue [gt | lt packetsize] [address bstun-group bsc-addr]

Syntax Description

Defaults

Prioritize based on BSTUN header.

Command Modes

Global configuration

Command History

Examples

In the following example, the output interface examines the header information and places packets with the BSTUN header on the output queue specified as medium:

priority-list 1 protocol bstun medium

Related Commands

priority-list protocol ip tcp

To establish block serial tunnel (BSTUN) or serial tunnel (STUN) queueing priorities based on the TCP port, use the priority-list protocol ip tcp command in global configuration mode. To revert to normal priorities, use the no form of this command.

priority-list list-number protocol ip queue tcp tcp-port-number

no priority-list list-number protocol ip queue tcp tcp-port-number

Syntax Description

Defaults

The default queue value is normal.

Command Modes

Global configuration

Command History

Usage Guidelines

Use the priority-list protocol stun address command first. Priority settings created with this command are assigned to Synchronous Data Link Control (SDLC) ports.

Note SDLC local acknowledgment with the priority option must be enabled using the stun route address tcp command.

Examples

In the following example, queueing priority for address C1 using priority list 1 is set to high. A priority queue of high is assigned to the SDLC port 1994.

priority-list 1 stun high address 1 c1

priority-list 1 protocol ip high tcp 1994

In the following example, queueing priority for address C1 using priority list 1 is set to high. A priority queue of high is assigned to BSTUN port 1976.

priority-list bstun high address 1 c1

priority-list 1 protocol ip high 1976

Related Commands

priority-list protocol stun address

To establish serial tunnel (STUN) queueing priorities based on the address of the serial link, use the priority-list protocol stun address command in global configuration mode. To revert to normal priorities, use the no form of this command.

priority-list list-number protocol stun queue address group-number address-number

no priority-list list-number protocol stun queue-keyword address group-number address-number

Syntax Description

Defaults

The default queue value is normal.

Command Modes

Global configuration

Command History

Usage Guidelines

Note SDLC local acknowledgment with the priority option must be enabled using the stun route address interface serial command.

The priority-list command is described in greater detail in the "Performance Management Commands" chapter in the Cisco IOS Configuration Fundamentals Command Reference.

Examples

In the following example, queueing priority for address C1 using priority list 1 is set to high:

priority-list 1 stun high address 1 c1

Related Commands

profile

To specify a name and a security protocol for a security profile or to modify a profile and enter profile configuration mode, use the profile command in security configuration mode. To remove this name and protocol specification, use the no form of this command.

profile profilename [ssl | none]

no profile profilename {ssl | none}

Syntax Description

Defaults

No default behavior or values

Command Modes

Security configuration

Command History

Usage Guidelines

This command creates or modifies a security profile. To create a profile, specify the name of the new profile along with the security type. To modify a security profile, specify the name of the profile without the security type. The security type is required only when creating a profile. Using the security type when modifying a profile will result in an error.

Profile names cannot be duplicated.

Entering the no form of this command deletes the profile definition and all of its subcommand definitions (encryptorder, servercert, keylen, certificate reload commands). Entering the no form of this command deletes the sec-profile command specifications on all listen points where it is defined.

Entering the profile command places the router in profile configuration mode. Entering the no form of the command places the user into the security configuration mode.

This command has no retroactive effect.

Examples

The following example specifies LAM as the profile name and ssl as the security protocol. When the no profile LAM command is configured, all new client connections will be nonsecure.

tn3270-server

 security

 profile LAM ssl

  keylen 40

  servercert slot0:lam

  certificate reload

listen-point 10.10.10.1 

 sec-profile LAM

 pu DIRECT 012ABCDE tok 0 04

 no profile LAM none

Related Commands

pu (DLUR)

To create a physical unit (PU) entity that has no direct link to a host or to enter PU configuration mode, use the pu command in DLUR configuration mode. To remove the PU entity, use the no form of this command.

pu pu-name idblk-idnum ip-address

no pu pu-name

Syntax Description

Defaults

No PU is defined.

Command Modes

DLUR configuration

Command History

Usage Guidelines

If the PU is already created, the pu pu-name command with no arguments places the router in PU configuration mode. In this mode you can modify an existing PU DLUR entity.

A typical usage for the IP address is to reserve an IP address per host application. For example, clients wanting to connect to Time Sharing Option (TSO) specify an IP address that will be defined with PUs that have LOGAPPL=TSO.

Examples

The following example defines three PUs. Two of the PUs share the same IP address and the third PU has a separate IP address:

pu p0  05D99001 192.195.80.40

pu p1  05D99002 192.195.80.40

pu p2  05D99003 192.195.80.41

Related Commands

pu (listen-point)

To create a physical unit (PU) entity that has a direct link to a host or to enter listen-point PU configuration mode, use the pu command in listen-point configuration mode. To remove the PU entity, use the no form of this command.

pu pu-name idblk-idnum type adapter-number lsap [rmac rmac] [rsap rsap] [lu-seed lu-name-stem]

no pu pu-name

Syntax Description

Defaults

The default remote SAP address is 04 (hexadecimal).

Command Modes

Listen-point configuration

Command History

Usage Guidelines

The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in listen-point PU configuration mode, where you can modify an existing PU entity.

The pu listen-point command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.

For a link via a channel on this Cisco Mainframe Channel Connection (CMCC) adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids contention for SAP numbers and is also necessary if you configure duplicate MAC addresses for fallback Cisco Systems Network Architecture (CSNA) or Cisco Multipath Channel (CMPC) access to the host.

Examples

The following example configures the TN3270 server to be active and has one PU, CAPPU1, trying to connect. An LU seed using hexadecimal digits is defined.

tn3270-server

pu CAPPU1 05D18101 token-adapter 3 04 rmac 4000.0501.0001 lu-seed CAP01L##

The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.

lan tokenring 0

 adapter 0 4000.0000.0001

 adapter 1 4000.0000.0002

tn3270-server

 listen-point 10.20.30.40

  pu PU1 05d00001 token-adapter 1 8 rmac 4000.0000.0001 rsap 4

Related Commands

pu (TN3270)

To create a physical unit (PU) entity that has its own direct link to a host and enter PU configuration mode, use the pu command in TN3270 server configuration mode. To remove the PU entity, use the no form of this command.

pu pu-name idblk-idnum ip-address type adapter-number lsap [rmac rmac] [rsap rsap] [lu-seed lu-name-stem]

no pu pu-name

Syntax Description

Defaults

No PU is defined.
The default remote SAP address is 04 (hexadecimal).

Command Modes

TN3270 server configuration

Command History

Usage Guidelines

The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode, where you can modify an existing PU entity.

The pu (TN3270) command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.

For a link via a channel on this Cisco Mainframe Channel Connection (CMCC) adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback Cisco Systems Network Architecture (CSNA) or Cisco Multipath Channel (CMPC) access to the host.

Examples

The following example configures the TN3270 server to be active, and has one PU, CAPPU1, trying to connect in. An LU seed using hexadecimal digits is defined.

tn3270-server

pu CAPPU1 05D18101 10.14.20.34 token-adapter 3 04 rmac 4000.0501.0001 lu-seed CAP01L##

The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on token ring adapter 0.

lan tokenring 0

 adapter 0 4000.0000.0001

 adapter 1 4000.0000.0002

tn3270-server

 pu PU1 05d00001 10.0.0.1 token-adapter 1 8 rmac 4000.0000.0001 rsap 4

Related Commands

pu dlur (listen-point)

To create a physical unit (PU) entity that has no direct link to a host or to enter listen-point PU configuration mode, use the pu dlur command in listen-point configuration mode. To remove the PU entity, use the no form of this command.

pu pu-name idblk-idnum dlur [lu-seed lu-name-stem]

no pu pu-name idblk-idnum dlur [lu-seed lu-name-stem]

Syntax Description

Defaults

No PU is defined.

Command Modes

Listen-point configuration

Command History

Usage Guidelines

If the PU is already created, the pu dlur command without any arguments starts listen-point PU configuration mode. In this mode you can modify an existing listen-point Dependent Logical Unit Requestor (DLUR) PU entity.

You should define the DLUR before you configure the listen-point DLUR PU.

A typical usage for the IP address is to reserve an IP address for each application. For example, clients wanting to connect to Time Sharing Option (TSO) specify an IP address that is defined with PUs that have LOGAPPL=TSO.

If the lu-seed option is not configured, the PU name is used as the implicit Luseed to generate the LU name. If the lu-seed option is configured, then there is an explicit LU name.

If the explicit LU names conflict, the TN3270 server will reject the PU configuration. If the implicit LU names (that is, the PU names) conflict, the TN3270 server will accept the PU definitions, but the LU names will consist of a modified, truncated version of the PU name and the local address. Valid and invalid LU seed syntax is shown in Table 16.

Examples

The following example defines three PUs in the listen point with an IP address of 172.18.4.18:

tn3270-server

listen-point 172.18.4.18

 pu p0  05D99001 dlur

 pu p1  05D99002 dlur

 pu p2  05D99003 dlur

The following is an example of the TN3270 server configured with LU pooling. A listen-point PU is configured to define DLUR PUs using the dynamic LU naming. Note that the lu deletion command must be configured with the named option. The PU pu1 is defined with lu-seed abc##pqr. Using hexadecimal numbers for ##, the LU names for this PU are ABC01PQR, ABC02PQR, ABC0APQR.... up to ABCFFPQR. Similarly, the PU pu2 is defined with lu-seed pqr###. Using decimal numbers for ###, the LU names for this PU are PQR001, PQR002... up to PQR255.

The LUs ABC01PQR through ABC32PQR and PQR100 through PQR199 are allocated to the pool SIMPLE. The LUs ABC64PQR through ABC96PQR and PQR010 through PQR035 are allocated to the pool PCPOOL. The remaining LUs are in the generic pool.

tn3270-server

 pool simple cluster layout 1s

 pool pcpool cluster layout 4s1p

 lu deletion named

 dlur neta.shek neta.mvsd

  lsap tok 15 04

    link she1 rmac 4000.b0ca.0016

 listen-point 172.18.4.18

 pu pu1 91903315 tok 16 08 lu-seed abc##pqr

   allocate lu 1 pool simple clusters 50

   allocate lu 100 pool pcpool clusters 10

 pu pu2 91913315 dlur lu-seed pqr###

   allocate lu 10 pool pcpool clusters 5

   allocate lu 100 pool simple clusters 100

Related Commands

qllc accept-all-calls

To enable the router to accept a call from any remote X.25 device, use the qllc accept-all-calls command in interface configuration mode. To cancel the request, use the no form of this command.

qllc accept-all-calls

no qllc accept-all-calls

Syntax Description

This command has no arguments or keywords.

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

This command allows Qualified Logical Link Control (QLLC) to accept all inbound X.25 calls, provided that the QLLC Call User Data (CUD) is in the call packet and the destination X.121 address in the call packet matches the serial interface's configured destination X.121 address or subaddress. When this command is used, the source X.121 address need not be configured via an x25 map qllc command for the call to be accepted.

This command is applicable to QLLC support for data-link switching plus (DLSw+), Advanced Peer-to-Peer Networking (APPN), and downstream physical unit (DSPU). It is not applicable to QLLC support for source-route bridging (SRB) and remote source-route bridging (RSRB).

Examples

The following example enables QLLC connectivity for DLSw+ and allows QLLC to accept all inbound X.25 calls. Every X.25 connection request for X.121 address 0308 with QLLC CUD is directed to DLSw+. The first switched virtual circuit (SVC) to be established will be mapped to virtual MAC address 4000.0B0B.0001. If a call comes in with an X.121 address of 0308, the call will be forwarded to MAC address 4001.1161.1234.

interface serial 0

 encapsulation x25

 x25 address 0308

 qllc accept-all-calls

 qllc dlsw vmac 4000.0B0B.0001 500 partner 4001.1161.1234

Related Commands

qllc dlsw

To enable data-link switching plus (DLSw+) over Qualified Logical Link Control (QLLC), use the qllc dlsw command in interface configuration mode. To cancel the configuration, use the no form of this command.

qllc dlsw {subaddress subaddress | pvc pvc-low [pvc-high]} [vmac vmacaddr poolsize] [partner partner-macaddr] [sap ssap dsap] [xid xidstring] [npsi-poll]

no qllc dlsw {subaddress subaddress | pvc pvc-low [pvc-high]} [vmac vmacaddr poolsize] [partner partner-macaddr] [sap ssap dsap] [xid xidstring] [npsi-poll]

Syntax Description

Defaults

No default behavior or values

Command Modes

Interface configuration

Command History

Usage Guidelines

Any incoming call whose X.121 destination address matches the router's X.121 address and this subaddress will be dispatched to DLSw+ (with an ID.STN IND). If a router is providing several QLLC services, different subaddresses must be used to discriminate between them. Subaddresses can be used even if a remote X.25 device is not explicitly mapped to a specific virtual MAC address. This is most useful when PU 2.1 devices are connecting to a host because the X.25 device's control point name and network name are used to validate the connection, rather than some virtual MAC address. The subaddress is optional. If no subaddress is provided, any incoming call that matches the router's X.121 address will be dispatched to DLSw+. On outgoing calls the subaddress is concatenated to the interface's X.121 address.

When DLSw+ receives a Can You Reach inquiry about a virtual MAC address in the pool, the QLLC code will attempt to set up a virtual circuit to the X.121 address that maps to the virtual MAC address specified. If an incoming call is received, QLLC sends an ID.STN.IND with a virtual MAC address from the pool to DLSw+. If there is no virtual MAC address, then the x25 map qllc or x25 pvc qllc command must provide a virtual MAC address.

The npsi-poll keyword is needed to support PU 2.0 on the partner side that wants to connect to a front-end processor (FEP) on the X.25 side. In a Token Ring or DLSw+ environment, the PU 2.0 will send a null XID to the FEP. If the software forwards this null XID to an X.25 attached FEP, the FEP will assume that it is connecting to PU2.1, and will break off the connection when the PU 2.0 next sends an XID Format 0 Type 2.

Examples

The following commands assign virtual MAC address 1000.0000.0001 to a remote X.25-attached 3174, which is then mapped to the X.121 address of the 3174 (31104150101) in an X.25-attached router:

interface serial 0

 x25 address 3110212011

 x25 map qllc 1000.000.0001 31104150101

 qllc dlsw partner 4000.1161.1234

qllc largest-packet

To indicate the maximum size of the Systems Network Architecture (SNA) packet that can be sent or received on an X.25 interface configured for Qualified Logical Link Control (QLLC) conversion, use the qllc largest-packet command in interface configuration mode. To restore the default largest packet size, use the no form of this command.

qllc largest-packet virtual-mac-addr max-size

no qllc largest-packet virtual-mac-addr max-size

Syntax Description

Defaults

Maximum size is 265 bytes.

Command Modes

Interface configuration

Command History

Usage Guidelines

SNA packets that are larger than the largest value allowed on the X.25 connection and are received on the Logical Link Control, type 2 (LLC2) interface are segmented before being sent on the X.25 interface. When a segmented packet is received on the X.25 interface, it is passed immediately to the LLC2 interface, and no effort is made to wait for the segment to be completed.

When the remote X.25 device has a limit on the maximum total length of recombined X.25 segments it will support, you can use the qllc largest-packet command to ensure that the length is not exceeded. For example, a device whose maximum SNA packet size is limited to 265 bytes might not be able to handle a series of X.25 packets that it has to recombine to make a 4, 8, or 17 KM SNA packet, such as one often encounters in an LLC2 environment.

You use the qllc largest-packet command in conjunction with the x25 map qllc and qllc srb commands.

Note Do not configure the maximum SNA packet size on an X.25 interface to be larger than the maximum SNA packet size allowed on the LLC2 interface.

Consult your IBM documentation to set the maximum packet size on the remote X.25 device.

Examples

In the following example, the maximum packet size that has been established for the virtual circuit is used as the maximum packet size that can be sent or received on the X.25 interface:

interface serial 0

 encapsulation x25

 x25 address 31102120100

 x25 map qllc 0100.0000.0001 31104150101

 qllc srb 0100.0000.0001 201 100

!

 qllc partner 0100.0000.0001 4000.0101.0132

 qllc xid 0100.0000.0001 01720001

 qllc largest-packet 0100.0000.0001 521

Related Commands

qllc npsi-poll

To enable a connection between a physical unit (PU) 2 on the LAN side and a front-end processor (FEP) running Network Control Program (NCP) Packet Switching Interface (NPSI) on the X.25 side, use the qllc npsi-poll command in interface configuration mode. To disable this capability, use the no form of this command.

qllc npsi-poll virtual-mac-addr

no qllc npsi-poll virtual-mac-addr

Syntax Description

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

The qllc npsi-poll command is necessary only when the upstream device is a front-end processor (FEP) running NPSI and the downstream device is a PU 2.

This command is necessary because in a Token Ring or remote source-route bridging (RSRB) environment the LAN attached devices start up by sending a null exchange ID packet upstream. If the Cisco IOS software forwards this null exchange identification (XID) to an X.25-attached FEP, the FEP responds as if it were connecting to a PU2.1 device, and breaks the connection when the PU 2 next sends an XID Format 0 Type 2. The qllc npsi-poll command intercepts any null XID packet that the software receives on the LAN interface, and returns a null XID response to the downstream device. It continues to allow XID Format 3 and XID Format 0 packets through the X.25 device.

Examples

The following example facilitates a connection between a FEP running NPSI and a downstream PU 2.0:

qllc npsi-poll 0100.0000.0001

Related Commands

qllc partner

To enable a router configured for Qualified Logical Link Control (QLLC) conversion to open a connection to the local Token Ring device on behalf of the remote X.25 device when an incoming call is received, use the qllc partner command in interface configuration mode. To disable this capability, use the no form of this command.

qllc partner virtual-mac-addr mac-addr

no qllc partner virtual-mac-addr mac-addr

Syntax Description

Defaults

Disabled

Command Modes

Interface configuration

Command History

Usage Guidelines

When the Cisco IOS software receives an incoming call from the designated X.121 address, it opens a Logical Link Control, type 2 (LLC2) connection with the device at the given MAC address. Both the MAC address of the Token Ring device and the virtual MAC address for the remote X.25 device with which it is to communicate are required in order for the software to initiate connections with the Token Ring device. This allows the Token Ring host to be permanently ready to accept a connection rather than requiring operator action at the host to initiate the connection with the X.25 device.

You must issue the qllc partner command for each remote X.25 device that will communicate with the local Token Ring host through this interface.

You use the qllc partner command in conjunction with the x25 map qllc and qllc srb commands.

Examples

In the following example, the qllc partner command is used to associate the virtual MAC address 0100.0000.0001, as defined in the previous x25 map qllc entry, with the MAC address of the Token Ring host that will communicate with the remote X.25 device:

interface serial 0

 encapsulation x25

 x25 address 31102120100

 x25 map qllc 0100.0000.0001 31104150101

 qllc srb 0100.0000.0001 201 100

 qllc partner 0100.0000.0001 4000.0101.0132

 qllc xid 0100.0000.0001 01720001

Related Commands