Once opAddress is installed use this guide to complete the initial setup / configuration. Return to this guide to extend the configuration to meet your changing needs.
Basic setup - Step-by-step guide
- Update configuration file so IP addresses are automatically added and scanned rather than just added
- Rename the organisational structure parts (this is not required for the system to work but if you do not want "default" as the Organisation name, Network Domain name and Security Zone name then you should rename them now as updates are not easy later)
- Add integration to NMIS so we can import NMIS data
- Add integration to OAE so we import OAE data
- Check your imports and subnet scans to check if things are working as expected
To understand the terms and concepts above please refer to opAddress Concepts page. You should also get an understanding of how opAddress gathers information from How opAddress discovers information
Advanced configuration and tuning topics
- Adjusting the schedules in cron for Subnet Scanning and NMIS/OAE imports
Update opCommon.nmis to recommended default for operating with NMIS and OAE imports.
opAddress automatically creates address entries, inferred from the subnets it knows of. When opAddress FIRST creates the address entry it will give it an "admin status" this defaults to an "admin status" of "unknown" which is a very safe option but not so useful if we want the IP address to be scanned and reported on in a useful way. We recommend in most instances to change the default "admin status" on creation to "allocated" or "unallocated".
To change the default address status, edit the following opCommon.nmis (using vi or nano etc).
Change:
'opaddress_default_address_state' => undef,
To:
'opaddress_default_address_state' => "allocated", # or "unallocated"
Related articles