We have two Data Centers, East and West. The West is considered our DR site (separate, but identical Hw). If the EDC data center craters, we would like to spin up the WDC using the EDC's Master System config.
Currently we are using a tool to pull the System config by running 'copy run disk0:/MasterSystem.cfg. Below is the Context for ITAM, from a 'sh run' vs a 'copy run disk0:/..' Is there a issue with the 'mac-address auto' lines when using this config on a separate Hw Cluster at the WDC, or should we only use the 'sh run' config (and thus no 'mac-address' statements).
Below, is a portion of the Systems config showing only the context definition
sh run
context ITAM-SF-EDC
allocate-interface Management0/0 oob
allocate-interface Port-channel9.1500 outside
allocate-interface Port-channel9.1501 inter_agency
allocate-interface Port-channel9.1502 intra_agency
allocate-interface Port-channel9.1503 dmz
allocate-interface Port-channel9.1504 inside
config-url disk0:/ITAM-SF-EDC.cfg
copy run disk0:/
context ITAM-SF-EDC
allocate-interface Management0/0 oob
mac-address auto Management0/0 a2ae.0800.001c a2ae.0800.001d
allocate-interface Port-channel9.1500 outside
mac-address auto Port-channel9.1500 a2ae.0800.001e a2ae.0800.001f
allocate-interface Port-channel9.1501 inter_agency
mac-address auto Port-channel9.1501 a2ae.0800.0020 a2ae.0800.0021
allocate-interface Port-channel9.1502 intra_agency
mac-address auto Port-channel9.1502 a2ae.0800.0022 a2ae.0800.0023
allocate-interface Port-channel9.1503 dmz
mac-address auto Port-channel9.1503 a2ae.0800.0024 a2ae.0800.0025
allocate-interface Port-channel9.1504 inside
mac-address auto Port-channel9.1504 a2ae.0800.0026 a2ae.0800.0027
config-url disk0:/ITAM-SF-EDC.cfg
Dan Schauss
