This process was working as of yesterday. Had an issue on the server and had to reboot and now I'm getting this odd error. This is a linux host running RHEL 5.2. It's connecting to a 3270 running 8.0.2P3.
This linux server has a script that connects to 2 luns, each on different filers. Both filers give the same error when running the command below:
[root@server bin]# snapdrive snap connect -lun data/disk disk_2012-04-17 -snapname filer:/vol/volume/data/disk:daily-2012-04-17
connecting filer:/vol/volume/data/disk: creating unrestricted volume clone filer:/vol/lun_data ... success
mapping new lun(s) ... done discovering new lun(s) ... *failed*
Cleaning up ... - LUN filer:/vol/lun_data/disk__2012-04-17 ... deleted - deleting volume clone ... filer:/vol/rootdb_data done 0001-476 Admin error: Unable to discover the device associated with filer:/vol/data/disk_2012-04-17. If multipathing in use, there may be a possible multipathing configuration error. Please verify the configuration and then retry.
Multipathing was not previously in use on this server. I tried this with and without multipathd running.
Anyone know what might be causing this?
"dan_j_finn" == Dan Finn dan_j_finn@yahoo.com writes:
dan_j_finn> [root@server bin]# snapdrive snap connect -lun data/disk dan_j_finn> disk_2012-04-17 -snapname filer:/vol/volume/data/disk:daily-2012-04-17
dan_j_finn> connecting filer:/vol/volume/data/disk: creating dan_j_finn> unrestricted volume clone filer:/vol/lun_data ... success dan_j_finn> mapping new lun(s) ... done dan_j_finn> discovering new lun(s) ... *failed*
dan_j_finn> Anyone know what might be causing this?
Check your routing tables? We ran into that same error last week while setting up a LUN on a slightly odd network (i.e. all storage data going across a different interface that wasn't the default route). We fixed (?) it by tweaking the -mgmtpath setting:
snapdrive config set -mgmtpath <filer-other-interface> <filer-name>
K.
It actually ended up being an iscsi issue. I had to run iscsiadm to log into each filer. It's back to working normally now.
On Apr 18, 2012, at 6:03 AM, fubar@pir.net (Kendall Libby) wrote:
"dan_j_finn" == Dan Finn dan_j_finn@yahoo.com writes:
dan_j_finn> [root@server bin]# snapdrive snap connect -lun data/disk dan_j_finn> disk_2012-04-17 -snapname filer:/vol/volume/data/disk:daily-2012-04-17
dan_j_finn> connecting filer:/vol/volume/data/disk: creating dan_j_finn> unrestricted volume clone filer:/vol/lun_data ... success dan_j_finn> mapping new lun(s) ... done dan_j_finn> discovering new lun(s) ... *failed*
dan_j_finn> Anyone know what might be causing this?
Check your routing tables? We ran into that same error last week while setting up a LUN on a slightly odd network (i.e. all storage data going across a different interface that wasn't the default route). We fixed (?) it by tweaking the -mgmtpath setting:
snapdrive config set -mgmtpath <filer-other-interface> <filer-name>
K. _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Dan Finn -
fubar＠pir.net