3-201
Cisco Signaling Gateway Manager User Guide
78-15589-01
Chapter3 Managing ITP Networks Using SGM
Working with Links
cleans them up and sends a “PEER NOT READY” to the MTP3. A
subsequent request to start the link from the MTP3 will then cause the
link to come up.
–
Communication lost—M2PA/SCTP has determined that the remote end
signaling point is no longer reachable. Possible reasons include:
– The maximum number of consecutive retries of a packet has been
reached.
– In the absence of data, SGM failed to receive heartbeat ACKs in
response to heartbeats, for the maximum number of retries.
–
No Listen posted—An MTP3 tried to start a link, but the local-peer port
associated with the link is not available, probably because of a bad
configuration.
–
Unable to allocate buffer—M2PA/SCTP cannot get buffers for sending
or receiving packets. Buffer problems can be temporary or permanent.
Temporary buffer problems will generally clear with little side effects.
Permanent buffer problems can lead to failed linksets or links.
–
Link card removed—A link card has been removed.
–
Link card inserted—A link card has been inserted.
–
False link congestion—A false link congestion indication has been
received.
–
Configuration downloading—The configuration is downloading.
Statistics Tab: Packet Information
To view packet information for the selected link, select the Statistics tab.
The Packet Information sub-section displays the following information for the
selected link:
•Sent Per Sec—Number of packets sent by the link per second. This field
initially displays the phrase Waiting for second poll. After two polling
cycles, SGM populates this field with actual calculated rates.
•Received Per Sec—Number of packets received by the link per second. This
field initially displays the phrase Waiting for second poll. After two polling
cycles, SGM populates this field with actual calculated rates.
•Drops—Total number of packets that have been dropped by the link.