Avamar: Proxy Status "Unknown" When Proxy Hostname Contains an Underscore
Summary: In the Avamar HTML5 Administrator UI, the Proxy Status section under Proxy Management may display a status of "Unknown" for certain proxies. Despite this status, the proxy continues to function correctly, accepting backup and restore jobs. The Avamar server can also communicate with the proxy on all required TCP ports. ...
Symptoms
-
One or more proxies show a status of "Unknown" in the UI.
-
Proxy status updates using Proxy Deployment Manager (PDM) fail during the
getProxyStatusoperation.
Error Details
In the PDM log file (/usr/local/avamar/var/log/vcs/deploymanager.log) on the Avamar server, the following error is shown:
<date> ERROR [:1-8543-exec-10][impl.ProxyService# getProxyStatus]: getProxyStatus:
java.rmi.RemoteException: WBEMException; nested exception is:
WBEMException: CIM_ERR_INVALID_PARAMETER (Malformed URI)
at com.emc.avamar.vmware.cimsdk.cim.SblimCIMProxyMgmtConnection.login(SblimCIMProxyMgmtConnection.java:79)
Cause
This issue occurs when the proxy's hostname contains an underscore (_). According to Request For Comment (RFC) 1035, underscores are not valid characters in Domain Name System (DNS) hostnames.
The Proxy Status feature uses Java-based CIM/WBEM libraries that enforce strict Uniform Resource Identifier(URI) validation. Hostnames with underscores are treated as malformed, resulting in the CIM_ERR_INVALID_PARAMETER error.
Example:
-
❌
proxy_idpa_01.example.com- Not allowed -
✅
proxy-idpa-01.example.com- Allowed
Resolution
To resolve this issue, redeploy the affected proxy using a hostname that does not contain an underscore. Use hyphens (-) instead of underscores to ensure compatibility with DNS standards.
Additional Information
For similar issue with Proxy Status see Avamar: Proxy Management Proxy Status ERROR: "Proxy is unreachable. Check the network settings"