GlobalVision
Quick Start Guide

GlobalVision is equipped with an extensive help system; therefore, this manual will not attempt to document the user interface of GlobalVision. Instead this manual will provide an overview of the GlobalVision architecture and instructions for GlobalVision installation.

Overview

GlobalVision is the Cubix management system for managing Cubix devices in a LAN/WAN environment. GlobalVision provides monitoring, alarming, supervisory control, and usage reporting from a central management console. GlobalVision provides all network communications using SNMP (Simple Network Management Protocol).

Cubix Device Types

GlobalVision manages five types of devices.

• Cubix Processor
• Cubix QL Series Processor - Cubix single board computer designed specifically as a NetWare workstation.
• Intelligent Environmental Sensor (IES) - a hardware component installed in Cubix processor enclosures. The IES monitors the enclosure environment and any Cubix processors installed in the enclosure. Each IES is equipped with an interface to a Cubix data highway. This is an out-of-band highway that connects up to thirty-one IES modules to the GlobalVision Console.
• SafeStor/FT II Intelligent Environmental Sensor (IES) - a hardware component installed in a SafeStor/FT II hard drive enclosure. The IES monitors the enclosure environment and the hard drive groups in a SafeStor/FT II enclosure. Each IES is equipped with an interface to a Cubix data highway. This is an out-of-band highway that connects up to thirty-one IES modules to the GlobalVision Console.
• QL Supervisor - NetWare Loadable Module (NLM) that manages QL processors installed in a single NetWare file server or router. The QL Supervisors monitor network communications and the status of the QL processors. For each type of QL processor, QL 3000 Series or QL 4000 Series, installed in a NetWare file server or router, there must be an associated QL Supervisor NLM loaded.

Components

GlobalVision consists of two main software components.

• GlobalVision Console Software
• GlobalVision Agents and IES Responders (installed on each Cubix device managed by GlobalVision).

Figure 1 Functional Relationship of GlobalVision Components

GlobalVision Console Software

A GlobalVision Console is a Windows NT workstation running the GlobalVision application. The GlobalVision application provides the user interface for the management of Cubix devices. A GlobalVision Console also collects and stores data from the GlobalVision Agents. Multiple GlobalVision Consoles can communicate with each other and share information. A user at a GlobalVision Console can manage devices that are physically attached to the Console and also devices which are attached to remote GlobalVision Consoles.

Additionally, each GlobalVision Console maintains two databases: the Alarm Database and the Usage Database. The Alarm database stores alarms that have occurred on the IES modules that are physically attached to the GlobalVision Console and any alarms that have been reported by QL Supervisors associated with the GlobalVision Console. The Usage Database stores usage information on the Cubix processors that are associated with the GlobalVision Console. A GlobalVision Console can access information from the local database and a remote GlobalVision Console’s database in the form of reports.

GlobalVision Agents and IES Responders

Cubix processors managed by GlobalVision require a SNMP Agent and an IES Responder driver.

SNMP Agents

In order for GlobalVision to receive usage and inventory information from Cubix processors, a SNMP Agent must be installed on each processor. Alarms are also generated by these agents in the form of SNMP traps.

• DOS/Windows 3.x Agent - provides status, inventory, and usage information from Cubix processors running DOS or Windows 3.x
• Windows NT Agent - provides status, inventory, and usage information from Cubix processors running Windows NT
• Windows 95 Agent - provides status, inventory, and usage information from Cubix processors running Windows 95
• NetWare Agent - provides status and inventory information from Cubix processors running as a NetWare file server or router
• QL Supervisor Agent - provides QL Supervisor status and QL-related alarms

Note that the GlobalVision Console serves as a proxy SNMP Agent for the IES Module and provides IES status and IES-related alarms.

IES Responder drivers

The IES Responder drivers running on the Cubix processors support GlobalVision by responding to the IES status poll. The driver used depends on the operating system installed on the processor. Refer to Agent Workstation Setup for additional information about each driver.

Before You Begin

The GlobalVision Console application is installed on any Intel x86 based desktop system running Windows NT (v3.51 or greater, Workstation or Server).

