Ceterus Universal Transport System

Transcription

1 Ceterus Universal Transport System

2 Notice Copyright Notice Copyright present 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. 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 virus-free. 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 with 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 USA Phone: U.S. toll-free: Web site: Page 2

3 Contents Notice... 2 Preface... 5 Intended Audience... 5 How to Use This Guide... 6 Text Conventions... 7 Document Feedback... 7 Online Documents... 8 Required Reading... 8 Overview... 9 Device Support... 9 Device MIB Support...12 Traps, Events, and Alarms Trap Support...13 Application Support RFC and IEEE Standard Applications...16 Device Views Web Administration...17 Entity Tables...17 Deployment Scenarios Configuring for Different Deployments...18 Single (Unique) IP Mode...19 Dual IP Mode...21 Modeling Considerations...22 Configuring Live Links...22 Interface Model Naming...25 Trap Processing Trap Processing Configuration...27 Page 3

4 Trap Storm Configuration...28 Index Page 4

5 Preface Welcome to the user guide for SPECTRUM s Ceterus Universal Transport System management module. Please take a moment to read through this short preface, which explains how the information in this guide is organized and presented and lets you know how to access information about other SPECTRUM products. In this section: Intended Audience [page 5] How to Use This Guide [page 6] Text Conventions [page 7] Document Feedback [page 7] Online Documents [page 8] Required Reading [page 8] Intended Audience This guide is intended for users of SPECTRUM s Ceterus Universal Transport System (SM-CET1000) management module. Page 5

6 How to Use This Guide Use this document as a guide for managing the Ceterus devices described in Device Support [page 9] with SPECTRUM management module SM- CET1000. The guide is organized as follows: Overview [page 9] Traps, Events, and Alarms [page 13] Application Support [page 16] Device Views [page 17] Deployment Scenarios [page 18] Trap Processing [page 27] For general information about device management using SPECTRUM and explanations of SPECTRUM functionality and navigation techniques, refer to the topics listed under Required Reading [page 8]. Page 6

7 Text Conventions The following text conventions are used in this document: Element Convention Used Example User-supplied parameter names Courier and Italic in angle brackets <>. The user needs to type the password in place of <password>. On-screen text Courier The following line displays: path= /audit User-typed text Courier Type the following path name: C:\ABC\lib\db Cross-references References to SPECTRUM documents (title and number) Functionality enabled by SPECTRUM Alarm Notification Manager (SANM) Underlined and hypertextblue Italic SANM in brackets []. See Document Feedback [page 7]. SPECTRUM Installation Guide (5136) [SANM] AGE_FIELD_ID Document Feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Page 7

8 Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Required Reading To use this documentation effectively, you must be familiar with the information covered by the SPECTRUM documents listed below. Getting Started with SPECTRUM for Operators (1763) Getting Started with SPECTRUM for Administrators (0985) How to Manage Your Network with SPECTRUM (1909) SPECTRUM Views (2517) SPECTRUM Menus (2519) SPECTRUM Icons (2518) Application View and MIBs (2560) SPECTRUM Software Release Notice Page 8

9 Overview This section introduces the SPECTRUM documentation for the management module. In this section: Device Support [page 9] Device MIB Support [page 12] Device Support SPECTRUM management module SM-CET1000 currently provides modeling for the following devices (Table 1). Figure 1 shows the Device Icon in the Topology view. Table 1: Supported Devices, Firmware, and Model Type Supported Devices Description Firmware Revision Model Type UTS /100 Ethernet (client) Ports and 4 T1/ E1 (client) ports Transports data over 8 bonded T1/E1 (line) ports Integrated Voice and Ethernet platform 10/100 Ethernet as well as TDM voice carried over bonded T1 Side-Band Management for NMS UTS Gigabit Ethernet Ports, or 4 10/100 Ethernet Ports Up to 6 DS3s, or 2 OC3/OC12s. Side-Band Management for NMS UTS 1100 Up to 8 Gigabit Ethernet Ports, or up to 16 10/100 Ethernet Ports Transports data over up to 12 bonded DS3s, or 4 bonded OC3s or OC12s Speeds from 45Mbps to 2.5 Gbps Side-Band Management for NMS R1.1.0 R1.2.1 R1.2.1 CeterusUTS CeterusUTS CeterusUTS Page 9

