VMware Smart Assurance Adapter for GuideSince 5620 SAM EMS Release 7.0/R1, LLDP is supported in 7450s, 7750s, and 7710s. n Support for Alcatel-Lucent 7210 SAS-E, including the following:

VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMS UserGuide

VMware Smart Assurance 10.1.0

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

If you have comments about this documentation, submit your feedback to

[email protected]

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

Copyright © 2019 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS User Guide

VMware, Inc. 2


mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

1 Introduction 7Overview 7

New features and changes 7

New features in Foundation 10.1 9

New features in ASAM Patches 11

Architecture 11

IP Availability Manager/Performance Manager 13

MPLS Manager 14

Network Protocol Manager for BGP 14

Network Protocol Manager for OSPF 15

Network Protocol Manager for IS-IS 15

Multicast Manager 15

Adapter Platform 16

Discovery 16

Full discovery 16

Incremental discovery 16

Physical and logical discovery 17

Discovery of connections 18

Event processing 18

Adapter Platform alarms 18

Multi-vendor topology support 18

Fault tolerance 19

Troubleshooting 20

2 Configuring the Adapter Deployment 21Methods for modifying user configuration parameters 21

Using the Global Console 22

Using the command line 22

Configuring the Alcatel-Lucent 5620 SAM EMS server 22

Creating a user for SAM-O interface access 23

Configuring statistics polling 23

Copying required .jar files 24

Copying required .jar files for EMS 17.9 and 19.6 24

Configuring the Adapter 25

Editing the emsConfig.import file 25

emsConfig.import parameters 26

Preventing access to an optional server 33

Generating an MD-5-hashed password 33

VMware, Inc. 3

Configuring the WANLink driver 34

Configuring JMS message filtering 35

Monitored events 35

JMS message filter 35

Default JMS filter 36

Modifying the default JMS filter 38

Configuring alarm processing 38

Configuring alarms 39

Considerations for working with alarms 41

Aggregating alarms 42

Configuring aggregate alarms 42

Notes on alarms 44

Reloading alarm configuration files 44

Filtering out alarms in maintenance 44

New INACTIVE alarms in ASA-Alarm.conf 45

Configuring Domain Managers 46

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

Scenario 2: Deployment with mixed vendor environment and IP Manager 49

Scenario 3: Deployment with IP Manager 50

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

Additional configuration for NPM Managers 55

Configure individual Network Protocol Managers 55

Additional configuration for the Multicast Manager 55

External polling auto-configuration 56

New polling groups 56

Replacing existing Domain Manager repositories 57

Rolling the Adapter Log 58

Device filtering (optional) 58

Overview of device filtering 58

3 Start up and Discovery 60Starting Adapter and Domain Manager services 60

Starting the Domain Manager services 60

Stopping a Domain Manager service 61

Initiating discovery 62

Initiating full discovery 62

Initiating partial discovery 62

Scheduling a periodic discovery 63

Synchronizing alarms 64

Removing an unused JMS durable connection 64


VMware, Inc. 4

4 Mapping of SAM-O Elements to Smarts Objects 65Examples of EMS elements mapped to VMware Smart Assurance objects 65

Physical model 65

Logical NPM BGP model 66

Logical NPM OSPF model 67

Logical NPM ISIS model 68

Logical Multicast model 69

Logical MPLS VLL model 70

Logical MPLS VPLS model 71

Logical MPLS VPRN model 72

Interfaces, Physical, Network, L2/L3 74

Modeling of LSP paths and SDP tunnels 77

Modeling of IES-IES services 79

Power supply instantiation 79

SAM-O element to VMware Smart Assurance object mapping 79

5 Mapping of Smarts objects and SAM-O Objects 85Discovered inventory objects 85

Mapping of SAM-O equipment objects 86

Mapping of SAM-O service objects 91

6 Mapping of SAM-O Objects and Smarts Notifications 105Element to notification mapping 105

7 Notification Log Entries 112Notification Log entries 112

8 Logs 116Adapter log file 116

Startup sequence 116

Loading mappings 116

Starting up the server 117

Connecting to Domain Managers 117

Establishing the JMS connection 118

Discovery Log messages 118

Discovery log examples 118

Event messages 121

Event log examples 122

Alarm messages 122

Alarm log examples 122

Discarding example 122


VMware, Inc. 5

Queue Log messages 122

Queuing analysis 123

Example output 123

Warning messages 123

No SAM-O license 123

Turn on verbosity example 124

restartJMSConnector example 124

9 Troubleshooting 125Use ASL scripts for troubleshooting 125

General functioning 125

EMS troubleshooting 126

Managing devices not in effect 129

Discovery 130

10 Understanding the sm_edit Utility 132Example 132

Modify ics.conf 132

11 Getting help 134Where to get help 134


VMware, Inc. 6

Introduction 1This guide provides information about the VMware Smart Assurance Adapter for Alcatel-Lucent 5620SAM EMSfor use with the Alcatel-Lucent 5620 Service Aware Manager (SAM) Element ManagementSystem (EMS). In addition, it includes information for configuring and using the Adapter.

This chapter includes the following topics:

n Overview

n Architecture

n Discovery

n Multi-vendor topology support

n Fault tolerance

n Troubleshooting

Overview

The VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS provides a link from theAlcatel-Lucent 5620 SAM EMS Service Aware Manager Open Interface (SAM-O) to the following VMwareSmart Assurance Domain Managers:

n IP Availability Manager

n MPLS Topology Manager

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

n Multicast Manager

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

New features and changes

VMware, Inc. 7

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

n VMware Smart Assurance Adapter for Alcatel-Lucent 5620 SAM EMS is now supported on Red HatEnterprise Linux (RHEL) 7.6. The base installer name is setup-ASAM-3_5_0_0-linux64.bin.

Note There is one installer for RHEL 6.9/6.10, RHEL 7.5, and RHEL 7.6 . The VMware SmartAssurance Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.4.0.X Patch Readme provides moreinformation.

n Support for Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server version 17.9 is availableon adapters 3.3.0.1 and higher. Supported versions of the Alcatel-Lucent 5620 Service SAM EMSserver are 17.9 to 19.6.

n Support for Alcatel-Lucent 7250 switches

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

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

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

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

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

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

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

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

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

n Discover and monitor Alcatel-Lucent OmniSwitch physical components.

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

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

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

n Create Cables via interfaces between OmniSwitches when physical links are manually configuredin the Alcatel-Lucent 5620 SAM.

n Create Cables between OmniSwitches when LLDP is configured in the Alcatel-Lucent 5620 SAMthat builds the physical links.


VMware, Inc. 8

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

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

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

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

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

n Support for 7210-SAS-Sx Satellite device discovery on 7750 SRs.

n Support for CMG-a8 devices.

n Support for VPRN IPsec interfaces.

n The Adapter for Alcatel-Lucent 5620 SAM EMS interoperates with VMware Smart Assurance IPManager Versions 9.4.2 through 10.1.0. When deploying new versions of both products, you nowneed to add the IP domain as a source to MPLS, NPM, and MCAST domains if they are included inyour network. Chapter 2 Configuring the Adapter Deployment provides more information.

New features in Foundation 10.1

This release of the Adapter for Alcatel-Lucent 5620 SAM EMS is based upon foundation 10.1.Documentation explaining Foundation 10.1 features is listed in the VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMS Release Notes. Here are highlights of changes related to Foundation10.1:

Internationalization

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

In this release, the foundation has been internationalized and is functionally localized to AmericanEnglish. Localization to the other target languages, as dictated by the VMware globalization policy andcustomer 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 havethe following syntax: <name>_<locale>_<encoding>.log. For example,MYDOMAINMANAGER_en_US_UTF-8.log. The System Administration Guide provides completeinformation about locale and log files.

ICIM Ref 1.10

Foundation 10.1 has been updated to support ICIM Reference 1.10.


VMware, Inc. 9

New SmRestartableDomainManager class

You can now use SmRestartableDomainManager in place of SmRemoteDomainManager with minimalchanges to accommodate it. The benefit of using the SmRestartableDomainManager is that yourapplication does not need to write code to check the status of the remote server and to try to reconnect ifthe server shuts down and is restarted.

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

New MODEL operations to retrieve description text

There are a number of API operations that have been re-implemented as MODEL operations. TheseMODEL operations retrieve description texts. The texts that are retrieved will be in the locale that was seteither by the initial connection or by the locale set by the most recent call to the setRemoteLocale APIoperation. 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 isCI_Locale::DEFAULT.

The operations are:

n getPropDescription — retrieve the description of the MODEL property

n getEventDescription — retrieve the description of the MODEL event

n getOpDescription — retrieve the description of the MODEL event

n getClassDescription — retrieve the description of the MODEL class

These MODEL operations are described in the VMware Smart Assurance MODEL Reference Guide.

New command line option in sm_adapter

A new option, alarmInterval, has been added to sm_adapter. You can use the alarmInterval option with asubscriber front end ( --subscribe or --subscribeProp). Setting alarmInterval causes the front end togenerate 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, inorder to use alarmInterval, your script must recognize a message type of Timer_Alarm.

--alarmInterval=secs

New ICF Core classes

A 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 classesinherit CMP core classes, and are used by ICIM core and ICF framework.

The ICF Core classes are described further in the VMware Smart Assurance ICIM Reference.


VMware, Inc. 10

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 checkfor other changes. The Perl Reference Guide provides more information.

Changes in sm_server --version

The operating system (OS) name that the product is running on and OS version identifier have beenadded 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 newclasses which are now the super classes for ICIM-Core:

n CORE_ManagedObject

n CORE_Collection

n CORE_MetaObject

n 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.4.0.X patches, consult the patch documentation on theVMware Docs website, docs.vmware.com.

Architecture

The Adapter provides a link from the Alcatel-Lucent 5620 SAM EMS Service Aware Manager OpenInterface (SAM-O) to the following VMware Smart Assurance Domain Managers:

n IP Availability Manager or Network-Resource Manager

n MPLS Topology Manager

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

n Multicast Manager


VMware, Inc. 11


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

Adapter for Alcatel-Lucent 5620 SAM EMSarchitectureshows the event, alarm, and notification flowthrough the Adapter and the VMware Smart AssuranceDomain Managers and Adapter Platform.

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


VMware, Inc. 12

Figure 1-1. Adapter for Alcatel-Lucent 5620 SAM EMSarchitecture

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 otherVMware Smart Assuranceproducts.

IP Availability Manager/Performance Manager

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

Note In IP Manager, the Network-Resource Manager receives the topology information from theAdapter.


VMware, Inc. 13

The Adapter also supports performance status information from the Alcatel-Lucent 5620 SAM EMS serveron 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 andVPN topology information from the Alcatel-Lucent 5620 SAM EMS server into the VMware SmartAssurance MPLS Manager.

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

Enhanced identification of Level 3 Virtual Private Network (VPN) IPaddresses

Each VPN includes IP addresses that are unique within that VPN. This can lead to VPN discovery issueswhen 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 byVirtual 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

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 theVMware Smart Assurance Network Protocol Manager for BGP. The Adapter does not support EBGP(External BGP) endpoints/sessions.


VMware, Inc. 14

The Network Protocol Manager for BGP diagnoses connectivity failures for the BGP protocol. TheNetwork Protocol Manager for BGP, working with the IP Availability Manager and the importedinformation for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers andmonitors network devices running BGP services, diagnoses BGP-related failures, and reports the resultsof its analysis to the Global Manager. The Network Protocol Manager for BGP also detects commonconfiguration 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 theVMware Smart Assurance Network Protocol Manager for OSPF.

The Network Protocol Manager for OSPF diagnoses connectivity failures for the OSPF protocol.TheNetwork Protocol Manager for OSPF, working with the IP Availability Manager and the importedinformation for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers andmonitors network devices running OSPF services, diagnoses OSPF-related failures, and reports theresults of its analysis to the Global Manager. The Network Protocol Manager for OSPF also detectscommon 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-IntermediateSystem (IS-IS) network, importing IS-IS topology information from the Alcatel-Lucent 5620 SAM EMSserver into the VMware Smart Assurance Network Protocol Manager for IS-IS.

The Network Protocol Manager for IS-IS diagnoses connectivity failures for the IS-IS protocol. TheNetwork Protocol Manager for IS-IS, working with the IP Availability Manager and the importedinformation for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server, discovers andmonitors network devices running IS-IS services, diagnoses IS-IS-related failures, and reports the resultsof its analysis to the Global Manager. The Network Protocol Manager for IS-IS also detects commonconfiguration problems that occur when deploying and maintaining the routing infrastructure.

Multicast Manager

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

n Internet Group Management Protocol (IGMP)

n 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 importedinformation for Alcatel-Lucent devices from the Alcatel-Lucent 5620 SAM EMS server. The MulticastManager 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 andmaintaining the multicast infrastructure.


VMware, Inc. 15

Adapter Platform

The VMware Smart Assurance Adapter Platform imports alarms and event information from the Adapterfor Alcatel-Lucent 5620 SAM EMS and imports network topology information from the IP AvailabilityManager.

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

Discovery

The Adapter for Alcatel-Lucent 5620 SAM EMS does not perform SNMP polling of the network elementthrough 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 thetopology is correctly maintained:

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

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

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

Full discovery

The Alcatel-Lucent 5620 SAM EMS pushes JMS messages to the Adapter using an XML/SOAPconnection. The Adapter transforms the XML data into VMware Smart Assurance topological objects andvalues, which it pushes to the various Domain Managers. In addition, the EMS provides state changesthat the Adapter processes; the Adapter does not maintain topology state itself.

Incremental discovery


VMware, Inc. 16

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

n Alarms to the Adapter Platform

n 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 directcorrelation between Alcatel-Lucent database objects and the VMware Smart Assurance topologyelements to which they are mapped. Logical discovery is more complex, because the Adapter must querymultiple Alcatel-Lucent 5620 SAM EMS database structures in order to determine the logicalrelationships.

The Adapter discovers the following topology elements:

n Physical topology—Routers, Switches, BaseCards, DaughterCards, Chassis, IPs, NetworkConnections, IPNetworks, MACs, and Interfaces

