Further testing shows the same problem regardless of which node I shut
down. After shutting any single node down the UI reports:

3 control nodes down
2 analytics nodes down
2 config nodes down
1 database node down

-Dan






On Thu, Aug 20, 2015 at 11:08 PM, Dan Houtz <[email protected]> wrote:

> So it turns out the import error was related to what must have been a
> corrupt VM snapshot that I was rolling back to. After reinstalling a couple
> of the VMs I was able to complete a successful install with VRRP working
> properly.
>
> Unfortunately my first HA test has failed....
>
> Upon powering down host1, I am seeing a number of nodes down in the
> Contrail UI (See attachment).
>
> If I run contrail-status on the remaining nodes things look correct:
>
> root@contrail-ctrl2:~# contrail-status
> == Contrail Control ==
> supervisor-control:           active
> contrail-control              active
> contrail-control-nodemgr      active
> contrail-dns                  active
> contrail-named                active
>
> == Contrail Analytics ==
> supervisor-analytics:         active
> contrail-analytics-api        active
> contrail-analytics-nodemgr    active
> contrail-collector            active
> contrail-query-engine         active
> contrail-snmp-collector       active
> contrail-topology             active
>
> == Contrail Config ==
> supervisor-config:            active
> contrail-api:0                active
> contrail-config-nodemgr       active
> contrail-device-manager       active
> contrail-discovery:0          active
> contrail-schema               active
> contrail-svc-monitor          active
> ifmap                         active
>
> == Contrail Web UI ==
> supervisor-webui:             active
> contrail-webui                active
> contrail-webui-middleware     active
>
> == Contrail Database ==
> supervisor-database:          active
> contrail-database             active
> contrail-database-nodemgr     active
>
> == Contrail Support Services ==
> supervisor-support-service:   active
> rabbitmq-server               active
>
>
>
> --------------------------------------
>
> root@contrail-ctrl3:/opt/contrail/contrail_packages# contrail-status
> == Contrail Control ==
> supervisor-control:           active
> contrail-control              active
> contrail-control-nodemgr      active
> contrail-dns                  active
> contrail-named                active
>
> == Contrail Analytics ==
> supervisor-analytics:         active
> contrail-analytics-api        active
> contrail-analytics-nodemgr    active
> contrail-collector            timeout
> contrail-query-engine         active
> contrail-snmp-collector       active
> contrail-topology             active
>
> == Contrail Config ==
> supervisor-config:            active
> contrail-api:0                active
> contrail-config-nodemgr       active
> contrail-device-manager       backup
> contrail-discovery:0          active
> contrail-schema               backup
> contrail-svc-monitor          backup
> ifmap                         active
>
> == Contrail Web UI ==
> supervisor-webui:             active
> contrail-webui                active
> contrail-webui-middleware     active
>
> == Contrail Database ==
> supervisor-database:          active
> contrail-database             active
> contrail-database-nodemgr     active
>
> == Contrail Support Services ==
> supervisor-support-service:   active
> rabbitmq-server               active
>
>
> -----------------------------------------
>
> root@contrail-tsn1:~# contrail-status
> == Contrail vRouter ==
> supervisor-vrouter:           active
> contrail-vrouter-agent        initializing (XMPP:control-node:10.10.10.11
> connection down Number of connections:7, Expected: 6)
> contrail-vrouter-nodemgr      active
>
>
> Again, everything showed up and operation in the UI overview until I
> powered down host1. Thoughts?
>
> -Dan
>
>
> On Thu, Aug 20, 2015 at 8:03 PM, Dan Houtz <[email protected]> wrote:
>
>> OK, so solved with my plan to move computer role to standalone node once
>> I get fab scripts working again :)
>>
>> Thanks!
>> Dan
>>
>> On Thu, Aug 20, 2015 at 7:49 PM, Nischal Sheth <[email protected]>
>> wrote:
>>
>>>
>>> Hi Dan,
>>>
>>> It's for underlay multicast.
>>>
>>> It happens on servers running vRouter, so workaround would be to use
>>> dedicated servers for controllers i.e. don't run vRouter on controllers.
>>>
>>> -Nischal
>>>
>>> On Aug 20, 2015, at 5:30 PM, Dan Houtz <[email protected]> wrote:
>>>
>>> Hi Nischal,
>>>
>>> To confirm, this bug is related to overlay mutlicast, underlay
>>> multicast, or both? I assume underlay since you are referencing my issues
>>> with HA install. Is there a workaround or is it not possible to do HA
>>> install on 2.2, build 64?
>>>
>>> Thanks!
>>> Dan
>>>
>>> On Thu, Aug 20, 2015 at 5:20 PM, Nischal Sheth <[email protected]>
>>> wrote:
>>>
>>>>
>>>> Sounds like https://bugs.launchpad.net/juniperopenstack/+bug/1485432.
>>>>
>>>> -Nischal
>>>>
>>>> On Aug 20, 2015, at 2:33 PM, Ranjeet R <[email protected]> wrote:
>>>>
>>>> Dan
>>>>
>>>> Your config looks right to me. The issue should be with vrouter running
>>>> in the controller which does not hand over the VRRP multicast packets to
>>>> the host networking stack and hence every keepalived daemon assumes that it
>>>> is the VRRP master.
>>>>
>>>> If you configure a separate compute and re-run provisioning, this
>>>> should be resolved.
>>>>
>>>> Ranjeet
>>>>
>>>> *From:* Dan Houtz [mailto:[email protected] <[email protected]>]
>>>> *Sent:* Thursday, August 20, 2015 12:08 PM
>>>> *To:* Ranjeet R <[email protected]>
>>>> *Cc:* Sunil Bakhru <[email protected]>; [email protected];
>>>> Suresh Kumar Vinapamula Venkata <[email protected]>; Sanju Abraham <
>>>> [email protected]>
>>>> *Subject:* Re: [Users] Problems with VRRP/Keepalived on HA install
>>>>
>>>> Hi Ranjeet,
>>>>
>>>>
>>>> Thank you for the pointer on the compute nodes. We aren't actually
>>>> doing any Open Stack / Virtual Machine stuff so the only reason I even
>>>> provisioned compute is to turn up TOR/TSN after the basics are working.
>>>> I'll go ahead and do a separate host for compute.
>>>> * Your testbed.py
>>>>
>>>> Attached
>>>>
>>>> *  keepalived.conf in /etc/keepalived
>>>>
>>>> vrrp_script chk_haproxy_INTERNAL_10_10_10_10 {
>>>>         script "killall -0 haproxy" # verify if pid exists
>>>>         interval 1
>>>>         timeout 3
>>>>         rise 2
>>>>         fall 2
>>>> }
>>>>
>>>> vrrp_script chk_ctrldatanet_INTERNAL_10_10_10_10 {
>>>>     script "/opt/contrail/bin/chk_ctrldata.sh"
>>>>     interval 1
>>>>     timeout 3
>>>>     rise 1
>>>>     fall 1
>>>> }
>>>>
>>>> vrrp_instance INTERNAL_10_10_10_10 {
>>>>         interface eth0
>>>>         state MASTER
>>>>         preempt_delay 7
>>>>         garp_master_delay 5
>>>>         garp_master_repeat 3
>>>>         garp_master_refresh 1
>>>>         advert_int 1
>>>>         virtual_router_id 100
>>>>         vmac_xmit_base
>>>>         priority  100
>>>>         virtual_ipaddress {
>>>>                 10.10.10.10/28 dev eth0
>>>>         }
>>>>         track_script  {
>>>>                 chk_haproxy_INTERNAL_10_10_10_10
>>>>         }
>>>>
>>>>         track_script  {
>>>>             chk_ctrldatanet_INTERNAL_10_10_10_10
>>>>         }
>>>>         track_interface {
>>>>             eth0
>>>>             eth0
>>>>         }
>>>> }
>>>>
>>>>
>>>> * “ip a s” in all three controllers
>>>>
>>>> root@contrail-ctrl1:~# ip addr show
>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>>> group default
>>>>     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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
>>>> group default qlen 1000
>>>>     link/ether 00:0c:29:3c:78:40 brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.10/28 scope global eth0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fe3c:7840/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 3: pkt1: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void 02:8c:c5:60:50:a4 brd 00:00:00:00:00:00
>>>> 4: pkt3: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void 2a:0f:6c:45:3b:2d brd 00:00:00:00:00:00
>>>> 5: pkt2: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void 36:48:d4:53:62:e1 brd 00:00:00:00:00:00
>>>> 6: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 1000
>>>>     link/ether 00:0c:29:3c:78:40 brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.11/28 brd 10.10.10.15 scope global vhost0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fe3c:7840/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>>>> state DOWN group default
>>>>     link/ether fe:8b:4f:4d:ea:07 brd ff:ff:ff:ff:ff:ff
>>>>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>>>>        valid_lft forever preferred_lft forever
>>>> 8: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 500
>>>>     link/ether a2:fe:56:9d:31:d3 brd ff:ff:ff:ff:ff:ff
>>>>     inet6 fe80::a0fe:56ff:fe9d:31d3/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>>
>>>> root@contrail-ctrl2:~# ip addr show
>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>>> group default
>>>>     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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
>>>> group default qlen 1000
>>>>     link/ether 00:0c:29:a8:f8:75 brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.10/28 scope global eth0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fea8:f875/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 3: pkt1: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void ee:ee:d5:be:b2:da brd 00:00:00:00:00:00
>>>> 4: pkt3: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void b2:3c:0c:35:3a:ec brd 00:00:00:00:00:00
>>>> 5: pkt2: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void 12:1f:47:41:fe:76 brd 00:00:00:00:00:00
>>>> 6: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 1000
>>>>     link/ether 00:0c:29:a8:f8:75 brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.12/28 brd 10.10.10.15 scope global vhost0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fea8:f875/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>>>> state DOWN group default
>>>>     link/ether 92:2b:3d:68:2f:06 brd ff:ff:ff:ff:ff:ff
>>>>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>>>>        valid_lft forever preferred_lft forever
>>>> 8: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 500
>>>>     link/ether be:23:b2:35:77:d4 brd ff:ff:ff:ff:ff:ff
>>>>     inet6 fe80::bc23:b2ff:fe35:77d4/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>>
>>>> root@contrail-ctrl3:~# ip addr show
>>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>>> group default
>>>>     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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
>>>> group default qlen 1000
>>>>     link/ether 00:0c:29:31:bc:2a brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.10/28 scope global eth0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fe31:bc2a/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 3: pkt1: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void 4e:6e:2b:09:36:b8 brd 00:00:00:00:00:00
>>>> 4: pkt3: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void ea:7b:f6:70:e0:85 brd 00:00:00:00:00:00
>>>> 5: pkt2: <> mtu 65535 qdisc noop state DOWN group default
>>>>     link/void ea:72:86:5e:92:6e brd 00:00:00:00:00:00
>>>> 6: vhost0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 1000
>>>>     link/ether 00:0c:29:31:bc:2a brd ff:ff:ff:ff:ff:ff
>>>>     inet 10.10.10.13/28 brd 10.10.10.15 scope global vhost0
>>>>        valid_lft forever preferred_lft forever
>>>>     inet6 fe80::20c:29ff:fe31:bc2a/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>> 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
>>>> state DOWN group default
>>>>     link/ether 52:80:7d:6d:1b:76 brd ff:ff:ff:ff:ff:ff
>>>>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>>>>        valid_lft forever preferred_lft forever
>>>> 8: pkt0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>>> state UNKNOWN group default qlen 500
>>>>     link/ether 0a:9c:03:a7:0a:e5 brd ff:ff:ff:ff:ff:ff
>>>>     inet6 fe80::89c:3ff:fea7:ae5/64 scope link
>>>>        valid_lft forever preferred_lft forever
>>>>
>>>> * /etc/network/interfaces in all three controllers
>>>>
>>>>
>>>> root@contrail-ctrl1:~# cat /etc/network/interfaces
>>>> # This file describes the network interfaces available on your system
>>>> # and how to activate them. For more information, see interfaces(5).
>>>>
>>>> # The loopback network interface
>>>> auto lo
>>>> iface lo inet loopback
>>>>
>>>> # The primary network interface
>>>> auto eth0
>>>> iface eth0 inet manual
>>>>     pre-up ifconfig eth0 up
>>>>     post-down ifconfig eth0 down
>>>>     pre-up ethtool --offload eth0 rx off
>>>>     pre-up ethtool --offload eth0 tx off
>>>>
>>>>
>>>> auto vhost0
>>>> iface vhost0 inet static
>>>>     pre-up /opt/contrail/bin/if-vhost0
>>>>     netmask 255.255.255.240
>>>>     network_name application
>>>>     address 10.10.10.11
>>>>     gateway 10.10.10.1
>>>>     dns-search zone1.ord6.hannibal.scnet.net
>>>>     dns-nameservers 172.16.18.1
>>>>
>>>>
>>>> root@contrail-ctrl2:~# cat /etc/network/interfaces
>>>> # This file describes the network interfaces available on your system
>>>> # and how to activate them. For more information, see interfaces(5).
>>>>
>>>> # The loopback network interface
>>>> auto lo
>>>> iface lo inet loopback
>>>>
>>>> # The primary network interface
>>>> auto eth0
>>>> iface eth0 inet manual
>>>>     pre-up ifconfig eth0 up
>>>>     post-down ifconfig eth0 down
>>>>     pre-up ethtool --offload eth0 rx off
>>>>     pre-up ethtool --offload eth0 tx off
>>>>
>>>>
>>>> auto vhost0
>>>> iface vhost0 inet static
>>>>     pre-up /opt/contrail/bin/if-vhost0
>>>>     netmask 255.255.255.240
>>>>     network_name application
>>>>     address 10.10.10.12
>>>>     gateway 10.10.10.1
>>>>     dns-search zone1.ord6.hannibal.scnet.net
>>>>     dns-nameservers 172.16.18.1
>>>>
>>>>
>>>> root@contrail-ctrl3:~# cat /etc/network/interfaces
>>>> # This file describes the network interfaces available on your system
>>>> # and how to activate them. For more information, see interfaces(5).
>>>>
>>>> # The loopback network interface
>>>> auto lo
>>>> iface lo inet loopback
>>>>
>>>> # The primary network interface
>>>> auto eth0
>>>> iface eth0 inet manual
>>>>     pre-up ifconfig eth0 up
>>>>     post-down ifconfig eth0 down
>>>>     pre-up ethtool --offload eth0 rx off
>>>>     pre-up ethtool --offload eth0 tx off
>>>>
>>>>
>>>> auto vhost0
>>>> iface vhost0 inet static
>>>>     pre-up /opt/contrail/bin/if-vhost0
>>>>     netmask 255.255.255.240
>>>>     network_name application
>>>>     address 10.10.10.13
>>>>     gateway 10.10.10.1
>>>>     dns-search zone1.ord6.hannibal.scnet.net
>>>>     dns-nameservers 172.16.18.1
>>>>
>>>> On Thu, Aug 20, 2015 at 12:50 PM, Ranjeet R <[email protected]>
>>>> wrote:
>>>>
>>>> Resending to make sure its sent to the list. Had some issues with list
>>>> subscription.
>>>>
>>>> Ranjeet
>>>>
>>>> *From:* Ranjeet R
>>>> *Sent:* Thursday, August 20, 2015 10:39 AM
>>>> *To:* Sunil Bakhru <[email protected]>; Dan Houtz <[email protected]>;
>>>>  [email protected]
>>>> *Cc:* Suresh Kumar Vinapamula Venkata <[email protected]>; Sanju
>>>> Abraham <[email protected]>
>>>> *Subject:* RE: [Users] Problems with VRRP/Keepalived on HA install
>>>>
>>>> Dan
>>>>
>>>> VRRP Advertisement are sourced from the local IP Address in keepalived
>>>> as well.
>>>>
>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>> decode
>>>> listening on p1p1, link-type EN10MB (Ethernet), capture size 65535 bytes
>>>> 10:29:38.438090 IP 10.84.24.32 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 112, prio 99, authtype none, intvl 1s, length 20
>>>>
>>>> VIP address does not show up ifconfig, hence I am not sure how you have
>>>> configured your network interfaces. The following will help us debug this
>>>> further -
>>>>
>>>> * Your testbed.py
>>>> *  keepalived.conf in /etc/keepalived
>>>> * “ip a s” in all three controllers
>>>> * /etc/network/interfaces in all three controllers
>>>>
>>>> I also see that you are using the controller as a compute node as well
>>>> which is not supported in HA mode because of an existing bug in vrouter in
>>>> handling multicast packets. I would recommend to use a separate compute
>>>> node.
>>>>
>>>> Ranjeet
>>>>
>>>>
>>>> *From:* Sunil Bakhru
>>>> *Sent:* Thursday, August 20, 2015 10:25 AM
>>>> *To:* Dan Houtz <[email protected]>; [email protected]
>>>> *Cc:* Ranjeet R <[email protected]>; Suresh Kumar Vinapamula
>>>> Venkata <[email protected]>; Sanju Abraham <[email protected]>
>>>> *Subject:* Re: [Users] Problems with VRRP/Keepalived on HA install
>>>>
>>>> Dan,
>>>>
>>>>    Something is not adding up in your setup. All three controllers
>>>> should not be the master.
>>>> I am cc’ing the HA team members to follow up with you regarding this
>>>> issue.
>>>>
>>>> Thanks,
>>>> Sunil
>>>>
>>>> *From: *Dan Houtz <[email protected]>
>>>> *Date: *Thursday, August 20, 2015 at 9:05 AM
>>>> *To: *"[email protected]" <[email protected]>
>>>> *Subject: *[Users] Problems with VRRP/Keepalived on HA install
>>>>
>>>>
>>>> Hi everyone,
>>>>
>>>> We are currently working on our first HA build of Contrail as up until
>>>> not we've only tested on single node installs.
>>>>
>>>> At this point the install seems to work well but we are seeing issue
>>>> with keepalived and the VIP address. For some odd reason all 3 Contrail
>>>> nodes are master for the VIP despite tcpdump showing each box receiving
>>>> vrrp multicast packets from each other and showing each with a different
>>>> priority.
>>>>
>>>> Should the mcast packets be sources from the VIP? I see our Juniper
>>>> boxes source their VRRP packets from interfaces local address.
>>>>
>>>> I've done plenty of VRRP on hardware routers but don't have any
>>>> previous experience with keepalived so If anyone has any pointers it would
>>>> be greatly appreciated. If there is any other data that would help to
>>>> diagnose I am happy to provide it.
>>>> Thanks!
>>>> Dan
>>>>
>>>>
>>>>
>>>> root@contrail-ctrl1:~# tcpdump -n vrrp
>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>> decode
>>>> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
>>>> 10:58:41.487505 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:58:41.564731 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:58:42.156237 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:58:42.178271 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:58:42.198405 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:58:42.567434 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:58:42.567685 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:58:43.157471 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:58:43.178394 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:58:43.178440 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>>
>>>>
>>>> root@contrail-ctrl2:~# tcpdump -n vrrp
>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>> decode
>>>> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
>>>> 10:57:46.197718 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:57:46.197844 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:57:46.411012 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:57:46.749765 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:57:46.749907 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:57:47.209753 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>>
>>>>
>>>> root@contrail-ctrl3:~# tcpdump -n vrrp
>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol
>>>> decode
>>>> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
>>>> 10:59:19.946640 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:19.949357 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:20.248377 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:59:20.631787 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:59:20.631853 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:59:21.067412 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:21.067490 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:21.332021 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>> 10:59:21.642771 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:59:21.645999 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 100, authtype none, intvl 1s, length 20
>>>> 10:59:22.053416 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:22.059508 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> (ttl 254), vrid 100, prio 99, authtype none, intvl 1s, length 20
>>>> 10:59:22.404645 IP 10.10.10.10 > 224.0.0.18: VRRPv2, Advertisement,
>>>> vrid 100, prio 98, authtype none, intvl 1s, length 20
>>>>
>>>> root@contrail-ctrl1:~# ifconfig eth0
>>>> eth0      Link encap:Ethernet  HWaddr 00:0c:29:3c:78:40
>>>>           inet addr:10.10.10.10  Bcast:0.0.0.0  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fe3c:7840/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:2957429 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:2970106 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:693687361 (693.6 MB)  TX bytes:857618328 (857.6 MB)
>>>>
>>>> root@contrail-ctrl1:~# ifconfig vhost0
>>>> vhost0    Link encap:Ethernet  HWaddr 00:0c:29:3c:78:40
>>>>           inet addr:10.10.10.11  Bcast:10.10.10.15  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fe3c:7840/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:2278044 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:2221017 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:644167184 (644.1 MB)  TX bytes:5245411872 (5.2 GB)
>>>>
>>>>
>>>> root@contrail-ctrl2:~# ifconfig eth0
>>>> eth0      Link encap:Ethernet  HWaddr 00:0c:29:a8:f8:75
>>>>           inet addr:10.10.10.10  Bcast:0.0.0.0  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fea8:f875/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:4370215 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:4785945 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:929798623 (929.7 MB)  TX bytes:907980495 (907.9 MB)
>>>>
>>>> root@contrail-ctrl2:~# ifconfig vhost0
>>>> vhost0    Link encap:Ethernet  HWaddr 00:0c:29:a8:f8:75
>>>>           inet addr:10.10.10.12  Bcast:10.10.10.15  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fea8:f875/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:3664174 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:4159902 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:878825685 (878.8 MB)  TX bytes:2547421114 (2.5 GB)
>>>>
>>>> root@contrail-ctrl3:~# ifconfig eth0
>>>> eth0      Link encap:Ethernet  HWaddr 00:0c:29:31:bc:2a
>>>>           inet addr:10.10.10.10  Bcast:0.0.0.0  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fe31:bc2a/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:539492 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:411385 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:266613501 (266.6 MB)  TX bytes:73900674 (73.9 MB)
>>>>
>>>>
>>>> root@contrail-ctrl3:~# ifconfig vhost0
>>>> vhost0    Link encap:Ethernet  HWaddr 00:0c:29:31:bc:2a
>>>>           inet addr:10.10.10.13  Bcast:10.10.10.15  Mask:255.255.255.240
>>>>           inet6 addr: fe80::20c:29ff:fe31:bc2a/64 Scope:Link
>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>           RX packets:406152 errors:0 dropped:0 overruns:0 frame:0
>>>>           TX packets:395289 errors:0 dropped:0 overruns:0 carrier:0
>>>>           collisions:0 txqueuelen:1000
>>>>           RX bytes:258079952 (258.0 MB)  TX bytes:73573553 (73.5 MB)
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> [email protected]
>>>>
>>>> http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
>>>>
>>>>
>>>>
>>>
>>>
>>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org

Reply via email to