Configure NPV

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: Migrate SAN A to the NPV Design

The following are high-level subtasks that you will perform in this task to migrate N9K-A to function as an NPV switch:

• Enable NPV on N9K-A. This action will make the switch reload and erase most of the configuration.
• Reconfigure the N9K-A and configure interfaces toward MDS to function as NP (Node Proxy) Ports.
• Configure interfaces on MDS toward N9K-A to function as F Ports.
• Investigate how the behavior of N9K-A and MDS changed with the conversion.

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:

You have VLAN 1000 allocated to carry the FCoE traffic. VSAN is already configured on the switch for SAN-A. 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, and Server WWNN.

Tip:
Login using the admin username and the 1234QWer password.
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
==========================
Using keyboard-interactive authentication.
Password:

N9K-A#

• Step 4:

On N9K-A, investigate the FLOGI database and the FCNS database for VSAN 1011.

Tip:
Enter the following commands. Within the FLOGI database, you should see an entry that belongs to the VIC on UCS-A; the interface should be
vFC 1000.
N9K-A# show flogi database
-------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
-------------------------------------------------------------------------
vfc1000 1011 0x3d0000 20:00:00:25:B5:01:01:01 20:00:00:25:B5:01:01:01

You should see an FCNS database populated with pWWNs from a CNA on UCS-A.

N9K-A# show fcns database

VSAN 1011:
------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
------------------------------------------------------------------------
0x5e0000 N 20:00:00:25:B5:01:01:01 (Cisco) scsi-fcp:init fc-gs
<... output omitted ...>

• 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.

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

On MDS, investigate the FLOGI database and FCNS database for VSAN 1011.
 Tip:
In the CLI, use the following commands.
MDS# show flogi database
No flogi sessions found.

You should see an FCNS database populated with pWWNs from a CNA on UCS-A.

MDS# show fcns database

VSAN 1011:
------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
------------------------------------------------------------------------
0x5e0000 N 20:00:00:25:B5:01:01:01 (Cisco) scsi-fcp:init fc-gs
<... output omitted ...>

• Step 8:

On N9K-A, try to enable the NPV-FCoE feature set.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI, use the following commands.

N9K-A# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.
N9K-A(config)# install feature-set fcoe-npv
fcoe-npv feature-set cannot be installed since fcoe feature-set is already installed/enabled(0x40aa002c)

• Step 9:

On N9K-A, try to disable the FCoE feature set.

Tip:
In the CLI, use the no feature-set fcoe command.
N9K-A(config)# no feature-set fcoe
no feature-set fcoe command is allowed only when there is no FC ports configured. Convert all FC ports to Eth and try again

• Step 10:

On N9K-A, convert all Fibre Channel ports to Ethernet.

Tip:
In the CLI use the following commands.
N9K-A(config)# slot 1
N9K-A(config-slot)# port 45-48 type ethernet
Port type is changed. ACTION REQUIRED: Please save configurations and reload the switch

• Step 11:

Save configurations and reload the switch. The switch will take about 5 minutes to reboot. Log back into the switch after it reboots.

Tip:
In the CLI, use the following commands.
N9K-A(config)# copy running-config startup-config
[########################################] 100%
Copy complete, now saving to disk (please wait)...
Copy complete.
N9K-A(config)# reload
This command will reboot the system. (y/n)? [n] y

• Step 12:

Login and disable and uninstall the FCoE feature set. Then save configuration and reload the switch again.

Tip:
Login using the admin username and the 1234QWer password. After logging in, use the following commands.
N9K-A# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
N9K-A(config)# no feature-set fcoe
Feature-set Operation may take up to 30 minutes depending on the size of configuration.

Disabling feature-set. ACTION REQUIRED: Copy the running config to startup and reload the box for the disable to take effect correctly
N9K-A(config)# no install feature-set fcoe
N9K-A(config)# copy running-config startup-config
 [########################################] 100%
Copy complete, now saving to disk (please wait)...
Copy complete.
N9K-A(config)# reload
This command will reboot the system. (y/n)? [n] y

• Step 13:

Login again and install and enable the FCoE-NPV feature set. This will install both Fibre Channel and FCoE-NPV feature sets.

Tip:
Login using the admin username and the 1234QWer password. After logging in, use the following commands.
N9K-A# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
N9K-A(config)# install feature-set fcoe-npv
N9K-A(config)# feature-set fcoe-npv

• Step 14:

On N9K-A, configure ports uplink to the parent switch as Fibre Channel ports. Then save configuration and reload the switch again.

Tip:
In the CLI use the following commands.
N9K-A(config)# slot 1
N9K-A(config-slot)# port 45-48 type fc
Port type is changed. Please reload the switch
N9K-A(config-slot)# copy running-config startup-config
[########################################] 100%
Copy complete, now saving to disk (please wait)...
N9K-A(config-slot)# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y
<... output omitted ...>

• Step 15:

Login again and configure everything as it was before the conversion to NPV, except for the switch port mode on the uplink to MDS; set the switch
port mode of that interface to NP.

Tip:
Login using the admin username and the 1234QWer password. After logging in, use the following commands.
N9K-A# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
N9K-A(config)# interface fc1/47-48
N9K-A(config-if-range)# channel-group 10
fc1/47 fc1/48 added to port-channel 10 and disabled
please do the same operation on the switch at the other end of the port-channel,
then do "no shutdown" at both ends to bring it up
N9K-A(config-if-range)# no shutdown

When it comes to the switch port mode configuration on the upstream interface (to the parent switch, MDS), you should configure the NP mode.

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

N9K-A(config-if)# switchport mode ?
E E port mode
F F port mode
NP NP port mode for N-Port Virtualizer (NPV) only
auto Autosense mode
N9K-A(config-if)# switchport mode np
N9K-A(config-if)# channel mode active

Map your Pod VSAN 1011 to VLAN 1000. Create a vFC interface and bind it to the Ethernet 1/5 interface.

N9K-A(config)# vlan 1000

N9K-A(config-vlan)# fcoe vsan 1011
N9K-A(config-vlan)# interface vfc1000
N9K-A(config-if)# bind interface Ethernet1/5
N9K-A(config-if)# switchport trunk allowed vsan 1011
Warning: This command will remove all VSANs currently being trunked and trunk only the specified VSANs.
Do you want to continue? (y/n) [n] y
N9K-A(config-if)# no shutdown

N9K-A(config-if)# vsan database

N9K-A(config-vsan-db)# vsan 1011
N9K-A(config-vsan-db)# vsan 1011 interface san-port-channel 10
N9K-A(config-vsan-db)# vsan 1011 interface vfc1000

You will notice that some of the commands that were present before the conversion to NPV will not work now. NPV switch does not run all storage
services and does not consume a domain ID.

N9K-A(config-vsan-db)# fcdomain ?
^
% Invalid parameter detected at '^' marker.
N9K-A(config-vsan-db)# zone ?
^
% Invalid parameter detected at '^' marker.
 N9K-A(config-vsan-db)# zoneset ?
^
% Invalid parameter detected at '^' marker.

• Step 16:

To enable trunking and for the FLOGI from NP uplink of Cisco Nexus 9000 Series Switches to be successful on the core switch (MDS), the core
should be configured with the OUI of a Cisco Nexus 9000 Series Switch. Check the OUI of the N9K switch.

Tip:
In the CLI, use the show wwn switch command.
N9K-A(config-vsan-db)# show wwn switch
Switch WWN is 20:00:c0:14:fe:bc:d4:40

• Step 17:

On MDS, check if the OUI (in this example, 0xac4a67) is already registered. If the OUI is not registered with the MDS, configure it manually.

Tip:
Switch to the MDS PuTTY instance.

In the CLI, use the following commands.

MDS# show wwn oui | include c014fe

MDS# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
MDS(config)# wwn oui 0xc014fe

• Step 18:

On MDS, check that the NPIV feature is enabled.

Tip:
In the CLI, use the show feature | include npiv command.
MDS# show feature | include npiv
npiv 1 enabled

• Step 19:

On MDS, configure interfaces fc1/1 and fc1/2 (which connect to your N9K-A) as F Ports.

Because interfaces fc1/1 and fc1/2 are already bundled into port channel 10, you should not perform the configuration on the interface level but
on port channel level. Even more, the switch will not even allow you to perform the configuration on the interface level. Shut down the port and
then re-enable it.

Tip:
In the CLI, use the following commands.
MDS(config)# interface port-channel 10
MDS(config-if)# switchport mode f
MDS(config-if)# channel mode active
MDS(config-if)# shutdown
MDS(config-if)# no shutdown

• Step 20:

On N9K-A, bounce the san-port-channel 10.

Tip:
Switch to the N9K-A PuTTY instance.

In the CLI, use the following commands.

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

N9K-A(config-if)# shutdown
N9K-A(config-if)# no shutdown

• Step 21:

On MDS, verify that the port channel 10 is operational.

 Tip:
Switch to the MDS PuTTY instance.

MDS# show interface port-channel 10

port-channel 10 is up
<... output omitted ...>
Port mode is F
Port vsan is 1011
<... output omitted ...>

You should see that the port channel is up, the mode is F, and VSAN is 1011.

• Step 22:

On N9K-A, verify that the port channel 10 is operational.

Tip:
Switch to the N9K-A PuTTY instance.

N9K-A# show interface san-port-channel 10

san-port-channel 10 is up
<... output omitted ...>
Port mode is NP
Port vsan is 1011
<... output omitted ...>

You should see that port channel is up, the mode is NP, and VSAN is 1011.

• Step 23:

On N9K-A, investigate the status of NPV.

Tip:
In the CLI, use the show npv status command.
N9K-A# show npv status

npiv is disabled

disruptive load balancing is disabled

External Interfaces:
====================
Interface: san-port-channel 10, State: Up
VSAN: 1011, State: Up, FCID: 0xa50000

Number of External Interfaces: 1

Server Interfaces:
==================
Interface: vfc1000, VSAN: 1011, State: Up

Number of Server Interfaces: 1

You should see one external (SAN port channel 10) and one server (vFC 1000) interface listed and operational. External interfaces are
northbound interfaces (connected to MDS) and internal interfaces are southbound interfaces (connected to hosts).

• Step 24:

On N9K-A, investigate the FLOGI database, and the FCNS database.

You will see that N9K-A does not know any of the regular SAN commands, now that you turned it into an NPV switch. The NPV switch will just
proxy all SAN information to the parent switch.

Cisco NPV edge switches are essentially transparent to the fabric, and most Fibre Channel services of the switches are disabled. The switches
do not have domain IDs, so they do not appear in the FSPF routing table. From the perspective of SAN, the target or initiator that is connected to
the NPV edge switch, will appear as directly connected to the NPV core switch.

Tip:
In the CLI, use the following commands.
N9K-A# show flogi database
 ^
% Invalid command at '^' marker.
N9K-A# show fcns database
^
% Invalid command at '^' marker.

• Step 25:

On MDS, investigate the FLOGI database, the FCNS database, and active zoning for VSAN 1011.

Tip:
Switch to the MDS PuTTY instance.

On MDS, you should notice two FLOGI entries through port channel 10. One of the two entries is the N9K-A; remember that you configured the
interfaces on MDS toward N9K-A as F Ports. The other FLOGI entry belongs to the CNA on UCS-A that is connected to N9K-A through interface
Ethernet 1/5.

MDS# show flogi database

---------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
---------------------------------------------------------------------------
port-channel10 1011 0xa10000 24:0a:c0:14:fe:f9:93:20 23:f3:c0:14:fe:f9:93:21
port-channel10 1011 0xa10001 20:00:00:25:b5:01:01:01 20:00:00:25:b5:01:01:01
Total number of flogi = 2.

MDS# show fcns database

VSAN 1011:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x010000 N 24:0a:c0:14:fe:f9:93:20 (Cisco) 229
0x010001 N 20:00:00:25:b5:01:01:01 (Cisco) scsi-fcp:init fc-gs

Total number of entries = 2.

• Step 26:

On N9K-A, investigate the NPV FLOGI table.

Tip:
So while there is no show flogi database command on a NPV-enabled switch, you can use the show npv flogi-table command to see devices
that logged in to the parent switch through the NPV-enabled switch.
N9K-A# show npv flogi-table
--------------------------------------------------------------------------------
SERVER PORT NAME EXTERNAL
INTERFACE VSAN FCID (NODE NAME) INTERFACE
--------------------------------------------------------------------------------
vfc1000 1011 0x010001 20:00:00:25:b5:01:01:01 San-po10
(20:00:00:25:b5:01:01:01)

Total number of flogi = 1.

• Step 27:

Save configuration on the N9K-A switch.

Tip:
In the CLI, use the copy running-config startup-config command.
N9K-A# copy running-config startup-config

• Step 28:

Save configuration on the MDS switch.

Tip:
Switch to the MDS PuTTY instance.

In the CLI, use the copy running-config startup-config command.

MDS# copy running-config startup-config

 • Step 29:

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'.