Cisco Cisco Prime Optical 9.3 Technical References

Although authentication is external, authorization is local. For example, user privileges are managed 
locally.

The following table lists the RADIUS attributes that Prime Optical supports. The table uses the 
following values:

Request/Accept/Reject/Challenge:

0—The attribute MUST NOT be present in the packet.

0+—Zero or more instances of the attribute MAY be present in the packet.

0-1—Zero or one instance of the attribute MAY be present in the packet. 

1—Exactly one instance of the attribute MUST be present in the packet. 

No.—Number of the RADIUS attribute as specified in the referenced RFC.

Attribute—Name of the RADIUS attribute.

Details—Details about the attribute: how it is used, delivered, or interpreted by the RADIUS client 
on the Prime Optical server.

RFC—Number of the referenced RFC.

RFC Req. Type—Whether a “requirement statement” is present in the referenced RFC.

MUST, MUST NOT, SHOULD, MAY, and so on—Requirement types as specified in RFC 2119. 
These words indicate that a requirement statement is present in the RFC. Note that the “MAY” 
requirements are optional requirements. 

Unspecified—The attribute has no associated requirement statement. The RFC contains only a 
description of the attribute. 

Supported—Indicates Prime Optical support for the attribute:

Yes—Supported

No—Not supported

N/A—Not applicable

Partial—Partially supported

0-1

0-1

0

0

1

User-Name 

The value is the username 
of the authenticating 
Prime Optical user.

2865

MUST

Yes

0-1

0

0

0

2

User-Password

—

2865

MUST

Yes

0-1

0

0

0

3

CHAP-Password

Does not include the PPP 
protocol to connect users 
with the RADIUS client.

2865

MUST

N/A