I am in the process of migrating clients from 192.168. IPs over to 172.
The way I have figured I would do this is to migrate the current L3 address on the VLAN (using SVI's) to the new 172 address and then use the existing 192.168. as a secondary L3, in order to not cause disruption and allow clients already with a 192.168 address pointing to the 192.168 gateway to maintain connectivity.
However, one problem would be printers etc with reserved IP's in the 192.168 range - if these were to be rebooted and ask DHCP for an address again they will receive a 172. address, as the MLS will forward to DHCP using the primary L3 address on the SVI. I have tested this theory and a client regardless of having a reservation in the 192.168 scope receives a new address in the 172 scope.
Is there a way of informing DHCP to issue out reserved IPs from one scope relating to the secondary L3 on the SVI for some devices?
My alternative would be to create a new VLAN (legacy-vlan) for each scope I am migrating and keep this in the 192.168 range and assign switch ports to this legacy vlan for printers, though this increases management burden!
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...