# RADIUS-VMS
product documentation

Previous | Contents

# Chapter 6
An additional information and appendixes.

# Appendix A
RADIUS-VMS Messaging & Troubleshooting.

RADIUS-VMS provide a lot of diagnostic messages which help to admins to performs management & maintenance task.

> RADIUS-I-main_CMD_SHUT, MAIN:Shutdown is requested.

Severity: INFORMATIONAL
Explanation: Informational message.
User Action: None.

> RADIUS-I-main_CMD_RSET, MAIN:Reset is requested.

Severity: INFORMATIONAL
Explanation: Informational message.
User Action: None.

> RADIUS-I-main_CMD_RSTA, MAIN:Full restart is requested.

Severity: INFORMATIONAL
Explanation: Informational message.
User Action: None.

> RADIUS-I-main_NETOPEN, MAIN:Started listener on ip address !AZ/udp port !UW

Severity: INFORMATIONAL
Explanation: Informational message.
User Action: None.

> RADIUS-I-main_VERSION, MAIN:!AZ/!AZ Server, Was built at !AZ

Severity: INFORMATIONAL
Explanation: Informational message.
User Action: None.

> RADIUS-I-main_NTFSTS, Command (!XL) has been sent to !AS (!XL),status=%x!XL

Severity: INFORMATIONAL
Explanation:
User Action:

> RADIUS-E-main_ERRNETOPEN, MAIN:Error open network device with ip address !AZ/udp port !UW,status=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS at startup time experienced problem with network stuff.
User Action: Ensuring that TCP/IP support installed, configured , and started. Check using of this UDP port by other application. An additional information can be obtained by status code, it's result of $QIO calls.

> RADIUS-E-main_ERREXTINIT, MAIN:External INIT routine return status=%x!XL, external module will be not used

Severity: ERROR
Explanation: An external routine from external module return error VMS condition code. RADIUS-VMS will call othre routines from the external module.
User Action: Investigate a situation by condition code.

> RADIUS-E-main_ERREXTCLEANUP, MAIN:External CLEANUP routine return status=%x!XL

Severity: ERROR
Explanation: An external routine from external module return error VMS condition code.
User Action: Investigate a situation by condition code.

> RADIUS-E-main_INVNODE, Invalid node name !AS

Severity: ERROR
Explanation: A node name has been specified by the /NODE option is invalid or not present in the cluster.
User Action: Check typos or cluster members by SHOW CLUSTER command.

> RADIUS-F-dict_CNTREAD, DICT:Could not read file RADIUS_DICTIONARY,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS can't open RADIUS_DICTIONARY file at startup time.
User Action: Check the RADIUS_DICTIONARY logical, also check out a reason by examination of the status code. RADIUS-VMS can't work w/o RADIUS_DICTIONARY file.

> RADIUS-F-dict_INSFMEM, DICT:Ran out of memory after reading line !UL,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS experienced a memory allocation problem, it possible a quota problem for this process.
User Action: Check out SYSGEN's PQL group of parameters. An additional information can be obtained from VMS ACCOUNTING by ACC /SINCE/IMAGE=RADIUS_SERVER.EXE. The status code is a result of calling lib$get_vm().

> RADIUS-E-dict_INVATTR, DICT:Invalid attribute on line !UL

Severity: ERROR
Explanation: RADIUS-VMS during startup time performs parsing of the RADIUS_DICTIONARY file, load it into memory for fastest access.
User Action: Check RADIUS_DICTIONARY file at line showed in the error message.

> RADIUS-E-dict_INVVENDOR, DICT:Invalid vendor attribute on line !UL

Severity: ERROR
Explanation: RADIUS-VMS during startup time performs parsing of the RADIUS_DICTIONARY file, load it into memory for fastest access.
User Action: Check RADIUS_DICTIONARY file at line showed in the error message, restart RADIUS-VMS server.

> RADIUS-E-dict_VNTOOLONG, DICT:Vendor name is too long on line !UL

Severity: ERROR
Explanation: Name of VENDOR can't be more 31 characters of length.
User Action: Revise RADIUS_DICTIONARY file and reduce length of the vendor name, or use reduced form for the vendor.

> RADIUS-E-dict_ATOOLONG, DICT:Attribute name too long on line !UL

Severity: ERROR
Explanation: Name of ATTRIBUTE can't be more 31 characters of length.
User Action: Revise RADIUS_DICTIONARY file and reduce length of the attribute name, or use reduced form for the attribute name. For example: ATTRIBUTE Speed_of_Async_connections_at_DECServer_90M ... can be change to: ATTRIBUTE SpeedDS90M ...

> RADIUS-E-dict_VNNODIGIT, DICT:Vendor attribute has not a numeric value on line !UL

Severity: ERROR
Explanation: RADIUS-VMS can't interpret given value as numeric. Any VENDOR attribute in RADIUS_DICTIONARY file must be represented by numeric value.
User Action: Check out VENDOR entry at line number is showed in error message; use decimal notation for value.

> RADIUS-E-dict_ANODIGIT, DICT:Attribute has not a numeric value on line !UL

