ONTAP Discussions

Zoning made using physical wwpn

leaqui

Hi all,

 

Well, all the set up seems ok, but the tape backup simply doesn't run from the new nodes. Node1 and Node2 are working fine.

From the storage I can see the mc and tapes, from the backup app I can connect to the nodes.

But I was checking and I found this:

node port wwnn wwpn
------------ ---- ---- ----
node1 4a 20:00:00:0e:1e:17:xx:xx 21:00:00:0e:1e:17:xx:xx
node2 4a 20:00:00:0e:1e:17:xx:xx 21:00:00:0e:1e:17:xx:xx
node3 0e 50:0a:09:82:0b:4b:xx:xx 50:0a:09:82:0b:4b:xx:xx
node4 0e 50:0a:09:82:0b:4c:xx:xx 50:0a:09:82:0b:4c:xx:xx

 

You must use the WWPNs of the target LIFs, not the WWPNs of the physical FC ports on the storage nodes. The LIF WWPNs are all in the range 2x:xx:00:a0:98:xx:xx:xx, where x is any hexadecimal digit. The physical port WWPNs are all in the range 50:0a:09:8x:xx:xx:xx:xx

 

Apparently I need to create a LIF to the storage port 0e on node3 and node4?

I can just find docs to create a LIF into network ports, but now a storage port, so would anyone be able to assist please?

5 REPLIES 5

Re: Zoning made using physical wwpn

Ontapforrum

Hi,

 

Process of creating a data LIF is same: You can use these commands.

 

::> network interface create -vserver <vserver_name> -lif <lif1> -role data  -data-protocol fcp -home-node node3 -home-port 0e


::> network interface create -vserver <vserver_name> -lif <lif2> -role data  -data-protocol fcp -home-node node4 -home-port 0e

 

In the above command: Network address of 0e will be 2x:xx:blah:blah

This command will display it.
::> network interface show -vserver <vserver_name>

 

Note (Extract from NetApp docs): In cDOT/ONTAP, you must use the WWPNs of the target LIFs, not the WWPNs of the physical FC ports on the storage nodes.The LIF WWPNs are all in the range 20:xx:00:a0:98:xx:xx:xx, where x is any hexadecimal digit.The physical port WWPNs are all in the range 50:0a:09:8x:xx:xx:xx:xx.. If you do not see LIF WWPNs logged into the FC switch, but you do see the physical WWPNs, then you do not have NPIV enabled. cDOT uses NPIV in order to map WWPNs of different vservers to the same physical port. As per SAN best practices, it is advisable to create single initiator zones that contain the LIF WWPNs, not the vserver WWNN.

 

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.exp-fc-cpg%2FGUID-9D2AAC92-A160-4C01-B381-C6892342E071.html

 

Thanks!

Re: Zoning made using physical wwpn

leaqui

Hi, thank you for your assistance with this.

 

The problem is that for node1 and node2 I can't see any LIF configured for this.(we just use FCP to our tape backups)

cluster1::> network interface show -vserver * -role data -data-protocol fcp
There are no entries matching your query.

 

Also, the connection is not to a SVM but to the node.  So I'm unable to create a LIF to a node port.

 

Any suggestion?

 

 

Re: Zoning made using physical wwpn

Ontapforrum

In your case : Is Filer FC initiator port is connected to Library via FC switch (zonned) ?

 

Could you give us this output:

::> network interface show
::> node run -node <node1/2> -command fcp topology show
::> storage tape show
::> storage tape show-media-changer
::> network port show

::> fcp adapter show

 

Also, is this the first time you are trying to configure NDMP tape backups on NetApp FIler ?

 

Which is the backup software ?

Re: Zoning made using physical wwpn

leaqui

Hi!

 

Yeah, this is the first time I'm doing it.

The software is NetBackup 7.6

Yes, we have a brocade FC switch in the middle

 

 

cluster1::> node run -node node1 -command fcp topology show
fcp not found. Type '?' for a list of commands


cluster1::> storage tape show


Device ID: sw300:0.126
Device Type: tape drive
Description: IBM LTO-6 ULTRIUM

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 st5 ready-write-enabled normal
node3 st2 ready-write-enabled normal
node4 st4 ready-write-enabled normal


Device ID: sw300:0.126L1
Device Type: media changer
Description: QUANTUM Scalar i40-i80

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 mc0 available normal
node3 mc0 available normal
node4 mc0 available normal


Device ID: sw300:1.126
Device Type: tape drive
Description: IBM LTO-6 ULTRIUM

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 st6 ready-write-enabled normal
node3 st0 ready-write-enabled normal
node4 st3 ready-write-enabled normal


Device ID: sw300:2.126
Device Type: tape drive
Description: IBM LTO-6 ULTRIUM

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 st7 ready-write-enabled normal
node3 st1 ready-write-enabled normal
node4 st1 ready-write-enabled normal


Device ID: sw300:3.126
Device Type: tape drive
Description: IBM LTO-6 ULTRIUM

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 st8 ready-write-enabled normal
node3 st3 ready-write-enabled normal
node4 st2 ready-write-enabled normal


Device ID: sw300:4.126
Device Type: tape drive
Description: IBM LTO-6 ULTRIUM

Node Alias Device State Status
-------------------------- ----- ------------------------ ------
node2 st10 ready-write-enabled normal
node3 st4 ready-write-enabled normal
node4 st0 ready-write-enabled normal
18 entries were displayed.


cluster1::> storage tape show-media-changer

Media Changer: sw300:0.126L1
Description: QUANTUM Scalar i40-i80
WWNN: 5:003:08c38d:1bxxxx
WWPN: 5:003:08c38d:1bxxxx
Serial Number: xxxx

Errors: -

Paths:
Node Initiator Alias Device State
--------------------------- --------- ----- ------------------------
node2 4a mc0 available
node3 0e mc0 available
node4 0e mc0 available
3 entries were displayed.


cluster1::> network port show

Node: node1
Speed(Mbps) Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a Default - up 9000 auto/- healthy
a0a-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0a-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0a-29 Default 10.1.29.0/24 up 1500 auto/- healthy
a0b Default - up 9000 auto/- healthy
a0b-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0b-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0b-29 Default 10.1.29.0/24 up 1500 auto/- healthy
e0M Default 10.1.32.0/24 up 1500 auto/1000 healthy
e0a Cluster Cluster up 9000 auto/10000 healthy
e0b Default - up 9000 auto/10000 healthy
e0c Cluster Cluster up 9000 auto/10000 healthy
e0d Default - up 9000 auto/10000 healthy
e0e Cluster Cluster down 9000 auto/- -
e0f Default - down 9000 auto/- -
e0g Cluster Cluster down 9000 auto/- -
e0h Default - down 9000 auto/- -
e0i Default - up 9000 auto/1000 healthy
e0j Default - up 9000 auto/1000 healthy
e0k Default - up 9000 auto/1000 healthy
e0l Default - up 9000 auto/1000 healthy

Node: node2
Speed(Mbps) Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a Default - up 9000 auto/- healthy
a0a-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0a-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0a-29 Default 10.1.29.0/24 up 1500 auto/- healthy
a0b Default - up 9000 auto/- healthy
a0b-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0b-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0b-29 Default 10.1.29.0/24 up 1500 auto/- healthy
e0M Default 10.1.32.0/24 up 1500 auto/1000 healthy
e0a Cluster Cluster up 9000 auto/10000 healthy
e0b Default - up 9000 auto/10000 healthy
e0c Cluster Cluster up 9000 auto/10000 healthy
e0d Default - up 9000 auto/10000 healthy
e0e Cluster Cluster down 9000 auto/- -
e0f Default - down 9000 auto/- -
e0g Cluster Cluster down 9000 auto/- -
e0h Default - down 9000 auto/- -
e0i Default - up 9000 auto/1000 healthy
e0j Default - up 9000 auto/1000 healthy
e0k Default - up 9000 auto/1000 healthy
e0l Default - up 9000 auto/1000 healthy

Node: node3
Speed(Mbps) Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a Default - up 9000 auto/- healthy
a0a-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0a-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0a-29 Default 10.1.29.0/24 up 1500 auto/- healthy
e0M Default 10.1.32.0/24 up 1500 auto/1000 healthy
e0a Cluster Cluster up 9000 auto/10000 healthy
e0b Cluster Cluster up 9000 auto/10000 healthy
e0c Default - up 9000 auto/10000 healthy
e0d Default - up 9000 auto/10000 healthy

Node: node4
Speed(Mbps) Health
Port IPspace Broadcast Domain Link MTU Admin/Oper Status
--------- ------------ ---------------- ---- ---- ----------- --------
a0a Default - up 9000 auto/- healthy
a0a-20 Default 10.1.20.0/24 up 1500 auto/- healthy
a0a-21 Default 10.1.21.0/24 up 1500 auto/- healthy
a0a-29 Default 10.1.29.0/24 up 1500 auto/- healthy
e0M Default 10.1.32.0/24 up 1500 auto/1000 healthy
e0a Cluster Cluster up 9000 auto/10000 healthy
e0b Cluster Cluster up 9000 auto/10000 healthy
e0c Default - up 9000 auto/10000 healthy
e0d Default - up 9000 auto/10000 healthy
60 entries were displayed.


cluster1::> fcp adapter show
(network fcp adapter show)
Connection Port Admin Operational
Node Adapter Established Address Status Status
------------ ------- ----------- --------- ------- -----------------------
node1 0e false 0 up link not connected
node1 0f false 0 up link not connected
node1 0g false 0 up link not connected
node1 0h false 0 up link not connected
node2 0e false 0 up link not connected
node2 0f false 0 up link not connected
node2 0g false 0 up link not connected
node2 0h false 0 up link not connected
node3 0c false 0 up link not connected
node3 0d false 0 up link not connected
node4 0c false 0 up link not connected
node4 0d false 0 up link not connected
12 entries were displayed.

 

Re: Zoning made using physical wwpn

Ontapforrum

Thanks for sharing the info.

 

We need '3' components here:
1) NDMP host (NetApp Filer)
2) Netbackup server 7.6 (Media Server)
3) Fabric Zoned Library & Tape Drives.

 

I see 'Tape Drive' and 'Robotic Arm (Medium Changer) are seen from NetApp console, so they are zoned properly.

 

Next thing, is to 'Detect/Configure Device', this part is usually run by the Backup Software support. Usually, Backup software support representatives are better equipped to help configure it via backup software. However, it is not very difficult.

 

For you:  NMDP host & Netbackup Media Server are both Fabric zoned I suppose. Next thing is to 'scan/detect' from your Media Server.  Let us know how it goes, if it error's or complains ?


Follow Page 74 onwards:
Using the NetBackup Device Configuration Wizard for NDMP hosts.

Have attached 7.6 guide, which I downloaded from google.

 

Thanks!

View solution in original post

Earn Rewards for Your Review!
GPI Review Banner
All Community Forums
Public