Hi Rohit, The isolation is correct, VLAN , which same DB Table.
I found the cause of the issue, it is due to IPv6. For this design, on share network, it only allow One Prefix per Network. So we have to create two subnet for two prefix . However if you need to use IPv6, the current design is only allow one /64 prefix per VLAN, even-though if you create multiple ipv4 prefix and network per vlan, you are not allow to create diff /64 ipv6 prefix . So what todo is use the same /64 prefix for multiple network of same VLAN. And when this happen the error message comes out. I am also found a work around is , in IPv6 , even though the same /64, use different start and end ip of IPv6, and issue will solve, However, when deploying VM, the system did not follow the start and end Ip as defined. And I notice last few part of the Ipv6 assignment is following VM mac address. And I hope it wont happen IP conflic in future. On Sun, Jan 17, 2021 at 11:18 PM Rohit Yadav <[email protected]> wrote: > Hi Hean, > > Can you check if you've VLAN enable for your zone as isolation method and > if you've available/free VLANs in the physical network of your zone where > you're deploying the guest network. > > > Regards. > > ________________________________ > From: Hean Seng <[email protected]> > Sent: Friday, January 15, 2021 19:34 > To: [email protected] <[email protected]> > Subject: Error Create Network - isolation type is not BCF_SEGMENT > > HI All > > I am testing on Cloudstack 4.15, and create the network on security group. > , Due to now one Guest Network only can accept One prefix one network , > I have one Vlan and 2 prefix ( for example, a.a.a.0/24 and b.b.b.0/24 . > > Initially am able to do that without issue, but when delete the network > and recreate back , i seme not able to create the same VLAN and different > prefix , the log show following: > > It have following error : > > aultSharedNetworkOfferingWithSGService] by AffinityGroupAccessChecker > > 2021-01-15 21:56:39,428 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network, the physical isolation type is not BCF_SEGMENT > > 2021-01-15 21:56:39,432 DEBUG [o.a.c.n.c.m.ContrailGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,435 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,439 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,442 DEBUG [c.c.n.g.OvsGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,446 DEBUG [c.c.n.g.DirectNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) VLAN: VLAN > > 2021-01-15 21:56:39,478 INFO [c.c.n.g.DirectNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,488 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) SSP not > configured to be active > > 2021-01-15 21:56:39,491 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Refusing to > design this network > > 2021-01-15 21:56:39,495 DEBUG [o.a.c.e.o.NetworkOrchestrator] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Releasing > lock for Acct[bbe8ee05-49be-11eb-b0f8-7845c4fad15b-system] > > 2021-01-15 21:56:39,505 DEBUG [c.c.c.ConfigurationManagerImpl] > (qtp537066525-2202:ctx-db7cf415 ctx-6d305c8e) (logid:f8bafeb5) Access > granted to Acct[bbe9e97d-49be-11eb-b0f8-7845c4fad15b-admin] to zone:1 by > AffinityGroupAccessChecker > > 2 > > > -- > Regards, > Hean Seng > > [email protected] > www.shapeblue.com > 3 London Bridge Street, 3rd floor, News Building, London SE1 9SGUK > @shapeblue > > > > -- Regards, Hean Seng
