To address this issue and prevent the
AuthTypeMismatch error, you must make sure both of the OSPF endpoints have the same
AuthType value configured. The AuthType value can be configured to one of the following:
The following sections explain how to determine the current AuthType attribute value configured for an OSPF endpoint, using either the Smarts console or the SNMP walk of the OSPF device objects.
In the Smarts ConsoleTo determine the current AuthType attribute value configured for an OSPF endpoint using the Smarts console, do the following:
- Navigate to the Smarts NPM domain in question.
- Open the OSPFInterface object and select the OSPF relationship in question
- In the attribute window to the right, select AuthType.
- The Value field displays the AuthType configured for the selected OSPF interface. The following screenshot shows an OSPF interface configured to use the MD5 AuthType:
In the SNMP walkTo determine the current AuthType attribute value configured for an OSPF endpoint in the SNMP walk of the devices, check the
ospfIfAuthType OID (1.3.6.1.2.1.14.7.1.20) and compare the
OspfAuthenticationType setting for the two OSPF endpoints:
Object | ospfIfAuthType |
OID | 1.3.6.1.2.1.14.7.1.20 |
Type | OspfAuthenticationType 0:none 1:simplePassword 2:md5 |
Permission | read-create |
Status | current |
MIB | OSPF-MIB ; - View Supporting Images |
Description | "The authentication type specified for an interface. Note that this object can be used to engage in significant attacks against an OSPF router." |