Network Management lost, No Nic display Consol
-
Good evening Legends.
Im Truly sorry, but im in need of some assistance, Minor, Major mess i made.
After an emergency Network Reset i am unable to see any NICS displayed in on the XE Console, Going into the shell i can see the Network cards are there using ip a and ifconfig -a
if i ip link set <Interface> up. It comes up and im able to assign an IP to this interface, this then also allows me to Ping another hypervisor Host within the same subnet.
Yet still no Management interface and no Nics to display in the console.
i have attempted to do the xe-management-reconfiguration uuid. and it just keeps stating that it cannot get an IP from the Master.
This has me truly stumped and i have no idea where to start looking, i had done toolstack restart, I had confirmed XAPI is active on the system yet still not able to create a management interface to assign it back to the system pool.
What would i have to do.
-
@FMOTrust Hey, I think I also am suffering from the same issue that you do. Could you please verify that you have the same issue as me? https://xcp-ng.org/forum/topic/10687/after-an-update-the-nic-s-has-disappeared-but-still-works-somehow?_=1743438466779
It might be a bug or something wrong with an update?
-
@FMOTrust I had this issue as well on a Slave host in my test environment. I was able to do Network Reset from xsconsole, but then after the Host rebooted to finish the reset, the Host reverted back to not having/seeing the Mgmt network, and...like you, I couldn't see any NICs either.
Since this was for testing, and I had no VMs on it, I just reinstalled XCP. I think there's a way to reset XCP I saw in another Forums post by removing the Local SR? Olivier shared that in the post..but I don't remember what post it was.
Not sure if this is a test or prod Host/environment for you...but if you can, unless someone from the Vates team comments, I think all that can be done is reinstall.
-
I know this is old, but I also had this issue. I updated my pool from 8.2.1 to 8.3 using the installer ISO. Both hosts came back up, I did an update on the pool master and then the slave, and now the slave has lost its network interfaces. In ifconfig, I see eth0, lo, and xenbro with no IP, along with a "xentemp" which has the IP address I assigned the management address. I did an xe-toolstack-restart and emergency network reset, which did not seem to help. xe pif-list, network-list and all other xe commands simply hang forever.
-
This is a classic issue with XAPI, once you have hosts in a pool and the slave cannot reach the master it will go crazy. Never seen this issue with standalone hosts tho.
We usually had this issue when upgrading xenserver, so we simply stopped doing that and then never had any issues. We went to "new" versions by simply standing up a new pool and migrate all the vm's over to it
-
@nikade Can you elaborate on that more for us? Do you create a new pool with existing host? if so how? or do you pull a host make new pool from that host and migrate the rest over?
-
@acebmxer It's not pretty, but its failsafe. The proceedure looked like this in our case:
- Disable HA in the "old pool"
- Put a host in the "old pool" into maintenance mode
- Reinstall that host and connect it to XOA and then patch it
- Create a "new pool" from that host
- Create a new LUN or NFS share in the SAN for "new pool" and attach it to "new pool"
- Live migrate VM's over from "old pool" to "new pool"
- Once you've freed up another host you repeate step 2 and 3 and then join that host to "new pool". It is important that you patch it before joining it to the pool, that is done by going to Settings -> Servers in XOA and connect to it manually.
And then just continue untill you're done. Live migration is pretty reliable now days, so this works pretty good and since we had 10G network its not taking as long as it used to do with 1G network.
We did this after a major incident on our primary production site where 2 out of 4 hosts in a pool "suddenly" lost their NIC's after updating them. Since then we never updated the pools again. Standalone hosts are fine tho, they never did this.Luckily we had 2 other pools where we could migrate the VM's to, but we couldn't realy trust the updating after that.
