Registering a client after creating vLans

Avamar 7.3 integrated with vCenter 5.5 and DDOS 5.7

Avamar configured with one bonded (eth0 & eth2) interface for data, repl, mgmt. and internal. Multiple vlans then created on top of the physical, each vlan representing a different tenant with their own ip.When now trying to register a client residing within one the vlan networks I am getting failed to register issues/errors.

Types of errors I am seeing are:

Error trying to update MCS with new ip address

Unable to securely register with the MCS
MCS unknown, entering listen mode

Certificate could not be verifed

The above are from the avagent.log on the client and in no particular order

I think it might be one of two things:

1) The MCS is registered to the physical bonded interface call it 1.2.3.4, and we are trying to register the client on the vlan ip address 5.6.7.8 - not sure but........

2) Or could it be due to the fact that the Avamar self-signed cert was created when we installed the Avamar s/w - at that point we did not have the vlans configured and therefore the cert is looking for the physical bonded interface (SAN list) and we are trying to register with the vlan ip address so the registration is failing with cert errors. We are onsidering trying generate a new self-signed cert but my experience of messing around with certs means I do not think that will end particularly well.

I really don't know and maybe completely clutching at straws but.......................any info/advice/feedback/experience greatly received.

Neil