VVB Login Issue

[Shibinbly]

Hello Experts,

I recently upgraded my lab VVB from 12.5.1 to 12.5.1SU and it went fine however when I did a switch version in order to test the back-out I am not able to login to VVB CLI/Web , the switch version appears to be fine. Any idea why it happened and do I now need to follow the CLI admin password reset procedure? kindly advise.

[bill.king1]

What specific version of 12.5.1 did you go to? And when you say you can't login, what happens (i.e. you get error message in GUI, you get error message in CLI, etc.

[Shibinbly]

Hi Bill ,

I moved to 12.5.1SU .It says wrong password even though I am typing the correct one .

Regards,

Shibin

[bill.king1]

What SU/ES/COP file did you apply? And you're getting the wrong password message in both the GUI and CLI?

[Shibinbly]

I have upgraded to 12.5.2.99000-275 (12.5.1SU) and applied COP file ucos.v1_java_deserial-CSCwd64245.cop.sgn. In CLI it I get access denied error and in GUI wrong user ID / Password.

[bill.king1]

You say 12.5.2 but 12.5.1 in original post. What specific ES did you apply? There are some defects re: not being able to log in for instance like https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv79257

[Shibinbly]

Hi Bill,

I have uploaded the correct version for your reference.

[smcarthur444]

Same upgrade path, 12.5(1) to SU1 (UCSInstall_VVB_12_5_2_UCOS_12.5.2.99000-275.sgn.iso)

We switchover to 12.5(2) installed COP: ucos.v1_java_deserial-CSCwd64245.cop.sgn

For this customer, after switchover & after COP install, we get 404 when trying to reach URL uccxservice or appadmin - either IP or FQDN - doesn't matter.

TAC gathered logs and they are investigating. Tomcat seems to be acting up:

test - tomcat_memory       : Failed - Tomcat's memory usage is unusually high.

test - tomcat_connectors   : Failed - The HTTP and HTTPS ports are not responding to local requests.

[smcarthur444]

Cisco TACs response for our issue.

From the install logs I found there are two ungraceful shutdown events. This means that the system was not shutdown gracefully with utils system shutdown command so that can cause file system corruption: https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/220970-recover-from-ungraceful-shutdowns-on-vos.html

09:20:08 | root: Boot 12.5.1.99000-21 Start

 06:38:30 | root: Boot 12.5.1.99000-21 Start

 22:58:28 | root: Boot 12.5.2.10000-281 Start

23:20:28 | root: Boot 12.5.2.10000-281 Start

The recommendation would be to rebuild the servers to ensure file integrity of the system, however before consider that option I will escalate to BU and see if there’s an additional troubleshooting step to try with the Tomcat issue.

While I escalate to BU, I’d like you to try the following steps:

1. Run utils system switch-version command after hours in one of the VVB servers.
2. Once server is in 12.5(2), mount the Recovery Disk ISO on VVB server and run the File System check: http://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/118948-technote-cucm-00.html
3. Unmount the Recovery Disk ISO and boot the VM to load the VVB server. Verify if web access works.

[bill.king1]

I thought based on this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwb26895 that there still wasn't a way to confirm if you really need to rebuild or not?

[smcarthur444]

Thanks Bill. I threw that back at TAC.