Open Issues

ACX7509: some of the interfaces from 16x100G and 20XSFP56 will not go down after evo-pfemand restart. PR1592388

The error messages - Supercon-core 0000:xx:xx:x: Supercon scratch, are observed in the boot log of backup Routing Engine. The errors are observed only during booting of Backup Routing Engine and do not have any functional impact. These messages should be ignored.PR1594136

Timing applications cannot be restarted successfully on the ACX7100 platform with the first software version G.8275.1.PR1597120

With IGMPv3 reports received at a higher rate more than 1600 pps, packets are dropped due to control plane rate limit. Therefore, it is not possible to form 2,56,000 IGMP groups. Need to tweak DDOS configuration for reaching 2,56,000 IGMP groups. PR1599998

The output of the show system processes extensive command shows high short term CPU utilization. The values ranges from 50 percent or higher for evo-pfemand. This is a single CPU view. As the ACX7509 system is a multi-core CPU, this has no impact on performance. PR1603899

G.8275.1- G.8273.2 1PPS cTE performance test might be marginally outside class-C for PTP BC on ACX7100-48L. On each reboot, the 1PPS cTE measurement might be within the class-C measurement threshold, or might randomly be out of threshold by a few nanoseconds.PR1607381

Interfaces mapped to the same Ethernet PHY flap when any one of the interfaces speed is modified. For example, the interface 0-7 flapping when speed(10g) on port 5 was removed or applied on the 20xsfp56 card. There can be a combination of speed as initial configuration. However, a link flap is observed within the ports of the port groups if the speeds of any port are reconfigured to other speeds. To avoid such a situation all the ports of the port group can have single-speed or do not reconfigure the speed within the port group.PR1608223

The syncE to PTP and syncE to 1pps transient response marginally fails. This happens when the servo get the initial 100 nano seconds jump in one measurement window and the next 100 nano seconds in the next measurement window adjusting less initially. PR1611848

On ACX7509 devices, 1GE interface does not comes up with copper 1G SFP-T optics and this issue is specific to copper 1G cables. PR1614286

On ACX7509 devices, after multiple FPC online or offline, FPCs are going to fault state. PR1616227

If a system is fully scaled across features and firewall is also scaled, CPU consumption might be more for a small window of around 5 seconds after every 18 seconds or so. Evo-pfemand might be busy collecting the scaled firewall statistics for that 5 second window and any other applications like 'pfe-cli' trying to execute commands might fail during it. PR1629342

On ACX7100-32C and ACX7509 routers, 4x100g channels do not come up after multiple iterations Tx lase disabled alarm on. PR1631193

On ACX7509 devices, on ungraceful removal of FEB, RCB crash/vmcore might be observed. RCB comes back up after reboot.PR1636780

On ACX7509, on multiple FPC restart, link is not coming up with huge FEC errors. PR1639666

With combination of triggers like restart rpd and fpc, route object leaks are observed in Packet Forwarding Engine. PR1641947

When CLI based trigger of FPC restart is given and subsequently a Routing Engine switchover event is triggered, before the FPCs have come back online. The FPCs might not come online after switchover. It might be stuck in the offline or Fault state.PR1645305

When the original flow egresses out through an aggregate Ethernet interface, the corresponding sampled sflow frame does not reflect the correct egress port number. This occurs only when the flow egresses out through an aggregate Ethernet interface, while it works fine in a non-aggregate Ethernet egress interface and the sflow frame reflects the correct egress port.PR1647870

If FPC is restarted with multi-D scale configuration, then PICD or evo-pfemand app core will be observed occasionally. However, the app will be restarted and system will be restored automatically.PR1650302

On ACX7100 and ACX7509 devices, OAM link fault management (LFM) discovery state is not correct for some interfaces and discovery state is either Active Send Local or Fault. PR1651580

If the first port of a group used as channelised port (example port 8 from phy 3) instead of "unused" we don't see issue of particular phy going out of sync.PR1657531

G.8275.1.enh 2Way cTE performance test might be outside class-C when using channelized 25G ports with 40G ports for PTP BC on ACX7100-32C. On each reboot, the 2Way cTE measurement might be within the class-C measurement threshold, or might randomly be out of it by a few nanoseconds.PR1662367

In a dual routing engine setup, while switchover happens, there are some references that are help by the interfaces software which is not cleared. This anomaly is observed when switchover happens as a result of the primary routing engine/FEB being turned-off/rebooted. This memory leak does not have any impact on service and will be fixed in the subsequent release.PR1662411

Interface flaps are observed on performing primary role switchover using the primary Routing Engine offline button press, however, no intermittent flaps are observed after switchover. PR1668509

The traffic drop greater than 50 milliseconds is sometimes observed on an ungraceful jack out or in of primary Routing Engine, however, switchover happens and traffic resumes.PR1668780

The traffic hit can sometimes be in seconds on a switchover caused by master FEB power-fault. The expected traffic hit is less than 50 milliseconds. There is no lingering effect due to this. The system will subsequently work normally.PR1668890

The hwdre and evo-pfemand applications might crash if idmd, fabtoken and hwdre are restarted immediately after a FEB offline.PR1669130

Switchover caused by primary RCB power-fault might cause links to go down.PR1669162

In rare cases and with scaled scenarios, it is possible for Packet Forwarding Engine data path to not get properly programmed after a FEB offline or online. This can result in traffic not passing through. Workaround is to deactivate the scaled configuration, offline and online the FEB, and then activate the config again.PR1669211

In a ACX7509 system with dual Routing Engine and FEB, when there is a power fault of primary FEB, a switchover should happen and backup Routing Engine and FEB will take up primary role. Post switchover a VMCore might be generated in the new backup Routing Engine. This failure should not impact the system uptime. Post Vmcore backup Routing Engine will reboot and come back online. PR1671198

If a FEB goes to fault state due to a power-fault (real or artificially triggered for testing), then the subsequent FEB offline can take a few minutes (instead of completing within a minute for a normal offline). There is no other collateral due to this. A FEB online subsequent to the delayed offline will work normally and the FEB will become fully functional again.PR1671719

Links to backup FEB might go down on primary FEB restart. This can become a problem on a subsequent switchover. Workaround is to do an restart of the backup FEB after primary FEB has come back online (following the restart).PR1673274

On performing Graceful Routing Engine swithchover on ACX7509 device with EVPN services, some IFLs are missing. PR1646722

On triggerring Routing Engine switchover (graceful and ungraceful), large number of overlay and ref-counting ERROR messages are visible in the journalctl and syslog. These error messages start with prefix OF: ERROR. These error messages can be ignored. They do not impact the system behaviour. PR1639342