EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version … · 2018. 12. 16. · Alcatel-Lucent...

1

EMC® Smarts®

Adapter for Alcatel-Lucent 5620 SAM EMSVersion 3.3

P/N 302-004-787REV 01

May 2018

RELEASE NOTES

These release notes contain supplemental information about this release of the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS. Topics include:

◆ Product description................................................................................................... 2◆ New features and changes ........................................................................................ 2◆ Fixed problems ......................................................................................................... 5◆ Environment and system requirements ................................................................... 13◆ Known problems and limitations............................................................................. 15◆ Technical notes....................................................................................................... 20◆ Documentation ....................................................................................................... 20◆ Software media, organization, and files .................................................................. 21◆ Installation ............................................................................................................. 22◆ Troubleshooting and getting help ........................................................................... 23

Release Notes

2 EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes

Product description

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

◆ IP Availability Manager

◆ MPLS Topology Manager

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

◆ Multicast Manager

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

New features and changesThe Adapter for Alcatel-Lucent 5620 SAM EMS provides the following new features:

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

New features in Foundation 9.5.1

This release of the Adapter for Alcatel-Lucent 5620 SAM EMS is based upon Foundation 9.5.1. Documentation explaining Foundation 9.5.1 features is listed in Table 6 on page 21. Here are highlights of changes related to foundation 9.5.1:

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

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

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

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

New features and changes

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes 3

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

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

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

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

The operations are:

◆ getPropDescription — retrieve the description of the MODEL property

◆ getEventDescription — retrieve the description of the MODEL event

◆ getOpDescription — retrieve the description of the MODEL event

◆ getClassDescription — retrieve the description of the MODEL class

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

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

--alarmInterval=secs

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

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

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


New features and changes

Changes in sm_server --versionThe operating system (OS) name that the product is running on and OS version identifier have been added to the output of the sm_server command. “Version numbers” on page 15 provides an example.

sm_server --version

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

◆ CORE_ManagedObject

◆ CORE_Collection

◆ CORE_MetaObject

◆ CORE_AbstractIndication

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

relationshipset MetaMemberOf, CORE_Collection, MetaConsistsOf

The reverse relationship in CORE_Collection has been modified accordingly.

relationshipset MetaConsistsOf, CORE_MetaObject, MetaMemberOf

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

New features in ASAM Patches

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

Fixed problems


Fixed problems Table 1 on page 5 lists software fixes for the Adapter.

Table 1 Fixes for the Adapter for Alcatel-Lucent 5620 SAM EMS (page 1 of 9)

CQ Synopsis of fix

Fixed in ASAM version

IS-8560SR 86155782

Receiving too many ASAM sourced alarms has been reported post discovery. The AlarmRetrievalOnFullDiscovery” flag is introduced to control whether the alarm retrieval (fm.AlarmObject) from 620Sam server will be initiated when full discovery is performed. The default value is TRUE, that indicates alarms retrieval will happen.

3.3

IS-9391 The ASAM adapter does not connect to standby EMS server during primary EMS server failover. With the enhanced exception handling, ASAM adapter keeps trying to connect to EMS until it comes up.

3.3

IS-9641 The Nokia EMS17.9 HSQ card support in ASAM is needed. The new card HSQ support has been added in the adapter.

3.3

IS-9670 The Annual ASAM certification for Nokia new 5620 EMS released version (NFM-P17.6) is needed. The Nokia NPM-P 17.6 support has been provided in the ASAM.

3.3

IS-9023SR 07842041

TSM repository not being saved and post processing not running after ASAM sync. Persistence manager save is called after full discovery in ASAM.

3.3

IS-9352SR 11111111

Unsupported EMS version error occurs in ASAM log file. Supported version list has been updated with EMS version no 14.

3.3

IS-7286SR 82087180

Excess soap requests from ASAM is observed on user system. This additional soap request was redundant and it was carried forward with legacy code base. The scope of its need has been carefully evaluated, and removed the additional calls while processing the state event change.

3.3

IS-6258 Extended support for Nokia 9966 SCGW device. Following new components will be added under this chassis:Shelf Manager CardAlarm CardBlade HardwareBono InterfaceEthernet interfaceMelbo Card (Femto.SCATCASwitchSlot)Health Components(PowerSupply & FanTray)

3.3

IS-5859 Discovery and monitoring support for ChassisType:sr_shelf_12Slote. NE with chassisType = “sr_shelf_12Slote” and the associated components will get discovered and monitored in ASAM.

3.3

IS-5632 ASAM Service is not processing alarms while discovery. Virtual router discovery is restricted to router specific discovery.

3.3


Fixed problems

