in the PersistenceTrapMIB. For example, if maxRows is set to 10, then only the last 10 notifications will be stored in the database. 12.10.4.1.2 Forwarding Notifications Notifications are sent to the Managers which have registered with the JMX Agent. Details of the Managers able to receive the notifications are specified in the Forwarding table. These details are the same for the SNMPvl/v2c, but there is a considerable difference from the details that must be provided for the SNMPv3. In particular, SNMPv3 requires that security-related details of the recipient Managers be provided also. It is possible to suspend notifications to some Managers temporarily. A Manager can be permanently unregistered by deleting the row corresponding to that Manager in the Forwarding table. 12.10.4.2 System Group The system group is concerned with providing the Manager with details about the system. Such details include basic information required by the NMS to manage the 49 Variable binding simply refers to the values of the variables. 12 Fault Management EMS. Details such as version, host name, start time, up-time and ports available are exposed as scalar values by this group. Some values in the system group are exposed as tables, namely the TrapPort and the scheduler tables. 12.10.4.2.1 Log Configuration The JMX Agent provides a feature for configuring the log files. This module provides for setTable values. The data exposed by this module are: name of the log files directory name of the log files number of files of the type number of lines in the files whether logging must be done or not whether time-stamping must be done or not the level at which logging must be done. The configuration of Log Files is also carried out through some values which are exposed as table attributes. The tables involved are the Log and the Log User tables. 12.10.4.2.2 Proxy Service The JMX Agent can act as a proxy for any other agent. Unlike dynamic registration, the proxy service does not register the target device's agent as a sub-agent. The value of o