Details
Description
On 21 May 2015, at 10:29, Singh, Devender <dsingh@virtela.net> wrote:
Hi Cloudstack Team,
We had no problems building and using /31 networks on 4.2.0, but after our upgrade to 4.4.2 we are no longer able to add new ones.
We have a lot of them already in place. As an example I pasted some output from cloudmonkey on a link that is already established and working.
Does anyone have a workaround, or can point me in the right direction for a patch?
(local) > list networks id=e044c442-48f7-4bae-8c5d-530423a249f7
count = 1
network:
id = e044c442-48f7-4bae-8c5d-530423a249f7
name = VLAN180
acltype = Domain
broadcastdomaintype = Vlan
broadcasturi = vlan://180
canusefordeploy = False
cidr = 202.90.43.0/31
displaynetwork = True
displaytext = VM-UTILITY-2
dns1 = 4.2.2.1
domain = ROOT
domainid = 8acf0368-e5b1-11e2-b5cf-2ef4cf18a6ae
gateway = 202.90.43.0
ispersistent = False
issystem = False
netmask = 255.255.255.254
networkofferingavailability = Optional
networkofferingconservemode = False
networkofferingdisplaytext = private-guest1_switch
networkofferingid = 0b63d457-5f5e-426f-a81e-8797e522eb8c
networkofferingname = private-guest1_switch
physicalnetworkid = cf4c2846-2418-4ba4-b307-6a6405860799
related = e044c442-48f7-4bae-8c5d-530423a249f7
restartrequired = False
service:
specifyipranges = True
state = Setup
strechedl2subnet = False
subdomainaccess = True
tags:
traffictype = Guest
type = Shared
vlan = 180
zoneid = 88066cb4-64ab-4c54-83a9-3279a1e030cb
zonename = UTILITY-ZONE-1