EasyManua.ls Logo

Ericsson EFN324 - Remote Management for Stand-alone Nodes

Ericsson EFN324
176 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Glossary
The ‘configuration’ resource contains the names and statuses of configuration
data sets. Status indicates which set is the latest restored and which is
appointed permanent.
10.3 Remote Management for Stand-alone Nodes
The EFN324 is intended mainly for remote management using either ssh,
telnet or SNMP.
10.3.1 Management VLAN
In order to distinguish between End-user and management traffic, the remote
management of the EFN324 is done through a dedicated management VLAN.
10.3.2 Management Access List
EFN324 allows the operator to specify which IP hosts are allowed to run
Telnet, SSH sessions, or to communicate through SNMP.
10.3.3 IP Addresses for an EFN324 Node
Management of the EFN324 is normally carried out remotely from operation
and maintenance sites located elsewhere. Communication is done through the
IP network. Therefore, the EFN324 must function as an IP host.
An IP host must be configured with adequate address information in order for
the IP based functions in the node to work properly. The IP address, net mask
and IP default gateway must be allocated and set.
Address information is stored in the ‘cpu’ resource.
10.3.4 SNMP
The snmp object contains information related to SNMP. Write, read and trap
‘communities’ may be defined. Communities are a simple access control
mechanism offered by SNMP.
Up to three trap receivers can be defined.