Enabling PPP SNMP

Edit online

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:

retrieval of PPP Link Configuration information (such as Maximum Receive Unit size and Asynchronous Character Mapping)
setting of PPP Link Configuration information
retrieval of LCP interface information for active LCP links
changing of the state of active LCP links can be changed to "down" by setting the appropriate ifAdminStatus Management Information Base (MIB) object

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:

The pppLinkConfigMagicNumber object is read only. In PPP, magic number negotiation is always performed and cannot be disabled.
The pppLinkConfigFcsSize object is read only. PPP only supports FCS sizes of 16 with this operating system.

By default, SNMP for PPP is disabled. To enable PPP SNMP, you can 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 described in Asynchronous Point-to-Point Protocol configuration before enabling PPP SNMP.

Start the SMIT Interface and display the Change/Show a Link Configuration screen by entering:
```
smit chglcp
```
Toggle the Enable PPP SNMP subagent field to yes.
Accept your changes and exit SMIT.

PPP SNMP is not enabled until PPP is restarted.

If PPP is currently running,
1. Stop PPP using the smit stopppp fast path (see the table in Asynchronous Point-to-Point Protocol configuration).
2. Periodically check to see if the subsystem has completed shutdown by entering:
```
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.
3. Start PPP using the smit startppp fast path (see the table in Asynchronous Point-to-Point Protocol configuration).
If PPP is not currently running, start PPP using the smit startppp fast path (see the table in Asynchronous Point-to-Point Protocol configuration).