This content has been marked as final. Show 6 replies
While I have never seen that specific error, I do have a couple questions.
1. What version of Linux?
2. Have you set a separate DNS name for the second interface IP? You probably should.
3. Do you still have a single default route or are you trying to use more than one?
I run 5 nics on my VM Manager. All on different subnets. I suspect the VM Manager is getting confused when it comes to identify its hostname and the various connections the host has.
Thank you for your support!
1. What version of Linux? OL 62 x64
2. Have you set a separate DNS name for the second interface IP? No, although we are using/setup dnsmasq on the second interface/eth3 to dish up DNS on the private network. DNS name resolutions works like a charm on the private vlan.
3. Do you still have a single default route or are you trying to use more than one? The second interface is in a private unroutable network. the front end network/NIC eth0 is routable and on a public network.
Public/Private Network Setup:
* Public network with oracle vm manager on eth0/10.4.x.x. This is how we access the ovm manager GUI, and ssh to manager, and via manager ssh to the dom0s. The dom0s are on private nonroutable networks available via the manager host's eth3.
* Private networks accessible via the oracle vm manager host eth3/802.1q/VLAN xxx. this is the server management network channel, this vlan is not routable. We have two other vlans, i.e. heartbeat and live migration, both also not routable.
Check out this document.
I think you're looking for section 4.4 thru 4.4.2
I would at least try adding a different host name of the nic you added. Add an entry to hosts file for the IP and then vi the if-eth# nic you added and add a entry
Then do a "service network restart".
You want to get rid of the conflict, you probably don't care about actually making weblogic accessible on the new nic. Hope this helps.
Thank you for your support!
We did try http://docs.oracle.com/cd/E29505_01/doc.1111/e13806/network.htm#i1078331, no love.
We discovered that adding interfaces post oracle vm manager installations generate the "A port conflict was detected in the server config" errors/condition. O support was unable to provide a fix. We uninstalled oracle vm manager, did a UUID reinstall, and the A port conflict was detected in the server config" error was gone.
thank you again for your support!
I also had this problem, but the reason was that I had two virtual eth adapters (eth1.1 and eth1.2). IPV6 generates the same link local adres for both interfaces (based on MAC of physical adapter) and then weblogic / ovm manager wouldnt start. I removed the double ipv6 adres from the adapter and all works.
You should spot double ipv6 adresses with ifconfig -a on the host, do you have any virtual adapters configured?
Thank you for your assistance!
We do have a virtual 802.1q interface on one of the two active interfaces, i.e. eth0/access port, eth3/802.1q VLAN.