Welcome, Guest
Username Password: Remember me

CS Beta 3.0 - Network Configuration issue
(1 viewing) (1) Guest
  • Page:
  • 1

TOPIC: CS Beta 3.0 - Network Configuration issue

CS Beta 3.0 - Network Configuration issue 3 months, 1 week ago #9009

  • blade
  • OFFLINE
  • Fresh Boarder
  • Posts: 6
  • Karma: 0
Hi
I have an issue network configuration with Beta 3(CloudStack-acton-beta3-3.0.0-1-rhel6.2).


Setup Process
--------------------------------------------------------------------------------------------------------------------
1. XenServer Networks Name editing
- Network 0 > cloud-private (Primary Management Interface)
- Network 1 > cloud-public (Secondary Management Interface)
2. CloudStack Beta3 Single Node setup
3. Global Settings editing
- host : 172.16.10.204
- management.network.cidr : 172.16.10.0/24
- secstorage.allowed.internal.sites : 172.16.10.0/24
- xen.private.network.device : cloud-private
- xen.public.network.device : cloud-public
4. Zone creation
- Physical Network : cloud-private(Management & VM-to-VM & Storage), cloud-public(Internet-to-VM)
- Public Traffic : 192.168.0.81 ~ 192.168.0.90 (VLAN : empty=untagged)
- Pod : 172.16.10.81 ~ 172.16.10.90
- Guest Traffic : cloud-private / VLAN Range 100-200
- XenServer Host : 172.16.10.206
- Primary & Secondary Storage : 172.16.10.210, 172.16.10.202
1.gif


2.gif




Network issue
- cloud-private network has a "Public" and cloud-public network has a "Management"
> "Public" and "Management", I think that should be interchangeable
- Public IP address of Secondary Storage VM does not seem to on the Web Console
> However, s-1-VM's eth2 has a public IP.

3.gif


4.gif
Last Edit: 3 months ago by blade.

Re: CS Beta 3.0 - Network Configuration issue 2 months, 3 weeks ago #9170

  • pxatzis
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
Hello ,

I'm trying to setup CS 3 beta with a similar network configuration but initial zone creation fails with an error in the public traffic whet there is no VLAN specified (VLAN : empty=untagged).

It looks like that the zone creation script is taking the next number as VLAN id which in fact is the start IP range :

Caused by: java.lang.NumberFormatException: For input string: " 209"




012-02-21 09:59:27,315 ERROR [cloud.api.ApiDispatcher] (catalina-exec-7:null) Exception while executing CreateVlanIpRangeCmd:
java.lang.RuntimeException: Incorrect number
at com.cloud.utils.net.NetUtils.ip2Long(NetUtils.java:362)
at com.cloud.utils.net.NetUtils.ipRangesOverlap(NetUtils.java:328)
at com.cloud.configuration.ConfigurationManagerImpl.checkOverlapPrivateIpRange(ConfigurationManagerImpl.java:1179)
at com.cloud.configuration.ConfigurationManagerImpl.createVlanAndPublicIpRange(ConfigurationManagerImpl.java:2188)
at com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1190)
at com.cloud.api.commands.CreateVlanIpRangeCmd.execute(CreateVlanIpRangeCmd.java:164)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:137)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:508)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:415)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:65)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:883)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2258)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.NumberFormatException: For input string: " 209"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:470)
at java.lang.Integer.parseInt(Integer.java:514)
at com.cloud.utils.net.NetUtils.ip2Long(NetUtils.java:360)

Re: CS Beta 3.0 - Network Configuration issue 2 months, 3 weeks ago #9206

  • pxatzis
  • OFFLINE
  • Fresh Boarder
  • Posts: 2
  • Karma: 0
OK , the error above was a typo

Caused by: java.lang.NumberFormatException: For input string: " 209"

There was a space before 209 !

I'm still trying to do a setup like the OP BUT I don't have Guest Traffic : cloud-private / VLAN Range 100-200 set as I have no access to the LAN.

So when I specify a IP rage (172.23.4.170 to .185) I get :

2012-02-21 13:43:43,589 WARN [cloud.network.NetworkManagerImpl] (Job-Executor-13:job-13) Unable to parse vnet range:
java.lang.NumberFormatException: For input string: "172.23.4.170"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:481)
at java.lang.Integer.parseInt(Integer.java:514)
at com.cloud.network.NetworkManagerImpl.updatePhysicalNetwork(NetworkManagerImpl.java:4479)
at com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1190)
at com.cloud.api.commands.UpdatePhysicalNetworkCmd.execute(UpdatePhysicalNetworkCmd.java:102)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:137)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:433)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
2012-02-21 13:43:43,599 INFO [cloud.api.ApiDispatcher] (Job-Executor-13:job-13) Please provide valid vnet range between 0-4096

And if I just try to add a new guest net :

2012-02-22 05:13:43,937 INFO [cloud.api.ApiDispatcher] (catalina-exec-4:null) More than one physical networks exist in zone id=1 and no tags are specified in order to make a choice

Any hint ?????

Thanks !
  • Page:
  • 1
Time to create page: 0.59 seconds

Resources

Open Source Resources Discuss Site Info

The CloudStack™project is in the process of moving to the Apache Foundation as a podling in the Apache Incubator. Going forward CloudStack will be developed and governed in the Apache way. CloudStack is available under the Apache License 2.0