@anav, I agree with you 100%, when he “clarified” things, he must have taken his example from Google home, which often gives an incomplete answer, then asks “would you like more context?”, and if you reply “yes”, it just repeats the same thing over again, with no additional information. Compare Post #1 with the the “clarification” in post #5. To me the only difference is the formatting.
This is evidently a continuation of this thread Vlans and export config with a more detailed diagram in post #10
Note that even though he is talking about vlans in that thread, I am still not convinced that the “concept” of what vlans are has “clicked” yet for him. What he is currently using for separation is port-isolation in the CSS326, which a different concept than vlans; it is limiting for each switch-port, what other switch-ports can be forwarded to. This is like asymmetrical subsets of the same broadcast domain, more like overlapping circles in a venn diagram, where there is a non-empty intersection. Additionally, port isolation has no significance off the switch, any thing past the switch is either included of excluded.
Vlans are different in that the broadcast domains for vlans have no overlap (intersection). And vlans can extend beyond the switch border, since tags can carry the “membership credentials” with the ethernet frame.
It is very unclear to me what the purpose of the Hex is.
And I thought I would let others know about the other thread, because he is currently using only port-isolation the keep things separate, because he has a single ip subnet.