HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Licensing issue due to incorrect IP detection
Server Management - Systems Insight Manager
1828861
Members
2581
Online
109985
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
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
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
11-07-2005 03:40 AM
11-07-2005 03:40 AM
Licensing issue due to incorrect IP detection
I have a small (so far since we only use this in test atm) issue with PMP and licensing.
Actually it is an error in SIM itself from what I believe, and it comes from incorrect detection of servers with multiple IP adresses, for example Veritas clusters.
And no, the latest SMH update does not solve this issue.
Anyway, what happens is that let's say I have a 6-node Veritas cluster running SQL Server, with 6 instances. One instance on each node.
The point of this is that in case one node fails the SQL server database instance can then fail over to another node. This cluster is not in anyway connected to SIM except that I want SIM to manage the hardware just as with any other server I have.
So, each node has its own IP adress, and in addition they have the IP adress to the SQL instance. That makes 2 IP adresses per server.
Now I set up PMP before SQL was installed, so I licensed the physical server A on IP adress 1, but when the SQL instance is running SIM will find server A on IP 2. (I have tried IP binding in the SMH to adress 1 with no success)
First of all this will result in SIM not correctly identifying the server as it finds the machine on the wrong adress. This is just an issue in detection, but could be ever so troublesome since the adress it finds could then fail over to another node (and frequently does, when we do maintenance on one node and run the instance on another).
However except for that issue there's also a licensing problem, since I licensed server A on IP 1, but now server A is detected as IP 2 (even if IP 1 is still responding). This makes the server unlicensed and I need to use another license for it and I cannot revoke the already used one (which I don't want to do since its the proper IP for the server).
So I need two licenses for one server.
Now in case of problems or maintenance, I may want to fail over the other instances to the node, and in a 6-node cluster the possible combinations are then 7 IP adresses (1 physical + 6 virtual) on 6 machines = 42 IP adress combinations. Meaning 42 licenses for 6 servers.
So what I'd like to know is if there is any way to make SIM aware of Veritas clusters in the same way that it automatically finds MSCS clusters on any server where installed and correctly binds that information to the right name and adress ?
(OS'es where seen are Windows 2000 SP4, Windows 2003 RTM or Windows 2003 SP1, with Veritas cluster 2.0 and Veritas Foundation 4.2 or 4.3)
Actually it is an error in SIM itself from what I believe, and it comes from incorrect detection of servers with multiple IP adresses, for example Veritas clusters.
And no, the latest SMH update does not solve this issue.
Anyway, what happens is that let's say I have a 6-node Veritas cluster running SQL Server, with 6 instances. One instance on each node.
The point of this is that in case one node fails the SQL server database instance can then fail over to another node. This cluster is not in anyway connected to SIM except that I want SIM to manage the hardware just as with any other server I have.
So, each node has its own IP adress, and in addition they have the IP adress to the SQL instance. That makes 2 IP adresses per server.
Now I set up PMP before SQL was installed, so I licensed the physical server A on IP adress 1, but when the SQL instance is running SIM will find server A on IP 2. (I have tried IP binding in the SMH to adress 1 with no success)
First of all this will result in SIM not correctly identifying the server as it finds the machine on the wrong adress. This is just an issue in detection, but could be ever so troublesome since the adress it finds could then fail over to another node (and frequently does, when we do maintenance on one node and run the instance on another).
However except for that issue there's also a licensing problem, since I licensed server A on IP 1, but now server A is detected as IP 2 (even if IP 1 is still responding). This makes the server unlicensed and I need to use another license for it and I cannot revoke the already used one (which I don't want to do since its the proper IP for the server).
So I need two licenses for one server.
Now in case of problems or maintenance, I may want to fail over the other instances to the node, and in a 6-node cluster the possible combinations are then 7 IP adresses (1 physical + 6 virtual) on 6 machines = 42 IP adress combinations. Meaning 42 licenses for 6 servers.
So what I'd like to know is if there is any way to make SIM aware of Veritas clusters in the same way that it automatically finds MSCS clusters on any server where installed and correctly binds that information to the right name and adress ?
(OS'es where seen are Windows 2000 SP4, Windows 2003 RTM or Windows 2003 SP1, with Veritas cluster 2.0 and Veritas Foundation 4.2 or 4.3)
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-08-2006 07:33 PM
02-08-2006 07:33 PM
Re: Licensing issue due to incorrect IP detection
Ok, this one's now sent in as a support case.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP