23.1 Function Overview

IPX Discovers and models IPX networks by communicating with one or more topology export/import agent (NXIS) located on the Novell Management platform (Managewise). NXIX exports topology data discovered by Managewise; Managewise need not be running during this process. The data is then modeled appropriately, and a format topology is displayed and stored out to the database.

The NXIS script Format Specification 1.0 specifies how data is exported and protocols for communication between SunNet Manager and NXIS. NXIS listens for client connections at TCP/IP port 1486 at the NMS console.

23.1.1 Configuring the Export/Import Agent

Before you begin IPX Discover, ensure that the Export/Import Agent (NXIS) is running on the Novell Managewise console. The console need not be running, but the NetExplorer program which discovers Novell Networks must be running on the Novell Server.

To configure NXIS on the Novell server:

1. Click on the Export Agent Setup window.

2. Enter the Console Name.

   The name you provide here must be the same name you provide in the IPX configuration setup.

3. Enter the Password.

   The name you provide here must be the same name you provide in the IPX configuration setup.

4. Console Type: Other

5. Select Advance.

6. Port Number: configure for 1486

7. Database Extraction Schedule: Enter information specifying when information is to be extracted from the database.

8. Advance window: Click OK

9. Main window: Click OK

10. Restart Export/Import Communication Agent.

23.1.2 IPX MIBs and Schema

Following are the schemas related to IPX devices that support SNMP over IP.

· nwalarm.schema
· nwhostx.schema
· nwserver.schema
· nwtrend.schema
· snmp-mibii.schema

To begin the search:

1. Click SELECT on the Console Menu Tools button, and drag to Discover, then to IP Discover. You receive the screen in Figure 23-1.

2. Click SELECT on the Configuration button on the IPX Discover Home screen to configure the search for NetWare devices.

   You receive the screen shown in Figure 23-2. Enter the appropriate search information.

Figure 23-1

Figure 23-2

---

Note - You must choose "Other" as the option in which to send data, not IBM File Format.

---

23.2 Forwarding Novell's NMS Alarms to SunNet Manager

This section describes how to configure the current release of SunNet Manager and Novell's NetWare Management System (NMS) to forward NMS SNMP alarms from NMS to SunNet Manager over TCP/IP using the NMS Export Import Service (NXIS).

23.2.1 Software Requirements

Prior to making the configuration changes described below, verify that the following software requirements are met:

• The current release of SunNet Manager is installed.
• For the NetWare Management System server:

  · NetWare Management Agent 1.5 software is installed.

  · TCPIP NLM is loaded.

  · NW2SNMP NLM is loaded with the GA switch set to ON ("load nw2snmp ga=on").

23.2.2 Configuration Changes Needed to SNM and NMS

To forward alarms from NMS to SunNet Manager, configuration changes are needed on both sides. NMS must be configured to send the alarms to SunNet Manager and SunNet Manager must be configured to understand and interpret the alarm information. These changes are described below.

23.2.2.1 SunNet Manager Configuration Changes

The alarms forwarded from NMS to SunNet Manager are generically referred to as "enterprise-specific traps." In order for SunNet Manager to handle and interpret the Novell enterprise traps, Novell's NetWare Server trap MIB (nwalarm.mib) must be integrated into SunNet Manager as described in the following steps. For more details, refer to "Part 2: Reference." In the examples below <SNM_path> refers to the location where SunNet Manager has been installed. The default location is as follows:

• /opt/SUNWconn/snm for Solaris 2.x installations
• /usr/snm for Solaris 1.x installations

Obtain a copy of the nwalarm.mib file from the NetWare Management Agent Setup diskette.

4. As root, load this file into the <SNM_path>/agents directory.

5. As root, run the SunNet Manager mib2schema utility on the nwalarm.mib file. This will produce three files (nwalarm.mib.schema, nwalarm.mib.oid, and nwalarm.mib.traps) as shown below:

hostname# <SNM_path>/bin/mib2schema nwalarm.mib Translating.... Translation Complete. Schema file in "nwalarm.mib.schema" Oid file in "nwalarm.mib.oid" Traps in "nwalarm.mib.traps"

6. As root, run the SunNet Manager build_oid utility. This will update the object identifier database with the information from the nwalarm.mib.oid file as follows:

hostname# <SNM_path>/bin/build_oid Parsing <SNM_path>/agents/enterprises.oid Parsing <SNM_path>/agents/snmp-mibII.oid Parsing <SNM_path>/agents/snmp.oid Parsing <SNM_path>/agents/sun-snmp.oid Parsing <SNM_path>/agents/nwalarm.mib.oid Writing <database_path>/oid.dbase

7. If the nwalarm.mib.traps file is the only trap file that you need for your devices, you can copy the contents of that file to the default trap file. On the system where the trap daemon is running, append the contents of nwalarm.mib.traps to the end of the file specified in snm.conf as the na.snmp-trap.default-trapfile file. (The snm.conf file is located in /etc/opt/SUNWconn/snm for Solaris 2.x; in /etc for Solaris 1.x.) Refer to "Part 2: Reference" for detailed information on the trap daemon and creating an SNMP host file.

For Solaris 2.x:

hostname# cd /opt/SUNWconn/snm/agents hostname# cat nwalarm.mib.traps >> /var/opt/snm/snmp.traps

For Solaris 1.x:

hostname# cd /usr/snm/agents hostname# cat nwalarm.mib.traps >> /var/adm/snm/snmp.traps

or: Create (or update) an SNMP host file by inserting the appropriate entry for the NetWare Management server host and specifying the nwalarm.mib.schema and nwalarm.mib.traps files (in the agents directory) as the schema and trap files respectively. Refer to "Part 2: Reference" for detailed information on the trap daemon and creating an SNMP host file.

An example entry added to the snmp.hosts file for the NMS server "steam" follows:

steam public public 10 <SNM_path>/agents/nwalarm.mib.schema <SNM_path>/agents/nwalarm.mib.traps

23.2.2.2 NMS Configuration Changes

In the Netware Management system, the file TRAPTARG.CFG defines the recipients of SNMP traps (alarms).

This file is located in the SYS:\ETC directory of servers in which the NetWare Management Agent 1.5 software is installed. The file allows the user to define recipients to receive SNMP traps over IPX and UDP.

To forward traps to SunNet Manager, edit the TRAPTARG.CFG file and under the UDP section, add the IP address of the SunNet Manager machine which is to be the recipient of the SNMP alarms. In the following example, the IP address 123.123.34.56 has been added to the UDP section of the TRAPTARG.CFG file:

Protocol UDP # In this section you can put SNMP managers that want to receive # traps from the local node over UDP. Use either IP address or # logical name. (If you use a logical name be sure the name and its # corresponding ip address appear in the sys:etc\hosts file.) # By default, the local node sends traps at least to itself. 127.0.0.1 # send traps to the loopback address 123.123.34.56 # IP address of SunNet Manager system

23.2.3 Example Forwarded Trap

Following is a typical trap report which has been generated by SunNet Manager after receiving a forwarded trap from NMS. In this particular example, a supervisor has established a login connection with the server STEAM.

Mon Sep 20 15:08:56 1993 [ steam ] : Trap: sequence=1 receive-time=Mon Sep 20 15:08:56 1993 version=0 community=PUBLIC enterprise=Novell.mibDoc.nwalarm-mib source-time=87:09:54.30 trap-type=loginConnection serverName=STEAM trapTime=748555591 userName=SUPERVISOR connectionNumber=1