241-6003-100 Generic Device Integration Installation Guide: Draft March 2006 Document Version: 1.3

241-6003-100
Generic Device Integration Installation

Guide
Draft March 2006
Document version: 1.3
About this document

Introducing device integration
Installing a device integration cartridge for the first time
Replacing a device integration cartridge
Removing a device integration cartridge
Administration procedures
Copyright 2006 Nortel, All Rights Reserved.
The information contained herein is the property of Nortel and is strictly confidential. Except as expressly
authorized in writing by Nortel, the holder shall keep all information contained herein confidential, shall disclose it
only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses to protect its own confidential information, but
with no less than reasonable care. Except as expressly authorized in writing by Nortel, the holder is granted no
rights to use the information contained herein.
Nortel, Nortel Networks, the Nortel logo are trademarks of Nortel. UNIX is a trademark of X/Open Company
Limited.
3
About this document

This document contains the procedures to install and administer device integration software
cartridges. Device integration software cartridges provide customers using the Nortel
Multiservice Data Manager (MDM) with:
a means to use SNMP to collect fault management information from a variety of devices
in the network
optionally, a means to forward the fault management information to the Nortel Network
Services Platform (NSP) or the Nortel Applications Platform (AP)
This document:
explains how fault management for SNMP devices integrates into the Nortel network
management platforms
explains how fault information from the device integration software cartridges is
displayed using Nortel MDM, Nortel NSP, and Nortel AP
contains procedures to install, initialize, remove, and replace device integration software
cartridges
Because the installation procedures are almost identical for all of the device integration
software cartridges, the installation procedures have been collected within this generic
installation guide.
Audience for this document

This document is for persons who install, manage, and configure the following Nortel
software:
device integration software cartridges
Nortel NSP, and Nortel AP
Technical support and information

When you purchase a device integration software cartridge, Nortel supplies you with a
telephone number for technical support. If you do not have this number, access the
following web page to find the support number for the region in which you are located:
http://www.nortelnetworks.com/help/contact/global
Generic Device Integration Installation Guide 241-6003-100

4 About this document
System information formats

Throughout this document you will see system information such as command strings,
prompts and responses represented in consistent ways.
Command strings
Command strings that you type appear in boldface, as in the following example:
cd /tmp
Note: You must type the command string exactly as shown, including spaces, and then
press the Return key.
Variable parameters appear in angle brackets, as in the following example:
mkdir /<directory name>
An explanation of the meaning of the variable follows the command string, as in the
following example:
where
<directory name> is the name of the CD-ROM directory
Prompts and responses from the system

System prompts and responses appear in courier font, as in the following example:
Press Return to continue.
Directory and path names
Directory and path names appear in courier font, as in the following example:
/opt/nortel/AP
Buttons and menu items
Buttons and menu items in the application interface appear in boldface, as in the following
example:
Click on the OK button.
Keyboard keys
Keyboard key names appear in boldface, as in the following example:
Press Return.
Results of an action and comments
Results of an action and comments are printed in italic type, as in the following example:
The Controller List window opens.
Nortel Standard February 2006

About this document 5
References
This document references the following Nortel technical publications (NTP):
Nortel MDM Installation and Initial Configuration Guide, 241-6001-100
Nortel MDM Fault Management User Guide, 241-6001-011
Nortel MDM Customization and Server Administrator Guide, 241-6001-303
Nortel MDM Server Reference Guide, 241-6001-310
Nortel MDM SNMP Surveillance Adapter Guide, 241-6001-118
Nortel MDM Alarms Reference, 241-6001-501
Nortel Multiservice Data Manager Device Adapter Installation and Administration User
Guide, 241-6001-121
W-NMS Network Services Platform User Guide, 411-5221-211
Nortel Packet Core Manager for GPRS Networks 2.0.0 Solution Guide, 450-3101-338
Nortel Service Activation System Configuration User Guide for Applications Platform,
450-3101-013
Nortel Applications Platform Installation and Administration Guide, 450-3101-201
Nortel Applications Platform Planning Guide, 450-3101-601
Nortel Applications Platform 8.0.2 Introduction, 450-3101-100
Nortel Applications Platform 8.0.2 User Guide, 450-3101-014
If you are using releases of MDM prior to MDM 13.2, the following documents are also
referenced:
Nortel Fault Management Adapter User Guide, 450-3101-340
Nortel Fault Management Adapter Planning Guide, 450-3101-639

6 About this document

7
1 Introducing device integration

Device integration enables you to install plug-in software called a device integration
software cartridge on a Nortel Multiservice Data Manager (MDM) network managment
workstation to collect fault information from SNMP devices in the network. The fault
information is displayed using
the MDM user interfaces
optionally, the user interfaces of the Nortel Network Services Platform (NSP) or the
Nortel Applications Platform (AP)
A device integration software cartridge consists of a set of device driver files that enables
the MDM software to translate traps from an SNMP device into alarms. The MDM
software displays the translated alarms in the MDM Network Viewer and Alarm Display.
Optionally, the MDM software can be configured to forward the translated alarms to other
operations support systems (OSSs) and to other Nortel network management software such
the Nortel Network Services Platform (NSP) and the Nortel Applications Platform (AP).
A device integration cartridge consists of
the device driver that provides fault management information to MDM. The device
driver software includes:
an icon for the device that is displayed in the MDM Network Viewer
the data collection daemon (DCD) for the device
the Network Model for the device
the Network Viewer files
the documentation for the device driver. This documentation includes:
this guide, which is provided with every device cartridge
a device integration software cartridge user guide that describes the alarms
supported by the device driver and special configuration instructions specific to the
cartridge (if any exist)
a README file that describes known problems with the device driver and possible
solutions for these problems
Device integration documentation is intended for use in conjunction with several additional
Nortel Technical Publications (NTPs), listed in References on page 5.
Prerequisites
Before you install device integration software cartridges using this document:

install and configure the Multiservice Data Manager (MDM) software

