11.07.2015 Views

PDF user manual for CopperEdge 150

PDF user manual for CopperEdge 150

PDF user manual for CopperEdge 150

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

&RQILJXULQJ5DGLXV6HUYHUVIRU&RSSHU(GJHRadius servers and their software are available in a number ofdifferent versions and implementations. Because setup andconfiguration procedures may vary, consult the documentation<strong>for</strong> whichever type you are using <strong>for</strong> full configuration particulars.Similarly, while the <strong>CopperEdge</strong> Radius Client uses all the applicableRadius attributes as documented in RFC-2138 andRFC-2139, certain <strong>CopperEdge</strong>-specific parameters must firstbe translated so the server can interpret and deal with them appropriately:1. Radius Attribute NAS-Identifier may be omitted in thepacket if the <strong>CopperEdge</strong> SystemName object is empty.2. The value of Radius Attribute Filter-Id substitutes <strong>for</strong>the <strong>CopperEdge</strong> Context and Privilege attributes(objects). Filter-Id attribute should contain the stringsContext=HH (with HH a hexadecimal value) andPrivilege=DD (with DD a decimal value) as describedbelow. The syntax of the Filter-Id string is importantbecause the <strong>CopperEdge</strong> unit must extract the valuesof HH and DD to properly complete the login process.Two Filter-Id strings are expected in an Access_Acceptpacket.The filter ID values <strong>for</strong> the <strong>CopperEdge</strong> Contextattributes can be found on the previous page.1 2 7 (Valid numeric values in the Context string can generally be combinedto enable the same operator record to be used in multiple contexts.For example, decimal 12 (Hex 0c) enables both Telnet (04) and Serial(08) contexts. But to distinguish SNMP sessions from normaloperator logins, and to prevent an operator from logging in using onlythe community string, SNMP <strong>user</strong> records must specify a Context ofSNMP only. If an SNMP <strong>user</strong> has a login context value indicatinganything other than SNMP, authentication will be rejected by the<strong>CopperEdge</strong> unit even if accepted by the RADIUS server.The filter ID values <strong>for</strong> the <strong>CopperEdge</strong> Privilegeattributes can be found on the previous page.The Radius Reply-Message attribute may be configuredwith a text string (up to 128 characters) to serve as anerror message in case an attempted login is denied(Access Reject). This string accompanies theAccess_Reject packet, and is entered in the<strong>CopperEdge</strong> Event Log.&RSSHU(GJH,QVWDOODWLRQDQG2SHUDWLQJ*XLGH

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!