|
|
This appendix summarizes the database tables used by CiscoWorks Blue Maps and SNA View applications.
This chapter includes the following main sections:
 |
Caution Do not modify database table information. On UNIX workstations, database-knowledgeable users should see the schema files located in /opt/CSCOcb/etc. |
This section contains database tables used for the RSRB, DLSw, and VTAM. The database tables discussed in this section are found in $CWBROOT/etc/AsaSchemaCommon.
This section includes the following tables:
The Client List table (client_list) contains a list of graphical user interface (GUI) applications, which are registered with the monitor daemon so that views can be updated. There is one record for each client. The monitor daemon initializes its client list by reading entries from this table at startup; it updates the 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 edit this table to remove client records.
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 the routers obtained from the seed file or network management system database. Maps uses this table to show only one icon for each router although more than one alias might be 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 the device is discovered.
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 an alteration causes the view to change in any of those tables, the sequence number is incremented. By checking the sequence number, the GUI determines whether a view is up-to-date.
The Membership table (members) maintains a list of all devices connected or attached to a real or virtual ring. This table is used for displaying views centered on virtual rings and in determining which real rings are associated with each of the routers in the view.
The MIB Version table (mib_version) lists the version of each MIB for each protocol.
The Node table (node_table) contains information about all 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. This table 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 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.
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.
Typically, one virtual ring is defined per router, so this table has 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:
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 covers the database tables used for the RSRB protocol. The database tables in this section are found in $CWBROOT/etc/AsaSchemaRsrb.
This section includes the following tables:
The Address ID table (addr_id) maps the IP address used for RSRB to the device ID. Typically, there is 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 covers the database tables used just by the DLSw Maps application. The database tables in this section are found in $CWBROOT/etc/AsaSchemaDlsw. This section includes the following tables:
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: Tue Aug 5 15:48:44 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.