Severity: ERROR
Explanation: RADIUS-VMS can't interpret given value as numeric. Any ATTRIBUTE in RADIUS_DICTIONARY file must be represented by numeric value.
User Action: Check out ATTRIBUTE entry at line number is showed in error message; use decimal notation for value.

> RADIUS-E-dict_INVALUE, DICT:Invalid value entry on line !UL

Severity: ERROR
Explanation: RADIUS-VMS can't interpret the VALUE definition in the RADIUS_DICTIONARY file.
User Action: A VALUE entry must contains 4 fields, check out syntax for entry at line number showed in error message.

> RADIUS-E-dict_VTOOLONG, DICT:Value name is too long on line !UL

Severity: ERROR
Explanation: VALUE entry parsing problem. Name of VALUE can't be more 31 characters of length.
User Action: Revise RADIUS_DICTIONARY file and reduce length of the value name, or use reduced form for the value name.

> RADIUS-E-dict_VNONDIGIT, DICT:Value has non-numeric value on line !UL

Severity: ERROR
Explanation: VALUE entry parsing problem. Any VALUE entry in RADIUS_DICTIONARY file must be represented by numeric value.
User Action: Check out VALUE entry at line number showed in error message; use decimal notation for value.

> RADIUS-E-dict_NOVENDOR, DICT:VENDOR '!AZ' not found, bad ATTRIBUTE line !UL

Severity: ERROR
Explanation: A VENDOR specific ATTRIBUTE entry in RADIUS_DICTIONARY file must be placed after related VENDOR entry.
User Action: Examine dictionary file at line number showed in error message. Put the ATTRIBUTE entry after related VENDOR entry in the RADIUS_DICTIONARY file.

> RADIUS-E-dict_NOATTR, DICT:Attribute '!AZ' not found, bad VALUE line !UL

Severity: ERROR
Explanation: A VALUE entry in RADIUS_DICTIONARY file must be placed after related ATTRIBUTE entry.
User Action: Examine dictionary file at line number showed in error message. Put the VALUE entry after related ATTRIBUTE entry in the RADIUS_DICTIONARY file.

> RADIUS-E-user_ZERONAME, USER:Zero length username has been rejected

Severity: ERROR
Explanation: Incoming authentication request not contains username, or length of the username string is zero. Commonly, it's user's typos.
User Action: Contact user, and check user input for correctness. Also it can be of a remote RADIUS server problem in case a roaming user.

> RADIUS-E-user_CNTPARSE, USER:Unable to parse check-items '!AZ' for user '!AD'

Severity: ERROR
Explanation: RADIUS-VMS server can't parse Check-Item data from RADIUS_USERS file during processing have gotten an authentication request. It can be of result of typos in RADIUS_USERS; also RADIUS_DICTIONARY file may not contains ATTRIBUTE entry for this Check-Item.
User Action: Check that all ATTRIBUTE(s) which are used in the RADIUS_USERS file has been defined in the RADIUS_DICTIONARY file. Also check case of ATTRIBUTE items in the RADIUS_USERS file. After any corrections you need to restart RADIUS-VMS server.

> RADIUS-E-user_ERRPARSE, USER:Unable to parse reply-items '!AZ' for user '!AD'

Severity: ERROR
Explanation: RADIUS-VMS server can't parse Reply-Item data from RADIUS_USERS file during processing have gotten an authentication request. It can be of result of typos in RADIUS_USERS; also RADIUS_DICTIONARY file may not contains ATTRIBUTE entry for this Reply-Item.
User Action: Check that all ATTRIBUTE(s) which are used in the RADIUS_USERS file has been defined in the RADIUS_DICTIONARY file. Also check case of ATTRIBUTE items in the RADIUS_USERS file. After any corrections you need to restart RADIUS-VMS server.

> RADIUS-E-user_INSFMEM, USER:Ran out of memory,status=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS experienced a memory allocation problem, it possible a quota problem for this process.
User Action: Check out SYSGEN's PQL group of parameters. An additional information can be obtained from VMS ACCOUNTING by ACC /SINCE/IMAGE=RADIUS_SERVER.EXE.

> RADIUS-E-user_BADTIME, USER:Can't parse date format '!AZ',status=%x!XL

Severity: ERROR
Explanation: Check out date format, date must present in VMS specification. An additional information can be obtained from status code, it's result of $BINTIM system service.
User Action: Study of a VMS date & time format by HELP Specify Date_Time.

> RADIUS-F-user_CNTOPEN, USER:Could not open RADIUS_USERS file, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS could not open RADIUS_USERS file.
User Action: Investigate a reason by examination of status and stv codes, it's result of the RMS's $OPEN calls. After corrections you need restart RADIUS-VMS server.

> RADIUS-F-user_CNTOPENS, USER:Could not open RADIUS_USERS file stream, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS could not open stream to RADIUS_USERS file.
User Action: Investigate a reason by examination of status and stv codes, it's result of the RMS's $CONNECT calls.

> RADIUS-F-user_CNTREAD, USER:Could not read RADIUS_USERS file, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS experienced an error during read from RADIUS_USERS file, investigate a reason by examination of status and stv codes, it's result of the RMS' $GET calls.
User Action: Check access mode of the account runing the RADUS-VMS.

> RADIUS-F-acct_ERRTHREAD, ACCT:Could not create thread #!UL,errno=!AZ

Severity: FATAL
Explanation: RADIUS-VMS could not create a thread for accounting requests, errno string provides an additional information about of reason.
User Action: You can increase quotas for the process, or reducing a number of threads (see purpose of the RADIUS_NUMTHREADS logicals).

> RADIUS-F-acct_NETIOERR, ACCT:Network I/O error,status=%x!XL

Severity: FATAL
Explanation: A network I/O error is occurred in an accounting thread, investigate a reason by examination of the status code, it's result of the $QIO system calls.
User Action: Check using of this UDP port by other programs on the same node.

> RADIUS-F-acct_BCNTOPEN, ACCT:Could not open RADIUS_ACCBIN file, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS's could not open RADIUS_ACCBIN file, investigate a reason by examination of status code, it's result of the RMS $OPEN calls. RADIUS-VMS will continue work after this error.
User Action: Check an accessibility of the file pointed by RADIUS_ACCBIN file.

> RADIUS-F-acct_ERRPUTBIN, ACCT:Can't write detail record status=%x!XL,stv=%x!XL

Severity: FATAL
Explanation: RADIUS server can't write a detail accounting record to the RADIUS_ACCTBIN file.
User Action: Investigate a situation with status & stv codes, it was a result of $PUT or $FLUSH RMS calls.

> RADIUS-E-acct_ACNTOPEN, ACCT:Could not open RADIUS_ACCOUNTING file, status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS's could not open RADIUS_ACCOUNTING file, investigate a reason by examination of status code, it's result of the RMS $OPEN calls. RADIUS-VMS will continue work after this error.
User Action: Check an accessibility of the file pointed by RADIUS_ACCOUNTING file.

> RADIUS-E-acct_ACNTOPENS, ACCT:Could not open stream to RADIUS_ACCOUNTING file, status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not open stream to RADIUS_ACCOUNTING file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $CONNECT calls.

> RADIUS-E-acct_BCNTOPENS, ACCT:Could not open stream to RADIUS_ACCBIN file, status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not open stream to RADIUS_ACCBIN file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $CONNECT calls.

> RADIUS-E-acct_CCNTREADS, ACCT:Could not read RADIUS_CURRENT record,status=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not read a record from RADIUS_CURRENT file.
User Action: Investigate a reason by examination of status code, it's result of the RMS $GET calls.

> RADIUS-E-acct_ERRPUTDETAL, ACCT:Can't write detail record status=%x!XL,stv=%x!XL

Severity: ERROR
Explanation: RADIUS server can't write a detail accounting record to the RADIUS_DETAIL file.
User Action: Investigate a situation with status & stv codes, it was a result of $PUT or $FLUSH RMS calls.

> RADIUS-E-acct_ERREXTACCT, ACCT:External ACCOUNTING routine return status=%x!XL

Severity: ERROR
Explanation: An external routine from external module return error VMS condition code.
User Action: Investigate a situation by condition code.

> RADIUS-E-acct_UNKNCLNT, ACCT:Unknown client !AZ (!AZ),ignore request

Severity: ERROR
Explanation: RADIUS-VMS got and dropped accounting request from client wich had been not defined in a RADIUS_CONFIG.
User Action: Investigate a situation by looking to IP address of incoming request, it's possible a setup problem at remote site.

> RADIUS-E-acct_CANTDLENTRY, ACCT:Can't delete entry in RADIUS_CURRENT for '!AZ' at !AZ;status=%x!XL,stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS can't delete user's record from RADIUS_CURRENT due a some problem.
User Action: Investigate a status & stv code it's result of RMS's $DELETE call.

> RADIUS-E-acct_CCNTOPEN, ACCT:Could not open RADIUS_CURRENT file,status=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS's could not open RADIUS_CURRENT file.
User Action: Investigate a reason by examination of status code, it's result of the RMS $OPEN calls.

> RADIUS-W-acct_UNKNREALM, ACCT:Unknown realm in '!AF', possible request droping from !AC

Severity: WARNING
Explanation: An username in accounting request contains realm suffix has been not defined in the RADIUS_CONFIG file.
User Action: Investigate situation and take appropriate actions.

> RADIUS-W-acct_CCNTOPENS, ACCT:Could not open RADIUS_CURRENT stream,status=%x!XL

Severity: WARNING
Explanation: RADIUS-VMS could not open stream to RADIUS_CURRENT file.
User Action: Investigate a reason by examination of status code, it's result of the RMS $CONNECT calls.

> RADIUS-W-acct_INVAUTH, ACCT:Client !AC sent request with invalid digest

Severity: WARNING
Explanation: An accounting request is contains an invalid digest.
User Action: Check out a shared secret in the RADIUS_CONFIG file and on the NAS for matching. In some case wrong digest is result of using old NAS(s) like DEC Server 90M or USR Total Control.

> RADIUS-W-acct_NOENTRY, ACCT:No entry in RADIUS_CURRENT for '!AZ' at !AZ