ensure that the version of the device integration software cartridge is compatible with:
the software version on the devices
the version of the MDM software
the version of software running on other network management platforms such as
Network Services Platform (NSP) and Applications Platform (AP)
if you plan to use a remote primary management client, you also need to have the
primary management server installed and configured on the client workstation
do not install a device integration software cartridge on the same workstation as an HP
OpenView Desktop client. Installation of the device data collection daemon with the HP
OpenView desktop client is not supported.
if you are using MDM 13.1, or older, you must install and configure the Fault
Management Adapter (FMA) release 1.0.1 on the same workstation as the MDM
software. To install the FMA, see the Fault Management Adapter User Guide,
450-3101-340.
Note: The Fault Management Adapter is not required for MDM 13.2 ,or later.
For information about the version of a device and the platforms on which a device
integration software cartridge is compatible, refer to the Device Integration Cartridge
Compatibility Matrix. To obtain the compatibility matrix
goto URL www.nortelnetworks.com
select Support -> Software Downloads
select Preside
select Software under one of the following products:
Nortel for Wireless Device Integration Cartridges
Nortel Multiservice Data Manager Device Integration Cartridges
Nortel for Optical Ethernet
Surveillance of SNMP devices

This section explains how the devices supported by a device integration software cartridge
uses the SNMP Surveillance Adapter software (part of the Multiservice Data Manager
software) to integrate fault management of SNMP devices into:
the Nortel Multiservice Data Manager (MDM) Fault toolset
the Nortel Network Services Platform Alarm Manager
the Nortel Applications Platform Graphical Network Browser
For a diagram of the elements that make up an SNMPv1/v2 supported framework, see
Figure 1-1 on page 9.

Introducing device integration 9
Figure 1-1
MDM, Network Services Platform, Applications Platform SNMPv1/v2 surveillance architecture
Surveillance workstation
MDM Fault toolset

Network Services Platform
MDMDA
Applications Platform
Network Model NDAM
API Other OSS
GMDR
Collection workstation (optional)
SNMP Surveillance Adapter:
SMDR
alarms and states
Generic DCD Generic DCD
traps traps
polls TSVR polls TSVR
TRep TRep
traps traps
Supported Supported
device device

To support surveillance of an SNMP device, there must be a device integration data

collection daemon (DCD) for that device running on the workstation. A separate DCD is
required for each device type.
Surveillance for SNMP devices is handled by the SNMP Surveillance Adapter (SSA) which
includes a generic data collection daemon (DCD). The SSA permits discovery and
rediscovery of devices, reachability tests, state polling, and trap processing. For details
about this adapter, see MDM SNMP Surveillance Adapter Guide, 241-6001-118.
To manage SNMP devices, the following MDM processes must be running:
the trap server daemon (TSVR) used only in Legacy frameworks
For details, see Trap server daemon (TSVR) in MDM Server Reference Guide,
241-6001-310.
the SNMP management data router (SMDR)
For details, see SNMP Management Data Router (SMDR) in MDM Server Reference
Guide, 241-6001-310.
the general management data router (GMDR)
For details, see General Management Data Router (GMDR) in MDM Server
Reference Guide, 241-6001-310.
the SNMP IP discovery server (IPDSVR)
For details, see SNMP IP Discovery server (IPDSVR) in MDM Server Reference
Guide, 241-6001-310.
SNMP Surveillance Adapter integration architecture

The SNMP Surveillance Adapter (SSA), part of the MDM software, enables support of
SNMP devices by the Nortel Multiservice Data Manager (MDM). The SSA SNMPv1/v2
frameworks consist of a trap reporter, a trap server, a generic data collection daemon, and
an SNMP management data router server.
Trap reporter (TRep)
The trap reporter (TRep), used only in Legacy frameworks, receives trap information from
devices and forwards this information to the trap server (TSVR). The TRep normally binds
to UDP port 162 and cannot co-exist with any other process that needs to bind to this port.
The TReps only responsibility is to empty this UDP port input buffer as fast as possible so
that no information is discarded. The TSVR creates the TRep and monitors the state of the
TSVRs connection with the TRep. The TSVR recreates the TRep if it dies. The TRep
monitors the state of its connection with TSVR and stops if the TSVR dies.
TSVR
The trap server daemon (TSVR), used only in Legacy frameworks, receives trap
information from the trap reporter, filters the traps according to a set of data collection
daemon (DCD) filter rules, and forwards the filtered traps to any DCD that has a matching
filter.

DCD
A generic data collection daemon (DCD) is one of the most important components of the
SNMP Surveillance Adapter. The DCD makes surveillance data available to the MDM
Fault toolsets by:
polling the device for component information
polling the device for state information
receiving trap information from the TSVR
converting the poll and trap information into a format that is consistent with the
Multiservice Data Manager (MDM) state and alarm information
routing the information through SMDR and GMDR to MDM
notifying the SMDR about new or deleted components and any component state changes
SMDR
The SNMP management data router (SMDR) collects alarms and raw state change
information from the DCD and forwards this information to GMDR. SMDR also issues
proxy alarms as needed.
Under the SNMPv3 frameworks, SMDR also connects to SPSVR servers and uses them to
poll for the sysObjectID of devices to be discovered, and to forward LCD configuration
data to BRASS servers.
GMDR
The general management data router (GMDR) makes the surveillance data available to a
number of the Multiservice Data Manager (MDM) fault management tools. The GMDR
stores the alarms in a common format and forwards these alarms to the MDM Fault toolset.
The GMDR also supports alarm and status application programming interfaces for devices.
This API can be used to make fault information available to external Operations Support
Systems (OSSs).
IP DISCOVERY SERVER (IPDSVR)
SNMP IP Discovery (IPDSVR) server monitors the changes to the properties of SNMP
devices. SNMP-managed devices can be viewed and monitored through the IP Discovery
graphical-user interface (GUI). The following device properties are displayed:
the IP address of the device
the Read Community string used to communicate with the device
the SNMP version used to communicate with the device.
For SNMP v1 and v2c, IP Discovery directly communicates with devices. The IPDSVR
establishes a connection with the GMDR server and synchronizes with any changes to
the existing SNMP-managed devices. IPDSVR server periodically queries the GMDR
server for information about discovered devices.
Network Model
The Network Model is a repository for the management data collected and calculated by
the MDM servers, including status information. The Network Model contains a current
view of the devices and components in the network and their states.

NDAM
The Network Data Access Mediator (NDAM) server makes the surveillance data from the
GMDR and status information from the Network Model available to the MDMDA.
MDMDA
The MDM Device Adapter (MDMDA) is a CORBA-compliant device adapter. It takes the
surveillance data from the GMDR and the status data from the NDAM and translates them
into CORBA transactions that can be used by Network Services Platform (NSP) or
Applications Platform (AP).
This access information is provided by SPSVR on receipt of an API request that the
IPDSVR initiates.
Surveillance methods
The Nortel Multiservice Data Manager (MDM) obtains surveillance information from
SNMP devices using two methods: polling and trap reception. As Figure 1-1 shows,
surveillance information can be transferred directly from an SNMP device or indirectly
through a collection workstation running the data collection daemon (DCD) and trap server
(TSVR).
Polling
The following steps occur when the SNMP Surveillance Adapter polls an SNMP device:
1 The DCD obtains configuration and state information directly from the device. With
polling, the DCD initiates the information flow from the device. It polls the device
according to an internal schedule to maintain the synchronization of configuration and
state information between the device and the DCD.
The DCD sends configuration and state information requests to the device. The device
SNMP agent collects the requested configuration and state information and sends the
information back to the DCD. If the DCD receives information on a state change, a
changed or deleted component, or a new component, it sends a notification to the
SMDR.
2 The SMDR collects the surveillance information that it receives from the poll, calculates
the raw component states, and forwards them to the GMDR server process.
Trap translation
The following steps occur when the SNMP Surveillance Adapter receives a trap from an
SNMP device.
1 The DCD receives the trap information through the TRep and the TSVR. For event
notification from traps, the device initiates the information flow.
2 The device gathers traps and forwards them to the TSVR.
3 The TSVR forwards the traps to the DCD.
4 The DCD translates the traps into MDM alarms and forwards them to the SMDR.
The DCD translates traps into three types of alarms:
- SET: These alarms are added to the active alarm list (AAL).
- CLEAR: These alarms cause the removal of their corresponding active SET alarms.
- MSG: These message traps have no impact on the AAL.

The SMDR then recalculates state information from the new AAL.
5 Based on the contents of the trap, a state poll or a discovery poll can be triggered; see
Polling (page 12).
Distribution of alarms
1 The GMDR needs to be registered with the SMDR server to allow the GMDR to obtain
surveillance information from the SMDR server. The SMDR server can send the same
set of alarms to multiple GMDR servers on several workstations by registering the
SMDR server on the GMDR servers.
2 The GMDR server distributes the alarms and status information to MDM applications
such as the Alarm Display and Network Viewer tools, and to external applications
through GMDRs application interface.
3 If the state from a poll does not agree with the state calculated based on the received
traps, the SMDR server creates proxy alarms.
How fault information from a device is displayed in MDM

The Nortel Multiservice Data Manager (MDM) Fault toolset enables you to manage fault
and surveillance of devices with the following tools and displays:
Network status bar
Network viewer
Alarm display
Component status display
Component information viewer
These tools provide textual and graphical displays of component state and alarm
information. With these tools you can detect, diagnose and correct faults.
For details about the MDM Fault toolset, see MDM Fault Management User Guide,
241-6001-011.
Accessing device interfaces from the MDM Network Viewer
To access the device interfaces for a supported device using the Network Viewer:
1 Click on the devices icon in the Network Viewer to highlight it.
2 Press the right mouse button to open the object menu and choose Start Tool >
Configuration. Up to three types of device access may be supported from the menu
that appears. To launch:
To Launch a telnet session to reach through to the device (device reach through),
choose <Telnet to Device>
where
<Telnet to Device> is the option to telnet to the specific device
A terminal window appears. Depending on the device, you may need to open a
telnet session (by entering open <IP_address>). You also need to have a valid
user account for the device interface to log into the device interface.

To Launch a devices element management system (EMS) interface, choose

Launch <EMS>
where
<EMS> is the name of the element management system for the
device
To Launch a devices Web interface, choose Launch WebBrowser.

Note: Not all launch options are supported by all device integration software cartridges.
Refer to the devices Device Integration Cartridge User Guide for the supported device
interface access methods.
How fault information from a device is displayed in the

Network Services Platform (NSP)
Nortel Network Services Platform (NSP) allows you to manage fault and surveillance of
devices using the following tools and displays:
Resource Browser
Alarm Manager
With these tools you can view alarms at both the network and network element levels.
For details about fault management with Network Services Platform, see W-NMS Network
Services Platform User Guide, 411-5221-211.
Accessing applications from the Network Services Platform (NSP)
Resource Browser
Access to applications, including device interfaces, for a supported device is possible from
the Resource Browser.
Note: Device interfaces run on UNIX host machines. Before launching a device
interface, a terminal emulator such as Exceed from Hummingbird Communications
Ltd., must be installed and running on the Network Services Platform (NSP) client
machine.
To access an application, including the device interfaces:
1 Click on the device icon in the Resource Browser to highlight it.
2 Press the right mouse button to open the object menu.
Up to four types of application launches may be supported from the resulting menu:
Launch a telnet session to reach through to a device, choose: Login to NE
Launch the devices element management system (EMS interface), choose
Launch <EMS>
where
<EMS> is the name of the element management system for the
device
Note: The option to launch an EMS interface is device-specific.

Launch MDM, choose MDM Toolset

Launch the IP Device Discovery tool, choose Discover Data Devices
Note: Not all four launch options are supported byall device integration software
cartridges. Refer to the devices Device Integration Cartridge User Guide for the
supported device interface access methods.
end
How fault information from a device is displayed in the

Applications Platform (AP)
The Nortel Applications Platform (AP) provides the network adminstrator with two
graphical user interface tools: the Graphical Network Editor (GNE) and the Graphical
Network Browser (GNB). The GNE enables the network administrator to perform
administration and configuration operations. The GNB uses the network and subnetwork
displays, created by the GNE, to monitor the network. An AP user can monitor the entire
network for alarms through the graphical network displays. Graphical alarm attributes
applied to the network elements assist the user to quickly identify alarm conditions. These
attributes include colors (for example Network Elements in red) to distinguish alarm
severity, balloons to indicate new alarms, text notations to indicate the number and severity
of alarms, and audible indications.
For details about fault management with the Nortel Applications Platform (AP), refer to the
following NTPs:
Applications Platform 8.0.2 Introduction, 450-3101-100
Applications Platform 8.0.2 User Guide, 450-3101-014
Accessing applications form the Applications Platform (AP)

Graphical Network Browser
The Nortel Applications Platform (AP) Graphical Network Browser (GNB) provides reach
through to devices and access to the Multiservice Data Manager (MDM) IP Discovery tool.
To access an application, including the device interfaces:
1 Click on the device icon in the Resource Browser to highlight it.
2 Press the right mouse button to open the object menu and choose Data Applications.
A number of application launches may be supported from the menu that appears. To
launch:
The MDM IP Discovery tool, choose MDM Toolset, then choose Fault, then IP
Discovery
a Telnet session to reach through to a device, choose Login, then Login to NE:
<NE_name>


17
2 Installing a device integration cartridge

for the first time
Use the information in this chapter to install a new device integration software cartridge.
Note: To replace an existing version of a cartridge, see Replacing a device integration
cartridge (page 29).
Chapter task list
Perform the procedures listed in the following table to install a device integration cartridge
for the first time.
Procedure Task Page
2-1 Checking dependencies 18
2-2 Installing a cartridge 19
2-3 Initializing the help system to provide access to alarm 22

help for the newly installed cartridge
2-4 Setting the DCD log level (optional) 23
2-5 Discovering devices in the network 24
2-6 Installing cartridge support for NSP 25
2-7 Installing cartridge support for AP 26
2-8 Accessing the device integration cartridge user guide 28

18 Installing a device integration cartridge for the first time
Procedure 2-1
Checking dependencies
Before you install a device integration cartridge, use this procedure to ensure that:
the software package NTPMDMen, or MDMDOCen, is installed on your workstation
before you install the cartridge software. One of these documentation packages will be
included with the Multiservice Data Manager (MDM) software. If one of these packages
is not installed, you will not be able to display alarm help information for the device.
the version of the device integration cartridge you are installing is compatible with:
- the software version running on the devices to be managed with the cartridge
- the version of the MDM software
- the version of software running on other network management platforms such as
Network Services Platform (NSP) and Applications Platform (AP) (if you are
planning to export fault information to them)
Action
Step Action
1 Examine the Device Integration Cartridge Compatibility Matrix for the compatibility
information that applies to the cartridge you are about to install.
2 Log in to the MDM workstation as userID root.
3 Open an Xterm.
4 If you have MDM 13.4, or earlier, enter the following command in the Xterm:
pkginfo | grep NTPMDMen
If you have MDM 14.1, or later, enter the following command in the Xterm:
pkginfo | grep MDMDOCen
The following response should appear.
application <NTPMDMen | MDMDOCen>
5 If the response appeared continue at step 6.
If the response did not appear, you will be unable to see alarm information for the
device. Use the information in 241-6001-100, MDM Installation and Initial
Configuration to install the appropriate documentation package before you continue at
step 6.
6 If you are using MDM 13.1, or older, the Fault Management Adapter (FMA) Release
1.0.1 software must be installed and running. This allows you to use the IP Device
Discovery window to add and remove devices. See the Fault Management Adapter
User Guide, 450-3101-340.
Note: The IP Device Discovery window is incorporated in MDM 13.2, and above, and
the Nortel Fault Management Adapter is no longer required.
end

Installing a device integration cartridge for the first time 19
Procedure 2-2
Installing a cartridge
Use this procedure to install a device integration cartridge.

If you have downloaded the device integration cartridge from the Nortel distribution site,
you will have probably already performed this procedure using the instructions contained
on the Web site. If you have not installed the device integration cartridge, perform this
procedure now.
Prerequisites
The Server Daemon (SVMDMN) must be running to ensure proper installation of some
cartridges.
The SNMP Management Data Router (SMDR) must be running to ensure proper
installation of some cartridges.
Action
Step Action

2 Create a temporary directory into which you are going to download the cartridge:
Example:
mkdir /tmp/newcartridge
3 Download the tar file that contains the cartridge from the Nortel distribution site to the
temporary directory you just created. You can get the latest version of the cartridge
from the following web site:
http://www130.nortelnetworks.com/cgi-bin/eserv/cs/main.jsp
Note: You will only be able to download software from this site if you have purchased
a Nortel support plan and registered to be able to download software.
4 Access the temporary directory:
Example:
cd /tmp/newcartridge
5 Uncompress the file in the temporary directory:
Example:
tar xvf MDM_Baystack_450_Cartridge_V1.0.0_Sun_b100.tar
The software load creates a new subdirectory inside your temporary directory and
expands the contents of the tar file into the new subdirectory.
6 Access the new subdirectory:
Example:
cd /tmp/newcartridge/

7 List the contents of the new subdirectory:

ls
The system displays the contents of the directory:
Example:
BayR450

Procedure 2-2 (continued)

Installing a cartridge
8 Access the contents of the directory:

cd <directory name>
Example:
cd BayR450
9 List the contents of the directory:
ls
The system displays the contents of the directory:
Example:
NNBayR450
10 Install the cartridge and answer all prompts appropriately.
Installation Example:
Note that this example does not apply when using W-NMS 5.0/
pkgadd -d . NNBayR450
As the cartridge loads, the system displays a series of information messages. If there
are already other cartridges installed you may receive messages like this:
The following files are already installed on the system and are being used by another
package:
/opt/MagellanNMS/ext/bin/addIdiDcd
/opt/MagellanNMS/ext/bin/listIdiDcd
/opt/MagellanNMS/ext/bin/removeIdiDcd
/opt/MagellanNMS/ext/bin/smdrDeleteServer
/opt/MagellanNMS/ext/idi-doc/DI_Generic.pdf
/opt/MagellanNMS/ext//lib/cfg/error_message
/opt/MagellanNMS/ext//lib/cfg/idi_launchUI.cfg
/opt/MagellanNMS/ext//lib/cfg/launchUI
Do you want to install these conflicting files [y, n, ?, q]n
Enter y
end

