<div dir="ltr">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.<div><br></div><div>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.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 21, 2018 at 12:17 PM Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">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.<div><br></div><div>This is similar to the whole UAS/UAC discussion with SIP and 5060.</div><div><br></div><div>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</div><div><br></div><div><div><font face="monospace, monospace">PeerAddress=+16125551212</font></div><div><font face="monospace, monospace">PeerId=2100</font></div><div><span style="background-color:rgb(255,242,204)"><font face="monospace, monospace">RemoteSignallingIPAddress=10.10.10.10</font></span></div><div><span style="background-color:rgb(255,242,204)"><font face="monospace, monospace">RemoteSignallingPort=50124</font></span></div><div><font face="monospace, monospace">RemoteMediaIPAddress=10.20.20.20</font></div><div><font face="monospace, monospace">RemoteMediaPort=28326</font></div><div><font face="monospace, monospace">tx_DtmfRelay=rtp-nte</font></div><div><font face="monospace, monospace">VAD = disabled</font></div><div><font face="monospace, monospace">CoderTypeRate=g711ulaw</font></div><div><br></div><div>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</div></div><div><br></div><div><div><font face="monospace, monospace">PeerAddress=+16215551212</font></div><div><font face="monospace, monospace">PeerId=2200</font></div><div><span style="background-color:rgb(255,242,204)"><font face="monospace, monospace">RemoteSignallingIPAddress=10.10.10.10</font></span></div><div><span style="background-color:rgb(255,242,204)"><font face="monospace, monospace">RemoteSignallingPort=5060</font></span></div><div><font face="monospace, monospace">RemoteMediaIPAddress=10.20.20.20</font></div><div><font face="monospace, monospace">RemoteMediaPort=28524</font></div><div><font face="monospace, monospace">tx_DtmfRelay=rtp-nte</font></div><div><font face="monospace, monospace">VAD = disabled</font></div><div><font face="monospace, monospace">CoderTypeRate=g711ulaw</font></div></div><div><font face="monospace, monospace"><br></font></div><div><i>PS I get that output from the following command on CUBE: show call active voice | in PeerAddr|PeerId|RemoteS|RemoteM|Dtmf|Coder|VAD</i><br></div><div><br></div><div>Put that in an alias command, and you're a few short keystrokes away from some sexy data.</div><div><br></div><div>Now, back to the TCP re-transmissions, this is most likely a lower layer issue, and not a problem with PLM/CUCM.</div><div><br></div><div>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:</div><div><br></div><div><a href="https://www.netcraftsmen.com/application-analysis-using-tcp-retransmissions-part-1/" target="_blank">https://www.netcraftsmen.com/application-analysis-using-tcp-retransmissions-part-1/</a><br></div><div><br></div><div>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.</div><div><br></div><div>As for logs, I'd imagine it wont show you anything more valuable than your packet capture; that's probably pretty telling.</div><div><br></div><div>Good luck. I'm curious to see how this turns out.</div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 21, 2018 at 10:08 AM Brian Meade <<a href="mailto:bmeade90@vt.edu" target="_blank">bmeade90@vt.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Are you sure the destination port is 56648 and it's not the source port in that handshake?</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 21, 2018 at 10:51 AM Jason Aarons (Americas) <<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<br>
<br>
<div class="gmail-m_-5129224552412524315gmail-m_-5046867934431012211gmail-m_-5233718741927375366WordSection1">
<p class="MsoNormal">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.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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.”<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">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?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><img width="1449" height="720" style="width: 15.0937in; height: 7.5in;" id="gmail-m_-5129224552412524315gmail-m_-5046867934431012211gmail-m_-5233718741927375366Picture_x0020_1" src="cid:167d1814bba4cff311"><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Jason Aarons, CCIEx2 No. 38564<u></u><u></u></p>
<p class="MsoNormal">Advanced Technology Consultant<u></u><u></u></p>
<p class="MsoNormal">Dimension Data<u></u><u></u></p>
<p class="MsoNormal">904-338-3245<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<br>
<br>
<font>
This email and all contents are subject to the following disclaimer:<br>
<a href="http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx" target="_blank">"http://www.dimensiondata.com/emaildisclaimer"</a>
</font>
<font color="white"></font>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div>
</blockquote></div>