- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- EBIPA (Enclosure Bay IP Addressing) option for Int...
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
03-02-2010 11:59 AM
03-02-2010 11:59 AM
EBIPA (Enclosure Bay IP Addressing) option for Interconnects?
Terri had run into this question:
Hello all,
I was told sometime in the past that the EBIPA (Enclosure Bay IP Addressing) option for Interconnects is really for those modules that don't have a CLI (like Pass-Thru and VC-FC). Is this correct?
I keep getting folks (customers and HP) who disagree and say if they set it in EBIPA it will set it on a Cisco Ethernet switch, Cisco MDS SAN Switch, Brocade SAN switch, GBE2c, etc...which would mean the OA would have to understand all those different switch operating systems...
Clarification?
Monty had an answer:
The OA EBIPA feature is based on DHCP - so this feature is independent of the device operating system.
To use OA EBIPA to set the IP address for a bay you need the following prerequisites:
1. The blade or interconnect module must use the enclosure management network
a. Cisco Ethernet modules can be configured to use the enclosure management network but default to VLAN management on an uplink
b. Virtual Connect modules always use the enclosure management network
2. The blade or interconnect module management processor must use – or be configured to use - DHCP to obtain its IP address
3. The OA must be configured to provide an EBIPA IP address, etc for that bay – OR – the OA management port must be connected to a network with a DHCP server
Share your experiences in this area.