HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

316 of 739
Firewall configuration
If you have not done so already, launch the Storage Mirroring Console.
If your source and target are on opposite sides of a NAT or firewall, you will need to
configure your hardware to accommodate Storage Mirroring Recover communications.
You must have the hardware already in place and know how to configure the hardware
ports. If you do not, see the reference manual for your hardware.
In a NAT or firewall environment, you must have a static mapping where a single,
internal IP address is always mapped in a one-to-one correlation to a single, external IP
address. Storage Mirroring Recover cannot handle dynamic mappings where a single,
internal IP address can be mapped to any one of a group of external IP addresses
managed by the router.
Storage Mirroring Console ports
You will need to verify that the following ports are open for Storage Mirroring Recover
communications:
Product Port
Storge Mirroring 6320
Storage Mirroring Recover Virtual Recovery Assistant for Hyper-V 6330
Storage Mirroring Recover for Hyper-V 6332
Storage Mirroring Recover uses ICMP pings to monitor the source for failover. A failover
monitor will not be created if ICMP is blocked (although the data and system state will
still be protected). You should configure your hardware to allow ICMP pings between the
source and target. If you cannot, you will have to monitor for a failure manually and
create a dummy monitor at failover time that can be manually failed over. Contact
technical support for assistance with this manual process.
Microsoft Windows ports
Storage Mirroring Recover uses WMI (Windows Management Instrumentation) which
uses RPC (Remote Procedure Call). By default, RPC will use ports at random above
1024, and these ports must be open on your firewall. RPC ports can be configured to a
specific range by specific registry changes and a reboot. See the Microsoft Knowledge
Base article 154596 for instructions.
Storage Mirroring Recover also relies on other Microsoft Windows ports.
● Microsoft File Share uses ports 135 through 139 for TCP and UDP
communications.