Preferred: Remote access (from my office) to an HMC in remote datacenters
(50+ miles and 200+ miles)
Built-in redundancy.
Also allow HMC's to network so either location can support the other....
i.e.
your office-----HMCNETWORK
/ \
HMC#1 <--> HMC#2
HTH,
<snip>
Any reason to prefer one setup over the other?
Local (my office) HMC connected to remote datacenters (50+ miles and 200+ miles)
Remote access (from my office) to an HMC in remote datacenters (50+ miles and
200+ miles)
I'm going to have 2 datacenters (200+ miles apart) in CoLo providers Closest
datacenter will be within 50 miles of the office where I work Intent is to have
only "smart" third party support access to the datacenter (for
racking/cabling/rebooting) Mainframe activity (IPL/POR) to take place remotely
with fallback to "smart" third party support if needed.
Rack space will be at a premium so they don't want to waste it on an HMC if
they can avoid it.
</snip>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