10 Figure 1: Device Icon The (UTS) provides transport of Ethernet service over existing infrastructure. The UTS bonds line-side facilities from DS1/E1 to OC-n into a single pipe, enabling the use of existing line facilities, Add Drop Multiplexers (ADMs), or other network elements for broadband services. The UTS then combines all client signals regardless of signal type into a single payload. The UTS can be used over copper or fiber for a variety of applications, including: Transparent LAN Service Internet Access Service Storage Area Networking/Remote Data Center connection VoIP service port extension Virtual Point of Presence (POP) Ethernet-based Wireless Cell Site backhaul Page 10

11 The is a chassis shelf with preinstalled interface and line/control cards. Each shelf contains a combination of the following components: Line/control cards which are inserted into the shelf and are responsible for management, circuit, and packet operations Physical interface cards which provide network access A fan subsystem Power inputs and circuit breakers to regulate -48V direct current LEDs to indicate status and alarms within cards Page 11

12 Device MIB Support SPECTRUM supports the device-specific MIBs shown in Table 2 for the management module. Table 2: MIB Support Proprietary MIB CETERUS-ALARM CETERUS-CHASSIS CETERUS-COMMON-TC CETERUS-DS0-EXT CETERUS-DS1-EXT CETERUS-DS1-PM CETERUS-DS3-EXT CETERUS-DS3-PM CETERUS-ETH CETERUS-ETH-PM CETERUS-MGMTPORT CETERUS-PRODUCTS CETERUS-SMI CETERUS-SONET-EXT CETERUS-SWDB CETERUS-SYNCN CETERUS-SYS CETERUS-UTPP-PROT CETERUS-UTS1x00-SWDB Page 12

13 Traps, Events, and Alarms This section describes the traps supported by the Ceterus Universal Transport System management module. In This Section Trap Support [page 13] Trap Support The management module supports the standard and device-specific traps shown in Table3 [page14]. See Deployment Scenarios [page 18] and Trap Processing Configuration [page 27] for more information on trap processing. Page 13

14 Table 3: Trap Support Trap Name / OID Varbinds Event Condition Rule and Varbind(s) Varbind Value Event Generated Alarm Generated or Cleared and Severity Varbind Disciminators linkdown standard N/A N/A 0x x Minor N/A linkup entconfigchange standard N/A N/A 0x Clears 0x N/A standard N/A N/A 0xc xc40005 N/A cetalarmnotif cetnotiftag (1,0) entphysicalname (2,0) cetactivealarmentitytype (3,0) cetactivealarmcondtype (4,0) cetactivealarmntfcncode (5,0) cetactivealarmsrvceffect (6,0) cetactivealarmcondeffect (7,8) cetactivealarmocrdatetime (9,0) cetactivealarmdescp (10,0) Set condition of the alarm generated is based on the value of cetactivealarmntfcncode. Possible enumerations are critical, major, minor, non-alarmed, non reported, and cleared. N/A 0x4ba0002 0x4ba0003 0x4ba0004 0x4ba0005 0x4ba0006 Alarm severity for this alarm is based on the varbind value of cetactivealarm NtfcnCode. 2 and 4 Page 14

15 Trap Name / OID Varbinds Event Condition Rule and Varbind(s) Varbind Value Event Generated Alarm Generated or Cleared and Severity Varbind Disciminators cettcanotif cetdbchgnotif cetnotiftag (1,0)\ entphysicalname (2,0)\ cettcaentitytype (3,0)\ cettcamonitoredobjectid (4,0)\ cettcamonitoredobjectvalue (5,0)\ cettcamonitoredobjectthreshold (6,0)\ cettcalocation (7,0)\ cettcaocrdatetime (8,0)\ cettcadescp (9,0) cetnotiftag (1,0)\ entphysicalname (2,0)\ cetdbchgseqnum (3,0)\ cetdbchgdescp (4,0) N/A N/A 0x04ba0001 N/A N/A N/A N/A 0x04ba0000 N/A N/A Page 15

16 Application Support This section describes the applications supported by the management module. In This Section RFC and IEEE Standard Applications [page 16] RFC and IEEE Standard Applications The management module supports various RFC and IEEE standard applications. The applications are created and associated with the device model based on the specific device s capabilities. The following guides contain complete documentation for each of the standard applications supported by SPECTRUM: Bridging Applications (2562) MIB II Applications (2561) Routing Applications (3080) Technology Applications (5065) Transmission Applications (5064) Page 16

17 Device Views This section describes the available device-specific views for the management module. In This Section Web Administration [page 17] Entity Tables [page 17] Web Administration Access: From the Icon Subviews menu for the Device icon in the SpectroGRAPH, select Web Administration. This provides access to the URL set in the device s WebAdminURL attribute. Note: The default value of the WebAdminURL attribute is (0x1027f is the Network_Address attribute, which contains the device s IP Address). You can use the Global Attribute Editor in Search Manager to change the value of the WebAdminURL attribute. See the Global Attribute Editor section of the Search Manager User Guide (2383) for more information. Entity Tables Access: From the Icon Subviews menu for the Device icon in the SpectroGRAPH, select Entity Tables > Physical/Logical Tables. In OneClick, select the Information tab of the Component Detail panel for the device and expand the Entity View. This provides access to the RFC2737App s Physical and Logical Entity tables (see Application Support [page 16]). Page 17

18 Deployment Scenarios This section describes common deployment scenarios for the devices and how to model them in SPECTRUM. In This Section Configuring for Different Deployments [page 18] Modeling Considerations [page 22] Configuring for Different Deployments There are two supported types of deployments in SPECTRUM, Single (Unique) IP Mode [page 19] and Dual IP Mode [page 21]. Both types are described in this section using an example featuring a local Ceterus device (Local) as well as a remote Ceterus device (Remote). If Ceterus devices are deployed in a scenario where two devices share the same IP address, then Single (Unique) IP Mode [page 19] must be configured for each model. If Ceterus devices are deployed with different IP addresses, then Dual IP Mode [page 21] must be configured for each model. This setting can be configured in the SpectroGRAPH by rightclicking the Device Model icon for a CeterusUTS model. Page 18

19 Single (Unique) IP Mode In this mode, SPECTRUM has IP connectivity to a single device and must use a single IP address to reach both the Local and Remote devices. Figure 2: Single IP Scenario [page 19] shows the Remote and Local Ceterus devices in a SPECTRUM environment. The Local and Remote devices share the same IP address. Remote does not have IP connectivity to SPECTRUM, but performs SNMP communications via the Local device. The Local device performs this forwarding function by evaluating the community string stored in the SNMP packet. Figure 2: Single IP Scenario Configuring Single IP Mode 1. Set Deployment Mode to Single IP Mode (Figure 3). Page 19

20 Figure 3: Single IP Mode Page 20

21 Dual IP Mode The Dual IP Scenario [page 21] shows the Remote and Local Ceterus devices in a SPECTRUM environment. Local and Remote have different IP addresses. Both devices have IP connectivity to SPECTRUM. Note: Dual IP Mode is set by default for models of the CeterusUTS model type. In this mode, Spectrum has IP connectivity to both Local and Remote devices. Figure 4: Dual IP Scenario Page 21

22 Configuring Dual IP Mode 1. Set Deployment Mode to Dual IP Mode (Figure 5). Figure 5: Dual IP Mode Modeling Considerations This section provides details for Configuring Live Links [page 22] and Trap Storm Configuration [page 28]. Configuring Live Links Ceterus UTS devices do not support layer 2 and/or layer 3 functions, therefore, SPECTRUM cannot AutoDiscover links between Ceterus devices automatically. However, this can be done in the SpectroGRAPH by manually creating links between specific ports and then enabling live links (see the How to Manage Your Network with SPECTRUM (1909) guide for more information), as shown in Figure 6. Once this has been done, SPECTRUM will monitor the status of the link and will report whether the link is up or down. Page 22

23 Figure 6: Enable Live Links Figure 7 shows a live pipe between two devices connecting port 402 of a Local device and port 402 of a Remote device. In this example, a single link was manually set up between port 402 on the pair of devices. Figure 7: Live Pipe When a port goes down on either end of the link, link up/link down traps are sent to the appropriate device and then asserted on the corresponding Page 23

24 interface model. SPECTRUM then determines where the fault has occurred and brings down the most appropriate link in SPECTRUM and generates any needed alarms. In this example, a link has been lost on port 402 of the Local device model. An alarm is asserted upon that interface and the condition is rolled up to the device as seen by the orange triangle on the device model (Figure 8). Additionally, the link representing the connection between the Local port 402 and the Remote port 402 will go down (as indicated by the red link). Figure 8: Link Down Page 24

25 In OneClick, if you click and select the link between the two devices, the Component Detail panel will display a Link Information tab view with details about the ports and links (Figure 9). Figure 9: Link Information Interface Model Naming Interface model names can be configured with a suffix of either ifindex, ifdescr, ifname, or ifalias. For the example shown in Figure 10, ifname was chosen because it provides additional detail about the type and location of the interface. For more information, see the Configuring Interface Model Name Suffix example in the How to Manage Your Network with SPECTRUM (1909) guide. Page 25

26 Figure 10: Interface Model Naming Page 26

27 Trap Processing This section describes trap processing in SPECTRUM for the devices SPECTRUM. In This Section Trap Processing Configuration [page 27] Trap Storm Configuration [page 28] Trap Processing Configuration The Remote Ceterus device can be configured to forward traps through its EOC channel to the Local device. In this configuration, the Local device acts as a gateway and forwards these traps. Please refer to the Ceterus documentation for more information on this feature. The Remote device can also be configured with an SNMP target IP address. In this configuration, it will send traps via its management port. If both of these capabilities are configured at the same time, then SPECTRUM will receive duplicate traps. The Ceterus management module was designed to handle this case. It will evaluate incoming Ceterus traps and assert those traps on the most appropriate SPECTRUM device model by comparing the Ceterus device s community string sent with the trap with the device s value for sysname. Important: Because SPECTRUM relies on the device s community name to make this determination, it is important that the device s community name is synchronized with its sysname. Polling of sysname occurs every five minutes by default. Changing the TID may affect trap handling until sysname has been properly updated via a poll. For example, if an administrator changes the TID (sysname) on a given Ceterus device from Device A to Device B, then the device sends traps to that model, SPECTRUM will be unable to process the traps until sysname is updated (up to a maximum of five minutes by default). Page 27

28 Trap Storm Configuration Modeling Ceterus devices in SPECTRUM requires special consideration to avoid trap storms. A trap storm can be defined as the number of traps received per second that will disable trap handling in SPECTRUM, provided the rate is sustained for the amount of time specified. See the Trap Storm Rate section of the Distributed SpectroSERVER (2770) guide for complete details. The default setting for trap storm rate is 20 traps per five seconds. Note: A trap storm can occur on behalf of both mapped and unmapped (unmanaged) traps. The most likely Ceterus traps to cause trap storms are the Threshold Crossing trap and/or the Database Change trap. Threshold Crossing traps can frequently be seen as bandwidth fluctuates in a network. Database Change traps occur any time an administrator makes a change to an attribute using the Web Administration [page 17] interface, resulting in a single trap or hundreds of traps being sent. The trap rate also depends on the number of devices existing in the SPECTRUM management network. Page 28

29 Figure 11 shows 111 traps having been received within two minutes after pulling and replacing boards on the UTS1x00 devices. The large number of Threshold Crossing notifications was the primary cause of this trap storm. Figure 11: Trap Storm To avoid trap storms, you can increase the trap storm rate in SPECTRUM (see the Trap Storm Rate section of the Distributed SpectroSERVER (2770) guide). This management module was tested with a trap storm setting of 1000 traps in one second. Page 29

30 Index A Add Drop Multiplexers (ADMs) [10] C Ceterus Universal Transport System (UTS) [10] CeterusUTS model type [9] D Device-specific MIBs [12] Traps [13] Views [17] E Entity Tables [17] F Firmware [9] I IEEE [16] Interface Model Naming [25] M MIB Support [12] Model Type [9] N Network_Address [17] Page 30

31 R RFC [16] RFC2737App [17] S SM-CET1000 [9] Supported Devices [9] sysname [27] T Trap Processing [27] Trap Storm [28] Configuring rate of [29] Trap Support [13] Traps Database Change [28] Threshold Crossing [28], [29] U Universal Transport System (UTS) [10] UTS 1000 [9] UTS 1100 [9] UTS 900 [9] W Web Administration [17] WebAdminURL [17] Page 31