You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Anton Rubets <pl...@gmail.com> on 2013/07/02 11:03:10 UTC

Cloudmonkey create network problem

Hi. i try create the shared network with cloudmonkey with command:
create network name=Shared-Network displaytext=Shared-Network
networkofferingid=f03374d2-a8dc-40ab-8839-94dc31238410
physicalnetworkid=246635bf-1cda-4e1b-bc8f-b4ddb242e81c gateway=10.1.1.1
netmask=225.225.225.0 networkdomain=*************************
startip=10.1.1.2 endip10.1.1.124
zoneid=13fde89f-5eea-4e94-a38b-ede647126022
but always have error
HTTP Error 431:
if remove the network domain option:
HTTP Error 401: Unauthorized

Can someone deal with it ?
Thanks

Re: Cloudmonkey create network problem

Posted by Anton Rubets <pl...@gmail.com>.
Thanks for reply. I found solution after detailed reading cloudstack logs.
In the information flow hard to see right info.
So who will read this , look at cloudstack-menagement.log
Now i have problem with VM creation, but this is another story

Re: Cloudmonkey create network problem

Posted by Geoff Higginbottom <ge...@shapeblue.com>.
Not currently in front of my computer to check but I suspect that as its a Shared Network you are trying to create you need to specify the domain unless you are trying to share at Zone Level.

You are also specifying an IP Range but no VLAN ID, theses settings are always required together.

Check and confirm the offering you are referencing is for a shared network, and has the Specify VLAN flag set, as this also enables (enforces) the allocation of a guest IP range rather than just the CIDR.

Also what account are you running this under, shared networks can only be created by Root Admins.

Regards

Geoff Higginbottom
CTO / Cloud Architect

D: +44 20 3603 0542<tel:+442036030542> | S: +44 20 3603 0540<tel:+442036030540>| M: +447968161581<tel:+447968161581>

geoff.higginbottom@shapeblue.com<ma...@shapeblue.com> |www.shapeblue.com | Twitter:@shapeblue<https://twitter.com/#!/shapeblue>

ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N 4HS


On 2 Jul 2013, at 10:04, "Anton Rubets" <pl...@gmail.com>> wrote:

Hi. i try create the shared network with cloudmonkey with command:
create network name=Shared-Network displaytext=Shared-Network
networkofferingid=f03374d2-a8dc-40ab-8839-94dc31238410
physicalnetworkid=246635bf-1cda-4e1b-bc8f-b4ddb242e81c gateway=10.1.1.1
netmask=225.225.225.0 networkdomain=*************************
startip=10.1.1.2 endip10.1.1.124
zoneid=13fde89f-5eea-4e94-a38b-ede647126022
but always have error
HTTP Error 431:
if remove the network domain option:
HTTP Error 401: Unauthorized

Can someone deal with it ?
Thanks
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Cloudmonkey create network problem

Posted by Rohit Yadav <bh...@apache.org>.
On Tue, Jul 2, 2013 at 2:33 PM, Anton Rubets <pl...@gmail.com> wrote:

> Hi. i try create the shared network with cloudmonkey with command:
> create network name=Shared-Network displaytext=Shared-Network
> networkofferingid=f03374d2-a8dc-40ab-8839-94dc31238410
> physicalnetworkid=246635bf-1cda-4e1b-bc8f-b4ddb242e81c gateway=10.1.1.1
> netmask=225.225.225.0 networkdomain=*************************
> startip=10.1.1.2 endip10.1.1.124
> zoneid=13fde89f-5eea-4e94-a38b-ede647126022
> but always have error
> HTTP Error 431:
> if remove the network domain option:
> HTTP Error 401: Unauthorized
>
> Can someone deal with it ?
>

For 403: Try what Geoff suggests.
For 401: Check if you're using port 8080, that requires apiKey and
secretKey to be set or you've authorization to execute this API (check user
type and ACL permissions).

Cheers.


> Thanks
>