Specifies whether the Compression Control Protocol
(RFC 1962) is enabled. Note that enabling CCP does not
automatically cause the CVX to compress frames it
transmits; that is controlled by the CompressFrames
entry. This configuration was split into two options
because many common client implementations of CCP can
take over 30 seconds to connect when CCP is disabled.
To get these clients to connect quickly, set
CCPEnabled to 'true'. To prevent the CVX from actually
compressing the data, set CompressFrames to 'false.'
Parsed from file aptis_config.mib.txt
Company: None
Module: APTIS-CONFIG-MIB
Specifies whether the Compression Control Protocol
(RFC 1962) is enabled. Note that enabling CCP does not
automatically cause the CVX to compress frames it
transmits; that is controlled by the CompressFrames
entry. This configuration was split into two options
because many common client implementations of CCP can
take over 30 seconds to connect when CCP is disabled.
To get these clients to connect quickly, set
CCPEnabled to 'true'. To prevent the CVX from actually
compressing the data, set CompressFrames to 'false.'
Parsed from file APTIS-CONFIG-MIB.mib
Module: APTIS-CONFIG-MIB
Vendor: Aptis Communications, Inc.
Module: APTIS-CONFIG-MIB
[Automatically extracted from oidview.com]
pppConfigCCPEnabled OBJECT-TYPE SYNTAX Boolean ACCESS read-write STATUS mandatory DESCRIPTION "Specifies whether the Compression Control Protocol (RFC 1962) is enabled. Note that enabling CCP does not automatically cause the CVX to compress frames it transmits; that is controlled by the CompressFrames entry. This configuration was split into two options because many common client implementations of CCP can take over 30 seconds to connect when CCP is disabled. To get these clients to connect quickly, set CCPEnabled to 'true'. To prevent the CVX from actually compressing the data, set CompressFrames to 'false.'" ::= { pppConfigEntry 1011 }
pppConfigCCPEnabled OBJECT-TYPE SYNTAX Boolean MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies whether the Compression Control Protocol (RFC 1962) is enabled. Note that enabling CCP does not automatically cause the CVX to compress frames it transmits; that is controlled by the CompressFrames entry. This configuration was split into two options because many common client implementations of CCP can take over 30 seconds to connect when CCP is disabled. To get these clients to connect quickly, set CCPEnabled to 'true'. To prevent the CVX from actually compressing the data, set CompressFrames to 'false.'" DEFVAL { true } ::= { pppConfigEntry 1011 }
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.2637.2.1.1313.1.1012 | pppConfigCompressFrames | 0 | 0 | Compress transmitted frames when CCP has been negotiated. Set this to 'false' to prevent the CVX from compressing frames, even wh… |
| 1.3.6.1.4.1.2637.2.1.1313.1.1013 | pppConfigStac3Enabled | 0 | 0 | Stac check mode 3 (Sequence Number) enabled (RFC 1962) |
| 1.3.6.1.4.1.2637.2.1.1313.1.1014 | pppConfigStac4Enabled | 0 | 0 | Stac check mode 4 (Extended Mode) enabled (RFC 1962) |
| 1.3.6.1.4.1.2637.2.1.1313.1.1015 | pppConfigMPPCEnabled | 0 | 0 | Microsoft Point-to-Point Compression enabled (RFC 2118) |
| 1.3.6.1.4.1.2637.2.1.1313.1.1016 | pppConfigStacPerformance | 0 | 0 | Stac compression performance parameter |
| 1.3.6.1.4.1.2637.2.1.1313.1.1017 | pppConfigStacMode | 0 | 0 | Stac compression performance mode parameter |
| ... | ||||