|
|
This appendix summarizes the database tables used by CiscoWorks Blue Maps and CiscoWorks Blue SNA View applications. It includes these major sections:
| Caution Do not modify database table information. Database-knowledgeable users should see the schema files located in /opt/CSCOcb/etc. |
This section contains database tables used by for the RSRB, DLSw, and VTAM. The database tables in this section can be found in $CWBROOT/etc/AsaSchemaCommon. This section includes the following table information:
The Devices table (devices) stores necessary information about known devices. There is one record for each device.When the status field changes, or when a device is added or removed, the display is updated.
The Interface table (if_table) is used to store information about the interface such as the device ID, type, and physical address.
The IP Address table (ipaddr_table) is used to store all of the IP addresses configured on each 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. Maps uses the IP Address table to show only one icon for a router even though there might be more than one alias entered in the Maps application.
The Locate Router table (locate_rtr_table) is used to generate the unique device ID for each new device. An entry is made in this table the first time that the device is discovered.
The Logical Unit table (lu_table) contains information about each LU. There is one record for each known LU.
The Logical Views table (logical_views) associates a sequence number with each type of view. This sequence number is passed to the GUI with every view. Sequence numbers are updated by several triggers set on devices, and peer 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.
The MIB Version table (mib_version) lists the version of each MIB for each protocol. This table is for future use only.
The Node table (node_table) contains information about all of the major nodes discovered by the SNA Host component. There is one record for each major node in this table.
The Physical Unit table (pu_table) contains information about all discovered PUs. It is initially populated by the SNA Host discovery process, but is constantly updated by the Status Monitor. For each PU, this table contains the PU name, MAC address, routing information field (RIF) (if available), PU type, local and remote MAC addresses, local and remote SAPs, and current status.
The PU Dependents table (pu_dependents) contains information, taken from the RIF data, about the path that a PU session takes through the network. There is one record for each device in the path. Each record contains the PU name of the device, the device type, and the device name.
The Process Control table (process_control) contains entries for processes that can automatically restart themselves.
The Ring Bridge table (ring_bridge) maintains information about the relationships between real rings 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, Maps can determine the referenced device. Maps parses the PU's RIF to extract (ring, bridge, ring) tuples. And by referring to this tuple, Maps can determine the dependency list for the PU.
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 router. In terms of router configuration commands, every occurrence of the following router command results in one entry in the Ring Bridge table:
source-bridge real-ring bridge-no virtual-ring
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.
This section describes the database tables used for the RSRB protocol. The database tables in this section can be found in $CWBROOT/etc/AsaSchemaRsrb. This section includes the following table information:
The Address ID table (addr_id) 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.
The Peer table (peer_table) contains information about RSRB peers defined on every device. There is 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.
This section describes the database tables used by just the DLSw Maps application. The database tables in this section can be found in $CWBROOT/etc/AsaSchemaDlsw. This section includes the following table information:
The DLSw Address table (dlsw_addr_id) correlates each device ID with an IP address.
The DLSw Circuit table (dlsw_circuits) stores the circuit information.
The DLSw Peer table (dlsw_peers) stores information about the DLSw peer device such as the device ID, domain, local and remote address, and status of the peer connection.
Posted: Thu Sep 9 08:55:19 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.