FOXMAN-UN - Main/Standby Solution- Application Note
Executive Summary
The FOXMAN-UN Main/Standby Solution offers Network Management Redundancy in case a FOXMAN-UN System fails and thus helps protecting critical network infrastructure. Its simple concept, seamless integration into FOXMAN-UN and a clear number of components that support the operator in managing the solution makes it highly attractive for Hitachi Energy customers.
The concept of the FOXMAN-UN Main/Standby Solution is straightforward. In the beginning two servers are set up with a FOXMAN-UN system to manage the same network infrastructure. Apart from using different IP addresses, the setup of the two FOXMAN-UN systems is identical. One of the servers further on is acting as Main Server, the other one as Standby Server. The Main Server is brought into operational state, meaning FOXMAN-UN clients can connect to it and manage the network. The Standby Server is brought into standby state, meaning it is waiting to be operated in case of Main Server breakdown.
During this normal operational phase FOXMAN-UN database dumps of the Main Server are periodically copied to the Standby Server and imported to its database and IP addresses of Element Agents are properly replaced. The Standby Server on the other hand asks the Main Server at regular intervals for its state. In case the Standby Server cannot reach the Main Server or the Main Server reports to be no longer in operational state, the Standby Server deems the Main Server to be broken down. In this situation the Standby Server will behave differently depending on its type. If it is of type “Cold Standby” it will do nothing. An operator explicitly must bring it up to operational state. If it is of type “Warm Standby” it will automatically go to operational state. Now the Standby Server is ready to manage the network and FOXMAN-UN clients can connect to it.
A limited set of FOXMAN-UN components helps the operator to set up, maintain, and use the solution.
The NEM Remote Admin Tool is a Graphical User Interface which serves configuration, supervision and control of the Main/Standby solution.
The NEM Login Window displays Main/Standby-specific information whether a Server is a Standard, Main or a Standby Server and whether this Server is in “Not running”, “Standby” or “Running” state.
The NEM Host Manager displays Main/Standby-specific information whether a Server is a Standard, a Main, or a Standby Server and whether this Server is in “Not running”, “Standby” or “Running” state. It also shows the corresponding Partner Server of a Main or a Standby Server.
The NEM Desktop displays Main/Standby-specific information in the “Connected to” field whether the client is currently connected to a Standard, Main or Standby Server, or whether it has lost connection to the server.
The NEM Alarm List and Event List display alarms and events which are related to the operation of the Main/Standby solution.