Display Filter Reference: SAToP (no RTP support)
Protocol field name: pwsatopcw
Versions: 1.2.0 to 3.4.5
Back to Display Filter Reference
| Field name | Description | Type | Versions |
|---|---|---|---|
| Control Word | Label | 1.2.0 to 1.2.18 | |
| pwsatop.cw | Control Word | Label | 1.4.0 to 3.4.5 |
| pwsatop.cw.bits03 | Bits 0 to 3 | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.bits03.not_zero | Bits 0..3 of Control Word must be 0 | Label | 1.12.0 to 3.4.5 |
| pwsatop.cw.frag | Fragmentation | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.frag.not_allowed | Fragmentation of payload is not allowed for SAToP | Label | 1.12.0 to 3.4.5 |
| pwsatop.cw.lbit | L bit: TDM payload state | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.length | Length | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.rbit | R bit: Local CE-bound IWF | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.rsv | Reserved | Unsigned integer, 1 byte | 1.2.0 to 3.4.5 |
| pwsatop.cw.rsv.not_zero | RSV bits of Control Word must be 0 | Label | 1.12.0 to 3.4.5 |
| pwsatop.cw.seqno | Sequence number | Unsigned integer, 2 bytes | 1.2.0 to 3.4.5 |
| pwsatop.packet_size_too_small | PW packet size (%d) is too small to carry sensible information | Label | 1.12.0 to 3.4.5 |
| pwsatop.padding | Padding | Sequence of bytes | 1.2.0 to 1.2.18 |
| pwsatop.payload | TDM payload | Sequence of bytes | 1.2.0 to 3.4.5 |
| pwsatop.payload.len | TDM payload length | Signed integer, 4 bytes | 1.4.0 to 3.4.5 |
| pwsatop.payload.size_invalid | Bad Length: too small | Label | 1.12.0 to 3.4.5 |
| pwsatop.payload.undecoded | SAToP payload: omitted to conserve bandwidth | Label | 1.12.0 to 3.4.5 |
Go Beyond with Riverbed Technology
I have a lot of traffic...
ANSWER: SteelCentral™ AppResponse 11
- • Full stack analysis – from packets to pages
- • Rich performance metrics & pre-defined insights for fast problem identification/resolution
- • Modular, flexible solution for deeply-analyzing network & application performance