Nortel Observe User Manual page 118

If the packets are arriving properly, the TS should be equal to the current time.
If all the values here are 0, then no packets are arriving. Check that the
difference in timestamps between successive packets is not greater than one
second. If so, re-examine the RSM refresh rate setting at the SCCS server (see
page 37)
6. Check that the packets have been arriving consistently.
->displayRsmParseStatistics
Statistics since card was rebooted
***********************************************
Number of packets at socket:
Bad release:
BadNumRecords:
BadRecordSize:
BadType:
InvalidTimePackets:
Valid Packets Received:
Latest Parsed Timestamp:
NoAgents in Current RSM stream:
Sets of timestamp data parsed:
***********************************************
The "Valid Packets Received" should equal the "Number of Packets at socket"
field, and the error count fields should all read zero. The InvalidTimePackets
may sometimes read a small value, in the aftermath of events like network
congestion, resulting in re-sends of data.
->displayMonitorStatistics
Statistics since card was rebooted with function called every
15 secs
***********************************************
Monitor rsm data called:
Curr ticks is:
LatestParsedTimestamp:
12:40:06
No.times no data arrived:
No.times Timestamp reset:
DataArrivingSucessfully:
If the "No.times no data arrived" field is non-zero this indicates that the RSM
data has not been arriving consistently, since the card was rebooted. This may
indicate an intermittent network problem.
Planning, Installation and Administration Guide
24022
0
0
0
0
0
24022
3f3f7799 -->17/08/03 12:39:53
1507
7996
279
67801
3f3f77a6 --> 17/08/03
0
0
279
Nortel Proprietary
118