[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663717#comment-13663717 ]
Mice Xia commented on CLOUDSTACK-2215: -------------------------------------- NDK, I also built an env following your description to reproduce the issue: * NIC 1 (management/storage) management: untagged, 1.1.1.130 - 1.1.1.139 storage: vlan 2215, 192.168.11.130 - 192.168.11.139 * NIC 2 (public/guest) public: untagged 192.168.10.130 - 192.168.10.139 * Secondary storage: 192.168.11.8 (vlan 2215) * ip route result on SSVM: 8.8.8.8 via 1.1.1.10 dev eth1 1.1.1.0/24 dev eth1 proto kernel scope link src 1.1.1.131 192.168.11.0/24 dev eth3 proto kernel scope link src 192.168.11.132 192.168.10.0/24 dev eth2 proto kernel scope link src 192.168.10.134 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.1.157 default via 192.168.10.254 dev eth2 i didn't see there is anything wrong from the routing table, management traffic via eth1, public on eth2 which is the default gw, storage on eth3, and control on eth0; '8.8.8.8' is the configured internal DNS and routed from eth1. this issue is probably related to the env/config, what's the result of "cat /var/cache/cloud/cmdline" on your ssvm? > ACS41 SSVM does not use allocated storage ip range > -------------------------------------------------- > > Key: CLOUDSTACK-2215 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller, Storage Controller > Affects Versions: 4.0.1, 4.0.2, 4.1.0 > Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've > not seen fixes for this yet. > VMWare vSphere 5.0 with Advanced Network > Reporter: ilya musayev > Priority: Blocker > Labels: Network, SSVM > > Create Advanced Network Zone, assign a range of IPs to storage network, also > predefine public range. > The Secondary Storage VM gets the IPs of Public Networks and not whats its > been given. In my example, i've defined two public networks - with very small > ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, > and 1 IP from Public Network B. > If you have stringent setup and you need to allocate IPs as designed and > setup firewall rules, one would expect to setup firewall rules on storage ip > range, thinking that SSVM is going to use the IP from that range, however, > instead - it uses public ip range. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira