Netbox Extended Connector

Oomnitza's Netbox Extended Connector allows organizations to pull device information from Netbox and populate it in Oomnitza. More info in Netbox can be found here: https://netbox.readthedocs.io/

NetBox

Authentication

Netbox uses an API token for authentication, and requires Read Only access to devices in Netbox. When creating a Netbox Credential on Oomnitza the fields should be filled out as follows:

Authorization type: API Key
Token Name: Authorization
API Key:  Token <your API token>
Add to: Header

mceclip1.png

More information on Netbox's REST API can be found here: https://netbox.readthedocs.io/en/stable/rest-api/authentication/#rest-api-authentication 

Setup

Details on setting up Oomnitza Extended Connectors can be found in Oomnitza's Articles on Connector Setup. In addition to the standard fields required, your Netbox URL needs to be specified while setting up the connection.

mceclip0.png

Standard Mappings

The following fields can be mapped from Netbox using Oomnitza's User Interface. For more information on creating Extended Connector Mappings, please see our article on Mapping Extended Connectors.

  • Asset Tag
  • Changed at
  • Cluster
  • Comments
  • Created at
  • Device Role
  • Face
  • Manufacturer
  • Model
  • Name
  • Platform
  • Position # in rack
  • Primary IP
  • Primary IPv4
  • Primary IPv6
  • Rack
  • Serial Number
  • Site
  • Status
  • Tenant

Custom Mappings

Additional fields may be available through Netbox. For details on how to retrieve them, please reach out to support@oomnitza.com or see our article on Mapping Extended Connectors.

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk