 |
|
|
|
Cubix
Management System
Chapter 3 - Installation (1 of 2)
Overview
Preparation
CMS Console Installation
Agent Installation
CMS is a complete system for Cubix device management. CMS performs all network communications using SNMP (Simple Network Management Protocol) on a NetWare network. Novell provides SNMP support on NetWare workstations as part of the NetWare DOS Requester v1.2 (or higher). SNMP support is also provided on NetWare file servers and routers in the form of a NetWare Loadable Module (SNMP.NLM). Every device to be monitored by CMS must have the appropriate NetWare software installed. Instructions for this installation are included in this chapter.
If the network on which CMS is to be installed is equipped with Novell's Management System (NMS), CMS may be integrated into NMS to provide one seamless management system. Refer to the CMS Console Installation section for more information on NMS integration. Regardless of whether CMS is to be integrated with NMS or not, the CMS agents must be installed on each Cubix device to be managed as explained in this chapter.
CMS installation requires the following:
. The CMS console must be configured as a NetWare workstation with SNMP support.
. The CMS Servers and Databases must be installed on the CMS console.
. The CMS Administrators must be installed on the CMS console as part of the new Cubix Management System group.
. The CMS Administrators for the BC processors and BC Supervisors must be integrated into NMS (if NMS integration is to be performed).
. Each BC processor, QL processor, and BC Supervisor must be configured as a NetWare workstation with SNMP support.
. Each QL Supervisor installed on a NetWare file server or router must be equipped with SNMP support.
. A CMS agent must be installed on every Cubix device.
Before beginning the CMS installation, verify that all of the required components are available:
. Cubix Management System Diskettes (v1.00)
. CMS ODBC Setup Diskette (v1.00)
. CMS Console - this must be a computer that meets the minimal system requirements described under System Requirements
. Novell NetWare DOS Requester v1.2 or higher (includes VLM.EXE and STPIPX.COM)
NOTICE!<
The following files must each be version 1.2 or higher:
WSSNMP.VLM WSTRAP.VLM WSREG.VLM WSASN1.VLM MIB2IF.VLM STPIPX.COM
The CMS setup application places these files in an AGENTS subdirectory in the target installation directory on the CMS console. Note that VLM.EXE must be obtained from Novell.
. Novell NetWare SNMP Data Server v1.79 or higher
. Microsoft ODBC Driver Manager v1.05 or higher
Before beginning CMS installation, it may be necessary to update the software installed on Cubix network devices:
. QL Software - update all QL drivers to software v5.0 or higher, installing the NetWare DOS Requester architecture (VLMs, not NETX)
* Current QL drivers are available on the Cubix BBS.
. IES Supervisory Software - update all BC Supervisors to software v1.3 or higher; also install the NetWare DOS Requester architecture (VLMs, not NETX)
. BC Series Software - update all BC processors with v2.0 or higher of the BC Series Software; also install the NetWare DOS Requester architecture (VLMs, not NETX)
In addition, all Cubix devices being managed must use the NetWare Login Utility v4.00 or higher, which is distributed on the Cubix Management System Diskette. The login files must be updated on each server accessible by clients using QL and BC processors. If v4.0 or higher of the Login Utility is not used, agents installed on the QL and BC nodes will not be able to collect usage information for the Usage Server. Therefore, usage reporting will not be available.
NOTICE!
An additional restriction applies to users logging into a NetWare 4.x file server. Not only must v4.0 or higher of the Login Utility be used, but users must log in using the /b option which logs them in as bindery objects. If this option is not specified, usage reporting will not be available for the user's session.
System Requirements
The computer used as the CMS console must meet the following requirements:
. AT compatible 80486 or higher
. Minimum of 8 Mbytes RAM (12 Mbytes recommended)
. VGA or higher resolution video
. Microsoft Windows v3.1 or higher
. Minimum of 120 Mbyte hard disk drive (250 Mbytes recommended)
. Floppy disk drive (3.5") for installation only
In addition, the CMS console must be dedicated to running the CMS Servers. Servers are windows applications designed to run as minimized icons, making the system available for running other applications. The CMS Servers must always be running for CMS to avoid data loss.
The CMS console is a Windows-based PC that meets the specifications previously outlined in the System Requirements section. The CMS console must also be configured as a NetWare workstation running the NetWare DOS Requester v1.2 (or higher).
CMS uses the Microsoft ODBC database system to interface with the CMS Database, Alarm Database, and Usage Database. These databases are stored in Microsoft Access formats. Therefore, ODBC must be installed on the CMS console and configured to support Access database formats. ODBC installation instructions are included in the CMS console installation instructions below.
NMS Integration
If Novell's Management System (NMS) is installed on the network, CMS may optionally be integrated as a "snap-in" application for NMS. This requires installing CMS on the NMS console.
NMS displays network devices on the NMS network map. If CMS is integrated into NMS, the Cubix devices will be identified on the map with a Cubix icon. A new Cubix menu item will also be displayed on the NMS menu bar. When a Cubix device is selected (by clicking on the device icon), the appropriate CMS Administrator may be launched from the Cubix menu. For example, if a BC processor is selected, the Node Administrator for that BC may be launched. If a BC Supervisor is selected, the BCVision Administrator for that Supervisor may be launched.
Instructions to perform the integration are included in the CMS console installation instructions below.
NOTICE!
Snap-in applications for NMS are available only for Cubix BC Processors and BC Supervisors. Snap-in applications for the QL Processors and QL Supervisors are not included. Use CMS rather than NMS to manage the QL device types.
Installation Instructions
1. On the CMS console, run Windows. Insert the CMS ODBC Setup Diskette into the diskette drive. Select the File menu from the Program Manager and choose the Run option. Invoke the following application:
a:/setup
2. Select "Continue" from the opening screen.
3. Highlight "Access Data (*.mdb)" in the Available ODBC Drivers list and select OK.
4. If a Microsoft Access Driver that is older than the version supplied by Cubix is already installed on the CMS console, the existing driver will be replaced with the new version. If a driver is already installed that has the same version or a newer version as the driver supplied by Cubix, a prompt will be displayed. Respond to the prompt if necessary.
5. Select "Close" when asked to configure ODBC Data Sources.
! The CMS Setup application explained below will automatically configure the data sources required by CMS.
6. The Exit screen will be displayed. Select OK to exit.
7. Insert the Cubix Management System Setup Diskette (disk 1 of 2) into the diskette drive. Select the File menu from the Program Manager and choose the Run option. Invoke the following application:
a:/setup
8. Read the Installation Description and select OK.
9. Select a drive and path in which the CMS files will be placed. This location is the target directory.
10. The setup application will copy the CMS files into the target directory. In addition, a "Cubix Management System" windows group will be created in the Program Manager, and the Startup group will be modified to automatically load the server applications (CMS Server, Alarm Server, and Usage Server) every time Windows is invoked. The AUTOEXEC.BAT file will also be modified as follows:
- the PATH statements required by CMS will be inserted
- If the DOS SHARE.EXE utility is not already loaded on the CMS console, the following command will be inserted in AUTOEXEC.BAT:
SHARE.EXE /F:4096 /L:50
SHARE.EXE installs file sharing and locking capabilities. The /F parameter specifies the number of bytes used for file-sharing data, and the /L parameter determines the number of files that may be simultaneously locked. If SHARE.EXE is already installed on the CMS console, add these parameters to the invocation command (the CMS setup utility will not modify a pre-existing invocation of SHARE.EXE).
11. A prompt will be displayed to determine if CMS is to be integrated with NMS on this CMS console. Respond appropriately. If NMS integration is desired, the setup application will attempt to locate NMS on the CMS console. If NMS is not found, the CMS installation will abort.
12. If NMS integration is performed, an option to integrate the Cubix MIBs into NMS is available. Selecting this option allows the NMS alarm manager to recognize Cubix alarms. There are no other advantages to integrating the Cubix MIBs into NMS. Therefore, select this option if the ability to manage Cubix alarms with the NMS Alarm Manager is required.
HINT!
The agents installed on Cubix devices send SNMP traps to CMS. Most of these traps contain status information and do not indicate an alarm condition. NMS should be configured to ignore these traps as follows:
. From the NMS menu, select Fault.
. Select Alarm Disposition.
. Select the SNMP Family.
. Change the status of the Cubix Traps to "Informational". Do not log or display these alarms. Cubix Traps are identified as follows:
QL3 Supervisor Status
QL4 Supervisor Status
Cubix Trap (there are three traps with this identification)
13. Setup is complete. The CMS console will be rebooted to allow the changes in the AUTOEXEC.BAT file to take effect. Remember to modify the SHARE.EXE invocation command if required (refer to step 10).
14. Version 1.2 of the following files are now installed in the AGENTS subdirectory of the target directory on the CMS console:
WSSNMP.VLM
WSTRAP.VLM
WSREG.VLM
WSASN1.VLM
MIB2IF.VLM
VLM.EXE
STPIPX.COM
Copy these files into the directory containing the NetWare Client software.
15. Edit the NET.CFG file on the CMS console. The NetWare DOS Requester section of this file specifies the VLM files that will be loaded by VLM.EXE in addition to the standard VLMs (refer to NetWare documentation for instructions on loading the standard VLM files). In addition, any of the commands below not already included in the NetWare DOS Requester section must be added in the order specified.
NetWare DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
Sample files are included in Appendix B.
16. A Desktop SNMP section of the NET.CFG file similar to the following should also be included:
Desktop SNMP
enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Description"
sysLocation = "Location"
sysContact = "Contact"
snmpEnableAuthenTraps = on
where:
Description is a text description of the CMS console
Location describes of the location of the CMS console
Contact provides contact information for the CMS console
F These are standard MIB II fields.
17. On the CMS console, add the following commands to AUTOEXEC.BAT. Both files are included in v1.2 of the NetWare DOS Requester. VLM.EXE will load the VLM files specified in the NET.CFG file, and STPIPX.COM provides the SNMP support required by CMS.
vlm
stpipx
18. Reboot the CMS console so that the changes to AUTOEXEC.BAT and CONFIG.SYS take effect.
19. Run Windows. Verify that the SNMP Data Server, CMS Server, Alarm Server, and Usage Server icons are displayed, indicating that these processes are running as minimized applications.
20. CMS functions may be directly accessed via the Cubix Management System group (represented by an icon in the Program Manager), or via NMS (if NMS integration was performed).
NOTE!
No Cubix devices will be recognized by CMS until the agent installation is complete as described in the following sections.
To complete the installation:
. Install one Cubix agent as described in the Agent Installation section of this chapter.
. Verify that CMS recognizes the device with the agent installed.
. Repeat the two steps above for each Cubix device on the network.
. If NMS integration was performed, invoke the CMS-NMS Integrator (refer to the section below).
CMS-NMS Integrator
If NMS integration is selected during CMS installation, the CMS-NMS Integrator will be added to the Cubix Management System group. Otherwise, this application is not required.
NMS maintains a list of all devices on the network in a database. For CMS integration to function, CMS must update this database and instruct NMS to invoke CMS when the user wishes to manage a Cubix device. This is the function performed by the CMS-NMS Integrator.
Because devices may be added to and removed from the network, it is necessary to run the CMS-NMS Integrator periodically so that it can keep the NMS database up to date with Cubix device information. No automatic update function is provided. Note that the CMS-NMS Integrator will only recognize Cubix devices that are properly installed with the appropriate Cubix agent.
NOTICE!
It is the user's responsibility to run the CMS-NMS Integrator application periodically. It must be invoked as agents are installed on Cubix devices added to the network and also as Cubix devices are removed from the network. Running the application at least once a day is recommended.
An agent must be installed on each device to be managed by CMS. Instructions for installing the agent on each type of device are provided in the following sections.
Trap Configuration
All Cubix devices monitored by CMS generate status traps on a regular interval. This is the Trap Interval. The default trap interval is thirty seconds, but this default may be modified as explained in the following sections.
CMS traps are initiated by the agent on the device and transferred over the network to the CMS console. Therefore, each agent must be configured with the address of the CMS console, so that the agent knows where to send the status trap. This address is the Trap Target.
Before proceeding with the installation, it is necessary to determine the network address of the CMS console so that it may be configured as the Trap Target. To determine this address, log into the network from the CMS console and enter the command:
userlist /a
The current users and the network address of the workstation from which each user is logged in will be displayed. An asterisk will indicate the line describing the CMS console. Write the network address in the space provided below for later reference:
CMS Trap Target:
F The network address must be in the format xxxxxxxx:yyyyyyyyyyyy, where xxxxxxxx is an eight digit hexadecimal net number and yyyyyyyyyyyy is a twelve digit hexadecimal node number.
HINT!
It is recommended that one agent be installed to verify CMS functionality. Once CMS is running and successfully managing this one device, return to the agent installation instructions and install agents on the remaining devices.
BC Processors
There are four scenarios for BC processor agent installation:
. BC running DOS or Windows that is connected to an IES Supervisory System
. BC running DOS or Windows that is not connected to an IES Supervisory System
. BC functioning as a NetWare file server or router (running NetWare v3.x or v4.x) that is connected to an IES Supervisory System
. BC functioning as a NetWare file server or router (running NetWare v3.x or v4.x) that is not connected to an IES Supervisory System
F No other BC configurations are supported by CMS.
BC DOS/Windows Environment with IES
1. Verify that the following files are installed on the workstation in the directory containing the NetWare Client software:
WSSNMP.VLM
WSTRAP.VLM
WSREG.VLM
WSASN1.VLM
MIB2IF.VLM
CBXNODE.VLM
VLM.EXE
STPIPX.COM
All files except CBXNODE.VLM must be v1.2 or higher. Copy these files from the AGENTS subdirectory of the installation target directory on the CMS console if necessary.
2. Edit the NET.CFG file on the BC processor. The NetWare DOS Requester section of this file specifies the VLM files that will be loaded by VLM.EXE in addition to the standard VLMs (refer to NetWare documentation for instructions on loading the standard VLM files). In addition, any of the commands below not already included in the NetWare DOS Requester section must be added in the order specified.
NetWare DOS Requester
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = CBXNODE.VLM
Sample files are included in Appendix B.
3. Determine the network address of the BC Supervisor managing this processor (the BC Supervisor is the BC running the BCVision application). To determine this address, log into the network from the BC Supervisor and enter the command:
userlist /a
The current users and the network address of the workstation from which each user is logged in will be displayed. An asterisk will indicate the line describing the BC Supervisor. Write down the network address for later reference.
F The network address must be in the format xxxxxxxx:yyyyyyyyyyyy, where xxxxxxxx is an eight digit hexadecimal net number and yyyyyyyyyyyy is a twelve digit hexadecimal node number.
4. Determine the Data Highway Address of the IES module connected to this BC processor. This address is set with two rotary switches on the end bracket of the IES module. The address is also displayed in BCVision.
5. Determine the number of the group in the Cubix enclosure that contains this BC processor. The group number is displayed in BCVision.
6. Add the following section to the NET.CFG file:
Cubix Node Agent
TrapInterval = xx
SupervisorAddress = BC Supervisor Address
DataHighwayAddress = IES Address
Group = BC Group
DeviceType = BC
where:
xx is the trap interval in seconds (default is 30 seconds)
BC Supervisor Address is the address determined in Step 3
IES Address is the address determined in Step 4
BC Group is the number determined in Step 5
7. Add the following line to the Transport Provider IPX section of NET.CFG:
Transport Provider IPX
trap target = CMS Trap Target
where CMS Trap Target is the address written on page 3 - 11.
8. A Desktop SNMP section of the NET.CFG file similar to the following should also be included:
Desktop SNMP
enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Description"
sysLocation = "Location"
sysContact = "Contact"
snmpEnableAuthenTraps = on
where:
Description is a text description of this BC workstation
Location describes of the location of this workstation
Contact provides contact information regarding this workstation
F These are standard MIB II fields.
9. On the BC workstation, add the following commands to AUTOEXEC.BAT to activate the agent. Both files are included in v1.2 of the NetWare DOS Requester. VLM.EXE will load the VLM files specified in the NET.CFG file, and STPIPX.COM provides the SNMP support required by CMS.
vlm
stpipx
10. Reboot the BC processor so that the changes to AUTOEXEC.BAT take effect.
Continue to Chapter 3, part 2 of 2
This document, and all Web contents, Copyright © 1997
by Cubix Corp., Carson City, NV, USA.
