- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: HP StorageWorks 400 Multi-Protocol Router
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 08:18 AM
тАО02-12-2009 08:18 AM
HP StorageWorks 400 Multi-Protocol Router
Have 2 x new HP SW 400 MPR that we are trying to connect to an MSA1000. Connect the Server(s) via Fibre directly to the MSA1000 and everything works as expected and can configure via the ACU. If we try and go through the 400 MPR(s) we cannot see the MSA1000 controllers (or disks).
The Port Status lights on the front of the MPR are flashing amber for 2sec at a time, which the documentation suggests may mean that the ports have been disabled (Default?). I have run the portCfgPersistentEnable cmd and restarted to no avail.
Any advice appreciated - Current Fabric OS v5.3
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 09:47 AM
тАО02-12-2009 09:47 AM
Re: HP StorageWorks 400 Multi-Protocol Router
Default behavior on Brocade Fabric devices is to allow no devices to talk to each other.
Why do you have MPR's? and not regular SAN Switches?
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-12-2009 09:55 AM
тАО02-12-2009 09:55 AM
Re: HP StorageWorks 400 Multi-Protocol Router
i) No zoning configured as yet, as I cannot see any devices to add to my zones.
ii) You have a way to enable devices to communicate via the Brocade? I haven't yet found one.
iii) Not sure about why they are MPR and not SAN Switch, think it was recommended as a solution to do with SAN to SAN replication - Same Brocade Web Tools interface as our other SAN switches so I guess it can do the same?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 08:15 AM
тАО02-13-2009 08:15 AM
Re: HP StorageWorks 400 Multi-Protocol Router
Yes, this is different behavor from the other switches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 09:02 AM
тАО02-13-2009 09:02 AM
Re: HP StorageWorks 400 Multi-Protocol Router
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2009 09:18 AM
тАО02-13-2009 09:18 AM
Re: HP StorageWorks 400 Multi-Protocol Router
My experience is that a portenable still needs to follow the portcfgperistentenable when done via the cli (telnet/ssh) but not when done with webtools.
You may also need to lock the portspeed at 2GB or 1GB, depending upon the device. I've had some 2GB hbas refuse to sync up to a 4GB port when both are set to auto-negotiate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-19-2009 08:41 AM
тАО02-19-2009 08:41 AM