[cisco-voip] Installation new phone firmware cop file installation

2016-01-29 Thread Reto Gassmann 
Hello Group

I have a UCM cluster 10.5 with 8 servers. TFTP service runs on the
publisher.
I now have a new 8831 to install and have to Upgrade the Firmware
(cmterm-8831-sip.10.3.1SR2EU.k3.cop.sgn) in order to get the 8831 running.

Is it ok to install the cop file on the TFTP Server and restart the TFTP
after installtion or so I have to install the cop file on every server in
the cluster?

Tanks a lot and have a great weekend
Regards Reto
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Installation new phone firmware cop file installation

2016-01-29 Thread Haas, Neal 
Just on the TFTP server.

Thank you,
Neal Haas

Neal Haas

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Reto 
Gassmann
Sent: Friday, January 29, 2016 6:55 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Installation new phone firmware cop file installation

Hello Group

I have a UCM cluster 10.5 with 8 servers. TFTP service runs on the publisher.
I now have a new 8831 to install and have to Upgrade the Firmware 
(cmterm-8831-sip.10.3.1SR2EU.k3.cop.sgn) in order to get the 8831 running.

Is it ok to install the cop file on the TFTP Server and restart the TFTP after 
installtion or so I have to install the cop file on every server in the cluster?

Tanks a lot and have a great weekend
Regards Reto
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 core question - AlterateSyslogAlarm malloc backtrace

2016-01-29 Thread Ryan Ratliff (rratliff) 
Until you identify what specifically spiked then you don’t know what to prevent.

Do you have a TAC case open yet?

-Ryan

On Jan 28, 2016, at 7:42 PM, Erick Bergquist 
> wrote:

Thanks Ryan. Nothing really standing out on the ESXi side.

Any suggestions to prevent this in future?

The VMware KB articles suggest a higher timeout on application side so 
transient issues and conditions on the VM side of things don't negatively 
impact the application.

On Friday, January 22, 2016, Ryan Ratliff (rratliff) 
> wrote:
That's your culprit right there. That 16 second sdlrouter thread timer is one 
of the few things I bet hadn't changed since 4.x.

Can you look at esxi stats for that time period to see what the host thought 
was going on?

-Ryan

