|
|
This chapter describes native client interface architecture (NCIA) support for Systems Network Architecture (SNA) devices. NCIA Server and the NCIA client/server model extends the scalability of NCIA I, the earlier NCIA implementation, by minimizing the number of central-site RSRB or DLSw+ peer connections required to support a large number of NCIA clients. For a complete description of the commands mentioned in this chapter, refer to the "NCIA Server Configuration Commands" chapter of the Bridging and IBM Networking Command Reference.
Cisco's NCIA server feature implements RFC 2114, Data Link Switch Client Access Protocol.
The network configuration shown in Figure 115 includes NCIA clients that connect to a front-end processor (FEP) on a Token Ring through a local router (the NCIA server). The virtual ring is used in conjunction with DLSw+ local switch. The routing information field (RIF) of each circuit is terminated on the virtual ring. Figure 116 shows a logical view of an NCIA server session using a DLSw+ local switch (connected to a local Token Ring). In addition to Token Ring, an NCIA server also supports Ethernet, SDLC, and QLLC network connections as well as Channel Interface Processor (CIP) connections through a DLSw+ local switch. For more information on the different media types that a DLSw+ local switch supports, refer to the "Configuring DLSw+" chapter.


To configure an NCIA session connected to a local Token Ring, perform the tasks in the following sections.
For a configuration example, see "NCIA Server Session to Local Token Ring Using DLSw+ Local Switch Example" at the end of this chapter.
In DLSw+, the source-bridge ring group specifies the virtual ring that will appear to be the last ring in the RIF. This ring is transparent to the NCIA client. From the host's point of view, all NCIA clients look like stations sitting on the virtual ring. To define a source-bridge ring group for DLSw+, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Define a ring group. | source-bridge ring-group ring-group [virtual-mac-address]1 |
| Task | Command |
|---|---|
| Define the DLSw+ local peer. | dlsw local-peer [peer-id ip-address] [group group] [border] [cost cost] [lf size] [keepalive seconds] [passive] [promiscuous] [biu-segment]1 |
Configuring an NCIA server on a router enables the router to perform two roles:
To configure an NCIA server, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Configure the NCIA server. | ncia server server-number server-ip-address server-virtual-mac-address virtual-mac-address virtual-mac-range [inbound-only] [keepalive seconds] [tcp_keepalive minutes] |
In the network configuration shown in Figure 117, the NCIA server uses DLSw+ to connect its clients to the FEP through a remote router. Figure 118 shows a logical view of the NCIA Server session with DLSw+.


For a configuration example, see "NCIA Server Session with DLSw+ Example" at the end of this chapter.
The source-bridge ring can be shared between DLSw+ and SRB/RSRB. In DLSw+, the source-bridge ring group specifies the virtual ring that will appear to be the last ring in the RIF. Because RIFs are terminated at the router, there is no correlation between the ring-group number specified in DLSw+ peers. The numbers can be the same for management simplicity, but they do not have to be. To define a source-bridge ring group for DLSw+, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Define a ring group. | source-bridge ring-group ring-group [virtual-mac-address]1 |
| Task | Command |
|---|---|
| Define the DLSw+ local peer. | dlsw local-peer [peer-id ip-address] [group group] [border] [cost cost] [lf size] [keepalive seconds] [passive] [promiscuous] [biu-segment] |
| Task | Command |
|---|---|
| Define a TCP encapsulation remote peer. | dlsw remote-peer list-number tcp ip-address [backup-peer ip-address] [bytes-netbios-out bytes-list-name] [cost cost] [dest-mac mac-address] [dmac-output-list access-list-number] [dynamic] [host-netbios-out host-list-name] [inactivity minutes] [keepalive seconds] [lf size] [linger minutes] [lsap-output-list list] [no-llc minutes] [priority] [tcp-queue-max size] [timeout seconds] |
Configuring an NCIA server on the local router enables the router to perform two roles:
To configure an NCIA server, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Configure the NCIA server. | ncia server server-number server-ip-address server-virtual-mac-address virtual-mac-address virtual-mac-range [inbound-only] [keepalive seconds] [tcp_keepalive minutes] |
In the network configuration shown in Figure 119, the NCIA server uses DSPU to connect its clients to the FEP through a remote router. Figure 120 shows a logical view of the NCIA Server session with RSRB/DLSw+ and DSPU.


For a configuration example, see "NCIA Server Session with DSPU Example" at the end of this chapter.
| Task | Command |
|---|---|
| Define a DSPU host over Token Ring, Ethernet, FDDI, RSRB, or virtual data link control connections. | dspu host host-name xid-snd xid rmac remote-mac [rsap remote-sap] [lsap local-sap] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] [focalpoint] |
| Task | Command |
|---|---|
| Explicitly define a downstream PU over Token Ring, Ethernet, FDDI, RSRB, virtual data link control , or NCIA connections. | dspu pu pu-name [rmac remote-mac] [rsap remote-sap] [lsap local-sap] [xid-rcv xid] [interface slot/port] [window window-size] [maxiframe max-iframe] [retries retry-count] [retry-timeout retry-timeout] |
| Task | Command |
|---|---|
| Define a dedicated LU or a range of dedicated LUs for a downstream PU. | dspu lu lu-start [lu-end] {host host-name host-lu-start | pool pool-name} [pu pu-name] |
| Task | Command |
|---|---|
| Configure the NCIA server as the underlying transport mechanism. | dspu ncia [server-number] |
| Task | Command |
|---|---|
| Enable local SAP for downstream PUs. | dspu ncia enable-pu [lsap local-sap] |
The network configuration shown in Figure 121 includes NCIA clients that connect to a FEP on a Token Ring through a remote router. Figure 122 shows a logical view of the NCIA Server session with RSRB (to a remote Token Ring). Because DLSw+ is the latest technology provided by Cisco, Cisco does not encourage using the NCIA Server feature with RSRB. If the router on the host side is running DLSw+, RSRB should not be used. Support for the NCIA Server feature with RSRB is provided to encourage RSRB users to migrate to DLSw+.


For a configuration example, see "NCIA Server Session with DLSw+ Example" at the end of this chapter.
The source-bridge virtual ring can be shared between DLSw+ and SRB/RSRB. In DLSw+, the source-bridge ring group specifies the virtual ring that will appear to be the last ring in the RIF. Because RIFs are terminated at the router, the ring group numbers specified in commands to set up DLSw+ peers can be different. The ring group numbers can be the same for management simplicity, but they do not have to be.
To define a source-bridge ring group for DLSw+, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Define a ring group. | source-bridge ring-group ring-group [virtual-mac-address]1 |
In our implementation, whenever you connect Token Rings using non-Token Ring media, you must treat that non-Token Ring media as a virtual ring by assigning it to a ring group. Every router with which you want to exchange Token Ring traffic must be a member of this same ring group. For more information about defining a ring group, see the "Define a Ring Group in SRB Context" section of the "Configuring Source-Route Bridging" chapter of this document.
To identify the remote peers, perform the following task in global configuration mode:
Specify one source-bridge remote-peer command for each peer router that is part of the virtual ring. Also specify one source-bridge remote-peer command to identify the IP address of the local router.
NCIA Server supports only RSRB pass-through mode. Local acknowledgment is not supported.
| Task | Command |
|---|---|
| Define the DLSw+ local peer. | dlsw local-peer [peer-id ip-address] [group group] [border] [cost cost] [lf size] [keepalive seconds] [passive] [promiscuous] [biu-segment] |
Configuring an NCIA server on a router enables the router to perform two roles:
To configure an NCIA server, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Configure the NCIA server. | ncia server server-number server-ip-address server-virtual-mac-address virtual-mac-address virtual-mac-range [inbound-only] [keepalive seconds] [tcp_keepalive minutes] |
To configure an RSRB ring for the NCIA server on the local router, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Define the NCIA/RSRB interface. | ncia rsrb virtual-ring local-bridge local-ring ncia-bridge ncia-ring virtual-mac-address |
You can monitor and maintain the operation of an NCIA Server network. To display information about the state of the NCIA Server feature and perform maintenance tasks, perform the following tasks in EXEC mode:
| Task | Command |
|---|---|
| Show the status of the NCIA server. | show ncia server [server-number] |
| Show the status of the NCIA client. | show ncia client [sap-list] [ip-address] |
| Terminate an NCIA client connection. | clear ncia client [ip-address] |
| Show the status of an NCIA circuit. | show ncia circuits [id-number] |
| Drop an NCIA circuit. | clear ncia circuit [id-number] |
| Terminate the active connection to the specified client and release all control blocks of the registered client. | clear ncia client registered [ip-address] |
| Stop an NCIA server. | ncia stop |
| Restart an NCIA server. | ncia start |
The following sections provide NCIA Server configuration examples:
Figure 123 illustrates the use of DLSw+ local peer with an NCIA Server session to a local Token Ring.

The following is a configuration file for the network example shown in Figure 123:
source-bridge ring-group 44 dlsw local-peer ncia server 1 10.2.20.4 4000.3174.0001 4000.0000.0001 128 ! interface token ring 0 ring-speed 16 source-bridge 21 3 44
Figure 124 illustrates the use of DLSw+ with an NCIA Server session.

The following is a configuration file for the network example shown in Figure 124:
source-bridge ring-group 44 dlsw local-peer peer-id 10.2.20.4 dlsw remote-peer 0 tcp 10.2.20.3 ncia server 1 10.2.20.4 4000.3174.0001 4000.0000.0001 128
Figure 125 illustrates an NCIA Server session with RSRB/DLSw+ and DSPU.

The following is a configuration file for the network example shown in Figure 125:
ncia server 1 10.2.20.4 4000.3745.0001 4000.0000.0001 128 ! dspu ncia 1 dspu ncia enable-pu lsap 8 ! dspu host HOST-9370 xid-snd 11100001 rmac 4000.1060.1000 rsap 4 lsap 4 ! dspu pu CISCOPU-A xid-rcv 01700001 dspu lu 2 6 host HOST-9370 2 ! interface TokenRing 0 ring-speed 16 llc2 xid-retry-time 0 dspu enable-host lsap 4 dspu start HOST-9370
Figure 126 illustrates the use of RSRB with an NCIA Server session.

The following is a configuration file for router Cisco 2 for the network example shown in Figure 126:
source-bridge ring-group 44 source-bridge ring-group 22 source-bridge remote-peer 22 tcp 10.2.20.3 source-bridge remote-peer 22 tcp 10.2.20.4 dlsw local-peer ncia server 1 10.2.20.4 4000.3174.0001 4000.0000.0001 128 ncia rsrb 22 2 33 4 44 1111.1111.2222
|
|