Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
protection manager mirror relationship goes to non-conformant status

2010-03-11
01:51 AM
3,526 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
While trying to setup a mirror relationship at the volume level and trying to conform the relationship,
Here is the setup :
SourceSystem: fas980-rtp7
Destination System: fas980-rtp8
SourceVol: new_src
DestinationVol:new_dst
The hostnames of both the storages are resolved and pingable from the windows host which is running the netapp management console.
please let me know if i am missing something during this setup.
Best Regards
sarbjit
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try to ping the source system fas980-rtp7 from Destination System: fas980-rtp8 with its hostname fas980-rtp7.
If it's not reachable, try adding an entry in the /etc/hosts file to locally resolve it on the destination filer.
Regards
adai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Adai,
Yes,the ping works successfully to the destination and vice versa.The entries already exist on the source and destination on the /etc/hosts.
Have added the entries in the "hosts" file on windows server running PM too.
have tried SM on another source & destination volume pair on the same storage systems using the "snapmirror initialize" and it works perfectly.
best regards,
sarbjit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sarbjit --
Adai is on the right track. The issue is the two storage systems talking to each other -- changing anything on the DFM station won't make a difference.
Try double-checking the snapmirror.access list on the source filer. Perhaps it is denying access. You can do this with the host diagnose wizard in NMC.
-- Pete
