- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: OA network connectivity
BladeSystem - General
1753797
Members
7388
Online
108799
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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-2007 02:28 PM
08-01-2007 02:28 PM
It's my understanding the the network ports for OA, all iLO's and interconnect management ports all run through the one copper connection on the OA module. I'm assuming then that all of the IP's for these connections must be on the same subnet.... or is there some way that they don't have to be any still make everything work?
Thanks,
Eric
Thanks,
Eric
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2007 02:43 AM
08-02-2007 02:43 AM
Solution
Eric,
you are correct. All of the ILOs, Interconnect Modules and the OAs reside on the same layer 2 broadcast domain. They would all need to be in the same IP subnet for proper communication unless you chose to have 2 or more IP subnets on the same layer 2 broadcast domain (not recommended).
On GBE2c and Cisco 3020 switches, you can disable the interface connecting back to the OA (GBE2c - IF 256 & Cisco 3020 - Fa0) and use an in-band management IP address that would be accessible through the switch's uplinks.
ILO2's have the option to configure VLAN tags but I don't think the OA will allow tagged frames to pass. I haven't tried this so it may be something to look at which would allow you to separate the ILOs on to a different network. But this may not work yet and could be an enhancement request.
you are correct. All of the ILOs, Interconnect Modules and the OAs reside on the same layer 2 broadcast domain. They would all need to be in the same IP subnet for proper communication unless you chose to have 2 or more IP subnets on the same layer 2 broadcast domain (not recommended).
On GBE2c and Cisco 3020 switches, you can disable the interface connecting back to the OA (GBE2c - IF 256 & Cisco 3020 - Fa0) and use an in-band management IP address that would be accessible through the switch's uplinks.
ILO2's have the option to configure VLAN tags but I don't think the OA will allow tagged frames to pass. I haven't tried this so it may be something to look at which would allow you to separate the ILOs on to a different network. But this may not work yet and could be an enhancement request.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP