Using Protocol Stacks

This document offers information and instructions for anyone who needs to create a protocol stack that your router has not already created automatically. It provides an introduction to the manual creation of protocol stacks for inverse multiplexing, WAN Restoral, and device pools and discusses the stack configuration and monitoring commands in detail.

Note: If you do not need to create a protocol stack for inverse multiplexing, WAN Restoral, or device pools, you do not need to read this document. This document includes the following topics.

Overview

Protocol Stacks

Displaying Prompts

Configuring Protocol Stacks

Configuring Devices

Protocol Stack Commands

Overview

 OpenROUTE(TM) not only creates protocol stacks automatically based on the interfaces and data-link protocols that you defined using the add interface and set data-link commands. It also allows you to create protocol stacks manually for inverse multiplexing, WAN Restoral, and device pools and to use these stacks in multiple configurations. This modular approach to configuring your routers provides better control and greater efficiency in updating and managing your network connections and also provides the flexibility to re-arrange devices in order to use them with particular interfaces. It enables you to mix and match your router configurations.

Terminology

The following list defines the terms used for protocol stacks:

Service

 Software capability that OpenROUTE offers. For example, the Point-to-Point Protocol (PPP) and Basic Rate ISDN (BRI).

Protocol Stack

 A set of services, layered one upon the other, that process data packets for Wide Area Network (WAN) devices, such as, high speed serial lines and BRI.

Instance

 Actual concrete instance of services. OpenROUTE allocates instances based on the protocol stack definition that lists the services configured within the stack.

Layer

 OpenROUTE assembles protocol stacks in layers that roughly correspond to layers 1 and 2 of the OSI reference model.

Component

 Instance of a service, device, or reference to other protocol stacks. A layer can contain several components.

Interface

 A logical object over which the router sends or receives packets. The protocol forwarders, such as IP, IPX, and AppleTalk, route packets between interfaces.

Device

 Physical port on the router. OpenROUTE now restricts the term device to the physical ports on the router.

Protocol stacks are created either automatically or manually:

Protocol stacks can include references to other protocol stacks. You need to configure a protocol stack referenced by other protocol stacks just once. Other protocol stacks can then share it. For example, you can create a protocol stack that defines a pool of devices that several other protocol stacks can then share.

Stacking Capabilities by Router Platform

Table 1 defines the stacking capabilities of various GlobeTrotter routers. The table identifies the commands that are available on different routers for manually creating or reconfiguring protocol stacks.

Table 1 Stacking Capabilities of GlobeTrotter Routers

OpenROUTE Command GT 60 Series
GT 70 Series 		GTS 100
GTS 205
GTS 250 		GTAM
Add Device

X

Add Interface X

 X

 X

Add Stack

X

 X

Change Device

X

Change Interface X

 X

 X

Change Stack

X

 X

Clear Device X

 X

 X

Clear Stack X

 X

 X

Delete Device

X

Delete Interface X

 X

 X

Delete Stack

X

 X

Disable Device X

 X

 X

Disable Interface X

 X

 X

Enable Device X

 X

 X

Enable Interface X

 X

 X

List Devices X

 X

 X

List Interfaces X

 X

 X

List Services

X

 X

List Stacks

X

 X

Set Data-Link X

 X

 X

Test Device X

 X

 X

Test Interface X

 X

 X

Protocol Stacks

A protocol stack is a modular layering of components stacked one on top of the other and/or stacked on top of a device. The services within the router are the building blocks used to assemble the protocol stacks.

Service Lists

In its simplest form, a service list is a list of modules strung between an interface at the top of the protocol stack and a device at the bottom of that stack. The service list defines the stack.

Table 2 provides definitions of the service list operators.

Table 2 Service List Operators
Operator Meaning
: (Colon) Represents the linkage between two layers within a protocol stack.

& (Ampersand) Groups multiple components within a layer. Indicates that the items joined by & are both in the same layer on the stack.

() (Parentheses) Enclose the components of the stack for each individual device pool.

