Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Blue

Update jrmuser.properties after hostnamechange.pl?

With LMS 3.1, does jrmuser.properties need to be manually updated after running hostnamechange.pl? The former still has the old hostname appended in there. Or does it get updated automatically once I start dmgtd?

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Update jrmuser.properties after hostnamechange.pl?

Yes, it must be unique. If you have two servers, serverA and serverB, you must use a unique jrm ServiceName on both servers regardless of the LMS version. Both ServiceNames MUST NOT contain dots (thus the hostname component must be the short hostname).

3 REPLIES
Cisco Employee

Re: Update jrmuser.properties after hostnamechange.pl?

It is not necessary. All that needs to happen is that the jrm service name must be unique on the network. If you would like to update this file, be sure you ONLY use the short hostname. If you use the FQDN, this will break jrm.

Blue

Re: Update jrmuser.properties after hostnamechange.pl?

Does it only have to be unique across two same-version LMS boxes? What about one LMS 2.6 (ServiceName=JrmServiceManager_hostnameA.fqdn.com) and one LMS 3.1 (ServiceName=JrmServiceManager_hostnameA)?

Cisco Employee

Re: Update jrmuser.properties after hostnamechange.pl?

Yes, it must be unique. If you have two servers, serverA and serverB, you must use a unique jrm ServiceName on both servers regardless of the LMS version. Both ServiceNames MUST NOT contain dots (thus the hostname component must be the short hostname).

164
Views
0
Helpful
3
Replies