Each I/O module is connected by a high-speed back plane bus to a Switch Fabric on the CPU SF module. All ingress and egress traffic, even if it's contained on the same I/O module port, passes across the high-speed back plane bus through the Switch Fabric. To guard against data bit errors, the CPU software continuously monitors the data integrity between I/O modules and CPU Switch Fabric. If an anomaly/error is detected, it could propagate a data error into the Switch Fabric, which could compromise the integrity of the egress traffic. In the event an anomaly/error is detected between an I/O module and Switch Fabric, the CPU software closely monitors all egress traffic for the next six seconds. If no errors are detected, the software will continue on as normal. However, if an error is detected, the software will reset the SWIP (Switch Fabric ASIC) and all TapMux ASICs (Application Specific Integrated Circuits), and will log: "WARNING Task=tChasServ FAD Mis-Align detected, SWIP Reset Status=8" and/or "HwCheck: Fad CRR Failed, Reset swip". And then the software will continue on as normal.
In short, this is nothing to worry about as long as you only have a few. If you start to see large numbers within a time period it may point to a hardware error on one of the cards.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.