My major concern is IP address conflicts. Right now, with my offline network,
it's completely isolated, with the UCS solution, unless I buy a UCS server(s)
that is sized accordingly to hold the VMs sized for my production environment
(which is unlikely), I'll have to consider feeding the UCS
I've found it useful to put your duplicate network behind separate NAT
router.
Create a L2 (only L2, no L3 interface) VLAN on your production network,
call it "Isolated"
Pick a L2/L3 network that can be your NAT "outside" This network should
be fully reachable in the enterprise and have
My preferred approach is to leverage a CSR1000v to do all the routing and then
NAT that traffic out to the network. In the art of transparency, I am currently
an architect for a Lab as a Service (LaaS) style service, and migrations is one
of the primary use cases. Once the migration is done in
I have two approaches;
If I am remote I'll spinup a linux vm for dns, dhcp and sftp service on a
seperate port group this all assuming everything is on one network
segment. If I am crossing network boundaries i'll throw in a cloud services
router or something.
If I am onsite, I have an
my Cisco EOL RSS feed sprung back to life over the last week or so
still no CCM hot issues though. :(
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354
le...@uoguelph.ca
