[cisco-voip] CallManager and PLM 11.5.1 ports (firewall issues)

Wed Dec 26 12:22:23 EST 2018

Can you take packet captures from both sides (affected cluster and PLM) at the same time?
That would make clear if packets are modified along the way.

I would check the firewall first, if it is dropping packets failing inspection, for example. Had a similar problem a couple of Weeks ago. A PaloAlto firewall dropping UDP traffic.

Regards,

Ariel.

De: cisco-voip <cisco-voip-bounces at puck.nether.net> En nombre de Ryan Ratliff (rratliff) via cisco-voip
Enviado el: viernes, 21 de diciembre de 2018 16:00
Para: Brian Meade <bmeade90 at vt.edu>
CC: cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Asunto: Re: [cisco-voip] CallManager and PLM 11.5.1 ports (firewall issues)

I’d second the MTU problem, especially if frame 13 in the capture (the 1514 one) has DF set.

Assuming this was taken at the remote CUCM, the retransmitted packets at the bottom are all 1514 bytes, so it’s very likely whatever frame 13 was never received by PLM.

 - Ryan Ratliff

On Dec 21, 2018, at 1:51 PM, Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>> wrote:

One thing to start looking at would be why the TLS Client Hello from PLM is showing as malformed.  There's some large packets in there as well (1482 and 1514).  I'd bet you've got an MTU issue somewhere on the path.

Was the capture taken from the CUCM side?  I would bet it does since it's sending 1514 byte packets and those are the ones you're not getting Acks from PLM on.

On Fri, Dec 21, 2018 at 12:17 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
To echo what Brian is saying with his question: 443 is a server listening port (HTTPS), and therefore, the port on PLM talking to it, is an ephemeral client port, or random port, and wouldn't be documented anywhere.

This is similar to the whole UAS/UAC discussion with SIP and 5060.

Take this Outbound call for example, where my CUBE (UAS) is talking SIP with CUCM (UAC) (10.10.10.10) on CUCM's port 50124

PeerAddress=+16125551212
PeerId=2100
RemoteSignallingIPAddress=10.10.10.10
RemoteSignallingPort=50124
RemoteMediaIPAddress=10.20.20.20
RemoteMediaPort=28326
tx_DtmfRelay=rtp-nte
VAD = disabled
CoderTypeRate=g711ulaw

And then this Inbound call example, where my CUBE (UAC) is talking SIP with CUCM (UAS) (10.10.10.10) on CUCM's port 5060

PeerAddress=+16215551212
PeerId=2200
RemoteSignallingIPAddress=10.10.10.10
RemoteSignallingPort=5060
RemoteMediaIPAddress=10.20.20.20
RemoteMediaPort=28524
tx_DtmfRelay=rtp-nte
VAD = disabled
CoderTypeRate=g711ulaw

PS I get that output from the following command on CUBE: show call active voice | in PeerAddr|PeerId|RemoteS|RemoteM|Dtmf|Coder|VAD

Put that in an alias command, and you're a few short keystrokes away from some sexy data.

Now, back to the TCP re-transmissions, this is most likely a lower layer issue, and not a problem with PLM/CUCM.

A quick google search resulted in this article, which I found well written, but does go deep, with links to other articles which take you even deeper:

https://www.netcraftsmen.com/application-analysis-using-tcp-retransmissions-part-1/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.netcraftsmen.com%2Fapplication-analysis-using-tcp-retransmissions-part-1%2F&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cdded756273f244d66fbb08d66776cc2d%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636810157277759903&sdata=Gt%2FS3mwNmmn5wmVwXpnZOBW6OHAGwmlOymnBCTBlTyA%3D&reserved=0>

Since you have the same PLM talking to multiple CUCM clusters, and only a problem with one cluster (or so it sounded like), I'd wager this problem is not with the PLM side, but is probably on the network path where it begins to be unique for this CUCM cluster in question, to include the CUCM cluster (or more specifically, the Publisher) itself.

As for logs, I'd imagine it wont show you anything more valuable than your packet capture; that's probably pretty telling.

Good luck.  I'm curious to see how this turns out.

On Fri, Dec 21, 2018 at 10:08 AM Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>> wrote:
Are you sure the destination port is 56648 and it's not the source port in that handshake?

On Fri, Dec 21, 2018 at 10:51 AM Jason Aarons (Americas) <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:

Have a centralized Prime License Manager (PLM) for several clusters.   One cluster the Product Instance shows “Unknown error”.  We have firewalls between PLM and clusters.

I hit Test Connection in PLM and see traffic from source PLM coming in to remote cluster on TCP/443 and then I see traffic back source TCP/443 to destination TCP/56648 and then lots of TCP retransmissions.  The GUI in PLM says “Test Connection Failed.The cause of the error is unknown. Check the Cisco Prime License Manager log for details.”

I can’t find in the Port Usage guide where TCP/56648 is documented?  What log file do I look at via RTMT on PLM?

<image001.png>

Jason Aarons, CCIEx2 No. 38564
Advanced Technology Consultant
Dimension Data
904-338-3245

This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer"<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dimensiondata.com%2FGlobal%2FPolicies%2FPages%2FEmail-Disclaimer.aspx&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cdded756273f244d66fbb08d66776cc2d%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636810157277759903&sdata=j80J8GkFmUwt0D16%2BnZkR2AjjY9WnFUrdJNrpYlIQ2Y%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cdded756273f244d66fbb08d66776cc2d%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636810157277759903&sdata=mhruNoTPuFpzegHNHbqbxG9FxGKZSfwvjNtY5l4%2BUGo%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cdded756273f244d66fbb08d66776cc2d%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636810157277759903&sdata=mhruNoTPuFpzegHNHbqbxG9FxGKZSfwvjNtY5l4%2BUGo%3D&reserved=0>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20181226/23459663/attachment.html>