ACE A2.2.4 issue

Answered Question
Jul 30th, 2010

Hi,

I was facing a situation that the traffics were not forwarded from ACE to real servers.

All VIPs and Rservers were not PING-able from the ACE.

But, it was PIng-able from the L2 switch direct connected server.

We did failover from an active ACE to a standby ACE after getting 'show tech' off from the ACE .

After the failover,all the services got well.

We find something weird on ACE show tech.

Is there anyone know about the following error information.

`show np 1 me-stats -sreceive`
Receive Statistics: (Current)
------------------
Idle:                                    1031619208        100888
Frames Received:                          928414914            37
Control Frames Received:                   15546857             2
Forward Buffered:                         928414914            37

`show np 2 me-stats -sreceive`
Receive Statistics: (Current)
------------------
Idle:                                    1052721624        100915
Frames Received:                          717293743            15
Control Frames Received:                   11970690             0
Forward Buffered:                         717293281            15
Error(rbuf skip):                             25808             8


`show np 1 me-stats -snormalization`
Normalization Statistics: (Current)
------------------------
[Drops] TCP syn options on non-syn:            4300             0
(Context 1 Statistics)
(No relevant stats)

`show np 1 me-stats -snorm`
Normalization Statistics: (Current)
------------------------
[Drops] TCP syn options on non-syn:            4300             0
(Context 1 Statistics)
(No relevant stats)

`show np 2 me-stats -snormalization`
Normalization Statistics: (Current)
------------------------
[Drops] TCP invalid conn miss flags:              6             0
[Drops] TCP syn options on non-syn:            4933             0
(Context 1 Statistics)
[Drops] L4 invalid header len:                13097             1

`show np 2 me-stats -snorm`
Normalization Statistics: (Current)
------------------------
[Drops] TCP invalid conn miss flags:              6             0
[Drops] TCP syn options on non-syn:            4933             0
(Context 1 Statistics)
[Drops] L4 invalid header len:                13101             2

Correct Answer by Gilles Dufour about 6 years 6 months ago

The rbuf skip means the buffer got corrupted and the information it contains can't be trusted.

This check was recently added A2(2.3) with ddts CSCta54223:  Add additional checking for CDE hardware issues

So, it sounds like a hardware issue with that blade.

The other counter is related to the length of the ip packet.

Normally the ip header length is 20 bytes...if you add options it can grow but must be padded so that the length is on an expected boundary.

This counter increment when a packet does not follow that rule.

Since the CDE seems to be corrupted, it could mess up the packets.

You should RMA that board.

Gilles.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Gilles Dufour Fri, 07/30/2010 - 05:18

The rbuf skip means the buffer got corrupted and the information it contains can't be trusted.

This check was recently added A2(2.3) with ddts CSCta54223:  Add additional checking for CDE hardware issues

So, it sounds like a hardware issue with that blade.

The other counter is related to the length of the ip packet.

Normally the ip header length is 20 bytes...if you add options it can grow but must be padded so that the length is on an expected boundary.

This counter increment when a packet does not follow that rule.

Since the CDE seems to be corrupted, it could mess up the packets.

You should RMA that board.

Gilles.

Actions

This Discussion