Home/Catalog/ATT-VPN-GATEWAY-MIB

ATT-VPN-GATEWAY-MIB

AI MIB Summary

The ATT-VPN-GATEWAY-MIB provides SNMP management capabilities for AT&T VPN Gateway appliances, enabling the monitoring of tunnel interface states, session establishment counts, and gateway resource utilization metrics. This module facilitates the tracking of VPN connectivity status and performance data essential for maintaining secure enterprise network links.

The MIB module for the AT&T VPN Gateway.
Main OID:
attVpnGatewayMIB.1.3.6.1.4.1.74.1.30.8
435
Objects
Active
Status
4
Dependencies

Imported Objects

SNMPv2-SMI
SNMPv2-TC
INET-ADDRESS-MIB
SNMPv2-CONF

Objects

435 total
Object Name
att_2
OBJECT IDENTIFIER
.1.3.6.1.4.1.74
att_products
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1
attVpnGateway
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30
ngHardwareInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.1
nghwHardwareVersionHardware Version.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.1
nghwCodeVersionSoftware code version.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.2
nghwAccountThe account in Service Manager this device is registered under.ro
DisplayString
.1.3.6.1.4.1.74.1.30.1.3
nghwUtcOffsetIndicates how many minutes away from UTC time the device is located. Values must be in 30 minute increments. Valid range is -840 to 840.ro
Integer32(-840..840)
.1.3.6.1.4.1.74.1.30.1.4
nghwDstAllowedIndicates if the device is located in an area that observes daylight savings time.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.5
nghwDstActiveIndicates if daylight savings time is current active at this date and time.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.6
nghwWanConnectionMethodThe current primary IPv4 WAN connection setting. This is configured via the web interface and is not read from Service Manager.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.7
nghwHostnameThe name of the current host.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.8
nghwDnsServers
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.1.9
ngDnsTableThe (conceptual) table of DNS on the device. An entry shall be placed in the storage table for each DNS.
SEQUENCE OF NgDnsEntry
.1.3.6.1.4.1.74.1.30.1.9.1
ngDnsEntryA (conceptual) entry for one logical DNS area on the host.
NgDnsEntry
.1.3.6.1.4.1.74.1.30.1.9.1.1
ngdnIndexA unique value for each logical DNS contained on the device.
Integer32
.1.3.6.1.4.1.74.1.30.1.9.1.1.1
ngdnServerThe IP address of an indivdual name server in use.ro
IpAddress
.1.3.6.1.4.1.74.1.30.1.9.1.1.2
ngDnsIPv6TableThe (conceptual) table of IPv6 DNS on the device. An entry shall be placed in the storage table for each DNS.
SEQUENCE OF NgDnsIPv6Entry
.1.3.6.1.4.1.74.1.30.1.9.2
ngDnsIPv6EntryA (conceptual) entry for one logical IPv6 DNS area on the host.
NgDnsIPv6Entry
.1.3.6.1.4.1.74.1.30.1.9.2.1
ngdnIPv6IndexA unique value for each logical IPv6 DNS contained on the device.
Integer32
.1.3.6.1.4.1.74.1.30.1.9.2.1.1
ngdnIPv6ServerThe IPv6 IP address of an indivdual name server in use.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.1.9.2.1.2
nghwDeviceStatusThe current device status.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.10
nghwLanguageThe language that will be displayed on the CGI web interface. The valid values are: EN = English JA = Japanese ES = Spanish BP = Brazil Portuguese FC = French Canadian TC = Traditional Chinese SC = Simplified Chinesero
DisplayString
.1.3.6.1.4.1.74.1.30.1.11
nghwCustComm
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.1.12
ngCustCommTableThe (conceptual) table of customer info (such as comments) on the device. An entry shall be placed in the storage table for each one.
SEQUENCE OF NgCustCommEntry
.1.3.6.1.4.1.74.1.30.1.12.1
ngCustCommEntryA (conceptual) entry for one logical customer comment area on the host.
NgCustCommEntry
.1.3.6.1.4.1.74.1.30.1.12.1.1
ngcuIndexA unique value for each logical customer info.
Integer32
.1.3.6.1.4.1.74.1.30.1.12.1.1.1
ngcuCustCommentA free-format field that can be added to the AT&T VPN Gateway's profile at a customer's request. Currently only one comment field can be specified.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.12.1.1.2
nghwPorts
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.1.13
ngPortTableThe (conceptual) table of ports on the device. An entry shall be placed in the storage table for each port.
SEQUENCE OF NgPortEntry
.1.3.6.1.4.1.74.1.30.1.13.1
ngPortEntryA (conceptual) entry for one logical port area on the host.
NgPortEntry
.1.3.6.1.4.1.74.1.30.1.13.1.1
ngpoIndexA unique value for each logical port contained on the device.
Integer32
.1.3.6.1.4.1.74.1.30.1.13.1.1.1
ngpoStatusThe link status of an individual hardware port.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.13.1.1.2
nghwCurrentWanConnectionMethodThe currently active IPv4 WAN connection, which may differ from the configured primary IPv4 WAN connection setting. For example, the primary IPv4 WAN is configured for DHCP (wanConfigDHCP), but because of a network outage the PPPoE secondary WAN connection (wanConfigPPPoE2) is currently providing connectivity.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.14
nghwIPv6WanConnectionMethodThe current primary IPv6 WAN connection setting. This is configured via the web interface and is not read from Service Manager.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.15
nghwIPv6CurrentWanConnectionMethodThe currently active IPv6 WAN connection, which may differ from the configured primary IPv6 WAN connection setting. For example, the primary IPv4 WAN is configured for DHCP (wanConfigIPv6DHCP), but because of a network outage the static IP secondary WAN connection (wanConfigIPv6Static2) is currently providing connectivity.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.16
nghwLastFullQueryTimeDATThe last time when the AT&T VPN Gateway was successfully able to retrieve its full profile from an AT&T Administration Server.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.17
nghwLastAnyQueryTimeDATThe last time when the AT&T VPN Gateway was successfully able to retrieve its profile from an AT&T Administration Server. If this time does not match nghwLastFullQueryTimeDAT then that means only part of the profile was retrieved. This is to prevent any possible reboots if critical portions of the profile were to change.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.18
nghwLastUpgradeTimeDATThe last time when the software version of AT&T VPN Gateway was successfully upgraded. Returns January 1 year 0 time 0 when this cannot be determined.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.19
hwMacThe main WAN MAC address of this device used to identify its profile in Service Manager.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.20
hwRollbackVersionSoftware code version that will be used if the rollback feature is activated.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.21
hwDualWanTies to the 'Use as Internet Primary' field in Service Manager. Controls the Dual WAN configuration.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.22
hwWan2ConnectionMethodThe current WAN2 IPv4 WAN connection setting. This is not configured via the web interface and is read from Service Manager.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.23
hwIPv6Wan2ConnectionMethodThe current WAN2 IPv6 WAN connection setting. This is not configured via the web interface and is read from Service Manager.ro
Enumeration
.1.3.6.1.4.1.74.1.30.1.24
hwWan1GwayMacThis is the MAC Address of the WAN1 Gateway router if it is in use. For MAC Address range from 002704000000 to 002704009999, it is a NetBridge (SX) device. For MAC Address range from 002704010000 to 002704010425, it is a NetBridge (FX) device. For MAC Address range from 002704010426 to 002704019999, it is a Cell Extender (6200-FX) device. For MAC Address range from 002704270000 to 002704279999, it is a Cell Extender (6300-CX) device.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.25
hwWan2MacThis is the MAC Address of the WAN2 interface if it is in use.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.26
hwWan2GwayMacThis is the MAC Address of the WAN2 Gateway router if it is in use. For MAC Address range from 002704000000 to 002704009999, it is a NetBridge (SX) device. For MAC Address range from 002704010000 to 002704010425, it is a NetBridge (FX) device. For MAC Address range from 002704010426 to 002704019999, it is a Cell Extender (6200-FX) device. For MAC Address range from 002704270000 to 002704279999, it is a Cell Extender (6300-CX) device.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.1.27
ngInterfaceInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.2
ngifActiveWanIfaceThe interface that is currently in use for the primary connection.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.2.1
ngifTotalBytesInTotal bytes in on the active WAN interface.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.2.2
ngifTotalBytesOutTotal bytes out on the active WAN interface.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.2.3
ngifTimeInDialHow long the current dial connection has been up.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.2.4
ifTimeInBackupHow long the backup connection has been up. This is very similar to ngifTimeInDial. The difference is that ngifTimeInDial isn't necessarily measuring a backup connection. For example, when configured for 'Dial As Primary' ifTimeInBackup will always remain zero because there is no backup for Dial As Primary but ngifTimeInDial will be non-zero when the connection is up. In other WAN configurations (such as DHCP, for example) both ngifTimeInDial and ifTimeInBackup will be non-zero when the backup connection is in use.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.2.5
ifInterfaceFormatSetting from the Service Manager profile that controls SNMP interface persistence. Zero indicates that this feature is not in use.ro
Enumeration
.1.3.6.1.4.1.74.1.30.2.6
ifIfaceStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.2.7
ifStatTableThe (conceptual) table of interface statistics on the device. An entry shall be placed in the storage table for each interface statistic.
SEQUENCE OF IfStatEntry
.1.3.6.1.4.1.74.1.30.2.7.1
ifStatEntryA (conceptual) entry for one logical interface statistic area.
IfStatEntry
.1.3.6.1.4.1.74.1.30.2.7.1.1
ifStatsMainIndexA unique value for each logical interface statistic.
Integer32
.1.3.6.1.4.1.74.1.30.2.7.1.1.1
ifStatsifIndexThe value of this index reported by ifIndex in the standard MIBs. This is needed because index numbers can be skipped in the standard MIBs.ro
Integer32
.1.3.6.1.4.1.74.1.30.2.7.1.1.2
ifStatsifDescrA textual string containing information about the interface.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.2.7.1.1.3
ifStatsRxCrcErrReceived CRC errors for the interface.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.2.7.1.1.4
ifCircuitSpeedInformational string that is pulled from the device profile. Useful for the scenario where the physical connection to the WAN interface will be 10, 100 or 1000 Mbps (depending on the ISP modem/router) but the speed allocated by the ISP will be much lower (2, 4, or 8 Mbps). This field does not control speed and does not indicate a measurement of speed. It is manually entered by an administrator for informational purposes only.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.2.8
ngVlanInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.3
ngVlanTableThe (conceptual) table of VLANs on the device. An entry shall be placed in the storage table for each VLAN.
SEQUENCE OF NgVlanEntry
.1.3.6.1.4.1.74.1.30.3.1
ngVlanEntryA (conceptual) entry for one logical VLAN area on the host.
NgVlanEntry
.1.3.6.1.4.1.74.1.30.3.1.1
ngvlIndexA unique value for each logical VLAN contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.3.1.1.1
ngvlIdThis is the number assigned to the VLAN. Please note: A VLAN with an ID of 4070 is a special VLAN used to hold ports that are disabled.ro
Integer32
.1.3.6.1.4.1.74.1.30.3.1.1.2
ngvlPortsThe ports assigned to the VLAN.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.3.1.1.3
ngvlSpeedThis is the speed supported on the VLAN Ethernet interfaces. If the VLAN Ethernet speed is configured for auto negotiation then autoNegot will be reported and the negotiated speed will be reported by ngvlSpeedCurrent. If the VLAN Ethernet speed is configured for a specific speed that speed will be reported.ro
Enumeration
.1.3.6.1.4.1.74.1.30.3.1.1.4
ngvlIpRangeThe range of IP addresses handed out via DHCP on this VLAN. Values will be 0.0.0.0 0.0.0.0 if DHCP is not enabled on this VLAN. Followed by number of addresses assigned and number of total addresses. NOTE: As of AT&T VPN Gateway version 5.3 the number of addresses assigned will no longer be returned. A zero will be returned for that field.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.3.1.1.5
ngvlDhcpRelayAddrWhen the DHCP Type is 'R', this is the address the AT&T VPN Gateway devices uses to relay DHCP requests. This field is required when the DHCP Type is 'R'. A second address can be specified.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.3.1.1.6
ngvlDhcpDefRouteThis field is required when VRRP Active Indicator is 'Y' and is optional otherwise. If specified, it must be within the local LAN subnet of the AT&T VPN Gateway but cannot fall within the DHCP pool start and end addresses. For the DHCP Default Route on the AT&T VPN Gateway device profile, if entered, the address must be within the network specified by the LAN Address and LAN Subnet, but not within the address range specified by the DHCP Start Address and DHCP End Address.ro
IpAddress
.1.3.6.1.4.1.74.1.30.3.1.1.7
ngvlLanAddrThis is the LAN address for the device on the VLAN.ro
IpAddress
.1.3.6.1.4.1.74.1.30.3.1.1.8
ngvlLanSubAddrThis is the LAN subnet address for the device on the VLAN.ro
IpAddress
.1.3.6.1.4.1.74.1.30.3.1.1.9
ngvlIPv6IpRangeStartThe start of the range of IPv6 IP addresses handed out via DHCP on this VLAN. Value will be all zeroes if DHCP is not enabled on this VLAN.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.3.1.1.10
ngvlIPv6IpRangeEndThe end of the range of IPv6 IP addresses handed out via DHCP on this VLAN. Value will be all zeroes if DHCP is not enabled on this VLAN.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.3.1.1.11
ngvlIPv6DhcpRelayAddrPriWhen the DHCP Type is 'R', this is the primary address the AT&T VPN Gateway devices uses to relay DHCP requests. This field is required when the DHCP Type is 'R' and IPv6 is in use.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.3.1.1.12
ngvlIPv6DhcpRelayAddrBakWhen the DHCP Type is 'R', this is the primary address the AT&T VPN Gateway devices uses to relay DHCP requests.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.3.1.1.13
ngvlIPv6LanAddrThis is the IPv6 LAN address for the device on the VLAN.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.3.1.1.14
ngvlIPv6LanPrefixThis is the IPv6 LAN prefix for the device on the VLAN.ro
Integer32
.1.3.6.1.4.1.74.1.30.3.1.1.15
ngvlSpeedCurrentThis is the current speed in use on the VLAN Ethernet interfaces. This is helpful to determine what was chosen if the speed was set to auto negotiate. If the VLAN Ethernet speed is configured for auto negotiation then the negotiated speed will be reported. If the VLAN Ethernet speed is configured for auto negotiation and there is no link then noLink will be reported. If the VLAN Ethernet speed is configured for a specific speed that speed will be reported.ro
Enumeration
.1.3.6.1.4.1.74.1.30.3.1.1.16
ngVrrpInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.4
ngVrrpTableThe (conceptual) table of VRRPs on the device. An entry shall be placed in the storage table for each VRRP.
SEQUENCE OF NgVrrpEntry
.1.3.6.1.4.1.74.1.30.4.1
ngVrrpEntryA (conceptual) entry for one logical VRRP area on the host.
NgVrrpEntry
.1.3.6.1.4.1.74.1.30.4.1.1
ngvrIndexA unique value for each logical VRRP contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.4.1.1.1
ngvrIfaceThe interface associated with this VRRP.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.4.1.1.2
ngvrIdVirtual router ID.ro
Integer32
.1.3.6.1.4.1.74.1.30.4.1.1.3
ngvrMasterStatusShows what the status is (master, backup, not active).ro
Enumeration
.1.3.6.1.4.1.74.1.30.4.1.1.4
ngvrPriorityVRRP_PRIO_OWNER 255 /* priority of the ip owner -- rfc2338.5.3.4 */ VRRP_PRIO_DFL 100 /* default priority -- rfc2338.5.3.4 */ VRRP_PRIO_STOP 0 /* priority to stop -- rfc2338.5.3.4 */ro
Enumeration
.1.3.6.1.4.1.74.1.30.4.1.1.5
ng3GInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.5
ng3GTableThe (conceptual) table of 3G cards on the device. An entry shall be placed in the storage table for each 3G card.
SEQUENCE OF Ng3GEntry
.1.3.6.1.4.1.74.1.30.5.1
ng3GEntryA (conceptual) entry for one logical 3G card area on the host.
Ng3GEntry
.1.3.6.1.4.1.74.1.30.5.1.1
ng3gIndexA unique value for each logical 3G card contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.5.1.1.1
ng3gSlotNumThe slot the card is plugged into. Returns -1 if no card is found. NOTE: this refers to PCMCIA slots, not USB ports.ro
Integer32
.1.3.6.1.4.1.74.1.30.5.1.1.2
ng3gModemTypeThe modem type.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.3
ng3gManufacturerThe 3G card manufacturer.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.4
ng3gModelThe 3G card model.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.5
ng3gRevisionThe 3G card revision.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.6
ng3gIDEither the IMEI or ESN depending on the card.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.7
ng3gSignalStrengthSignal Strength at the connect. This value will remain zero if cellBars is non-zero.ro
Integer32
.1.3.6.1.4.1.74.1.30.5.1.1.8
ng3gCarrierInformation about the carrier.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.9
ng3gImsiStatusThe IMSI attach status.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.10
ng3gCellConnNetworkThe connected network.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.11
ng3gPhoneNumThe cell phone number.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.12
ng3gApnThe access point name.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.13
ng3gApnUserThe APN userid. Only populated when the access point name exists.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.14
ng3gApnPasswordThe APN password. Only populated when the access point name exists.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.15
ng3gCellModemPresentIf the cellular modem is a supported unit that allows the AT&T VPN Gateway to query its current status then this value will indicate whether or not the unit is physically present. Unsupported units will always have a value of 'unknown'.ro
Enumeration
.1.3.6.1.4.1.74.1.30.5.1.1.16
ng3gSIMCardNumberThe SIM number of the card.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.17
ng3gDeviceTypeThe type of hardware of the cellular modem.ro
Enumeration
.1.3.6.1.4.1.74.1.30.5.1.1.18
cellCollectionTimeDATThe date and time the cell stats were collected. Not set if the date and time on the device hasn't been set yet.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.19
cellConnStatusThe current status of the cellular connection.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.20
cellNetworkTechCell network technology.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.21
cellCarrierCellular carrier.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.22
cellMCCA mobile country code (MCC) is used in combination with a mobile network code (MNC) (also known as a MCC / MNC tuple) to uniquely identify a mobile phone operator (carrier) using the GSM, UMTS, LTE, and iDEN public land mobile networks as well as some CDMA, TETRA, and satellite mobile networks.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.23
cellMNCMobile network codero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.24
cellLACTower location area code.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.25
cellCIDA GSM Cell ID (CID) is a generally unique number used to identify each Base transceiver station (BTS) or sector of a BTS within a Location area code (LAC) if not within a GSM network. In some cases the last digit of CID represents cells' Sector ID. A valid CID ranges from 0 to 65535 on GSM and CDMA networks and from 0 to 268435455 on UMTS and LTE networks.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.26
cellBarsA number indicating the signal strength as a bar count. If this value is non-zero then ng3gSignalStrength will return zero.ro
Integer32
.1.3.6.1.4.1.74.1.30.5.1.1.27
cellRSSIReceived signal strength indicator.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.28
cellECIOEC/IO measurement.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.29
cellRSRPReferences LTE signals: Reference Signal Received Power is the average power of resource elements that carry cellular specific reference signals over the entire bandwidth. Valid values : all values are valid. Typical values are between -199 and -85. The larger the number (-85 for instance) the better the signal.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.30
cellRSRQReferences LTE Signals: represents the Cell Quality.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.31
cellSINRReferences LTE signals: LTE - The signal-to-interference-plus-noise ratio of the modem.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.32
cellSNRReferences LTE signals: The signal-to-noise ratio of the modem.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.33
cellIfaceThe interface on the device associated with this cell modem.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.5.1.1.34
ngTunnelInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.6
ngTunnelTableThe (conceptual) table of tunnels on the device. An entry shall be placed in the storage table for each tunnel.
SEQUENCE OF NgTunnelEntry
.1.3.6.1.4.1.74.1.30.6.1
ngTunnelEntryA (conceptual) entry for one logical tunnel area on the host.
NgTunnelEntry
.1.3.6.1.4.1.74.1.30.6.1.1
ngtuIndexA unique value for each logical tunnel contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.6.1.1.1
ngtuIpsecIfaceThe ipsec interface associated with the tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.2
ngtuAuthStateAn internal state used to indicate the tunnel's current operation.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.3
ngtuStateAn internal state used to indicate the tunnel's status. This state was created because the ngtuAuthState can change while the tunnel is still up. For example, when the clock is being set. This state is always attTunnelUp when the tunnel is up.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.4
ngtuDurationHow long the tunnel has been up.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.6.1.1.5
ngtuEndpointIP of the endpoint the tunnel is connected to. Populated if the ngtuState is 'up'.ro
IpAddress
.1.3.6.1.4.1.74.1.30.6.1.1.6
ngtuEndpointTypeType of the endpoint the tunnel is connected to. Populated if the ngtuState is 'up'.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.7
ngtuBulkEncryptModeBulk encryption mode.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.8
ngtuCurrEncryptCeIpBulk encryption CE address.ro
IpAddress
.1.3.6.1.4.1.74.1.30.6.1.1.9
ngtuEspAlgESP algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.10
ngtuAuthAlgAUTH algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.11
ngtuCompressionAlgCOMPRESSION algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.12
ngtuAuthTypeIndicates the authentication server that will be used by the tunnel endpoint.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.13
ngtuAuthProtThe authentication protocol.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.14
ngtuReasonCodeA numeric value that indicates why an inbound or outbound tunnel came down. The one exception is tnlAlive, which is sent for the tunnel 'alive' message for a tunnel that is still up.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.15
ngtuServerMgmtAGNS managed or not.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.16
ngtuTunInitiatorWhat initiated the tunnel.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.17
ngtuTunModeThe tunnel control mode.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.18
ngtuIPv6EndpointIPv6 IP of the endpoint the tunnel is connected to. Populated if the ngtuState is 'up' and IPv6 is in use.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.6.1.1.19
tunCurrAutomationThe tunnel automation that is currently in use and whether or not it is currently active. NOTE: Active does not necessarily mean that the tunnel is up. It could mean that the tunnel is up, in the process of coming up, or is in a state where it will be brought up if the right conditions are met. There is no automation for User Initiated mode.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.20
tunInitVpnConThe tunnel automation (if any) configured for the primary connection in Service Manager. If configured for User Initiated the user can choose to override that setting from the CGI interface and select Persistent or Traffic Initiated instead.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.21
tunInitVpnBkupConSimilar to tunInitVpnCon except that this controls tunnel automation via the backup connection.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.22
tunConnectionIdThe tunnel connection ID is a unique value assigned to each instance of a tunnel. It is used to associate the tunnel up, tunnel alive, and tunnel down traps together. When a tunnel goes down and is then re-established it will be assigned a new tunnel connection ID. This is the same value reported by ngevTunConnectionId in traps.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.23
tunNameThe name associated with this tunnel. Note that the name will be 'settings' if multi-tunnel is disabled.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.6.1.1.24
tunDirectionIndicates whether this is an inbound or outbound tunnel.ro
Enumeration
.1.3.6.1.4.1.74.1.30.6.1.1.25
ngCosInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.7
ngcoEnabledIndicates if COS is enabled or not. As of version 6.2 bandwidth testing can be active without COS being enabled. When that happens ngcoEnabled will return zero (notActive) but ngcoNextTestTimeDAT will not return January 1 year 0 time 0 for the time.ro
Enumeration
.1.3.6.1.4.1.74.1.30.7.1
ngcoNextTestTimeWhen the next bandwidth test is scheduled to run. MM/DD/YYYY HH:MM:SS. Returns '00/00/0000 00:00:00' when no test is scheduled. The time returned is the local time on the AT&T VPN Gateway. To determine how the AT&T VPN Gateway's local time relates to UTC view the following OIDs: nghwUtcOffset (current UTC offset), nghwDstAllowed (daylight saving time allowed), nghwDstActive (daylight savings time active). NOTE: This entry is made obsolete by ngcoNextTestTimeDAT.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.7.2
ngcoWanMtuCurrent WAN interface MTU value.ro
Integer32
.1.3.6.1.4.1.74.1.30.7.3
ngcoCurUpstreamBandwCurrent upstream bandwidth high water mark in use.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.7.4
ngcoCurDownstreamBandwCurrent downstream bandwidth high water mark in use.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.7.5
ngcoNextTestTimeDATWhen the next bandwidth test is scheduled to run. Returns January 1 year 0 time 0 when no test is scheduled. NOTE: This entry replaces ngcoNextTestTime.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.7.6
ngcoLastTestTimeDATThe date and time of when the last bandwidth test was performed. NOTE: The date and time of high water marks retained after a reboot will return January 1 year 0 time 0 for the time.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.7.7
ngcoLastUpstreamResultThe upstream bandwidth measured when the last bandwidth test was performed.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.7.8
ngcoLastDownstreamResultThe downstream bandwidth measured when the last bandwidth test was performed.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.7.9
attVpnGatewayMIBThe MIB module for the AT&T VPN Gateway.
MODULE-IDENTITY
.1.3.6.1.4.1.74.1.30.8
ngMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.1
ngMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.1.1
ngBasicComplianceRevThe compliance statement for AT&T VPN Gateway entities which implement this MIB module.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.1.1
ngMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.1.2
nghwGroupThe hardware group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.1
ngifGroupThe interface group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.2
ngvlGroupThe VLAN group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.3
ngvrGroupThe VRRP group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.4
ng3gGroupThe 3G group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.5
ngtuGroupThe tunnel group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.6
ngcoGroupThe COS group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.7
ngfwGroupThe firewall group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.8
ngrmGroupThe Rogue MAC group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.9
ngdiGroupThe dial group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.10
ngdhlGroupThe DHCP leases group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.11
ngCapPorGroupThe Captive Portal group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.12
attInbTunGroupThe Inbound Tunnel group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.13
attInbTunNetGroupThe Inbound Tunnel Network group.
Unknown
.1.3.6.1.4.1.74.1.30.8.1.2.14
ngEvents
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2
ngEventNotification
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.0
ngevIpConntrackTableSent if the Firewall Connection table reaches the specified threshold.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.1
ngevIpConntrackTableFullIndicates the firewall Connection table has reached capacity.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.2
ngevExcessiveDialThe device has been in dial backup longer than the allowed threshold.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.3
ngevActiveWanIpChangedThe IP address associated with the active WAN interface has changed. For example, dial backup was initiated because WAN connectivity was lost. Another example is that a PPPoE connection changed its IP address.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.4
ngevRogueMacDetectedThe unauthorized MAC detection feature is enabled and an unauthorized MAC address was detected.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.5
ngevRogueMacNoFileThe unauthorized MAC detection feature is enabled and the authorized MAC file doesn't exist.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.6
ngevNoTepsThe AT&T VPN Gateway cannot bring up a tunnel to any of the tunnel endpoints.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.7
ngevDeviceDiscoOrNotFoundSent if the AT&T VPN Gateway profile is not found. If the AT&T VPN Gateway goes too long without finding its device profile then the device will switch its status to discontinued, which will also trigger a trap/inform.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.8
ngevTunnelUpInformation about the results of a tunnel connection attempt.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.9
ngevTunnelDownInformation about a tunnel disconnect. The one exception is a tunnel 'alive' message, which is sent for a tunnel that is still up. Tunnel 'alive' messages have a ngtuReasonCode of tnlAlive.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.10
ngevDialAutotestFailureThe Dial Autotest (and all specified retries) failed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.11
ngevDeviceRebootSent when the device reboots. Requestor IP will be set to loopback if an automated process caused the reboot.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.12
ngevDeviceShutdownSent when the device shuts down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.13
ngevSshLoginSent when a user accesses the device via SSH.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.14
ngevDhcpPoolExhaustedSent when a VLAN's DHCP pool is full.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.15
ngevForTestingOnlyOnly for use by QA and development for testing.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.16
ngevSecondaryAuthAttemptSent when a secondary login attempt occurs. Secondary logins are performed when someone tries to ssh into the AT&T VPN Gateway.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.17
ngevSwitchUseridAttemptSent when a user who is ssh'ed into the AT&T VPN Gateway tries to switch to another userid.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.18
ngev8200VPortDownSent when either port 7 or 8 is determined to be not active. Only used by the AT&T VPN Gateway 8200V.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.19
ngevCellModemRequiredSent when either the AT&T VPN Gateway boots without a cell modem present or when the AT&T VPN Gateway detects that the cell modem has been removed. The cellular modem must be a supported unit that allows the AT&T VPN Gateway to query its current status.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.20
evVrrpStateChangeSent when there is a VRRP state change.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.21
evDualWanIfaceProblemSent when the AT&T VPN Gateway is configured to also use the second WAN port as Internet Primary and one of the interfaces could not be brought up.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.22
evOOBCableRequiredOptional USB cables allow out of bound (OOB) access to the AT&T VPN Gateway. The number of OOB cables expected to be plugged into the AT&T VPN Gateway is controlled by a setting in Service Manager. This event is sent when either the AT&T VPN Gateway boots without the expected number of cables present, when the AT&T VPN Gateway detects that a cable was present but has been removed, or when all missing cables are returned.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.23
evTunConfigChangedSent when the tunnel configuration has changed. All tunnels (if any) are restarted when this occurs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.24
evDataUsageReportReporting of average bandwidth along with high water mark calculations.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.25
evPingTestResultSent to indicate the result of a ping test.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.26
evNoIPinCDPoolSent to indicate that there are no available IP addresses in the customer direct pool.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.27
evMaxInbTunSent to indicate that there are no inbound tunnels available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.28
evReportDualWanIPSent to report on the IP addresses in use when both Dual WAN interfaces are up.
NOTIFICATION-TYPE
.1.3.6.1.4.1.74.1.30.8.2.0.29
ngEventObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.1
ngevMacThe MAC address in Service Manager this device is registered under.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.1
ngevRogueMacThe MAC address of the unauthorized machine detected when MAC monitoring is enabled.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.2
ngevActiveWanIpThe IP address of the active WAN interface. When viewing the output of the SNMP tree this can be determined from the interface statistics. However, for traps the active WAN interface might not be used to send the trap (i.e. it could be down the tunnel. Set to zero if not used.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.3
ngevIpConntrackMaxPercentageAn alert will be sent when the ip_conntrack table is within this percentage of the maximum.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.4
ngevIpConntrackCurrentPercentageThe ip_conntrack table is currently at this percentage of the maximum.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.5
ngevTimeInDialThe number of minutes the device has been connected via dial.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.6
ngevQueryProblemUsed to indicate what type of problem is happening with the device's status. profileNotFound means that a profile for the device was not found on an AT&T Administration Server in any region. discontinuingTheDevice means that the device has gone too long without having a valid profile in any region. bandwNoResults means that a bandwidth test failed and no previous bandwidth test results have been found, which results in the device being marked as discontinued until a bandwidth test works.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.7
ngevTunConnectionIdThe tunnel connection ID is a unique value assigned to each instance of a tunnel. It is used to associate the tunnel up, tunnel alive, and tunnel down traps together. When a tunnel goes down and is then re-established it will be assigned a new tunnel connection ID.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.8
ngevTunnelDateAndTimeThe timestamp from when the tunnel came up, tried to come up, or came down.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.9
ngevConnectionTypeIndicates whether the tunnel is via broadband or dial.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.10
ngevAccountIn the tunnel up/down trap it is the customer account used to start the tunnel. In the secondary auth attempt trap it is the account used for the login attempt.ro
DisplayString
.1.3.6.1.4.1.74.1.30.8.2.1.11
ngevUseridIn the tunnel up/down trap it is the customer userid used to start the tunnel. In the secondary auth attempt trap it is the userid used for the login attempt.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.12
ngevTunConReasonString that shows a message that explains the results of a tunnel connection attempt.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.13
ngevDialTestFailReasonString that shows why the dial test failed.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.14
ngevSshSourceIpThe IP address of the client that ssh'ed into the device.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.15
ngevRequestorIpThe IP address of the machine that initiated a particular request (reboot, shutdown, secondary auth attempt, etc.). Will be set to loopback if an automated process caused the reboot.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.16
ngevDialTestFailCategoryShows what type of category the dial test failure would be put in. For example, a busy signal would be a warning but a bad password would be an error.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.17
ngevRogueIpThe IP address of the unauthorized machine detected when MAC monitoring is enabled. Set to zero if not used.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.18
ngevRogueInterfaceThe interface of the unauthorized machine detected when MAC monitoring is enabled.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.19
ngevTrapDescriptionFor MAC monitoring this is the Service Manager description field. Other traps may use this field for other purposes.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.20
ngevLoginResultSpecifies the result of the secondary login attempt when someone tries to ssh into the AT&T VPN Gateway.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.21
ngevNewLocalIDThe userid that the user became after their secondary login attempt was successful. Secondary logins are performed when someone tries to ssh into the AT&T VPN Gateway. The userid that the user became (or tried to become) for their switch user attempt.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.22
ngevOldLocalIDThe userid that was in use when the user made their switch user attempt.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.23
ngevMaxTimeInDialUntilAlertThe max number of minutes the device can be connected via dial without a trap being sent for excessive dial. Once this maximum is reached a trap will be sent.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.8.2.1.24
ngevPortDownAn individual port that is currently not active. Only used by the AT&T VPN Gateway 8200V.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.25
ngevIPv6ActiveWanIpThe IP address of the active IPv6 WAN interface. When viewing the output of the SNMP tree this can be determined from the interface statistics. However, for traps the active WAN interface might not be used to send the trap (i.e. it could be down the tunnel. Set to zero if not used.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.26
ngevIPv6RogueIpThe IPv6 IP address of the unauthorized machine detected when MAC monitoring is enabled. Set to zero if not used.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.27
ngevIPv6RequestorIpThe IPv6 IP address of the machine that initiated a particular request (reboot, shutdown, secondary auth attempt, etc.). Will be set to loopback if an automated process caused the reboot.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.28
ngevCardNotFoundTimeThe timestamp that indicates when the AT&T VPN Gateway noted that the required cellular card was missing.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.29
ngevVPNServiceIPv4AddressThe VPN Service Address assigned for this tunnel connetion. Will be not set if this is an IPv6 tunnel or the tunnel did not come up.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.30
ngevVPNServiceIPv6AddressThe VPN Service Address assigned for this tunnel connetion. Will be not set if this is an IPv4 tunnel or the tunnel did not come up.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.31
ngevTunConReasonNUMA numeric value that indicates the results of an inbound or outbound tunnel connection attempt.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.32
evIfaceThe interface in question for this event.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.33
evNotFoundTimeThe timestamp that indicates when the AT&T VPN Gateway noted that the item in question was missing.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.34
evTrapCreatedTimeThe timestamp that indicates when the trap was actually generated. If informs are in use and the server is temporarily not reachable it could be a long time before the inform is actually received.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.35
evDualWanProbUsed to help indicate why IPv4 WAN2 could not be brought up when configured for Dual WAN. The generic 'dwTrapGeneralErr' is used when a specific reason isn't available. 'dwTrapNone' means that there was no error.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.36
evDualWanV6ProbUsed to help indicate why IPv6 WAN2 could not be brought up when configured for Dual WAN. The generic 'dwTrapGeneralErr' is used when a specific reason isn't available. 'dwTrapNone' means that there was no error.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.37
evFoundOOBHow many OOB cables were detected when at least one was found to be missing.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.38
evExpectedOOBHow many OOB cables were expected when at least one was found to be missing.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.39
evResultGeneric field to indicate a result.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.40
evSrcV4Generic source IPv4 address.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.41
evDestV4Generic destination IPv4 address.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.42
evSrcV6Generic source IPv6 address.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.43
evDestV6Generic destination IPv6 address.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.44
evResponseMaxGeneric field to indicate how long a test waited for a response.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.45
evFailureCountGeneric field to indicate how many failures occurred before this event was generated.ro
Integer32
.1.3.6.1.4.1.74.1.30.8.2.1.46
evDescriptionGeneric field for description.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.47
evSendTrapWhenGeneric field used to indicate when to send a trap after a test is performed.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.48
evWan1IPv4IPField used to report on the IP of the first interface if it is using IPv4.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.49
evWan1IPv4NameField used to report on the name of the first interface if it is using IPv4.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.50
evWan1IPv6IPGeneric field used to report on the IP of the first interface if it is using IPv6.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.51
evWan1IPv6NameField used to report on the name of the first interface if it is using IPv6.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.52
evWan2IPv4IPGeneric field used to report on the IP of the second interface if it is using IPv4.ro
IpAddress
.1.3.6.1.4.1.74.1.30.8.2.1.53
evWan2IPv4NameField used to report on the name of the second interface if it is using IPv4.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.54
evWan2IPv6IPGeneric field used to report on the IP of the second interface if it is using IPv6.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.8.2.1.55
evWan2IPv6NameField used to report on the name of the second interface if it is using IPv6.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.56
evNatTEnabledTunnel field that indicates whether or not Nat-T is in use.ro
Enumeration
.1.3.6.1.4.1.74.1.30.8.2.1.57
evESPAlgorithmTunnel field that indicates the ESP Algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.58
evAuthAlgorithmTunnel field that indicates the Auth Algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.59
evCompressionAlgorithmTunnel field that indicates the (optional) Compression Algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.8.2.1.60
ngEventConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.2
ngEventCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.2.1
ngevBasicComplianceRevThe compliance statement for AT&T VPN Gateway entities which implement this MIB module.
Unknown
.1.3.6.1.4.1.74.1.30.8.2.2.1.1
ngEventGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.2.2
ngevNotificationsGroupThe event notifications
Unknown
.1.3.6.1.4.1.74.1.30.8.2.2.2.1
ngevObjectsGroupThe event ojects.
Unknown
.1.3.6.1.4.1.74.1.30.8.2.2.2.2
ngEventDataUsageObjectsGroupThe event ojects used only for data usage statistics.
Unknown
.1.3.6.1.4.1.74.1.30.8.2.2.2.3
ngEventDataUsageObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.2.3
evDataUpHwmThe upstream high water mark to be used for the calculations.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.1
evDataDownHwmThe downstream high water mark to be used for the calculations.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.2
evDataUp1Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.3
evDataDown1Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.4
evDataUp2Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.5
evDataDown2Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.6
evDataUp3Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.7
evDataDown3Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.8
evDataUp4Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.9
evDataDown4Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.10
evDataUp5Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.11
evDataDown5Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.12
evDataUp6Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.13
evDataDown6Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.14
evDataUp7Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.15
evDataDown7Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.16
evDataUp8Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.17
evDataDown8Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.18
evDataUp9Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.19
evDataDown9Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.20
evDataUp10Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.21
evDataDown10Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.22
evDataUp11Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.23
evDataDown11Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.24
evDataUp12Average upstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.25
evDataDown12Average downstream bandwidth measured over a certain time period.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.8.2.3.26
ngPlatforms
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.3
attVpnGateway8200
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.3.1
attVpnGateway8300
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.3.2
attVpnGatewayVM
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.8.3.3
ngFirewallInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.9
ngFirewallTableThe (conceptual) table of firewall tables on the device. An entry shall be placed in the storage table for each table.
SEQUENCE OF NgFirewallTableEntry
.1.3.6.1.4.1.74.1.30.9.1
ngFirewallTableEntryA (conceptual) entry for one logical firewall table area on the host.
NgFirewallTableEntry
.1.3.6.1.4.1.74.1.30.9.1.1
ngfwTableIndexA unique value for each logical firewall table contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.1.1.1
ngfwTableNameThe name of this table.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.1.1.2
ngfwTableNumberOfChainsThe number of chains in this particular table.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.1.1.3
ngFirewallChainTableThe (conceptual) chain of firewall chains on the device. An entry shall be placed in the storage chain for each chain.
SEQUENCE OF NgFirewallChainEntry
.1.3.6.1.4.1.74.1.30.9.2
ngFirewallChainEntryA (conceptual) entry for one logical firewall chain area on the host.
NgFirewallChainEntry
.1.3.6.1.4.1.74.1.30.9.2.1
ngfwChainIndexA unique value for each logical firewall chain contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.2.1.1
ngfwChainTableIndexShows what table this chain belongs to. Corresponds to ngfwTableIndex in ngFirewallTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.2.1.2
ngfwChainNameThe name of this chain.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.2.1.3
ngfwChainsNumberOfRulesThe number of rules in this particular chain.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.2.1.4
ngFirewallRuleTableThe (conceptual) table of firewall rules on the device. An entry shall be placed in the storage rule for each rule.
SEQUENCE OF NgFirewallRuleEntry
.1.3.6.1.4.1.74.1.30.9.3
ngFirewallRuleEntryA (conceptual) entry for one logical firewall rule area on the host.
NgFirewallRuleEntry
.1.3.6.1.4.1.74.1.30.9.3.1
ngfwRuleIndexA unique value for each logical firewall rule contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.3.1.1
ngfwRuleTableIndexShows what table this rule belongs to. Corresponds to ngfwTableIndex in ngFirewallTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.3.1.2
ngfwRuleChainIndexShows what chain this rule belongs to. Corresponds to ngfwChainIndex in ngFirewallChainTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.3.1.3
ngfwRulePacketsTotal packets for this rule.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.9.3.1.4
ngfwRuleBytesTotal bytes for this rule.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.9.3.1.5
ngfwRuleTargetThe rule target.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.3.1.6
ngfwRuleProtocolThe rule protocol.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.3.1.7
ngfwRuleInIfaceThe rule input interface.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.3.1.8
ngfwRuleOutIfaceThe rule output interface.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.3.1.9
ngfwRuleSrcIpThe rule source IP.ro
IpAddress
.1.3.6.1.4.1.74.1.30.9.3.1.10
ngfwRuleSrcMaskThe rule source mask in CIDR-compliant format.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.3.1.11
ngfwRuleDstIpThe rule destination IP.ro
IpAddress
.1.3.6.1.4.1.74.1.30.9.3.1.12
ngfwRuleDstMaskThe rule destination mask in CIDR-compliant format.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.3.1.13
ngfwRuleMiscThe rule MISC section.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.3.1.14
ngfwIpConntrackNumEntriesThe number entries in the ip_conntrack file.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.4
ngfwIpConntrackMaxNumEntriesThe maximum number of entries in the ip_conntrack file.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.5
ngIPv6FirewallTableThe (conceptual) table of IPv6 firewall tables on the device. An entry shall be placed in the storage table for each table.
SEQUENCE OF NgIPv6FirewallTableEntry
.1.3.6.1.4.1.74.1.30.9.6
ngIPv6FirewallTableEntryA (conceptual) entry for one logical IPv6 firewall table area on the host.
NgIPv6FirewallTableEntry
.1.3.6.1.4.1.74.1.30.9.6.1
ngfwIPv6TableIndexA unique value for each logical IPv6 firewall table contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.6.1.1
ngfwIPv6TableNameThe name of this table.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.6.1.2
ngfwIPv6TableNumberOfChainsThe number of chains in this particular table.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.6.1.3
ngIPv6FirewallChainTableThe (conceptual) chain of IPv6 firewall chains on the device. An entry shall be placed in the storage chain for each chain.
SEQUENCE OF NgIPv6FirewallChainEntry
.1.3.6.1.4.1.74.1.30.9.7
ngIPv6FirewallChainEntryA (conceptual) entry for one logical IPv6 firewall chain area on the host.
NgIPv6FirewallChainEntry
.1.3.6.1.4.1.74.1.30.9.7.1
ngfwIPv6ChainIndexA unique value for each logical IPv6 firewall chain contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.7.1.1
ngfwIPv6ChainTableIndexShows what table this chain belongs to. Corresponds to ngfwIPv6TableIndex in ngIPv6FirewallTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.7.1.2
ngfwIPv6ChainNameThe name of this chain.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.7.1.3
ngfwIPv6ChainsNumberOfRulesThe number of rules in this particular chain.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.7.1.4
ngIPv6FirewallRuleTableThe (conceptual) table of IPv6 firewall rules on the device. An entry shall be placed in the storage rule for each rule.
SEQUENCE OF NgIPv6FirewallRuleEntry
.1.3.6.1.4.1.74.1.30.9.8
ngIPv6FirewallRuleEntryA (conceptual) entry for one logical IPv6 firewall rule area on the host.
NgIPv6FirewallRuleEntry
.1.3.6.1.4.1.74.1.30.9.8.1
ngfwIPv6RuleIndexA unique value for each logical IPv6 firewall rule contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.9.8.1.1
ngfwIPv6RuleTableIndexShows what table this rule belongs to. Corresponds to ngfwIPv6TableIndex in ngIPv6FirewallTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.8.1.2
ngfwIPv6RuleChainIndexShows what chain this rule belongs to. Corresponds to ngfwIPv6ChainIndex in ngIPv6FirewallChainTable.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.8.1.3
ngfwIPv6RulePacketsTotal packets for this rule.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.9.8.1.4
ngfwIPv6RuleBytesTotal bytes for this rule.ro
Unsigned32
.1.3.6.1.4.1.74.1.30.9.8.1.5
ngfwIPv6RuleTargetThe rule target.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.8.1.6
ngfwIPv6RuleProtocolThe rule protocol.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.8.1.7
ngfwIPv6RuleInIfaceThe rule input interface.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.8.1.8
ngfwIPv6RuleOutIfaceThe rule output interface.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.8.1.9
ngfwIPv6RuleSrcIpThe rule source IP. Not used and set to all zeroes for IPv4 firewall output.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.9.8.1.10
ngfwIPv6RuleSrcMaskThe rule source mask in CIDR-compliant format. Not used and set to all zeroes for IPv4 firewall output.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.8.1.11
ngfwIPv6RuleDstIpThe rule source IP. Not used and set to all zeroes for IPv4 firewall output.ro
InetAddressIPv6 (INET-ADDRESS-MIB)
.1.3.6.1.4.1.74.1.30.9.8.1.12
ngfwIPv6RuleDstMaskThe rule source mask in CIDR-compliant format. Not used and set to all zeroes for IPv4 firewall output.ro
Integer32
.1.3.6.1.4.1.74.1.30.9.8.1.13
ngfwIPv6RuleMiscThe rule MISC section.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.9.8.1.14
ngRogueMacInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.10
ngRogueMacStatusInidicates whether or not Rogue MAC detection has been enabled in Service Manager.ro
Enumeration
.1.3.6.1.4.1.74.1.30.10.1
ngRogueMacTableThe (conceptual) table of rogue MACs detected by the device. An entry shall be placed in the storage table for each rogue MAC.
SEQUENCE OF NgRogueMacEntry
.1.3.6.1.4.1.74.1.30.10.2
ngRogueMacEntryA (conceptual) entry for one logical rogue MAC area on the host.
NgRogueMacEntry
.1.3.6.1.4.1.74.1.30.10.2.1
ngrmIndexA unique value for each logical rogue MAC detected by the device.
Integer32
.1.3.6.1.4.1.74.1.30.10.2.1.1
ngrmMacThe MAC address of this detected rogue MAC. One entry that is zeroed out is returned when there are no rogue MACs detected.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.10.2.1.2
ngrmTimestampThe date and time of when this rogue MAC was detected. Returned as a regular string in the format MM/DD/YYYY HH:MM:SS. Returns '00/00/0000 00:00:00' when there are no rogue MACs detected. The time returned is the local time on the AT&T VPN Gateway. To determine how the AT&T VPN Gateway's local time relates to UTC view the following OIDs: nghwUtcOffset (current UTC offset), nghwDstAllowed (daylight saving time allowed), nghwDstActive (daylight savings time active). NOTE: This entry is made obsolete by ngrmTimestampDAT.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.10.2.1.3
ngrmIfaceThe interface this rogue MAC was detected on. One entry that with a value of 'NONE' and a msg is returned when there are no rogue MACs detected.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.10.2.1.4
ngrmTimestampDATThe date and time of when this rogue MAC was detected. Returns January 1 year 0 time 0 when there are no rogue MACs detected or the time is unknown. NOTE: This entry replaces ngrmTimestamp.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.10.2.1.5
ngDialInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.11
ngdiPhoneNumThe full phone number that will be dialed by the AT&T VPN Gateway. This also includes dial prefix information. For example, the AT&T VPN Gateway might have to dial the number nine and then a comma to access an outside line. The nine and the comma will be included in this entry.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.11.1
ngdiLastTestResultThe result of the last dial test. If no dial test has been performed yet then 'failure' is returned. If a dial test is not needed because dial is currently up then 'success' is returned.ro
Enumeration
.1.3.6.1.4.1.74.1.30.11.2
ngdiLastTestCompleteTimeThe approximate time the last dial test completed given in the format MM/DD/YYYY HH:MM:SS. Returns '00/00/0000 00:00:00' when no test is scheduled. or when no test has run yet. If the dial connection is currently in use then the dial test is not needed (since dial is obviously already working). ngdiLastTestCompleteTime is simply updated to the recent time whent the AT&T VPN Gateway last verified that the dial connection was still up. The time returned is the local time on the AT&T VPN Gateway. To determine how the AT&T VPN Gateway's local time relates to UTC view the following OIDs: nghwUtcOffset (current UTC offset), nghwDstAllowed (daylight saving time allowed), nghwDstActive (daylight savings time active). NOTE: This entry is made obsolete by ngdiLastTestCompleteTimeDAT.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.11.3
ngdiDialTestFailCategoryShows what type of category the dial test failure would be put in. For example, a busy signal would return dialProblemWarning but a bad password would return dialProblemError. If a dial test is not needed because dial is currently up then dialProblemMessage is returned.ro
Enumeration
.1.3.6.1.4.1.74.1.30.11.4
ngdiDialTestFailReasonString that shows why the dial test failed. If the test was successful or the dial connection is currently up then 'success' is returned.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.11.5
ngdiLastTestCompleteTimeDATIf the dial connection is currently in use then the dial test is not needed (since dial is obviously already working). ngdiLastTestCompleteTimeDAT is simply updated to the recent time whent the AT&T VPN Gateway last verified that the dial connection was still up. Returns January 1 year 0 time 0 when no test is scheduled or when no test has run yet. The time returned is the local time on the AT&T VPN Gateway. To determine how the AT&T VPN Gateway's local time relates to UTC view the following OIDs: nghwUtcOffset (current UTC offset), nghwDstAllowed (daylight saving time allowed), nghwDstActive (daylight savings time active). NOTE: This entry replaces ngdiLastTestCompleteTime.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.11.6
ngdiSecondaryPhoneNumSpecifies the secondary phone number to be tried for Dial Backup in case the primary Dial Backup phone number is not available.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.11.7
ngDhcpLeaseInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.12
ngDhcpLeaseTableThe (conceptual) table of all current, active DHCP leases on the device. An entry shall be placed in the storage table for each DHCP lease.
SEQUENCE OF NgDhcpLeaseEntry
.1.3.6.1.4.1.74.1.30.12.1
ngDhcpLeaseEntryA (conceptual) entry for one logical DHCP lease on the host.
NgDhcpLeaseEntry
.1.3.6.1.4.1.74.1.30.12.1.1
ngdhlIndexA unique value for each logical DHCP lease contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.12.1.1.1
ngdhlLeaseAddrThe IP address associated with an indivdual DHCP lease.ro
IpAddress
.1.3.6.1.4.1.74.1.30.12.1.1.2
ngdhlMacThe MAC address associated with an indivdual DHCP lease.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.12.1.1.3
ngdhlHostnameThe hostname associated with an indivdual DHCP lease.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.12.1.1.4
ngdhlPortThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.12.1.1.5
ngdhlVlanIdThe VLAN ID on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.12.1.1.6
ngCaptPortalInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.13
ngCapPorTableThe (conceptual) table of all current, active DHCP leases on the device. An entry shall be placed in the storage table for each DHCP lease.
SEQUENCE OF NgCapPorEntry
.1.3.6.1.4.1.74.1.30.13.1
ngCapPorEntryA (conceptual) entry for one logical DHCP lease on the host.
NgCapPorEntry
.1.3.6.1.4.1.74.1.30.13.1.1
ngcpIndexA unique value for each logical DHCP lease contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.1
ngcpAddrThe IP address associated with an indivdual DHCP lease.ro
IpAddress
.1.3.6.1.4.1.74.1.30.13.1.1.2
ngcpMacThe MAC address associated with an indivdual DHCP lease.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.13.1.1.3
ngcpUserThe hostname associated with an indivdual DHCP lease.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.13.1.1.4
ngcpDurationThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.5
ngcpMaxDurationThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.6
ngcpStateThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.7
ngcpIdleThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.8
ngcpMaxIdleThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.9
ngcpPortThe physical port (if valid) on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.10
ngcpVlanIdThe VLAN ID on the device associated with an indivdual DHCP lease.ro
Integer32
.1.3.6.1.4.1.74.1.30.13.1.1.11
attInbTunInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.74.1.30.14
attInbTunTableThe (conceptual) table of inbound tunnels on the device. An entry shall be placed in the storage table for each inbound tunnel.
SEQUENCE OF AttInbTunEntry
.1.3.6.1.4.1.74.1.30.14.1
attInbTunEntryA (conceptual) entry for one logical inbound tunnel area on the host.
AttInbTunEntry
.1.3.6.1.4.1.74.1.30.14.1.1
inbTunIndexA unique value for each logical inbound tunnel contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.14.1.1.1
inbTunClientTransAddrThe client transport address of this inbound tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.2
inbTunLocalIpsecIfaceThe IPsec interface associated with this inbound tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.3
inbTunTypeThe tunnel type of this inbound tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.4
inbTunUseridThe userid associated with this inbound tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.5
inbTunSrvConfigProfThe Service Manager profile associated with this inbound tunnel.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.6
inbTunTimeEstablishedTime this inbound tunnel was established.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.1.1.7
inbTunDurationHow long this inbound tunnel has been up.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.14.1.1.8
inbTunIdleTimeoutThis inbound tunnel's idle timeout setting.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.14.1.1.9
inbTunCurrIdleTimeoutHow long this inbound tunnel has been idle.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.14.1.1.10
inbTunNegIkePhase1LifetThis inbound tunnel's negotiated IKE Phase 1 lifetime.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.14.1.1.11
inbTunNatTNegotiatedIs NAT-T negotiated for this inbound tunnel?ro
Enumeration
.1.3.6.1.4.1.74.1.30.14.1.1.12
inbTunActClientSaNegActive client SA's negotiated for this inbound tunnel.ro
Integer32
.1.3.6.1.4.1.74.1.30.14.1.1.13
attInbTunNetTableThe (conceptual) table of inbound tunnel networks on the device. An entry shall be placed in the storage table for each inbound tunnel network.
SEQUENCE OF AttInbTunNetEntry
.1.3.6.1.4.1.74.1.30.14.2
attInbTunNetEntryA (conceptual) entry for one logical inbound tunnel network area on the host.
AttInbTunNetEntry
.1.3.6.1.4.1.74.1.30.14.2.1
inbTunNetIndexA unique value for each logical inbound tunnel's network contained by the device.
Integer32
.1.3.6.1.4.1.74.1.30.14.2.1.1
inbTunNetNetworkThis inbound tunnel network.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.2.1.2
inbTunNetTimeEstablishedTime this inbound tunnel network was established.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.2.1.3
inbTunNetNegIkePhase2LifetThis inbound tunnel network's negotiated IKE Phase 2 lifetime.ro
TimeTicks (SNMPv2-SMI)
.1.3.6.1.4.1.74.1.30.14.2.1.4
inbTunNetEspAlgorithmThis inbound tunnel network's ESP algorithm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.2.1.5
inbTunNetCompressionIs compression negotiated for this inbound tunnel?ro
Enumeration
.1.3.6.1.4.1.74.1.30.14.2.1.6
inbTunNetClientTransAddrShows what inbound tunnel this network belongs to. Corresponds to inbTunClientTransAddr in attInbTunEntry.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.74.1.30.14.2.1.7
ATT-VPN-GATEWAY-MIB - SNMP MIB Reference | MIBs Explorer