[Top] [Prev] [Next] [Bottom]
This chapter describes how to configure the PortMaster to connect two local area networks (LANs) via ISDN using V.25bis dialing on a Basic Rate Interface (BRI) with an integrated network termination device (NT1). This chapter also provides an example to demonstrate this type of configuration.
For information on the PortMaster 3 and ISDN PRI service, see Chapter 11, "Configuring the PortMaster 3."
The following topics are discussed:
ISDN is most commonly used to provide low-cost connectivity between sites that cannot justify the cost of a dedicated high-speed leased line. However, ISDN connections provide more bandwidth than asynchronous dial-up connections can, as well as quicker call completion-approximately 1 second instead of 45 seconds.
PortMaster products support manual dial-on-demand and automatic ISDN connections using the BRI port and the PPP protocol. BRI supports two 64Kbps B channels for data and one 16Kbps D channel for signaling. ISDN ports are available as either a U or S/T interface.
ISDN ports are easier to configure than asynchronous or synchronous ports. Because the ISDN U interface has the NT1 device integrated in the port, no modem, CSU/DSU, or external terminal adapter is required.
For the ISDN S/T interface, a PortMaster requires an external terminal adapter to connect from the PortMaster synchronous port to the ISDN link. For terminal adapters that do not have automatic dialing or for administrators who want to manually connect with the terminal adapter, the PortMaster supports automatic location table scripting. For more information, see Chapter 8, "Configuring Dial-Out Connections." For more information about configuring the PortMaster for ISDN with an external terminal adapter and automatic location table scripting, refer to Chapter 14, "Using Synchronous V.25bis Connections."
ISDN BRI ports can provide the same services that an asynchronous port provides, except for direct network hardwired connections. The PortMaster automatically detects whether the port is providing asynchronous or synchronous, 56Kbps or 64Kbps.
ISDN BRI connections can be initiated as needed, or they can remain active continuously. A dial-out location must be specified in the location table for dial-out connections, and a dial-in user must be specified in the user table or RADIUS for
dial-in connections. Figure 12-1 shows an example of an ISDN connection.
You can use PAP and CHAP for dial-in and dial-out authentication.
Contact your service provider for specific information about your ISDN switch type and service profile identifier (SPID).
The following ISDN-specific settings need to be configured for each ISDN BRI port on the PortMaster to permit ISDN service:
Example of an ISDN Connection
To help you determine the kind of provisioning you require for your ISDN setup, refer to the information in the hardware installation guide and on the Lucent Remote Access website at http://www.livingston.com.
This section describes the commands that you need to configure a PortMaster for ISDN BRI service.
The North American ISDN U interface and international S/T interface require different switch type settings on your PortMaster.
The ISDN switch type for North American ISDN connections (U interface) can be set to one of four values, shown in Table 12-1.
The PortMaster ISDN S/T interface for use in Japan, Europe, and other countries using international ISDN standards uses a different set of switch type settings, shown in Table 12-2.
To set the ISDN switch type for an ISDN BRI U interface, use the following commands:
To set the ISDN switch type for an ISDN BRI S/T interface, use the following commands:
Note ¯ 
You must reboot the PortMaster after changing the switch type for the change to take effect.
The service profile identifier (SPID) is a unique number assigned by the telephone company that identifies your ISDN equipment to the telephone company's switch. SPIDs are used with BRI ports only, and only in the United States. A SPID can have up to 20 digits. If you are connecting to a 5ESS point-to-point switch, a SPID is not required.
To set the SPID, use the following command:
The set debug isdn on command shows any invalid SPIDs.
The terminal identifier (TID) is a numeric value used by some telephone switches for additional identification. Some telephone companies require the SPID, while others require a TID, as well. When configuring the PortMaster, append the TID to the SPID if required by your carrier.
The optional directory number is a 10-digit phone number provided by the telephone company. If it is set, an incoming call must match this number to determine which port the call should be taken on.
Use either of the following commands to set the directory number.
Multilink PPP V.120 is supported on ISDN interfaces only. The PortMaster accepts and detects both multiline load balancing and Multilink PPP connections. Multiple lines can be used to increase bandwidth, either using Multilink PPP as defined in RFC 1990 or using Lucent Remote Access' multiline load balancing.
To enable Multilink PPP, use the following command:
For countries that support BRI via the S/T bus interface, you can enable the multiple subscriber network (MSN) feature. When enabled, this feature allows multiple ISDN devices attached to the same BRI line to receive calls not intended for the PortMaster.
When the MSN feature is disabled, the PortMaster rejects the call if a port is not available. In this case other S/T connected devices are not given an opportunity to check or accept the call. This is the default.
To enable the MSN for an ISDN S/T interface, use the following command:
You can set port limits on a per-user basis for Multilink V.120, Multilink PPP, and asynchronous multiline load balancing users. If a port limit is set, the user is limited to that number of ports on the PortMaster. If the number of dial-in ports is left unconfigured, port limits are not imposed and Lucent Remote Access' multiline load balancing, Multilink V. 120, and Multilink PPP sessions are allowed. You can also configure this setting using the RADIUS Port-Limit attribute.
To set port limits, use the following command:
Data over voice is supported for inbound and outbound ISDN connections. The PortMaster accepts inbound voice calls and treats them as data calls.
To force a data-over-voice call for an outbound ISDN connection, use the following command:
Use the following tips to help you configure your ISDN BRI port:
This example illustrates how to connect a PortMaster located in one office (Denver) with a PortMaster located in another office (San Francisco) using an on-demand ISDN connection.
To install your PortMaster, follow the instructions in the hardware installation guide. If you need additional help, refer to the troubleshooting chapter of the guide. The example in this chapter shows variables in italics. Change these values to reflect your network.
Once you have assigned an IP address to the PortMaster, continue with the following steps:
-
Use a cable with RJ-45 connectors to connect the BRI port to the ISDN telephone line.
Caution ¯ 
Do not plug an analog telephone line into the PortMaster BRI port. The PortMaster could be damaged.
-
Configure the following settings for the PortMaster in Denver:
a. Configure global settings (page 12-9).
b. Configure Ethernet interface settings (page 12-10).
c. Configure ISDN port settings (page 12-10).
d. Configure dial-in users (page 12-11)
e. Configure dial-out locations (page 12-12)
-
Configure the following settings for the PortMaster in San Francisco:
a. Configure global settings (page 12-14).
b. Configure Ethernet interface settings (page 12-14).
c. Configure ISDN port settings (page 12-15).
d. Configure dial-in users (page 12-16).
e. Configure dial-out locations (page 12-17).
-
Test the configuration (page 12-18).
-
Troubleshoot the configuration (page 12-19).
The PortMaster in Denver is being configured for an ISDN dial-up connection to the PortMaster in San Francisco.
Configure the global settings on the PortMaster in Denver to the values shown in Table 12-3.
Once you have configured the global settings shown in Table 12-3, save the configuration by using the following command:
For more information about global settings, refer to Chapter 3, "Configuring Global Settings."
Configure the following Ethernet interface settings to the values shown in Table 12-4.
Once you have configured the Ethernet interface as shown in Table 12-4, save the configuration using the following command:
For more information on Ethernet settings, refer to Chapter 4, "Configuring the Ethernet Interface."
Configure the ISDN port with the values shown in Table 12-5 for the example in this chapter. This example assumes that the BRI used is port S1-S2 on a PortMaster ISDN Office Router (OR-U). If your application uses ports S10 through S29 on a PortMaster 2E, adjust these values accordingly.
All the other parameters should be left at their default values. Once you have configured the ISDN BRI port as shown in Table 12-5, reset the ports and save the configuration using the following commands:
For more information about synchronous ports, refer to Chapter 6, "Configuring a Synchronous WAN Port."
A user account must be set up on the PortMaster router in Denver so that PortMaster in San Francisco can dial in when traffic is queued. The new user sf should be configured with the values shown in Table 12-6.
Once you have configured the user table as shown in Table 12-6, save the configuration using the following command:
For more information about configuring user table parameters, refer to Chapter 7, "Configuring Dial-In Users."
A location entry on the PortMaster in Denver must be created for the location identified as sf. This allows the PortMaster router in Denver to call the PortMaster in San Francisco when network traffic is queued. The new location sf should be configured with the values shown in Table 12-7.
Note ¯ 
Configuring the maximum ports setting to a value higher than 0 causes the PortMaster to dial out to a continuous location, or become available for dial-out to an on-demand location. By configuring the maximum ports setting last, you ensure that the PortMaster will not attempt to make a connection with a location until you have configured all the settings for that location.
Once you have configured location table settings as shown in Table 12-7, save the configuration using the following command:
For more information about configuring Location Table parameters, refer to Chapter 8, "Configuring Dial-Out Connections."
The PortMaster in San Francisco is being configured for an ISDN dial-up connection to the PortMaster in Denver.
Configure the global settings to the values shown in Table 12-8.
Once you have configured the global settings shown in Table 12-8, save the configuration by using the following command:
For more information about global settings, refer to Chapter 3, "Configuring Global Settings."
Configure the Ethernet settings to the values shown in Table 12-9.
Once you have configured the Ethernet interface as shown in Table 12-9, save the configuration using the following commands:
For more information on Ethernet settings, refer to Chapter 4, "Configuring the Ethernet Interface."
Configure the ISDN port with the values shown in Table 12-10 for the example in this chapter. This example assumes that the BRI used is port S1-S2 on a PortMaster ISDN Office Router (OR-U). If your application uses ports S10 through S29 on a PortMaster 2E, adjust these values accordingly.
All the other settings should be left at their default values. Once you have configured the synchronous WAN port as shown in Table 12-10, reset the ports and save the configuration using the following commands:
For more information about synchronous ports, refer to Chapter 6, "Configuring a Synchronous WAN Port."
A user account must be set up on the PortMaster router in San Francisco so that PortMaster in Denver can dial in when traffic is queued. The new user denver should be configured with the values shown in Table 12-11.
Once you have configured the user table as shown in Table 12-11, save the configuration using the following command:
For more information about configuring user table parameters, refer to Chapter 7, "Configuring Dial-In Users."
A location entry on the PortMaster in San Francisco must be created for the location identified as denver. This allows the PortMaster router in San Francisco to call the PortMaster in Denver when network traffic is queued. The new location denver should be configured with the values shown in Table 12-12.
Note ¯ 
Configuring the maximum ports setting to a value higher than 0 causes the PortMaster to dial out to a continuous location, or become available for dial-out to an on-demand location. By configuring the maximum ports setting last, you ensure that the PortMaster will not attempt to make a connection with a location until you have configured all the settings for that location.
Once you have configured location table settings as shown in Table 12-12, save the configuration using the following command:
For more information about configuring location table parameters, refer to Chapter 8, "Configuring Dial-Out Connections."
Use the dialer to connect between the two offices as instructed in the next section. Once everything is working properly, you can change the location type from manual to on-demand on both routers and reset the ports.
You should test the configuration before setting either of the locations for on-demand dialing. To test the configuration, follow these steps:
-
Enter the following commands on the PortMaster in Denver to connect from location denver to location sf:
-
Monitor the dial-and-connect sequence between the two locations.
-
If everything connects as expected, do the following:
a. Turn off debugging on the console:
b. Reset the port on the Office Router in Denver and change the location type of location sf to on-demand:
-
If you notice a problem, do the following:
a. Reset the port on the PortMaster in Denver.
b. Change the settings you think are causing the problem.
c. Dial San Francisco again.
d. Repeat this procedure until the connection is made correctly.
-
Repeat Steps 1 through 4, dialing from San Francisco to Denver.
Most ISDN configurations come up with little trouble if you have configured the PortMaster using information from your telephone company. However, if you are having problems, use the information in this section to try to debug your configuration.
To display ISDN debug information on the console, use the following commands:
To turn off debugging, use the following commands:
If you are having trouble with an ISDN connection, verify the following:
Table 12-13 describes how to interpret the output of the show S10 command for ISDN BRI ports.
[Top] [Prev] [Next] [Bottom]
spider@livingston.com
Copyright © 1998, Livingston Enterprises, Inc. All rights
reserved.