ZETRON 2000 Series Specifications Page 304

  • Download
  • Add to my manuals
  • Print
  • Page
    / 376
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 303
System Configuration Files
304 025-9035AA
Table 46: Reported TNPP Events
The network.cus file can have more than one ports... report command line, however if the
lines are contradictory, the last command line is always implemented. TNPP events
reporting can be customized by using several network.cus command lines to configure
each port individually.
The following lines are some examples of valid network.cus entries. Several of these lines
could be combined in one network.cus file.
ports 1 report LinkDown ResetIn LinkUp
ports 2 5 7 8 report ResetIn linkup
PORTS 3 report None
Ports 4 report UnknownDst NAKexpired DestDown
Ports ALL report None ; turns off all TNPP reporting
Log Posting
When an event is reported, it gets noted in the current log file. The general form is as
follows:
@ <timestamp> <event-type> <event-message> <actions-to-take>
When a customized message string (“<msg>” field) is specified, it appears in the log file
right after the <event-message> entry.
All events pages are sent at the priority of the subscriber record. They are logged much
like normal pages, except their source field is Event! rather than a trunk, and their
subscriber status field is
evnt pg.
Event Keyword Description of TNPP Event
LinkDown link to other node has gone down
(or) powerup (immediately followed by LinkUp report)
LinkUp link to other node has been established
DestDown destination port is down; usually ReSend tries counted out
NAKexpired transmitted packet got too many NAKs
RSexpired ReSend count expired; usually link is too busy
BadCRC received packet with CRC error; usually link interference
CANreply other node did not like packet; usually unknown destination
node ID
UnknownDst unknown node ID, got packet & could not route it
ZeroInertia got packet to route with inertia = 1
ResetIn other node sent RESET packet
ResetOut RESET packet sent to other node
NONE turn off all events reporting for specified ports
NO turn off all events reporting for specified ports
OFF turn off all events reporting for specified ports
Page view 303
1 2 ... 299 300 301 302 303 304 305 306 307 308 309 ... 375 376

Comments to this Manuals

No comments