10-12-2011 10:30 PM - edited 03-07-2019 02:46 AM
Does anyone have documentation on all the fields in an elam capture?
I am troubleshooting a very wierd vPC problem and I am getting drop_oth. I notice my di field has 11a0 or 11a1. On a successful packet my di field is a38 or a39.
The di and associated values is what I'm looking for specifically but if someone has a decoder tool or documentation that would be greatly appreciated!
Solved! Go to Solution.
10-12-2011 10:49 PM
Hi Brian,
DI seems to be Destination Index for a packet. You can decode those hex values to particular port/processor with
sh system internal pixm info ltl INDEX
e.g.
sh system internal pixm info ltl 0x11a0
Nik,
10-12-2011 11:31 PM
10-12-2011 10:49 PM
Hi Brian,
DI seems to be Destination Index for a packet. You can decode those hex values to particular port/processor with
sh system internal pixm info ltl INDEX
e.g.
sh system internal pixm info ltl 0x11a0
Nik,
10-12-2011 11:03 PM
Thank you for the quick reply!! That certainly helps but unfortunately deepens the mystery, all of my indices are "Not Configured" with the exception of 0xa38.
0x11a0 is not configured
0x11a1 is not configured
0x0a39 is not configured
PC_TYPE PORT LTL RES_ID LTL_FLAG CB_FLAG MEMB_CNT
------------------------------------------------------------------------------
MCT Po501 0x0a38 0x160001f4 0x00000000 0x00000002 2 PC_TYPE PORT LTL RES_ID LTL_FLAG CB_FLAG MEMB_CNT
------------------------------------------------------------------------------
MCT Po501 0x0a38 0x160001f4 0x00000000 0x00000002 2
10-12-2011 11:31 PM
Right - can be SW defect.
Nik
10-12-2011 11:38 PM
I think you're right. I've got an SR open on it right now and the BU is setting up a lab to try and duplicate because this is causing packet loss in our environment.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide