As far as IP addressing is concerned, the VLAN interfaces will behave in the same way as physical interfaces: that is, you cannot have overlapping IP ranges on two interfaces.
You can do the opposite, i.e. have more than one subnet on a single interface, by using the keywod "secondary". In that case, the subnet may or may not overlap, as you wish.
The only way I can think of to put the same IP range on two VLAN - and I have never tried this, so I don't know if it would work - is to create a BVI interface and to bridge the two VLANs together. Of course, you would get the same IP range, as well as the same broadcast domain, on both sides.
This is all logical, if you think about it - if the router had a packet for that an IP address in that range, which VLAN would it send it to?
It does not work to have 1 IP subnet on two VLANs. A VLAN is a layer 2 broadcast domain and should have a unique IP subnet. The basic problem is that the layer 3 interface forwarding into the first VLAN believes that all of the subnet is locally connected into that VLAN and can nor forward to addresses in the same subnet but in a different VLAN.
If you have one subnet and you have 2 VLANs then what you can think about doing is to split the subnet in two parts (wich creates two smaller but independent subnets) and put a unique subnet onto each VLAN. Your question mentions possibly having a /23. If for example you have 172.16.4.0/23 you could divide that and have 172.16.4.0/24 in one subnet on the first VLAN and have 172.16.5.0/24 in the second subnet on the second VLAN. That approach will work. So you can split the subnet and use the parts but you can not put the same subnet into 2 VLANs.
basically what you are going to do to make this work is take a L3 switch and build the two vlans you want (will refer to them as X and Y) in the SUP
console (enable) set vlan x name x state active
vlan x created
console (enable) set vlan y name y state active
vlan y created
Now you are going to get into the layer 3 portion of the L3 device, whatever that may be, and assuming you are using 1 class C subnet for your IP space, your command structure would look something like this
(# = whatever IP structure you want to use)
router#(config) int vlan x
router#(config-int) ip add #.#.#.1 255.255.255.128
router#(config-int) no shut
router#(config-int) int vlan y
router#(config-int) ip add #.#.#.129 255.255.255.128
router#(config-int) no shut
again, this is a very basic configuration! Depending on the piece of equipment you are trying to configure this on... you should do some research on intervlan routing. 9 times out of 10 depending on the equipment, you will find step by step procedures more taylored to your needs
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...