Re-synchronizing data between network elements and network management system using partial node discovery

1. A method for network recovery, comprising:

verifying completion of full node discovery;

detecting recovery activities of a network management system (“NMS”);

issuing a re-synchronizing signal indicating a partial node discovery;

retrieving a saved last sequence number associated with a first network element (“NE”) from a database in the NMS;

obtaining a current last sequence number associated with the first NE from the first NE;

identifying missing sequence numbers associated with the first NE in response to the saved last sequence number and the current last sequence number; and

synchronizing event status associated with the first NE in accordance with the missing sequence numbers.

2. The method of claim 1 , wherein retrieving a saved last sequence number associated with a first NE from a database in an NMS includes fetching the saved last sequence number from a local database in the NMS.

3. The method of claim 1 , wherein obtaining a current last sequence number associated with the first NE from the first NE includes issuing a network command indicating to get a last sequence number associated with the first NE from the first NE at present time.

4. The method of claim 3 , wherein issuing a network command indicating to get a last sequence number associated with the first NE from the first NE further includes,

reading a last-send event sequence number from an entry of event history table at the first NE; and

forwarding the last-send event sequence number from the first NE to the NMS.

5. The method of claim 1 , wherein identifying missing sequence numbers associated with the first NE includes:

comparing the saved last sequence number with the current last sequence number; and

determining a difference between the saved last sequence number and the current last sequence number.

6. The method of claim 1 , wherein synchronizing event status associated with the first NE in accordance with the missing sequence numbers includes:

obtaining the missing sequence numbers from the first NE to the NMS one at a time and;

processing each event in accordance with each of the missing sequence numbers.

7. The method of claim 1 , wherein synchronizing event status associated with the first NE in accordance with the missing sequence numbers includes obtaining the missing sequence numbers from the first NE to the NMS in bulk at a time.

8. The method of claim 1 , further comprising:

retrieving a saved last sequence number associated with a second NE from the database in a NMS;

obtaining a current last sequence number associated with the second NE from the second NE;

identifying missing sequence numbers associated with the second NE in response to the saved last sequence number and the current last sequence number; and

synchronizing sequence numbers associated with the second NE in the database in accordance with the missing sequence numbers.

9. A network system, comprising:

a first network element (“NE”) capable of storing each sequence number indicating network activities in a first event history table;

a NMS coupled to the first NE via a connection and capable of verifying completion of full node discovery and detecting a recovery activity, wherein the NMV able to issue a re-synchronizing signal for performing a partial node discovery includes,

a comparator module configured to compare a saved last sequence number associated with the first NE and a current last sequence number from the first NE; and

a synchronizing module coupled to comparator module and configured to synchronize sequence numbers associated with the first NE in a database in the NMS in response to a result of comparison from the comparator module.

10. The system of claim 9 , further comprising a second NE coupled to the NMS and capable of storing each sequence number indicating network activities in a second event history table, wherein,

the comparator module configured to compare a saved last sequence number associated with the second NE and a current last sequence number from the second NE; and

the synchronizing module coupled to comparator module and configured to synchronize sequence numbers associated with the second NE in a database in the NMS in response to a result of comparison from the comparator module.

11. The system of claim 10 , wherein the NMS is capable of initiating partial node discoveries for the first NE and the second NE at substantially same time.

12. The system of claim 9 , wherein the NMS further includes a loading module capable of retrieving the saved last sequence number associated with the first NE from the database in the NMS.

13. The system of claim 12 , wherein the NMS further includes a fetch module capable of obtaining the current last sequence number associated with the first NE from the first NE via the connection.

14. The system of claim 13 , wherein the NMS further includes a calculator module capable of identifying missing sequence numbers associated with the first NE in response to comparison between the saved last sequence number and the current last sequence number.

15. A method for obtaining network information, comprising:

verifying completion of full node discovery;

detecting recovery activities of a network management system (“NMS”);

issuing a re-synchronizing signal indicating a partial node discovery;

retrieving a saved last sequence number of a first network element (“NE”) from a database in the NMS;

obtaining a last-send event sequence number from an event history table in the first NE via a first connection; and

loading sequence events between the saved last sequence number and the last-send event sequence number from the event history table to the database.

16. The method of claim 15 , further comprising:

synchronizing event status associated with the first NE in accordance with missing sequence numbers.

17. The method of claim 16 , further comprising:

retrieving a saved last sequence number of a second NE from a database in the NMS;

obtaining a last-send event sequence number from an event history table in the second NE via a first connection; and

loading sequence events between the saved last sequence number and the last-send event sequence number from the event history table for processing event and synchronizing the database.

18. The method of claim 15 , further comprising performing a process of a full node discovery when the saved last sequence number of the first NE is equal to zero.

19. The method of claim 18 , wherein loading sequence events between the saved last sequence number and the last-send event sequence number from the event history table to the NMS further includes reading a plurality of entries from the event history table in accordance with the saved last sequence number and the last-send event sequence number.