User`s guide

USER’S GUIDE
86 SFVRA Connection Manager
NETWORK PROXIES
The RIP service operates by advertising itself as a path to reach one or more remote subnets. If the
RIP service data is destined for a remote subnet, the RIP service forwards the connection
information to the SFVRA service. The SFVRA service will initiate a call to the remote subnet
through a local CyberSWITCH. The CyberSWITCH then advertises itself as the path to the remote
subnet. This procedure operates most efficiently when the RIP service resides on the same IP subnet
as the CyberSWITCH that eventually makes the outgoing call, because local routers do not have to
update their routing tables when a call is made. If the CyberSWITCHES are located on separate
subnets, system performance is adversely affected when the RIP service only resides on the same
machine as the SFVRA service.
Distributed RIP services allows multiple RIP services to be located on the separate subnets. Each
service only advertises for the CyberSWITCHES on its local subnet. Each RIP service can be
configured to belong to one or more CyberSWITCH - User Groups. Since the services advertise for
remote devices, assigning a RIP Service to a group(s) prevents multiple RIP Services from
advertising for the same remote device.
The Proxy ARP Service will receive all ARP requests on the network. For each ARP request, the
service will check the IP addresses and the static routes of all connected devices, and check the IP
pool addresses currently in use for a match with the target IP address. If a match is found, a proxy
ARP reply is sent using the MAC address of the connecting CyberSWITCH as the sender MAC
address. If a match is not found, the service will check the IP addresses and static routes of all
callable remote devices for a match with the target IP address. If a match is found, an ARP reply is
sent using the MAC address of the local machine as the sender MAC address. This will cause any
subsequent IP packets destined for the target IP address to be sent to the Proxy ARP Service.
A similar procedure is used for receiving IP packets as well. Each IP packet received, the service
will check the IP addresses and static routes of all connected remote devices, and check the IP pool
addresses currently in use for a match with the target IP address. If a match is found, the packet is
discarded. If a match is not found, the service checks the IP addresses and static routes of all callable
remote devices for a match with the target IP address. If a match is found, a request is sent to the
SFVRA Service to establish a connection to the remote device. The IP packet is then placed into a
list of pending IP packets. When a connection to the remote device is established, the SFVRA
Service notifies the Proxy ARP Service. If the connection is not established within 15 seconds the
packet is discarded.
The SFVRA Service sends notification messages to the Proxy ARP Service whenever connections
are established or terminated. When the Proxy ARP Service receives a connection notification
message, it marks the remote device as connected. It then checks the destination IP addresses in the
list of pending IP packets for a match with the remote device’s static routes or IP address. If a match
is found, the Proxy ARP Service broadcasts a gratuitous ARP for the destination IP address with
the CyberSWITCH’S MAC address as the sender MAC address. This will cause all local devices to
update their ARP cache entry for this IP address, if they have such an entry.
The Proxy ARP Service can be configured to belong to one or more groups.