Configure Zoning

Note: Be sure to review the Objectives and

Job Aids links above for required
information. Password Information and
Command Lists for Detailed Lab Steps are
in the Job Aids link.

Task 1: Configure Basic Zoning

In this procedure, you will configure zoning for SAN of your storage network.

Show Steps

• Step 1:

Click the Play icon in the middle of the screen or the Play button on the player below the simulation screen to begin the simulation.

Note

If stuck, click the Forward button in the Playbar to continue to the next slide.

Tip:
The following are the Playbar buttons and their functions:
◦ Rewind: Resets the interactive activity.
◦ Play: Plays the interactive activity. In the middle of the interactive activity, it can also be used to go to the next slide.
◦ Back: Go to the previous slide.
◦ Forward: Go to the next slide.

Note

When clicking off the interactive activity, the hover function will stop responding. To fix this, click anywhere in the interactive activity. If the step requires text input, you must also click on the input field
needed for this step (the cursor will change to the text pointer). When using the CLI-based slide, this will usually be just behind the number (#) sign.

• Step 2:

Use PuTTY and choose N9K-A from the preconfigured device list to connect to your N9K-A.

Tip:
Open PuTTY, under Saved Sessions choose the N9K-A option, and click the Open button.
• Step 3:

In the CLI enter the username and password provided in the Job Aid and note down the Pod, VSAN, Server PWWN, Server WWNN, and NetApp PWWN values.

Tip:
Login using the admin username and the 1234QWer password.

Note

The password characters in the activity are rendered as dots, in the actual CLI the password characters are not rendered.

login as: admin

========== Info ==========

Device: N9K-A
Pod: 1
VSAN: 1011
Server PWWN: 20:00:00:25:B5:01:01:01
Server WWNN: 20:00:00:25:B5:01:01:01
NetApp PWWNs:
20:0e:00:a0:98:d5:6c:36 (NetApp1)
20:0f:00:a0:98:d5:6c:36 (NetApp2)
==========================
Using keyboard-interactive authentication.
Password:

N9K-A#

• Step 4:

Examine the device-alias status.

Tip:
In the CLI enter the show device-alias status command.
N9K-A# show device-alias status
Fabric Distribution: Enabled
Database:- Device Aliases 0 Mode: Enhanced
Checksum: 0xb713791d47fd2d205e1a5fa01ea9c447

Device-alias distribution is enabled, mode is enhanced, and the database is empty.

• Step 5:

Use PuTTY to connect to your MDS.

Tip:
Open another PuTTY instance. Under Saved Sessions choose the MDS option and click the Open button.
• Step 6:

In the CLI enter the username and password provided in the Job Aid and note down the Pod, VSAN, Server PWWN, Server WWNN, and NetApp PWWN values.

Tip:
Login using the admin username and the 1234QWer password.
login as: admin

========== Info ==========

Device: MDS
Pod: 1
VSAN: 1011
Server PWWN: 20:00:00:25:B5:01:01:01
Server WWNN: 20:00:00:25:B5:01:01:01
NetApp PWWNs:
20:0e:00:a0:98:d5:6c:36 (NetApp1)
20:0f:00:a0:98:d5:6c:36 (NetApp2)
==========================
Using keyboard-interactive authentication.
Password:

• Step 7:

Examine the device-alias status.

Tip:
In the CLI enter the show device-alias status command.
MDS# show device-alias status
Fabric Distribution : Enabled
Database:- Device Aliases 0 Mode: Enhanced
Checksum: 0xb713791d47fd2d205e1a5fa01ea9c447

You should find the same device-alias status as on the Nexus 9000.

• Step 8:

On N9K-A, examine the pWWN of the C220 server that is logged in to the switch and configure the device alias Server for that server.

Tip:
Switch to the N9K-A PuTTY instance.
N9K-A# show flogi database
-------------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
-------------------------------------------------------------------------------------
vfc1000 1011 0x1c0000 20:00:00:25:B5:01:01:01 20:00:00:25:B5:01:01:01

Total number of flogi = 1.

N9K-A# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
N9K-A(config)# device-alias database
N9K-A(config-device-alias-db)# device-alias name Server pwwn 20:00:00:25:B5:01:01:01
N9K-A(config-device-alias-db)# device-alias commit

You need to commit the device-alias information to be effective.

• Step 9:

On MDS, verify the distribution of the device-alias information, both in the device-alias and in the fcns database.

Tip:
Switch to the MDS PuTTY instance.

In the CLI enter the following commands.

MDS# show device-alias database

device-alias name Server pwwn 20:00:00:25:b5:01:01:01

Total number of entries = 1

MDS# show fcns database

VSAN 1011:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x1c0000 N 20:00:00:25:b5:01:01:01 scsi-fcp:init fc-gs
[Server]

Total number of entries = 1

You should see the device alias in the FCNS database on the MDS.

• Step 10:

On N9K-A, verify that the basic zoning mode is enabled.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the show zone status vsan 1011 command.

N9K-A# show zone status vsan 1011

VSAN: 1011 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
<... output omitted ...>

The basic zoning mode is the default mode on Cisco Nexus switches.

• Step 11:

On MDS, verify that the basic zoning mode is enabled.

Tip:
Switch to the MDS PuTTY instance.

In the CLI use the show zone status vsan 1011 command.

MDS# show zone status vsan 1011

VSAN: 1011 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
<... output omitted ...>

The basic zoning mode is the default mode on MDS switches.

• Step 12:

On N9K-A, configure the zone Server-NetApp for VSAN 1011, and add the device alias Server to it.

To enter the zone configuration mode, use the zone name name vsan vsan command. Then add zone members using the member {pwwn pwwn} {device-alias device-alias} command.

You can use the member ? command to see which identifiers you can use to configure zone members.

Configuration of zoning in its simplest form is similar to an access list that allows communication between servers and storage. That access list is called a zone. After you create a zone, you need to
include it into a container called a zone set. Lastly, you need to activate that zone set. The server will then be able to see the disk on storage and mount that disk.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the show fcns database command.

N9K-A# show fcns database

VSAN 1011:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x1c0000 N 20:00:00:25:b5:01:01:01 scsi-fcp:init fc-gs
[Server]

Total number of entries = 1

N9K-A(config)# zone name Server-NetApp vsan 1011

N9K-A(config-zone)# member device-alias Server

The easiest way to ensure that you correctly define members of a zone is to view the FCNS database and then copy the identifiers (for example, pWWNs, device aliases, FCIDs).

As you can see, pWWNs are not easily readable; device aliases lend themselves better for zoning configuration.

• Step 13:

On N9K-A, add the zone that you created in the previous step to the zone set Zoneset-Server-NetApp.

Each VSAN can have multiple zone sets, but only one zone set can be active at any given time. When you create a zone set, that zone set becomes a part of the full zone database. When you
activate a zone set, a copy of the zone set from the complete zone set is used to enforce zoning. It is called the active zone set. You cannot modify an active zone set. A zone that is part of an active
zone set is called an active zone.

First enter the zone set configuration mode using the zoneset name zoneset_name vsan vsan command. Then, add a member to the zone set using the member zone_name command.

Tip:
In the CLI enter the following commands.
N9K-A(config)# zoneset name Zoneset-Server-NetApp vsan 1011
N9K-A(config-zoneset)# member Server-NetApp

• Step 14:

On N9K-A, investigate the configured and active zones and zoneset.

Tip:
In the CLI enter the following commands.
N9K-A# show zone vsan 1011
zone name Server-NetApp vsan 1011
device-alias Server

N9K-A# show zone active vsan 1011

Zone not present

N9K-A# show zoneset vsan 1011

zoneset name Zoneset-Server-NetApp vsan 1011
zone name Server-NetApp vsan 1011
device-alias Server

N9K-A# show zoneset active vsan 1011

Zoneset not present

You will not see your zone among the active zones because you have not yet activated the zone set.

• Step 15:

On MDS, examine the zoning information.

Tip:
Switch to the MDS PuTTY instance.

In the CLI enter the following commands.

MDS# show zone vsan 1011

Zone not present
MDS# show zone active vsan 1011
Zone not present
MDS# show zoneset vsan 1011
Zoneset not present
MDS# show zoneset active vsan 1011
Zoneset not present

No zoning information has been distributed to the MDS because in basic mode the full zoning information is distributed on demand, as opposed to the automatic distribution in the enhanced mode.

• Step 16:

On N9K-A, configure the distribution of a full zone set for your VSAN.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI enter the zoneset distribute full vsan 1011 command.

N9K-A(config)# zoneset distribute full vsan 1011

Use the zoneset distribute full vsan vsan command to enable the distribution of the full zone set on each activation. By default, switches distribute only the active zone set; you need to explicitly
enable the distribution of the full zone set. This command only distributes the full zone set information, and it does not save the information to the startup configuration. You must explicitly issue the
copy running-config startup-config command to save the full zone set information to the startup configuration.

• Step 17:

On MDS, re-examine the zoning information.

Tip:
Switch to the MDS PuTTY instance.
In the CLI enter the following commands.

MDS# show zone vsan 1011

Zone not present
MDS# show zone active vsan 1011
Zone not present
MDS# show zoneset vsan 1011
Zoneset not present
MDS# show zoneset active vsan 1011
Zoneset not present

No zoning information will be distributed to the MDS until you activate a zoneset.

• Step 18:

On N9K-A, activate your zone set.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the zoneset activate name Zoneset-Server-NetApp vsan 1011 command to activate zone set. You would deactivate the zone set by prepending no to this command.

N9K-A(config)# zoneset activate name Zoneset-Server-NetApp vsan 1011

Zoneset activation initiated. check zone status

If one zone set is active and you activate another zone set, the currently active zone set is automatically deactivated. You do not need to explicitly deactivate the currently active zone set before
activating a new zone set.

After a zone set activation, the switch will distribute the active zone set configuration to other switches in the VSAN, and all switches in the VSAN will enforce the rules of this zone set.

• Step 19:

On N9K-A, validate the active zone in your VSAN.

Tip:
In the CLI use the show zone active vsan 1011 command.
N9K-A# show zone active vsan 1011
zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]

The asterisk tells you that the device has logged in to the fabric. A missing asterisk may indicate an offline device or an incorrectly configured zone, possibly a mistyped pWWN.

• Step 20:

On MDS, examine the configured and active zones in your VSAN.

Tip:
Switch to the MDS PuTTY instance.

In the CLI use the following commands.

MDS# show zone vsan 1011

zone name Server-NetApp vsan 1011
device-alias Server

MDS# show zone active vsan 1011

zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]

MDS# show zoneset vsan 1011

zoneset name Zoneset-Server-NetApp vsan 1011
zone name Server-NetApp vsan 1011
device-alias Server

MDS# show zoneset active vsan 1011

zoneset name Zoneset-Server-NetApp vsan 1011
zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]

You will not see your zone on the MDS if you did not configure the distribution of the full zone set. The output should be identical to N9K-A.

Task 2: Configure Enhanced Zoning

In production networks, it is recommended that you configure enhanced zoning on both SAN A and SAN B. It is also recommended that you configure zoning in a consistent fashion—for example, use device
aliases for all entries on both sides of the SAN. Consistency helps to make documentation clearer and simplifies potential troubleshooting processes.

Show Steps

• Step 1:

On MDS, enable enhanced zoning for your VSAN.

Tip:
In the CLI use the zone mode enhanced vsan 1011 command to change the mode from basic to enhanced.
MDS# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
MDS(config)# zone mode enhanced vsan 1011
WARNING: This command would distribute the zoning database of this switch throughout the fabric. Do you want to continue? (y/n) [n] y
Set zoning mode command initiated. Check zone status