Severity: WARNING
Explanation: RADIUS-VMS tried to delete user's record from the RADIUS_CURRENT file, after user logout.
User Action: It's can be result of the network or performance problem.

> RADIUS-W-acct_BUSYENTRY, ACCT:Can't delete entry in RADIUS_CURRENT for '!AZ' at !AZ;there is user = '!AD'

Severity: WARNING
Explanation: RADIUS-VMS don't delete user's record if in a RADIUS_CURRENT exist a record with other username with the same NAS/Port pair.
User Action: None.

> RADIUS-W-acct_CNTENTRY, ACCT:Error write entry in RADIUS_CURRENT for '!AD' at !AD, status=%x!XL, stv=%x!XL

Severity: WARNING
Explanation: RADIUS-VMS can't write status record to the RADIUS_CURRENT file.
User Action: Investigate a reason by examination of status and stv codes, it's a result of the RMS's $PUT calls. Check access to the RADIUS_CURRENT file by custom applications. Stop RADIUS-VMS, delete RADIUS_CURRENT file, and restart RADIUS-VMS.

> RADIUS-W-acct_NOUSERNM, ACCT:Request from client !AC contains no user name

Severity: WARNING
Explanation: Incoming accounting request has not an username. Or length of the username string is zero. Commonly, it's user's typos.
User Action: Contact user for ensuring that user input right value for username.

> RADIUS-F-recv_INSFMEM, RECV:Ran out of memory,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS can't processing incoming request due problem with memory allocation.
User Action: Investigate a reason by examination of the status code, it's result of the LIB$GET_VM system calls. Increase process memory quotas.

> RADIUS-F-recv_TOOSHORT, RECV:Request from node !AZ:!UW is too short to be real (!UW bytes)

Severity: FATAL
Explanation: Request was dropped due consistence control.
User Action: Network problem ? Hacker attack ? Keep your eyes open!

> RADIUS-F-recv_INVLEN, RECV:Request from node !AZ:!UW claimed length !UW, only !UW bytes found

Severity: FATAL
Explanation: Request was dropped due consistence control.
User Action: Network problem ? Hacker attack ? Keep your eyes open!

> RADIUS-F-recv_ATTRTOLONG, RECV:Received attribute !UB from node !AZ:!UW is too long, length of !UB exceed !UW

Severity: FATAL
Explanation: An attribute length is exceed a real data length in the buffer or internal limit. A paring is stopped and rest of attribute/value pairs will not be processed. The packet will be silently droped.
User Action: Network problem ? Hacker attack ? Keep your eyes open!

> RADIUS-F-recv_UNKNTYPE, RECV:Unknown request code !UB from node !AZ:!UW

Severity: FATAL
Explanation: Request was dropped due consistence control. Network problem ? Hacker attack ? Keep your eyes open!
User Action: Contact support staff for investigate of the reason for this request, ask Radius-VMS support group for additional explanation.

> RADIUS-W-recv_INVATTR, RECV:Received unknown attribute !UL (vendor=!UL) from node !AZ:!UW, attribute is ignored

Severity: WARNING
Explanation: RADIUS-VMS received request which contains unknown attribute.
User Action: You can manually add entry for this ATTRIBUTE into a RADIUS_DINCTIONARY, or download latest dictionary file from a support site. Check out docs for your equipment for obtaining correct definition of the ATTRIBUTE.

> RADIUS-F-auth_UCNTOPENS, AUTH:Could not open RADIUS_USERS stream,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS could not open stream to RADIUS_USERS file at startup time or during self restart of authentication threads.
User Action: Investigate a reason by examination of status code, it's result of the RMS $CONNECT calls. Check process quota, reduce number of threads.

> RADIUS-F-auth_CCNTOPENS, AUTH:Could not open RADIUS_CURRENT stream,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS could not open stream to RADIUS_CURRENT file.
User Action: Investigate a reason by examination of status code, it's result of the RMS $CONNECT calls.

> RADIUS-F-auth_ERRTHREAD, AUTH:Could not create thread #!UL,errno=!AZ

Severity: FATAL
Explanation: RADIUS-VMS could not create a thread for authentication requests, errno string provides an additional information about of reason.
User Action: You can increase quotas for the process, or reducing a number of total threads (see purpose of RADIUS_NUMTHREADS logical).

> RADIUS-F-auth_NETIOERR, AUTH:Network I/O error,status=%x!XL

Severity: FATAL
Explanation: A network I/O error is occurred in an authentication thread.
User Action: Investigate a reason by examination of the status code, it's result of the $QIO system calls. Check using of this UDP port by other programs on the same node.

> RADIUS-E-auth_UNDEFDOM, AUTH:Undefined domain preffix in username '!AF'

Severity: ERROR
Explanation: Domain is not defined in RADIUS_CONFIG.
User Action: Check RADIUS_CONFIG file, add domain definition entry.

> RADIUS-E-auth_ERRAUTHDOM, AUTH:Error authenticate user '!AF' in domain '!AC'

Severity: ERROR
Explanation: Error authenticate a user on DC, it's possible a network problem.
User Action: Investigate a situation with a status code, it can be a network problem. Reboot DC, install a latest SP, kick ass BG, and reboot again the DC.

> RADIUS-E-auth_NOEXTERN, AUTH:Can't authenticate, external procedure is not defined

Severity: ERROR
Explanation: RADIUS-VMS can't performs authentication forced by Auth-Type = Extern in the RADIUS_USERS file.
User Action: Check RADIUS_USERS file, check RADIUS' server log file for possible intialization errors.

> RADIUS-E-auth_INVREQST, AUTH:Unknown request type !UB from !AZ (!AZ),request ignored

Severity: ERROR
Explanation: RADIUS-VMS received request with code which is not supported.
User Action: Contact Radius-VMS support group.

> RADIUS-E-auth_UNKNCLNT, AUTH:Unknown client !AZ (!AZ), request ignored

Severity: ERROR
Explanation: RADIUS-VMS dropped request from unknown client.
User Action: Investigate situation, add CLIENT entry for given in error message IP name/address into the RADIUS_CONFIG file, and restart RADIUS-VMS server.

> RADIUS-E-auth_NOUSERNM, AUTH:Request from !AC (CLID='!AD') is rejected - no user name

Severity: ERROR
Explanation: A received request not contains username, or username have zero length.
User Action: None.

> RADIUS-E-auth_BADCHAR, AUTH:Request from !AC is rejected;bad characters in username '!AF'

Severity: ERROR
Explanation: RADIUS-VMS send reject to the client due presence in username of invalid characters.
User Action: Refer to RADIUS-VMS documentaion about of allowed characters for username.

> RADIUS-E-auth_NOPASSW, AUTH:Request from !AC (CLID='!AD') for '!AD' is rejected;no password or CHAP password is used

Severity: ERROR
Explanation: RADIUS-VMS reject any authentication request w/o password. It can't performs authentication for SYSUAF users by CHAP, because SYSUAF keep one-way hashed passwords only.
User Action: Contact user and ensure that it have entered password, take advice do not use CHAP, or add entry for this user into the RADIUS_USERS file.

> RADIUS-E-auth_NOACCESS, AUTH:Request from !AC denied for unknown user '!AZ'

Severity: ERROR
Explanation: RADIUS-VMS can't find user in the RADIUS_USERS file, and in SYSUAF.
User Action: Check an existence of the account by using the AUTHORIZE utility, remove all spaces and tabs before username in a RADIUS_USERS file.

> RADIUS-E-auth_NO56K, AUTH:Connection speed=!UL;56K access not authorized - connection denied for '!AD'

Severity: ERROR
Explanation: User have not authorized high speed dial-in access.
User Action: Refer to RADIUS-VMS docs for using of 56K right id.

> RADIUS-E-auth_NOISDN, AUTH:Connection type=!UL;ISDN access not authorized - connection denied for '!AD'

Severity: ERROR
Explanation: User have not authorized high speed ISDN access.
User Action: Refer to RADIUS-VMS docs for using of ISDN right id.

> RADIUS-E-auth_DISAISDN, AUTH:Analog connection type=!UL denied for '!AD' with ISDN right id

Severity: ERROR
Explanation: User with ISDN right id can't use analog type of connection.
User Action: Refer to RADIUS-VMS docs for using of ISDN right id.

> RADIUS-E-auth_NOID, AUTH:Access to NAS !AC is not authorized by !AC;connection denied for '!AD'

Severity: ERROR
Explanation: ID showed in error message is required for access to showed NAS. These restrictions is configured in the RADIUS_CONFIG file.
User Action: None.

> RADIUS-E-auth_NOBYID, AUTH:Access to NAS !AC is rejected by !AC;connection denied for '!AD'

Severity: ERROR
Explanation: Presence of ID showed in message denied access for this user to the NAS.
User Action: None.

> RADIUS-E-auth_LIMRATE, AUTH:Connection rate with !UL is not allowed for '!AD'

Severity: ERROR
Explanation: None.
User Action: None.

> RADIUS-E-auth_NOACCREAL, AUTH:Login from realm '!AC' is not authorized by '!AC' for '!AD'

Severity: ERROR
Explanation: None.

> RADIUS-E-auth_NOBYACCREAL, AUTH:Login from realm '!AC' is rejected by '!AC' for '!AD'

Severity: ERROR
Explanation: None.
User Action: None.

> RADIUS-E-auth_UNKNREALM, AUTH:Unknown realm in '!AF',ignore request from !AC

Severity: ERROR
Explanation: In authentication request present realm suffix which is not defined in the RADIUS_CONFIG file. It's can be user's typos.
User Action: None.

> RADIUS-E-auth_ILLREALM, AUTH:Request for user '!AF' is rejected due to realm block for client '!AC'

Severity: ERROR
Explanation: In authentication request present realm suffix which is not allowed for the client with /ACCEPT_REALM or blocked with /REJECT_REALM.
User Action: None.

> RADIUS-I-auth_PWDCHNG, AUTH:Change password request for '!AF'@'!AC', CLID='!AD','!AD'

Severity: INFORMATIONAL
Explanation: A request contains a password change option.
User Action: None.

> RADIUS-E-proxy_NOSIG, PROXY:ACK/REJECT Packet from server '!AC' is ignored;no RADIUS-VMS PROXY-STATE attribute

Severity: ERROR
Explanation: RADIUS-VMS drop packets with missing of PROXY-STATE attrubutes which has been attached when request is forwarded to remote RADIUS server. Remote RADIUS server must be fully RFC-compliant.
User Action: Contact remote RADIUS support representative, performs additional testing in DEBUG mode.

> RADIUS-E-proxy_BADSIG, PROXY:ACK/REJECT Packet from server '!AC' is ignored;RADIUS-VMS PROXY-STATE attribute is not valid

Severity: ERROR
Explanation: RADIUS-VMS performs additional checking for validity of the packets comming from remote RADIUS server and drop invalid packets.
User Action: Contact remote RADIUS support representative, performs additional testing in DEBUG mode.

> RADIUS-E-proxy_INVAUTH, PROXY:Packet from server '!AC' (Id=!UB,Code=!UB) sent with invalid digest

Severity: ERROR
Explanation: RADIUS-VMS can't validate digest for packets arrived from remote RADIUS.
User Action: Check out shared secret key for the remote RADIUS server, contact remote RADIUS support representative.

> RADIUS-E-proxy_UNKNCLNT, PROXY:Packet for unknown client !AZ (!AZ,Id=!UB,Code=!UB), request ignored

Severity: ERROR
Explanation: RADIUS-VMS got&drop a packet for unknown client, hackers attack?
User Action: Investigate situation, contact RADIUS-VMS support staff.

> RADIUS-E-proxy_LOOP, PROXY:Can't forward packet from client !AC (Id=!UB,Code=!UB) to itself, request ignored

Severity: ERROR
Explanation: RADIUS-VMS prevent to loop packets to itself.
User Action: Check entries in the RADIUS_CONFIG file.

> RADIUS-W-proxy_FWDREQ, Forwarding REQuest (Id=!UB,Code=!UB,NAI='!AD',CLID='!AD') from !AC to !AC (Realm=!AC, LF=!SW)

Severity: WARNING
Explanation: RADIUS-VMS has resent a request to a subscriber's 'Home AAA', the 'Home AAA' has been matched by using realm 'domain' suffix or the CLID/IMSI prefix.
User Action: None.

> RADIUS-W-proxy_FWDANS, Forwarding ANSwer (Id=!UB,Code=!UB,NAI='!AD',CLID='!AD') from !AC (LF=!SW) to !AC

Severity: WARNING
Explanation: None.
User Action: None.

> RADIUS-F-conf_CNTREAD, CONF:Could not read file RADIUS_CONFIG, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS experienced an error during read from RADIUS_CONFIG file, investigate a reason by examination of status and stv codes, it's result of the RMS $GET calls.
User Action: Check access mode of custom programs to this file.

> RADIUS-F-conf_CNTOPEN, CONF:Could not open file RADIUS_CONFIG,status=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS could not open RADIUS_CONFIG file at startup time.
User Action: Investigate a reason by examination of status and stv codes, it's result of the RMS $OPEN calls. After corrections start RADIUS-VMS server.

> RADIUS-E-conf_NOCLNTENT, CONF:Server(s) with IP addr '!AZ' has been not defined as CLIENT,entry ignored

Severity: ERROR
Explanation: Destination remote host for forwared request is not defined as CLIENT.
User Action: Add CLIENT entry into the RADIUS_CONFIG file.

> RADIUS-E-conf_INVID, CONF:Can't translate !AC right id to binary format,status=%x!XL

Severity: ERROR
Explanation: Non-existen Right ID take place in RADIUS_CONFIG. An additional information can be obtained from status code, it's result of $ASCTOID system calls.
User Action: Ensure that this right id present in the RIGHTSLIST.DAT file by MCR AUTHORIZE SHOW /ID id. Add this right id into the RIGHTSLIST.DAT by MCR AUTHORIZE ADD/ID id, and start RADIUS-VMS server.

> RADIUS-E-conf_INVCLNM, CONF:Client IP name '!AZ' can't be resolved

Severity: ERROR
Explanation: RADIUS-VMS can't resolve IP name given in CLIENT entry.
User Action: Check IP name in the RADIUS_CONFIG file, check ability to resolve this name by NSLOOKUP utility, or replace IP name by IP address.

> RADIUS-E-conf_NOKEY, CONF:No secret key present for client '!AC'

Severity: ERROR
Explanation: CLIENT entry must containg shared secret to performs request processing from/to client.
User Action: Revise syntax, of CLIENT entries in the RADIUS_CONFIG file. Add /SECRET=quoted_string option to a CLIENT definition.

> RADIUS-E-conf_INVHOME, CONF:Invalid IP name/address for home '!AS'

Severity: ERROR
Explanation: RADIUS-VMS can't interpret a IP address or resolve IP name given in the HOME entry.
User Action: Check RADIUS_CONFIG file, correct problem.

> RADIUS-E-conf_INVDCIP, CONF:Domain Controller IP name '!AZ' can't be resolved

Severity: ERROR
Explanation: RADIUS-VMS can't resolve IP name given in DOMAIN entry.
User Action: Check IP name in the RADIUS_CONFIG file, check ability to resolve this name by NSLOOKUP utility, don't use an IP address notation because RADIUS server generation a NETBISO name by using the IP name.

> RADIUS-E-conf_INVINCL, CONF:INCLIDE directive is not allowed is in included file

Severity: ERROR
Explanation: INCLIDE directive is not allowed is in included file, configuration parser will skip this directive.
User Action: Find and remove INCLUDE directive, reorganize RADIUS's configuration files.

> RADIUS-E-dom_ERRCONN, DOM:Unable to connect to '!AC' DC,status=%x!XL.

Severity: ERROR
Explanation: RADIUS-VMS can't open TCP-connection to SMB server on the DC host defined in the RADIUS_CONFIG.
User Action: Contact remote DC support representative, performs additional testing in DEBUG mode.

> RADIUS-E-dom_REJSESSN, DOM:'!AC' DC rejected the session setup,status=%x!XL.!/SMB specific error = !AZ

Severity: ERROR
Explanation: RADIUS-VMS can't open session to SMB server on the DC host defined in the RADIUS_CONFIG.
User Action: Contact remote DC support representative, performs additional testing in DEBUG mode.

> RADIUS-E-dom_REJPROTNEG, DOM:'!AC' DC rejected the negotiate protocol,status=%x!XL.!/SMB specific error = !AZ

Severity: ERROR
Explanation: RADIUS-VMS can't negotiate a protocol to SMB server on the DC host defined in the RADIUS_CONFIG.
User Action: Contact remote DC support representative, performs additional testing in DEBUG mode.

> RADIUS-E-dom_REJSESSNST, DOM:'!AC' DC rejected the session setup,status=%x!XL.!/SMB specific error = !AZ

Severity: ERROR
Explanation: RADIUS-VMS can't negotiate a protocol to SMB server on the DC host defined in the RADIUS_CONFIG.
User Action: Contact remote DC support representative, performs additional testing in DEBUG mode.

> RADIUS-E-dom_ERRSEND, DOM:Error send a SMB message to '!AC' DC host,status=%x!XL

Severity: ERROR
Explanation: Error sending a packet to the DC.
User Action: Check matching NETBIOS name and Internet name of the DC without a internet domain suffix. For example DC internet full domainname - sysman.deltatel.ru NETBIOS name must be SYSMAN.

> RADIUS-I-loop_REQ, Sent REQuest (Code=!UB) ID #!UB to !AZ:!UW

Severity: INFORMATIONAL
Explanation:
User Action:

> RADIUS-I-loop_ANS, Received ANSwer (Code=!UB) ID #!UB from !AZ:!UW

Severity: INFORMATIONAL
Explanation:
User Action:

> RADIUS-E-loop_IPMATCH, IP (!AZ) server in response is not match IP in request (!AZ)

Severity: ERROR
Explanation:
User Action:

> RADIUS-E-loop_PORTMATCH, Got response from UDP Port (!UW), expected from UDP Port !UW

Severity: ERROR
Explanation:
User Action:

> RADIUS-E-loop_IDMATCH, Got response with ID #!UB, expected ID #!UB

Severity: ERROR
Explanation:
User Action:

> RADIUS-E-loop_TIMEOUT, Receive timeout (!%T)

Severity: ERROR
Explanation:
User Action:

> RADIUS-E-loop_DIGEST, Bad digest

Severity: ERROR
Explanation:
User Action:

> RADIUS-S-REQRECV, Got request ID #!UB, Code = !UB, from !AZ:!UW

Severity: SUCCESS

> RADIUS-S-REQSENT, Sent answer ID #!UB, Code = !UB, to !AZ:!UW

Severity: SUCCESS

> RADIUS-S-AUTHSTATUS, Request #!UB, Code = !UB, from !AZ:!UW, Username = !AD

Severity: SUCCESS

> RADIUS-F-db_OPEN, DB:Could not open RADIUS_DB file, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS's could not open RADIUS_DB file, investigate a reason by examination of status code, it's result of the RMS $OPEN/$CONNECT calls. RADIUS-VMS will continue work after this error.
User Action: Check an accessibility of the file pointed by RADIUS_DB logical.

> RADIUS-F-db_CLOSE, DB:Error closing RADIUS_DB file, status=%x!XL, stv=%x!XL

Severity: FATAL
Explanation: RADIUS-VMS's get error status duting closing RADIUS_DB file, investigate a reason by examination of status code, it's result of the RMS $CLOSE calls. RADIUS-VMS will continue work after this error.
User Action: Check an accessibility of the file pointed by RADIUS_DB logical.

> RADIUS-W-db_MISSPWD, DB:Password attribute is missing in entry at !AS:!UL, Username/NAI='!AC'

Severity: WARNING
Explanation: The Password attribute is missing in the user's entry.
User Action: Add the Password field into the entry.

> RADIUS-W-db_AUTHVMS, DB:SYSUAF flag is enforced for Username/NAI='!AC' (!AS:!UL)

Severity: WARNING
Explanation: If user's entry in the source file is contains Auth-Type = System and there is not Password attribute then SYSUAF flag will be set for user entry. It's meant that Authentication/Authorization will be performed against VMS SYSUAF. Only PAP can be used for VMS's SYSUAF accounts.
User Action: Add the Password field into the entry.

> RADIUS-E-db_SKIP, DB:Skip entry at !AS:!UL

Severity: ERROR
Explanation: None.
User Action: None.

> RADIUS-E-db_ERRPARSE, DB:Unable to parse Check/Reply-Items at !AS:!UL

Severity: ERROR
Explanation: RADIUS-VMS server can't parse Check/Reply-Item data from file in the RADIUS_USERS format during loading record from the plain-text file. It can be of result of typos in source file; also RADIUS_DICTIONARY file may not contains ATTRIBUTE entry for this Check/Reply-Item.
User Action: Check that all ATTRIBUTE(s) which are used in the RADIUS_USERS file has been defined in the RADIUS_DICTIONARY file. Also check case of ATTRIBUTE items in the RADIUS_USERS file. After any corrections you need to restart RADIUS-VMS server.

> RADIUS-E-db_CNTREAD, DB:Could not read !AS file, status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS experienced an error during read from RADIUS_USERS file, investigate a reason by examination of status and stv codes, it's result of the RMS calls.
User Action: Check access mode of the account running the RADUS-VMS.

> RADIUS-E-db_SAVE, DB:Could not write record for the '!AC', status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not update a record for the user in the RADIUS_DB file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $PUT calls.

> RADIUS-E-db_GET, DB:Could not get record for the '!AS' (at '!AS',CLID='!AD'), status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not find/get a record for the user in the RADIUS_DB file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $GET/$FIND calls.

> RADIUS-E-db_NILCLID, DB:Calling station id is missing in request for '!AS' (at '!AS')

Severity: ERROR
Explanation: RADIUS-VMS cannot performs an authentication of a request because the Calling-station-Id attribute is missing but required by RADDB$V_CLID entry's option.
User Action: Remove the RADDB$V_CLID from the entry record or check an originator of the request.

> RADIUS-E-db_UPD, DB:Could not update record for the '!AC', status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not update a record for the user in the RADIUS_DB file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $UPDATE calls.

> RADIUS-E-db_NOPWD, DB:Request for the '!AS' (at '!AS',CLID='!AD') no contains CHAP-Password

Severity: ERROR
Explanation: DB authentication cannot be performed without CHAP-Password.
User Action: Check for possible general network problem, or intruder/hacker attacks.

> RADIUS-E-db_DELT, DB:Could not delete record for the '!AC', status=%x!XL, stv=%x!XL

Severity: ERROR
Explanation: RADIUS-VMS could not delete a record for the user in the RADIUS_DB file. RADIUS-VMS will continue work after this error.
User Action: Investigate a reason by examination of status code, it's result of the RMS $DELETE calls.

> RADIUS-W-db_NOCBA12, DB:No MN ID(IMSI) has been configured for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: WARNING
Explanation: A Mobile Network Id (IMSI, MN ID) must be returned on successful authentication, this information should be stored in the profile as value of the Callback-Id attribute. An accept of the login will be sent.
User Action: Add a Callback-Id attribute & value pair into the user's profile.

> RADIUS-S-db_SUCCESS, DB:The subscriber '!AS' (at '!AS',CLID='!AD',REALM='!AC') has been authenticated

Severity: SUCCESS
Explanation: None.
User Action: None.

> RADIUS-S-db__LOAD, DB:!AS, !UL records, entries: total = !UL, skiped = !UL, stored = !UL

Severity: SUCCESS
Explanation: None.
User Action: None.

> RADIUS-S-db_ACCEPT, DB:Accept login for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: SUCCESS

> RADIUS-S-db_LOGGED, DB:'!AS' has been logged (at '!AS',CLID='!AD',REALM='!AC')

Severity: SUCCESS

> RADIUS-E-db_BADHOUR, DB:Login at this time has not been authorized for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: ERROR

> RADIUS-E-db_REJECT, DB:Reject login for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: ERROR

> RADIUS-E-db_INVPWD, DB:Wrong CHAP-Password in access-request for the '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: ERROR

> RADIUS-E-db_DISUSER, DB:The subscriber '!AS' (at '!AS',CLID='!AD',REALM='!AC') has been disabled

Severity: ERROR

> RADIUS-E-db_NOIROAM, DB:International Roaming has not allowed for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: ERROR

> RADIUS-E-db_NONROAM, DB:National Roaming has not allowed for '!AS' (at '!AS',CLID='!AD',REALM='!AC')

Severity: ERROR

> RADIUS-E-db_CHAPLEN, DB:Request for the '!AS' (at '!AS') contains invalid CHAP-Password length(!UL)

Severity: ERROR
Explanation: RADIUS-VMS checked that CHAP-Password length is invalid, RADIUS-VMS will continue work after this error.
User Action: Check for possible general network problem, or intruder/hacker attacks.

Previous | Next | Contents