User guide

Known problems and limitations
EMC Avamar 7.0 Release Notes 37
Avamar Client Manager
The following table lists known problems for this release of Avamar Client Manager.
Avamar Administrator
The following table lists known problems for this release of Avamar Administrator.
Table 7 Avamar Client Manager known problems
ID Description
48138 Avamar Client Manager cannot manage clients of Avamar servers that have the
additional firewall hardening feature installed
When you install the firewall hardening feature on an Avamar server, the firewall blocks
an Avamar server port that must be open for full functionality of Avamar Client
Manager.
The
EMC Avamar Product Security Guide describes a workaround for this problem.
45872
49451
Avamar Client Manager cannot activate more than one batch of 1,000 clients
This problem occurs when Avamar Client Manager is used to activate several batches
of 1,000 clients each. The first batch of clients activate successfully, but subsequent
batches are queued with a connection exception.
The root cause of the problem is an overflow in the ARP cache of the Avamar server
associated with the clients. The problem occurs on both RHEL and SLES servers, and
the workaround is the same on both.
To work around this problem, complete the following steps to increase the ARP cache
size before using Avamar Client Manager to activate clients on an Avamar server:
1. Follow the procedure for logging in as root on the Avamar server associated with the
clients.
2. Type the following command with no line break:
echo "net.ipv4.neigh.default.gc_thresh1=1024" >>
/etc/sysctl.conf
3. Type the following command with no line break:
echo "net.ipv4.neigh.default.gc_thresh2=2048" >>
/etc/sysctl.conf
4. Type the following command with no line break:
echo "net.ipv4.neigh.default.gc_thresh3=4096" >>
/etc/sysctl.conf
5. Type the following command:
sysctl –p
Table 8 Avamar Administrator known problems
ID Description
1078 Jobs do not appear in the Activity Monitor after server restart
If you stop and then restart the administrator server, then jobs that started before the
administrator server stop do not appear in the Activity Monitor.
6781 Client name change impacts license quota
If you rename a client, the old name of the client remains for activities reporting data
for the client. Avamar treats new activities for the same client as if they were for a new
client, leading to double counting the number of bytes protected for licensing
purposes. If a client name change is required, consult EMC Customer Service to ensure
that the database is correctly updated.