Server CI is not binding with IP address on production instance but its binding on dev instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2024 12:16 AM
I have created event rule and set default binding because node is server IP address. So it should bind to the server CI. Same configurations are working on dev instance but not on production instance. IP address is also available in cmdb_ci table in dev and prod both instance.
Dev instance worknotes
Binding alert CI process flow:
Node is IP address
Node will be resolved to CI id: 76c0afcbdbabdf008a0e138b4b96190e : found by IP address
Event CI type is empty
No related CI found for binding, alert CI will be bound to node (id): 76c0afcbdbabdf008a0e138b4b96190e
Bind to 76c0afcbdbabdf008a0e138b4b96190e
Prod instance worknotes
Binding alert CI process flow:
Node is IP address
Node was not found, checking by name
Event CI type is empty
No CI found for binding (Failed to resolve the event node to CI id)
Binding Failure Reason: Failed to find the host with name: 22.195.123.21
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 05:35 AM
did you check the state of the CI in Prod? Its unable to find that IP address and hence the binding is not working... Other than this try to re- verify the mapping done on Dev and Prod.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2024 11:23 AM
@nirbhaysingham The IP address in the CMDB might not be fully populated or accurate in the production instance. Even though the IP address exists in cmdb_ci, it may not be linked correctly to the CI.
Please verify below:
Verify that the CI with the IP address 22.195.123.21 exists in the cmdb_ci table in production and has proper relationships defined (IP Address to the CI).
Compare the Discovery status and relationships for this CI between dev and production.
The CMDB data model or relationships in production might differ slightly from dev.
Ensure the IP address is listed under the correct attribute (e.g., ip_address or ip_network).
Compare cmdb_ci records for the target CI in dev and prod to ensure consistency.
And also validate that the "Binding to CI" rules are identical and are set to look up CIs by IP address.
Hope this will help you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-10-2025 02:06 AM
Hi @nirbhaysingham,
Wondering if you got to resolve this? I'm encountering the same error T.T