VCS Error Codes for all platforms
You would hope that one error code can't mean different things on different platforms, but the reverse is not true - i.e the same error condition can have different codes on different platforms and in fact if you look at /opt/VRTSvcs/bin/ag_i18n_inc.sh you see:
case ${SYSTEM} inAIX)VCS_LOG_CATEGORY=10011;;HP-UX)VCS_LOG_CATEGORY=10021;;Linux)VCS_LOG_CATEGORY=10031;;SunOS)PATH=/usr/xpg4/bin:$PATH; # for correct grepVCS_LOG_CATEGORY=10001;;esacAnd therefore for example if you search for "No disk group name specified in the resource" at https://sort.symantec.com/ecls you get:UMI Message Severity Component V-16-10011-9503 No disk group name specified in the resource definition... n/a Veritas Cluster Server V-16-10001-11504 No disk group name specified in the resource definition... n/a Veritas Cluster Server V-16-10031-12511 No disk group name specified in the resource definition... n/a Veritas Cluster Server Note not only is VCS_LOG_CATEGORY different, but the last part of the code is different in all cases and there is no match for HP-ux, so HP-ux may not have this error code, or it might use different wording.I have had several customers ask for a list of codes and I was never able to get this list. Clearly this list exists (even if not complete) at https://sort.symantec.com/ecls, but it seems you can only get 100 codes at a time and there is not even a "next" to list the next 100 codes, so I guess there is no way for an end user to get a list of codes held at https://sort.symantec.com/ecls and even if you could it would require a lot of work to correlate all the different error codes as for instance if you search for "No disk group specified" at https://sort.symantec.com/ecls you get:UMI Message Severity Component V-16-10031-1531 No disk group specified. n/a Veritas Cluster Server V-16-10011-916 No disk group specified n/a Veritas Cluster Server So I would guess this means the same thing and if I search for "No disk group" in /opt/VRTSvcs/bin/DiskGroup on VCS 5.1 on Linux then I get:# grep "No disk group" *monitor: VCSAG_LOG_MSG "E" "No disk group specified." 1531So this looks at I ONLY have error code V-16-10031-1531 on VCS 5.1 on Linux so it maybe that you get error code V-16-10031-12511 on another version of VCS on Linux.MikeHi All,
The UMI message IDs would be different for VCS bundled agents on various platforms for a given message as Mike said. The Category ID is different on each platform for bundled agents and for each category ID the message numbers starts from 1.
Message format: V-<ProductID>-<CategoryID>-<MessageID>.
While the UMI would be different on each platform for a message, it is guranteed that the UMI code remains same for a message across VCS releases.
For example, if a message "xyz" has a UMI V-16-10001-1 in VCS 5.1 release on Solaris, the message UMI for the message would remain as V-16-10001-1 in VCS 6.0 release. If any change made to the message "xyz" say "xyzw" then a different UMI would be used.
Thanks,
Venkat
