Management from PEM
42 1553-CNH 160 0787 Uen PA2 2005-09-23
8 Management from PEM
After the initial configuration is completed, the EAN can be managed from
PEM as an EAN, but before any management can be done from PEM, the
EAN must be defined in the PEM database, which is done using the Dis-
cover function in PEM, and before the EAN can be discovered in PEM the
EAN SW and the software for the embedded nodes must be installed on
the Management Server, see the ECN330 Installation Guide or the
ECN320 Installation Guide, PEM Installation Guide for Windows and/or
PEM Installation Guide for Solaris for further information about installation
of node SW.
8.1 Discovering an EAN
8.1.1 Prerequisites
The following must be done before the EAN can be discovered by PEM:
• The initial configuration described in section
7 on page 39 must be
completed. When PEM discovers an EAN, the EAN is automatically
assigned to the Domain Subnet created in the IP Network, which con-
tains the IP address of the EAN. If there are multiple Domain Subnets
in the same IP Network, the EAN would be assigned to the Domain
Subnet that was created first (chronologically). The EAN cannot be
moved to another Domain Subnet.
Note: If there are no IP network in PEM able to contain the IP ad-
dress of the ECN, or if the IP address is already in use by an-
other node known to PEM, the EAN will not be discovered.
• The SW of the EAN and the embedded nodes must be installed in PEM
(the normal installation procedure in PEM, please see PEM Installation
Guide for Windows and/or PEM Installation Guide for Solaris.
New EAN nodes are discovered in PEM through the Network Configuration
Manager (NCM). Please see PEM User Guide for more information about
how to discover a network element.
To Next Page
Loading...
