MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 10 (transmission). 95 (l2tp). 1 (l2tpObjects). 2 (l2tpDomainConfigTable). 1 (l2tpDomainConfigEntry). 1 (l2tpDomainConfigId)
OID : 1.3.6.1.2.1.10.95.1.2.1.1
TXT : iso. org. dod. internet. mgmt. mib-2. transmission. l2tp. l2tpObjects. l2tpDomainConfigTable. l2tpDomainConfigEntry. l2tpDomainConfigId
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.10.95.1.2.1.1
Module L2TP-MIB (ietf)
Noml2tpDomainConfigId
Accesnoaccess
Statuscurrent
DescriptionThe identifier, usually in the form of a Domain Name (full or partial), describing a single tunnel endpoint or a domain of tunnel endpoints. This is typically used as a 'handle' to identify the tunnel configuration requirements for both incoming and outgoing tunnel connection attempts. Both the LAC and LNS could use information provided in the Host Name AVP attribute however the tunnel initiator could use other means not specified to identify the domain's tunnel configuration requirements. For example; three rows in this table have l2tpDomainConfigId values of 'lac1.isp.com', 'isp.com' and 'com'. A tunnel endpoint then identifies itself as 'lac1.isp.com' which would match the 'lac1.isp.com' entry in this table. A second tunnel endpoint then identifies itself as 'lac2.isp.com'. This endpoint is then associated with the 'isp.com' entry of this table.
SyntaxeOctetString (1...80)