User Manual

Basic Remote Networking Managing Connections With Sites
4-5
Note: Site Commands are discussed on page 12-134.
Currently active sites can be edited, but changes will not take effect until the site is logged out.
4.2.4 Testing Sites
The Test Site command causes a site to start as if outgoing traffic for the site had come into the SCS. It
allows users to test sites without having to generate packet traffic. To test a site, enter a command similar
to the following.
Figure 4-7: Testing a Site
The terminal will display a message that the specified site has started. To stop the test, enter the Logout Site
command followed by the site name.
In the event that there is a problem with the site, or if the Test Site command does not work, use the SCS
site logging feature to troubleshoot the problem. See Set/Define Logging Site on page 12-174 and Show/
Monitor/List Logging Site on page 12-179 for more information.
4.2.5 Deleting Sites
To delete a site, use the Purge Site command.
Figure 4-8: Deleting a Site
When the Purge command is used with the default site, the site’s default configuration will be restored. Any
editing changes you’ve made to the default site will be removed.
Figure 4-9: Restoring Default Site Configuration
4.2.6 Using Sites for Incoming Connections
Incoming connections, both remote node and LAN to LAN, can use either custom sites or temporary sites
which use the default site’s configuration.
Custom sites allow the most flexibility in the control and configuration of incoming connections. They are
used when a specific configuration is required for the incoming router or remote node, and should be named
for the location or user that is calling the SCS. Custom sites are required for Dialback and are recommended
for incoming LAN to LAN connections.
If a group of incoming connections can use the same configuration, they can be allocated temporary sites
used only for that session to save time and system resources. Each temporary site takes its configuration
from the SCS default site. The default site may be customized in the same manner as custom (named) sites;
this customized configuration can then be shared with many remote routers and remote nodes.
Local>> TEST SITE irvine
Local>> PURGE SITE irvine
Local>> PURGE SITE DEFAULT