Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,Cisco 3548 configured for ptp not working properly , The configuration is made as it is said in the document https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3548/sw/system_mgmt/602/b_N3548_System_Management_Config_602A11/b_N3548_...
Hello,We have the following setup, when we start dumpcap logs on Host1 interfaces everything seems normal. But when we move logging to SPAN ports on 1/1 and 1/3 some packets gets logged in wrong order. For example TCP acks logged before requests. Log...
Hello ,We have the following network setup as a minimal multicast testing environment. Please don't bother about 194.x.x.x ip addresses used in the intranet. Udp sender host can send the udp multicast to the interface ethernet 1/36 and Udp receiver h...
We have Cisco nx-os 3548 , the software version is nxos.9.2.2.bin. The switch periodically transmit some unknown 60 byte packets to the Unix machines connected to VLAN 1 access ports. On the unix server when we check the interface with ifconfig we se...
I have to share some striking information this issue;There is a big misperception about the source of the PTP server . As i saw the source IP address of the PTP server in the dumpcap log, i thought that the announce / sync and follow up messages are ...
Hello,At the end we understand the problem. Its not related to Cisco switch . Its about packet timestamping of the server host. Dumpcap packet capture is using the server software timing for timestamping of the packets and its not stable. The result ...
Hello,İts normal SPAN . We tried WARP SPAN , because of lack of resource we couldnt make it the WARP SPAN with another SPAN together. We could make the WARP SPAN without any other SPAN session.I dont know may be after increasing buffer span-threshold...
Hello,Here are the zipped pcap files . Wireshark shows black labeled lines as error , but actually these are not errors , i think the only problem is that the order of logged packets are incorrect.
