Command Reference Guide
unit/slot/port Naming Convention
CLI Command Reference
September 2014 Page 15
HP Moonshot Switch Module CLI Command Reference
unit/slot/port Naming Convention
HP Moonshot Switch Module software references physical entities such as cards and ports by using a unit/
slot/port naming convention. The HP Moonshot Switch Module software also uses this convention to identify
certain logical entities, such as Port-Channel interfaces.
The unit number identifies the stack member within a stack of switches. The slot number has two uses. In the
case of physical ports, it identifies the card containing the ports. In the case of logical and CPU ports it also
identifies the type of interface or port.
The port identifies the specific physical port or logical interface being managed on a given slot.
Table 3: Type of Slots
Slot Type Description
Physical slot numbers Physical slot numbers begin with zero, and are allocated up to the maximum
number of physical slots. Internal ports are located on slot 0, and external
ports are located on slot 1. For example, the external uplink/stacking ports are
1/1/1, 1/1/2, 1/1/3, and so on.
Logical slot numbers Logical slots immediately follow physical slots and identify port-channel (LAG)
or router interfaces.
A LAG (port-channel) interface uses 3 as the slot number. By default, the first
LAG that is configured is 0/3/1.
A VLAN routing interface uses 4 as the slot number. By default, the first VLAN
configured as a VLAN routing interface is 0/4/1.
CPU slot numbers The CPU slots immediately follow the logical slots.
Table 4: Type of Ports
Port Type Description
Physical Ports The physical ports for each slot are numbered sequentially starting from one,
For example, port 1 on slot 0 (an internal port) for a stand alone (nonstacked)
switch is 1/0/1, port 2 is 1/0/2, port 3 is 1/0/3, and so on.
Logical Interfaces Port-channel or Link Aggregation Group (LAG) interfaces are logical interfaces
that are only used for bridging functions.
VLAN routing interfaces are only used for routing functions.
Loopback interfaces are logical interfaces that are always up.
CPU ports CPU ports are handled by the driver as one or more physical entities located on
physical slots.
Note: In the CLI, loopback interfaces do not use the unit/slot/port format. To specify a loopback
interface, you use the loopback ID.