Before you begin, ensure you have the following diskettes:

• GlobalVision Console - 4 diskettes
• GlobalVision DOS/Windows Agent - 1 diskette
• GlobalVision Windows NT/95 Agents - 2 diskettes
• GlobalVision NetWare Agent Diskette - 1 diskette

Installation Procedure

Console Physical Installation

To install the IES Data Highway, consult the hardware installation guide for the Cubix product containing the IES module.

Console Software Installation

Preliminary

Install TCP/IP or IPX/SPX protocols before installing the GlobalVision Console.

The GlobalVision Console installation provides the option of installing Microsoft ODBC files. Ignore instructions for installing these files if Microsoft ODBC has been previously installed.

Remove or disable the SNMP Service if it has been previously installed.

Installation Instructions

1. Insert disk 1 into the floppy drive and select File then Run from the Program Manager menu bar.
2. Type a:\setup and click OK. The GlobalVision installation program will load and display a Welcome screen
3. Click on Next> after reading the Welcome screen.
4. Select the GlobalVision Files and Microsoft ODBC checkboxes, then select Next>.
5. Select OK when the SNMP Information dialog is displayed.
6. Type your name and company and click on Next>.
7. Select Next> when prompted for the installation directory.
8. Select the Program Folder where you wish to install GlobalVision icons, then select Next>.
9. Select Next> when the Start Copying Files dialog is displayed. Insert disks 2 through 4 when prompted.

If you did not choose to install ODBC files, skip to step 19.

10. Select OK when the ODBC Setup Information dialog is displayed.
11. If ODBC has previously been installed on this workstation, click on the Add/Remove option. Otherwise, click Continue at the ODBC license agreement screen.
12. Choose the Custom install option.
13. From the Custom setup screen, click on Continue.
14. If ODBC was previously installed, click OK to exit the ODBC Setup program and skip to step 18. Otherwise, continue with step 15.
15. From the Choose Program Group setup screen, click on Continue to choose the default for the program group.
16. From the Data Source setup screen, click on Close.
17. Click on OK to exit the ODBC Setup program.
18. When prompted, select Delete ODBC Installation Files and then Next>.
19. When prompted, select Finish. You may optionally select Yes, I want to view the ReadMe file now.
20. Start GlobalVision Console by double-clicking on the GlobalVision Icon in the GlobalVision Group.

Configuration of Remote GlobalVision Consoles

In addition to managing the devices connected to a GlobalVision Console it is possible for one GlobalVision Console to manage the devices connected to other GlobalVision Consoles across a LAN or WAN. This management includes not only the ability to see and manipulate devices across the LAN or WAN, but also the ability to receive and display alarms across the LAN or WAN. In order for this management to take place a "connection" must be made between two GlobalVision Consoles. In the following discussion a "Local GlobalVision Console" is the console from which you are working. A "Remote GlobalVision Console" is any other GlobalVision Console on the LAN or WAN. To Create a "connection" between a Local GlobalVision Console and a Remote GlobalVision Console perform the following:

On the Local GlobalVision Console:

1. Right click on "Cubix Enterprise".
2. Select "Add Remote GlobalVision Console" from the pop-up menu.
3. Enter the IP or IPX address of the GlobalVision Console to be managed. A remote console icon will now be added to the "Cubix Enterprise" tree.

To receive alarms from a remote GlobalVision Console perform the following:

1. Right click on a remote console icon.
2. Select "Alarm...", then "Receive Alarms from..." from the pop-up menus.
3. The IP/IPX address of the remote console will appear in an edit box at the top left of the "Receive Alarms from" Dialog. Click on the Add button to add this remote console to the list of consoles from which you receive alarms.
4. Select the alarms you want forwarded to you from the list of alarms on the right of the dialog box.

Note: Any GlobalVision Console can act as either a Local or Remote GlobalVision Console simultaneously. Thus, it is possible for two GlobalVision Consoles to monitor each other’s devices. Additionally, any GlobalVision Console can monitor multiple Remote GlobalVision Consoles.