> On Jan 22, 2016, at 4:45 PM, Erick Bergquist 
> > wrote:
>
> Normal CPU usage up to core, then a CPU spike right after core when
> things are starting back up. Different hosts, same storage.
>
> Only gap in trace file line entries is 23:54:59.957 to 23:55:18.402
> but maybe no activities?
>
> 11574290.000 |23:54:59.957 |SdlStat  |Period: 6s #Lines: 19 #Bytes:
> 3701 Total Number of Buffers: 1 Free LWM: 9989 Free LWM(total):
> 9192
> 11574291.000 |23:55:18.402 |AppInfo
> |SIPSocketProtocol(2,100,14,137)::handleReadComplete send SdlReadRsp:
> size 370
> 11574292.000 |23:55:18.402 |SdlStat  |Period: 19s #Lines: 1 #Bytes:
> 117 Total Number of Buffers: 1 Free LWM: 9998 Free LWM(total):
> 9192
> 11574293.000 |23:55:18.959 |AppInfo  |CMProcMon - ERROR   SDL
> Router Services Dead: timeBeforeSleep: 804509608, currentMontiorTime:
> 804530608, deltaTime: 21000, LoopCount= 19
>
> The deltaTime is 21000 which would be more then the 20 seconds for the
> router thread in the previously mentioned document covering 3.x/4.x.
>
> Do these services shutdown and restart themselves if over 16 seconds
> (SDL Timer) or 20 seconds (Router Thread) still in 10.x like that
> document states at those same thresholds?
>
> VMWare KB suggests the SCSI timeout should be increased to handle
> transient conditions. I would think these timers should be able to
> handle transient issues without failing the service?  Maybe the
> thresholds need to be increased to handle these periods.
>
> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US=displayKC=1009465
>
> I've only seen this with the ccm and ctimanager service. None of the
> other services.
>
> Thanks.
>
>
> On Fri, Jan 22, 2016 at 2:44 PM, Ryan Ratliff (rratliff)
> > wrote:
>> How about CPU usage leading up to the cores?
>> If you have CCM traces from before are there gaps in the timestamps between 
>> line numbers?
>>
>> If you are virtualized were those two nodes on the same host?  If so did 
>> other VMs on that host experience any odd issues at the time?
>> -Ryan
>>
>> On Jan 22, 2016, at 3:29 PM, Erick Bergquist 
>> > wrote:
>>
>> Ryan,
>>
>> I'm seeing a small spike in IOWait but not for that long, No gaps in
>> the Perfmon logs.  Only the ccm service core dumped on both the call
>> manager nodes on this cluster at the same time.
>>
>> Would the system shutdown the CCM and CTI Manager service itself if
>> these timers are to long, like that document from CCM 3.x/4.x days
>> eludes to with the 16 second SDL Timer Thread and 20 Second Router
>> Thread threshold?
>>
>>
>> The subscriber had a different backtrace, Intentional Abort..
>>
>> 
>> backtrace - CUCM
>> ===
>> #0  0xf776c430 in __kernel_vsyscall ()
>> #1  0xf697b871 in raise () from /lib/libc.so.6
>> #2  0xf697d14a in abort () from /lib/libc.so.6
>> #3  0x0837609e in IntentionalAbort () at ProcessCMProcMon.cpp:88
>> #4  CMProcMon::verifySdlRouterServices () at ProcessCMProcMon.cpp:748
>> #5  0x083762ca in CMProcMon::callManagerMonitorThread
>> (cmProcMon=0xefc73038) at ProcessCMProcMon.cpp:429
>> #6  0xf6c9c5a8 in ACE_OS_Thread_Adapter::invoke (this=0xe6a5d818) at
>> OS_Thread_Adapter.cpp:103
>> #7  0xf6c5c5f1 in ace_thread_adapter (args=0xe6a5d818) at
>> Base_Thread_Adapter.cpp:126
>> #8  0xf6932b39 in start_thread () from /lib/libpthread.so.0
>> #9  0xf6a33c1e in clone () from /lib/libc.so.6
>> 
>> info registers
>> 
>>
>>
>> Thanks,
>> Erick
>>
>>
>> On Fri, Jan 22, 2016 at 1:23 PM, Ryan Ratliff (rratliff)
>> > wrote:
>>> That backtrace is usually accompanied by CTIManager crashing due to 
>>> intentional abort.
>>>
 09465138.001 |23:55:15.448 |AppInfo  |CMProcMon::star_sdlVerification
 - Test Timer exceeded minimum timer latency threshold of 1000
 milliseconds, Actual latency: 54360 milliseconds
>>>
>>> That is quite spectacularly bad.  The SDLTimer thread is responsible for 
>>>

Re: [cisco-voip] Installation new phone firmware cop file installation

2016-01-29 Thread Brian Meade 
If you're just upgrading firmware, technically you only have to do it on
your TFTP server and manually update the device defaults.  If the publisher
also happens to be your TFTP server, the device defaults should get updated
automatically.

On Fri, Jan 29, 2016 at 9:55 AM, Reto Gassmann  wrote:

> Hello Group
>
> I have a UCM cluster 10.5 with 8 servers. TFTP service runs on the
> publisher.
> I now have a new 8831 to install and have to Upgrade the Firmware
> (cmterm-8831-sip.10.3.1SR2EU.k3.cop.sgn) in order to get the 8831 running.
>
> Is it ok to install the cop file on the TFTP Server and restart the TFTP
> after installtion or so I have to install the cop file on every server in
> the cluster?
>
> Tanks a lot and have a great weekend
> Regards Reto
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] FQDN removal

2016-01-29 Thread Ryan Huff 
David,


There will always be a hostname/domain name in the node. If you wish the node 
not to use DNS resolution, then delete the DNS entries from the node. Simply 
deleting the DNS entries will not cause a node reboot but it will restart the 
eth0 network interface of the node, I would do this in a maintenance window.


Prior to doing that and as a safety check, I would also run run sql select 
name,nodeid from ProcessNode from the node CLI FIRST and verify that all nodes 
are listed by IP address. The last item I would consider before deleting DNS is 
if the NTP server of the node is using a FQDN vs. IP Address; you'd need to 
change it first before deleting the DNS server if it is.


Once you've completed all your changes I would wait about 15 minutes (then 
again at 30 minutes) and issue, util dbreplication runtimestate from the 
publisher CLI and verify each node shows (2) Setup Completed. If not, you'll 
need to investigate why and possibly reset DB replication.


Again, if you are changing the hostname or domain name of the node; that is a 
horse of a different color 
(http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/8_6_1/ipchange/ipchg861.html).


Thanks,


= Ryan =



Email: ryanthomash...@outlook.com

Spark: ryanthomash...@outlook.com

Twitter: @ryanthomashuff

LinkedIn: ryanthomashuff

Web ryanthomashuff.com



From: David Jengan 
Sent: Thursday, January 28, 2016 9:56 PM
To: Ryan Huff
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] FQDN removal

Hi Ryan,

Thanks for the detailed explanation. Sorry I may not have been completely clear 
in the ask, what I'm after is to remove the DNS pointers from this Node, and 
additionally domain-name and Alias it was built with. So removing all DNS 
entries would take care of removing these as well and your suggestion for 
removing DNS without reboot still hold valid?

I'm cognizant of the points you raised regarding the server being listed by 
hostname instead of IP which isn't the case, and also the URLs are by IP 
instead of hostname.
So with this being clear, I can remove the DNS pri/sec pointers from CLI on the 
desired node, and not worry about restarting it or the cluster. From what 
you've pointed out, it appears that this will trigger db replication to break 
and then re-establish? Can you please confirm.

Regarding your query, I agree but at this time I want consistency, while at a 
later time implementing DNS would be planned for all nodes together.

In case it helps, listing the hosts on cli shows:
x.x.x.x sub1.domain.com sub1
x.x.x.x sub2
x.x.x.x sub3
x.x.x.x pub


On sub1 node: network details shows DNS entries and domain name.


Best,
David


On Thu, Jan 28, 2016 at 8:55 PM, Ryan Huff 
> wrote:

Hi David,


Removing the DNS server entries alone from the cluster nodes, would not require 
a restart. Removing/changing the hostname/domain name of the nodes would; this 
carries its own set of risks and considerations with SBD and db replication. If 
you are doing that, please consult; 
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/10_0_1/ipchange/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100_chapter_011.html
 first.


If you are just removing the DNS entries from the node then what you'll want to 
be uniquely aware of and cautious with is; any node listed in the CM 
ProccessNode table (Cisco Unified CM Administration -> System -> Server) with a 
hostname or FQDN (Vs. an IP Address). If you have any nodes in the CM Server 
section listed by either hostname or FQDN, you'll need to first change those to 
IP addresses BEFORE removing the DNS server entries in the CLI.


Additionally, you'll want to take stock of any 3rd party 
applications/integrations that you might have which requires the CUCM nodes to 
perform DNS queries/lookups. You will also likely want to verify that the the 
Phone URL Parameters under Enterprise Parameters are using IP addresses and not 
hostnames/FQDNs.


After you're done with your changes, you'll want to verify good DB Replication 
in the cluster (from the CLI of the publisher, issue utils dbreplication 
runtimestate and verify Setup Completed for each node).


