- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Looking for CLI listing for HP 4/16 SAN switch A79...
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
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
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
08-01-2011 08:31 AM
08-01-2011 08:31 AM
Can anyone point me to comprehensive documentation for using the CLI on a HP 4/16 SAN switch A7985A? Up to now everything I've had to do could be accomplished using the web interface. We are now working on tying a Cisco blade server, complete with it's own switch, into this switch. It is my understanding that in order to do this I must make a change to the ISL mode on that specific port, but I haven't found specific procedures on how to do this. Most documentation that I have found mentions having to disable the switch before making some changes. Is it necessary to do so to make this specific change? And again, is there documentation out there somewhere that covers the CLI commands?
TIA
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2011 09:09 PM - edited 08-01-2011 09:18 PM
08-01-2011 09:09 PM - edited 08-01-2011 09:18 PM
SolutionDisabling the switch depends on the change you need to make. Most changes are instant... some, like setting the Domain ID and maybe Compatibility mode... require disableing it.
What version of FOS is it running?
Assuming it is a Brocade switch, at the CLi run the command version, or check in the GUI.
Support page for said device: " http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=uk&docIndexId=64902&taskId=101&prodTypeId=12169&prodSeriesId=1143930 "
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
08-01-2011 10:16 PM
08-01-2011 10:16 PM
Re: Looking for CLI listing for HP 4/16 SAN switch A7985A
Hi,
if I understand correctly you need to connect a Cisco SAN switch to a Brocade SAN switch?
To do this you need to change the interop mode on the Brocade-switch (and on the cisco vsan as well).
I haven't double checked but I am quite confident that to change interop mode you need to disable the switch first.
There is a (legacy) document on HP SPOCK here:
http://h20272.www2.hp.com/Pages/spock2Html.aspx?htmlFile=an_fabric_interoperability.html
However, I wonder why it's in legacy. I'd read the fabric interopability document and then check out the commands that it uses to see if they are still valid.
Would be quite handy if you could just put the new Cisco switch in NPIV-mode (Access Gateway) and have it log on through an F_port instead of requiring a merge. If that would work then you'd not have to reboot the Brocade switch anyway. But if this functionality exists on the Cisco then I doubt it can integrate with a Brocade switch..