Not Able To Fetch Comp-link Report For STP

Asset ID:	1-72-2128083.1
Update Date:	2017-02-23
Keywords:

Solution Type Problem Resolution Sure

Solution 2128083.1 : Not Able To Fetch Comp-link Report For STP

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 3x.x and later
Tekelec

Symptoms

Not able to fetch comp-link report for one of our STPs.

Cause

IP link between Eagle active E5MASP and the far end is not up.
Ping to FTP server IP and trace route are successful from 1113, but not successful from 1115.

Currently; 1115 is primary card. Hence no measurement reports are passing.

> pass:loc=1115:cmd="ping FTP IP"

stpclli 16-04-15 07:25:25 IST EAGLE5 44.0.5-64.34.26
PING xxx.xx.x.xxx: 56 data bytes

PING: no answer from xxx.xx.x.xxx <---------------------

PING command complete

lets try by making a trace route, please provide the next commands:

PASS:LOC=1113:CMD="TRACEROUTE xxx.xx.x.xxx"
PASS:LOC=1115:CMD="TRACEROUTE xxx.xx.x.xxx"

> pass:loc=1113:cmd="traceroute xxx.xx.x.xxx"

  stpclli 16-04-15 14:12:23 IST EAGLE5 44.0.5-64.34.26
  pass:loc=1113:cmd="traceroute xxx.xx.x.xxx"
  Command entered at terminal #18.
;

  stpclli 16-04-15 14:12:23 IST EAGLE5 44.0.5-64.34.26
  PASS: Command sent to card
;
Command Accepted - Processing
  stpclli 16-04-15 14:12:25 IST EAGLE5 44.0.5-64.34.26

;
Command Executed
  stpclli 16-04-15 14:12:23 IST EAGLE5 44.0.5-64.34.26

  TRACEROUTE command in progress

;
  stpclli 16-04-15 14:12:25 IST EAGLE5 44.0.5-64.34.26
  Traceroute to xxx.xx.x.xxx (xxx.xx.x.xxx),
  10 hops max, 100 byte packets
  1 2ms 1ms 0ms (172.30.5.1)
  2 23ms 22ms 22ms (172.30.91.8)
  3
  TRACEROUTE command complete

;
> pass:loc=1115:cmd="traceroute xxx.xx.x.xxx"

  stpclli 16-04-15 14:13:11 IST EAGLE5 44.0.5-64.34.26
  pass:loc=1115:cmd="traceroute xxx.xx.x.xxx"
  Command entered at terminal #18.
;

  stpclli 16-04-15 14:13:11 IST EAGLE5 44.0.5-64.34.26
  PASS: Command sent to card
;
Command Accepted - Processing
  stpclli 16-04-15 14:13:13 IST EAGLE5 44.0.5-64.34.26

;
Command Executed
  stpclli 16-04-15 14:13:11 IST EAGLE5 44.0.5-64.34.26
  Traceroute to xxx.xx.x.xxx (xxx.xx.x.xxx),
  10 hops max, 100 byte packets
  1
  TRACEROUTE ERROR: sendto
  TRACEROUTE: wrote xxx.xx.x.xxx 100 chars, ret=65

  TRACEROUTE command failed: Traceroute Error Code = 2

;
  stpclli 16-04-15 14:13:11 IST EAGLE5 44.0.5-64.34.26

  TRACEROUTE command in progress

Solution

1. Switch MASP activity so that 1113 becomes Active: init-card:loc=location of Active MASP (1113 or 1115)
2. Wait for next Polling period and check if the measurement reports are reaching far end.
3. If measurement reports are reaching far end; then check from your IT team or far end why ping from 1115 to far end is not successful.

Attachments

This solution has no attachment