Non-Persistent Connections Manager User Guide

Transcription

1 Titlepage Non-Persistent Connections Manager User Guide Document Network Management

2 Copyright Notice Document Copyright July 2002 by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ( Aprisma ) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. Non-Persistent Connections Manager User s Guide Page 1

3 Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III(g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virusfree. Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100 percent effective, we strongly recommend that you write-protect the licensed software and verify (with an antivirus system in which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc. 273 Corporate Drive Portsmouth, NH Phone: U.S. toll-free: Web site: Non-Persistent Connections Manager User s Guide Page 2

4 Contents Introduction 4 Creating Dialup_Link Models 5 Types of Links Supported...5 Dial Backup Link (DBL)...5 Bandwidth on Demand Link (BODL)...5 Primary on Demand Link (PODL)...6 Model Creation...6 Configuring A Non-Persistent Connection 9 Dial Backup Links and Bandwidth on Demand Links...10 Primary on Demand Links...10 Configuring Secondary Interfaces on the Remote Router...10 Configuring Primary Interfaces on the Remote Router...11 Configuring Secondary Interfaces on the Host Router...13 Viewing the Dialup_Link in the Topology View...14 Advanced Configurations 15 Multilink Secondary Interfaces on a Remote Router...15 Multiple Dial Backup Links (MDBLs)...18 Multiple Remote Routers to a Common Host Router...19 Single Remote Router to Multiple Host Routers or Host Router Interfaces...21 Monitoring Non-Persistent Connections 23 Dialup_Link Information View...24 The Active NPC Summary View...25 Dialup_Link Condition Color...26 Alarms...27 Index 29 Non-Persistent Connections User s Guide Page 3

5 Introduction This section provides an overview of SPECTRUM s Non-Persistent Connections Manager and describes the types of links it allows you to manage. SPECTRUM s Non-Persistent Connections Manager allows you to manage transient communications links. These non-persistent connections generally remain in an inactive state and are activated only under certain conditions. They can be activated manually as needed to serve as normal dialup type communications links, or they can be configured to activate automatically in either of the following two scenarios: To serve as a backup when failure of a primary connection occurs. To provide load balancing or extra bandwidth for another overloaded communications link. The Non-Persistent Connections Manager gives you quick access to three key pieces of information, namely: When a link is activated. Whether a link has failed to activate. How long a particular link has been active. Events and alarm conditions are generated and logged to maintain accurate link usage statistics. There is also a graphical representation (icon) of the link so that you can differentiate between normal connections and non-persistent connections and determine a connection s current status by merely looking at it. The Dialup_Link model type provides this important functionality. The following chapters discuss how to create Dialup_Link models to represent non-persistent connections, how to configure these models, and how to monitor them for information about the non-persistent connection. Non-Persistent Connections Manager User s Guide Page 4

6 Creating Dialup_Link Models This section explains how to create a Dialup_Link model to represent a non-persistent connection. Types of Links Supported The Dialup_Link model type provides functionality for three distinct types of non-persistent connections: Dial Backup Link (DBL) Bandwidth on Demand Link (BODL) Primary on Demand Link (PODL) When you create a Dialup_Link model, you will choose the type of connection that best suits your needs. Dial Backup Link (DBL) A Dial Backup Link (DBL) provides a redundant link if a primary link fails. Not only does this type of link provide monitoring support for a oneto-one relationship between primary and secondary links, it also provides support for multiple primary and secondary link configurations. Each DBL model can provide monitoring capabilities for multiple primary links using a common secondary interface. This feature is useful when many remote sites use one phone number at a central site (common interface) to support a non-persistent connection. Bandwidth on Demand Link (BODL) A Bandwidth on Demand Link (BODL) provides extra bandwidth for connections experiencing congestion problems. Links of this type may or may not be active in conjunction with the primary link. BODLs provide the same redundant capabilities as Dial Backup Links. Non-Persistent Connections Manager User s Guide Page 5

7 Creating Dialup_Link Models Primary on Demand Link (PODL) Model Creation The Primary on Demand Link (PODL) is not a redundant connection of any type. These links are activated manually when needed and function as a primary connection. There is no primary-secondary relationship involved. Model Creation You should create one Dialup_Link model for each phone number that the remote router(s) could dial to create the non-persistent connection. If the remote router(s) can dial one number that can be picked up by one of several host routers or host router interfaces, one Dial_Up link model is used to represent this connection [see Advanced Configurations (Page 15)]. The Dialup_Link model must be created manually. To create a Dialup_Link model from within a SPECTRUM Topology view, follow the instructions below. 1 Select File > Edit > New Model to display the Select Model Type dialog box. 2 In the Select Model Type dialog, select the Dialup_Link model type and click OK to display the Dialup_Link Creation View (Figure 1 on Page 7). 3 In the Dialup_Link Creation View, enter or adjust the following values/settings: a b Model Name: The name of the Dialup_Link model (1 to 16 ASCII characters). Security String: Assign a SPECTRUM Security String to the Dialup_Link model. (Refer to Security and User Maintenance for details on setting up security in SPECTRUM.) Non-Persistent Connections Manager User s Guide Page 6

8 c d Dialup Type: The functional type of the Dialup_Link. Possible types are Backup (DBL), Primary (PODL), and Bandwidth (BODL). (Refer to Types of Links Supported on Page 5). Dialup Protocol Type: The protocol type that will be used on the Dialup_Link. Possible protocol types are: Analog, Switch_56, ISDN, and Frame Relay. Figure 1: The Dialup_Link Creation View e Activation Grace Period (Minutes): This field allows you to specify the time allowed, in minutes, for the secondary link to become active after a primary link failure. If this grace period expires before the secondary link is active, then a red alarm is Non-Persistent Connections Manager User s Guide Page 7

9 Creating Dialup_Link Models Model Creation f g generated. This field is only used by DBL-type link models. The default setting is 3 minutes. Deactivation Grace Period (Minutes): This field allows a user to specify the time allowed, in minutes, for an active secondary link to deactivate after the failed primary link reactivates. If the secondary link is still active after this grace period expires, then a yellow alarm is generated. This field is only used by DBL-type link models. The default setting is 3 minutes. Maximum Uptime (Hours): The value in this field determines how long the link can remain active in hours before a yellow excessive activation alarm is generated. The default setting is 24 hours. 4 After the Creation view is completed, click OK. This will cause a Dialup_Link model to appear in the Topology view. When first created, the model will be in a normal inactive state and will have a brown condition. Figure 2: Dialup _Link Model Model Name Protocol Type Non-Persistent Connections Manager User s Guide Page 8

10 Configuring A Non-Persistent Connection This section provides the information necessary to configure a basic non-persistent connection once you have created the Dialup_Link model as described in the previous section. Configuring non-persistent connections involves designating primary and secondary interfaces on a remote router and a host router. Remote routers initiate dialup links. Host routers answer dialup calls from remote routers to establish the link. Management information is obtained by monitoring the remote router. There are a few different configurations that can be used to model the non-persistent connections on your network. This section discusses the most basic of these configurations: a host and a remote router with a primary and a secondary link connecting them. All of the connections for the secondary link are resolved to the interface level on both the host and the remote router. The steps in this chapter form the basis for the more complex configurations that are discussed in the Advanced Configurations (Page 15). Non-Persistent Connections Manager User s Guide Page 9

11 Configuring A Non-Persistent Connection Dial Backup Links and Bandwidth on Demand Links Dial Backup Links and Bandwidth on Demand Links Dial Backup Links (DBLs) and Bandwidth on Demand Links (BODLs) involve the redundant relationship between a primary link and a secondary link. The Dialup_Link model representing a DBL or a BODL monitors a primary link for a possible failure; it also monitors a related secondary link to verify its activation in a backup or supporting role if the primary link fails. In general, the following three tasks are required to configure these types of links. As described below, the secondary interface must be configured before the primary interface. 1 Configure the secondary interface. This is the interface on the remote router that will serve as the dialing end of the dialup connection. 2 Configure the primary interface on the remote router. This is the interface that serves as the connection to the primary link and is monitored by the Dialup_Link model. If this interface goes down, the dialup connection is used. 3 Configure the connection on the host router that will serve as the receiving end of the dialup connection. Primary on Demand Links Primary on Demand Links (PODLs) are non-persistent connections that are used as transient primary links. You configure these links using the same procedure described above; however, since this type of link model does not need to monitor a primary interface, you can skip step 2. Configuring Secondary Interfaces on the Remote Router When configuring the non-persistent connection, the first task is the configuration of a fixed secondary interface on the remote router. Doing this resolves the Dialup_Link model to the secondary interface in the Non-Persistent Connections Manager User s Guide Page 10

12 Device Topology view. This must be done manually as described below, since there is no information within any MIB that would denote a specific interface or link as acting in a redundant or secondary capacity. 1 Select File > Edit. 2 Highlight the Dialup_Link model that needs to be resolved. 3 Select Edit > Copy. 4 Select File > Close Edit. 5 Navigate into the Device Topology view of the remote router where you want to configure a secondary interface. 6 Select File > Edit. 7 Select Edit > Paste. 8 Drag the Dialup_Link icon onto the correct secondary interface model. 9 Select File > Close Edit to exit Edit mode. Configuring Primary Interfaces on the Remote Router After you configure the secondary interface on the remote router, you must configure the primary interface on the remote router. (Note that this step is not necessary for Primary on Demand Links). When you configure a primary interface, you associate the secondary link to the primary link(s) it is supporting. This is done in the Primary Interface Configuration view. You access the Primary Interface Configuration view by highlighting the Dialup_Link model and selecting Primary Interface Configuration from the Icon Subviews menu. Non-Persistent Connections Manager User s Guide Page 11

13 Configuring A Non-Persistent Connection Configuring Primary Interfaces on the Remote Router Figure 3: The Primary Interface Configuration View The Primary Interface Configuration view features two lists: The Complete Interface List includes all of the interfaces on all of the devices associated with the Dialup_Link model. For this basic configuration scenario, this is all of the interfaces on the remote router where the secondary interface has been configured. The Primary Interface List includes all currently configured Primary Interfaces for this Dialup_Link model. To configure a primary interface, do the following: 1 From the Complete Interface List, select the primary connection s remote router interface. 2 Click the Add Interfaces button. The newly configured Primary Interface will now appear in the Primary Interface List. Non-Persistent Connections Manager User s Guide Page 12

14 Configuring A Non-Persistent Connection Configuring Secondary Interfaces on the Host Router Note: If more than one primary interface on a single remote router is selected through the Primary Interface Configuration view, these interfaces will be treated as a group. The status of the group of primary interfaces is determined by the healthiest group member. The backup interface will activate only if all of the primary interfaces in the group fail. Configuring Secondary Interfaces on the Host Router The final task is the configuration of a secondary interface on the host router. To do this, you must resolve the Dialup_Link model to the secondary interface in the Device Topology view of the host router. As with the interfaces on the remote router, this must be done manually as described below. 1 Select File > Edit. 2 Highlight the Dialup_Link model that needs to be resolved. 3 Select Edit > Copy. 4 Select File > Close Edit. 5 Navigate into Device Topology view of the remote router where you want to configure a secondary interface. 6 Select File > Edit. 7 Select Edit > Paste. 8 Drag the Dialup_Link icon onto the correct secondary interface model. 9 Select File > Close Edit to exit Edit mode. Non-Persistent Connections Manager User s Guide Page 13

15 Configuring A Non-Persistent Connection Viewing the Dialup_Link in the Topology View Viewing the Dialup_Link in the Topology View Once you have configured the Dialup_Link model connections and specified the interface on the remote router for the primary connection, the Dialup_Link model is fully integrated into the current modeling scheme and will react according to the type of link it represents. The Topology view containing the Dialup_Link model will show live pipes connecting the Dialup_Link model to the remote and host routers. The live pipes will have a brown condition when the dialup link is inactive. If the modeled primary link and secondary links involve the same two devices, the topology configuration involving the host and remote routers should look similar to Figure 4. Figure 4: The Modeled Non-Persistent Connection Primary Link Dialup_Link Model { Fixed Secondary (Backup) Link Non-Persistent Connections Manager User s Guide Page 14

16 Advanced Configurations This section discusses various advanced non-persistent connection configurations. Beyond the basic configuration discussed in the previous section (Configuring A Non-Persistent Connection on Page 9), there are two additional non-persistent connection configurations that can be modeled: Multilink Secondary Interfaces on a Remote Router (Page 15): This type of configuration allows you to use one Dialup_Link model to specify a secondary link consisting of multiple interfaces that make up one logical link. This secondary link can be initiated by one or more ports on the remote router. Note that you must have the latest set of patches for SPECTRUM version in order to support this functionality. Multiple Dial Backup Links (MDBLs) (Page 18): This type of configuration allows you to have variable or unspecified links between a remote router and a host router. You could have multiple remote routers linking to a single host router or a single remote router linking to multiple host routers. Multilink Secondary Interfaces on a Remote Router It is possible to use one Dialup_Link model to support multiple secondary interfaces on a single remote router. For example, if your dialup connection uses a Multilink PPP over ISDN BRI configuration, you could associate a single Dialup_Link model with each of the PPP interfaces associated with the ISDN B-Channel connections. The figure below shows a remote router that has two connections to a host router. Since these two connections make up one logical link, you can use one Dialup_Link model to represent the link. Depending on the type of connectivity you are using, you can resolve the Dialup_Link model at the interface or the subinterface level. Non-Persistent Connections Manager User s Guide Page 15

17 Advanced Configurations Multilink Secondary Interfaces on a Remote Router Figure 5: Host Router Multilink Secondary Interfaces on a Remote Router Device B 1 1 Remote Router Device A Connectivity resolved at the interface level. Host Router 1 1 Device B Remote Router Device A 2 2 Connectivity resolved at the subinterface level. Primary Interfaces Secondary Interfaces There are three main tasks involved in creating this configuration. Each of these tasks is described below and references step-by-step instructions given in the previous chapter. Non-Persistent Connections Manager User s Guide Page 16

18 Advanced Configurations Multilink Secondary Interfaces on a Remote Router 1 The first task is to configure the secondary interfaces on the remote router. This involves resolving the Dialup_Link model to the secondary interfaces in the Device Topology view. For instructions, see Configuring Secondary Interfaces on the Remote Router on Page 10. Repeat this process using the same Dialup_Link model for each secondary interface on the device. Secondary Groups When a Dialup_Link model is associated with more than one interface on the same device, these interfaces will form a secondary group. SPECTRUM determines the status of the connection by looking at the state of the group. The DevSecGrpActiveCriteria attribute allows you to change how SPECTRUM determines the state of the secondary group. This attribute has a default value of AnySecondaryIFActive (0). This means that the group will be active if any member of the group is up; and dormant only if all members of the group are down. The other possible value for this attribute is AllSecondaryIfsActive (1). If this is the value, the secondary group will only be considered active if all members of the group are up, and will be considered inactive if one member goes down. You can change the value of this attribute in the Dialup_Link Information View (Page 24). 2 The next task is to configure a primary interface. When you configure a primary interface, you associate the secondary link to the primary link(s) it is supporting. This is done in the Primary Interface Configuration view. For instructions, see Configuring Primary Interfaces on the Remote Router on Page The final task is the configuration of the secondary interfaces on the host router. This involves resolving the Dialup_Link model to the secondary interfaces in the Device Topology view of the host router. For instructions, see Configuring Secondary Interfaces on the Host Router on Page 13. Non-Persistent Connections Manager User s Guide Page 17

19 Advanced Configurations Multiple Dial Backup Links (MDBLs) Multiple Dial Backup Links (MDBLs) A single Dialup_Link model can support configurations that include multiple secondary links. Only one Dialup_Link model is needed to monitor multiple secondary connections, because only a single active secondary connection can exist between the host router and the remote router at one time. Multiple Dial Backup Links (MDBLs) are used in either of the following scenarios: Multiple remote routers each with a dial backup link that connects to a common host router [see Multiple Remote Routers to a Common Host Router (Page 19)]. A single remote router with a dial backup link that could connect to one of several host routers [see Single Remote Router to Multiple Host Routers or Host Router Interfaces (Page 21)]. Non-Persistent Connections Manager User s Guide Page 18

20 Advanced Configurations Multiple Dial Backup Links (MDBLs) Multiple Remote Routers to a Common Host Router This figure shows three remote routers (devices B, C, and D) using one interface on a host router (Interface 4 of Device A) to provide redundant support for their primary links. Figure 6: A Dial Backup Link that Connects to a Common Host Router 1 2 Device B Host Router Device A 1 2 Device C Remote Routers Device D Primary Interfaces Secondary Interfaces Non-Persistent Connections Manager User s Guide Page 19

21 Advanced Configurations Multiple Dial Backup Links (MDBLs) There are three main tasks involved in creating this configuration. Each of these tasks is described below and references step-by-step instructions given in the previous chapter. 1 The first task is the configuration of the secondary interfaces on the remote routers. Configuration of these interfaces involves resolving the Dialup_Link model to each secondary interface in the Device Topology view of each remote router. For instructions, see Configuring Secondary Interfaces on the Remote Router on Page 10. Repeat these instructions for each remote router. 2 After you configure all of the secondary interfaces on the remote routers, you must configure the appropriate primary interfaces. When you configure a primary interface, you associate the secondary link to the primary link(s) it is supporting. This is done in the Primary Interface Configuration view. For instructions, see Configuring Primary Interfaces on the Remote Router (Page 11). Note: SPECTRUM will automatically affiliate the secondary interface configured on a device with the primary interface configured on the device, so that if this primary interface fails, the proper secondary connection will be monitored. 3 The final step is the configuration of fixed a secondary interface on the host router. This involves resolving the Dialup_Link model to the secondary interface in the Device Topology view of the host router. For instructions, see Configuring Secondary Interfaces on the Host Router (Page 13). Non-Persistent Connections Manager User s Guide Page 20

22 Advanced Configurations Multiple Dial Backup Links (MDBLs) Single Remote Router to Multiple Host Routers or Host Router Interfaces The figure below shows the remote router (device C) has secondary links established with two host routers (devices A and B) to provide redundant support for the primary link between device A and device C. When the secondary link becomes active, it will connect with either router A or router B. Before the connection is actually made, you cannot determine which of these routers the link will connect to. The same scenario exists if the redundant link could connect to one of several interfaces on a host router or routers. In all of these cases, the connection to the host router(s) is resolved at the device level. Figure 7: Dial Backup Link Connecting to Multiple Host Routers Device A Host Router Remote Router 1 2 Device C Host Router Device B Primary Link Secondary Link Non-Persistent Connections Manager User s Guide Page 21

23 Advanced Configurations Multiple Dial Backup Links (MDBLs) There are three main tasks involved in creating this configuration. Each of these tasks is described below and references step-by-step instructions given in the previous chapter. 1 The first task is the configuration of a secondary interface on the remote router. This involves resolving the Dialup_Link model to the secondary interface in the Device Topology view. For instructions, see Configuring Secondary Interfaces on the Remote Router (Page 10). 2 After you configure the secondary interface on the remote routers, you must configure the appropriate primary interface. When you configure a primary interface, you associate the secondary link to the primary link it is supporting. This is done in the Primary Interface Configuration view. For instructions, see Configuring Primary Interfaces on the Remote Router (Page 11). 3 The final task is the configuration of the connection to the host router. If it is unknown which host router and/or host router interface the remote router will connect to, you should resolve the dialup connection to the device level rather than the interface level. a b c d In the Topology view where you have created the dialup link, choose File > Edit. Double-click on the Dialup_Link model and then click on the host router. This creates a device level connection without connecting directly to one interface. If there are multiple host routers that the remote router could connect to, repeat this step for each of those host routers. Choose File > Save to save this view. Repeat these steps for each host router that the secondary link could connect to. Non-Persistent Connections Manager User s Guide Page 22

24 Monitoring Non-Persistent Connections This section describes how SPECTRUM lets you monitor and manage non-persistent connections. SPECTRUM displays the status of non-persistent connections in a variety of ways. The Dialup_Link Information View (Page 24) provides general information about the Dialup_Link model. The The Active NPC Summary View (Page 25) shows the status of each non-persistent connection. The Dialup_Link Condition Color (Page 26) is displayed on the Dialup_Link model in the Topology view. Alarms (Page 27) are generated on the Dialup_Link model for various reasons. The details of the alarm can be viewed in the Alarm Manager. Non-Persistent Connections Manager User s Guide Page 23

25 Monitoring Non-Persistent Connections Dialup_Link Information View Dialup_Link Information View The Dialup_Link Information view (Figure 8) displays information about the creation, current settings, and status of the Dialup_Link model. You access the Dialup_Link Information view by highlighting the Dialup_Link model icon and selecting Information from the Icon Subviews menu. Figure 8: The Dialup_Link Information View Non-Persistent Connections Manager User s Guide Page 24

26 Monitoring Non-Persistent Connections The Active NPC Summary View The Active NPC Summary View The Active NPC (Non-Persistent Connections) Summary view provides a report on all Dialup_Link models that are currently active in a landscape. The view is dynamically updated. You access the Active NPC Summary view by highlighting the Dialup_Link model icon and selecting Active NPC Summary View from the Icon Subviews menu. Figure 9: The Active NPC Summary View The following information is presented in this view: Model Name: The model name for the Dialup_Link model. Activation Time: The time that the Dialup_Link model became active; i.e., when the Dialup_Link model was connected to the appropriate interfaces. From Point: The remote router model name. To Point: The host router model name. Duration: The length of time that the connection has been active. NPC Type: The type of link between the two points. Possible types are Backup (DBL), Primary (PODL), and Bandwidth (BODL). (Refer to Types of Links Supported on Page 5). Non-Persistent Connections Manager User s Guide Page 25

27 Monitoring Non-Persistent Connections Dialup_Link Condition Color Dialup_Link Condition Color The way in which the Dialup_Link model reacts to changes in the primary and secondary links depends upon the type of non-persistent connection this model represents. The following tables show the possible conditions for the Dialup_Link model representing a Dial Backup Link, Bandwidth on Demand Link, or a Primary On Demand Link. Table 1: Dial Backup Link Conditions Primary Link Secondary Link Dialup_Link Condition Generated Events Up Up Yellow Both primary and secondary links active. Up Down Brown Secondary link inactive. Down Up Green Secondary link active. Down Down Red Secondary link has failed to activate. Table 2: Bandwidth on Demand Link Conditions Primary Link Secondary Link Dialup_Link Condition Generated Events Up Up Green None Up Down Brown Dialup_Link is inactive. Down Up Green Secondary link is active. Down Down Red Secondary link has failed to activate. Non-Persistent Connections Manager User s Guide Page 26

28 Table 3: Primary On Demand Link Conditions Primary Link Dialup_Link Condition Generated Events Up Green No event is generated. Primary On Demand Link is active. Down Brown No event is generated. Primary On Demand Link is inactive. Up Yellow The maximum uptime value has been exceeded. There are two exceptions to the Dialup_Link Condition Tables. These involve special alarm conditions of Gray and Orange. A Gray condition is asserted on a Dialup_Link model when all secondary interfaces are considered unreachable. An Orange condition is asserted only in a multiple primary/secondary configuration when a primary link has failed but the secondary link is already active in support of another connection. Alarms The following list shows the alarms that SPECTRUM can generate on a Dialup_Link model. Alarm Code Alarm Alarm Cause 0x022ffff8 User excess timer has been exceeded. The link has been active for longer than the time specified in the Maximum Uptime attribute [see Model Creation (Page 6)]. Non-Persistent Connections Manager User s Guide Page 27

29 Alarm Code Alarm Alarm Cause 0x022ffff9 Backup link is already active. This alarm occurs when SPECTRUM attempts to activate a dialup link that is already active. 0x022ffffa 0x022ffffb Both the primary and the secondary links are active. The secondary link failed to activate. Both the primary and the secondary links have been activated. An attempt to activate the secondary link was unsuccessful. 0x022ffffc The secondary link is inactive. The primary link is functioning properly and the secondary link has returned to an inactive status. 0x022ffffd The Dialup_Link model is unreachable. This alarm is generated when all of the Dialup_Link model s neighbors are down. Neighbors include any interface model or device model to which the Dialup_Link model has a resolved connection. Non-Persistent Connections Manager User s Guide Page 28

30 Index A Activation Grace Period 7 Active NPC Summary View 25 Add Interfaces 12 B Bandwidth on Demand Link 5 BODL 5 D DBL 5 Deactivation Grace Period 8 Dial Backup Link 5 Dialup Protocol Type 7 Dialup Type 7 Dialup_Link Creation View 7 Dialup_Link Information View 24 Dialup_Link model 6, 10, 13, 14, 17, 18, 22, 24, 25 H Host Router 13 L load balancing 4 M Maximum Uptime 8 Model Name 8 Multiple Dial Backup Links 18 P PODL 5 Primary Interface Configuration 11 Primary on Demand Link 5, 6, 10 S Secondary Interfaces 13 Security String 6 U unspecified links 15 I Information 24 Non-Persistent Connections Manager User s Guide Page 29