The Administrator Cannot Access the Web-based NMS

• Cause one: There is no reachable route.

   

  Ping the IP address of the Web-based NMS to be accessed on the PC. If the Web-based NMS cannot be pinged through, it indicates that there is no reachable route. In this case, check the setting of the IP address of the local PC or the interface on the .

   

• Cause two: The Web-based NMS is not bound to an IP address or the port number is incorrect.

   

  1. Run the system-view command to enter the system view.
  2. Run the display web-manager ip address command to view the IP address of the Web-based NMS.

     If there is no IP address in the information that is displayed, enable the Web-based NMS and bind the Web-based NMS to an IP address.

  3. Run the interface GigabitEthernet interface-number command to enter the Ethernet interface view.
  4. Run the ip address ip-address net-mask command to set the IP address of the interface.
  5. Run the quit command to return to the system view.
  6. Run the web-manager ip address ip-address [ port port-number] command to bind the Web-based NMS and the IP address.
      NOTE:

     If port-number is not set to 443, when you enter the IP address to log in to the Web-based NMS, add :port number after the IP address. For example, https://x.x.x.x:port.

   

• Cause three: The devices between the PC and the SVN3000, such as border firewalls, disable the port of the Web-based NMS.

   

  Run the telnet ip-address service-port command on the SVN3000 to check whether the port is enabled on the device between the PC and the SVN3000. If connections can be established, it indicates that the port on the device between the PC and the SVN3000 is enabled. Otherwise, enable the port on the device between the PC and the SVN3000.

   NOTE:

  Parameter ip-address indicates the IP address of the device between the PC and the SVN3000.

  Parameter service-port indicates the port number that the Web-based NMS uses.

   

Cause one: There is no reachable route.

Cause two: The Web-based NMS is not bound to an IP address or the port number is incorrect.

Cause three: The devices between the PC and the SVN3000, such as border firewalls, disable the port of the Web-based NMS.