Nagetive frame time that is collected from PAA and WireShark
Question of reading packages in Ethereal/Wireshak, that were collected from PAA:
When a read or write command comes in --- the first SCSI request package and the last SCSI complete package has high possibility not in the same capture file, especially when the capture file is not big.
Then I will see: [time from Exchange First: -5.763400000 seconds]
Does that mean total complete time is 5.7634 seconds???
I went back to 5-6 seconds from that frame, but could not find the first frame. So I was wondering maybe -5.7634 seconds does not really mean it. Do I need to do some kind of math to find the first request frame in previous files???
Re: Nagetive frame time that is collected from PAA and WireShark
A negative time here could also mean two different fiber channel exchanges (SCSI command sequences) used the same originator exchange ID (OX_ID) and WireShark is getting confused. It's not against the standards for a device to use the same OX_ID, so this is not an issue with the PAA or the integrity of the packets. One way to tell Exchanges apart is to look at the receiver exchange ID (RX_ID). It's likely the RX_ID for a frame from the receive will be different for two different exchanges where the OX_ID is the same.
Let me start by telling you that there is already a very nice document in the Cisco Community Forums which describes the procedure to upgrade the APIC CIMC. In case you came across this document before looking into the mentioned one, here is...
2020年7月14日 (初版)主な問題F3 ラインカードを利用した場合、Shared Policers の設定により通信レートを期待値に制御できません。CIR 値を 1048600 に設定し、以下一例となります。128 byte のペイロードのパケットが通過している場合の、egress port 側の sh int の出力：N7K(config)# sh int e1/1 | i i rate
Rate mode is dedicated
30 seconds input ...