Procedure 2-3
Initializing the help system to provide access to alarm help
for the newly installed cartridge
Perform this procedure to restart the web server and the Web browser to display alarm help
for the device supported by the newly installed cartridge.
Action
Step Action

2 Open a terminal window.
3 Enter one of the following sets of commands to restart the web server according to the
release of MDM software on the workstation on which you are installing the cartridge.
MDM release 15.1 and above:
/opt/nortel/3rd_party/apache/current_tomcat/bin/shutdown.sh
/opt/nortel/3rd_party/apache/current_tomcat/bin/startup.sh
MDM release 14.1 to 14.3:
/etc/init.d/jtomcatctl404 stop
/etc/init.d/jtomcatctl404 start
MDM release 13.4 and below
cd /opt/MagellanContrib/apache/1.3.9/bin
./apachectl stop
./apachectl start
4 If there are users logged in to MDM who need to see information for the newly installed
cartridge, have them log out of MDM and log back in again.
end

Procedure 2-4
Setting the DCD log level (optional)
If additional information is required while enrolling new devices, use this procedure to
change the log level for the DCD. This setting enables you to view cartridge
request/response information.
Action
Step Action

3 Change directories.
cd /opt/MagellanNMS/cfg/dcd
4 Edit the configuration file for the appropriate IDI. For example,
vi idi_<DCD_process>dcd.cfg
5 Set the parameter logLevels to
logLevels: INFO, MINOR, MAJOR
6 Restart the DCD process using the Server Administration tool (SVM).
7 The logs are written to file /opt/MagellanNMS/data/idi_<device>dcd.log.
end

Procedure 2-5
Discovering devices in the network
Once the cartridge software is installed and the associated MDM servers started, you must
discover the devices in your network, so that they can be managed by MDM, NSP, or AP.
Do this using:
the IP Device Discovery window (to enrol and de-enrol devices)
Users of MDM 13.1 and below: see the Fault Management Adapter User Guide,
450-3101-340.
Users of MDM 13.2 and up: see the IP Discovery chapter in MDM Fault
Management User Guide, 241-6001-011.
the dcdAddNode utility provided with MDM. See the MDM SNMP Surveillance
Adapter Guide, 241-6001-118.

Procedure 2-6
Installing cartridge support for NSP
This procedure installs and configures the NSP software.
If a device integration cartridge is installed on a network management workstation using
MDM 15.2, and above, and the cartridge requires the NSP software, the NSP software is
installed and/or configured when the device integration cartridge software is installed.
Therefore, you can skip this procedure.
Step Action
1 Log in to the NSP workstation as userID root.

2 Download the tar file for NSP Anywhere to the /tmp directory.
3 Access the temporary directory:
cd /tmp
4 Uncompress the configuration file for NSP Anywhere:
tar xvf /opt/MagellanNMS/ext/lib/macros/
<idiDcdName>_MDMD_NSP_Configure.tar
5 Install the icons for NSP and the launch points:
./<didDcdName>Install_IDI_NSP_Icons
./<idiDcdName>Install_IDI_NSP Launchpoints
6 Restart the NSP client user interface.
The NSP platform is now configured to work with the cartridge.
Provided the MDM Device Adapter software is configured to work with the other
platform, its client interface will display the correct network element icons and launch
menus for the new network elements supported by the device integration cartridge.
end

Procedure 2-7
Installing cartridge support for AP
Perform this procedure to enable support of Applications Platform (AP).
The Multiservice Data Manager (MDM) software cannot be installed on the same the
workstation as the AP software. AP must be installed on a Hewlett Packard workstation and
the Multiservice Data Manager (MDM) must be installed on a Sun Microsystems Inc.
workstation.
Action
Step Action
1 Log in to the workstation where the Graphical Network Browser (GNB) for the AP
platform is installed. Use the userID root.
2 Access the /tmp directory:
cd /tmp
3 Establish an FTP session to the MDM workstation:
ftp <IP address of the MDM workstation>
4 Access the macro directory on the MDM workstation:
cd /opt/MagellanNMS/ext/lib/macros
5 Set the file transfer mode to binary:
bin
6 Download the script from the MDM workstation to the AP workstation:
get <cartridge namee>_AP_Config_V<version number>
Example: get Nortel_Radius_AP_Config_VR3.0
7 End the FTP session:
bye
8 Change the file permissions on the downloaded macro:
chmod 755 <cartridge name>
9 Type the following:
./<cartridge name>
10 Restart the MDM device adapter applications (nmsAdapter, fmMoa, rmMoa) on the
MDM DA workstation.
When a cartridge is installed, information is added to configuration files (deviceTypes
and inm.map) used by the MDM device adapter. If the MDM device adapter is not
restarted, the device adapter cannot obtain the new cartridge information.
11 Restart the AP client user interface.
The other platform is now configured to work with the cartridge.
If the MDM Device Adapter software is configured to work with the other platform, the
client interface will display the correct network element icons and launch menus for the
new network elements supported by the device integration cartridge.

end

Procedure 2-8
Accessing the device integration cartridge user guide
A device integration cartridge user guide (PDF) is provided with each device integration
software cartridge. This guide contains information about alarms, trap to alarm translation,
and the object tree for the device.
The user guides are located on the MDM workstation in /opt/MagellanNMS/ext/idi-doc.
Note: You need the Acrobat Reader from Adobe Systems Incorporated to view or print
this document. Adobe Acrobat can be downloaded from
http://www.adobe.com/acrobat.

29
3 Replacing a device integration cartridge

Use the information in this chapter to replace an existing version of an installed device
integration software cartridge with a new version of the cartridge.
Task list
Perform the procedures listed in the following table to replace an existing version of a
device integration software cartridge with a new version.
Procedure Task Page
2-1 Checking dependencies 18
3-1 Preparatory steps 30
3-2 or 3-3 Remove the existing cartridge:
If the existing cartridge was installed with 31

InstallAnywhere
If the existing cartridge was installed with the pkgadd 32

command
2-2 Installing a cartridge 19
3-4 Restoring discovered devices 33
Note: To reduce the bulk of this document, we have not repeated procedures in this
chapter that are available in other chapters. Therefore, in some cases, this table refers
you to procedures that are contained in other chapters.

Procedure 3-1
Preparatory steps
Use this procedure to prepare to replace a previous version of a cartridge with another
version.
Before starting this procedure, check your cartridge dependencies as described in
Procedure 2-1 on page 18.
Action
Step Action.
1 If you are using MDM 13.1 or older:

Back up the network element address file. For information about backing up the
network element address file, see the section on importing and exporting a network
element address file in the Fault Management Adapter User Guide, 450-3101-340.
If you are using MDM 13.2 and up:
From the IP discovery main window, save the device list. For instructions to do this,
see the IP Discovery chapter in MDM Fault Management User Guide, 241-6001-011.
2 In some cases you may have manually added a device using the dcdAddNode
command. If you have done this, back up the seed file by saving it in a temporary
directory that will not be affected by cartridge removal:
Access the directory where the seed files are stored:
cd /opt/MagellanNMS/cfg
List the files that are stored in this directory:
ls
Look for a seed file for the cartridge with the form
<process_name>.sed
Example:
idi_shastadcd.sed
If you find one, copy it into a temporary directory where it will not be affected by
cartridge removal. Example:
cp <process_name>.sed /tmp
3 Go to one of the following procedures to remove the existing cartridge.
Procedure 3-2 on page 31 if the existing cartridge was installed with
InstallAnywhere
Procedure 3-3 on page 32 if the existing cartridge was installed with the pkgadd
command.
end

Replacing a device integration cartridge 31
Procedure 3-2
Removing a cartridge installed with InstallAnywhere
Use this procedure to removing an existing cartridge that was installed with the IDI version
(not the MDM version) InstallAnywhere. If the existing cartridge was installed with the
pkgadd command, see Procedure 3-3 on page 32.
Action
Step Action

2 Enter the following commands:
cd /opt/MagellanNMS
ls | grep idi
A listing of all the data files for removing DI cartridges installed with InstallAnywhere
appears. For example:
idi_B450_UninstallerData
idi_BPS2000_UninstallerData
idi_JUNIPER_UninstallerData
idi_PP1200_UninstallerData
idi_ERS8600-MERS8600_UninstallerData
If there are no UninstallerData files listed, use the procedure Removing an existing
cartridge installed with pkgadd on page 332.
3 Enter the following command to remove the cartridge:
./IDIUninstaller idi_<device>UninstallerData
For example:
./IDIUninstaller idi_PP2430_UninstallerData
The InstallAnywhere window opens. Follow the prompts that are displayed to remove
the cartridge.
4 Install the new cartridge using Procedure 2-2 on page 19, then go to Procedure 3-4
on page 33.
end

Procedure 3-3
Removing an existing cartridge installed with pkgadd
Perform this procedure to remove an existing cartridge that was installed using the pkgadd
command before upgrading to a new cartridge. If the existing cartridge was installed with
InstallAnywhere, see instead Procedure 3-2 on page 31.
Action
Step Action

2 Use the pkginfo command to determine which cartridges are installed:
pkginfo | grep "MDM DI"
A list of software packages appears on the screen. Among them is the package name
for the device cartridge you wish to remove. For example: NNBayR450.
3 Remove the package:
pkgrm <package_name>
Example:
pkgrm NNBayR450
A description of the package to be removed appears followed by a prompt that asks
to you to confirm that you want to remove the package:
Do you want to remove the package?
4 Enter y.
##Removing installed package instances <packagename>
This package contains scripts which will be executed with super -user
permission during the process of removing this package.
Do you want to continue with the removal of this package [y, n?, q]
5 Enter y.
##Verifying package dependencies.
##Processing package information<
## Executing preremove script.
Stop and Remove the DCD server for this cartridge.
Enter local MDM Server Administration password to stop and remove DCD server.
6 Enter the administrator password for the Server Manager Administration tool.
The script displays a number of messages ending with:
Removal of <packagename> was successful.
7 Install the new cartridge using Procedure 2-2 on page 19 then go to Procedure 3-4 on
page 33.
end

Replacing a device integration cartridge 33
Procedure 3-4
Restoring discovered devices
Refer to the following documents to make the existing set of discovered devices available
to the new version of the device integration cartridge.
Action
Step Action
1 Do one of the following to restore the discovered devices:

If you are using MDM 13.1 or older:
Restore the network element address file. For the instructions to do this see the
section on importing and exporting a network element address file in the Fault
Management Adapter User Guide, 450-3101-340,
If you are using MDM 13.2 and up:
From the Discover window, restore the device list you saved in step 2 using the
Load From tab. For the procedure to restore the device list, see the IP Discovery
chapter in the MDM Fault Management User Guide, 241-6001-011.
If you manually added a device with the dcdAddNode command, restore the seed
(<process_name>.sed) file from the temporary directory in which you stored the
seed file before removing the previous version of the cartridge.
Example:
cp /tmp/ssgdcd.sed /opt/MagellanNMS/cfg/idi_shastadcd.sed
The software re-reads the seed files only once every two hours. Therefore, it is
possible that you can wait up to two hours for the seed file to be updated. If this
wait is unacceptable, use the Sever Manager Administration tool to restart the
DCD process for the device.
2 If there are users logged in to the MDM workstation who need to see information for
the newly installed cartridge, have them log out of the workstation and log back in
again,
end


35
4 Removing a device integration cartridge

