start_h5.fm
P31003-H3550-S403-4-7620, 02/05
HiPath 3000 V5.0, HiPath 5000 V5.0, Service Manual
6-47
HiPath 5000 Startup and Administration
Perform HiPath 5000 Basic Configuration
6.10 Perform HiPath 5000 Basic Configuration
A distinction should be drawn between the basic configuration of a
● HiPath 5000 PC with HiPath ComScendo service
The HiPath ComScendo Service is virtually a complete HiPath 3000 node that is only con-
figured as software on a PC. Apart from the pure TDM features, all features of V5.0 are
available.
HiPath ComScendo Service is administered over HiPath 3000 Manager E, while the
HG 1500 resources (see Page 10-38) are administered over Web-based Management
(WBM).
● HiPath 5000 server as central administration unit in an IP network, with or without HiPath
ComScendo Service .The formation of a “single system image” allows the central admin-
istration of all associated nodes (HiPath 3000 and HiPath 5000 with HiPath ComScendo
Service).
The IP network is administered via the Feature server. The HiPath 3000 Manager E admin-
istration tool does not communicate with the individual nodes but exchanges data with the
Feature server. The Feature server ensures that the networked nodes receive synchro-
nized CDB data. The Feature Server is an MS Windows service that automatically starts
at the same time as the HiPath 5000 server.
HG 1500 boards are still administered on a board-specific basis using Web-based man-
agement (WBM).
The administration of IP networking with HiPath 3000 Manager E is divided into the follow-
ing steps:
a) Configuring the individual nodes belonging to the network (HiPath 3000 and HiPath
5000 with HiPath ComScendo Service) = Configuration of the individual customer da-
tabases.
b) Configuring the Feature server = Create an empty server net file.
c) Start data transfer = registration of the individual nodes and transfer of the node data
to the server net file.
d) Transfer the central database for IP networking = Load the server net file to the Feature
server. The customer database is then automatically distributed to the various nodes.
Future administrative node work is then performed by the server.