| United States-English |
|
|
|
![]() |
HP OpenCall SS7 platform Operations Guide: For Release 3.1 on Linux > Chapter 6 Managing and Monitoring
the PlatformMonitoring the SS7 Network Using the SS7 Monitor |
|
To monitor the SS7 network, use the SS7 Monitor. You can do this in either Operator or Administrator mode. The Monitor Entities and Single Entity Statistics menu items let you monitor and get statistics on the SS7 network and about hardware status. These menus can be accessed in Operator (non-privileged) mode, as well as in Administrator mode. Refer the SS7 Monitor on-line help for details on the information provided. “SS7 Monitor Interface” for information on syntax and navigation. To switch between the available modes, edit the file /etc/opt/OC/management/mgtProcessList.conf to comment out the lines that you do not require:
Using the Operator’s interface, you can monitor the following:
If you choose MTP from the main menu, you can choose to monitor one of the following:
From the Monitor MTP window you can activate, deactivate, and monitor the overall traffic of the MTP layer of the SS7 stack. From the Monitoring Destinations/Routes window you can activate, deactivate, and monitor the status of destinations, or individual routes to one destination. The window shows the states as defined in the ITU-T/ANSI recommendations.
SearchUse the (S)earch function (type S) to find a particular destination point code. TestUse the (T)est function (type T) to test the route in the TTC standard. The local host sends a SRT and expects the return of an SRA. The return notification will display, for example:
or
This testing function is not available for the ITU-T nor ANSI standards. If you try to test these standards, you will see an error message. You cannot access the route while it is being tested. From the Monitoring Links/Linksets window you can activate, deactivate, inhibit, uninhibit and monitor the status of links to adjacent DPCs. You can also monitor overall traffic on the linksets. Abbreviations used in this window are as follows:
Link InhibitThe link inhibit command works for ANSI and ITU-T stacks, but is not in the TTC standard. If you use TTC, you will see an error (ILLEGAL_OA_OPERATION) if you try to inhibit a link. SearchUse the (S)earch function (type S) to find a particular destination point code. When the Stack StartsThe activation behavior of Link/Linkset is automatic if the links have been configured, that is your links become ACTIVE. If a Signaling Unit has a status of ONLINE, the link(s) pass from INACTIVE, to OUT_OF_SERVICE to ACTIVE. If the Signaling Unit has a status other than ONLINE or STANDBY, the Signaling Unit is reloaded until it has an ONLINE or STANDBY state, and then the links will pass through the states as described above. When the Stacks SwitchoverIf the Signaling Unit must pass from STANDBY to ACTIVE in the case of a HP OC SS7 host switchover, the links are not impacted and remain ACTIVE. Starting Up After a Switchover (Active/Standby Mode Only)If a switchover occurs when the MTP is not active, it means that synchronization failed. In this case, stop the synchronization before you re-start. You should: The GDI configuration screen allows you to configure the remote hosts which are authorized to connect to a particular HP OpenCall SS7 stack using GDI. Connection attempts from a non-authorized hosts are refused. A GDI remote host is identified by its DGPC (Distant GDI Point Code) and by one or two IP addresses. The DGPC is a logical local identifier. The remote IP address and the corresponding LAN must be configured on the remote client.
The following options are available:
The statistical data for the selected entity is updated every few seconds. From this window you can see the MTP statistics for the local point code. Enter S, then enter the entity (select from 1 to 5) and parameters that you want to monitor: Example: (2) Local User [ 2 <ssn> ]: in this case, enter 2 then the ssn. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||