|
|
This appendix describes the layout of the database tables used by CiscoWorks Blue Maps and CiscoWorks Blue SNA View applications. The following Sybase 10 tables are described:
 | Caution Do not modify database table information. For Sybase-knowledgable users, refer to the schema files located in $CWBROOT/etc. |
Table A-1 lists the conventions used in defining fields.
| Convention | Description |
|---|---|
int | Whole number between 231 -1 (2,147,483,647) and -231 (-2,147,483,648) inclusive. Storage size is 4 bytes. |
smallint | Whole number between 215 -1 (32,767) and -215 (-32,768), inclusive. Storage size is 2 bytes. |
tinyint | Whole number between 0 and 255, inclusive. Storage size is 1 byte. |
NULL | Field that does not have to be filled in. The word null does not have to be entered; the field may be left blank. |
varchar | Variable character defined by the number of characters in parentheses. |
text | Text string. |
image | Block of data. |
Table-to-table links throughout the database structure are accomplished using id fields (such as device_id, people_id, and admin_id).
This section contains database tables used by both the RSRB and DLSw Maps applications.
The Devices table (Table A-2) stores necessary information about known devices, with one record per device. There is an update trigger on the status field, and an insert and delete trigger on the entire table that increments the sequence number field in the Logical Views table for Global, Virtual Ring, and Focus Views.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL UNIQUE | Unique device ID generated by Sybase at the time of insertion into the table. Used as the primary index to the table. |
device_name | char(32) | NOT NULL UNIQUE | Device name or IP address. |
rd_community | char(32) | NULL | Read community string. |
community | char(32) | NULL | Write community string. |
platform_id | int | NULL | Platform type. |
disc_status | smallint | NULL | Discovery status. |
protocols | smallint | NULL | Contains a bit to represent each protocol enabled on the router device. Facilitates determination of protocols configured on the device. |
status | smallint | NULL | Status is either active (111) or inactive (113) at time of insertion into the table. This field changes at discovery time depending on the SNMP response. |
properties | smallint | NULL | Used by DLSw to mark a device as a key device. |
The Locate Router table (Table A-3) is used to generate the unique device_id for each new device and it also stores the dsquery and dbname environment variables that are used to identify the database that contains the device information. An entry is made in this table the first time that the device is discovered. In a distributed environment, this table resides in the master database.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | IDENTITY | Unique device ID generated by Sybase at the time of insertion into the table. Used as the primary index into the table. |
dsquery | char(30) | NOT NULL | Sybase dataserver name where this device's name is stored. |
dbname | char(30) | NULL | Database name. |
device_name | varchar(100) | NOT NULL | Device name or IP address. |
ip_address | int | NOT NULL | IP address used by the router for that protocol. |
The IP Address table (Table A-4) is used to store all of the IP addresses configured on the router. This table is used to correlate the IP addresses of all of the routers obtained from the seed file or network management system database. The goal is to show only one icon for a router even though there might be more than one alias entered in the Maps application.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID generated by Sybase at the time of insertion into the table. Used as the primary index into the table. |
ip_address | int | NOT NULL | IP address used by the router. |
iip_netmask | int | NOT NULL | IP mask used by the router. |
if_index | smallint | NULL | Interface index on the router where this IP address is found. |
The Interface table (Table A-5) is used to store information about the interface such as it's device ID, type, or physical address.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID generated by Sybase at the time of insertion into the table. Used as the primary index into the table. |
if_index | smallint | NULL | Interface index. |
if_type | smallint | NULL | Type of the interface. |
iif_phy_addr | varbinary(12) | NULL | Physical address of the interface. |
The Process table (Table A-6) maintains the status of ownership information of RSRB daemons. The daemons update this table when they are started.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
id | smallint | NOT NULL UNIQUE | Process ID number of a daemon. |
status | smallint | NULL | Current status of this daemon. |
name | char(20) | NULL | Logical name of the owner of this daemon. |
unix_id | int | NULL | Process ID. |
dtime | datetime | NULL | Date and time of this daemon's startup. |
parameters | char(30) | NULL | Command line parameters used to start this daemon. |
The Logical Views table (Table A-7) associates a sequence number to each type of view. This sequence number is passed to the GUI with every view. Sequence numbers are updated by several Sybase triggers set on devices, peer tables, and PU tables. When a change occurs in any of those tables that causes a view to change, the sequence number is incremented. By checking the sequence number, the GUI determines whether a view is up-to-date.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
type | smallint | NOT NULL | View type. |
sequence | int | NULL | Sequence number of this view. |
The Client List table (Table A-8) maintains a list of GUI applications that are registered with the Monitor daemon so that views can be updated. The Monitor daemon initializes its client list by reading entries from this table at startup. It updates this table by adding an entry for each registration request received and by deleting an entry for each deregistration request received. To clear the client list, start the Monitor daemon with the -c option, or truncate this table manually.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
ip_address | int | NOT NULL | IP address of client. |
udp_port | smallint | NOT NULL | The UDP port on which this client listens. |
requests | smallint | NULL | Specify RSRB or DLSw. |
The Ring Bridge table (Table A-9) maintains information about relationships between real and virtual rings on every known RSRB or DLSw device. This table maps directly to the (ring, bridge, ring) tuples extracted from the RIF of each device. Given a (ring, bridge, ring) tuple, the device being referenced can be determined. The PU's RIF is parsed to extract (ring, bridge, ring) tuples, and, by referring to this tuple, the dependency list for the PU can be determined.
There is typically one virtual ring defined per router, so this table will have no more entries than the number of real token ring interfaces on the device. In terms of router configuration commands, every "source-bridge <real-ring> <bridge-no> <virtual ring>" results in one table entry. The total number of entries in this table is an indication of the number of token rings in the network that are bridged using RSRB or DLSw.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Index into this table (from the Devices table). |
ring1 | smallint | NULL | Number of Token Ring 1. |
type1 | smallint | NULL | Indicates whether ring 1 is real or virtual. |
bridge | smallint | NULL | Bridge number between ring 1 and 2. |
ring2 | smallint | NULL | Number of Token Ring 2. |
type2 | smallint | NULL | Indicates whether ring 2 is real or virtual. |
This section contains database tables used by just the RSRB Maps application.
The Address ID table (Table A-10) maps the IP address used for RSRB to the device ID. There is typically one IP address per device for RSRB, but there can be multiple IP addresses if the router defines more than one virtual ring. This table is used to establish peer relationships between routers by matching IP addresses in the Peer Table.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID from the Device table. |
ip_address | int | NULL | IP address used by this device for RSRB. |
The Membership table (Table A-11) maintains a list of all devices connected or attached to a real or virtual ring. It is useful in drawing virtual-ringcentric views and in determining which real rings are associated with each of the routers in the view.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Index into this table. Unique ID of this device from the Devices table. |
ring_no | smallint | NOT NULL | Virtual or real ring number of this device. |
ring_type | smallint | NOT NULL | Indicates whether the ring is real or virtual. |
The Peer table (Table A-12) contains information about RSRB peers defined on every device, with one record per peer definition per router. The poller constantly updates the status of the peers in this table. There are triggers for additions and deletions to this table.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Index into this table from the Devices table. |
vring | smallint | NULL | The virtual ring on which the peer is defined. |
pindex | smallint | NULL | Peer index to allow retrieval of statistical information about a given peer relationship. |
ip_addr | int | NULL | Remote IP address of the peer, if any. |
encap | smallint | NULL | Encapsulation. |
state | smallint | NULL | Current state of this peer. A trigger on this field causes update of the sequence number for RSRB-related views. |
latest | smallint | NULL | Used by the poller for updating peer entries. |
This section contains database tables used by just the DLSw Maps application.
The DLSw Address table (Table A-13) maintains the device ID and IP address used by this device.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID. |
ip_address | int | NULL | IP address used by this device. |
The DLSw Peer table (Table A-14) stores information the DLSw peer device such as device ID, domain, local and remote address, and state of the peer connection.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID. |
domain | smallint | NULL | Transport mechanism. |
local_addr | int | NULL | Local transport address. |
remote_addr | int | NULL | Remote transport address. |
state | smallint | NULL | State of the peer connection. |
config_index | smallint | NULL | Configuration index. |
type | smallint | NULL | Setup type. |
latest | smallint | NULL | Used for updating. |
The DLSw Circuit table (Table A-15) stores the device ID, local MAC address, and local SAP address for the DLSw circuit.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
device_id | numeric(9,0) | NOT NULL | Unique device ID. |
mac1 | binary(12) | NULL | Local MAC address. |
sap1 | binary(2) | NULL | Local SAP. |
if_index | smallint | NULL | Interface index. |
dlc_type | smallint | NULL | Data-link connection type. |
rif | binary(18) | NULL | Route information. |
mac2 | binary(12) | NULL | Remote MAC address. |
sap2 | binary(2) | NULL | Remote SAP. |
location | smallint | NULL | Location. |
domain | smallint | NULL | Transport domain. |
remote_addr | int | NULL | Remote transport address. |
origin | smallint | NULL | Origin. |
state | smallint | NULL | State of the circuit. |
latest | smallint | NULL | Used for updating. |
This section contains database tables that are available only when the CiscoWorks Blue SNA View product is installed.
The Physical Unit table (Table A-16) contains information about all PUs discovered by the SNA driver. It is initially populated by the SNA discovery process, but is constantly updated by the status manager that runs in the background. This table contains information about the PU name, MAC address, RIF (if available), PU type, local and remote MAC addresses, local and remote SAPs, and current status. PU_ID, a unique number assigned to every PU, is the primary index into this table. There is one record per PU in this table . There is a trigger on the status column that increments the sequence number for the PU/LU view in the Logical Views table.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
pu_id | numeric(9,0) | IDENTITY | Unique identifier of this PU. |
pu_name | varchar(17) | NOT NULL | PU name, as defined in VTAM. |
pu_type | smallint | NULL | PU type; type 2.1 is stored as 21. |
status | smallint | NULL | Current status of this PU. |
pu_mac | binary(12) | NULL | Local MAC address (PU MAC address). |
ncp_mac | binary(12) | NULL | Remote MAC address. |
pu_sap | binary(2) | NULL | Local SAP. |
ncp_sap | binary(2) | NULL | Remote SAP. |
xid | binary(4) | NULL | VTAM exchange ID. |
rif | binary(18) | NULL | RIF. |
ring_no | smallint | NULL | The real Token Ring number on which this PU resides, or 0 if there is no RIF for this PU from which to extract the number. |
The Logical Unit table (Table A-17) contains information about LUs. There is one record per known LU. LU status changes are linked to PU status changes, so there is no trigger mechanism to update sequence numbers in the Logical Views table.
| Field Name | Field Type | Field Value | Description |
|---|---|---|---|
pu_name | char(10) | NULL | PU to which this LU is attached. |
lu_name | char(18) | UNIQUE | Name of this LU. |
status | smallint | NULL | Status of the LU is the same as the status of the PU to which it is attached. |
Posted: Thu Aug 19 11:41:38 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.