This is more just a question out of my own curiosity, is there a specific 
reason you do not want to use DNS? In modern versions of CUCM such as 10, DNS 
is generally recommended. Additionally, several UC applications that could be 
used with CUCM are enhanced with DNS (IM, CUC) not to mention the UCCX would 
consider it a requirement. While you may not be using those products now, you 
never know what you may do in the future, always best to bake in the 
scalability early on, IMO.


= Ryan =



Email:

[cisco-voip] Upgrade issue with Dial Plan

2016-01-29 Thread Andy Carse 
Is there anyway to download a file other than the files used for tftp?
I'm doing a hardware replacement and upgrade to 10.5 effectively in a
secure environment with no outside connectivlty.
I have seen some posts where TAC had to root in and bin the IDP's.
I thought I'd try uninstalling them to see if that would fix the issue, but
they are on the production server not on the new hardware.
One of the files is no longer available for download but its installed on
the publisher.
Hence the question.

-- 
Rgds Andy
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] JAMS JConnector and UCCX 10.6 CAD

2016-01-29 Thread norm.nicholson 

We are looking to install this in a few months, has anyone installed this 
product and any information good or bad is appreciated.




Thanks





Norm Nicholson
Telecom Analyst
City of Kitchener
(519) 741-2200 x 7000


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Installation new phone firmware cop file installation

2016-01-29 Thread Ryan Huff 
While you only need to do this on the tftp server; I've always considered 
applying to every node. That way, if I make node/tftp changes in the future I 
don't even have to take this in to consideration.


Thanks,


Ryan


From: cisco-voip  on behalf of Reto 
Gassmann 
Sent: Friday, January 29, 2016 9:55 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Installation new phone firmware cop file installation

Hello Group

I have a UCM cluster 10.5 with 8 servers. TFTP service runs on the publisher.
I now have a new 8831 to install and have to Upgrade the Firmware 
(cmterm-8831-sip.10.3.1SR2EU.k3.cop.sgn) in order to get the 8831 running.

Is it ok to install the cop file on the TFTP Server and restart the TFTP after 
installtion or so I have to install the cop file on every server in the cluster?

Tanks a lot and have a great weekend
Regards Reto
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get used?

2016-01-29 Thread Brian Meade 
The application dial rules are downloaded via TFTP so they don't happen on
CUCM for the modt part.  That means any device could technically use them
if that BU allowed it.  That results in the full list not being able to
really be maintained by anyone.

Technically web dialer does it as part of the API if "Apply Application
Dial Rules on Dial" is set under WebDialer Web service parameter.

IPMA can use them too if you use the desktop interface.

Jabber definitely uses them.

SNR/MVA use them as part of those services.



On Fri, Jan 29, 2016 at 10:33 AM, Ed Leatherman 
wrote:

> The documents i've seen don't give a definitive list of what cases these
> get applied - it just says "applications such as".
>
> I want to add in some rules here for Jabber click to call stuff, for
> example changing 1+10 digits to sometime dialable in our current plan. I'm
> being a little cautious about unintended consequences.
>
> IPMA
> Cisco Web Dialer
> Jabber - Click to call, what other cases?
> Remote Destinations
>
> Is there a rule that gets checked to see when these rules get applied?
>
>
> --
> Ed Leatherman
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get used?

2016-01-29 Thread Ryan Huff 
on-prem WebEx Meeting server can use them too


From: cisco-voip  on behalf of Brian Meade 

Sent: Friday, January 29, 2016 10:57 AM
To: Ed Leatherman
Cc: Cisco VOIP
Subject: Re: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get 
used?

The application dial rules are downloaded via TFTP so they don't happen on CUCM 
for the modt part.  That means any device could technically use them if that BU 
allowed it.  That results in the full list not being able to really be 
maintained by anyone.

Technically web dialer does it as part of the API if "Apply Application Dial 
Rules on Dial" is set under WebDialer Web service parameter.

IPMA can use them too if you use the desktop interface.

Jabber definitely uses them.

SNR/MVA use them as part of those services.



