Discovery of MDS IBM FC Bladecenter by Cisco MDS 9513

Hi all,
Supose I have "9513", connected to it several "Bladecenters" and several "9513" switches.
My wish is to discover the attached switches with CLI commands.
The additional 9513 I can recognize with "show topology" that gives me the attached (trunk, port-channel) switches IP.
How can discover the blades? I would like to somehow to get their IPs.
Best regards,
Igor.

Another question:
The output of "show fcs database" at MDS 9513 I get:
     FCS Local Database in VSAN: 1
     Switch WWN               : XX:XX:XX:XX:XX:XX:XX:XX
     Switch Domain Id         : 0x05(5)
     Switch Mgmt-Addresses    : snmp://10.235.159.60/eth-ip
                                http://10.235.159.60/eth-ip
     Fabric-Name              : YY:YY:YY:YY:YY:YY:YY:YY
How can I get the "Fabric-Name" from BLADE switches?
Regards,
Igor.

Similar Messages

UCS B-Series / FC 6120 / MDS 9513: Setting up FI and B-Series in UCSM

We are receiving FC SAN connections from an MDS 9513 we do not own, within the same physical building. We have been given a range of WWNN and WWPN to create pools in UCSM.
I am not a storage manager, nor much of a systems manager, but I know there are more details to set up within UCSM in order to connect a blade to this SAN. I do not know the details within UCSM that have to be specified, order of operations to perform these configurations. Is there a document within Cisco Support or elsewhare to direct me through the process?

Hi Steven,
I believe you have already configured the FC uplink ports on the Fabric Interconnect (FI) and done the physical cabling to your MDS? If not, you need to do that first
++ Create the VSANs as required in the VSAN Tab in UCSM, under SAN Cloud. Make sure that these VSAN's are defined in the MDS.
Refer to
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_010110.html
++ Now You need to decide which ports on the FI you will use for the FC uplink and configure it as FC uplink ports from the UCSM. Make sure that the FC uplink ports are in same VSAN as the ports in MDS which connects to FI.
Refer to
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html
Check for the FC Uplink ports to come online. This is important. If this is done then you can go to next steps.
Next thing is that create the WWNN Pool and WWPN Pool under the SAN tab. Refer to
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_011000.html
Now you are all set. Next thing is when creating the service profile, under storage tab, create vHBA's as required, use the WWPN pool and WWNN pool that you created. Again make sure that you select the right VSAN for the vHBA's. Provide these WWPN details to storage admin and request for the LUN's that you need to be allocated and rest will be handled from the storage admin.
If you need more details you can always go to
http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html and select the configuration guide, either CLI or GUI according to the UCS version you are running.
Hope this helps.

Best Design practices of SAN with the MDS 9513,MDS 9509 and Brocade 8510

Hi
Am searching best design to implement CISCO MDS 9513,9509, Brocade 8510,Storage and UCS all clubbed in the topology. And please suggest me any tool to compare MDS and Brocade 8510 performance.

Boomi,
Both MDS and Brocade will serve basic features of Storage networking. Both can be mix and match to achieve redundancy, which you already have. However, if you are looking for any tool or perfmon then there isn't much to compare. You can use IOmeter or Akkori. I see that you have enterprise level hardware in your setup. Not sure what other line cards you have installed and what application are running through, and if you have remote sites (SAN islands) then the real difference of features and best practices can be discussed. For example, IVR, FCIP, ISCSI, FCoE, etc.
Thanks,
Nisar
Sent from Cisco Technical Support iPad App

MDS 9513 in a Telco Rack?

We recently purchased 2 - MDS 9513 SAN switches. The only place to install them in our data center is in 2 Telco racks. I realize this is unsupported and we are on our own in terms of how to physically install this. We have placed one on a shelf and are looking for a way to secure or fasten the system to the rack somehow. The mounting ears can't be used because the unit is too deep to be flush mounted.
Has anyone out there been forced to use a Telco rack? If so, do you have any ideas on how to fasten to the rack?
Thanks

Jose,
can't you move the ears back? I just looked at our 9513's and there are what appear to be two more sets of holes on the sides for the ears. This is a picture of one or our 9509's in a telco rack and it came with the big plates that bolt to the telco rack that the switch sits on for this kind of mounting. I believe the 9513 (and 9509) chasiss are the same as the big Catalyst switches and we have those telco rack mounted all over the place so I bet you could get some of these mounting plates from Cisco (or your reseller.)

