We have a standalone Service Monitor server, that resides on a separate server from Operations Manager, we have not amulti-server environment, and the communication between the servers is not enabled by a "trust" model addressed by certificates and shared secrets. Everything was working fine, we changed the passwords for local users in the server (administrator and casuser, by going to My Computer>Manage>Local Users and Groups>Users>(username)>Set Password), and the admin and guest passwords in Common Services by going to Common Services > Server > Security > Local User Setup > Modify My Profile
As soon as we changed these passwords, everything was still working fine
However, after the weekend, without making any other changes to the environment, when we tried to login to Service Monitor webpage via https://<Service_Monitor_IP_address>/CSCOnm/servlet/login/login.jsp with the admin account, we were unable to, even though we were sure the password was OK. We then login with guest account and went to Common Services > Server > Security > Local User Setup and found out that the admin user was not listed there anymore (even though nobody deleted it)
We then tried to reset the Common Services admin user password using CLI by following the procedure stated in this link:
We found out that the Service Monitor daemon was not started and we were unable to start it, neither from Windows Services, nor with net stop crmdmgtd and then net start crmdmgtd CLI commands
We then tried to login to Service Monitor webpage again with the admin account and we were able, but we got this error message:
The license file is invalid. Please click this link for information about obtaining a valid purchase license or click here for current licensing information Otherwise, please contact your Cisco representative for purchasing information.
Even though the license we have is still valid, and we have not exceed the maximum number of Cisco 1040 sensors registered for the license we have (we have only 4 Cisco 1040 sensors and the license is for 10)
We then click on "click here for current licensing information" to go to Common Services > Server Admin > Licensingand we get this error message:
Error communicating with License Server. License Server may be down. Please start the License Server, then refresh the page.
We have no new entries in the LicenseServer.log, the latest one is:
[Tue Jun 26 14:10:46 PDT 2007] Property file C:/PROGRA~1/CSCOpx\objects\licenses\log4j-license.properties 3334150400 62691 Buffer is0019bbc6 Buffer ise3f40000 Buffer isxxx Value from license is"xxx xxx" Flex host idxxx
In the License.log file since we were unable to start the Service Monitor daemon, we received the following entries in the License.log:
[ Mon Aug 02 02:37:39 BRT 2010 ] [Thread-839797] INFO com.cisco.nm.license.server.LicenseServer - Getting CMF features [ Mon Aug 02 02:37:39 BRT 2010 ] [Thread-839798] INFO com.cisco.nm.license.server.LicenseServer - Executing GetFeature [ Mon Aug 02 02:38:39 BRT 2010 ] [Thread-839799] INFO com.cisco.nm.license.server.LicenseServer - Executing GetFeature [ Mon Aug 02 02:38:39 BRT 2010 ] [Thread-839799] INFO com.cisco.nm.license.server.LicenseServer - Got VMS features Until Mon Aug 02 19:33:39 BRT 2010
Has anyone in the community experienced a similar problem? Does anyone has any idea what is the root cause of the problem and how to solve it?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...