Data Infrastructure Management Software Discussions

Re: snapmirror multi interfaces not available in PM

Hi there,

Here's a sample demo:

Primary host: sim733a

Preferred IP address 1:                      192.168.34.140
Preferred IP address 2:                      192.168.34.141

Secondary host: sim733b

Preferred IP address 1:                      192.168.34.141
Preferred IP address 2:                      192.168.34.161

Created a relationship through PM:

Portion of job progress messge in PM:

Event Id:      8673
Event Status:  normal
Event Type:    job-progress
Job Id:        870
Timestamp:     18 Oct 2010 19:00:16
Message:       sim733a:/mirror: Using connection sim733a_sim733b_1287442815 (192.168.34.140 -> 192.168.34.141,192.168.34.141 -> 192.168.34.161), id = 1
Error Message:

Event Id:                         8675
Event Status:                     normal
Event Type:                       rel-create-progress
Job Id:                           870
Timestamp:                        18 Oct 2010 19:00:17
Message:                          Set connection to sim733a_sim733b_1287442815 (1)
Error Message:
Source Volume or Qtree Id:        1262
Source Volume or Qtree Name:      sim733a:/mirror
Destination Volume or Qtree Id:   1267

Snapmirror.conf entry

#Regenerated by registry Mon Oct 18 23:15:18 GMT 2010

sim733a_sim733b_1287442815=multi(192.168.34.140,192.168.34.141)(192.168.34.141,192.168.34.161)

sim733a_sim733b_1287443717:mirror sim733b:mirror_mirror connection_mode=inet - - - -

sim733a_sim733b_1287443717=multi(192.168.34.140,192.168.34.141)(192.168.34.141,192.168.34.161)

After create relationship failed the Preferred IP address 1 of secondary host

ns0: flags=0x2408866<BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.34.141 netmask-or-prefix 0xffffff00 broadcast 192.168.34.255
        inet 192.168.34.150 netmask-or-prefix 0xffffff00 broadcast 192.168.34.255
        ether 00:50:56:05:d4:ee (auto-100tx-fd-cfg_down)
ns1: flags=0x2c48867<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.34.161 netmask-or-prefix 0xffffff00 broadcast 192.168.34.255
        ether 00:50:56:06:d4:ee (auto-100tx-fd-up)
lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 9188
        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1

Executed the job: portion of job message in PM:

Event Id:      8720
Event Status:  normal
Event Type:    job-progress
Job Id:        872
Timestamp:     18 Oct 2010 19:15:17
Message:       Using connection sim733a_sim733b_1287443717 (192.168.34.140 -> 192.168.34.141,192.168.34.141 -> 192.168.34.161), id = 2
Error Message:

Event Id:          8722
Event Status:      normal
Event Type:        snapmirror-progress
Job Id:            872
Timestamp:         18 Oct 2010 19:15:18
Message:           Set connection to sim733a_sim733b_1287443717 (2)
Error Message:
Source Id:         1262
Source Name:       sim733a:/mirror
Destination Id:    1267
Destination Name:  sim733b:/mirror_mirror
Bytes Transferred: 0

Job was succesful

So to Adai's point and your point it is multi in the snapmirror.conf, but PM can also perform failover and succesfully complete the job.

Thanks and regards

Shiva Raja

Re: snapmirror multi interfaces not available in PM

That’s what I remembered, its failover between the hostpreferredAddr1 and hostpreferredAddr2 connections.

But with just hostpreferredAddr1 connection its multi.

But Shiva I see that IP addr are same.

Primary host: sim733a

Preferred IP address 1:                      192.168.34.140
Preferred IP address 2:                      192.168.34.141

Secondary host:

Preferred IP address 1:                      192.168.34.141
Preferred IP address 2:                      192.168.34.161

This is the man pages excerpt from ONTAP.

Each connection definition is a single line giving a name to one or two pairs of IP addresses along with a mode of operation for the connection. The lines are specified in the following format:

name = mode( source_ip_addr1 , dest_ip_addr1 ) ( source_ip_addr2 , dest_ip_addr2 )

name This is the name of the connection you would like to define. This name is to be used as the source filer in relationship definitions.

mode The mode is optional and specifies the mode in which two IP address pairs will be used. Two modes are allowed multiplexing and failover mode and are specified by using the multi and failover keywords. If not specified, multiplexing mode is used.

The multiplexing mode causes snapmirror to use both paths at the same time. If one should fail, it will switch to use the remaining path only and use both again should the failing path be repaired.

Failover mode causes snapmirror to use the first path as the desired path and only use the second path should problems arise with the first path.

So that confirms the behaviour of multi when both are specifed, also failover when one of them is not available.

Regards

adai

Forums