The following MIB object is not supported:

• fsaxFlow

The following MIB object is not supported:

• fsaxQueue

The following configuration commands are not supported:

• qos-queue-group

• qos-queue-list

• traffic-shape rate

In the access-list configuration for filtering and QoS, the following commands can be configured, but the configuration does not take effect:

• range parameter of tcp port and udp port

• neq parameter of tcp port and udp port

• layer2 parameter of deny and permit

• layer3 parameter of deny and permit

• advance access-list resequence

• ip access-list resequence

• ipv6 access-list resequence

• mac access-list resequence

The following limitations apply when access list logging is configured for protocol control packets addressed to this device.

• It will be excluded from access list logging.

• Packets are not discarded even if the filter is specified to be discarded.

If you want to discard protocol control packets addressed to this device, do not apply access list logging to the filter.

Daylight saving time should be set using the number parameter in the “clock timezone”.

Do not use the “clock summer-time” configuration command.

When using IGMP snooping, configure one or more multicast router ports for VLAN where IGMP snooping is enabled.

When using MLD snooping, configure one or more multicast router ports for VLAN where MLD snooping is enabled.

When the “system flash-monitor configuration command” is set, the following recovery system message is not displayed even if the free space of the internal flash memory falls below the threshold specified in the recovery-threshold parameter:

01221011 The internal flash memory has enough free space.

• The “show system” operation command and MIB object are set to “1000BASE-T full (auto)” for the speed of the management port, regardless of the configuration.

• If multiple LCs are used, the LC power status displayed by “show power” is “-”.

The “system temperature-warning-level” configuration might not take effect when the device starts up. If this occurs, you need to delete and reconfigure the “system temperature-warning-level” configuration.

The following FAN-related issues occur:

• When the system is powered on, a false FAN unit failure is detected, causing all three FAN units to run at high speed.

• When a FAN unit is replaced, a false failure of the newly installed FAN unit is detected, causing all three FAN units to continue running at high speed.

• When a FAN unit is removed, the following system message, which should not normally be generated for the removed FAN unit, is output incorrectly:

  S4 FAN FAN:X 01213006 00 ffcb0a000000 The fan speed was changed to high.

To recover from these issues, the system must be rebooted using the “reload” command without turning the power off. When the system restarts, all three FAN units initially run at high speed. The FAN units slow down gradually and back to normal speed within approximately 30 to 40 minutes.

Brief outages of packet forwarding intra VLAN (bridging) and SVI (routing) occur after the following events. In the following description, “affected” means a brief outage on that VLAN (for an average of 35 milliseconds).

• Configuration changes by operator:

  • VLANs are affected when they are removed from the list of allowed VLANs for the trunk port.

  • The default VLAN (VLAN 1) is affected when “switchport access vlan <n>” is configured.

  • When IPv4 direct broadcast forwarding is enabled on an SVI, and upon disabling it, the corresponding VLAN is affected.

• Network state changes without the operator’s intervention:

  • VLANs are affected when configured as allowed VLANs on the channel group, and the entire channel group goes up or down.

  • The VLAN is affected when the corresponding SVI is the IPv4/IPv6 unicast route’s outgoing interface, ARP/NDP for the next hop is removed, and the MAC address for the next hop is not learned.

• Network state changes when PIM is configured on FS-AX9004G:

  • The VLAN is affected when a MAC address learned by IGMP/MLD snooping is removed.

  • The VLAN is affected when a destination port for a MAC address learned by IGMP/MLD snooping is removed.

  • The VLAN is affected when a multicast router port for a MAC address learned by IGMP/MLD snooping is removed.

  • The VLAN is affected when the output interface of a IPv4/IPv6 multicast route is removed.

Device-originated packets sent to an SVI (VLAN interface) are detected by a filter configured for inbound traffic on the same SVI (VLAN interface).

Workaround: This issue can be avoided by applying a filter to the Ethernet interface. If you want to apply a filter to an SVI (VLAN interfaces), you can set the filter to prevent packets transmitted by this device from being discarded by applying the source MAC address and source IP address to the detection conditions.

In case of VRF extranet communication, the subnet broadcast traffic is incorrectly forwarded, even if there is no directed-broadcast option in the “ip address” configuration.

In the “show ip arp” and “show ipv6 neighbors” commands, entries with the “I” (Incomplete) status are not displayed.

This device does not send ICMP redirect packets or ICMPv6 redirect packets.

Port-channel subinterfaces cannot be used when they are untagged. You can use them when they are tagged.

IGMP snooping and IPv4 multicast routing or MLD snooping and IPv6 multicast routing cannot be used at the same time on the same SVI (VLAN interface).

The mixed use of AC and DC power supply units is not supported.

• AC power supply: FS-AX9000G-PS-3KAC

• DC power supply: FS-AX9000G-PS-2K5DC

VLAN tag translation is not supported on the control VLAN of the Ring Protocol (AXRP).

The “update software usb-flash-file” operational command does not work.

Workaround: Copy the file to the device with the “cp usb-flash-file” operation command in advance and then update the software with the “update software” command.

The statistics for the following commands and MIBs are fixed to 0.

Operation commands:

• show ip interfaces statistics

• show ipv6 interfaces statistics

• show ip-dual interfaces statistics

• show vlan statistics

MIBs:

• ifTable(VLAN,Subinterface)

• ifXTable(VLAN, Subinterface)

Storm control configurations for the LC10S, LC25, and LC100 ports do not take effect when the device is restarted. After restarting the device, delete the storm control settings and then set them up again.

• When using VRRP with VRF, you cannot use the accept mode on the virtual router (using the configuration command “vrrp accept”).

• If you are using VRRP, do not delete all “vrrp ip” or “vrrp ipv6” commands. If you want to delete all “vrrp ip” or “vrrp ipv6” commands, delete all VRRP configurations, save the configuration, and then restart the device.

• When an interface using VRRP detects duplicate IP addresses, the following system message is produced, but the VRF ID contained in the message is fixed to 0:

  00400100 S5 Duplication of IPv4 address with the node was detected.

Do not use the “no system-source-address” configuration command on the loopback interface.

The following SNMP notifications related to the layer-2 loop detection feature are always sent to the SNMP manager, regardless of the “snmp-server notify-filter” configuration command:

• fsaxL2ldLinkDown

• fsaxL2ldLinkUp

• fsaxL2ldLoopDetection

When you get the IfIndex MIB object of the primary loopback interface, it responds with an invalid value.

The correct value: <loopback number>+20000

The invalid value: <vrf id>+20000 (“<vrf id>” is the VRF to which the loopback interface belongs.)

The following MIB information cannot be retrieved successfully or responds with incorrect values:

• fsaxModelType

• fsaxSoftware

• fsaxSystemAlarmTable

• fsaxFanUnitTable

• fsaxFanUnitLedStatus

• Part of fsaxSupBoardTable

• Part of fsaxSupCpuTable

• Policy-based mirroring cannot be used for traffic on VLANs with the Spanning Tree or Ring Protocol enabled.

• Policy-based mirroring cannot be used when the default VLAN (VLAN 1) is shut down.