|
|
This appendix lists the data types and fields for the Cisco Info Server.
Table D-1 describes the data types available within the Cisco Info Server.
| Data type | Description |
|---|---|
char | A string of characters, maximum size is defined by the field size. |
int | An integer value. |
time | Time and date as a value in seconds since Midnight, Jan 1st 1970. |
ltime | Time and date as above, but automatically maintained for last occurrence fields. |
timestamp | Time and date as above, but automatically filled in by the Cisco Info Server when the record is created. |
incr | An integer field which is automatically filled with a Cisco Info Server internal variable when the record is inserted. Used for unique serial number generation. |
optime | A time field which is automatically updated with current date and time whenever an insert or update is done. |
opcount | An integer field which is incremented whenever a record is inserted or an attempt is made to insert a record which already exists. |
The alerts.status table is the storage point for all events and correlations of those events. Table D-2 shows the alerts.status table's default fields in the Cisco Info Server.
| Field Name | Field Type | Field Size | Mandatory | Description |
|---|---|---|---|---|
Identifier | char | 255 | Yes | Internal hash key/table identifier. |
Serial | incr |
| Yes | Cisco Info Center serial number for item. |
Node | char | 64 | Yes | Host or IP address or other name identifying where the alert originated. |
NEName | char | 64 | No | Name of the network element reporting the event. |
Manager | char | 64 | Yes | Descriptive name of the Manager that generated the alert. |
Agent | char | 64 | No | Descriptive name of the sub Manager that generated the alert. |
AlertGroup | char | 64 | No | Descriptive name of the group within the Manager that generated the alert. |
AlertKey | char | 64 | Yes | Descriptive key with reference to the alert (for example, disk partition where threshold exceeded or particular port on a hub). |
Severity | int |
| Yes | Severity of problem: |
Summary | char | 255 | Yes | Summary of alert/problem as human readable text to appear on the administration console. |
StateChange | optime |
| Yes | Automatically maintained timestamp at the Cisco Info Server of last insert/update of alert from any source. |
FirstOccurrence | time |
| Yes | Time (in seconds from Jan. 1, 1970) when this alert was created or when polling started at Info Mediator. |
LastOccurrence | ltime |
| Yes | Time when this alert was last updated at Info Mediator. |
InternalLast | timestamp |
| Yes | Time when this alert was updated at the Cisco Info Server. |
Poll | int |
| No | Frequency of polling for this alert in seconds. |
Type | int |
| No | Type of alert (4 = Trap, 12 = polled event). |
Tally | opcount |
| Yes | Automatically maintained count of the number of inserts/updates of the alert from any source. |
Class | int |
| Yes | Alert class. |
Grade | int |
| No | Grade of alert/problem within the set severity. |
Location | char | 64 | No | Not used: reserved for location identification. |
OwnerUID | int | 8 | Yes | User ID of the user who is assigned to handle this alert. |
OwnerGID | int | 8 | No | Group ID of the group that is assigned to handle this alert. |
Acknowledged | int | 8 | Yes | Has assigned user acknowledged the assignment? (0 = No, 1 = Yes). |
Flash | int |
| No | Enables the option to make the Event List flash. |
ServerName | char | 64 | Yes | Name of originating server. Used by Info Gateways to control propagation of alerts between Cisco Info Servers. |
ServerSerial | int | 8 | Yes | Serial number of alert on originating server (if not originated on this server). Used by Info Gateways to control propagation of alerts between Cisco Info Servers. |
NEAddress | char | 32 | Yes | IP address of the network element used by the CWM machine to access the network element. |
NEType | int |
| Yes | 1 - BPX 8600 2- IGX 8400 3 - MGX 8220 4 - DAS 5 - VNS 6 - DASD 11 - C3800 12 - ESP 14 - MGX 8850 100 - IPX 426 - CWMHost 555 - CSCOrtr 999 - Unknown 1000 InfoCenter Mediator |
ObjectType | char | 64 | Yes | NE |
SubObjectType | char | 64 | No | 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 | int |
| No | The current status of the object reporting the event (for example, " Events cleared by Automation containing " |
Slot | char | 4 | No | Slot number of the network element reporting the event. |
PSAP | char | 6 | No | 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 For multi-port cards, physical line number starts at |
LSAP | char | 6 | No | 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, it is this number which remains constant, even when lines are added and deleted from the port. For virtual trunks, the LSAP contains the user assigned Trunk ID. |
DSAP | char | 24 | No | 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 upon the trap type and trap subtype, this field would contain: FR: DSAP = <DLCI> (DLCI) ATM: DSAP = <VPI>[.<VCI>] (VPI/VCI) |
RemoteNEName | char | 64 | No | This field contains the remote network element name for connection and trunk events. |
RemoteSlot | char | 4 | No | This field contains the slot number for the remote network element name for connection and trunk events. |
RemotePSAP | char | 6 | No | This field contains the PSAP for the remote network element name for connection and trunk events. |
RemoteLSAP | char | 6 | No | This field contains the LSAP for the remote network element name for connection and trunk events. |
RemoteDSAP | char | 24 | No | This field contains the DSAP for the remote network element name for connection events. |
AdditionalInfo | char | 255 | No | This field contains values for all SNMP VarBinds received in the traps that don't fall into one of the other fields. |
TrapReason | char | 64 | No | This field contains the trap reason code as specified in the MIB for BPX 8600 and IGX 8400. For AXIS 8220, 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 upon trap identifiers. |
Customer | char | 64 | No | This field is currently not used. It can be populated with the customer name by the Service Provider. |
Site | char | 64 | No | Physical location field. This is specified by the Service Provider. |
ServiceIdentifier | char | 64 | No | This field is currently not used and can be used by the Service Provider. |
ServiceType | char | 24 | No | 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 | char | 36 | No | This field contains the BitMap from one of the SNMP VarBinds received by the Mediators.The Deocode BitMap tool uses the information within this field, along with the Convert field, to display the decoded values. |
Convert | char | 64 | No | Field used by the BitMap Decode tool to define the conversion values for the BitMap held in the above field. |
OldObjectStatus | int |
| No | Field used to hold the original status as the ObjectStatus field can be modified by Automation. |
OldClass | int |
| No | Field used to hold the original class as the ObjectStatus field can be modified by Automation. |
NELANAddress | char | 32 | Yes | Reserved for internal use only. |
NetworkName | char | 16 | No | Network name of the CWM network to which the network element is attached. |
LNNI | int |
| No | Local-end NNI (Network-to-Network Interface). |
RNNI | int |
| No | Remote-end NNI. |
NEFWVersion | char | 10 | No | The firmware version of the network element. This field is used to determine whether to run the Equipment Manager or CiscoView 4.11 program. |
SVVersion | char | 8 | No | Version of the CWM software (for example, 8.4, 9.1, 9.2). |
NEModelID | char | 12 | No | Model ID of the network element. (This field is for release CWM 9.2) |
Before execution of the rules file, Info Mediator initializes and sets some alert fields as specified in Table D-3. Info Mediator can override these values.
| Field | Set To: |
|---|---|
Identifier | Null string |
Serial | 0 |
Node | Null string |
NodeAlias | Null string |
Manager | Value of the Manager property. |
Agent | Null string |
AlertGroup | Null string |
AlertKey | |
Severity | |
Summary | Null string |
StateChange | |
FirstOccurrence | Current time at the creation of the alert. |
LastOccurrence | Current time at the creation of the alert. |
InternalLast | |
Poll | |
Type | |
Tally | |
Class | |
Grade | |
Location | Null string |
OwnerUID | |
Acknowledged | |
ServerName | Name of server the Info Mediator is connected to (for example, |
ServerSerial | |
OwnerGID | |
Flash | |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Jun 13 17:00:19 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.