Note: A GlobalVision Console that is not managing any devices locally should not be configured as a Remote GlobalVision Console because it has nothing to be managed. This console could be used to manage other GlobalVision Consoles, however.

Agent Workstation Setup

The following sections explain the installation of the GlobalVision Agent (and any required support files) for the DOS/Windows 3.x, Windows95, Windows NT, and NetWare operating systems.

Before You Begin

Before you begin installing GlobalVision Agents you should have the following information available:

Install Directory - Location where GlobalVision files will be installed.

GlobalVision Console Address - For IPX networks this is the network number and MAC address of the NT station where GlobalVision is installed. For example:

00000080:0020940200D5

For TCP/IP networks, this is the IP address, of the NT station where GlobalVision is installed.

128.135.127.201

(Refer to the section Determining the IPX or IP Address of the GlobalVision Console.)

Trap Interval - The frequency, in seconds, at which the GlobalVision Agent sends trap information to the GlobalVision Console. Thirty seconds is suggested.

IES Address - The IES (Intelligent Environmental Sensor) Data Highway address (1 - 31) assigned to the processor board. This address is set with either two rotary switches on the end bracket of the IES module for the ERS/FT and ERS II or one DIP switch on the surface of the IES for the ERS/FT II or SafeStor/FT II. For more information regarding setting the Data Highway Address refer to the hardware installation manual for the subsystem being used.

Group - The backplane group (segment) number
(1 - 8) where the processor board is installed. The group number is displayed on the front panel of the enclosure.

DOS and Windows 3.x

The Cubix DOS IES Responder, CBXIES.SYS, supports GlobalVision by providing the primary status for Cubix processors. The Cubix SNMP Agent for DOS provides status, inventory and usage information to the GlobalVision Console.

Preliminary

Remove write protection from the GlobalVision DOS/Windows Agent diskette before performing the following procedure.

Installation Instructions

1. Boot to the DOS prompt, i.e. C:\.
2. Insert the GlobalVision DOS/Windows Agent disk in the floppy drive, type A:\ and press ENTER.
3. At the A:\ prompt, type setup.exe and press ENTER.
4. Follow the instructions to install the IES Responder and the SNMP Agent.

Windows 95

The Cubix DOS IES Responder, CBXIES.SYS, supports GlobalVision by providing the primary status for Cubix processors. The Cubix Windows 95 SNMP Agent provides status, inventory and usage information to the GlobalVision Console.

Installation Instructions

Note: The Windows 95 SNMP service is required by the GlobalVision Windows 95 Agent. The SNMP service is automatically installed by the Cubix Windows NT/95 Agent Setup.

1. Boot the Agent processor and start Windows 95.
2. Insert the Windows NT/95 Agents disk 1 into the floppy drive.
3. Select Start and then Run from the Taskbar.
4. When prompted, type A:\setup in the Run window entry field and press Enter.
5. Follow the instructions to install the IES Responder and the Windows 95 SNMP Agent.

Windows NT

The Cubix NT IES Responder, CBXIES.SYS, supports GlobalVision by providing the primary status for Cubix processors running Windows NT. The Cubix SNMP Agent for Windows NT provides status, inventory and usage information to GlobalVision.

Note: The Windows NT SNMP service is required by the GlobalVision NT Agent. Install and configure the SNMP service before installing the GlobalVision Windows NT Agent.

To configure the SNMP Service for Windows NT:

1. Select Network from the Control Panel
2. Select SNMP Service.
3. Select "Configure" (NT 3.51) or "Properties" (NT 4.0).
4. Set the community name. The GlobalVision default community name is "public" (case sensitive).
5. Enter the IP or IPX address of the GlobalVision Console as a trap destination. (Refer to the section Determining the IPX or IP Address of the GlobalVision Console.)

Installation Instructions

1. Boot the Agent processor and start Windows NT.
2. Insert the GlobalVision Windows NT/95 Agents disk 1 into the floppy drive.

Windows NT 3.51:

1. From the "Program Manager" window, select File, and then Run. To start the Agent setup program, type A:\setup and press Enter.

Windows NT 4.0:

1. Select Start and then Run from the Taskbar.
2. When prompted, type A:\setup in the Run window entry field and press Enter.
3. Follow the prompts provided by the Setup program to install the IES Responder and the Windows NT SNMP Agent.

NetWare

Primary status of Cubix Processors used as NetWare file servers is provided by two separate IES Responder drivers. CBXIES.SYS is the responder for DOS, and CBXIES.NLM is the responder for NetWare. The Cubix SNMP Agent for NetWare is CBXNDNW.NLM. In addition, there is a preload utility, CBXNWPLU.EXE.

Installation Instructions

Install will copy CBXIES.SYS and CBXNWPLU.EXE to your root directory. Install will modify your CONFIG.SYS to load CBXIES.SYS and will execute CBXNWPLU.EXE to create the data file CBXNWPLU.DAT.

1. Boot to the DOS prompt of your NetWare server.
2. Insert the GlobalVision NetWare Agent disk in the floppy drive, type A:\ and press ENTER.
3. At the A:\ prompt, type cd install and press ENTER.
4. At the A:\install prompt, type install.exe and press ENTER.
5. Follow the prompts provided by the Install program to install the IES Responder.
6. Boot your file server.

Setup Instructions

Setup will create CBXNODE.NCF and will copy CBXNDNW.NLM and CBXIES.NLM to your root SYSTEM directory. Setup will create CBXNODE.INI and modify TRAPTARG.CFG in your ETC directory.

1. Log in from a workstation connected to your file server.
2. Insert the GlobalVision NetWare Agent disk in the floppy drive, type A:\ and press ENTER.
3. At the A:\ prompt, type cd setup and press ENTER.
4. At the A:\setup prompt, type setup.exe and press ENTER.
5. Follow the prompts provided by the Setup program to install the NetWare IES Responder and SNMP Agent.
6. Update your AUTOEXEC.NCF file to load CBXNODE.NCF (in SYSTEM) or add the lines in CBXNODE.NCF to your AUTOEXEC.NCF file.

Note: If the old IES Responder, BCACTIVE.NLM, is loaded by AUTOEXEC.NCF, it should be removed. Previous references to SNMP.NLM should also be removed from AUTOEXEC.NCF.

7. Down your server, then bring it back up to load the IES Responder and NetWare SNMP Agent.

Sample Files for Cubix Processor Setup

The following pages provide sample NET.CFG files for IPX and IP support on the DOS/Windows Agent Workstation. Sample CBXNODE.INI, and TRAPTARG.CFG required by Cubix Processors running NetWare are also included.

NET.CFG for IPX Support on DOS//Windows Workstation

Link Driver PCNTNW

Frame Ethernet_802.3

NetWare DOS Requester

checksum = 0
FIRST NETWORK DRIVE = F
PREFERRED SERVER=ADMIN1
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = CBXNODE.VLM

Cubix Node Agent

TrapInterval = 30
DataHighwayAddress = 14
Group = 7
DeviceType=BC

Transport Provider IPX

trap target = 00000017:0001c05df05f

Desktop SNMP

enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Suzanne Marshall x294"
sysLocation = "Building 2"
sysContact = "suzanne@admin.com"
snmpEnableAuthenTraps = on

NET.CFG for IP Support on DOS/Windows Workstation

Link Driver PCNTNW

Frame Ethernet_II

NetWare DOS Requester

CHECKSUM=0
FIRST NETWORK DRIVE=F
VLM = WSSNMP.VLM
VLM = WSTRAP.VLM
VLM = WSREG.VLM
VLM = WSASN1.VLM
VLM = MIB2IF.VLM
VLM = CBXNODE.VLM

Desktop SNMP

enable monitor community = any
monitor community = "public"
enable control community = specific
control community = "public"
enable trap community = specific
trap community = "public"
sysName = "Lab #5"
sysLocation = "Lockheed.CarsonCity.USA"
sysContact = "702.888.1000"
snmpEnableAuthenTraps = on

Transport Provider UDP

trap target = 129.1.0.3

Cubix Node Agent

TrapInterval = 30
DataHighwayAddress = 14
Group = 7
DeviceType=BC

