I.2. L2TP information
Prev Appendix I. FireBrick specific SNMP objects Next

I.2. L2TP information

Information about specific L2TP peers.

Note

Some OIDs contains an IP. This is coded as either 4.a.b.c.d for IPv4 address a.b.c.d, or 16 followed by 16 entries each 0 to 255 for the bytes in the IPv6 address when represented in net byte order. The IP is the IP of the L2TP peer you wish to check.

Table I.2. iso.3.6.1.4.1.24693.1701

...OIDTypeMeaning
0.1.0IntegerNumber of tunnels in FREE state
0.1.1IntegerNumber of tunnels in OPENING state
0.1.2IntegerNumber of tunnels in LIVE (incoming) state
0.1.3IntegerNumber of tunnels in LIVE (outgoing) state
0.1.4IntegerNumber of tunnels in CLOSING state
0.1.5IntegerNumber of tunnels in FAILED state
0.1.6IntegerNumber of tunnels in CLOSED state
0.2.0IntegerNumber of sessions in FREE state
0.2.1IntegerNumber of sessions in WAITING state
0.2.2IntegerNumber of sessions in OPENING state
0.2.3IntegerNumber of sessions in NEGOTIATING state
0.2.4IntegerNumber of sessions in AUTH-PENDING state
0.2.5IntegerNumber of sessions in STARTED state
0.2.6IntegerNumber of sessions in LIVE state
0.2.7IntegerNumber of sessions in ACCT-PENDING state
0.2.8IntegerNumber of sessions in CLOSING state
0.2.9IntegerNumber of sessions in CLOSED state
0.2.10IntegerNumber of session negotiation slots free
1.IPStringThe login name
2.IPStringThe host name
3.IPIntegerNumber of incoming tunnels
4.IPIntegerNumber of outgoing tunnels
5.IPIntegerSeconds since oldest live tunnel connected
6.IPIntegerNumber of live tunnels
7.IPIntegerNumber of sessions

Prev Up Next
Appendix I. FireBrick specific SNMP objects Home I.3. VoIP information