SolutionPack for Alcatel-Lucent 5620 SAM Summary Sheet – Service Assurance Suite 9.4

Table of Contents

Overview

Learn how to install and configure the SolutionPack for Alcatel-Lucent 5620 SAM (Service Aware Manager). This SolutionPack collects data from the Alcatel-Lucent 5620 Service Aware Manager platform. This platform offers element, network, and service management for advanced Layer 2 and Layer 3 network solutions and services based on the Alcatel-Lucent's Carrier Ethernet and the IP/MPLS Service Routing portfolio.

SolutionPack for Alcatel-Lucent 5620 SAM offers the following:
  • Highly scalable solutions supporting active and standby Alcatel-Lucent SAM architectures
  • Powerful dashboards
  • Topology data and device statistics collected from Alcatel-Lucent equipment
  • Accurate real-time service-oriented views for operations, engineering, and customers
  • Provisioning and statistics within the MPLS infrastructure integrated with other managed networks and equipment
  • Report data based on the following:
    • Customers and Services
    • MPLS, Tunnels, and VRE
    • Performance, Health, and OAM probes
Back to Top

Technical specifications

SolutionPack version

1.0

Compatible EMC M&R versions

6.5u1 and later

Data collection method

Alcatel-Lucent 5620 SAM-O collector

The collector for Alcatel-Lucent 5620 SAM communicates with the Alcatel-Lucent SAM-O module via the Statistic Log Subscription using the Java Messaging Service (JMS). The Alcatel-Lucent 5620 SAM-O collector does the following:

Supported devices

Alcatel-Lucent 5620 SAM release 11

Alcatel-Lucent 5620 release 11 (SAM-O module)

Main reports

Generic Device Performance (such as CPU and memory)

Physical and Logical Interface Performance

Multiprotocol Label Switch (MPLS) and Label-Switched Paths (LSPs) & Virtual Routing and Forwarding (VRF) Measurements

Service Access Points (SAPs)

Service Tunnel Traffic (SDPs)

Class of Forwarding Measurements

Ingress and Egress Traffic Details

Service Level Agreement (SLA)

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack by completing a Support Request (SR) form, which is available on the EMC Online Support website at http://support.emc.com.

Back to Top

Performing prerequisite installation tasks

This SolutionPack requires that you verify that the Alcatel-Lucent 5620 SAM environment is ready for the installation.

Procedure

  1. Verify the Alcatel-Lucent 5620 SAM-O Module is configured and running.
  2. Verify the FTP or SFTP server is running on the Alcatel-Lucent 5620 SAM server with valid permissions to the server folder, which stores the log files. These permissions enable the Alcatel-Lucent 5620 SAM-O collector to retrieve log files from the Alcatel-Lucent 5620 SAM server.
  3. During the installation, you are asked for details about the Alcatel-Lucent 5620 SAM server, such as user name, password, and SAM-O Module port number. Contact the Alcatel-Lucent 5620 SAM administrator for these details.
Back to Top

Installing the SolutionPack for Alcatel-Lucent 5620 SAM

Before you begin

  • Determine whether you need a SolutionPack license file by checking the feature names and expiration dates listed in Centralized Management > License Management. If the license is not listed, obtain one by completing a Support Request (SR) form, which you can find on the EMC Online Support website at http://support.emc.com.

  • Make sure the core modules, such as the Module-Manager, are up-to-date on all servers since not all module dependencies are validated during the SolutionPack installation. See the EMC M&R (Watch4net) Installation and Configuration Guide for more information.

Procedure

  1. Log in to the EMC M&R platform with your user name and password.
  2. Select Administration.
  3. Select Centralized Management.
  4. Select SOLUTIONPACK CENTER.
  5. Select the SolutionPack in the Browse and Install SolutionPacks screen.
  6. Fill out the form with details for the Alcatel-Lucent 5620 SAM server and click Install.
  7. Select the Administration Web-Service Instance as the default and click Next.
  8. Wait until the installation is complete and then click OK.
  9. Select Centralized Management > SolutionPack to verify the installed SolutionPack.
Back to Top

Performing post installation tasks

After you install the SolutionPack for Alcatel-Lucent 5620 SAM, you must perform certain tasks.

Procedure

  1. Copy the samOss.jar file from your Alcatel-Lucent 5620 SAM installation to your EMC M&R Stream collector lib folder.
    For example, copy /opt/5620sam/client/nms/lib/SAM_11_0_R1/samOss.jar to /opt/APG/Collecting/Stream-Collector/alcatel-sam5620/lib/samOss.jar
  2. Change the ownership on the jar file in the Stream collector path.
    For example, chown apg:apg /opt/APG/Collecting/Stream-Collector/alcatel-sam5620/lib/samOss.jar
  3. Start the collector by going to Centralized Management > Collecting > Collector-Manager::alcatel-sam5620 > Start.
  4. Check the logs at /opt/APG/Collecting/Collector-Manager/alcatel-sam5620/logs
Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Modules.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

What to do if the Collector-Manager does not start

Error message shown in log file

If you see this type of error message in the log files, verify the samOss.jar file from the Alcatel-Lucent 5620 SAM installation is correctly installed in the EMC M&R server. See Performing post installation tasks.

SEVERE   -- [2014-12-01 02:19:22 EST] -- StreamCollector::start(): 
Error while starting com.watch4net.apg.ubertext.parsing.retriever.StreamRetrieverException: 
Error while creating JMS context for source jnp://hostname:1099
at com.watch4net.apg.ubertext.parsing.retriever.JMSListenerRetriever$JMSConnection.<init>(JMSListenerRetriever.java:404)
at com.watch4net.apg.ubertext.parsing.retriever.JMSListenerRetriever$JMSConnection.<init>(JMSListenerRetriever.java:329)
at com.watch4net.apg.ubertext.parsing.retriever.JMSListenerRetriever.startAutomaticRetrieving(JMSListenerRetriever.java:127)
at com.watch4net.apg.ubertext.parsing.DataRetriever.startAutomaticRetrieving(DataRetriever.java:227)
at com.watch4net.apg.ubertext.collector.Collecting.scheduleCollecting(Collecting.java:148)
at com.watch4net.apg.ubertext.collector.StreamCollector.start(StreamCollector.java:129)
at com.watch4net.apg.v2.collector.CollectorManagerImpl.startComponents(CollectorManagerImpl.java:601)
at com.watch4net.apg.v2.collector.CollectorManagerImpl.start(CollectorManagerImpl.java:665)
at com.watch4net.apg.v2.collector.Bootstrap.serviceStart(Bootstrap.java:91)
at com.watch4net.apg.v2.collector.Bootstrap.main(Bootstrap.java:140)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.watch4net.apg.module.plugin.service.Bootstrap.main(Bootstrap.java:59)

Back to Top