Validating network port configuration in Shell and Web

Last Updated : Oct 30, 2026 |
Prolog information
Metadata
Keywords:
Use this procedure to verify network port configuration.
  1. From the CLI, execute nmcli conn to display network interfaces.
    ADDITIONAL INFORMATION:
    For example:

    [custadm@asp130-r660xs ~]$ nmcli connection
    NAME             UUID                                  TYPE      DEVICE
    Mgmt_VM_Network  752f89b7-b88a-4d19-9e80-22780767cb9a  bridge    bridge0
    bridge0-port     39d39997-a927-409a-8ea9-3e52511bf793  ethernet  eno8303
    eno12399         0511544c-3643-4c19-ae35-edf837ad51ce  ethernet  --
    eno12409         2a5d44f5-ee72-40e2-9ffb-4ad1a0170722  ethernet  --
    eno12419         ed57f1cf-e0ed-463b-887c-4fe52b69bfb7  ethernet  --
    eno12429         3f7276a8-b7ce-4997-bd09-837dc78dc51c  ethernet  --
    eno8303          e3111d99-7aa6-467c-b15e-29b3e671bfe7  ethernet  --
    Services         6e6abe63-0b19-4841-b994-62873d86080a  ethernet  --
     
  2. Cockpit can also be used to display network interfaces.
    ADDITIONAL INFORMATION:
    Note that the Connection Profile name does not appear in Cockpit, but the “Device Name” is displayed.
    ASP R7.x R660xs
    Connection Profile Name
    R660xs Device Name
    Notes
    Mgt_VM_Network
    bridge0 (eno8303)
    Default w/out OOBM enabled
    VM_Network
    With OOBM enabled
    Services
    eno8403
    192.11.13.6 services port
    OOBM_Network
    bridgeOOB (eno12399)
    Optional: Must be enabled during configuration
    The “Connection Profile Name” is what is seen when the nmcli connection shell command is executed. The Connection Profile Name does not appear in the Cockpit UI. The “Device Name” is what is seen in the Cockpit UI.
    Additional ports are available on the server, the ones listed above are most relevant for installation.