Receiving alarms from TX based tasks: txalarm

Use txalarm under Natural Access to display and optionally log alarm messages generated by NaturalAccess Signaling Software tasks running on all TX boards. txalarm supports Hot Swap.

If you want to bypass the Natural Access environment, use the txalarm_ utility to display and optionally log alarm messages.

Procedure

Run txalarm according to the following syntax:

txalarm [-f filename]

where filename specifies the file to which alarms are copied.

Description

The following example is a sample txalarm message:

<01/07/2004 16:17:04> mtp  1  18180 MTP3 Link 1 Down

All TX-based tasks that need to log their board load activity or send asynchronous change-in-status indications pass messages to the txalarm channel. Alarms are broken into two major divisions:

All alarm numbers are defined in the include file “txlog.h”.

The following table describes all TXBASE alarms as well as alarms that are issued by the common core libraries in use by the Natural Access Signaling tasks. For a description of other alarms that may be issued by the given higher layer task, refer to the specific NaturalAccess Signaling Layer’s manual.

Number

Name

Severity

Message

296

OS
NO
REARIO

Info

CPCI Rear IO board not present

304

OS
SYSMON
FANSTOP

Critical

CPU Fan has stopped!

Board Temp dC [dF]. CPU Temp dC [dF]

Note: TX 4000 Series alarms do not include temperatures.

305

OS
SYSMON
FANSTART

Critical

CPU Fan has Re-Started.

Board Temp dC [dF]. CPU Temp dC [dF]

Note: TX 4000 Series alarms do not include temperatures.

306

OS
SYSMON
TEMP

Info
Critical

On Board Temp <tempName>: dC [dF].

CPU Temp dC [dF]. Fan State:<fanState>

tempName: Normal, Warm, High, Very High or Critical

fanState: Running, Stopped, Restarted

Note: TX 4000 Series alarms do not CPU or Fan information.

307

OS SYSMON
DISABLE

Critical

Disabling <resource>

resource: Ethernets, TDMs, 8260, etc. (board type-specific)

Final Text: Board will be Disabled if temp continues to rise

320

OS
CLK
ROLE

Info

CT Bus Clock Role: Slaved to CT Bus Clocks

CT Bus Clock Role: Secondary CT Bus Master

CT Bus Clock Role: Primary CT Bus Master

320

OS
CLK
ROLE

Error

CT Bus Clock Role: Invalid Fallback Clock Config

321

OS
CLK
FAILURE

Warning

Primary Clock Failure, fallback to Secondary clock source

Secondary Clock Failure, fallback to Secondary CT Clock

Secondary Clock Failure, fallback to Secondary CT Clock Ref

Clock Fallback, unknown State, fallback to internal OSC

Invalid Configuration, fallback to Internal OSC

Secondary CT Bus Clock Failure, fallback to Internal OSC

Clock Fallback Timer, Unexpected State, stopping timer

Clock Fallback, unknown State, Event=CT_CLOCK_RECOVER

Primary Clock Failure, Mastering secondary clock

Secondary Clock Failure, fallback to internal OSC

Clock Fallback, unknown State, fallback to internal OSC

Primary Clock Failure, fallback to secondary clock

321

OS
CLK
FAILURE

Error

Error in Clock Fallback

322

OS
CLK
RECOVERED

Info

Primary Clock Recovery, Returning to Primary clock source

Secondary CT Clock Recovery, return to secondary CT clock

Primary Clock Master SEM, Unknown Event

Secondary Clock Master SEM, Unknown Event

Secondary Clock Recovery, return to secondary clock

Clock Slave SEM, Unexpected Event

336

OS
DHCP
ERR

Error

DHCP [<iface>]: TIMEOUT while trying to …

DHCP [<iface>]: Invalid DHCP OFFER received (..)

338

OS
DHCP
ACQ

Info

DHCP [<iface>]: Acquired IP Address <address>

352

OS
LICENSE
HSL

Error

Cannot create port <portNum>: board not licensed for High Speed Links

16384

SS7
INIT

Error

<message indicating specific initialization step that failed>

Example:

Cannot run task ..: board not licensed for full stack operation

 

Note: Each time a TX board initializes all active protocol layers will perform license verification.  

16385

SS7
SERROR

Error

<SS7 higher-layer error message>

16386

SS7
SLOGERROR

Error

<SS7 higher-layer error message>

16387

SS7
SPRINT

Error

<SS7 higher-layer log (print) message>

Example: Invalid TDM port number (17) configured

Note: An alarm with a similar description to this example is issued any time a link number is configured that is beyond the number of links the given board is licensed for. An error message will also be displayed by the MTP3CFG utility whenever this alarm is generated: Specified link exceeds maximum.

16388

SS7

INTERNAL

Error

Internal Error <SS7 higher-layer error description>

16389

SS7
HOST

Error

hbus_notif:<error description>

Note: hbus errors indicate problems communication with host-based application(s).

16390

SS7
MBOX

Error

mbox_notif: <error description>

Note: mbox errors indicate problems using mailbox messaging to communicate with other board-based tasks.

16391

SS7
IBC

Error

ibc_notif: <error description>

Note: ibc errors indicate problems with Inter-Board Communication (redundant mate communication)

16640

MTP1
IFACE

Error

<errors reported from MTP level-1 driver>

Example: SS7 level-1 driver [MCC <mccNum>] Global Reset

19200

SIGTRAN
INTERNAL

Error

<SIGTRAN-related internal error message>

Example: UNKNOWN packet type received

19201

SIGTRAN
IFACE

Warning
Error

<virtual socket interface communication error message>

Example: vsockif_notif error: [CHECKSUM] receive error


The following example shows a sample txalarm message from the mtp task that is executing on TX board number 1:

<07/20/20049 16:17:04> mtp  1  18180 MTP3 Link 1 Up