Global Vision - Frequently Asked Questions

GlobalVision
Frequently Asked Questions
& Troubleshooting Tips
(Last Update: 12/15/97 ADM)

1. 1:	ODBC installation cannot find one of the ODBC files in the \GV directory.
1. 2:	Network Communications Failure
1. 3:	An Error Occurred While Accessing the Registry
1. 4:	Agent Conflict
1. 5:	A Memory Exception Occurred
1. 6:	SNMP Services Failure
1. 7:	GlobalVision Agent Status Inactive
1. 8:	Remote GlobalVision Console Already Exists
1. 9:	Cannot Set GlobalVision Offline
1.10:	Could Not Communicate with Remote GlobalVision Console
1.11:	SNMP Trap Trouble
1.12:	Remote GlobalVision Console will not Expand
1.13:	The SNMP Subsystem Could not be Initialized
1.14:	System Information Not Shown in GlobalVision Console
1.15:	Client Name/Login Duration Information not being displayed
1.16:	Agent Status not showing "In Use" while user is logged in.
1.17:	The Filter Dialog Could not be Created
1.18:	The Requested Report Could not be Completed
1.19:	An Error Occurred While Accessing the Usage Database

2.1:	No IES Clock
2.2:	Processor Inactive or Keeps Resetting
2.3:	Firmware API Invalid
2.4:	Download Unsuccessful
2.5:	Could Not Read/Open Firmware File
2.6:	Invalid Firmware Checksum
2.7:	IES Configuration Unsuccessful

4.1:	The Selected File does not Exist in the Given Path
4.2:	The Name of the Sound or Command File is Invalid
4.3:	The Alarm Subsystem failed to Initialize
4.4:	Unable to Access the Alarm Database

Q1.1: ODBC installation cannot find one of the ODBC files in the \GV directory.

A1.1: When you install the ODBC files, you must select the "CUSTOM" option, and select only some of the available options. See the GlobalVison "Quick Start Guide" for the correct steps, or follow the steps in the NotePad README file during the ODBC installation.

A1.2: GlobalVision tried to send/receive a request or trap, but was unsuccessful. The problem may be that a remote GlobalVision console is no longer running, or the system is low on memory. Ensure that all GlobalVision consoles in the Global View are running, and the system is not low on memory.

A1.3: GlobalVision tried to access the registry, but the key in the registry was not found. The registry may be corrupt. Un-install GlobalVision, then re-install it. This should bring back any keys in the registry that have been lost.

A1.4: Two or more GlobalVision agents are reporting the same IES Data Highway Address and Group Number for this GlobalVision Console. Check the configuration of the agents on the BC processors with the conflict.

A1.5: GlobalVision tried to perform an action that required it to allocate memory, but, there was not enough free memory to allocate. Try shutting down other applications and trying the action again. If the problem persists, you may have to add more memory to your system.

A1.6: GlobalVision tried to perform an SNMP action and it failed. The most likely cause is lack of free memory. Try shutting down other applications and trying again. If the problem persists, the CBXSNMP.DLL file may be corrupted in the GlobalVision directory. Un-install GlobalVision, then re-install it.

A1.7: If the status of the GlobalVision Agent for a processor is "inactive" then the local GlobalVision Console is not receiving SNMP status traps from the GlobalVision Agent running on the processor. Make sure that the trap target for the agent is the correct network address of the local GlobalVision Console.

If the status of the GlobalVision Agent is fluctuating between "active" or "in use" and "inactive" the agent trap interval needs to be set with the GlobalVision Agent Trap Interval Dialog. See also Q2.2

A1.8: A Remote GlobalVision Console already exists with the specified network address. Each Remote GlobalVision Console may only be added to the hierarchical tree once.

A1.9: A BC processor with "GlobalVision" anywhere in the description cannot be set offline. Consider carefully how the processor running GlobalVision is going to be set back online since GlobalVision will not be available to set itself back online. If the node still must be set offline change the description and set the node offline.

A1.10: This message is displayed when an SNMP request sent to the Remote GlobalVision Console has timed out waiting for a response. There are several causes for communication failure between two GlobalVision consoles, following are the more common:

If this message is displayed while the Remote GlobalVision Console is being set up for the first time the address of the Remote GlobalVision Console may have been entered incorrectly. Make sure that the network address is correct. Alternatively, the time-out value may need to be increased if there is a great distance or network time lag between the two consoles.