• Step 2:

On MDS, verify the zone mode.

Tip:
In the CLI use the show zone status vsan 1011 command.
MDS# show zone status vsan 1011
VSAN: 1011 default-zone: deny distribute: full Interop: default
mode: enhanced merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
rscn-format: fabric-address
activation overwrite control: disabled
Default zone:
qos: none broadcast: unsupported ronly: unsupported
Full Zoning Database :
DB size: 292 bytes
Zonesets: 1 Zones: 1 Aliases: 0 Attribute-groups: 1
Active Zoning Database :
DB Size: 96 bytes
Name: Zoneset-Server-NetApp Zonesets: 1 Zones: 1
Current Total Zone DB Usage: 388 / 4000000 bytes (0 % used)
Pending (Session) DB size:
Full DB Copy size: 0 bytes
Active DB Copy size: 0 bytes
SFC size: 0 / 4000000 bytes (0 % used)
Status: Set zoning mode complete at 14:02:59 UTC Dec 1 2023

MDS operates now in the enhanced mode, but the change has been propagated to other switches in the VSAN. With the enhanced zoning, entering the zone configuration mode will lock the fabric
within the VSAN.

• Step 3:

On N9K-A, verify the zone mode.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the show zone status vsan 1011 command.

N9K-A# show zone status vsan 1011

