Nokia NCM_20002021610 Dumps

Based on both the available free memory and the reclaimable memory

Based on the available free memory

Based on the reclaimable memory

Based on both the available free memory and swap memory

All the ADM are active in a network.

By running the command /opt/dbm/jboss/bin/is_active.sh as dbmrun user on any ADM.

By running the command “/etc/init.d/jboss active”.

There is no way to identify it from the system. The customer has to know based on history of events done in his network.

By looking at notifs.log.

By checking soap logs at BDS and comparing with Application FE.

By checking failed attempt delivery logs.

By checking dead letter logs.

LDAP clients list is a while list of all the clients that can have an LDAP connection to the OneNDS. It is administered via ADM GUI.

There are two separate lists: white list and black list of LDAP clients. Both these lists can be administered via ADM GUI.

There is no concept of white/black list LDAP clients in OneNDS, anyone can connect and retrieve the data stored.

LDAP clients are white list and are added at the installation time via TPO.

DSA Selection Mode (start reset with data search in directory)

Number Selection Mode (start immediate reset with manually provided VLR/SGSN/MME data)

Profile Management (start or schedule reset based on existing reset profile, created earlier at some stage)

Subscriber selection mode (start reset to a set of subscribers via a text file)

Not possible via ADM GUI. Logs of each node have to be collected separately by logging into that node.

Using ‘Log management – Log File Overview’ section of ADM GUI.

Using collect_symptoms

Using collect_logs.sh script.

/opt/provgw/tomcat/logs/instanceX

/srv/sftp/smc-sftp-DEFAULT/outbox/, where “DEFAULT” is the tenant name

/srv/sftp/smc-sftp/outbox

Only available in the provisioning client result file.

Bulk request can be executed on any of the PGW.

Bulk request can only be executed on 1 PWG identified as master PGW & the master PGW is selected via TPD during installation.

Bulk request can only be executed on 1 PGW identified as master PGW & the master PGW can be switched to any of 5 PGW via a configuration change.

The request can be submitted to any of the PGW and it internally forwards to the Master PGW.

Obfuscation of encryption key in PWG logs.

Double encryption of AUC key.

Avoid duplication of AUC key during SIM creation.

Encrypting the KI with storage key.