Unit/Slot/Port Naming Convention - NETGEAR ProSafe M7100-24X User Manual

Unit/Slot/Port Naming Convention

Managed switch software references physical entities such as cards and ports by using a
unit/slot/port naming convention. The software also uses this convention to identify certain
logical entities, such as Port-Channel interfaces.
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.
Table 3. Type of Slots
Slot Type
Physical slot numbers
Logical slot numbers
CPU slot numbers
The port identifies the specific physical port or logical interface being managed on a given
slot.
Table 4. Type of Ports
Port Type
Physical Ports
Logical Interfaces
CPU ports
Note: In the CLI, loopback and tunnel interfaces do not use the
unit/slot/port format. To specify a loopback interface, you use the
loopback ID. To specify a tunnel interface, you use the tunnel ID.
Using a Command's "No" Form
The no keyword is a specific form of an existing command and does not represent a new or
distinct command. Almost every configuration command has a no form. In general, use the
no form to reverse the action of a command or reset a value back to the default. For example,
ProSafe M4100 Series Managed Switches
Description
Physical slot numbers begin with zero, and are allocated up to the maximum
number of physical slots.
Logical slots immediately follow physical slots and identify port-channel (LAG) or
router interfaces.
The CPU slots immediately follow the logical slots.
Description
The physical ports for each slot are numbered sequentially starting from zero.
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.
Tunnel interfaces are logical point-to-point links that carry encapsulated packets.
CPU ports are handled by the driver as one or more physical entities located on
physical slots.
Using the Command-Line Interface
12