Q: How to obtain the CAR vlaue for MA5200 of each version?
For standard RADIUS protocol at R002/r006/9xxx Version, only No. 25 attribute is configured with CAR, so if the attribute of class is set to act as CAR, the user gets its attribute from RADIUS 25; otherwise, it gets the attribute at local. For R009 B03 version, the No. 25 attribute of CLASS and the sub-attribute of 1-6 of No.26 may be configured with CAR value. If MA5200 sets the attribute of class as CAR, the user prefers the attribute of No.25 of RADIUS; if No. 25 is not correct, it will get the attribute from the sub-attribute 1-6 of No. 26. If No. 26 attribute is not correct in format or does not have the attribute, the user will get it from local template. If MA5200 is not configured with CLASS-AS-CAR, the sub-attribute of No. 26 enjoy the preference; if the format of No. 26 attribute is not correct or No. 26 does not have the attribute, the user turns to local template. (Note: Version 9308 needs to load with the latest patch). For MA2.10-71xx version, No. 25 CLASS and the sub-attribute 1-6 of No. 26 may be configured with CAR value, so if the undo radius-server class-as-car command is configured, and No. 26 is configured with CAR with correct format, the sub-attribute 1-6 of No. 26 enjoy the top priority; otherwise, it turns to the l ocal template. If undo radius-server class-as-car is not configured, the last one among No. 25 or the sub-attribute 1-6 of No. 26 brought back by RADIUS will take effect first (even though 9308 version is not loaded with patch). If the format of both attributes are false or both are not configured, the local template is preferred.
For RADIUS+1.0/1.1, CAR depends on the 1-6 sub-attribute of No. 26.