Previous Page

Appendix A - Protocol Information

Viewing Protocol Information

VINES Neighbors
VINES Routes
VINES Source-Level Routes
TCP/IP ARP Cache
TCP/IP Interfaces
TCP/IP Domain Name Servers
TCP/IP Routes
TCP/IP UDP Entries
TCP/IP TCP Connections Entries
AppleTalk ARP Cache
AppleTalk Ports
AppleTalk Port Zones
AppleTalk Names
AppleTalk Zones
AppleTalk Routes

Figure A-1. Protocol Information Screen

VINES Neighbors

#

LinkAdr

Sig

NetId

SNetId

NbrT

Slot

Line

IfcT

Table A-1. Interface Types

IfcAdr

VINES Routes

#

NetId

Metric

TTL

Flags

GateNetId

PrefNetId

VINES Source-Level Routes

BrTy

BrNu

S_Ring

T_Ring

Metric

TCP/IP ARP Cache

#

IPAdr

Flags

7 6 5 4 3 2 1 0
0 0 1 0 0 0 0 1

Table A-2. ARP Entries

LnkAdr

Sig

IfcTyp

Slot

Send Qu

TCP/IP Interfaces

IPAdr

SubnetMask

BCastAdr

Flags

15   14  13  12  11  10  9  8  7  6  5  4  3  2  1  0
  0   0   0   0   0   0  0  0  0  0  1  0  0  0  0  1

Table A-3. Interface Entries

IfcTyp

Slot

TCP/IP Domain Name Servers

#

IPAdr

HostName

CSDEPT1.STATEU.EDU

TCP/IP Routes

#

DestIPAdr

GateIPAdr

Flags

15   14  13  12  11  10  9  8  7  6  5  4  3  2  1  0
  0   0   0   0   0   0  0  0  0  0  0  0  0  0  1  1

Bit 0 (0x1) - Indicates that the route can be used.

Bit 1 (0x2) - Indicates that the destination is reached through a gateway.

Bit 2 (0x4) - Indicates that the destination is a host.

Bit 3 (0x8) - Indicates that the entry was created automatically by an ICMP redirect message. These messages tell the server about problems encountered during delivery of data. Typically, gateways make use of ICMP redirect messages to update routes, discover unreachable destinations, and become alerted to network congestion.

Bit 4 (0x10) - Indicates that the gateway specified in the entry was modified dynamically by an ICMP redirect message. An ICMP redirect message tells a server about a better route to a destination than one that the server chose to use previously.

Bit 5 (0x20) - Indicates that the entry was created from the server console through the TCP/IP configuration program.

Bit 6 (0x40) - Indicates that an administrator used the TCP/IP configuration program to delete the routing entry from the server console, but that copies of the entry are still being used by TCP/IP-based applications, such as the SMTP gateway. When these applications have finished using copies of the entry, the entry will be deleted from the TCP/IP routing table.

Bit 7 (0x80) - Indicates that the entry is for a route to a subnetwork, but is not in use because both of the following conditions are met:

- The interface that connects the server to the route's destination subnetwork and the subnetwork itself have the same network numbers.

- One of the addresses - the address of the interface or the address of the adjacent network - is not subnetted.

In this case, TCP/IP option software uses the network route entry that was created automatically when the interface was configured. However, the software keeps the subnetwork entry in case the network number in the address assigned to the interface is changed.

Bit 8 (0x100) - Indicates that the entry is for a manually defined route to an adjacent network or subnetwork that is in use. The administrator creates these routes through the TCP/IP configuration program.

Bit 9 (0x200) - Indicates that the route entry is for the default gateway.

Bit 10 (0x400) - Indicates that the route is a tunnel through a VINES network, and the gateway is a server that has the TCP/IP Routing option installed.

Bit 11 (0x800) - Indicates that the route is through a VINES network, which could be either a tunnel to PCs running PC/TCP or a tunnel that uses a server equipped with the TCP/IP Routing option.

Slot

MedTyp

RefCount

PktFwd

TCP/IP UDP Entries

Local Address

Local

TCP/IP Connection Entries

Local Address

Remote Address

Local

Remote

ConnSt

Table A-4. States of the Connection

MaxSeg

SndWin

RcvW

AppleTalk ARP Cache

#

Net

Node

AdrTyp

Sig

LnkAdr

Timer

Flag

7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 1

IfcTyp

Port

AppleTalk Ports

#

Slot

Net

Node

RngBeg

RngEnd

Status and Flags

Phase 1

1. The server broadcasts AppleTalk ARP probe packets on the cable to determine if the preliminary AppleTalk node ID it selected is not in use by another AppleTalk node. AppleTalk software on the server sets status to INITIALIZING. The software also sets the probing flag (bit 3) to indicate that a probe is in progress.

2. When the server receives a successful response to the probe broadcast from other AppleTalk nodes, it turns off the probing flag. This indicates that the AppleTalk node ID that the server originally selected can be used.

If the selected node ID is in use, the server keeps the probing flag set and probes again with a new address. If the response is successful, the server turns off the probing flag. The server sets the port to SHUTDOWN status if an unused node ID cannot be found.

3. If the port is a seed port, the server sets the network information flag (bit 6) and sends RTMP requests to neighbor AppleTalk seed routers to verify that the network number configured for the port is the same as the network numbers configured for other ports on the cable. The server turns off the network information flag when it receives responses to the RTMP requests, and the responses indicate that the network number for the port is the same as the network number configured for other seed ports on the cable. Otherwise, the network information flag is left on and the server sets status to CONFLICT.

If the port is a non-seed port, the server sets the network information flag and sends RTMP requests to neighbor AppleTalk seed routers to obtain a network number. It turns the network information flag off if the other routers respond with a number.

If no responses are received on a non-seed or a seed port, the port can still initialize if the port is the only port on the server. In this case, the server chooses a network number of 0 for the port and uses * (the asterisk) for the zone name. The server changes status from INITIALIZING to ALONE, and sets the flag that indicates that the initialization period is over (bit 2). The server sets status to ALONE and sets the ALONE flag (bit 9). The ALONE status and flag mean that the port can be used and there are no other routers on the cable connected to the port.

If no responses are received and the port is not the only one on the server, the server sets the port status to NEEDINFO and sets the ALONE flag (bit 9).

4. If the server receives a response to the RTMP request, the server sends a ZIP query request broadcast on the cable connected to the port. The zone information flag (bit 7) is turned on. This flag is turned off when a response to the ZIP query request is processed successfully.

- If the port is a seed port, the server compares the zone names that it receives in ZIP reply packets from other seed routers to the one configured for its own seed port. If the name matches, the port is initialized, status is changed from INITIALIZING to CONFIRMED, and the flag that indicates that the verification period is over (bit 2) is set. Otherwise, the server sets the status of the port to CONFLICT and sets the shut down flag (bit 8) to 1.

- If the port is a non-seed port and the server receives ZIP replies to the ZIP query, the server initializes the port, changes status from INITIALIZING to CONFIRMED, and sets the flag that indicates that the verification period is over (bit 2) to 1.

Phase 2

1. The server broadcasts AppleTalk ARP probe packets on the cable to determine if the provisional node address in the startup range that was selected is not in use by another AppleTalk node. AppleTalk software on the server sets status to INITIALIZING. The software sets the probing flag to indicate that a probe is in progress.

2. If the results of the probe indicate that the provisional node address is valid, the server turns the probing flag off and sets the preliminary address flag (bit 4). Otherwise, the server attempts to probe again.

3. The server broadcasts ZIP GetNetInfo packets and sets the network information flag (bit 6).

4. If the port is a non-seed port and seed routers respond to the broadcast, the server accepts the range and the default zone, and turns the network information flag off.

A non-seed port cannot initialize until a seed router responds to the GetNetInfo broadcast. If no response is received after three tries, the status of the port is set to NEEDINFO and the server continues to send GetNetInfo packets on the cable.

If the port is a seed port and seed routers respond to the broadcast, the server compares the cable range and the default zone in the response to the cable range and the default zone configured for the port. If the routers respond with different ranges and default zones, the server sets the status of the port to CONFLICT, and sets the shut down flag (bit 8), which indicates that the port is shut down. Otherwise, the server accepts the range and the zone, and turns the network information flag off.

If there is no response after three tries, the server assumes that it is the only seed router on the cable.

5. The server sets the re-probing flag (bit 5) and probes again to see if the address it selected is already in use within the network number range for the cable. (The purpose of the preceding probe was to see if the address selected was unique within the startup range). If the results of the probe indicate that the combination is unique, the server turns the re-probe flag off and accepts the address.

If the port is a seed port and the server is the only seed router on the cable, the server sets status to ALONE. The port is now initialized.

6. This step applies to non-seed ports and seed ports that are connected to cables on which other seed routers reside.

The server next broadcasts ZIP query packets and sets the zone information flag (bit 7).

If the port is a non-seed port and seed routers respond to the broadcast, the server accepts the zone lists, turns the zone information bit off, and changes status to CONFIRMED. The port is now initialized.

If the port is a seed port and seed routers respond, the server compares the zone list it has configured for the port with the zone lists that it receives from the other seed routers. If there is no match, the status of the port is set to CONFLICT and the shut down flag is set. This means that the port cannot initialize. Otherwise, the server turns the zone information bit off and sets the status of the port to CONFIRMED. The port is now initialized.

1 - CONFIRMED status. This status applies to non-seed ports and seed ports that are connected to the seed ports of other AppleTalk routers. This status indicates that the port is fully initialized and operational.

2 - INITIALIZING status. This status indicates that the port is in the process of verifying configuration information and performing other functions that determine whether it becomes operational.

3 - ALONE status. This status indicates that the server is the only seed router on the cable.

4 - NEEDINFO status. This status indicates that the server is waiting to discover its AppleTalk internet address and its zone information. The port is not operational while this status appears. If this status continues to appear, it indicates that the port is a non-seed port and the seed routers on the cable are not functioning. The port could be configured as a seed port in order to make it operational.

5 - CONFLICT status. This status applies to seed ports only. It indicates that the configuration of other ports on the cable conflicts with this port's configuration. For example, the ports may not be configured with the same network range, or their default zones may not be the same. The port is not operational.

6 - USERDISABLED status. This status indicates that the port was disabled through the AppleTalk configuration program, which is run from the server console. The disabling of the port appears in the server operating system log.

7 - SHUTDOWN status. This status indicates that the port cannot operate due to insufficient communication buffers or other problems. Consider increasing communication buffers. See Chapter 15 for more information on increasing communication buffers.

15   14  13  12  11  10  9  8  7  6  5  4  3  2  1  0
  0   0   0   0   0   0  0  0  0  0  1  0  0  0  1  1

Bit 0 (0x1) - The port was enabled manually through the AppleTalk configuration program.

Bit 1 (0x2) - The port is a seed port.

Bit 2 (0x4) - The port no longer has to wait for its configuration information, such as zone names and network numbers, to be verified. The bit is set when the port is fully operational.

Bit 3 (0x8) - The port is waiting for the results of an AppleTalk ARP probe broadcast. This broadcast determines whether the AppleTalk internet address that the AppleTalk software dynamically selected for the port is in use by another AppleTalk node on the attached LAN segment.

Bit 4 (0x10) - For AppleTalk Phase 2 ports, the server sets this flag when the initial probe was successful and the server found an unused node ID within the startup range for the port. The address is considered preliminary. The address does not become final until the re-probe succeeds.

For AppleTalk Phase 1 ports, the server sets this flag when the server successfully chooses an unused AppleTalk node ID.

Bit 5 (0x5) - This flag applies to AppleTalk Phase 2 ports only. The flag indicates that the AppleTalk ARP re-probe is in progress. The re-probe occurs after the first probe succeeds and the network range for the port is verified or discovered. The purpose of the re-probe is to determine whether the dynamically selected node ID is unique within the network range for the cable.

Bit 6 (0x40) - For AppleTalk Phase 2 ports, this flag indicates that a GetNetInfo broadcast is being sent on the cable, and the server is waiting for a response. The purpose of this broadcast is to obtain or verify a network number or range of network numbers for the port.

For AppleTalk Phase 1 ports, the server sets this flag when RTMP request packets are broadcast on the cable to discover or verify the network number.

Bit 7 (0x80) - This flag indicates that a zip query is being sent on the port to obtain or verify a zone name or list of zone names for the cable. The flag is turned off when replies to the broadcast are received and successfully processed.

Bit 8 (0x100) - This flag indicates that the port is not operational. This can be caused by any number of problems, ranging from no available AppleTalk internet addresses on the cable to insufficient communication buffers. When no AppleTalk internet addresses are available, they are all in use by other nodes on the cable.

See Chapter 15 for information on increasing communication buffers.

Bit 9 (0x200) - This flag indicates that the server is the only router on the cable associated with the port.

Bit 10 (0x400) - This flag indicates that the port is for tunnelling AppleTalk traffic through VINES. The port is not associated with a LAN card.

NZones

AppleTalk Port Zones

Port

ZonTyp

1 - The zone is the default zone for the port.

2 - The zone is not the default zone.

ZonNam

AppleTalk Names

Net

Node

DDPS

Enum

Name

AppleTalk Zones

EthMulticast and TrnMulticast

ZonNam

Netwks

20 42 43 44 45 41

AppleTalk Routes

Previous PageTop Of Page