- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MC Service Guard Cluster and Package Naming Conven...
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-08-2012 12:25 AM
06-08-2012 12:25 AM
MC Service Guard Cluster and Package Naming Conventions
Hi,
Are there any conventions / restrictions on Cluster / Package names in MCSG.
If so, pl let me know the document i can refer to.
Ramesh KR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2012 08:25 AM
06-12-2012 08:25 AM
Re: MC Service Guard Cluster and Package Naming Conventions
No,
There is no such naming convention for Cluster and packages. Usually packages are named as per the type of DB or applications will run on Cluster. It's not mandatory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2012 12:30 PM
06-13-2012 12:30 PM
Re: MC Service Guard Cluster and Package Naming Conventions
Hi Ramesh,
There is no such rule but please use logical name related to environment.
regards
RC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2012 10:50 PM
06-13-2012 10:50 PM
Re: MC Service Guard Cluster and Package Naming Conventions
HI
You have to put as you wish.
Ajin.S
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-25-2012 04:39 PM
07-25-2012 04:39 PM
Re: MC Service Guard Cluster and Package Naming Conventions
While there are no specific conventions for naming clusters or packages, you should consult the Managing Serviceguard Manual. For example, it states:
CLUSTER_NAME
The name of the cluster as it will appear in the output of
cmviewcl and other commands, and as it appears in the
cluster configuration file.
The cluster name must not contain any of the following
characters: space, slash (/), backslash (\), and asterisk (*).
NOTE: In addition, the following characters must not be
used in the cluster name if you are using the Quorum Server:
at-sign (@), equal-sign (=), or-sign (|), semicolon (;).
These characters are deprecated, meaning that you should
not use them, even if you are not using the Quorum Server,
because they will be illegal in a future Serviceguard release.
All other characters are legal. The cluster name can contain
up to 39 characters (bytes).
CAUTION: Make sure that the cluster name is unique
within the subnets configured on the cluster nodes; under
some circumstances Serviceguard may not be able to detect
a duplicate name and unexpected problems may result.
In particular make sure that two clusters with the same name
do not use the same Quorum Server; this could result in one
of the clusters failing to obtain the Quorum Server’s
arbitration services when it needs them, and thus failing to
re-form.
Likewise, there is a statement for package_name:
package_name
Any name, up to a maximum of 39 characters, that:
• starts and ends with an alphanumeric character
• otherwise contains only alphanumeric characters or dot (.), dash (-), or underscore (_)
• is unique among package names in this cluster
IMPORTANT: Restrictions on package names in previous Serviceguard releases were less
stringent. Packages whose names do not conform to the above rules will continue to run, but
if you reconfigure them, you will need to change the name; cmcheckconf and cmapplyconf
will enforce the new rules.
It's always worth consulting the manual on precise guidelines for each parameter.