Configuration Data - Nortel 5100 Release Note

50 Server security, administration, and maintenance software features
•
•
File system structure
The file system structure changes facilitate the deployment of multiple
network instances of the same server and minimize the differences between
Windows, Linux and Solaris operating systems.
Table 7
File system structure comparisons
Operating system
Linux
Solaris
Windows
The Linux /opt/mcp and /var/mcp directories (and their Solaris and Windows
counterparts) are hierarchical and contain specific information.
Table 8
Linux file structure
Path
Subdirectory
/opt/mcp ned
/opt/mcp lib
/opt/mcp java
/var/mcp loads
run
/var/mcp
/var/mcp spool
oss
/var/mcp
License Key handling
Components on an NE register their interest in particular keycodes within
the license key. When the license key is updated, the keycodes are
automatically sent to the components that register against the keycode.
Configuration data
Configuration data is shared to eliminate the duplication of information.
Instead of data being located in multiple locations, the data resides in one
place and all network elements access the data from this location. Sharing
data eliminates data synchronization problems that come with a distributed
data architecture.
Copyright © 2007, Nortel Networks
.
acting as a watchdog for the NE processes
restarting NE processes when they unexpectedly exit
Installed software path
/opt/mcp
/opt/mcp
D:\mcp
Purpose
NE Daemon
shared library files
JRE versions required for any Java Virtual Machine (JVM)
(System Manager only) contains deployable software load
NE Daemon file deployment area. Each NE on the server has a
subdirectory.
unformatted NE fault, performance and accounting data
FPM and AM formatted records
Nortel Multimedia Communication Server 5100
New in this Release
NN42020-404 03.08 Standard
Release 4.0 11 September 2007
Deployed software, logs and OMs path
/var/mcp
/var/mcp
D:\mcp