Contrail Platform Developers
Highlighted
Contrail Platform Developers

After Contrail installation can only connect to controller on local subnet

‎03-07-2020 04:30 PM

Hi, I have a three server setup with command, aio (controller and compute) and compute node. Each server has two NIC - management and data. After installation using the GUI from a remote network I can ssh to command, but not to aio and compute node. From command I can ssh to aio and compute node.

 

This appears to be important as I can connect to command:9091 but cannot connect to aio:8143

 

I would appreciate knowing if this is expected behavior and what I should do to be able to connect to the management subnet remotely.

 

Thank you

6 REPLIES 6
Highlighted
Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

‎03-07-2020 10:24 PM

I suspect that vhost0 interface is causing this behaviour. Can you attach the o/p of ifconfig -a from the aio and compute node ?

Ashish Paul
Highlighted
Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

[ Edited ]
‎03-08-2020 05:04 PM

thx Ashish, I have Centos 7 minimal, so no ifconfig. I've used ip addr and ip r for both servers.

 

aio

[root@contprdap22 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:88:b5:86 brd ff:ff:ff:ff:ff:ff
inet 10.102.128.27/24 brd 10.102.128.255 scope global noprefixroute ens192
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe88:b586/64 scope link
valid_lft forever preferred_lft forever
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:88:00:93 brd ff:ff:ff:ff:ff:ff
4: pkt1: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void 82:ac:db:fc:be:ae brd 00:00:00:00:00:00
5: pkt3: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void e2:81:d8:ce:55:7c brd 00:00:00:00:00:00
6: pkt2: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void 86:de:e5:ec:79:d2 brd 00:00:00:00:00:00
7: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:50:56:88:00:93 brd ff:ff:ff:ff:ff:ff
inet 10.102.129.27/24 brd 10.102.129.255 scope global vhost0
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe88:93/64 scope link
valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:43:c1:78:43 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
9: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether da:1a:40:c6:ab:56 brd ff:ff:ff:ff:ff:ff
inet6 fe80::d81a:40ff:fec6:ab56/64 scope link
valid_lft forever preferred_lft forever

 

[root@contprdap22 ~]# ip r
default via 10.102.129.254 dev vhost0
default via 10.102.128.254 dev ens192 proto static metric 100
10.102.128.0/24 dev ens192 proto kernel scope link src 10.102.128.27 metric 100
10.102.129.0/24 dev vhost0 proto kernel scope link src 10.102.129.27
169.254.0.1 dev vhost0 proto 109 scope link
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1

 

[root@contprdap23 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:88:b0:61 brd ff:ff:ff:ff:ff:ff
inet 10.102.128.28/24 brd 10.102.128.255 scope global noprefixroute ens192
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe88:b061/64 scope link
valid_lft forever preferred_lft forever
3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:88:49:09 brd ff:ff:ff:ff:ff:ff
4: pkt1: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void f6:7c:f0:aa:ad:da brd 00:00:00:00:00:00
5: pkt3: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void 96:1f:12:9d:fa:47 brd 00:00:00:00:00:00
6: pkt2: <UP,LOWER_UP> mtu 65535 qdisc noqueue state UNKNOWN group default qlen 1000
link/void ce:d9:ab:ec:f2:bd brd 00:00:00:00:00:00
7: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:50:56:88:49:09 brd ff:ff:ff:ff:ff:ff
inet 10.102.129.28/24 brd 10.102.129.255 scope global vhost0
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:fe88:4909/64 scope link
valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:f5:a2:3a:0b brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
9: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 7e:a2:36:00:56:00 brd ff:ff:ff:ff:ff:ff
inet6 fe80::7ca2:36ff:fe00:5600/64 scope link
valid_lft forever preferred_lft forever

 

[root@contprdap23 ~]# ip r
default via 10.102.129.254 dev vhost0
default via 10.102.128.254 dev ens192 proto static metric 100
10.102.128.0/24 dev ens192 proto kernel scope link src 10.102.128.28 metric 100
10.102.129.0/24 dev vhost0 proto kernel scope link src 10.102.129.28
169.254.0.1 dev vhost0 proto 109 scope link
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1

 

Highlighted
Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

‎03-12-2020 05:59 PM

bump

Highlighted
Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

‎03-12-2020 09:02 PM

What i suspected (issue with vhost0 i/f) doesn't seem to be triggering it!!!. vhost is up and running with a IP address.

Are you able to ping the vhost0 ip ? Can you check the network connection from aio and compute nodes ? IF network connection is fine can you check if the issue is specific to ssh service ?

Ashish Paul
Highlighted
Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

‎03-12-2020 10:08 PM

Hi Ashish,

 

I cannot ping nor ssh nor access webpages on the management IP of the aio and compute, but I can ping and ssh to the data IP for aio and compute. I think this is shown in the previous messages. My concern is not that I can ssh, but that I cannot access the webpages on aio on the management IP.

Contrail Platform Developers

Re: After Contrail installation can only connect to controller on local subnet

‎03-12-2020 10:15 PM

You will need to review your install logs to indentify the interfaces that contrail services are bonded to.

run a netstat on the services/ports and validate which is te listening interfaces.

 

Ashish Paul
Feedback