EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version ... · MPLS Manager ... Alcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following EMC Smarts

EMC® Smarts®

Adapter for Alcatel-Lucent 5620 SAM EMSVersion 3.2

User GuideP/N 300-010-148REV 03

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide2

Copyright © 2005 - 2015 EMC Corporation. All rights reserved. Published in the USA.

Published May 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

http://support.emc.com

CONTENTS

Chapter 1 Introduction

Overview..................................................................................................... 12New features and changes .................................................................... 12New features in Foundation 9.0............................................................. 13New features in ASAM Patches .............................................................. 15

Architecture ................................................................................................ 16IP Availability Manager/Performance Manager ...................................... 18MPLS Manager ...................................................................................... 18Network Protocol Manager for BGP ........................................................ 19Network Protocol Manager for OSPF ...................................................... 19Network Protocol Manager for IS-IS ....................................................... 19Multicast Manager ................................................................................ 20Adapter Platform ................................................................................... 20

Discovery .................................................................................................... 20Full discovery ........................................................................................ 21Incremental discovery ........................................................................... 21Physical and logical discovery............................................................... 21Discovery of connections ...................................................................... 22Event processing................................................................................... 22Adapter Platform alarms........................................................................ 22

Multi-vendor topology support .................................................................... 23 Fault tolerance ............................................................................................ 23 Troubleshooting.......................................................................................... 24

Chapter 2 Configuring the Adapter Deployment

Methods for modifying user configuration parameters................................. 26Using the Global Console ...................................................................... 26Using the command line........................................................................ 26

Granting Windows 2008 UAC write permissions .......................................... 27local\conf directory ............................................................................... 27local\conf\alcatel-sam directory............................................................ 28

Configuring the Alcatel-Lucent 5620 SAM EMS server.................................. 28Creating a user for SAM-O interface access............................................ 28Configuring statistics polling................................................................. 28

Copying required .jar files............................................................................ 30Copying required .jar files for EMS 6.1 and 7.0 ...................................... 30

Configuring the Adapter .............................................................................. 30Editing the emsConfig.import file .......................................................... 31emsConfig.import parameters ............................................................... 31Preventing access to an optional server................................................. 38Generating an MD-5-hashed password.................................................. 38Changing the SM_LIBPATH value (Windows platform only) .................... 39Configuring the WANLink driver ............................................................. 39

Configuring JMS message filtering ............................................................... 41Monitored events .................................................................................. 41JMS message filter ................................................................................ 41Default JMS filter ................................................................................... 41Modifying the default JMS filter ............................................................. 43

Configuring alarm processing ...................................................................... 43

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide 3

Contents

Configuring alarms................................................................................ 44Considerations for working with alarms................................................. 46Aggregating alarms ............................................................................... 47Configuring aggregate alarms................................................................ 47Notes on alarms.................................................................................... 48Reloading alarm configuration files ....................................................... 49Filtering out alarms in maintenance....................................................... 49New INACTIVE alarms in ASA-Alarm.conf................................................ 50

Configuring Domain Managers .................................................................... 52Scenario 1: Deployment with IP 7.0.3 in an all Alcatel-Lucent environment.......................................................................................... 52Scenario 2: Deployment with mixed vendor environment and IP Manager 7.x ...................................................................................... 54Scenario 3: Deployment with IP Manager 8.1......................................... 55Scenario 4: Deployment with the Topology Split Manager (TSM)............ 57

Additional configuration for NPM Managers ................................................ 59 Additional configuration for the Multicast Manager ..................................... 60 External polling auto-configuration.............................................................. 61

New polling groups ............................................................................... 61 Replacing existing Domain Manager repositories......................................... 62 Rolling the Adapter Log ............................................................................... 62 Device filtering (optional) ............................................................................ 63

Overview of device filtering ................................................................... 63

Chapter 3 Start up and Discovery

Starting Adapter and Domain Manager services .......................................... 66Starting the Domain Manager services .................................................. 66Stopping a Domain Manager service ..................................................... 67

Initiating discovery...................................................................................... 67Initiating full discovery .......................................................................... 67Initiating partial discovery ..................................................................... 67Scheduling a periodic discovery ............................................................ 68Synchronizing alarms............................................................................ 68

Removing an unused JMS durable connection ............................................. 69

Appendix A Mapping of SAM-O Elements to Smarts Objects

Examples of EMS elements mapped to EMC Smarts objects ........................ 72 Power supply instantiation.......................................................................... 85 SAM-O element to EMC Smarts object mapping........................................... 85

Appendix B Mapping of Smarts objects and SAM-O Objects

Discovered inventory objects ...................................................................... 92 Mapping of SAM-O equipment objects ........................................................ 93 Mapping of SAM-O service objects .............................................................. 98

Appendix C Mapping of SAM-O Objects and Smarts Notifications

Element to notification mapping ............................................................... 112

Appendix D Notification Log Entries

Notification Log entries ............................................................................. 120

4 EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide

Contents

Appendix E Logs

Adapter log file ......................................................................................... 126 Startup sequence...................................................................................... 126 Discovery Log messages ........................................................................... 129 Event messages ........................................................................................ 132 Alarm messages........................................................................................ 133

Discarding example............................................................................. 133 Queue Log messages ................................................................................ 134 Warning messages.................................................................................... 134

No SAM-O license ............................................................................... 134Turn on verbosity example .................................................................. 135restartJMSConnector example ............................................................. 135

Appendix F Troubleshooting

Use ASL scripts for troubleshooting........................................................... 138

Appendix G Understanding the sm_edit Utility

Appendix H Getting help

Where to get help...................................................................................... 148

Index


Contents


Title Page

FIGURES

1 Adapter for Alcatel-Lucent 5620 SAM EMS architecture ............................................... 172 Architecture for multi-vendor topology support............................................................ 233 EMS to IP Manager mapping........................................................................................ 724 EMS to Network Protocol Manager for BGP mapping.................................................... 735 EMS to Network Protocol Manager for OSPF mapping .................................................. 746 EMS to Network Protocol Manager for IS-IS mapping ................................................... 757 EMS to Multicast Manager mapping ............................................................................ 768 EMS to MPLS Manager VLL mapping............................................................................ 779 EMS to MPLS Manager VPLS mapping ......................................................................... 7810 EMS to MPLS Manager VPRN mapping......................................................................... 7911 EMS to MPLS Manager VPRN Route Target mapping..................................................... 8012 EMS to IP Manager interface mapping ......................................................................... 8113 Modeling of VLAN and related components in the MPLS Manager................................ 8214 Relationship between a VLAN and a VPLS.................................................................... 8315 Modeling of LSP paths and SDP tunnels ...................................................................... 84


EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS User Guide8

Title Page

TABLES

1 Adapter configuration parameters ............................................................................... 322 Alarm processing parameters...................................................................................... 443 Mapping of Alcatel-Lucent 5620 SAM EMS and EMC Smarts Alarm severities .............. 464 New INACTIVE alarms in this release............................................................................ 505 New polling groups ..................................................................................................... 616 Mapping of SAM-O Elements to EMC Smarts objects ................................................... 857 Adapter support for 5620 SAM EMS inventory ............................................................. 928 Mapping of SAM-O equipment objects to EMC Smarts class ........................................ 939 Mapping of SAM-O service objects to EMC Smarts objects........................................... 9810 Mapping of Alcatel-Lucent elements to notifications ................................................. 11211 Global Console notifications ..................................................................................... 12012 Log warning level settings ......................................................................................... 138


Tableses


CHAPTER 1Introduction

This guide provides information about the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS for use with the Alcatel-Lucent 5620 Service Aware Manager (SAM) Element Management System (EMS). In addition, it includes information for configuring and using the Adapter.

This chapter contains the following information:

• Overview................................................................................................................. 12• Architecture ............................................................................................................ 16• Discovery ................................................................................................................ 20• Multi-vendor topology support ................................................................................ 23• Fault tolerance ........................................................................................................ 23• Troubleshooting...................................................................................................... 24

Introduction 11

Introduction

OverviewThe EMC® Smarts® Adapter for Alcatel-Lucent 5620 SAM EMS provides a link from the Alcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following EMC Smarts Domain Managers:

◆ IP Availability Manager

◆ MPLS Topology Manager

◆ Network Protocol Managers (Manager for BGP, Manager for OSPF, Manager for IS-IS)

◆ Multicast Manager

The Adapter sends topology queries by XML streams to the EMS, where they are processed. Near real-time events are passed from the EMS by Java Message Service (JMS), also in XML format, to the Adapter. Based on the events, the Adapter creates notifications in the Adapter Platform. The Adapter Platform creates notifications for display in the Service Assurance Global Console.

New features and changes

The Adapter for Alcatel-Lucent 5620 SAM EMS provides the following new features:

◆ EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS is now supported on Red Hat Enterprise Linux (RHEL) 6. The base installer name is setup-ASAM-3_2_0_0-linux-rhAS60.bin.

Even though there is a separate base installer for RHEL 6, a common patch installer is available for both RHEL 5 and RHEL 6. The EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.2 Patch Readme provides more information.

◆ Support for Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server version 10.x on adapters 3.2.0.3 and higher. Supported versions of the Alcatel-Lucent 5620 Service SAM EMS server are 6.1 through 12.x.

◆ Support for Alcatel-Lucent 7250 switches

• Discover and monitor Alcatel-Lucent 7250 switch physical components.

• Discover and monitor Alcatel-Lucent 7250 VPLS elements in unqualified mode.

• Discover and monitor Alcatel-Lucent 7250 VPLS elements in qualified mode (including discovery of VLANs at the VPLS endpoint).

• Discover and monitor Alcatel-Lucent 7250 switch VLAN elements in VLAN mode.

• Associate VLANs on the 7250 switches with VPLS on other devices (7450s, 7750s, and so on).

• Create Cables for 7250 switches when physical links are manually configured in the Alcatel-Lucent 5620 SAM.

• Create NetworkConnections for 7250 switches when 30-bit or 31-bit subnets are used on a 7250.


Introduction

Although some 7250 switches support OSPF, the 5620 SAM EMS does not retrieve OSPF information from the 7250 devices. As a result, the Adapter cannot build Cables or NetworkConnections based on the OSPF neighbors. Additionally, 7250 switches do not support LLDP. As a result, NetworkConnections can only be built for 7250s when 30-bit or 31-bit subnets are used on a 7250.

◆ Support for Alcatel-Lucent OmniSwitch, including the following:

• Discover and monitor Alcatel-Lucent OmniSwitch physical components.

• Discover and monitor Alcatel-Lucent OmniSwitch VLAN elements in TLS mode.

• Discover and monitor Alcatel-Lucent OmniSwitch VLAN elements in BTV mode.

• Associate VLANs on the OmniSwitches with VPLS on other devices (7450s, 7750s, and so on.)

• Create Cables via interfaces between OmniSwitches when physical links are manually configured in the Alcatel-Lucent 5620 SAM.

• Create Cables between OmniSwitches when LLDP is configured in the Alcatel-Lucent 5620 SAM that builds the physical links.

• Create Cables between OmniSwitches and non-Omni devices when LLDP is supported and enabled in those non-Omni devices. Since 5620 SAM EMS Release 7.0/R1, LLDP is supported in 7450s, 7750s, and 7710s.

◆ Support for Alcatel-Lucent 7210 SAS-E, including the following:

• Discover and monitor Alcatel-Lucent 7210 switch physical components.

• Create Cables for 7210 switches when physical links are manually configured in the Alcatel-Lucent 5620 SAM.

• Create NetworkConnections for 7210 switches when 30-bit or 31-bit subnets are used on a 7210

◆ The Adapter for Alcatel-Lucent 5620 SAM EMS interoperates with EMC Smarts IP Manager Versions 8.x and 9.x. When deploying new versions of both products, you now need to add the IP domain as a source to MPLS, NPM, and MCAST domains if they are included in your network. “Configuring the Adapter Deployment” on page 25 provides more information.

New features in Foundation 9.0

This release of the Adapter for Alcatel-Lucent 5620 SAM EMS is based upon foundation 9.0. Documentation explaining Foundation 9.0 features is listed in the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes. Here are highlights of changes related to Foundation 9.0:

Overview 13

Introduction

InternationalizationAny information that the Foundation 9.0 manages is now manipulated, stored and retrieved in a language-aware manner. The internationalization functionality of the foundation covers broad areas of logging, locale awareness, legacy character encoding and Unicode encoding, string externalization, and utilities and programming interfaces for application enablement of these same features.

In this release, the foundation has been internationalized and is functionally localized to American English. Localization to the other target languages, as dictated by the EMC globalization policy and customer requirements, will be undertaken at a future date.

The name of the log files in the IP Manager reflects these changes in foundation software. Log files have the following syntax: <name>_<locale>_<encoding>.log. For example, MYDOMAINMANAGER_en_US_UTF-8.log. The System Administration Guide provides complete information about locale and log files.

ICIM Ref 1.10Foundation 9.0 has been updated to support ICIM Reference 1.10.

New SmRestartableDomainManager classYou can now use SmRestartableDomainManager in place of SmRemoteDomainManager with minimal changes to accommodate it. The benefit of using the SmRestartableDomainManager is that your application does not need to write code to check the status of the remote server and to try to reconnect if the server shuts down and is restarted.

The SmRestartableDomainManager has the ability to reconnect with the remote domain manager when the remote server comes back up.

New MODEL operations to retrieve description textThere are a number of API operations that have been re-implemented as MODEL operations. These MODEL operations retrieve description texts. The texts that are retrieved will be in the locale that was set either by the initial connection or by the locale set by the most recent call to the setRemoteLocale API operation. For earlier versions of foundation software, whose protocol is incapable of specifying locales, the locale is set to en_US.

If these operations are run outside of the context of a remote session, then the effective locale is CI_Locale::DEFAULT.

The operations are:

◆ getPropDescription — retrieve the description of the MODEL property

◆ getEventDescription — retrieve the description of the MODEL event

◆ getOpDescription — retrieve the description of the MODEL event

◆ getClassDescription — retrieve the description of the MODEL class

These MODEL operations are described in the EMC Smarts MODEL Reference Guide .


Introduction

New command line option in sm_adapter A new option, alarmInterval, has been added to sm_adapter. You can use the alarmInterval option with a subscriber front end ( --subscribe or --subscribeProp). Setting alarmInterval causes the front end to generate a message on its own if no new updates have been received in the last <alarmInterval> seconds. You can use this feature to have your script wake up after periods of inactivity. However, in order to use alarmInterval, your script must recognize a message type of Timer_Alarm.

--alarmInterval=secs

New ICF Core classesA new ICF-Core.mdl has been added. The ICF Core model defines base classes for managed element, configuration, setting, instrumentation, product, software feature, and hierarchical group. These classes inherit CMP core classes, and are used by ICIM core and ICF framework.

The ICF Core classes are described further in the EMC Smarts ICIM Reference.

Changes in Application Program Interfaces (APIs)Code based on Java, Perl, or C API needs to be modified to point to IP Manager and retested to check for other changes. The Perl Reference Guide provides more information.

Changes in sm_server --versionThe operating system (OS) name that the product is running on and OS version identifier have been added to the output of the sm_server --version command.

icim-core split The icim-core subsystem now depends on a new subsystem, called cmp-core. It contains four new classes which are now the super classes for ICIM-Core:

◆ CORE_ManagedObject

◆ CORE_Collection

◆ CORE_MetaObject

◆ CORE_AbstractIndication

In addition, the relationship "MemberOf" in CORE_MetaObject has been renamed to "MetaMemberOf".

relationshipset MetaMemberOf, CORE_Collection, MetaConsistsOf

The reverse relationship in CORE_Collection has been modified accordingly.

relationshipset MetaConsistsOf, CORE_MetaObject, MetaMemberOf

The new classes in the cmp-core subsystem are described in the ICIM Reference.

New features in ASAM Patches

For the latest enhancements provided by 3.2.0.x patches, consult the patch documentation on the EMC support website, https://support.emc.com.

Overview 15

Introduction

ArchitectureThe Adapter provides a link from the Alcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following EMC Smarts Domain Managers:

• IP Availability Manager (IP 7.0.3) or Network-Resource Manager (IP 8.1)

• MPLS Topology Manager

• Network Protocol Managers (Manager for BGP, Manager for OSPF, Manager for IS-IS)

• Multicast Manager

The Adapter sends topology queries by XML streams to the EMS, where they are processed. Near real-time events are passed from the EMS by Java Message Service (JMS), also in XML format, to the Adapter. Based on the events, the Adapter creates notifications in the Adapter Platform. The Adapter Platform creates notifications for display in the EMC Smarts Service Assurance Global Console.

Figure 1 on page 17 shows the event, alarm, and notification flow through the Adapter and the EMC Smarts Domain Managers and Adapter Platform.

IMPORTANT

The Adapter for Alcatel-Lucent 5620 SAM EMS does not communicate directly with network elements; rather, it imports information from the Alcatel-Lucent 5620 SAM EMS server only.


Introduction

Figure 1 Adapter for Alcatel-Lucent 5620 SAM EMS architecture

Note: Generally, the Adapter is not installed on the same host as the Alcatel-Lucent 5620 SAM EMS. Depending on deployment considerations, it may be installed on the same or different host as other EMC Smarts products.

Adapter Platform

Topology and events

Alarms

Physical and logical topology and non-alarm events

status subscription

Global Manager

Global Console

Alarm notifications

Topology and eventsTopology and events

Topology and events

Notifications for display


status subscription

Topology and events

Multicast Manager IP DomainManager


status subscription

Alcatel-Lucent 5620 SAM EMS Adapter

Alcatel-Lucent 5620 SAM EMS

Monitoring Server

Analysis Server

Topology Server

MPLS ManagerNPM Managers

OSPFIS-ISBGP

Topology and events

Topology

Architecture 17

Introduction

IP Availability Manager/Performance Manager

The Adapter supports full and incremental discovery of the IP network, importing Layer 2 and Layer 3 topology information from the Alcatel-Lucent 5620 SAM EMS server into the IP Availability Manager.

Note: In IP Manager Version 8.1, the Network-Resource Manager receives the topology information from the Adapter.

The Adapter also supports performance status information from the Alcatel-Lucent 5620 SAM EMS server on physical components such as router fans, memory, processors, and so on.

In addition, the IP Availability Manager may be configured to perform independent discovery of non-Alcatel-Lucent networks, providing that topology to the Domain Managers, which will create a cross-vendor topology.

MPLS Manager

The Adapter supports optional full and incremental discovery of the MPLS network, importing MPLS and VPN topology information from the Alcatel-Lucent 5620 SAM EMS server into the EMC Smarts MPLS Manager.

The MPLS Manager manages MPLS networks and virtual private routed networks (VPRNs), IP virtual private networks (IP VPNs), virtual leased lines (VLLs), and virtual private LAN services (VPLS). The MPLS Manager supports generic routing encapsulation (GRE) tunnels configured and provisioned over these virtual entities. The MPLS Manager provides mapping and correlation between the MPLS and the VPN domains, as well as between the MPLS/VPN domains and the underlying transport domain. This is accomplished by means of cross-domain correlation and cross-domain impact analysis.

Enhanced identification of Level 3 Virtual Private Network (VPN) IP addressesEach VPN includes IP addresses that are unique within that VPN. This can lead to VPN discovery issues when identical IP addresses overlap on the access interfaces between the VPN Provider Edge devices (PE) and the Customer Edge devices (CE).

Each VPN includes a single routeTargetId that uniquely identifies it. Routing within VPNs is managed by Virtual Routing and Forwarding tables (VRF) that track each routeTargetId within the network. PE devices, such as routers, use VRF tables to establish Layer 3 VPN paths through the MPLS network.

The Adapter appends the VPN routeTargetId to the configured name of each IP address within a VPN, uniquely identifying each IP address. The new identifier is in the following format:

IP-w.x.y.z/routeTargetId


Introduction

Network Protocol Manager for BGP

The Adapter supports optional full and incremental discovery of the Border Gateway Protocol (BGP) network, importing BGP topology information from the Alcatel-Lucent 5620 SAM EMS server into the EMC Smarts Network Protocol Manager for BGP. The Adapter does not support EBGP (External BGP) endpoints/sessions.

The Network Protocol Manager for BGP diagnoses connectivity failures for the BGP protocol. The Network Protocol Manager for BGP, working with the IP Availability Manager and the imported information for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers and monitors network devices running BGP services, diagnoses BGP-related failures, and reports the results of its analysis to the Global Manager. The Network Protocol Manager for BGP also detects common configuration problems that occur when deploying and maintaining the routing infrastructure.

Network Protocol Manager for OSPF

The Adapter supports optional full and incremental discovery of the Open Shortest Path First (OSPF) network, importing OSPF topology information from the Alcatel-Lucent 5620 SAM EMS server into the EMC Smarts Network Protocol Manager for OSPF.

The Network Protocol Manager for OSPF diagnoses connectivity failures for the OSPF protocol.The Network Protocol Manager for OSPF, working with the IP Availability Manager and the imported information for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers and monitors network devices running OSPF services, diagnoses OSPF-related failures, and reports the results of its analysis to the Global Manager. The Network Protocol Manager for OSPF also detects common configuration problems that occur when deploying and maintaining the routing infrastructure.

Network Protocol Manager for IS-IS

The Adapter supports optional full and incremental discovery of the Intermediate System-Intermediate System (IS-IS) network, importing IS-IS topology information from the Alcatel-Lucent 5620 SAM EMS server into the EMC Smarts Network Protocol Manager for IS-IS.

The Network Protocol Manager for IS-IS diagnoses connectivity failures for the IS-IS protocol. The Network Protocol Manager for IS-IS, working with the IP Availability Manager and the imported information for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers and monitors network devices running IS-IS services, diagnoses IS-IS-related failures, and reports the results of its analysis to the Global Manager. The Network Protocol Manager for IS-IS also detects common configuration problems that occur when deploying and maintaining the routing infrastructure.

Architecture 19

Introduction

Multicast Manager

The Adapter supports optional full and incremental discovery of the following IP multicast-related entities:

• Internet Group Management Protocol (IGMP)

• Protocol Independent Multicast (PIM)

The Multicast Manager diagnoses connectivity failures for the Internet Group Management Protocol (IGMP). The Multicast Manager works with either the IP Availability Manager or the imported information for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server. The Multicast Manager discovers and monitors network devices running multicast services, diagnoses multicast-related failures, and reports alarms received and the results of its analysis to the Global Manager. The Multicast Manager also detects common configuration problems that occur when deploying and maintaining the multicast infrastructure.

Adapter Platform

The EMC Smarts Adapter Platform imports alarms and event information from the Adapter for Alcatel-Lucent 5620 SAM EMS and imports network topology information from the IP Availability Manager.

The Adapter reads and processes events, such as additions and deletions of devices, which it exports to the Global Manager. The Adapter supports both initial synchronization of historical events and ongoing handling of asynchronous events. In addition, the Adapter processes alarms and then creates or deletes notifications in the Adapter Platform, which are then forwarded to the Global Manager. The Adapter maps alarms to notifications for display in the Notification Log of the Global Console. To process an alarm, the Adapter maps the Alarm ID, Type, and Cause parameters to table entries containing text for the notification.

DiscoveryThe Adapter for Alcatel-Lucent 5620 SAM EMS does not perform SNMP polling of the network element through a traditional discovery process; rather, the Adapter gets all topology information from the Alcatel-Lucent 5620 SAM EMS database.

The Adapter provides the following discovery options for initiating discovery and ensuring that the topology is correctly maintained:

• Full discovery—Manually initiated or scheduled rediscovery for all topology elements. This process examines all Alcatel-Lucent 5620 SAM EMS physical objects and adds or updates the topology in all appropriate Domain Managers at the same time.

• Incremental additions/deletions/changes—The Adapter receives updates to the topology of the Alcatel-Lucent 5620 SAM EMS. Incrementally applied status updates are applied to the appropriate Domain Manager and automatically propagated to other Domain Managers that rely on that information. This is sometimes referred to as incremental discovery.

• Partial rediscovery—Manually initiated or scheduled rediscovery for selected topology elements such as a single router and its elements, or service (logical) items only. This process updates the topology in the appropriate Domain Managers at the same time.


Introduction

Full discovery

The Alcatel-Lucent 5620 SAM EMS pushes JMS messages to the Adapter using an XML/SOAP connection. The Adapter transforms the XML data into EMC Smarts topological objects and values, which it pushes to the various Domain Managers. In addition, the EMS provides state changes that the Adapter processes; the Adapter does not maintain topology state itself.

