- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: San Switch 16
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
тАО04-13-2004 08:09 PM
тАО04-13-2004 08:09 PM
Can I/Do I need to upgrade the firmware on the existing 2 switches before connecting the new ones?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2004 12:58 AM
тАО04-14-2004 12:58 AM
Solutionyou don't need to update the firmware, but there is one parameter you need to verify before you connect the new ones:
fabric.ops.mode.pidFormat
Also called CoreSwitchPID.
(you can check it by running configShow from a telnet prompt)
It's needed for communication larger switches (more than 16 ports), something about the way ports are addressed.
1Gbit Switches had this default set to 0, newer 2Gbit Switches have it set to 1. For the 2 switches to merge into a single fabric, some parameters have to be identical, including this parameter. If it's not, when you connect the 2 switches, the interlink port LED will blink, and the switch will report an "incompatible" E-port. To change this, you must disable the switch (switchdisable), then run the configure command. Modify Fabric Parameters, accept default for all values except CoreSwitchPID format. Then run "switchenable" to re-enable the switch. It doesn't really matter on which switch you do it, as you don't have any 32 or 64-Port switches (unless you plan to purchase any in the future). So set it to the same value on all switches.
Also make sure the new switches have no zoning config on them before you add them to the existing fabric. Then they will accept the zoning info from the existing switches.
The SAN Design Reference Guide - Chapter 3, has some info, as well as the Fabric OS 3.1.x/4.1.x Procedures Guide.
http://h200007.www2.hp.com/bc/docs/support/SupportManual/c00093939/c00093939.pdf
http://h200001.www2.hp.com/bc/docs/support/SupportManual/lpg29430/lpg29430.pdf
Regards,
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2004 06:44 AM
тАО04-14-2004 06:44 AM
Re: San Switch 16
I have attached an example how to turn it on on the 1 GBit switches. Turning it off on the 2 GBit switches will look similar.
HP suggest that you turn it on, but, as Stephen has written, that requires you to disable of the switch. If you have a redundant fabric you can do this one-by-one, but it has another effect:
the fibre channel adresses will change after you have enabled the bit. That means that some operating systems like HP-UX (and I beleive AIX) will no longer see the disks, so you have to reconfigure new I/O paths.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2004 06:39 PM
тАО04-14-2004 06:39 PM
Re: San Switch 16
Thanks very much for the info and the links. All servers currently have 2 cards in, so I shall take down the switches one at a time to make the necessary changes.
Kind Regards
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2008 07:14 PM
тАО04-10-2008 07:14 PM
Re: San Switch 16
1. Check PID. PID should be IDENTICAL to both switches.
2. Chech Domain ID. ID should be VARIOUS for both switches.
3. Check ports type, through which are connected switches.
Port type should be E_port:
portcfgislmode or portcfglongdistance (this command requires an Extended Fabrics license).
4. If you connect IDENTICAL switch, on both switches should be off (disable) interopmode:
interopmode 0.
If on one switch interopmode enable, and on other switch interopmode disable, that will arise the following error:
E-Port segmented,(incompatible),
and Port Status LED will be "Slow-flashing green (on one second, off one second)" that means "Port is online but segmented, indicating a loopback cable or incompatible switch".