What if two service modules fail on a MDS 9513?

Hello,
We recently had a service module failure on one of our core MDS 9513 directors.
It is fixed now but I was wondering what would happen if the second service module had failed as well a bit later...
Will the director still function? All line cards and crossbars are still functionning. But there will be no management possible etc...
Will the traffic continue?
Kind regards,
Ivy

Ivy
The director would then fail completely.
Though I don't know anyone that unlucky

Do we have an procedure to gracefully shut down the MDS-9513?

Hello All
Do we have an procedure to gracefully shut down the MDS-9513?
Please advise
Thanks
Chetan

Hi Chetan,
There is no separate command required on MDS switches for a graceful
shutdown of the MDS switches.
Disengage the power or down the power source feeding the MDS to
shutdown the switch.
The MDS has enough RAM memory and does not require any fschk when it
will power back UP unlike other vendor switches. The MDS is architected
that way.
As a prudence you can take these measures:
1) Halt I/O or gracefully shutdown the attached servers and hosts
2) After your servers have been halted, follow the shutdown procedures
for all attached storage devices
3) Other tips to keep in mind if you were running HP-UX or AIX onyour
servers. In this case, you would want to make sure that you have turned
on static
domains and persistent FCIDs prior to powering these servers down (this
would insure that hosts and associated storage come back up with the
same domains and FCIDs.
4) Save your switch configuration by doing "copy run start" as well as
save your configuration externally to a FTP/TFTP server in case you need
to restore that back.
After all devices have been shutdown/quiesced, it is okay to simply
power off the MDS switches.
Best regards,
Jim

Is it possible to downgrade a MDS-9513 crossbar module?

IHAC that purchased a Generation 3 24-Port 8Gbps Module for two (2) of their MDS-9513 at Site A. The customer just discovered that they have a Generation 1 crossbar module [DS-13SLT-FAB1]. The customer has two (2) additional MDS-9513 at Site B that has a Generation 2 module [DS-13SLT-FAB2]. We want to swap crossbar modules from Site B to Site A, vice-versa.
Is it possible to downgrade a crossbar module?

No. You can't install earler versions of the OS than that with which (any) Mac was originally delivered.
If you REALLY want to investigate this, read this thread....
https://discussions.apple.com/thread/3209335?tstart=0

Cisco MDS 9513/9509 LDAP/AD Auth via SSH & Fabric Manager

Hello Folks,
I am trying to look for working config with LDAP auth over SSH. I know how to use them over TACACS+ & Radius. But due to other internal issue, currently I am trying to get the Cisco MDS to directly auth using LDAP/AD. Also, I see no option of LDAP/AD in FM(Fabric Manager), but just TACACS+, Radius, LocalFM and MDS. Do using MDS uses default auth(ie whatever AAA authentication is configured for ? or local DB on the switch). Does the new DCNM supports LDAP/AD auth on the GUI ?
Larger goal is SSH(CLI) & FM(GUI) using the same LDAP/AD auth. I understand the snmp-server user issue. But once I have SSH working over LDAP/AD I can figure that out to..
Here's what I need to ensure when using LDAP/AD auth
1) What is the exact config for this LDAP/AD auth
2) How do I ensure that network-admin & network-opertor roles are assigned when certain AD Groups Logins in Like ADMIN-AD-GROUP , OPERATOR-AD-GROUP --> trying to login to the switch
3) Also using SSL port for LDAP, do details are encrypted over the network.
4) Do I need to use the PASSWORD in paintext when BINDING the BaseDN ?, can it be an encrypted password.
Appreciate any info on this. Thanks for your time.

As of DCNM 6.1 (aka - Fabric Manager Server) we support LDAP authentication adding to existing Radius, TACACS+, local and switch authentications. You can upgrade from Fabric Manager 5.0 to DCNM 5.2 to DCNM 6.1 if you like to keep current performance, events, config data alive. We do recommend fresh install as we don't know what state your server dabatabase might be in. Including some links for you to help out with deployment and best practices (see release notes).
Resources:
Main Website:
http://www.cisco.com/go/dcnm
How To Video Series: http://www.cisco.com/en/US/prod/netmgtsw/ps6505/ps9369/cisco_dc_nm_video_library.html
Install and Licensing Guide:
http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Evaluation Licenses: http://tools.cisco.com/SWIFT/LicensingUI/Home?FormId=65
Download Linux and Windows Executables: http://www.cisco.com/cisco/pub/software/portal/select.html?&i=!m&mdfid=281722751
Data Sheets: http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6505/ps9369/data_sheet_c78-639737.html
Install Guide: http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
Configure Guide: http://www.cisco.com/en/US/products/ps9369/products_installation_and_configuration_guides_list.html
API Programming Guide:
http://www.cisco.com/en/US/products/ps9369/products_programming_reference_guides_list.html
Reference Guide: http://www.cisco.com/en/US/products/ps9369/prod_technical_reference_list.html
Release Notes: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_general_information.html

Connectivity IBM 2210 router with Cisco

Customer have existing IBM 2210 routers, and they just bought Cisco router for their expanded network. So they need to integrate Cisco router with their old IBM routers by connecting SDLC-to-SDLC between 3746 and 3174.
The diagram is like follow:
3174 -sdlc- IBM2210 --ethernet-- Cisco -sdlc- 3746
Is this connection possible? Can be done by using DLSw or other way?
Since I've never handled IBM router before.
Thanks a lot,
Chris

Providing the IBM router can handle DLSW to SDLC, then it should work with DLSW. The Cisco router does convert from SDLC to DLSW, although this is not part of the DLSW standard, but it is transparant to the other end what media the end device is on.

Port speed for ISL's and SP's , Hosts (MDS 9513)

Is there any recommendation/best practise for
1) setting port speed ie choose Auto or hard code eg 2gb, 4gb wrt b/w available ?
2) ratemode ie dedicated or shared ?
For ISL's And Storage processors/Controllers and hosts
Thanks,

For ISL's, if the line card is gen2, it must be configured as dedicated. For the port mode, I would recommend that you hard code the mode to E. I also like to code the speed on ISLs so that there is no chance that they would negotiate to a slower speed. IE: you don't want to have a 2GB link negotiate at 1GB.
As for storage controllers, depending on the fan in ratio, I would recommend hard coding them to the device speed, and if the port-group has the bandwidth available, make them dedicated.
As for hosts, they should be on the shared port, and I would leave them as port mode = auto. This way they can negotiate F or FL. You might want to configure a 'maximum allowable auto speed setting'.
IE: if your hosts have 2GB HBAs, and are plugged into a 4GB capable port, they will never negotiate to 4GB...so why have the MDS think it needs to keep some bandwidth for that port (in shared mode). I forget the command, but there is way to set auto-max for the port speed on shared ports.
Hope this helps,
Mike

Connecting QLE2562 Host Adapter FCode(SPARC): 2.03 06/30/08 to MDS 9513

Hi, Did someone knows what this event mean:" E_IPS_INIT_FAIL"? It appears when I try to connect "QLE2562 for SPARK" and I run the following command:
show hardware internal fcmac port 43 port-event
Regards
Eugene

bash-3.00# uname -a
SunOS sparky 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Blade-1000
bash-3.00#
bash-3.00# lsiutil
LSI Logic MPT Configuration Utility, Version 1.40, September 23, 2005
1 MPT Port found
Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev
1. itmpt0 LSI Logic SAS1068 B0 105 01120000
Select a device: [1-1 or 0 to quit] 1
1. Identify firmware, BIOS, and/or FCode
2. Download firmware (update the FLASH)
4. Download/erase BIOS and/or FCode (update the FLASH)
8. Scan for devices
10. Change IOC settings (interrupt coalescing)
13. Change SAS IO Unit settings
16. Display attached devices
20. Diagnostics
21. RAID actions
22. Reset bus
23. Reset target
30. Beacon on
31. Beacon off
60. Show non-default settings
61. Restore default settings
97. Reset SAS phy
98. Reset SAS link
99. Reset port
Main menu, select an option: [1-99 or e for expert or 0 to quit] 1
Current active firmware version is 01120000 (1.18.00)
Firmware image's version is MPTFW-01.18.00.00-IE
LSI Logic
x86 BIOS image's version is MPTBIOS-6.06.06.00 (2006.03.22)
FCode image's version is MPT SAS FCode Version 1.00.40 (2006.03.02)
Main menu, select an option: [1-99 or e for expert or 0 to quit]

