The Point-to-Point Protocol (PPP), specified in RFC 1661, provides a standard method for transporting multi-protocol datagrams over point-to-point links.
PPP is designed for simple links that transport packets between two peers. These links provide full-duplex simultaneous bi-directional operation, and are assumed to deliver packets in order. It is intended that PPP provide a common solution for easy connection of a wide variety of hosts, bridges and routers.
PPP is not a single protocol, but consists of several partly dependent protocols, of which LCP, IPCP and authentication protocols are of the most importance.
The Link Control Protocol (LCP) is the base of PPP, negotiating basic link parameters such as timeouts, retries and authentication. It is build as the finite state automaton, having 10 states and driven by such events as link up/down, incoming packets and timeouts.
The IP Control Protocol (IPCP) is an example of a Network Control Protocol (NCP), and is responsible for transporting IP traffic over a PPP link. Like LCP, it has the form of a finite state automaton, though a bit simplified. It negotiates IP addresses, DNS addresses and IP compression.
This PPP implementation makes use of one of the following protocols: PAP (Password Authentication Protocol), CHAP (Challenge-Handshake Authentication Protocol) and MS-CHAP (Microsoft CHAP) versions 1 and 2.
PAP is a simple plain-text protocol, requiring user to send username and password and server to respond with appropriate response. Due to its simplicity it is the most widespread protocol, but it is not very secure because of password transmitted in plain text form.
CHAP is more advanced protocol. Here client does not send password in plain form, but rather sends a value, derived from username, password and some data received from server. The process of calculating this value ("hashing") is such that it does not allow reconstructing password from it, thus making interception inefficient. However, it still requires both server and user to store password in plain text form, thus being vulnerable to theft attacks.
Microsoft has developed its own version of CHAP, solving this problem. There are two versions of MS-CHAP: version 1 and version 2. the latter being the most secure. Both are supported by current version.
For more information, consult the following documents:
The PPP port is provided with the parameters described in this section.
The layout of the PPP port parameters changes considerably according to the used lower layer port type.
PPP over SYNC.
[13:51:12] ABILIS_CPX: D P PO:541 . PO:541 ------------------------------------------------------------------------ PPP LOG:DS LOWPO:1 - Tcp-MSS/Lcp/IpCp ----------------------------------------------------- TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414 maxmru:1500 DNS:NO - Authentication ------------------------------------------------------- USERNAME:myuserid LOCAL:CHAP PASSWORD:******************************** SERVNAME: REMOTE:CHAP REPEAT:0
PPP over FRAME-RELAY.
[13:51:12] ABILIS_CPX: D P PO:541 . PO:541 ------------------------------------------------------------------------ PPP LOG:DS LOWPO:101 DLCI:16 CIR:19200 BC:19200 BE:0 SC:4 CC:YES - Tcp-MSS/Lcp/IpCp ----------------------------------------------------- TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414 maxmru:1500 DNS:NO - Authentication ------------------------------------------------------- USERNAME:myuserid LOCAL:CHAP PASSWORD:******************************** SERVNAME: REMOTE:CHAP REPEAT:0
PPP over ISDN.
[13:51:12] ABILIS_CPX: D P PO:541 . PO:541 ------------------------------------------------------------------------ PPP LOG:DS LOWPO:17 BCHAN:B2 - Tcp-MSS/Lcp/IpCp ----------------------------------------------------- TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414 maxmru:1500 DNS:NO - Authentication ------------------------------------------------------- USERNAME:myuserid LOCAL:CHAP PASSWORD:******************************** SERVNAME: REMOTE:CHAP REPEAT:0
PPP over EIR (S-LINK).
[13:51:12] ABILIS_CPX: D P PO:541 . PO:541 ------------------------------------------------------------------------ PPP LOG:DS LOWPO:200 VSPID:NONE DT-IN:300 DT-OUT:300 - Dial-in -------------------------------------------------------------- DIAL-IN:YES CGI:* SGI:* CDI:* SDI:* - Dial-out ------------------------------------------------------------- DIAL-OUT:YES RTY:LIN NRTY:5 NRTY2:3 NRTY3:3 TB:3 CGO:# SGO:# CDO:# SDO:# - Tcp-MSS/Lcp/IpCp ----------------------------------------------------- TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414 maxmru:1500 DNS:NO - Authentication ------------------------------------------------------- USERNAME:myuserid LOCAL:CHAP PASSWORD:******************************** SERVNAME: REMOTE:CHAP REPEAT:0
PPP over EIR (P-LINK).
[13:51:12] ABILIS_CPX: D P PO:541 . PO:541 ------------------------------------------------------------------------ PPP LOG:DS LOWPO:200 VSPID:1 - Tcp-MSS/Lcp/IpCp ----------------------------------------------------- TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414 maxmru:1500 DNS:NO - Authentication ------------------------------------------------------- USERNAME:myuserid LOCAL:CHAP PASSWORD:******************************** SERVNAME: REMOTE:CHAP REPEAT:0
To activate changes made on the low case parameters it is needed to restart the system, on the contrary for the high case ones, it is enough to execute the initialization command INIT PO:.
LOWPO: | Identifier of the lower level Abilis CPX port |
NONE | 1 - 999, NONE |
Sets the lower level port; it can be any P-LINK or an S-LINK port.
The value "NONE" makes the PPP port unusable.
BCHAN: | Identifier of the channel B to use |
B1 | B1, B2 |
The parameter appears and can be modified only if the lower port is an ISDN Basic Rate port type, i.e. the service provided by "only data" ISDN adaptors.
Defines the channel to be used on the lower level ISDN port.
DLCI: | Identifier of the DLCI to use |
NONE | 16-991, 1024-63487, 131072-8126463, NONE |
The parameter appears and can be modified only if the lower port is a FR port type.
Defines the identifier of the DLCI to use the lower lever FR port.
The value "NONE" means "no DLCI" and it disables the connection with the lower level FR port.
The validity of allowed values intervals for the DLCI identifier depends on the length of the header Frame-Relay in use:
Value | Meaning |
---|---|
NO | No cryptography is applied. |
DATA | Cryptography is applied only on DATA traffic type. |
VOICE | Cryptography is applied only on VOICE traffic type. |
ALL | Cryptography is always in use, whatever is the traffic data type. |
CC: | Activation of the congestion control |
YES | NO, YES |
The parameter appears and can be modified only if the lower port is a FR port type.
Makes possible to apply or to not apply the throughput reduction as reaction to congestion notifications.
Not obeying to congestion notification may cause severe malfunctioning, therefore we strongly recommend to always use CC:YES. Ignoring congestion notification may be needed for some testing activities, certainly not during the regular work.
SC: | Value of the "step count" for Congestion Control |
4 | 1 - 50 |
The parameter appears and can be modified only if the lower port is a FR port type.
Sets how many consecutive frames with BECN=1 have to be received for reducing the throughput, according to the rule fixed by ANSI T1.618 annex A §2.1.1.
Value 4 suits the most frequent situations, however the right value can be evaluated by using the Calculator.
CIR: | Value of "Committed Information Rate" |
0 | 0, 4800 - 2500000 in bit/sec |
The parameter appears and can be modified only if the lower port is a FR port type.
Defines the value of "Committed Information Rate", i.e. the throughput the frame-relay network has to guarantee in normal working conditions. This throughput is measured in the time interval TC (Time Committed) given by the following formula: TC=BC/CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
BC: | Value of "Burst Committed" |
0 | 0, 2400 - 5000000 in bits |
The parameter appears and can be modified only if the lower port is a FR port type.
Defines the "Burst Committed", i.e. the number of bits the network can accept, during the time interval TC, to guarantee the CIR.
If the network is congested, it sends a signal (BECN or FECN) that require the user to progressively reduce his throughput to values smaller than CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
BE: | Value of "Burst Excess" |
0 | 0 - 5000000 in bits |
The appears and can be modified only if the lower port is a FR port type.
Defines the "Burst Excess", i.e. the number of bits in excess that the network can manage, during the time interval TC, if there is availability of exceeding resources. The "exceeding throughput" is evaluated by using the following formula ThExcess=BE*TC.
When the network does not have resources in excess sends a signal (BECN or FECN) that engages the user to immediately limit the throughput to the value of the CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
VSP-ID: | Service Identifier |
NONE | NONE, 1 - 32 |
The parameter appears and can be modified only if the lower port is a EIR port type.
This parameter indicates which Virtual Synchronous Port (VSP) of those defined in the TDM table the PPP must use.
DT-IN: | Disconnect timer on incoming call |
300 | numeric |
The parameter appears and can be modified only if the lower port is any S-LINK, e.g. EIR port type with VSPID=NONE.
This parameter specifies inactivity timer for incoming calls, i.e if this PPP
is called from outside and link is idle for this time, connection will be terminated.
Note that in this case only incoming packets are counted - packets coming from us to the client
are not counted as activity.
DT-OUT: | Disconnect timer on outgoing call |
300 | numeric |
The parameter appears and can be modified only if the lower port is any S_LINK, e.g. EIR port type with VSPID=NONE.
This parameter specifies inactivity timer for outgoing calls, i.e if this PPP itself called a remote host and link is idle for this time, connection will be terminated.
Note that in this case only outgoing packets are counted - packets coming from the server are not counted as activity.
DIAL-IN: | Incoming call allowance |
YES | NO, YES |
Determines if this PPP will answer incoming calls, i.e. serve as a Dial-Up Server.
Usually only one of DIAL-IN and DIAL-OUT should be set.
CGI: | Calling address of the incoming call |
* | from 1 up to 20 numerical characters [0- 9], * |
Sets up the calling address, that the incoming call must contain.
The character "*" means "any number".
SGI: | Calling sub-address of the incoming call |
* | from 1 up to 20 alphanumerical [0- 9, a - z, A- Z], * |
Sets up the calling sub-address, that the incoming call must contain.
The character "*" means "any character".
CDI: | Called address of the incoming call |
* | from 1 up to 20 numerical characters [0- 9], * |
Sets up the called address, that the incoming call must contain.
The character "*" means "any number".
SDI: | Called sub-address of the incoming call |
* | from 1 up to 20 alphanumerical [0- 9, a - z, A- Z], * |
Sets up the called sub-address, that the incoming call must contain.
The character "*" means "any character".
DIAL-OUT: | Outgoing call allowance |
YES | NO, YES |
Determines if this PPP is allowed to make outgoing calls, e.g. call an ISP.
Usually only one of DIAL-IN and DIAL-OUT should be set.
RTY: | Calls repetition rule on failures |
INC | LIN, INC, US |
Allows to select the calls repetition rule on the S-Link channel following an unsuccessful call, and if the attempts are exhausted the S-Link channel is placed in STOPPED1 state.
If the switched connection is established the attempts counter is reset (connection was established!), however if "link-checks" are active a "second level verification" is executed and if it fails the connection is classified as "link-check failure". Three consecutives "link-check failures" forces the S-Link channel in STOPPED2 state preventing any further outgoing or incoming call!
The behaviour upon exhausted attempts is slightly different when RTY:US, see below or details.
Value | Calls repetition rules |
---|---|
LIN | The time interval between a call attempt and the next one is
fixed and configurable through the parameter TB:. |
INC | The time interval between a call attempt and the next one, is doubled at every attempt, starting with the value defined in the parameter TB:. |
US | The abbreviation "US" stands for "unattended site". In this case the S-Link channel driver activates the following procedure until success:
It is important to emphasize that points 2,3,4,5,6 of the procedure do not distinguish between failure's reason (connection not established or connection established with "link-check" error) until the last attempt is reached and the last failure reason is used to set the final state (STOPPED1 or STOPPED2). |
NRTY: | Maximum number of CALL repetitions |
5 | 0 - 65534, NOMAX |
Specifies the maximum number of call repetitions for the S-Link channel when the connection cannot be established due to CALL command failure.
Once attempts are exhausted the port is placed in STOPPED1 state.
The behaviour upon exhausted attempts is slightly different when RTY:US.
Value | Meaning |
---|---|
0 | Outgoing calls are disabled. |
1-65534 | Calls are repeated as many times as the value. |
NOMAX | Calls are repeated indefinitely. For "RTY:INC" the time interval of calls after the 65535th will not increase further, keeping the interval TB: * 65535 seconds. For "RTY:US" the actual behaviour is identical to RTY:LIN because the condition that starts the "unattended site retries" will not be reached. |
NRTY2: | |
3 | 0 - 65534, NOMAX |
Specifies the maximum number of call repetitions for the S-Link channel when the connection cannot be established due to negotiation timeout.
Once attempts are exhausted the port is placed in STOPPED2 state.
NRTY3: | |
3 | 0 - 65534, NOMAX |
Specifies the maximum number of call repetitions for the S-Link channel when the connection cannot be established due to negotiation failure (e.g. authentication error).
Once attempts are exhausted the port is placed in STOPPED3 state.
TB: | Time base interval between calls repetitions |
3 | 3 - 255 (in seconds) |
Defines the "base" time interval that the retry procedure set in RTY: uses to calculate the delay between a call attempt that fails and the next one.
CGO: | Calling address of the outgoing call |
# | from 1 up to 20 numerical characters [0- 9], # |
Sets up the calling number of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the calling address.
SGO: | Calling sub-address of the outgoing call |
# | from 1 up to 6 alphanumerical [0- 9, a - z, A- Z], # |
Sets up the calling sub-address of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the calling sub-address.
CDO: | Called address of the outgoing call |
# | from 1 up to 20 numerical characters [0- 9], # |
Sets up the called number of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the called address.
SDO: | Called sub-address of the outgoing call |
# | from 1 up to 6 alphanumerical [0- 9, a - z, A- Z], # |
Sets up the called sub-address of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the called sub-address.
TCP-MSS-CLAMP: | Whether to perform TCP MSS clamping |
NO | NO, YES |
If set, forces PPP to change value of Maximum Segment Size in all TCP packets to one equal or lower than set with TCP-MSS-VALUE: option to avoid certain problems with PPP over Ethernet "black hole". Also can be used to reduce link latency at the cost of some bandwidth loss.
TCP-MSS-VALUE: | Maximal TCP MSS value to allow |
1414 | 496-1452 |
Specifies maximal allowed value for TCP Maximum Segment Size option.
This option is only visible if MSS clamping is allowed via TCP-MSS-CLAMP: parameter.
MAXMRU: | Maximal value of MRU accepted |
1500 | 1500 - 65535, NONE |
Specifies the maximal value of MRU (Maximal Receive Unit) to be negotiated.
One can try increasing this value to improve performance slightly
Changes to this value cannot be applied without CPX restart.
DNS: | DNS addresses negotiation |
NO | NO, RETRIEVE, PROVIDE |
Specifies negotiation of DNS addresses with a remote host.
Value | Meaning |
---|---|
NO | No DNS address negotiation is performed. |
PROVIDE | PPP can provide DNS addresses (if specified in corresponding IP Port) to a remote host. This is a common setting to be used on a Dial-Up Server. |
RETRIEVE | PPP requests DNS addresses from a remote host. This is a typical setting while accessing an ISP. |
USERNAME: | Login UserName |
no value | up to 32 characters |
Specifies UserName to authenticate to a remote peer.
Need not be set when operating as a Dial-Up Server.
PASSWORD: | Login Password |
no value | up to 32 characters |
Specifies Password to authenticate to a remote peer.
Need not be set when operating as a Dial-Up Server.
SERVNAME: | CHAP Server name |
no value | up to 32 characters |
Specifies this Server name to be sent along with CHAP Challenge.
Only needed for Dial-Up servers authorizing complicated clients with CHAP, usually can be left empty
LOCAL: | As-Client Authentication allowed |
CHAP | NONE, any combination of PAP,CHAP,MSCHAP1,MSCHAP2 |
Specifies authentication protocols usable in Client mode, i.e if remote requires us to authenticate.
REMOTE: | As-Server Authentication allowed |
CHAP | NONE, any combination of PAP,CHAP,MSCHAP1,MSCHAP2 |
Specifies authentication protocols usable in Server mode, i.e we'll require the remote to authenticate using one of these protocols.
Preference order is from most to least secure: MSCHAP2, MSCHAP1, CHAP, PAP.
REPEAT: | CHAP Repeating authentication |
NONE | 1 - 999, NONE |
Specifies how often, if ever, should CHAP require re-authentication while already connected, in seconds.
This parameter is intended to use when REMOTE:parameterr contains any CHAP protocol.
[15:18:04] CPX-INTERNET:D S PO:541 PO:541 ------------------------------------------------------------------------ PPP STATE:DOWN LCP-PH:DEAD IPCP-PH:DEAD LINK:READY LCP-ST:STARTING IPCP-ST:STARTING LOCAL-IP:000.000.000.000 REMOTE-IP:000.000.000.000 ST1:0 ST2:0 ST3:0 TIME_CUR_CALL:0 RTY:0 DT:0 USRTY:0 TDEL:0 TREM:0 -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| FAIL-CALL | 0| 0|SUCC-CALL | 0| 0| TIME-CALL | 0| 0| | | | AUTH-FAIL | 0| 0|CHR | 0| 0| PCK | 0| 0|PCK-SYS | 0| 0| DROPPED | 0| |LOST | 0| | ------------------------------------------------------------------------
[15:18:04] CPX-INTERNET:D SE PO:541 PO:541 ------------------------------------------------------------------------ PPP --- Cleared 000:00:00:11 ago, on 03/09/2002 at 15:17:53 ---------------- ST1:0 ST2:0 ST3:0 TIME_CUR_CALL:0 -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| FAIL-CALL | 0| 0|SUCC-CALL | 0| 0| TIME-CALL | 0| 0| | | | AUTH-FAIL | 0| 0|CHR | 0| 0| PCK | 0| 0|PCK-SYS | 0| 0| DROPPED | 0| |LOST | 0| | ------------------------------------------------------------------------
STATE: | General PPP state |
UP, DOWN, DELAYING, STOPPED1, STOPPED2, STOPPED3 |
States | Meaning |
---|---|
UP | PPP is either already connected or ready to connect. |
DOWN | Lower layer not connected. |
DELAYING | Temporarily unable to call due to delay after unsuccessful attempt. Incoming calls are accepted. |
STOPPED1 | Unable to call due to call failure limit exceeded. Incoming calls are accepted. |
STOPPED2 | Unable to call due to negotiation timeout limit exceeded. Incoming calls are accepted. |
STOPPED3 | Unable to call due tonegotiationn failure limit exceeded. Incoming calls are accepted. |
LINK: | Link state |
NOTPRESENT, DOWN, READY, LISTENING, CONNECTED, CALLING, CALLED, CLEARING, CLEARED |
Specifes state of a lower layer link.
States | Meaning |
---|---|
NOTPRESENT | Port specified by LOWPO: is not present or inactive. |
DOWN | Link is down due to some lower layer problems. |
READY | Link is ready to connect/listen. |
LISTENING | Link is listening for an incoming call. |
CONNECTED | Link is connected and ready to transmit data. |
CALLING | Link is actively calling the remote host. |
CALLED | Link is processing an incoming call. |
CLEARING | Link is actively terminating existing connection. |
CLEARED | Link was terminated from remote. |
LCP-PH: | LCP Protocol phase |
DEAD, ESTABLISHING, AUTHENTICATING, NETWORK, TERMINATING |
Current LCP Protocol phase, Consult RFC 1661 for details
States | Meaning |
---|---|
DEAD | LCP is inactive. |
ESTABLISHING | LCP is negotiating link parameters. |
AUTHENTICATING | Authentication protocol is running. |
NETWORK | LCP is ready to transmit upper layer traffic, NCPs can start. |
TERMINATING | LCP is terminating a connection. Over P-LINK LCP never goes to DEAD state, remaining in this one. |
LCP-ST: | |
STARTING, STOPPED, STOPPING, REQSENT, ACKRCVD, ACKSENT, OPENED |
Current LCP state
States | Meaning |
---|---|
STARTING | Waiting for lower link to go UP. |
STOPPED | Work finished, waiting for lower link to go DOWN. |
STOPPING | Terminate-Request sent. |
REQSENT | Configure-Request sent. |
ACKRCVD | Configure-Request sent and Configure-Ack received, but no Configure-Request received. |
ACKSENT | Configure-Request sent, Configure-Request received and Configure-Ack sent, but no Configure-Ack received. |
OPENED | Negotiation complete. |
IPCP-PH: | |
DEAD, ESTABLISHING, NETWORK, TERMINATING |
Current IPCP phase. For description, see LCP-PH:
IPCP-ST: | IPCP state |
STARTING, STOPPED, STOPPING, REQSENT, ACKRCVD, ACKSENT, OPENED |
Current IPCP state. For description, see LCP-ST:
LOCAL-IP: | Local IP address |
0.0.0.0 | xxx.xxx.xxx.xxx |
IP address of this machine, corresponding to this IP port.
The value is set either if preset in IP port configuration, or retrieved from remote host.
REMOTE-IP: | Remote IP address |
0.0.0.0 | xxx.xxx.xxx.xxx |
IP address of machine on the other end of a link.
The value is set either if preset in IP port configuration, or provided by the remote host (which overrides preset value).
ST1: | STOPPED1 Count |
numeric |
Determines how much times PPP went into STOPPED1 state
ST2: | STOPPED2 Count |
numeric |
Determines how much times PPP went into STOPPED2 state
ST3: | STOPPED3 Count |
numeric |
Determines how much times PPP went into STOPPED3 state
TIME_CUR_CALL: | Current call time duration |
numeric |
Specifies how long is the current connection taking time.
RTY: | STOPPED counter |
numeric |
Specifies how much times call was unsuccessful. When it reaches NRTY: value, and RTY: parameter is not US, PPP will go into STOPPEDx state. IfRTY: is US, additional, retries will be indicated by USRTY stat.
USRTY: | STOPPED counter for RTY=US |
numeric |
Specifies how much times call was unsuccessful, after reaching NRTY: value.
When it reaches 25, PPP will go into STOPPEDx state.
Valid only for RTY==US setting.
DT: | Inactivity timer |
numeric |
Specifies time for which PPP was inactive. When it reaches the DT-IN: or DT-OUT: value PPP will close the link.
TDEL: | Current delay between calls |
numeric |
Specifies how much PPP delays after ununsuccessfulAL before trying again.
TREM: | Delay remaining |
numeric |
If STATE=DELAYING, specifies delay remaining before new CALL can be tried
SUCC-CALL: | Successful CALLs |
numeric |
Specifies number of successful outgoing CALLs
FAIL-CALL: | Failed CALLS |
numeric |
Specifies number of failed outgoing CALLs
TIME-CALL: | Total connection time |
numeric |
Total time when PPP was connected
AUTH-FAIL: | Authentication failed |
numeric |
Total number of authentication failures
CHR: | Characters in/out |
numeric |
Total number of bytes received/sent
PCK: | |
numeric |
Total number of packets received/sent
PCK-SYS: | |
numeric |
Total number of system (LCP, IPCP and authentication) packets received/sent
DROPPED: | |
numeric |
Number of packets dropped due to unknown protocol or incorrect order. Small numbers (about 1-2 per connection) do not indicate any malfunction
LOST: | |
numeric |
Total number of packets lost due to queue overflow
Trap own code | Trap mnemonic | SNMP variables shown in the trap | Description |
---|---|---|---|
60 | cxTrapPppDown | cxPortIndex, cxPortType, cxPppDiagPppState, cxPppDiagLinkState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the PPP port driver goes in to the "Down" states set. |
61 | cxTrapPppUp | cxPortIndex, cxPortType, cxPppDiagPppState, cxPppDiagLinkState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the PPP port driver exits the "Down" states set. |
62 | cxTrapPppStopped | cxPortIndex, cxPortType, cxPppDiagPppState, cxPppDiagLinkState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the PPP port driver goes in to the "Stopped" states set. |
63 | cxTrapPppReady | cxPortIndex, cxPortType, cxPppDiagPppState, cxPppDiagLinkState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the PPP port driver exits the "Stopped" states set. |
cxPortIndex | ETH port which the SNMP trap refers to |
0 - 999 |
This variable shows the CPX port number which the SNMP trap refers to.
cxPortType | Type and description of the PPP port which the trap refers to |
type - description |
This variable shows either the port type which the trap refers to (in this case PPP) and the description eventually associated to it.
cxPppDiagPppState | General PPP state |
stopped1(0), stopped2(1), stopped3(2), delaying(3), down(4), up(5) |
This variable stores the general PPP state value when the trap is generated (See STATE:).
SNMP variable value | Corresponding General PPP state |
---|---|
stopped1(0) | STOPPED1 |
stopped2(1) | STOPPED2 |
stopped3(2) | STOPPED3 |
delaying(3) | DELAYING |
down(4) | DOWN |
up(5) | UP |
cxPppDiagLinkState | Link state |
not_present(0), down(1), ready(2), listening(3), calling(4), called(5), clearing(6), cleared(7), connected(8) |
This variable stores the lower link state value when the trap is generated (See LINK:).
SNMP variable value | Corresponding Link state |
---|---|
not_present(0) | NOTPRESENT |
down(1) | DOWN |
ready(2) | READY |
listening(3) | LISTENING |
calling(4) | CALLING |
called(5) | CALLED |
clearing(6) | CLEARING |
cleared(7) | CLEARED |
connected(8) | CONNECTED |
sysUpTime | Elapsed time from the system start to the event occurrence |
0 - 4.294.967.295 or "ddd:hh:mm:ss" |
This variable stores the elapsed time (in cent of second) from the system start to the SNMP trap event occurrence.
This value is usually shown by the format days:hours:minutes:seconds.
LSN 0: | Debug commands help |
PO:541 ------------------------------------------------------------------------ PPP BufferLength:207 Date/Time:30/08/2002 15:17:11 TraceTime:<NotRunning> LSN 1: PPP information LSN 2: IP information LSN 3: Negotiated options LSN 4: LCP/IPCP/Link states LSN 5: Four above combined LSN 10: CALL log (20 to clear) LSN 11: PPP Negotiation log (21 to clear)
LSN 1: | PPP information |
PPP Not Connected, State=UP STOPPED1 Counter: 0 (NRTY=5) STOPPED2 Counter: 0 / 3 STOPPED3 Counter: 0 / 3
Time Connected: 00:00:47 Authentication: Local: NONE, Remote: NONE Idle: 00:00:47 (DT=00:05:00 as server)
LSN 2: | IP information |
Not Connected CONFIGURED Local IP: 192.168.002.002 Remote IP: 000.000.000.000 Primary DNS: 000.000.000.000 Secondary DNS: 000.000.000.000 MRU: 1500 MTU: 1500
CONFIGURED NEGOTIATED Local IP: 192.168.002.003 192.168.002.003 Remote IP: 000.000.000.000 192.168.002.005 Primary DNS: 000.000.000.000 000.000.000.000 Secondary DNS: 000.000.000.000 000.000.000.000 MRU: 1500 1500 MTU: 1500 1492
LSN 3: | Negotiated options |
Not Connected Local parameters: MRU=1500 MagicNumber=0x30D61E2E AuthProto=CHAP PFC=YES ACFC=YES VJ=NO Remote parameters: MRU=1500 MagicNumber=0x00000000 AuthProto=NONE PFC=NO ACFC=NO VJ=NO Will accept negotiation: PAP Will require negotiation: CHAP
Local parameters: MRU=1500 MagicNumber=0x30D61E2E AuthProto=CHAP PFC=YES ACFC=YES VJ=NO Remote parameters: MRU=1492 MagicNumber=0x7D9C661A AuthProto=NONE PFC=YES ACFC=YES VJ=NO
LSN 4: | LCP/IPCP/Link states |
Not Connected Link State: CONNECTED LCP Phase: TERMINATING, State: STOPPED IPCP Phase: DEAD, State: STARTING
Link State: CONNECTED LCP Phase: NETWORK, State: OPENED IPCP Phase: NETWORK, State: OPENED
LSN 5: | Shows info for LSN 2, 3 and 4 in one call |
LSN 10: | CALL log |
30.08.02 15:16:38 Listening 30.08.02 15:25:11 Accepting 30.08.02 15:25:11 Accepting - succeeded 30.08.02 15:29:35 Hanging up with cause 0x81-0x90 - 0xF0-0xA3 30.08.02 15:29:35 Hanging up - succeeded 30.08.02 15:29:35 ----------------
LSN 11: | PPP negotiation log |
30.08.02 15:29:35 LCP: Unsupported/unallowed CHAP method requested: 0x05 30.08.02 15:29:35 ----------------