OpenText Network Operations Management (NOM) — Network Discovery & Monitoring

Blog Series: OpenText NOM — Part 2

➡ Part 1: SNMP Explained for Monitoring Engineers

After understanding SNMP fundamentals, the next step is to see how monitoring tools actually use it in real environments.

OpenText Network Operations Management (NOM) automatically discovers devices, builds topology and monitors network health continuously.

This article explains how discovery and monitoring work in real NOC environments.

📌 Role of NOM in Network Operations

Enterprise networks contain:

  • Routers

  • Switches

  • Firewalls

  • Load balancers

  • Servers

Manual monitoring is impossible.

OpenText NOM provides centralized visibility and automated monitoring across the network infrastructure

What is Network Discovery?

Network discovery automatically identifies devices connected to the network and gathers:

  • IP address

  • Vendor & model

  • Interfaces

  • Routing relationships

It continuously discovers nodes and keeps topology updated

🖼️ Discovery Overview

How NOM Discovers Devices

NOM primarily uses Simple Network Management Protocol and ICMP.

SNMP collects device status variables and configuration information from network equipment

Discovery Flow

  1. Admin defines IP range

  2. Tool sends ICMP ping

  3. SNMP query sent to device

  4. Device identified

  5. Topology mapped automatically

Discovery Types

Discovery TypePurpose
IP DiscoveryFind devices
SNMP DiscoveryCollect device information
Layer-2 DiscoverySwitch connectivity
Layer-3 DiscoveryRouting paths

🖼️ Discovery Workflow

Network Monitoring in NOM

After discovery, monitoring starts automatically.

The tool continuously checks device health and performance.

Metrics Monitored

CategoryExamples
AvailabilityUp / Down
PerformanceCPU / Memory
InterfacesBandwidth usage
ErrorsPacket drops
HardwareTemperature, power

🖼️ Monitoring Dashboard

Polling vs Traps

Polling

Monitoring server queries device periodically

SNMP Traps

Device sends alert instantly

Example:

Link Down: Gi0/1 Switch-Core

Immediate alert generated.

Event Correlation (Root Cause Analysis)

Instead of showing 100 alarms:

Switch Down → Server Down → Application Down

NOM correlates them into one root cause alarm

This reduces alert noise and speeds troubleshooting

🖼️ Event Correlation

Best Practices

✔ Use SNMPv3 credentials
✔ Discover during off-peak hours
✔ Tune polling interval
✔ Configure thresholds
✔ Enable traps for critical devices

Why This Matters

Without monitoring:

  • Late outage detection

  • Manual troubleshooting

  • Service downtime

With NOM:

  • Proactive detection

  • Faster resolution

  • Capacity planning

📚 Recommended Reading

Part 1 — SNMP Fundamentals

Also read:

🎯 Conclusion

SNMP provides the data.
NOM provides the visibility.

Discovery builds the network map.
Monitoring keeps the network healthy.

This is the foundation of modern Network Operations Centers.

💼 Professional Support Available

If you are facing issues in real projects related to enterprise backend development or workflow automation, I provide paid consulting, production debugging, project support, and focused trainings.

Technologies covered include Java, Spring Boot, PL/SQL, CMS, Azure, and workflow automation (jBPM, Camunda BPM, RHPAM).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital metal podium


Comments

Post a Comment

Popular posts from this blog

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more