If you are having issues logging into avamar and you see the following message “com.avamar.asn.NetworkException: Unable to connect to a login server” then the issue is usually environmental. Avamar 5.x relies heavily on DNS and improperly configured DNS will cause this issue. If you are using windows AD for DNS, then make sure that DNS records are setup in the same domain as the domain that Avamar was setup in. If they are and still having this issue, remove duplicate avamar records from subdomains. This should resolve your issue. If the DNS server is unix/linux based case sensitivity is usually the culperate.

Incoming search terms:

• avamar gsan degraded
• gsan status degraded
• com avamar asn networkexception
• avamar garbage collection not running
• gsan status: degraded
• gsan degraded
• dpnctl: INFO: Maintenance windows scheduler status: suspended
• avamar hfs check
• dpnctl: INFO: gsan status: not running
• com avamar asn networkexception: Unable to connect to a login server