Next Page

StreetTalk for Windows NT Administrator's Guide

Chapter 1 - Server-to-Server UDP

How the Software Works

Figure 1-1 StreetTalk for Windows NT Server Using Another Server for Routing

How Addresses Are Mapped

The destination server if it runs S-to-S UDP software.

or

A gateway server that runs S-to-S UDP software. When a destination server does not run S-to-S UDP software, it does not have an IP address that has significance for VINES packets. (The server can be running TCP/IP and have an IP address.) Thus, the IP address that is placed in the packet must identify a gateway server that has a StreetTalk for Windows NT route to the destination. Once the packet reaches that gateway server, it can be forwarded to the destination using VINES IP.

Figure 1-2. Routing a VINES Packet

The only way it can reach Server D is through Server C.
Server C can be reached only through an IP network.
Server C's IP address and serial number (VINES IP address).

The IP packets contains a VINES IP packet.
The packet is to be unencapsulated
Based on its VINES IP header, it is destined for Server D.

Encapsulation

Figure 1-3. Server-to-Server UDP Encapsulation

Figure 1-4. VINES IP Packet

Figure 1-5. VINES IP Packet Encapsulated IN UDP Packet

Server Configuration for Server-to-Server UDP

Local and Remote Connections

Figure 1-6. Connecting to a StreetTalk for Windows NT Server

Routing Metric

Metrics for Directly Connected Networks

Note: If the speed of a network is not known (for example, is the network a 4 Mbps or 16 Mbps Token-Ring?), the metric for the slowest network of that type is used.

Table 1-1. Metrics of Network Adapters Recognized by StreetTalk Communications

 Network Adapter

 Metric
 FDDI (Fiber Distributed Data Interface)

1
 Ethernet

2
 Token-Ring

4
 ARCNET

5

Table 1-2. Metrics for Different Types of Media

Type of Media Routing Metric
Fiber Distributed Data Interface (FDDI)

1
10 Mbps Ethernet/16 Mbps Token-Ring

2
10 Mbps ProNET-10

3
4 Mbps Token-Ring

4
2.5 Mbps ARCNET

5
1 Mbps StarLAN, Omninet, and LANSTAR

10
2 Mbps PC-NET

15
Serial Line 56000 baud

45
Serial Line 9600 baud

90
Serial Line 4800 baud

150
Serial Line 1200 baud

450
Fractional T1 1536 Kbps

22
Fractional T1 1024 Kbps

30
Fractional T1 768 Kbps

34
Fractional T1 512 Kbps

38
Fractional T1 384 Kbps

40
Fractional T1 256 Kbps

42
Fractional T1 128 Kbps

44
Fractional T1 64 Kbps

45

Metrics for Remote Networks

Manual Connectivity

Caution: Only one server in a StreetTalk for Windows NT local network should run S-to-S UDP and act as a gateway to the same IP network; do not have redundant links. If two servers act as gateways between two StreetTalk for Windows NT networks, both running S-to-S UDP, and one server fails, that server may have incorrect routing information when it reboots. This is because S-to-S UDP is dependent on other services and takes time to start, thus the routing table is established before S-to-S UDP is ready. You can have multiple S-to-S UDP servers in one network as long as they do not each create a path to the same remote networks.

Names and Serial Numbers

Selecting an IP Address

Note: The S-to-S UDP configuration program attempts to look up the IP address associated with the hostname. You may not need to know the IP address if you know the hostname.

Subnetwork Mask

Table 1-3. Common Subnetwork Mask Values

IP Address Class No Subnetwork Field 4-bit Subnetwork Field 8-bit Subnetwork Field
Class A 255.0.0.0 255.240.0.0 255.255.0.0
Class B 255.255.0.0 255.255.240.0 255.255.255.0
Class C 255.255.255.0 255.255.255.240 Not supported

Metric Values

Metric = 2 + 45 + 4 + 2 = 53

Figure 1-7. Routing Through Three Physical Interfaces

Automatic Connectivity

Changing the Server-to-Server UDP Configuration

Enable or disable automatic connectivity of servers on directly connected or remotely connected networks.
Change metric values and enable or disable broadcasts to remote subnetworks for manually and automatically connected servers.
Add, modify, or delete manually configured connections.
Enter the subnetwork mask when configuring manual connections.
Enable or disable remote subnetwork-directed broadcasts.

Note: Do not enable S-to-S UDP software unless your server requires it. Enabling S-to-S UDP support consumes server resources and causes the StreetTalk Naming service to broadcast additional packets on your network that can impair its performance.

Figure 1-8. Configure Server-to-Server UDP Communications Dialog Box

Note: It is recommended that you always enable any connection that you add.

Table 1-4. Configuration Actions Summary

 

 Local

Remote

 Manual
   Enable/Disable  Metric  Enable/Disable  Metric  Enable/Disable  Metric
 S-S Enabled  Dynamic  Reboot  Dynamic  Reboot  Dynamic  Dynamic
 S-S Disabled  Reboot  Reboot  Reboot  Reboot  Reboot  Reboot

Troubleshooting Server-to-Server UDP

Check TCP/IP.
Check the interface.
Check Security Settings.
Display network neighbors.

Check TCP/IP

Check the LAN Interface

1. Physically disable the interface over which VINES IP traffic runs.

2. Check StreetTalk for Windows NT statistics in Performance Monitor to confirm that encapsulated VINES IP packets are still being received and sent over the IP interface. For example, if no VIP packets are shown as being received or sent over the IP interface, assume that S-to-S UDP software or the interface is not working.

Check Security Settings

Display Servers Connected by S-to-S UDP

Redirection

Figure 1-9. Server-to-Server UDP Redirection

Generate redirects over S-S UDP tunnels
Receive and process the redirects

Metrics

Security

Tunnel Life

Top Of PageNext Page