Access to a NetWare application, such as print or file services or network management, usually requires that the appropriate protocol is routed on each interface that provides access to use that application. However, when a protocol is bridged on an interface, it cannot be routed on that interface. Therefore, when bridging is used, alternate access to the application is provided through a virtual internal ring. This principle applies to all NetWare applications and services, including RCONSOLE, SNMP, NetWare for Macintosh, NetWare for SAA*, and NetWare for NFS*.
The virtual internal ring is attached to each bridged interface through a separate virtual internal bridge (as described in Configuring Multiport Bridging ). In this case, the required protocol must be attached to the virtual internal ring through a virtual token ring board that uses the SRBRIDGE.LAN driver. The virtual board is then attached to the virtual internal ring automatically. Figure 10 shows an example of this configuration using IPX. Note that the two token rings might be part of a larger looped topology.
Figure 10
Server-Based Bridging
Ensure that the necessary frame types are configured in NIASCFG when making attachments (bindings). The virtual token ring board uses the same two frame types that physical boards use:
For more information about server-based bridging, refer to Understanding.
Before you begin, you must complete one of the following tasks:
To configure bridging with access to applications, complete the following steps:
Load NIASCFG and configure the SRBRIDGE.LAN driver.
Select Configure NIAS > Protocols and Routing > Boards and do one of the following:
If you are adding a new virtual board:
If you are modifying an existing virtual board, select the interface to which you are binding the protocol.
NOTE: The SRBRIDGE.LAN driver replaces the VBRIDGE.LAN driver from previous NetWare routing software releases.
Enter a name in the Board Name field that identifies the network interface, press Enter , then press Esc to return to the Internetworking Configuration menu.
NOTE: Use of a SRBRIDGE virtual board adds only one node address to the source route bridge node table.
Select the following parameter path:
Select Protocols > Source Route Bridge
Set the Bridge Status parameter to Enabled .
Assign a value to the Bridge Number parameter.
If necessary, assign a value to the Virtual Ring Number to enable the internal virtual ring, press Enter , then press Esc to return to the Internetworking Configuration menu.
The internal virtual ring does not need a number unless more than two interfaces are attached.
Bind each protocol you need to access applications to the SRBRIDGE driver by selecting Bindings and doing one of the following for each protocol:
If you are adding a new binding:
If you are modifying an existing binding, select the SRBRIDGE driver to which you are binding the protocol.
NOTE: SRBRIDGE automatically configures source route end station support.
Bind the source route bridge software to each LAN interface.
Select Bindings and do one of the following:
If you are adding a new binding:
If you are modifying an existing binding, select the interface to which you are binding the protocol.
For LAN interfaces, set the Ring Number parameter to the correct value for the token ring connected to the interface.
For WAN interfaces, select the WAN call destination that connects the interface to the token ring network.
For information about defining WAN call destinations, refer to Configuring a Permanent PPP Connection in the NetWare Link/PPP documentation.
Press Esc to return to the Internetworking Configuration menu; save your changes when prompted.
If you want these changes to take effect immediately, restart the router.
If you want to configure other parameters, do so now, then restart the router when you are finished.