Smarts NCM: Adding a second Network Interface to NCM causes jobs to fail.
book
Article ID: 331313
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
High - Will affect communications of NCM and all jobs will stop processing. Jobs will be stuck in "Queued for Execution" status.
Adding another network interface card to the NCM Application server or device server.
Environment
VMware Smart Assurance - NCM
Cause
NCM by design will attempt to communicate with any available network interface, so if there are two or more interfaces NCM will choose one interface the first time, but might choose the other one the second time.
Resolution
To resolve this issue you will need to configure static routes on the NCM Server that you added the additional network interface card to.
To add static routes please do the following at the command prompt:
Goto /etc/config/network-scripts/ directory
Edit the interface you want NCM to statically communicate through.
vi ifcfg-Auto_eth0
Define a static route to each NCM device server. Each line is parsed as an individual route:
10.10.10.2/24 via 192.168.0.1 dev eth0
172.16.1.56/24 via 192.168.0.1 dev eth0
Once saved you will need to restart Network Services