Troubleshooting the Service

Test Commands

In the event that an issue was discovered with an installed application or line card, depending on the severity, it may be necessary to take corrective action.

The system provides several redundancy and fail-over mechanisms to address issues with application and line cards in order to minimize system downtime and data loss. These mechanisms are described in the sections that follow.

Using the Test IPCF Command

This command tests the status of IPCF BindMux Manager instance and also provides ability to start or stop the BindMux Manager instance on the chassis.

IMPORTANT:

This command must be executed from within the context in which at least one PCC service is configured.

The command has the following syntax:

test ipcf bindmux [start | stop]]

Keyword/Variable	Description
start	Starts the IPCF BindMux Manager instance running on the chassis.
stop	Stops the IPCF BindMux Manager instance running on the chassis.

Keyword/Variable

Description

start

Starts the IPCF BindMux Manager instance running on the chassis.

stop

Stops the IPCF BindMux Manager instance running on the chassis.

Checking Reachability of Node Using Ping

This command tests the reachability of network nodes from a chassis.

The command has the following syntax:

ping host_ip_address [broadcast] [count num_packets ] [pattern packet_pattern] [size octet_count ] [src {src_host_name | src_host_ip_address} ] ]

Keyword/Variable	Description
`host_ip_address`	Identifies the remote node to which the ability to communicate with is to be verified. `host_ip_address`: specifies the remote node using the node’s assigned IP address specified using the standard IPv4 dotted decimal notation.
broadcast	Sends ping packets to broadcast addresses.
count `num_packets`	Specifies the number of packets to send to the remote host for verification. `num_packets` must be within the range 1 through 10000.
pattern `packet_pattern`	Specifies a pattern to use to fill the internet control message protocol packets with. `packet_pattern` must be specified in hexadecimal format with a value in the range hexadecimal 0x0000 through 0xFFFF. `packet_pattern` must begin with a ‘0x’ followed by up to 4 hexadecimal digits.
size `octet_count`	Specifies the number of bytes each IP datagram. `octet_count` must be a value in the range 40 through 18432.
src {`src_host_name` \| `src_host_ip_address`}	Specifies an IP address to use in the packets as the source node. `src_host_name`: specifies the source node using the node’s logical host name which must be resolved via DNS lookup. `src_host_ip_address`: specifies the source node using the node’s assigned IP address specified using the standard IPv4 dotted decimal notation.

Using the Diameter Test Command

This command disables a Diameter endpoint without removing the peer’s configuration.

Use this command to perform a troubleshooting by resetting the Diameter endpoint.

IMPORTANT:

This command must be executed from within the context in which at least one Diameter node is configured.

The command has the following syntax:

diameter {disable | enable | reset connection} endpoint endpoint_name peer peer_id

Keyword/Variable	Description
disable	Disables a Diameter endpoint and peer host configured in it before starting troubleshooting.
enable	Enables a Diameter endpoint and peer host configured in it after troubleshooting.
reset connection	Resets the connection between Diameter endpoint and peer host configured in it as a first attempt to resolve the issue before disabling it for troubleshooting.
endpoint `endpoint_name`	Specifies the endpoint in which the peer is configured. `endpoint_name` must be the name of the endpoint, and must be an alpha and/or numeric string of 1 through 63 characters in length.
peer `peer_id`	Specifies the peer id which is to be reset. `peer_id` must be the Diameter peer host name, and must be a string of 1 through 63 characters in length.