I have created a manual trace in the console and when I open this trace I notice that there is a difference in what DCRUM found and what Wireshark finds. e.q. a port number found by the console can not be found in Wireshark. What am I missing?
KR Henk Stobbe
What protocol is it?
Possibly a PROXY of some kind?
Wireshark is packet focused and will expose per packet information while DC RUM is more geared towards messages even though you can force it to relinquish TCP/IP data
Bigger story, (I have created ticket). The issue is that AMD splts traffic based on Physical ethernet address, so A->B B->A on level 3 looks (in my AMD) as two seprate streams. Wireshark does not to make that separation and has no issue's, In the sam ticketI asked to adjust default min packet size on AMD,
Ticket 5744, just shipped to development,
Sorry, just the one AMD. I copied the cap file from AMD to pc, and it shows up very nice in Wireshark. FYI it is FabricPath traffic, so to get IP you have to chop off a few bytes to get the ethernet packet. Maybe this conversion is not perfect in AMD,