VMware vRealize Network Insight: Install, Configure, Manage [V6.1] — Lesson 2: vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health.
• Demonstrate the workflow and leave reproducible evidence in data-source onboarding record and topology completeness check.
• Recommend a preventive improvement after resolving flow telemetry arriving without device configuration context needed for path analysis.

Detailed Topics

• VCenter
• NSX
• Physical switches
• Routers
• Firewalls
• Cloud sources
• Flow data
• Discovery
• Entity relationships
• Topology
• And collection health
• Decision ownership, prerequisites, and acceptance evidence for vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

Using realistic infrastructure, identities, and workloads, the instructor demonstrates vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health. Checkpoints are captured in data-source onboarding record and topology completeness check, with discussion of alternatives, side effects, and acceptance conditions.

Hands-On Exercise

Build or execute vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health for a defined scenario. Introduce the condition “flow telemetry arriving without device configuration context needed for path analysis,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in data-source onboarding record and topology completeness check.

1. Map the current workflow and mark where the expected result can first be observed.
2. Run the scenario while preserving timestamps, object identifiers, and relevant output.
3. Apply a reversible correction only after evidence supports the cause.
4. Retest the original case plus an unaffected case and update the handover record.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how data-source onboarding record and topology completeness check should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health. Preserve the failing example, review data-source onboarding record and topology completeness check, and verify whether “flow telemetry arriving without device configuration context needed for path analysis” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• The requirement for vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health is linked to an owner and observable acceptance condition.
• Data-source onboarding record and topology completeness check contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply vCenter, NSX, physical switches, routers, firewalls, cloud sources, flow data, discovery, entity relationships, topology, and collection health, explain the decisions made, and defend the result with data-source onboarding record and topology completeness check.