 |
|
|
|
Cubix
Management System
Chapter 3 - Installation
BC processors not attached to an IES module may be monitored by CMS. However, the control functions available via CMS that are available on processors associated with a BC Supervisor or a QL Supervisor will not be available on BC processors with no IES. This is because the control functions performed on BC processors are implemented through the IES attached to the BC. Control functions include the ability to reset a processor, force a processor online/offline, etc.
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. Add the following section to the NET.CFG file:
Cubix Node Agent
TrapInterval = xx
DeviceType = BC
where xx is the trap interval in seconds (default is 30 seconds)
4. 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.
5. 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.
6. 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
7. Reboot the BC processor so that the changes to AUTOEXEC.BAT take effect.
BC Running NetWare with IES
For a BC running NetWare to be managed by CMS, a DOS application must be run on the BC. This application is the Cubix NetWare Preload Utility (CBXNWPLU.EXE). The Preload Utility will create a data file, CBXNWPLU.DAT, in the root directory of the C: drive. After NetWare is loaded, a Cubix NLM (CBXNDNW.NLM) must be loaded. This NLM is the agent used to communicate management information to the CMS console.
The Preload Utility needs to be run before the agent NLM is loaded for the first time. The utility does not need to be run again unless the hardware configuration on the BC processor is changed (more memory is added, disk drives configurations are changed, etc.).
1. Verify that the CBXNWPLU.EXE utility is installed in the root directory of the C: drive. If necessary, copy CBXNWPLU.EXE from the AGENTS subdirectory of the installation target directory on the CMS console.
2. Add the command to the AUTOEXEC.BAT file to execute this utility on reset:
cbxnwplu
3. Reset the BC. Verify that the file CBXNWPLU.DAT is created in the root directory of the C: drive.
4. Determine the network address of the BC Supervisor managing this processor. 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.
5. 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.
6. Determine the number of the group in the Cubix enclosure that contains this BC processor. The group number is displayed in BCVision.
7. Load NetWare on the BC processor being configured.
8. Create a file named CBXNODE.INI containing the following information in the SYS:/ETC directory of the BC processor:
[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
* No white space characters (spaces, carriage returns, etc.) may precede these lines in the CBXNODE.INI file.
Sample files are included in Appendix B.
9. Create a file named TRAPTARG.CFG in the SYS:/ETC directory of the server or router (or edit the file if it already exists). The Trap Target address of the CMS console, written on page 3 - 11, must be specified in the ProtocolIPX section of this file.
10. If no SNMP.CFG file exists in the SYS:/ETC directory, create one similar to the following:
Name
Description
Hardware
Hardware Platform
Location
Location
Contact
Contact
where:
Description is a text description of this BC file server or router
Hardware Platform describes the server/router hardware
Location describes of the location of this BC
Contact provides contact information regarding this BC
* These are standard MIB II fields.
11. Install CBXNDNW.NLM in the SYS:SYSTEM directory. CBXNDNW.NLM is located in the AGENTS subdirectory of the installation target directory on the CMS console.
12. Verify that the Novell SNMP.NLM is installed in the SYS:SYSTEM directory. Load SNMP.NLM.
13. Load the CBXNDNW agent NLM.
* The CBXNDNW NLM accesses the CBXNWPLU.DAT file. Therefore, if DOS is to be unloaded on this server or router, CBXNDNW.NLM must be loaded before DOS is unloaded.
BC Running NetWare with No IES
For a BC running NetWare to be managed by CMS, a DOS application must be run on the BC. This application is the Cubix NetWare Preload Utility (CBXNWPLU.EXE). The Preload Utility will create a data file, CBXNWPLU.DAT, in the root directory of the C: drive. After NetWare is loaded, a Cubix NLM (CBXNDNW.NLM) must be loaded. This NLM is the agent used to communicate management information to the CMS console.
The Preload Utility needs to be run before the agent NLM is loaded for the first time. The utility does not need to be run again unless the hardware configuration on the BC processor is changed (more memory is added, disk drives configurations are changed, etc.).
1. Verify that the CBXNWPLU.EXE utility is installed in the root directory of the C: drive. If necessary, copy CBXNWPLU.EXE from the AGENTS subdirectory of the installation target directory on the CMS console.
2. Add the command to the AUTOEXEC.BAT file to execute this utility on reset:
cbxnwplu
3. Reset the BC. Verify that the file CBXNWPLU.DAT is created in the root directory of the C: drive.
4. Load NetWare on the BC processor being configured.
5. Create a file named CBXNODE.INI containing the following information in the SYS:/ETC directory of the BC processor:
[CUBIX NODE AGENT]
TrapInterval = xx
DeviceType = BC
where:
xx is the trap interval in seconds (default is 30 seconds)
* No white space characters (spaces, carriage returns, etc.) may precede these lines in the CBXNODE.INI file.
Sample files are included in Appendix B.
6. Create a file named TRAPTARG.CFG in the SYS:/ETC directory of the server or router (or edit the file if it already exists). The Trap Target address of the CMS console, written on page 3 - 11, must be specified in the ProtocolIPX section of this file.
7. If no SNMP.CFG file exists in the SYS:/ETC directory, create one similar to the following:
Name
Description
Hardware
Hardware Platform
Location
Location
Contact
Contact
where:
Description is a text description of this BC file server or router
Hardware Platform describes the server/router hardware
Location describes of the location of this BC
Contact provides contact information regarding this BC
* These are standard MIB II fields.
8. Install CBXNDNW.NLM in the SYS:SYSTEM directory. CBXNDNW.NLM is located in the AGENTS subdirectory of the installation target directory on the CMS console.
9. Verify that the Novell SNMP.NLM is installed in the SYS:SYSTEM directory. Load SNMP.NLM.
10. Load the CBXNDNW agent NLM. This should be added to the AUTOEXEC.NCF file so that the CMS agent is automatically loaded every time the server is booted.
* The CBXNDNW NLM accesses the CBXNWPLU.DAT file. Therefore, if DOS is to be unloaded on this server or router, CBXNDNW.NLM must be loaded before DOS is unloaded.
QL Processors
By definition, QL processors are running DOS (and optionally Windows). The QL Supervisor NLM is required, so there is no option to configure a QL processor without QL Supervisor support. Instead, the configuration scenarios for QL processors depend upon whether a hard disk drive is installed on the workstation.
QL Equipped with a Disk Drive
Installing the agent on a QL equipped with a hard disk drive requires changes to the files on the disk. This is most simply performed by attaching a monitor and keyboard to the QL workstation. Refer to the QL Series Hardware Installation Guide for instructions on monitor and keyboard installation.
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 QL processor. The NetWare DOS Requester section of this file specifies the VLM files that will be loaded by VLM.EXE. The standard VLMs should already be listed in this section (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 QL Supervisor managing this processor. To determine this address, enter the following command on the NetWare console where the QL Supervisor NLM is loaded:
config
The value displayed as the "IPX Internal Network Number" represents the net address of the QL Supervisor. The node address is one. Construct the node address in the format xxxxxxxx:000000000001, where xxxxxxxx is the eight digit hexadecimal net number displayed on the console and 000000000001 is a twelve digit representation of the node number.
Write down the network address for later reference.
4. Add the following section to the NET.CFG file:
Cubix Node Agent
TrapInterval = xx
SupervisorAddress = QL Supervisor Address
DeviceType = QL
where:
xx is the trap interval in seconds (default is 30 seconds)
QL Supervisor Address is the address determined in Step 3.
5. 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.
6. 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 QL workstation
Location describes of the location of this workstation
Contact provides contact information regarding this workstation
* These are standard MIB II fields.
7. On the QL 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
8. Reboot the BC processor so that the changes to AUTOEXEC.BAT take effect.
QL Not Equipped with a Disk Drive
Diskless workstations boot from an image file rather than a disk drive. Follow the instructions below to configure a diskless QL workstation for CMS management.
Default Image File
A default image file is included with the QL software v5.0. This default image file is configured to load the CMS agent. The default file makes one assumption: that the file server designated as the server from which the QL processors will boot is also the server in which the boards are physically installed. If the default image file is being used, and this assumption is correct, no changes to the image file are required.
However, if the assumption stated above is not correct, or if a custom image file is being used instead of the default file, the image file will require modification. To modify the default image file, perform only steps 3 and 4 below. Alternatively, if the default image file has been replaced with a custom image file, modify the custom image file beginning with step 1 below.
NOTICE!
Changing an image file requires using the Novell DOSGEN utility. Instructions for modifying image files are included in the QL Series Technical Reference Guide. If any changes to the image file are required, please refer to these instructions.
1. The following files must be included in the image file in the directory containing the NetWare Client software:
WSSNMP.VLM
WSTRAP.VLM
WSREG.VLM
WSASN1.VLM
MIB2IF.VLM
CBXNODE.VLM
VLM.EXE
NET.CFG
All files except CBXNODE.VLM and NET.CFG 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. The NET.CFG file in the image file must contain the following commands in the NetWare DOS Requester section. The NetWare DOS Requester section of this file specifies the VLM files that will be loaded by VLM.EXE. The standard VLMs should already be listed in this section (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 QL Supervisor managing this processor. To determine this address, enter the following command on the NetWare console where the QL Supervisor NLM is loaded:
config
The value displayed as the "IPX Internal Network Number" represents the net address of the QL Supervisor. The node address is one. Construct the node address in the format xxxxxxxx:000000000001, where xxxxxxxx is the eight digit hexadecimal net number displayed on the console and 000000000001 is a twelve digit representation of the node number.
Write down the network address for later reference.
4. Add the following section to the NET.CFG in the image file:
Cubix Node Agent
TrapInterval = xx
SupervisorAddress = QL Supervisor Address
DeviceType = QL
where:
xx is the trap interval in seconds (default is 30 seconds)
QL Supervisor Address is the address determined in Step 3,
5. 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 QL workstation
Location describes of the location of this workstation
Contact provides contact information regarding this workstation
* These are standard MIB II fields.
6. In addition to the NET.CFG file contained in the image file, a second NET.CFG file exists in the SYS:/LOGIN directory of the file server with the image file. Add the following line to the Transport Provider IPX section of this NET.CFG file:
Transport Provider IPX
trap target = CMS Trap Target
where CMS Trap Target is the address written on page 3 - 16.
7. Copy STPIPX.COM into SYS:/LOGIN. STPIPX.COM is included in the NetWare DOS Requester v1.2. STPIPX must be loaded after VLM.EXE by the QL workstation. Commands to load these files reside in the files QL3BOOT.BAT (for QL 3000 Series products) and QL4BOOT.BAT (for QL 4000 Series products) included in v5.0 of the QL Series Software. They are included here for informational purposes only. The commands are as follows:
vlm.exe /Mx
stpipx.com /c=f:net.cfg
* Command line parameters must be specified as shown.
8. Boot the QL workstation so that the changes in the NET.CFG file take effect.
BC Supervisor
By definition, a BC Supervisor is running the BCVision application. Beginning with v2.0, the agent required to manage a BC Supervisor is integrated into the BCVision software. To support CMS, the BC Supervisor itself must be configured as a NetWare workstation. Install an appropriate version of BCVision on the BC Supervisor, and follow the instructions below to complete the CMS integration.
1. Verify that the following files are installed on the BC Supervisor in the directory containing the NetWare Client software:
WSSNMP.VLM
WSTRAP.VLM
WSREG.VLM
WSASN1.VLM
MIB2IF.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 Supervisor. 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. 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 - 16.
4. 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 Supervisor
Location describes of the location of this Supervisor
Contact provides contact information regarding this Supervisor
* These are standard MIB II fields.
5. On the BC Supervisor, 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
6. Reboot the BC processor so that the changes to AUTOEXEC.BAT take effect.
QL Supervisor
By definition, a QL Supervisor is an NLM running on a NetWare file server or router containing QL processors. Beginning with v5.0, the agent required to manage a QL Supervisor is integrated into the QL Supervisor NLM. In addition to installing an appropriate version of the NLM, create a file named TRAPTARG.CFG in the SYS:/ETC directory of the server or router (or edit the file if it already exists). The Trap Target address of the CMS console, written on page 3 - 16, must be specified in the ProtocolIPX section of this file.
Before loading the QL Supervisor NLM, load Novell's SNMP.NLM. SNMP.NLM provides SNMP support on the server or router on which it is loaded. SNMP.NLM must be loaded using the command line parameters specified below:
load snmp.nlm Trap = Control =
where no value is specified for either Trap or Control. Also, the capitalization of both Trap and Control must be entered as shown.
Note: The QL software will create a QL3.INI or QL4.INI file depending upon the type of QL Supervisor installed. The Trap Interval is configured in this INI file as thirty seconds. This value may be modified by changing the following line in the INI file:
TRAPINTERVAL = xx
where xx is the desired trap interval in seconds.
Do not change the format or case of this line. Do not change any other lines in the QL3.INI or QL4.INI file.
* If the file server or router on which the QL Supervisor is installed is a Cubix BC board, configure the BC for node management as described in the BC Processor installation section earlier in this chapter.
At this point the CMS installation is complete. The following steps have been performed:
. The CMS console is configured as a NetWare workstation with SNMP support.
. The CMS Servers and Databases are installed on the CMS console.
. The CMS Administrators are installed on the CMS console, and they are accessible via the Cubix Management System group.
. The CMS Administrators for the BC processors and BC Supervisors are integrated into NMS (if NMS integration was performed).
. Each BC processor, QL processor, and BC Supervisor is configured as a NetWare workstation with SNMP support.
. Each QL Supervisor is installed on a NetWare file server or router with SNMP support.
. A CMS agent is installed on every Cubix device.
This document, and all Web contents, Copyright © 1997
by Cubix Corp., Carson City, NV, USA.
