Cisco Catalyst 2960-X 48FPD-L

Cisco · 1U switch, 48 PoE+ ports, 2 SFP+ 10 Gb/s ports · Cisco Catalyst WS-C2960X-48FPD-L

Front panel (to-scale schematic)
Rear panel
gniazdo modulu FlexStack-Plus (zaslepka)RPS (DC)IEC C14

what it is

A 1U switch for a 19" rack: 48 gigabit ports with PoE+ power and two SFP+ 10 Gb/s ports for uplinks. Chassis 4.5 × 44.5 × 36.8 cm, 5.8 kg, with a fan and an internal power supply. Operates from −5 to 45°C (vendor datasheet). Next to the data ports there is a separate 10/100 management port that does not take part in switching.

The 740 W budget means 24 ports at 30 W or 48 at 15.4 W. A full set of 48 devices, each requesting the full 30 W, will not fit — the budget counts, not the number of ports.

LAN Base license: layer 2 switching and static routes. With the optional FlexStack-Plus module, up to eight switches can be stacked.

Life cycle: end of sale on October 31, 2022, maintenance releases until October 31, 2023, and security fixes until October 31, 2027. The successor is the Catalyst C9200L-48P-4X (vendor end-of-sale notice).

what we read from it

We read this model over SNMP. The interface, error counter, bridge, component inventory, environment, PoE, cable test, LLDP, spanning tree, CPU, memory, flash, license, configuration and stack branches respond. We collect the state of every port with speed and duplex, traffic, error counters, firmware version and uptime.

In addition the switch returns:

SFP transceiver diagnostics

For every transceiver with digital diagnostics the switch returns five sensors: temperature, supply voltage, laser bias current, transmit power and receive power. Each sensor has four thresholds — alarm and warning, high and low — plus an assessment of whether a threshold is exceeded. The thresholds come from the transceiver's own memory, so every transceiver model has its own.

Three things set this reading apart from what the command line shows:

A transceiver without digital diagnostics has no sensors at all in SNMP, and the command line prints Diagnostic Monitoring is not implemented. This is the correct state for such a transceiver, not a reading error.

A full transceiver memory dump is given by show idprom interface , but only in privileged mode. The EEPROM PAGE A2 Bytes section in this dump is all zeros and looks as if the transceiver had no diagnostics. The real data is further down, in the SFF-8472 Digital Diagnostic Monitoring Data section.

transceivers from other vendors

Every transceiver without Catalyst coding — including Cisco ones from the Small Business line, for example MGBSX1 — triggers two messages at startup:

Without two commands in the configuration, the port then goes into the err-disable state:

After write erase both disappear. Transceivers that worked before the reset stop working after it — these two commands have to be entered first.

one port, two names

An SFP+ port with a 10 Gb/s transceiver is named Te1/0/1, and with a 1 Gb/s transceiver — Gi1/0/49. Monitoring keyed by interface name loses the port's history every time the transceiver is swapped for one of a different speed.

PoE on a link to another PoE switch

Measured on a copper link to a PoE port of another switch: in the first two minutes after startup the switch detected a PoE powered device on the other side, allocated power to it, withdrew it and brought the link up and dropped it five times before the link stabilized. Two power sources facing each other try to power one another. On a port linking to another PoE switch, power inline never is the right setting.

console

The console runs at 9600 b/s, 8N1. On the welcome screen the system ignores everything except the Enter key: for a minute the port may not return a single byte or echo typed characters. No echo does not mean the port is not working — a single Enter returns the prompt.

what we cannot read

transceivers tested in this device

Transceivers we checked in this device, and whether the device showed their optical diagnostics (temperature, power, alarm thresholds):

All transceivers and switches in one place, with filters: what each device shows.

full list of parameters read via SNMP

The list shows WHAT the device exposes — including parameters we do not use ourselves. There are no values here at all: it is a catalog of capabilities, not a reading from anyone's network. It is not a closed list either — explanation below the table.

28 parameters

parametertype
SNMP::BRIDGE-MIB dot1dBase (whole branch)branch responds
SNMP::CISCO-CABLE-DIAG-MIB (whole branch)branch responds
SNMP::CISCO-CONFIG-MAN-MIB (whole branch)branch responds
SNMP::CISCO-ENTITY-FRU-CONTROL-MIB (whole branch)branch responds
SNMP::CISCO-ENTITY-SENSOR-MIB entSensorThresholdTable (whole branch)branch responds
SNMP::CISCO-ENTITY-SENSOR-MIB entSensorValueTable (whole branch)branch responds
SNMP::CISCO-ENVMON-MIB temperature (whole branch)branch responds
SNMP::CISCO-ENVMON-MIB fans (whole branch)branch responds
SNMP::CISCO-ENVMON-MIB power supplies (whole branch)branch responds
SNMP::CISCO-ERR-DISABLE-MIB (whole branch)branch responds
SNMP::CISCO-FLASH-MIB (whole branch)branch responds
SNMP::CISCO-IMAGE-MIB (whole branch)branch responds
SNMP::CISCO-LICENSE-MGMT-MIB (whole branch)branch responds
SNMP::CISCO-MEMORY-POOL-MIB (whole branch)branch responds
SNMP::CISCO-PORT-SECURITY-MIB (whole branch)branch responds
SNMP::CISCO-POWER-ETHERNET-EXT-MIB (whole branch)branch responds
SNMP::CISCO-PROCESS-MIB cpmCPUTotal (whole branch)branch responds
SNMP::CISCO-STACKWISE-MIB (whole branch)branch responds
SNMP::CISCO-STP-EXTENSIONS-MIB (whole branch)branch responds
SNMP::CISCO-SYSLOG-MIB (whole branch)branch responds
SNMP::CISCO-VTP-MIB vtpVlanTable (whole branch)branch responds
SNMP::ENTITY-MIB entPhysicalTable (whole branch)branch responds
SNMP::EtherLike-MIB dot3StatsTable (whole branch)branch responds
SNMP::IF-MIB ifTable (whole branch)branch responds
SNMP::IF-MIB ifXTable (whole branch)branch responds
SNMP::LLDP-MIB lldpRemTable (whole branch)branch responds
SNMP::POWER-ETHERNET-MIB pethPsePortTable (whole branch)branch responds
SNMP::SNMPv2-MIB system (whole branch)branch responds

This is not a closed list. It comes from reading a unit we had access to — it shows what we managed to retrieve, not everything the device can return. A different firmware version, hardware variant or reading path can expose fields that are not here. If you are interested in a specific unit and a specific value — please ask; there is a good chance it can be obtained, even if you do not see it below.

List source: reading of 1 working unit (as of 2026-10-18). The list is the sum of what we observed — more units reveal more parameters, so numbers for different models are not directly comparable.