6.10.1 |
Configuring HiPath 5000 RSM as a Central Administration Unit in an IP Network |
| The IP network is administered via the Feature server. The HiPath 3000/5000 Manager E administration tool does not communicate with the individual nodes but exchanges data with the Feature server. The Feature server ensures that the networked nodes receive synchronized CDB data. To facilitate this, a central customer database, the so called server net file, must be created for IP networking. |
6.10.1.1 |
Creating a Central Customer Database for IP Networking |
| An empty server net file must be created in order to create a central customer database for IP networking. |
Procedure |
| 1. | Start HiPath 3000/5000 Manager E. |
| 2. | Activate the HiPath 5000 RSM/AllServe server by selecting File - HiPath 5000 RSM/AllServe - Transfer or via the appropriate button in the toolbar. |
|
| 3. | The Transfer (HiPath 5000 RSM/AllServe Server) dialog appears. |
| 4. | The PC to be used as the HiPath 5000 server should be entered in the Server field. |
| Note: If the required software is not installed on the specified PC, the error message "HiPath 5000 RSM/AllServe Server not Installed on this PC" appears. |
| 5. | Click Server -> Manager to create an empty server net file. |
| 6. | Then click Close. |
6.10.1.2 |
Adding Individual Nodes for IP Networking |
| The next steps in creating a central database for IP Networking are the registration of the individual nodes and the transfer of the node data to the server net file. The server net file is now loaded to the Feature server. The customer database is then automatically distributed to the various nodes. |
| The prerequisite for adding nodes (HiPath 3000) to a HiPath 3000/5000 network is the successful installation (see Chapter 4 "Installing HiPath 3000") and startup (see Chapter 5 "Starting Up HiPath 3000") of these systems. |
Procedure |
| 1. | To select the node to be added to the CDB, call File - HiPath 5000 RSM/AllServe - New - HiPath 3000. |
| 2. | The Enter Source dialog appears. |
| 3. | Select the appropriate source: |
| • | Customer database file (to open a saved CDB file) In this case, select the appropriate CDB file in the Open customer database dialog displayed. |
| • | Create offline (to create a CDB generated offline) In this case, define the new CDB in the Enter node data dialog displayed. You must then configure customer-specific data. |
| • | Load from system (to load a CDB directly from a node) In this case, select the HiPath 3000 node with the CDB that is to be loaded from the subsequent Transfer (Communication Settings) dialog that appears. You must then start the transfer (system -> PC). |
| If the Copy netwide data in node option is activated, the service and substitution codes are copied from the CDB firstly created to all other CDB files of the node belonging to IP networking. |
| 4. | Clicking Finish opens the Transfer... dialog. Here, specify the node whose data should be read. |
| 5. | To add the node, invoke File - HiPath 5000 RSM/AllServe - Transfer - HiPath 5000 RSM/AllServe Server. |
| 6. | The Transfer (HiPath 5000 RSM/AllServe Server) dialog appears. |
| Apply the node data to the server net file by clicking the Add node button. |
| The number of nodes loaded during previous actions is displayed. |
| 7. | Finally, rewrite the data from HiPath 3000/5000 Manager E to the HiPath 5000 server (Manager -> Server button). |
|
| HiPath 3000/5000 V9, Service Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590S100017620 | 2014-02-27 |