1. EAGLE SIGTRAN User's Guide
  2. Troubleshooting

7 Troubleshooting

This chapter offers troubleshooting procedures based on symptoms occurring in the network.

7.1 General troubleshooting

  1. Work from the bottom of the protocol stack up: first, IP Network; then the SS7 link or connection; then traffic routing.
  2. Review provisioning and verify configuration in this order:
    • Card
    • Signaling (SS7) link
    • Linkset
    • IP link or IP network
    General troubleshooting tools include the following:
    • Ethereal – PC-based network analyzer (sniffer) – www.ethereal.com/www.wireshark.com
    • netstat/sctp pass commands to display TCP/IP or SCTP/IP network statistics
    • ualog/asplog/linkinfo pass command to retrieve logs of events in stack and control messages transmitted or received
    • msucount pass command to display traffic counts of MSUs that have been transmitted, received, rerouted, or discarded, and the discard reason

7.2 Verify UIMs and UAMs

  1. If there are any Unsolicited Information Messages (UIMs) or Unsolicited Alarm Messages (UAMs) occurring related to the SIGTRAN configuration, refer to Unsolicited Alarms and Information Messages Reference.

7.3 Is the card configured correctly?

  1. Card in system?

    rtrv-card

    rept-stat-card

    • IP link configured correctly? (rtrv-ip-lnk; preferred settings are 100/full duplex on card AND switch - no AUTO configure)
    • IP link configured correctly? (rtrv-ip-lnk; preferred settings are 100/full duplex on card AND switch - no AUTO configure)
    • IP host table configured? (rtrv-ip-host; check for local and remote addresses)
    • Signalling links (SLKs) and linksets configured correctly? (rept-stat-slk/rept-stat-ls)
  2. IP link configured correctly?

    rtrv-ip-lnk

    Preferred settings are 100/full duplex on card AND switch - no AUTO configure

  3. IP routing configured?

    rtrv-ip-rte

    rtrv-ip-card

  4. IP host table configured?

    rtrv-ip-host

    Check for local and remote addresses.

  5. Signalling links (SLKs) and linksets configured correctly?

    rept-stat-slk

    rept-stat-ls

7.4 Connection does not become established

  1. Card up and stable?

    rept-stat-card

  2. Association status?

    rept-stat-assoc

  3. Network connectivity?

    netstat -I

    rept-stat-card:mode=full

  4. Errors (collisions, etc.) on the network interface?

    netstat -d 0/1t

  5. Far end reachable?

    ping

    traceroute

  6. Near end and far end use same SCTP CRC?

    netstat –p

    sctp/rtrv-sg-opts

7.5 Connection bounces and is unstable

  1. Transport stable?

    netstat –i

    netstat –d

  2. RMIN set too low?

    ping

    assocrtt

    rtrv-assoc

    Rule of thumb is above 1.2 * average RTT

7.6 Traffic not arriving at IP destination or traffic is lost

  1. Route to destination’s PC entered and available?

    rept-stat-dstn

  2. Traffic being received/discarded on IP card? There can be numerous discard reasons!

    msucount -l

7.7 Are connection(s) congesting?

  1. Is SCTP buffering set correctly for network RTT?

    rtrv-assoc

    assocrtt,

    sctp

  2. Is an interface set to half-duplex somewhere in the path to the far end, causing excessive retransmissions?

    rtrv-ip-lnk

    sctp

7.8 Traffic not load-balanced properly

  1. Source traffic has uneven SLS distribution?
  2. All cards in linkset or mateset do not host a connection to the IP Application Server(IPSG only)?

    rtrv-assoc

    rtrv-as

  3. IPSG cards in mateset with no established connections have signaling link deactivated to minimize ‘double-hopping’ (IPSG only)?

    rept-stat-card

    msucount -l

7.9 Link Level Events

  1. IPSG pass command

    linkinfo -l

  2. IPSG linkinfo has other interesting options?

    -c

    -m

  3. IPSG pass command

    ualog

    aslog

  4. Both commands have event filtering (link events vs. traffic), so look at options

7.10 Association

  1. IPSG/ pass command

    sctp -a