| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
fabric:Ep The root container of all fabric configuration objects. |
|
├
|
fabric:EthEstcCloud A container of logical Configuration Objects for Ethernet-based storage, such as NFS filers
attached to the Fabric Interconnects ports.
The contained configuration objects specify the logical storage configuration, including
logical ports on fabric A and B, VLANs used specifically for NAS storage, and threshold policy.
|
|
|
├
|
fabric:EthEstc Container for External Storage Target Connectivity (ESTC) Objects
that are specific to a Fabric Interconnect.
|
|
|
|
├
|
fabric:EthEstcPc A logical Ethernet Port Channel on a Fabric Interconnect, for connectivity
to an external NAS storage.
This object is created explicitly by the user. Creation of this object
indicates that the terminated port will be a port channel connected to NAS storage.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
fabric:Ep The root container of all fabric configuration objects. |
|
├
|
fabric:LanCloud A container for logical Ethernet configuration Objects that span
across the Fabric Interconnects.
The contained configuration objects specify the logical Ethernet configuration,
including fabric A and B, VLANs, pin groups, flow control policy, QoS policy,
threshold policy, and port profiles.
|
|
|
├
|
fabric:EthLan Represents an Ethernet fabric, which contains the
user-configured VLANs, Ethernet interfaces and Ethernet
port channel interfaces.
In a UCS HA configuration, there are two Ethernet Fabrics,
A and B. Each fabric can contain a distinct set of configured
VLANs, Ethernet interfaces and port channel interfaces.
The VLAN may be configured per Ethernet fabric (i.e. fabric A
or fabric B) or per Lan Cloud, in which case the VLAN wi... |
|
|
|
├
|
fabric:EthLanPc An Ethernet Port Channel Interface, which aggregate multiple
Ethernet ports to increase the link throughput and increase redundancy
for higher availability.
This is configured by the API user.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
compute:RackUnit
A physical compute RackUnit. Physical compute item representing
a Rack mountable unit.
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
compute:Blade
A physical compute blade. Physical compute item in
blade form factor.
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:SwitchIOCard Represents an inventoried FI-IOM Card on a UCS-Mini Chassis
This object is created implicitly when an FI-IOM Card is detected during hardware
discovery.
TODO: This is model similar to IOCard currently however this does not behave like a
IOCard (IOM) and some of the properties will be removed if not needed.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:SwitchIOCard Represents an inventoried FI-IOM Card on a UCS-Mini Chassis
This object is created implicitly when an FI-IOM Card is detected during hardware
discovery.
TODO: This is model similar to IOCard currently however this does not behave like a
IOCard (IOM) and some of the properties will be removed if not needed.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
├
|
equipment:SwitchIOCard Represents an inventoried FI-IOM Card on a UCS-Mini Chassis
This object is created implicitly when an FI-IOM Card is detected during hardware
discovery.
TODO: This is model similar to IOCard currently however this does not behave like a
IOCard (IOM) and some of the properties will be removed if not needed.
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
equipment:Chassis A physical unit that can accomodate multiple blade servers.
For example, the Cisco UCS 5108 Blade Server Chassis is six rack units
(6RU) high, can mount in an industry-standard 19-inch rack and uses
front-to-back cooling.
|
|
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
|
├
|
equipment:IOCard Represents an inventoried IO Card on a device, such as an IO module on a UCS chassis or FEX.
This object is created implicitly when an IO Card is detected during hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
network:Element Represents a physical network element, such as a Fabric Interconnect. |
|
|
├
|
equipment:SwitchCard Represents a physical switch card, such as a fixed module on a Fabric Interconnect
or an extension module.
This object is automatically created through hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
network:Element Represents a physical network element, such as a Fabric Interconnect. |
|
|
├
|
equipment:SwitchCard Represents a physical switch card, such as a fixed module on a Fabric Interconnect
or an extension module.
This object is automatically created through hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
ether:ServerIntFIo Represents a server-facing physical Ethernet port on an IO Card.
IO Modules on a UCS chassis and IO modules on a FEX have Ethernet ports
that are connected to a Fabric Interconnect and Ethernet ports that
are connected to the servers.
This object represents the Ethernet ports on the IO Card that are
connected to the servers.
|
| top:Root This class represents the root element in the object hierarchy.
All managed objects in the system are descendants of the Root element. |
├
|
top:System Provides general information about this system, such as the name, IP address
and current time. |
|
├
|
network:Element Represents a physical network element, such as a Fabric Interconnect. |
|
|
├
|
equipment:SwitchCard Represents a physical switch card, such as a fixed module on a Fabric Interconnect
or an extension module.
This object is automatically created through hardware discovery. |
|
|
|
├
|
port:Group A collection of physical ports on a device.
A port group is created implicitly during device discovery of IO devices
such as IO cards on a Fabric Interconnect, or IO modules on a UCS chassis.
All the ports in a portGroup have the same type (i.e. FC, Ethernet).
|
|
|
|
|
├
|
port:SubGroup
A SubGroup contains ports which are made availabe by connecting a break-out cable to an
aggregated port. Example in UCS-Mini a 40GB Scalability
port is connected to a 4x10GB breakout cable to get 4 10GB ports.
|
|
|
|
|
|
├
|
ether:PIo An inventoried Physical Ethernet Port on a physical device,
such as a L2 switch, FEX, or IOM module on a Chassis.
The "ifRole" property specifies if this is a server-facing port or
uplink Ethernet port.
|
|