You may encounter a situation where you have a multi-MGR configuration and both MGRs are stuck in the slave configuration, possibly after a failed failover and failback. You may notice output like thi...
Overview After upgrading a node in a NewNet environment, certain components such as the PBC or the AMS may fail to start. This can be caused by a kernel memory lockdown during an unclean restart, whic...
Introduction In some cases, a node may appear reachable (successful ping) but still fail to establish TCP connections on required service ports such as 2775 (SMPP) or 1035 (UCP). Typical symptoms incl...
NewNet Lithium makes use of SNMP for configuration, monitoring, and sending event notifications (traps). Because of this reliance on SNMP, a problem can develop if the system is left running for long...
Occasionally, to troubleshoot some performance or network related issues it may be necessary to collect a wide range of logs with information about system and network performance. These are not NewNe...
If you encounter an error like this: Jul 27 12:43:21 RTR01 textpass: Application MyApp1 of ID 34 sent unexpected data - see 'RTR Operator Manual' [3 times]Jul 27 12:43:21 RTR01 tp_hub: App: 'MyApp1' -...
You may want to setup a permission scheme for users in NewNet such that certain users only have access to certain lists. This is not possible in NewNet. The finest level of granularity for user permi...
You may wonder what will happen if there are multiple routing rules with the same priority. In this case, there is no specified determination of what will occur. Please find the following excerpt fro...
Overview A sudden and sustained increase in CPU utilization was observed on two SMSC RTR nodes. This increase was identified via internal monitoring tools and confirmed by performance logs and system ...
Overview High CPU utilization may unexpectedly affect one or more servers or network elements, potentially degrading performance or causing resource contention. This issue can arise even without any c...