Enterasys Networks CSX7000, CSX5500, CSX6000 manual CSM Authentication Server Configuration Elements

CONFIGURING OFF-NODE SERVER INFORMATION

RADIUS Server

CSM AUTHENTICATION SERVER CONFIGURATION ELEMENTS

TCP PORT NUMBER

The TCP port number used by CSM. Note that you can assign a device-defined port number, but that the CSM TCP port number must be entered identically on both the CyberSWITCH and CSM.

CSM AUTHENTICATION SERVER BACKGROUND INFORMATION

When a remote site calls a CyberSWITCH, it sends its identification (such as the system name) and a password (or challenge). The system then sends the data in a message to CSM on a TCP connection. CSM will find the device in its database, searching for the system name (if provided) or the Ethernet address for Combinet Proprietary Protocol (CPP) devices. After finding the device, the password or challenge is verified, and configuration information about the device is sent to the system.

Before allowing data to be sent to the newly-connected device, the system will again query CSM, this time to verify if the call is acceptable. CSM checks against various configuration settings to see if the call is to be allowed.

RADIUS SERVER

You may use the RADIUS Server as an Authentication Server, an Accounting Server, or both. Refer to the following sections for details on configuring these off-node servers.

CONFIGURING A RADIUS AUTHENTICATION SERVER

Notes: In order for the CyberSWITCH to reference a RADIUS Server, ensure the following:

•IP Routing must be enabled. If you try to enable the RADIUS Server before IP routing has been enabled, an error message will be displayed.

•The appropriate LAN network interface(s) must be configured to represent the local IP network.

•The appropriate WAN network information must be configured for each type of remote device configured that will connect to the system.

•The system must have a valid route to the RADIUS Server. This route can be via a directly connected network interface or via a static route. If the RADIUS Server has a direct physical connection to the network, the appropriate network interface must then be configured for that connection. If the RADIUS Server has no direct physical connection to the network, then a static route needs to be configured to establish a route, with one exception: if the router connecting the system to the RADIUS Server supports RIP, no static route is needed. If there are multiple CyberSWITCHes at one site, it is more convenient to maintain all of the static route information for these systems on a central RADIUS Server. The static routes then do not need to be duplicated on all of the Cabletron systems. This is done by enabling the “IP Routes via RADIUS” feature available under CFGEDIT’s IP Information Menu, and including a Framed Route attribute for each system’s RADIUS device entry.

Central Site Remote Access Switch 209