IS-5874 False Alcatel Interface Alarms. The fix has been made where only when there is a State change triggered on interfaces, ASAM adapter will compute the OperStatus.

3.3

IS-6333 ASAM Adapter discover inconsistently. Fix has been added to delete device from ASAM along with other repositories during device deletion in EMS

3.3

CQ 615869 ASAM disconnects from EMS JMS when there are network outage, network disconnect etc. and ASAM never attempts to reconnect. ASAM now use Java Timer Task to keep trying to reconnect every 30 seconds till network connection restored and / no more network outage

3.3

CQ 654768 ASL print statement has the limitation of 10KB for the return output. Beyond 10 KB, data will be ignored. ACT_File mechanism has been introduced to capture output in a file rather than print statement. With ACT_File, there is no limitation on the size of output.

3.3

CQ 503789 The Adapter for Alcatel-Lucent 5620 SAM EMS is unable to discover Alcatel 7210 SAS-X switches. Certified the Alcatel 7210 SAS-X switch.

3.3

CQ 290909 The Global Console allows users to delete, discover, and unmanage the Alcatel-Lucent 5620 SAM EMS devices. The Global Console version 8.0 has been enhanced to disable the delete, discover, and unmanage operations for Alcatel-Lucent 5620 SAM EMS devices.

3.3

CQ 535964SR 37525190

The Adapter for Alcatel-Lucent 5620 SAM EMS incorrectly creates the relationship between the VLAN and the L2 Access Interface if the IP Availability Manager has the VLAN object with the same VLAN ID as the encapsulation value of an L2 Access Interface.The Adapter now uses additional information from the Alcatel-Lucent 5620 SAM EMS to determine that the L2 Access Interface is indeed part of the VLAN. Only those L2 Access Interfaces are related to the VLAN.

3.3

CQ 495134SR 36910386

The Adapter for Alcatel-Lucent 5620 SAM EMS does not discover physical links when configured to connect to Alcatel-Lucent 5620 SAM EMS 6.x.The Adapter now uses the netw.PhysicalLink SAM-O class to discover the physical links in the Alcatel-Lucent 5620 SAM EMS 6.x.

3.3

CQ 495102 SR 36772822

When the dmctl command is invoked from the ASAM installation, this error is displayed: dmctl: error while loading shared libraries: libedit.so.0: cannot open shared object file: No such file or directory

The patch installation program for the Adapter for Alcatel-Lucent 5620 SAM EMS 3.2.0.2 now creates the symbolic link to the shared libedit.so.0 library during the patch installation.

3.3


CQ Synopsis of fix


Fixed problems


CQ 502296 If an Alcatel-Lucent device has a large number of forwarders, the deletion operation of the forwarder takes a long time (10-30 seconds) to complete.This issue has been fixed in the model of the Adapter for Alcatel-Lucent 5620 SAM EMS. The forwarders are now part of HostsMPLSServices relationship. Since the forwarders are no longer part of the HostsServices relationship of a device, a monitoring tree no longer needs to be re-evaluated when a forwarder is deleted.The deletion of a forwarder occurs faster. This fix also requires a newer version of the MPLS VPN-Tagging Server.

3.3

CQ 502148 The MAC Address objects were not populated for the physical ports belonging to Alcatel-Lucent 6850 Omni switches. The Adapter for Alcatel-Lucent 5620 SAM EMS now uses the hwMacAddress attribute from the Alcatel-Lucent 5620 SAM EMS for the MAC Address for 6850 Omni Switch Physical ports.

3.3

CQ 424237 The IsDisabledInRemote attribute of the managed Access Interfaces in the MPLS Monitoring Server is grayed out. The Adapter for Alcatel-Lucent 5620 SAM EMS now sets the SuppressDisabledNotification attribute to false for the Access Interface in the IP Availability Manager.

3.3

CQ 424238 The Model attribute of the Alcatel-Lucent Switch/Router is set to “Alcatel” instead of “Alcatel-Lucent.” The Adapter for Alcatel-Lucent 5620 SAM EMS now sets the Model attribute to “Alcatel-Lucent” for Alcatel-Lucent devices.

3.3

CQ 502975 Need to provide an option to unmanage 7210 switch ports which are not used.A new configuration parameter UnmanageUnused7210Ports has been added to the emsConfig.import file:• If the parameter is set to TRUE, the Adapter for

Alcatel-Lucent 5620 SAM EMS unmanages all physical ports belonging to the 7210 Service Access Switch which are not underlying any other network or access interface.

• The default is FALSE.

3.3


CQ Synopsis of fix



Fixed problems

