NMS300 Software Release 1.5.0.11

This release notes contains features and known issues for NETGEAR ProSAFE NMS300 Network Management Software release 1.5.0.11.

NMS300 issues fixed on 1.5.0.11

• Removed the menu service start/stop in the start menu. The service start/stop menu doesn't work on windows 10. User can start/stop service via service manager which is provided by windows.
• On NMS300v1.4, SMTP uses computer's name to create a sender's email which is blocked by some SMTP server in some scenario.
• The Common STP data is not available for some switch models such as GS724TPS, GS48TPS, GS724TS, GS748TS, GS724TP, GS748TP, GS728TP, GS728TPP and GS752TP.
• Launching direct access to device web UI via HTTP/HTTPS from NMS300 fails for these device models - GS724Tv3, GS748Tv4, FS752TP, FS728TPv2, GS716Tv2, GS724TP, GS748TP, FS728TP, GS724TS, GS748TS, GS724TPS, & GS748TPS. The work around is to launch the device web UI directly via a web browser.

Enhancements since release 1.4:

• Support for additional switch, wireless access point & firewall devices. See table below.
• Support the user-defined threshold for the links in topology view. It allows users to define the threshold for TX / RX utilization or packets loss and flash the link when the monitored data exceeds the threshold.

• Support backup and restore NMS300 configuration and DB data to an external server on the network.
• Enhance MIB Browser UI, make it look and feel like other well-known MIB Browsers.
• Support new MIB files upload. It allows user to upload multiple new MIB file and compile them in MIB browser.
• Support SNMP set function. It allows user to change the value of OID.
• Support OID search function. It allows user to find MIB object based on a given OID or a MIB entry name.
• Search Host feature. It allows user to enter the IP or Mac address of the host, and the system will find the switch in the network that directly connects to the host.

The below list provides the specific device models which are now supported in NMS300 starting from this 1.5 release:

• XS728T
• WND930
• WAC720
• WAC730
• RN716X

NMS300 Known issues and limitations

• Some older managed switches do not support all features available in NMS300.
• SMS functionality is only working in P.R China, all of other countries or regions don't support it.
• Safari and IE9 don't support upload multiple MIB files one time.

Browsers supported by this Beta release of NMS300 are:

• Internet Explorer 9 and above
• Firefox
• Chrome
• Safari

Operating Systems supported by this release of NMS300 are:

• Microsoft Windows 7 (Professional, Enterprise and Ultimate) 32-bit & 64-bit
• Microsoft Windows XP (Professional) 32-bit & 64-bit with SP3 or later
• Windows Server 2008 (Enterprise) 32-bit & 64-bit
• Windows Server 2003 (Standard, Enterprise and Web), 32-bit & 64-bit
• Windows Server 2012 (Standard) 64-bit
• Windows 8 Enterprise 64-bit
• Microsoft Windows 10 (Home) 32-bit & 64-bit
• Microsoft Windows 10 (Pro & Enterprise) 32-bit & 64-bit 

System requirements for this release of NMS300 are:

• 2.8 GHz Dual Core CPU
• 4G RAM (32 Bit OS) or 8G RAM (64 Bit OS)
• 20G storage

Steps to get NMS300 up and running:

• There are 2 installers. One for 32bit Windows OS and another for 64bit Windows OS. Download the appropriate zip file, which corresponds to either 32bit or 64bit Windows, from the published web site.
• Using the Download Link below, download and extract the new firmware to a convenient place such as your desktop.
  
  Download Link:

  Win32 bit: http://www.downloads.netgear.com/files/GDC/NMS300/NMS300_V1.5.0.11(Win32).zip

  Win64 bit: http://www.downloads.netgear.com/files/GDC/NMS300/NMS300_V1.5.0.11(Win64).zip

•  
• Make sure to choose a machine that has static IP address assigned in order for running NMS300 on it. The NMS300 is a server application and it binds itself to the static IP address of the machine
• Unzip the file to obtain the executable installer file.
• Double click on this executable in order to launch the installer wizard.
• The wizard of the installer will guide you through the default settings and allows the user to customize them. For instance, if another application is already using port number 8080 on the Windows machine, then the user can modify this default setting to a different port number. Similarly, there are a few other settings which can be customized as well.
  Also, if you have multiple NICs (Network Interface Cards) on your machine, then make sure to choose the appropriate NIC in the NIC selection page in the wizard.
• Once the installer finishes executing, it will prompt you whether or not you want to reboot the system now. It is strongly recommended that you reboot the system at this point.
• Once rebooted, the NMS300 application should be up and running as a service.
• There is no need to enter a license key in order to get the NMS300 to start managing devices.
• In order to launch the NMS300 web GUI from the same machine as where you installed NMS300, enter the URL http://localhost:8080 . In case you had entered a different port number for the web server during the NMS300 installation, then make sure to replace 8080 in this URL with the port number you provided during installation.
• In case you are trying to access the NMS300 web GUI from a remote machine, then you can access it by replacing “localhost” with the IP address of the NMS300 machine.
• Make sure to clear your web browser’s cache prior to using the web GUI of NMS300. This will prevent you from encountering issues while using the web GUI of NMS300.
• Once you access the URL in a supported web browser, you will see the login page for NMS300 web GUI. The default user name is admin and the default password is admin

Notes:

• You will need to run the latest released firmware version for the devices in order to be able to manage the devices from NMS300. You will need to upgrade the device to the latest version by using the device’s web GUI since the device needs to be running the latest firmware before it can be discovered and become manageable by NMS300. However, once this one-time upgrade from device’s web GUI is done, future upgrade of the device’s firmware can be done centrally from NMS300 without having to use the device web GUI.
• NMS300 uses a combination of SNMP, HTTP and Telnet protocols to interact with the devices. Hence, it is crucial that NMS300 is configured with the correct port number and credentials in order to be able to communicate with the device and authenticate successfully with the device over these protocols. The way this can be achieved in NMS300 is by configuring the appropriate Device Credential. The Device Credential used during discovery of a device will remain associated with that device for subsequent interactions from NMS300 to the device.
  If the device is listening on a non-default port number for any of the above mentioned protocols, then make sure to reflect the correct port number in the Device Credential.
  If the devices have been reconfigured such that the default password for the admin user has been changed, then make sure to create a Device Credential in NMS300 that is set with the matching password for the admin user. Similarly, if the default SNMP community strings have been changed then make sure to create a Device Credential that is set with the matching community strings.
• NMS300 listens for SNMP Traps and it is crucial that the devices are configured to send SNMP traps to the NMS300 server’s IP address. Both SNMPv1 and SNMPv2 traps are supported.
• As already mentioned above, install the NMS300 on a machine with static IP address. The NMS300 is a server application and it binds itself to the static IP address of the machine
• As already mentioned previously, make sure to clear your web browser’s cache prior to using the web GUI of NMS300. This will prevent you from encountering issues while using the web GUI of NMS300.
• NMS300 by default allows you to manage up to 200 devices. The customer will be able to purchase a license if they need to manage higher device counts.
• NETGEAR ProSAFE Firewall FVS318G uses port number 8080 when HTTPS is enabled. Hence, ensure that the Device Credential configured in NMS300 has this port number configured within it.