Christian, Thanks for sharing those emails. I had to purge manually all of my license keys on the dev server when the NIC switched. They never said just change 28 in the Host ID to 29, would have been alot easier. But I thought the Host ID was somehow tied into the license key and would not have accepted that.
I'm alert now to it and since we're going to end up switching out our production server to another one, I'll definitely be checking that out. Thanks, Susan On 4/23/07, Christian Rom <[EMAIL PROTECTED]> wrote:
** I had the exact same issue happen twice. Got my licenses based on host id in Admin tool, installed a few more products and CMDB with associated reboot and suddenly the (Win2003) server was using the other host id and my licenses did not work. See BMC's responses below. I ended up disabling the second NIC since this was just a sandbox but that may not be an option for a production box. Rgds, Christian H. Rom Schlumberger - Service Desk Engineering ------------------------------- -----Original Message----- From: Remedy Support [*mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]> ] Hello Chris, I am assisting on this issue and have had this question come up before. I understand what you're asking. We know that the AR Server uses the snmp protocl to get the host id. There is a function call and algorithm as to how it finds the host id of the NIC. This involves something called the Lana Number of the NIC. Lana is short for LAN Configuration. The Windows OS assigns a lan number to each network adaptor on the system and function calls to get a MAC Address utilize this number. Here is a KB that talks a little about this from Microsoft: * http://support.microsoft.com/kb/118623/en-us*<http://support.microsoft.com/kb/118623/en-us> The problem with this KB is that it talks about using the NetBios protocol. We used to do that a long time ago and were told NetBios is old and not the best way to do it. We have used snmp to do the same thing since version 5.0. The actual logic used in contained in the code and we don't have access to that to tell you "exactly" how the host id is found. We do know though that we're getting the Lana number 1, which is the first valid NIC on the system. We make no other effort to detemine if this is correct, or to prompt the user that this is the NIC we're licensing off of. A common question or issue that customers ask about is that they have 2 NICs, a primary and a backup. All network traffic comes through the primary NIC yet AR Server licensing is bound to the backup NIC, is this okay? We answer yes ...the AR Server does not care if the NIC is in use or not. I has to be enabled, but thats it. We can bind off any NIC that is enabled on the server. Here is another case ....lets say you select the AR Server license from the Product Feature menu in the Add/Remove license window. It auto-populates the host id. The licenses are bound to a different host id on the same server. You can manually type in the other host id and it will work. Just because the function call to find and auto-populate the host id was different doesn't mean you can't license off another valid NIC on the server. The function call is just grabbing the network adaptor associated with Lana Number 1 on the OS. When validating the license key against the server, it will cycle through all valid network adaptors. Now please correct me if I'm wrong, but it sounds like what you are seeing is that AR Server and related products all used one method to get the host id, but when it came to the Incident Management product, suddenly it must have used a different method because it found a different host id, correct? It is possible that the there was a change to the server sometime between the licensing of the AR Server and the Incident Management. We remember from the old pre-5.0 licensing days that we could NOT license off any valid NIC on the server. It had to be the Lana Number `1 NIC. We had to use a Microsoft utility called Lana Config to change the LANA number the OS associated with the NICs so that the NIC we wanted the licenses bound to was Lana number 1. This change would not take affect until the server was rebooted. So its possible that a reboot of the server changed the ordering of the lana numbers associated with the NICs. Since this is a separate product.... I don't want to discount the possibility that the method for determining the host id with Incident Management is in fact different than the other AR System products. I will definitely look into this. I'll let you digest this information and will be prepared for questions and clarification that you may have. Kind Regards, XXX -----Original Message----- XXX, I have already resolved the issue by disabling one NIC and using the other. I am not asking for your help in configuring my server, but for an explanation on how AR System picks the host ID on systems with two NICs The question is: why did AR System initially use the MAC address of the first NIC and let me add all the licenses successfully and install CMDB 2.0 but when I try to install Incident Management it suddenly saw the other NIC which translates to the host ID. Rgds, chris -----Original Message----- From: Remedy Support [*mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>] Chris, Evidently one of the host id's on the NIC card is preempting the other. We don't actuall work with the NIC card issues in our support center. Please talk to your internal people regarding the NIC card and ask them how to select (stablize) the primary host id that the NIC card is using. Hopefully they can make the host id that the licenses are tied to the primary one, if not you will need to contact us to have them purged as Trial keys cannot be purged online. Kind regards, XXX __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
