Server Tables - 3Com corebuilder 3500 Implementation Manual

Hide thumbs Also See for corebuilder 3500:

Table of Contents

Server Tables

Server information table

Router SAP agents use a special aging mechanism to deal with a SAP

agent that goes down suddenly without sending a DOWN broadcast. A

hardware failure, power interruption, or power surge can cause this

Each SAP agent maintains a timer for each entry in its server information

tables. The timer tracks the elapsed time since this entry has been

updated. This information is either new or changed, and the SAP agent

immediately passes it on. Changes are quickly captured and stored

throughout the intranetwork.

SAP Request Handling

When a SAP agent receives a general request, it notifies the sending

source about all servers known to the agent. This response includes the

same information that is sent out in periodic SAP broadcasts. When the

request is specific, the SAP agent notifies the sending source about all

servers of the requested type.

Server information tables contain data about all active servers on the

intranetwork. SAP agents use these tables to store information received

in SAP broadcasts. Server tables are dynamically and statically created.

Figure 78 shows an example of a Server Information Table.

Figure 78 Sample Server Information Table

00-00-00-00-00-01

Do you have a question about the corebuilder 3500 and is the answer not in the manual?