[Top] [Table Of Contents] [Prev] [Next] [Index]

Using ISDN BRI        12

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."

This chapter discusses the following topics:

Overview of ISDN BRI Connections

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

Provisioning

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.

Configuring ISDN

This section describes the commands that you need to configure a PortMaster for ISDN BRI service.

ISDN BRI Switch Types

The North American ISDN U interface and international S/T interface require different switch type settings on your PortMaster.

North American ISDN BRI Switch Types

The ISDN switch type for North American ISDN connections (U interface) can be set to one of four values, shown in Table 12-1.  
North American ISDN BRI Switch Types

ISDN Switch Type

Used for

ni-1

National ISDN-1 (NI-1) (default)

dms100

Northern Telecom DMS 100 Custom

5ess

AT&T 5ESS Custom Multipoint

5ess-ptp

AT&T 5ESS Custom Point-to-Point

International ISDN BRI Switch Types

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.  
International ISDN BRI Switch Types

ISDN Switch Type

Used for

net3

EuroISDN standard (includes Swiss standards)

vn4

France-current national switch type

1tr6

Germany-older switch type

ntt

Japan

kdd

Japan

Setting the Switch Type

To set the ISDN switch type for an ISDN BRI U interface, use the following commands:

Command> set isdn-switch ni-1|dms-100|5ess|5ess-ptp
Command> reboot

To set the ISDN switch type for an ISDN BRI S/T interface, use the following commands:

Command> set isdn-switch net3|vn4|1tr6|ntt|kdd
Command> reboot

Note ¯ You must reboot the PortMaster after changing the switch type for the change to take effect.

Service Profile Identifier (SPID) for ISDN BRI

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 and save the configuration to nonvolatile RAM, use the following commands:

Command> set S0 spid Number
Command> save all

The set debug isdn on command shows any invalid SPIDs.

Terminal Identifier (TID) for ISDN BRI

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.

Directory Number

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.

Command> set S0 dn Number
Command> set S0 directory Number

Enter the following command to save the configuration to Flash:

Command> save all

Information Elements (IEs)

"Number plan" and "number type" are values that relate to attributes associated with the called and calling party information elements (IEs) used to exchange phone numbers within a setup message in ISDN. These values can vary among countries and telephone companies.

You can configure the PortMaster to autodetect number plan and number type settings on incoming calls and, if necessary, automatically modify the PortMaster configuration. If the PortMaster detects a difference between the current settings and those of an incoming call, it sends the following console message indicating that the values are different and have been changed:

Call recvcd numberplans do not match (n:n)

The first n refers to the new number type and the second n refers to the new number plan setting. Use the save all command to save modified settings to nonvolatile RAM.

To turn on autodetection of IEs, enter the following command:

Command> set isdn-numberauto on

Note ¯ numberauto is off by default.

 

Setting the Number Type

To change the number type from the default manufacturer setting (so that you can, for example, begin successfully to place outbound calls), use the following command:

Command> set isdn-numbertype 0|1|2|4

The new setting becomes effective immediately; it does not need to be saved to nonvolatile RAM.

Enter this command without a number type value to display a list of all plan values available, and the current setting.

Setting the Number Plan

To change the number plan from the default manufacturer setting (so that you can, for example, begin successfully to place outbound calls), use the following command:

Command> set isdn-numberplan 0|1|2|7|8

The new setting becomes effective immediately; it does not need to be saved to nonvolatile RAM.

Enter this command without a number plan value to display a list of all plan values available, and the current setting.

Multilink PPP

Multilink PPP V.120 is supported on analog and ISDN interfaces. 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 1717 or using Lucent's multiline load balancing.

To enable Multilink PPP, use the following command:

Command> set location Locname multilink on

Multiple Subscriber Network for an S/T Interface

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, enter the following command:

Command> set isdn-msn on

Port Limits

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 the PortMaster's 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:

Command> set user Username maxports Number

Data over Voice

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:

Command> set location Locname voice on|off

ISDN Port Configuration Tips

Use the following tips to help you configure your ISDN BRI port:

ISDN BRI Unnumbered IP Configuration Example

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.

Configuration Steps

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:

  1. 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.

  2. Configure the following settings for the PortMaster in Denver:

a. Configure global settings (page 12-11).

b. Configure Ethernet interface settings (page 12-12).

c. Configure ISDN port settings (page 12-12).

d. Configure dial-in users (page 12-13).

e. Configure dial-out locations (page 12-14).
  1. Configure the following settings for the PortMaster in San Francisco:

a. Configure global settings (page 12-16).

b. Configure Ethernet interface settings (page 12-16).

c. Configure ISDN port settings (page 12-17).

d. Configure dial-in users (page 12-18).