If this message is displayed after communication between the two consoles has been established the Remote GlobalVision Console may not be running or there may be a physical break in the network between the two consoles.

A1.11: All of the GlobalVision Agents send status traps to the Local GlobalVision Console. These traps should be limited to the LAN by specifying a trap target that is on the LAN. The frequency of these traps may be reduced to once every 5 minutes (300 seconds) by configuring the agents. Note that the Agent Trap Interval Dialog must be used to configure the expected frequency of traps on the GlobalVision Console.

While a Local GlobalVision Console is in fault it will send SNMP traps to the other GlobalVision Consoles if it has been requested to do so via the Receive Alarms From option once every 30 seconds to indicate that it is alarmed. To stop the traps clear the fault condition.

A1.12: This GlobalVision Console may not be able to communicate with the Remote GlobalVision Console. If this is the case a message should show up in the status bar of this GlobalVision application. See "Q1.10: Could Not Communicate with Remote GlobalVision Console"

Alternatively, the Remote GlobalVision Console may not have anything to expand. Make sure that the GlobalVision Console acting as the remote still has devices listed.

A1.13: The SNMP subsystem could not be initialized. Make sure no SNMP services are running on the system. If GlobalVision was just shut down and restarted GlobalVision may still be in the process of shutting down. Wait a few seconds and try running GlobalVision again. No more than one session of GlobalVision may be running at a time.

A1.14: GlobalVision defaults to "public" as your SNMP community string. Use the following steps for community strings other than "public":

1. From the GV console main menu, select Network, and SNMP Community String.
2. Type in the Community string that you wish that GlobalVision console to be a member of.

1. Open the Control Panel Icon from the Main Program Group.
2. Open up the Network Icon.
3. Highlight the SNMP service under Installed Network Software.
4. Select either Configure or Properties.
5. Make sure the Community name of the GlobalVision console is in the Community Names box, and The GlobalVision consoles address is in the List of Addresses to trap to.
6. Click on Securities.
7. Make sure the GlobalVision console Community string is in the Accepted Community Names box.
8. Close all the network dialog boxes.
9. From Control Panel, select Services.
10. Highlight the SNMP service, and select STOP.
11. After SNMP has stopped, make sure it is highlighted, and select START.
12. This NT agent should now be sending traps to the GlobalVision console.

1. From the START button, select Programs->GlobalVision Agent->SNMP Configuration Utility.
2. Make sure that the name of the GlobalVision consoles community string is in the list of community strings, and its address is in the list of addresses to trap to for that community.
3. Open the Registry Editor (REGEDIT.EXE).
4. Open the following keys:
HKEY_LOCAL_MACHINE
System
CurrentControlSet
Services
SNMP
Parameters
Valid Communities
5. Highlight Valid Communities, to the right should appear a list of communities.
6. If the name of the GlobalVision consoles community is not in this list, add it. NOTE: the name of the values, add one to the last value in the list, name the new value that.
7. From a DOS prompt, type SNMP -CLOSE, then type SNMP.
8. This agent should now be trapping to the GlobalVision console.

A1.15: If using the DOS/Win 3.x agent, make sure you are using LOGIN.EXE version 4.0 or later. Also, user must be logged in using bindery mode (i.e. LOGIN [username] /b)

A1.16: If using the DOS/Win 3.x agent, make sure you are using LOGIN.EXE version 4.0 or later. Also, user must be logged in using bindery mode (i.e. LOGIN [username] /b)

A1.17: A command (Generating a Usage Report or Clearing the Usage Database ) was requested, but the Usage Filter Settings dialog could not be created. The most likely cause is low system memory.

A1.18: A Usage Report was requested from a Remote GlobalVision Console, but either the GlobalVision console is no longer running, its address was entered incorrectly, or the retry or time-out value was not set appropriately. Ensure that the GlobalVision console is still running. If it is, ensure that its IP/IPX address is entered correctly. If both of these conditions are met, try adjusting the retry and time-out values for that GlobalVision console.

A1.19: GlobalVision cannot open the Usage Database, or cannot access it. The cause is most likely a corrupt Usage Database file. Close GlobalVision, and from the File Manager, copy the default Usage Database (located in the GlobalVision directory\DEFAULT path) into the GlobalVision directory (make sure that you copy it and not move it - this file should exist in both directories). Run GlobalVision again. If the problem persists, un-install GlobalVision and install it again.

A2.1: The selected IES is not equipped with a real-time clock. The date and time could not be set. The current date and time from the GlobalVision Console is used instead.

A2.2: IES modules constantly poll the BC processors Supervisory Interrupt to monitor the processors’ status. Polling consists of generating an interrupt on the processors, repeating the poll as set by the poll-interval. If the processor fails to respond to a poll within one second, the IES will detect a processor failure. If CPR is enabled, the processor will be reset, otherwise the processor will be reported as inactive.

1. Poll-interval is too short. Increase the poll interval by right-clicking on the IES node and choosing "Configure..." in GlobalVision's "Global View" tree.

2. Interrupt Conflict. Make sure no other device is using the same interrupt as the Supervisory Interrupt (default: IRQ 15). The Supervisory Interrupt can be set to either IRQ 10 or IRQ 15 via switch settings on the processor board. Refer to your BC or DP Series documentation for switch settings.

Note: if using a processor with a PCI chipset, make sure the interrupt chosen (IRQ 10 or 15) is set to ISA/EISA in the CMOS setup under "PCI/Plug and Play Setup". For processor boards with two IDE channels enabled, use IRQ 10 for the supervisory interrupt (eg. DP6200 & BC Triton Series)

3. Software/Hardware Mismatch. Make sure the physical switch settings for Supervisory Interrupt on the BC or DP board match with the IRQ specified in the Agent installation or BCSETUP.SYS command line. Refer to your BC or DP Series documentation for switch settings.

A2.3: The IESFRMWR.BIN firmware file contains a version of the firmware that is not compatible with your version of GlobalVision. Reinstall IESFRMWR.BIN to the GlobalVision installation directory.

A2.4: The firmware could not be downloaded to the IES module. Make sure that the IES Data Highway is connected properly. If an IES Data Highway address was specified make sure that the address is correct.

A2.5: The IESFRMWR.BIN firmware file could not be opened. Reinstall the IESFRMWR.BIN file to the GlobalVision installation directory.

A2.6: The checksum of the firmware in the IESFRMWR.BIN file is invalid. Reinstall the IESFRMWR.BIN file to the GlobalVision installation directory.

A2.7: The IES could not be configured properly. Make sure the IES Data Highway is connected properly. As a last resort:

1. Invalidate the firmware on the IES through the menu option on the IES node in the Global View tree.

2. Select "Add IES" from the local GlobalVision Console or wait for the IES to be automatically discovered.

For BCSETUP.SYS, use the -i=n parameter in the CONFIG.SYS file to specify the interrupt desired. If the -i parameter is not used, the default is IRQ 15. Only IRQ 15 or IRQ 10 may be used.

Example for DOS/Win 3.x:
DEVICE=BCSETUP.SYS -i=10 (for Supervisory Interrupt 10)

Example for Windows 95:
DEVICE=BCSETUP.SYS -M -i=10 (for Supervisory Interrupt 10)

Note that the -M parameter is used to disable multiplexed mouse support since Windows 95 uses CBXMOUSE.VXD instead.

Also, make sure the physical switch settings on the processor board match this interrupt. Refer to the BC or DP documentation for switch settings.

A4.1: The filename of the sound file or batch file is either missing or invalid. Open the Announcement Options Dialog by right clicking on the local GlobalVision console icon, selecting alarm, and selecting Announce Options from the resulting menu. Ensure that the pathways and names of the sound and batch files are legitimate. Ensure that at least one alarm is selected as either playing a sound file or executing a batch file.

A4.2: The filename of the sound file or batch file is either missing or invalid. Open the Announcement Options Dialog by right clicking on the local GlobalVision console icon, selecting alarm, and selecting Announce Options from the resulting menu. Ensure that there are valid filenames entered in the Sound and Executable edit boxes. Ensure that at least one alarm is selected as playing a sound file or executing a batch file.

A4.3: GlobalVision did not initialize. This message should be preceded by another message that gives the exact reason the Alarm Administrator did not initialize. Refer to that message for further information.

A4.4: GlobalVision cannot open the Alarm Database , or cannot access it. The cause is most likely a corrupt Alarm Database file. Close GlobalVision, and from the File Manager, copy the default Alarm Database (located in the GlobalVision directory\DEFAULT path) into the GlobalVision directory (make sure that you copy it and not move it - this file should exist in both directories). Run GlobalVision again. If the problem persists, un-install GlobalVision and re-install it.

This document, and all Web Site contents, Copyright �
2000 by Cubix Corp., Carson City, NV, USA.