Incremental discovery

For alarms and events, the 5620 SAM EMS pushes JMS messages to the Adapter. The Adapter transforms the XML data into data that it pushes to the various analysis servers to update object status, as follows:

• Alarms to the Adapter Platform

• Events to the various Domain Managers as topology creation, deletion, or change events.

Physical and logical discovery

Discovery is broken into two phases: physical and logical. For physical discovery, there is a direct correlation between Alcatel-Lucent database objects and the EMC Smarts topology elements to which they are mapped. Logical discovery is more complex, because the Adapter must query multiple Alcatel-Lucent 5620 SAM EMS database structures in order to determine the logical relationships.

The Adapter discovers the following topology elements:

• Physical topology—Routers, Switches, BaseCards, DaughterCards, Chassis, IPs, Network Connections, IPNetworks, MACs, and Interfaces

• Logical topology:

• IP Availability Manager—NetworkAdapterRedundancyGroups (from Alcatel-Lucent 5620 SAM EMS Link Aggregation Groups)

• MPLS—VPLS, VLLs, GREs, LDPs, VPNs, VRFs, MPLSServices, LSPs, LSPHops, and ForwarderEndpoints

• NPM-BGP—Confederation, AutonomousSystem, BGPProtocolEndpoint, BGPSession, BGPService, BGPCluster

• NPM-OSPF—OSPFArea, OSPFAreaConfiguration, OSPFService, OSPFNetwork, OSPFNeighborEndpoint, OSPFVirtualNeighborEndpoint, OSPFInterface, OSPFVirtualInterface, OSPFNeighborRelationship, OSPFVirtualLink

• NPM-ISIS—ISISAdjacency, ISISArea, ISISInterface, ISISNeighborEndpoint, ISISNetwork, ISISService

• Multicast—IGMPInterface, IGMPNetwork, MulticastGroup, MulticastService, MulticastSource, MulticastTree, PIMInterface, PIMStarG, PIMSourceG, PIMHop

The Adapter instantiates physical topology into the IP Availability Manager, physical and logical topology into the MPLS Manager, the NPM Managers (BGP, OSPF, and IS-IS), and the Multicast Manager.

Discovery 21

Introduction

For detailed information about the mapping and filtering of 5620 SAM EMS elements to EMC Smarts objects, the following appendices are available:

• “Mapping of Smarts objects and SAM-O Objects” on page 91

• “Mapping of SAM-O Objects and Smarts Notifications” on page 111

Discovery of connections

The Adapter creates connections between Alcatel-Lucent 5620 SAM EMS NPM topology elements as follows:

A Cable is instantiated for:

• Each pair of point-to-point OSPF or ISIS neighbors

• Each Physical Link on the 5620 SAM EMS. A Physical Link on the EMS can either be manually created by the operator or automatically instantiated via the LLDP (Link Layer Discovery Protocol) run at the port level.

A NetworkConnection is instantiated for:

• Each pair of OSPF or ISIS neighbors

• Each pair of IP addresses in 30-bit or 31-bit subnets, if the IP/AM WANLink driver is called.

Note: The WANLink driver is called by default in the IP Availability Manager 8.1 or above. “Configuring the WANLink driver” on page 39 provides instructions for configuring the Adapter for the WANLink driver in an installation that includes the IP Availability Manager 7.0.3.

Event processing

The Adapter updates the status of the 5620 SAM EMS elements, based on a filtered set of events received from the 5620 SAM EMS through the SAM-O interface using a JMS connection, and creates notifications.

For detailed information about JMS configuration, the following is available:

• “Configuring JMS message filtering” on page 41

• “Configuring alarm processing” on page 43

The Adapter transforms the XML data into EMC Smarts topological objects and values, which it pushes to the various analysis servers. In addition, the EMS provides state changes that the Adapter processes, but the Adapter does not maintain topology state itself.

Adapter Platform alarms

When the Adapter loses connectivity with the JMS channel, the Adapter begins an EMS reconnection recovery phase.

The Adapter sends an alarm to the Adapter Platform, giving Operations a visual indication that a major Adapter failure has occurred.

When the adapter reconnects to the EMS, the Adapter Platform alarm clears automatically.


Introduction

Multi-vendor topology supportThe Adapter discovers Alcatel-Lucent devices and creates a topology of the network managed by the Alcatel-Lucent 5620 SAM EMS.

The Adapter discovers the Alcatel-Lucent topology through the Alcatel-Lucent 5620 SAM EMS and populates this topology in the Managers such as the IP Availability Manager, MPLS Manager, and the NPM Managers. In addition, the Domain Managers discover the non-Alcatel-Lucent entities in the network.

The Managers individually handle post-processing to stitch together the physical and logical topologies from both the EMS and other sources in a heterogeneous network. Figure 2 on page 23 illustrates this architecture. Post-processing creates objects such as a NetworkConnection between an Alcatel-Lucent element and a non-Alcatel-Lucent element.

Figure 2 Architecture for multi-vendor topology support

Note: The Adapter does not provide multi-vendor support for the Multicast Manager.

Fault toleranceIf the Alcatel-Lucent 5620 SAM EMS fails over, the Adapter is designed to connect to the newly activated EMS.

Adapter for Alcatel-Lucent 5620 SAM EMS

Alcatel-Lucent 5620 SAM EMS

Domain ManagersIP, MPLS, NPM

Non-Alcatel-Lucent topologySNMP/CLI polling

Post-processing forcross-vendor topology stitching

Cisco/Juniper Network Alcatel-Lucent Network

PushedAlcatel-Lucent topology

Multi-vendor topology support 23

Introduction

TroubleshootingThe following information is available in “Troubleshooting” on page 137:

• Using pre-defined ASL scripts to troubleshoot Adapter functioning.

• Using informational entries in the ASA.log that provide a trail of events reported by the Alcatel-Lucent 5620 SAM EMS or showing progress of a discovery.

• Querying the Alcatel-Lucent 5620 SAM EMS database for object data, in the event that the information is not directly available from the EMS user interface.


CHAPTER 2Configuring the Adapter Deployment

This chapter explains how to configure the Adapter for Alcatel-Lucent 5620 SAM EMS deployment. It includes procedures for configuring a deployment that includes the EMC Smarts MPLS Manager, EMC Smarts Network Protocol Manager, and the EMC Smarts Multicast Manager. Your deployment may include some or all of these products. Please ignore any procedures that do not apply to your deployment. In addition, this chapter contains configuration information for the Alcatel-Lucent SAM-O client and EMS.


• Methods for modifying user configuration parameters............................................. 26• Granting Windows 2008 UAC write permissions ...................................................... 27• Configuring the Alcatel-Lucent 5620 SAM EMS server.............................................. 28• Copying required .jar files........................................................................................ 30• Configuring the Adapter .......................................................................................... 30• Configuring JMS message filtering ........................................................................... 41• Configuring alarm processing .................................................................................. 43• Configuring Domain Managers ................................................................................ 52• Additional configuration for NPM Managers ............................................................ 59• Additional configuration for the Multicast Manager ................................................. 60• External polling auto-configuration.......................................................................... 61• Replacing existing Domain Manager repositories..................................................... 62• Rolling the Adapter Log ........................................................................................... 62• Device filtering (optional) ........................................................................................ 63

You may encounter some new terminology when performing configuration tasks. For example, you may see references to the ASA or ASAM (Adapter for Alcatel-Lucent 5620 SAM EMS), SAM (Global Manager), InCharge (EMC Smarts software), SAM-O (Alcatel-Lucent Service Aware Manager - Open Interface).

Configuring the Adapter Deployment 25

Configuring the Adapter Deployment

Methods for modifying user configuration parametersThere are two methods for modifying user configuration parameters:

• Use the Global console to edit the user configuration files and modify configuration parameters.

• Use the command line to issue the dmctl command to temporarily modify configuration parameters when the Adapter is running.

Some configuration changes can only be made by modifying the parameter settings in the configuration files and then restarting the Adapter. Every time the Adapter starts, it sets its configurations in accordance to the settings in the user (and other) configuration files.

Using the Global Console

EMC Smarts provides the sm_edit utility to ensure that modified files are always saved to the appropriate local area and that original copies of the files remain unchanged.

To invoke the sm_edit utility from the command line, go to the BASEDIR/smarts/bin directory and specify the path and the name of the file (relative to the BASEDIR/smarts directory) that you want to edit. For example,

sm_edit conf/alcatel-sam/emcConfig.import

opens a local copy of the emcConfig.import file in BASEDIR/smarts/local/conf/alcatel-sam (or an original copy of the emcConfig.import file in BASEDIR/smarts/conf/alcatel-sam if no local copy exists) in a text editor and saves the modified version of the file to the BASEDIR/smarts/local/conf/alcatel-sam directory.

You can use the sm_edit utility to edit any text file (configuration file, rule set file, tool script, template) in the BASEDIR/smarts (or BASEDIR/smarts/local) directory. Because sm_edit assumes a starting point of BASEDIR/smarts, you specify the path and the name of the text file beginning with the directory name (conf, rules, script) under the BASEDIR/smarts directory.

The EMC Smarts System Administration Guide provides additional information about the sm_edit utility.

In addition, “Granting Windows 2008 UAC write permissions” on page 27 provides information about permissions for Windows Server 2008.

Note: Original versions of files may be changed or updated as part of an EMC Smarts software upgrade. However, files located in the BASEDIR/smarts/local directory are retained during an upgrade.

Using the command line

You can use the following dmctl command to change the value of any basic-type attribute (string, boolean, integer, float, and so on) defined in an ICIM class:

dmctl -s <Domain Manager instance name> put <class::instance::attribute> <value>

Upon issuing a dmctl command, you will be prompted for a username and password. Respond with your administration account (for example, admin and changeme).



Using the dmctl command to modify a parameter setting is temporary in the following sense: When the Domain Manager is restarted, it reads the original parameter value in the configuration file. To make the change permanent, use the sm_edit utility to change the parameter setting in the configuration file.

Granting Windows 2008 UAC write permissionsWith Windows Server 2008, User Account Control (UAC) does not allow editing configuration files unless specific permissions are granted. This does not need to be done if:

• UAC is disabled, or

• The built-in administrator is performing the configuration

Grant permissions in both the \local\conf and \local\conf\alcatel-sam directories.

local\conf directory

After the installation, any member of the administration group that performs configuration must give themselves write permission to the following files in the BASEDIR\smarts\local\conf directory:

• brokerConnect.conf

• clientConnect.conf

• serverConnect.conf

• runcmd_env.sh files

Note: The files in BASEDIR\smarts\conf must remain as installed. Use sm_edit to edit configuration files as described in “Using the Global Console” on page 26.An administration group user must also have write permission granted for any other files that need to be edited for configuration.

To grant Write permission:

1. Go to the \local\conf directory in the Adapter installation area.

cd BASEDIR\smarts\local\conf

2. Right click on one of the files.

3. From the menu select Properties.

4. Click the Security tab

5. Click the Advanced button

6. In the Advanced dialog window, add Write permission.

7. Click the OK button.

Repeat Steps 2 - 7 for each file in the list above.

Granting Windows 2008 UAC write permissions 27


local\conf\alcatel-sam directory

Follow steps 1-7 to provide Write permission for the following files in the BASEDIR\smarts\local\conf\alcatel-sam directory:

• emsConfig.import

• ASA-Filter.conf

• ASA-Alarm.conf

• AggregateAlarms

• DevicesNotInEffect.conf

Configuring the Alcatel-Lucent 5620 SAM EMS serverConfigure the Alcatel-Lucent 5620 SAM EMS server to create a user with the required Alcatel-Lucent 5620 SAM EMS OSS Management permission to allow access to the SAM-O interface by the Adapter. In addition, configure polling for statistics.

Note: Your installation must include a license for the Alcatel-Lucent 5620 SAM-O interface in addition to the license for the Alcatel-Lucent 5620 SAM EMS.

Creating a user for SAM-O interface access

In the Alcatel-Lucent 5620 SAM EMS GUI administrative interface, create a user. Follow the procedures in the EMS User Guide.

IMPORTANT

The user password should be the same as that in the Adapter configuration file, EMSConfig.import, for the parameters EMSInstance and JmsUser, as described in Table 1 on page 32. One password instance is encrypted and the other one is not.

Configuring statistics polling

To configure the Alcatel-Lucent 5620 SAM EMS server to enable collection of statistics for MPLS root cause analysis, do the following:

• Enable the Events policy.

• Enable a MIB Administrative State entry.

• Set the appropriate ports for a firewall, if present.

Note: This section provides an overview of the procedures to configure the Alcatel-Lucent 5620 SAM EMS server. The Alcatel-Lucent 5620 Service Aware Manager User Guide provides detailed instructions.



Enabling the Events policyEnable the Events policy, allowing the Adapter to collect VRF statistics:

1. From the Alcatel-Lucent 5620 SAM EMS GUI, select Tools Menu, and then select Log Records.

2. In the Manage Log Records window, modify the filter to generate a list of statistical data:

a. Specify the Log Class parameter by selecting RouteStats from the menu of log classes.

b. Specify the Log Type by choosing Log Policy.

c. Click Search. The list of statistics log records for that class appears.

3. Select Events to enable.

Enabling a MIB Administrative State entryEnable collecting of the RoutesInVrf statistics:

1. From the Alcatel-Lucent 5620 SAM EMS GUI, select Tools >Statistics >MIB Policies.

2. Modify an existing statistics MIB policy, if necessary:

a. In the script pop-up window, highlight the NE MIB Statistics Policy (snmp), and click Search.

b. Highlight the policy and click Properties.

c. Click MIB Entry Policies.

d. Locate the TIMETRA-VRTR-MIB vRtrStatEntry entries. (You can sort the entries by MIB Name.) Each of these entries should show the value Up. If any entry does not, click Properties to change the value.

– In the dialog box, locate the Administrative State pulldown menu, and select Up for each entry.

– Click OK to save the changes.

e. Close the window.

3. Resync all routers. For assistance, check with your Alcatel-Lucent 5620 SAM EMS administrator.

Setting the appropriate ports for a firewallIf there is a firewall between the Alcatel-Lucent 5620 SAM EMS and the Adapter, ensure that all of the following ports are open:

• TCP 1096–1100

• TCP 4444–4447

• TCP 8080

• TCP 8443

• TCP 8093

• TCP 8094

Configuring the Alcatel-Lucent 5620 SAM EMS server 29


The Alcatel-Lucent 5620 SAM EMS planning guide provides more information.

Copying required .jar filesYour installation requires the copying of some .jar files from the Alcatel-Lucent 5620 SAM EMS server and the installation DVD. The steps vary with the version of the Alcatel-Lucent 5620 SAM EMS.

IMPORTANT

If the version of the Alcatel-Lucent 5620 SAM EMS has been upgraded since your last Adapter installation, you must copy the new samOss.jar file in BASEDIR/smarts/local/classes before starting the Adapter.

Copying required .jar files for EMS 6.1 and 7.0

This version requires the samOss.jar file that is part of the Alcatel-Lucent 5620 SAM EMS installation.

1. Locate the following file:

../5620sam/server/nms/integrations/SAM_O/samOss.jar file

2. Copy the samOss.jar file and paste it to the Adapter host at:

ASAM_BASEDIR/smarts/local/classes

Configuring the AdapterConfigure the Adapter to use EMC Smarts Domain Managers. In addition, configure parameters that support communications between the Adapter and the Domain Managers.

IMPORTANT

No prior version of the emsConfig.import file that may have been previously installed is compatible with this version of the Adapter. You may wish to save the file in another location so you can refer to information such as network addresses.

Note: When configuring the Adapter, you must include the MD-5-hashed version of the password for the Alcatel-Lucent 5620 SAM EMS. “Generating an MD-5-hashed password” on page 38 provides instructions.



Note: By default, generic commands are provided for a UNIX platform. When entering commands, please adjust for your local practice. For example, When entering a command in a UNIX environment, place “./” directly in front of the command (with no space between it and the command). For example:./sm_edit conf/alcatel-sam/emsConfig.importWhen entering a command in a Windows environment, do not use “./”, but change the direction of any directory path slashes. For example:sm_edit conf\alcatel-sam\emsConfig.import

Editing the emsConfig.import file

1. At ASAM_BASEDIR/smarts/bin, enter the following command:

sm_edit conf/alcatel-sam/emsConfig.import

2. Specify values for the parameters listed in Table 1 on page 32, as appropriate for your deployment.

Note: This procedure assumes that you are configuring a deployment that includes the IP Availability Manager, Adapter Platform, MPLS Manager, Multicast Manager, and NPM Managers for BGP, OSPF, and IS-IS. If you wish to leave any of these out of your deployment, configure one or more of these character strings as blank, as described in “Preventing access to an optional server” on page 38.

3. Save the file.

“Understanding the sm_edit Utility” on page 145 provides more information.

emsConfig.import parameters

When configuring the parameters listed in Table 1 on page 32, configure server names for the following:

• IP Availability Manager (AMServerName)

• Adapter Platform (OIServerName)

• Adapter server name (ASAServerName)

The MPLS, Multicast, BGP, OSPF, and IS-IS servers are optional. “Preventing access to an optional server” on page 38 provides important information.

Configuring the Adapter 31


Table 1 Adapter configuration parameters (page 1 of 7)

Parameter Type Description Values

EMS/JMS connection configuration parameters

EMSVersion string Specifies the EMS version Can be 6.1-12.x

EmsInstance 4 strings Specifies: • IP address where the

Alcatel-Lucent 5620 SAM EMS server is running

• Alcatel-Lucent 5620 SAM EMS server port number

• user login• user password (must be

MD-5-hashed)

• An IP address• The port number, usually 8080• The Alcatel-Lucent 5620 SAM

EMS user login name in clear text

• The MD-5-hashed version of the password described in Step 7 of “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28.

“Generating an MD-5-hashed password” on page 38 provides important instructions.NOTE: This user name must be configured with OSS Management privileges, as described in “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28.NOTE: For assistance with Alcatel-Lucent 5620 SAM EMS user names and passwords, consult your Alcatel-Lucent administrator.

AltEmsInstance 4 strings For the standby Alcatel-Lucent 5620 SAM EMS server, specifies:• IP address where the

Alcatel-Lucent 5620 SAM EMS server is running

• Alcatel-Lucent 5620 SAM EMS server port number

• user login• user password (must be

MD-5-hashed)

• An IP address• The port number, usually 8080• The Alcatel-Lucent 5620 SAM

EMS user login name in clear text

• The MD-5-hashed version of the password described in Step 7 of “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28.

“Generating an MD-5-hashed password” on page 38 provides important instructions.NOTE; If there is no standby Alcatel-Lucent 5620 SAM EMS server, enter the same values as for EmsInstance.NOTE: For assistance with Alcatel-Lucent 5620 SAM EMS user names and passwords, consult your Alcatel-Lucent administrator.



JmsPort string Specifies the URL:port where the SAM-O accepts requests to monitor asynchronous events.Check with your 5620 SAM EMS administrators when setting the value for JmsPort and AltJmsPort. If it is improperly set, the Adapter will not be able to connect to the alternate 5620 SAM EMS server when a switchover occurs.

Must be resolvable from the machine where the adapter is running.NOTE: The Alcatel-Lucent 5620 SAM EMS behaves differently based on which JMS Ports are selected. If the 5620 SAM EMS is running in • Standalone mode—Use port

1099.• Redundant mode for High

Availability—Use port 1100. If necessary, check with your Alcatel-Lucent 5620 SAM EMS administrator to determine the mode.

AltJmsPort string Specifies the URL:port on the standby Alcatel-Lucent 5620 SAM EMS server where the SAM-O accepts requests to monitor asynchronous events.Check with your 5620 SAM EMS administrators when setting the value for JmsPort and AltJmsPort. If it is improperly set, the Adapter will not be able to connect to the alternate 5620 SAM EMS server when a switchover occurs.

Must be resolvable from the machine where the adapter is running.NOTE: The Alcatel-Lucent 5620 SAM EMS behaves differently based on which JMS Ports are selected. If the 5620 SAM EMS is running in • Standalone mode—Use port

1099.• Redundant mode for High

Availability—Use port 1100. If necessary, check with your Alcatel-Lucent 5620 SAM EMS administrator to determine the mode.

ClientId string The identifier the Adapter is to use when making XML requests to Alcatel-Lucent 5620 SAM EMS.

Recommended to be of format: smarts@12345

JmsUniqueId string For durable JMS connections, this ID identifies the Adapter to the Alcatel-Lucent 5620 SAM EMS server.

Recommended to be of format: smarts@12345NOTE: For non-durable JMS connections, leave this field blank.

JmsUser string JMS connections require valid user names and passwords. This field specifies the user name to be used by the Adapter.

Must match the user name configured on the Alcatel-Lucent 5620 SAM EMS server, as provided by your Alcatel-Lucent administrator. Step 7 of “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28 provides instructions.NOTE: This user name must be configured with OSS Management privileges, as described in “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28.NOTE: For assistance with Alcatel-Lucent 5620 SAM EMS user names and passwords, consult your Alcatel-Lucent administrator.





JmsPassword string JMS connections require valid user names and passwords. This field specifies the password to be used by the Adapter.

Must match the password configured on the Alcatel-Lucent 5620 SAM EMS server, as provided by your Alcatel-Lucent administrator. Step 7 of “Configuring the Alcatel-Lucent 5620 SAM EMS server” on page 28 provides instructions.This must be the clear text version, not the md5-hashed version.NOTE: For assistance with Alcatel-Lucent 5620 SAM EMS user names and passwords, consult your Alcatel-Lucent administrator.

JMS reconnection management

EMSReconnectInterval integer Specifies the interval at which the Adapter tries to reconnect to the EMS server. This value is in seconds.

Default is 60If set to zero, the Adapter does not automatically reconnect to the EMS, so you must initiate reconnection manually, as described in “restartJMSConnector.asl” on page 142.

JmsConnectionMode string Specifies whether the JMS server sends new messages before earlier messages have been acknowledged. There are two modes:• DUPS

(DUPS_OK_ACKNOWLEDGE): JMS server may send new messages before earlier messages are acknowledged (this mode is valid only for EMS 6.1 or later)

• AUTO (AUTO_ACKNOWLEDGE): JMS server will not send a new message until message is acknowledged

Default is AUTO

MissedKeepAliveMessages integer Specifies the number of consecutive KeepAlive messages that are missed to determine the EMS Connection to have failed.

Default is 3

RestartTimeAfterTerminateClient integer Specifies the time interval at which the adapter will try to reconnect to the EMS after receiving the TerminateClientSession message from the EMS.

The time is specified in seconds and defaults to 600. (10 minutes)

Discovery options





DiscoveryOnStartup boolean This parameter controls whether a full discovery will be performed immediately after startup.

TRUE or FALSEDefault is FALSE.NOTE: Alcatel-Lucent does not recommend that you set this parameter to TRUE. If the parameter is set to TRUE, the Adapter will start a full discovery upon startup. After the repositories are populated by a discovery, you should set this parameter to FALSE for future restarts.

DiscoveryOnJmsLoss boolean This parameter controls whether SAM-O discovery will be initiated automatically when JMS events are missed or when the 5620 SAM server switches.

TRUE or FALSE. Default is TRUE.NOTE: For large topologies, Alcatel-Lucent recommends that you set this to FALSE.

FibDiscoveryEnabled boolean This parameter controls whether discovery of FIB will be performed.WARNING: Enabling this in a large-scale network could increase discovery time drastically.

TRUE or FALSE. Default is FALSE.

IGMPNetworkDiscoveryEnabled boolean This parameter controls whether discovery of IGMPNetwork will be performed.Please edit the file <SM_HOME>/conf/alcatel-sam/ASA-Filter.conf and uncomment the line containing "igmp.IfGroup" if IGMPNetwork discovery is enabled.WARNING: Enabling this in a large-scale network could increase Multicast discovery time drastically.


MulticastTreeDiscoveryEnabled boolean This parameter controls whether discovery will be performed to construct Multicast Tree components such as (S,G), (*,G) and PIM Hops.WARNING: Enabling this in a large-scale network could increase Multicast post-processing time drastically.






Create7210NetworkConnections boolean This parameter controls whether the adapter creates network connections based on /30 and /31 IP addresses in 7210 SAS-E Switches. Note: When setting this parameter to TRUE, set CreateIESSAPs and CreateVPRNSAPs to TRUE also.