On Fri, Jan 29, 2016 at 10:33 AM, Ed Leatherman 
> wrote:
The documents i've seen don't give a definitive list of what cases these get 
applied - it just says "applications such as".

I want to add in some rules here for Jabber click to call stuff, for example 
changing 1+10 digits to sometime dialable in our current plan. I'm being a 
little cautious about unintended consequences.

IPMA
Cisco Web Dialer
Jabber - Click to call, what other cases?
Remote Destinations

Is there a rule that gets checked to see when these rules get applied?


--
Ed Leatherman

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] CUCM 10.x Application Dial Rules - When do they get used?

2016-01-29 Thread Ed Leatherman 
The documents i've seen don't give a definitive list of what cases these
get applied - it just says "applications such as".

I want to add in some rules here for Jabber click to call stuff, for
example changing 1+10 digits to sometime dialable in our current plan. I'm
being a little cautious about unintended consequences.

IPMA
Cisco Web Dialer
Jabber - Click to call, what other cases?
Remote Destinations

Is there a rule that gets checked to see when these rules get applied?


-- 
Ed Leatherman
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get used?

2016-01-29 Thread Lelio Fulgenzi 

I think you hit the nail on the head... those are the ones I understand are 
affected. I'm not sure if remote destinations are affected though. And it's all 
of jabber, not just click to call. 

I have route patterns that know when a call is local or not, so i just add a 1 
regardless using the rules. 

Here are what mine look like... our AD directory stores our telephone numbers 
with a +1 areacode number with a space and the extension. It's not pretty. In 
order to get around that, and to dial someone's extension, I added those last 
three rules. The space is interpreted as a 9, so the match works. for now. 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
le...@uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

- Original Message -

From: "Ed Leatherman"  
To: "Cisco VOIP"  
Sent: Friday, January 29, 2016 10:33:35 AM 
Subject: [cisco-voip] CUCM 10.x Application Dial Rules - When do they get used? 

The documents i've seen don't give a definitive list of what cases these get 
applied - it just says "applications such as". 

I want to add in some rules here for Jabber click to call stuff, for example 
changing 1+10 digits to sometime dialable in our current plan. I'm being a 
little cautious about unintended consequences. 

IPMA 
Cisco Web Dialer 
Jabber - Click to call, what other cases? 
Remote Destinations 

Is there a rule that gets checked to see when these rules get applied? 


-- 
Ed Leatherman 

___ 
cisco-voip mailing list 
cisco-voip@puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] cisco cucm 11 unable to login cli

2016-01-29 Thread Ryan Huff 
Hey Claiton,


It might be possible to rebuild cliCommands.xml file (if the is the actual 
issue) via the rescue disk.  I'd open up a TAC case and have them take a look 
before rebuilding.


My guess though, is that the node is toast. Is this on the back of an upgrade 
or a new install?


Thanks,


= Ryan =



Email: ryanthomash...@outlook.com

Spark: ryanthomash...@outlook.com

Twitter: @ryanthomashuff

LinkedIn: ryanthomashuff

Web ryanthomashuff.com



From: cisco-voip  on behalf of Claiton 
Campos 
Sent: Friday, January 29, 2016 12:10 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] cisco cucm 11 unable to login cli

I'm in trouble when I try to log into the CUCM via CLI and the following 
message appears and then the connection is terminated
Command Line Interface is starting up, please wait ...
[Fatal Error] :-1:-1: Premature end of file.
cannot find any commands in /usr/local/platform/conf/cliCommands.xml Cannot 
start
Has anyone had a similar problem with that?
The CUCM this in version 11.0.1.

Regards.

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] cisco cucm 11 unable to login cli

2016-01-29 Thread Claiton Campos 
I'm in trouble when I try to log into the CUCM via CLI and the following
message appears and then the connection is terminated
*Command Line Interface is starting up, please wait ...*
*[Fatal Error] :-1:-1: Premature end of file.*
*cannot find any commands in /usr/local/platform/conf/cliCommands.xml
Cannot start*
Has anyone had a similar problem with that?
The CUCM this in version 11.0.1.

Regards.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] IPC not answering?

2016-01-29 Thread Scott Voll 
Has anyone recently seen issues with IP Communicator in window 7/8 not
allowing the use of the Answer button?  I'm wondering if it's a windows
update?  We have seen more the 5 or 10 users calling in, in the last two
days.

TIA

Scott
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM 10.5 core question - AlterateSyslogAlarm malloc backtrace

2016-01-29 Thread Erick Bergquist 
I'll unicast you the details Ryan.

On Fri, Jan 29, 2016 at 8:28 AM, Ryan Ratliff (rratliff)
 wrote:
> Until you identify what specifically spiked then you don’t know what to
> prevent.
>
> Do you have a TAC case open yet?
>
> -Ryan
>
> On Jan 28, 2016, at 7:42 PM, Erick Bergquist  wrote:
>
> Thanks Ryan. Nothing really standing out on the ESXi side.
>
> Any suggestions to prevent this in future?
>
> The VMware KB articles suggest a higher timeout on application side so
> transient issues and conditions on the VM side of things don't negatively
> impact the application.
>
> On Friday, January 22, 2016, Ryan Ratliff (rratliff) 
> wrote:
>>
>> That's your culprit right there. That 16 second sdlrouter thread timer is
>> one of the few things I bet hadn't changed since 4.x.
>>
>> Can you look at esxi stats for that time period to see what the host
>> thought was going on?
>>
>> -Ryan
>>
>> > On Jan 22, 2016, at 4:45 PM, Erick Bergquist  wrote:
>> >
>> > Normal CPU usage up to core, then a CPU spike right after core when
>> > things are starting back up. Different hosts, same storage.
>> >
>> > Only gap in trace file line entries is 23:54:59.957 to 23:55:18.402
>> > but maybe no activities?
>> >
>> > 11574290.000 |23:54:59.957 |SdlStat  |Period: 6s #Lines: 19 #Bytes:
>> > 3701 Total Number of Buffers: 1 Free LWM: 9989 Free LWM(total):
>> > 9192
>> > 11574291.000 |23:55:18.402 |AppInfo
>> > |SIPSocketProtocol(2,100,14,137)::handleReadComplete send SdlReadRsp:
>> > size 370
>> > 11574292.000 |23:55:18.402 |SdlStat  |Period: 19s #Lines: 1 #Bytes:
>> > 117 Total Number of Buffers: 1 Free LWM: 9998 Free LWM(total):
>> > 9192
>> > 11574293.000 |23:55:18.959 |AppInfo  |CMProcMon - ERROR   SDL
>> > Router Services Dead: timeBeforeSleep: 804509608, currentMontiorTime:
>> > 804530608, deltaTime: 21000, LoopCount= 19
>> >
>> > The deltaTime is 21000 which would be more then the 20 seconds for the
>> > router thread in the previously mentioned document covering 3.x/4.x.
>> >
>> > Do these services shutdown and restart themselves if over 16 seconds
>> > (SDL Timer) or 20 seconds (Router Thread) still in 10.x like that
>> > document states at those same thresholds?
>> >
>> > VMWare KB suggests the SCSI timeout should be increased to handle
>> > transient conditions. I would think these timers should be able to
>> > handle transient issues without failing the service?  Maybe the
>> > thresholds need to be increased to handle these periods.
>> >
>> >
>> > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US=displayKC=1009465
>> >
>> > I've only seen this with the ccm and ctimanager service. None of the
>> > other services.
>> >
>> > Thanks.
>> >
>> >
>> > On Fri, Jan 22, 2016 at 2:44 PM, Ryan Ratliff (rratliff)
>> >  wrote:
>> >> How about CPU usage leading up to the cores?
>> >> If you have CCM traces from before are there gaps in the timestamps
>> >> between line numbers?
>> >>
>> >> If you are virtualized were those two nodes on the same host?  If so
>> >> did other VMs on that host experience any odd issues at the time?
>> >> -Ryan
>> >>
>> >> On Jan 22, 2016, at 3:29 PM, Erick Bergquist 
>> >> wrote:
>> >>
>> >> Ryan,
>> >>
>> >> I'm seeing a small spike in IOWait but not for that long, No gaps in
>> >> the Perfmon logs.  Only the ccm service core dumped on both the call
>> >> manager nodes on this cluster at the same time.
>> >>
>> >> Would the system shutdown the CCM and CTI Manager service itself if
>> >> these timers are to long, like that document from CCM 3.x/4.x days
>> >> eludes to with the 16 second SDL Timer Thread and 20 Second Router
>> >> Thread threshold?
>> >>
>> >>
>> >> The subscriber had a different backtrace, Intentional Abort..
>> >>
>> >> 
>> >> backtrace - CUCM
>> >> ===
>> >> #0  0xf776c430 in __kernel_vsyscall ()
>> >> #1  0xf697b871 in raise () from /lib/libc.so.6
>> >> #2  0xf697d14a in abort () from /lib/libc.so.6
>> >> #3  0x0837609e in IntentionalAbort () at ProcessCMProcMon.cpp:88
>> >> #4  CMProcMon::verifySdlRouterServices () at ProcessCMProcMon.cpp:748
>> >> #5  0x083762ca in CMProcMon::callManagerMonitorThread
>> >> (cmProcMon=0xefc73038) at ProcessCMProcMon.cpp:429
>> >> #6  0xf6c9c5a8 in ACE_OS_Thread_Adapter::invoke (this=0xe6a5d818) at
>> >> OS_Thread_Adapter.cpp:103
>> >> #7  0xf6c5c5f1 in ace_thread_adapter (args=0xe6a5d818) at
>> >> Base_Thread_Adapter.cpp:126
>> >> #8  0xf6932b39 in start_thread () from /lib/libpthread.so.0
>> >> #9  0xf6a33c1e in clone () from /lib/libc.so.6
>> >> 
>> >> info registers
>> >> 
>> >>
>> >>
>> >> Thanks,
>> >> Erick
>> >>
>> >>
>> >> On Fri, Jan 22, 2016 at 1:23 PM, Ryan Ratliff (rratliff)
>> >>  wrote:
>> >>> That backtrace is usually

Re: [cisco-voip] cisco cucm 11 unable to login cli

2016-01-29 Thread Ryan Ratliff (rratliff) 
Your best bet is for TAC to replace that file with a copy from a sub. You 
probably took a power hit and had to use the recovery disk to get it booted.

You will hear from TAC that you need to rebuild simply because UCM doesn’t have 
any way to know what files were truncated when fsck did its thing.

-Ryan

On Jan 29, 2016, at 12:17 PM, Ryan Huff 
> wrote:

Hey Claiton,

It might be possible to rebuild cliCommands.xml file (if the is the actual 
issue) via the rescue disk.  I'd open up a TAC case and have them take a look 
before rebuilding.

My guess though, is that the node is toast. Is this on the back of an upgrade 
or a new install?

Thanks,

= Ryan =


Email: ryanthomash...@outlook.com
Spark: ryanthomash...@outlook.com
Twitter: @ryanthomashuff
LinkedIn: ryanthomashuff
Web ryanthomashuff.com



From: cisco-voip 
> 
on behalf of Claiton Campos 
>
Sent: Friday, January 29, 2016 12:10 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] cisco cucm 11 unable to login cli

I'm in trouble when I try to log into the CUCM via CLI and the following 
message appears and then the connection is terminated
Command Line Interface is starting up, please wait ...
[Fatal Error] :-1:-1: Premature end of file.
cannot find any commands in /usr/local/platform/conf/cliCommands.xml Cannot 
start
Has anyone had a similar problem with that?
The CUCM this in version 11.0.1.

Regards.

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip