Cisco Info Server Database

This appendix contains information about the tables in the Cisco Info Server database.

This appendix contains the following sections:

Default Fields in the Status Table

An alert in the Event List displays information in each column. Each column represents a field in the alerts.status table in the Cisco Info Server.

An alert comprises fifty default fields. Table C-1 lists the default fields for each alert.

Table C-1: Default Fields
Column Title Use

NEName

Name of the network element reporting the event.

NEAddress

IP address of the network element used by the Cisco WAN Manager 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 - IPX

1 - BPX

2 - IGX

3 - Axis

4 - DAS

5 - VNS

6 - DASD

11 - C3800

12 - 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 that have been cleared by automation have cleared in 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.

Summary

Summary of the event reported by the network element.

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.

Location

This field is currently not used and can be used by the Service Provider to populate this with the location name.

AdminDomain

This field is currently not used and can be used by the Service Provider for administrative region definition.

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.

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.

Severity

Current severity of the event.

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.

Count

Count of the number of times an event has occurred indicates the deduplication.

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.

Trapd is the Cisco WAN Manager Mediator.

Node

This field identifies the origin of alerts. As the origin is usually the Cisco WAN Manager (SNMP Manager) this field contains either the name or IP address of the Cisco WAN Manager hosts.

The only exception to this is for User Connection traps. See the Cisco Info Center Mediator and Gateway Reference for more information.

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).

InternalLast

Time when the alert last occurred using Cisco Info Server time.

StateChange

Automatically maintained timestamp at Cisco Info Server of last insert/update of alert from any source.

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.

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.

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.

ServerName

Name of originating server (gates).

ServerSerial

Serial number of alert in originating server (gates).

Flash

Enables the option to make the Event List flash.

**Table C-1: Default Fields**
Column Title	Use
NEName	Name of the network element reporting the event.
NEAddress	IP address of the network element used by the Cisco WAN Manager 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 - IPX 1 - BPX 2 - IGX 3 - Axis 4 - DAS 5 - VNS 6 - DASD 11 - C3800 12 - 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 that have been cleared by automation have cleared in 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.
Summary	Summary of the event reported by the network element.
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.
Location	This field is currently not used and can be used by the Service Provider to populate this with the location name.
AdminDomain	This field is currently not used and can be used by the Service Provider for administrative region definition.
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.
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.
Severity	Current severity of the event.
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.
Count	Count of the number of times an event has occurred indicates the deduplication.
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. Trapd is the Cisco WAN Manager Mediator.
Node	This field identifies the origin of alerts. As the origin is usually the Cisco WAN Manager (SNMP Manager) this field contains either the name or IP address of the Cisco WAN Manager hosts. The only exception to this is for User Connection traps. See the Cisco Info Center Mediator and Gateway Reference for more information.
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).
InternalLast	Time when the alert last occurred using Cisco Info Server time.
StateChange	Automatically maintained timestamp at Cisco Info Server of last insert/update of alert from any source.
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.
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.
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.
ServerName	Name of originating server (gates).
ServerSerial	Serial number of alert in originating server (gates).
Flash	Enables the option to make the Event List flash.

Details Table

The Details table contains the detail attributes of the alerts in the system. Table C-2 shows the alerts.details table fields in the ObjectServer.

Field name	Description
KeyField	Internal sequencing string for uniqueness.
Identifier	Identifier (as per status table) to relate details to entries in status table.
AttrVal	Boolean; when true, Name and Detail fields are valid, otherwise, only the Detail field is valid.
Sequence	Sequence number, used for ordering entries in the Detail fields.
Name	Name of attribute stored in Detail field.
Detail	Attribute value.

Table C-2: Fields in the alerts.details Table

Field name Description

KeyField

Internal sequencing string for uniqueness.

Identifier

Identifier (as per status table) to relate details to entries in status table.

AttrVal

Boolean; when true, Name and Detail fields are valid, otherwise, only the Detail field is valid.

Sequence

Sequence number, used for ordering entries in the Detail fields.

Name

Name of attribute stored in Detail field.

Detail

Attribute value.

Journal Table

The Journal table provides a history of work done on alerts. Table C-3 shows the fields that are in the alerts.journal table in the ObjectServer.

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.

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.

Table of Contents