Use the information in this chapter to permanently remove a device integration software
cartridge and to delete fault information for devices supported by the cartridge.
Do not use the information in this chapter if you are going to replace a cartridge with a new
version. See Replacing a device integration cartridge (page 29).
Task list
Perform the procedures listed in the following table to remove a device integration
cartridge:
Procedure Task Page
Remove the discovered devices
4-1 Removing discovered devices 36
Remove the existing cartridge:
3-2 If the existing cartridge was installed with 31

InstallAnywhere
3-3 If the existing cartridge was installed with the pkgadd 32

command
Note: To reduce the bulk of this document, we have not repeated procedures in this
chapter that are available in other chapters. Therefore, in some cases, this table refers
you to procedures that are contained in other chapters.

Procedure 4-1
Removing discovered devices
Use this procedure to remove all of the instances of the devices from the Multiservice Data
Manager (MDM), and, optionally, from the Network Services Platform (NSP) and
Applications Platform (AP).
Prerequisites
Before you start this procedure
open the MDM IP Device Discovery window.
open the MDM GDMR Administration window.
Action
Step Action
1 In the IP Device Discovery window, left-click with the mouse to select a discovered
device to delete.
2 Right-click with the mouse to open the pop-up menu, and choose Delete.
The Delete Options window opens.
3 In the Delete Options window, select Attempt Device Deletion from Network Model.
Note: Click the OK button.If you have the MDM Network Viewer window open, the
icon for any device that you delete will turn gray.
4 Repeat steps 1 to 3 to remove each device associated with the cartridge you removed.
5 In the MDM GMDR Administration window, select Security > Login as Admin...
6 Enter your password and click OK.
7 Click Show Components in the GMDR Administration window.
8 Look at the list of components and verify that the devices related to the cartridge you
are removing no longer appear in the list.
Tip: If a device remains left-click on the device to selected it, then click Delete.
Software removes the device is immediately removed from the list.
9 Remove instances of discovered devices from NSP and AP.
For:
NSP, refer to the W-NMS Network Services Platform User Guide,
411-5221-211.
APs Graphical Network Browser window, refer to the procedure for deleting a
controller in the Graphical Network Editor (GNE) in the Service Activation System
Configuration User Guide for Applications Platform, 450-3101-013
continued

Removing a device integration cartridge 37
Procedure 4-1 (continued)

Removing discovered devices
10 Remove the device integration software cartridge with one of the following procedures:
If the cartridge was originally installed with InstallAnywhere, see Procedure 3-2
(page 31)
If the cartridge was originally installed with the pkgadd command, see
Procedure 3-3 (page 32).
end


39
5 Administration procedures
This chapter contains procedures that you may need to perform occasionally once a device
integration cartridge has been installed.
Procedure list
Refer to any of the procedures listed in the following table.
Procedure Title Page
5-1 Starting a DCD 40
5-2 Managing DCDs 41
5-3 Stopping a DCD 42
5-4 Removing a DCD 43
5-5 Displaying a list of the device cartridges installed on the 44

workstation
5-6 Updating MDM servers to recognize a new cartridge 45

with the poprest command
5-7 Starting and stopping the Web server 46
2-5 Discovering devices in the network 24
2-6 Installing cartridge support for NSP 25
3-4 Restoring discovered devices 33
Note: To reduce the bulk of this document, we have not repeated procedures that are
available in other chapters. Therefore, in some cases, this table refers you to procedures
that are contained in other chapters.

Procedure 5-1
Starting a DCD
If you followed the procedures in this book to install a device integration cartridge, the data
collection daemon (DCD) for the cartridge should already be started and running. Under
certain circumstances, it may be necessary to start one or more DCDs. Use this procedure
to start DCDs.
If a device integration cartridge is installed on a network management workstation using
MDM 15.2, and above, and the cartridge requires the NSP software, the NSP software is
installed and/or configured when the device integration cartridge software is installed.
Therefore, you can skip this procedure.
Step Action
1 Type
cd /opt/MagellanNMS/ext/bin
2 Type
./listIdiDcd
A list of all the installed IDI data collection daemons (DCD) and their current state is
displayed.
3 Use the addIdiDcd utility to add the IDI DCDs you require:
./addIdiDcd -password <password> <idiDcd1> <idiDcd2>...
This is the recommended form of this command to use. It will add and start only the
specified DCDs.
This will add and start all the listed DCDs.
where
<password> is the SVM password. If an SVM password has not
been set, then you can omit this parameter.
<idiDcd1> <idiDcd2> ... is the IDI DCD to start.
After the addIdiDcd command is processed, a new list of the updated state of the
DCDs is displayed.
end

Administration procedures 41
Procedure 5-2
Managing DCDs
The default configuration used during installation configures and launches one data
collection daemon (DCD) for each network device-type installed. This is acceptable in a
network where there are many devices, but only a few device-types. However, there are two
situations when you might want to manage DCDs differently:
It is very resource intensive to have many device-types, and only a few devices of each
type. To avoid this, consolidate several device profiles into a single configuration.
There is a limit of 1,000 devices a single DCD can handle. To support more than 1,000
devices, partition them across multiple DCDs.
For information, see Chapter 3 Configuring the SNMP Surveillance Adapter in MDM
SNMP Surveillance Adapter Guide, 241-6001-118.

Procedure 5-3
Stopping a DCD
Use this procedure to stop a data collection daemon (DCD).
Action
Step Action

3 Enter
cd /opt/MagellanNMS/bin
4 Start the MDM toolsets:
./nmstool Admin.tsets &
5 Click on the Nortel logo.
The MDM toolsets menus appear.
6 In the menus, select System->Administration->Server Administration
The Server Manager window opens and lists all of the servers that are running and
their states.
7 Select Security->Authorize.
8 Enter the SVM administration password.
9 Scroll down the list of servers until you find the name of the DCD for the device. The
DCD names have the following syntax:
idi_<device name>DCD
10 When you find the DCD for the device, click on the DCD to select it.
The DCD name becomes highlighted.
11 With the cursor still on the highlighted DCD, press and hold the right mouse button to
open the pop-up menu,
12 In the pop-up menu, select Stop
After a short delay the status of the DCD changes to Stopped.
end

