Unsolved
This post is more than 5 years old
2 Posts
0
2750
December 1st, 2016 11:00
Avamar dedicated network for management
Hello,
I am just in the middle of Avamar implementation project ( Single Node Gen4T M1200 + DataDomain ) and one of customer's requirment is to isolate mgmt trafic from backup.
I have configured networks as described in documentation: there is dedicated BMC interface, bond0 (eth1 and eth2) and eth5 for management purpose. MGMT address on eth5 was configured in Avamar Installation Manager.
Unfortunately when trying connect with Avamar Administrator to mgmt ip it is immposible: "connection refused" even when network communication is ok. In same time Avamar Adminsitrator connect to Mgmt server using bond0 Ip, which was intended to backup trafic only.
It seems that Management Server is "binded" only to one address. In probe.xml there two interfaces:
bond0: backup,replication,management
eth5: management
Problem is that eth5 is completlly useless.
Do You have some real experience with dedicated mgmt network in Avamar ?
Please share, I have no idea what I am doing wrong
Jsvebeck
10 Posts
0
December 5th, 2016 01:00
Hi Ernest,
Probably a DNS problem. We created a separate DNS-record for the management interface for the clients to contact for management purposes. In some cases we had to use the hostfile on the backupserver som it knows what interface to use when it contacts a certain adress.
Jsvebeck
10 Posts
0
December 7th, 2016 05:00
Any luck?
ernest.lojan
2 Posts
0
December 7th, 2016 11:00
Sorry for delay..I am in the middle of battle
It seems that there are few reasons
- routing problem for avamar OS: it is strange but communication to mgmt network from avamar box is working but I have problem to get from outside to avamar box
- I got some guide how set up dedicated mgmt network from support team, and it seems that I have to add this mgmt address as rmi_address in mcserver.xml file. At this moment it production system so not really I can do some tests etc with config.
- I agree that last task would be DNS stuff
Honestlly, I think that for server mgmt more usefull is dedicated RMC port: remote console, power management etc...
Jsvebeck
10 Posts
0
December 13th, 2016 00:00
Hi,
No problem, just curious. Yes, correct the management address is supposed to be the RMI-address.
What I meant with DNS problem is that the Avamar server uses a DNS server on the backup interface, so when it wants to talk mgmt it asks the DNS-server on the backup interface. So the DNS and the hostfile got to work together. =)