13.6.16 |
Management Tools |
13.6.16.1 |
Overview |
| The following tools support administrators in performing their tasks: |
| • | Web-Based Management (WBM) via an integrated HTTP server |
| Provides a step-by-step configuration and easy access to all management functions. WBM is the primary management tool. |
| • | Command line (CLI) via a serial V.24 interface or Telnet |
| The command line is designed as the secondary management tool and provides a limited function scope. It can be used to modify certain configuration data, update and restart the system and to diagnose the system configuration. |
| Security-relevant settings (such as SSL configurations) cannot be made via Telnet. |
| • | SNMP-supported management via an SNMP agent |
| SNMP-supported management enables gateway integration in network management systems. Systems like this can manage devices from other manufacturers. |
| HG 1500 supports SNMP versions 1 and 2. Information such as statistics can be read and some important data can be modified using SNMP. Traps are also supported. |
| • | HTTP applications via a command interface |
| HG 1500 configuration data can be read out and modified and commands can be executed via the HTTP port. This applies to insecure (HTTP) and secure (HTTPS) connections. |
| The Universal Resource Identifier (URI) in the HTTP sequence is recognized by the gateway board as an administration command. The HTTP header contains information required for authentication. |
| In addition to the HG 1500 management tools, the HiPath 3000 Manager E is available. |
| • | HiPath 3000 Manager E |
| The HiPath 3000 Manager E is an independent application installed on a PC. It displays the relevant parts of the network as a virtual HiPath system. (Some HG 1500 settings can be configured both with this application and HG 1500 tools, depending on the version of the HiPath environment.) |
13.6.16.2 |
Multi-Gateway Administration (MGA) |
| The configuration of a large number of gateways, in particular, can cost administrators considerable time and effort, and so can - even only minor - modifications to a configuration. |
| HG 1500 therefore supports the distribution of configurations from a master gateway to any number of slave gateways. |
Prerequisites |
| In order to use Multi-Gateway Administration (MGA), no special hardware or software prerequisites are required on the gateways involved. However, the following conditions for configuration must be met: |
| • | All slave gateways must be able to be accessed by the master gateway via IP. |
| • | The port used for WBM must have the same number on each gateway (usually 8085) and must be accessible from the master gateway. Therefore, access must not be blocked by a firewall, for example. |
| • | All slave gateways must have a user access for MGA. All accesses must have the same name and password. This access must have root access privileges. |
| • | The slave gateways must be entered on the master gateway. (The list of slave gateways can also be imported by another master gateway, if necessary) |
Using MGA |
| The administrator first configures the master gateway as required. He then uses a command to transfer this configuration data to slave gateways. The administrator can specify individually to which slave gateways the data will be transferred and also select which configuration tables will be transferred. |
| HiPath 3000/5000 V9, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590S100017620 | 2014-02-27 |