Procedure 5-4
Removing a DCD
Use this procedure to stop and completely remove a data collection daemon (DCD) for a
device.
Note: If the Fault Management Adapter (FMA) has been installed and you want to
remove it, you must first remove the cartridge software.
Action
Step Action

3 Enter
cd /opt/MagellanNMS/ext/bin
4 Enter
./listIdiDcd
A list of the installed IDI data collection daemons (DCD) is displayed.
5 Use the removeIdiDcd utility to stop IDI DCDs that are running. Enter
./removeIdiDcd -password <password> <idiDcd1> <idiDcd2>...
where
<password> is the SVM password. If an SVM password has not
been set, then you can omit this parameter.
<idiDcd1> <idiDcd2> ... is the IDI DCD to remove.
After the removeIdiDcd command is processed, a new list of the updated state of the
DCDs is displayed.
end

Procedure 5-5
Displaying a list of the device cartridges installed on the
workstation
Use this procedure to determine which version of a device integration software cartridge is
installed on the workstation and whether it was installed with InstallAnywhere or with the
pkgadd command.
Action
Step Action

2 Enter the following commands:
cd /opt/MagellanNMS
ls | grep idi
A listing of all the data files for removing DI cartridges installed with InstallAnywhere
appears. For example:
idi_B450_UninstallerData
idi_BPS2000_UninstallerData
idi_JUNIPER_UninstallerData
idi_ERS8600-MERS8600_UninstallerData
Each one of these represents an installed device cartridge that was installed with the
InstallAnywhere script.
3 Run the pkginfo command to determine which cartridges have been installed with the
pkgadd command
pkginfo | grep "MDM DI"
Example:
A list of all software packages for device integration cartridges installed with the
pkgadd command appears on the screen.
end

Procedure 5-6
Updating MDM servers to recognize a new cartridge with the
poprest command
When you install a cartridge, the installation script uses the opt/MagellanNMS/bin/poprest
command to enable the network model to recognize fault information from the new
cartridge.
If you find it necessary, after installation, to signal network model servers to recognize the
new cartridge, use this procedure.
Action
Step Action

2 Run the poprest command to update the network model servers to recognize devices
monitored with a new cartridge, type
/opt/MagellanNMS/bin/poprest -u

Procedure 5-7
Starting and stopping the Web server
When you install a new version of a device integration software cartridge, you need to
restart the web server to ensure that the help system recognizes the contents of the new
cartridge. For MDM 14.1, and up, the web server is a Tomcat web server. For MDM 13.4,
and older, the web server is an Apache web server.
The procedures in previous sections tell you how to stop and restart these servers during the
installation process. However, on occasion, you may find it necessary to restart the web
server after installation.
Action
Step Action

2 Enter one of the following sets of commands to restart the web server according to the
release of MDM software on the workstation.
MDM release 15.1 and above:
/opt/nortel/3rd_party/apache/current_tomcat/bin/shutdown.sh
/opt/nortel/3rd_party/apache/current_tomcat/bin/startup.sh
MDM release 14.1 to 14.3:
/etc/init.d/jtomcatctl404 stop
/etc/init.d/jtomcatctl404 start
MDM release 13.4 and older
cd /opt/MagellanContrib/apache/1.3.9/bin
./apachectl stop
./apachectl start
end

241-6003-100 Generic Device Integration Installation Guide: Draft March 2006 Document Version: 1.3

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

241-6003-100 Generic Device Integration Installation Guide: Draft March 2006 Document Version: 1.3

Hochgeladen von

Copyright:

Verfügbare Formate

241-6003-100

Generic Device Integration Installation

About this document

About this document

Audience for this document

Technical support and information

Generic Device Integration Installation Guide 241-6003-100

System information formats

Prompts and responses from the system

Nortel Standard February 2006

Generic Device Integration Installation Guide 241-6003-100

Nortel Standard February 2006

1 Introducing device integration

Generic Device Integration Installation Guide 241-6003-100

install and configure the Multiservice Data Manager (MDM) software

Surveillance of SNMP devices

Nortel Standard February 2006

MDM Fault toolset

Network Model NDAM

API Other OSS

SNMP Surveillance Adapter:

alarms and states

Generic DCD Generic DCD

polls TSVR polls TSVR

Generic Device Integration Installation Guide 241-6003-100

To support surveillance of an SNMP device, there must be a device integration data

SNMP Surveillance Adapter integration architecture

Nortel Standard February 2006

Generic Device Integration Installation Guide 241-6003-100

Nortel Standard February 2006

How fault information from a device is displayed in MDM

Generic Device Integration Installation Guide 241-6003-100

To Launch a devices element management system (EMS) interface, choose

To Launch a devices Web interface, choose Launch WebBrowser.

How fault information from a device is displayed in the

Note: The option to launch an EMS interface is device-specific.

Nortel Standard February 2006

Launch MDM, choose MDM Toolset

How fault information from a device is displayed in the

Accessing applications form the Applications Platform (AP)

Generic Device Integration Installation Guide 241-6003-100

Nortel Standard February 2006

2 Installing a device integration cartridge

2-1 Checking dependencies 18

2-2 Installing a cartridge 19

2-3 Initializing the help system to provide access to alarm 22

2-4 Setting the DCD log level (optional) 23

2-5 Discovering devices in the network 24

2-6 Installing cartridge support for NSP 25

2-7 Installing cartridge support for AP 26

2-8 Accessing the device integration cartridge user guide 28

Generic Device Integration Installation Guide 241-6003-100

Nortel Standard February 2006

Use this procedure to install a device integration cartridge.

1 Log in to the MDM workstation as userID root.

Generic Device Integration Installation Guide 241-6003-100

7 List the contents of the new subdirectory:

Nortel Standard February 2006

Procedure 2-2 (continued)

8 Access the contents of the directory:

Generic Device Integration Installation Guide 241-6003-100

1 Log in to the MDM workstation as userID root.

Nortel Standard February 2006