n Logical topology:

n IP Availability Manager—NetworkAdapterRedundancyGroups (from Alcatel-Lucent 5620 SAMEMS Link Aggregation Groups)

n MPLS—VPLS, VLLs, GREs, LDPs, VPNs, VRFs, MPLSServices, LSPs, LSPHops, andForwarderEndpoints

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

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

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

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

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

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

n Chapter 5 Mapping of Smarts objects and SAM-O Objects

n Chapter 6 Mapping of SAM-O Objects and Smarts Notifications


VMware, Inc. 17

Discovery of connections

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

A Cable is instantiated for:

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

n Each Physical Link on the 5620 SAM EMS. A Physical Link on the EMS can either be manuallycreated by the operator or automatically instantiated via the LLDP (Link Layer Discovery Protocol) runat the port level.

A NetworkConnection is instantiated for:

n Each pair of OSPF or ISIS neighbors

n 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 or above. Configuringthe WANLink driver provides instructions for configuring the Adapter for the WANLink driver in aninstallation that includes the IP Availability Manager.

Event processing

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

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

n Configuring JMS message filtering

n Configuring alarm processing

The Adapter transforms the XML data into VMware Smart Assurance topological objects and values,which it pushes to the various analysis servers. In addition, the EMS provides state changes that theAdapter 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 reconnectionrecovery phase.

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

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

Multi-vendor topology support


VMware, Inc. 18

The Adapter discovers Alcatel-Lucent devices and creates a topology of the network managed by theAlcatel-Lucent 5620 SAM EMS.

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

The Managers individually handle post-processing to stitch together the physical and logical topologiesfrom both the EMS and other sources in a heterogeneous network. Architecture for multi-vendor topologysupportillustrates this architecture. Post-processing creates objects such as a NetworkConnectionbetween an Alcatel-Lucent element and a non-Alcatel-Lucent element.

Figure 1-2. Architecture for multi-vendor topology support

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

Fault tolerance

If the Alcatel-Lucent 5620 SAM EMS fails over, the Adapter is designed to connect to the newly activatedEMS.


VMware, Inc. 19

Troubleshooting

The following information is available in Chapter 9 Troubleshooting:

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

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

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


VMware, Inc. 20

Configuring the AdapterDeployment 2This chapter explains how to configure the Adapter for Alcatel-Lucent 5620 SAM EMSdeployment. Itincludes procedures for configuring a deployment that includes the VMware Smart Assurance MPLSManagement Suite, VMware Smart Assurance Network Protocol Management Suite, and the VMwareSmart Assurance Multicast Manager. Your deployment may include some or all of these products. Pleaseignore any procedures that do not apply to your deployment. In addition, this chapter containsconfiguration information for the Alcatel-Lucent SAM-O client and EMS.


n Methods for modifying user configuration parameters

n Configuring the Alcatel-Lucent 5620 SAM EMS server

n Copying required .jar files

n Configuring the Adapter

n Configuring JMS message filtering

n Configuring alarm processing

n Configuring Domain Managers

n Additional configuration for NPM Managers

n Additional configuration for the Multicast Manager

n External polling auto-configuration

n Replacing existing Domain Manager repositories

n Rolling the Adapter Log

n Device filtering (optional)

Methods for modifying user configuration parameters

There are two methods for modifying user configuration parameters:

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

n Use the command line to issue the dmctl command to temporarily modify configuration parameterswhen the Adapter is running.

VMware, Inc. 21

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

Using the Global Console

VMware Smart Assurance provides the sm_edit utility to ensure that modified files are always saved tothe 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 specifythe path and the name of the file (relative to the BASEDIR/smarts directory) that you want to edit. Forexample,

sm_edit conf/alcatel-sam/vmwareConfig.import

