Latest buzzword is Cloud Computing
Utility Computing, Grid Computing, Cluster Computing, Distributed Computing, Provisioning, Application Service Providers, Software as a Service, Hardware as a Service and Software Oriented Architecture
Process Area Networking/Virtualization.
2009 will be the year of Cloud computing! These helps
you improve elasticity of your network/computer/IT
meanwhile having high security.
http://blogs.zdnet.com/BTL/?p=8199
* Deployment speed. One big hang-up for enterprises is figuring out how to procure and provision infrastructure to support a new application. In other words, you can develop an application in two weeks, but wait six weeks to procure and then install the servers that support it. Toss in capacity planning and the time to market expands more.
* Costs. To acquire those additional servers to support a new app requires budget. Staten notes you can’t just run out and buy a server anymore.
* Businesses want fast prototypes. Corporations can deliver faster prototypes by using cloud computing services. Simply put, it makes sense to use cloud computing as a testbed for projects that don’t have a fully-baked business case. For instance, research and development projects, low priority business applications and collaboration services are all good candidates for the cloud.
http://i.zdnet.com/blogs/forr.png
Monday, January 26, 2009
Wednesday, December 3, 2008
Telepresence.
It is close to OMNIpresence, you are present in every location geographically apart,
if you want to be. Couple of senses are fed - visual and audio. - Visual Networking.
The revolution of phone is taken to next level. With Telepresence booths, which
brings similar to phone booths --- public telepresence .. and also service provider
telepresence. You can reduce travel.
cisco Telepresence
Using the system itself, Cisco says its employees have avoided travel to more than 16,000 meetings, saving the company more than $150 million, and preventing the production of 47,000 metric tons of greenhouse gas emissions.
Procter & Gamble, a Cisco customer, is eyeing similar results. P&G has installed 40 TelePresence systems globally and estimates the infrastructure will eliminate some 1,000 business trips per month. Of course, Cisco’s TelePresence solution is an elite corporate offering, with units priced up to $300,000. However, the company says a SoHo version is in the works, with availability planned in about a year. A long list of competitors is attacking the category as wel
With reducing environment footprint, soon it will be cheaper to host telepresence.
With broadband speed,eventually telepresence will come to each home.. highspeed
network, big TV and good video camera.. Here is Web 3.0.
Video conference Telepresence helps to get visual clues.With travel cuts, this
seems good option. Cisco's growth was 5 times...
if you want to be. Couple of senses are fed - visual and audio. - Visual Networking.
The revolution of phone is taken to next level. With Telepresence booths, which
brings similar to phone booths --- public telepresence .. and also service provider
telepresence. You can reduce travel.
cisco Telepresence
Using the system itself, Cisco says its employees have avoided travel to more than 16,000 meetings, saving the company more than $150 million, and preventing the production of 47,000 metric tons of greenhouse gas emissions.
Procter & Gamble, a Cisco customer, is eyeing similar results. P&G has installed 40 TelePresence systems globally and estimates the infrastructure will eliminate some 1,000 business trips per month. Of course, Cisco’s TelePresence solution is an elite corporate offering, with units priced up to $300,000. However, the company says a SoHo version is in the works, with availability planned in about a year. A long list of competitors is attacking the category as wel
With reducing environment footprint, soon it will be cheaper to host telepresence.
With broadband speed,eventually telepresence will come to each home.. highspeed
network, big TV and good video camera.. Here is Web 3.0.
Video conference Telepresence helps to get visual clues.With travel cuts, this
seems good option. Cisco's growth was 5 times...
Tuesday, April 29, 2008
MDS Fc port stuck in initializing
Reasons:
- flogi server not responding correctly
show flogi internal event interface fc x/y
- persistent fcid limit exceeded ( 255 entries with all area unique fcid because
of qlogic hbas)
MDS9513-83-SJ# show run | include "vsan Z" | include fcid | count
where Z is vsan #.
- conflict in persistent fcids ( MDS can't assign the fcid allocated
to WWN)
- # of devices more than 255 if qlogic or devices that need area unique fcid
is allocated
- supervisor failure or module issue, flogi command not reaching the supervisor
or flogi process.
show fc2 internal even errors
these are few causes.
- flogi server not responding correctly
show flogi internal event interface fc x/y
- persistent fcid limit exceeded ( 255 entries with all area unique fcid because
of qlogic hbas)
MDS9513-83-SJ# show run | include "vsan Z" | include fcid | count
where Z is vsan #.
- conflict in persistent fcids ( MDS can't assign the fcid allocated
to WWN)
- # of devices more than 255 if qlogic or devices that need area unique fcid
is allocated
- supervisor failure or module issue, flogi command not reaching the supervisor
or flogi process.
show fc2 internal even errors
these are few causes.
Flex Attach in MDS!
MDS gives virtual pwwn that is used for zoning and lun masking, so when a host
connected a port dies, you can either connect a new host to same port or reconfigure
flexattach config on port where spare host is connected. So this is a security concern
because anyone can come and attach another host to port and get all the access to luns.
Similar way someone can replace or remove hba and connect it to a different server.
This can be reduced by using port-security.
http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/command/reference/CR03_f.html#wp1393061
connected a port dies, you can either connect a new host to same port or reconfigure
flexattach config on port where spare host is connected. So this is a security concern
because anyone can come and attach another host to port and get all the access to luns.
Similar way someone can replace or remove hba and connect it to a different server.
This can be reduced by using port-security.
http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/command/reference/CR03_f.html#wp1393061
MDS callhome for bootflash errors!
When a bootflash fails, if callhome is configured correctly, we would expect
XML destination to send the callhome, it does not happen even if Cisco_TAC alert group
is added because of the bug
CSCso71302.
Workaround is defined in the above Cisco MDS bug.
Symptom:
BOOTFLASH failure does not generate callhome to default XML destination profile.
Workaround:
Default XML destination profile is configured to receive alerts from Cisco-Tac alert group by default. You need to add linecard-hardware and supervisor-hardware alert groups to that destination profile to get callhome messages like BOOTFLASH failure
for eg.
callhome
destination-profile xml message-level 2
destination-profile xml email-addr auto-notify@cisco.com
destination-profile xml alert-group linecard-hardware
destination-profile xml alert-group supervisor-hardware
destination-profile xml alert syslog-group-port
XML destination to send the callhome, it does not happen even if Cisco_TAC alert group
is added because of the bug
CSCso71302.
Workaround is defined in the above Cisco MDS bug.
Symptom:
BOOTFLASH failure does not generate callhome to default XML destination profile.
Workaround:
Default XML destination profile is configured to receive alerts from Cisco-Tac alert group by default. You need to add linecard-hardware and supervisor-hardware alert groups to that destination profile to get callhome messages like BOOTFLASH failure
for eg.
callhome
destination-profile xml message-level 2
destination-profile xml email-addr auto-notify@cisco.com
destination-profile xml alert-group linecard-hardware
destination-profile xml alert-group supervisor-hardware
destination-profile xml alert syslog-group-port
Friday, April 25, 2008
NPIV sample config
Sample config:
9513(NPIV enable)--fc2/2---- ---fc1/1(NP port)---9134---(fc1/10 host)
All the ports are in vsan 30
NPV switch 9134 config:
Make sure switch password and console access is there before you do this,
npv enable.
npv enable and set the port to NP mode
MDS9134-SJ# show run int fc1/1
version 3.2(1a)
interface fc1/1
port-license acquire
switchport mode NP
no shutdown
This port is upstream to NPIV enabled switch and
fc1/10 is where host is connected
MDS9134-SJ# show run int fc1/10
version 3.2(1a)
interface fc1/10
port-license acquire
switchport mode F
no shutdown
They both have to be in same vsan else
NPIV upstream not availabe error might be there.
sh npv internal errors
192) Event:E_DEBUG, length:186, at 683624 usecs after Fri Apr 25 16:17:04 2008
[102] npivp_mts_hdlr_fwd_internal_flogi_update(1165): Unable to match the fw
d response for internal FLOGI with any of the outstanding responses, ignoring th
e resp, error: fu unknown error
193) Event:E_DEBUG, length:136, at 652218 usecs after Fri Apr 25 16:17:04 2008
[112] E(1,fc1/1) Upstream Port VSAN(30) for this interface is different from
the local port VSAN(1)Failing this external interface: fc1/1
MDS9134-SJ# show npv flogi-table
--------------------------------------------------------------------------------
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFAC
E
--------------------------------------------------------------------------------
fc1/10 1 0x0a0400 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e fc1/1
Total number of flogi = 1.
MDS9134-SJ# show npv status
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, VSAN: 1, FCID: 0x0a000d, State: Up
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Pre-Initialized
Interface: fc1/10, VSAN: 1, State: Up
Number of Server Interfaces: 2
Eari
Earlier Error
MDS9134-SJ(config-if)# do show int fc1/10
fc1/10 is down (NPV upstream port not available)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:0a:00:0d:ec:51:05:40
Admin port mode is F
snmp link state traps are enabled
Port vsan is 30
Ve
Becasuse upstream port fc1/1 is in vsan 1 and fc1/10 is vsan 30..?
What if upstream port in vsan 30 but remote switch with npiv does
not have vsan 30.
MDS9134-SJ# show npv sta
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, State: Failed(Mismatch in VSAN for this upstream port)
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Waiting for External Interface
Interface: fc1/10, State: Waiting for External Interface
Number of Server Interfaces: 2
Created vsan 30 on 9513
then
MDS9134-SJ# show npv sta
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, VSAN: 30, FCID: 0xa00000, State: Up
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Waiting for External Interface
Interface: fc1/10, VSAN: 30, State: Up
Number of Server Interfaces: 2
ee
No flogi commands are there...
Commands
MDS9134-SJ# show npv internal event- flogi-fsm interface fc1/10
7) FSM: Transition at 922358 usecs after Fri Apr
25 16:50:55 2008
Previous state: [NPIVP_FLOGI_ST_WAIT_ON_FCID_ADD]
Triggered event: [NPIVP_FLOGI_EV_FCID_UPDATE_SUCCESS_RESP]
Next state: [NPIVP_FLOGI_ST_STEADY_STATE]
8) FSM: Transition at 922717 usecs after Fri Apr
25 16:50:55 2008
Previous state: [NPIVP_FLOGI_ST_STEADY_STATE]
Triggered event: [NPIVP_FLOGI_EV_SEND_FLOGI_ACC]
Next state: [FSM_ST_NO_CHANGE]
MDS9134-SJ# show npv internal event- ext-if-fsm int fc1/1\
497) FSM: Transition at 106900 usecs after Fri Apr 25 16:50:55
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSNN_RESPONSE_SUCCESSFUL]
Next state: [FSM_ST_NO_CHANGE]
498) FSM: Transition at 110396 usecs after Fri Apr 25 16:50:55
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSPN_RESPONSE]
Next state: [FSM_ST_NO_CHANGE]
499) FSM: Transition at 110406 usecs after Fri Apr 25 16:50:55
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSPN_RESPONSE_SUCCESSFUL]
Next state: [FSM_ST_NO_CHANGE]
500) FSM: Transition at 110412 usecs after Fri Apr 25 16:50:55
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_VALIDATE_INT_FLOGI_ACC_SUCCESS]
Next state: [NPIVP_EXT_IF_ST_UP]
Curr state: [NPIVP_EXT_IF_ST_UP]
NPIV switch config and commands:
MDS9513-83-SJ(config)# do show run int fc2/2
version 3.2(2c)
interface fc2/2
no shutdown
switchport mode F
MDS9513-83-SJ(config)# do show int fc2/2
fc2/2 is up
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:42:00:0d:ec:2c:54:c0
Admin port mode is F
snmp link state traps are enabled
Port mode is F, FCID is 0xa00000
Port vsan is 30
Speed is 4 Gbps
Rate mode is dedicated
Transmit B2B Credit is 16
Receive B2B Credit is 16
Receive data field Size is 2112
Beacon is turned off
5 minutes input rate 128 bits/sec, 16 bytes/sec, 0 frames/sec
5 minutes output rate 104 bits/sec, 13 bytes/sec, 0 frames/sec
231 frames input, 22980 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
257 frames output, 19556 bytes
0 discards, 0 errors
5 input OLS, 5 LRR, 5 NOS, 0 loop inits
MDS9513-83-SJ(config)# do show flogi database interface fc2/2
---------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
---------------------------------------------------------------------------
fc2/2 30 0xa00000 20:01:00:0d:ec:51:05:40 20:1e:00:0d:ec:51:05:41
fc2/2 30 0xa00100 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e
[Win_HBA0]
MDS9513-83-SJ# show fcns database npv NOde_wwn 20:1e:00:0d:ec:51:05:41
VSAN 30:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0xa00100 N 21:00:00:e0:8b:0b:38:0e (Qlogic) scsi-fcp:init
[Win_HBA0]
Total number of entries = 1
MDS9513-83-SJ# show flogi database details
---------------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME FLAGS
---------------------------------------------------------------------------------------
fc2/1 5 0xbd0000 21:00:00:e0:8b:08:dd:22 20:00:00:e0:8b:08:dd:22 ADOP
fc2/2 30 0xa00000 20:01:00:0d:ec:51:05:40 20:1e:00:0d:ec:51:05:41
fc2/2 30 0xa00100 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e AVDO
[Win_HBA0]
fc2/8 1 0x0a000c 50:06:01:68:88:02:90:ce 50:06:01:60:11:02:90:ce
fc2/10 777 0x490300 21:00:00:d0:b2:00:82:c0 20:00:00:d0:b2:00:82:c0 ADOP
fc2/11 777 0x490200 21:02:00:d0:b2:00:82:c0 20:02:00:d0:b2:00:82:c0 ADOP
fv4/1/1 1 0x0a0000 26:02:00:0d:ec:2c:54:c2 26:0b:00:0d:ec:2c:54:c2 P
fv4/1/2 1 0x0a0001 26:03:00:0d:ec:2c:54:c2 26:0c:00:0d:ec:2c:54:c2 P
fv4/2/1 1 0x0a0002 26:04:00:0d:ec:2c:54:c2 26:0d:00:0d:ec:2c:54:c2 P
fv4/2/2 1 0x0a0009 25:02:00:0d:ec:2c:54:c2 25:03:00:0d:ec:2c:54:c2 P
fv4/3/1 1 0x0a0003 26:05:00:0d:ec:2c:54:c2 26:0e:00:0d:ec:2c:54:c2 P
fv4/4/1 1 0x0a0004 26:06:00:0d:ec:2c:54:c2 26:0f:00:0d:ec:2c:54:c2 P
fv4/5/1 1 0x0a0005 26:07:00:0d:ec:2c:54:c2 26:10:00:0d:ec:2c:54:c2 P
fv4/6/1 1 0x0a0006 26:08:00:0d:ec:2c:54:c2 26:11:00:0d:ec:2c:54:c2 P
fv4/7/1 1 0x0a0007 26:09:00:0d:ec:2c:54:c2 26:12:00:0d:ec:2c:54:c2 P
fv4/8/1 1 0x0a0008 26:0a:00:0d:ec:2c:54:c2 26:13:00:0d:ec:2c:54:c2 P
Total number of flogi = 16.
FLAGS:
A area FCID allocation
L loop device
V FDISC
D the wwn matches the default OUI list
O the wwn matches the configured OUI list
P allocation was done based on the persistency table
--------------
MDS9513-83-SJ# show run | include npi
npiv enable
MDS9513-83-SJ# show fcns database npv
VSAN 30:
-------------------------------------------------------------------------------
NPV NODE-NAME NPV IP_ADDR NPV IF CORE SWITCH WWN CORE IF
-------------------------------------------------------------------------------
20:1e:00:0d:ec:51:05:41 172.16.33.23 fc1/1 20:00:00:0d:ec:2c:54:c0 fc2/2
172.16.33.23 is 9134 switch.
which has npv enabled
MDS9513-83-SJ# show fcns database npv de
------------------------------------------------------------
VSAN:30 NPV Node Name: 20:1e:00:0d:ec:51:05:41
------------------------------------------------------------
NPV Fabric Port-WWN :20:01:00:0d:ec:51:05:40
class :2,3
NPV IP Address :172.16.33.23
ipa :ff ff ff ff ff ff ff ff
fc4-types:fc4_features :npv
NPV Switch Name:Interface :MDS9134-SJ:fc1/1
port-type :NP
Core Switch fabric-port-wwn :20:42:00:0d:ec:2c:54:c0
permanent-port-wwn (vendor) :20:01:00:0d:ec:51:05:40 (Cisco)
Total number of entries = 1
======================================================================
9513(NPIV enable)--fc2/2---- ---fc1/1(NP port)---9134---(fc1/10 host)
All the ports are in vsan 30
NPV switch 9134 config:
Make sure switch password and console access is there before you do this,
npv enable.
npv enable and set the port to NP mode
MDS9134-SJ# show run int fc1/1
version 3.2(1a)
interface fc1/1
port-license acquire
switchport mode NP
no shutdown
This port is upstream to NPIV enabled switch and
fc1/10 is where host is connected
MDS9134-SJ# show run int fc1/10
version 3.2(1a)
interface fc1/10
port-license acquire
switchport mode F
no shutdown
They both have to be in same vsan else
NPIV upstream not availabe error might be there.
sh npv internal errors
192) Event:E_DEBUG, length:186, at 683624 usecs after Fri Apr 25 16:17:04 2008
[102] npivp_mts_hdlr_fwd_internal_flogi_update(1165): Unable to match the fw
d response for internal FLOGI with any of the outstanding responses, ignoring th
e resp, error: fu unknown error
193) Event:E_DEBUG, length:136, at 652218 usecs after Fri Apr 25 16:17:04 2008
[112] E(1,fc1/1) Upstream Port VSAN(30) for this interface is different from
the local port VSAN(1)Failing this external interface: fc1/1
MDS9134-SJ# show npv flogi-table
--------------------------------------------------------------------------------
SERVER EXTERNAL
INTERFACE VSAN FCID PORT NAME NODE NAME INTERFAC
E
--------------------------------------------------------------------------------
fc1/10 1 0x0a0400 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e fc1/1
Total number of flogi = 1.
MDS9134-SJ# show npv status
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, VSAN: 1, FCID: 0x0a000d, State: Up
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Pre-Initialized
Interface: fc1/10, VSAN: 1, State: Up
Number of Server Interfaces: 2
Eari
Earlier Error
MDS9134-SJ(config-if)# do show int fc1/10
fc1/10 is down (NPV upstream port not available)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:0a:00:0d:ec:51:05:40
Admin port mode is F
snmp link state traps are enabled
Port vsan is 30
Ve
Becasuse upstream port fc1/1 is in vsan 1 and fc1/10 is vsan 30..?
What if upstream port in vsan 30 but remote switch with npiv does
not have vsan 30.
MDS9134-SJ# show npv sta
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, State: Failed(Mismatch in VSAN for this upstream port)
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Waiting for External Interface
Interface: fc1/10, State: Waiting for External Interface
Number of Server Interfaces: 2
Created vsan 30 on 9513
then
MDS9134-SJ# show npv sta
npiv is enabled
External Interfaces:
====================
Interface: fc1/1, VSAN: 30, FCID: 0xa00000, State: Up
Number of External Interfaces: 1
Server Interfaces:
==================
Interface: fc1/2, State: Waiting for External Interface
Interface: fc1/10, VSAN: 30, State: Up
Number of Server Interfaces: 2
ee
No flogi commands are there...
Commands
MDS9134-SJ# show npv internal event- flogi-fsm interface fc1/10
7) FSM:
25 16:50:55 2008
Previous state: [NPIVP_FLOGI_ST_WAIT_ON_FCID_ADD]
Triggered event: [NPIVP_FLOGI_EV_FCID_UPDATE_SUCCESS_RESP]
Next state: [NPIVP_FLOGI_ST_STEADY_STATE]
8) FSM:
25 16:50:55 2008
Previous state: [NPIVP_FLOGI_ST_STEADY_STATE]
Triggered event: [NPIVP_FLOGI_EV_SEND_FLOGI_ACC]
Next state: [FSM_ST_NO_CHANGE]
MDS9134-SJ# show npv internal event- ext-if-fsm int fc1/1\
497) FSM:
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSNN_RESPONSE_SUCCESSFUL]
Next state: [FSM_ST_NO_CHANGE]
498) FSM:
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSPN_RESPONSE]
Next state: [FSM_ST_NO_CHANGE]
499) FSM:
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_NS_RSPN_RESPONSE_SUCCESSFUL]
Next state: [FSM_ST_NO_CHANGE]
500) FSM:
2008
Previous state: [NPIVP_EXT_IF_ST_WAITING_NS_REGISTRATION]
Triggered event: [NPIVP_EXT_IF_EV_VALIDATE_INT_FLOGI_ACC_SUCCESS]
Next state: [NPIVP_EXT_IF_ST_UP]
Curr state: [NPIVP_EXT_IF_ST_UP]
NPIV switch config and commands:
MDS9513-83-SJ(config)# do show run int fc2/2
version 3.2(2c)
interface fc2/2
no shutdown
switchport mode F
MDS9513-83-SJ(config)# do show int fc2/2
fc2/2 is up
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:42:00:0d:ec:2c:54:c0
Admin port mode is F
snmp link state traps are enabled
Port mode is F, FCID is 0xa00000
Port vsan is 30
Speed is 4 Gbps
Rate mode is dedicated
Transmit B2B Credit is 16
Receive B2B Credit is 16
Receive data field Size is 2112
Beacon is turned off
5 minutes input rate 128 bits/sec, 16 bytes/sec, 0 frames/sec
5 minutes output rate 104 bits/sec, 13 bytes/sec, 0 frames/sec
231 frames input, 22980 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
257 frames output, 19556 bytes
0 discards, 0 errors
5 input OLS, 5 LRR, 5 NOS, 0 loop inits
MDS9513-83-SJ(config)# do show flogi database interface fc2/2
---------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
---------------------------------------------------------------------------
fc2/2 30 0xa00000 20:01:00:0d:ec:51:05:40 20:1e:00:0d:ec:51:05:41
fc2/2 30 0xa00100 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e
[Win_HBA0]
MDS9513-83-SJ# show fcns database npv NOde_wwn 20:1e:00:0d:ec:51:05:41
VSAN 30:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0xa00100 N 21:00:00:e0:8b:0b:38:0e (Qlogic) scsi-fcp:init
[Win_HBA0]
Total number of entries = 1
MDS9513-83-SJ# show flogi database details
---------------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME FLAGS
---------------------------------------------------------------------------------------
fc2/1 5 0xbd0000 21:00:00:e0:8b:08:dd:22 20:00:00:e0:8b:08:dd:22 ADOP
fc2/2 30 0xa00000 20:01:00:0d:ec:51:05:40 20:1e:00:0d:ec:51:05:41
fc2/2 30 0xa00100 21:00:00:e0:8b:0b:38:0e 20:00:00:e0:8b:0b:38:0e AVDO
[Win_HBA0]
fc2/8 1 0x0a000c 50:06:01:68:88:02:90:ce 50:06:01:60:11:02:90:ce
fc2/10 777 0x490300 21:00:00:d0:b2:00:82:c0 20:00:00:d0:b2:00:82:c0 ADOP
fc2/11 777 0x490200 21:02:00:d0:b2:00:82:c0 20:02:00:d0:b2:00:82:c0 ADOP
fv4/1/1 1 0x0a0000 26:02:00:0d:ec:2c:54:c2 26:0b:00:0d:ec:2c:54:c2 P
fv4/1/2 1 0x0a0001 26:03:00:0d:ec:2c:54:c2 26:0c:00:0d:ec:2c:54:c2 P
fv4/2/1 1 0x0a0002 26:04:00:0d:ec:2c:54:c2 26:0d:00:0d:ec:2c:54:c2 P
fv4/2/2 1 0x0a0009 25:02:00:0d:ec:2c:54:c2 25:03:00:0d:ec:2c:54:c2 P
fv4/3/1 1 0x0a0003 26:05:00:0d:ec:2c:54:c2 26:0e:00:0d:ec:2c:54:c2 P
fv4/4/1 1 0x0a0004 26:06:00:0d:ec:2c:54:c2 26:0f:00:0d:ec:2c:54:c2 P
fv4/5/1 1 0x0a0005 26:07:00:0d:ec:2c:54:c2 26:10:00:0d:ec:2c:54:c2 P
fv4/6/1 1 0x0a0006 26:08:00:0d:ec:2c:54:c2 26:11:00:0d:ec:2c:54:c2 P
fv4/7/1 1 0x0a0007 26:09:00:0d:ec:2c:54:c2 26:12:00:0d:ec:2c:54:c2 P
fv4/8/1 1 0x0a0008 26:0a:00:0d:ec:2c:54:c2 26:13:00:0d:ec:2c:54:c2 P
Total number of flogi = 16.
FLAGS:
A area FCID allocation
L loop device
V FDISC
D the wwn matches the default OUI list
O the wwn matches the configured OUI list
P allocation was done based on the persistency table
--------------
MDS9513-83-SJ# show run | include npi
npiv enable
MDS9513-83-SJ# show fcns database npv
VSAN 30:
-------------------------------------------------------------------------------
NPV NODE-NAME NPV IP_ADDR NPV IF CORE SWITCH WWN CORE IF
-------------------------------------------------------------------------------
20:1e:00:0d:ec:51:05:41 172.16.33.23 fc1/1 20:00:00:0d:ec:2c:54:c0 fc2/2
172.16.33.23 is 9134 switch.
which has npv enabled
MDS9513-83-SJ# show fcns database npv de
------------------------------------------------------------
VSAN:30 NPV Node Name: 20:1e:00:0d:ec:51:05:41
------------------------------------------------------------
NPV Fabric Port-WWN :20:01:00:0d:ec:51:05:40
class :2,3
NPV IP Address :172.16.33.23
ipa :ff ff ff ff ff ff ff ff
fc4-types:fc4_features :npv
NPV Switch Name:Interface :MDS9134-SJ:fc1/1
port-type :NP
Core Switch fabric-port-wwn :20:42:00:0d:ec:2c:54:c0
permanent-port-wwn (vendor) :20:01:00:0d:ec:51:05:40 (Cisco)
Total number of entries = 1
======================================================================
Saturday, April 12, 2008
NPIV
Cisco SAN-OS release 3.0(1) supports the industry-standard N-port
identifier virtualization (NPIV), which allows a single Fibre Channel
HBA port to be assigned multiple Fibre Channel IDs. Under virtual
operating environments such as VMware, NPIV enables access control,
zoning, and port security to be configured for each virtual machine.
N Port virtualization (NPV) reduces the number of Fibre Channel domain IDs in SANs. Switches operating in the NPV mode do not join a fabric; rather, they pass traffic between NPV core switch links and end devices, which eliminates the domain IDs for these edge switches.
While NPV is similar to N port identifier virtualization (NPIV), it does not offer exactly the same functionality. NPIV provides a means to assign multiple FC IDs to a single N port, and allows multiple applications on the N port to use different identifiers. NPIV also allows access control, zoning, and port security to be implemented at the application level. NPV makes use of NPIV to get multiple FCIDs allocated from the core switch on the NP port.
NP Ports
An NP port (proxy N port) is a port on a device that is in NPV mode and connected to the NPV core switch using an F port. NP ports behave like N ports except that in addition to providing N port behavior, they also function as proxies for multiple, physical N ports.
NP Links
An NP link is basically an NPIV uplink to a specific end device. NP links are established when the uplink to the NPV core switch comes up; the links are terminated when the uplink goes down. Once the uplink is established, the NPV switch performs an internal FLOGI to the NPV core switch, and then (if the FLOGI is successful) registers itself with the NPV core switch's name server.
When an NP port comes up, the NPV device first logs itself in to the NPV core switch and sends a FLOGI request that includes the following parameters:
•The fWWN (fabric port WWN) of the NP port used as the pWWN in the internal login.
•The VSAN-based sWWN (switch WWN) of the NPV device used as nWWN (node WWN) in the internal FLOGI.
After completing its FLOGI request, the NPV device registers itself with the fabric name server using the following additional parameters:
•Switch name and interface name (for example, fc1/4) of the NP port is embedded in the symbolic port name in the name server registration of the NPV device itself.
•The IP address of the NPV device is registered as the IP address in the name server registration of the NPV device.
Note The BB_SCN of internal FLOGIs on NP ports is always set to zero. The BB_SCN is supported at the F-port of the NPV device.
lthough fWWN-based zoning is supported for NPV devices, it is not recommended because:
•Zoning is not enforced at the NPV device (rather, it is enforced on the NPV core switch).
•Multiple devices behind an NPV device log in via the same F port on the core (hence, they use same fWWN and cannot be separated into different zones).
•The same device might log in using different fWWNs on the core switch (depending on the NPV link it uses) and may need to be zoned using different fWWNs.
When you enable NPV, your system configuration is erased and the system is rebooted with NPV mode enabled
On the 91x4 platform, before you upgrade to 3.2(2b) or downgrade from 3.2(2b), shut the F-ports connected to NPIV capable hosts, and then disable the NPIV feature. After the upgrade or downgrade is complete, enable the NPIV feature and up the F-ports.
switch(config)# npiv enable
switch(config)# interface fc2/1
switch(config-if)# switchport mode F
switch(config-if)# no shutdown
Configure the NPIV core switch port as an F port.
Changes Admin status to bring up the interfaces
switch(config)# npv enable
Enables NPV mode on a NPV device (module, Cisco MDS 9124 or Cisco MDS 9134 Fabric Switch). The module or switch is rebooted, and when it comes back up, is in NPV mode.
Note A write-erase is performed during the reboot.
switch(config)# interface fc1/1
switch(config-if)# switchport mode NP
switch(config-if)# no shutdown
On the NPV device, select the interfaces that will be connected to the aggregator switch and configure them as NP ports.
By grouping devices into different NPV sessions based on VSANs, it is possible to support multiple VSANs at the NPV-enabled switch. The correct uplink must be selected based on the VSAN(s) that the uplink can carry.
Issues I have seen with NPIV
- HP Virtual Connect does not load balance between the ports, the frames
might get lost, if there are multiple connections.
- Few Bugs on Cisco side,
CSCsk96105
Symptom: If you upgrade to Cisco SAN-OS Release 3.2(2c) from a lower version, or downgrade from Cisco SAN-OS Release 3.2(2c) to a lower version on an MDS 9124 switch, MDS 9134 switch, Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM BladeCenter, zoning may not work as configured for the F ports connected to NPIV-capable hosts.
Workaround: This issue is resolved.
CSCsk00953
Symptom: HP Blade Servers that are connected through an HP Virtual Connect (VC) FC module to a Cisco Fabric Switch for HP c-Class BladeSystem using NPIV lose access to LUNs when load balancing on the VC module is switched from 16:1 to 8:1. When the load balancing ratio is 16:1, all servers connect through interface ext1. When the ratio is 8:1, servers 1 and 3 connect through ext1, servers 2 and 4 connect through ext2, and so on. Servers on ext2 are not affected by the switchover. In addition, packets might get dropped when the switchover occurs.
When more than 255 hosts logged into that vsan, there may be issue, if all the ports Qlogic ports.
As guessed each pwwn(of qlogic hba) belongs to auto-area-oui list and it consumes entire area. After 255 hosts are brought up in vsan 2 all 255 areas of domain 0x35 in vsan 2 are used and so the fcid allocation fails.
From fcdomain P2.log.txt:
grep "ENTIRE AREA" tt | grep " 2 " | wc -l
254
Workaround as suggested in Jerome's case:
MDS9216I-86-SJ# show fcid company-id-from-wwn 50:06:0b:00:00:c2:62:10
Extracted oui: 0x0060B0
MDS9216I-86-SJ# config t
MDS9216I-86-SJ(config)# no fcid-allocation area company-id 0x0060B0
shut all the hosts or host one by one to clear that area id.
purge fcdomain fcid vsan 2
identifier virtualization (NPIV), which allows a single Fibre Channel
HBA port to be assigned multiple Fibre Channel IDs. Under virtual
operating environments such as VMware, NPIV enables access control,
zoning, and port security to be configured for each virtual machine.
N Port virtualization (NPV) reduces the number of Fibre Channel domain IDs in SANs. Switches operating in the NPV mode do not join a fabric; rather, they pass traffic between NPV core switch links and end devices, which eliminates the domain IDs for these edge switches.
While NPV is similar to N port identifier virtualization (NPIV), it does not offer exactly the same functionality. NPIV provides a means to assign multiple FC IDs to a single N port, and allows multiple applications on the N port to use different identifiers. NPIV also allows access control, zoning, and port security to be implemented at the application level. NPV makes use of NPIV to get multiple FCIDs allocated from the core switch on the NP port.
NP Ports
An NP port (proxy N port) is a port on a device that is in NPV mode and connected to the NPV core switch using an F port. NP ports behave like N ports except that in addition to providing N port behavior, they also function as proxies for multiple, physical N ports.
NP Links
An NP link is basically an NPIV uplink to a specific end device. NP links are established when the uplink to the NPV core switch comes up; the links are terminated when the uplink goes down. Once the uplink is established, the NPV switch performs an internal FLOGI to the NPV core switch, and then (if the FLOGI is successful) registers itself with the NPV core switch's name server.
When an NP port comes up, the NPV device first logs itself in to the NPV core switch and sends a FLOGI request that includes the following parameters:
•The fWWN (fabric port WWN) of the NP port used as the pWWN in the internal login.
•The VSAN-based sWWN (switch WWN) of the NPV device used as nWWN (node WWN) in the internal FLOGI.
After completing its FLOGI request, the NPV device registers itself with the fabric name server using the following additional parameters:
•Switch name and interface name (for example, fc1/4) of the NP port is embedded in the symbolic port name in the name server registration of the NPV device itself.
•The IP address of the NPV device is registered as the IP address in the name server registration of the NPV device.
Note The BB_SCN of internal FLOGIs on NP ports is always set to zero. The BB_SCN is supported at the F-port of the NPV device.
lthough fWWN-based zoning is supported for NPV devices, it is not recommended because:
•Zoning is not enforced at the NPV device (rather, it is enforced on the NPV core switch).
•Multiple devices behind an NPV device log in via the same F port on the core (hence, they use same fWWN and cannot be separated into different zones).
•The same device might log in using different fWWNs on the core switch (depending on the NPV link it uses) and may need to be zoned using different fWWNs.
When you enable NPV, your system configuration is erased and the system is rebooted with NPV mode enabled
On the 91x4 platform, before you upgrade to 3.2(2b) or downgrade from 3.2(2b), shut the F-ports connected to NPIV capable hosts, and then disable the NPIV feature. After the upgrade or downgrade is complete, enable the NPIV feature and up the F-ports.
switch(config)# npiv enable
switch(config)# interface fc2/1
switch(config-if)# switchport mode F
switch(config-if)# no shutdown
Configure the NPIV core switch port as an F port.
Changes Admin status to bring up the interfaces
switch(config)# npv enable
Enables NPV mode on a NPV device (module, Cisco MDS 9124 or Cisco MDS 9134 Fabric Switch). The module or switch is rebooted, and when it comes back up, is in NPV mode.
Note A write-erase is performed during the reboot.
switch(config)# interface fc1/1
switch(config-if)# switchport mode NP
switch(config-if)# no shutdown
On the NPV device, select the interfaces that will be connected to the aggregator switch and configure them as NP ports.
By grouping devices into different NPV sessions based on VSANs, it is possible to support multiple VSANs at the NPV-enabled switch. The correct uplink must be selected based on the VSAN(s) that the uplink can carry.
Issues I have seen with NPIV
- HP Virtual Connect does not load balance between the ports, the frames
might get lost, if there are multiple connections.
- Few Bugs on Cisco side,
CSCsk96105
Symptom: If you upgrade to Cisco SAN-OS Release 3.2(2c) from a lower version, or downgrade from Cisco SAN-OS Release 3.2(2c) to a lower version on an MDS 9124 switch, MDS 9134 switch, Cisco Fabric Switch for HP c-Class BladeSystem, or a Cisco Fabric Switch for IBM BladeCenter, zoning may not work as configured for the F ports connected to NPIV-capable hosts.
Workaround: This issue is resolved.
CSCsk00953
Symptom: HP Blade Servers that are connected through an HP Virtual Connect (VC) FC module to a Cisco Fabric Switch for HP c-Class BladeSystem using NPIV lose access to LUNs when load balancing on the VC module is switched from 16:1 to 8:1. When the load balancing ratio is 16:1, all servers connect through interface ext1. When the ratio is 8:1, servers 1 and 3 connect through ext1, servers 2 and 4 connect through ext2, and so on. Servers on ext2 are not affected by the switchover. In addition, packets might get dropped when the switchover occurs.
When more than 255 hosts logged into that vsan, there may be issue, if all the ports Qlogic ports.
As guessed each pwwn(of qlogic hba) belongs to auto-area-oui list and it consumes entire area. After 255 hosts are brought up in vsan 2 all 255 areas of domain 0x35 in vsan 2 are used and so the fcid allocation fails.
From fcdomain P2.log.txt:
grep "ENTIRE AREA" tt | grep " 2 " | wc -l
254
Workaround as suggested in Jerome's case:
MDS9216I-86-SJ# show fcid company-id-from-wwn 50:06:0b:00:00:c2:62:10
Extracted oui: 0x0060B0
MDS9216I-86-SJ# config t
MDS9216I-86-SJ(config)# no fcid-allocation area company-id 0x0060B0
shut all the hosts or host one by one to clear that area id.
purge fcdomain fcid vsan 2
Subscribe to:
Posts (Atom)