CQ 502967 Enhance the ASA-Connection-Lost alarm to display the Alcatel-Lucent 5620 SAM EMS Manager which has failed.The Adapter for Alcatel-Lucent 5620 SAM EMS includes the server IP address in the AlcatelConnectionLost event. The server IP address varies according to the scenarios:• In the failover setup during the initial connection, if the

Adapter is not able to connect to any of the servers, both primary and backup server IP addresses are listed in the event.

• After the Adapter is successfully connected to the primary or backup server, if the active server goes down, only the IP address of the disconnected server is listed in the event.

• If the AlcatelConnectionLost event is generated because of a keepAlive problem, the IP address of the server, to which the Adapter is connected, is listed in the event.

• If the TerminateClientMessage is received, the IP address of the server that sent the TerminateClientMessage is listed in the event.

3.3

CQ 502306,CQ 495664

The Adapter for Alcatel-Lucent 5620 SAM EMS does not populate the IP Performance Manager-related topology to the Topology Split Manager.The Adapter populates the IP Performance Manager-related topology like voltage sensor, temperature sensor, power supply and memory when the Adapter is configured to communicate with the Topology Split Manager.

3.3

CQ 425186 The Adapter for Alcatel-Lucent 5620 SAM EMS instantiates the VoltageSensor and TemperatureSensor objects in the topology for the unequipped PowerSupply Trays.The Adapter has been modified not to populate the voltage sensor and temperature sensor objects belonging to the unequipped power supply trays in Alcatel-Lucent devices.

3.3

CQ 495584SR 38329236

The Interface::InterfaceNumber attribute is not unique between PhysicalPorts and NetworkInterface.• For the physical ports, the Adapter for Alcatel-Lucent

5620 SAM EMS uses the equipment.PhysicalPort::portId to populate the InterfaceNumber.

• For the NetworkInterface, the Adapter uses the rtr.NetworkInterface::Id.

The issue has been fixed as follows:• For the physical ports and channels, the Adapter for

Alcatel-Lucent 5620 SAM EMS populates the Interface::DeviceID attribute but will not populate the Interface::InterfaceNumber attribute. The DeviceID attribute is set to the CLI Name of the physical ports and channels.

• For the NetworkInterface, the Adapter populates the Interface::InterfaceNumber attribute. The InterfaceNumber is set to the rtr.NetworkInterface::Id.

3.3


CQ Synopsis of fix


Fixed problems


CQ 422448 When the base card is set to Admin Down or removed, the BaseCard Down event is suppressed. However, daughter card and physical port Down events are still present and are not correlated to the base card. Also, instrumentation for the daughter card is removed.This issue is due to the fact that the Adapter for Alcatel-Lucent 5620 SAM EMS unmanages the base card when the base card is set to Admin Down or removed, while the daughter card and physical ports are still being managed. This issue has been fixed. The Adapter no longer unmanages the cards when the card is Admin Down or not equipped.The new behavior is that the Adapter only handles the OperationalState and no longer handles the Admin status on the card. As a result, when the card is Admin Down, the Card Down event is generated. Also when the card is removed, the Adapter no longer unmanages the card. The string [Removed] is appended to the DisplayName. Even in this case, the Card Down event is generated. Instrumentation for the daughter card is no longer removed.

3.3

CQ 422456 AuthKey did not get reset in the Network Protocol Manager for OSPF when the password was removed from the Alcatel-Lucent 5620 SAM EMS. As a result, the AuthKeyMismatch event is not cleared properly.The Adapter for Alcatel-Lucent 5620 SAM EMS has been modified to allow an empty string value for AuthKey. When the AuthKey value is removed from the Alcatel-Lucent 5620 SAM EMS, the old password is removed from the Network Protocol Manager for OSPF.

3.3

CQ 422502 When a processor card is removed, the display name (DisplayName) of the processor is not changed to indicate that it has been removed.The Adapter for Alcatel-Lucent 5620 SAM EMS now handles the compositeEquipmentState change events on processors. When a card is removed, the string [Removed] is appended to the DisplayName of the processor.

3.3

CQ 493944SR 33875978

Some ASCII printable characters are not authenticated correctly in serverConnect.conf. The ASCII characters are:?,*,[,],^,,|,(,).Since wildcard characters are allowed in the target, user, and password fields of serverConnect.conf and clientConnect.conf files, the special status of these characters have to be removed by using \\ (double backslash). A note is added to both these files explaining this.Note: During installation, the serverConnect.conf and clientConnect.conf files are flagged for merge.

3.3

CQ 494077SR 34305644

The Adapter for Alcatel-Lucent 5620 SAM EMS full discovery does not clean up Network Adapter Redundancy Groups (NARGs) that have been removed while the Adapter is disconnected from the Alcatel-Lucent 5620 SAM EMS.Added logic to clean up deleted NARGs and to update the NARG if individual members were deleted.

3.3


CQ Synopsis of fix



Fixed problems

CQ 494185SR 34523126

In a multi-vendor environment with Network Protocol Managers, a second ASAM discovery may cause the subsequent IP Availability Manager-to-NPM synchronization to remove objects in the following classes in the Network Protocol Managers: Router, Switch, and OSPFNeighborRelationship.The relationship between a device and the NPM TopologyCollection (that is, OSPF_TopologyCollection), which specifies what to synchronize from IP Availability Manager to NPM, is no longer removed during an ASAM rediscovery.

3.3

CQ 500772 Multi-link PPP and bundle interfaces are not discovered. Multi-link PPP and bundle interfaces are now supported in Adapter for Alcatel-Lucent 5620 SAM EMS 3.2.0.1. They are modeled as NetworkAdapterRedundancyGroup objects.

3.3

CQ 501071 Physical links from Alcatel-Lucent 5620 SAM EMS 6.1 are not discovered in EMC Ionix Adapter for Alcatel-Lucent 5620 SAM EMS 3.2.Different classes are now queried based on the Alcatel-Lucent 5620 SAM EMS version.• For Alcatel-Lucent 5620 SAM EMS 6.1 only, the

netw.PhysicalLink class is queried.• For Alcatel-Lucent 5620 SAM EMS 7.0 and above, both

netw.PhysicalLink and netw.DiscoveredPhysicalLink classes are queried.

3.3

CQ 501253 For Alcatel-Lucent 5620 SAM EMS 8.0, support is needed for 7450 mixed mode. In mixed mode, the Alcatel 7450 switches can support VPRN and MCAST services.The Adapter for Alcatel-Lucent 5620 SAM EMS has been enhanced to populate these services belonging to switches which were earlier only relevant to routers.

3.3

CQ 501273 Due to the changes in Alcatel-Lucent 5620 SAM EMS 8.0, HTTP requests, which are not immediately accepted for processing, are not queued any more. These requests are rejected right away. Without any enhancement, the Adapter for Alcatel-Lucent 5620 SAM EMS does not retry the rejected requests. This may result in aborted discovery and event processing.The Adapter for Alcatel-Lucent 5620 SAM EMS has been enhanced to handle this exception and to retry the rejected HTTP requests.

3.3

CQ 501275 Support is needed for the Alcatel-Lucent 5620 SAM EMS 8.0 feature, “LSP make before break.” This is support for MPLS Path updates on Dynamic LSPs. The Adapter for Alcatel-Lucent 5620 SAM EMS has been enhanced to handle the events related to MPLS Path updates on Dynamic LSPs.

3.3


CQ Synopsis of fix


Fixed problems


CQ 501590 When a processor card went down, both the card and its redundant counterpart in the CardRedundancyGroup did not have the proper updated StandbyStatus.The StandbyStatus value corresponds to the value of the Alcatel-Lucent redundantStatus of the associated ControlProcessor. Code has been added to handle redundantStatus changes. As a result, the StandbyStatus of both the processor card and redundant card update properly.

3.3

CQ 501629 The Adapter for Alcatel-Lucent 5620 SAM EMS full discovery does not clean up label switched paths (LSPs) that have been removed from the MPLS Manager while the Adapter is disconnected from the Alcatel-Lucent 5620 SAM EMS.Added logic to clean up the deleted LSPs during full discovery.

3.3

CQ 501785 The OperStatus of label switched paths (LSPs) are grayed out for some of the LSPs in the MPLS Monitoring Server.The LSP OperStatus is a computed attribute in the Adapter for Alcatel-Lucent 5620 SAM EMS. The expression to compute this attribute was incorrect. The expression has been modified to correctly compute the LSP OperStatus.

3.3

CQ 502065 The L2 Access Interfaces configured on an IPIPE service are not discovered during a full discovery.The Alcatel-Lucent 5620 SAM-O model treats the L2 Access Interfaces on an IPIPE service differently than other VLL L2 Access Interfaces. The L2 Access Interface on IPIPE has its own subclass named ipipe.L2AccessInterface. All other VLL L2 Access Interfaces are abstracted from the same class, vll.L2AccessInterface. This issue has been fixed. The Adapter for Alcatel-Lucent 5620 SAM EMS now creates an object for the ipipe.L2AccessInterface subclass and discovers L2 Access Interfaces on IPIPE services.

3.3

CQ 502076,CQ 494519SR 35141554

