Hello,
Here is the Cisco Proximity Troubleshooting Guide written by Magnus (from the BU):
https://community.cisco.com/t5/mobile-applications-documents/troubleshooting-guide-cisco-proximity/ta-p/3148841#toc-hId--84856520
Within that he also links to a guide that explains how the Proximity Application communicates with the video system, and the network requirements for the feature to work.
https://projectworkplace.cisco.com/assets/pdf/proximity-networking.pdf
The clients will communicate directly with the codec over port 443 including the content.
Please let me know if you have any further comments, questions, issues, or concerns.
Kind regards,
... View more
If you want to do bi-directional captures using pktcap-uw then you can do the following command:
pktcap-uw --switchport 33554495 --dir 0 -o /tmp/33554495_in.pcap & \ pktcap-uw --switchport 33554495 --dir 1 -o /tmp/33554495_out.pcap &
You can also do this in one line if you remove the "\" and return:
pktcap-uw --vmk vmk0 --dir 0 -o /tmp/vmk0_in.pcap & pktcap-uw --vmk vmk0 --dir 1 -o /tmp/vmk0_out.pcap &
Important note: Because "&" cause the process to be run in the background you'll need to
manually kill the process after starting it. The easiest way to do this is to kill all instances of pktcap-uw:
kill $(lsof |grep pktcap-uw |awk '{print $1}'| sort -u)
You can verify all pcaps are ended by running the following command:
lsof |grep pktcap-uw |awk '{print $1}'| sort -u
References: http://networkgeekstuff.com/networking/minipost-capturing-bidirectional-traffic-of-virtual-machine-vms-on-vmware-esx-6-x-host/ https://kb.vmware.com/s/article/2051814
... View more
Hello,
I understand your frustrated with your Conductor that is facing this issue. I see this comment was made Aug 28, 2017, but the fix for this defect was in XC4.3.1 which was released Mar 29, 2017. Please make sure you update and if you continue having any issues open a TAC case with us and we will engage the BU with figuring why you're still hitting this issue on a release that has had the commit to fix this issue.
Kind regards,
Ben Andrews
TAC CSE - TelePresence
... View more
Hello Ajith and everyone else,
What negotiation mode are the interfaces with "SFP validation failed"? I ran into this issue today and I was able to resolve this issue by making sure "speed 1000" AND "negotiation auto" are both enabled on the device. You may be getting the "link not connected" because you'll probably need negotiation auto on the both sides of the link since it's enabled on the Nexus.
My best guess as to why both are necessary is that it performs more like Nexus's speed-group command than like the traditional IOS speed command. Meaning that is simply tells the interface that it wants to operate in 1G mode instead 10G mode. I should note that I am not on any nexus team that is just my guess from my personal experience.
Kind regards,
Ben
... View more
Important issue that we had was that we had to add TFTP to allowed traffic for the management-plane for the install to complete control-plane management-plane inband interface all allow TFTP !
... View more
