Network

Entry: /network. Network owns nodes, members, interfaces, addressing, connectivity and discovered evidence. Choose the correct Group and confirm inventory-management or IPAM authority for the task. Remote credentials, SSH collection and configuration backups have additional permissions; ordinary inventory access does not grant them.

Register a node and its members

1. Open Nodes and choose Register Device. Enter the node hostname, Device type, node type, deployment arrangement and relevant environment, software and management information.
2. Define the members required by that arrangement. A standalone node has one member; Stack/Cluster arrangements support two to eight and HA has two. Check each member's identity and serial.
3. If authorized Asset integration is available, a declared serial can match a unique current same-Group Asset. Review the actual association after saving; do not assume a typed serial proves a match.
4. Open the node's interfaces. Materialize or register the required physical ports explicitly using the available model/member controls before using them as connection endpoints.

Record an IP assignment

1. Open IPAM and select the relevant related view. Prepare the required VRF/VLAN context and create the subnet with its correct address family and CIDR.
2. Locate the intended interface and use the permitted Assign Ip Address action. Select the subnet and exact address.
3. Review the saved interface and subnet membership. Check that you have recorded the intended address rather than creating a conflicting assignment.
4. Use Routing for the supported routing records; treat those records as configuration knowledge unless a separate authorized operational process applies changes to equipment.

Review discoveries and topology

1. Open Discovery to inspect source/run evidence and the reconciliation queue. Filter it to the work you need and use continuation pages to reach older findings.
2. Compare a proposal with its observed source and current inventory. Choose Accept or Ignore only with the appropriate current permission and after reviewing the proposed effect.
3. Open Topology. Use the Physical view for observed neighbor evidence and the Logical view for interface/subnet/VRF relationships. Read timestamps and missing-evidence states before drawing conclusions.

Boundaries: Asset identity, node membership and Facilities placement remain distinct records. Linked-member removal can be blocked by assignments, interfaces or retained history. Discovery observations do not automatically rewrite authoritative inventory or IPAM. Recorded manual connections, observed neighbors and verified Cabling paths have different meanings; none should be substituted for another when evidence is absent.