...
Run the
setuporserver configurecommand after establishing a connection to the server using SSH or the hypervisor consoleUse Cloud-Init
...
Configuring Network Settings for NetMRI Deployment
With the help of the CLI and Cloud-Init, you can set up the IPv4 and/or IPv6 address, Netmask/prefix, IPv4 and/or IPv6 gateway, DNS servers, DNS domain names, NTP server, time zone, server name, and database name using the CLI and Cloud-Init.
Refer to the Configure Configuring Server CommandsOptions for more details.
The NetMRI image is initially released with one pre-installed network interface, but additional interfaces can be added for scanning purposes or HA. If a server has two connected network adapters, the SCAN interface can be configured during the initial setup. However, please note that subinterfaces cannot be configured through this method.
...
Configuring SCAN Interfaces for DHCP
If The SCAN interfaces will not receive an IP address during initial setup because the DHCP client is only enabled for the MGMT interface, the SCAN interfaces won't receive an IP address automatically during the initial setup. In such cases, you 'll will need to manually determine the IP address assigned by the DHCP server. For AWS or OpenStack, you can check this in the instance description, network section, or ENI description. Please note that NetMRI currently does not support DHCP clients for the SCAN interface.
Setting Up Server Command
Configuring without Scan SCAN Interface
| Code Block |
|---|
NetMRI-VM-UNKNOWN-PLATFORM> setup
Checking NetMRI status... OK.
This option allows you to configure system settings such as IP address,
subnet mask, default gateway, and DNS servers.
Do you want to start system setup now? (y/n) [n]: y
Default values, when available, are given within [].
You may clear defaults by typing a SPACE and pressing Enter.
+++ Configuring Network Identification Settings
Database Name is a descriptive name for this deployment. It is used in reports titles, headers, etc.
Recommended: Begin name with uppercase letter.
Database Name []: NetMRI
+++ Configuring Management Port Settings
You must configure an IPv4 address/mask on the management port.
Optionally you can configure an IPv6 address/prefix on the management port.
NetMRI can perform analysis from the management port or a separate scan port.
IPv4 Address (required) [172.19.14.244]:
IPv4 Subnet Mask (required) [255.255.255.0]:
IPv4 Default Gateway (required) [172.19.14.1]:
IPv6 Address (optional) []: fde0:44f3:fc37:c999::22
IPv6 Prefix (required) []: 64
IPv6 Default Gateway (required) []: fde0:44f3:fc37:c999::1
Configuring DNS Servers for MGMT interface...
DNS Servers are used to map hostnames to IP addresses.
You may enter up to 2 servers below.
NOTE: The DNS settings configured for the MGMT interface will also be configured globally,
NOTE: the DNS servers for each interface will handle DNS queries only if the domain name
NOTE: in the query matches the domain name configured for that interface, otherwise
NOTE: the global DNS servers will be used.
DNS Server 1 (reqired) [10.120.3.10]:
DNS Server 2 (optional) [10.103.3.10]: fde0:44f3:fc37:c999::1
Domain Names are used to truncate device names in NetMRI tables and reports,
additionally they are used to specify which DNS server will be used for resolving.
Recommended: specify local domain name(s).
Domain Name 1 (e.g., example.com) [inca.infoblox.com]:
Domain Name 2 (optional) [infoblox.com]:
Domain Name 3 (optional) []:
Time Servers are used to synchronize time with reliable time sources.
Recommended: use a local ntp server if available.
Time Server [us.pool.ntp.org]: ntp-01.inca.infoblox.com
Time Zone Regions
Choose your local region.
0. Africa 1. America 2. Antarctica 3. Asia 4. Atlantic
5. Australia 6. Europe 7. Indian 8. Pacific 9. US
10. GMT-14 11. GMT-13 12. GMT-12 13. GMT-11 14. GMT-10
15. GMT-9 16. GMT-8 17. GMT-7 18. GMT-6 19. GMT-5
20. GMT-4 21. GMT-3 22. GMT-2 23. GMT-1 24. GMT0
25. GMT+1 26. GMT+2 27. GMT+3 28. GMT+4 29. GMT+5
30. GMT+6 31. GMT+7 32. GMT+8 33. GMT+9 34. GMT+10
35. GMT+11 36. GMT+12 37. UTC
Enter choice (0-37) [9]:
Choose a location within your time zone.
0. Alaska 1. Aleutian 2. Arizona 3. Central 4. East-Indiana
5. Eastern 6. Hawaii 7. Indiana-Starke 8. Michigan 9. Mountain
10. Pacific 11. Samoa
Enter choice (0-11) [5]:
The Server Name identifies this system in SNMP and HTTPS server certificates.
The installed HTTPS certificate contains the following subject:
subject=CN = NetMRI-VM-UNKNOWN-PLATFORM, O = NetMRI
Server Name [NetMRI-VM-F4B3-DD7EC]:
Do you want to generate a new HTTPS Certificate? (y/n) [n]: y
Current settings:
Database Name: NetMRI
Server Name: NetMRI-VM-F4B3-DD7EC
Time Server: ntp-01.inca.infoblox.com
Time Region: US
Time Location: Eastern
Mgmt Port IP Address: 172.19.14.244
Mgmt Port Subnet Mask: 255.255.255.0
Mgmt Port IPv6 Address: fde0:44f3:fc37:c999::22
Mgmt Port IPv6 Prefix: 64
Mgmt Port IPv4 Default Gateway: 172.19.14.1
Mgmt Port IPv6 Default Gateway: fde0:44f3:fc37:c999::1
Mgmt Port DNS Server 1: 10.120.3.10
Mgmt Port DNS Server 2: fde0:44f3:fc37:c999::1
Mgmt Port Domain Names: inca.infoblox.com, infoblox.com
Scan Port IP Address:
Scan Port Subnet Mask:
Scan Port IPv6 Address:
Scan Port IPv6 Prefix:
Scan Port IPv4 Default Gateway:
Scan Port IPv6 Default Gateway:
Scan Port DNS Server 1:
Scan Port DNS Server 2:
Edit these settings? (y/n) [n]:
Configure the system with these settings? (y/n) [y]:
Configuring system ...
+++ Setting timezone...
+++ Configuring network...
Checking Network Views... OK.
Creating Network View... OK.
Configuring MGMT port... OK.
+++ Setting up time server settings...
Setting up time server...
Creating time server configuration... OK.
Setting timezone... OK.
Done setting up time server settings.
+++ Enabling NTP client... Done.
+++ Refreshing Server certificates... Done
+++ Updating Server Name... Done
+++ Updating FailOver configuration...
Generating standalone DRBD configuration...
Done generating DRBD configuration.
Failover not configured
+++ Restarting Services … OK |
Configuring with Scan SCAN Interface
| Code Block |
|---|
NetMRI-VM-UNKNOWN-PLATFORM> setup
Checking NetMRI status... OK.
This option allows you to configure system settings such as IP address,
subnet mask, default gateway, and DNS servers.
Do you want to start system setup now? (y/n) [n]: y
Default values, when available, are given within [].
You may clear defaults by typing a SPACE and pressing Enter.
+++ Configuring Network Identification Settings
Database Name is a descriptive name for this deployment. It is used in reports titles, headers, etc.
Recommended: Begin name with uppercase letter.
Database Name []: NetMRI
+++ Configuring Management Port Settings
You must configure an IPv4 address/mask on the management port.
Optionally you can configure an IPv6 address/prefix on the management port.
NetMRI can perform analysis from the management port or a separate scan port.
IPv4 Address (required) [172.19.14.246]:
IPv4 Subnet Mask (required) [255.255.255.0]:
IPv4 Default Gateway (required) [172.19.14.1]:
IPv6 Address (optional) []: fde0:44f3:fc37:c999::22
IPv6 Prefix (required) []: 64
IPv6 Default Gateway (required) []: fde0:44f3:fc37:c999::1
Configuring DNS Servers for MGMT interface...
DNS Servers are used to map hostnames to IP addresses.
You may enter up to 2 servers below.
NOTE: The DNS settings configured for the MGMT interface will also be configured globally,
NOTE: the DNS servers for each interface will handle DNS queries only if the domain name
NOTE: in the query matches the domain name configured for that interface, otherwise
NOTE: the global DNS servers will be used.
DNS Server 1 (reqired) [10.120.3.10]:
DNS Server 2 (optional) [10.103.3.10]: fde0:44f3:fc37:c999::1
Domain Names are used to truncate device names in NetMRI tables and reports,
additionally they are used to specify which DNS server will be used for resolving.
Recommended: specify local domain name(s).
Domain Name 1 (e.g., example.com) [inca.infoblox.com]:
Domain Name 2 (optional) [infoblox.com]:
Domain Name 3 (optional) []:
Do you want to configure the Scan 1 Port? (y/n) [n]: y
+++ Configuring Scan Port Settings
You must configure an IPv4 or IPv6 address/mask on the scan port.
IPv4 Address (optional) []: 192.168.254.246
IPv4 Subnet Mask (required) []: 255.255.255.0
IPv4 Default Gateway (required) []: 192.168.254.1
IPv6 Address (optional) []: fde0:44f3:fc37:c888::22
IPv6 Prefix (required) []: 64
IPv6 Default Gateway (required) []: fde0:44f3:fc37:c888::1
Configuring DNS Servers for SCAN interface...
DNS Servers are used to map hostnames to IP addresses.
You may enter up to 2 servers below.
NOTE: The DNS settings configured for the MGMT interface will also be configured globally,
NOTE: the DNS servers for each interface will handle DNS queries only if the domain name
NOTE: in the query matches the domain name configured for that interface, otherwise
NOTE: the global DNS servers will be used.
DNS Server 1 (optional) []: 192.168.254.1
DNS Server 2 (optional) []: fde0:44f3:fc37:c888::1
Domain Names are used to truncate device names in NetMRI tables and reports,
additionally they are used to specify which DNS server will be used for resolving.
Recommended: specify local domain name(s).
Domain Name 1 (optional) []: qanet.local
Domain Name 2 (optional) []: netmri.local
Domain Name 3 (optional) []:
Time Servers are used to synchronize time with reliable time sources.
Recommended: use a local ntp server if available.
Time Server [us.pool.ntp.org]: ntp-01.inca.infoblox.com
Time Zone Regions
Choose your local region.
0. Africa 1. America 2. Antarctica 3. Asia 4. Atlantic
5. Australia 6. Europe 7. Indian 8. Pacific 9. US
10. GMT-14 11. GMT-13 12. GMT-12 13. GMT-11 14. GMT-10
15. GMT-9 16. GMT-8 17. GMT-7 18. GMT-6 19. GMT-5
20. GMT-4 21. GMT-3 22. GMT-2 23. GMT-1 24. GMT0
25. GMT+1 26. GMT+2 27. GMT+3 28. GMT+4 29. GMT+5
30. GMT+6 31. GMT+7 32. GMT+8 33. GMT+9 34. GMT+10
35. GMT+11 36. GMT+12 37. UTC
Enter choice (0-37) [9]:
Choose a location within your time zone.
0. Alaska 1. Aleutian 2. Arizona 3. Central 4. East-Indiana
5. Eastern 6. Hawaii 7. Indiana-Starke 8. Michigan 9. Mountain
10. Pacific 11. Samoa
Enter choice (0-11) [5]:
The Server Name identifies this system in SNMP and HTTPS server certificates.
The installed HTTPS certificate contains the following subject:
subject=CN = NetMRI-VM-UNKNOWN-PLATFORM, O = NetMRI
Server Name [NetMRI-VM-38E5-2F7CD]:
Do you want to generate a new HTTPS Certificate? (y/n) [n]: y
Current settings:
Database Name: NetMRI
Server Name: NetMRI-VM-38E5-2F7CD
Time Server: ntp-01.inca.infoblox.com
Time Region: US
Time Location: Eastern
Mgmt Port IP Address: 172.19.14.246
Mgmt Port Subnet Mask: 255.255.255.0
Mgmt Port IPv6 Address: fde0:44f3:fc37:c999::22
Mgmt Port IPv6 Prefix: 64
Mgmt Port IPv4 Default Gateway: 172.19.14.1
Mgmt Port IPv6 Default Gateway: fde0:44f3:fc37:c999::1
Mgmt Port DNS Server 1: 10.120.3.10
Mgmt Port DNS Server 2: fde0:44f3:fc37:c999::1
Mgmt Port Domain Names: inca.infoblox.com, infoblox.com
Scan Port IP Address: 192.168.254.246
Scan Port Subnet Mask: 255.255.255.0
Scan Port IPv6 Address: fde0:44f3:fc37:c888::22
Scan Port IPv6 Prefix: 64
Scan Port IPv4 Default Gateway: 192.168.254.1
Scan Port IPv6 Default Gateway: fde0:44f3:fc37:c888::1
Scan Port DNS Server 1: 192.168.254.1
Scan Port DNS Server 2: fde0:44f3:fc37:c888::1
Scan Port Domain Names: qanet.local, netmri.local
Edit these settings? (y/n) [n]:
Configure the system with these settings? (y/n) [y]:
Configuring system ...
+++ Setting timezone...
+++ Configuring network...
Checking Network Views... OK.
Creating Network View... OK.
Configuring Scan port... OK.
Configuring MGMT port... OK.
+++ Setting up time server settings...
Setting up time server...
Creating time server configuration... OK.
Setting timezone... OK.
Done setting up time server settings.
+++ Enabling NTP client... Done.
+++ Refreshing Server certificates... Done
+++ Updating Server Name... Done
+++ Updating FailOver configuration...
Generating standalone DRBD configuration...
Done generating DRBD configuration.
Failover not configured
+++ Restarting Services … OK |
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
Options
If you are configuring server options, complete verify the following:
EnterIPv4 Address - public or private* IPv4 address
* It should be noted that IP addresses starting with 169.254.1.0/24 are not permitted.EnterIPv4 Network mask - IPv4 subnet network
EnterIPv4 Gateway - public or private IPv4 address from the same subnet as IPv4 Address
EnterIPv6 Address - public or private IPv6 address
EnterIPv6 Prefix - IPv6 prefix length
EnterIPv6 Gateway - both a public and private IPv6 address from the same subnet
EnterDNS Server - IPv4 or IPv6 address
EnterDNS Domain Name - Allows up to 253 symbols (including the server’s name), case-sensitive alphabetic letters, numbers, hyphens (-), and dots (.); each label cannot begin or end with a hyphen symbol
EnterServer Name - Allows up to 63 symbols, including case-sensitive insensitive alphabet letters, numbers, and hyphens (-)
EnterNTP Server - IPv4 or IPv6 address or domain name
EnterTime Zone - If one Allow any of the suggested CLI configurations was allowed, then to support any TZ listed in the IANA database (version 2023c) was supported by with cloud-init
EnterDatabase Name - CaseAllow case-sensitive insensitive alphabetic characters, digits, dots, hyphens, underscores, and spaces are permitted; however, they are not allowed , but do not permit them to end with spaces ( )
Note: It is not possible to configure the same IP address for each interface.
...
Upon the initial launch, NetMRI will attempt to acquire an IP address for the MGMT interface from the DHCP server if it 's is accessible within the network. If DHCP is not available, you can use the default 169.254.1.1 IP address for the initial connection and initial setup. Please note that the 169.254.1.1 IPv4 address is preconfigured as an additional MGMT IP and is not editable.
To connect locally, you can configure any IP within the 169.254.1.0/24 range on your device, such as a Windows or Linux machine, provided that the NIC is within the same broadcast domain as NetMRI. Furthermore, connecting through this IP address or via the hypervisor console is necessary if you intend to change the MGMT IP address through CLI. Failure to do so may result in an SSH connection drop while new settings are applied, potentially causing some settings to be missed.