VSAN: 1011 default-zone: deny distribute: full Interop: default
mode: enhanced merge-control: allow
session: none
hard-zoning: enabled broadcast: unsupported
smart-zoning: disabled
rscn-format: fabric-address
activation overwrite control: disabled
Default zone:
qos: none broadcast: unsupported ronly: unsupported
Full Zoning Database :
DB size: 292 bytes
Zonesets:1 Zones:1 Aliases: 0 Attribute-groups: 1
Active Zoning Database :
DB size: 96 bytes
Name: Zoneset-Server-NetApp Zonesets:1 Zones:1
Current Total Zone DB Usage: 388 / 2097152 bytes (0 % used)
Pending (Session) DB size:
Full DB Copy size: 0 bytes
Active DB Copy size: 0 bytes
SFC size: 0 / 2097152 bytes (0 % used)
Status: Set zoning mode success at 11:13:33 UTC Dec 1 2023

• Step 4:

On N9K-A, configure the device alias test for a non-existing port WWN.

Tip:
In the CLI use the following commands.
N9K-A(config)# device-alias database
N9K-A(config-device-alias-db)# device-alias name test pwwn 20:00:00:25:b5:00:00:01

• Step 5:

On N9K-A, commit the device alias configuration and verify the device alias database.

Tip:
In the CLI use the following commands.
N9K-A(config-device-alias-db)# device-alias commit
N9K-A(config)# show device-alias database
device-alias name test pwwn 20:00:00:25:b5:00:00:01
device-alias name Server pwwn 20:00:00:25:b5:01:01:01

Total number of entries = 2

• Step 6:

On MDS, verify the device alias database.

Tip:
Switch to the MDS PuTTY instance.
In the CLI use the show device-alias database command.

MDS# show device-alias database

device-alias name test pwwn 20:00:00:25:b5:00:00:01
device-alias name Server pwwn 20:00:00:25:b5:01:01:01

Total number of entries = 2

The device alias has been propagated to the MDS because the device alias mode is enhanced.

• Step 7:

On N9K-A, add the device alias test as a member to your zone Server-NetApp.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the following commands.

N9K-A(config)# zone name Server-NetApp vsan 1011

N9K-A(config-zone)# member device-alias test
Enhanced zone session has been created. Please 'commit' the changes when done.

• Step 8:

On N9K-A, examine the pending and active zone database.

Tip:
The configuration principle with enhanced zoning is very similar to the configuration of enhanced device aliases. The switch will lock the entire fabric and changes do not take effect until you commit
them.

In the CLI use the following commands.

N9K-A# show zone pending vsan 1011

zone name Server-NetApp vsan 1011
device-alias Server
device-alias test

N9K-A# show zone active vsan 1011

zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]
Within your pending zone configuration, you should see two entries. In the active zone database, you should see only one entry, without the device alias test that has yet to be committed.

You could also use the show zone pending-diff command to discover what the differences are between the pending and effective database; similarly as with device aliases.

• Step 9:

On N9K-A, activate the zoneset and commit the changes.

