I am kinda over-due to take a look at this stuff on Cisco.Greetings would like to provide you a way so that you can emulate Cisco switches (L2 as well as 元) and the most important, it's a 100% free solution! Just follow the following steps: I don't know if Cisco supports any crypto we don't support - OCI doesn't support AES 192 or 256 because Java doesn't, out of the box. It may be worth looking if any policies have been enabled on the switch to force certain levels of auth or encryption - if these have been set, but your user was not create in compliance with them, your user may be functionally unusable (i.e, no encryption password defined, but the switch only allows SNMPv3 usage with AES128). I unfortunately don't have much for notes on SNMP v3 on Cisco. Snmpwalk.bat 1.2.3.4 -v3 -sn extreme -ua authpasswordhere -sha -privpc AES128 -privp privpasswordhere Set SNMP Privacy Password to privpasswordhere And separate authentication passwords and encryption passwords could be required. Would be a way of testing such a config for user "ostiguy"Īt the opposite extreme, authentication and encryption could be required. You can configure a switch where no authentication or encryption (privacy) is required - in which case, from an OCI perspective, you simply need to: SNMP Privacy Password - only relevant for v3 configs SNMP Privacy Protocol - only relevant for v3 configs DES | TRIPLEDES | AES | NONE SNMP Auth Protocol - only relevant for v3 configs. It it MAY be functionally mandatory for snmp v3 configs, depending on how your device (in this case, a Cisco MDS switch) is configured Password - this field is optional, as it is irrelevant for anything *but* SNMP v3 configs. It is functionally mandatory for snmp v3 configs User name - this field is optional, as it is irrelevant for anything *but* SNMP v3 configs. So, you need to populate it with something, but the value is not used in v3 configs SNMP community string - this field is the datasource is mandatory, but irrelevant for SNMP v3 configs. So, the good news I can offer you is that the reply back, or error you are seeing in the OCI datasource is a pretty good sign that there is no firewall between OCI and the device in question, so I think we can probably eliminate that as a possibility.Īdmittedly, our terminology for SNMP is somewhat cryptic
0 kommentar(er)