Notes:

Naming Conventions

 The service, interface, device, and stack names are case-insensitive. "PPP" is identical to "ppp," and "NET-1" is identical to "net-1" or "Net-1." However, when the router automatically creates a protocol stack, it uses UPPER case for all names in the protocol stack (for example, NET-2). For that reason, OpenROUTE Networks recommends that you use lower case for names when you define a protocol stack. This allows you to visually distinguish your manually created stacks from those that the router creates automatically. (This chapter follows these conventions.)

Note: Every name must be unique. You must not use the same name simultaneously to define a stack, a protocol, an interface, a device, or a service.

Device Names

 Devices are physical ports on your router. Device names are platform-dependent. When your router automatically creates the protocol stack, OpenROUTE assigns device names to all the devices on the router (both LAN and WAN). The names that OpenROUTE assigns are the names that appear on the router's chassis; for example, ETH, WAN1, ISDN.

Note: On a GlobeTrotter Access Manager (GTAM), you can assign names to the devices.

Interface Names

 Interfaces are logical objects that represent a source or destination for data packets routed by the forwarding protocols (IP, IPX, and AppleTalk). When your router automatically creates a protocol stack, OpenROUTE assigns interface names using the following syntax: INTx, where x is the interface number. The protocol forwarders (IP, IPX, and AppleTalk) use the interface number to specify each interface's configuration, such as the interface's address.

Automatic Stack Creation

When you start your router for the first time, OpenROUTE automatically creates protocol stacks according to the device, interface, and data-link protocol configuration. When you restart your router after manually configuring interfaces, OpenROUTE automatically creates additional protocol stacks according to the configuration that you defined for your router.

The router automatically provides two protocol stacks for each of its physical WAN devices. For example,

BASE-1 SL:WAN
NET-1  INT1:PPP:BASE-1
The lower stack [BASE-1] contains the physical device [WAN] and a MAC layer handler [SL] that controls that device. This protocol stack is named BASE-X where X is the interface number. For example,

BASE-1 SL:WAN
The second stack [NET-1] contains the interface [INT1], the data-link layer software module [PPP], and a reference to the BASE-X protocol stack [BASE-1]. For example,

NET-1 INT1:PPP:BASE-1
Having two separate stacks, one referencing the other, provides the flexibility to re-arrange devices to be used with particular interfaces. Separating the stack into upper and lower halves lets each half have its own state. Redefinition of the upper stack does not affect the configuration state of the lower stack.

OpenROUTE creates a BASE stack using the serial line (SL) service for each serial device and a BASE stack using Basic Rate ISDN (BRI) for each BRI ISDN device. If DIAL is enabled and if a serial device has Async or Sync Dial enabled, then its BASE stack contains a DIAL service, the SL service, and the device.

Automatic Stack Names

When the router automatically creates a protocol stack, OpenROUTE assigns one of the following three types of stack names:
Stack Name OpenROUTE creates a stack for...
NET-X Each interface that uses a data-link protocol. For example, if the data-link protocol of interface 1 is PPP (a stackable data-link protocol), OpenROUTE assigns NET-1 as the stack name for interface 1.

BASE-X Every device and names these stacks BASE-X, where X is the number of the first interface linked to the device. For example, if the ISDN device on a GT 205 is interface 3, OpenROUTE assigns BASE-3 as the stack name for this ISDN device.

FRAME-X Frame Relay interfaces. This stack provides the Frame Relay Manager for Frame Relay virtual circuits and Frame Relay LAN Emulation. This is analogous to the mechanism that the BASE stacks that host multiple dial PPP stacks provide. Single or multiple Frame Relay virtual circuits can use the FRAME-X stack, where X is the number of the forst interface attached to the Frame Relay switch.

Commands for Changing Stacks

Table 3 lists the commands that are available for reconfiguring and managing stacks that the router creates automatically. See Protocol Stack Commands.

Table 3 Configuration Commands for Changing Stacks
Command Task Function
Add Interface Configure

 Adds a data-link protocol (for example, PPP or Frame Relay) that OpenROUTE supports over an interface.

Change Interface Configure

 Changes the data-link protocol or the base device associated with an interface that you added using the add interface command. These are the only interfaces that you can change.

Delete Interface Configure

 Deletes interfaces that you added with the add interface command. These are the only interfaces that you can delete.

List Interfaces Configure

 Lists the name of the base device and the interface with its data-link protocol.

Set Data-Link Configure

 Sets the data-link protocol used on an interface.

Manual Stack Creation

Stacks that you create manually supersede stacks that the router creates automatically.

In addition to being able to create a simple protocol stack, you can also manually create protocol stacks to provide the following:

Commands for Creating Protocol Stacks

 Table 4 lists the commands that are available for manually creating protocol stacks. See Protocol Stack Commands.

Table 4 Commands for Creating Protocol Stacks
Command Task Function
Add Stack Configure

 Defines a protocol stack and, in the configuration process, saves it permanently.

Change Stack Configure

 Changes the definition of a protocol stack that you created.

Delete Stack Configure

 Deletes a protocol stack that you created.

List Services Configure/Monitor

 Lists the services that your router uses to build its protocol stacks.

List Stacks Configure/Monitor

 Lists all of the router's protocol stacks.

Note: When you manually create your router's protocol stacks, changes that you make using the Configure (Config>) process take effect when you restart your router.

Configuration ID

 OpenROUTE uses an internal numeric identifier (called the configuration ID) to associate configuration parameters for different protocol stack components with a specific protocol stack. OpenROUTE determines this number in one of two ways based on whether the router created the stack automatically, or you created the stack manually:

In each of these cases, OpenROUTE associates the configuration ID with a protocol stack. What happens when one protocol stack is referenced from within another? In the following example, the BASE-2 stack directly contains the SL module, and the NET-2 stack indirectly contains it. 

NET-2   INT2:PPP:BASE-2
BASE-2  SL:WAN2
Which stack's configuration ID does OpenROUTE use to identify the configuration of SL? The answer is always the directly containing stack's, BASE-2 in this example. This is important because now the SL module within BASE-2 can be configured once, and its configuration still remains constant even when you reference BASE-2 from one protocol stack to another.

Device Configuration

You can configure devices manually on your router if your router is a modular router, that is, a router that has plug-in modules.

Modular routers allow you to add devices to meet your needs. Several commands are available to manage the addition, modification, and removal of these devices. Each physical device that you add to your router has a logical interface that the router creates automatically. If the device is a WAN device, such as a high speed serial line, then the router automatically creates the new device that binds the logical interface to the physical port. By default, the data-link protocol used on the new WAN device is PPP. The router selects the MAC layer based on the type of device installed (SL or HSSI).

OpenROUTE assigns a default name to your device. You can change this name when you add the device using the add device command. OpenROUTE assigns the names based on the device's type, slot number, and next available port number within that slot. Table 5 lists possible default names.

Table 5 Default Device Names
Name Type and Meaning
ETHs-p Ethernet in slot s, port number p.

TKRs-p Token Ring in slot s, port number p.

SLs-p Serial Line in slot s, port number p.

FDDIs FDDI in slot s.

HSSIs HSSI in slot s.

Table 6 defines the commands that you can use to create devices manually.

Table 6 Device Configuration Commands
Command Task Function
Add Device Configure

 Adds a device to your router.

Change Device Configure

 Changes an existing device to a new device referenced by their names.

Delete Device Configure

 Deletes a device that was added to your router using the add device command.

List Devices Configure

 Displays the router's devices by name.

Simple Stack

The stack example in this section shows a simple GlobeTrotter 60 configured to use PPP over a leased line attached to its sole WAN port. OpenROUTE always provides one interface (interface 1) for the WAN port.

If you configure the following:

Config>set data-link ppp 1
OpenROUTE automatically adds the following stacks when you restart your router:

NET-1 INT1:PPP:BASE-1
BASE-1 SL:WAN
You can manually create an equivalent stack:

Config>add stack my-isp int1:ppp:sl:wan
If you manually create a protocol stack, that stack supersedes any stacks that the router creates automatically based on the data-link protocol. Also, any configuration information that you entered for the stack that your router created automatically is lost because OpenROUTE assigns a new identifier (ID) for the stack you created manually.

Figure 1 illustrates both of these protocol stacks.

Figure 1 Simple Protocol Stack

Both stacks contain the same three components (INT1, PPP, and SL). The device that these stacks manage is WAN. The lines connecting these stack components represent the paths taken by data packets as they flow through the protocol stack. The stacks themselves are just logical groupings of software modules.

These stacks contain the same components but they are subtly different because one stack (NET-1) contains a reference to another stack. The inner BASE-1 stack provides a distinct configuration ID for the services it contains (SL in this example). In the other stack (my_isp), the SL module uses the same configuration ID as the other elements of the stack.

Inverse Multiplexing

Inverse multiplexing allows you to aggregate multiple physical devices into a single virtual circuit. OpenROUTE uses Multilink PPP (MP) to distribute data from a virtual circuit to and from multiple physical circuits. The physical circuits can be ISDN B-channels (on those routers that support ISDN), or they can be multiple serial interfaces.

Note: You can enable this capability only by creating protocol stacks manually.

Example 1

 The following is an example of a protocol stack on a GTS 250 that aggregates all four serial ports under one virtual circuit (VC). That VC appears as interface 1 to the protocol forwarders.

Config>add stack
Stack Name? invmux
Stack Service-List? int1:ppp:(sl:wan1)&(sl:wan2)&(sl:wan3)&(sl:wan4)
Figure 2 illustrates this topology.

Figure 2 Inverse Multiplexing Stack -- Example 1

All of the SL instances are within the single protocol stack invmux. They all use the same configuration parameters because OpenROUTE stores just one set of SL parameters with the invmux stack. This means that the following command sequence:

Config> network 1
Circuit Config > sl
SL Config> set speed 2048000
sets the line speed for every SL module to 2048000 bits/second. The sl command that accessed SL Config> does not ask you to specify which SL instance must be configured. It does not matter because all instances share the same configuration information.

Example 2

The following is an example of a two WAN port router (such as, a GTS 100) that uses dialers (DIAL) on each serial line to do Multilink PPP (MP) over dual modems. In this example, you define separate stacks for each physical device because you are using two separate types of modems (Hayes and USR). Because the dialers require different configurations for the two different modems, you must place the dialers in separate stacks:

Congig>add stack hayes dial:sl:wan1
Config>add stack usr dial:sl:wan2
Config>add stack dual_modem_mpp int1:ppp:hayes&usr
Figure 3 illustrates this topology.

Figure 3 Inverse Multiplexing Stack -- Example 2

If you need to configure the DIAL instances under interface 1, use the following commands:

Config> network 1
Circuit Config <dual_modem_mpp> dial
Select one instance of DIAL by specifying the name of the device
to which it is attached. The devices are WAN1, WAN2: ? wan1

Dial Serial Line Configuration
Dial Config <hayes>......
Dial Config <hayes> exit

Circuit Config <dual_modem_mpp> dial
Select one instance of DIAL by specifying the name of the device
to which it is attached. The devices are WAN1, WAN2: ? wan2

Dial Serial Line Configuration
Dial Config <usr>......
The router knows that these two instances of the DIAL service are in separate stacks (hayes and usr) thus the router prompts you to select the DIAL that you must configure.

Example 3

The following is an example of a router (such as a GTS 205) that uses heterogeneous devices under a single Multilink PPP (MP) interface. In this example, you use a dial modem attached to WAN2 together with a BRI interface on the ISDN device:

Figure 4 Inverse Multiplexing Stack -- Example 3

To define this protocol stack, enter the following:

Config>add stack heterogeneous1 int1:ppp:(dial:sl:wan2)&(bri:isdn)
Note:  
You can achieve the same results if you define heterogeneous1 in the following way:
add stack heterogeneous1 int1:ppp:base-2&base-3
if you define base-2 as dial:sl:wan2 and base-3 as bri:isdn.
An important property of OpenROUTE protocol stacks is that multiple devices aggregated by Multilink PPP (MP) are used in the order listed in the protocol stack service-list. In Example 3, the dial modem would be used for the first leg of the Multilink PPP session. By setting the Bandwidth-on-demand parameters in PPP, you can make the router bring up additional links over the Basic Rate ISDN (BRI) connection to add more bandwidth when the serial line to the modem gets full.

Only another OpenROUTE Networks router at the remote site can terminate this type of configuration.

WAN Restoral

The following is an example of a router (such as a GTS 100) that uses heterogeneous devices under a single Multilink PPP (MP) interface. In this example, you use a leased line attached to WAN1 together with a DIAL interface on the WAN2 device:

To define this protocol stack, enter the following:

Config>add stack heterogeneous2 int1:ppp:(sl:wan1)&(dial:sl:wan2)
This stack provides the same capability that earlier versions of OpenROUTE provided under WAN Restoral, but since OpenROUTE now implements this stacking under Multilink PPP (MP), the router can use all the links defined in the stack simultaneously.

When connecting to the remote router, your router uses the leased line first. It only uses the dial circuit when it needs more bandwidth than the leased line has or when the leased line fails. The WAN Restoral capability provides a backup for a serial link in the event of a failure on the leased line. The restoral process involves:

1. Detecting the leased line failure

2. Switching to the dial link

3. Detecting the leased line recovery

4. Switching back to the leased line

You can use a dial circuit configured for either a Serial Interface Dialer (DIAL) or a Basic Rate ISDN (BRI) interface as the dial link.

Notes:

Device Pools

 Another feature of OpenROUTE protocol stacking is its ability to create device pools.

A device pool is a protocol stack that contains a group of devices shared by other protocol stacks. A device pool is very useful for devices attached to dial media because it lets any device in the pool make or accept calls for protocol stacks attached to the device pool. The following example defines a device pool of two modems and three additional protocol stacks that share this device pool:

Config>add stack modem_pool (dial:sl:wan1)&(dial:sl:wan2)
Config>add stack dial-1 int1:ppp:modem_pool
Config>add stack dial-2 int2:ppp:modem_pool
Config>add stack dial-3 int3:ppp:modem_pool
The three dial-x protocol stacks share the two modems equally, on a first-come, first-served basis. The telephone numbers of the two modems can be distributed to all three remote locations, and then those three remote locations can use either one of the modems to connect to the router.

Note: You must configure each of the protocol stacks for dial-on-demand; otherwise, all three stacks try to use the two modems immediately after the router starts.

Figure 5 Modem Device Pool

Figure 5 illustrates the use of the modem_pool stack by all three client stacks (dial-1, dial-2, and dial-3). Since both the dial and sl modules are within the same stack (modem_pool), both dial and both sl modules share a single set of dial and sl configuration parameters.

Displaying Prompts

You configure and monitor stacks from the Config> and + prompts.

To display the Config> prompt, enter the config command at the * prompt.

*config
Config>
To display the + prompt, enter the monitor command at the * prompt.

*monitor
+

Configuring Protocol Stacks

 You can manually configure a protocol stack. To configure a stack manually, do the following:

1. Display the Config> prompt as described in Displaying Prompts.

2. Add a stack. 

Config>add stack
Stack Name?invmux
Stack Service-List?int1:ppp:(sl:wan1)&(sl:wan2)

Configuring Devices

 You can manually configure devices on GlobeTrotter routers that have plug-in modules. To configure a device manually, do the following:

1. Display the Config> prompt as described in Displaying Prompts.

2. Add a device. 

Config>add device hssi
Device Slot # (0-4) [3]?
Device Name [HSSI3]?
Adding device hssi3 as interface 7
Defaulting Data-link protocol to PPP