e. Configure dial-out locations (page 12-19).
  1. Test the configuration (page 12-20).

  2. Troubleshoot the configuration (page 12-21).

     Figure 12-2 illustrates the ISDN BRI example in this section using unnumbered interfaces.

  ISDN BRI Unnumbered For comparison, Figure 12-3 shows a similar configuration using ISDN BRI with numbered interfaces.

  ISDN BRI Numbered

Configuring the PortMaster in Denver

The PortMaster in Denver is being configured for an ISDN dial-up connection to the PortMaster in San Francisco.

Configuring Global Settings

Configure the global settings on the PortMaster in Denver to the values shown in Table 12-3.  
Global Values

Setting

Command

IP gateway

set gateway 192.168.1.1

System name

set sysname denver

ISDN switch

set isdn_switch ni-1

After you configure the global settings shown in Table 12-3, enter the following command to save the configuration:

Command> save all

For more information about global settings, refer to Chapter 3, "Configuring Global Settings."

Configuring Ethernet IP Interface Settings

Configure the following Ethernet interface settings to the values shown in Table 12-4.  
Ethernet Values

Setting

Command

Protocol

set ether0 ipx enable

IP address

set ether0 address 192.168.200.1

Netmask

set ether0 netmask 255.255.255.0

IPX network

set ether0 ipxnet F1

IPX frame type

set ether0 ipxframe ethernet_802.2

Broadcast address

set ether0 broadcast high

RIP routing

set ether0 rip on

After you configure the Ethernet interface as shown in Table 12-4, enter the following command to save the configuration:

Command> save all

For more information on Ethernet settings, refer to Chapter 4, "Configuring the Ethernet Interface."

Configuring ISDN Port Settings

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

Setting Command
Port type S1

set s1 network twoway

Port type S2

set s2 network twoway

Dial group S1

set s1 group 2

Dial group S2

set s2 group 2

Directory number S1

set s1 directory number 5551111

Directory number S2

set s2 directory number 7005551112

SPID S1

set s1 spid 700555111100

SPID S2

set s2 spid 700555111201

ISDN Port Values All the other parameters should be left at their default values.

After you configure the ISDN BRI port as shown in Table 12-5, enter the following commands to reset the ports and save the configuration:

Command> reset s1
Command> reset s2
Command> save all

For more information about synchronous ports, refer to Chapter 6, "Configuring a Synchronous WAN Port."

Configuring a Dial-In User

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.  
User Table Values

Setting

Command

Username

add netuser sf

Password

set user sf password anypasswd

Protocol

set user sf protocol ppp

User IP address

set user sf address 192.168.100.1

Netmask

set user sf netmask 255.255.255.0

IPX network

set user sf ipxnet F3

RIP routing

set user sf rip on

MTU

set user sf mtu 1500

Compression

set user sf compression on

After you configure the user table as shown in Table 12-6, enter the following command to save the configuration:

Command> save all

For more information about configuring user table parameters, refer to Chapter 7, "Configuring Dial-In Users."

Configuring a Dial-Out Location

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.  
Location Table Values

Setting

Command

Location name

add location sf

Type

set location sf manual

(Set the location for manual dialing until after the configuration has been tested. Once the configuration is verified, change the connection type to on-demand.)

Protocol

set location sf protocol ppp

IP destination

set location sf destination 192.168.100.1

Netmask

set location sf netmask 255.255.255.0

IPX network

set location sf ipxnet F3

RIP routing

set location sf rip on

MTU

set location sf mtu 1500

Idle timer

set location sf idle 2

Dial group

set location sf group 2

Username

set location sf username sf

Telephone number

set location sf telephone 5551212

Password

set location sf password anypasswd

High-water mark

set location sf high_water 0

Maximum ports

set location sf maxports 1

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.

After you configure location table settings as shown in Table 12-7, enter the following command to save the configuration:

Command> save all

For more information about configuring location table parameters, refer to Chapter 8, "Configuring Dial-Out Connections."

Configuring the PortMaster in San Francisco

The PortMaster in San Francisco is being configured for an ISDN dial-up connection to the PortMaster in Denver.

Configuring Global Settings

Configure the global settings to the values shown in Table 12-8.  
Global Values

Setting

Command

IP gateway

set gateway 192.168.1.2

(This is the address of the next upstream router.)

Default routing

set default off

System name

set sysname sf

ISDN switch

set isdn_switch ni-1

After you configure the global settings shown in Table 12-8, enter the following command to save the configuration:

Command> save all

For more information about global settings, refer to Chapter 3, "Configuring Global Settings."

Configuring Ethernet Interface Settings

Configure the Ethernet settings to the values shown in Table 12-9.  
Ethernet Value

Setting

Command

Protocol

set ether0 ipx enable

IP address

set ether0 address 192.168.100.1

Netmask

set ether0 netmask 255.255.255.0

