Cisco Info Server Database

This appendix contains the following sections:

Table C-1: Alerts Table Default Fields

Column Title	Use
Identifier	Internal hash key/table identifier. Set by the Info Mediators for the Cisco Info Server for deduplication.
Serial	Unique serial number generated by the Cisco Info Server.
NEName	Name of the network element reporting the event.
Manager	Name given to the Cisco Info Mediator to identify the source of the event. This is set within the Mediator properties. For example, NNM is the HP NNM Mediator. rttrapd (Robust Trap) is the Cisco SV+ Mediator.
Agent	Descriptive name of the submanager.
AlertGroup	Used in the Generic, Type-3, and Type-4 automations to group event pairs. See the Cisco Info Center Administrator Reference for more information on automations.
AlertKey	Descriptive key with reference to the event. This field contains the instance of the Object (for example, NEName Slot for Card Events, Serial0 for Cisco IOS Router Events).
Severity	Current severity of the event.
Summary	Summary of the event reported by the network element.
StateChange	Automatically maintained timestamp at Cisco Info Server of last insert/update of alert from any source.
FirstOccurence	Time the event was created.
LastOccurrence	Time the event last occurred. This field is updated during deduplication which is reflected in the Count field.
InternalLast	Time when the alert last occurred using Cisco Info Server time.
Poll	Frequency of polling for alert in seconds.
Type	Used in the Generic, Type-3, and Type-4 automations to define the relationship between event pairs. See the Cisco Info Center Administrator Reference for more information on automations.
Tally	Automatically maintained count of the number of inserts/updates of the alert from any source.
Class	Class the event belongs to. This field defines the context sensitive tools that are available to each event. See the Cisco Info Center Administrator Reference for more information on classes, menus, and menu options.
Grade	Grade of alert within the set severity.
Location	This field is currently not used and can be used by the Service Provider to populate this with the location name.
OwnerUID	UID of user who owns the alert.
OwnerGID	GID of group that owns the alert.
Acknowledged	Identifies whether an alert is acknowledged or deacknowledged.
Flash	Enables the option to make the Event List flash.
ServerName	Name of originating server (gates).
ServerSerial	Serial number of alert in originating server (gates).
NEAddress	IP address of the network element used by the Cisco StrataView Plus (SV+) machine to access the network element.
NEType	The network element type field which identifies the type of the system reporting the event. This is an integer field which is converted to string by the Cisco Info Server on display in the Cisco Info Admin Desktop. Defined values are: 0,100 - IPX 1,101 - BPX 2,102 - IGX 3,103 - AXIS 4,104 - DAS 5,105 - VNS 6,106 - DASD 12,112 - ESP 999 - Unknown 1000 - Cisco Info Center Mediator
ObjectType	Used to identify the type of object generating the event. An object can be physical or logical. The object-type field helps identify what kind of object in the network is responsible for the given event. It also serves as a means for filtering alarms based on object type (for example, view all port events, view all connection events.) This field must always be defined for every alarm that comes in. Valid field values are: NE Card Connection Endpoint Endpoint.FR Endpoint.ATM Endpoint.CE Endpoint.VOICE Line.access Line.trunk Peripheral Peripheral.dc Peripheral.disk Peripheral.fan Peripheral.ps Peripheral.ts Port Port.ATM Port.FR Port.VOICE System System.config System.connectivity System.general System.nic System.redundancy System.test
SubObjectType	Used to further identify the object. The value in this field depends upon the ObjectType. This field is not mandatory and may be blank in some cases.
ObjectStatus	The current status of the object reporting the event (for example, Downed, Added, Inserted, etc.) Events cleared by automation have cleared as the ObjectStatus.
Slot	Slot number of the network element reporting the event.
PSAP	Physical Service Access Point. The PSAP is a hierarchical identifier for the resource over which virtual circuits are provisioned. The word "Physical" refers to the OSI layer, thus, a PSAP identifies the Layer-1 facility. This hierarchical structure follows the following convention: <physical_line>.<sub_channel1>.<sub_channel2><sub_channeln>. For single port cards, physical line number is always 1. For multi-port cards, physical line number starts at 1.
LSAP	Logical Service Access Point. For naming consistency, the concept of logical port numbering at the card level was introduced. For cards such as UFM, FRSM, and AUSM, a logical identifier for the port is created when the port is provisioned. It can essentially be thought of as a random number, as it has no inherent physical information contained within it. These identifiers are stored in the LSAP field. For IMA, this number remains constant, even when lines are added and deleted from the port. For Virtual Trunks, the LSAP contains the user assigned trunk ID.
DSAP	Data Link Service Access Point. This field contains the Virtual Circuit Identifier (VCI). The syntax is <DSAP> (<annotation>), with a space delimiting the DSAP from the annotation, and the annotation appearing in parentheses. This SAP is used between OSI Layer-3 and Layer-2 to identify virtual circuits. Depending on the trap type and trap subtype, this field contains: FR: DSAP = <DLCI> (DLCI) ATM: DSAP = <VPI>[.<VCI>] (VPI/VCI)
RemoteNEName	This field contains the Remote Network Element Name for connection and trunk events.
RemoteSlot	This field contains the Slot number for the Remote Network Element Name for connection and trunk events.
RemotePSAP	This field contains the PSAP for the remote network element name for connection and trunk events.
RemoteLSAP	This field contains the LSAP for the remote network element name for connection and trunk events.
RemoteDSAP	This field contains the DSAP for the remote network element name for connection events.
AdditionalInfo	This field contains values for all SNMP VarBinds received in the traps that don't fall into one of the other fields.
TrapReason	This field contains the trap reason code as specified in the MIB for BPX and IGX. For AXIS, VNS, and ESP, trap reason is populated by the trap number itself, as each trap is associated with a specific event. This allows filtering on a range of traps, based on trap identifiers.
Customer	This field is currently not used and can be used by the Service Provider to populate this with the customer name.
Site	Physical location field. This is left to be specified by the Service Provider.
ServiceIdentifier	This field is currently not used and can be used by the Service Provider.
ServiceType	This field is used by the Real Time Counter tool to determine the counters. See the Cisco Info Center Administrator Reference for more information.
BitMapField	This field contains the BitMap from one of the SNMP VarBinds that is received by the Mediators. The Decode BitMap tool uses the information within this field along with the convert field to display the decoded values.
Convert	Field used by the Decode BitMap tool to define the conversion values for the BitMap held in the above field.
OldObjectStatus	Field used to hold the original status, as the ObjectStatus field can be modified by Automation.
FRASM_misc	Reserved for internal use only.
NetworkName	Network name of the Cisco SV+ network to which the network element is attached.
LNNI	Local end Network-to-Network Interface (NNI).
RNNI	Remote end NNI.
NEFWVersion	Firmware version number of the network element. This field is used to determine whether to run the Equipment Manager or CiscoView.
SVVersion	Version of the Cisco SV+ software (for example, 8.4, 9.1).
NEModelID	Model ID of the network element.

Table C-3: Fields in the alerts.journal Table

Field Name	Description
KeyField	Unique key field for table.
Serial	Serial number of alert this journal entry is related to.
UID	User ID of the user who made this entry.
Chrono	Time and date this entry was made.
Text1	First block of text for journal entry.
Text2	Second block of text for journal entry.
Text3	Third block of text for journal entry.
Text4	Fourth block of text for journal entry.
Text5	Fifth block of text for journal entry.
Text6	Sixth block of text for journal entry.
Text7	Seventh block of text for journal entry.
Text8	Eighth block of text for journal entry.
Text9	Ninth block of text for journal entry.
Text10	Tenth block of text for journal entry.
Text11	Eleventh block of text for journal entry.
Text12	Twelfth block of text for journal entry.
Text13	Thirteenth block of text for journal entry.
Text14	Fourteenth block of text for journal entry.
Text15	Fifteenth block of text for journal entry.
Text16	Sixteenth block of text for journal entry.