Intravue manual

When a device with this feature enabled re-connects to the network it becomes active in its perhaps new location without admin action. Laptop computers and other equipment that can be connected at a number of different locations should also have this feature enabled.

The event log will still document all connections made and lost. WAP all children wireless Enabling this check box causes any childrenn of this device to have a dashed line using the color that is appropriate for its line condition. This is automatically checked if the device is discovered to be a Wireless Access Point.

Enable Alarms to Device User If checked, any email alarms created by this device will go to the email address in the field ''Send To'' Send To This field is the email of the user that gets email for this particular device. The ''Enable Alarms to Device User'' checkbox must be enabled for this to work. Admin Verified When this is checked, the position of the device is frozen or locked to its current position.

If the device is moved, the IntraVUE browser will show a red filled box at the verified position and a tan box at the current location of the device. See a complete description about Admin Verification and its benefits. Unmanaged Switch or Wireless AP The checkbox will cause all peer devices of this device to become children of this device. It is provided as a convenience to using the MOVE function and works as new devices are discovered.

Many installations only have access to their local devices but not switches in other subnets or the router that bridges the subnets. This only works for switches. This is important for some devices which respond to SNMP but do not have a name or location configured. The Images Tab allows you to configure both thumbnail and icon images for all views in one dialog. Each view can have one thumbnail image and one icon image assigned to each device.

The display of the icons and images is turned on and off from the System Menu or by a setting in the ivserver. All images are assumed to be in the same file folder. The name of the image file is case sensitive. Users also copy images from manufacturer or other sites to the image directory and link those images to device views.

Browse To help you select an image, each icon and thumbnail has a Browse button. A list of all the available images located in the default location will be displayed and you can browse through the images and select an image to use as a thumbnail or icon.

In the Title column enter what you want users to see when they right click on a device. In the URL column enter the link to the page a view will see. There are two types of web pages that can be put in the URL column, local pages to the host and remote pages. Feel free to create new folders. You may have to create additional folders to store images that are referenced by the HTML file in relative paths. The other type of web link is to a page on a different computer.

As long as the users browsing to the IntraVUE host also have access to the other remote computer, you can link documents on other computers. NOTE: Filenames are case sensitive, check the case if the link does not seem to work. See the end of the file. The weblink below will open the IntraVUE browser on the Uppercase I and T set Icons and Thumbnails on, lowercase i and t set them off.

The view numbers are defined in the ivserver. There are several occasions when you may want to manually change the relationship between the devices shown on the IntraVUE browser dispaly.

You want to show non-IP address devices such as a copper to fiber media converter. You want show non-Ethernet devices such as serial devices that are connected through an Ethernet-to-Serial converter.

Unmanaged switches used to require manual moves but starting with version 2. Add Child This adds a new node under the selected device. This is typically used for devices connected via linking devices. The properties of the new node can be changed to reflect a device which is in the network but not visible to the scan engine. Typically, the other devices that are physically connected to the inserted node will be moved graphically to the new node using the MOVE function.

An event log entry is generated for this operation. There will be a black line connecting the new node. It will stay black unless an IP device is moved under it. Move Move allows the user to change the parent of a device. To make a move, first select the device you want to move. It will get a blue outline. While the device is still selected, right click on the parent device to which you want to move the device and select Move.

They may take the copper CAT5 cable and convert it to fiber or even wireless. A second device typically converts the signal back to copper. When doing this it is desireable to have the port of the managed switch be maintained. In the image below there is a port number for the line connecting the device. Use Add Child and add a child first to the device, and next to the just added child. You now have two unnamed child devices under the original device.

Now Delete the device with the IP address. It will be rediscoved and become a child under a NEW autoinserted node, at its original location. Next select the device it gets a blue outline and use Configure on the lowest child to MOVE the device below that node.

The auto-inserted node will go away, the connecting line to the first node will still have a port number, and the additional device nodes will help you understand you network when problems arise.

Example of Configuring a Bridge In the image below, the. The devices on the other side of the bridge will appear under the top bridge, along with the other end of the bridge. In this case, the. Select the. The devices on the other side of the bridge will now be under the. The image below shows the way IntraVUE will display an unmanaged switch having two devices connected to it. If a managed switch does not have its SNMP community set correctly it will appear the same.

The In order to show the network as it physically exists the administrator can select the Configure item from the unmanaged switches Device Menu. After a minute, the auto inserted node will go away as there is now only one device on the port of the managed switch and the other two devices are below it.. If you have a WAP that is not managed, you can check the checkbox yourself.

The result will be that all wireless devices will appear under the WAP and will have dashed, wireless, lines going to them. Virtual Machines If a host computer is setup with Virtual Machines, each VM will appear as a peer of the host, all under an auto-inserted node.

It will look just like an unmanaged switch. CleanDbBackup - files for creating a clean database. It also contains a batch file to create a clean database without a browser. Tools - utility programs. The Autoip folder contains many files. The data is stored in this file.

Details are found at ivserver. Any new items a user would like to use need to be copied to the ivserver. Details within the file. The 'tomcat5' folder under autoip contains all the files for the Apache Tomcat eTomcat web server. The only folder of interest to users is the root folder of the web server.

The root folder can be accessed from any computer browsing to the IntraVUE web server. Users are free to create their own content below this folder, including creating new folders.

The path to the root folder is Backing up files not in the MySql database backup file. This backup does not contain any content referenced by IntraVUE. In the event of a catastrophe, installing a new copy of IntraVUE from the installation CD and then restoring a saved backup will get you to where you were at the time of the backup. Content added by the user will not be in the backup. Other files that could be backed up via the Windows' backup application or by scheduled tasks might include: User created content User modifications to IntraVUE default files.

When the mysql database becomes large, these programs will lock critical resources longer than mysql can withstand. The result will be that mysql stops and consequently the Intravue scanner will not be able to make any updates until the mysql service is restarted via reboot or by the user. User created content can only be in the web server root folder described above. All user created content is preserved during upgrades. Backup the entire root folder to save any content you have added. There are some additional files that also contain configuration data.

Note that checking the Enable Autoip checkbox will cause an entry to be added to this file, but unchecking it will not cause it to be removed. You can only remove an entry using the AutoIP user interface or editing this file in a text editor. Each parameter is preceded by an explanation using the comment sign at the start of each line.

The line starting without a sign is the actual parameter in use. Note that when an upgrade is installed, the original ivserver. The ivserver. Follow the link for more details. All configuration is done in this file which is also self documenting in the form of comments. Note: the full capabilities of trapmailer are complex and require an effort to understand. Section 5. The ping and threshold data will be as if the Intravue host computer was located in the isolated network. Some OEM systems such as packaging machines or bottling machines contain their own private Ethernet networks.

These systems typically use the same IP addresses for each function in the system. When you have multiple systems using the same IP addresses it is impossible to monitor networks inside the systems with traditional networking tools. Isolated Networks. The Agent is connected to a switch inside the 'system' using one port of the agent and the other port of the agent is connected to a switch on the 'plant' side.

VLAN Access. A switch within the 'system' is configured with 2 vlans. The IntraVUE Agent has one interface connected to a 'system vlan' port of the switch and the other agent Ethernet interface connected to a 'plant vlan' port of the same switch. This file is located in the autoip folder of IntraVUE, normally Each of the parameters that can be set in this file contains a description of the parameter and a sample line showing the default value.

These are shown as comment lines in the file. Comment lines start with a ' ' character and have no effect. This file typically contains configuration items that are not normally changed by IntraVUE users or administrators.

Open the file with notepad or wordpad to view the various options or to make changes. Any settings already applied will not be changed. The new items will be set to their default states. It is located in the The actual name used is user configurable in the ivserver. An administrator could then setup several different trunking files for testing and other purposes. A side benefit of using the 'trunkingdefs.

The 'trunkingdefs. The format is simple. A switch is designated using square braces, [ ], around its IP address. This is followed by one or more lines of port assignments until the next set of square braces.

On the left is the port as known to the switch. On the right is how IntraVUE should treat and display that port. Many ports on the left can be assigned to the same number on the right.

If a number is repeated on the left, the last one will be used. Example 1 - Normal Case The Previously any device could affect the state and the state only changed after acknowledgment. Change bandwidth data to favor a managed switch as the source of the device, for more reliable data.

Made improvements to decrease the time it takes to get SNMP data from a managed switch by more than an order of magnitude. The IntraVUE installer no longer requires the dongle during installation. Minor fixes to dongle discovery mechanism. Minor changes to Supervisor event collecting.

Minor improvements in the scanner. Supervisor module - Fixed memory leak and event handling when a satellite IntraVUE's database is restored. Added logic to purge even some non-repetitive events from the event log. The installer uses admin mode in all cases.

Fixed bug starting at 2. Made sorting of the icons and thumbnail image names case insensitive when browsing for images. Added change of name to the event log, and also to event purging list. Refined and improved handling of 'generate support archive' to avoid security issues in the browser.

Fixed bug which could cause continuous automatic backups for monthly backups. Improved merging of top parent's auxiliary IP addresses. Added more logic to handle extremely unusual RSTP ring reversal use cases. Fixed bug which occurred when a device was in more than one IntraVUE network and it was deleted in one, it would reincarnate itself even if it was no longer in that network's scan range.

Ensure the scanner clears its memory of the bridge mib for a disconnected switch. Fixed SQL exception on optimized threshold logic. Fixed use of forward slash and backslash characters in support property files. Implemented a new feature for netbooks and technician laptops that automatically configures a new top parent and starts scanning a new network every time the host computer gets a new IP address. Any previous, meaningful data is automatically saved using logical file names before the new scan starts.

Fix problem where an internal Interface could have a mac address but no ip address. Fixed bug where email authentication was being lost because a wrong index had been used in the database. Adjusted size of dialogs for netbook screens. Removed momentary 'license exceeded' message when restoring a database. Fixed checking for Admin privileges on Windows 7 type machines.

Avoid problems when there are multiple versions of the Java Runtime Environment Fixed bug where peak values were not correctly calculated for the 15 to hour data. Introduce 'network group' concept to handle the case where multiple private networks have the same IP ranges. Record both peak and average values of ping and bandwidth to make it more convenient to troubleshoot issues older than 6 hours.

Network selection URL now explicitly 'shows' networks as well as 'hiding' them. Add 'link comment' facility which allows users to document wiring, unusual port numbering, ports of unmanaged switches, or any other text to appear as part of a connecting line's hover text. Arrange that the event log is systematically 'trimmed' to remove repetitive messages for a single device, resulting in much smaller database files. Add 'user archive' facility, where an enhanced system snapshot is taken and may be automatically transferred to an FTP server or user's browser.

Add French language help. Implement facility to allow agents on a network to be discovered regardless of IP address and have IP settings reconfigured.

Corrected bug which caused incorrect behavior when adding more than one network at once. Arrange that the list of networks and scan ranges entered is kept in order of insertion. Save all important user files and restore as part of an upgrade. Uses series of backup folders, 'prev' etc. Allow merging of user-entered changes to a new ivserver. Also, retains site license header. Warn user to make a backup before performing an upgrade. Correct focus issues on entering a password cursor already in the correct field.

Improve default settings for trapmailer. Avoid SQL exceptions when recording thresholds after a host computer system time change. Tune innodb parameters to avoid performance problems with larger databases and limited memory. Avoid change of MAC messages when using a virtual router. Correct bug which occasionally failed to detect missing devices. Arrange for Pelco and Supervisor software to be delivered on standard CD. Arrange that MySQL, ivserver, tomcat services auto-restart after any failure.

Block attempts to perform the manual move from one IntraVUE network to another. Support user-modifiable system default settings for threshold values. Handle situation better where a link on display has threshold data from both parent and child. Adjust both, suppress one. Support multiple email addresses on device disconnect. Arrange that 'backup' can be done without requiring admin privilege.

Avoid permanent ghost nodes on ring reversal by clearing 'admin verified' marker if a device is detached to avoid circular structure. Ensure large trap messages are truncated appropriately to store in the event log. Ensure displayed thresholds have consistent time ranges. Allow direct upgrade of systems from previous full release only 2. Otherwise prompt for explicit uninstall first. Enhance 'data not current' warning on graphic display to indicate the probable reason, specifically loss of dongle.

Improve license count detection and display. Arrange to pre-purge very large databases at the time of restore to avoid excessive memory use at startup.

Change applet jar file names on each release to avoid Java cache issues on client browsers. Improve timeout mechanism for JAVA detection to allow for slow startups. Make oidval table purge timing adjustable, not fixed 60 secs. Upgrade dongle driver to work with Windows 7. Change the name of UD3 from 'Diagnostics'. Install should block if the old version of MySQL is present and require a manual removal.

Microsoft deliverable file msvcr Fixed problem where 'public' was configured as the SNMP community for all devices without a community when Apply and CLose is executed. Added ghost nodes Red boxes with dashes in the IP to the Search results so you can easily find the current and previous location of a device.

Minor bug fixes. Allow installation by Domain administrators. Avoid exception of a device and its parent is manually deleted within the same scan cycle. Prevent screen update before a restored database is fully restored. Removed some MySQL operations which caused some dialogs to take a very long time to display. Avoid a problem which could cause the threshold data to grow without being averaged, resulting in huge database files.

Implemented feature to disable SNMP data for name and location of a device. Added ignoring the bridge mib and all SNMP. Provide the ability to learn MACs from switches, avoiding the need to access a router if only switch macs are needed. Avoid spurious event log entries if a device is disconnected and then the database is restored and the device is still disconnected. Ensure consistent reported of interfaces for routers that appear in more than one IntraVUE network.

Allow a device to be designated a 'managed hub' in which case all its peers will become children. Intended primarily for Wireless Access Points, but also useful for web-managed switches, Virtual Machines, and other situations.

Handle the case where a Layer 3 switch is a top parent and it is also switching. Allow suppression of SNMP name and location data.