07-30-2008 06:57 AM
The issue I am seeing with swapping the Mcdata blade center switch with a Brocade blade center switch is more of understanding the differences that we see from one switch to another.
To understand what I am saying and why we are doing this change following is the History and configuration as of today.
We have a SAN environment which uses as a core switch a Mcdata 2027 The Blade center Mcdata switch is connected to the SAN through an ISL to the McData 2027. On EFCM we can see the ISL connection and can manage the Blade center switch (ZONE) it is to say all ports on the blade center switch can be accessed through EFCM and are zoned through the EFCM.
Recently we bought two more switches to be added to our SAN Fabric, BROCADE 48000, when we ISL'ed these to the Core switches the existent McData Blade center switches did not support this thus crashing the Blade center servers.
The solution for this was supposedly to replace the Blade center McData Switches for Brocade Blade center Switches.
We have the Brocade blade center switches and as the documentation that we have to replace them we need two settings to happen 1. the blade center switch should work as a Gateway Access and 2. NPIV settings should be set. These two steps were set.
When we replaced the switch there were no issues and we were able to switch one of the servers path over to the new switch and see all the resources required by the server.
But what we saw confused to the point that we backed out. The issue that we see is :
1. In EFCM we do not see the ISL connection between the Brocade Bladecenter switches and the core switch, and the blade center switch appears as a standalone device.
2. Physcally when the Mcdata switch is in the Bladecenter there are thre gree lights truned on 2 solid and one blinking (Normal State). When the Brocade Switch is in there are no lights what-so-ever with the occasional flicker of on gree light.
3. Through EFCM or even through the Brocade Switch interface there is no option where we can manage the switch (ZONE)
4. We see that al Virtual Fiber channels ports are only visible through the one port that is ISL'ed to the Core Switch SAN Fabric, all the other ports appear unused.
5. Through the Blade Center switch GUI interface we do not see a continuous online state of any of the ports.
What we would like to know if these issues are the normal state of these switched or is it that we missed something in the settings.
To save time the McData 2027 has a maintenance level of 9.6.2 and the Brocade blade center switch has a maintenance level of 5.3.0.
Does anyone have a similar Fabric layout with experinece? Is it the Normal state we are seeing?
07-30-2008 08:21 AM
NOT SURE YOUR GET a DOUBLE ANSWER.
it is all a little confused. Can you please helpme to explain what is the McDATA 2027 ? I dont know any McDATA with this Code.
--->>> 1. In EFCM we do not see the ISL connection between the Brocade Bladecenter switches and the core switch, and the blade center switch appears as a standalone device.
AG Mode show the switch as Standalone.
--->>> . Through EFCM or even through the Brocade Switch interface there is no option where we can manage the switch (ZONE)
Is the Brocade Switch configured as Access Gateway , see below, more details can your find in the AG Admin Guide.
BROCADE FEATURES IN ACCESS GATEWAY MODE
When using a Brocade switch in Access Gateway mode, most features are no longer applicable.
These features include Admin Domains, Advanced Performance Monitoring, direct connection to
SAN target devices, Fibre Channel Arbitrated Loop support, Fabric Manager, FICON, IP over FC, ISL
trunking, extended fabrics, management platform services, name services (SNS), port mirroring,
Secure Fabric OS, SMI-S, and zoning. These switch features are available in the default switch mode of operation.
Access Gateway does not support any Secure Fabric OS features. All the security enforcement is
done in the enterprise fabric. DCC policy in the enterprise fabric should include N_Port WWN and
port WWNs of all F_Ports on Access Gateway mapped to that N_Port. In case of DCC policy
violation, the port in the enterprise fabric to which N_Port is connected will be disabled. This will
bring down the corresponding N_Port and F_Ports mapped to it on Access Gateway.
--->>> 4. We see that al Virtual Fiber channels ports are only visible through the one port that is ISL'ed to the Core Switch SAN Fabric, all the other ports appear unused.
AG Mode swow the switch as Single Device, all Internal Port work trough the NPIV.
07-30-2008 08:41 AM
You're right the switch is a 6140.
So what I understand is what I see is pretty much correct since the switch is now a Gateway access.
07-30-2008 08:49 AM