opens a local copy of the vmwareConfig.import file in BASEDIR/smarts/local/conf/alcatel-sam (or anoriginal copy of the vmwareConfig.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-samdirectory.

You can use the sm_edit utility to edit any text file (configuration file, rule set file, tool script, template) inthe BASEDIR/smarts (or BASEDIR/smarts/local) directory. Because sm_edit assumes a starting point ofBASEDIR/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 VMware Smart Assurance System Administration Guide provides additional information about thesm_edit utility.

Note Original versions of files may be changed or updated as part of an VMware Smart Assurancesoftware upgrade. However, files located in the BASEDIR/smarts/local directory are retained during anupgrade.

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 youradministration account (for example, admin and changeme).

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

Configuring the Alcatel-Lucent 5620 SAM EMS server


VMware, Inc. 22

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

Note Your installation must include a license for the Alcatel-Lucent 5620 SAM-O interface in addition tothe 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 proceduresin 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 #unique_45/unique_45_Connect_42__ALC5620_USER_CONFIGURATION_62953. One password instance isencrypted 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 rootcause analysis, do the following:

n Enable the Events policy.

n Enable a MIB Administrative State entry.

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

Note This section provides an overview of the procedures to configure the Alcatel-Lucent 5620 SAMEMS server. The Alcatel-Lucent 5620 Service Aware Manager User Guide provides detailedinstructions.

Enabling the Events policy

Enable 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

2 Log Records.

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

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

5 Specify the Log Type by choosing Log Policy.

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

7 Select Events to enable.

Enabling a MIB Administrative State entry


VMware, Inc. 23

Enable 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:

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

4 Highlight the policy and click Properties.

5 Click MIB Entry Policies.

6 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 thevalue.

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

n Click OK to save the changes.

7 Close the window.

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

Setting the appropriate ports for a firewall

If there is a firewall between the Alcatel-Lucent 5620 SAM EMS and the Adapter, ensure that all of thefollowing ports are open:

n TCP 1096–1100

n TCP 4444–4447

n TCP 8080

n TCP 8443

n TCP 8093

n TCP 8094

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

Copying required .jar files

Your installation requires the copying of some .jar files from the Alcatel-Lucent 5620 SAM EMS serverand 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 lastAdapter installation, you must copy the new samOss.jar file in BASEDIR/smarts/local/classes beforestarting the Adapter.

Copying required .jar files for EMS 17.9 and 19.6


VMware, Inc. 24

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 Adapter

Configure the Adapter to use VMware Smart Assurance Domain Managers. In addition, configureparameters 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 iscompatible with this version of the Adapter. You may wish to save the file in another location so you canrefer to information such as network addresses.

When configuring the Adapter, you must include the MD-5-hashed version of the password for theAlcatel-Lucent 5620 SAM EMS. Generating an MD-5-hashed password provides instructions.

By default, generic commands are provided for a UNIX platform. When entering commands, pleaseadjust for your local practice. For example,

When entering a command in a UNIX environment, place “./” directly in front of the command (with nospace between it and the command). 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 #unique_54/unique_54_Connect_42__ALC5620_USER_CONFIGURATION_62953, as appropriate for yourdeployment.

Note This procedure assumes that you are configuring a deployment that includes the IP AvailabilityManager, 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 thesecharacter strings as blank, as described in Preventing access to an optional server.

3 Save the file.

Chapter 10 Understanding the sm_edit Utility provides more information.


VMware, Inc. 25

emsConfig.import parameters

When configuring the parameters listed in Adapter configuration parameters , configure server names forthe following:

n IP Availability Manager (AMServerName)

n Adapter Platform (OIServerName)

n Adapter server name (ASAServerName)

The MPLS, Multicast, BGP, OSPF, and IS-IS servers are optional. Preventing access to an optionalserver provides important information.

Table 2-1. Adapter configuration parameters

Parameter Type Description Values

EMS/JMS connection configuration parameters

EMSVersion string Specifies the EMS version 17.9 to 19.6

EmsInstance 4 strings Specifies:

n IP address where theAlcatel-Lucent 5620 SAMEMS server is running

n Alcatel-Lucent 5620 SAMEMS server port number

n user login

n user password (must beMD-5-hashed)

n An IP address

n The port number, usually 8080

n The Alcatel-Lucent 5620 SAMEMS user login name in cleartext

n The MD-5-hashed version of thepassword described in Step 7 ofConfiguring the Alcatel-Lucent5620 SAM EMS server.

Generating an MD-5-hashedpassword provides importantinstructions.

NOTE: This user name must beconfigured with OSS Managementprivileges, as described inConfiguring the Alcatel-Lucent 5620SAM EMS server.

NOTE: For assistance with Alcatel-Lucent 5620 SAM EMS user namesand passwords, consult your Alcatel-Lucent administrator.


VMware, Inc. 26

Table 2-1. Adapter configuration parameters (continued)


AltEmsInstance 4 strings For the standby Alcatel-Lucent5620 SAM EMS server,specifies:

n IP address where theAlcatel-Lucent 5620 SAMEMS server is running

n Alcatel-Lucent 5620 SAMEMS server port number

n user login

n user password (must beMD-5-hashed)

n An IP address

n The port number, usually 8080

n The Alcatel-Lucent 5620 SAMEMS user login name in cleartext

n The MD-5-hashed version of thepassword described in Step 7 ofConfiguring the Alcatel-Lucent5620 SAM EMS server.

Generating an MD-5-hashedpassword provides importantinstructions.

NOTE; If there is no standby Alcatel-Lucent 5620 SAM EMS server, enterthe same values as for EmsInstance.


JmsPort string Specifies the URL:port wherethe SAM-O accepts requests tomonitor asynchronous events.

Check with your 5620 SAMEMS administrators whensetting the value for JmsPortand AltJmsPort. If it isimproperly set, the Adapter willnot be able to connect to thealternate 5620 SAM EMS serverwhen a switchover occurs.

Must be resolvable from the machinewhere the adapter is running.

NOTE: The Alcatel-Lucent 5620SAM EMS behaves differently basedon which JMS Ports are selected. Ifthe 5620 SAM EMS is running in

n Standalone mode—Use port1099.

n Redundant mode for HighAvailability—Use port 1100.

If necessary, check with your Alcatel-Lucent 5620 SAM EMS administratorto determine the mode.

AltJmsPort string Specifies the URL:port on thestandby Alcatel-Lucent 5620SAM EMS server where theSAM-O accepts requests tomonitor asynchronous events.

Check with your 5620 SAMEMS administrators whensetting the value for JmsPortand AltJmsPort. If it isimproperly set, the Adapter willnot be able to connect to thealternate 5620 SAM EMS serverwhen a switchover occurs.

Must be resolvable from the machinewhere the adapter is running.

NOTE: The Alcatel-Lucent 5620SAM EMS behaves differently basedon which JMS Ports are selected. Ifthe 5620 SAM EMS is running in

n Standalone mode—Use port1099.

n Redundant mode for HighAvailability—Use port 1100.

If necessary, check with your Alcatel-Lucent 5620 SAM EMS administratorto determine the mode.


VMware, Inc. 27



ClientId string The identifier the Adapter is touse when making XML requeststo Alcatel-Lucent 5620 SAMEMS.

Recommended to be of format:smarts@12345

JmsUniqueId string For durable JMS connections,this ID identifies the Adapter tothe Alcatel-Lucent 5620 SAMEMS server.

Recommended to be of format:smarts@12345

NOTE: For non-durable JMSconnections, leave this field blank.

JmsUser string JMS connections require validuser names and passwords.This field specifies the username to be used by theAdapter.

Must match the user nameconfigured on the Alcatel-Lucent5620 SAM EMS server, as providedby your Alcatel-Lucent administrator.Step 7 of Configuring the Alcatel-Lucent 5620 SAM EMS serverprovides instructions.

NOTE: This user name must beconfigured with OSS Managementprivileges, as described inConfiguring the Alcatel-Lucent 5620SAM EMS server.


JmsPassword string JMS connections require validuser names and passwords.This field specifies thepassword to be used by theAdapter.

Must match the password configuredon the Alcatel-Lucent 5620 SAMEMS server, as provided by yourAlcatel-Lucent administrator. Step 7of Configuring the Alcatel-Lucent5620 SAM EMS server providesinstructions.

This must be the clear text version,not the md5-hashed version.


JMS reconnection management

EMSReconnectInterval integer Specifies the interval at whichthe Adapter tries to reconnect tothe EMS server. This value is inseconds.

Default is 60

If set to zero, the Adapter does notautomatically reconnect to the EMS,so you must initiate reconnectionmanually, as described inrestartJMSConnector.asl.


VMware, Inc. 28



JmsConnectionMode string Specifies whether the JMSserver sends new messagesbefore earlier messages havebeen acknowledged. There aretwo modes:

n DUPS(DUPS_OK_ACKNOWLEDGE): JMS server may sendnew messages beforeearlier messages areacknowledged (this mode isvalid only for EMS 17.9 orlater)

n AUTO(AUTO_ACKNOWLEDGE):JMS server will not send anew message untilmessage is acknowledged

Default is AUTO

MissedKeepAliveMessages integer Specifies the number ofconsecutive KeepAlivemessages that are missed todetermine the EMS Connectionto have failed.

Default is 3

RestartTimeAfterTerminateClient integer Specifies the time interval atwhich the adapter will try toreconnect to the EMS afterreceiving theTerminateClientSessionmessage from the EMS.

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

Discovery options

DiscoveryOnStartup boolean This parameter controls whethera full discovery will beperformed immediately afterstartup.

TRUE or FALSE

Default is FALSE.

NOTE: Alcatel-Lucent does notrecommend that you set thisparameter to TRUE. If the parameteris set to TRUE, the Adapter will starta full discovery upon startup.

After the repositories are populatedby a discovery, you should set thisparameter to FALSE for futurerestarts.

DiscoveryOnJmsLoss boolean This parameter controls whetherSAM-O discovery will beinitiated automatically whenJMS events are missed or whenthe 5620 SAM server switches.

TRUE or FALSE. Default is TRUE.

NOTE: For large topologies, Alcatel-Lucent recommends that you set thisto FALSE.


VMware, Inc. 29



FibDiscoveryEnabled boolean This parameter controls whetherdiscovery of FIB will beperformed.

WARNING: Enabling this in alarge-scale network couldincrease discovery timedrastically.

TRUE or FALSE. Default is FALSE.

IGMPNetworkDiscoveryEnabled boolean This parameter controls whetherdiscovery of IGMPNetwork willbe performed.

Please edit the file<SM_HOME>/conf/alcatel-sam/ASA-Filter.conf and uncommentthe line containing"igmp.IfGroup" if IGMPNetworkdiscovery is enabled.

WARNING: Enabling this in alarge-scale network couldincrease Multicast discoverytime drastically.


MulticastTreeDiscoveryEnabled boolean This parameter controls whetherdiscovery will be performed toconstruct Multicast Treecomponents such as (S,G),(*,G) and PIM Hops.

WARNING: Enabling this in alarge-scale network couldincrease Multicast post-processing time drastically.


Create7210NetworkConnections boolean This parameter controls whetherthe adapter creates networkconnections based on /30and /31 IP addresses in 7210SAS-E Switches.

Note: When setting thisparameter to TRUE, setCreateIESSAPs andCreateVPRNSAPs to TRUEalso.


CreateIESSAPs boolean This parameter controls whetherService Access Point objects forIES services will be discovered.


CreateVLLSAPs boolean This parameter controls whetherService Access Point objects forVLL services will be discovered.



VMware, Inc. 30



CreateVPLSSAPs boolean This parameter controls whetherService Access Point objects forVPLS services will bediscovered.


CreateVPRNSAPs boolean This parameter controls whetherService Access Point objects forVPRN services will bediscovered.


UnmanageWhenInMaintenance boolean This parameter controls if theIsManaged attribute will be setto false when the topology is inmaintenance mode (olcState ==1).


VPLSRTPrefix integer The adapter will use this prefixto create RouteTargets for eachVPLS This parameter isrequired to be distinct for eachadapter in a multi- adapterenvironment. In addition, it isalso highly recommended thisvalue is chosen such that theresulting RouteTarget, which isformed by combining thisparameter with the VPLSservice component id (orservice manager id), will notcollide with RouteTargets ofVPRN 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 VMware SmartAssurance IP AvailabilityManager server

NOTE: This server ismandatory.

Default, INCHARGE-AM

OIServerName string Name of the VMware SmartAssurance Adapter PlatformServer

NOTE: This server ismandatory.

Default, INCHARGE-OI

MPLSServerName string Name of the VMware SmartAssurance MPLS Managerserver

Default, INCHARGE- MPLS-TOPOLOGY

Preventing access to an optionalserver provides importantinformation.


VMware, Inc. 31



BGPServerName string Name of the VMware SmartAssurance Network ProtocolManager for BGP server

Default, INCHARGE-BGP


OSPFServerName string Name of the VMware SmartAssurance Network ProtocolManager for OSPF server.

Default, INCHARGE-OSPF


ISISServerName string Name of the VMware SmartAssurance Network ProtocolManager for IS-IS

Default, INCHARGE-ISIS


MCASTServerName string Name of the VMware SmartAssurance Multicast Managerserver

Default, INCHARGE-MCAST


Domain Manager reconfiguration parameters

ReconfigureDelayTime integer Determines how long theadapter initially delays beforeinvoking a reconfigureAndWaiton a backend VMware SmartAssurance analysis server.Running a reconfiguration toooften can cause performanceissues on the backend servers.Certain processes inside theAdapter require a reconfigure totake place before processescan run.

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

ReconfigureSlidingWindow integer Determines how long theAdapter waits afterReconfigureDelayTime for aquiet period. This parameter isused to slide the delay forwardin tiny increments whentopology changes are stillrapidly being processed by theadapter.

This time is specified in seconds anddefaults to 10 seconds.

MaximumReconfigureDelayTime integer Determines the maximum delaythe Adapter will wait beforeinvoking a reconfigureAndWaiton a backend VMware SmartAssurance analysis server. Thisvalue should be longer or thesame asReconfigureDelayTime.

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

Raw Alcatel-Lucent 5620 SAM EMS alarm handling options


VMware, Inc. 32



ClearAlarmOnDelete boolean When SAM-O deletes alarms,this parameter controls whetherthe corresponding notificationsshould be cleared.


NOTE: This parameter is in effectonly when ArchiveOnDelete is set toTRUE.

ArchiveOnDelete boolean When SAM-O deletes alarms,this parameter controls whetherthe corresponding notificationsshould be archived.


Router Down analysis enhancement parameters

NeighborDownThresholdForRouterDown

integer Specifies the thresholdpercentage of NPM neighborsof a router that are experiencingSnmpReachability problems inorder to conclude that thisrouter is functionally down.

This is a percentage value anddefaults to 80. If this value is set to 0,then a router down event will begenerated whenever aSnmpReachabilityProblem (Alarm243) is received from the EMS.

RouterDownCheckInterval integer Specifies the time interval inseconds at which the routerdown verification procedureruns.

Default is 60

Miscellaneous configuration parameters

LogLevel integer Data logged at this level ormore important is kept, otherdata is discarded.

n Level 1 will log severe messagesonly.

n Level 2 will log warnings andsevere messages.

n Level 3 will log informationalmessages, warnings, and severemessages.

n Level 7 will log everything(including verbose internalmessages).

Preventing access to an optional server

To configure the Adapter so that it does not attempt to access an optional server, configure the parameteras 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


VMware, Inc. 33

Create an MD-5-hashed version of the password for each Alcatel-Lucent 5620 SAM EMS server. Using aclear-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.

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

3 Convert the password, as follows:

md5hash.bash <password string>

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

Configuring the WANLink driver

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

Note For IP 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

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 addthe 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.5

567.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.5

567.1.1.*|.1.3.6.1.4.1.6527.1.6.*|.1.3.6.1.4.1.738.1.5.100.1.1.19.*

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

1 Edit the <IP>/smarts/local/conf/discovery/tpmgr-param.conf file in the IP Availability Manager. Changethe 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.


VMware, Inc. 34

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

41.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.46

41.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 filtering

Configure the Adapter for Alcatel-Lucent 5620 SAM EMS to use either a durable or non-durable JMSconnection 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:

n Object creation—For incremental inventory and alarm posting

n Object deletion—For incremental inventory and alarm clearing

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

n State change—For monitoring JMS missed events and change of sysPrimaryIp upon which a fulldiscovery 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. TheAdapter transforms the JMS messages into data that it pushes to the various Domain Managers, asfollows:

n Alarms to the Adapter Platform

n 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 yourdeployment.

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


VMware, Inc. 35

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

apipe.L2AccessInterface

apipe.Site

bgp.Peer

cpipe.Site

cpipe.Cpipe

epipe.Epipe

epipe.L2AccessInterface

epipe.Site

equipment.BaseCard

equipment.ControlProcessor

equipment.DaughterCard

equipment.FanTray

equipment.FlashMemory

equipment.PhysicalPort

equipment.PowerSupplyTray

equipment.ProcessorCard

equipment.CardSlot

equipment.DaughterCardSlot

equipment.SwitchFabricProcessor

fpipe.Fpipe

fpipe.L2AccessInterface

fpipe.Site

ies.Ies

ies.Site

ies.L3AccessInterface

# IGMPNetwork discovery is disabled by default.

# Please uncomment the following line if IGMPNetwork discovery is enabled.

#igmp.IfGroup

igmp.Interface

igmp.Site

ipipe.Ipipe

ipipe.L2AccessInterface

ipipe.Site

isis.Adjacency

isis.Area

isis.AreaMember

#isis.AreaSite

isis.Interface

isis.InterfaceLevelOneConfig

isis.InterfaceLevelTwoConfig

isis.Site

# FIB discovery is disabled by default.

# Please uncomment the following two lines if FIB discovery is enabled.

#l2fib.FibEntry

#l2fib.MFibEntry


VMware, Inc. 36

lag.Interface

lag.PortTermination

ldp.Interface

ldp.TargetedPeer

mpls.DynamicLsp

mpls.Interface

mpls.LspPath

mpls.ProvisionedHop

mvpls.L2AccessInterface

mvpls.Mvpls

mvpls.Site

l3fwd.ServiceSite

netw.NetworkElement

netw.PhysicalLink

netw.DiscoveredPhysicalLink

ospf.AreaSite

ospf.Interface

ospf.Neighbor

ospf.Site

ospf.VirtualLink

ospf.VirtualNeighbor

pim.Groups

pim.Interface

pim.Neighbor

pim.RPSet

pim.Site

rtr.NetworkInterface

rtr.RouteStats

rtr.VirtualRouter

rtr.VirtualRouterIpAddress

service.SpokeConnector

service.CompositeService

sonetequipment.Sts12Channel





sonetequipment.TributaryChannel

sonetequipment.Tu3Channel

svt.MeshSdpBinding

svt.SpokeSdpBinding

svt.Tunnel

svt.TransportConnection

tdmequipment.DS0ChannelGroup

tdmequipment.DS1E1Channel


vlan.NetworkInterface

vlan.Vlan

vlan.Site

vlan.L2AccessInterface

vlan.NetworkInterfaceVlanBinding

vll.L2AccessInterface

vpls.L2AccessInterface

vpls.Site

vpls.Vpls


VMware, Inc. 37

vpls.VlanElement

vpls.VlanElementVplsSiteBinding

vpls.VlanPortL2AccessBinding

vprn.L3AccessInterface

vprn.Site

vprn.Vprn

vprn.IPsecInterface

fm.AlarmObject

TerminateClientSession

KeepAliveEvent

Modifying the default JMS filter

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

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

#igmp.IfGroup

Configuring alarm processing

Configure the Adapter to specify mapping of Alcatel-Lucent 5620 SAM EMS alarms to Global Managernotifications. These alarms are received over the JMS interface. Mapping is done in the ASA-Alarm.conffile, which contains default behavior specifications and examples of how to change default behavior forspecific 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 textadded 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 alsodetected by VMware Smart Assurance software. To facilitate this, the default configuration file has someannotated suggestions for filtering out such alarms.

Reloading alarm configuration files describes how to reload modified alarm files without restarting theAdapter.

Alarm processing parameters describes the configurable parameters for this file.


VMware, Inc. 38

Table 2-2. Alarm processing parameters

Parameter Description Context specifier Allowed values

SEVERITY If the Alcatel-Lucent 5620 SAM EMSdoes not provide a value for SEVERITYfor an alarm, the Adapter assigns thisdefault value.

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

MOMENTARY Alarms are DURABLE by default; theconf file defines certain alarms asMOMENTARY. To change an alarm fromDURABLE to MOMENTARY, you canadd the alarm to the list.

[DEFAULT | alarm-xx-xx-xx] The VMware Smart AssuranceService Assurance ManagerConfiguration Guide describesthese values in more detail.

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

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

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

[DEFAULT | alarm-xx-xx-xx] ON

OFF

NOTARGET For notifications not modeled by theAdapter, the expiration time is set to thisvalue.

Not applicable Integer seconds untilexpiration.

Default is 0

INACTIVE The specified alarm is discarded so it isnot passed to the Adapter Platform.

Most alarms are ACTIVE; the conf filelists the exceptions, which areINACTIVE.

[alarm-xx-xx-xx]

COMMENT Text string to be added to thenotification.

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

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

#

# 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


VMware, Inc. 39

# 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 ON

SEVERITY DEFAULT 7

EXPIRATION DEFAULT 0

NOTARGET 0

# An example

#DEDUP alarm-305-11-90 ON

INACTIVE alarm-305-11-90

MOMENTARY alarm-305-11-90

COMMENT alarm-305-11-90 "This is a test event"

SEVERITY alarm-305-11-90 8

EXPIRATION alarm-305-11-90 14400

# Inactive list

#

# Examples of 5620Sam alarms that correspond to VMware diagnoses

#

# IP/AMPM

INACTIVE alarm-10-3-8 # PhysicalPort EquipmmentDown = Interface Down

INACTIVE alarm-20-3-17 # LagDown = NetworkAdapterRedundancyGroup AllComponentsDown

INACTIVE alarm-36-13-32 # InterfaceDown = Interface Down

INACTIVE alarm-243-4-176 # SNMPReachabilityProblem = SNMPAgent Unreachable

INACTIVE alarm-249-32-32 # AccessInterfaceDown = Interface Down

# MPLS

INACTIVE alarm-25-12-19 # LspDown = LSP Down

INACTIVE alarm-97-16-83 # ServiceSiteDown = Forwarder Down

INACTIVE alarm-221-30-166 # SdpBindingDown = ForwarderEndpoint Down

# BGP

INACTIVE alarm-2-1-2 # PeerConnectionDown = BGPSession Disconnected


VMware, Inc. 40

# or BGPProtocolEndpoint RemoteSpeakerNotConfigured

# Momentary list

MOMENTARY alarm-31-4-24 # PollerProblem

MOMENTARY alarm-32-3-25 # NodeRebooted

The Alcatel-Lucent 5620 SAM EMS severities are translated to VMware Smart Assurance severitiesas shown in Mapping of Alcatel-Lucent 5620 SAM EMS and VMware Smart Assurance Alarmseverities.

Table 2-3. Mapping of Alcatel-Lucent 5620 SAM EMS and VMware Smart Assurance Alarmseverities

Alcatel-Lucent 5620 SAM EMS VMware Smart Assurance Description

8 1 Critical

7 2 Major

6 3 Minor

5,4,3,2 4 Unknown

1 5 Normal

Considerations for working with alarms

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

Removing unneeded alarms

The LSP path and tunnel enhancements eliminate the need for the Adapter to import certain alarms.Toavoid 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 # TunnelDown

INACTIVE alarm-26-12-20 # LspPathDown

4 Save and close the file.

Alarm default expiration time

You can set a default expiration time for all alarms or specific alarms using the adapter alarmconfiguration file. In this way, the alarm(s) will be cleared in VMware Smart Assurance even if they are notcleared in the Alcatel-Lucent 5620 SAM EMS server. If an alarm expiration is set to 0, it will stay in theVMware Smart Assurance Notification Log until a clear is sent by the Alcatel-Lucent 5620 SAM EMSserver through the Adapter.


VMware, Inc. 41

Alarms for objects with no associated repository objects

The Adapter sends alarms on objects that are not modeled in VMware Smart Assurance repositories.These are referred to as NOTARGET alarms. These alarms will be placed in the VMware SmartAssurance Notification Log, but they will not be associated with anything in VMware Smart Assurance.The NOTARGET alarms can be identified as alarms with Class names that start with SAMO- in theVMware Smart Assurance Notification Log. The Adapter alarm configuration file permits a different defaultvalue to be set for NOTARGET alarms than for alarms that have associated objects in VMware SmartAssurance.

Alarms that are set for manual clearing

The Adapter is configured by default to assume that operators will manually clear some alarms. Alarmsmay report unusual conditions but not clear when the conditions are cleared, based on the assumptionthat an operator will clear the alarm. This is not an optimum condition in the VMware Smart Assurancesoftware environment. Consult the Alcatel-Lucent 5620 SAM EMS training documentation for settingpolicies consistent with your operation.

Alarm synchronization

A request for a full discovery automatically synchronizes the alarms in the VMware Smart AssuranceNotification Log with the alarms in the Adapter. That is, it removes alarms in VMware Smart Assurancesoftware that are no longer in the Adapter, and it reintroduces alarms that have been removed or aremissing 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 AdapterPlatform (OI) are now inactive, are removed during sychronization. In addition, you can manually triggeralarm rediscovery by invoking the alarmRediscover.asl script. The Adapter has some configuration alarmswhich do not clear when the configuration problem is fixed, so the alarmRediscover.asl script can removealarms for conditions that no longer apply.

Aggregating alarms

You can aggregate alarms for convenience. When the Adapter sees one of the aggregating alarms, itcreates an aggregated alarm. The notification for the aggregate alarm is formed on the instance thattriggered 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


VMware, Inc. 42

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


VMware, Inc. 43

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 aremapped from the Alcatel-Lucent fm.AlarmObject object.

Each alarm contains three field elements, separated by hyphens(-). Use the hyphen (-) as a wildcard onthe <alarmType> and <alarmProbableCause> fields, if you wish to match any incoming alarm (for thatparticular 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>.

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

alarm-15--10

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

alarm-15-10-

n 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 withoutrestarting 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


VMware, Inc. 44

Use the InMaintenanceattribute on an alarm object to filter out alarms whose affected objects are inmaintenance mode. To enable this functionality, go to the Service Assurance Manager installationdirectory:

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 Acknowledged

attr InMaintenance

#attr Owner

#attr TroubleTicketID

New INACTIVE alarms in ASA-Alarm.conf

New INACTIVE alarms in this release lists new alarms that will be filtered as INACTIVE by default. Alarmsare located in the ASA-Alarm.conf file.

Note For more information regarding alarm handling by ASA-Alarm.conf, consult Configuring alarmprocessing.

Table 2-4. New INACTIVE alarms in this release

Default status Alarm Description



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

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



OSPF

INACTIVE alarm-141-24-112 # OspfInterfaceDown = OSPFInterface orOSPFNeighborRelationship Down

INACTIVE alarm-39-11-36 # InterfaceHelloConfig areaMismatch = OSPFInterfaceAreaIDMismatchSymptom

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


VMware, Inc. 45

Table 2-4. New INACTIVE alarms in this release (continued)

Default status Alarm Description

INACTIVE alarm-39-11-40 # InterfaceHelloConfig helloIntervalMismatch = OSPFInterfaceHelloOrDeadIntervalMismatchSymptom

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

INACTIVE alarm-39-11-42 # InterfaceHelloConfig optionMismatch = OSPFInterfaceAreaTypeMismatchSymptom

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

INACTIVE alarm-45-14-46 # InterfaceHelloAuthFailure authFailure = OSPFNetworkAuthKeyMismatchSymptom

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 = OSPFVirtualLinkNetmaskMismatchSymptom

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

Configuring Domain Managers

In an Alcatel-Lucent environment, the Adapter imports topology from the Alcatel-Lucent 5620 SAM EMSand then directly populates any associated Domain Managers with this topology.

Configure your deployment based on the following considerations:

n Scenario 1: Deployment with IP in an all Alcatel-Lucent environment. The network includes all Alcatel-Lucent devices; the deployment does not include the IP Availability Manager version 8.1 or theTopology Split Manager.


VMware, Inc. 46

n Scenario 2: Deployment with mixed vendor environment and IP Manager . The deployment includesboth Alcatel-Lucent and non-Alcatel-Lucent devices (a mixed-vendor environment) where IP 7.x getstopology from both ASAM and from non-ASAM devices.

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

n Scenario 3: Deployment with IP Manager

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

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

n Additional configuration for NPM Managers

n Additional configuration for the Multicast Manager

If your new Adapter for Alcatel-Lucent 5620 SAM EMS installation is in conjunction with upgradesfrom 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 DomainManager, and configure the Domain Manager to replace the existing repository with one populated bythe Adapter. Replacing existing Domain Manager repositories provides instructions.

Scenario 1: Deployment with IP in an all Alcatel-Lucentenvironment

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 or the Topology SplitManager.

Configuring the Adapter Platform

Using the Global Manager Administration Console, attach to the Adapter Platform, and then create adomain for the Adapter of the ASAM DomainType. This procedure is required because there is no defaultdomain for the Adapter.

Follow the procedure, Creating a domain, in the VMware Smart Assurance Service Assurance ManagerConfiguration Guide.

Configuring the Service Assurance Manager

Use the Global Manager Administration Console to create a domain for each of the Domain Managers inyour deployment.


VMware, Inc. 47

Follow the procedure, Creating a domain, in the VMware Smart Assurance Service Assurance ManagerConfiguration 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 thedeployments that include the IP Availability Manager, MPLS Manager, or NPM Managers for BGP, OSPF,and IS-IS.

Configuring the MPLS Manager

Configure the MPLS Manager to prevent automated topology transfer from the attached IP AvailabilityManager.

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

sm_edit conf/mpls-t/mpls.conf

2 Locate the section,

3 # InChargeDomain::InChargeDomain_INCHARGE-AM {

4 Comment out this section, as shown below.

# InChargeDomain::InChargeDomain_INCHARGE-AM {

# Type = "AM"

# DomainName = "INCHARGE-AM"

# DisplayName = "INCHARGE-AM"

# }

Configuring the Multicast Manager

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


sm_edit conf/mcast/multicast.conf

2 Locate the section,

3 # InChargeDomain::InChargeDomain_INCHARGE-AM {

4 Comment out this section, as shown below.

# InChargeDomain::InChargeDomain_INCHARGE-AM {

# Type = "AM"

# DomainName = "INCHARGE-AM"

# DisplayName = "INCHARGE-AM"

# }

5 Set the value as shown for the following variable:

IsEMS = TRUE


VMware, Inc. 48

Scenario 2: Deployment with mixed vendor environment and IPManager

The following environment setup is required for the Adapter to interoperate with IP in a mixed vendorenvironment:

Set up the IP Manager

1 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 Management Suite

1 At MPLS_BASEDIR/smarts/bin, enter the following command:


2 There are two parameters, named:

peek Vendor ~Alcatel

#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 AvailabilityManager server name. The VMware Smart Assurance MPLS Management Suite User Guideprovides 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 Management Suite


VMware, Inc. 49

In order to enable interoperability of the Network Protocol Management Suite with both IP AvailabilityManager and Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.5, you must add the IP AvailabilityManager as the source for each Network Protocol Manager.

Important For interoperability with IP Availability Manager you must choose the IP Availability Managerserver name as the topology source.

The VMware Smart Assurance Network Protocol Manager Discovery Guide Supplement explains theprocedure in more detail. Here is an example procedure to follow:

1 Start the 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:

3 Ensure that the VMware Smart Assurance Broker for your deployment appears in the Broker textbox.

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

5 Type your login username and password.

6 Click OK.

The Topology Browser console opens.

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

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

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

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

Scenario 3: Deployment with IP Manager

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






VMware, Inc. 50











4 Locate the section, Instances of AM Server, and set the AM server name to the IP-Analysis servername. The VMware Smart Assurance MPLS Management Suite User Guide provides additionalinformation.



1 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 servername. The VMware Smart Assurance Multicast Manager User Guide provides additional information.


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

--bootstrap=bootstrap-lite.conf


In order to enable interoperability of the Network Protocol Management Suite with both IP AvailabilityManager and Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.5, you must add the IP-AnalysisManager as the source for each Network Protocol Manager.

Important For interoperability with IP Availability Manager, you must choose the IP-Analysis Managerserver name as the topology source.


VMware, Inc. 51

The VMware Smart Assurance Network Protocol Manager Discovery Guide Supplement explains theprocedure in more detail. Here is an example procedure to follow:



sm_gui

Press Enter.





6 Click OK.




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

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

Run discovery and update the discovery timers for IP

After the Adapter completes a full discovery, update the discovery timers in the IP Manager. This allowsthe IP Availability Manager 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)


VMware, Inc. 52

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, Instancesof AM Server.















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



1 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 IPAvailability Manager servers that obtain topology from the TSM server.


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

--bootstrap=bootstrap-lite.conf


VMware, Inc. 53


In order to enable interoperability of the Network Protocol Management Suite with IP AvailabilityManager , the Topology Split Manager (TSM), and the Adapter for Alcatel-Lucent 5620 SAM EMS Version3.5, you must add multiple IP Availability Managers as topology sources for each Network ProtocolManager.

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

Here is an example procedure to follow:



sm_gui

Press Enter.





6 Click OK.




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

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

11 Continue to use the Add Source dialog box to add additional IP Availability Manager servers thatobtain topology from the TSM server.

Note If using TSM, you must contact VMware Professional Services to obtain the appropriatediscovery procedures.


VMware, Inc. 54

Additional configuration for NPM Managers

Important If your deployment includes Network Protocol Manager for BGP or Network ProtocolManager for OSPF version 9.4.2 or later, the configuration procedures outlined in this section are requiredto configure the DisplayName variable.

Configure individual Network Protocol Managers

Before starting a Network Protocol Manager for BGP or Network Protocol Manager for OSPF, configurethe 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 notperform step 5.

1 If running, stop the Network Protocol Manager, as described in the VMware Smart AssuranceNetwork 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

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

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

Additional configuration for the Multicast Manager


VMware, Inc. 55

Optionally, customize the Multicast GroupTypeInfo setting to specify mapping for Multicast group IPaddresses 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"}

# }

# }

#

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

4 Uncomment the customized section.


6 Restart the Multicast Manager.

External polling auto-configuration

This section describes the auto-configuration feature that supports external polling by the Alcatel-Lucent5620 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#unique_103/unique_103_Connect_42__ALC5620_USER_CONFIGURATION_34715. Look in the Pollingand 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 New polling groups. The VMwareSmart Assurance IP Availability Manager User Guide, VMware Smart Assurance MPLS ManagementSuite User Guide, VMware Smart Assurance Network Protocol Manager for BGP User Guide, theVMware Smart Assurance Network Protocol Manager for OSPF User Guide, and the VMware SmartAssurance Network Protocol Manager for IS-IS User Guide provide additional information about Pollingand Threshold Groups.


VMware, Inc. 56

Table 2-5. New polling groups

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 seethe following Connectivity Polling: External Poller settings:

n InstrumentCards parameter (under the Parameters tab) is set to true.

n Initial Status parameter is not initialized (set to UNKNOWN).

Available under 5620 SAM Managed Systems Polling Groups:

5620 SAM Managed Systems> Settings >

n Connectivity Polling - External Poller

IP AM/PM All options for the IP Availability Manager plus the following:

n 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

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

Replacing existing Domain Manager repositories

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


VMware, Inc. 57

Before starting the Domain Manager server, remove the repository file from each Domain Manager inyour 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.

3 Start the Domain Manager server.

After all servers are started, perform a full discovery.

Rolling the Adapter Log

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

Device filtering (optional)

The Adapter can filter devices from the Alcatel-Lucent 5620 SAM EMS server based on 5620 SAM EMSserver site names. Site names appear as the DisplayName property of UnitaryComputerSystems (routersand switches) in the VMware Smart Assurance Global Console.

Note Setting up device filtering requires use of Adapter Scripting Language (ASL) scripts. The VMwareSmart Assurance 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 serverprocessing. Filtering reduces the number of objects stored inside VMware Smart Assurance servers andlessens the process load on the Adapter. Filtering is recommended on devices that are in a constant stateof flux, where monitoring is not desired.

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

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


VMware, Inc. 58

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

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

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

Managing devices not in effect 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 fromASAM/routerDiscover.asl) is required to reload the Adapter's internal filtering list. A discovery isrequired because reloading the filter list requires several (potentially long) processes to run in order toclean 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

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. Tospecify how to match a character string that starts with HOUSTX, add .* (a period followed by anasterisk), which may be slightly different that what you expect from your experience searching forfiles, 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, thematching character string must have HOUSTX and zero or more of any possible characters.


VMware, Inc. 59

Start up and Discovery 3This chapter describes how to start the Adapter and associated Domain Managers, verify the productstatus, and initiate discovery. In addition, it describes options for managing file data.


n Starting Adapter and Domain Manager services

n Initiating discovery

n Removing an unused JMS durable connection

Starting Adapter and Domain Manager services

Note Use the sm_service command to start and stop Adapter and Domain Manager servers that wereinstalled as services. If you need to install a service manually, the VMware Smart Assurance Adapter forAlcatel-Lucent 5620 SAM EMS Installation Guide provides instructions.

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 theservice as described in this section. If you are starting the Domain Manager after it already has arepository, 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

VMware, Inc. 60

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-topology

sm_service start ic-mpls-analysis

sm_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


VMware, Inc. 61

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. Forexample,

sm_service stop ic-asam

Initiating discovery

This 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 aremapped to VMware Smart Assurance objects:

n Chapter 4 Mapping of SAM-O Elements to Smarts Objects

n Chapter 5 Mapping of Smarts objects and SAM-O Objects

Initiating full discovery

After installing, configuring, and starting the Adapter, you can manually initiate full discovery. To start a fulldiscovery, 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:

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

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

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

n Re-read files in the Adapter Platform.

Service-only discovery


VMware, Inc. 62

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

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

Scheduling a periodic discovery 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, MulticastManager, NPM Manager for BGP, OSPF, or IS-IS, use the -DQUALIFIER parameter, with a value ofMPLS, 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 IPaddress:

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 discoveryor if the JMS is intentionally disabled. For example, you can schedule periodic service discoveries toavoid using JMS for a rapidly changing topology.

To schedule periodic discoveries at time with low network usage, use the following procedure, whichillustrates 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 4am

0 0 4 * * * BASEDIR/smarts/bin/sm_adapter -s <adapter_name> asa/serviceDiscover.asl

<system_temporary_files_directory>


VMware, Inc. 63

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 5620SAM EMS and then synchronizes them. The procedure removes alarms from the Notification Log that nolonger exist in the Adapter, and adds new alarms to the Notification Log.

Removing an unused JMS durable connection

The Adapter is kept informed of changes to the Alcatel-Lucent network by the Alcatel-Lucent 5620 SAMEMS server. The mechanism by which this is accomplished is called Java Messaging Service (JMS). TheAdapter normally connects to the server using “durable” connections. This means that if the Adapter goesdown, the server will queue up changes that are taking place and deliver those changes to the Adapterwhen it reconnects. The Adapter is known to the Alcatel-Lucent 5620 SAM EMS server by itsJmsUniqueId.

The presence of an unused JMS durable connection causes the Alcatel-Lucent 5620 SAM EMS toaccumulate 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.

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

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


VMware, Inc. 64

Mapping of SAM-O Elements toSmarts Objects 4This chapter includes the following topics:

n Examples of EMS elements mapped to VMware Smart Assurance objects

n Power supply instantiation

n SAM-O element to VMware Smart Assurance object mapping

Examples of EMS elements mapped to VMware SmartAssurance objects

This section illustrates how EMS elements are mapped to VMware Smart Assurance elements for thevarious Domain Managers.

Physical model

EMS to IP Manager mapping shows an example of the mapping of physical elements (Router, Card,Interface, Memory Processors, and Network Adapter Redundancy Group), as shown in the Alcatel-Lucent5620 SAM EMS Equipment View and as they are instantiated in the VMware Smart Assurance IPManager Domain Managers. In this example, mappings are shown for IP classes such as the following:

n NE (Network Element) maps to Router or Switch

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

n Physical Port maps to Interface

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

n Fresh Memory maps to Memory

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

VMware, Inc. 65

Figure 4-1. EMS to IP Manager mapping

Logical NPM BGP model

EMS to Network Protocol Manager for BGP mapping shows an example of the mapping of logicalelements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Managerfor BGP.

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

n BGP Routing Instance maps to BGPService

n BGP Peer maps to BGPProtocolEndpoint

n Autonomous System maps to AutonomousSystem


VMware, Inc. 66

n Confederation maps to Confederation

.

Figure 4-2. EMS to Network Protocol Manager for BGP mapping

Logical NPM OSPF model

EMS to Network Protocol Manager for OSPF mapping shows an example of the mapping of logicalelements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Managerfor OSPF.

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

n OSPF Routing Instance maps to OSPF Service

n OSPF Area maps to OSPFArea

n OSPF Interface maps to OSPFInterface

n OSPF Neighbor maps to OSPFNeighborEndpoint

n OSPF Virtual Link maps to OSPFVirtualInterface


VMware, Inc. 67

Figure 4-3. EMS to Network Protocol Manager for OSPF mapping

Logical NPM ISIS model

EMS to Network Protocol Manager for IS-IS mapping shows an example of the mapping of logicalelements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the Network Protocol Managerfor IS-IS.

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

n ISIS Area Member maps to ISIS Service


VMware, Inc. 68

n ISIS Area maps to ISISArea

n ISIS Interface maps to ISISInterface

n ISIS Neighbor maps to ISISNeighborEndpoint

Figure 4-4. EMS to Network Protocol Manager for IS-IS mapping

Logical Multicast model

EMS to Multicast Manager mapping 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:

n PIM Routing Instance maps to MulticastService

n PIM Interface maps to PIMInterface.


VMware, Inc. 69

Figure 4-5. EMS to Multicast Manager mapping

Logical MPLS VLL model

EMS to MPLS Manager VLL mapping shows an example of the mapping of logical MPLS VLL elementsin 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:

n VLL Service maps to L2 VPN and PseudoWire

n VLL Sites maps to Forwarder


VMware, Inc. 70

n SDPBindings maps to Forwarder Endpoints.

Figure 4-6. EMS to MPLS Manager VLL mapping

Logical MPLS VPLS model

EMS to MPLS Manager VPLS mapping shows an example of the mapping of logical MPLS VPLSelements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager. In thisexample, mappings are shown for MPLS classes such as the following:

n VPLS Service maps to VPLS VPN


VMware, Inc. 71

n VPLS Sites maps to Forwarder

n SDPBindings maps to Forwarder Endpoints.

Figure 4-7. EMS to MPLS Manager VPLS mapping

Logical MPLS VPRN model

EMS to MPLS Manager VPRN mapping and EMS to MPLS Manager VPRN Route Target mapping showexamples of the mapping of logical MPLS VPRN elements in the Alcatel-Lucent 5620 SAM EMS as theyare instantiated in the MPLS Manager.


VMware, Inc. 72

EMS to MPLS Manager VPRN mapping shows an example of the mapping of logical MPLS VPRNelements in the Alcatel-Lucent 5620 SAM EMS as they are instantiated in the MPLS Manager. In thisexample, mappings are shown for MPLS classes such as the following:

n VPRN Service maps to L3 VPN

n VPRN Sites maps to VRF

Figure 4-8. EMS to MPLS Manager VPRN mapping


VMware, Inc. 73

EMS to MPLS Manager VPRN Route Target mapping shows an example of the mapping of RouteTargets in the Alcatel-Lucent 5620 SAM EMS as they are instantiated as RouteTargets in the MPLSManager.

Figure 4-9. EMS to MPLS Manager VPRN Route Target mapping

Interfaces, Physical, Network, L2/L3

EMS to IP Manager interface mapping shows an example of the mapping of interface elements in theAlcatel-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:

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

n Network interface is mapped to Interface (NW indicated)

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

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


VMware, Inc. 74

Figure 4-10. EMS to IP Manager interface mapping

VLAN in the MPLS Manager

The Adapter instantiates VLAN sites in the MPLS Manager as they are not supported in the MPLS model.Modeling of VLAN and related components in the MPLS Manager shows the relationship between aVLAN and its related elements in the MPLS Manager.


VMware, Inc. 75

Figure 4-11. Modeling of VLAN and related components in the MPLS Manager

Associating a VLAN with a VPLS

The Adapter uses the model shown in #unique_136/unique_136_Connect_42__ALC5620_USER_APPX_SAM-O_ELEMENTS_78001 to associate a VLANwith a VPLS in the MPLS Manager. Their relationship is determined by the following elements:

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

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

VLAN naming