The Adapter for Alcatel-Lucent 5620 SAM EMS event and alarm processing freezes. Also, the event and alarm queues keep growing continuously.The issue is due to a deadlock that occurs when the SDP binding creation event is processed by the event processing thread at the same time another thread is building the 7210 network connections. The event processing thread becomes deadlocked which causes the event and alarm processing to freeze. The issue has been fixed by eliminating the situation which can lead to this deadlock.

3.3


CQ Synopsis of fix



Fixed problems

CQ 502094 Deletion of a Forwarder object from the ASAM repository takes a considerable amount of time. As a result, the processing of events related to a deleted or unmanaged device with a large number of service sites takes a long time to complete.The Adapter for Alcatel-Lucent 5620 SAM EMS builds the HostedBy relationship between the Forwarders and the Switch or Router. The HostedBy relationship is also used to compute the IPStatus. The large number of Forwarders led to a huge monitoring tree structure. The deletion of a Forwarder took a very long time, because the monitoring tree needed to be reevaluated every time a Forwarder was deleted. This issue has been fixed. The HostedBy relationship between the Forwarder and Switch or Router in the ASAM repository is no longer populated. This reduces the size of the monitoring tree structure. The HostedBy relationship between the Forwarder and Switch or Router is used only for handling OLC state changes. This relationship exists in the MPLS repository and the Adapter for Alcatel-Lucent 5620 SAM EMS will leverage it for OLC state change handling.

3.3

CQ 502131SR 35307464ER 5241688

The Adapter for Alcatel-Lucent 5620 SAM EMS does not populate the VPRN L3 Access Interface belonging to a composite VPRN service.The L3 Access Interface on a VPRN service belonging to a composite service does not have a terminatedObjectPointer. The Adapter does not populate the VPRN L3 Access Interface without a terminatedObjectPointer. This issues has been fixed. The Adapter now populates the VPRN L3 Access Interface without a terminatedObjectPointer.

3.3

CQ 502162CQ 500444

When installing the Adapter for Alcatel-Lucent 5620 SAM EMS 3.2.0.1 patch on Windows, the services screen, that lists the running services, displays incorrect values for the service and its description.The patch installation program was not using the --description option of the sm_service command to display the value in the services screen and there was an error in the sm_service show command. Applying the Adapter for Alcatel-Lucent 5620 SAM EMS 3.2.0.1 patch corrects this issue. When a subsequent patch is installed, the service and its description will properly display in the services screen.

3.3

CQ 516600CQ 494048SR 34286932

When the Adapter for Alcatel-Lucent 5620 SAM EMS is restarted with the repository, the events are not processed until another full discovery is completed.The Adapter’s object that stores the indicator for full discovery completion is not persistent in the repository. When the Adapter is restarted with the repository, the Adapter does not detect a completed full discovery and discards all of the events.The configuration file has been modified so that the Adapter’s object that stores the indicator for full discovery completion is persistent.

3.3


CQ Synopsis of fix


Environment and system requirements


Environment and system requirementsThe Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.3 requires the 64-bit version of the operating system for all platforms. Ensure that hardware hosting the Adapter for Alcatel-Lucent 5620 SAM EMS runs a 64-bit operating system and is patched to the latest patch levels recommended by the manufacturer.

Supported platforms

Table 2 on page 13 summarizes the operating system platforms for the EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS:

Table 2 Supported operating system for the Adapter for Alcatel-Lucent 5620 SAM EMS

Operating system Supported version

Red Hat Enterprise Linux • AS 6• AS 7.2, 7.3

(64-bit operating system version only; for AMD64/EM64T chipsets)

Windows Server • Windows 2012, x64• Windows 2016, x64

Recommended patch levels

Table 3 on page 14 summarizes the required operating system patches.

CQ 520936SR 34108824

Adapter for Alcatel-Lucent 5620 SAM EMS was incorrectly setting the StandbyStatus attribute for base and daughter cards to ACTIVE. However, this attribute is only relevant to processor cards. Alcatel-Lucent base cards and daughter cards do not support card redundancy.Changed the default value of StandbyStatus to NOTAPPLICABLE in the Adapter for Alcatel-Lucent 5620 SAM EMS model.

3.3

CQ 425216 SR 31464428

Problems occurred during migration of the Alcatel-Lucent 5620 EMS to version 6.1. The EMC Smarts deployment did not correctly update the serviceName attribute for IP objects after an ASAM Adapter name change. This led to duplication of topology, causing correlation and notification problems.

3.1.0.1

CQ 424413SR 30272928

An error in the Adapter code led to incorrect reporting of ASL script errors by the IP Availability Manager, This error occurred during duplication of SNMPAgents, which is part of the process of creating overlapping topology among multiple IP Availability Managers to achieve cross-domain correlation. This error has been fixed so that the incorrect ASL script error messages are no longer generated.

