[ https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664012#comment-13664012 ]
Jayapal Reddy commented on CLOUDSTACK-2215: ------------------------------------------- It did not reproduce for me. Here is my setup details: CS 4.2 (latest master), Xenserver with two NICs * NIC 1 (public/management/guest) public: tagged-52 tagged 10.147.52.100 - 10.147.52.103 public: tagged-52 tagged 10.147.52.200 - 10.147.52.204 private: untagged 10.147.41.230 - 10.147.41.240 * NIC 2 (storage) storage: untagged: 10.147.42.200 - 10.147.42.210 * Secondary storage: 10.147.28.7 route on the ssvm: root@s-3-VM:~# ip route 10.147.28.7 via 10.147.42.1 dev eth3 10.103.128.16 via 10.147.40.1 dev eth1 10.252.241.237 via 10.147.40.1 dev eth1 10.147.42.0/24 dev eth3 proto kernel scope link src 10.147.42.207 10.147.52.0/24 dev eth2 proto kernel scope link src 10.147.52.100 10.147.40.0/23 dev eth1 proto kernel scope link src 10.147.41.236 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.1.151 default via 10.147.40.1 dev eth1 root@s-3-VM:~# Template is downloaded successfully. > 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