Tip:
In the CLI use the following commands.
N9K-A(config)# zoneset activate name Zoneset-Server-NetApp vsan 1011
N9K-A(config)# zone commit vsan 1011
Commit operation initiated. Check zone status

When you commit the changes, the switch will release the fabric lock for configuring zoning.

You can append the force keyword after the commit command to override a user lock. It is discouraged, however, because this action will erase all configuration written by the user acquiring the
lock.

In addition to locking the fabric for a single user at a time, enhanced zoning offers the advantage of automatic distribution of the full zone set.

• Step 10:

On N9K-A, verify the configured and active zone for your VSAN.

Tip:
In the CLI use the following commands.
N9K-A# show zone vsan 1011
zone name Server-NetApp vsan 1011
device-alias Server
device-alias test

N9K-A# show zone active vsan 1011

zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]
device-alias test

• Step 11:

On MDS, verify the configured and active zone for your VSAN.

Tip:
Switch to the MDS PuTTY instance.

In the CLI use the following commands.

MDS# show zone vsan 1011

zone name Server-NetApp vsan 1011
device-alias Server
device-alias test

MDS# show zone active vsan 1011

zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]
device-alias test

The zone and active zone information has been propagated throughout the VSAN. Optionally, check the same information for zoneset. It will be identical across both switches.

Task 3: Resolve Zoning Merger Failures

In this procedure, you will intentionally create a zone merger failure between your MDS and N9K-A and then resolve it. You will also resolve a zone merger failure between your MDS and the core MDS, induced
by the lab automation system.

Show Steps

• Step 1:

On N9K-A, shut down the SAN port channel connecting to the MDS.

Tip:
Switch to the N9K-A PuTTY instance.
In the CLI use the following commands.

N9K-A(config)# interface san-port-channel 10

N9K-A(config-if)# shutdown

Shutting down SAN port channel will also operatively bring down member interfaces. Having disconnected the N9K-A away from the MDS, you will make a change to an existing member of your
zone. After reconnecting the N9K-A to the MDS, the two switches will have different active databases and the inconsistency will create a merger conflict.

• Step 2:

On N9K-A, configure the device alias Conflict for another unused pWWN.

Tip:
In the CLI use the following commands.
N9K-A(config-if)# device-alias database
N9K-A(config-device-alias-db)# device-alias name Conflict pwwn 20:00:00:25:b5:00:00:02
N9K-A(config-device-alias-db)# device-alias commit
N9K-A(config)# show device-alias database
device-alias name test pwwn 20:00:00:25:b5:00:00:01
device-alias name Server pwwn 20:00:00:25:B5:01:01:01
device-alias name Conflict pwwn 20:00:00:25:b5:00:00:02

Total number of entries = 3

• Step 3:

On N9K-A, add the device alias to your zone.

Tip:
In the CLI use the following commands.
N9K-A(config)# zone name Server-NetApp vsan 1011
N9K-A(config-zone)# member device-alias Conflict
Enhanced zone session has been created. Please 'commit' the changes when done.

• Step 4:

On N9K-A, activate your zoneset and commit the zone changes for the VSAN.

Tip:
In the CLI use the following commands.
N9K-A(config)# zoneset activate name Zoneset-Server-NetApp vsan 1011
N9K-A(config)# zone commit vsan 1011
Commit operation initiated. Check zone status

• Step 5:

On N9K-A, bring the SAN port channel back up.

Tip:
In the CLI use the following commands.
N9K-A(config)# interface san-port-channel 10
N9K-A(config-if)# no shutdown

• Step 6:

Wait about 2 minutes to examine the information available in the output of the show logging last 10 command.

Tip:
Use the show logging last 10 command.
N9K-A(config-if)# show logging last 10
<... output omitted ...>
N9K-A %ZONE-2-ZS_MERGE_FAILED: %$VSAN 1011%$ Zone merge failure, isolating interface san-port-channel10 received reason: Member mismatch Received rjt from adjacent switch:[reason:0]
N9K-A %PORT-5-IF_TRUNK_DOWN: %$VSAN 1011%$ Interface san-port-channel10, vsan 1011 is down (Isolation due to zone merge failure)
<... output omitted ...>

