- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Rolling out vSphere Rep in 2 sites.
Running 6.5 up1 vSphere/ESXi
Installing 6.5.1 vSphere Replication
Site 1 (Main DC) Deployed OVF, VRep appliance installed without any issues.
Site 2 (DR Site) Used the same OVF as Site 1, when the appliance starts up, getting error No Networking detected. I have ran the command, but it will still not allow me to configure the network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So once you run this command, you don't get the menu?
/opt/vmware/share/vami/vami_config_net
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can run the cmd, it allows me to manually set the network info, but it gives an error when setting an IP to eth0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try clearing the contents of this file using VI (take a copy), then reboot.
/etc/udev/rules.d/70-persistent-net.rules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm getting no such file or directory when trying to rum the cmd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you happen to deploy from the thick client?
# Suhas
Don't Backup. Go Forward!
Rubrik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you run a LS command and screen shot it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Don't know what you mean by "thick client" Used the vSphere Web Client to import the OVF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
LS CMD
* just to make sure, I ran /etc/udev/rules.d/70-persistent-net.rules on the other vrep appliance (DC side) that file does not show up either and this one configured without any issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
even i am facing same issue, kindly advice if your issue resolved.@
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
had the same issue with one of the replication appliance deployments. turned out the IP address was already in use by one other VM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
will check it thank you, any other advise to check.@
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Console to VRMS and login.
Get the interface names with:
/opt/vmware/share/vami/vami_interfaces
Set the IP for the desired interface with:
/opt/vmware/share/vami/vami_set_network <interface name> STATICV4 <IP Address> <NETMASK> <GATEWAY>
Set DNS with:
/opt/vmware/share/vami/vami_set_dns -d <domain suffix> <DNS IP1> <DNS IP2>
REBOOT
Resolved the issue for me on vSphere Replication 8.4. Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you for the manual IP settings. I have deployed two replication appliances and both needed this configuration change.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot, The Manual IP settings Works Perfect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had to do this same thing again after upgrading two 8.4 appliances to the 8.5 release. One appliance worked and one failed with network config issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Think I might have found the issue. After deploying the appliance, and before starting it, please have a look at configure --> "vApp options" on the VM. If you press EDIT and check the options, the IP allocation scheme should be OVF environment. So none of the options in the template regarding to IP setting will be applied if left unchecked.
And its nice to know the commands for manually adjusting them but it should not be necessary after changing this setting. Poorly tested OVA template... shame on you VMware.