ly dumped into files on the network element. These performance records are collected from the network element at regular intervals by the NMS, the data is then parsed and formatted for final display or processing input for other modules. Authentication of user: The user of the NMS needs to be authenticated to prevent unauthorized use of the network management application. Maintenance commands that can bring down key elements in the network can be performed from the NMS, which leads to high levels of security implemented at the NMS. There are a set of user groups and each user is assigned to the user group. Each group or user has a set of privileges with regard to functionalities in the application. For example, with fault func- tionality, some users can only view the logs, others can view and edit the logs, yet another group or user in a group can even delete logs. With single- sign-on (SSO) functionality implemented at NMS, a single authentication should permit the user working on NMS to jump to the console of any net- work element that is managed or any element management application that is associated with the NMS. Download additional records and configuration data: Any other record in the element that is required by some functionality at NMS is also down- loaded from the network element. Predefined configuration data, like cor- relation between performance registers or rules for event handling are also downloaded. Once the resources are discovered and the historical data downloaded, then the NMS application is ready for performing any maintenance level activities. The maintenance activities or network functions are performed with the down- loaded data. These functions will include network provisioning, troubleshooting of network issues, maintenance of configured network elements, tracing the flow of data across multiple network elements, programming the network for optimal utilization of elements, and SO on. During a connection loss between the NMS and an already managed element, the NMS will try for a connec