Cisco Systems 78-16845-01 Wheelchair User Manual


  Open as PDF
of 68
 
3-67
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Chapter 3 Building the Network
3.12.1 Pinging an NE
3.12.1 Pinging an NE
Step 1 In the Domain Explorer tree, select the NE to ping.
Step 2 Choose Fault > Ping NE. The ping results include round-trip time and packet loss statistics.
Step 3 Click OK in the dialog box.
Note This function is enabled if the operational state of the NE is In Service or Under Maintenance. It is
disabled if the operational state of the NE is Out of Service or Preprovisioned.
Note A link to the ping utility must be present in your PATH variable on the CTM server. The default location
is /usr/sbin/ping. If a link to the ping utility is not present in your PATH variable, configure your PATH
settings to include it.
3.12.2 Testing NE Connectivity
Step 1 In the Domain Explorer tree, select an NE.
Step 2 Choose Fault > Test NE Connectivity. The Test NE Connectivity operation runs the ping command to
check the NE communication state. The results show whether the NE is available or unavailable:
• Available—If the CTM client can reach the NE through the ping command, the communication state
of the NE in the database is checked. If the NE communication state is Unavailable, it is changed to
Available and an event is sent to the CTM client, stating that the communication state was changed.
If the NE communication state is Available, there are no changes.
• Unavailable—If the CTM client cannot reach the NE through the ping command, the
communication state of the NE in the database is checked. If the NE communication state is
Available, it is changed to Unavailable and an event is sent to the CTM client, stating that the
communication state was changed. If the NE communication state is Unavailable, there are no
changes.
Step 3 Click OK in the dialog box.
3.13 How Do I Test Connectivity for MGX Voice Gateway
Devices?
Note You can run a diagnostic check at the node level to verify that CTM is correctly managing the selected
nodes. See 4.6.11.2 Running a Diagnostic Check at the Node Level, page 4-92.
 previous