Cisco SAN 9513s Slot dependancy for fc 24 & 48 port cards?

Newbee Question #1
I have a customer who is about to populate 2 new 9513s with fc 24 and 48 port cards. Are there any slot restrictions/dependancies for these FC cards. We know Slots 7 & 8 are reserved for the Sup-2 Engine cards.
May we populate slots 1 - 6 and 9 - 13 with 24 and/or 48 port cards?
Thanks, in advance, for your time and assistance.
Regards
R. W.

Yes, they can be installed in any slot other than the sup slots. Best practice is to install any Generation 1 cards before Generation 2 cards.

MDS 9513/Dense Line Cards

I know this has not been GA'ed as of yet, but does anyone have any doc's related to what is "going to be" released? different functionalities, etc? I'm also interested in the Dense port line cards that will be available soon (so they say-- 24port 2GB, 4GB modules, 48 port cards) any restrictions on the combination for which module can be installed? One more to throw out there is the backwards compatibility of the dense modules and the 9506 and 9509 directors (supervisor upgrades??) I know it was a loaded question, but customers are asking.
Thanks

Not even pre-release materials? I know these are probably hard to come by, but they must be out there. Thanks anyway.

The Cisco MDS 9000 Port Analyzer Adapter

Hi,
At my client place, we are having an issue with BackUp via TSM and a library.
We would like to analyse the traffic that pass in the Fiber Channel of our MDS-9513.
From what we saw, Wireshark, our soft to analyse network traffic is only using NIC card to analyse.
Is the only way to analyse the FC traffic to pass via "The Cisco MDS 9000 Port Analyzer Adapter" ?
If that is the only way, is there a way tor ent this equipment for the time necesery to analyse our trace ?
Thank you in advance for you help.
Christian Carrier

The Cisco Traffic Analyzer provides real-time analysis of SPAN traffic or analysis of captured traffic through a Web browser user interface. Traffic encapsulated by one or more Port Analyzer Adapters can be analyzed concurrently with a single PC and ntop, which is public domain software enhanced by Cisco for Fibre Channel traffic analysis. This Cisco Traffic Analyzer solution enables you to quickly determine the throughput for traffic between specific Fibre Channel sources and destinations, all traffic in a particular Virtual SAN (VSAN), or all network traffic. Round trip response times, SCSI I/Os per second, SCSI read vs. write traffic throughput and frame counts, SCSI session status and management task information are provided. Additional statistics are also available on Fibre Channel frame sizes and network management protocols.
For further information click this link.
http://www.cisco.com/en/US/products/hw/ps4159/ps4358/products_data_sheet09186a0080142d34.html#wp1002317

LMS 3.1 Device Discovery

Hi, Having had a fully operational version of Ciscoworks on a very old server we were advised to move it to a virtual server, with a new IP address. Unfortunately since then the device discovery is not collecting data on all devices on our network, and showing them as unreachable. Even though I have replaced the IP address in the configs on the network switches.
The odd thing is that it is finding 6 devices but not all of them. Just wondered if this is something anyone out there has seen before that may be able to shed some light for me.
Thanks
Jo

Hi,
Kindly make sure all the device are snmp reachable with the new IP from the CiscoWorks Server. However more information will be found by enabling the debugging for Device Discovery and then try to run the Device Discovery again.
To enable the debug for Device Discovery , kindly to Common Services > Device & Credentials > Device Discovery > Discovery Logging Configuration > select the modules you are using for device discovery along with Data Collector, Discovery DeviceInfo , Discovery Framework, Discovery util and run the device discovery again and then send the ngdiscovery.log from CSCOpx\log location.
Also kindly make sure you have make the required changes on the Schedule discovery settings as well since Schedule discovery have its own settings for Device Discovery as compared with Ad hoc Discovery settings.
Here is the good doc link created by Sir Joseph Clarke to understand the Device Discovery and for troubleshooting purposes.
https://supportforums.cisco.com/docs/DOC-9005
Note :- ngdiscovery.log contain information about the IP address of your device in the network.
Thanks,
Gaganjeet

Discovery of MDS IBM FC Bladecenter by Cisco MDS 9513

Similar Messages

Maybe you are looking for