[cisco-voip] CUCM 10.5 Missing CLI commands

[Techguy]

I don't think the builtin priv 4 account can be renamed. You can reset the
password for it but not rename the username.

Thanks
TG
Correct, you cannot rename the account name, just reset the password.

I think TAC can do it with root access, if it is a material issue.
Otherwise, you can rebuild the node.

-Ryan


-------- Original message --------
From: Dave Wolgast
Date:12/03/2015 12:26 PM (GMT-05:00)
To: Ryan Huff ,"Cisco VOIP Newsletter - puck.nether.net"
Subject: Re: [cisco-voip] CUCM 10.5 Missing CLI commands

Answering my own question now...I managed to guess the account name and
password. I want to beat whoever built this cluster.

Just to confirm, there is no way to rename the default administrator
account, right?

It will work just fine but the documentation will be a mess.

On Thu, Dec 3, 2015 at 12:12 PM Dave Wolgast <dwolgast at gmail.com> wrote:

> Nailed it.
>
> The account I am using, 'administrator' has privilege level 0. I note that
> that account on the other servers in the cluster has privilege level 4.
>
> The question becomes, is there a way to find out (with privilege level 0)
> what the original account was. I may be able to crack the password. If not,
> I will have to do a recovery.
>
> Thanks for the assist.
>
> On Wed, Dec 2, 2015 at 10:56 PM Ryan Huff <ryanhuff at outlook.com> wrote:
>
>> If you do go the route of re-building your subs; be mindful of any custom
>> moh files ... etc (they're easy to forget).
>>
>>
>> *file list activelog mohprep*
>>
>> *file get activelog mohprep/<filename>*
>>
>>
>> = Ryan =
>>
>>
>>
>> Email: ryanthomashuff at outlook.com
>>
>> Spark: ryanthomashuff at outlook.com
>>
>> Twitter: @ryanthomashuff <http://twitter.com/ryanthomashuff>
>>
>> LinkedIn: ryanthomashuff <http://linkedin.com/in/ryanthomashuff>
>>
>> Web ryanthomashuff.com
>>
>>
>> ------------------------------
>> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of
>> Ryan Huff <ryanhuff at outlook.com>
>> *Sent:* Wednesday, December 2, 2015 10:43 PM
>> *To:* Dave Wolgast; Cisco VOIP Newsletter - puck.nether.net
>> *Subject:* Re: [cisco-voip] CUCM 10.5 Missing CLI commands
>>
>>
>> My initial thoughts are that somehow you are not using the default
>> platform administrator account?
>>
>>
>> Can you run;
>>
>>
>> "show myself"
>>
>> AND
>>
>> "show account"
>>
>>
>>  What are the results?
>>
>>
>> = Ryan =
>>
>>
>>
>> Email: ryanthomashuff at outlook.com
>>
>> Spark: ryanthomashuff at outlook.com
>>
>> Twitter: @ryanthomashuff <http://twitter.com/ryanthomashuff>
>>
>> LinkedIn: ryanthomashuff <http://linkedin.com/in/ryanthomashuff>
>>
>> Web ryanthomashuff.com
>>
>>
>> ------------------------------
>> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of
>> Dave Wolgast <dwolgas1 at rochester.rr.com>
>> *Sent:* Wednesday, December 2, 2015 10:35 PM
>> *To:* Cisco VOIP Newsletter - puck.nether.net
>> *Subject:* [cisco-voip] CUCM 10.5 Missing CLI commands
>>
>> I just did a 5- node 7.1(5)->10.5(2) PCD migration, which appeared to go
>> pretty well. What I have noticed, though, is that two of my subscribers are
>> missing commands from the CLI.
>>
>> One thing I needed to do for the migrated cluster was to add DNS servers
>> and add a domain, but on 2 of the 5 servers, there was no 'set network'
>> option. I thought maybe a reboot would help, but alas, on the same servers,
>> there was no 'utils system' commands.
>>
>> Anybody ever seen anything like this before? I assume I will just be
>> rebuilding these subscribers manually, but it seems awfully strange,
>> especially since it didn't happen to every server.
>>
>> Baffled,
>> Dave Wolgast
>> Livonia, NY
>>
> --
> Dave Wolgast
> Livonia, NY
> 585.402.3375
>
-- 
Dave Wolgast
Livonia, NY
585.402.3375

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160112/b04159bb/attachment.html>