3.1.0.1


CQ Synopsis of fix



Environment and system requirements

Verify that your operating systems are patched to the levels recommended by the manufacturer. The following patch levels have been identified as critical to the proper functioning of the EMC Smarts software. The installation program will stop if it does not detect the required patches. Verify that the operating system is patched to the level described below.

Table 4 on page 14 lists disk space requirements for installing the Adapter for Alcatel-Lucent 5620 SAM EMS.

For multiple-adapter deployments, EMC recommends adding 400 MB additional disk space per Adapter.

Access requirement

The user performing the installation or migration must be a superuser (User ID 0) on UNIX platforms. The installation program will halt if the user does not have the appropriate privileges.

Table 3 Required operating system patches

Operating system Patches

Red Hat Enterprise Linux 6Red Hat Enterprise Linux 7

When installing on a 64-bit Linux platform, both 64-bit and 32-bit libraries are required.• glibc-2.2.4-32.i686• glibc-2.2.4-32.x86_64• glibc-common-2.2.4-32• compat-libstdc++-33-3.2.3-47.x86_64• compat-libstdc++-33-3.2.3-47.3.i686• redhat-lsb-4.1-24.e17.x86_64Additionally, for Service Assurance Manager Console:On Red Hat Enterprise Linux 7:• libstdc++-4.4.6-3.e16.i686• libXi-1.3-3.e16.i686• libXext-1.1-3.e16.i686• libXtst-1.0.99.2-3.e16.i686• libXrender-0.9.5-1.e16.i686On Red Hat Enterprise Linux 6:• libstdc++-4.4.6-3.el6.i686.rpm• libstdc++-4.4.6-3.el6.i686.rpm• libXi-1.3-3.el6.i686.rpm• libXext-1.1-3.el6.i686.rpm• libXtst-1.0.99.2-3.el6.i686.rpm

Table 4 Required disk space for the Adapter for Alcatel-Lucent 5620 SAM EMS

Platform Disk space

Red Hat Enterprise Linux AS 6 and 7 1.25 GB

Windows 2012, x64 and Windows 2016, x64 1.25 GB

Known problems and limitations


Version numbers

When you run a utility to report the version number of the software, you will see both the version number for the product suite as well as the version number for the underlying foundation software. These two version numbers may differ.

Checking the version numberFrom BASEDIR/smarts/bin/, enter the following command:

sm_server --version

Product versions vary and do not always match the software foundation version number. For example, if you select the About from the Help menu in the Global Console, you may see a different number.

The product version number is displayed during installation on the installation screen.

Third-party software

The Adapter requires the installation of the Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server. Supported versions of the Alcatel-Lucent 5620 Service SAM EMS server are 6.1 through 17.9.

Alcatel-Lucent 5620 Service Aware Manager (SAM) EMS server versions 10.x and higher require that the ASAM 5620 Adapter is at 3.2.0.12 or higher.

The Adapter must be installed on a different host from the Alcatel-Lucent 5620 SAM EMS server, and may be on different hosts from the EMC Smarts Domain Managers.

Known problems and limitationsThe following known problems and limitations are discussed:

◆ “Adapter for Alcatel-Lucent 5620 SAM EMS issues” on page 15

Adapter for Alcatel-Lucent 5620 SAM EMS issues

The following issues affect the Adapter for Alcatel-Lucent 5620 SAM EMS:

Issue

CQ 501166

Alarm discovery cannot complete due to OutOfMemoryError.

Resolution

Default heap size was too small (64MB).



Do not use the “--java” option by itself. Start up the adapter with

--java=maxheapsize=1024m

VLAN instances may be missing when using MPLS Version 3.0.0.3 or earlierCQ 500331

Issue

When the Adapter is deployed with MPLS 3.0.0.3 or earlier, some VLAN elements may be incorrectly deleted. This occurs only when there are VLAN elements managed by the Alcatel-Lucent 5620 SAM EMS. Due to this issue, a SEVERE error message as shown below may be recorded in the Adapter log file:

[November 13, 2009 11:34:10 AM EST +828ms] t@4 platformMAIN_MSG-*-STDFD_ERR-stderr: Nov 13, 2009 11:34:10 AM

com.smarts.asac.SmAsAdapterLog errorSEVERE: [SmWorker] ASAM-MPLS-TOPOLOGY setAttribute got

SmRemoteException:JAVA-E-JE_REMOTE_ERROR-Remote server error:CI-E-EGENERIC-At

/work/bluecurrent/FOUNDATION-7.2.0.X/50/smarts/repos/mr/classdef.c:2318

DiscoveryType: Specified property not found in class MR-PROPERTY_NOT_FOUND-Specified property not found in class ; in file "SmRemoteInterfaceHandler.java" at line 130 for: VLAN::VLAN-network:10.1.1.113:vlanId-88::DiscoveryType value:ASAM_ASAM

Resolution

A resolution will be available in an upcoming patch for the MPLS product.

False jbond connection attempts recordedCQ 441421

Issue

The Adapter’s jbond user makes false connection attempts to the Alcatel-Lucent 5620 SAM EMS. Notices of these attempts occur in the user sessions window or in the session log records

Resolution

This issue has no workaround. Ignore the jbond session notices.

Inconsistent VPN DisplayNames after MPLS Topology Server restartCQ 424011

Issue

Some VPN DisplayNames may be inconsistent upon restart of the MPLS topology server with repository. This occurs because the Adapter topology data that is kept in MPLS GA_StringDictionary is lost after restart of the MPLS topology server.

Resolution

As a workaround, run a full discovery.



False root cause appearing for LSPs having only the primary path configuredCQ 423732

Issue

In a typical configuration, an LSP is protected by two paths, one primary and one standby. In an atypical scenario, an LSP could have only one path (the primary) configured. In this case, if the single primary path goes down, the MPLS Manager will display two root causes: the Primary Path Down event and the LSP Down event. However, in a typical customer deployment with both primary and standby paths configured for LSPs, false root causes do not occur.

Resolution

This issue will be fixed in a later release.

Adapter does not operate correctly if a configured Domain Manager is not runningCQ 312911, CQ 390197, CQ 423736

Issue

Multiple problems may occur if the Domain Managers are not running when the Adapter starts. For example:

◆ The Adapter is unable to generate notifications.

◆ The Adapter pauses indefinitely in its startup sequence if a Domain Manager that is configured in the emsConfig.import file is not running. The adapter will wait until the Domain Manager has registered with the broker before it resumes startup.

◆ In the rare event that a Domain Manager is dead while the Broker still shows it to be RUNNING, the Adapter does not successfully start up.

Resolution

Ensure that all configured Domain Managers are running before attempting to start up the Adapter. Domain Managers need to be running at all times to ensure proper functionality from the EMC Smarts solution.

Adapter unaware of termination of non-durable JMS connectionCQ 354007

Issue

When a non-durable JMS session is terminated, the Adapter is not aware of it. In this circumstance, the Adapter does not do anything to repair the connection.

Resolution

This issue will be addressed in a later release.



No range check is defined for configuration parametersCQ 353223

Issue

The Adapter’s emsConfig.import file does not include range checks for configuration parameters. In the event that a user enters an inappropriate value, the Adapter may not generate an error message and may not function properly.

Resolution


IsManaged attribute not updated after user changeCQ 353940

Issue

If a user manually changes the value (True/False) of the configuration parameter, UnmanageWhenInMaintenance, while the operating state of the device is InMaintenance or InService, the Adapter will not update the IsManaged attribute in the Domain Managers upon restart.

Resolution


Starting an Adapter server on a dual-stack IPv4/IPv6 host causes two broker listingsCQ 353433

Issue

After installing the Adapter and IP Availability Manager with services, two Adapter servers appear in the Broker listing. One is the access point for the Adapter using IPv4, and the other is the Adapter server using IPv6.

Resolution

Ignore the second Adapter server with IPv6.

Error encountered when attempting to delete an MPLS object using the Topology Browser CQ 351708

Issue

There is a problem deleting objects from the MPLS topology using the Topology Browser. When you attempt to delete an object from the IP class, for example, the following error occurs:

com.smarts.store.com.SmStoreException: CI-E-EGENERIC-At ICIN_Core.c:1498 MR-E-NON_SINGLETON_SET-Set operation produced a set which is not a singleton



Resolution

You can remove the object from the topology using the dmctl command, as follows:

At ASAM-BASEDIR/smarts/bin, issue the following command on one line:

▼/dmctl -s DELETE ::▲For example,

./dmctl -s INCHARGE-MPLS-TOPOLOGY delete IP::10.1.1.85

The System Administration Guide provides additional information and examples for using the dmctl command.

SEVERE error message such as: Could not find based on CQ 351680

Issue

During discovery, you may see an error message such as the following:

SEVERE error - Could not find VRF based on service ID

This error may appear during discovery when the query requests more information than necessary. This error does not appear consistently.

Resolution

This error is not harmful; it will be addressed in a future release.

Initial IP discovery required for multivendor installationsCQ 351617

Issue

In a multivendor environment, the Adapter discovery process depends on interfaces previously discovered by the IP Availability Manager. This applies for discovery of Cisco and Juniper devices that are not discovered through the Alcatel-Lucent EMS.

