How long is the log retention time of managed devices on the Nokia NSP system?

NSP-NFMP will not save all logs from the nodes. It processes the SNMP traps from the log-id 98 and reports as alarms in the active alarm window. Again, not all traps convert into alarms. The maximum number of alarms in the active as well as historical alarm windows vary depends on NFM-P release.

Customer:
I want to ask how long is the log retention time of managed devices on the NSP system? I mean default setting log time.

Nokia:
Could you please clarify little more about the requirement here?
Is this a query related to the retention period of EmsServer logs? Or kindly clarify what type of logs are you looking for.
Also please share the NSP version details as well. 

Customer:
Is this a query related to the retention period of EmsServer logs?
I am not sure about this.
Please help me answer the following questions:
1/ Is the log from the device connected to the NSP saved by the NSP?
Example: All types of logs (Log-id 99,100,101…) from 7750 SR devices.
Note that, not the log generated from the NSP.
2/ If saved, how long is the default save time?

Nokia:
Please note that any of the logs from the Network Element (Eg: log Id 98,99,100 etc) will not get saved in NSP. From NSP, you can get only the logs generated by the NSP system. 
To answer the query: Can NSP act like SNMP client to collect snmp logs from every managed nodes? NSP will receive the events only from Log ID 98 of the NEs and not from any other log files. 

Customer:
Can NSP act like SNMP client to collect snmp logs from every managed nodes? So the question wants from you is: what is the maximum number of logs from log-id 98 which NSP can save? Is it limited by time or quantity? In any case, which will be its limitation: 1 month, 2 months, or 500k messages or something like that?

Nokia:
NSP-NFMP will not save all logs from the nodes. It processes the SNMP traps from the log-id 98 and reports as alarms in the active alarm window. Again, not all traps convert into alarms. The maximum number of alarms in the active as well as historical alarm windows vary depends on NFM-P release.
Below is the alarm scalability of NFMP latest release.

NFM-P’s trap processing rate depends on many factors including trap type, NE type, NE configuration, NE and network latency, network reliability as well as the size and speed of the servers hosting the NFM-P application.
Nodes and NFMP communicate over SNMP protocol, and we get the information in NFM-P. The default NFMP logs will write only basic details and if you need more information regarding the nodes/operations on nodes (Eg: back up, resynch, node discovery etc), extra debugging can be enabled from NFMP side, and the detailed information will be written in the NFMP logs.
Coming to the retention period of NFMP logs, the log files will be retained in the system based on the configuration done. The maximum number of archive log files can be configured in the config file. It is not limited by time. It is based on the number which is configured.
Please note that, logs mentioned here are the logs generated by NFMP and which will have the information of the NFMP system as well as the managed NEs.