verity. Fault notification details can be configured to be forwarded to any specific Manager. Trap filters can be con- figured using the Fault Management JMX Agent. The data that are necessary for configuring the trap filters file are exposed through the trap table. 12.10.5 Accessing JMX Agent The JMX Agent is protocol independent. By default, five protocols are supported by the JMX Agent. However, the user can plug in a protocol other than those specified using a protocol adaptor plug-in. The protocols supported at time of writing are SNMP v1/2/3, HTTP/HTML, RMI, CORBA and TL1. The details which can be queried by the FMS are the same in all protocols. The AdventNet Agent Toolkit provides the MIB Browser, the Remote Object Browser and the TL1 Browser. The JMX Agent can be accessed using the MIB Browser for SNMP protocol, Remote Object Browser for RMI, CORBA and HTTP protocols and the TL1 Browser for TL1 protocol. In the case of SNMP, the details which can be queried are exposed as MIBs. The SNMP Manager is the MIB Browser and can query the agent and obtain the result using the specified MIB. Thus the JMX Agent can be accessed using the SNMP v1/2/3 protocols. "Java edition" licences are sometimes sold separately by OSS vendors for add- itional revenue. In the case of AdventNet, the Agent Toolkit Java Edition makes the SNMP Agent able to access the JMX Agent. The JMX Agent can be accessed using SNMP v3 protocol by specifying the user name, password and context name in the Manager. By default, authentication for the JMX Agent is given for three users. 12.11 Using Fault Management Functionality Network events, alarm and alert grouping aspects of day-to-day fault management activities will be described in detail. 12.11.1 Network Events Network events (or just "events") represent specific changes in status of network devices. Network events can also convey general information or the current status of the devices in a network. An operator can learn the history of a device by browsing the Event Viewer in the Client. OSS 