You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wilder Rodrigues (JIRA)" <ji...@apache.org> on 2015/10/08 11:29:27 UTC
[jira] [Commented] (CLOUDSTACK-8876) VPC tier network restart,
missing ip on VR interface
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948365#comment-14948365 ]
Wilder Rodrigues commented on CLOUDSTACK-8876:
----------------------------------------------
Hi all,
I executed the steps above, SSH into the router and checked the IP:
root@r-57-VM:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 0e:00:a9:fe:02:cb brd ff:ff:ff:ff:ff:ff
inet 169.254.2.203/16 brd 169.254.255.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 06:1d:42:00:00:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.23.6/24 brd 192.168.23.255 scope global eth1
inet 192.168.23.7/24 brd 192.168.23.255 scope global secondary eth1
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 02:00:2c:c2:00:02 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.1/26 brd 10.0.1.63 scope global eth2
root@r-57-VM:~#
I then restarted the VPC, with Clean option checked, and checked the router IP again:
root@r-59-VM:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 0e:00:a9:fe:03:f7 brd ff:ff:ff:ff:ff:ff
inet 169.254.3.247/16 brd 169.254.255.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 06:26:7a:00:00:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.23.6/24 brd 192.168.23.255 scope global eth1
inet 192.168.23.7/24 brd 192.168.23.255 scope global secondary eth1
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 02:00:34:58:00:03 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.1/26 brd 10.0.1.63 scope global eth2
root@r-59-VM:~#
As you can see, all the IPs were reconfigured successfully!
root@r-59-VM:~# iptables -L -t nat --verbose
Chain PREROUTING (policy ACCEPT 33 packets, 2428 bytes)
pkts bytes target prot opt in out source destination
2 128 DNAT tcp -- eth1 any anywhere 192.168.23.7 tcp dpt:ssh to:10.0.1.44:22
Chain INPUT (policy ACCEPT 16 packets, 1128 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 21 packets, 1624 bytes)
pkts bytes target prot opt in out source destination
0 0 DNAT tcp -- any any anywhere 192.168.23.7 tcp dpt:ssh to:10.0.1.44:22
Chain POSTROUTING (policy ACCEPT 3 packets, 368 bytes)
pkts bytes target prot opt in out source destination
0 0 SNAT all -- any eth2 10.0.1.0/26 anywhere to:10.0.1.1
38 2751 SNAT all -- any eth1 anywhere anywhere to:192.168.23.6
0 0 SNAT tcp -- any any anywhere 192.168.23.7 tcp dpt:ssh to:10.0.1.44:22
root@r-59-VM:~#
I also SSH into the user VM via the public IP:
sbpltk1zffh04:phalanx wrodrigues$ ssh root@192.168.23.7
The authenticity of host '192.168.23.7 (192.168.23.7)' can't be established.
RSA key fingerprint is 06:5d:c2:12:87:18:4d:62:b9:cf:73:ed:07:ad:8c:2e.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.23.7' (RSA) to the list of known hosts.
root@192.168.23.7's password:
# ls /
bin boot dev etc home lib lib64 linuxrc lost+found media mnt opt proc root run sbin sys tmp usr var
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
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 pfifo_fast qlen 1000
link/ether 02:00:27:b8:00:01 brd ff:ff:ff:ff:ff:ff
inet 10.0.1.44/26 brd 10.0.1.63 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::27ff:feb8:1/64 scope link
valid_lft forever preferred_lft forever
# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=47 time=10.363 ms
64 bytes from 8.8.8.8: seq=1 ttl=47 time=10.087 ms
64 bytes from 8.8.8.8: seq=2 ttl=47 time=13.708 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 10.087/11.386/13.708 ms
# exit
Connection to 192.168.23.7 closed.
sbpltk1zffh04:phalanx wrodrigues$
So, I'm closing this issue.
Cheers,
Wilder
> VPC tier network restart, missing ip on VR interface
> -----------------------------------------------------
>
> Key: CLOUDSTACK-8876
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8876
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Devices
> Affects Versions: 4.5.0
> Reporter: Jayapal Reddy
> Assignee: Wilder Rodrigues
> Priority: Blocker
> Fix For: 4.6.0
>
>
> Reproducing steps:
> 1. Create a vpc and deploy a vm in tier.
> 2. Acquire a public ip and configure PF rule
> 3. check that the VR interface has two ip addresses.
> 4. Restart the tier network with cleanup.
> 5. After restart in VR interface ip (PF rule configured) is missed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)