Defining Network Discovery Observer jobs
You use the Network Discovery Observer to retrieve network topology data from the Network Discovery database via REST API and use this data to create topologies within the topology service.
Before you begin
The Network Discovery Services are installed as part of the core installation procedure. This includes the Network Discovery Observer, Network Discovery Collector and Network Discovery Engine, which have been installed and should be running, as well as the required scripts to manage jobs.
Before you configure a network discovery job, you must configure the discovery details. This procedure is described here: Configuring the network discovery services
When successful, the configuration details will be saved in topology management artifacts.
All observers have scripts to start and stop all available jobs, to list the status of a current job, to set its logging levels, and to configure its job parameters.
- For size0
- 10,000 entities
- For size01
- 1,000,000 entities
- Use the following command to verify that the docker containers are
running:
The system should return output indicating that the following containers have a state of Up and therefore are running:ASM_HOME/bin/docker-compose ps
asm_netdisco-observer_1 sh -c /opt/ibm/$APPNAME/st Up 9152/tcp, 9153/tcp nasm-net-disco-collector ./entrypoint.sh Up 8443/tcp, 8445/tcp nasm-net-disco-config ./entrypoint.sh Up 8443/tcp nasm-net-disco-consul /etc/init.sh agent -server Up 0.0.0.0:8501->8501/tcp nasm-net-disco-control ./entrypoint.sh Up 8443/tcp nasm-net-disco-schema- /etc/init.sh Up 8081/tcp, nasm-net-disco-security ./entrypoint.sh Up 8443/tcp nasm-net-disco-sftp ./entrypoint.sh Up 0.0.0.0:9022->9022/tcp nasm-net-disco-sidecar ./entrypoint.sh Up 0.0.0.0:8765->8443/tcp nasm-net-disco-status ./entrypoint.sh Up 8443/tcp nasm-net-disco-swagger- /etc/init.sh Up 8443/tcp, nasm-net-disco-swagger-ui /etc/init.sh Up 8443/tcp nasm-net-disco-topogram ./entrypoint.sh Up 8443/tcp nasm-net-disco-worker /bin/sh -c /opt/$SERVICE_N Up
- Check the status of the storage and discovery services. The status of the network discovery
services can be checked in the Consul UI on port 8501, for
example:
https://localhost:8501/ui/nasm_net_disco/services
- Workaround
-
- Verify via consul that the nasm-net-disco-schema-registry has failed its
healthcheck:
https://localhost:8501/ui/nasm_net_disco/services
- Restart the nasm-net-disco-schema-registry:
docker restart nasm-net-disco-schema-registry
- Wait until all Agile Service Manager services have registered with consul, and only then run the network discovery.
- Verify via consul that the nasm-net-disco-schema-registry has failed its
healthcheck:
For information about changing the values in the crio.conf file using Machine Configs, see Creating a ContainerRuntimeConfig CR to edit CRI-O parameters
For reference information about Machine Configs, see Red Hat Enterprise Linux CoreOS (RHCOS)
About this task
- Configure the discovery process
- Configure Network Discovery details (upon success, configuration details will be saved in the topology).
- Configure the full load job
- Triggers Network Discovery
The Network Discovery Observer receives network data from the network services. Once the discovery configuration has successfully been sent to the topology management artifact and Network Discovery engine, you can run a full load job to discover Network Discovery data.
Procedure
To edit the parameters in the configuration file
Results
What to do next
- netdisco_observer_load_stop.sh
- Stops the load job
- netdisco_observer_job_list.sh
- Lists the current job status
- netdisco_observer_log_level.sh
- Sets the log level
- netdisco_observer_discovery_status.sh
- Checks the discovery status
- netdisco_observer_discovery_stop.sh
- Stops the discovery
netdisco_observer_discovery_stop.sh
script as a standalone script. It is run by the
netdisco_observer_load_stop
script as part of a specific sequence to stop a network
discovery before stopping an observer job.