PDF user manual for CopperEdge 150

3. The Radius Reply-Message attribute may also containa second 128-character (maximum) text string for useif you want the server to ask the user for additionalinformation or to repeat the previous login attempt.The CopperEdge Radius client will respond to oneAccess_Challenge by resending the same UserNameand Password. If the server does not accept it, the loginfails. The string goes with the Access_Challenge packet.It appears in the CopperEdge Event Log.4. Finally, the Radius server must use the same sharedsecret (AuthKey) string when configuring the bothPrimary and Secondary SCM clients. We recommendthat you use the same AuthKey system-wide, but like agood password, it should be short-lived, unpredictable,and changed at irregular intervals.&RQILJXULQJ&RSSHU(GJHIRU5DGLXV6HUYHUVWhen the Radius server is configured and ready to communicate,and its database has been provisioned with the user database, the CopperEdge cmRadius MIB group can be configured:1. With cmRadius in its default state (Authentication=Disabled), configure all of its objects exceptauthentication. Example:CRAFT> set cmradius authkey=4cr37eiauthprimaryipaddr=10.122.4.4 authprimaryport=1645acctprimaryipaddr=10.122.4.6 acctprimaryport=1646Be sure to use whichever port numbers are recognizedby your Radius servers. Although the officially assignedport numbers for Radius Authentication andAccounting are 1812 and 1813, respectively, manycurrent radius servers still use the port numbers of theoriginal RFC: 1645 for authentication, and 1646 foraccounting. Be sure that the numbers you assign inthe CopperEdge cmRadius configuration match thoseused by your remote Radius servers.2. When you are sure the rest of the configuration iscomplete and correct, activate the Radius capability:CRAFT> set cmradius authentication=enabledFor more data about the cmRadius MIB group, see the Copper-Edge 150 CopperCraft Reference and MIB Definitions manual.&KDSWHU$GYDQFHG&RQILJXUDWLRQ