I apologize for asking what is probably a very basic question. I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network. I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ? Thanks in advance, Valerio
It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly, which can cause a bad route. Look at differences between the engine's network config (presuming it can reach outside the hypervisor host) and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM, if its connected to ovirtmgmt. "ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections. On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu> wrote:
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance, Valerio _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DW...
That was my first thought, so I tried to set up manually the default route and netmask on the VM to match the engine's, but it didn't solve the problem. Another network question: I have a second network card on the host that is connected to an internal switch, how do I add a bridge for that card to be used by the VMs ? I created a secondary bridge on the host and then I tried to play with the network options on the oVirt portal, but I couldn't figure out to associate the new bridge with an new network. Before anyone thinks that the two issues are related, I did this after failing to solve the first issue. On 9/10/20 8:00 AM, Edward Berger wrote:
It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly, which can cause a bad route.
Look at differences between the engine's network config (presuming it can reach outside the hypervisor host) and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM, if its connected to ovirtmgmt.
"ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections.
On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu <mailto:valerio.luccio@nyu.edu>> wrote:
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance, Valerio _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=FkCDYQbRRKw0YQpvSYfeiiVvAwXj5RhU9WtVkK04TuM&e=> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=F3bb60_z8-7_2gSPhwfklz-rVUmXJiokypfqBR8CF4M&e=> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DW... <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=MerUtEwXMg4sXTJtJTMg2r-0bdlzNIOolYwCmfEFF1U&e=>
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
The usual process to add another network bridge is to configure a new cluster logical network in the engine, then configure specific network interfaces on all hypervisors through the engine's "configure host networks". On Thu, Sep 10, 2020 at 11:43 AM Valerio Luccio <valerio.luccio@nyu.edu> wrote:
That was my first thought, so I tried to set up manually the default route and netmask on the VM to match the engine's, but it didn't solve the problem.
Another network question: I have a second network card on the host that is connected to an internal switch, how do I add a bridge for that card to be used by the VMs ? I created a secondary bridge on the host and then I tried to play with the network options on the oVirt portal, but I couldn't figure out to associate the new bridge with an new network. Before anyone thinks that the two issues are related, I did this after failing to solve the first issue.
On 9/10/20 8:00 AM, Edward Berger wrote:
It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly, which can cause a bad route.
Look at differences between the engine's network config (presuming it can reach outside the hypervisor host) and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM, if its connected to ovirtmgmt.
"ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections.
On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu> wrote:
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance, Valerio _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=FkCDYQbRRKw0YQpvSYfeiiVvAwXj5RhU9WtVkK04TuM&e=> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=F3bb60_z8-7_2gSPhwfklz-rVUmXJiokypfqBR8CF4M&e=> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DW... <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=MerUtEwXMg4sXTJtJTMg2r-0bdlzNIOolYwCmfEFF1U&e=>
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.
For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
Understood, but how ? I'm using the oVirt Visualization Manager 4.4. I see a "Network" tab where I can create a new network and a new vNIC profile, but a) I don't see how I associate the new network with the bridge I created and b) if I try to add this new network to my VM I get a message that says that the network does not exist on the host (which makes sense since the network I created is not connected to anything). I must say that all the examples I found online use a GUI that looks quite different from the one I have. Is there a separate GUI I should be running ? On 9/10/20 1:25 PM, Edward Berger wrote:
The usual process to add another network bridge is to configure a new cluster logical network in the engine, then configure specific network interfaces on all hypervisors through the engine's "configure host networks".
On Thu, Sep 10, 2020 at 11:43 AM Valerio Luccio <valerio.luccio@nyu.edu <mailto:valerio.luccio@nyu.edu>> wrote:
That was my first thought, so I tried to set up manually the default route and netmask on the VM to match the engine's, but it didn't solve the problem.
Another network question: I have a second network card on the host that is connected to an internal switch, how do I add a bridge for that card to be used by the VMs ? I created a secondary bridge on the host and then I tried to play with the network options on the oVirt portal, but I couldn't figure out to associate the new bridge with an new network. Before anyone thinks that the two issues are related, I did this after failing to solve the first issue.
On 9/10/20 8:00 AM, Edward Berger wrote:
It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly, which can cause a bad route.
Look at differences between the engine's network config (presuming it can reach outside the hypervisor host) and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM, if its connected to ovirtmgmt.
"ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections.
On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu <mailto:valerio.luccio@nyu.edu>> wrote:
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance, Valerio _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=FkCDYQbRRKw0YQpvSYfeiiVvAwXj5RhU9WtVkK04TuM&e=> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=F3bb60_z8-7_2gSPhwfklz-rVUmXJiokypfqBR8CF4M&e=> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DW... <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=MerUtEwXMg4sXTJtJTMg2r-0bdlzNIOolYwCmfEFF1U&e=>
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu <mailto:keith.sanzenbach@nyu.edu> and/or Pablo Velasco at pablo.velasco@nyu.edu <mailto:pablo.velasco@nyu.edu> For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu <mailto:valerio.luccio@nyu.edu> For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu <mailto:chrysa@nyu.edu> For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu <mailto:jennifer.mangan@nyu.edu>
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
On Fri, Sep 11, 2020 at 12:04 AM Valerio Luccio <valerio.luccio@nyu.edu> wrote:
Understood, but how ? I'm using the oVirt Visualization Manager 4.4. I see a "Network" tab where I can create a new network and a new vNIC profile, but a) I don't see how I associate the new network with the bridge I created
After adding the host to oVirt Engine, please avoid touching the network configuration of the host manually, oVirt will take care of the host's network configuration. Please remove the manually created bridge and open the oVirt Administration Portal in a browser and browse to Compute > Hosts > HOSTNAME > Network Interfaces, open the "Setup Host Networks" dialog and assign the logical network to the NIC. Did this work for you?
and b) if I try to add this new network to my VM I get a message that says that the network does not exist on the host (which makes sense since the network I created is not connected to anything).
I must say that all the examples I found online use a GUI that looks quite different from the one I have. Is there a separate GUI I should be running ?
On 9/10/20 1:25 PM, Edward Berger wrote:
The usual process to add another network bridge is to configure a new cluster logical network in the engine, then configure specific network interfaces on all hypervisors through the engine's "configure host networks".
On Thu, Sep 10, 2020 at 11:43 AM Valerio Luccio <valerio.luccio@nyu.edu> wrote:
That was my first thought, so I tried to set up manually the default route and netmask on the VM to match the engine's, but it didn't solve the problem.
Another network question: I have a second network card on the host that is connected to an internal switch, how do I add a bridge for that card to be used by the VMs ? I created a secondary bridge on the host and then I tried to play with the network options on the oVirt portal, but I couldn't figure out to associate the new bridge with an new network. Before anyone thinks that the two issues are related, I did this after failing to solve the first issue.
On 9/10/20 8:00 AM, Edward Berger wrote:
It sounds like you don't have a proper default route on the VM or the netmask is set incorrectly, which can cause a bad route.
Look at differences between the engine's network config (presuming it can reach outside the hypervisor host) and the VM's config. The VM should have the same subnet, netmask and default gateway as the engine VM, if its connected to ovirtmgmt.
"ip a" "ip r" "traceroute" and "ping" are the usual commands to check network connections.
On Thu, Sep 10, 2020 at 6:29 AM <valerio.luccio@nyu.edu> wrote:
I apologize for asking what is probably a very basic question.
I installed and created a self-hosted engine using cockpit on a server. I can reach the self-hosted engine from anywhere within my network.
I then created a new VM selecting the default ovirtmgmt for the network. The VM does not seem to connect to the network via the bridge. I the used the console to manually configured the network card and I have connectivity between the VM, the engine and the server, but not beyond. What am I doing wrong ? Can someone point to a good documentation page on the subject ?
Thanks in advance, Valerio _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_privacy-2Dpolicy.html&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=FkCDYQbRRKw0YQpvSYfeiiVvAwXj5RhU9WtVkK04TuM&e=> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_community_about_community-2Dguidelines_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=F3bb60_z8-7_2gSPhwfklz-rVUmXJiokypfqBR8CF4M&e=> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IFXOOU4DVR66DW... <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archives_list_users-40ovirt.org_message_IFXOOU4DVR66DWEUCR66CJ2LQFUFCN55_&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=zZK0dca4HNf-XwnAN9ais1C3ncS0n2x39pF7yr-muHY&m=09a69sjdPT4FnBs3SqcX_DdQWZ4bl9fBgaX-ncTrSLY&s=MerUtEwXMg4sXTJtJTMg2r-0bdlzNIOolYwCmfEFF1U&e=>
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.
For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.
For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
OK, got the network to my internal switch working (thanks Edward), but still no luck with the university backbone. One thing I did notice, which is different from my engine, is that the VM has defined the network interface virbr0 with static ip 192.168.122.1/26, which might be a problem since these machine are hooked to an internal network that is also 192.168 (192.168.122.1 is the IP of one of the gateways) and the IP of this VM is 192.168.39.87. The questions are: what is virbr0 for, should I change the IP, to what ? Here's some output, if it helps (the 10.20.30 network is my internal switch): $ ifconfig enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.39.87 netmask 255.255.255.192 broadcast 192.168.39.127 inet6 fe80::56a3:9c14:ce9:84e4 prefixlen 64 scopeid 0x20<link> ether 56:6f:41:2d:00:00 txqueuelen 1000 (Ethernet) RX packets 8002 bytes 541580 (528.8 KiB) RX errors 0 dropped 6 overruns 0 frame 0 TX packets 797 bytes 37166 (36.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.20.30.161 netmask 255.255.255.192 broadcast 10.20.30.191 inet6 fe80::5d02:5880:5073:7fdd prefixlen 64 scopeid 0x20<link> ether 56:6f:41:2d:00:03 txqueuelen 1000 (Ethernet) RX packets 2347 bytes 373160 (364.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 50 bytes 5422 (5.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1132 bytes 111424 (108.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1132 bytes 111424 (108.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:38:03:68 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.39.65 0.0.0.0 UG 100 0 0 enp1s0 10.20.30.128 0.0.0.0 255.255.255.192 U 101 0 0 enp7s0 192.168.39.64 0.0.0.0 255.255.255.192 U 100 0 0 enp1s0 192.168.122.0 0.0.0.0 255.255.255.0 U 425 0 0 virbr0 Thanks
Most probably you got libvirtd.service running (if the output is from a VM). Just disable it via 'systemctl disable --now libvirtd.service' and to verify that after reboot everything will be fine -> reboot the VM. Best Regards, Strahil Nikolov В петък, 11 септември 2020 г., 18:35:33 Гринуич+3, valerio.luccio@nyu.edu <valerio.luccio@nyu.edu> написа: OK, got the network to my internal switch working (thanks Edward), but still no luck with the university backbone. One thing I did notice, which is different from my engine, is that the VM has defined the network interface virbr0 with static ip 192.168.122.1/26, which might be a problem since these machine are hooked to an internal network that is also 192.168 (192.168.122.1 is the IP of one of the gateways) and the IP of this VM is 192.168.39.87. The questions are: what is virbr0 for, should I change the IP, to what ? Here's some output, if it helps (the 10.20.30 network is my internal switch): $ ifconfig enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.39.87 netmask 255.255.255.192 broadcast 192.168.39.127 inet6 fe80::56a3:9c14:ce9:84e4 prefixlen 64 scopeid 0x20<link> ether 56:6f:41:2d:00:00 txqueuelen 1000 (Ethernet) RX packets 8002 bytes 541580 (528.8 KiB) RX errors 0 dropped 6 overruns 0 frame 0 TX packets 797 bytes 37166 (36.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp7s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.20.30.161 netmask 255.255.255.192 broadcast 10.20.30.191 inet6 fe80::5d02:5880:5073:7fdd prefixlen 64 scopeid 0x20<link> ether 56:6f:41:2d:00:03 txqueuelen 1000 (Ethernet) RX packets 2347 bytes 373160 (364.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 50 bytes 5422 (5.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1132 bytes 111424 (108.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1132 bytes 111424 (108.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:38:03:68 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.39.65 0.0.0.0 UG 100 0 0 enp1s0 10.20.30.128 0.0.0.0 255.255.255.192 U 101 0 0 enp7s0 192.168.39.64 0.0.0.0 255.255.255.192 U 100 0 0 enp1s0 192.168.122.0 0.0.0.0 255.255.255.0 U 425 0 0 virbr0 Thanks _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
Thanks to all that gave me hints/suggestions, especially to Edward that pointed me to the right setup page. I was able to set up correctly my internal switch network, but I'm still having issues with the virtual network that connects to the university backbone. The route on the VM is setup just like on the host and the engine. I also tested traceroute and found out something puzzling: 1. traceroute on the host and the engine for any node on the university network returns the answer in milliseconds. 2. traceroute on the VM for a node on my internal switch returns the answer in milliseconds with the flag. 3. traceroute on the VM for the host or the engine returns answer after more than 10 seconds with the flag !X 4. traceroute on the VM for other hosts on the network returns the flag !H (host not reachable). According to the traceroute man pages the !X flag indicates "communication administratively prohibited". I temporarily turned off the firewall on the host and the engine and that removed the !X flag from 3, but did not speed it up and did not solve 4. Anyone have any clue what I should try next ? Thanks in advance, -- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
For others having issues with VM network routing... virbr0 is usually installed by default on centos, etc. to facilitate containers networking via NAT. If I'm not planning on running any containers I usually yum remove the associated packages, and a reboot to make sure networking is OK. Sometimes the ipv4 autoconfig stuff also gets in the way of desired routing, and I add NOZEROCONF=yes to /etc/sysconfig/network to disable it. When I've seen the !X in traceroutes it has usually been a firewall config issue on the remote host I'm tracing to. On Mon, Sep 14, 2020 at 11:50 AM Valerio Luccio <valerio.luccio@nyu.edu> wrote:
Thanks to all that gave me hints/suggestions, especially to Edward that pointed me to the right setup page.
I was able to set up correctly my internal switch network, but I'm still having issues with the virtual network that connects to the university backbone. The route on the VM is setup just like on the host and the engine. I also tested traceroute and found out something puzzling:
1. traceroute on the host and the engine for any node on the university network returns the answer in milliseconds. 2. traceroute on the VM for a node on my internal switch returns the answer in milliseconds with the flag. 3. traceroute on the VM for the host or the engine returns answer after more than 10 seconds with the flag !X 4. traceroute on the VM for other hosts on the network returns the flag !H (host not reachable).
According to the traceroute man pages the !X flag indicates "communication administratively prohibited". I temporarily turned off the firewall on the host and the engine and that removed the !X flag from 3, but did not speed it up and did not solve 4.
Anyone have any clue what I should try next ?
Thanks in advance, -- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.
For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives:
It turns out that for security reasons the university sets a default cap of two MAC addresses per port, so host and engine maxed it out. I requested that they increase the cap on this port and now things work as expected. -- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday. For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003 "In an open world, who needs windows or gates ?"
On Fri, Sep 25, 2020 at 3:41 PM Valerio Luccio <valerio.luccio@nyu.edu> wrote:
It turns out that for security reasons the university sets a default cap of two MAC addresses per port, so host and engine maxed it out. I requested that they increase the cap on this port and now things work as expected.
Thank you very much for sharing this!
-- As a result of Coronavirus-related precautions, NYU and the Center for Brain Imaging operations will be managed remotely until further notice. All telephone calls and e-mail correspondence are being monitored remotely during our normal business hours of 9am-5pm, Monday through Friday.
For MRI scanner-related emergency, please contact: Keith Sanzenbach at keith.sanzenbach@nyu.edu and/or Pablo Velasco at pablo.velasco@nyu.edu For computer/hardware/software emergency, please contact: Valerio Luccio at valerio.luccio@nyu.edu For TMS/EEG-related emergency, please contact: Chrysa Papadaniil at chrysa@nyu.edu For CBI-related administrative emergency, please contact: Jennifer Mangan at jennifer.mangan@nyu.edu
Valerio Luccio (212) 998-8736 Center for Brain Imaging 4 Washington Place, Room 158 New York University New York, NY 10003
"In an open world, who needs windows or gates ?"
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/A6DQYT7DGUNB2T...
participants (5)
-
Dominik Holler -
Edward Berger -
Strahil Nikolov -
Valerio Luccio -
valerio.luccio＠nyu.edu