Protocol Stack Commands

 Table 7 lists those commands that are relevant to configuring and monitoring protocol stacks. Not every command listed in Table 7 is available on every router platform.

Not all parameters apply to all router platforms. Press Space after you type a command to display the available parameters for each command for your router. Enter help for information about using the command line interface.

[C] means the command is available at the Config> prompt.

[M] means the command is available at the + prompt.

Table 7 Protocol Stack Commands

Command Function
Add [C] Adds a device, an interface, or a stack.

Change [C] Changes a device, an interface, or a stack.

Clear [C] Clears a device or stack configuration.

Delete [C] Deletes a device, an interface, or a stack.

Disable [C] [M] Disables a device or an interface.

Enable [C] Enables a device or an interface.

List [C] [M] At the Config> prompt, lists configuration of the devices, interfaces, services, and stacks on the router. At the + prompt, lists device status, interface statistics, available services, and stack definitions.

Set [C] Sets the data-link protocol.

Test [M] Tests (and enables) a device or an interface.

Add [C]

Adds a device, an interface, or a protocol stack.

Syntax: add

device
interface
stack

device device type slot number device name

 Adds a new device to your router. To display a list of the device types that your router supports, enter the add device command and press space twice.

Example: add device quad-serial

Device Slot # (0-4) [2]? 1
Device Name [SL1-2]?
Adding device SL1-2 as interface 7
Defaulting Data-link protocol to PPP
The router must be restarted before the new device can be used.

interface data-link protocol

 Adds an interface to your router.

Since OpenROUTE automatically installs an interface for each physical device, the only type of interface that you can add is one that provides a dial or virtual circuit.

Example: add interface ppp

Select the physical device used to host the interface from the
following list: WAN2, WAN3? wan3
In this example, since two devices had DIAL enabled so that either could be the device used for this logical interface, you have to select the device to host the new interface. If only one device has DIAL enabled, then OpenROUTE does not ask the question because the choice of the base device is unambiguous:

Adding interface 7 linked to base device WAN2-0.

stack stack name stack service-list

 Adds a protocol stack to your router.

Example: add stack

Stack Name? invmux
Stack Service-List? int1:ppp:(sl:wan1)&(sl:wan2)
The protocol stack can refer to interfaces (such as int1 in this example) that do not yet exist. Your router automatically creates these interfaces the next time you restart it.

Notes:

Change [C]

 Changes a device, an interface, or a stack.

Syntax: change

device
interface
stack

device device type old name new slot number new name

 Changes the configuration for an existing device on your router.

Example: change device token-ring

Device Name? Servers
Device Slot # (0-4)  [2]? 3
New Device Name [Servers]? Clients
Changing device Servers to Clients

interface data link interface number base device

 Changes the data-link protocol and/or the base device associated with an interface that you added using the add interface command.

Example: change interface ppp

Interface number [0]? 6
Select the physical device used to host the interface from the
following list: WAN2, WAN3 [WAN2]? wan3
There are two restrictions on the change interface command:

stack

 Changes a protocol stack definition.

Syntax: change stack stack name stack service-list

Example: change stack