The object name of a VLAN object is the same as the objectFullName of the SAM-O object vlan.Vlan (theVLAN 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 asVLAN-<vlanId>/VPLS-<vplsId> For example:

VLAN-<vlanId>/VPLS-<vplsId>


VMware, Inc. 76

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

Figure 4-12. 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 tunnelsare now all modeled using the LSP class. LSPs may be distinguished from the other LSP class instanceswith the following display name convention: <Source Node> -> <Destination Node>/LSP-X (X representsthe LSPid).

The relationships among these objects are illustrated in Modeling of LSP paths and SDP tunnels .


VMware, Inc. 77

Figure 4-13. Modeling of LSP paths and SDP tunnels

Modeling of LSP paths

This enhancement addresses the correlation gaps that were identified when an LSP Interface is shutdown, and the Adapter diagnosed both Interface Disabled and LSP Down as root causes. To make thisdiagnosis, the Adapter relied on dynamic MPLS cross-connect data to establish the relationship betweenan 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 Interfacesduring root-cause analysis.

The Adapter takes advantage of the fact that all LSP paths are statically provisioned. Using the hopinformation that is specified when LSP paths are provisioned, the Adapter will create the relationshipsbetween the LSP paths and the Interfaces that will be traversed. This applies to both strict and loosehops.

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

Modeling of SDP tunnels

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


VMware, Inc. 78

In previous versions of the Adapter, SDP tunnels using GRE transport were modeled as NetworkConnections. Beginning with version 3.1, both GRE and MPLS transport SDP tunnels are now modeled inthe 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 nameconvention: <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 iswidely 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:

n IES SDP binding is modeled as ForwarderEndpoint. A PseudoWire is created between each pair ofbindings.

n IES site is modeled as Forwarder.

n IES service is modeled as VPN.

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

Power supply instantiation

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

SAM-O element to VMware Smart Assurance objectmapping

For each Domain Manager, Mapping of SAM-O Elements to VMware Smart Assurance objects showshow Alcatel-Lucent 5620 SAM-O interface elements are mapped to VMware Smart Assurance objects,and indicates where these objects are displayed.

Table 4-1. Mapping of SAM-O Elements to VMware Smart Assurance objects

VMware Smart Assurance Object SAM-O Class Displayed in 5620 SAM EMS Console

IP AM/PM

Cable equipment.PhysicalLink Manage > Equipment > Physical Link

Card equipment.BaseCard


equipment.ProcessorCard

Manage > Equipment > Card

CardRedundancyGroup equipment.ProcessorCard (one for eachpair)

Manage > Equipment > Card > ProcessorCard


VMware, Inc. 79

Table 4-1. Mapping of SAM-O Elements to VMware Smart Assurance objects (continued)


Chassis Derived from

equipment.Card

Number equals to Manage > Equipment >Network Element

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

Interface equipment.PhysicalPort Manage > Equipment > Port > PhysicalPort

rtr.NetworkInterface Manage > Routing Instances > NetworkInterface

sonetEquipment.Sts1Channel





sonetEquipment.Tu3Channel




Manage > Equipment > Port > LogicalPort > Channel, and

Manage > Equipment > Port > LogicalPort > Interface



Manage > Services > AccessInterface >L3 Access Interface







Manage > Services > AccessInterface >L2 Access Interface

IP - Manage > Routing Instances > IPAddresses, and

Manage > Routing Instances > RouterSite > RoutingInstanceSite > RoutingInstance

IPNetwork - -

MAC - -

Memory equipment.FlashMemory Manage > Equipment > Flash Memory

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

NetworkConnection Derived from

mpls.CrossConnect

ospf.Neighbor

pim.Groups

svt.Tunnel

-

PowerSupply equipment.PowerSupplyTray Manage > Equipment > Power SupplyTray


VMware, Inc. 80



Processor equipment.Processor Manage > Equipment > Card > ProcessorCard, or

Manage > Equipment > Processor

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

SNMPAgent netw.NetworkElement Managed > Equipment > Network Element

MPLS

Forwarder vll.Site

apipe.Site

epipe.Site

fpipe.Site

ipipe.Site

Manage > Services > Site (ServiceManagement) > Site (vll)

vpls.Site Manage > Services > Site (ServiceManagement) > AbstractSite (vpls) > Site(vpls)

ForwarderEndpoint. svt.MeshSdpBinding

svt.SdpBinding

svt.SpokeSdpBinding

Manage > Services > SdpBinding, or

Manage > MPLS Objects > SdpBinding

LdpAdjacency ldp.TargetedPeer (one for each pair) -

LdpProtocolEndpoint ldp.Interface

ldp.TargetedPeer

Manage > Routing Instances >RouterTerminatingInterface >RouterTerminatingNonIpInterface > LDPInterface, and

Application > Navigation Tree > Network(Expand LDP in each Routing Instance tocheck the TargetedPeers)

LSP mpls.LspPath Manage > LSPs > Static + Dynamic

LSPHop mpls.CrossConnect Manage > MPLS Objects > In Segment,and

Manage > MPLS Objects > Out Segment

MPLSService Mpls.Interface

vprn.Site

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

PseudoWire Derived from

svt.MeshSdpBinding

svt.SdpBinding

svt.SpokeSdpBinding

-

VPN vll.Vll

apipe.Apipe

epipe.Epipe

fpipe.Fpipe

ipipe.Ipipe

vpls.Vpls

vprn.Site

Manage > Services > Service (ServiceManagement)


VMware, Inc. 81



VRF vprn.Site Manage > Services > Site (ServiceManagement) > Site (vprn)

BGP

AutonomousSystem Derived from

rtr.VirtualRouter

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

BGPCluster Derived from

bgp.Peer

-

BGPProtocolEndpoint bgp.Peer Application > Navigation Tree > Network(Expand to examine all BGP peers in eachrouting 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 BGPpeers)

Confederation Derived from

rtr.VirtualRouter

-

OSPF

OSPFArea Derived from

ospf.AreaSite

Application > Navigation Tree > OSPF(Only those with routing instancescreated)

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

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

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

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

OSPFNetwork - -

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

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


VMware, Inc. 82



OSPFVirtualLink ospf.VirtualNeighbor (One for each pair) Application > Navigation Tree > OSPF(Expand to see each pair ofVirtualNeighbors)

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

IS-IS

ISISArea isis.Area Application >Navigation Tree >ISIS

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

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 > IGMPInterface

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

MulticastGroup Derived from

pim.RPSet

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

MulticastService igmp.Site

pim.Site

Manage > Routing Instances > RouterSite> ProtocolSite > IGMP, or

Manage > Routing Instances > RouterSite> ProtocolSite > PIM

MulticastSource Derived from

pim.Group

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

MulticastTree - -

PIMHop Derived from

pim.Group

-

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


VMware, Inc. 83



PIMSourceG pim.Group (SourceG) Application > Navigation Tree > Network(For each PIM Instance, click Property >Groups and check instances with “SourceType” 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”)


VMware, Inc. 84

Mapping of Smarts objects andSAM-O Objects 5The Adapter for Alcatel-Lucent 5620 SAM EMSuses SOAP/XML over HTTP to perform a full networkinventory from the Alcatel-Lucent 5620 SAM-O interface and create the topology, mapping SAM-Oobjects to VMware Smart Assuranceobjects.


n Discovered inventory objects

n Mapping of SAM-O equipment objects

n Mapping of SAM-O service objects

Discovered inventory objects

Adapter support for 5620 SAM EMS inventory lists the discovered Alcatel-Lucent 5620 SAM EMSinventory objects.

Table 5-1. Adapter support for 5620 SAM EMS inventory

Inventory Discovered objects

Physical inventory All SAM-O objects listed in #unique_144/unique_144_Connect_42__ALC5620_USER_APPX_SAM-O_OBJECTS_33699

MPLS inventory n apipe.Apipe, apipe.L2AccessInterface, apipe.Site

n cpipe.Cpipe, cpipe.Site

n epipe.Epipe, epipe.L2AccessInterface, epipe.Site

n fpipe.Fpipe, fpipe.L2AccessInterface, fpipe.Site

n ipipe.Ipipe, ipipe.L2AccessInterface, ipipe.Site

n ldpInterface, ldpTargetPeer

n mpls.CrossConnect, mpls.Interface, mpls.LspPath

n rtr.RouteStats

n svt.MeshSdpBinding, svt.SdpBinding, svt.SpokeSdpBinding, svt.TransportConnection

n vll.L2AccessInterface, vll.Site, vll.Vll

n vpls.L2AccessInterface, vpls.Site, vpls.Vpls

n vprn.Site

Multicast inventory n igmp.IfGroup, igmp.Interface, igmp.Site

n pim.Group, pim.Interface, pim.Neighbor, pim.RPSet

n service.SpokeConnector

n svt.MeshSdpBinding

n vpls.L2AccessInterface

VMware, Inc. 85

Table 5-1. Adapter support for 5620 SAM EMS inventory (continued)

Inventory Discovered objects

BGP inventory n bgp.Peer

n rtr.VirtualRoute

OSPF inventory n ospfAreaSite

n ospfInterface

n ospfNeighbor

n ospfSite

n ospfVirtualLink

n ospfVirtualNeighbo

IS-IS inventory n isis.Area

n isis.AreaMember

n isis.Site

n isis.Interface

n isis.Adjacency

n isis.InterfaceLevelOneConfig

Mapping of SAM-O equipment objects

Mapping of SAM-O equipment objects to VMware Smart Assurance class maps SAM-O equipmentclasses to VMware Smart Assurance objects.

Table 5-2. Mapping of SAM-O equipment objects to VMware Smart Assurance class

VMware Smart Assurance class

VMware SmartAssuranceattribute

SAM-O equipmentclass SAMO-O property SAM-O filter

Router/Switch (unless statedotherwise)

netw.NetworkElement -

Model - chassisType

HostsAccessPoints-> IP

- ipAddress

Name - objectFullName

DisplayName - siteName

HostsAccessPoints-> IP (loopbackaddress)

- systemAddress

Card (unless stated otherwise) equipment.BaseCard siteName

AdminStatus - administrativeState

IsManaged - equipmentState


OperStatus - operationalState

PartOf -> Chassis - siteId


VMware, Inc. 86

Table 5-2. Mapping of SAM-O equipment objects to VMware Smart Assurance class(continued)




Processor equipment.ControlProcessor

equipment.SwitchFrabicProcessor

siteName

DisplayName - displayedName


Card equipment.DaughterCard

siteName





Description - specificType

Fan equipment.FanTray siteName


Status - deviceState

DeviceID - fanId

Description - hwName



Partof -> Router/Switch

- siteId

Memory equipment.FlashMemory

siteName

FreeMemory - amountUsed

TotalMemory - capacity



BufferUtilizationPct - percentageUsed

Cable equipment.PhysicalLink

siteName

DisplayName - endpointAPointer

DisplayName - endpointBPointer



VMware, Inc. 87





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

PowerSupply1Status

- powerSupply1Status

PowerSupply2Status

- powerSupply2Status

TemperatureSensor HighThreshold -psTemperatureThreshold

Status - temperatureStatus

PartOf -> Router/Switch

- siteId


VMware, Inc. 88





Card equipment.ProcessorCard

siteName

Adminstatus - administrativeState






- siteId

- specificType

IsManaged - olcState

An entry in AD_PersistentDataSet l2fib.FibEntry nodeName

terminationType

serviceType

-definedPerObjectPointer

- macAddress

- objectFullName

- serviceId

An entry in AD_PersistentDataSet l2fib.MFibEntry serviceSiteId

- grpAddr

- objectFullName

- portId

- serviceId

NetworkAdapterRedundancyGroup lag.Interface siteName




+ - siteName




- siteId


VMware, Inc. 89





create relationship betweenNetworkAdapterRedundancyGroupand its Interfaces

lag.PortTermination siteName

-terminatedPortPointer

Interface rtr.NetworkInterface nodeId

MaxTransferUnit - actualMtu



DisplayedName - displayedName

InterfaceNumber - id

Description - interfaceClass


- nodeId

DisplayNameQualifier

- nodeName



Underlying -> IP - primaryIPv4Address

LayeredOver -> -

Interface -terminatedObjectPointer

-terminatedPortClassName

Interface sonetEquipment.Sts1Channel





sonetEquipment.Tu3Channel

siteName


VMware, Inc. 90






DisplayName - SiteName +cardSlotId +daughterCardSlotId +portId +displayedName






MaxSpeed - speed

Interface tdmequipment.DS0ChannelGroup



siteName


DisplayName - SiteName +cardSlotId +daughterCardSlotId +portId +displayedName






MaxSpeed - speed

Mapping of SAM-O service objects

Mapping of SAM-O service objects to VMware Smart Assurance objects lists the SAM-O service objectsthe Adapter retrieves and the methods used.


VMware, Inc. 91

Table 5-3. Mapping of SAM-O service objects to VMware Smart Assurance objects

VMware Smart Assuranceobject

VMware SmartAssurance attribute

SAM-O equipmentclass SAM-O property SAM-O filter

BGPProtocolEndpoint

BGPCluster

BGPSession

bgp.Peer siteName

PeerAdminStatus - administrativeState

IsRouteReflector - clusterId

PeerState - connectionState

LocalAddress - localAddress


Name - peerAddress

RemoteAs - peerAS

HostedBy -> Router/Switch

- siteId


+ peerAddress

Interface ies.L3AccessInterface

nodeName

serviceId



Description - description, -interfaceClass



ComposedOf ->Router/Switch

- nodeId




-primaryIPv4PrefixLength

LayeredOver ->Interface

-terminatedObjectPointer


IGMPNetwork igmp.IfGroup

GroupAddress - group


VMware, Inc. 92

Table 5-3. Mapping of SAM-O service objects to VMware Smart Assurance objects(continued)





LastReportingAddress

-srcAddrOfLastReport

IGMPInterface igmp.Interface nodeName


igmpIfJoins - groupCount

PollingIndex,InterfaceNumber

- interfaceId

DisplayName - nodeName


InterfaceStatus - operationalState

InterfaceQuerier - querier



MulticastService igmp.Site



- siteId


LdpProtocolEndpoint

LdpAdjacency

ldp.Interface -

AdjacencyHoldTime - keepAliveTimeout


LocalAddress - nodeId

DisplayName - siteId

+ portName

Index - interfaceId


-terminatedPortPointer

PeerAddress - peerAddress



LdpProtocolEndpoint

LdpAdjacency

ldp.TargetedPeer

AdjacencyHoldTime - keepAliveTimeout


VMware, Inc. 93






LocalAddress - siteId

Index - interfaceId

PeerAddress - peerAddress



MPLSService mpls.Interface

HostedBy ->Router/Switch

- nodeId

name - nodeName



LSP mpls.LspPath

mpls.DynamicPath

svt.Tunnel

fromNodeName

Source - fromNodeId

DisplayName - fromNodeName +toNodeName + lspId

Name - lspName

Description - objectFullName


LSPId mpls.LspPath

svt.Tunnel

OSPFArea

OSPFAreaConfiguration

ospf.AreaSite


AreaID - areaId

AreaType - importAsExtern

PropagateSummaries - areaSummary


+ areaId

OSPFInterface ospf.Interface nodeName



+ nodeName


VMware, Inc. 94





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 -



VMware, Inc. 95






+ 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

MulticastSource

PIMSourceG

PIMStarG

pim.Group

GroupAddress - groupAddress


UpstreamNeighborAddress

- rpfNbrAddress


VMware, Inc. 96





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


VMware, Inc. 97





-monitoredObjectPointer

- routesInVrf

- timeCaptured

AutonomousSystem

BGPServiceConfederation

rtr.VirtualRouter bgpEnabled

AS -autonomousSystemNumber

DisplayName -confederationAutonomousSystemNumber

+ siteName


service.SpokeConnector

firstSvcPointer

secondSvcPointer

-compositeSvcPointer

- firstSiteId

- firstSvcPointer

- firstTunnelPointer

- secondSiteId

- secondSvcPointer

-secondTunnelPointer

ForwarderEndpoint. svt.MeshSdpBinding

svt.SdpBinding

svt.SpokeSdpBinding

fromNodeName

serviceId

serviceType

TunnelType - circuitTransport

HostedBy -> Switch/Router

- fromNodeId


Status - operationalState


VMware, Inc. 98





DisplayName - pathId

+ serviceId

+ vcId

+ toNodeId

+ fromNodeName

TunnelName - pathname

- returnCircuitPointer

PeerAddress - toNodeId

VC_ID - vcId

Create relationship betweenVRF and LSP

PIMInterface

svt.TransportConnection

fromNodeId

tunnelId

- fromNodeName

- resourceId

- resourcePointer

- toNodeId

- toNodeName

NetworkConnection

(for GRE Tunnel)

svt.Tunnel underlyingTransport

BuildConnectedSystemsand ConnectedToRelationships

- toCtp

BuildConnectedSystemsand ConnectedToRelationships

- 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


VMware, Inc. 99





Interface vll.L2AccessInterface





nodeName



Creates relationshipbased on thisparameter



- nodeId








Forwarder vll.Site

apipe.Site

epipe.Site

fpipe.Site

ipipe.Site

siteId

VPNName - serviceId



- siteId

- operationalState



VMware, Inc. 100





VPN

(VPNs will be created byMPLS postprocessing)

vll.Vll

apipe.Apipe

epipe.Epipe

fpipe.Fpipe

ipipe.Ipipe

Interface vpls.L2AccessInterface

outerEncapValue

serviceType

nodeName

terminatedPortClassName



- nodeId

DisplayName - nodeName

+ displayedName





Creates relationshipbased on thisparameter


Forwarder vpls.Site

VPNName - serviceId



- siteId

- operationalState


VPN

(VPNs will be created byMPLS postprocessing)

vpls.Vpls

Interface vprn.L3AccessInterface

nodeName





VMware, Inc. 101






Description - interfaceClass

-l3InterfaceAdministrativeState

LayeredOver ->Router/Switch

- nodeId




- primaryIPv4Length

- serviceId



Create relationshipbased on thisparameter


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


VMware, Inc. 102





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


VMware, Inc. 103





ISISService Isis.Site

AdminStatus administrativeState

DisplayName siteName

Name objectFullName

ServiceType levelCapability

SystemID isisSystemId

HostedBy->Router


VMware, Inc. 104

Mapping of SAM-O Objects andSmarts Notifications 6The Adapter for Alcatel-Lucent 5620 SAM EMSuses the VMware Smart Assurancepatented CodebookCorrelation Technology to do root-cause analysis. This analysis is based on many factors in the managednetwork, 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 acomponent, the Adapter stores this information in a repository object.


n Element to notification mapping

Element to notification mapping

Mapping of Alcatel-Lucent elements to notifications describes how the administrativeState oroperationalState information may be mapped to the notifications that are displayed in the Global Console,based on this and other considerations.

Alcatel-Lucent VMware Smart Assurance

Class state name and value Status attribute and value Class

VMware, Inc. 105

equipment.BaseCard


administrativeState:

- 2 (inService)

equipmentState:

- 5 (equipmentMissing)

olcState (EMS >= 17.9)

- 1 (maintenance)

- 2 (inService)

EMS >= 17.9:

- olcState inService, admininService, equip not missing

ALL OTHERS

EMS < 17.9:

- admin inService, equip notmissing

ALL 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 operationalStateand administrativeState arethe same as Base/Daughtercards

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)


VMware, Inc. 106

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, operunKnown

- admin inService, operprovisioned

- admin inService, operinService

Status:

- UNKNOWN

- UNKNOWN

- OK

PowerSupply

temperatureStatus:


- 3 (deviceStateOk)


Status:

- UNKNOWN

- OK

- CRITICAL

TemperatureSensor

acVoltageStatus/dcVoltageStatus:


- 3 (deviceStateOk)


Status:

- UNKNOWN

- OK

- CRITICAL

VoltageSensor




Refer toequipment.PhysicalPort

Interface

(Channel)


sonetequipment.Tu3Channel

sonetequipment.TributaryChannel




Refer toequipment.PhysicalPort

Interface

(Channel)


VMware, Inc. 107






cpipe.L2AccessInterface


mvpls.L2AccessInterface




- 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 SAMEMS does not track IPs asobjects with administrative oroperational states.

The Adapter sets IPStatus inparallel with the UnderlyingInterface operationalState.IPs do not haveadministrativeStatus inVMware Smart Assurancesoftware.

n If an Interface is DOWN,IPStatus is set toTIMEDOUT

n Otherwise, IPStatus is setto 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

AdminStatus:

- UP

- DOWN

- UNKNOWN

OperStatus:

- UP

- DOWN

- DOWN

- UNKNOWN

NetworkAdapterRedundancyGroup


VMware, Inc. 108

vpls.Site

mvpls.Site

vll.Site

apipe.Site

cpipe.site

epipe.Site

fpipe.Site

ipipe.Site


- 1 (serviceUp)

- 2 (serviceDown)

ALL OTHERS

operationalState:

- 1 (serviceUp)

- 2 (serviceDown)

ALL OTHERS

AdminStatus:

- UP

- DOWN

- UNKNOWN

OperStatus:

- UP

