User's Guide
Notice Enterasys Networks reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Enterasys Networks to determine whether any such changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice.
IRM-3, Media Interface Module, MicroMMAC, MIM, MMAC, MMAC-3, MMAC-3FNB, MMAC-5, MMAC-5FNB, MMAC-8, MMAC-8FNB, MMAC-M8FNB, MMAC-Plus, MRX, MRXI, MRXI-24, MultiChannel, NB20E, NB25E, NB30, NB35, NBR-220/420/620, RMIM, SecureFast Switch, SecureFast Packet Switching, SFS, SFPS, SPECTRUM Element Manager, SPECTRUM for Open Systems, SPIM-A, SPIM-C, SPIM-F1, SPIM-F2, SPIM-T, SPIM-T1, TPMIM, TPMIM-22, TPMIM-T1, TPRMIM, TPRMIM-36, TPT-T, TRBMIM, TRMM-2, TRMMIM, and TRXI are trademarks of Cabletron Systems, Inc.
NFS, PC-NFS, SPARC, Sun Microsystems, and Sun Workstation are registered trademarks; and OpenWindows, SPARCstation, SPARCstation IPC, SPARCstation IPX, Sun, Sun-2, Sun-3, Sun-4, Sun386i, SunNet, SunOS, SunSPARC, and SunView are trademarks of Sun Microsystems, Inc. OPEN LOOK and UNIX are registered trademarks of Unix System Laboratories, Inc. Ethernet, NS, Xerox Network Systems and XNS are trademarks of Xerox Corporation ANNEX, ANNEX-II, ANNEX-IIe, ANNEX-3, ANNEX-802.
(d) Any other rights or limitations regarding the use, duplication, or disclosure of this computer software are to be expressly stated in, or incorporated in, the contract. (e) This Notice shall be marked on any reproduction of this computer software, in whole or in part.
Contents Chapter 1 Introduction Using This Guide ............................................................................................................. 1-1 Getting Help..................................................................................................................... 1-2 Using On-line Help................................................................................................... 1-2 Accessing On-line Documentation ...........................................................
Contents Editing the Backup Configuration File ................................................................... 2-33 Performing a Backup .............................................................................................. 2-34 Restoring Files from a Backup Set ......................................................................... 2-35 Restoring Default Files ...........................................................................................
Contents Selecting Node Information to Display .................................................................. 4-11 Node Information Options............................................................................... 4-12 Selecting a Display Font......................................................................................... 4-14 Selecting the Nodes to Display: Using Filters........................................................ 4-15 Filter Categories .......................................
Contents Chapter 6 Creating Network Maps Working with Maps.......................................................................................................... 6-1 About the Map View................................................................................................. 6-2 About Submap Icons................................................................................................. 6-3 About GoTo Symbols ..................................................................................
Contents Saving Maps ........................................................................................................... 6-62 Deleting Maps and Folders..................................................................................... 6-62 Chapter 7 Node Management Overview Device Management ........................................................................................................ 7-1 Launching Device Management .....................................................................
Contents xii
Chapter 1 Introduction Using this guide; getting help Using This Guide This manual contains general information regarding NetSight Element Manager, including: • Chapter 1, Introduction, which introduces the product, provides an outline of this book’s structure, describes how to access and use the on-line documentation, and tells you how to get assistance while using the product.
Introduction • Chapter 5, Tree Views, describes the Tree View workspace and windows. These userconfigurable views let you display your network nodes in a hierarchical tree control format that provides a variety of information about the features supported by the device, including information about the interface through which NetSight Element Manager is communicating with each node.
Introduction Accessing On-line Documentation NOTE All of the online help windows use the standard Microsoft Windows help facility. If you are unfamiliar with this feature of Windows, you can select Help —>How to Use Help from the primary NetSight Element Manager window. The complete suite of documents available for NetSight Element Manager can be accessed via a menu option from the primary window menu bar: Help —> Online Documents.
Introduction Mailing Address: Enterasys Networks, Inc. Technical Support 35 Industrial Way Rochester, NH 03867 FTP: ftp.cabletron.
Chapter 2 Overview of NetSight Element Manager Key NetSight Element Manager features; customizing the NetSight Element Manager platform; backing up data files NetSight Element Manager for Windows™ provides a powerful and easy-to-use tool for monitoring and managing Enterasys and Cabletron devices from a Microsoft Windows workstation. Its open architecture and broad feature set also make it an attractive platform for third party development of management applications.
Overview of NetSight Element Manager any actions that you have configured on reception of a particular trap or event. Alarm and event management is highlighted in Alarm and Event Handling, beginning on page 2-11. • The Scheduler tool allows you to schedule unattended data back-ups and network discovery sessions that will launch automatically at a scheduled time and date.
Overview of NetSight Element Manager Toolbars can be undocked to become floating tool palettes (either inside or outside the main window) or be docked to a different place. The Workspace can also be undocked, and placed either inside or outside the main window. Views can be minimized, but must remain in the main window area. Hint text displays here when you move the cursor over any toolbar button.
Overview of NetSight Element Manager • Right-mouse button functionality for quick access to commonly-used menu commands (as shown in Figure 2-2). Clicking the right mouse button in NetSight Element Manager windows or workspaces, or on elements in those windows, will often bring up a menu with commonly used management selections. Figure 2-2. Sample Right Mouse Functionality • Print spooling to the Microsoft Windows Print Manager for record keeping purposes.
Overview of NetSight Element Manager IP or Host Locator An additional tool linked to but run separately from the Discover application allows you to resolve host names to IP addresses, and vice versa. You can also discover the IP addresses and host names of all devices located on a subnet, and locate both the IP and hostname for a device by its MAC address.
Overview of NetSight Element Manager List Views The List View workspace allows you to view and create specialized lists of the devices in your central node database. A default set of views is provided for you; you can also create your own views, selecting both the nodes and the information about each node you wish to display. Figure 2-3 illustrates a sample List View workspace and an associated List View window. Figure 2-3.
Overview of NetSight Element Manager The List View Workspace Individual List Views are represented as icons within the List View workspace; these icons are arranged in a standard tree hierarchy (using a standard Microsoft Windows tree view control). Double-clicking on a List View icon within the tree opens its associated List View window. The List View workspace also provides organizational structure to your List Views.
Overview of NetSight Element Manager Figure 2-4. Sample Tree View Workspace and Associated Tree View Window Each node icon in a Tree View window is presented at the top layer in the tree hierarchy.
Overview of NetSight Element Manager Map Views Map View windows in NetSight Element Manager provide a third — and perhaps the most flexible — means for viewing information about your network. Using maps, you can create a visual representation of your network: grouping devices by location rather than function, and using a variety of graphical tools (including bitmap backgrounds and drawn objects) to represent connections and other pertinent information about the physical structure of your network.
Overview of NetSight Element Manager Log Views NetSight Element Manager provides a Log View workspace, which contains information about traps and software events. Like the other workspaces, the Log View workspace — illustrated in Figure 2-6 — allows you to create, access, and organize the Log View windows which provide the foundation of alarm and event management.
Overview of NetSight Element Manager When you exclude a node from the central node database, that node is no longer displayed in any view, and is moved to the Excluded Nodes database. Though these nodes can no longer be displayed or managed, they are protected from re-discovery, and they can be re-included in the central node database at any time. Excluded nodes can also be deleted entirely.
Overview of NetSight Element Manager Remote Administration Tools Remote Administration Tools is a utility suite which allows you to conveniently perform routine management tasks on a single device — or on a group of devices — from your remote workstation, rather than requiring local terminal access to each device. Among these tasks are: • Configuring TFTP and BOOTP sessions with a selected device or device group.
Overview of NetSight Element Manager MIB Tools The MIB Tools suite of MIB browsing and editing tools comprises: • The MIB Browser — a simple graphical interface you can use to contact and query SNMP nodes on your network and examine their supported MIBs (as long as the MIBs are imported into the MIB Tools database). MIB Browser also lets you conveniently perform SETs on contacted devices. • MIB Details — a display of the descriptive information for management objects that you query from a node.
Overview of NetSight Element Manager Figure 2-7. The Options Window (with Workspace Options Selected) Workspace Options The Workspace options (displayed by default, as illustrated in Figure 2-7) control various settings for the NetSight Element Manager interface. You select or deselect each option by clicking the associated checkbox. A checked box indicates that the associated option is selected; a blank box indicates that option is deselected.
Overview of NetSight Element Manager Autofill Community Name fields When this option is selected, the community name text set via the Network options (or via the Welcome Wizard) will be automatically entered in any field that requires a community name.
Overview of NetSight Element Manager Figure 2-8. The Network Options NetSight Element Manager uses the Community Name to gain access to devices that you want to manage. You specify the community name you want to use to access a device when the device is inserted (as documented in Chapter 4, List Views) or discovered (as documented in Chapter 3, Discovering Nodes).
Overview of NetSight Element Manager IP Address Autofill As with community names, an IP address is required to add devices to, or modify existing devices in, the central node database. (The Insert Device and Device Discover Properties windows both have an IP address entry field.
Overview of NetSight Element Manager Figure 2-9. The Polling Options Node Polling Node polling establishes how often the contact status between NetSight Element Manager and the IP devices in your node database will be refreshed. You configure node polling by setting the interval for a polling cycle and the number of nodes that will be polled during that interval.
Overview of NetSight Element Manager window, as described in Configuring Node Interface Poll Settings in Chapter 4). This would override the polling refresh rate of the database (once per 50 seconds), by instead having NetSight Element Manager issue a once-hourly poll to that individual node. However, you cannot configure polling so that contact status with an individual node is refreshed more frequently than the refresh rate established by the Node database polling settings.
Overview of NetSight Element Manager Node Options The Node options (shown in Figure 2-10) let you configure the default contact poll settings that will be established when IP devices are added to the node database. Default Poll Settings Unlike the poll settings configured via the Polling Options tabbed page, the Node Options default poll settings determine the default poll values that will be assigned to each individual node via its Properties window.
Overview of NetSight Element Manager To change the interval (if desired): 1. Click in the Interval (sec) text field, and type in the poll interval to be used as a default when adding new devices. The range is from 5 to 9,999 seconds. Retries If individual device polling is in effect, this will determine the default number of times after a failed poll that NetSight Element Manager will re-poll a device before declaring it in a Critical (contact unavailable) state. To change the default Retries setting: 1.
Overview of NetSight Element Manager Figure 2-11. The Directories Options Map files This field specifies the default directory that is used when you save a map. You can either override the default value in the Save Map window as each new map is saved, or you can set a new default location here. Refer to Chapter 6, Creating Network Maps, for more information on creating and saving maps. The default directory is \NetSight Element Manager x.x\Maps. To specify the default Map directory: 1.
Overview of NetSight Element Manager Log files This read-only field indicates the directory used to store log files generated by NetSight Element Manager’s processes or applications (e.g., the alarm and event handling service). The default directory is \NetSight Element Manager x.x\Log. Executable files This read-only field indicates the directory whereNetSight Element Manager stores its executable files and dynamic link libraries (DLLs). The default directory is \NetSight Element Manager x.x\Bin.
Overview of NetSight Element Manager Chassis Manager Settings The Chassis Manager settings let you establish how the Chassis Manager and SmartSwitch/Matrix Chassis View applications poll a monitored device. There are two settings which you can configure: Poll Rate The interval, in seconds, at which the Chassis Manager or SmartSwitch/Matrix Chassis View will poll a device to check whether it is alive on the network (i.e., has a green contact status). To change the poll rate: 1.
Overview of NetSight Element Manager Figure 2-13. The Event Log Options Window You can establish an hourly purge of the event cache file by specifying that traps or events which meet certain conditions be deleted. These conditions are defined by three Event Log options you select or de-select by clicking in the associated checkbox. The fourth option — Set log size — allows you to control the overall size of the cache.
Overview of NetSight Element Manager To set the options in the Event Log Options window: 1. To activate the Clear deleted events, Clear acknowledged and closed events, or Clear normal and informational events options, click to check the appropriate selection. 2. To set a new event cache size: a. Click to check the Set log size option. Note that if this option is not selected, the cache size text field will not be editable. b. Click in the associated text field and type in the desired cache size.
Overview of NetSight Element Manager Figure 2-14. The Customize Window The top portion of the window allows you to define the menu pick, hint, and tool tip text that will label your new selection, as well as the graphic image that will be used as its tool bar icon. The lower portion of the window allows you to assign the appropriate executable and any necessary arguments; it also allows you to define certain launch parameters. You can use these same fields to edit any existing entry in the toolbar or menu.
Overview of NetSight Element Manager 2. In the edit box provided, enter the text you want to appear in the Tools menu for the new entry. Place an ampersand (&) before the character you’d like to use for the access key. NOTE If you select an access key that is already in use, a message window will note this when you try to enter your new item name. If you choose to configure an access key, it must be unique or the new Tools item cannot be added. 3.
Overview of NetSight Element Manager Figure 2-15. Select Image Window d. Click OK to save your image selection(s) and return to the Customize window. 6. Use the Browse button to the right of the Command field to locate the executable you wish to launch with your new Tools menu selection. The executable path and file name cannot be entered directly into the Command field; you must select it via the Browse window. 7.
Overview of NetSight Element Manager 9. In the Show field, use the drop-down list to select the default display mode for your tool application: Normally, Hidden, Minimized, or Maximized. 10. Click to select the Launch at Start-up option if you want this tool launched automatically with NetSight Element Manager. 11. Click OK to add your new option.
Overview of NetSight Element Manager TIP If you change the default Maps and/or Exported Files directory (via the Directories Options available in the Tools—>Options window), the Data File Manager will automatically back up any specified files that reside in the new default directories. Any files that reside in the original default directories, however, will no longer be backed up.
Overview of NetSight Element Manager • Subnet.dat — Subnet definitions • Tools.dat — Information on items in the Tools menu • Wrkspace.dat — Configuration of window placement and other appearance properties within the primary NetSight Element Manager window. • CSMIBDS.MDB — MIB database. • *.def and*.trapdef — Trap definition files. To access the Data File Manager: 1. Exit any current management sessions. NetSight Element Manager must be closed for the backup utility to operate. 2.
Overview of NetSight Element Manager Editing the Backup Configuration File When you perform a backup action, the Data File Manager looks in five directories in the \NetSight Element Manager x.x directory — \Data, \Bin, \Filters (and its automatically-created subdirectories), \Maps (or your configured Maps directory), and \Exports (or your configured Exported Files directory) — for the files and/or file types specified in the Backup Configuration File.
Overview of NetSight Element Manager To edit this list: 1. Create a file backup entry by using the text editor to type a new line that specifies the file name, or the *.XXX file extension (for all files of a similar type). Remember, only files in the five pre-set directories will be backed up, so you needn’t specify a path for any files you add to the list. 2. Save and exit the text file.
Overview of NetSight Element Manager 3. When the backup is complete, a successful backup message will be displayed. Click OK to exit this window and complete the backup procedure. NOTE If even one file listed in the Backup Configuration file could not be found, a message window opens noting that the backup operation failed. This doesn’t mean the entire operation failed; it just indicates the failure to back up the missing file.
Overview of NetSight Element Manager 2-36 Backing Up Data Files
Chapter 3 Discovering Nodes Accessing the Discover Manager window; creating and modifying Discover scripts; executing Discover scripts; the Discover process; starting the Discover Wizard; launching the Scheduler application; using the IP or Host Locator; using the Subnets window The Discover Manager application allows you to locate devices on a network. You can perform a Discover process within a specified range of IP (Internet Protocol) addresses, on an entire subnet, or on a combination of the two.
Discovering Nodes Figure 3-1. The Discover Manager Window The Discover Manager window lists all Discover scripts you have created, including their names, descriptions, and execution intervals. The Discover Manager window is the central interface through which you create new scripts and modify, execute, and delete existing scripts; from this window, you can also choose to run the Discover Wizard, and launch the Scheduler application.
Discovering Nodes To modify an existing Discover script: 1. In the Discover Manager window, highlight the script to be modified, and click Properties. or Click the right mouse button on the script to be modified, and select Properties from the resulting menu. The Discover Properties window, also illustrated in Figure 3-2, opens. Figure 3-2.
Discovering Nodes Using the Discover Properties window, you can name your script, enter an IP range for an IP Discovery process, and assign a community name. You can also define and select entire subnets for a Subnet Discovery, select a Script Filter for a discovery, and define the time interval at which your discovery will take place. Setting General Discover Properties The General page of the Discover Properties window is used to name and describe your Discover script (as shown in Figure 3-3).
Discovering Nodes 3. In the Description: field, enter a description of the Discover script. This description opens with the script’s name in the Discover Manager window, and may help you to select from among the available scripts. 4. Enter any additional information you wish to store about the script in the Notes: field. Note that this information is not displayed anywhere else. 5.
Discovering Nodes To define a Device Discovery script, you must specify a range of IP addresses to be queried and assign at least one community name that will give the Discover application read access to the devices you wish to discover. IP address ranges can be individually specified, or entire subnets can be selected; you can also combine subnets and specific ranges in a single script, as long as the total number of addresses to be queried does not exceed 2000.
Discovering Nodes NOTE Although you can define address ranges beginning with 0 and ending with 255 (for example, 132.117.18.0 to 132.117.18.255), devices at the .0 and .255 addresses will not be discovered. 4. If you wish to specify an address mask other than the default value, enter the desired address mask in the Address Mask field. The appropriate address mask depends upon your network configuration.
Discovering Nodes Subnets will be defined automatically each time a device is added to the node database (either manually or via a Discover script); they can also be defined manually, either via the Discover Properties window (as described in this section) or via the View—>Subnets window available from the NetSight Element Manager primary window menu bar. (See Using the Subnets Window, page 3-27, for more information about viewing subnets.
Discovering Nodes 3. If necessary, place the cursor in the Subnet Mask field and type the subnet mask for the subnet that you wish to discover. Note that the value set here will determine the number of IP addresses which are included in the defined subnet, regardless of whether or not this value correctly reflects the number of devices each of your subnets contains.
Discovering Nodes Figure 3-7. The General Page of the Subnet Properties Window 5. In the Description text box, enter a description for your subnet entry. This description is not displayed in the Discover Properties window, but will be displayed in the View—>Subnets window accessible from the primary window menu bar (see Figure 3-20 on page 3-28). 6. Enter any additional information about the subnet in the Notes text box. 7.
Discovering Nodes Defining a Community Name Once you have specified the IP addresses that will be queried during the Discover, you must supply the discover application with one or more community names that will provide at least Read access to the devices you wish to discover.
Discovering Nodes 4. To add another community name to your script, repeat steps 2-4. 5. Define your remaining Discover script parameters as explained in the following sections, or click OK to save your entries and return to the Discover Manager window. Selecting a Script Filter If you would like to further refine a device discovery script, you can add one of two Script Filters: one which restricts the discovery to Cabletron devices, and one which restricts it to devices which respond to an SNMP query. 1.
Discovering Nodes Setting a Discover Interval Defining a Discover Interval for your Discover script allows you to automatically start your script and determine how often (in minutes) your script will be automatically executed. The Discover Interval is defined using the Schedule page of the Discover Properties window (Figure 3-10), accessed by clicking on the Schedule tab.
Discovering Nodes Figure 3-10. The Schedule Page of the Discover Properties Window Executing Discover Scripts Once you have established the parameters for your Discover scripts, they are listed in the Discover Manager window (as shown in Figure 3-11), and can be executed at any time. 1. In the Discover Manager window, click to highlight the name of the Discover script to be executed, and click Execute.
Discovering Nodes You can’t execute a discover script while a Net Discover window is still open — either because there is a discover still in progress, or because the window was not closed when a previous discover completed. Figure 3-11. The Discover Manager Window You cannot execute a new discover session if a previous session is still running or if the Discover window from a previous session is still open.
Discovering Nodes The Discover Process Once a Discover script has been manually executed, the Discover Manager window closes, and the Network Discover window (Figure 3-12) opens. Figure 3-12. Network Discover Window A discover proceeds in a single phase: each IP address in the defined address ranges and/or subnets is queried in turn; as each response is received, information about the responding device (including status, model, name, and IP address) appears in the Discover window.
Discovering Nodes NEW and SECONDARY Discovers Discovery sessions are divided into two types: NEW and SECONDARY. The first time you run a device discover script, all IP addresses in the subnet or address range you have specified will be queried, and all discovered devices will be listed in the discover window and automatically added to the central node database. This is called a NEW Discovery.
Discovering Nodes Re-starting a completed discover script from the Network Discover window has the same effect as re-executing the script from the Discover Manager window. Scheduled Discovers A scheduled discover script — one which launches automatically at selected intervals — behaves a little differently than a manually-executed script. Once a scheduled discover is complete, the Network Discover window will close automatically; you need not close it manually, as with a normally-executed script.
Discovering Nodes Starting the Discover Wizard To use the Discover Wizard to create a new Discover script: 1. In the Discover Manager window, click Wizard. or Click the right mouse button anywhere in the Discover Manager window, select Wizard from the resulting menu. To use the Discover Wizard to modify an existing Discover script: 1. In the Discover Manager window, highlight the name of the script that you wish to modify, and click Wizard.
Discovering Nodes or Click the IP or Host Locator button ( Standard toolbar. ) on the NetSight Element Manager The IP or Host Locator window, Figure 3-15, opens. By default, the IP, Host, and Get MAC Address fields display the values assigned to your workstation Figure 3-15. The IP or Host Locator Window The following sections describe some common uses for this tool.
Discovering Nodes TIP Once located, IP addresses can be copied (using the right-mouse edit menu or Ctrl-C on the keyboard) and pasted (via Edit—>Paste) into the Insert Device window for addition to the central node database. For more information about inserting devices individually, see Chapter 4, List Views. Matching an IP Address to a Host Name You can also use a known IP address to locate a device’s host name. To do so: 1. Click Clear to clear the default values from the IP and Host fields. 2.
Discovering Nodes Subnet Search You can also use the Locator Tool to locate (and ping, if desired) all IP addresses on a subnet or a portion of a subnet, resolve host names to the located IP addresses, and resolve MAC addresses to the located IP/hostname pair. To do so: 1. Click Clear to clear the default values from the IP and Host fields. 2.
Discovering Nodes any time to stop a search in progress. If you have selected the Prompt option, a message window opens at the selected interval, asking if you want to continue the search. Click Yes to continue, or No to stop. If you have selected the Prompt option, a message window like this one opens at the defined interval. Click here to stop a search in progress at any time. Search results are displayed here. Figure 3-16.
Discovering Nodes Figure 3-17. Completed Subnet Search You can use these buttons to copy one, several, or all discovered IP addresses to the clipboard for pasting into the central node database or any text document: 1. Click Select All to select all discovered IP addresses, or click and drag with your mouse to select a contiguous portion of the discovered address list. or Click Copy Unnamed IPs, Copy Pinged IPs, or Copy Unpingable IPs to select specific groups of IPs.
Discovering Nodes Matching a MAC Address to a Host Name and IP You can also use a known MAC address and subnet location to locate the associated IP address and host name. To do so: 1. Click Clear to clear the default values from the IP and Host fields. 2.
Discovering Nodes When the selected MAC address is located, a message window will display, indicating the host name and IP address associated with the found MAC; this information will also be displayed in the list box. If the address is not located, a message window opens when the search is complete, indicating that the selected address could not be found.
Discovering Nodes Using the Subnets Window With the Subnets window, you can define and view subnet entries which can be used in Discover scripts. The Subnets window is accessed by selecting View—>Subnets from the NetSight Element Manager primary window menu bar. Any subnet entries that appear in the Subnets window will also appear in the Subnets group box on the Device page of the Discover Properties window, and vice versa (see Defining and Selecting Subnets, page 3-7).
Discovering Nodes Figure 3-20. The Subnets Window The Subnets window displays entries for all manually-defined (via this window or the Discover application) subnets; if you have manually added a node to the central node database, a subnet entry will be listed for that node’s subnet as well. Each subnet entry will be listed with its name, description, the network and subnet portions of its IP Address, its subnet mask, and count of the nodes in the central node database that reside on that subnet.
Discovering Nodes 2. Follow the steps outlined in Defining and Selecting Subnets, beginning on page 3-7. The procedure for defining and modifying subnet entries is the same from this window or when configuring a discover script. 3. Click OK to save your subnet discovery parameters and exit the Subnet Properties window. The name, description, address, and subnet mask of the defined subnet opens in the Subnets window.
Discovering Nodes 3-30 Using the Subnets Window
Chapter 4 List Views Using list views to view node information; using the List View workspace; creating and editing list views; changing the appearance of your list views; excluding nodes; adding network elements to the node database; editing node properties NetSight Element Manager stores information about all discovered or manually-inserted devices in one place: its central node database. This information can be viewed in a wide variety of customizable ways via List Views, Tree Views, and Maps.
List Views Click on this tab to bring the List View Workspace into view. Indicates the folder contains one or more list views. Click on the folder to expand and view the contents of the folder. These menus are available by right-clicking on the appropriate folder (above) or view (below). Indicates the folder is expanded and all the contents are displayed. Figure 4-1.
List Views Click the right mouse button on the appropriate folder to add a new folder beneath that selection in the hierarchy. Figure 4-2. Adding a New Folder to the List View Workspace 3. In the resulting menu, click to select New Folder. A new folder will automatically be added in the branch you have selected. Renaming a Folder By default, all new folders are named with the designation New Folder X, where X represents a sequential index; you can rename your folders, as follows: 1.
List Views Figure 4-4. The All Nodes List View The All Nodes List View display includes 11 of the 13 possible descriptive columns available, including Status, Model, Name, Logical Address, Physical Address, Time of Last Contact, System Up Time, Enterprise, Classes, Topologies, and Status Group; Label and Event information is omitted (but can be selected for other views).
List Views Device Views A single default Device View — the All Devices View — displays all IP devices. Enterprise Views A single default Enterprise View allows you to display only your Cabletron and Enterasys devices. Topology Views Two default topology views filter out all devices that do not provide Ethernet (Ethernet View) or Token Ring (Token Ring View) topology support.
List Views Small Icon Detail Format (View—>Small Icon Detail) Each node appears as a line in a multicolumn format. The columns consist of the information you have chosen to display from the List View Properties window (or the default columns, in the case of the All Nodes List View), in the order you have specified there. For each displayed information type which includes an icon, the small (16x16 pixel) graphic will be displayed.
List Views and a greater-than or less-than sign displayed in the selected column settings: a greater-than sign (>) indicates that the information in the associated column is sorted in ascending order; a less-than sign (<) indicates that the information is sorted in descending order. You can choose as many levels as you want for your sort, and you can mix ascending and descending sorts in different columns.
List Views To access the Find window: 1. Open or activate the List View that you wish to search. 2. Select Edit—>Find from the primary window menu bar. or Click on the List View toolbar. The List View Find window, Figure 4-7, opens. Use this text box to enter a string you wish to match in any available List View column. You can specify a case-sensitive search, or allow for a partial match of the string. The status bar displays the type of search currently in effect.
List Views 2. In the Text to find (in ANY column) text box at the top of the window, enter the string you wish to match. Note that this field will not be available unless the All columns option is selected in the Column to search list box. For your convenience, the ten most recent search strings will be listed in a drop-down menu. 3. To make your search case-sensitive, click to deselect the Any case option in the lower right corner of the window. To match any case, leave the option selected. 4.
List Views Creating and Editing List Views You can create a variety of list views customized to meet your network management needs, either by editing any of the default views provided (except the All Nodes List View) or by creating entirely new views. User-defined filter criteria allow you to select which nodes will be displayed; List View display properties allow you to select which information about those nodes will be displayed. To create a new list view: 1.
List Views NOTE When you add a new list view by any of the means described above, it will be added to the folder which is currently selected in the List View workspace; if you add a list view by right-clicking in a blank area of the workspace, the new view will be added to the root folder. Once a List View has been added, it cannot be moved from folder to folder. All folders and views are listed in the workspace in alphabetical order. To edit an existing list view: 1.
List Views 2. In the Columns list box, click to select the information you’d like displayed about each node in the view; click again to deselect any option you do not wish to view. Each selection in this list will add a column of information to your list view. Each of the available options is described below; you must select at least one column to create or save your view. TIP You can also use the Select All and Unselect All buttons to select or deselect all available column options. 3.
List Views • Unknown (Blue) - A blue status icon indicates that NetSight Element Manager has not yet been able to contact the represented node, and has not yet determined whether or not that contact will be successful. A node icon is blue only temporarily, while NetSight Element Manager determines whether or not contact can be made: if contact is successfully made, the icon will turn green; if not, it will turn red.
List Views Status Group If the device is part of a Distributed LAN Management status group, it will be indicated here. Both the name assigned to the DLM group and the node’s position in that group (“DLM Agent” or “DLM Client of (IP Address)” ) will be displayed. For more information on configuring and using Distributed LAN Management functions, see the DLM Status Groups chapter in the NetSight Element Manager Tools Guide, included with your document set.
List Views Figure 4-9. Font Window Change your font settings as desired using the Fonts, Font Style, and Size fields, then click on OK to set your changes. Selecting the Nodes to Display: Using Filters Using the View Filter window, you can set up filters that determine which of the nodes stored in the central node database will be displayed in your list view. You can filter nodes based on specific Subnet, Status Group, Enterprise, Class, and/or Topology attributes.
List Views The check boxes above the filter categories allow you to either select or de-select all of the specific attributes listed. You must leave at least one attribute selected in each category. Figure 4-10.
List Views Classes Lists the functional classes that NetSight Element Manager can detect. Classes available for filtering include: • Repeater • Router • Generic Bridge • Router/Gateway • Ethernet/Token Ring Bridge • Switch • Ethernet/FDDI Bridge • Ethernet/WAN Bridge • PBX • Multi-Topology Bridge • FDDI Concentrator • Terminal Server • Server • ATM Nodes which support more than one functional class will be displayed in any view for which one of its classes is selected.
List Views As with classes, nodes which support more than one topology will be displayed in any view for which one of its topologies is selected. You can also choose to filter on nodes whose topology is unknown. Creating the Filter When you create a filter, you select the specific attributes in each category that define the nodes you want to display, and de-select the attributes that define nodes you do not want to display.
List Views illustrated in Figure 4-11. Nodes excluded from an individual view will still appear as appropriate on all other views, and their placement on maps will not be affected; they can also be re-included in the view at any time. You may re-include individual nodes, groups of selected nodes, or the entire list by using these buttons. Nodes excluded from the “Active View” display here. Figure 4-11.
List Views Select the Delete key on your keyboard. or Select the Delete toolbar icon. or Click the right mouse button on any of the selected entries, and select Delete from the resulting menu. The Node Delete window (Figure 4-12) opens, with the node(s) you have selected for deletion highlighted in the central window. NOTE Using Edit —> Cut instead of Edit —> Delete will remove nodes from the active view without bringing up the Node Delete window, and place them on that list view’s excluded nodes list.
List Views To Re-include a Node in a View To remove a node from a view’s Excluded Nodes list and re-include it in the view: 1. Open or activate the view whose excluded nodes you wish to re-include. 2. Open the view’s Properties window by clicking the right mouse anywhere in the view, and select List View Properties (or Tree View Properties) from the resulting menu. or With the appropriate list view open and active, select View—>Properties from the primary window menu bar.
List Views 4. In the resulting confirmation window, click Yes to confirm the inclusion, or No to cancel. 5. Click OK to close the Properties window; note that the formerly excluded nodes are again displayed in the view. Excluding Nodes from the Central Node Database In addition to its central node database, NetSight Element Manager maintains a second database called the Excluded Nodes database.
List Views The Excluded Nodes List and Discover The Excluded Nodes list can be used to prevent certain nodes from being re-discovered and re-added to the central node database. Nodes which have been excluded from all views are no longer polled byNetSight Element Manager or displayed in any of its views, but they won’t be discovered by the Discover application, either.
List Views Figure 4-15. The Node Delete Window 3. Click to select the All Views option, then click OK to confirm the deletion. The selected nodes will be removed from the central node database and all views, and placed in the Excluded Nodes database. Remember, the excluded nodes database can be viewed via the Excluded Nodes window (Figure 4-14, page 4-22), available from the View menu in the primary window menu bar. Excluded nodes can also be either re-included in the database, or deleted entirely.
List Views TIP Remember, you can also click on any column header in the Excluded Nodes list to re-sort the nodes according to the information in the selected column; entries are always sorted in ascending order. 3. Click Yes to confirm. The node or nodes will be moved from the Excluded Nodes database to the central node database, and appear again in all appropriate list views. 4. Click Close to close the excluded nodes window.
List Views Figure 4-17. The Node Delete Window 3. Click to select the Database option, then click OK to confirm the deletion. The selected nodes will be removed from the central node database entirely. To delete a single node or group of nodes from the Excluded Nodes window: 1. Select View—>Excluded Nodes from the primary window menu bar to display the Excluded Nodes window. 2.
List Views The following sections describe how to add individual devices to the central node database, and how to edit the display properties of any node. Adding a Device In order to add a device to the central node database, you must have a List View or Tree View open and active in the primary window. If a map view is active, an inserted device must be placed in the map before it is added to the database; if no view is open, the insert device options will not be available.
List Views Figure 4-19. The Insert Device Window 2. In the Address field, enter the IP address assigned to the device you wish to add. 3. In the Community Name field, enter a community name that will provide at least Read access to the device you are adding. For full management access, use a community name that will provide superuser access.
List Views If you click Yes, the Device Properties window opens, and you can add an Unnamed PING device to the central node database. If you click No, no new device will be added. TIP If a map window was active when you selected the menu or toolbar option for adding a device, closing the Properties window will change the arrow pointer into a crosshair cursor.
List Views In the toolbar, click the Properties icon. or Right-click on the selected device and on the resulting menu select Properties. NOTE If you access the Properties window from within a List, Tree, or Map View, you will note that there are two properties-related options available on the menu which appears when you click on the selected device with the right mouse button.
List Views Device Properties The Device Properties tabbed page (Figure 4-22) allows you to edit the following properties: Figure 4-22. Device Properties Page Label The value set in this field will be displayed in the Label column in any list view which contains this field. Note that this is not the label that will be assigned to a device icon displayed in a Map View. There is no default value. Address The IP address assigned to the device. This field is not editable.
List Views Figure 4-23. Interface Properties Interface List Box The list box at the top of the Interfaces page displays the Topology, IfIndex, and Description of the contact interface on the selected device. Poll Settings The Poll Settings box displays the polling parameters assigned to the contact interface. Even though your managed device may have multiple interfaces, it will only be actively polled on a single interface (the first interface detected when the device is contacted).
List Views (along with any applicable arguments), and the OID that will be queried to determine the device’s type code. For more information on configuring these settings, see Editing Node Class Properties, page 4-37. Click on the Node Classes button to display the Node Classes window, which displays the properties associated with each node class, and which allows you to access the Node Class Properties window. See page 4-37 for more information. Figure 4-24.
List Views Configuring Node Interface Poll Settings You can configure the parameters which control how NetSight Element Manager polls the contact interface on a selected node via the Poll Settings options in the Interfaces tabbed page in the Properties window (Figure 4-23, page 4-32). NOTE The Properties button in the Interfaces tabbed page launches the Interface Properties window, Figure 4-25, with an identical Poll Settings area.
List Views If you have a mission-critical node which requires more frequent updates than can be achieved during the database polling cycle, you can keep Chassis Manager running to be constantly appraised of its contact status; the Chassis Manager application uses its own polling mechanism independent of the node database polling in the NetSight Element Manager platform.
List Views Editing Poll Settings for Multiple Nodes You can also edit interface poll settings for multiple nodes via the Multi-Node Properties window (illustrated in Figure 4-26). Figure 4-26. The Multi-Node Properties Window To edit interface poll settings: 1. Open and activate the view which contains the nodes whose interface poll settings you’d like to change, and use shift-click or ctrl-click to select the appropriate nodes.
List Views TIP You can also add an Object Note to multiple nodes; see Adding Notes to Multiple Nodes in Chapter 6, Creating Network Maps, for more information. Editing Node Class Properties NetSight Element Manager classifies devices according to what is called a Node Class. In the Node Classes window (Figure 4-27), the properties associated with each node class (model, icon, class, etc.) are displayed in column format.
List Views To edit Node Class Properties for an existing node type: 1. In the Node Classes window, click on the node classes entry you wish to edit, then click on Properties. or Click the right mouse button on the node classes entry you wish to modify, and choose Properties from the menu that appears. The Node Class Properties window (Figure 4-28) opens.
List Views To create a new node class entry: 1. In the Node Classes window, click on New. or Right-mouse click anywhere in the Node Classes window, and select New from the resulting menu. The New Node Class window opens. Note that this window is virtually identical to the Node Class Properties window displayed in Figure 4-28, except for the title and the fact that the General tabbed page is displayed first by default. Use the procedures outlined below to edit or create a node class.
List Views Figure 4-29. Default Symbol Sets Changing Management Application Information The Node Class page of the Node Class Properties window also allows you to choose the management application that will be launched for all nodes assigned to a given node class. You specify this via the Command field, in which you enter the path and filename of the appropriate executable (*.
List Views by the application. These fields can be edited by typing in a new command, argument, or directory, or by using the Browse and Build buttons, as described in the following sections. Choosing a Command (Executable) File The Command field in the Management Application area tells NetSight Element Manager which management application is to be launched for a given node class when any one of the Manage options is selected.
List Views Building an Argument List The Arguments field allows you to specify any command line parameters (or arguments) that are required by (or permitted by) the selected executable. This field can be manually edited by clicking in it and typing in desired changes, or you can build an argument list using the Build window: 1. In the Management Application area, click on Build. The Build window, Figure 4-31, opens. Figure 4-31. The Build Window 2.
List Views TIP The pre-defined argument list provided lists the argument symbols for data NetSight Element Manager can extract from the central node database for any node against which the selected executable will be launched. Using these symbols allows you to configure a Node Class that can be used for many individual devices.
List Views In most cases, the flags and related argument values are optional. If you do not specify a necessary value, you will be prompted to supply it when the application launches. Selecting A Working Directory If it is required by the executable you have selected, you can also specify a Working Directory. The working directory value sets the location of any secondary files that might be needed by the executable, if those files are not located in the same directory as the executable itself.
List Views Figure 4-32. The General Properties Window To enter information for a node class: 1. Click in the Name field, and type in a name for the node class. The value entered here is displayed in the Model field of the Node Classes window. 2. In the Description field, enter a description for the node class. 3. If there are any notes regarding the node class you wish to keep in the Properties window, type them into the Notes field. 4. Click OK to save your changes and exit the window.
List Views List Views and Maps NetSight Element Manager can help you sort out the relationship between your list views and your maps in two ways: by allowing you to select (and, if you wish, delete) any nodes in a view which have not been placed on a map; and by helping you locate the map on which a node has been placed. TIP Both the Orphan and Go to Map functions require your map files to be open, though they need not be active.
List Views Using the Go To Map Function You can use the Go to Map function to locate a node on the map on which it has been placed — provided, of course, that the map is open. 1. Open and/or activate the List View which contains the node or nodes whose map you wish to locate, and click to select one node. (The Go to Map options will not be available when multiple nodes are selected.) 2.
List Views 4-48 List Views and Maps
Chapter 5 Tree Views Accessing a tree view; navigating a tree view with the mouse, keyboard, and Tree View toolbar; tree view properties for nodes and interfaces; the default tree views; creating and editing tree views; excluding nodes Like List Views, Tree Views provide a window through which you can view selected information about the nodes in the central node database.
Tree Views The Tree View Workspace Using the Tree View workspace you can access and edit existing views, create new ones, and organize your views by arranging them in a hierarchy of folders. Click on this tab to bring the Tree View Workspace into view. Indicates the folder is expanded and all the contents are displayed. These menus are available by clicking the right mouse button on the appropriate folder (above) or view (below). Indicates the folder contains one or more tree views.
Tree Views TIP To add a folder at the top level of the Tree View hierarchy, click to select the main Tree Views folder. Click the right mouse button on the appropriate folder to add a new folder beneath that selection in the hierarchy. Figure 5-2. Adding a New Folder to the Tree View Workspace 3. In the resulting menu, click to select New Folder. A new folder will automatically be added in the branch you have selected.
Tree Views The All Nodes Tree View The All Nodes Tree View provides the most comprehensive look at the contents of your central node database. This special default view will always appear at the root of your Tree View hierarchy (as displayed in the Tree View workspace), and cannot be edited or deleted; by design, it displays information about every node in the central node database. Figure 5-4.
Tree Views Other Default Tree Views As with List Views, NetSight Element Manager provides a set of default views for your convenience. Unlike the List Views, however, these default views don’t exclude any nodes; they just exclude some of the information displayed about the nodes. These default views can be used as is, edited to better suit your needs, or deleted entirely.
Tree Views Expand All (View—>Expand All) Expands the entire tree view so that every level of information is displayed for every node. Expand One Level Collapse All Expand Two Levels Collapse Two Levels Expand All Collapse One Level Figure 5-5. The Tree View Toolbar Collapse One Level (View—>Collapse) Collapses the selected node or sub-node heading one level, if it has not already been collapsed.
Tree Views Creating and Editing Tree Views You can create a variety of tree views customized to meet your network management needs, either by editing any of the default views provided (except the All Nodes Tree View) or by creating entirely new views. User-defined filter criteria allow you to select which nodes will be displayed; Tree View display properties allow you to select which information about those nodes will be displayed. To create a new tree view: 1.
Tree Views To edit an existing tree view: 1. With the appropriate tree view open and selected in the NetSight Element Manager primary window, select View —> Properties from the primary window menu bar. or In the Tree View Workspace area, click the right mouse button on the name or icon associated with the view you wish to edit, and select Properties from the resulting menu. or Click with the right mouse button anywhere in the view you wish to edit, and select Tree View Properties from the resulting menu.
Tree Views TIP You can use the Select All and Unselect All buttons to either select or unselect all available Node and Interface items. 4. By default, a tree view will list nodes by their assigned Name; if you prefer devices to be listed by IP address, click to select the Display device addresses at node roots option.
Tree Views • Unknown (Blue) - NetSight Element Manager has not yet contacted the node, or has not determined whether that contact was successful. A node icon is blue only temporarily, while NetSight Element Manager determines whether contact can be made: if contact is successfully made, the icon will turn green; if not, it will turn red.
Tree Views DLM Status Group If the device is part of a Distributed LAN Management status group, it will be indicated here. Both the name assigned to the DLM group and the node’s position in that group (“DLM Agent” or “DLM Client of (IP Address)” ) will be displayed. For more information on configuring and using Distributed LAN Management functions, see the DLM Status Groups chapter in the Tools Guide. Model Indicates the model name of the device, along with the icon which represents that model type.
Tree Views Address Displays the IP address assigned to the node, and the MAC address of the contact interface. Interface Number Display the ifIndex value assigned to the contact interface. Poll Method Indicates the type of polling currently being used to contact the node. Poll Interval The configured interval between interface polls, in seconds. Poll Retries The number of polls that must fail before NetSight Element Manager declares communication with the interface has failed.
Tree Views Change your font settings as desired using the Fonts, Font Style, and Size fields, then click on OK to set your changes. Selecting the Nodes to Display: Using Filters Using the View Filter window, you can set up filters that determine which of the nodes stored in the central node database will be displayed in your tree view. You can filter nodes based on specific Subnet, Status Group, Enterprise, Class, and/or Topology attributes. To open the View Filter window: 1.
Tree Views TIP See Chapter 3, Discovering Nodes, for more information on creating and using subnet entries. Status Groups Any DLM Status Groups you have created will be displayed in this list box. You can choose to display only those nodes which are part of one or more selected status groups, or those which are part of any defined status group. Enterprises The Enterprise category allows you to filter nodes by hardware or software manufacturer.
Tree Views • Software Loopback • Ultra Tech • SMDS • Proteon 80Mbit • Proteon 10Mbit • ATM • AAL5 over ATM • RS-232 • Parallel Port • Arcnet • Arcnet Plus • SMDS DXI • SONET • SONET Path • SONET VT • SDLC • V.35 • Frame Relay • Frame Relay Service • HIPPI • HSSI • X.
Tree Views Excluded Nodes NetSight Element Manager’s architecture — which stores all node information in a central database, and lets you choose how to view it — provides you with great flexibility in the management and storage of node information. One of the ways you can manage your collected node information is through the use of Excluded Nodes. There are two levels of node exclusion: exclusion from an individual view, and exclusion from all views.
Tree Views TIP For nodes which are present on multiple maps, only one map will be selected — even if all related maps are open. To locate a node on more than one map, open all maps, use the Go to Map option to locate the node on one map, then close that map and repeat as necessary.
Tree Views 5-18 Tree Views and Maps
Chapter 6 Creating Network Maps Building a map hierarchy; about the Map View; creating new maps; adding submaps and GoTo symbols; generating submaps automatically; adding nodes to a map; importing MRM maps; customizing your maps; aligning map objects; saving maps NetSight Element Manager’s mapping capabilities provide a powerful means for creating logical and/or physical representations of your network.
Creating Network Maps About the Map View The Map View portion of the NetSight Element Manager workspace (illustrated in Figure 6-1) provides a bird’s-eye view of the submap hierarchy you have created among your maps via a standard indented tree structure: maps can be grouped in Folders; folders can contain Maps and/or additional folders; and each map can contain one or more Submaps.
Creating Network Maps From within the Map View workspace, you can create, delete, or rename folders and maps, and delete or rename submaps; you can also launch the Properties window for any map or submap. Each of these functions is described in the following sections.
Creating Network Maps There is only one restriction to submap relationships: a map cannot be defined as a submap of more than one root map. In the above example, then, FLOOR_1 cannot be made a submap of any other root map while it is defined as a submap of BUILDING_A. If you try to add a second submap icon representing the same (FLOOR_1) map, the submap relationship will change — for example, adding FLOOR_1 as a submap of BUILDING_B removes its submap relationship with BUILDING_A.
Creating Network Maps Status conditions as reported by each map — listed here in decreasing order of severity — are defined as follows: TIP TIP Critical (Red) At least one element on the represented map is reporting a critical condition; a node in critical condition is no longer in contact with NetSight Element Manager. Warning (Yellow) At least one element in the represented map is reporting a warning condition.
Creating Network Maps Building Your Network Map Before you begin creating maps, it’s useful to spend a few moments thinking about the organization of your network and how best to create a visual representation of that organization for the purposes of network management.
Creating Network Maps display the collective status of the maps it contains. Note that folders are a Map View workspace display convention only, and they can only be created from within the Map View workspace itself. 1. Display the Map View page of the workspace by clicking on the the Workspace View. tab in 2. Click the right mouse button on the folder to which you want to add a new folder; that folder will be highlighted (as illustrated in Figure 6-3), and a menu opens.
Creating Network Maps you must click the right mouse button on the folder of choice and select New View from the resulting menu (as described below), or make sure the folder you want to add the map to is highlighted in the Map View before using the File menu or toolbar options. TIP You can also create a new map when you add a Submap or GoTo icon; see Adding a Submap, page 6-13, or Adding a GoTo Symbol, page 6-18. To create a new map: 1.
Creating Network Maps Once you have created the new map, it displays in the appropriate place in the Map View tree hierarchy. The New Map View window allows you to set a variety of display and print options for your map. To create a map file, you need only assign a unique name; the name and any other map parameters can be changed later by accessing the Map Properties window (see Editing Map Properties, page 6-12, for more information). The following sections describe how to set map parameters.
Creating Network Maps Figure 6-5. Color Window (Expanded with Custom Colors) c. Select a color to apply to the map: 1.) Click one of the pre-defined Basic Colors from the palette. or Click Define Custom Colors option to expand the window, and use the cross-hair and color slide bar to create a color from the color refiner box.
Creating Network Maps TIP NetSight Element Manager includes a self-extracting ZIP file that contains a variety of bitmap images you can use for map backgrounds. The file — called “images.exe” — is located in the \NetSight Element Manager\Bin directory; double-clicking on this file will extract the bitmap images. Setting a Background Grid You can set up a grid in your map window to assist in drawing map items or in positioning map objects, symbols, and icons. To establish a grid: 1.
Creating Network Maps Figure 6-6. The Font Window 2. Select the desired font, style, size, effect, and color using the appropriate fields; note that the effect of the selected options will be displayed in the Sample text box. 3. Click OK to exit the window and apply your changes. The selected font style will be applied to all icon and symbol labels in the map.
Creating Network Maps or From within the map whose properties you wish to view, click the right mouse button on any blank space or map element, then select Map Properties from the resulting menu. or From within the map whose properties you wish to view, double-click anywhere on the map background. The Map View Properties window, Figure 6-7, opens. Figure 6-7. The Map Properties Window Follow the steps outlined in the previous sections to change any of the properties of the selected map.
Creating Network Maps 1. If necessary, open or activate the map to which you wish to add a submap icon. 2. In primary window menu bar, select Insert—>Sub Map. or In the toolbar, click the Insert Sub Map window, Figure 6-8, displays. icon. The Insert SubMap Figure 6-8. The Insert SubMap Window TIP If no other maps have yet been created, inserting a submap will launch the New Map View window directly. 3. To create an entirely new map, click on Create New.
Creating Network Maps The Map View workspace will update automatically to display the new map in its position in the hierarchy. The Submap icon itself will display the current status of its associated map; double-clicking on a Submap icon will also open or activate the associated map. TIP You can only place a Submap symbol in the root map that was active when the Insert Submap process was initiated.
Creating Network Maps 2. In the Root Map Name field, enter the name you’d like to assign to the root map of your hierarchy. This will be the map that contains the submap icons for each submap that is created; it can be an entirely new map, or you can enter (or use the Browse button to locate) an existing map. 3. The Subnets list box lists each of the submaps that will be created, along with the default name that has been assigned to each, and the subnet whose devices it will contain.
Creating Network Maps A Subnet label and GoTo symbol are added to each created submap if the Display Subnets and Insert GoTos options are selected in the Subnet Mapping window. Figure 6-11. Automatically Created Submaps Changing a Submap Link Whether you have chosen to create a new map, link an existing map, or create a submap hierarchy automatically, submap links are entirely flexible and can be changed at any time.
Creating Network Maps ! CAUTION If you use the Cut command to remove a submap icon, only the icon will be removed, and no confirmation is required. If you use the Delete command, the icon will be removed, and a prompt window opens asking if you wish to remove the view as well. Click Yes to remove both the submap icon and the map view it represents; click No to remove the icon only. If you accidentally select Yes, don’t forget you can still recover your map view by importing its associated .
Creating Network Maps 3. To create an entirely new map, click Create New. The New Map View window (as illustrated in Figure 6-4 on page 6-8) opens. Configure the name and display parameters as desired, then click OK. To link an existing map, select the name of the map you wish to link, then click OK. Only the maps available for GoTo linkage will be listed. 4.
Creating Network Maps Importing an MRM Map If you are upgrading from an earlier version of NetSight Element Manager, your map files should be backed up and restored automatically as part of the install process, and should open in their original condition. Although the .MRM maps are no longer a necessary step in converting your files from one version to another, you may still find that you occasionally need to import an .MRM file. Each map file in NetSight Element Manager is saved in both .
Creating Network Maps Figure 6-13. Importing MRM Maps Options 2. If you want all unknown nodes to be discovered at once (without requiring any input from you), select Automatically Insert Devices. If you want to be prompted with an Insert Device window for each unknown node, select Manually Insert Devices. 3. Click OK. The configured option will be used for all .MRM imports until a new option is selected. Importing a Map 1. In the Map View window, select the folder into which you wish to import the map.
Creating Network Maps 3. Use the Look in field to select the appropriate directory, then select the file you wish to import in the list box. The selected file opens in the File name: text box; click on Open to import the file. The Import Progress window, Figure 6-15, opens. Figure 6-15. MRM Import Progress Indicator NOTE If you import an .
Creating Network Maps Adding Network Elements to your Map For the most part, adding a device icon to a map simply involves dragging the selected icon or icons from any one of the available views or from another map, or using the standard Copy and Paste commands.
Creating Network Maps Note that the contents of the Map menu will change depending upon whether you accessed it from a blank map area or from a node icon. Figure 6-16. Displaying the Map Menu The Insert Device window, Figure 6-17, opens. Figure 6-17. The Insert Device Window 3. In the Address field, enter the IP address assigned to the device you wish to add. 4. In the Community Name field, enter a community name that will provide at least Read access to the device you are adding.
Creating Network Maps TIP If you have configured and activated the Autofill options (either via the Welcome Wizard or via the Tools—>Options window), the autofill values you have set for IP address and community name display automatically in the appropriate fields. You can keep these options or replace them, as necessary. 5. If the device is successfully contacted, the Device Properties window, Figure 6-19 (page 6-26), opens. Make any changes to the properties, as desired, then click on OK.
Creating Network Maps Click on the tabs to display the four different pages available in the Device Properties window. Figure 6-19. The Device Properties Window By default, device icons will be labeled by the MIB-II sysName (if one has been assigned) or, if no name has been assigned, by IP address. You can change the icon name via the Device Properties window; for more detailed, see Editing Device Properties in Chapter 4, List Views.
Creating Network Maps Map Tools include the Add Submap and Add GoTo buttons, as well as the layering tool buttons. Pointer Tool Line Tool By default, drawing tool buttons are displayed vertically on the right side of the primary window. Rectangle Tool Rounded Rectangle Ellipse Tool Text Tool By default, alignment tool buttons are displayed at the bottom of the primary window. Symbol Tool Connection Tool Figure 6-20.
Creating Network Maps The Select Symbol window, Figure 6-21, opens. By default, the available symbols will be displayed in Large Icon format; use the buttons at the top of the window to select a different display format, if desired. Figure 6-21. Select Symbol Window 3. Select the symbol you wish to add.
Creating Network Maps Editing Individual Symbol Properties When you place a symbol in your map, it will be labeled with the global label assigned to the symbol type in the symbol database. You can change this label for each individual symbol icon via the Symbol Properties window, Figure 6-22, as follows: 1. To access the Symbol Properties window from the appropriate map window, double-click on the symbol icon. or Select the symbol, then select Edit —> Properties from the primary window menu bar.
Creating Network Maps TIP If you can’t find a symbol in the database that suits your needs, but you are reluctant to permanently edit the symbol database, you might want to create an entirely new symbol instead. This new symbol will be added to the existing database, but will not change any existing symbol definitions. See Creating a New Symbol, page 6-32, for details. To edit the symbol database: 1. If necessary, open or activate a map window.
Creating Network Maps Figure 6-24. Global Symbol Properties Window 4. To change the label assigned to all symbols of the selected type, click in the Label field, and enter the desired text. 5. To change the numeric identifier assigned to the symbol type, click in the Identifier field, and enter a new numeric value.
Creating Network Maps selection. The image portion you have selected will be displayed below the Large Image radio button. Move the cursor and click again to change this selection until you find the one you want. 7. Click OK to save your new symbol definition. If you have changed the symbol label or image, the new properties will be displayed in the Select Symbol window.
Creating Network Maps 5. To assign a numeric identifier to your new symbol, click in the Identifier field, and enter a new numeric value.
Creating Network Maps 2. Click the Connection tool from the toolbar (see Figure 6-20, page 6-27). or Select Draw—>Connection from the primary window menu bar. 3. Move the cursor back into the map window, and note that it has changed from an arrow to a symbol. This symbol will change to a crosshair when the mouse is positioned over an object (node icon or symbol) which can support a connection. Position the crosshair over the first of the two elements you wish to connect, click the mouse, and release. 4.
Creating Network Maps If you are creating a rectangle or ellipse, click and hold the mouse button and drag to create the size and shape object you want. Releasing the mouse button completes the object, but note that the crosshair cursor remains, allowing you to draw additional objects of the same shape without having to re-select the tool. If you are creating a line, click the mouse button once to place the beginning line point, then move the cursor in the direction you wish to draw your line.
Creating Network Maps Use the Line Properties window to change the look of both lines and connections. Figure 6-26. Line and Shape Properties To specify Line Properties: 1. Select the Line Type by clicking the mouse button on the appropriate option: Solid, Dotted, or Dashed. 2. If you selected a Solid line, you can specify its Line Width in pixels. Dotted and dashed lines are fixed at 1 pixel. 3.
Creating Network Maps 3. The Sample portion of the window will display your changes as you make them; when the sample displays the look you want to achieve, click OK to apply changes and exit the window. You can also reshape existing objects, as follows. To reshape an existing line: 1. Click once on the line to display the handles for its vertices. 2. Move the mouse cursor over a handle to activate reshaping for that vertex (the cursor will display as a dual-headed arrow). 3.
Creating Network Maps 5. To move the text box, click and hold the mouse button, and drag the cursor to the appropriate location. (Note that you can move this text element any time, just like any other map element.) 6. When you have finished typing, click anywhere outside the text box. The default selections for font type, color, and size will be used for each new text element; to change the style or font of the text in the selected text element: 1. Double-click on the text.
Creating Network Maps 4. Using the Size: list box, select a font size for the string. 5. If you want your text to have a Strikeout or Underline Effect, click to select (X) the appropriate option. 6. Using the Color scrollbox, click to select a color for your text string. 7. As you edit the font properties, you can see the results in the Sample display. When you have finished, click OK to apply changes and exit the Font Properties window.
Creating Network Maps Figure 6-28. Object Notes Window 3. Click to place the cursor in the text area, and add your note. Note that the text will wrap automatically, or you can enter a carriage return by pressing Enter (if you are annotating a device icon) or ctrl-Enter (if you are annotating a map object). TIP Pressing Enter in a Notes window for a map object saves your changes and closes the window. 4.
Creating Network Maps 3. Enter the desired notes text in the Notes field available on the General Properties tabbed page. As illustrated in Figure 6-29, text entered in this Notes field will also be displayed in the Object Notes window, and vice versa. You can also add an Object Note to a device via the Properties window. Figure 6-29. Entering an Object Note via the Properties Window 4. Click Apply to save your changes (if applicable), then click OK to close the Properties window.
Creating Network Maps Adding Notes to Multiple Nodes You can also add the same note to multiple node icons simultaneously via the Multi-Node Properties window. Doing so will overwrite any existing notes attached to the selected nodes, without warning. To add a single note to multiple selected nodes: 1. Open and activate the view which contains the nodes to which you’d like to add a shared note, and use shift-click or ctrl-click to select the appropriate nodes.
Creating Network Maps Layering Items in a Map You can arrange any map object — node icons, symbols, shapes, lines, connections, and text elements — into layers by using the Layering Tools (see Figure 6-20, page 6-27) or via the Layout—>Layer menu on the primary window menu bar. The layering position of a single object is determined relative only to other contiguous objects — not to all objects in the map. 1.
Creating Network Maps To align selected objects to the top of the controlling object, click on the Align Top button or select Layout—>Align—>Top. To align selected objects to the bottom the controlling object, click on the Align Bottom button or select Layout—>Align—>Bottom. 4. The aligned objects remain selected after the alignment procedure is complete; you can move the group as a whole by clicking and holding the left mouse button, and dragging the group of objects to the desired map location.
Creating Network Maps or align the objects by the top, bottom, left, or right edges using the alignment tools described in the previous section. To de-select the objects, click the left mouse button anywhere in the map background. Make Same Width, Height, or Size You can use the Make Same Size tools to reshape graphic elements in relation to one another.
Creating Network Maps Align Objects in Grid The Grid tool allows you to align all selected objects into a grid formation starting in the upper-left-hand corner of the map window. 1. If necessary, open or activate the map which contains the objects you wish to align. (Remember, neither the Alignment Toolbar nor the Layout menu options will be active unless a map window is active.) 2. Press and hold the Ctrl key, and select the object(s) you wish to align in a grid formation.
Creating Network Maps 4. Place the crosshair cursor on the spot around which you want your ring to be centered, then click the mouse button to place the ring. The selected objects will be aligned according to the default spacing parameter, and a Ring Spacing window, Figure 6-30, opens. Figure 6-30. The Ring Spacing Window 5. If the default spacing parameter does not produce the desired results, adjust the spacing by entering a new pixel value in the Ring Spacing window and clicking Change.
Creating Network Maps (termed a “compound” document) — in this case, your network maps. You can use OLE to link or embed documents created via word processors, spreadsheets, databases, an audio application — or any other OLE server application — into your maps. A linked or embedded data structure is generically termed an Object, since the data can be created by any OLE supporting application.
Creating Network Maps NOTE For more information regarding Object Linking and Embedding, as well as the Microsoft Object Packager, refer to the Microsoft Windows User’s Guide for the Windows Graphical Environment. Embedding an Object in a Map File NOTES This section provides directions for creating an embedded object icon from within the map interface. You can also create an embedded object by working directly in the external source application, copy the data to the clipboard, and paste it into the map.
Creating Network Maps 4. Objects on your map will be confined within a resizable border that contains a pictorial representation of the object data. The pictorial representation may be an icon to indicate the linked or embedded document, or the source data itself may be visible within the border. Resizing the border will scale the object’s pictorial representation (the icon or the data). The pictorial display of an object will depend on its creating application type.
Creating Network Maps 3.) Select the From File radio button to change the icon to one that is associated with a different application or defined by a standard Windows icon file (with a .ico extension). The icon(s) associated with the selected application file or defined by the icon file displays in the scrollable list box immediately below the file path text field. Click to highlight the icon of interest, or use the associated text field to type in the path and name of the icon you want to use.
Creating Network Maps Figure 6-33. Sample Insert Object Window (Create From File Selected) b. If you wish to link the existing object, be sure to select the Link option before placing the object in your map (see the following section for details), or click OK to embed the object in your map.
Creating Network Maps Figure 6-34. Sample Object Packager Window 3. Create an Object Package. Embed or link an entire document (or part of a document) into the package, or build an MS-DOS command line to run a batch file or start an application via the package; then specify the icon and label to be used for the package. The details of how to create an Object Package are provided in your Microsoft Windows User’s Guide. 4.
Creating Network Maps Updating a Link You can use the Links window to see a list of all linked objects in any map, and: • Specify whether to manually or automatically update the appearance of the linked object data within its border (if it is not displayed as an icon). • Open the source document of any linked object. • Change the linked object to reference a new source document. • Remove the link to the source document, so that the object becomes a static item in your map.
Creating Network Maps NOTE Type This column indicates the source document’s type; if a link is selected this will also display in the Type field. Update Indicates whether the appearance of the object in the map will be automatically or manually updated to reflect changes to the source document; if a link is selected, this will also be indicated by the Automatic or Manual Update radio buttons at the bottom of the window.
Creating Network Maps Enter a file path and name directly in the Source text field at the top of the window, or use the Directories tree and Drives drop-down list box to scan your system directories; and use the List Files of Type drop-down list box and files panel to select a source file. Click to select a file and enter it in the Source text field. You can also remove a link between the object and a source document, so that the object no longer opens data via an external application.
Creating Network Maps 1. Open or activate the map which contains the object you wish to convert, and click to select the object. 2. From the primary window menu bar, select Edit—>XXX Object—>Convert. The Convert window, Figure 6-36, opens. Figure 6-36. Sample Convert Window 3. In the Object Type panel, click to highlight the application type to which you want to temporarily or permanently convert the embedded or linked data. 4.
Creating Network Maps You can also perform the standard Cut, Copy, and Paste options on embedded or linked objects in your map. If you copy an embedded object and paste it to another map, the source data will be copied into the new map; if you copy a linked object, the source file pointer will be copied into the new map.
Creating Network Maps Figure 6-37. The Node Delete Window Second, you can cut and paste or move Submap icons, and the links will change accordingly; remember, however, that no map can be a submap to more than one root map. If you try to place multiple submap icons representing the same map, the submap link will change without warning (and the workspace display will update accordingly). See About Submap Icons, page 6-3, and About GoTo Symbols, page 6-4, for more information.
Creating Network Maps 3. Select Edit —>Copy from the primary window menu bar, the Copy button on the toolbar, or the Copy option on the right-mouse map menu. 4. Create, open, or activate the map to which you wish to add the copied icons, and select Edit —>Paste Special (No IPs) from the primary window menu bar. 5. Place the No IP Paste cursor in the location to which you wish to paste the icon group, and click the mouse button to paste.
Creating Network Maps When a locked map is the active map, the map icon in the upper-left-hand corner of the map window will change into a lock; also, a lock icon will precede the map name in the workspace, and the Lock option on the View menu will be preceded by a check mark. To unlock the map, click to select the Lock option again. A map’s locked state will persist until it is changed by user action.
Creating Network Maps Saving Maps When NetSight Element Manager saves a map file, it actually saves it in two distinct formats: a .MAP format, which is the format in which you open and edit maps within the primary window; and a .MRM format — a text-based format which allows you to recover corrupted or accidentally-deleted .MAP files, or allows you to move a map from one folder to another (see Importing an MRM Map, page 6-20, for more information.
Creating Network Maps The selected map or folder will be deleted without further confirmation. Note that deleting a map deletes only the .MAP version of the map file; the .MRM version remains intact in the assigned directory and can be re-imported at any time. (To remove lingering .MRM files, use the Windows Explorer or any other Windows file management application.
Creating Network Maps 6-64 Managing Maps and Folders
Chapter 7 Node Management Overview Device management overview; using Source Address Naming; using the PING tool This chapter provides a brief overview of some of the management capabilities provided by NetSight Element Manager, including device management, source address naming, and the use of the PING tool. Device Management NetSight Element Manager provides extensive device management capabilities through its Device Manager and Chassis Manager applications.
Node Management Overview 1. In any map, list, or tree view, click the right mouse button once to select the device you wish to manage. 2. On the resulting menu, click to select Manage. You can also access Device Manager and Chassis Manager from the Start menu: 1. From the Start menu, select Programs > Enterasys Networks > NetSight Element Manager > Device Manager (or Chassis Manager). 2. Enter the desired IP address and community name, and click OK. The Device View opens.
Node Management Overview A Device View displays information for a single module; a Chassis View, for all modules installed in the chassis. Interfaces are color-coded to indicate status. Basic information about the device, including contact status, surrounds the port display area. The question mark in the status icon indicates that NetSight Element Manager does not recognize the device type. Figure 7-1.
Node Management Overview TIP The Chassis Manager application will generate an event when it is used to perform an SNMP SET; this event will record the MIB object and instance that was changed for tracking administrative actions on devices. All SNMP SETs made through Chassis Manager will be recorded in the Alarm and Events Manager’s cache by default. You can turn off logging of device SETs by using a text editor to edit the CTRON.
Node Management Overview For this function to work your ENETADDR.DEF file must be saved in a text-only format. NOTE Figure 7-2 displays a sample ENETADDR.DEF file. Figure 7-2. Sample ENETADDR.DEF File 2. Edit the ctron.ini file by adding the following line under the heading [SpectrumElementManager2]: SrcAddrFileName= where is the path to the data directory in NetSight Element Manager (by default, \NetSight Element Manager x.x\bin). 3. Save and close the ctron.
Node Management Overview Figure 7-3. Sample Source Addresses Window TIP If you have Network Analyzer software, you can use the ENETADDR.DEF file generated by the Analyzer for all source addresses. Simply copy the existing file into the NetSight Element Manager data directory (by default, \NetSight Element Manager x.x\bin). If you are upgrading from a previous version, your existing ENETADDR.DEF file will automatically be saved and restored to the bin directory.
Node Management Overview A successful ping, and one which has timed out. Figure 7-4. The PING Window NetSight Element Manager sends a PING request to the selected device, and the response, if any, is displayed in the PING window.
Node Management Overview 7-8 PING
Appendix A Batch Customization via AddTool, AddImage, and AddDevType Using the AddTool, AddImage, and AddDevType tools to expand the capabilities of NetSight Element Manager Three options — the ability to add an option to the Tools menu, the ability to define a new Node Class to represent a device type, and the ability to define (and add an icon representing) a new Model, Class, Enterprise, or Topology value — are available external to the NetSight Element Manager framework via three executables: AddTool,
Batch Customization via AddTool, AddImage, and AddDevType Bubble Text Bubble text appears in a pop-up window when the mouse pointer is held over the associated Toolbar button. Command This parameter specifies the executable that will be launched when the associated Toolbar button or Tools menu item is selected. Note that you must specify a file which exists, or the AddTool operation will fail; you should also specify the full path to the executable.
Batch Customization via AddTool, AddImage, and AddDevType Large Image File You can use this optional field to specify the large (32x32 pixel) bitmap image file that will be associated with your application. Be sure to specify the path to the bitmap image. If you choose not to specify an image file, the default image associated with the application will be used. Note that the large image file is not displayed anywhere in the NetSight Element Manager framework.
Batch Customization via AddTool, AddImage, and AddDevType need not use placeholders for optional fields you do not wish to use. The end of each entry is signaled by a separator line containing three dots; any additional blank lines between entries are ignored. Note that the filename cannot contain spaces. If you choose to use the tag/data format for your input files, you must launch the AddTool utility with a special switch, as described in Executing the AddTool Command, page A-4.
Batch Customization via AddTool, AddImage, and AddDevType 3. Click OK to launch the utility. If the tool did not run successfully, an error message will appear, indicating the source of the problem. Note that the tool stops executing at the first error, so if your file contains multiple errors, they will only be detected one at a time, each time you run the tool If no message windows appear, the tools have been added successfully.
Batch Customization via AddTool, AddImage, and AddDevType Small Image File Use this field to specify the small (16x16 pixel) bitmap image file that will be used to represent your image in a variety of places within the NetSight Element Manager framework (in the appropriate Select Symbol window, in a List View or Tree View, etc.). Be sure to specify the path to the bitmap image.
Batch Customization via AddTool, AddImage, and AddDevType class, Roundabouter, c:\small_icons\round16.bmp, c:\big_icons\round32.bmp, 711 topology, RoundLAN, c:\small_icons\LAN16.bmp, c:\big_icons\LAN32.bmp, 712 model, KidMobile, c:\small_icons\car16.bmp, c:\small_icons\car32.bmp, 713 enterprise, Mom-n-Pop, c:\small_icons\folks16.bmp, c:\small_icons\folks32.
Batch Customization via AddTool, AddImage, and AddDevType ... Image Image Small Large Image ... TIP type : enterprise name : Mom-n-Pop image file : c:\small_icons\folks16.bmp image file : c:\small_icons\folks32.bmp id : 714 Although the sample input file shown here assigns a different Image ID value to each new image, images of different types can share Image IDs.
Batch Customization via AddTool, AddImage, and AddDevType Using the AddDevType Utility In addition to defining new node class attributes (as described in Using the AddImage Utility, page A-5), NetSight Element Manager also allows you to add entirely new node classes. Your new Node Class can use existing Model, Class, Topology, and Enterprise attribute types, or any new ones you have defined via the AddImage utility.
Batch Customization via AddTool, AddImage, and AddDevType Topologies This field specifies the Topology type or types which apply to the device defined by your new node class. You must select Topology images which have already been defined, and you must be sure to specify their names using the correct case. To specify multiple topology images, separate the values with commas; for a file in CSV format, enclose the entire attribute value in double quotes.
Batch Customization via AddTool, AddImage, and AddDevType Notes Use this optional parameter to specify any additional note information you’d like to display by default in the Properties window for devices represented by your new node class. Creating an AddDevType Input File You can create your AddDevType input file in one of two formats: multi-line tag/data format, or single-line comma-separated variable (CSV) format. Each method is described below.
Batch Customization via AddTool, AddImage, and AddDevType Tag/Data Format To create a file using the multi-line tag/data format, you must place each field name and the value you want to use in its own line. Field names and their values are separated by a colon with a space on either side. To specify multiple values for a single parameter (for example, multiple Class or Topology images), separate the values with commas.
Batch Customization via AddTool, AddImage, and AddDevType /D or /d signals that the input file is in CSV format, but does not contain the initial descriptive line input_filename specifies the path and filename of your input file 3. Click OK to launch the utility. If the tool did not run successfully, an error message will appear, indicating the source of the problem.
Batch Customization via AddTool, AddImage, and AddDevType A-14 Viewing the Log File
Index Symbols *.dmf 2-31 *.map files 2-31 *.mmp files 2-31 .dat files 2-31 .MAP files inadvertently deleting 6-59 .
Index Discover Process 3-16 Discover Properties Device 3-5 General 3-4 Discover Properties window, accessing 3-2 Discover Scripts deleting 3-18 Discover scripts 3-1, 3-2, 3-19 Discover Scripts, creating and modifying 3-2 Discover Scripts, executing 3-14 Discover Wizard 3-1 starting 3-19 Discovery Parameters IP Address Ranges 3-5 Subnets 3-7 Display As Icon 6-50 DLM Agent 4-35 DLM Client 4-35 DLM Client (Direct) 4-35 E embedded object 6-48 embedded objects converting 6-56 updating 6-53 ENETADDR.
Index M MAC address, locating 3-19 MAC search 3-25 manual insertion, when importing maps 6-22 Manual link updates 6-55 Map View 6-2 maps adding a bitmap background 6-10 adding connections 6-33 adding new 6-7 position in Map View hierarchy 6-8 adding non-manageable graphical objects 6-26 adding shapes and lines 6-34 adding symbols 6-27 and Discover 6-23 and folders, relationships 6-2, 6-6 and Goto symbols, relationships 6-4 and submaps, relationship restrictions 6-4 and submaps, relationships 6-3 changing 6
Index RMFLT.LDB 2-31 rmflt.
