FeedbackIntroduction
This release note is for Version 4.10.0.82. This software supports the Catalyst 1300x Stackable Managed Switch Series.
 Note |
The full list of the supported SKUs and the minimal supported version per SKU can be found in below. |
Supported Platform
The following tables lists the SKUs that are supported in the Catalyst 1300x series. Each table lists one of the Catalyst 1300x Series and provides information on each SKU description, OID and minimum supported version. Boards not listed in the following table are not supported by Catalyst C1300x release.
sysOID branch: iso (1) . org (3) . dod (6) . internet (1) . private (4) . enterprises (1) . cisco (9) . ciscoProducts (1) (OID field below begins from cisco (9) . ciscoProducts (1))
|
Device PID |
Description |
OID |
Minimum Supported Version |
|
C1300X-24P-4X |
Catalyst 1300X Series Managed Switch, 24GE+4SFP28,PoE (C1300X-24P-4X) |
9.1.3413 |
4.10.0.82 |
|
C1300X-24T-4X |
Catalyst 1300X Series Managed Switch, 24GE+4SFP28 (C1300X-24T-4X) |
9.1.3414 |
4.10.0.82 |
|
C1300X-48P-4X |
Catalyst 1300X Series Managed Switch, 48GE+4SFP28, PoE (C1300X-48P-4X) |
9.1.3416 |
4.10.0.82 |
|
C1300X-48T-4X |
Catalyst 1300X Series Managed Switch, 48GE+4SFP28 (C1300X-48T-4X) |
9.1.3417 |
4.10.0.82 |
What's New
This section details the new features found on firmware version 4.10.0.82
Note |
This release does not support the 802.1x command “dot1x control-direction”. This command will be added in future releases. |
SAN (Subject Alternative Name) HTTPS Certificate Field
In the Cisco Catalyst 1300x series release 4.10.0, the user can configure the Subject Alternative Name (SAN) field when creating HTTPS certificates. SAN allows a certificate to secure multiple domain names or IP addresses, offering more flexibility and broader coverage than the traditional Common Name (CN) field, which supports only a single domain.
The SAN field is optional and can be configured when generating a self-signed certificate or a certificate request
Note |
In this release the feature is supported only via CLI commands. GUI support will be added in later features |
OSPFv2 and OSPFv3 Support
The C1300X Series release 4.10.0 supports OSPFv2 and OSPFv3. the details of the settings and functionality that are supported can be found in the C1300x CLI Guide.
Note |
The GUI supports only a subset of the OSPF commands. |
Stacking Enhancements
On the Catalyst 1300x Series line the uplink interfaces support a maximum speed of 25G, so the user can select to set the stacking interface speed to 25G (the default) or 10G.
Note |
25G is supported only if the uplink interfaces are configured as stacking interfaces. When configured as (regular) network ports the maximum speed is 10G. |
PoE 802.3BT
In Catalyst C1300x, some PoE interfaces also support 4-pair 802.3BT PoE which can provide up to 60W PoE. Please check specific PoE SKU details to determine which ports support 2-pair 802.3BT and which support 4-pair 802.3BT.
The 802.3BT auto-class feature is supported on both types of PoE ports. The autoclass supports Auto/LLDP and Manual activations.
FIPS Enabled - GUI Control
In the Catalyst 1300x Series release 4.10.0, GUI support was added, allowing users to control the feature through the GUI interface.
Caveats
Caveats Acknowledged in Release 4.10.0.82.
|
Bug ID |
Description |
|---|---|
|
CSCwr76525 |
Symptom
The console may lose response in rare scenarios. WorkaroundUse SSH or telnet to access the CLI. |
|
CSCwr76554 |
Symptom C1300x - UDLD exchange fails with the Cisco Nexus switch. WorkaroundNone. |
|
CSCwr76557 |
Symptom CDP Negotiated power is 0 when an AIR-CAP3702I/CAP36021 AP is connected to the port. WorkaroundNone. |
|
CSCwr71240 |
Symptom The device crashes if the "show ip ospf database router" command is executed with more than 3000 route entries. Crash notice: %SNMP-F-FTLERR: SNMP Package: SnmpCen Routine: 24 Location: 10 Error: Bad value returned by application: Range error: variable = 3353, field = rlOspfRouterLsaType, value =8". WorkaroundNone. |
|
CSCwr76537 |
Symptom The port PoE status shows 'Fault' because of a short condition when a NIC is connected to the device. WorkaroundNone. |
|
CSCwr71246 |
Symptom OSPFv2 ASBR advertisement does not turn on bit E (ASBR). WorkaroundNone. |
|
CSCwr76565 |
Symptom The “no redistribute ospf [process-id] command cannot be executed without optional parameters. WorkaroundProvide an optional parameter with the required settings. |
|
CSCwr76567 |
Symptom OSPFv3 displays a learned /128 route in the totally stub/nssa area. WorkaroundNone. It's a display issue and it does not effect the functionality. |
|
CSCwr76572 |
Symptom Occasionally, the output of the “show ipv6 route” command may display OIA route types as an O route type. WorkaroundNone. It's a display issue and it does not effect the functionality. |
|
CSCwr76574 |
Symptom In certain cases a ping may fail when MSTP topology changes. WorkaroundNone. ICMP packet forwarding is delayed and this causes the ping to timeout. IP connectivity is not broken. |
|
CSCwr69885 |
Symptom The SFP-10G-T-X module installed in the C1300X uplink port does not establish a link when connected to the mGig ports on certain C9200 models, such as the C9200L-24PXG-4X. WorkaroundIf possible connect to a non Mgig port on the 9200 or use a different SFP. |
|
CSCwr76652 |
Symptom In some cases, after disabling and then re-enabling CDP negotiation, the device supplies 39W of power even though the access point requested only 30W. This issue occurs only with certain access points that support class 6. WorkaroundDisconnect and reconnect the AP for proper delivery of power. |
|
CSCwr76655 |
Symptom The device’s online help indicates that Auto Detection is a supported console speed setting. However, only static speeds are actually supported. WorkaroundNone. |
|
CSCwr76658 |
Symptom OSPF stops sending updates and does not resume until the 'clear ipv6 ospf process' command is issued. WorkaroundNone. |
|
CSCwr76659 |
Symptom The area area-id virtual-link command accepts the message-digestparameter even if the md5 parameter appears before the message-digest-key parameter. WorkaroundNone. The command is accepted and functions properly in both formats. |
|
CSCwr76660 |
Symptom In some cases, OSPFv2 routes are not redistributed into RIP. WorkaroundApply the no redistribute ospf x command and then apply the redistribute ospf x command. |
|
CSCwr7662 |
Symptom Philips device with CSR8510 Bluetooth 4.0 is not recognized in some of the C1300X devices. WorkaroundNone. |
|
CSCwr76663 |
Symptom The syslog date time on the remote log server is incorrect when the timezone is configured with a negative offset. WorkaroundNone. |
|
CSCwr76665 |
Symptom In some cases the OSPFv3 DR may advertise the wrong prefix in the Intra-Area Prefix-LSA (for example 2008:1::2/64 instead of sement address 2008:1::/64. WorkaroundNone. |
|
CSCwr76675 |
Symptom The DUT always displays the "Invalid signature detected" log if it is connected to the PoE port of another switch. WorkaroundNone. |
|
CSCwr76694 |
Symptom If the OSPFv3 virtual link hello time is changed multiple times, the virtual link will remain down. WorkaroundApply the clear ipv6 ospf process command. |
|
CSCwr76698 |
Symptom The OSPFv3 “nssa translator-role always” command does not function properly, and routes are still learned from a different router. WorkaroundNone. |
|
CSCwr76699 |
Symptom The Cisco SFP-10/25Gbase-LR cannot work as stacking ports. WorkaroundNone. |
|
CSCwr76701 |
Symptom SNTP web GUI should support four types of authentication-key like the CLI. WorkaroundUse the CLI to configure. |
|
CSCwr76704 |
Symptom When the clock is updated using an SNTP broadcast packet, the "last synchronized" field always shows 00:00:00 instead of the actual synchronization time. This is only a display issue—the clock is synchronized correctly. WorkaroundNone. |
|
CSCwr76706 |
Symptom The OSPFv3 route table show the /128 route even though the parent route /64 is also present. WorkaroundNone. |
|
CSCwr76707 |
Symptom It is not possible to change the OSPFv2 area ID of an Area Network. A “Success” indication is presented even though the operation failed. WorkaroundUse CLI to modify the Area ID of network. |
|
CSCwr76708 |
Symptom In some cases, a “Bad Packet” message may be displayed when connecting devices after configuring OSPFv2. This is only a display issue, the OSPF neighbor process completes successfully. WorkaroundNone. |
|
CSCwr76709 |
Symptom Generating a self-signed certificate with SAN (Subject Alternative Name) information may result in security warnings or connection failures in some browsers. WorkaroundUse Firefox. |
|
CSCwr76711 |
Symptom The maximum hardware resources for QoS and ACL cannot be fully utilized. WorkaroundNone. |
|
CSCwr76713 |
Symptom Cisco CWDM SFP VID cannot be read via the show inventory command. WorkaroundNone. |
|
CSCwr76715 |
Symptom The sFlow flow-sample does not work when a port added to a port channel. WorkaroundNone. |
|
CSCwr76716 |
Symptom CPU input rate can't automatically be refreshed. WorkaroundNone. |
|
CSCwr76722 |
Symptom The privacy methods AES256 and AES192 in SNMPv3 cannot be configured in web GUI. WorkaroundUse the CLI to configure. |
|
CSCwr76723 |
Symptom In the POE port limit mode, LLDP power negotiation may cause abnormal behavior. WorkaroundNone. |
|
CSCwr28463 |
Symptom The Cisco DBS-210 base station cannot be powered on via the PoE. WorkaroundNone. |