- DOWN

- UNKNOWN

Forwarder

svt.SdpBinding

svt.SpokeSdpBinding

svt.MeshSdpBinding


- 1 (circuitUp)

- 2 (circuitDown)

ALL OTHERS

operationalState:

- 1 (circuitUp)

- 5 (circuitDown)

ALL OTHERS

AdminStatus:

- UP

- DOWN

- UNKNOWN

OperStatus:

- UP

- DOWN

- UNKNOWN

ForwarderEndpoint

vprn.site administrativeState:

- 1 (serviceUp)

- 2 (serviceDown)

ALL OTHERS

operationalState:

- 1 (serviceUp)

- 2 (serviceDown)

ALL OTHERS

AdminStatus:

- UP

- DOWN

- UNKNOWN

OperStatus:

- UP

- DOWN

- UNKNOWN

VRF

ldp.Interface

ldp.TargetedPeer


- 2 (tmnxInService)

- 3 (tmnxOutOfService)

ALL OTHERS

operationalState:

- 2 (tmnxInService)


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


VMware, Inc. 109

ospf.Site administrativeState:

- 0 (ospfUnknown)

- 1 (ospfUp)

- 2 (ospfDown)

AdminStatus:

- UNKNOWN

- ENABLE

- DISABLE

OSPFService

ospf.Interface

ospf.VirtualLink


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

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


VMware, Inc. 110

igmp.Interface administrativeState:

- 2 (tmnxInService)


operationalState:

- 2 (tmnxInService)


- Admin OutOfService

- Admin InService, operInService

- Admin InService, operOutOfService

ALL 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


VMware, Inc. 111

Notification Log Entries 7Alarms and events received from the Alcatel-Lucent 5620 SAM EMS are processed by various VMwareSmart Assurance Domain Managers ( MPLS Manager, Multicast Manager, IP Availability Manager,Network Protocol Manager for BGP, Network Protocol Manager for OSPF, Network Protocol Manager forIS-IS, and the Adapter Platform). Root-cause and impact analysis and diagnoses created by theseDomain Managers are provided to the operator through the Notification Log of the Global Console, acomponent of the VMware Smart Assurance Service Assurance Manager.


n Notification Log entries

Notification Log entries

The Notification Log includes two general types of entries: event notifications from the Domain Managersand alarm (problem) notifications forwarded from the Alcatel-Lucent 5620 SAM EMS. Global Consolenotifications describes some of the VMware Smart Assurance notification entries generated by theDomain Managers, their meanings, and possible indicated actions. This table is organized by Elementand Notification.

Table 7-1. Global Console notifications

Element Notification

Event,problem, orimpact 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 twoBGPProtocolEndpoints. If neither of the endpoints areadministratively down and at least one of them does not havePeerState = ESTABLISHED, then the BGPSession is consideredto be Disconnected.

An endpoint's PeerState is set from the Alcatel-Lucent 5620 SAMEMS's report of the connectionState of the endpoint (it shouldshow as ESTABLISHED in 5620 SAM). This leads directly to theBGPSession Down problem.

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

VMware, Inc. 112

Table 7-1. Global Console notifications (continued)



Card Down Problem Determined when the operational state of a card is CRITICAL(that is, down). The operational state of a card in VMware SmartAssurance is taken from the 5620 SAM’s report of operationalstate for it, which can include UNKNOWN, OK, and CRITICAL.

Note that 5620 SAM reports cards as down (CRITICAL) if thecard slot is provisioned but no card is present. Additionally, aBase card being Down will consume DaughterCard Downdiagnoses. DaughterCard Down diagnoses will consume physicalport Interfaces being Down.

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

IGMPInterface Unreachable Problem Results when the InterfaceStatus of the IGMPInterface isNOTINSERVICE or NOTREADY. Such InterfaceStatus valuesoccur when the 5620 SAM reports that the operational state oradministrative state of the IGMPInterface is Down.

In the case of IGMPInterfaces that are based on VPLS-modeMulticast configurations, these InterfaceStatuses are based onthe 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 Interfacehas an operational state of DOWN and an administrative state ofUP. These are values reported directly by 5620 SAM and insertedby the adapter into IP AM.

For Network Interfaces, if they are not Network Connected toother Network Interfaces, the same conditions (Oper Down,Admin Up) will conclude they are Down. The presence of aNetwork Connection will cause a different diagnosis to beconcluded.

Note that an Interface Down does not by itself impact objects thatuse the Interface. For example, OSPF Services will be Impactedif the OSPFInterfaces are Down, not the network or physicalinterfaces. Presumably if either of the latter were truly Down, theOSPFInterface would also be reported Down by the 5620 SAM.

ISISAdjacency Down Problem Results from ISISAdjacency NeighborStateAlarm event

If the neighbor ISISInterface on both side of ISISAdjacency arePOINT_TO_POINT type, and at least one side of ISISInterface isdown, the NPM IS-IS manager will send NeighborStateAlarmevent to the Notification log.


VMware, Inc. 113




LSP Impacted Impact LSP impacts may have reported Caused Bys such as RouterDown. In the 5620 SAM environment there are scenarios wherethese Impacts can be notified without Caused By being present.This will happen when the 5620 SAM reports an LSP'soperational state to be Down.

When this happens, the LSP's IsDownInRemote attribute is set toTrue. If the user navigates to the LSP in question then it will beIsDownInRemote.

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

PIMInterface PIMInterfaceUnreachable

Problem Results when the InterfaceStatus of the PIMInterface isNOTINSERVICE or NOTREADY. Such InterfaceStatus valuesoccur when the 5620 SAM reports the operational state oradministrative state of the PIMInterface is Down.

In the case of PIMInterfaces which are based on VPLS-modeMulticast configurations, these InterfaceStatuses are based onthe states of the underlying Interfaces.

Note that even when the PIMInterface is deemed unreachable,specific multicast groups are not shown as impacted.

Router Down Problem A Router Down problem is diagnosed when a router isunresponsive and there is no better explanation. If an Interfaceoutage or SNMPAgent outage might explain the router's beingunresponsive, those are concluded.

Router Down is a precondition for a number of impacts in variousVMware Smart Assurance servers, particularly impacts in theMulticast domain.

The diagnosis of Router Down does not eliminate the InterfaceDown notifications.

Unresponsive Event An Unresponsive event is triggered when a Router's IP Statusesand SnmpManager are all set to Unresponsive. This happenswhen 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 asRouter Down. In the 5620 SAM environment, there are scenarioswhere these Impacts can notified without Caused By beingpresent. This will happen when 5620 SAM reports an LSP'soperational state to be Down. When this happens, the LSP'sIsDownInRemote attribute is set to True. However, the usercannot see this relationship from the information in theNotification Log.

To find the specific LSP causing the impact, you must navigatethrough the VPN's VRFs; for each VRF, examine the LSPs it isLayeredOver to see which one of them will be IsDownInRemote.


VMware, Inc. 114




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 thatit is Layered Over are Down.

Impacted Impact VRF impacts may have reported Caused By diagnoses such asRouter Down. In the 5620 SAM environment there are scenarioswhere these Impacts can notified without Caused By beingpresent. This will happen when 5620 SAM reports an LSP'soperational state to be Down. When this happens, the LSP'sIsDownInRemote attribute is set to True. However, the usercannot see this relationship from the information in theNotification Log.

The solution to this is navigating to the VRF in question and thenexamining the LSPs it is LayeredOver; one of them will beIsDownInRemote.

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

WarningThresholdCrossed

Event You can set values in the MPLS Manager for a warning thresholdand a max value, as described in the VMware Smart AssuranceMPLS Management Suite User Guide . These events aretriggered when a VRF's NumberOfRoutes reaches theserespective values. As with the NoRoutes event, theNumberOfRoutes is set by the Adapter based on information keptin the 5620 SAM. The 5620 SAM will only track this informationfor VRFs that are configured to have Route Distinguishers.

MaxRoutesReached Event


VMware, Inc. 115

Logs 8This appendix provides an overview of the VMware Smart Assurance Adapter for Alcatel-Lucent 5620SAM EMSlog functionality for startup, discovery, and JMS message processing.


n Adapter log file

n Startup sequence

n Discovery Log messages

n Event messages

n Alarm messages

n Queue Log messages

n Warning messages

Adapter log file

The 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 verbositydefault 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 messagesmay change every code release.

Startup sequence

This section describes logging for the startup sequence, including the following:

n Loading mappings

n Starting up the server

n Connecting to Domain Managers

n Establishing the JMS connection

Loading mappings

VMware, Inc. 116

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

[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 Framework

ASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: Initializing JVM interface...


ASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: JVM Interface initialization complete.


ASL_MSG-*-ASLP-alcatel-sam/jvm-init.asl: JVM has been created.


ICF_MSG-*-ICF_LICENSEDFEATURE-Enabling the following licensed feature(s):

ASAM Adapter

[December 14, 2009 5:40:02 PM EST +468ms] t@3324

ICF_MSG-*-ICF_RECONFIGURESTART-PolicyManager: reconfigure started


ICF_MSG-*-ICF_RECONFIGUREFINISH-PolicyManager: reconfigure finished

[December 14, 2009 5:40:03 PM EST +359ms] t@4016 dmboot

HTTP-W-FPO-Listening for HTTP requests on IPv4 port 63680


RSRV-N-DMSTARTED-Domain Manager ASAM started on qa-vmw2k8b:63680


ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] SmAdapterSettings ready.


RSRM-*-RSRM_SUITE_VERS-Suite version: ALCATEL_SAM_SUITE: V3.2.0.0/64(94533), 14-Dec-2009 09:11:37

Copyright 1995-2009, vmware Corporation - Build 31

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

Connecting to Domain Managers


VMware, Inc. 117

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

[December 16, 2009 11:53:14 AM EST +532ms] t@69

ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-AM-PM]

via broker [fish:3680]


ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-OI] via

broker [fish:3680]


ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-MPLS-

TOPOLOGY] via broker [fish:3680]


ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-BGP] via

broker [fish:3680]


ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-OSPF]



ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-MCAST]



ASAM_MESSAGE-*-INFO-.[Adapter Construction Thread] Attached to InCharge repository [INCHARGE-ISIS]


Establishing the JMS connection

The following shows an example startup sequence for a JMS connection, including the IP address of theactive JMS server and the EMS version.

ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.


ASAM_MESSAGE-*-INFO-.[Connector] Completed createTopicSession with AUTO_ACKNOWLEDGE


ASAM_MESSAGE-*-WARNING-.[MessageToEventConverter] StateChangeEvent status:systemInfo

PrimaryIP:10.9.252.54


ASAM_MESSAGE-*-WARNING-.[MessageToEventConverter] JMS active server is 10.9.252.54


ASAM_MESSAGE-*-INFO-.[Connector] 5620Sam EMS version detected: 7.0.R3.0

Discovery Log messages

The Adapter logs discovery status messages during a full discovery. These log messages can be used todetermine discovery progress. For example, you can use a grep command to monitor discovery times, asfollows:

grep “Discovery completed” IC-ASAM.log

Discovery log examples


VMware, Inc. 118

The following example shows the sequence of Discovery Log messages, including step completion andwarning messages.


ASAM_MESSAGE-*-INFO-.[SmWorker] Full Discovery starting. Available memory:29514448


ASAM_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}


ASAM_MESSAGE-*-INFO-.[SmWorker] Card Discovery completed - Discovered #Cards:56


ASAM_MESSAGE-*-INFO-.[SmWorker] Discovered #Interfaces:500 #Macs:239


ASAM_MESSAGE-*-INFO-.[SmWorker] Physical Port Discovery completed - Discovered #Interfaces:711

#Macs:344


ASAM_MESSAGE-*-INFO-.[SmWorker] ProcessorCard Discovery completed - 15 equipment.ProcessorCard

elements processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] FlashMemory Discovery completed - 22 equipment.FlashMemory elements

processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] Controller Processor Discovery completed - 15

equipment.ControlProcessor elements processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] Switch Processor Discovery completed - 15

equipment.SwitchFabricProcessor elements processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] PowerTray Discovery completed - equipment.PowerSupplyTray discovered:

19


ASAM_MESSAGE-*-INFO-.[SmWorker] FanTray Discovery completed - Discovered #FanTrays:26


ASAM_MESSAGE-*-INFO-.[SmWorker] Channel Discovery completed - Discovered 143 sonet interfaces

DS3Channels:3 DS1 Channels:2 DS0ChannelGroups:1


ASAM_MESSAGE-*-INFO-.[SmWorker] Link Aggregation Group Discovery completed - 5 lag.Interface elements

processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] Physical Link Discovery completed - Discovered #PhysicalLinks:3


ASAM_MESSAGE-*-INFO-.[SmWorker] Network Interface Discovery completed - Created and related 68

Network Interfaces

0 secondary IPs processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] VRPN Discovery completed - Discovery set #vrfs:318


ASAM_MESSAGE-*-INFO-.[SmWorker] VPRN Service Interface Discovery completed - 310 VPRN Service

Interfaces



VMware, Inc. 119

ASAM_MESSAGE-*-INFO-.[SmWorker] IES Service Interface Discovery completed - 9 IES Service Interfaces


ASAM_MESSAGE-*-INFO-.[SmWorker] VLL Service Interface Discovery completed - 3 VLL Service Interfaces


ASAM_MESSAGE-*-INFO-.[SmWorker] Non-primary IP Discovery completed - 0 secondary IPs processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] VPLS Service Interface Discovery completed - 21 VPLS Service

Interfaces


ASAM_MESSAGE-*-INFO-.[SmWorker] Fib discovery disabled - skipping discovery step


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] Confederation Discovery completed - 4 rtr.VirtualRouter elements

processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] BGPSession Discovery completed - 6 bgp.Peer elements processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFArea Discovery completed - 16 ospf.AreaSite elements

processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFService Discovery completed - 9 ospf.Site elements processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFInterface Discovery completed - 23 ospf.Interface elements

processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] OSPFNeighbor Discovery completed - 17 ospf.Neighbor elements

processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] VirtualLink Discovery completed - 2 ospf.VirtualLink elements

processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] VirtualNeighbor Discovery completed - 2 ospf.VirtualNeighbor

elements processed.


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISService Discovery completed - Created 8 ISIS Services


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISArea Discovery completed - Created 4 ISIS Areas


ASAM_MESSAGE-*-INFO-.[SmWorker] Tunnel Discovery completed.Discovered 45 tunnels


ASAM_MESSAGE-*-INFO-.[SmWorker] MPLS Interface Discovery completed.


ASAM_MESSAGE-*-INFO-.[SmWorker] LSP Discovery completed - Collected info on 34 LSPs


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISInterface Discovery completed - Created 15 ISIS Interfaces


ASAM_MESSAGE-*-INFO-.[NPMDiscovery] ISISNeighborEndpoint Discovery completed - Created 8 ISIS

NeighborEndpoints


ASAM_MESSAGE-*-INFO-.[SmWorker] LSPPath Discovery completed - Collected info on 37 LSPPaths


ASAM_MESSAGE-*-INFO-.[SmWorker] VRF to Tunnel Mapping Discovery completed - #Tunnel IDs found:0


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] MulticastService Discovery completed - 4 pim.Site elements

processed.



VMware, Inc. 120

ASAM_MESSAGE-*-INFO-.[SmWorker] LDP TargetedPeer Discovery completed.Created 22 TargetedPeers


ASAM_MESSAGE-*-INFO-.[SmWorker] LDP Interface Discovery completed.Created 22 Ldp Interfaces


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] MulticastService Discovery completed - 4 igmp.Site elements

processed.


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] PIMInterface Discovery completed - 4 pim.Interface elements

processed.


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] IGMPInterface Discovery completed - 3 igmp.Interface elements

processed.


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] IGMPNetwork Discovery completed - 3 igmp.IfGroup elements

processed.


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] pim.Neighbor Discovery completed - 2 pim.Neighbor elements

processed.


ASAM_MESSAGE-*-INFO-.[MCASTDiscovery] PIMSgEntry Discovery completed - 3 pim.Groups elements

processed.


ASAM_MESSAGE-*-INFO-.[SmWorker] VLL Site Discovery completed - Discovered 6 VLL Sites


ASAM_MESSAGE-*-INFO-.[SmWorker] VPLS Site Discovery completed - Discovered 27 VPLS Sites


ASAM_MESSAGE-*-INFO-.[SmWorker] ForwarderEndpoint Discovery completed. Created 5 VLL, 24 VPLS, 3 IES,

6 VPRN ForwarderEndpoints


ASAM_MESSAGE-*-INFO-.[SmWorker] ProvisionedHops Discovery completed - Collected info on 71

ProvisionedHops


ASAM_MESSAGE-*-INFO-.[SmWorker] Full Discovery completed at Wed Dec 16 11:55:35 EST 2009

Event messages

The Adapter logs JMS messages. The log file records the event type and EMS instance to which themessage refers.

There are four types of event message:

n State changes

n AttributeValueChange events

n ObjectCreation events

n ObjectDeletion events

Note The EMS instance name does not map directly to an VMware Smart Assurance object name.Chapter 4 Mapping of SAM-O Elements to Smarts Objects provides details about mapping.


VMware, Inc. 121

Event log examples

The following are examples of event log messages:


ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] Event Processing

com.smarts.asac.events.AttributeValueChangeEvent for mpls.DynamicLsp::lsp:from-10.1.1.95-id-4


ASAM_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


ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] Event Processing com.smarts.asac.events.ObjectDeletionEvent

for vlan.Vlan::svc-mgr:service-379

Alarm messages

The Adapter logs alarms in a similar format to events. The key differences between events and alarmsare:

n Events typically create/delete/change topology state

n Alarms only push/clear notifications in the Adapter Platform; they are similar to those seen by theEMS 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

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


ASAM_MESSAGE-*-INFO-.[SmAlarmProcessor] Discarding

inactive:faultManager:[email protected]@router-1@[email protected]@interface-6|alarm-39-11-36-

packetSourceIpAddress=172.18.7.2

Queue Log messages

The EMS and the Adapter each use queues. The Adapter reads the JMS messages in a queue on theEMS and places the messages in the Adapter’s internal XML, alarm, and event queues.


VMware, Inc. 122

The XML queue stores raw, unparsed messages from the EMS. The Adapter does not specify themessage 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 usethe 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 messagebackup. 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.


ASAM_MESSAGE-*-INFO-.[SmAlarmProcessor] EventDelta Timestamp:1260982545526 Thread:SmAlarmProcessor

QueueName:Alarm QueueSize:50


104110288:ASAM_MESSAGE-*-INFO-.[SmTiEventProcessor] EventDelta Timestamp:1260893003859

Thread:SmTiEventProcessor QueueName:Event QueueSize:50

Warning messages

Most entries in the ASA.log are informational, providing a trail of events reported by the Alcatel-Lucent5620 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


ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:javax.jms.JMSSecurityException

SAM-O Access Violation

and/or


ASAM_MESSAGE-*-SEVERE-.[SmTiEventProcessor] Adapter cannot connect to the 5620Sam EMS

server

<SOAP:Envelope

xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Header><

header

xmlns="xmlapi_1.0"><requestID>smarts@8598</requestID><requestTime>Aug

15, 2007 11:39:21 PM</requestTime><responseTime>Aug 15, 2007 11:39:22

PM</responseTime></header></SOAP:Header><SOAP:Fault><faultcode>SOAP:C

lient</faultcode><faultstring> security] Users require OSS Management

privileges to use


VMware, Inc. 123

SAM-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 thelines 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.


ASAM_MESSAGE-*-INFO-.[MessageToEventConverter] Parse: endElement local:

qualified:eventName chars:AttributeValueChange



qualified:MTOSI_osTime chars:1196887261476



qualified:ALA_clientId chars:



qualified:MTOSI_objectType chars:netw.NetworkElement



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:


ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.


ASAM_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


VMware, Inc. 124

Troubleshooting 9You 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.


n Use ASL scripts for troubleshooting

Use ASL scripts for troubleshooting

The Adapter provides ASL scripts for troubleshooting the following:

n General functioning

n EMS functioning

n Managing devices not in effect

n Discovery

General functioning

The following ASL scripts are available to help you troubleshoot general Adapter functioning:

n logLevel.asl

n reloadOI.asl

logLevel.asl

This script sets the logging levels, as shown in Log warning level settings.

Table 9-1. Log warning level settings

Warning level Description

1 SEVERE

2 WARNING

3 INFO

4 CONFIG

5 FINE

6 FINER

7 FINEST (default)

VMware, Inc. 125

To run this script:


sm_adapter –s <adapter_name> -Dlvl="2" alcatel-sam/logLevel.asl

reloadOI.asl

This script reloads the ASA-Alarm.conf and AggregateAlarms.conf fileswithout the need to restart thesystem. To run this script:


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

EMS troubleshooting

Query the Alcatel-Lucent 5620 SAM EMS database for object data, in the event that the information is notdirectly available from the EMS user interface. To do this, you can run the following ASL scripts:

n readRecords.asl—Lists all records for a specified object; for example, all routers

n soap.asl—Submits an xml query and returns the responses to the standard output (stdout) or a file

showStatus.asl

The following ASL script prints JMS message rate status to the Adapter log file. It provides the followinginformation:

n JMS message receiving rate. This is the rate at which the Adapter receives JMS messages from theEMS.

n 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 seconds

JMS message received:63 Avg msg/sec:0.09

TextMessage queue:0 used:39 discarded:24 discarded pct:38% last discarded:

Alarm queue:0 is locked? false Alarms processed:7 Avg alarm/sec:0.01

Event queue:0 is locked? false Events processed:32 Avg Topo event/sec:0.04


VMware, Inc. 126

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:

t/sm_adapter -s <adapter_name> -Dpkg=<SAM-O class name> alcatel-sam/readRecords.asls

For example, to list all of the routers and their properties:

t/sm_adapter -s <adapter_name> -Dpkg=netw.NetworkElement alcatel-sam/readRecords.asls

The results will be located in /var/tmp/netw.NetworkElement.xml.

soap.asl

This script supports single or multiple queries in a single call.

To run this script:


t

sm_adapter -s<

adapter_name>

--file=<query file and pathname>alcatel-sam/soap.asls

The following examples illustrate single and multiple queries.

Example of a single query

sm_adapter -s <a

dapter_name>

--file=find.xml alcatel-sam/soap.asl

The following is a sample find.xmlfile for a single query (network element).

In this example, the file limits the attribute list to the following, and skips any child objects:

n objectFullName


VMware, Inc. 127

n 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:

Example of a multiple queries

The following is a sample find.xmlfile for multiple queries (network element and equipment card):

<find xmlns="xmlapi_1.0"><fullClassName>netw.NetworkElement</


attribute><children/></resultFilter></find><find

xmlns="xmlapi_1.0"><fullClassName>equipment.Card</


attribute><children/></resultFilter></find>

verboseXml.asl

Change 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)


VMware, Inc. 128


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 info

INFO: [MessageToEventConverter] Parse: endElement local: qualified:MTOSI_osTime chars:1196887261476


INFO: [MessageToEventConverter] Parse: endElement local: qualified:ALA_clientId chars:


INFO: [MessageToEventConverter] Parse: endElement local: qualified:MTOSI_objectType

chars:netw.NetworkElement


INFO: [MessageToEventConverter] Parse: endElement local: qualified:MTOSI_NTType

chars:NT_ATTRIBUTE_VALUE_CHANGE


Turn off verbosity (get less detail)


sm_adapter -s <adapter_name> -Dval=false alcatel-sam/verboseXml.asl

restartJMSConnector.asl

Reconnect 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 connector


INFO: [Connector] Attempting (re)connection to JMS.

Dec 3, 2007 9:22:58 PM com.smarts.asac.SmAsAdapterLog fine

FINE: [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.

n insertFilters.asl


VMware, Inc. 129

n deleteFilters.asl

n clearFilters.asl

n showFilters.asl

The filters are contained in the file, “GA_StringDictionary::AdapterFilters”, which containsDisplayName filters for UnitaryComputerSystems. Overview of device filtering provides moreinformation.

insertFilters.asl

Insert filters:


tsm_adapter -s <adapter_name> -f

<path/fileName>

alcatel-sam/insertFilters.asls

deleteFilters.asl

Delete filters:


tsm_adapter -s <adapter_name> -f

<path/fileName>

alcatel-sam/deleteFilters.asls

clearFilters.asl

Remove all filters:


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

showFilters.asl

Show the filter DisplayNames:


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

Discovery


VMware, Inc. 130

Use the following ASL scripts to initiate the following types of discovery:

n discover.asl

n routerDiscover.asl

n servicediscover.asl

n alarmRediscover.asl

discover.asl

Manually initiate full discovery:


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

routerDiscover.asl

Manually initiate discovery of a particular Alcatel-Lucent device:


tsm_adapter –s <adapter_name> -DIP=10.1.1.77 alcatel-sam/routerDiscover.asls

servicediscover.asl

Manually initiate discovery of a particular type of service:


tsm_adapter –s <adapter_name> -DQUALIFIER=<SERVICE TYPE> alcatel-sam/serviceDiscover.asls

Where valid <SERVICE TYPEs> are the following: AM, MPLS, NPM, MCAST.

alarmRediscover.asl

Manually initiate discovery of current alarms from the EMS:


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


VMware, Inc. 131

Understanding the sm_editUtility 10As part of the VMware Smart Assurancedeployment and configuration process, you need to modifycertain files. User modifiable files include configuration files, rule set files, templates, and seed files thatcontain encrypted passwords. Original versions of these files are installed into appropriate subdirectoriesunder the BASEDIR/smarts/ directory.

The original versions of files should not be altered. If a file must be modified, a new version should becreated and then stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories.

When VMware Smart Assurancesoftware requires one of these files, it is designed to first search for amodified file in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is notfound in the local area, VMware Smart Assurancesoftware then searches corresponding BASEDIR/smarts directories for the original version of the file.

To ease file editing and storage, VMware, Inc.provides the sm_edit utility with every VMware SmartAssuranceproduct suite. When invoked, sm_edit opens the specified file in a text editor. This utilityensures that modified files are always saved to the appropriate local area and that non-local copies of allfiles 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 withheader information set for encryption, sm_edit encrypts certain fields in the file. In addition, sm_editpreserves the file permissions of modified files, which helps ensure that important configuration files arenot altered by unauthorized users.

In UNIX, you can configure sm_edit to use your favorite text editor when you invoke sm_edit.


n Example

Example

Modify ics.conf

To use sm_edit from the command line, specify the file name and include the subdirectory under /localwhere the file resides. For example, to edit the ics.conf, enter:

# BASEDIR/smarts/bin> sm_edit conf/ics/ics.conf

VMware, Inc. 132

In this example, sm_edit searches in the BASEDIR/smarts/local/conf/ics directory for the ics.conf file. If itfinds the ics.conf file, it opens the file in a text editor. If sm_edit does not find the ics.conf file in theBASEDIR/smarts/local/conf/ics directory, it creates a local copy of the ics.conf file and writes it to theBASEDIR/smarts/local/conf/ics directory.

The VMware Smart Assurance System Administration Guide provides additional information about thesm_edit utility, including how to configure the utility to use a specific editor.


VMware, Inc. 133

Getting help 11This chapter includes the following topics:

n Where to get help

Where to get help

VMware support, product, and licensing information can be obtained as follows:

Product information

For documentation, release notes, software updates, or information about VMware products, go toVMware Online Support at:

docs.vmware.com

support.vmware.com

Technical support

Go to VMware Online Support. You will see several options for contacting VMware Technical Support.Note that to open a service request, you must have a valid support agreement. Contact your VMwaresales representative for details about obtaining a valid support agreement or with questions about youraccount.

VMware, Inc. 134

http://support.emc.com

Documents

VMware Smart Assurance Adapter for GuideSince 5620 SAM EMS Release 7.0/R1, LLDP is supported in 7450s, 7750s, and 7710s. n Support for Alcatel-Lucent 7210 SAS-E, including the following: