[2022A04] =========================================================================== Nortel Networks Updated: 2/25/2000 Optivity NMS OIT Package README for New Device/Agent: BayStack 350 10/100 Series Autosense Switch, agent software v3.0 =========================================================================== OIT PACKAGE SUMMARY: ==================== This document contains installation instructions, new feature, and known restriction information for Optivity Integration Toolkit (OIT) files when used with the BayStack 350 10/100 Series Autosense Switch and version 3.0 software. These OIT installation instructions are not included in the Optivity and BayStack 350 10/100 Series Autosense Switch documentation. Manual installation of this OIT file will be required for Optivity NMS v9.0.x releases. For Optivity NMS 9.0 this OIT file requires the NMS 9.0.0.2 patch to be installed. DEVICES SUPPORTED: ==================== BayStack 350 10/100 Series Autosense Switches, running agent software v3.0 on the following BayStack devices with sysObjectID 1.3.6.1.4.1.45.3.30.2 BayStack 350T with Chassis ID 528 BayStack 350F with Chassis ID 529 BayStack 350F-HD with Chassis ID 530 BayStack 350T-HD with Chassis ID 531 Chassis ID is available in the s5ChasComTable NOTE: **** This OIT package requires NMS 9.0.0.2 or later **** NOTES FOR INSTALLATION: ======================= All installation commands are relative to the directory containing the extracted (un-tarred or un-zipped) OIT package. The following commands should be executed in that directory. The default locations for an Optivity install are: Unix ($OITHOME): /usr/oit Windows 95/98/NT (%OITHOME%): :\Optivity\OIT Installing on UNIX ------------------ 1. Install the NMS 9.0.0.2 patch (not required with NMS 9.0.1 or later). 2. On your workstation, log into Optivity NMS as root (su command). 3. Open a unix shell window and prepare your user environment with one of the following commands: source /opt/lnms/bin/opt_cshrc (for csh and tcsh) . /opt/lnms/bin/opt_kshrc (for sh or ksh) 4. In the /usr/oit directory, create the following subdirectory structures: mkdir ${OITHOME}/wpd/baystack/common/ 5. Copy contents of the OIT package to various locations: cp *.mib ${OITHOME}/wpd/baystack/common cp *.mi1 ${OITHOME}/wpd/baystack/common cp NMS-bs350c-v30-A.oit ${OITHOME}/wpd/baystack 6. At the command prompt, type (you must have superuser permissions): oitInstall -u $OITHOME/wpd/baystack/NMS-bs350c-v30-A.oit where -u indicates to upgrade Optivity NMS. If you do not specify the -u parameter, a syntax check only is performed on the OIT file. Installing on PC ---------------- 1. Install the NMS 9.0.0.2 patch (not required with NMS 9.0.1 or later). 2. On your workstation, log in as administrator 3. Open a command prompt 4. In the \usr\oit directory, create the following subdirectory structures: mkdir %OITHOME%\wpd\baystack\common\ 5. Copy contents of the OIT package to various locations: copy *.mib %OITHOME%\wpd\baystack\common copy *.mi1 %OITHOME%\wpd\baystack\common copy NMS-bs350c-v30-A.oit %OITHOME%\wpd\baystack 6. Run the oitInstall executable as follows: oitInstall -u %OITHOME%\wpd\baystack\NMS-bs350c-v30-A.oit where -u indicates to upgrade Optivity NMS. If you do not specify the -u parameter, a syntax check only is performed on the OIT file. Installation Results -------------------- When you installed Optivity NMS, the installation program copied an oitinstalled.cnf file and an oitapplied.cnf file to the default location. These were empty files. When you upgrade Optivity NMS with new device support, these files are updated with an entry for the new device support. The contents of the oitinstalled.cnf and oitapplied.cnf in the file should be the same. An entry in each of the *.cnf files is as follows (each installed OIT package creates a line of format " "): # This file contains all the OIT updates that are potential # update candidates. (UNIX EXAMPLE) NMS-bs350c-v30-A.oit /usr/oit/wpd/baystack NMS-bs350-v20-B.oit /usr/oit/wpd/baystack NMS-bs410-v20-B.oit /usr/oit/wpd/baystack NMS-bs450-v20-B.oit /usr/oit/wpd/baystack NEW FEATURES IN THIS RELEASE: ============================= -- Autotopology. With this OIT package, links between BayStack and other Nortel network devices can be automatically detected and depicted in the InfoCenter Datalink Layer View and InfoCenter Physical Layer View options (by using the Format > Graphical menu option). -- OmniView support o Autotopology (s5 Ethernet Multi-Segment Topology MIB) o Spanning Tree Groups and Ports (Rapid City Enterprise MIB) OLD FEATURES REMOVED IN THIS RELEASE: ===================================== None BUGS FIXED IN THIS RELEASE: =========================== None FILES ASSOCIATED WITH THIS OIT KIT: =================================== ~--~--~ README.txt NMS-bs350c-v30-A.oit rfc1213.mib rfc1493.mib rfc1643.mib rfc1757.mib rfc1902v.mi1 rfc1903v.mi1 rvlan000.mib s5age140.mib s5cha127.mib s5emt104.mib s5ifx100.mib s5roo115.mib s5tcs112.mib synro167.mib ~--~--~ KNOWN LIMITATIONS: ================== -- After installation of the NMS 9.0.0.2 patch and the BayStack 350 10/100 Autosense Switches V3.0 OIT packages and a subsequent rediscovery of any subnets which contain these devices, it may appear that some of the devices have "duplicates" within the InfoCenter subnet view. These "duplicates" are actually two different database object representations of the same device in the subnet. They appear to be duplicates because the label names are the same. This situation can be corrected in the following manner: 1. On Unix based systems, use a text editor to open the file: $LNMSHOME/apps/topology/topology.cnf On NT based systems the file is: %LNMSHOME%\apps\topology\topology.cnf 2. Change the value for the "Age_Out_Period" parameter to 0 (the number Zero). 3. Save the file. 4. Run the topology "rediscover" process for any subnets which exhibit the problem. This will clear most (if not all) situations of this type. If the effect is not seen immediately, it may be necessary to simply refresh the InfoCenter subnet view which you might have had open when you ran the rediscover process against the subnet. In most cases the view will refresh itself. When you are finished, it is advisable to return the Age_Out_Period value back to your normal setting. -- When you use the Datalink and Physical views, you must use the graphical format in order for the layout options to display accurately. -- OmniView RMON->History Table displays error message "Pane is not supported" CR # 113708-1 -- The first port in a Multi-Link Trunk is used to report the dot1dStpPortEnable state of the whole trunk. All other members of the trunk will not report the Spanning Tree state. For example, if ports 3, 4, 5, and 7 are members of a trunk, getting the dot1dStpPortTable will contain the following: dot1dStpPortEnable.1 I enable dot1dStpPortEnable.2 I enable dot1dStpPortEnable.3 I enable <-- 1st trunk member dot1dStpPortEnable.6 I enable dot1dStpPortEnable.8 I enable ... As a result the Omniview "Ports-by-Slot" pane will not display column information for interface (IF) numbers of ports which are members of a multilink trunk or in addition for IF numbers of ports directly adjacent to IF numbers of ports which are members of multilink trunks. CR # 1121172-1 -- When viewing OMNIVIEW's Slots - Profile Pane for a BayStack 350T-HD or 350F-HD, the Model column will return an OID rather than a logical name for the device. To determine the correct device model, use the table below: Device OID Returned 350T-HD 1.3.6.1.4.1.45.1.6.1.3.6.531 350F-HD 1.3.6.1.4.1.45.1.6.1.3.6.530 CR # 121169-1 -- Omniview pane "Autopology - Network Managment Module (NMM) Data" if left open may not reflect proper information after multiple topology changes occur on connected devices. For the most up to date topology information you must close, then reopen the "Autopology - Network Managment Module (NMM) Data" pane against the device being monitored. CR # 121893-1 (c) 1998-2000 Nortel Networks Incorporated. All rights reserved. ===========================================================================