Logging Commands

IPriori's logging system records, collects, filters, and displays logging messages generated from Avici router subsystems and provides efficient system monitoring. Efficient logging systems give troubleshooters the necessary information to correct system errors when they occur. For example, subsystem logging messages provide:

• Reports to system administration of unexpected events for analysis.
  
  
• Program tracing and debugging aids in order to search and resolve problems.
  
  
• Appropriate indications to operations network management centers when critical errors generate.
  
  

For specific information regarding subsystem logging messages, refer to "IPriori Messages and Glossary" manual.

Logging Subsystems

All logging messages originate on subsystems and each subsystem operates on a specific platform: server, module, or bay controller. When configuring standard logging files, users must be in correct configuration mode (server, module, or bay controller) for the subsystems being monitored. Subsystems may be hardware or software related. Table 14-1 displays the platforms where subsystem messages originate.

Table 14-1. Logging Subsystems Supported - listed by Platform

Subsystem	Server	Module	Bay Controller	Description
aaa	X			AAA error messages
arp-cache-mgr	X			ARP Cache Manager messages
atm	X	X		ATM error messages
arp-cache-mgr	X			ARP Cache Manager messages
arp-tbl-mgr	X			ARP Table Manager messages
bay_common			X	Bay controller general logging messages
bay-controller			X	Bay controller communications/hardware messages
bgp-events	X			BGP events information
bgp-updates	X			BGP updates information
cli	X			CLI messages
co-alarm	X			Central office alarm messages
data link				Data link layer messages
debug	X			system debug messages
environment	X		X	Environmental-based messages Includes temperature and fans
failure-protection- handler		X		Interface or module failure messages
frl	X	X		Frame Relay messages
gated-ldp	X			Gated support for LDP
gated-ldp	X			Gated support for LDP
gated-te	X			Gated Extensions for Traffic Engineering
hello-proc	X			Hello Processore hellopm/hellops messages
high-availability	X			High Availability logging messages
hii		X		Hardware independent interface error messages
isis	X			IS-IS routing protocol messages
isis-adjacency				ISIS adjacency changes
isis-te	X			ISIS Extensions for Traffic Engineering
ldp	X			MPLS Label Distribution Protocol (LDP) messages
lnkdb		X		Link database error messages
management	X	X	X	Management error messages
mcast	X			Mcast messages
message-transport	X	X		Message Transport error messages
module		X		Router module communications/hardware messages
mpls-statc	X			TE/MPLS Statistics Collector messages
msdp				MSDP protocol messages
os	X	X	X	System module; includes: operating system logging, Avici router logging, and memory and buffer management
ospf-events	X			OSPF events
ospf-linkstate	X			OSPF Link state packets, flooding and spf
ospf-spf	X			OSPF SPF timings and related information
ospf-te	X			OSPF Extensions for Traffic Engineering
packer				Packer driver error messages
packet-filtering				Packet filtering messages
pim	X			PIM Protocol messages
pktsched		X		Packet scheduler driver error messages
policy	X			Routing policy messages
post		X	X	POST messages
power-monitor			X	Bay controller power monitoring error messages
qos-manager	X			QOS manager messages
resource-mgmt				Resource management events
routing	X			Non-specific routing functionality.
scrubbing	X			Scrubbing error messages
server	X			Server communications/hardware messages
server-fsm	X			Server FSM logging messages
snmp	X			SNMP error messages
snmp-traps	X	X	X	SNMP generated trap messages.
system-events	X	X	X	Special events signalling a change of platform or interface state
te-api-common	X			Common Traffic Engineering Internal API.
te-api-gated	X			Gated Traffic Engineering Internal API.
te-api-pathmgr	X			Path Manager Internal API.
te-api-rsvpd	X			RSVPd Traffic Engineering Internal API.
te-api-swmap	X			Switch Mapping Internal API.
te-ipc-library	X			TE IPC library messages.
te-ipc-memory	X			TE IPC memory allocation.
traffic-engineering	X			Traffic engineering messages
transport		X		Transport messages
user-commands	X	X	X	CLI commands entered during sessions.

Message Severity Levels

IPriori provides eight levels of severity used for logging messages as shown in Table 14-2:

Table 14-2. Logging System Severity Levels 

Level	Description
1 Critical	Errors that result in a platform reset or could cause the platform to halt very soon. Also used to indicate that a critical system failed to initialize correctly. Due to the severity of the conditions that cause the generation of a critical message, it is possible that the message does not reach the server and get logged at the time it is generated. However, upon system reset, these messages are retrieved from NV-RAM and logged.
2 Major	Errors that result in performance degradation. The problem can result in the incorrect operation of more than one system and could cause a halt.
3 Minor	A problem that affected one system, but operation of other systems should be unaffected.
4 Warning	Notification of an unexpected event or an abnormal condition. The unit should continue to operate normally.
5 Cleared	Used by network management to indicate that a previous error condition has passed.
6 Information	Notices of an informational nature that do not indicate a problem with the system.
7 Trace	Tracing messages
8 Debug	Debug messages

The following pages describe the commands to configure logging on the Avici router.

Copyright © 2005 Avici Systems Inc.
Avici® and TSR® is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are trademarks of Avici Systems Inc.

   Source File Name: Logging.fm
    HTML File Name: Logging.html
    Last Updated: 02/25/05 at 14:31:54

Please email suggestions and comments to: doc@avici.com