Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Verifying Network Requirements

 

Basic network connectivity is required to complete the tasks in this chapter. Although it is not a strict requirement, we recommend that a production site use separate networks for RADIUS traffic, SBR administration and SNMP, and SSR traffic.

Verifying Network Connectivity

Verifying Network Connectivity

Use the ping command both to and from another computer to verify that the server on which you are going to install Steel-Belted Radius Carrier can communicate with other devices, such as remote access servers, database servers, DHCP servers, DNS servers, and management workstations on your network, using TCP/IP.

  • If you are going to use CCM, make sure that the primary server and all replica servers can communicate with each other.

  • If you are going to use Session State Register, make sure that all node hosts can communicate with all other node hosts.

For example:

ping 192.168.12.54

If the ping command fails, verify that the IP address of the Steel-Belted Radius Carrier host is correct, that is operational, and that all routers between your server and the remote host are operational.

Verifying Hostname Resolution

Verifying Hostname Resolution

The server on which you are going to install Steel-Belted Radius Carrier must have a stable, accessible IP address that is mapped in /etc/hosts or the Domain Name System (DNS) server to a resolvable hostname.

Note

If you are using installing Session State Register hosts, which must have two network interface cards to provide redundant communications, be sure to test both unless multipathing has already been set up.

To verify that the server has a resolvable hostname, use the ping command with the server’s hostname. For example:

ping foo.juniper.net