Stack Name? invmux
Stack Service List? [[int1:ppp:(sl:wan1)&(sl:wan2)]?int1:ppp:(sl:wan3)&(sl:wan4)
This new definition for protocol stack invmux changes the devices used from wan1 and wan2 to wan3 and wan4.

Notes:

You can use the change stack command only to modify the configuration of a stack that you created manually. OpenROUTE first searches memory for the stack specified by you and modifies any definition found there. If it finds a match, you can modify that stack definition, and OpenROUTE writes that modified stack definition to memory.

Note: This command has no effect on protocol stacks of this name that are already present in the running router. The change only takes effect when you restart your router.

Clear [C]

 Clears configuration information for a device or a stack.

Syntax: clear

device
stack
Example: clear stack

Delete [C]

At the Config> prompt, deletes a device, an interface, or a stack.

Syntax: delete

device
interface
stack

device device name

 Deletes a device. You can delete a physical device that you added to the configuration of a modular router.

Example: delete device

Device Name? clients

interface interface number

 Deletes an interface.

Example: delete interface

Interface number [0]? 5
There are two restrictions on the delete interface command:

stack stack name

 Deletes a protocol stack from the router's memory.

Example: delete stack

Stack Name? invmux
This command has no effect on protocol stacks of this name that are already present in the running router. The deletion does not take effect until you restart the router.

Notes:

Disable [C] [M]

 Disables a device or an interface.

Syntax: disable

device
interface

device device name

 Disables a device.

Example: disable device

Device Name? TKR1-0

interface interface number

 Disables an interface.

Example: disable interface

Interface number [0]? 1

Enable [C]

 Enables a device or an interface.

Syntax: enable

device
interface

device device name

 Enables a device.

Example: enable device

Device Name? TKR1-0

interface interface number

 Enables an interface.

Example: enable interface

Interface number [0]? 1

List [C] [M]

 Lists device, interface, services, and stack configurations and statistics.

List [C]

At the Config> prompt, lists configuration of the devices, interfaces, services, and stacks on the router.

Syntax: list

devices
interfaces
services
stacks

devices

 Displays information on the router's physical devices by name.

Example: list devices

ETH0-0       slot 0  port 0     Ethernet/802.3 
ETH0-1       slot 0  port 1     Ethernet/802.3 
ETH0-2       slot 0  port 2     Ethernet/802.3 
ETH0-3       slot 0  port 3     Ethernet/802.3 
SL1-0        slot 1  port 0     Quad Serial Line 
SL1-1        slot 1  port 1     Quad Serial Line 
SL1-2        slot 1  port 2     Quad Serial Line 
Corporate    slot 1  port 3     Quad Serial Line 


Note:  
Most of these device names are the default names that the router generated.  The only name that you provided is Corporate.

interfaces

 Lists all of the interfaces configured on the router, even those that you have disabled. The listing shows the name of the base device used with each interface. It also shows those interfaces that have a Dialer or Frame Relay LAN Emulation enabled.

Example: list interfaces

Ifc   0, Ethernet/IEEE 802.3 (via device ETH0-0)
        (5 Receive Buffers)
Ifc   1, Token-Ring/802.5 (via device TKR1-0)
        (10 Receive Buffers)
Ifc   2, Token-Ring/802.5 (via device TKR1-1)
Ifc   3, Point to Point (via device WAN2-0, with Dialer)
Ifc   4, Frame Relay (via device WAN2-1, with LAN Emulation)
Ifc   5, Point to Point (via device WAN2-2)
Ifc   6, Point to Point (via device WAN2-3)
Ifc   7, Point to Point (via device WAN2-0)

services

 Lists the stackable WAN services enabled on the router.

Example: list services

Service         Description
-------         -----------
DIAL            Dial Serial Interface
FRLANE          Frame Relay LAN Emulation
FRMGR           Frame Relay Manager
FRVC            Frame Relay Virtual Circuit
HSSI            High-Speed Serial Interface
INT3            Interface 3
INT4            Interface 4
PPP             Point-to-Point Protocol
SL              Serial Line

stacks

 Displays all of the protocol stacks in the router, whether created manually or automatically.

Example: list stacks

Stack           Creator  State    ID  Service List
-----           -------  -----    --  ------------
BASE-3          Router   Closed    3  SL:SL2-0
FRAME-3         Router   Closed    3  FRMGR:BASE-3
invmux          User     Closed  128  int1:ppp:(sl:wan1)&(sl:wan2)
NET-3           Router   Closed    3  INT3:FRVC:FRAME-3
NET-4           Router   Closed    4  INT4:PPP:BASE-3
Stack

 Stack name.

Creator

 Indicates who defined each protocol stack: the router or the user.

State

 Open or closed. In the Config> listing, the state is always closed. Only in the + listing does the state display as either open or closed. Open Available to accept calls (on dial-oriented WANs such as ISDN), and, if a call is in progress, an open stack can transfer data packets. Closed Equivalent to a disabled interface. It cannot transfer data packets.
ID

 Configuration ID. See Configuration ID on page 10.

Service List

 Services used by a protocol stack.

List [M]

At the + prompt, lists device status, interface statistics, available services, and stack definitions.

Syntax: list

device
interface
services
stacks

device

 Lists information on the status of each device.

Example: list device

Device        Hardware           CSR      Vector   State
ETH0-0        Ethernet/802.3     80700000 0        Up
TKR1-0        ProNET-4           80710000 1        Not present
TKR1-1        ProNET-4           80710000 1        Disabled
SL2-0         Quad Serial Line   80720000 2        Up
SLOT3-0       None               80730000 3        Not present
wan5          High Speed Serial  80730000 3        Up

interface

 Lists information on the status of each interface, or, if you enter a particular interface's number, lists a detailed description of the interface's state.

Example: list interface

                 Self-Test  Self-Test   Maintenance
 Nt   Interface    Passed     Failed       Failed
 0      Eth/0        1          0            0
 1      NULL/0       0          0            0
 2      TKR/0        0          0            0
 3      FR/0         0          0            0
 4      NULL/2       0          0            0
 5      NULL/3       0          0            0
 6      FDDI/0       0          0            0
Example: list interface 2

                 Self-Test  Self-Test   Maintenance
 Nt   Interface    Passed     Failed       Failed
 2      TKR/1        0          1119         0

 Token-Ring/802.5 data-link layer on ProNET-4/16 interface

  Physical address        000000000000
  Network speed           4 Mbps
  Max packet size (INFO)  2052
  Handler state           Testing
  Interface Restarts         0

  # times Signal lost        0    # times Beaconing          0
  Hard errors                0    Lobe wire faults           0
  Auto-removal errors        0    Removes received           0
  Ring recovery actions      0

  Line errors                0    Burst errors               0
  ARI/FCI errors             0    Inputs dropped             0
  Frame copy errors          0    Token errors               0
  Lost frames                0
  Input overflows            0    Driver output errors       0
  Dest refused               0

  Input Buffers Low/Zero     0/    0

services

 Lists each service available on your router with a brief description of each.

Example: list services

Service         Description
-------         -----------
DIAL            Dial Serial Interface
FRLANE          Frame Relay LAN Emulation
FRMGR           Frame Relay Manager
FRVC            Frame Relay Virtual Circuit
HSSI            High-Speed Serial Interface
INT1            Interface 1
INT3            Interface 3
INT4            Interface 4
PPP             Point-to-Point Protocol
SL              Serial Line

stacks

 Lists information on each stack configured for your router and the state of each.

Note: Only in the + listing does the State display as either Open or Closed. Example: list stacks

Stack      Creator  State    ID  Service List
-----      -------  -----    --  ------------
BASE-3     Router   Open      3  SL:SL2-0
FRAME-3    Router   Open      3  FRMGR:BASE-3
invmux     User     Closed  128  int1:ppp:(sl:wan1)&(sl:wan2)
NET-3      Router   Open      3  INT3:FRVC:FRAME-3
NET-4      Router   Closed    4  INT4:PPP:BASE-3

Set [C]

 Sets the data-link protocol (layer 2) used by a router's interface.

Syntax: set

data-link data-link protocol
Example: set data-link ppp

Note: Interface Number [0]? 1
Note: OpenROUTE does not accept the set data-link command if a manually created (that is, user-defined) protocol stack references the specified interface. The manually created protocol stack definition takes precedence over the data-link protocol.

Test [M]

 Tests devices and interfaces.

Syntax: test

device
interface
Example: test device

Name of the device? wan
Testing device WAN...successful
Example: test interface

Interface number [0]? 3

Testing network 3 PPP/0...successful


docs@openroute.com
Copyright © 1998, OpenROUTE Networks, Inc. All rights reserved.