Network Management

SWOES EOC: Nodes with Custom “Device Category” Showing Under Others in Node Category View

In EOC, node category views are driven by the built‑in Node Category field, not by custom properties such as device category. When Node Category remains at the default (e.g., Others), nodes may appear under Others even if a custom property says network or server.

First published date

6/2/2026 4:39 PM

Last published date

6/2/2026 4:39 PM

Overview

After creating a custom node property (for example, device category with values like network, server, and others) you expect EOC’s node category views to categorize nodes based on that custom property.

In these scenarios, some nodes that clearly belong to Network or Server (based on their custom property and polling method, e.g., SNMP/Agent) still appear under the Others category in EOC. This leads to a perceived functional defect and a “lack of visibility” complaint, as admins cannot reliably filter or report on Network/Server nodes using the built‑in category views.

However, the current product behavior is by design: these views are tied to the internal Node Category field on each node. If Node Category is not aligned with the custom property, EOC will continue to group nodes under Others, even when the custom “device category” is set to network or server. The fix is a configuration alignment, not a product change.

Product section

Enterprise Operations Console

Cause

 

  • EOC node category views use the built‑in Node Category field as their source of truth.

  • A custom property is configured (e.g., device category = network/server/others) and it is assumed EOC will use it for categorization.

  • For affected nodes, the Node Category field is still left at its default (typically Others), while the custom property is set to network or server.

  • Because the view does not read the custom property, EOC correctly puts those nodes under Others based on their Node Category, resulting in an apparent mismatch between expectation (custom property) and behavior (Node Category).

Resolution

Confirm Which Field Drives the View

  • EOC node category views are driven by the Node Category field, not by the custom “device category” (or any other custom property).

  • Changing the custom property alone will not affect how nodes are grouped in those specific views.

2. Check Current Node Category on an Affected Node

  1. In the main platform UI, navigate to the affected node.

  2. Choose Edit Node.

  3. Locate the Node Category field.

  4. Note its current value (for example, Others).

3. Align Node Category with Intended Category

  1. For nodes that should be treated as network devices, set Node Category = Network (or the appropriate built‑in category).

  2. For nodes that should be treated as servers, set Node Category = Server.

  3. Save the node configuration.

After saving, re-check the EOC node category views; the updated node should now appear under Network or Server instead of Others.

4. Apply Changes for Multiple Nodes (If Needed)

If many nodes are affected:

  • Use bulk-edit tools (Manage Nodes / node lists, discovery results, or appropriate bulk‑edit mechanism in the customer’s environment) to update Node Category for groups of nodes that share the same intended category.

  • Align any internal documentation, scripts, or property mapping so that when new nodes are onboarded, Node Category is set consistently with your syntax (and not only the custom “device category” field).

5. Best Practices

  • For any EOC view labeled by “node category”, use and maintain the Node Category field as the canonical categorization.

  • Continue to use custom properties (like device category) for reporting, filtering, and custom dashboards, but do not assume they automatically drive built‑in category views unless explicitly documented.

  • When new categorization/reporting needs arise, verify first which field a given EOC view or widget actually uses, and plan property mappings accordingly.