Offline Configuration Spreadsheet Template

To generate a spreadsheet template, you select an existing offline config from the Offline Config page and the OCSDM takes all of the headers and bind variables from this offline configuration and puts them into the generated template.

Note:

If the offline configuration from which you generated your template is changed after you have created your spreadsheet, you must regenerate the template. Anytime a change is made to an offline configuration, the OCSDM performs validation checks on all associated spreadsheets and marks any spreadsheets invalid that fail.

When you generate a template, the OCSDM automatically names the file using the following format:

OfflineConfigName_<SoftwareVersion>_<Platform>_<Timestamp>

You can change the template name when you save the file.

When you generate a template, the spreadsheet's top two rows are filled in automatically, with the first row containing the details of the Software, platform, and schema of the offline configuration in the following format:

Offline Config, <Offline Config Name>, Software version, <Software version of the Offline Config>, Platform, <Platform of the Offline Config>, Schema name <Schema name of the offline config>

The second row's header fields are generated depending on whether this is a SNMP v1v2 device or a SNMPv3 device. The following header rows appear in the second row, separated by commas, for an SNMPv1v2 device:

Header	Description	Required?
Device name	The name of the device to be added.	Yes
Primary IP address	The primary IP address of the device; this value must be a valid IP address.	Yes
Secondary IP address	The secondary IP address of the device; this value must be a valid IP address.	No
Username	The username for accessing the device.	Yes
Password	The password for accessing the device.	Yes
SNMP Port	The port for SNMP access; this must be a valid port and must be a numeric value.	Yes
SNMP Community Name	The SNMP community name present on the device; this must be a valid SNMP community and must contain a valid SDM IP address.	Yes
2FA Status	Provide if 2FA is enabled/disabled value.	Yes - for a 2FA device No - for a non 2FA device
KeyFile name	Path to private KeyFile for connecting to SBC. This path can be any path in server where SDM is running and is accessible by nncentral user. Applicable only when 2FA status is enabled. For more information on how to upload the private KeyFile, see Importing Key Files	No. Do not be use while adding a non-2FA device or when the 2FA status is disabled or blank.
Passphrase	An alphanumeric value which can be used to decrypt the uploaded private key file. SDM automatically uploads the keyfile that was mentioned in the path described in the OC template.	No. Applicable only when 2FA status is enabled.
Synchronized mode	Indicates if the device is powered by the original offline configuration; this may be `true` or `false`.	No; the OCSDM uses the value configured at the cluster level
Bind variable ..<n> Name	Corresponds to the bind variables for the selected offline configuration; this value must be of the same type.	No

The following header rows appear in the second row, separated by commas, for an SNMP v3 device:

Header	Description	Required?
Device name	The name of the device to be added.	Yes
Primary IP address	The primary IP address of the device; this value must be a valid IP address.	Yes
Secondary IP address	The secondary IP address of the device; this value must be a valid IP address.	No
Username	The username for accessing the device.	Yes
Password	The password for accessing the device.	Yes
SNMP Port	The port for SNMP access; this must be a valid port and must be a numeric value.	Yes
SNMPv3 username	The SNMPv3 username.	Yes
SNMPv3 Authentication protocol	SNMPv3 authentication protocol: HMAC384SHA5126 HMAC192SHA2256 NONE	Yes
SNMPv3 Authentication password	The SNMPv3 authentication password.	No
SNMPv3 privacy protocol	The SNMPv3 privacy protocol: NONE AES128	Yes
SNMPv3 privacy password	The SNMPv3 privacy password	No
Synchronized mode	Indicates if the device is powered by the original offline configuration; this may be `true` or `false`.	No; the OCSDM uses the value configured at the cluster level
Bind variable ..<n> Name	Corresponds to the bind variable for the offline configuration; this value must be of the same type.	No