Hi Forum buddies,
Situation
File Server (Virtual, Windows 2012 R2 Core) with 3 IP addresses - PROD (IP, Mask, GW, DNS) STORAGE (IP and MASK Only) BACKUP (IP and MASK Only). Binding order is PROD, Storage, Backup.
Cloud Agent is installed and working, running the latest version.
The asset always lists the Storage IP as its IP Address. We use tags quite a lot and the IP Range for the Storage consists of only 4 devices which talk direct to a storage device. No other means of access. None of the devices within this network have gateways or DNS. I'm a little confused as to why it's not showing the PROD IP as its identifying IP address. All other servers with multiple IP's (Hyper-V Hosts for example) list the PROD Address (Though they are GUI Versions as opposed to Core).
I set the binding order using a Powershell script and have also uninstalled and reinstalled the agent a few times (This is part of a test lab so I have carte blanche to do "Stuff").
Anyone got any idea's or thoughts on this?
Presumably this has got something to do with where the cloud agent is actually installed and invoked from on this host?
Being the agent is a file based solution it sort of makes sence to me that it would find the storage IP if it was indeed installed on a SAN or NAS distributed storage cluster.
Have you tried adding the asset by IP rather than using the cloud agent, the results may show more.
Regards,
Dan