- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Enclosure Bay IP Addressing (EBIPA) issue
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
06-07-2010 12:11 PM
06-07-2010 12:11 PM
Enclosure Bay IP Addressing (EBIPA) issue
Dave had a question about EBIPA and how to calculate subnet addresses and what is reserved for what:
****************************************************************************************************************
Have a customer using a subnet mask of 255.255.252.0 and filled in the first bay with address 172.16.230.249 and select autofill. Bay 7 gets the address of 172.16.230.255 and bay 8 gets the address 172.16.231.0. I know EBIPA is doing what its designed to do, and the customer hasn’t complained that they cannot reach the iLO in bay 8 but I thought IP address “xxx.xxx.xxx.0” was reserved for lack of a better term. Is this a potential issue for this customer?
**********************************************************************************************************
Cullen and Monty chimed in:
********************************************************************************************************
Cullen:
There are two “reserved” addresses used for broadcast in a network: host bits all 0, and host bits all 1.
The network portion of 172.16.231.0/22 (255.255.252.0) is 172.16.228.0 and the host portion is 3.0 (or binary 1100000000) which is neither all 0 nor all 1.
Monty:
IP Subnet Calculator is your friend J
http://www.subnet-calculator.com/subnet.php?net_class=B
If you select Class B and 22 Mask Bits and plug in 172.16.230.251
The calculator indicates the Host Address Range is 172.16.228.1 – 172.16.231.254.
Both 172.16.230.255 and 172.16.231.0 are allowed host IP addresses.
Only two IP addresses are reserved in all subnets – the first .0 and the last .255. The ones in between for subnets larger than 255 are allowed.
Cullen:
Real men figure out subnet masks in their head.
*******************************************************************************************************
Good discussion and good info with the calculator. Any other good tools you use?