just my thoughts. if i am understanding your intention correctly, you want to use a dedicated physical network on the hosts for "customized" guest traffic, correct?
You will need to add a "new" physical network to the zone with the networklabel, assaign the traffic type "guest" and start to use tags for the physical networks. Afterwards you would need to implement a dedicated network service offering for this network - by using a tag to associate the network offering to the physical network. Your idea would currently not work cause the "physical network" in a zone is a 1:1 representation of the physical network on the hosts. afterwards you have some like a 1:m (one CS physical network - many various traffic types possible) but not n:1 (many physical networks : one traffic type - even "worse" you would have different "flavours" of one traffic type). Maybe another way to display the relation (physical Network on host - phyical network in a zone - traffic type): Currently used in CS: 1 - 1 - m Not supported in in CS: 1 - n - m what i understand you are looking for: 2 - 1 - 1 (while the traffic type guest would be segmentet into "default" and "custome") Hope that someone can imagine what i mean :-D Am Do., 7. Okt. 2021 um 08:37 Uhr schrieb <cristian.c@istream.today>: > Hello, > > > > Is there a way to use multiple network labels for the same network > type? > for example; I have Guest traffic with network label "vSwitch1, but I also > want to have a vSwitch0 or anything else. If this is not possible, is > there > a way to create custom networks traffic types using the same type of > network > offering but create under a different network. > > label? > > > > I want to have 2 traffic types for Guest, (Guest And GuestCustom) > using > the same network offering but create the under the different network label. > The idea is to have the possibility to create/duplicate same type of > traffic > but deploy under different network label (vSwitchX). > > > > > > > > Regards, > > Cristian > >
