How does NPM handle interface naming and user-defined mapping?

How does NPM handle interface naming and user-defined mapping?

• A. It always uses the raw interface names exactly as reported by devices
• B. NPM uses interface IDs and allows aliasing or mapping to friendly names for clarity in dashboards and alerts
• C. It cannot map interface names
• D. It requires vendor-specific plugins to rename interfaces

Answer: (B)

NPM identifies each interface by a stable internal identifier (such as an interface ID) and allows you to map that interface to a friendly, user-defined label for display. This means the dashboards and alerts can show clear, meaningful names instead of only the device-reported raw interface names, which can be long, inconsistent, or change with devices. The aliasing is built into NPM, so you can apply readable names without altering the actual device configuration. This makes monitoring more intuitive across large networks and helps ensure consistency in graphs, reports, and alerts. Raw device names aren’t always stable or readable, and you don’t need vendor plugins to rename interfaces—the built-in aliasing handles this directly.

NPM identifies each interface by a stable internal identifier (such as an interface ID) and allows you to map that interface to a friendly, user-defined label for display. This means the dashboards and alerts can show clear, meaningful names instead of only the device-reported raw interface names, which can be long, inconsistent, or change with devices. The aliasing is built into NPM, so you can apply readable names without altering the actual device configuration. This makes monitoring more intuitive across large networks and helps ensure consistency in graphs, reports, and alerts.

Raw device names aren’t always stable or readable, and you don’t need vendor plugins to rename interfaces—the built-in aliasing handles this directly.