Link Support

Buffers 8 1500
MemPool 4096

Protocol TCPIP

PATH TCP_CFG C:\IPNET\TCP
ip_address 129.1.0.2
ip_netmask 255.255.00.00
ip_router 129.1.0.1

NWIP

NWIP_DOMAIN_NAME NWIP.DOPEY.COM.
NSQ_BROADCAST ON
NWIP1_1 COMPATIBILITY OFF
AUTORETRIES 1
AUTORETRY SECS 10

CBXNODE.INI for NetWare File Server

[CUBIX NODE AGENT]

TrapInterval = 30
DataHighwayAddress = 31
Group = 1
DeviceType = BC

TRAPTARG.CFG for NetWare File Server

#####################################################
# traptarg.cfg
#
# SNMP Agent Trap Target ( Destination) Configuration
#
# File format:
#
# Protocol <name>
# Specifies the beginning of a list of names or
# addresses of managers to which to send traps using the
# protocol specified by <name> if that protocol is
# registered as a service provider to the SNMP Agent.
#
# All destinations must be preceded by white space
# Each destination must be listed on a separate line.
#
# The Protocol keyword, left justified, signifies the
# start of a new protocol section.
#
# Comments are preceded by the hash mark, and proceed
# to the end of the line.
#
#####################################################

Protocol IPX

# In this section you can put SNMP managers that want to receive
# traps from the local node over IPX. Managers can be identified
# by NetWare service name (a NetWare filer server name, for example)
# or by IPX address

00000007:00001b0ad24d
00000007:0000c099f05f
00000007:00001b404622
00000007:0000c08ff05f

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
# name. By default, the local node sends traps at least to itself

Support File Installation for QL Series Processors

GlobalVision Support

GlobalVision requires QL Series Installation Disk V5.05 or higher.

QL Supervisor

1. By definition, a QL Supervisor is an NLM running on a NetWare 3.1x or 4.x file server or router containing QL processors. The agent required to manage a QL Supervisor is integrated into the QL Supervisor NLM.
2. On the file server or router containing the QL boards, edit the following file (if the file does not exist, create it):

   SYS:\ETC\TRAPTARG.CFG

3. Enter the address of the GlobalVision Console. (Refer to the section Determining the IPX or IP Address of the GlobalVision Console).
4. Before loading the QL Supervisor NLM, load Novell’s SNMP.NLM. SNMP.NLM provides SNMP support on the server or router in which it is loaded. SNMP.NLM must be loaded using the command line parameters specified below:

Trap=<community name> Control=<community name> Monitor=<community name>

5. The GlobalVision Console will default to the "public" community string. The community string is case sensitive.

Note: The QL software will create a QLX.INI file. The Trap Interval is configured in this INI file as 30 seconds. This value may be modified by changing the following line:

[QL SUPERVISOR AGENT]

TRAPINTERVAL=XX

where XX in the desired trap interval in seconds (300 max.)

 

Determining the IPX or IP Address of the GlobalVision Console

To determine the IPX address of the GlobalVision Console in a NetWare environment, log on to the network from the GlobalVision Console and enter the following command from a DOS window.

ipxroute config

The following similar information will be displayed.

Net:1 network number 0000007, frame type 802.3

device AMDDCNI (00209404048A)

Thus, the IPX address of the GlobalVision Console is 0000007:00209404048A

You also can enter this 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 address of the GlobalVision Console. Write down the network address for later reference.

Alternatively, the IPX node address can be determined by selecting Windows NT Diagnostics from the Administrative Tools Program Group, and selecting Network. The node address is the twelve-digit hex address listed under Transports.

F Important: The IPX 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.

To determine the IP address of the GlobalVision Console, select Control Panel from the Main Program Group, select Network, then TCP/IP Protocol, and finally, Configure. The IP address is listed in the TCP/IP configuration dialog.

The IP network address must be in the format xxx.xxx.xxx.xxx, where xxx is a decimal number between 0 and 255.

This document, and all Web contents, Copyright © 1997 by Cubix Corp., Carson City, NV, USA.