- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Best practices for naming new blades in a new data...
BladeSystem - General
1823420
Members
2500
Online
109655
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
Forums
Discussions
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО10-18-2007 12:59 AM
тАО10-18-2007 12:59 AM
Best practices for naming new blades in a new data-center
I have a customer that is purchasing their first set of blades. The customer has two data centers in two different cities within the same state. The blades are the go forward solution for production / development / testing. The customer has asked me to find out what are the best practices for a naming convention for the racks & enclosures?
For the rack I have suggested a three character city code, then a 3 character code for PRD/DEV/TST, followed by a four character rack number (R001).
For the enclosure I was thinking of the three character city code, the four character rack code then a five character enclosure code (ENC01).
My thought was that if a problem arose then if you hear the name of a rack / enclosure you knew which city it was in and approximate location. The customer does make use of a floor grid (A,B,C..1,2,3) on the walls. I was thinking about including this info in the rack name to identify a specific location.
I welcome any and all suggestions that are posted and Thank You in advance for your time.
For the rack I have suggested a three character city code, then a 3 character code for PRD/DEV/TST, followed by a four character rack number (R001).
For the enclosure I was thinking of the three character city code, the four character rack code then a five character enclosure code (ENC01).
My thought was that if a problem arose then if you hear the name of a rack / enclosure you knew which city it was in and approximate location. The customer does make use of a floor grid (A,B,C..1,2,3) on the walls. I was thinking about including this info in the rack name to identify a specific location.
I welcome any and all suggestions that are posted and Thank You in advance for your time.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2007 05:22 AM
тАО10-21-2007 05:22 AM
Re: Best practices for naming new blades in a new data-center
Hello Jeff,
That indeed is a flawless way to name the Enclosure & rack; Easy, simple & very efficient; Yes, in case of trouble, you can know where exactly to look for !
& just for the Record:
Enclosure Name├в The default setting is a unique factory-assigned name. The accepted character values are 0├в 9, A├в Z, a├в z, -, _ and . is used to signal the end of the name.
NOTE: Do not use the symbol in the middle of a text field. Entries in text fields will be
truncated to the last character before the symbol.
TIP: Select Clear from the navigation bar to quickly clear entries in text fields up to the symbol.
Rack Name├в The default setting is UnnamedRack The accepted character values are 0├в 9, A├в Z, a├в z, -, _ and . is used to signal the end of the name.
Insight Display PIN#├в The default setting is Not Set. HP recommends that you set a PIN to protect the enclosure configuration from unauthorized changes. You must enter the PIN after each inactivity period to change options in the Enclosure Settings menu. The accepted character values are 0├в 9, A├в
Z, a├в z, -, _ and . is used to signal the end of the name.
h20000.www2.hp.com/bc/docs/support/SupportManual/c00698286/c00698286.pdf
James.
That indeed is a flawless way to name the Enclosure & rack; Easy, simple & very efficient; Yes, in case of trouble, you can know where exactly to look for !
& just for the Record:
Enclosure Name├в The default setting is a unique factory-assigned name. The accepted character values are 0├в 9, A├в Z, a├в z, -, _ and . is used to signal the end of the name.
NOTE: Do not use the symbol in the middle of a text field. Entries in text fields will be
truncated to the last character before the symbol.
TIP: Select Clear from the navigation bar to quickly clear entries in text fields up to the symbol.
Rack Name├в The default setting is UnnamedRack The accepted character values are 0├в 9, A├в Z, a├в z, -, _ and . is used to signal the end of the name.
Insight Display PIN#├в The default setting is Not Set. HP recommends that you set a PIN to protect the enclosure configuration from unauthorized changes. You must enter the PIN after each inactivity period to change options in the Enclosure Settings menu. The accepted character values are 0├в 9, A├в
Z, a├в z, -, _ and . is used to signal the end of the name.
h20000.www2.hp.com/bc/docs/support/SupportManual/c00698286/c00698286.pdf
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2007 08:28 AM
тАО10-21-2007 08:28 AM
Re: Best practices for naming new blades in a new data-center
Are they using RDP and SIM?
RDP uses the right most 15 characters of
so newly deployed servers will not have the function or City displayed in their name when they first boot PXE into RDP.
SIM can link enclosures to racks in reports so there is no need to duplicate information.
I'd make the enclosure name the minimum possible eg E001...E999. And each enclosure is best named uniquely as you will get several E001 displayed in SIM if you sort by name and they are not unique. Can get confusing.
I try and recommend that customers make this information the minimum.
Do you really need 3 chars for city?
Why PRD/DEV/TST why not P/D/T?
Dont they number their racks already?
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP