The Asynchronous Point-to-Point Protocol (PPP) subsystem provides an alternative to SLIP. PPP provides a standard method for transporting multiprotocol datagrams over point-to-point media. PPP is comprised of three main layers:
This implementation of PPP supports the following Request for Comments (RFCs):
PPP differentiates between client and server. This operating system can act as both a client and a server. The distinction is made to simplify configuration. PPP servers tend to allocate a pool of IP addresses among the connections that are being made. There is some correlation between the media devices. This implementation of PPP breaks this correlation. All server PPP connections are allocated on a first-available basis. This facilitates the separation of PPP from the media. The attachment process must request to be linked to the proper type of link.
The Asynchronous Point-to-Point Protocol on this operating system utilizes three user-level processes:
You can use Web-based System Manager or SMIT to configure the Asynchronous Point-to-Point Protocol. The following table shows all tasks that you may need when configuring your system. You must have root privileges to perform the tasks in this table.
At a minimum, when you initially configure your system, you must choose the following tasks from the table:
Task | SMIT fast path | Web-based System Manager Management Environment |
---|---|---|
Create Link Control Configuration | smit ppplcp | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link. |
Add a Link Configuration | smit addlcp |
|
Change/Show a Link Configuration | smit chglcp |
|
Remove a Link Configuration1 | smit rmlcp | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Link Configuration --> Remove Link Configuration. |
Create PPP IP Interfaces | smit pppip |
|
Add a Server Interface | smit addpppserver | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to Point (PPP) --> Configure the Point-to-Point Link --> Server Interfaces --> Add/Change Interface. |
Change/Show a Server Interface | smit listserver | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Server Interfaces --> Add/Change Interface. |
Remove a Server Interface1 | smit rmlistserver | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Server Interfaces --> Delete Interface. |
Add a Demand Interface | smit addpppdemand | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Demand Interfaces --> Add/Change Interface. |
Change/Show a Demand Interface | smit listdemand | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Demand Interfaces --> Add/Change Interface. |
Remove a Demand Interface1 | smit rmlistdemand | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Configure the Point-to-Point Link --> Demand Interfaces --> Delete Interface. |
Manipulate PAP users/passwords | smit ppppap |
|
Add a PAP User | smit addpapuser |
|
Change/Show a PAP User | smit listpapuser |
|
Remove a PAP User | smit rmpapuser |
|
Manipulate CHAP users/passwords | smit pppchap |
|
Add a CHAP User | smit addchapuser |
|
Change/Show a CHAP User | smit listchapuser |
|
Remove a CHAP User | smit rmchapuser |
|
Start PPP2 | smit startppp | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Start the PPP Subsystem. |
Stop PPP3 | smit stopppp | Software --> Network --> TCPIP (IPv4 and IPv6) --> Point-to-Point (PPP) --> Stop the PPP Subsystem. |
Notes:
- Selecting this task destroys the existing information.
- An alternative way to start PPP is to issue the startsrc -s pppcontrold command. However, the SMIT interface also allows you to set PPP to start at boot time.
- An alternative way to stop PPP is to issue the stopsrc -s pppcontrold command. However, the SMIT interface also allows you to have PPP not start at boot time.
PPP can interact with the TCP/IP SNMP daemon to report PPP link layer configuration information as well as information about active Link Control Protocol (LCP) interfaces. Providing that both the TCP/IP SNMP and the SNMP management software are configured correctly, PPP SNMP enables:
Not all objects defined by RFC1471 for the PPP MIB are supported. Only the pppLink table applies to the PPP subsystem, thus the pppLqr and pppTests portions are not supported. The pppLink portion is supported with the following exceptions:
By default, SNMP for PPP is disabled. To enable PPP SNMP, you can use the Web-based System Manager, wsm, or use the following procedure. You must have root privileges to perform this procedure.
Note: The following procedure assumes that PPP Link Configuration is already set. If not, perform the procedure in "Configuring the Asynchronous Point-to-Point Protocol" before enabling PPP SNMP.
smit chglcp
PPP SNMP is not enabled until PPP is restarted.
lssrc -s pppcontrold
The amount of time it takes to completely stop the subsystem is dependent on the number of links defined in the PPP configuration. The subsystem is completely shut down when the output of this command shows a status of inoperative.