Both modules can be operated side by side: the older devices over SNMP v1 and v2,
the ones switched to v3 over SNMPv3. In both cases a connected
gateway is required.
The wizard shows four steps for both; only the middle part differs from the
standard path in Creating a Scan Job.
Entering the targets
The Targets step carries a table with one row per target. The columns are almost the same for both modules:
Into the target column may go a single address, a range, a network in CIDR
notation (e.g. /24) or a hostname. A whole network therefore fits into one row.
The column is called Credentials with both modules, even though with
SNMP v1 and v2 a community stands in it and no account. The entry in the
Credentials for all targets field above the table applies to all rows without
their own assignment. With SNMP v1 and v2 the cell per row stays a picker with free
text – so a community can be typed straight into the row.
The access data
An entry of the type SNMP v1 and v2 carries a single field: the Community. An entry of the type SNMPv3 carries Username, Authentication Algorithm (None, MD5 or SHA-1), Authentication Password, Encryption Algorithm (None, AES, AES-128, AES-192, AES-256, DES or TDES), Encryption Password and Context Name.If the authentication stands at None, the encryption jumps back to None
automatically: encryption without authentication does not exist in SNMPv3 and
cannot be created here either.