HM2-VPN-MIB
This MIB defines the SNMP interface for Hirschmann VPN implementations.
Main OID:
hm2VpnMib.1.3.6.1.4.1.248.11.120
99
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
99 total| Object Name |
|---|
hm2VpnMibThis MIB defines the SNMP interface for Hirschmann VPN implementations. MODULE-IDENTITY .1.3.6.1.4.1.248.11.120 |
hm2VpnMibNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.0 |
hm2VpnUpTrapA hm2VpnUpTrap trap signals that a VPN connection is about to enter the up state from some other state (see 'hm2VpnConnOperStatus'). NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.120.0.1 |
hm2VpnDownTrapA hm2VpnDownTrap trap signals that a VPN connection is about to enter the down state from some other state (see 'hm2VpnConnOperStatus'). NOTIFICATION-TYPE .1.3.6.1.4.1.248.11.120.0.2 |
hm2VpnMibObjects OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.1 |
hm2VpnGeneralGroup OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.1.1 |
hm2VpnConnectionGroup OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.1.2 |
hm2VpnConnMaxMaximum number of VPN connections supported. Notice that the maximum number of active and up VPN connections is limited to hm2VpnConnActiveMax.ro Integer32 .1.3.6.1.4.1.248.11.120.1.2.1 |
hm2VpnConnActiveMaxMaximum number of active (and up) VPN connections supported.ro Integer32 .1.3.6.1.4.1.248.11.120.1.2.2 |
hm2VpnConnNextThis object always holds an appropriate value to be used for hm2VpnConnIndex when creating entries in the hm2VpnConnTable. The value 0 indicates that no unassigned entries are available. To obtain the hm2VpnConnIndex value for a new entry, the management station issues a SNMP retrieval operation to obtain the current value of this object. After each row creation or deletion the agent modifies the value to the next unassigned index.ro Integer32 .1.3.6.1.4.1.248.11.120.1.2.3 |
hm2VpnConnTableA list of VPN connections. SEQUENCE OF Hm2VpnConnEntry .1.3.6.1.4.1.248.11.120.1.2.10 |
hm2VpnConnEntryA VPN connection entry. Hm2VpnConnEntry .1.3.6.1.4.1.248.11.120.1.2.10.1 |
hm2VpnConnIndexAn index that uniquely identifies the entry in the table.ro Integer32 .1.3.6.1.4.1.248.11.120.1.2.10.1.1 |
hm2VpnConnIkeVersionVersion of the IKE protocol: o ike: accept IKEv1/v2 as responder, start with IKEv2 as initiator o ikev1: used protocol is IKE version 1 (ISAKMP) o ikev2: used protocol is IKE version 2rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.2 |
hm2VpnConnIkeStartupIf this host acts as a responder it does not initiate a key exchange (IKE) nor connection parameters negotiation. Otherwise, this host acts as an initiator - then it initiates an IKE actively.rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.3 |
hm2VpnConnIkeLifetimeLifetime of IKE security association in seconds. The maximum value is 24 hours (86400 seconds).rw Integer32 ( 300..86400) .1.3.6.1.4.1.248.11.120.1.2.10.1.4 |
hm2VpnConnIkeDpdTimeoutIf greater than zero, the local peer sends Dead Peer Detection (DPD) messages (according to RFC 3706) to the remote peer. This value specifies the timeout in seconds, the remote peer is declared dead, if not responding. The value 0 disables this feature.rw Integer32 ( 0..86400) -- max. 24 hours .1.3.6.1.4.1.248.11.120.1.2.10.1.5 |
hm2VpnConnIkeLocalAddrHostname (FQDN) or IP address of local security gateway. If the value is 'any', then the IP address of the matching interface is used. Establishing the connection may be delayed until the hostname (if specified) can be resolved.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.6 |
hm2VpnConnIkeRemoteAddrTypically the hostname (FQDN) or IP address of remote security gateway. If this value is 'any', then any IP address is accepted when establishing an IKE-SA as responder. Also a network in CIDR notation, to be accepted when establishing the IKE-SA, is allowed as responder. As initiator such values are not allowed. Establishing the VPN connection may be delayed until the hostname (if specified) can be resolved.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.7 |
hm2VpnConnIkeAuthTypeType of authentication to be used: pre-shared key, individual X509 certificates (separate for CA and local identification) or one PKCS12 container with all the needed certificates (including the CA).rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.8 |
hm2VpnConnIkeAuthModeThe phase 1 exchange mode to be used (IKEv1).rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.9 |
hm2VpnConnIkeAuthCertCAPEM encoded X.509 certificate file name (RFC 1422), if authentication type in 'hm2VpnConnIkeAuthType' is 'individualx509'. This certificate is used for RSA based signature verification in local and remote certificates. The file needs to be uploaded separately.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.10 |
hm2VpnConnIkeAuthCertRemotePEM encoded X.509 certificate file name (RFC 1422), if authentication type in 'hm2VpnConnIkeAuthType' is 'individualx509'. This certificate is used for RSA based authentication of remote peer at the local side. This certificate binds the identity of remote peer to it's public key. It is optional because typically send by the remote peer while negotiating an ISAKMP/IKE security association. The file needs to be uploaded separately.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.11 |
hm2VpnConnIkeAuthCertLocalPEM encoded X.509 certificate file name (RFC 1422) to be used, if authentication type in 'hm2VpnConnIkeAuthType' is 'individualx509' or 'pkcs12'. This certificate is used for authentication of local peer at the remote side. The certificate binds the identity of local peer to it's public key, signed by the certification authority (CA) from 'hm2VpnConnIkeAuthCertCA'. The file needs to be uploaded separately.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.12 |
hm2VpnConnIkeAuthPrivKeyPrivate key file name to be used, if authentication type in 'hm2VpnConnIkeAuthType' is 'individualx509' and the key stored on the device is encrypted with a passphrase (so it cannot automatically be matched with the certificate). Note that this is only the filename of the private key. The passphrase must be added to 'hm2VpnConnIkeAuthPasswd'.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.13 |
hm2VpnConnIkeAuthPasswdPassphrase to be used for decryption of private key from 'hm2VpnConnIkeAuthPrivKey' or the certificate container for 'pkcs12' type certificates which are uploaded encrypted.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.14 |
hm2VpnConnIkeAuthPskPre-shared key (passphrase) to be used if authentication type in 'hm2VpnConnIkeAuthType' is 'psk'. The pre-shared key sequence cannot contain newline or double-quote characters. Alternatively to characters sequence, pre-shared secrets can be represented as hexadecimal or Base64 encoded binary values. A character sequence beginning with 0x is interpreted as sequence hexadecimal digits. Similarly, a character sequence beginning with 0s is interpreted as Base64 encoded binary data.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.15 |
hm2VpnConnIkeAuthLocIdLocal peer identifier to be sent within ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details when using IKEv1 and RFC 4306, section 3.5 for IKEv2). Allowed formats for this object depend on 'hm2VpnConnIkeAuthLocType': o default: don't care o address: don't care, take IPv4 address or host name from hm2VpnConnIkeLocalAddr o id: - IPv4 address or host name - key identifier - fully qualified domain name - fully qualified RFC 822 email address - X.500 distinguished name (DN)rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.16 |
hm2VpnConnIkeAuthLocTypeType of local peer identifier in 'hm2VpnConnIkeAuthLocId': o default: If 'hm2VpnConnIkeAuthType' is 'psk' then use the IP address or host name from 'hm2VpnConnIkeLocalAddr' as local identifier. In case of 'individualx509' or 'pkcs12' use the DN from local certificate in 'hm2VpnConnIkeAuthCertLocal'. o address: use the IP address or DNS name from 'hm2VpnConnIkeLocalAddr' as local identifier. o id: use the configured value in hm2VpnConnIkeAuthLocId (it can be of any type in the description). For further information see RFC 2407, section 4.6.2rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.17 |
hm2VpnConnIkeAuthRemIdRemote peer identifier to be compared with ID payload during negotiation. The ID payload is used to identify the initiator of the security association. The identity is used by the responder to determine the correct host system security policy requirement for the association (see RFC 2407, section 4.6.2 for details when using IKEv1 and RFC 4306, section 3.5 for IKEv2). Allowed formats for this entry depend on 'hm2VpnConnIkeAuthRemType': o any: don't care o address: don't care, take IPv4 address or host name from hm2VpnConnIkeRemoteAddr o id: - IPv4 address or host name - key identifier - fully qualified domain name - fully qualified RFC 822 email address - X.500 distinguished name (DN)rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.18 |
hm2VpnConnIkeAuthRemTypeType of remote peer identifier in hm2VpnConnIkeAuthRemId: o any: received remote identifier is not checked o address: use the IP address or host name from 'hm2VpnConnIkeRemoteAddr' as remote identifier. o id: use the configured value in hm2VpnConnIkeAuthRemId (it can be of any type in the description). For further information see RFC 2407, section 4.6.2rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.19 |
hm2VpnConnIkeAlgDhDiffie-Hellman key agreement algorithm to be used for establishment of IKE-SA: o any: accept all supported algorithms as responder, use default as initiator o modp1024: RSA with 1024 bits modulus (DH Group 2) o modp1536: RSA with 1536 bits modulus (DH Group 5) o modp2048: RSA with 2048 bits modulus (DH Group 14) o modp3072: RSA with 3072 bits modulus (DH Group 15) o modp4096: RSA with 4096 bits modulus (DH Group 16)rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.20 |
hm2VpnConnIkeAlgMacIntegrity (MAC) algorithm to be used in IKEv2: o any: accept all supported algorithms as responder, use various pre-defined as initiator o hmacmd5: HMAC-MD5 (length 96 bit) o hmacsha1: HMAC-SHA1 (length 96 bit) o hmacsha256: HMAC-SHA256 (length 128 bit) o hmacsha384: HMAC-SHA384 (length 196 bit) o hmacsha512: HMAC-SHA512 (length 256 bit)rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.21 |
hm2VpnConnIkeAlgEncrEncryption algorithm to be used in IKE: o any: accept all supported algorithms as responder, use various pre-defined as initiator o des: DES o des3: Triple-DES o aes128: AES with 128 key bits o aes192: AES with 192 key bits o aes256: AES with 256 key bitsrw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.22 |
hm2VpnConnIkeReAuthwhether re-keying of an IKE_SA should also re-authenticate the peer. In IKEv1, re-authentication is always done (also when set to false). In IKEv2, a value of false does re-keying without un-installing the IPsec SAs, a value of true creates a new IKE_SA from scratch and tries to recreate all IPsec SAs.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.248.11.120.1.2.10.1.23 |
hm2VpnConnIpsecModeIPsec encapsulation mode.rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.24 |
hm2VpnConnIpsecLifetimeLifetime of IPsec security association in seconds. The maximum value is 8 hours (28800 seconds).rw Integer32 ( 300..28800) .1.3.6.1.4.1.248.11.120.1.2.10.1.25 |
hm2VpnConnMargintimeHow long before connection expiry or keying-channel expiry should attempts to negotiate a replacement begin. The maximum value is half an hour (1800 seconds). The margin time needs to be at most half of the lifetime.rw Integer32 ( 1..1800) .1.3.6.1.4.1.248.11.120.1.2.10.1.26 |
hm2VpnConnIpsecAlgDhDiffie-Hellman key agreement algorithm to be used for IPsec-SA session key establishment: o any: accept all supported algorithms as responder, use various pre-defined as initiator o modp1024: RSA with 1024 bits modulus (DH Group 2) o modp1536: RSA with 1536 bits modulus (DH Group 5) o modp2048: RSA with 2048 bits modulus (DH Group 14) o modp3072: RSA with 3072 bits modulus (DH Group 15) o modp4096: RSA with 4096 bits modulus (DH Group 16) o none: no Perfect Forward Secrecy (PFS)rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.27 |
hm2VpnConnIpsecAlgMacIntegrity (MAC) algorithm to be used in IPsec: o any: accept all supported algorithms as responder, use various pre-defined as initiator o hmacmd5: HMAC-MD5 (length 96 bit) o hmacsha1: HMAC-SHA1 (length 96 bit) o hmacsha256: HMAC-SHA256 (length 128 bit) o hmacsha384: HMAC-SHA384 (length 196 bit) o hmacsha512: HMAC-SHA512 (length 256 bit)rw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.28 |
hm2VpnConnIpsecAlgEncrEncryption algorithm to be used for payload encryption in IPsec: o any: accept all supported algorithms as responder, use various pre-defined as initiator o des: DES o des3: Triple-DES o aes128: AES-CBC with 128 key bits o aes192: AES-CBC with 192 key bits o aes256: AES-CBC with 256 key bits o aes128ctr: AES-COUNTER with 128 key bits o aes192ctr: AES-COUNTER with 192 key bits o aes256ctr: AES-COUNTER with 256 key bits o aes128gcm64: AES-GCM with 64 bit ICV with 128 key bits o aes128gcm96: AES-GCM with 96 bit ICV with 128 key bits o aes128gcm128: AES-GCM with 128 bit ICV with 128 key bits o aes192gcm64: AES-GCM with 64 bit ICV with 192 key bits o aes192gcm96: AES-GCM with 96 bit ICV with 192 key bits o aes192gcm128: AES-GCM with 128 bit ICV with 192 key bits o aes256gcm64: AES-GCM with 64 bit ICV with 256 key bits o aes256gcm96: AES-GCM with 96 bit ICV with 256 key bits o aes256gcm128: AES-GCM with 128 bit ICV with 256 key bitsrw Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.29 |
hm2VpnConnOperStatusThe current operational status of the VPN connection: o 'up': the IKE-SA and all IPsec SAs are up; o 'down': the IKE-SA and all IPsec SAs are down; o 'negotiation': key exchange and algorithm negotiation is in progress (or, as responder, waiting to be contacted for that purpose); o 'constructing': the IKE-SA is up, but at least one IPsec-SA is not established so far; o 'dormant': waiting for a precondition to be fulfilled before connection setup, e.g.: - a dynamically assigned IP address; - successful hostname resolution; - assignment of a valid system time. o 're-keying': key exchange is in progress after timeout of lifetime has occured, either IKE or IPSEC;ro Enumeration .1.3.6.1.4.1.248.11.120.1.2.10.1.30 |
hm2VpnConnDescUser defined text.rw DisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.31 |
hm2VpnConnLastErrorLast error notification occurred for this connection. This is useful if the connection does not reach the up state to see if an error has occurred in the proposal exchange or when establishing the tunnel. In most cases this variable should be empty.ro HmLargeDisplayString .1.3.6.1.4.1.248.11.120.1.2.10.1.32 |
hm2VpnConnDebugUsed for debugging purpose of the VPN connections. May affect the performance significant. Please handle with care. If the bit is set informational(0) messages, unhandled(1) messages (not handled by the stack) are logged to the event logrw Bits .1.3.6.1.4.1.248.11.120.1.2.10.1.33 |
hm2VpnConnRowStatusThe row status of this table entry. If the row status is 'active' then it is not allowed to change any value (this applies also to active traffic selectors). The maximum number of active VPN connections is limited to hm2VpnConnMax. The maximum number of active and up VPN connections is limited to hm2VpnConnActiveMax.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.120.1.2.10.1.34 |
hm2VpnConnInfoTableA list of VPN connections. SEQUENCE OF Hm2VpnConnInfoEntry .1.3.6.1.4.1.248.11.120.1.2.15 |
hm2VpnConnInfoEntryA VPN connection entry. Hm2VpnConnInfoEntry .1.3.6.1.4.1.248.11.120.1.2.15.1 |
hm2VpnConnInfoIkeVersionUsedVersion of the IKE protocol used by connection: o ikev1: used protocol is IKE version 1 (ISAKMP) o ikev2: used protocol is IKE version 2ro Enumeration .1.3.6.1.4.1.248.11.120.1.2.15.1.1 |
hm2VpnConnInfoIkeProposalAlgorithms the IKE use for key exchange.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.2 |
hm2VpnConnInfoIpsecProposalAlgorithms IPsec use for the data communication.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.3 |
hm2VpnConnInfoLocalHostLocal host detected by IKE.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.4 |
hm2VpnConnInfoRemoteHostRemote host detected by IKE.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.5 |
hm2VpnConnInfoEstablishedTime in seconds since the connection has been established (is updated after IKE re-authentication).ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.6 |
hm2VpnConnInfoIKEReauthTime in seconds when the next IKE re-authentication will take place.ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.7 |
hm2VpnConnInfoIKERekeyingTime in seconds when the next IKE re-keying will take place.ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.8 |
hm2VpnConnInfoIpsecRekeyingTime in seconds when the next IPsec re-keying will take place.ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.9 |
hm2VpnConnInfoIpsecInBytesNumber of input Bytes from this IPsec tunnel.ro Counter64 .1.3.6.1.4.1.248.11.120.1.2.15.1.10 |
hm2VpnConnInfoIpsecInPacketsNumber of input packets from this IPsec tunnel.ro Counter64 .1.3.6.1.4.1.248.11.120.1.2.15.1.11 |
hm2VpnConnInfoIpsecInUseTime in seconds since the IPsec tunnel has received last time data.ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.12 |
hm2VpnConnInfoIpsecOutBytesNumber of output Bytes to this IPsec tunnel.ro Counter64 .1.3.6.1.4.1.248.11.120.1.2.15.1.13 |
hm2VpnConnInfoIpsecOutPacketsNumber of output packets to this IPsec tunnel.ro Counter64 .1.3.6.1.4.1.248.11.120.1.2.15.1.14 |
hm2VpnConnInfoIpsecOutUseTime in seconds since to the IPsec tunnel has sent last time data.ro Unsigned32 .1.3.6.1.4.1.248.11.120.1.2.15.1.15 |
hm2VpnConnInfoIKEInitiatorSPIThe IKE initiator SPI (local or remote, depends on initiator settings).ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.16 |
hm2VpnConnInfoIKEResponderSPIThe IKE responder SPI (local or remote, depends on initiator settings).ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.17 |
hm2VpnConnInfoIpsecInSPIThe input IPsec SPI.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.18 |
hm2VpnConnInfoIpsecOutSPIThe output IPsec SPI.ro DisplayString .1.3.6.1.4.1.248.11.120.1.2.15.1.19 |
hm2VpnTrafficSelGroup OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.1.3 |
hm2VpnTrafficSelTableA list of traffic selectors. For details on the role of traffic selectors in IPsec protocol see RFC 2409, section 5.5 and RFC 4306, section 2.9. SEQUENCE OF Hm2VpnTrafficSelEntry .1.3.6.1.4.1.248.11.120.1.3.1 |
hm2VpnTrafficSelEntryA traffic selector entry. A traffic selector defines the subnet/host addresses for which this IPSec connection (SA) is responsible. Hm2VpnTrafficSelEntry .1.3.6.1.4.1.248.11.120.1.3.1.1 |
hm2VpnTrafficSelIndexAn index that (together with the connection index hm2VpnConnIndex) identifies the entry in the traffic selector table. This index can be choosen freely, but must be greater than 0. Integer32 .1.3.6.1.4.1.248.11.120.1.3.1.1.1 |
hm2VpnTrafficSelSrcAddrHost or subnet address in CIDR notation (a.b.c.d/n) for which this traffic descriptor (and the associated VPN connection) is responsible. This address is compared to the source address of IP packets sent, when determining the associated IPsec and IKE-SA. The special keyword 'any' means that the address comparison always matches.rw DisplayString .1.3.6.1.4.1.248.11.120.1.3.1.1.2 |
hm2VpnTrafficSelDstAddrHost or subnet address in CIDR notation (a.b.c.d/n) for which this traffic descriptor (and the associated VPN connection) is responsible. This address is compared to the destination address of IP packets sent, when determining the associated IPsec and IKE-SA. The special keyword 'any' means that the address comparison always matches.rw DisplayString .1.3.6.1.4.1.248.11.120.1.3.1.1.3 |
hm2VpnTrafficSelSrcRestThe optional source restrictions (names or numbers) <protocol/port>, e.g. tcp/http which is equal to 6/80, or udp which is equal to udp/any or /53 which is equal to any/53rw DisplayString .1.3.6.1.4.1.248.11.120.1.3.1.1.4 |
hm2VpnTrafficSelDstRestThe optional destination restrictions (names or numbers) <protocol/port>, e.g. tcp/http which is equal to 6/80, or udp which is equal to udp/any or /53 which is equal to any/53rw DisplayString .1.3.6.1.4.1.248.11.120.1.3.1.1.5 |
hm2VpnTrafficSelDescUser defined text.rw DisplayString .1.3.6.1.4.1.248.11.120.1.3.1.1.6 |
hm2VpnTrafficSelRowStatusThe row status of this table entry. Only traffic selector entries with an 'active' row status will be considered if the connections row status is set 'active'. Independent of that dependency any value in this entry can be changed only if the row status is not 'active'.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.248.11.120.1.3.1.1.7 |
hm2VpnCertificateGroup OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.1.4 |
hm2VpnCertificateUploadPassphraseSetting the correct passphrase here before uploading an encrypted private key or an encrypted PKCS12 container will trigger the decryption of the uploaded file before storing on the device. The value cannot be read and is not stored after the file transfer. WARNING: the file is stored unencrypted on the device. Use with care!rw DisplayString .1.3.6.1.4.1.248.11.120.1.4.1 |
hm2VpnCertificateTableThe list of certificates available on the device. SEQUENCE OF Hm2VpnCertificateEntry .1.3.6.1.4.1.248.11.120.1.4.10 |
hm2VpnCertificateEntryA certificate file entry. A certificate file which has been copied to the device and can be used for VPN connections. Hm2VpnCertificateEntry .1.3.6.1.4.1.248.11.120.1.4.10.1 |
hm2VpnCertificateIndexIndex of the entry. Integer32 .1.3.6.1.4.1.248.11.120.1.4.10.1.1 |
hm2VpnCertificateSubjectSubject field of certificate.ro DisplayString .1.3.6.1.4.1.248.11.120.1.4.10.1.2 |
hm2VpnCertificateIssuerCertificate issuer.ro DisplayString .1.3.6.1.4.1.248.11.120.1.4.10.1.3 |
hm2VpnCertificateStartDateTime and date when certificate is begining to be valid.ro HmTimeSeconds1970 (HM2-TC-MIB) .1.3.6.1.4.1.248.11.120.1.4.10.1.4 |
hm2VpnCertificateEndDateTime and date when certificate will expire.ro HmTimeSeconds1970 (HM2-TC-MIB) .1.3.6.1.4.1.248.11.120.1.4.10.1.5 |
hm2VpnCertificateFileNameName of the file consisting of alphanumeric characters plus hyphen, underscore and dot.ro DisplayString .1.3.6.1.4.1.248.11.120.1.4.10.1.6 |
hm2VpnCertificateTypeType of the container file used.ro Enumeration .1.3.6.1.4.1.248.11.120.1.4.10.1.7 |
hm2VpnCertificateCertUploadDateTime and date of last write access using the content of the variable hm2SystemTime.ro HmTimeSeconds1970 (HM2-TC-MIB) .1.3.6.1.4.1.248.11.120.1.4.10.1.8 |
hm2VpnCertificatePrivateKeyStatusShows if a Peer certificate has a private key uploaded on the device. A Peer certificate cannot be used without a private key uploaded to the device. Does not apply to CA certificates.ro Enumeration .1.3.6.1.4.1.248.11.120.1.4.10.1.9 |
hm2VpnCertificatePrivateKeyFileName of the file consisting of alphanumeric characters plus hyphen, underscore and dot.ro DisplayString .1.3.6.1.4.1.248.11.120.1.4.10.1.10 |
hm2VpnCertificateNoConnectionsNumber of active connections that use this certificate. The certificate cannot be deleted from the device unless there are no active connections using it (this field is set to 0).ro Integer32 .1.3.6.1.4.1.248.11.120.1.4.10.1.11 |
hm2VpnCertificateUserActionsProvides a way to delete unused certificate files from the device. A certificate can only be deleted if there are no active connections using it (see hm2VpnCertificateNoConnections). Deleting a Peer certificate automatically deletes the private key asociated with it (if any).rw Enumeration .1.3.6.1.4.1.248.11.120.1.4.10.1.12 |
hm2VpnMibSNMPExtensionGroup OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3 |
hm2VpnMibSNMPExtensionNoTrafficSelectorIndicates that for a VPN connection no active traffic selectors are available. OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3.1 |
hm2VpnMibSNMPExtensionTooManyActiveIndicates that too many VPN connections are in active state. OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3.2 |
hm2VpnMibSNMPExtensionTooManyConnsIndicates that too many VPN connections shall be added to the configuration. OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3.3 |
hm2VpnMibSNMPExtensionActiveRowIndicates that an active row shall be changed. OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3.4 |
hm2VpnMibSNMPExtensionInitiatorAnyIndicates that for a VPN connection as initiator the remote end point is set to any. OBJECT IDENTIFIER .1.3.6.1.4.1.248.11.120.3.5 |