CreateIESSAPs boolean This parameter controls whether Service Access Point objects for IES services will be discovered.


CreateVLLSAPs boolean This parameter controls whether Service Access Point objects for VLL services will be discovered.


CreateVPLSSAPs boolean This parameter controls whether Service Access Point objects for VPLS services will be discovered.


CreateVPRNSAPs boolean This parameter controls whether Service Access Point objects for VPRN services will be discovered.

TRUE or FALSE. Default is TRUE.

UnmanageWhenInMaintenance boolean This parameter controls if the IsManaged attribute will be set to false when the topology is in maintenance mode (olcState == 1).


VPLSRTPrefix integer The adapter will use this prefix to create RouteTargets for each VPLS This parameter is required to be distinct for each adapter in a multi- adapter environment. In addition, it is also highly recommended this value is chosen such that the resulting RouteTarget, which is formed by combining this parameter with the VPLS service component id (or service manager id), will not collide with RouteTargets of VPRN VPN.

Default is 9999.

Domain Manager names

ASAServerName string Name of the Adapter for Alcatel-Lucent 5620 SAM EMS server

Default, ASAM

AMServerName string Name of the EMC Smarts IP Availability Manager serverNOTE: This server is mandatory.

Default, INCHARGE-AM





OIServerName string Name of the EMC Smarts Adapter Platform ServerNOTE: This server is mandatory.

Default, INCHARGE-OI

MPLSServerName string Name of the EMC Smarts MPLS Manager server

Default, INCHARGE- MPLS-TOPOLOGY“Preventing access to an optional server” on page 38 provides important information.

BGPServerName string Name of the EMC Smarts Network Protocol Manager for BGP server

Default, INCHARGE-BGP“Preventing access to an optional server” on page 38 provides important information.

OSPFServerName string Name of the EMC Smarts Network Protocol Manager for OSPF server.

Default, INCHARGE-OSPF“Preventing access to an optional server” on page 38 provides important information.

ISISServerName string Name of the EMC Smarts Network Protocol Manager for IS-IS

Default, INCHARGE-ISIS“Preventing access to an optional server” on page 38 provides important information.

MCASTServerName string Name of the EMC Smarts Multicast Manager server

Default, INCHARGE-MCAST“Preventing access to an optional server” on page 38 provides important information.

Domain Manager reconfiguration parameters

ReconfigureDelayTime integer Determines how long the adapter initially delays before invoking a reconfigureAndWait on a backend EMC Smarts analysis server. Running a reconfiguration too often can cause performance issues on the backend servers. Certain processes inside the Adapter require a reconfigure to take place before processes can run.

This time is specified in seconds and defaults to 180 seconds (3 minutes).

ReconfigureSlidingWindow integer Determines how long the Adapter waits after ReconfigureDelayTime for a quiet period. This parameter is used to slide the delay forward in tiny increments when topology changes are still rapidly being processed by the adapter.

This time is specified in seconds and defaults to 10 seconds.

MaximumReconfigureDelayTime integer Determines the maximum delay the Adapter will wait before invoking a reconfigureAndWait on a backend EMC Smarts analysis server. This value should be longer or the same as ReconfigureDelayTime.

The time is specified in seconds and defaults to 210 seconds (3.5 minutes).





Preventing access to an optional server

To configure the Adapter so that it does not attempt to access an optional server, configure the parameter as null with empty quotation marks. For example,

Default:

MCASTServerName = "INCHARGE-MCAST"

Configured so that the Adapter does not attempt to access the Multicast server:

MCASTServerName = ""

Generating an MD-5-hashed password

Create an MD-5-hashed version of the password for each Alcatel-Lucent 5620 SAM EMS server. Using a clear-text password may suspend the account. To convert a clear-text password string:

1. Open a command tool or shell on the Alcatel-Lucent 5620 SAM EMS server.

Raw Alcatel-Lucent 5620 SAM EMS alarm handling options

ClearAlarmOnDelete boolean When SAM-O deletes alarms, this parameter controls whether the corresponding notifications should be cleared.

TRUE or FALSE. Default is TRUE.NOTE: This parameter is in effect only when ArchiveOnDelete is set to TRUE.

ArchiveOnDelete boolean When SAM-O deletes alarms, this parameter controls whether the corresponding notifications should be archived.


Router Down analysis enhancement parameters

NeighborDownThresholdForRouterDown

integer Specifies the threshold percentage of NPM neighbors of a router that are experiencing SnmpReachability problems in order to conclude that this router is functionally down.

This is a percentage value and defaults to 80. If this value is set to 0, then a router down event will be generated whenever a SnmpReachabilityProblem (Alarm 243) is received from the EMS.

RouterDownCheckInterval integer Specifies the time interval in seconds at which the router down verification procedure runs.

Default is 60

Miscellaneous configuration parameters

LogLevel integer Data logged at this level or more important is kept, other data is discarded.

• Level 1 will log severe messages only.

• Level 2 will log warnings and severe messages.

• Level 3 will log informational messages, warnings, and severe messages.

• Level 7 will log everything (including verbose internal messages).





2. Go to the <install directory>/nms/bin directory, where <install directory> is the server installation directory.

3. Convert the password, as follows:

md5hash.bash <password string>

where <password string> is the password that you want to convert to MD5hash format.

4. Copy and paste the resulting MD5-hashed password string to the password area of the EmsInstance and AltEmsInstance fields of the emsConfig.import file.

Changing the SM_LIBPATH value (Windows platform only)

The Adapter software includes a UNIX-specific default value for the SM_LIBPATH variable in the runcmd_env.sh file. If your deployment is in a UNIX environment, no change is needed.

If your deployment is in a Windows environment, change this value:

1. At ASAM_BASEDIR\smarts\bin, enter the following command:

sm_edit conf\runcmd_env.sh

2. Change the value for the SM_LIBPATH variable, as follows:

SM_LIBPATH=C:\InCharge\ASAM\smarts\jre\lib

3. Save the runcmd_env.sh file and close it.

4. Restart the server for the environmental variable to take effect.

Configuring the WANLink driver

The WANLink driver allows NetworkConnections to be created for each pair of interfaces in which IP addresses are in the same /30 or /31 subnet. Configuration differs between IP Manager Versions 7.0.3 and 8.1 as shown in the following examples.

Note: For both IP 7.0.3 and 8.1 add these additional switch patterns in conf/discovery/tpmgr-param.conf: .1.3.6.1.4.1.6527.1.6.*|.1.3.6.1.4.1.738.1.5.100.1.1.19.*

For IP Manager Version 7.0.3

1. Uncomment the following line in the ipPostProcessors.conf file in the Adapter:

#Post-Processor-WANLink-Driver



2. Edit the <IP>/smarts/local/conf/discovery/tpmgr-param.conf file in the IP Availability Manager to add the switch patterns:

Layer3SwitchPattern .1.3.6.1.4.1.9.1.400|.1.3.6.1.4.1.9.5.44|.1.3.6.1.4.1.4641.1.*|.1.3.6.1.4.1.5567.1.1.*

change to

Layer3SwitchPattern .1.3.6.1.4.1.9.1.400|.1.3.6.1.4.1.9.5.44|.1.3.6.1.4.1.4641.1.*|.1.3.6.1.4.1.5567.1.1.*|.1.3.6.1.4.1.6527.1.6.*|.1.3.6.1.4.1.738.1.5.100.1.1.19.*

For IP Manager Version 8.1

The WANLink driver is enabled by default in IP Manager Version 8.1 however you must edit the tpmgr-param.conf file to add the switch patterns:

1. Edit the <IP>/smarts/local/conf/discovery/tpmgr-param.conf file in the IP Availability Manager. Change the following line in tpmgr-param.conf:

Layer3SwitchPattern.1.3.6.1.4.1.9.1.282|.1.3.6.1.4.1.9.1.283|.1.3.6.1.4.1.9.1.298|.1.3.6.1.4.1.9.1.400|.1.3.6.1.4.1.9.1.449|.1.3.6.1.4.1.9.1.501|.1.3.6.1.4.1.9.1.516|.1.3.6.1.4.1.9.1.519|.1.3.6.1.4.1.9.1.534|.1.3.6.1.4.1.9.1.537|.1.3.6.1.4.1.9.1.563|.1.3.6.1.4.1.9.1.615|.1.3.6.1.4.1.9.1.626|.1.3.6.1.4.1.9.1.634|.1.3.6.1.4.1.9.1.657|.1.3.6.1.4.1.9.1.659|.1.3.6.1.4.1.9.5.44|.1.3.6.1.4.1.2272.31|.1.3.6.1.4.1.4641.1.*|.1.3.6.1.4.1.5567.1.1.*|.1.3.6.1.4.1.5624.2.1.53|.1.3.6.1.4.1.5624.2.1.79|.1.3.6.1.4.1.5624.2.1.80

change to

Layer3SwitchPattern.1.3.6.1.4.1.9.1.282|.1.3.6.1.4.1.9.1.283|.1.3.6.1.4.1.9.1.298|.1.3.6.1.4.1.9.1.400|.1.3.6.1.4.1.9.1.449|.1.3.6.1.4.1.9.1.501|.1.3.6.1.4.1.9.1.516|.1.3.6.1.4.1.9.1.519|.1.3.6.1.4.1.9.1.534|.1.3.6.1.4.1.9.1.537|.1.3.6.1.4.1.9.1.563|.1.3.6.1.4.1.9.1.615|.1.3.6.1.4.1.9.1.626|.1.3.6.1.4.1.9.1.634|.1.3.6.1.4.1.9.1.657|.1.3.6.1.4.1.9.1.659|.1.3.6.1.4.1.9.5.44|.1.3.6.1.4.1.2272.31|.1.3.6.1.4.1.4641.1.*|.1.3.6.1.4.1.5567.1.1.*|.1.3.6.1.4.1.5624.2.1.53|.1.3.6.1.4.1.5624.2.1.79|.1.3.6.1.4.1.5624.2.1.80|.1.3.6.1.4.1.6527.1.6.*|.1.3.6.1.4.1.738.1.5.100.1.1.19.*



Configuring JMS message filteringConfigure the Adapter for Alcatel-Lucent 5620 SAM EMS to use either a durable or non-durable JMS connection to monitor Alcatel-Lucent 5620 SAM EMS events through the SAM-O interface. In addition, you can configure the JMS event filter.

Monitored events

The following are the types of monitored JMS events:

• Object creation—For incremental inventory and alarm posting

• Object deletion—For incremental inventory and alarm clearing

• Attribute value change—For updating object properties and alarm severities

• State change—For monitoring JMS missed events and change of sysPrimaryIp upon which a full discovery will be triggered if configured to do so.

The JMS client subscribes to the following JMS topic: 5620-SAM-topic-xml.

JMS message filter

The Adapter uses a JMS filter to subscribe to relevant Alcatel-Lucent 5620 SAM EMS events. The Adapter transforms the JMS messages into data that it pushes to the various Domain Managers, as follows:

• Alarms to the Adapter Platform

• Events to the various Domain Managers as topology creation, deletion, or change events.

The Adapter includes a default file, ASA-Filter.conf, which you can modify as needed for your deployment.

Consult the Alcatel-Lucent 5620 Service Aware Manager Release 5.0/6.0 OSS Interface Developer Guide for detailed information about JMS filters.

Default JMS filter

The Adapter provides the following default JMS filter in the ASA-Filter.conf file.

# This file contains Alcatel events or classes (packageName.ClassName) that will be included in the JMS.

# The maximum size of JMS topic is 100K (total from all sessions). To use *include*, instead of

# *exclude* is to reduce the risk of the topic being full so quickly.apipe.Apipeapipe.L2AccessInterfaceapipe.Sitebgp.Peercpipe.Sitecpipe.Cpipeepipe.Epipeepipe.L2AccessInterfaceepipe.Siteequipment.BaseCardequipment.ControlProcessorequipment.DaughterCardequipment.FanTray

Configuring JMS message filtering 41


equipment.FlashMemoryequipment.PhysicalPortequipment.PowerSupplyTrayequipment.ProcessorCardequipment.CardSlotequipment.DaughterCardSlotequipment.SwitchFabricProcessorfpipe.Fpipefpipe.L2AccessInterfacefpipe.Siteies.Iesies.Siteies.L3AccessInterface# IGMPNetwork discovery is disabled by default.# Please uncomment the following line if IGMPNetwork discovery is

enabled.#igmp.IfGroupigmp.Interfaceigmp.Siteipipe.Ipipeipipe.L2AccessInterfaceipipe.Siteisis.Adjacencyisis.Areaisis.AreaMember#isis.AreaSiteisis.Interfaceisis.InterfaceLevelOneConfigisis.InterfaceLevelTwoConfigisis.Site# FIB discovery is disabled by default.# Please uncomment the following two lines if FIB discovery is enabled.#l2fib.FibEntry#l2fib.MFibEntrylag.Interfacelag.PortTerminationldp.Interfaceldp.TargetedPeermpls.DynamicLspmpls.Interfacempls.LspPathmpls.ProvisionedHopmvpls.L2AccessInterfacemvpls.Mvplsmvpls.Sitel3fwd.ServiceSitenetw.NetworkElementnetw.PhysicalLinknetw.DiscoveredPhysicalLinkospf.AreaSiteospf.Interfaceospf.Neighborospf.Siteospf.VirtualLinkospf.VirtualNeighborpim.Groupspim.Interfacepim.Neighborpim.RPSetpim.Sitertr.NetworkInterfacertr.RouteStatsrtr.VirtualRouterrtr.VirtualRouterIpAddressservice.SpokeConnectorservice.CompositeService



sonetequipment.Sts12Channelsonetequipment.Sts192Channelsonetequipment.Sts1Channelsonetequipment.Sts3Channelsonetequipment.Sts48Channelsonetequipment.TributaryChannelsonetequipment.Tu3Channelsvt.MeshSdpBindingsvt.SpokeSdpBindingsvt.Tunnelsvt.TransportConnectiontdmequipment.DS0ChannelGrouptdmequipment.DS1E1Channeltdmequipment.DS3E3Channelvlan.NetworkInterfacevlan.Vlanvlan.Sitevlan.L2AccessInterfacevlan.NetworkInterfaceVlanBindingvll.L2AccessInterfacevpls.L2AccessInterfacevpls.Sitevpls.Vplsvpls.VlanElementvpls.VlanElementVplsSiteBindingvpls.VlanPortL2AccessBindingvprn.L3AccessInterfacevprn.Sitevprn.Vprnfm.AlarmObjectTerminateClientSessionKeepAliveEvent

Modifying the default JMS filter

Modify the filter as needed. For example, if the volume of if igmp join/leave events is adversely affecting processing time, you can remove them from the filter.

To remove igmp join/leave events, comment out the line, as follows:

#igmp.IfGroup

Configuring alarm processingConfigure the Adapter to specify mapping of Alcatel-Lucent 5620 SAM EMS alarms to Global Manager notifications. These alarms are received over the JMS interface. Mapping is done in the ASA-Alarm.conf file, which contains default behavior specifications and examples of how to change default behavior for specific alarms.

At a minimum, specify values for SEVERITY, DEDUP, EXPIRATION, and NOTARGET times. In addition, if you wish to override the default values for specific alarms, discard an alarm, or have additional text added to the notification, specify those preferences in this file.

Note: Many customers use this mapping to filter out JMS alarms that report conditions that are also detected by EMC Smarts software. To facilitate this, the default configuration file has some annotated suggestions for filtering out such alarms.

Configuring alarm processing 43


Note: “Reloading alarm configuration files” on page 49 describes how to reload modified alarm files without restarting the Adapter.

Table 2 on page 44 describes the configurable parameters for this file.

Configuring alarms

To configure the alarm mapping:


sm_edit conf/alcatel-sam/ASA-Alarm.conf

2. Find the section, # Configurations for ASA.

3. Type the new value, as required for your configuration. The following sample shows the section of code.

## Configurations for ASA## Event Active/Inactive - used to disable events, default is ACTIVE# INACTIVE alarm-xx-xx-xx## Event Durable/Momentary - used to make events momentary, default is DURABLE

Table 2 Alarm processing parameters

Parameter Description Context specifier Allowed values

SEVERITY If the Alcatel-Lucent 5620 SAM EMS does not provide a value for SEVERITY for an alarm, the Adapter assigns this default value.

[DEFAULT | alarm-xx-xx-xx] Integer from 1-8. Default is 7.

MOMENTARY Alarms are DURABLE by default; the conf file defines certain alarms as MOMENTARY. To change an alarm from DURABLE to MOMENTARY, you can add the alarm to the list.

[DEFAULT | alarm-xx-xx-xx] The EMC Smarts Service Assurance Manager Configuration Guide describes these values in more detail.

EXPIRATION Value in seconds before an alarm expires. By default, alarms do not expire. To enable alarm expiration, you can add an alarm to the list and include a value other than zero.

[DEFAULT | alarm-xx-xx-xx] Default is 0

DEDUP If the value is set to ON, the Adapter suppresses repeated notifications.

[DEFAULT | alarm-xx-xx-xx] ONOFF

NOTARGET For notifications not modeled by the Adapter, the expiration time is set to this value.

Not applicable Integer seconds until expiration. Default is 0

INACTIVE The specified alarm is discarded so it is not passed to the Adapter Platform.Most alarms are ACTIVE; the conf file lists the exceptions, which are INACTIVE.

[alarm-xx-xx-xx]

COMMENT Text string to be added to the notification.

[alarm-xx-xx-xx] Text of comment



# MOMENTARY alarm-xx-xx-xx## Event De-duplication - used to block repeat events# DEDUP DEFAULT represents default response# DEDUP alarm-xx-xx-xx represents individual DEDUP value## Event Comments - appears at the end of event text# COMMENT alarm-xx-xx-xx "This is a sample comment"## Event Severity - used if actual severity is not included in event# SEVERITY DEFAULT 7 (MAJOR)# SEVERITY alarm-xx-xx-xx 8 (CRITICAL) ## Event Expiration - time in seconds to clear notification after becoming inactive# EXPIRATION DEFAULT 0 (live forever)# EXPIRATION alarm-xx-xx-xx 60 (live 60 seconds)## Expiration for Alarms without a corresponding InCharge target # NOTARGET 28800 (expire after 8 hours)## EventName Aliases are defined with lines that have the original alarm-1-2-3 # followed by the new alias that should be used for the EventName# alarm-8-3-6 EquipmentRemoved##----------------------------------------------------------------------------------

DEDUP DEFAULT ONSEVERITY DEFAULT 7EXPIRATION DEFAULT 0NOTARGET 0

# An example#DEDUP alarm-305-11-90 ONINACTIVE alarm-305-11-90MOMENTARY alarm-305-11-90COMMENT alarm-305-11-90 "This is a test event"SEVERITY alarm-305-11-90 8EXPIRATION alarm-305-11-90 14400

# Inactive list## Examples of 5620Sam alarms that correspond to EMC diagnoses## IP/AMPMINACTIVE alarm-10-3-8 # PhysicalPort EquipmmentDown = Interface DownINACTIVE alarm-20-3-17 # LagDown = NetworkAdapterRedundancyGroup AllComponentsDownINACTIVE alarm-36-13-32 # InterfaceDown = Interface DownINACTIVE alarm-243-4-176 # SNMPReachabilityProblem = SNMPAgent UnreachableINACTIVE alarm-249-32-32 # AccessInterfaceDown = Interface Down# MPLSINACTIVE alarm-25-12-19 # LspDown = LSP DownINACTIVE alarm-97-16-83 # ServiceSiteDown = Forwarder DownINACTIVE alarm-221-30-166 # SdpBindingDown = ForwarderEndpoint Down# BGPINACTIVE alarm-2-1-2 # PeerConnectionDown = BGPSession Disconnected # or BGPProtocolEndpoint RemoteSpeakerNotConfigured

# Momentary listMOMENTARY alarm-31-4-24 # PollerProblemMOMENTARY alarm-32-3-25 # NodeRebooted



The Alcatel-Lucent 5620 SAM EMS severities are translated to EMC Smarts severities as shown in Table 3 on page 46.

Considerations for working with alarms

The following are some suggestions for working with Alcatel-Lucent 5620 SAM EMS alarms.

Removing unneeded alarmsThe LSP path and tunnel enhancements eliminate the need for the Adapter to import certain alarms.To avoid display of unneeded alarms in the Notification Log, follow this procedure:


sm_edit conf/alcatel-sam/ASA-Alarm.conf

2. Find the section, # Configurations for ASA.

3. Add the following lines:

INACTIVE alarm-30-12-23 # TunnelDownINACTIVE alarm-26-12-20 # LspPathDown

4. Save and close the file.

Alarm default expiration timeYou can set a default expiration time for all alarms or specific alarms using the adapter alarm configuration file. In this way, the alarm(s) will be cleared in EMC Smarts even if they are not cleared in the Alcatel-Lucent 5620 SAM EMS server. If an alarm expiration is set to 0, it will stay in the EMC Smarts Notification Log until a clear is sent by the Alcatel-Lucent 5620 SAM EMS server through the Adapter.

Alarms for objects with no associated repository objectsThe Adapter sends alarms on objects that are not modeled in EMC Smarts repositories. These are referred to as NOTARGET alarms. These alarms will be placed in the EMC Smarts Notification Log, but they will not be associated with anything in EMC Smarts. The NOTARGET alarms can be identified as alarms with Class names that start with SAMO- in the EMC Smarts Notification Log. The Adapter alarm configuration file permits a different default value to be set for NOTARGET alarms than for alarms that have associated objects in EMC Smarts.

Table 3 Mapping of Alcatel-Lucent 5620 SAM EMS and EMC Smarts Alarm severities

Alcatel-Lucent 5620 SAM EMS EMC Smarts Description

8 1 Critical

7 2 Major

6 3 Minor

5,4,3,2 4 Unknown

1 5 Normal



Alarms that are set for manual clearingThe Adapter is configured by default to assume that operators will manually clear some alarms. Alarms may report unusual conditions but not clear when the conditions are cleared, based on the assumption that an operator will clear the alarm. This is not an optimum condition in the EMC Smarts software environment. Consult the Alcatel-Lucent 5620 SAM EMS training documentation for setting policies consistent with your operation.

Alarm synchronizationA request for a full discovery automatically synchronizes the alarms in the EMC Smarts Notification Log with the alarms in the Adapter. That is, it removes alarms in EMC Smarts software that are no longer in the Adapter, and it reintroduces alarms that have been removed or are missing from the Adapter.

Note: The Adapter does not reintroduce alarms if the alarm is configured to be INACTIVE.

You can change the ASA-Alarm.conf file so that alarms that were previously placed in the Adapter Platform (OI) are now inactive, are removed during sychronization. In addition, you can manually trigger alarm rediscovery by invoking the alarmRediscover.asl script. The Adapter has some configuration alarms which do not clear when the configuration problem is fixed, so the alarmRediscover.asl script can remove alarms for conditions that no longer apply.

Aggregating alarms

You can aggregate alarms for convenience. When the Adapter sees one of the aggregating alarms, it creates an aggregated alarm. The notification for the aggregate alarm is formed on the instance that triggered the alarm. The eventName of the notification is the name of the specified aggregate.

Note: The ASA-Alarm.conf file does not recognize wildcard entries for alarms.

Configuring aggregate alarms

To configure aggregate alarms:


sm_edit conf/alcatel-sam/AggregateAlarms.conf

2. Edit the alarm, using the following format:

AggregateAlarm { alarm-alarmName-alarmType-alarmProbableCause <another alarm> <another alarm> }



The following is an example AggregateAlarms.conf file:

# This file is where aggregate alarms are configured.# The file syntax is as follows:## aggregate-alarm { alarm1 alarm2 alarm3 }# ^ ^ ^ ^# | \ | /# The aggregate alarm \ | /# created in OI \ | /# \ | /# \ | /# aggregating 5620 alarms### The aggregating alarms can be on multiple lines like so:## aggregate-alarm { # alarm1# alarm2# alarm3# alarm4 }## The '#' character denotes a commented line. Anything on the# line after the comment is ignored so aggregates can be# created like so:## aggregate-alarm { alarm-1-2-3 # an example 5620 alarm# alarm-2-3-4 # an example 5620 alarm# }## Alarms are of the form alarm-alarmName-alarmType-# alarmProbableCause# They can also be configured without alarmType and/or# alarmProbableCause.# This is useful to aggregate alarms based simply on the# alarmName.

# A test aggregate. Will form if any of the four 5620 test# alarms are seen.# The alarmType and alarmProbableCause are ignored; only the# alarmName is used

5620TestAggregate { alarm-15-- alarm-16--alarm-17-- alarm-18--}

Notes on alarms

An alarm has the format of (literal string), alarm-<alarmName>-<alarmType>-<alarmProbableCause>. Thus an alarm has 3 fields: <alarmName>, <alarmType>, and <alarmProbableCause>. These alarms are mapped from the Alcatel-Lucent fm.AlarmObject object.

Each alarm contains three field elements, separated by hyphens(-). Use the hyphen (-) as a wildcard on the <alarmType> and <alarmProbableCause> fields, if you wish to match any incoming alarm (for that particular field). To do this, leave that particular field empty in the alarm string.



For example, to aggregate on the Alcatel-Lucent 5620 NMSTestFakeAlarmOne alarm, (alarmName = 15) with a licensingAlarm type (alarmType = 23) and a FakeAlarmOne probable cause(alarmProbableCause = 13), write the alarm as:

alarm-15-23-13

To ignore the type and probable cause fields, write it as alarm-15--

You can use wildcards to aggregate alarms based on any given <alarmType> or <alarmProbableCause>.

• To match all types, leave the< alarmType> field blank; for example,

alarm-15--10

• To match all causes, leave the leave the <alarmProbableCause> field blank; for example,

alarm-15-10-

• To match all types and causes, leave both alarm fields blank; for example,

alarm-15--

Reloading alarm configuration files

Edit the ASA-Alarm.conf or AggregateAlarms.conf configuration files to initiate file reloading without restarting the Adapter.

At ASAM_BASEDIR/smarts/bin, enter the following command:

sm_adapter -s <adapter_name> alcatel-sam/reloadOI.asl

Filtering out alarms in maintenance

Use the InMaintenance attribute on an alarm object to filter out alarms whose affected objects are in maintenance mode. To enable this functionality, go to the Service Assurance Manager installation directory:

1. At /opt/InCharge7/SAM/smarts/bin, enter the following command:

sm_edit conf/ics/dxa-oi.conf

2. Uncomment the InMaintenance line as follows:

notification#attr Acknowledgedattr InMaintenance#attr Owner#attr TroubleTicketID



New INACTIVE alarms in ASA-Alarm.conf

Table 4 on page 50 lists new alarms that will be filtered as INACTIVE by default. Alarms are located in the ASA-Alarm.conf file.

Note: For more information regarding alarm handling by ASA-Alarm.conf, consult “Configuring alarm processing” on page 43.

Table 4 New INACTIVE alarms in this release (page 1 of 2)

Default status Alarm Description

INACTIVE alarm-30-12-23 # TunnelDown

INACTIVE alarm-26-12-20 # LspPathDown

INACTIVE alarm-145-3-116 # FanEquipmentFailure = Fan Down/StateNotNormal

INACTIVE alarm-455-3-326 # EquipmentAdministrativelyDown = Interface Disabled

INACTIVE alarm-30-12-23 # TunnelDown

INACTIVE alarm-26-12-20 # LspPathDown

OSPF

INACTIVE alarm-141-24-112 # OspfInterfaceDown = OSPFInterface or OSPFNeighborRelationship Down

INACTIVE alarm-39-11-36 # InterfaceHelloConfig areaMismatch = OSPFInterface AreaIDMismatchSymptom

INACTIVE alarm-39-11-37 # InterfaceHelloConfig unknownNbmaNbr = OSPFNeighborEndpoint UnknownNbmaNeighborEvent

INACTIVE alarm-39-11-38 # InterfaceHelloConfig unknownVirtualNbr = OSPFNeighborEndpoint UnknownVirtualNeighborEvent

INACTIVE alarm-39-11-39 # InterfaceHelloConfig netMaskMismatch = OSPFNeighborRelationship NetmaskMismatchSymptom

INACTIVE alarm-39-11-40 # InterfaceHelloConfig helloIntervalMismatch = OSPFInterface HelloOrDeadIntervalMismatchSymptom

INACTIVE alarm-39-11-41 # InterfaceHelloConfig deadIntervalMismatch = OSPFInterface HelloOrDeadIntervalMismatch

INACTIVE alarm-39-11-42 # InterfaceHelloConfig optionMismatch = OSPFInterface AreaTypeMismatchSymptom

INACTIVE alarm-45-14-45 # InterfaceHelloAuthFailure authTypeMismatch = OSPFNetwork AuthTypeMismatchSymptom

INACTIVE alarm-45-14-46 # InterfaceHelloAuthFailure authFailure = OSPFNetwork AuthKeyMismatchSymptom



INACTIVE alarm-54-11-36 # VirtualLinkHelloConfig areaMismatch = OSPFVirtualInterface AreaIDMismatchSymptom

INACTIVE alarm-54-11-37 # VirtualLinkHelloConfig unknownNbmaNbr = OSPFVirtualNeighborEndpoint UnknownNbmaNeighborEvent

INACTIVE alarm-54-11-38 # VirtualLinkHelloConfig unknownVirtualNbr = OSPFVirtualNeighborEndpoint UnknownVirtualNeighborEvent

INACTIVE alarm-54-11-39 # VirtualLinkHelloConfig netMaskMismatch = OSPFVirtualLink NetmaskMismatchSymptom

INACTIVE alarm-54-11-40 # VirtualLinkHelloConfig helloIntervalMismatch = OSPFVirtualInterface HelloOrDeadIntervalMismatchSymptom

INACTIVE alarm-54-11-41 # VirtualLinkHelloConfig deadIntervalMismatch = OSPFVirtualInterface HelloOrDeadIntervalMismatch

INACTIVE alarm-54-11-42 # VirtualLinkHelloConfig optionMismatch = OSPFVirtualInterface AreaTypeMismatchSymptom

INACTIVE alarm-60-14-45 # VirtualLinkHelloAuthFailure authTypeMismatch = OSPFNetwork AuthTypeMismatchSymptom

INACTIVE alarm-121-20-103 # NeighborDown = OSPFNeighborRelationship Down

ISIS

INACTIVE alarm-301-1-1 # IsisInterfaceDown = ISISInterface or ISISAdjacency Down

INACTIVE alarm-153-31-232 # IsisAdjacencyDown = ISISAdjacency Down

Table 4 New INACTIVE alarms in this release (page 2 of 2)

Default status Alarm Description



Configuring Domain ManagersIn an Alcatel-Lucent environment, the Adapter imports topology from the Alcatel-Lucent 5620 SAM EMS and then directly populates any associated Domain Managers with this topology.

Configure your deployment based on the following considerations:

• “Scenario 1: Deployment with IP 7.0.3 in an all Alcatel-Lucent environment” on page 52. The network includes all Alcatel-Lucent devices; the deployment does not include the IP Availability Manager version 8.1 or the Topology Split Manager.

• “Scenario 2: Deployment with mixed vendor environment and IP Manager 7.x” on page 54. The deployment includes both Alcatel-Lucent and non-Alcatel-Lucent devices (a mixed-vendor environment) where IP 7.x gets topology from both ASAM and from non-ASAM devices.

Note: There is no support for the Multicast Manager in mixed-vendor environments.

• “Scenario 3: Deployment with IP Manager 8.1” on page 55

• “Scenario 4: Deployment with the Topology Split Manager (TSM)” on page 57

In addition, if your deployment includes either the Network Protocol Manager or the Multicast Manager, follow these instructions:

• “Additional configuration for NPM Managers” on page 59

• “Additional configuration for the Multicast Manager” on page 60

If your new Adapter for Alcatel-Lucent 5620 SAM EMS installation is in conjunction with upgrades from previous versions of the IP Availability Manager, NPM Manager for BGP, OSPF, or IS-IS, Multicast Manager, or MPLS Manager, you must remove the existing repository in each Domain Manager, and configure the Domain Manager to replace the existing repository with one populated by the Adapter. “Replacing existing Domain Manager repositories” on page 62 provides instructions.

Scenario 1: Deployment with IP 7.0.3 in an all Alcatel-Lucent environment

This section provides configuration instructions for a deployment where the network includes all Alcatel-Lucent devices and the deployment does not include the IP Availability Manager version 8.1 or the Topology Split Manager.

Configuring the Adapter PlatformUsing the Global Manager Administration Console, attach to the Adapter Platform, and then create a domain for the Adapter of the ASAM DomainType. This procedure is required because there is no default domain for the Adapter.

Follow the procedure, Creating a domain, in the EMC Smarts Service Assurance Manager Configuration Guide.



Configuring the Service Assurance ManagerUse the Global Manager Administration Console to create a domain for each of the Domain Managers in your deployment.

Follow the procedure, Creating a domain, in the EMC Smarts Service Assurance Manager Configuration Guide.

Note: “External polling auto-configuration” on page 61 provides important information about the auto-configuration feature that supports external polling by the Alcatel-Lucent 5620 SAM EMS Adapter for the deployments that include the IP Availability Manager, MPLS Manager, or NPM Managers for BGP, OSPF, and IS-IS.

Configuring the MPLS ManagerConfigure the MPLS Manager to prevent automated topology transfer from the attached IP Availability Manager.

1. At BASEDIR/smarts/bin, enter the following command:

sm_edit conf/mpls-t/mpls.conf

2. Locate the section, # InChargeDomain::InChargeDomain_INCHARGE-AM {

3. Comment out this section, as shown below.

# InChargeDomain::InChargeDomain_INCHARGE-AM {# Type = "AM"# DomainName = "INCHARGE-AM"# DisplayName = "INCHARGE-AM"# }

Configuring the Multicast ManagerConfigure the Multicast Manager to prevent automated topology transfer from the attached IP Availability Manager and, optionally, to set mapping for group names and IP addresses.


sm_edit conf/mcast/multicast.conf

2. Locate the section, # InChargeDomain::InChargeDomain_INCHARGE-AM {

3. Comment out this section, as shown below.

# InChargeDomain::InChargeDomain_INCHARGE-AM {# Type = "AM"# DomainName = "INCHARGE-AM"# DisplayName = "INCHARGE-AM"# }

4. Set the value as shown for the following variable:

IsEMS = TRUE

Configuring Domain Managers 53


Scenario 2: Deployment with mixed vendor environment and IP Manager 7.x

The following environment setup is required for the Adapter to interoperate with IP 7.x in a mixed vendor environment:

Set up the IP Manager1. At IP_BASEDIR/smarts/bin, enter the following command:

sm_edit conf/discovery/tpmgr-param.conf

2. Locate the parameter, DisableProtocolDiscovery, and set the value to FALSE.

3. Locate the parameter, DisableMulticastDiscovery, and set the value to FALSE.


Set up the MPLS Manager1. At MPLS_BASEDIR/smarts/bin, enter the following command:


2. There are two parameters, named:

peek Vendor ~Alcatel

Change both instances to:

#peek Vendor ~Alcatel

3. Enter the following command:


4. Locate the section, Instances of AM Server, and set the AM Server name to the IP 7.x Availability Manager server name. The EMC Smarts MPLS Manager User Guide provides additional information.


Set up the Multicast Manager

Note: There is no support for the Multicast Manager in mixed-vendor environments.

Set up the Network Protocol ManagerIn order to enable interoperability of the Network Protocol Manager with both IP Availability Manager Version 7.x and Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.2, you must add the IP Availability Manager as the source for each Network Protocol Manager.

IMPORTANT

For interoperability with IP Availability Manager Version 7.x you must choose the IP Availability Manager server name as the topology source.



The EMC Smarts Network Protocol Manager Discovery Guide explains the procedure in more detail. Here is an example procedure to follow:

1. Start the Global Console.

• On a Windows system, select Start > Programs > InCharge 7> EMC Smarts Global Console.

• On a UNIX system, go to the BASEDIR/smarts/bin directory in the Service Assurance Manager (Global Manager) installation area and type:

sm_gui

Press Enter.

2. In the dialog box:

a. Ensure that the EMC Smarts Broker for your deployment appears in the Broker text box.

b. Click the Manager list box or the Browse button to display a list of active (running) Managers, and from that list select a Network Protocol Manager to which you want to connect.

c. Type your login username and password.

d. Click OK.

The Topology Browser console opens.

3. On the Console, select Configure > Domain Manager Administration Console.

4. In the Domain Manager Administration Console attached to a Network Protocol Manager such as INCHARGE-BGP, select Topology > Add Source to launch the Add Source dialog box.

5. In the Add Source dialog box, select AM from the Element Type list, and type the name of the IP Availability Manager in the Element Name field.

6. Click OK to add the IP Availability Manager as a topology source.

Scenario 3: Deployment with IP Manager 8.1

The following environment setup is required for the Adapter to interoperate with IP 8.1
















4. Locate the section, Instances of AM Server, and set the AM server name to the IP-Analysis server name. The EMC Smarts MPLS Manager User Guide provides additional information.


Set up the Multicast Manager1. At MCAST_BASEDIR/smarts/bin, enter the following command:


2. Locate the section, Instances of AM Server, and set the AM server name to the IP-Analysis server name. The EMC Smarts Multicast Manager User Guide provides additional information.


4. When starting the Multicast Manager, use the following parameter:

--bootstrap=bootstrap-lite.conf

Set up the Network Protocol ManagerIn order to enable interoperability of the Network Protocol Manager with both IP Availability Manager Version 8.1 and Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.2, you must add the IP-Analysis Manager as the source for each Network Protocol Manager.

IMPORTANT

For interoperability with IP Availability Manager Version 8.1, you must choose the IP-Analysis Manager server name as the topology source.

The EMC Smarts Network Protocol Manager Discovery Guide explains the procedure in more detail. Here is an example procedure to follow:




sm_gui

Press Enter.







d. Click OK.




5. In the Add Source dialog box, select AM from the Element Type list, and type the name of the IP-Analysis Manager in the Element Name field.

6. Click OK to add the IP-Analysis Manager as a topology source.

Run discovery and update the discovery timers for IP 8.1After the Adapter completes a full discovery, update the discovery timers in the IP Manager version 8.1. This allows the IP Availability Manager 8.1 to complete post-processing.

1. Run a full discovery. At ASAM_BASEDIR, enter the following command:

sm_adapter -s ASAM alcatel-sam/discover.asl

2. When discovery is complete, enter the following command on one line:

bin/dmctl -s <Network-Resource> invoke ICF_TopologyManager::ICF-TopologyManager updateDiscoveryTimers

Scenario 4: Deployment with the Topology Split Manager (TSM)

When configuring the Adapter for Alcatel-Lucent 5620 SAM EMS to work with the Topology Split Manager (TSM) feature, follow these procedures:

Note: For MPLS, Multicast, or NPM configurations, adjust the entries in the section describing, Instances of AM Server.
















4. Locate the section, Instances of AM Server, and set the AM Server name(s) to the multiple IP 7.x Availability Manager servers that obtain topology from the TSM server.


Set up the Multicast Manager1. At MCAST_BASEDIR/smarts/bin, enter the following command:


2. Locate the section, Instances of AM Server, and set the AM server name(s) to the multiple IP 7.x Availability Manager servers that obtain topology from the TSM server.


4. When starting the Multicast Manager, use the following parameter:

--bootstrap=bootstrap-lite.conf

Set up the Network Protocol ManagerIn order to enable interoperability of the Network Protocol Manager with IP Availability Manager Version 7.x, the Topology Split Manager (TSM), and the Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.2, you must add multiple IP Availability Managers as topology sources for each Network Protocol Manager.

IMPORTANT

For interoperability with IP Availability Manager Version 7.x and the TSM feature, add the multiple IP Availability Manager server names that obtain topology from the TSM server.

Here is an example procedure to follow:




sm_gui

Press Enter.







d. Click OK.




5. In the Add Source dialog box, select AM from the Element Type list, and type the name of the IP Availability Manager in the Element Name field.

6. Click OK to add the IP Availability Manager as a topology source.

7. Continue to use the Add Source dialog box to add additional IP 7.x Availability Manager servers that obtain topology from the TSM server.

Note: If using TSM, you must contact EMC Professional Services to obtain the appropriate discovery procedures.

Additional configuration for NPM Managers

IMPORTANT

If your deployment includes Network Protocol Manager for BGP or Network Protocol Manager for OSPF version 2.1.0.7 or later, the configuration procedures outlined in this section are required to configure the DisplayName variable.

Configure individual Network Protocol Managers

Before starting a Network Protocol Manager for BGP or Network Protocol Manager for OSPF, configure the DisplayName variable, and restart the Manager without the Repository (.rps file).

Note: If your Network Protocol Manager installation is new and does not have a Repository file, do not perform step 5.

1. If running, stop the Network Protocol Manager, as described in the EMC Smarts Network Protocol Management Suite Installation Guide.

2. At NPM_BASEDIR/smarts/bin, enter the following command:

sm_edit conf/<bgp or ospf_directory>/<bgp or ospf>.conf

Additional configuration for NPM Managers 59


3. Locate the variable, IsDisplayNameCustom, and set the value to “TRUE”, as follows:

IsDisplayNameCustom = TRUE


5. If the Network Protocol Manager has a Repository (.rps file), first remove it. If these is no Repository file, skip this step.

At NPM_BASEDIR/smarts/bin, enter the following command:

rm ../local/repos/icf/<bgp or ospf_repository_filename>

6. Start the Adapter.

7. Start the Network Protocol Manager.

8. After all of the Network Protocol Managers in your deployment are started, launch a full discovery using the following command:

bin/sm_adapter -s <ASAM adapter name> alcatel-sam/discover.asl

Additional configuration for the Multicast ManagerOptionally, customize the Multicast GroupTypeInfo setting to specify mapping for Multicast group IP addresses and names.


sm_edit conf/mcast/GROUP.import

2. Locate the GroupTypeInfo section, which is configured with examples that are commented out:

## MulticastManager::MCAST-Manager {# GroupTypeInfo = {# {"224.1.1.1", "NASDAQ", "StockQuotes"},# {"224.1.1.2", "NASDAQ", "News"},# {"224.1.1.3", "PROV1", "BusinessNews"}# }# }#

In the example,

• “224.1.1.1” maps to “NASDAQ-StockQuotes”

• “224.1.1.2” maps to “NASDAQ-News”

• “224.1.1.3” maps to “PROV1-BusinessNews”

3. To name a group for your deployment, follow the example and specify an IP address and group name to which the IP address maps. Add entries as needed.

4. Uncomment the customized section.


6. Restart the Multicast Manager.



External polling auto-configurationThis section describes the auto-configuration feature that supports external polling by the Alcatel-Lucent 5620 SAM EMS Adapter for the Availability Manager, MPLS Manager, and NPM Managers for BGP, OSPF, and IS-IS.

The auto-configuration feature creates a new polling group in each Domain Manager, as listed in Table 5 on page 61. Look in the Polling and Thresholds console to verify the presence of these polling groups after installing each product.

New polling groups

The auto-configuration feature creates new Polling Groups, as listed in Table 5 on page 61. The EMC Smarts IP Availability Manager User Guide, EMC Smarts MPLS Manager User Guide, EMC Smarts Network Protocol Manager for BGP User Guide, the EMC Smarts Network Protocol Manager for OSPF User Guide, and the EMC Smarts Network Protocol Manager for IS-IS User Guide provide additional information about Polling and Threshold Groups.

Table 5 New polling groups (page 1 of 2)

Domain Manager New polling group

IP Availability Manager

Available under 5620 SAM Managed Systems Polling Groups:This group is listed at higher priority than other polling groups. You can expand the group to see the following Connectivity Polling: External Poller settings: • InstrumentCards parameter (under the Parameters tab) is set to true.• Initial Status parameter is not initialized (set to UNKNOWN).Available under 5620 SAM Managed Systems Polling Groups:5620 SAM Managed Systems > Settings >• Connectivity Polling - External Poller

IP AM/PM All options for the IP Availability Manager plus the following:• Environment Polling - External Poller

MPLS Manager Available under Forwarder Polling Groups:5620 SAM Forwarder > Settings > Forwarder Remote Setting

Available under ForwarderEndpoint Polling Groups:5620 SAM ForwarderEndpoints > Settings > ForwarderEndpoint Remote Setting

Available under LdpProtocolEndpoint Polling Groups:5620 SAM LdpProtocolEndpoint > Settings > LDP Session Remote Setting

Available under VRFs Polling Groups:5620 SAM VRFs >Settings > VRF Remote Setting

Available under LSPs Polling Groups:5620 SAM LSPs > Settings > LSP Remote Settings

External polling auto-configuration 61


Replacing existing Domain Manager repositoriesIf your new Adapter for Alcatel-Lucent 5620 SAM EMS installation is in conjunction with upgrades from previous versions of the IP Availability Manager, NPM Manger for BGP, OSPF, and IS-IS, Multicast Manager, or MPLS Manager, you must manually remove the existing repository in each Domain Manager, and configure the Domain Manager to replace the existing repository with one populated by the Adapter.

Before starting the Domain Manager server, remove the repository file from each Domain Manager in your deployment:

1. At the BASEDIR/smarts/bin for that product, enter the following command:

rm ../local/repos/icf/<repository_filename>

2. Configure the Domain Manager, as described in “Configuring Domain Managers” on page 52.

3. Start the Domain Manager server.

After all servers are started, perform a full discovery.

This step is required only after installation on those EMC Smarts Domain Managers that will reload with existing repositories. These procedures will override earlier settings, so you must configure the new settings in each repository.

Rolling the Adapter LogThe Adapter is run as an EMC Smarts server with its log file being sent to ASAM_BASEDIR/smarts/local/logs/ <Adapter_Name>.log. As with other EMC Smarts Domain Managers, configure a cron job to cause the log to be rolled occasionally so it does not consume all of the disk space. The Managing Log Files chapter in the EMC Smarts System Administration Guide provides more information on rolling log files.

NPM Manager for BGP Available under BGP Polling Groups:5620 SAM BGP >Settings > BGP External Setting

NPM Manager for OSPF

Available under OSPF Polling Groups:5620 SAM OSPF >Settings > OSPF External Setting

NPM Manager for IS-IS Available under ISIS Polling Groups:5620 SAM Devices >Settings > ISIS External Setting

Table 5 New polling groups (page 2 of 2)

Domain Manager New polling group



Device filtering (optional)The Adapter can filter devices from the Alcatel-Lucent 5620 SAM EMS server based on 5620 SAM EMS server site names. Site names appear as the DisplayName property of UnitaryComputerSystems (routers and switches) in the EMC Smarts Global Console.

Note: Setting up device filtering requires use of Adapter Scripting Language (ASL) scripts. The EMC Smarts ASL Reference Guide provides more information.

Overview of device filtering

The Adapter filters devices using regular expressions loaded from ASAM_BASEDIR/smarts/conf/DevicesNotInEffect.conf. Each line of the file represents one regular expression. Lines may begin with a “#” character to denote a comment. Comment lines are ignored when loading the file.

Filtered devices do not appear in Domain Managers. They are ignored during 5620 SAM EMS server processing. Filtering reduces the number of objects stored inside EMC Smarts servers and lessens the process load on the Adapter. Filtering is recommended on devices that are in a constant state of flux, where monitoring is not desired.

The Adapter loads filters from the DevicesNotInEffect.conf file only on Adapter startup. If you wish to change filters during Adapter runtime, you may invoke the following asl rules:

• alcatel-sam/showFilters.asl— Print the currently loaded filters in the Adapter.

• alcatel-sam/deleteFilters.asl—Delete the filters given from the specified filter frontend. This is usually a file front end loaded with the --file flag passed to sm_adapter. Filters are deleted based on exact string matching.

• alcatel-sam/insertFilters.asl—Insert the filters given from the specified filter frontend. This is usually a file front end loaded with the --file flag passed to sm_adapter.

• alcatel-sam/clearFilters.asl—Remove all filters in the Adapter.

“Managing devices not in effect” on page 142 describes how you can use these scripts to manage the filters.

The addition and deletion of filters at runtime will not change what the Adapter is currently filtering on. A full discovery (invoked from alcatel-sam/discover.asl) or a router-specific discovery (invoked from ASAM/routerDiscover.asl) is required to reload the Adapter's internal filtering list. A discovery is required because reloading the filter list requires several (potentially long) processes to run in order to clean up (newly) filtered objects that may exist in InCharge servers.

Sample filter procedure

The following sample procedure will perform runtime filtering on CLLI codes, based on the site name. This procedure will filter all routers and switches, where the site name begins with HOUSTX:

1. At ASAM_BASEDIR/smarts/bin, enter the following command to create a configuration file, filters.txt:

sm_edit conf/alcatel-sam/DevicesNotInEffect.conf

Device filtering (optional) 63


2. Edit the empty file to include a single line with the contents, HOUSTX.*


Note: Regular expressions are powerful ways of specifying how one can match character strings. To specify how to match a character string that starts with HOUSTX, add .* (a period followed by an asterisk), which may be slightly different that what you expect from your experience searching for files, where an asterisk is usually sufficient. In regular expressions, HOUSTX* (without the period) would match HOUST, HOUSTX, HOUSTXX, HOUSTXXX, etc. If the HOUSTX.* is specified, the matching character string must have HOUSTX and zero or more of any possible characters.


CHAPTER 3Start up and Discovery

This chapter describes how to start the Adapter and associated Domain Managers, verify the product status, and initiate discovery. In addition, it describes options for managing file data.

The chapter contains the following information:

• Starting Adapter and Domain Manager services ...................................................... 66• Initiating discovery.................................................................................................. 67• Removing an unused JMS durable connection ......................................................... 69

Note: After starting up the Adapter, you must manually initiate full discovery at least one time, as described in “Initiating full discovery” on page 67.

Start up and Discovery 65

Start up and Discovery

Starting Adapter and Domain Manager services

Note: Use the sm_service command to start and stop Adapter and Domain Manager servers that were installed as services. If you need to install a service manually, the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide provides instructions.

Note: Execute the commands listed below from the /bin directory under any of the product paths. For example, you can execute these commands from ASAM_BASEDIR/smarts/bin.

Starting the Domain Manager services

Note: If you are starting a Domain Manager for the first time with a fresh installation, you can start the service as described in this section. If you are starting the Domain Manager after it already has a repository, you may remove the repository so the Manager can create a new one.

To start the Adapter and Domain Manager servers:

1. If the Broker is not already started, enter the following command:

sm_service start ic-broker

2. To start the IP Availability Manager service, enter the following command:

sm_service start ic-am-server

3. To start the Multicast Manager service, enter the following command:

sm_service start ic-mcast-server

4. The MPLS Manager includes three servers, which are started separately. To start these services, enter the following commands:

sm_service start ic-mpls-topologysm_service start ic-mpls-analysissm_service start ic-mpls-monitoring

5. To start the Network Protocol Manager for BGP service, enter the following command:

sm_service start ic-npm-bgp-server

6. To start the Network Protocol Manager for OSPF service, enter the following command:

sm_service start ic-npm-ospf-server

7. To start the Network Protocol Manager for IS-IS service, enter the following command:

sm_service start ic-npm-isis-server

8. To start the Adapter Platform service, enter the following command:

sm_service start ic-icoi-server

9. To start the Global Manager service, enter the following command:

sm_service start ic-sam-server



10. To start the Adapter for Alcatel-Lucent 5620 SAM EMS service, enter the following command:

sm_service start ic-alcatel-sam

Stopping a Domain Manager service

To stop a service, enter the following command:

sm_service stop <service_name>

where the server name is as listed in “Starting Adapter and Domain Manager services” on page 66. For example,

sm_service stop ic-asam

Initiating discoveryThis section provides commands for initiating full and partial discovery.

Note: Execute these commands from ASAM_BASEDIR/smarts/bin.

The following appendices show how the elements monitored by the Alcatel-Lucent 5620 SAM EMS are mapped to EMC Smarts objects:

• “Mapping of SAM-O Elements to Smarts Objects” on page 71

• “Mapping of Smarts objects and SAM-O Objects” on page 91

Initiating full discovery

After installing, configuring, and starting the Adapter, you can manually initiate full discovery. To start a full discovery, enter the following command:

sm_adapter -s <adapter_name> alcatel-sam/discover.asl

Initiating partial discovery

This section provides the following options for initiating partial discovery:

• Service-only—Discovers all service elements from the Alcatel-Lucent 5620 SAM EMS (does not discover Routers, Switches, Chassis, Cards, Physical Ports, and Channels). If the network is static and you only need to refresh the records for services using it, a service-only discovery would be appropriate and quicker than a full discovery.

• Specific domain—Discovers elements from a specific domain, such as MPLS, Multicast or NPM.

• Router—Discovers a single router with the designated IP.

• Re-read files in the Adapter Platform.

Initiating discovery 67


Service-only discoveryTo initiate a service-only discovery, enter the following command:

sm_adapter -s <adapter_name_name> alcatel-sam/serviceDiscover.asl

“Scheduling a periodic discovery” on page 68 provides instructions for scheduling periodic service discovery.

Discovery of a specific domain To restrict the discovery to a domain managed by one of the following: MPLS Manager, Multicast Manager, NPM Manager for BGP, OSPF, or IS-IS, use the -DQUALIFIER parameter, with a value of MPLS, MCAST, or NPM. For example:

sm_adapter -s <adapter_name> -DQUALIFIER=NPM alcatel-sam/serviceDiscover.asl

Router-only discovery To initiate a discovery of a single Router, enter the following command, which specifies the router IP address:

sm_adapter -s <adapter_name> -DIP=<Router System ID> alcatel-sam/routerDiscover.asl

For example,

sm_adapter -s <adapter_name> -DIP=”10.1.1.77” alcatel-sam/routerDiscover.asl

Scheduling a periodic discovery

Use periodic discovery if needed in a situation if there are problems with the JMS incremental discovery or if the JMS is intentionally disabled. For example, you can schedule periodic service discoveries to avoid using JMS for a rapidly changing topology.

To schedule periodic discoveries at time with low network usage, use the following procedure, which illustrates the command for a periodic service discovery.

1. At /var/spool/cron/crontabs/root, add lines such as the following example for service discovery:

# ASA Adapter# Purpose: Schedule Service Discover at 4am0 0 4 * * * BASEDIR/smarts/bin/sm_adapter -s <adapter_name> asa/serviceDiscover.asl <system_temporary_files_directory>

2. Signal the crontab process to re-read the file:

crontab /var/spool/cron/crontab/root

Synchronizing alarms

To initiate an alarm rediscovery (synchronization), enter the following command:

sm_adapter -s <adapter_name> alcatel-sam/alarmRediscover.asl

This procedure compares alarms in the Notification Log with those in the Adapter for Alcatel-Lucent 5620 SAM EMS and then synchronizes them. The procedure removes alarms from the Notification Log that no longer exist in the Adapter, and adds new alarms to the Notification Log.



Removing an unused JMS durable connectionThe Adapter is kept informed of changes to the Alcatel-Lucent network by the Alcatel-Lucent 5620 SAM EMS server. The mechanism by which this is accomplished is called Java Messaging Service (JMS). The Adapter normally connects to the server using “durable” connections. This means that if the Adapter goes down, the server will queue up changes that are taking place and deliver those changes to the Adapter when it reconnects. The Adapter is known to the Alcatel-Lucent 5620 SAM EMS server by its JmsUniqueId.

The presence of an unused JMS durable connection causes the Alcatel-Lucent 5620 SAM EMS to accumulate transactions that will never be delivered to the Adapter, consuming unnecessary disk space. The durable connections in the Alcatel-Lucent 5620 SAM EMS server are recorded in the 5620sam/server/nms/jboss/server/default/conf/jbossmq-state.xml file.

EMC Corporation recommends that you remove an unused JMS connection in order to release the server from its “obligation” to store undelivered transaction, if you have changed the value of the JmsId parameter in the emsConfig.import file.

To remove an unused JMS durable connection from the 5620 Sam server, use the Alcatel-Lucent 5620 SAM EMS GUI. The Alcatel-Lucent 5620 SAM EMS documentation provides instructions.

Removing an unused JMS durable connection 69



APPENDIX AMapping of SAM-O Elements to Smarts Objects

This appendix includes the following contents:

• Examples of EMS elements mapped to EMC Smarts objects .................................... 72• Power supply instantiation...................................................................................... 85• SAM-O element to EMC Smarts object mapping....................................................... 85

EMC® Smarts® is the name that replaces EMC® Ionix™ or EMC® ITOI. Earlier documents, figures, or screen captures may use EMC® Ionix™ or EMC® ITOI.

Mapping of SAM-O Elements to Smarts Objects 71

Mapping of SAM-O Elements to Smarts Objects

Examples of EMS elements mapped to EMC Smarts objectsThis section illustrates how EMS elements are mapped to EMC Smarts elements for the various Domain Managers.

Physical model

Figure 3 on page 72 shows an example of the mapping of physical elements (Router, Card, Interface, Memory Processors, and Network Adapter Redundancy Group), as shown in the Alcatel-Lucent 5620 SAM EMS Equipment View and as they are instantiated in the EMC Smarts IP Manager Domain Managers. In this example, mappings are shown for IP classes such as the following:

• NE (Network Element) maps to Router or Switch

• Card (including Base, Daughter, Processor) maps to Card

• Physical Port maps to Interface

• LAG (Link Aggregation Group) maps to NARG (Network Adapter Redundancy Group)

• Fresh Memory maps to Memory

• Processor (Control Processor, Switch Fabric) maps to Processor.

Figure 3 EMS to IP Manager mapping

Alcatel – Equipment View

EMC Ionix IP Manager Topology

Router

Card

Interface

MemoryProcessors(APM only)

NARG



Logical NPM BGP model

Figure 4 on page 73 shows an example of the mapping of logical elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Manager for BGP.

In this example, mappings are shown for NPM BGP classes such as the following:

• BGP Routing Instance maps to BGPService

• BGP Peer maps to BGPProtocolEndpoint

• Autonomous System maps to AutonomousSystem

• Confederation maps to Confederation.

Figure 4 EMS to Network Protocol Manager for BGP mapping

Network View

Alcatel

Peer/Endpoint

Peer/Endpoint

Service

Service

NPM BGPEMC Ionix

Examples of EMS elements mapped to EMC Smarts objects 73


Logical NPM OSPF model

Figure 5 on page 74 shows an example of the mapping of logical elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Manager for OSPF.

In this example, mappings are shown for NPM OSPF classes such as the following:

• OSPF Routing Instance maps to OSPF Service

• OSPF Area maps to OSPFArea

• OSPF Interface maps to OSPFInterface

• OSPF Neighbor maps to OSPFNeighborEndpoint

• OSPF Virtual Link maps to OSPFVirtualInterface

Figure 5 EMS to Network Protocol Manager for OSPF mapping

Area

Area

OSPF Interface

Virtual Interface

Ionix NPM OSPF



Logical NPM ISIS model

Figure 6 on page 75 shows an example of the mapping of logical elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Manager for IS-IS.

In this example, mappings are shown for NPM ISIS classes such as the following:

• ISIS Area Member maps to ISIS Service

• ISIS Area maps to ISISArea

• ISIS Interface maps to ISISInterface

• ISIS Neighbor maps to ISISNeighborEndpoint

Figure 6 EMS to Network Protocol Manager for IS-IS mapping



Logical Multicast model

Figure 7 on page 76 shows an example of the mapping of logical elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Multicast Manager.

In this example, mappings are shown for Multicast classes such as the following:

• PIM Routing Instance maps to MulticastService

• PIM Interface maps to PIMInterface.

Figure 7 EMS to Multicast Manager mapping

Service <- PIM instance

PIM Interfaces

Alcatel



Logical MPLS VLL model

Figure 8 on page 77 shows an example of the mapping of logical MPLS VLL elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager. In this example, mappings are shown for MPLS classes such as the following:

• VLL Service maps to L2 VPN and PseudoWire

• VLL Sites maps to Forwarder

• SDPBindings maps to Forwarder Endpoints.

Figure 8 EMS to MPLS Manager VLL mapping

EMC Ionix MPLS – VPN (L2, P2P)Alcatel – VLL Service ViewVPN

Service

VLL Sites = Forwarders

SDP Bindings = Endpoints



Logical MPLS VPLS model

Figure 9 on page 78 shows an example of the mapping of logical MPLS VPLS elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager. In this example, mappings are shown for MPLS classes such as the following:

• VPLS Service maps to VPLS VPN

• VPLS Sites maps to Forwarder

• SDPBindings maps to Forwarder Endpoints.

Figure 9 EMS to MPLS Manager VPLS mapping

Alcatel – VPLS Service View



Logical MPLS VPRN model

Figure 10 on page 79 and Figure 11 on page 80 show examples of the mapping of logical MPLS VPRN elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager.

Figure 10 on page 79 shows an example of the mapping of logical MPLS VPRN elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager. In this example, mappings are shown for MPLS classes such as the following:

• VPRN Service maps to L3 VPN

• VPRN Sites maps to VRF

Figure 10 EMS to MPLS Manager VPRN mapping

Alcatel – VPRN Service

EMC Ionix MPLS L3VPN

VPRN Sites = VRFs

L3SAP Interface



Figure 11 on page 80 shows an example of the mapping of Route Targets in the Alcatel-Lucent 5620 SAM EMS as they are instantiated as RouteTargets in the MPLS Manager.

Figure 11 EMS to MPLS Manager VPRN Route Target mapping

Alcatel – VPRN Service

EMC Ionix MPLS L3VPN

VPRN Sites = VRFs

L3SAP Interface



Interfaces, Physical, Network, L2/L3

Figure 12 on page 81 shows an example of the mapping of interface elements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the IP Availability Manager. In this example, mappings are shown for interfaces such as the following:

• Physical port is mapped to Interface (port number indicated)

• Network interface is mapped to Interface (NW indicated)

• L2 access interface is mapped to Interface (L2 SAP indicated)

• L3 access interface is mapped to Interface (L3 SAP indicated)

Figure 12 EMS to IP Manager interface mapping

EMC Ionix

AlcatelEquipment

View

Network View

L2 Service View

L3 Service View

L3SAP

L2SAP

Physical

Network



VLAN in the MPLS ManagerThe Adapter instantiates VLAN sites in the MPLS Manager as they are not supported in the MPLS model. Figure 13 on page 82 shows the relationship between a VLAN and its related elements in the MPLS Manager.

Figure 13 Modeling of VLAN and related components in the MPLS Manager

Associating a VLAN with a VPLSThe Adapter uses the model shown in Figure 14 on page 83 to associate a VLAN with a VPLS in the MPLS Manager. Their relationship is determined by the following elements:

• A Cable links two physical ports, one used by the VLAN site and the other by the VPLS site. However, the same physical port could be shared by multiple VLANs and multiple VPLSs. Thus, further evidence is needed to link a VLAN and a VPLS.

• The VLAN and the VPLS are linked by matching the VLAN id on the VLAN side with the encapsulation value configured on the VPLS access interface.

VLAN namingThe object name of a VLAN object is the same as the objectFullName of the SAM-O object vlan.Vlan (the VLAN service). The following is an example:

The following is an example:

svc-mgr:service-369

The DisplayName is set to VLAN-<vlanId>. If the VLAN is related to a VPLS, the DisplayName is set as VLAN-<vlanId>/VPLS-<vplsId> For example:

VLAN-<vlanId>/VPLS-<vplsId>



After this relationship is determined, the Adapter creates a LayeredOver/Underlying relationship between the VLAN and the VPLS site (Forwarder) in the MPLS Manager. this allows the MPLS Manager to perform VLAN impact analysisd.

Figure 14 Relationship between a VLAN and a VPLS

Modeling of LSP paths and SDP tunnels

The Adapter now supports modeling of LSP paths and SDP tunnels. LSPs, LSP paths, and SDP tunnels are now all modeled using the LSP class. LSPs may be distinguished from the other LSP class instances with the following display name convention: <Source Node> -> <Destination Node>/LSP-X (X represents the LSPid).



The relationships among these objects are illustrated in Figure 15 on page 84.

Figure 15 Modeling of LSP paths and SDP tunnels

Modeling of LSP pathsThis enhancement addresses the correlation gaps that were identified when an LSP Interface is shut down, and the Adapter diagnosed both Interface Disabled and LSP Down as root causes. To make this diagnosis, the Adapter relied on dynamic MPLS cross-connect data to establish the relationship between an LSP and the Interfaces that this path traverses. That data disappeared when the LSP went down, making the relationship disappear. Thus, the Adapter could not use the correlation with the Interfaces during root-cause analysis.

The Adapter takes advantage of the fact that all LSP paths are statically provisioned. Using the hop information that is specified when LSP paths are provisioned, the Adapter will create the relationships between the LSP paths and the Interfaces that will be traversed. This applies to both strict and loose hops.

LSP paths may be distinguished from the other LSP class instances with the following display name convention: <Source Node> -> <Destination Node>/LSP-X-PATH-Y (X represents the LSPid of the associated LSP, Y represents the LSP path binding ID).

Modeling of SDP tunnelsThe Adapter now instantiates Service Distribution Paths (SDP), also referred as service tunnels, in the MPLS topology. The SDP is the separator between the transport layer (label-switched path or LSP) and the service layer (Forwarder/ForwarderEndpoint/PseudoWire). The Adapter will show the relationships between the SDP, the LSPs, and the related service objects. In addition, SDP-related alarms will be correlated with relevant notifications.



In previous versions of the Adapter, SDP tunnels using GRE transport were modeled as Network Connections. Beginning with version 3.1, both GRE and MPLS transport SDP tunnels are now modeled in the LSP class. For SDP tunnel instances, the Description attribute identifies the transport type.

SDP tunnels may be distinguished from the other LSP class instances with the following display name convention: <Source Node> -> <Destination Node>/SDP-X (X represents the SDP ID).

Modeling of IES-IES services

Internet Enhanced Service (IES) provides routing capability on top of MPLS network. In addition, it is widely used for multicast routing in order to take advantage of LSP path protection.

The Adapter now instantiates IES-IES services that have at least one SDP binding in the MPLS topology. These services are modeled as follows:

• IES SDP binding is modeled as ForwarderEndpoint. A PseudoWire is created between each pair of bindings.

• IES site is modeled as Forwarder.

• IES service is modeled as VPN.

In addition, the Adapter correlates IES alarms with relevant notifications in the MPLS Manager.

Power supply instantiationThe Alcatel-Lucent SAM-O model provides status for two power supplies in each tray. The Adapter has been enhanced so that it no longer instantiates un-equipped power supplies. When a power supply is put in place with an “equipped” state, the Adapter will instantiate it.

SAM-O element to EMC Smarts object mappingFor each Domain Manager, Table 6 on page 85 shows how Alcatel-Lucent 5620 SAM-O interface elements are mapped to EMC Smarts objects, and indicates where these objects are displayed.

Table 6 Mapping of SAM-O Elements to EMC Smarts objects (page 1 of 6)

EMC Smarts Object SAM-O ClassDisplayed in 5620 SAM EMS Console

IP AM/PM

Cable equipment.PhysicalLink Manage > Equipment > Physical Link

Card equipment.BaseCardequipment.DaughterCardequipment.ProcessorCard

Manage > Equipment > Card

CardRedundancyGroup equipment.ProcessorCard (one for each pair)

Manage > Equipment > Card > Processor Card

Power supply instantiation 85


Chassis Derived fromequipment.Card

Number equals to Manage > Equipment > Network Element

Fan (PM only) equipment.FanTray Manage > Equipment > Fan Tray

Interface equipment.PhysicalPort Manage > Equipment > Port > Physical Port

rtr.NetworkInterface Manage > Routing Instances > Network Interface

sonetEquipment.Sts1ChannelsonetEquipment.Sts3ChannelsonetEquipment.Sts12ChannelsonetEquipment.Sts48ChannelsonetEquipment.Sts192ChannelsonetEquipment.Tu3Channeltdmequipment.DS0ChannelGrouptdmequipment.DS1E1Channeltdmequipment.DS3E3Channel

Manage > Equipment > Port > Logical Port > Channel, andManage > Equipment > Port > Logical Port > Interface

ies.L3AccessInterfacevprn.L3AccessInterface

Manage > Services > AccessInterface > L3 Access Interface

vll.L2AccessInterfaceapipe.L2AccessInterfaceepipe.L2AccessInterfacefpipe.L2AccessInterfaceipipe.L2AccessInterfacevpls.L2AccessInterface

Manage > Services > AccessInterface > L2 Access Interface

IP - Manage > Routing Instances > IP Addresses, andManage > Routing Instances > Router Site > RoutingInstanceSite > Routing Instance

IPNetwork - -

MAC - -

Memory equipment.FlashMemory Manage > Equipment > Flash Memory

NetworkAdapterRedundancyGroup lag.Interface Manage > Equipment > Port > Logical Port > Port Group > LAG

NetworkConnection Derived frommpls.CrossConnectospf.Neighborpim.Groupssvt.Tunnel

-

PowerSupply equipment.PowerSupplyTray Manage > Equipment > Power Supply Tray





Processor equipment.Processor Manage > Equipment > Card > Processor Card, orManage > Equipment > Processor

Router/Switch netw.NetworkElement Managed > Equipment > Network Element

SNMPAgent netw.NetworkElement Managed > Equipment > Network Element

MPLS

Forwarder vll.Siteapipe.Siteepipe.Sitefpipe.Siteipipe.Site

Manage > Services > Site (Service Management) > Site (vll)

vpls.Site Manage > Services > Site (Service Management) > AbstractSite (vpls) > Site (vpls)

ForwarderEndpoint. svt.MeshSdpBindingsvt.SdpBindingsvt.SpokeSdpBinding

Manage > Services > SdpBinding, orManage > MPLS Objects > SdpBinding

LdpAdjacency ldp.TargetedPeer (one for each pair) -

LdpProtocolEndpoint ldp.Interfaceldp.TargetedPeer

Manage > Routing Instances > RouterTerminatingInterface > RouterTerminatingNonIpInterface > LDP Interface, andApplication > Navigation Tree > Network (Expand LDP in each Routing Instance to check the TargetedPeers)

LSP mpls.LspPath Manage > LSPs > Static + Dynamic

LSPHop mpls.CrossConnect Manage > MPLS Objects > In Segment, andManage > MPLS Objects > Out Segment

MPLSService Mpls.Interfacevprn.Site

Manage > MPLS Objects > MPLS (Path/Routing Management: MPLS)

PseudoWire Derived fromsvt.MeshSdpBindingsvt.SdpBindingsvt.SpokeSdpBinding

-



SAM-O element to EMC Smarts object mapping 87


VPN vll.Vllapipe.Apipeepipe.Epipefpipe.Fpipeipipe.Ipipevpls.Vplsvprn.Site

Manage > Services > Service (Service Management)

VRF vprn.Site Manage > Services > Site (Service Management) > Site (vprn)

BGP

AutonomousSystem Derived from rtr.VirtualRouter

Application > Navigation Tree > Network (For each BGP instance, right click Property and check the “S Properties” tab)

BGPCluster Derived frombgp.Peer

-

BGPProtocolEndpoint bgp.Peer Application > Navigation Tree > Network (Expand to examine all BGP peers in each routing instance)

BGPService rtr.VirtualRouter Manage > Routing Instances > RouterSite > RoutingInstanceSite > Routing Instance (Use filter “BGP Enabled” equal to true)

BGPSession bgp.Peer (One for each pair) Application > Navigation Tree > Network (Expand to examine each pair of BGP peers)

Confederation Derived from rtr.VirtualRouter

-

OSPF

OSPFArea Derived fromospf.AreaSite

Application > Navigation Tree > OSPF (Only those with routing instances created)

OSPFAreaConfiguration ospf.AreaSite Manage > Routing Instances > RouterSite > SubProtocolSite > AreaSite (Routing Management OSPF)

OSPFInterface ospf.Interface Manage > Routing Instances > RouterTerminatingInterface > RouterTerminatingIpInterface > OSPF Interface (Use filter “Interface Class” equals “Numbered”)

OSPFNeighborEndpoint ospf.Neighbor Application > Navigation Tree > OSPF (Expand all the way to see each resulting Neighbor)





OSPFNeighborRelationship ospf.Neighbor (One for each pair) Application > Navigation Tree > OSPF (Expand all the way to see each pair of Neighbors)

OSPFNetwork - -

OSPFService ospf.Site Manage > Routing Instances > RouterSite > ProtocolSite > OSPF

OSPFVirtualInterface ospf.VirtualLink Application > Navigation Tree > OSPF (Expand to see each VirtualLink)

OSPFVirtualLink ospf.VirtualNeighbor (One for each pair)

Application > Navigation Tree > OSPF (Expand to see each pair of VirtualNeighbors)

OSPFVirtualNeighborEndpoint ospf.VirtualNeighbor Application > Navigation Tree > OSPF (Expand to see each resulting VirtualNeighbor)

IS-IS

ISISArea isis.Area Application >Navigation Tree >ISIS

ISISInterface isis.Interface Application >Navigation Tree >ISIS >IS-IS Interface

ISISNeighborEndpoint isis.Adjacency Application > Navigation Tree > ISIS > IS-IS Interface (Expand the IS-IS Interface)

ISISService isis.Site Application > Navigation Tree > ISIS > Area Member

MCAST

IGMPInterface igmp.Interface Manage > Routing Instances > RouterTerminatingInterface > RouterTerminatingNonIpInterface > IGMP Interface

IGMPNetwork igmp.IfGroup Application > Navigation Tree > Network (For each IGMP Instance, click Property and check the “Multicast Group/Source” tab)

MulticastGroup Derived frompim.RPSet

Application > Navigation Tree > Network (For each PIM Instance, click Property >Groups and check distinct “Group Address”)

MulticastService igmp.Sitepim.Site

Manage > Routing Instances > RouterSite > ProtocolSite > IGMP, orManage > Routing Instances > RouterSite > ProtocolSite > PIM



SAM-O element to EMC Smarts object mapping 89


MulticastSource Derived frompim.Group

Application > Navigation Tree > Network (For each IGMP Instance, right click Property > Multicast Group/Source and check all instances with “Source” equal to “.0.0.0”)

MulticastTree - -

PIMHop Derived frompim.Group

-

PIMInterface pim.Interface Manage > Routing Instances > RouterTerminatingInterface > RouterTerminatingNonIpInterface > PIM Interface

PIMSourceG pim.Group (SourceG) Application > Navigation Tree > Network (For each PIM Instance, click Property > Groups and check instances with “Source Type” equal to “SG”)

PIMStarG pim.Group (StarG) Application > Navigation Tree > Network (For each PIM Instance, click Property > Groups and check all with “Source Type” equal to “StarG”)




APPENDIX BMapping of Smarts objects and SAM-O Objects

The Adapter for Alcatel-Lucent 5620 SAM EMS uses SOAP/XML over HTTP to perform a full network inventory from the Alcatel-Lucent 5620 SAM-O interface and create the topology, mapping SAM-O objects to EMC Smarts objects. This appendix includes the following information:

• Discovered inventory objects .................................................................................. 92• Mapping of SAM-O equipment objects .................................................................... 93• Mapping of SAM-O service objects .......................................................................... 98

Mapping of Smarts objects and SAM-O Objects 91

Mapping of Smarts objects and SAM-O Objects

Discovered inventory objectsTable 7 on page 92 lists the discovered Alcatel-Lucent 5620 SAM EMS inventory objects.

Table 7 Adapter support for 5620 SAM EMS inventory

Inventory Discovered objects

Physical inventory All SAM-O objects listed in Table 9 on page 98

MPLS inventory • apipe.Apipe, apipe.L2AccessInterface, apipe.Site• cpipe.Cpipe, cpipe.Site• epipe.Epipe, epipe.L2AccessInterface, epipe.Site• fpipe.Fpipe, fpipe.L2AccessInterface, fpipe.Site• ipipe.Ipipe, ipipe.L2AccessInterface, ipipe.Site• ldpInterface, ldpTargetPeer• mpls.CrossConnect, mpls.Interface, mpls.LspPath• rtr.RouteStats• svt.MeshSdpBinding, svt.SdpBinding, svt.SpokeSdpBinding,

svt.TransportConnection• vll.L2AccessInterface, vll.Site, vll.Vll• vpls.L2AccessInterface, vpls.Site, vpls.Vpls• vprn.Site

Multicast inventory • igmp.IfGroup, igmp.Interface, igmp.Site• pim.Group, pim.Interface, pim.Neighbor, pim.RPSet• service.SpokeConnector• svt.MeshSdpBinding• vpls.L2AccessInterface

BGP inventory • bgp.Peer• rtr.VirtualRoute

OSPF inventory • ospfAreaSite• ospfInterface• ospfNeighbor• ospfSite• ospfVirtualLink• ospfVirtualNeighbo

IS-IS inventory • isis.Area• isis.AreaMember• isis.Site• isis.Interface• isis.Adjacency• isis.InterfaceLevelOneConfig



Mapping of SAM-O equipment objectsTable 8 on page 93 maps SAM-O equipment classes to EMC Smarts objects.

Table 8 Mapping of SAM-O equipment objects to EMC Smarts class (page 1 of 6)

EMC Smarts classEMC Smarts attribute

SAM-O equipment class SAMO-O property SAM-O filter

Router/Switch (unless stated otherwise)

netw.NetworkElement -

Model - chassisType

HostsAccessPoints -> IP

- ipAddress

Name - objectFullName

DisplayName - siteName

HostsAccessPoints -> IP (loopback address)

- systemAddress

Card (unless stated otherwise) equipment.BaseCard siteName

AdminStatus - administrativeState

IsManaged - equipmentState


OperStatus - operationalState

PartOf -> Chassis - siteId

Processor equipment.ControlProcessorequipment.SwitchFrabicProcessor

siteName

DisplayName - displayedName


Card equipment.DaughterCard

siteName





Description - specificType

Fan equipment.FanTray siteName


Status - deviceState

DeviceID - fanId

Mapping of SAM-O equipment objects 93


Description - hwName



Partof -> Router/Switch

- siteId

Memory equipment.FlashMemory

siteName

FreeMemory - amountUsed

TotalMemory - capacity



BufferUtilizationPct - percentageUsed

Cable equipment.PhysicalLink

siteName

DisplayName - endpointAPointer

DisplayName - endpointBPointer


Interface equipment.PhysicalPort

siteName


DisplayName - SiteName + cardSlotId + daughterCardSlotId + portId+ displayedName

Description - description

OperStatus - equipmentState

MAC HostedBy -> Router/Switch

- macAddress

MaxTransferUnit - mtuValue


PartOf -> Router - siteId

Type - specificType

MaxSpeed - speed

PowerSupply equipment.PowerSupplyTray

siteName

AC VoltageSensor Status - acVoltageStatus






DC VoltageSensor Status - dcVoltageStatus

Description - hwName


Status - operationalState

DisplayName - powerSupplyId+ siteName

PowerSupply1 Status

- powerSupply1Status

PowerSupply2 Status

- powerSupply2Status

TemperatureSensor HighThreshold - psTemperatureThreshold

Status - temperatureStatus

PartOf -> Router/Switch

- siteId

Card equipment.ProcessorCard

siteName

Adminstatus - administrativeState






- siteId

- specificType

IsManaged - olcState

An entry in AD_PersistentDataSet l2fib.FibEntry nodeNameterminationTypeserviceType

- definedPerObjectPointer

- macAddress

- objectFullName

- serviceId

An entry in AD_PersistentDataSet l2fib.MFibEntry serviceSiteId

- grpAddr






- objectFullName

- portId

- serviceId

NetworkAdapterRedundancyGroup

lag.Interface siteName



DisplayName - displayedName+ - siteName




- siteId

create relationship between NetworkAdapterRedundancyGroup and its Interfaces

lag.PortTermination siteName

- terminatedPortPointer

Interface rtr.NetworkInterface nodeId

MaxTransferUnit - actualMtu



DisplayedName - displayedName

InterfaceNumber - id

Description - interfaceClass


- nodeId

DisplayName Qualifier

- nodeName



Underlying -> IP - primaryIPv4Address

LayeredOver -> -

Interface - terminatedObjectPointer






- terminatedPortClassName

Interface sonetEquipment.Sts1ChannelsonetEquipment.Sts3ChannelsonetEquipment.Sts12ChannelsonetEquipment.Sts48ChannelsonetEquipment.Sts192ChannelsonetEquipment.Tu3Channel

siteName


DisplayName - SiteName + cardSlotId + daughterCardSlotId + portId + displayedName






MaxSpeed - speed

Interface tdmequipment.DS0ChannelGrouptdmequipment.DS1E1Channeltdmequipment.DS3E3Channel

siteName


DisplayName - SiteName + cardSlotId + daughterCardSlotId + portId + displayedName









Mapping of SAM-O service objectsTable 9 on page 98 lists the SAM-O service objects the Adapter retrieves and the methods used.



MaxSpeed - speed




Table 9 Mapping of SAM-O service objects to EMC Smarts objects (page 1 of 13)

EMC Smarts object EMC Smarts attributeSAM-O equipment class SAM-O property SAM-O filter

BGPProtocolEndpointBGPClusterBGPSession

bgp.Peer siteName

PeerAdminStatus - administrativeState

IsRouteReflector - clusterId

PeerState - connectionState

LocalAddress - localAddress


Name - peerAddress

RemoteAs - peerAS

HostedBy -> Router/Switch

- siteId

DisplayName - siteName+ peerAddress

Interface ies.L3AccessInterface nodeNameserviceId



Description - description, - interfaceClass



ComposedOf -> Router/Switch

- nodeId






- primaryIPv4PrefixLength

LayeredOver -> Interface

- terminatedObjectPointer


IGMPNetwork igmp.IfGroup

GroupAddress - group


LastReportingAddress - srcAddrOfLastReport

IGMPInterface igmp.Interface nodeName


igmpIfJoins - groupCount

PollingIndex, InterfaceNumber

- interfaceId

DisplayName - nodeName


InterfaceStatus - operationalState

InterfaceQuerier - querier



MulticastService igmp.Site



- siteId


LdpProtocolEndpointLdpAdjacency

ldp.Interface -

AdjacencyHoldTime - keepAliveTimeout


LocalAddress - nodeId

DisplayName - siteId+ portName



Mapping of SAM-O service objects 99


Index - interfaceId


- terminatedPortPointer

PeerAddress - peerAddress



LdpProtocolEndpointLdpAdjacency

ldp.TargetedPeer

AdjacencyHoldTime - keepAliveTimeout


LocalAddress - siteId

Index - interfaceId

PeerAddress - peerAddress



MPLSService mpls.Interface

HostedBy ->Router/Switch

- nodeId

name - nodeName



LSP mpls.LspPathmpls.DynamicPathsvt.Tunnel

fromNodeName

Source - fromNodeId

DisplayName - fromNodeName + toNodeName + lspId

Name - lspName

Description - objectFullName


LSPId mpls.LspPathsvt.Tunnel

OSPFAreaOSPFAreaConfiguration

ospf.AreaSite






AreaID - areaId

AreaType - importAsExtern

PropagateSummaries - areaSummary

DisplayName - siteName+ areaId

OSPFInterface ospf.Interface nodeName


DisplayName - displayedName+ nodeName

DiscoveredAreaID - areaId

IfType - interfaceType

TransitDelay - transitDelay

RetransmitInterval - retransmissionInterval

HelloInterval - helloInterval

DemandInterface - demandProceduresEnabled





hostedBy ->Router/Switch

- nodeId

RouterPriority - priority

DesignatedRouter - designatedRouterId

BackupDesignatedRouter

- backupDesignatedRouterId

AuthKey - authenticationKey

AuthType - authenticationType

DeadInterval - routerDeadInterval

OSPFNeighborEndpoint ospf.Neighbor siteName


NeighborState - operationalState





NbmaNeighborPermanence

- permanence

HelloSupressed - helloSuppressed

Description - neighboringIpAddress

NeighborRouterId - neighboringRouterId

OSPFService ospf.Site -


DisplayName - siteName+ areaId

RouterID - ospfRouterId


IsABR - isAreaBorderRouter

IsASBR -isAutonomousSystemBorderRouter

OSPFVirtualInterface ospf.VirtualLink siteName


IfState - operationalState

LayeredOver -> Interface, LayeredOver -> IP

- localEgressIfIpAddress

AuthKey - authenticationKey

AuthType - authenticationType


DeadInterval - routerDeadInterval

RetransmitInterval - retransmissionInterval

TransitDelay - transitDelay

OSPFVirtualNeighbor ospf.VirtualNeighbor siteName

HelloSupressed - helloSuppressed

Description - ipAddress


NeighborState - operationalState





Displayname - siteName+ - virtualNeighborRouterId

MulticastSourcePIMSourceGPIMStarG

pim.Group

GroupAddress - groupAddress


UpstreamNeighborAddress

- rpfNbrAddress

PollingIndex - rpfIfIndex

SourceAddress - sourceAddress

InRPTable - sourceRPAddress

DisplayName - siteName + sourceAddress + groupAddress

PIMInterface pim.Interface interfaceClass


DRAddress - drIPAddress


PollingIndex - interfaceId


- nodeId


InterfaceStatus - operationalState



pim.Neighbor

- neighboringIpAddress

- objectFullName

MulticastGroup pim.RPSet

- objectFullName

Name - rpGroupIPAddress

GroupNetmask - rpGroupMask





MulticastService pim.Site



- siteId


BSRAddress - bsrAddress

RPAddress - crpAddress

- bsrCandidatePriority

rtr.RouteStats

- monitoredObjectPointer

- routesInVrf

- timeCaptured

AutonomousSystemBGPServiceConfederation

rtr.VirtualRouter bgpEnabled

AS - autonomousSystemNumber

DisplayName - confederationAutonomousSystemNumber+ siteName


service.SpokeConnector

firstSvcPointersecondSvcPointer

- compositeSvcPointer

- firstSiteId

- firstSvcPointer

- firstTunnelPointer

- secondSiteId

- secondSvcPointer

- secondTunnelPointer

ForwarderEndpoint. svt.MeshSdpBindingsvt.SdpBindingsvt.SpokeSdpBinding

fromNodeNameserviceId serviceType





TunnelType - circuitTransport

HostedBy -> Switch/Router

- fromNodeId


Status - operationalState

DisplayName - pathId + serviceId + vcId + toNodeId + fromNodeName

TunnelName - pathname

- returnCircuitPointer

PeerAddress - toNodeId

VC_ID - vcId

Create relationship between VRF and LSPPIMInterface

svt.TransportConnection

fromNodeIdtunnelId

- fromNodeName

- resourceId

- resourcePointer

- toNodeId

- toNodeName

NetworkConnection(for GRE Tunnel)

svt.Tunnel underlyingTransport

Build ConnectedSystems and ConnectedTo Relationships

- toCtp

Build ConnectedSystems and ConnectedTo Relationships

- fromCtp

Interface DisplayName - fromNodeName

Interface DisplayName - toNodeName

Interface AdminStatus - administrativeState

Interface OperStatus - operationalState

Interface part of -> Router/Switch

- sourceNodeId





Interface part of -> Router/Switch

- destinationNodeId

Interface Name - objectFullName

Interface vll.L2AccessInterfaceapipe.L2AccessInterfaceepipe.L2AccessInterfacefpipe.L2AccessInterfaceipipe.L2AccessInterface

nodeName



Creates relationship based on this parameter



- nodeId








Forwarder vll.Siteapipe.Siteepipe.Sitefpipe.Siteipipe.Site

siteId

VPNName - serviceId



- siteId

- operationalState






VPN(VPNs will be created by MPLS postprocessing)

vll.Vllapipe.Apipeepipe.Epipefpipe.Fpipeipipe.Ipipe

Interface vpls.L2AccessInterface

outerEncapValueserviceTypenodeNameterminatedPortClassName



- nodeId

DisplayName - nodeName+ displayedName





Creates relationship based on this parameter


Forwarder vpls.Site

VPNName - serviceId



- siteId

- operationalState


VPN(VPNs will be created by MPLS postprocessing)

vpls.Vpls

Interface vprn.L3AccessInterface

nodeName





Description - interfaceClass





- l3InterfaceAdministrativeState

LayeredOver -> Router/Switch

- nodeId




- primaryIPv4Length

- serviceId



Create relationship based on this parameter


IsManaged olcState

VPN / VRF / MPLSService vprn.Site siteId

VRF Name - objectFullName

- operationalState

DisplayName - serviceId+ siteId

- serviceName

MPLSService Name - siteId

VRF Description - subscriberName

- adminstrativeState


Tag - routedistinguisher

MPLSService DisplayName - siteName

ISISArea Isis.Area

AreaID areaID

Description areaDescription

DisplayName displayedName

Name objectFullName

ConnectedSystems->Router

siteId





ConsistsOf->ISISService

Isis.AreaMember siteId

ISISInterface Isis.Interface

AdminStatus administrativeState

DiscoveredAdminStatus

administrativeState

DisplayName nodeName

Description description

IfType interfaceType

IsPassive passive

RetransmitInterval retransmitInterval

Accesses->ISISService nodeId

HostedBy->Router nodeId

LayeredOver->Interface, IP

terminatedObjectPointer

HelloInterval Isis. InterfaceLevelConfig

helloInterval

RouterPriority priority

MulticastForwarding Isis.Site multicastImport/unicastImport

MemberOf->ISISArea

ISISNeighborEndpoint Isis.Adjacency

Name objectFullName

Description siteName

DisplayName siteName

NeighborIpAddress adjNeighbourId

NeighborState adjState

NeighborSystemID neighSysId

LocalAddress localIp

HostedBy->Router siteId

LayeredOver->ISISInterface

terminatedObjectPointer

ISISService Isis.Site

AdminStatus administrativeState





DisplayName siteName

Name objectFullName

ServiceType levelCapability

SystemID isisSystemId

HostedBy->Router




APPENDIX CMapping of SAM-O Objects and Smarts Notifications

The Adapter for Alcatel-Lucent 5620 SAM EMS uses the EMC Smarts patented Codebook Correlation Technology to do root-cause analysis. This analysis is based on many factors in the managed network, including, but not limited to, Operational or Administrative status. However, when the Alcatel-Lucent 5620 SAM EMS server generates either administrativeState or operationalState information for a component, the Adapter stores this information in a repository object. This appendix includes the following contents:

• Element to notification mapping ........................................................................... 112

Mapping of SAM-O Objects and Smarts Notifications 111

Mapping of SAM-O Objects and Smarts Notifications

Element to notification mappingTable 10 on page 112 describes how the administrativeState or operationalState information may be mapped to the notifications that are displayed in the Global Console, based on this and other considerations.

Table 10 Mapping of Alcatel-Lucent elements to notifications (page 1 of 6)

Alcatel-Lucent EMC Smarts

Class state name and value Status attribute and value Class

equipment.BaseCardequipment.DaughterCard

administrativeState:- 2 (inService)

equipmentState:- 5 (equipmentMissing)

olcState (EMS >= 6.1)- 1 (maintenance) - 2 (inService)

EMS >= 6.1:- olcState inService, admin inService, equip not missingALL OTHERS EMS < 6.1:- admin inService, equip not missingALL OTHERS

operationalState:- 1 (unknown)- 8 (provisioned)- 2 (inService)- 10 (upgrade)- 11 (downgrade)- 12 (inServiceUpgrade)- 13 (inServiceDowngrade)

IsManaged:

- true

- false

- true- false

Status:- UNKNOWN- NOTPRESENT- OK- OK- OK- OK- OK

Card(BaseCard, DaughterCard)

equipment.ProcessorCard Mappings on operationalState and administrativeState are the same as Base/Daughter cards

Card(Processor Card)

equipment.ControlProcessor redundantStatus:- 2 (redundantActive)- 3 (redundantStandby)- 4 (redundantSplit)- 6 (redundantSynching)ALL OTHERS

StandbyStatus:- ACTIVE- INACTIVE- UNKONWN_STANDBY- OTHER_STANDBY- NOTAPPLICABLE

Card(Processor Card)



equipment.PhysicalPort administrativeState:- 1 (noop)- 2 (inService)

operationalState:- 1 (unknown)- 2 (inService)

equipmentState:- 5 (equipmentMissing)- 13 (indeterminate)

AdminStatus:- UNKNOWN- UP

OperStatus:- UNKNOWN- UP

- OTHER- UNKNOWN

Interface(Port)

equipment.FanTray deviceState:- 1 (deviceStateUnknown)- 3 (deviceStateOk) - 4 (deviceStateFailed)

Status:- UNKNOWN- OK- CRITICAL

FAN

equipment.PowerSupplyTray administrativeState:- 2 (inService)

operationalState:- 1 (unknown)- 8 (provisioned)- 2 (inService)

- admin inService, oper unKnown- admin inService, oper provisioned- admin inService, oper inService

Status:

- UNKNOWN- UNKNOWN- OK

PowerSupply

temperatureStatus:- 1 (deviceStateUnknown)- 3 (deviceStateOk) - 4 (deviceStateFailed)


TemperatureSensor

acVoltageStatus/dcVoltageStatus:- 1 (deviceStateUnknown)- 3 (deviceStateOk) - 4 (deviceStateFailed)


VoltageSensor

tdmequipment.DS0ChannelGrouptdmequipment.DS1E1Channeltdmequipment.DS3E3Channel

Refer to equipment.PhysicalPort

Interface (Channel)


Element to notification mapping 113


sonetequipment.Sts1Channelsonetequipment.Tu3Channelsonetequipment.TributaryChannelsonetequipment.Sts12Channelsonetequipment.Sts48Channelsonetequipment.Sts192Channel

Refer to equipment.PhysicalPort

Interface(Channel)

vll.L2AccessInterfaceapipe.L2AccessInterfaceepipe.L2AccessInterfaceipipe.L2AccessInterfacefpipe.L2AccessInterfacecpipe.L2AccessInterfacevpls.L2AccessInterfacemvpls.L2AccessInterface

ies.L3AccessInterfacevprn.L3AccessInterface

administrativeState:- 1 (serviceUp)- 2 (serviceDown)ALL OTHERS

operationalState:- 1 (serviceUp)- 2 (serviceDown)ALL OTHERS

AdminStatus:- UP- DOWN- UNKNOWN

OperStatus:- UP- DOWN- UNKNOWN

Interface (L2SAP, L3SAP)

N/A The Alcatel-Lucent 5620 SAM EMS does not track IPs as objects with administrative or operational states.

The Adapter sets IPStatus in parallel with the Underlying Interface operationalState. IPs do not have administrativeStatus in EMC Smarts software.• If an Interface is DOWN,

IPStatus is set to TIMEDOUT• Otherwise, IPStatus is set to

OK.

IP

mpls.DynamicLsp administrativeState:- 1 (LspUnknown)- 2 (LspUp)- 3 (LspDown)

operationalState:- 1 (LspUnknown)- 2 (LspUp)- 3 (LspDown)

AdminStatus:- Unknown- Up- Down

OperStatus:- Unknown- Up- Down

LSP

lag.Interface administrativeState:- 2 (portInService)- 3 (portOutOfService)ALL OTHERS

operationalState:- 2 (portInService)- 3 (portOutOfService)- 5 (portFailed)ALL OTHERS


OperStatus:- UP- DOWN- DOWN- UNKNOWN

NetworkAdapterRedundancyGroup




vpls.Sitemvpls.Sitevll.Siteapipe.Sitecpipe.siteepipe.Sitefpipe.Siteipipe.Site

administrativeState:- 1 (serviceUp)- 2 (serviceDown)ALL OTHERS




Forwarder

svt.SdpBindingsvt.SpokeSdpBindingsvt.MeshSdpBinding

administrativeState:- 1 (circuitUp)- 2 (circuitDown) ALL OTHERS

operationalState:- 1 (circuitUp)- 5 (circuitDown) ALL OTHERS



ForwarderEndpoint

vprn.site administrativeState:- 1 (serviceUp)- 2 (serviceDown)ALL OTHERS




VRF

ldp.Interfaceldp.TargetedPeer

administrativeState:- 2 (tmnxInService)- 3 (tmnxOutOfService)ALL OTHERS

operationalState:- 2 (tmnxInService)- 3 (tmnxOutOfService)ALL OTHERS

AdminStatus:- ENABLE- DISABLE- UNKNOWN

OperStatus:- ENABLE- DISABLE- UNKNOWN

LdpProtocolEndpoint

bgp.Peer administrativeState:- 1 (bgpDown) - 2 (bgpUp)ALL OTHERS

connectionState:- 1 (idle)- 2 (connect)- 3 (active)- 4 (opensent)- 5 (openconfirm)- 6 (established) ALL OTHERS

PeerAdminStatus:- STOP- START- UNKNOWN

PeerState:- IDLE- CONNECT- ACTIVE- OPENSENT- OPENCONFIRM- ESTABLISHED- UNKNOWN

BGPProtocolEndpoint




ospf.Site administrativeState:- 0 (ospfUnknown)- 1 (ospfUp)- 2 (ospfDown)

AdminStatus:- UNKNOWN- ENABLE- DISABLE

OSPFService

ospf.Interfaceospf.VirtualLink

administrativeState:- 1 (ospfInterfaceEnabled)- 2 (ospfInterfaceDisabled)

operationalState:- 1 (ospfInterfaceDown)- 2 (ospfInterfaceLoopBack)- 3 (ospfInterfaceWaiting)- 4 (ospfInterfacePointToPoint)- 5 (ospfInterfaceDesignatedRouter)- 6 (spfInterfaceBackupDesignatedRouter)- 7 (ospfInterfaceOtherDesignatedRouter)ALL OTHERS

AdminStatus:- ENABLED- DISABLED

IfState:- DOWN- LOOPBACK- WAITING- POINT_TO_POINT- DESIGNATED_ROUTER- BACKUP_DESIGNATED_ROUTER- OTHER_DESIGNATED_ROUTER- UNKNOWN

OSPFInterface

ospf.Neighborospf.VirtualNeighbor

operationalState:- 1 (ospfNeighborDown)- 2 (ospfNeighborAttempt)- 3 (ospfNeighborInit)- 4 (ospfNeighborTwoWay)- 5 (ospfNeighborExchangeStarted)- 6 (ospfNeighborExchange)- 7 (ospfNeighborLoadin)- 8 (ospfNeighborFull)ALL OTHERS

NeighborState:- DOWN- ATTEMPT- INIT- TWO_WAY- EXCHANGE_START- EXCHANGE- LOADING- FULL- UNKNOWN

OSPFVirtualInterface

pim.Interface administrativeState:- 2 (pimUp)- 3 (pimDown)

operationalState:- 2 (pimUp)- 3 (pimDown)

- admin DOWN- admin UP, oper UP- admin UP, oper DOWN ALL OTHERS

InterfaceStatus:

- NOTREADY- ACTIVE- NOTINSERVICE- UNKNOWN

PIMInterface




igmp.Interface administrativeState:- 2 (tmnxInService)- 3 (tmnxOutOfService)

operationalState:- 2 (tmnxInService)- 3 (tmnxOutOfService)

- Admin OutOfService- Admin InService, oper InService- Admin InService, oper OutOfServiceALL OTHERS

InterfaceStatus:

- NOTREADY- ACTIVE- NOTINSERVICE

- UNKNOWN

IGMPInterface

isis.Site administrativeState:- 1 (isisDown)- 2 (isisUp)ALL OTHERS

AdminStatus:- DISABLED- ENABLED- UNKNOWN

ISISService

isis.Interface administrativeState:- 1 (isisDown)- 2 (isisUp)ALL OTHERS

AdminStatus:- DISABLED- ENABLED- UNKNOWN

ISISInterface

isis.Adjacency adjState:- 1 (adjInitializing)- 2 (adjUp)-3 (adjFailed)- 4 (adjDown)ALL OTHERS

NeighborState:- INIT- UP- FAILED- DOWN- UNKNOWN

ISISNeighborEndpoint





APPENDIX DNotification Log Entries

Alarms and events received from the Alcatel-Lucent 5620 SAM EMS are processed by various EMC Smarts Domain Managers (MPLS Manager, Multicast Manager, IP Availability Manager, Network Protocol Manager for BGP, Network Protocol Manager for OSPF, Network Protocol Manager for IS-IS, and the Adapter Platform). Root-cause and impact analysis and diagnoses created by these Domain Managers are provided to the operator through the Notification Log of the Global Console, a component of the EMC Smarts Service Assurance Manager. This appendix includes the following contents:

• Notification Log entries ......................................................................................... 120

Notification Log Entries 119

Notification Log Entries

Notification Log entriesThe Notification Log includes two general types of entries: event notifications from the Domain Managers and alarm (problem) notifications forwarded from the Alcatel-Lucent 5620 SAM EMS. Table 11 on page 120 describes some of the EMC Smarts notification entries generated by the Domain Managers, their meanings, and possible indicated actions. This table is organized by Element and Notification.

Table 11 Global Console notifications (page 1 of 4)

Element Notification

Event, problem, or impact Description

ASA (the Adapter)

AlcatelConnectionLost-<AdapterName>

Event Indicates that the connection with the EMS has been lost.

BGPSession Disconnected Event This event is based on a BGPSession's two BGPProtocolEndpoints. If neither of the endpoints are administratively down and at least one of them does not have PeerState = ESTABLISHED, then the BGPSession is considered to be Disconnected. An endpoint's PeerState is set from the Alcatel-Lucent 5620 SAM EMS's report of the connectionState of the endpoint (it should show as ESTABLISHED in 5620 SAM). This leads directly to the BGPSession Down problem.

Down Problem Results directly from a BGPSession Disconnected event unless there is another explanation for the Disconnected event.

Card Down Problem Determined when the operational state of a card is CRITICAL (that is, down). The operational state of a card in EMC Smarts is taken from the 5620 SAM’s report of operational state for it, which can include UNKNOWN, OK, and CRITICAL. Note that 5620 SAM reports cards as down (CRITICAL) if the card slot is provisioned but no card is present. Additionally, a Base card being Down will consume DaughterCard Down diagnoses. DaughterCard Down diagnoses will consume physical port Interfaces being Down.

ForwarderEndpoint

Down Problem Indicates that the operational or administrative status of the ForwarderEndpoint is down. This event is implemented only for Juniper devices.

IGMPInterface Unreachable Problem Results when the InterfaceStatus of the IGMPInterface is NOTINSERVICE or NOTREADY. Such InterfaceStatus values occur when the 5620 SAM reports that the operational state or administrative state of the IGMPInterface is Down.In the case of IGMPInterfaces that are based on VPLS-mode Multicast configurations, these InterfaceStatuses are based on the states of the underlying Interfaces. Note that even when the IGMPInterface is deemed unreachable, specific multicast groups are not shown as impacted.



Interface Down Problem Detected when a Physical Port Interface or a Service Interface has an operational state of DOWN and an administrative state of UP. These are values reported directly by 5620 SAM and inserted by the adapter into IP AM. For Network Interfaces, if they are not Network Connected to other Network Interfaces, the same conditions (Oper Down, Admin Up) will conclude they are Down. The presence of a Network Connection will cause a different diagnosis to be concluded. Note that an Interface Down does not by itself impact objects that use the Interface. For example, OSPF Services will be Impacted if the OSPFInterfaces are Down, not the network or physical interfaces. Presumably if either of the latter were truly Down, the OSPFInterface would also be reported Down by the 5620 SAM.

ISISAdjacency Down Problem Results from ISISAdjacency NeighborStateAlarm eventIf the neighbor ISISInterface on both side of ISISAdjacency are POINT_TO_POINT type, and at least one side of ISISInterface is down, the NPM IS-IS manager will send NeighborStateAlarm event to the Notification log.

LSP Impacted Impact LSP impacts may have reported Caused Bys such as Router Down. In the 5620 SAM environment there are scenarios where these Impacts can be notified without Caused By being present. This will happen when the 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. If the user navigates to the LSP in question then it will be IsDownInRemote.

OSPFService ABRNotInBackbone Event By default, NPM Manager for OSPF sends this event to the Notification Log. This event recognizes that there is an OSPFService that is an Area Border Router, it is not in the backbone (area 0.0.0.0), and it has associated OSPFInterfaces.

PIMInterface PIMInterfaceUnreachable

Problem Results when the InterfaceStatus of the PIMInterface is NOTINSERVICE or NOTREADY. Such InterfaceStatus values occur when the 5620 SAM reports the operational state or administrative state of the PIMInterface is Down. In the case of PIMInterfaces which are based on VPLS-mode Multicast configurations, these InterfaceStatuses are based on the states of the underlying Interfaces. Note that even when the PIMInterface is deemed unreachable, specific multicast groups are not shown as impacted.




Notification Log entries 121


Router Down Problem A Router Down problem is diagnosed when a router is unresponsive and there is no better explanation. If an Interface outage or SNMPAgent outage might explain the router's being unresponsive, those are concluded.Router Down is a precondition for a number of impacts in various EMC Smarts servers, particularly impacts in the Multicast domain.The diagnosis of Router Down does not eliminate the Interface Down notifications.

Unresponsive Event An Unresponsive event is triggered when a Router's IP Statuses and SnmpManager are all set to Unresponsive. This happens when the Alcatel-Lucent 5620 SAM EMS emits an alarm-243 (SnmpReachabilityProblem) for a given Router.These attributes are reset to OK when the alarm clears.

VPN Impacted Impact VPN impacts may have reported Caused By diagnoses such as Router Down. In the 5620 SAM environment, there are scenarios where these Impacts can notified without Caused By being present. This will happen when 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. However, the user cannot see this relationship from the information in the Notification Log. To find the specific LSP causing the impact, you must navigate through the VPN's VRFs; for each VRF, examine the LSPs it is LayeredOver to see which one of them will be IsDownInRemote.






VRF Down Problem A VRF is determined to be Down when 1) it is operationally Down, and 2) it is not LayeredOver any Interfaces or if all the Interfaces that it is Layered Over are Down.

Impacted Impact VRF impacts may have reported Caused By diagnoses such as Router Down. In the 5620 SAM environment there are scenarios where these Impacts can notified without Caused By being present. This will happen when 5620 SAM reports an LSP's operational state to be Down. When this happens, the LSP's IsDownInRemote attribute is set to True. However, the user cannot see this relationship from the information in the Notification Log. The solution to this is navigating to the VRF in question and then examining the LSPs it is LayeredOver; one of them will be IsDownInRemote.

NoRoutes Event Event is triggered when the NumberOfRoutes attribute in the VRF is 0. This value is supplied by the 5620 SAM rtr.RouteStats <routesInVrf> attribute. Note that the 5620 SAM will only provide data on the number of routes in a VRF if the VRF’s Route Distinguisher type is set to Type0 or Type1.

WarningThresholdCrossed

Event You can set values in the MPLS Manager for a warning threshold and a max value, as described in the EMC Smarts MPLS Manager User Guide. These events are triggered when a VRF's NumberOfRoutes reaches these respective values. As with the NoRoutes event, the NumberOfRoutes is set by the Adapter based on information kept in the 5620 SAM. The 5620 SAM will only track this information for VRFs that are configured to have Route Distinguishers.

MaxRoutesReached Event




Notification Log entries 123



APPENDIX ELogs

This appendix provides an overview of the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS log functionality for startup, discovery, and JMS message processing.


• Adapter log file ..................................................................................................... 126• Startup sequence.................................................................................................. 126• Discovery Log messages ....................................................................................... 129• Event messages .................................................................................................... 132• Alarm messages.................................................................................................... 133• Queue Log messages ............................................................................................ 134• Warning messages................................................................................................ 134

Logs 125

Logs

Adapter log fileThe Adapter maintains a log file in the standard InCharge log directory, <ASAM_BASEDIR>/smarts/local/logs.

The Adapter logs informational messages, warnings, and severe errors at a configurable log verbosity default value. You can increase the log verbosity on a short-term basis during Adapter troubleshooting. Note that the messages logged are not intended to be understood by non-developers and the messages may change every code release.

Startup sequenceThis section describes logging for the startup sequence, including the following:

• “Loading mappings” on page 126

• “Starting up the server” on page 127

• “Connecting to Domain Managers” on page 128

• “Establishing the JMS connection” on page 128

Loading mappings

The following example shows the sequence as various mappings are loaded.

[December 14, 2009 5:40:01 PM EST +937ms] t@3192 ICIM-PortTypeMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadEquipmentTypeMap.asl: Creating GA_StringDictionary::PortTypeMap

[December 14, 2009 5:40:01 PM EST +937ms] t@3188 ICIM-PortTypeConversionMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::PortTypeConversionMap

[December 14, 2009 5:40:01 PM EST +937ms] t@3184 ICIM-InstrumentationClassMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::InstrumentationClassMap

[December 14, 2009 5:40:01 PM EST +953ms] t@3176 ICIM-EquipmentInterfaceStatsMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::equipment.InterfaceStats

[December 14, 2009 5:40:01 PM EST +953ms] t@3160 ICIM-EquipmentInterfaceAdditionalStatsMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::equipment.InterfaceAdditionalStats

[December 14, 2009 5:40:01 PM EST +953ms] t@3172 ICIM-BGPTopologyCollectionMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::BGPTopologyCollection

[December 14, 2009 5:40:01 PM EST +953ms] t@3168 ICIM-ISISTopologyCollectionMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::ISISTopologyCollection


Logs

[December 14, 2009 5:40:01 PM EST +953ms] t@3196 ICIM-OSPFTopologyCollectionMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::OSPFTopologyCollection

[December 14, 2009 5:40:01 PM EST +953ms] t@3180 ICIM-MCASTTopologyCollectionMap-Driver

ASL_MSG-*-ASLP-alcatel-sam/loadSimpleMap.asl: Creating GA_StringDictionary::MCASTTopologyCollection

Starting up the server

The following example shows the sequence during startup.

[December 14, 2009 5:39:58 PM EST +421ms] t@3292 InCharge FrameworkASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: Initializing JVM interface...

[December 14, 2009 5:39:58 PM EST +421ms] t@3292 InCharge FrameworkASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: JVM Interface initialization

complete.

[December 14, 2009 5:40:01 PM EST +437ms] t@3292 InCharge FrameworkASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: JVM has been created.

[December 14, 2009 5:40:01 PM EST +921ms] t@3292 InCharge FrameworkICF_MSG-*-ICF_LICENSEDFEATURE-Enabling the following licensed

feature(s): ASAM Adapter

[December 14, 2009 5:40:02 PM EST +468ms] t@3324ICF_MSG-*-ICF_RECONFIGURESTART-PolicyManager: reconfigure started

[December 14, 2009 5:40:02 PM EST +859ms] t@3324ICF_MSG-*-ICF_RECONFIGUREFINISH-PolicyManager: reconfigure finished

[December 14, 2009 5:40:03 PM EST +359ms] t@4016 dmbootHTTP-W-FPO-Listening for HTTP requests on IPv4 port 63680

[December 14, 2009 5:40:03 PM EST +359ms] t@4016 dmbootRSRV-N-DMSTARTED-Domain Manager ASAM started on qa-vmw2k8b:63680

[December 14, 2009 5:40:03 PM EST +609ms] t@3304ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] SmAdapterSettings

ready.

[December 14, 2009 5:40:03 PM EST +609ms] t@4016 dmbootRSRM-*-RSRM_SUITE_VERS-Suite version: ALCATEL_SAM_SUITE:

V3.2.0.0/64(94533), 14-Dec-2009 09:11:37 Copyright 1995-2009, EMC Corporation - Build 31

DMT V9.0.0.1/64(93634), 06-Nov-2009 21:50:28 Copyright 1995-2009, EMC Corporation - Build 1204

Startup sequence 127

Logs

Connecting to Domain Managers

The following example shows the sequence for connecting to various Domain Manager repositories.

[December 16, 2009 11:53:14 AM EST +532ms] t@69ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to

InCharge repository [INCHARGE-AM-PM] via broker [fish:3680]


InCharge repository [INCHARGE-OI] via broker [fish:3680]


InCharge repository [INCHARGE-MPLS-TOPOLOGY] via broker [fish:3680]


InCharge repository [INCHARGE-BGP] via broker [fish:3680]


InCharge repository [INCHARGE-OSPF] via broker [fish:3680]


InCharge repository [INCHARGE-MCAST] via broker [fish:3680]


InCharge repository [INCHARGE-ISIS] via broker [fish:3680]

Establishing the JMS connection

The following shows an example startup sequence for a JMS connection, including the IP address of the active JMS server and the EMS version.

ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.

[December 16, 2009 11:53:34 AM EST +821ms] t@133ASAM_MESSAGE-*-INFO-.[Connector] Completed createTopicSession with

AUTO_ACKNOWLEDGE

[December 16, 2009 11:53:35 AM EST +011ms] t@132ASAM_MESSAGE-*-WARNING-.[MessageToEventConverter] StateChangeEvent

status:systemInfo PrimaryIP:10.9.252.54

[December 16, 2009 11:53:35 AM EST +012ms] t@132ASAM_MESSAGE-*-WARNING-.[MessageToEventConverter] JMS active server is

10.9.252.54

[December 16, 2009 11:53:35 AM EST +117ms] t@133ASAM_MESSAGE-*-INFO-.[Connector] 5620Sam EMS version detected:

7.0.R3.0


Logs

Discovery Log messagesThe Adapter logs discovery status messages during a full discovery. These log messages can be used to determine discovery progress. For example, you can use a grep command to monitor discovery times, as follows:

grep “Discovery completed” IC-ASAM.log

Discovery log examples

The following example shows the sequence of Discovery Log messages, including step completion and warning messages.

[December 16, 2009 11:53:26 AM EST +986ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Full Discovery starting. Available

memory:29514448

[December 16, 2009 11:53:39 AM EST +005ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Router Discovery completed -

Discovered #Routers:13 {sim242_88=Switch::network:10.1.1.88, qa-ASAMpe8=Switch::network:10.9.7.178, sim87=Switch::network:10.1.1.87, 7250nd=Switch::network:10.1.1.113, stack_3=Switch::network:10.1.1.2, omni187=Switch::network:10.1.1.1, qa-ASAMpe7=Router::network:10.9.7.177, dev-ASAMpe9=Router::network:10.9.7.179, qa-ASAMpe4=Switch::network:10.9.7.174, sim78=Router::network:10.1.1.78, qa-asamce9=Switch::network:10.9.77.91, sim242_77=Router::network:10.1.1.77, sim80=Switch::network:10.1.1.95}

[December 16, 2009 11:53:41 AM EST +754ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Card Discovery completed - Discovered

#Cards:56

[December 16, 2009 11:53:51 AM EST +187ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Discovered #Interfaces:500 #Macs:239

[December 16, 2009 11:53:54 AM EST +638ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Physical Port Discovery completed -

Discovered #Interfaces:711 #Macs:344

[December 16, 2009 11:54:01 AM EST +347ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] ProcessorCard Discovery completed - 15

equipment.ProcessorCard elements processed.

[December 16, 2009 11:54:01 AM EST +348ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] FlashMemory Discovery completed - 22

equipment.FlashMemory elements processed.

[December 16, 2009 11:54:01 AM EST +350ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Controller Processor Discovery

completed - 15 equipment.ControlProcessor elements processed.

[December 16, 2009 11:54:01 AM EST +350ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Switch Processor Discovery completed -

15 equipment.SwitchFabricProcessor elements processed.

[December 16, 2009 11:54:01 AM EST +351ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] PowerTray Discovery completed -

equipment.PowerSupplyTray discovered: 19

[December 16, 2009 11:54:01 AM EST +352ms] t@128

Discovery Log messages 129

Logs

ASAM_MESSAGE-*-INFO-.[SmWorker] FanTray Discovery completed - Discovered #FanTrays:26

[December 16, 2009 11:54:11 AM EST +044ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Channel Discovery completed -

Discovered 143 sonet interfaces DS3Channels:3 DS1 Channels:2 DS0ChannelGroups:1

[December 16, 2009 11:54:12 AM EST +047ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Link Aggregation Group Discovery

completed - 5 lag.Interface elements processed.

[December 16, 2009 11:54:12 AM EST +177ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Physical Link Discovery completed -

Discovered #PhysicalLinks:3[December 16, 2009 11:54:15 AM EST +936ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Network Interface Discovery completed

- Created and related 68 Network Interfaces0 secondary IPs processed.

[December 16, 2009 11:54:50 AM EST +499ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VRPN Discovery completed - Discovery

set #vrfs:318

[December 16, 2009 11:55:08 AM EST +327ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VPRN Service Interface Discovery

completed - 310 VPRN Service Interfaces

[December 16, 2009 11:55:08 AM EST +328ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] IES Service Interface Discovery

completed - 9 IES Service Interfaces

[December 16, 2009 11:55:08 AM EST +328ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VLL Service Interface Discovery

completed - 3 VLL Service Interfaces

[December 16, 2009 11:55:08 AM EST +329ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Non-primary IP Discovery completed - 0

secondary IPs processed.

[December 16, 2009 11:55:08 AM EST +329ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VPLS Service Interface Discovery

completed - 21 VPLS Service Interfaces

[December 16, 2009 11:55:08 AM EST +488ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Fib discovery disabled - skipping

discovery step

[December 16, 2009 11:55:08 AM EST +781ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] Confederation Discovery completed

- 4 rtr.VirtualRouter elements processed.

[December 16, 2009 11:55:10 AM EST +325ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] BGPSession Discovery completed - 6

bgp.Peer elements processed.

[December 16, 2009 11:55:10 AM EST +627ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFArea Discovery completed - 16

ospf.AreaSite elements processed.

[December 16, 2009 11:55:10 AM EST +897ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFService Discovery completed -

9 ospf.Site elements processed.

[December 16, 2009 11:55:13 AM EST +221ms] t@167


Logs

ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFInterface Discovery completed - 23 ospf.Interface elements processed.

[December 16, 2009 11:55:15 AM EST +409ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFNeighbor Discovery completed -

17 ospf.Neighbor elements processed.

[December 16, 2009 11:55:16 AM EST +526ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] VirtualLink Discovery completed -

2 ospf.VirtualLink elements processed.

[December 16, 2009 11:55:17 AM EST +856ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] VirtualNeighbor Discovery

completed - 2 ospf.VirtualNeighbor elements processed.

[December 16, 2009 11:55:17 AM EST +976ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISService Discovery completed -

Created 8 ISIS Services

[December 16, 2009 11:55:18 AM EST +118ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISArea Discovery completed -

Created 4 ISIS Areas

[December 16, 2009 11:55:19 AM EST +448ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Tunnel Discovery completed.Discovered

45 tunnels

[December 16, 2009 11:55:19 AM EST +542ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] MPLS Interface Discovery completed.

[December 16, 2009 11:55:21 AM EST +036ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] LSP Discovery completed - Collected

info on 34 LSPs

[December 16, 2009 11:55:22 AM EST +218ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISInterface Discovery completed

- Created 15 ISIS Interfaces

[December 16, 2009 11:55:22 AM EST +791ms] t@167ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISNeighborEndpoint Discovery

completed - Created 8 ISIS NeighborEndpoints

[December 16, 2009 11:55:22 AM EST +819ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] LSPPath Discovery completed -

Collected info on 37 LSPPaths

[December 16, 2009 11:55:22 AM EST +895ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VRF to Tunnel Mapping Discovery

completed - #Tunnel IDs found:0

[December 16, 2009 11:55:22 AM EST +948ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] MulticastService Discovery

completed - 4 pim.Site elements processed.

[December 16, 2009 11:55:23 AM EST +420ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] LDP TargetedPeer Discovery

completed.Created 22 TargetedPeers

[December 16, 2009 11:55:23 AM EST +754ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] LDP Interface Discovery

completed.Created 22 Ldp Interfaces

[December 16, 2009 11:55:23 AM EST +999ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] MulticastService Discovery

completed - 4 igmp.Site elements processed.

Discovery Log messages 131

Logs

[December 16, 2009 11:55:24 AM EST +214ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] PIMInterface Discovery completed

- 4 pim.Interface elements processed.

[December 16, 2009 11:55:24 AM EST +350ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] IGMPInterface Discovery

completed - 3 igmp.Interface elements processed.

[December 16, 2009 11:55:24 AM EST +475ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] IGMPNetwork Discovery completed

- 3 igmp.IfGroup elements processed.

[December 16, 2009 11:55:24 AM EST +536ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] pim.Neighbor Discovery completed

- 2 pim.Neighbor elements processed.

[December 16, 2009 11:55:24 AM EST +691ms] t@170ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] PIMSgEntry Discovery completed -

3 pim.Groups elements processed.

[December 16, 2009 11:55:25 AM EST +489ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VLL Site Discovery completed -

Discovered 6 VLL Sites

[December 16, 2009 11:55:28 AM EST +150ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] VPLS Site Discovery completed -

Discovered 27 VPLS Sites

[December 16, 2009 11:55:31 AM EST +010ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] ForwarderEndpoint Discovery completed.

Created 5 VLL, 24 VPLS, 3 IES, 6 VPRN ForwarderEndpoints

[December 16, 2009 11:55:35 AM EST +232ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] ProvisionedHops Discovery completed -

Collected info on 71 ProvisionedHops

[December 16, 2009 11:55:35 AM EST +466ms] t@128ASAM_MESSAGE-*-INFO-.[SmWorker] Full Discovery completed at Wed Dec 16

11:55:35 EST 2009

Event messagesThe Adapter logs JMS messages. The log file records the event type and EMS instance to which the message refers.

There are four types of event message:

• State changes

• AttributeValueChange events

• ObjectCreation events

• ObjectDeletion events

Note: The EMS instance name does not map directly to an EMC Smarts object name. “Mapping of SAM-O Elements to Smarts Objects” on page 71 provides details about mapping.


Logs

Event log examples

The following are examples of event log messages:

[December 16, 2009 11:55:36 AM EST +120ms] t@129ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] Event Processing

com.smarts.asac.events.AttributeValueChangeEvent for mpls.DynamicLsp::lsp:from-10.1.1.95-id-4

[December 16, 2009 11:58:33 AM EST +968ms] t@129ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] Event Processing

com.smarts.asac.events.ObjectCreationEvent for equipment.DaughterCardSlot::network:10.1.242.79:shelf-1:cardSlot-1:card:daughterCardSlot-2

[December 16, 2009 2:02:36 PM EST +411ms] t@129ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] Event Processing

com.smarts.asac.events.ObjectDeletionEvent for vlan.Vlan::svc-mgr:service-379

Alarm messagesThe Adapter logs alarms in a similar format to events. The key differences between events and alarms are:

• Events typically create/delete/change topology state

• Alarms only push/clear notifications in the Adapter Platform; they are similar to those seen by the EMS operators in the Alcatel-Lucent Alarm Manager.

Alarm log examples

The following are examples of alarm log messages:

INFO: [SmAlarmProcessor] Alarm Processing com.smarts.asac.events. AttributeValueChangeEvent for fm.AlarmObject::faultManager:[email protected]|alarm-31-4-24

Note: If an alarm is discarded because of ASA-Alarms.conf configuration, the Adapter will still log the alarm and, optionally, the discard, as shown below:

ASAM_MESSAGE-*-INFO-.[SmAlarmProcessor] Alarm Processing com.smarts.asac.events.AttributeValueChangeEvent for fm.AlarmObject::faultManager:[email protected]@shelf-1@cardSlot-2@card@port-1|alarm-14-6-12-currentData=equipment.InterfaceStats-thresholdName=receivedOctetsPeriodic

Discarding example

The following is an example of a discard message[December 16, 2009 11:55:35 AM EST +569ms] t@131ASAM_MESSAGE-*-INFO-.[SmAlarmProcessor] Discarding

inactive:faultManager:[email protected]@router-1@[email protected]@interface-6|alarm-39-11-36-packetSourceIpAddress=172.18.7.2

Alarm messages 133

Logs

Queue Log messagesThe EMS and the Adapter each use queues. The Adapter reads the JMS messages in a queue on the EMS and places the messages in the Adapter’s internal XML, alarm, and event queues.

The XML queue stores raw, unparsed messages from the EMS. The Adapter does not specify the message type until it parses the message and then places it in the alarm or event queue.

The Adapter logs when any of these queues changes size by 50 messages more or fewer. You can use the Queue Log to determine if the Adapter is processing messages slowly, causing message backup.

Queuing analysis

You can use the Queue Log to determine if the Adapter is processing messages slowly, causing message backup. For example, to use a grep command to search for Adapter queuing:

grep EventDelta IC-ASAM.log

Example output

The following is an example of a queue log.

[December 16, 2009 11:55:45 AM EST +527ms] t@131ASAM_MESSAGE-*-INFO-.[SmAlarmProcessor] EventDelta

Timestamp:1260982545526 Thread:SmAlarmProcessor QueueName:Alarm QueueSize:50

[December 16, 2009 11:58:23 AM EST +859ms] t@129104110288:ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] EventDelta

Timestamp:1260893003859 Thread:SmTiEventProcessor QueueName:Event QueueSize:50

Warning messagesMost entries in the ASA.log are informational, providing a trail of events reported by the Alcatel-Lucent 5620 SAM EMS or showing progress of a discovery. This section discusses a warning message.

No SAM-O license

SEVERE: [Connector] Exception Type:javax.jms.JMSSecurityException SAM-O Access Violation

and/or

[December 16, 2009 11:53:31 AM EST +496ms] t@133ASAM_MESSAGE-*-SEVERE-.[Connector] Exception

Type:javax.jms.JMSSecurityExceptionSAM-O Access Violationand/or[December 16, 2009 11:53:59 AM EST +492ms] t@129ASAM_MESSAGE-*-SEVERE-.[SmTiEventProcessor] Adapter cannot connect to

the 5620Sam EMS


Logs

server<SOAP:Envelopexmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Header><headerxmlns="xmlapi_1.0"><requestID>smarts@8598</requestID><requestTime>Aug15, 2007 11:39:21 PM</requestTime><responseTime>Aug 15, 2007 11:39:22PM</responseTime></header></SOAP:Header><SOAP:Fault><faultcode>SOAP:Client</faultcode><faultstring> security] Users require OSS Managementprivileges to useSAM-O</faultstring><faultactor>XmlApi</faultactor><detail><requestID>smarts@8598</requestID></detail></SOAP:Fault></SOAP:Envelope>

Explanation: No Alcatel-Lucent 5620 SAM-O license is present on the Adapter system. Please note the lines in bold text for the relevant information.

Turn on verbosity example

The following is an example of a message with the verbosity option turned on.

[December 16, 2009 11:53:18 AM EST +165ms] t@132ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement

local:qualified:eventName chars:AttributeValueChange[December 16, 2009 11:53:18 AM EST +165ms] t@132ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement

local:qualified:MTOSI_osTime chars:1196887261476[December 16, 2009 11:53:18 AM EST +165ms] t@132ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement

local:qualified:ALA_clientId chars:[December 16, 2009 11:53:18 AM EST +165ms] t@132ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement

local:qualified:MTOSI_objectType chars:netw.NetworkElement[December 16, 2009 11:53:18 AM EST +165ms] t@132ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement

local:qualified:MTOSI_NTType chars:NT_ATTRIBUTE_VALUE_CHANGE

[December 16, 2009 2:24:11 PM EST +806ms] t@246 SM_ProtocolEngine-46 sm_adapter ASL

ASAM_MESSAGE-*-INFO-.[Thread-45] Starting the JMS connector

restartJMSConnector example

The following is an example of the message for a JMSConnector restart:

[December 16, 2009 2:24:42 PM EST +800ms] t@231ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.

[December 16, 2009 2:24:42 PM EST +802ms] t@231ASAM_MESSAGE-*-FINE-.[Connector] Call

InitialContext:{java.naming.provider.url=10.9.252.61:1100,10.9.252.54:1100, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.disableDiscovery=true, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}

org.jnp.interfaces

Warning messages 135

Logs


APPENDIX FTroubleshooting

You can troubleshoot Adapter functioning by using various ASL scripts that are provided with the Adapter. In addition, you can examine log entries, as described in this appendix.

This appendix includes the following contents:

• Use ASL scripts for troubleshooting....................................................................... 138

Troubleshooting 137

Troubleshooting

Use ASL scripts for troubleshootingThe Adapter provides ASL scripts for troubleshooting the following:

• General functioning

• EMS functioning

• Managing devices not in effect

• Discovery

General functioning

The following ASL scripts are available to help you troubleshoot general Adapter functioning:

• logLevel.asl

• reloadOI.asl

logLevel.aslThis script sets the logging levels, as shown in Table 12 on page 138.

To run this script:


sm_adapter –s <adapter_name> -Dlvl="2" alcatel-sam/logLevel.asl

reloadOI.aslThis script reloads the ASA-Alarm.conf and AggregateAlarms.conf files without the need to restart the system. To run this script:


sm_adapter –s <adapter_name> alcatel-sam/reloadOI.asl

Table 12 Log warning level settings

Warning level Description

1 SEVERE

2 WARNING

3 INFO

4 CONFIG

5 FINE

6 FINER

7 FINEST (default)


Troubleshooting

EMS troubleshooting

Query the Alcatel-Lucent 5620 SAM EMS database for object data, in the event that the information is not directly available from the EMS user interface. To do this, you can run the following ASL scripts:

• readRecords.asl—Lists all records for a specified object; for example, all routers

• soap.asl—Submits an xml query and returns the responses to the standard output (stdout) or a file

showStatus.aslThe following ASL script prints JMS message rate status to the Adapter log file. It provides the following information:

• JMS message receiving rate. This is the rate at which the Adapter receives JMS messages from the EMS.

• Total number of JMS messages received

Use the following command to view this information in the log:

bin/sm_adapter -s ASAM alcatel-sam/showStatus.asl

The following is an example of output from the log:

Status is taken for the duration of last 10 minutes 0 secondsJMS message received:63 Avg msg/sec:0.09TextMessage queue:0 used:39 discarded:24 discarded pct:38% last

discarded:Alarm queue:0 is locked? false Alarms processed:7 Avg alarm/sec:0.01Event queue:0 is locked? false Events processed:32 Avg Topo

event/sec:0.04

readRecords.asl

Note: This script is available for UNIX only.

To run this script:

At ASAM_BASEDIR/smarts/bin, enter the following command on one line:

▼/sm_adapter -s <adapter_name> -Dpkg=<SAM-O class name> alcatel-sam/readRecords.asl▲

For example, to list all of the routers and their properties:

▼/sm_adapter -s <adapter_name> -Dpkg=netw.NetworkElement alcatel-sam/readRecords.asl▲

The results will be located in /var/tmp/netw.NetworkElement.xml.

soap.aslThis script supports single or multiple queries in a single call.

To run this script:


▼sm_adapter -s <adapter_name> --file=<query file and pathname> alcatel-sam/soap.asl▲

Use ASL scripts for troubleshooting 139

Troubleshooting

The following examples illustrate single and multiple queries.

Example 1 Example of a single query

sm_adapter -s <adapter_name> --file=find.xml alcatel-sam/soap.asl

The following is a sample find.xml file for a single query (network element).

In this example, the file limits the attribute list to the following, and skips any child objects:

• objectFullName

• displayedName

<find xmlns="xmlapi_1.0"> <fullClassName>netw.NetworkElement</fullClassName> <resultFilter> <attribute>objectFullName</attribute> <attribute>displayedName</attribute> <children/> </resultFilter></find>

The output will look something like the following example:


Troubleshooting

Example 2 Example of a multiple queries

The following is a sample find.xml file for multiple queries (network element and equipment card):

<find xmlns="xmlapi_1.0"> <fullClassName>netw.NetworkElement</fullClassName> <resultFilter> <attribute>objectFullName</attribute> <attribute>displayedName</attribute> <children/> </resultFilter></find><find xmlns="xmlapi_1.0"> <fullClassName>equipment.Card</fullClassName> <resultFilter> <attribute>objectFullName</attribute> <attribute>displayedName</attribute> <children/> </resultFilter></find>

verboseXml.aslChange the level of verbosity in the JMS text messages in the log file in order to get more or less detail.

Turn on verbosity (get more detail)


sm_adapter -sALCATEL-SAM -Dval=true alcatel-sam/verboseXml.asl

Output examples:

INFO: [MessageToEventConverter] Parse: endElement local: qualified:eventName chars:AttributeValueChange

Dec 5, 2007 3:41:05 PM com.smarts.asac.SmAsAdapterLog infoINFO: [MessageToEventConverter] Parse: endElement local:

qualified:MTOSI_osTime chars:1196887261476Dec 5, 2007 3:41:05 PM com.smarts.asac.SmAsAdapterLog infoINFO: [MessageToEventConverter] Parse: endElement local:

qualified:ALA_clientId chars:Dec 5, 2007 3:41:05 PM com.smarts.asac.SmAsAdapterLog infoINFO: [MessageToEventConverter] Parse: endElement local:

qualified:MTOSI_objectType chars:netw.NetworkElementDec 5, 2007 3:41:05 PM com.smarts.asac.SmAsAdapterLog infoINFO: [MessageToEventConverter] Parse: endElement local:

qualified:MTOSI_NTType chars:NT_ATTRIBUTE_VALUE_CHANGEDec 5, 2007 3:41:05 PM com.smarts.asac.SmAsAdapterLog info

Turn off verbosity (get less detail)


sm_adapter -s <adapter_name> -Dval=false alcatel-sam/verboseXml.asl


Troubleshooting

restartJMSConnector.aslReconnect to the EMS JMS server, restart the JMS connector:


sm_adapter -s <adapter_name> alcatel-sam/ restartJMSConnector.asl

Output examples:

INFO: [Thread-18] Starting the JMS connectorDec 3, 2007 9:22:58 PM com.smarts.asac.SmAsAdapterLog infoINFO: [Connector] Attempting (re)connection to JMS.Dec 3, 2007 9:22:58 PM com.smarts.asac.SmAsAdapterLog fineFINE: [Connector] Call

InitialContext:{java.naming.provider.url=jnp://10.5.24.68:1099/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.disableDiscovery=true, jnp.timeout=60000, java.naming.factory.url

.pkgs=org.jboss.naming:org.jnp.interfaces}

Managing devices not in effect

Use the following ASL scripts to manage the filters that determine which devices will not be discovered.

• insertFilters.asl

• deleteFilters.asl

• clearFilters.asl

• showFilters.asl

The filters are contained in the file, “GA_StringDictionary::AdapterFilters”, which contains DisplayName filters for UnitaryComputerSystems. “Overview of device filtering” on page 63 provides more information.

insertFilters.aslInsert filters:


▼sm_adapter -s <adapter_name> -f <path/fileName> alcatel-sam/insertFilters.asl▲

Note: After insertion, perform a discovery to make the filters take effect.

deleteFilters.aslDelete filters:


▼sm_adapter -s <adapter_name> -f <path/fileName> alcatel-sam/deleteFilters.asl▲

Note: After deletion, perform a discovery to make the filters take effect.


Troubleshooting

clearFilters.aslRemove all filters:


sm_adapter -s <adapter_name> alcatel-sam/clearFilters.asl

Note: After clearing the filters, perform a discovery to make the change take effect.

showFilters.aslShow the filter DisplayNames:


sm_adapter -s <adapter_name> alcatel-sam/showFilters.asl

Discovery

Use the following ASL scripts to initiate the following types of discovery:

• discover.asl

• routerDiscover.asl

• servicediscover.asl

• alarmRediscover.asl

discover.aslManually initiate full discovery:


sm_adapter -s <adapter_name> alcatel-sam/discover.asl

routerDiscover.aslManually initiate discovery of a particular Alcatel-Lucent device:


▼sm_adapter –s <adapter_name> -DIP=10.1.1.77 alcatel-sam/routerDiscover.asl▲

Note: the IP is the system ID, not the Management IP Address.

servicediscover.aslManually initiate discovery of a particular type of service:


▼sm_adapter –s <adapter_name> -DQUALIFIER=<SERVICE TYPE> alcatel-sam/serviceDiscover.asl▲

Where valid <SERVICE TYPEs> are the following: AM, MPLS, NPM, MCAST.


Troubleshooting

alarmRediscover.aslManually initiate discovery of current alarms from the EMS:


sm_adapter -s <adapter_name> alcatel-sam/alarmRediscover.asl


APPENDIX GUnderstanding the sm_edit Utility

As part of the EMC Smarts deployment and configuration process, you need to modify certain files. User modifiable files include configuration files, rule set files, templates, and seed files that contain encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory.

The original versions of files should not be altered. If a file must be modified, a new version should be created and then stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories.

When EMC Smarts software requires one of these files, it is designed to first search for a modified file in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is not found in the local area, EMC Smarts software then searches corresponding BASEDIR/smarts directories for the original version of the file.

To ease file editing and storage, EMC Corporation provides the sm_edit utility with every EMC Smarts product suite. When invoked, sm_edit opens the specified file in a text editor. This utility ensures that modified files are always saved to the appropriate local area and that non-local copies of all files remain unchanged. If an appropriate subdirectory does not exist for the file you are modifying, sm_edit creates the appropriate subdirectory before saving the modified file to that location. For files with header information set for encryption, sm_edit encrypts certain fields in the file. In addition, sm_edit preserves the file permissions of modified files, which helps ensure that important configuration files are not altered by unauthorized users.

In UNIX, you can configure sm_edit to use your favorite text editor when you invoke sm_edit.

In Windows, you can configure sm_edit so that your favorite text editor is automatically invoked when user-modifiable files are double-clicked in Windows Explorer..

Example Modify ics.conf

To use sm_edit from the command line, specify the file name and include the subdirectory under /local where the file resides. For example, to edit the ics.conf, enter:

# BASEDIR/smarts/bin> sm_edit conf/ics/ics.conf

In this example, sm_edit searches in the BASEDIR/smarts/local/conf/ics directory for the ics.conf file. If it finds the ics.conf file, it opens the file in a text editor. If sm_edit does not find the ics.conf file in the BASEDIR/smarts/local/conf/ics directory, it creates a local copy of the ics.conf file and writes it to the BASEDIR/smarts/local/conf/ics directory.

The EMC Smarts System Administration Guide provides additional information about the sm_edit utility, including how to configure the utility to use a specific editor.

Understanding the sm_edit Utility 145

Understanding the sm_edit Utility


APPENDIX HGetting help

This appendix provides the following topics:

◆ Where to get help.................................................................................................. 148

Getting help 147

Getting help

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:

https://support.emc.com

Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.


http://support.emc.com

INDEX

Numerics5620-SAM-topic-xml 41

AAD_PersistentDataSet 95Adapter

technical notes 111Adapter Log

rollling 62AggregateAlarms.conf file 47

reload 49Aggregating

alarms 47Alarm

COMMENT 44DEDUP 44default expiration time 46EXPIRATION 44INACTIVE 44MOMENTARY 44NOTARGET 44objects with no associated repository objects 46set for manual clearing 47SEVERITY 44synchronization 47

Alarm processing 43, 46alarmRediscover.asl 47Alarms

aggregate 47best practices 46NOTARGET 46rediscovery 47

Alcatel-Lucent 5620 SAM EMS Open Interface 33AltEmsInstance 32AltJmsPort 33AMInstance 31, 36apipe.Apipe 107apipe.L2AccessInterface 106apipe.Site 106ArchiveOnDelete 38ASA 31, 36ASA.log entries 134ASA-Alarm.conf 47ASA-Alarm.conf file 44, 46

reload 49ASA-Filter.conf file 41Auto-configuration 61AutonomousSystem 104

Bbgp.Peer 88, 115BGPInstance 37BGPServiceConfederation 104

BGPSessionDisconnected 120

CCable 94Card 93

Down 120ClearAlarmOnDelete 38clearFilters.asl 63ClientId 33Configuration 43Configuring

statistics polling 28CreateVPLSSAPs 36

DdeleteFilters.asl 63DevicesNotInEffect.conf 63Discovery 20DiscoveryOnJmsLoss 35DiscoveryOnStartup 35dmctl command 26dp.TargetedPeer 87

EemsConfig.import 31EmsInstance 32EMSReconnectInterval 34EMSVersion 32Enabling

Events Policy 29epipe.Epipe 107epipe.Site 106equipment.BaseCard 85, 93, 112equipment.Card 86equipment.ControlProcessor 93, 112equipment.ControlProcessor 93equipment.DaughterCard 93equipment.DaughterCard 85, 112equipment.FanTray 86, 93, 113equipment.FlashMemory 86, 94equipment.PhysicalLink 85, 94equipment.PhysicalPort 86, 94, 113equipment.PowerSupplyTray 86, 94, 113equipment.Processor 87equipment.ProcessorCard 85, 95, 112equipment.SwitchFrabicProcessor 93Events policy

Enabling 29

FFan 93


Index

FibDiscoveryEnabled 35Firewall ports 29fm.AlarmObject object 48Forwarder 106, 107ForwarderEndpoint 120ForwarderEndpoint. 104fpipe.Fpipe 107fpipe.Site 106

GGRE Tunnel 105

Iies.L3AccessInterface 98ies.L3AccessInterface 86igmp.IfGroup 89igmp.Interface 89, 99, 117igmp.Site 99IGMPInterface 99IGMPInterface IGMPInterfaceUnreachable 120IGMPNetworkDiscoveryEnabled 35insertFilters.asl 63Interface 94, 96, 97, 98, 106, 107Interface Down 121ipipe.Ipipe 107ipipe.Site 106Isis.Adjacency 109isis.Adjacency 89, 117Isis.Area 108isis.Area 89Isis.Interface 109isis.Interface 89, 117Isis.Site 109isis.Site 89, 117ISISAdjacency 121ISISArea 108ISISInterface 109ISISNeighborEndpoint 109ISISServerName 37ISISService 109

JJMS durable connection 69JMS filter

default 41JMS message filtering 41JmsConnectionMode 34JmsPassword 34JmsPort 33JmsUniqueId 33JmsUser 33

Ll2fib.FibEntry 95l2fib.MFibEntry 95L3 Virtual Private Network (VPN) IP addresses 18lag.Interface 86, 96, 114lag.PortTermination 96

ldp.Interface 99ldp.Interface 87, 115ldp.TargetedPeer 100, 115LdpAdjacency 99LdpProtocolEndpoint 99Logical topology 21LogLevel 38LSP 100

Impacted 121

MMAC 94MaximumReconfigureDelayTime 37MCASTInstance 37MD-5-hashed password 38Memory 94MIB Administrative State 29MissedKeepAliveMessages 34mpls.CrossConnect 87mpls.CrossConnect 86mpls.DynamicLsp 114mpls.DynamicPath 100Mpls.Interface 87mpls.Interface 100mpls.LspPath 87, 100MPLSInstance 37MPLSService 100Multicast Manager 20MulticastGroup 103MulticastService 99, 104MulticastSource 103MulticastTreeDiscoveryEnabled 35Multi-vendor topology 23

NNeighborDownThresholdForRouterDown 38netw.NetworkElement 87, 93NetworkAdapterRedundancyGroup 96NetworkConnection 105

OOIInstance 31, 37ospf.AreaSite 88, 100ospf.Interface 88, 101ospf.Interface 116ospf.Neighbor 86, 88, 101ospf.Neighbor 116ospf.Site 89, 102, 116ospf.VirtualLink 89, 102, 116ospf.VirtualNeighbor 102, 116ospf.VirtualNeighbor ( 89OSPFArea 100OSPFAreaConfiguration 100OSPFInterface 101OSPFNeighborEndpoint 101OSPFServerName 37OSPFService 102

ABRNotInBackbone 121OSPFVirtualInterface 102


IndexIndex

OSPFVirtualNeighbor 102

PPhysical topology 21pim.Group 90, 103pim.Interface 90, 103, 116pim.Neighbor 103pim.RPSet 89, 103pim.Site 104PIMInterface 103, 105

PIMInterfaceUnreachable 121PIMSourceG 103PIMStarG 103Polling

statistics 28Polling Groups 61

BGP 62ForwarderEndpoint 61LdpProtocolEndpoint 61OSPF 62VRFs 61

PowerSupply 94Processor 93

RReconfigureDelayTime 37ReconfigureSlidingWindow 37Repository

replace existing 62RestartTimeAfterTerminateClient 34Router

Down 122Router/Switch 93routerDiscover.asl 63RouterDownCheckInterval 38RoutesInVrf statistics 29rtr.NetworkInterface 86, 96rtr.RouteStats 104rtr.VirtualRouter 88, 104runcmd_env.sh file 39

SSAM-O 33, 46SAM-O interface 28Security

File write permissions 26, 27Windows Server 2008 26, 27

Service discovery, scheduling 68service.SpokeConnector 104serviceDiscover.asl 68showFilters.asl 63Site names 63sm_edit utility 26, 27SM_LIBPATH 39sonetEquipment.Sts1Channel 86, 97sonetequipment.Sts1Channel 114svt.MeshSdpBinding 87, 104svt.SdpBinding 104, 115svt.TransportConnection 105

svt.Tunnel 105

Ttdmequipment.DS0ChannelGroup 97, 113TemperatureSensor 95Topology

logical 21multi-vendor 23

UUAC write permission 27UnmanageWhenInMaintenance 36

Vvll.L2AccessInterface 86, 106vll.L2AccessInterface 114vll.Site 106vll.Site 87vll.Vll 88, 107vpls.L2AccessInterface 107vpls.Site 87, 107vpls.Site 115vpls.Vpls 107VPLSRTPrefix 36VPN 107, 108

Impacted 122vprn.L3AccessInterface 107vprn.Site 87, 88, 108vprn.site 115VRF 108

Down 123vt.SpokeSdpBinding 104

WWindows Server 2008

File write permissions 26, 27User Account Control (UAC) 26, 27


Index


Documents

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version ... · MPLS Manager ... Alcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following EMC Smarts