Resolution

Before performing the Adapter discovery, perform discovery by the IP Availability Manager, as described in the IP Manager Discovery Guide.

Lack of status for CurrentUtilization of the Processor classCQ 350754

The lack of status for the attribute, CurrentUtilization of the Processor class, results because the Alcatel-Lucent EMS does not have the status available.

Resolution

This issue requires a change in the Alcatel-Lucent 5620 SAM EMS.


Technical notes

Problem creating/removing VPLS and VLL objectsCQ 319147

Issue

Creation and removal of VPLS and VLL managed objects is inconsistent when there are no sites in the VPLS or VLL.

Resolution

This issue will be resolved in a future release.

MPLS incremental discovery results in delay for display of operational statusCQ 319101

Issue

In the current MPLS architecture, the entire topology is transferred to the Monitoring Server during each incremental creation. For large MPLS environments, if MPLS objects are incrementally created, it could take approximately 60 minutes for operational status to appear in the Smarts MPLS Monitoring Server.

Resolution

You can modify the dxa-am.conf to exclude monitoring of certain objects such as ForwarderEndpoints, thereby reducing topology sync time to a manageable level. Please contact EMC Tech Support for this solution and refer to Primus article emc169931.

Technical notesThere are no technical notes for this release.

DocumentationThe following documentation is available and is updated periodically. Electronic versions of the updated manuals are available on EMC Online Support: https://support.emc.com.

Table 5 EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS product documentation

Part Number Revision Title

300-010-148 A03 Adapter for Alcatel-Lucent 5620 SAM EMS User Guide

302-004-788 A01 Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide

302-004-787 A01 Adapter for Alcatel-Lucent 5620 SAM EMS Release Notes

300-010-151 A01 Adapter for Alcatel-Lucent 5620 SAM EMS Third-Party Copyright Read Me

302-004-764 A01 Adapter for Alcatel-Lucent 5620 SAM EMS Version 3.3 Documentation Portfolio

Software media, organization, and files


EMC Smarts documentation

The Foundation documents in Table 6 on page 21 are product-independent and thus relevant to users of all products:

Table 6 Foundation documentation

Part number Revision Item

300-010-019 A05 System Administration Guide

300-010-022 A02 ICIM Reference

300-010-017 A03 ASL Reference Guide

300-010-018 A02 Perl Reference Guide

300-010-016 A02 MODEL Reference Guide

Software media, organization, and filesThe documentation is updated periodically. Electronic versions of the updated manuals are available on EMC Online Support: https://support.emc.com.


Installation

InstallationInstallation instructions, including information about migrating from a previous version, are available in the Adapter for Alcatel-Lucent 5620 SAM EMS Installation Guide.

Licensing

To use the Adapter for Alcatel-Lucent 5620 SAM EMS, the following licenses are required.

EMC Corporation

For the Adapter for Alcatel-Lucent 5620 SAM EMS, you must obtain a license.

For each EMC Smarts Domain Manager deployed in your Adapter installation, you must obtain the following licenses:

◆ The regular Domain Manager license

◆ A special ASAM Adapter license to allow access by the Adapter for Alcatel-Lucent 5620 SAM EMS

The System Administration Guide provides information on obtaining and installing licenses.

Alcatel-Lucent Corporation

You must obtain the following licenses:

◆ The Alcatel-Lucent 5620 EMS license

◆ The Alcatel-Lucent 5620 SAM-O license

To obtain or update your product license, open a Service Request in the Service Center. The license will be sent through email.

Troubleshooting and getting help


Troubleshooting and getting helpEMC support, product, and licensing information can be obtained as follows:

Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:

https://support.emc.com

Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

Copyright © 2013-2018 Dell Inc. or its subsidiaries. All rights reserved. Published in the USA.

Published May 2018

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

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

Dell, EMC, and other trademarks are registered trademarks or trademarks of Dell Inc. or its subsidiaries in the United States and other countries. All other trademarks used herein are the property of their respective owners.

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

http://support.emc.com

Product descriptionNew features and changesNew features in Foundation 9.5.1New features in ASAM Patches

Fixed problemsEnvironment and system requirementsSupported platformsRecommended patch levelsAccess requirementVersion numbersThird-party software

Known problems and limitationsAdapter for Alcatel-Lucent 5620 SAM EMS issues

Technical notesDocumentationEMC Smarts documentation

Software media, organization, and filesInstallationLicensing

Troubleshooting and getting help

EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version … · 2018. 12. 16. · Alcatel-Lucent...

Documents

Transcript of EMC Smarts Adapter for Alcatel-Lucent 5620 SAM EMS Version … · 2018. 12. 16. · Alcatel-Lucent...