the VSA portion of the Access-Accept frames, can only be used with the shell protocol value. The
following examples show the roles attribute that is supported by the Cisco Access Control Server (ACS):
shell:roles=network-operator network-admin
shell:roles*“network-operator network-admin
The following examples show the roles attribute that is supported by FreeRADIUS:
Cisco-AVPair = shell:roles=\network-operator network-admin\
Cisco-AVPair = shell:roles*\network-operator network-admin\
When you specify a VSA as shell:roles*"network-operator network-admin" or
"shell:roles*\"network-operator network-admin\"", this VSA is flagged as an optional attribute and other
Cisco devices ignore this attribute.
Note
accountinginfo
Stores accounting information in addition to the attributes covered by a standard RADIUS accounting
protocol. This attribute is sent only in the VSA portion of the Account-Request frames from the RADIUS
client on the switch. It can be used only with the accounting protocol data units (PDUs).
Licensing Requirements for RADIUS
This table shows the licensing requirements for this feature.
License Requirement
Product
RADIUS requires no license. Any feature not included in a license package is bundled with
the nx-os image and is provided at no extra charge to you. For an explanation of the Cisco
NX-OS licensing scheme, see the
Cisco NX-OS Licensing Guide
.
Cisco NX-OS
Prerequisites for RADIUS
RADIUS has the following prerequisites:
• Obtain IPv4 or IPv6 addresses or hostnames for the RADIUS servers.
• Obtain keys from the RADIUS servers.
• Ensure that the Cisco NX-OS device is configured as a RADIUS client of the AAA servers.
Guidelines and Limitations for RADIUS
RADIUS has the following guidelines and limitations:
Cisco Nexus 9000 Series NX-OS Security Configuration Guide, Release 9.x
42
Configuring RADIUS
Licensing Requirements for RADIUS