Académique Documents
Professionnel Documents
Culture Documents
SNMP, System Log (SYSLOG). Terminal Access Controller Access Control System
(TACACS) and Lightweight Directory Access Protocol (LDAP)
Overview
JMX Specifications
Overview
For any proper management structure, a defined communication channel is required between the High
Level and Low Level Managers. Here, the NMS acts as the Higher Level Manager and the EMS acts as
the Lower Level Manager.
Note: The communication between the NMS and the EMS is called Northbound Communication. Like any
other communication between devices, this communication is also effected by protocols like SNMP,
HTTP/HTML, RMI, CORBA, TL1, etc,.
The communication between the NMS and the EMS is brought into reality through an Interface called
the NMS JMX Agent. It is so named, as it is developed based on JMX Specifications, where JMX stands
for Java Management Extensions. The main function of NMS JMX Agent, is to facilitate the easy transfer
of information pertaining to the NEs managed by a specific EMS to its corresponding High Level
Manager.
SNMP
CORBA
RMI
HTTP/HTML
TL1
Provides details like EMS Host name, Total Memory, Free Memory etc,. These details are got by
the NMS by querying the EMS through the NMS JMX Agent
Enables NMS runtime configurations, for e.g., registering as a sub agent, registering for proxy
service etc.,
The EMS responds to the queries of the NMS through the NMS JMX Agent. It should be remembered
that the NMS JMX Agent can either perform the query on the NE and get the details or check the
database of the particular NE and provide responses. The protocol involved sending a response to the
NMS, through the NMS JMX Agent is in par with the protocol of the query received.
JMX Specifications
The Java Management Extensions (JMX) Specifications define the architecture, design patterns, APIs
and services for application and network management in Java programming language. The major benefit
of this specification is that it provides a way to use common instrumentation on the agent and support
multiple protocols for management. Since JMX instrumentation is independent of the management
infrastructure, the agent developer is freed from the details of each management protocol.
The major advantages in using the JMX Specifications to develop the JMX Agent are listed below:
Instrumentation level
Agent level
The instrumentation level of the JMX specification defines how to instrument resources in the Java
programming language so that they can be managed. These resources developed are called Java
Manageable Resources.
The Java objects which implement the resources and their instrumentation are called Managed Beans, or
MBeans in short. MBeans must follow the design patterns and interfaces defined in this part of the
specification. This ensures that all MBeans provide the instrumentation of managed resources in a
standardized way.
The NMS JMX Agent uses Model MBeans. The Model MBeans are dynamic MBeans that are fully
configurable and self described at run-time; they provide a generic MBean class with default behavior for
dynamic instrumentation of resources.
As of now the NMS JMX Agent has achieved the support of five main protocols. They are SNMP,
CORBA, RMI, HTTP/HTML and TL1.
For more information on the JMX specification, please
visit http://java.sun.com/products/JavaManagement/wp.