IPX network

set ether0 ipxnet F2

IPX frame type

set ether0 ipxframe ethernet_802.2

Broadcast address

set ether0 broadcast high

RIP routing

set ether0 rip on

After you configure the Ethernet interface as shown in Table 12-9, enter the following command to save the configuration:

Command> save all

For more information on Ethernet settings, refer to Chapter 4, "Configuring the Ethernet Interface."

Configuring ISDN Port Settings

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.  
ISDN Port Values

Setting

Command

Port type S1

set s1 network twoway

Port type S2

set s2 network twoway

Dial group S1

set s1 group 2

Dial group S2

set s2 group 2

set directory number S1

set s1 directory number 5552222

set directory number S2

set s2 directory number 5552223

SPID S1

set s1 spid 700555222200

SPID S2

set s2 spid 7005552222301

All the other settings should be left at their default values.

After you configure the synchronous WAN port as shown in Table 12-10, enter the following commands to reset the ports and save the configuration:

Command> reset s1
Command> reset s2
Command> save all

For more information about synchronous ports, refer to Chapter 6, "Configuring a Synchronous WAN Port."

Configuring a Dial-In User

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.  
User Table Values

Setting

Command

Username

add netuser denver

Password

set user denver password anypasswd

Protocol

set user denver protocol ppp

User IP address

set user denver address 192.168.200.1

Netmask

set user denver netmask 255.255.255.0

IPX network

set user denver ipxnet F3

RIP routing

set user denver rip on

MTU

set user denver mtu 1500

Compression

set user denver compression on

After you configure the user table as shown in Table 12-11, enter the following command to save the configuration:

Command> save all

For more information about configuring user table parameters, refer to Chapter 7, "Configuring Dial-In Users."

Configuring a Dial-Out Location

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.  
Location Table Values

Setting

Command

Location name

add location denver

Type

set location denver manual

(Set the location for manual dialing until after the configuration has been tested. Once the configuration is verified, change the connection type to on-demand.)

Protocol

set location denver ppp

IP destination

set location denver destination 192.168.200.1

Netmask

set location denver netmask 255.255.255.0

IPX network

set location denver ipxnet F3

RIP routing

set location denver rip on

MTU

set location denver mtu 1500

Idle timer

set location denver idle 2

Dial group

set location denver group 2

Username

set location denver username sf

Telephone number

set location denver telephone 5551212

Password

set location denver password anypasswd

High-water mark

set location denver high_water 0

Maximum ports

set location denver maxports 1

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.

After you configure location table settings as shown in Table 12-12, enter the following command to save the configuration:

Command> save all

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.

Testing the Setup

You should test the configuration before setting either of the locations for on-demand dialing. To test the configuration, follow these steps:

  1. Enter the following commands on the PortMaster in Denver to connect from location denver to location sf:

    Command> set console s1
    Command> set debug 0x51
    Command> set debug isdn on
    Command> dial sf

  2. Monitor the dial-and-connect sequence between the two locations.

  3. If everything connects as expected, do the following:

a. Turn off debugging on the console. Command> set debug isdn off
Command> reset console


b. Reset the port on the Office Router in Denver and change the location type of location sf to on-demand. Command> reset s1
Command> set location sf on_demand
  1. 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.
  1. Repeat Steps 1 through 4, dialing from San Francisco to Denver.

Troubleshooting an ISDN BRI Connection

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, enter the following commands:

Command> set console s1
Command> set debug isdn on

To turn off debugging, enter the following commands:

Command> set debug isdn off
Command> reset console

If you are having trouble with an ISDN connection, verify the following:

Interpreting ISDN BRI Port Status

 Table 12-13 describes how to interpret the output of the show S10 command for ISDN BRI ports.  
ISDN BRI Port Status

Port Status

Modem Status

Description

NO-SERVICE

DCD- CTS- TELCO- NT1-

No SPID is set.

NO-SERVICE

DCD- CTS- TELCO- NT1+

Port has either no cable or no circuit connecting it to the telephone company.

NO-SERVICE

DCD- CTS+ TELCO+ NT1+

Cable and ISDN circuit are functioning, but the SPID is not registered.

IDLE

DCD- CTS+ TELCO+ NT1+

SPID is registered and ready to use

ESTABLISHED

DCD- CTS+ TELCO+ NT1+

Port is connecting or providing device service, but no carrier is sensed.

ESTABLISHED

DCD+ CTS+ TELCO+ NT1+

Port is connected.

ESTABLISHED

DCD+ CTS- TELCO+ NT1+

Port is connected with a V.120 asynchronous connection, but the other end of the connection is providing flow control information.


[Top] [Table Of Contents] [Prev] [Next] [Index]

spider@livingston.com
Copyright © 1998, Lucent Technologies. All rights reserved.