NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NMS 2.0 Rev B Update DOCUMENT ID: TID200043 DOCUMENT REVISION: A DATE: 29APR94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: NMS190.EXE NOVELL PRODUCT and VERSION: NetWare Management Systems 2.0 ABSTRACT: This is an update to NMS 2.0. It contains three pieces, update to the NMS 2.0 Console, update to the NMS 2.0 NetExplorer(tm) server, and update to the NMS 2.0 install. Read the entire NMS190.TXT document before upgrading your installation. WARNING: Install NMS 2.0 Rev B one time only. Multiple installations of NMS 2.0 Rev B will overwrite backup copies of NMS 2.0 files and will invalidate the NMS 2.0 Rev B deinstallation procedures. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ADDITIONAL CONFIGURATION Other: NOTE: NetWare Client 1.1 If you are running a version of the NetWare Client(tm) software that is earlier than 1.1, Novell recommends that you upgrade to the latest version. To determine the version of NetWare Client software you are running, type the following command in the directory that your NetWare Client software is located in: VERSION VLM.EXE If the version you are running is earlier than NetWare Client 1.1, you can get the latest version of NetWare Client software from the NOVFILES library on the NetWire(R) electronic bulletin board. It is included in the DOSUP9.EXE file. SYMPTOM This is an update to NMS(tm) 2.0. It contains three pieces, update to the NMS 2.0 Console, update to the NMS 2.0 NetExplorer(tm) server, update to the NMS 2.0 install. The NMS 2.0 Console and NMS 2.0 NetExplorer server updates add functionality as described below. The update to the NMS 2.0 install permits the installation of the NMS 2.0 NetExplorer server without installing the console software during the same session. TROUBLESHOOTING NOTE: NMS 2.0 was previously updated with a patch release on the NetWire(R) electronic bulletin board. This release was titled NMS 2.0a and was withdrawn because it had the following problem: In the NMS 2.0a release, the Alarm Monitor and the Alarm Report did not display the alarm information correctly for some alarms. Specifically, some of the fields in the Alarm Report would read "not available" instead of correctly reporting their status. SOLUTION This release (NMS 2.0 Rev b) corrects this problem and should be installed for all users of NMS 2.0 and NMS 2.0a as described in this README file. Self-Extracting File Name: NMS190.EXE Revision: A Files Included Size Date Time \ NMS190.TXT (This File) NMS.TXT 16288 04-29-94 11:03a SETUP.BMP 22812 04-13-94 3:09a SETUP.EXE 276480 04-13-94 3:09a SETUP.INS 21059 04-13-94 3:09a SETUP.PKG 677 04-13-94 3:09a NMSPATCH.Z 904195 04-13-94 3:09a INSTALL.INS 83358 04-13-94 3:09a NMSSTAR.BMP 5998 04-13-94 3:09a NMSPATCH.DLL 25664 04-13-94 3:09a N_NMSVER.DLL 5216 04-13-94 3:09a N_SHUTDN.DLL 4432 04-13-94 3:09a Installation Instructions: PREREQUISITES FOR INSTALLING THE NMS CONSOLE UPDATES 1. We recommend that you run the NetWare Client 1.1 on your NMS Console. 2. The NMS 2.0 software should be installed and performing in a functional manner on your Console PC. 3. You should have a minimum of 10 MB of free disk space on the disk drive where the NMS 2.0 software resides. INSTALLATION WARNING: Install NMS 2.0 Rev B one time only. Multiple installations of NMS 2.0 Rev B will overwrite backup copies of NMS 2.0 files, and will invalidate the NMS 2.0 Rev b deinstallation procedures. Before installing the NMS 2.0 Rev b updates, check that all the following files are present and have the correct size and date: NMSPATCH Z 904193 04-13-94 3:09a NMSPATCH DLL 25664 04-13-94 3:09a SETUP EXE 276480 04-13-94 3:09a SETUP INS 21059 04-13-94 3:09a INSTALL INS 83358 04-13-94 3:09a SETUP PKG 677 04-13-94 3:09a N_NMSVER DLL 5216 04-13-94 3:09a NMSSTAR BMP 5998 04-13-94 3:09a N_SHUTDN DLL 4432 04-13-94 3:09a SETUP BMP 22812 04-13-94 3:09a INSTALLING THE NMS CONSOLE AND NMS NETEXPLORER SERVER UPDATES To install the NMS Console update, the NMS NetExplorer server update, or both, complete these steps: 1. Before continuing with the NMS Console installation, close all the NMS applications running on your system. If you fail to close any of the NMS applications, a dialog box will appear for each application that is open, requesting you to close it. You should respond "Yes" to any of these requests. 2. Run the SETUP.EXE program from the MS Windows Program Manager. 3. Select the checkbox labeled Console Update, the checkbox labeled Server Update, or both, then click OK. If you selected only the NMS Console Update, the Setup process continues to completion. Skip to Step 5. Otherwise, Setup presents a list of servers to choose for updating. Continue with Step 3. 4. Select one NetExplorer server to update. If you need to update more than one server, complete this procedure and then run Setup again. 5. Enter the server name and password when Setup prompts you. The user must have SUPERVISOR equivalent privileges. The Setup process continues to completion. 6. If you successfully updated the NMS Console software, exit MS Windows; then start MS Windows again to ensure that the console software is loaded properly. 7. If you updated a server, restart the server. If you want to update another server, run Setup again. You do not need to restart MS Windows each time you update an additional server. INSTALLING THE NMS 2.0 INSTALLATION UPDATE This update modifies the NMS 2.0 installation software to let you install NMS 2.0 NetExplorer software on a different server, or to reinstall it on the previously selected server (without installing the NMS Console software). 1. Format a 3.5-inch high-density (1.44 MB) floppy diskette and label it NMS 2.0 Setup (Update). 2. Copy the contents of the NMS 2.0 Setup diskette (shipped with NMS 2.0) to the NMS 2.0 Setup (Update) diskette. 3. Copy the INSTALL.INS file to the root directory of the NMS 2.0 Setup (Update) diskette. 4. Use the NMS 2.0 Setup (Update) diskette in place of the original NMS 2.0 Setup diskette when you install NMS components. DEINSTALLING THE NMS CONSOLE AND NMS NETEXPLORER SERVER UPDATES To remove the NMS 2.0 Rev b Console Updates and restore the NMS 2.0 environment, copy the following files from the BACKUP subdirectory of the directory where NMS 2.0 was installed to their respective directories listed below: DIRECTORY FILE --------- ------------ BIN N_TDNW.DLL BIN N_NETADD.DLL BIN N-OLF.DLL BIN N-ICON.DLL BIN N-SNOOPR.DLL BIN N-DB.DLL BIN N-TABLE.DLL BIN N-VER.DLL BIN N-NMSVER.DLL BIN WBTRCNMS.DLL BIN N-OLFI.EXE BIN N-HUBUTL.DLL BIN N-HUBGTB.DLL BIN N-HUBMAN.DLL BIN N-HUBCON.DLL BIN N-HUBRES.DLL BIN N-HUBMIB.DLL BIN N-HUBNOD.DLL BIN N-HUBDRW.DLL BIN N-HUBMAP.DLL BIN N-HUBDAQ.DLL BIN HSMID.DLL OLF N-HUBNOD.OLF OLF N-HUBMAN.OLF OLF N-HUBMAP.OLF VERSIONS N_TD.VST VERSIONS N_RSM.VST VERSIONS N_HSM.VST VERSIONS N_NMM.VST [windows] HSM.INI Where: [windows] denotes the location where MS Windows is installed on the system. To remove the NMS 2.0 Rev b Server Updates and restore the NMS 2.0 environment, copy the following files from the BACKUP subdirectory in the root of the "SYS" volume of the chosen server to the NMDISK directory of the same volume: NXPIP.NLM NXPIPX.NLM After copying the NXPIP.NLM and NXPIPX.NLM files, as described above, restart your server. --------------------------------------------------------- INSTALLATION NOTES =================== This section lists items to help you install NMS 2.0 software and related NMS products. � Verify that SHARE is running on the NMS workstation console. � If a copy operation fails while you are installing the NetExplorer software, you encounter the error message "Unable to copy or decompress file..." and, after you click OK, the installation program exits immediately, it might be due to one of the following: � SHARE is not loaded. Load SHARE and try to install the NetExplorer software again. � Too little conventional memory is available on your console. A minimum of 580 KB of base memory is required. Free some conventional memory by unloading some TSRs and install the NetExplorer software again. � You are logged in during the NMS installation process. Log out of the servers on which you want to install NetExplorer and NetExplorer Plus(tm) software. Note: The installation program logs in during the installation process. � NMS 2.0 is compatible with both NetWare Management Agent(tm) 1.0 and 1.5 software, but Novell recommends that you upgrade to NetWare Management Agent 1.5 for the patches, bug fixes, performance improvements, and additional server alarms it provides. However, do not install the NMS updates that come with NetWare Management Agent. They overwrite more current files included with NMS 2.0. Additionally, if you have NetWare Management Agent 1.0, install it before NMS 2.0. NetWare Management Agent 1.0 must not be installed on a server after NMS 2.0 or after NetWare LANalyzer Agent 1.0, because it causes them to malfunction. (Specifically, installing NetWare Management Agent 1.0 over the newer products overwrites the NMSBASE.NCF file, fails to load newer software patches, loads SNMP with community names that do not allow SET commands from the NMS Console, and prevents packet capture and top station statistics functions from operating on the server.) __________________________________________________________ KNOWN PROBLEM ============== After changing the configuration of a NetWare server (changing the operating system, protocols, or network cards), the NetExplorer server must be brought down, or the NetExplorer NLM files must be unloaded, then reloaded. Otherwise, the old configuration information appears in the maps. __________________________________________________________ KNOWN PROBLEM ============== If you are running NetExplorer on any NetWare 4.x server, update STREAMS with the set of STREAMS NLM files provided on the NMS 2.0 release diskette, or use any STREAMS NLM files later than version 4.01. Problems occur if NetExplorer runs with the original NetWare 4.01 STREAMS NLM files. The following symptoms might indicate that STREAMS NLM files need to be updated: � You cannot communicate from the NMS Console to NetExplorer using the IPX(tm) protocol. � The NetExplorer discovery process stops unexpectedly (there are no error messages indicating that this occurred). � An error message is displayed with a negative value error code. The STREAMS NLM files provided on the NMS 2.0 release diskette are not updated automatically by the installation process and must be copied manually. Use the README.TXT file provided on the NetWare 4.01 Server Update Disk to update the set. If the server already has a later version, disregard. The STREAMS NLM files provided on the NMS 2.0 release diskette are as follows: � IPXS.NLM 8-23-93 � SPXS.NLM 9-14-93 � TLI.NLM 9-14-93 � STREAMS.NLM 9-14-93 __________________________________________________________ Solution Specifics: The update to the NMS 2.0 install permits the installation of the NMS 2.0 NetExplorer server without installing the console software during the same session. NEW FEATURE - IPX Scoping (NetExplorer Server) ============================================== In NMS 2.0, it was possible to specify IP network addresses to be used to control the scope of IP discovery. This upgrade adds a similar feature to IPX(tm) discovery. This section describes that feature, and explains how you can use scoping. DESCRIPTION Typically, NetExplorer attempts to discover all nodes within the IPX internetwork. If your internetwork is large, you might not be interested in discovering all parts of it. IPX scoping allows you to restrict the scope of IPX discovery to certain IPX network numbers. You specify a list of IPX network numbers to be discovered. Only these networks, and IPX nodes connected to these networks, are discovered. The effect of this is to reduce memory, disk usage, bandwidth, and CPU usage on both your NetExplorer server and your NMS Console. It also reduces traffic on your internetwork. By restricting discovery to only those networks in which you are interested, NMS is also likely to detect any changes that occur in your network more quickly. These are the steps you should take to use IPX scoping: 1. First, you need to decide which IPX networks you want to include in your normal scoping. One way to decide this is to first run NMS without scoping, and then decide which networks you want from the NMS internet map. Alternatively, you can use the DISPLAY NETWORKS command at the console of the server running NetExplorer. This displays a list of all IPX networks in your internetwork, and shows the hop count and an estimate of the delay to reach that network. The delay is in units of 1/18th of a second. For example: 00001232 5/6 means that Network 00001232 is 5 hops away - delay is 6/18 second. A good approach is to start by including only networks that are close, just a few hops away. Note that a network will only be discovered if there is a path to that network through networks that are also in the specified list. All nodes that are attached to a particular IPX network are discovered, even if they have other IPX addresses that are not within your specified scope. 2. The network numbers that you want to include in the scope of your IPX discovery need to be included in the SYS:\NMDISK\NXPINI.INI file using the format specified below. Note that you can use the '?' character to match any single hexadecimal digit. This is most useful if IPX network numbers have been assigned with some geographical or other administrative significance. 3. If you have previously discovered IPX networks that are no longer in your specified scope, you should reset your NMS database before reloading NetExplorer on your server. PROCEDURE Add to the SYS:\NMDISK\NXPIPX.INI file a line of the following format for each IPX network to be included within the scope of IPX discovery: IPXQNET=xxxxxxxx where * IPXQNET can be in uppercase or lowercase. Each IPXQNET line specifies an IPX network, which can be an IPX internal network number or an IPX network number to which a network node interface is bound. * The discovery scope MUST include the IPX network number where the NetExplorer software resides. If this network number is omitted, nothing is discovered by NXPIPX. * Scoping can consist of a single network or a list of networks. If no valid IPXQNET line is specified, NXPIPX interprets that as indicating that IPX discovery is not to be restricted. * All IPXQNET network number values are hexadecimal. If an invalid value is entered on an IPXQNET line, NXPIPX displays the invalid value and the file location on the system console and unloads NXPIPX with error code 10061. * A network is only discovered if there is a path to it through networks that are also in the specified list. That is, NXPIPX cannot go through an unlisted network to get to a listed network. * xxxxxxxx is an 8-digit hexadecimal string. If there are fewer than 8 digits, it is padded with leading zeros. * A question mark (?) can be used as a wildcard to indicate that any value can be accepted in that specific digit position. For example: IPXQNET=C824???? IPXQNET=C834???? IPXQNET=C7?????? IPXQNET=7777ABCD This restricts IPX discovery to IPX network numbers that begin with the values C824, C834, or C7, and to the network 7777ABCD. If a node is connected to more than one IPX network, that node is discovered if any of its addresses are specified. This means that a system with an IPX internal network number is discovered, even if the internal network has not been specified as long as the IPX network number of at least one of its interfaces has been specified. For example, in the following topology, where there are two NetWare servers (S1 and S2) and one IPX workstation (W1), it is only necessary to specify the IPX network numbers of the two LANs (120000C6 and 120000C7) to discover all three nodes, and any other nodes connected to these LANs. ------- | W1 | Workstation ------- | | ------------------- Network 120000C6 | | ------- | S1 | - Internal Network 120000FF ------- | | -------------------------- Network 120000C7 | | ------- | S2 | - Internal Network 12000076 ------- RESTRICTIONS TO IPX SCOPING 1. If a node that was previously within the scope of IPX discovery is moved to a network that is outside that scope, the change is not detected - the node remains in the database at its old location. To remove this node, you should take the following steps: - Unload the NetExplorer software on your server. - Delete the node from the NMS map (using Edit->Delete) or reset your NMS database. - Reload the NetExplorer software on your server. 2. Setting up IPX scoping does not totally eliminate NetExplorer IPX traffic outside the networks specified. This is because IPX discovery periodically tries to see whether there are any new IPX addresses that match one of the specified networks. 3. The presence of NetWare LANalyzer(R) Agent(tm) software in your internetwork might result in networks that are outside the IPX scope continuing to be discovered. The solution is to make sure that the NetWare LANalyzer Agent SAP type (570 decimal, 23A hex) is being filtered between all NetWare LANalyzer Agent software that is outside the IPX scope, and your NetExplorer discovery server. The simplest way to do this might be to ensure that all your routers filter out this SAP type, so that the SAP is never sent beyond the local network where the NetWare LANalyzer Agent generated it. SAP filtering can be performed in any NetWare 3.11 server or later. When doing this, be careful only to filter the NetWare LANalyzer Agent from networks that you do not want to discover. Indiscriminate filtering of the NetWare LANalyzer Agent SAP could result in a diminished capacity to discover networks within your desired scope. After you have set up these filters, you should take the following steps: - Unload the NetExplorer software on your server. - Reset your NMS database. - Reload the NetExplorer software on your server. 4. Nodes that do not respond to IPX diagnostic requests show up in discovery in progress. This is true even for nodes that are outside the scope, because they do not provide enough information to determine that they are not within the discovery scope. __________________________________________________________ NEW FEATURE - IP Scoping (NetExplorer Server) ========================================== IP discovery, by default, discovers routers that are within the network to which the NetExplorer system is directly attached. NMS 2.0 has a feature to allow you to expand discovery to other networks, by specifying these addresses in the NXPIP.INI file. This release adds the ability to specify a network of *.*.*.*, which means discover all IP networks. DESCRIPTION This section describes how you can set up IP scoping using either specified IP network numbers or the new *.*.*.* wildcard network number. By default, the NetExplorer discovery software discovers IP routers on only the local IP network, as defined by the class of the IP network. The class of your IP network is determined by the first byte of your IP address: The range of class A addresses is 1-127. The range of class B addresses is 128-191. The range of class C addresses is 192-223. For class A addresses, the IP network is the first byte. For class B addresses, the IP network is the first two bytes. For class C addresses, the IP network is the first three bytes. Format of a class A address: ------------------------------------- | | | | | |Network | | | | | | | | | ------------------------------------- Format of a class B address: ------------------------------------ | | | | | |<--- Network --->| | | | | | | | ------------------------------------- Format of a class C address: ------------------------------------- | | | | | |<-------- Network ------->| | | | | | | ------------------------------------- Examples: Your server has an IP address of 195.6.25.4. This is a class C address. IP discovery is restricted to network 195.6.25.0. Your server has an IP address of 139.56.15.9. This is a class B address. IP discovery is restricted to network 139.56.0.0. This includes all IP subnetworks within this network. Your server has an IP address of 33.22.2.11. This is a class A address. IP discovery is restricted to network 33.0.0.0. This includes all IP subnetworks within this network. Note: NetExplorer finds the local IP network address by examining the first address that is bound to a driver on the NMS Server. If the server has multiple bindings to subnetworks that are in different networks, all the networks must be included in SYS:\NMDISK\NXPIP.INI. Otherwise, only the first IP network is discovered. If you want to extend the range of IP networks discovered by NetExplorer, you should edit the file SYS:\NMDISK\NXPIP.INI on the server to list the IP networks that you want to add. For example: 89.0.0.0 139.56.0.0 195.6.25.0 This adds three IP networks: a class A network, a class B network, and a class C network to the scope of IP discovery. NetExplorer IP discovery does not discover a system in a listed IP network, unless all the IP networks needed to reach that network are also listed. An IP node with more than one IP address is discovered if any of its IP addresses is in a listed network. This release adds the ability to specify a wildcard network of *.*.*.*, which means discover all IP networks. Note: Novell recommends that you do NOT use this feature if your IP internetwork is connected to the Internet, because you might unintentionally start discovering the Internet. The Internet is a worldwide internetwork that connects many public and private institutions. If you have an Internet connection and still want to use the IP wildcard address (*.*.*.*), you should ensure that the community access string of the router that is the boundary between your internetwork and the Internet is unique and DOES NOT appear in the SNMP community strings file on the NMS Server. This prevents NetExplorer from discovering this router, and any routers beyond it. Reminder: The SNMP community strings filename, if used, is described in the NETXPLOR.NCF file and is used with the /C parameter on the LOAD NXPIP command line. It includes the SNMP community strings used by the routers in your internetwork, if they use any string other than "public." Note: Because IP discovery only discovers one IP network by default, IP scoping is a means to extend discovery to other IP networks. IPX scoping, on the other hand, is a means of restricting IPX discovery so that instead of the whole IPX internetwork, only certain IPX networks are discovered. IP scoping cannot be used to restrict discovery to anything less than the local IP network, as defined by the class of the IP address. Note: For more information about the discovery process, see the "NetExplorer Rules of Thumb" document supplied with NMS 2.0. RESTRICTION TO IP SCOPING If a node that was previously within the scope of IP discovery is moved to a network that is outside that scope, the change is not detected - the node remains in the database at its old location. To remove this node, you should take the following steps: � Unload the NetExplorer software on your server. � Delete the node from the NMS map (using Edit->Delete) or reset your NMS database. � Reload the NetExplorer software on your server. __________________________________________________________ NEW FEATURE - Avoiding NetWare Server Connections (NetExplorer Server) ========================================================== NetExplorer temporarily takes up an NCP connection on each server it discovers. For some servers, this might not be desirable, specifically, when the server has no connections to spare and is periodically performing some operation. This is particularly problematic for servers that use NetWare Runtime(tm) software and have only one login connection, such as Intel* StorageExpress*. NetExplorer logs in to the server only to determine the usernames for workstations. It queries the mapping between IPX address and logged-in user. It ignores GUEST and SUPERVISOR logins. NetExplorer can avoid logging in to servers for well-known Service Advertising Protocol (SAP) values by entering these values in the NXPIPX.INI file in the NMDISK subdirectory of the server. For example, you might enter the following lines: ServiceOnAServerNotToBeQuery = 376 ServiceOnAServerNotToBeQuery = 43B where: * All values are hexadecimal. * The equal sign (=) is required between the keyword and the value, but spacing before and after the equal sign is not required. The values shown in the sample lines exclude Intel StorageExpress servers from workstation discovery. The benefit of excluding a server from being queried is that it avoids disruption of critical services, such as server backups. The disadvantage of excluding a server from being queried is that it will not be discovered by NMS. __________________________________________________________ NEW FEATURE - Avoiding Consolidation (NMS Console) ================================================== Network devices that have the same MAC address for multiple instances of the same device are improperly consolidated on the NMS maps. The NetExplorer software attempts to consolidate every individual instance of these devices into a single device on the map. To avoid these consolidations, add a DupMac entry to the NMS.INI file, which is located in the MS Windows directory on the NMS Console for every duplicate MAC address on your network. Each entry must have the following form: DupMacn=MAC_address where: * n is a number that is incremented for each DupMac entry. * MAC_address is the specific MAC address that is duplicated. Your NMS.INI file has DupMac1 and DupMac2 entries by default; you might have added DupMac3, DupMac4, and so forth, because of previously overconsolidated segments. The following devices are known to have this problem: 1. NetWare Connect(tm) servers 2. NetWare SNA Links(tm) software 3. Cubix Series 3000 and Series 4000 communications processors 4. NetWare MultiProtocol Router(tm) 2.1 or later software 5. NetWare DOS Box NLM(tm) software To prevent the improper consolidation problem for any of the devices mentioned above, add the following DupMac entry to the NMS.INI file: DupMacn=000000 This problem exists only if you have more than one of these devices on your network. If you have only one of these devices on your network, you do not have to do anything. __________________________________________________________ NEW FEATURE - IP Timeout (NetExplorer Server) ============================================= If IP discovery is being performed over low speed links such as a WAN, the default timeout of five seconds might be too short. The user can change this timeout by starting NXPIP.NLM with a different timeout value. This can be changed in the NETXPLOR.NCF file. For example: LOAD SYS:\NMDISK\NXPIP /t 10 This command changes the timeout to 10 seconds. Default is 5 seconds. __________________________________________________________ NEW FEATURE - Redundant Router Discovery (NetExplorer Server) ========================================================== Redundant routers were not discovered because the routers were not involved in the routing scheme. These can be discovered by adding the IP address of redundant routers to a file. To discover these routers, NXPIP.NLM should be loaded with the /a option, followed by the filename. This can be changed in the NETXPLOR.NCF file. For example: LOAD SYS:\NMDISK\NXPIP /a redrout.lst where the redrout.lst file contains the following entries: 132.54.20.2 121.22.50.72 __________________________________________________________ NEW FEATURE - Hub Services Manager Update (NMS Console) ======================================================= Hub Services Manager has been updated to support token ring and custom hubs. The use of this update requires support from the hub vendor. This update is transparent to the current hub management. Any information required to use the new interface is supplied by the hub vendor. __________________________________________________________ CORRECTION TO OPERATION - View IP Networks Connections (NMS Console) ========================================================== The calculation for the legal host address range hasn't always been correct when you selected Open->View->IP Networks and double-clicked an entry to bring up the IP Nodes list. This has been corrected. __________________________________________________________ CORRECTION TO OPERATION - Some Routers Not Being Discovered (NetExplorer Server) ========================================================== The Object ID type in an SNMP request packet was set to ASN.1 type OBJECT IDENTIFIER, but should have been set to ASN.1 type NULL in the SNMP request packet. This resulted in some routers not responding to the SNMP request. This occurred in Timplex routers and some versions of Wellfleet routers. __________________________________________________________ NMS 2.0 Rev B Contents The files listed below constitute the NMS 2.0 Rev b update. The directories listed are the locations that the NMS 2.0 Rev b files are placed in through the installation process. Unless otherwise specified, directories are relative (subdirectories) to the location where NMS 2.0 is installed. DIRECTORY FILE SIZE DATE --------- ------------ ------ -------- BIN N_TDNW DLL 246880 04-12-94 5:41p BIN N_NETADD DLL 75008 04-12-94 7:44p BIN N-OLF DLL 82832 04-12-94 11:00a BIN N-ICON DLL 13440 04-12-94 11:06a BIN N-SNOOPR DLL 160208 04-12-94 12:02p BIN N-DB DLL 83520 04-12-94 10:58a BIN N-TABLE DLL 109216 04-12-94 11:46a BIN N-VER DLL 2992 04-13-94 11:40a BIN N-NMSVER DLL 5216 04-13-94 10:43a BIN WBTRCNMS DLL 51936 04-11-94 7:14p BIN N-OLFI EXE 37088 04-12-94 11:01a BIN N-HUBUTL DLL 81696 02-28-94 2:12p BIN N-HUBGTB DLL 11872 02-28-94 2:13p BIN N-HUBMAN DLL 69504 02-28-94 2:20p BIN N-HUBCON DLL 35600 02-28-94 2:15p BIN N-HUBRES DLL 125936 02-28-94 2:07p BIN N-HUBMIB DLL 32064 02-28-94 2:47p BIN N-HUBNOD DLL 289616 02-28-94 2:41p BIN N-HUBDRW DLL 14832 02-28-94 2:03p BIN N-HUBMAP DLL 39728 02-28-94 3:42p BIN N-HUBDAQ DLL 68000 02-28-94 2:46p BIN HSMID DLL 3488 02-28-94 2:48p OLF N-HUBNOD OLF 5809 09-28-93 6:25p OLF N-HUBMAN OLF 4266 08-23-93 11:06a OLF N-HUBMAP OLF 4037 08-23-93 11:06a VERSIONS N_TD VST 3040 04-12-94 5:45p VERSIONS N_RSM VST 3216 04-12-94 7:35p VERSIONS N_HSM VST 3072 02-28-94 2:48p VERSIONS N_NMM VST 3040 04-12-94 1:08p [windows] HSM INI 13833 01-04-94 2:24p [nmdisk] NXPIP NLM 156068 04-15-94 11:22a [nmdisk] NXPIPX NLM 346887 04-15-94 11:31a Where: [windows] denotes the location where Microsoft* (MS) Windows is installed on the system. [nmdisk] denotes the NMDISK directory in the root of the SYS: volume of the NetWare server chosen for installation. __________________________________________________________ Copyright (c) 1994 Novell, Inc. All rights reserved. Trademarks Novell, NetWare, the N-Design, and LANalyzer are registered trademarks and the NetWare Logotype (the teeth logo), IPX, NetExplorer, NetWare Client, NetWare Connect, NetWare LANalyzer Agent, NetWare Management Agent, NetWare Management System, NetWare MultiProtocol Router, NetWare Runtime, NLM, NMS, and NetWare SNA Links are trademarks of Novell, Inc. NetWire is a registered service mark of Novell, Inc. Intel is a registered trademark and StorageExpress is a trademark of Intel Corporation. Microsoft is a registered trademark of Microsoft Corporation. __________________________________________________________ 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 