Nice to know I have that straight. Roger A. Nall Manager, OSSNMS Remedy T-Mobile, USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of David Sanders Sent: Tuesday, April 22, 2008 12:27 PM To: [email protected] Subject: Re: Server Group Floating Write License Issue You could be right Roger - I am on a 7.1 server David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application See the ESS Concepts Guide tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger Sent: Tuesday, April 22, 2008 5:17 PM To: [email protected] Subject: Re: Server Group Floating Write License Issue David, I believe it is in v7.1 where the Server licenses are stored in the database. User license no longer have license keys. Of course I could be all wrong. HTH, Roger A. Nall Manager, OSSNMS Remedy T-Mobile, USA Desk: 813-348-2556 Cell: 973-652-6723 FAX: 813-348-2565 sf49fanv AIM IM RogerNall Yahoo IM -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of David Sanders Sent: Tuesday, April 22, 2008 12:12 PM To: [email protected] Subject: Re: Server Group Floating Write License Issue I could be wrong here, but it was my understanding that in ARS v7 the licenses are stored in the database, not in the file system. Although armonitor.conf still contains a pointer to the old location of the license files, these no longer exist. So, you will probably not have a multilicense file to delete. I am assuming that you have 2 ARS servers sharing one database, either the dev database (servers 1 and 3) or when you switch, the production database (servers 2 and 3). When you added server 3 to your production server and deleted the floating licenses, you were deleting the floating licenses from your production database (i.e. from server 2). What you should have done is to ADD the server license for server 3 to the one already visible (which was for server 2). The production and development servers need to have different server group names. You need to end up with the following licenses stored in the databases: Dev server database - AR Server Licenses for server 1 and server 3, and floating licenses for server group dev Prod server database - AR Server Licenses for server 2 and server 3, and floating licenses for server group prod In other words, the server 3 licenses needs to be added to both server groups. Bear in mind that when you connect to a server, the licenses you view are those stored in the database you are connecting to, not to the bit of hardware you happen to be connecting through. HTH David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application See the ESS Concepts Guide tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk ________________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Walters, Mark Sent: Tuesday, April 22, 2008 4:06 PM To: [email protected] Subject: Re: Server Group Floating Write License Issue There have been a number of defects with floating licenses and server groups in earlier releases of 7.0.1. The first thing you should do is get your servers all up to patch 6, I believe this resolves all the ones we are aware of. As also pointed out you should delete the /etc/arsystem/.multilicense file if you change the licenses on the server - this file will be recreated, with the current license details, on startup. Mark From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wangler, Dan Sent: 22 April 2008 15:36 To: [email protected] Subject: Server Group Floating Write License Issue ** Dear List We are trying to set up a Server Group. Below is our environment. We are running ARS 7.0.1 patch 3 on Sun Unix serverss with Solaris 9 with and Oracle 10. DB #1 and DB #2 are remote databases. In our development environment, the primary server is Server #1. In our production environment, the primary server is Server #2. We have another server that we are using for test, Server #3. It will be part of the production environment at the conclusion of our testing. We have different ar.conf files to point Server #3 to either the production or the development databases. Both Server #1 and server #2 are fully licensed with an AR Server and AR User Floating licenses. The floating licenses have been generated with the hostid for Server #1 in development and the hostid for Server #2 in production, each with a server group name of sg1. The license keys were also defined with SERVERGROUP=sg1 in the License Key Information field. Server #3 is fully licensed with an AR Server license key. When we first brought up Server #3 as part of the development environment using the ar.conf #1 file, we installed the same AR User Floating license key we have on Server #1. We checked the License Tab under the Server Information menu item in the Admin tool and saw 3 fixed write licenses and 5 floating write licenses corresponding to the license keys we had installed. We ran tests with users logging on to both machines. Each was able to see the data in the database. Each received warnings when the same records was being updated by moth. It appears to work as designed. After testing in the development environment, we shut down Server #3 and restarted it with the ar.conf file #2 to reflect the production environment. The server came up. According to the Server Group logs, Server #3 recognized it coming online and connecting to the Server Group. We still had the user floating license from Server #1 installed on Server #3. We deleted it and installed a key from Server #2. However, when we went to check the licenses in the license tab, it showed 3 fixed write licenses and 0 floating write licenses. We tried logging from both Server #2 and Server #3 with user floating licenses. We were able to work on Server #2 but only got a floating read licenses on Server #3. We tried several combination but never could get the floating write licenses to appear in the production environment. We then shut down Server #3 and restarted it with ar.conf file #1 to put it back into the development environment. But we saw the same results as in production. ARS is recognizing the server license but not the floating licenses. We have tried many difference combinations to get ARS to recognize the floating licenses but we have not been successful Has anyone had issues setting up a server group and floating write licenses and could not get the user licenses to connect? We feel we are overlooking something simple. But after a week of trial and error, we are no closer to solving this than when we started. Any ideas as to why the licenses are not connecting? Development Environment Production Environment Primary Server = Server #1 Primary Server = Server2 Database = DB #1 Database = DB #2 SERVERGROUP=sg1 SERVERGROUP=sg1 Test Server = Server 3 ar.conf for Development environment = ar.conf #1 ar.conf for Production environment = ar.conf #2 Dan Wangler, Team Lead, STARS Group Phone: 214-567-8304; email: [EMAIL PROTECTED] Client/Server Services, IT Operations Texas Instruments, Inc. 6500 Chase Oaks Blvd., MS 8401 Plano, Texas, 75023 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