The switch will isolate the interface SAN port channel and also tell you the reason for this merger failure. You can verify the same results on the MDS.

• Step 7:

On N9K-A, examine the trunking status of the SAN port channel.

Tip:
In the CLI use the show interface san-port-channel 10 command.
N9K-A(config-if)# show interface san-port-channel 10
san-port-channel10 is trunking (Not all VSANs UP on the trunk)
Hardware is Fibre Channel
Port WWN is 24:0a:ac:4a:67:de:69:e0
Admin port mode is E, trunk mode is on
snmp link state traps are enabled
Port mode is TE
Port vsan is 1011
Speed is 16 Gbps
Trunk vsans (admin allowed and active) (1,1011)
Trunk vsans (up) (1)
Trunk vsans (isolated) (1011)
Trunk vsans (initializing) ()
<... output omitted ...>

Your VSAN will be isolated.

• Step 8:

On N9K-A, resolve the merger failure by importing the zone set from MDS.

Tip:
In the CLI use the zoneset import interface san-port-channel 10 vsan 1011 command.
N9K-A(config-if)# zoneset import interface san-port-channel 10 vsan 1011

Wait up to one minute for the Cisco Nexus switch to import and activate the zone set. Meanwhile, if you examine the trunk, you will see the trunk VSAN status as initializing.

Alternatively, you could use the zoneset export vsan command on the exporting switch, or manually correct the zoning information.

• Step 9:

On N9K-A, re-examine the SAN port channel.

Tip:
In the CLI use the show interface san-port-channel 10 command.
N9K-A(config-if)# show interface san-port-channel 10
san-port-channel10 is trunking
Hardware is Fibre Channel
Port WWN is 24:0a:ac:4a:67:de:69:e0
Admin port mode is E, trunk mode is on
snmp link state traps are enabled
Port mode is TE
Port vsan is 1011
Speed is 16 Gbps
Trunk vsans (admin allowed and active) (1,1011)
Trunk vsans (up) (1,1011)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
<... output omitted ...>

Your VSAN should be up instead of being isolated.

• Step 10:

On N9K-A, investigate the active zone set for your VSAN.

Tip:
In the CLI use show zone active vsan 1011 command.
N9K-A(config-if)# show zone active vsan 1011
zone name Server-NetApp vsan 1011
* fcid 0x1c0000 [device-alias Server]
device-alias test

The device alias Conflict is gone because the import action has overwritten the previous zone set on N9K-A.

• Step 11:

On MDS, verify the state of the interface fc1/3, which connects your MDS to the core MDS.

Tip:
Switch to the MDS PuTTY instance.

In the CLI use the show interface fc1/3 command.

MDS# show interface fc1/3

fc1/3 is down (Isolation due to zone merge failure)
Port description is Connects to MDS-CORE
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:03:00:3a:9c:54:3d:f0
Admin port mode is E, trunk mode is auto
snmp link state traps are enabled
Port vsan is 1011
<... output omitted ...>

The interface is down due to zone merge failure. You will resolve it by importing the zoninng information from the core MDS.

• Step 12:

On MDS, resolve the merger failure by importing the zone set from the core MDS and verify the active zoneset on the MDS.

Tip:
In the CLI use the zoneset import interface fc1/3 vsan 1011 command.
MDS# zoneset import interface fc1/3 vsan 1011

• Step 13:

On MDS, wait about 30 seconds and verify the active zoneset.

Tip:
In the CLI use the show zoneset active vsan 1011 command.
MDS# show zoneset active vsan 1011
zoneset name Zoneset-Host-NetApp vsan 1011
zone name Host-NetApp vsan 1011
* fcid 0x910000 [pwwn 20:00:00:25:b5:01:01:01] [Server]
pwwn 20:00:00:25:b5:01:01:10
* fcid 0x0b49aa [pwwn 20:0e:00:a0:98:d5:6c:36]
* fcid 0x0b4aaa [pwwn 20:0f:00:a0:98:d5:6c:36 ]

zone name IVRZ_EG01-Pod01 vsan 1011

* fcid 0x910000 [pwwn 20:00:00:25:b5:01:01:01] [Server]
* fcid 0x0b49aa [pwwn 20:0e:00:a0:98:d5:6c:36]
* fcid 0x0b4aaa [pwwn 20:0f:00:a0:98:d5:6c:36]

The previous zone (Server-NetApp) and zoneset (Zoneset-Server-NetApp) has been wiped out and overwritten by the zoning information pulled from the core MDS.

• Step 14:

On N9K-A, verify the active zoneset.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI use the show zoneset active vsan 1011 command

N9K-A# show zoneset active vsan 1011

zoneset name Zoneset-Host-NetApp vsan 1011
zone name Host-NetApp vsan 1011
* fcid 0x910000 [pwwn 20:00:00:25:b5:01:01:01] [Server]
pwwn 20:00:00:25:b5:01:01:10
* fcid 0x0b49aa [pwwn 20:0e:00:a0:98:d5:6c:36]
* fcid 0x0b4aaa [pwwn 20:0f:00:a0:98:d5:6c:36 ]

zone name IVRZ_EG01-Pod01 vsan 1011

* fcid 0x910000 [pwwn 20:00:00:25:b5:01:01:01] [Server]
* fcid 0x0b49aa [pwwn 20:0e:00:a0:98:d5:6c:36]
* fcid 0x0b4aaa [pwwn 20:0f:00:a0:98:d5:6c:36]

The imported zoning information includes an IVR zone (IVRZ_EG01-Pod1) and a regular zone (Host-NetApp). Each zone contains the port WWNs of your C220 server and NetApp.

Task 4: Verify Visibility of NetApp Storage from the ESXi Server

NetApp storage is preconfigured with logical unit numbers (LUNs) for you to test if your server can now see the NetApp disks.

Show Steps

• Step 1:

Open a web browser and go to https://10.10.1.100. Accept any security warnings and log in as root with password 1234QWer.

Tip:
In the address bar enter the https://10.10.1.100 URL.

Click the Advanced button and then click the Proceed to 10.10.1.100 (unsafe) link.
Enter the root user name and 1234QWer password.

• Step 2:

In the vSphere Web client, navigate to Storage > Devices. You should see 2 entries, NETAPP iSCSI Disk and NETAPP Fibre Channel Disk.

Tip:
From the navigation pane, navigate to Storage and choose the Devices tab.
In addition to the initial NETAPP iSCSI Disk, the ESXi should discover (assuming that you correctly configured storage networking in the previous two procedures) a LUN representing the logical disk
on NetApp storage. It should appear as NETAPP Fibre Channel Disk. This newly discovered LUN will not be automatically added to the Datastores. You will configure the datastore manually.

• Step 3:

Navigate to Storage > Datastores and click the New Datastore button.

Tip:
Click the Datastores tab and click the New Datastore button.
• Step 4:

In the New Datastore wizard, in the Select creation type window, choose Create new VMFS datastore and click Next.

Tip:
Click the Create new VMFS datastore option and click the Next button.

• Step 5:

In the New Datastore wizard, in the Select device window, enter the datastore name and click the Next button. Use LUN Datastore as the datastore name.

Tip:
Enter the LUN Datastore datastore name and click the Next button.
• Step 6:

Leave the Use full disk and VMFS-6 option and click the Next button.

Tip:
Leave the default values and click the Next button.

• Step 7:

Check the summary and finish the configuration.

Tip:
Click the Finish button.
• Step 8:

Confirm the disk erasure.

Tip:
Click the Yes button.

• Step 9:

Verify that the new datastore has appeared in the list.

Tip:
LUN Datastore should appear in the list.
The successful configuration of the datastore completes this lab activity.

• Step 10:

You have completed the lab activity. Click the Finish button to go to the Summary slide.

Tip:
Click the Finish button.

Lab Completion Instructions

You have now completed this lab exercise.
Please click 'End Session'.

Choose 'Exit'.