VSC8491-17 Datasheet

WAN/LAN/Backplane RXAUI/XAUI to SFP+/KR 10 GbE

SerDes PHY with IntelliSec™ and VeriTime™
 Microsemi makes no warranty, representation, or guarantee regarding the information contained herein or the suitability of
its products and services for any particular purpose, nor does Microsemi assume any liability whatsoever arising out of the
application or use of any product or circuit. The products sold hereunder and any other products sold by Microsemi have
been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications. Any
performance specifications are believed to be reliable but are not verified, and Buyer must conduct and complete all
performance and other testing of the products, alone and together with, or installed in, any end-products. Buyer shall not
Microsemi Headquarters
rely on any data and performance specifications or parameters provided by Microsemi. It is the Buyer’s responsibility to
One Enterprise, Aliso Viejo, independently determine suitability of any products and to test and verify the same. The information provided by Microsemi
CA 92656 USA hereunder is provided “as is, where is” and with all faults, and the entire risk associated with such information is entirely
Within the USA: +1 (800) 713-4113 with the Buyer. Microsemi does not grant, explicitly or implicitly, to any party any patent rights, licenses, or any other IP
Outside the USA: +1 (949) 380-6100 rights, whether with regard to such information itself or anything described by such information. Information provided in this
Sales: +1 (949) 380-6136 document is proprietary to Microsemi, and Microsemi reserves the right to make any changes to the information in this
Fax: +1 (949) 215-4996 document or to any products and services at any time without notice.
Email: sales.support@microsemi.com
www.microsemi.com
About Microsemi
©2018 Microsemi, a wholly owned Microsemi, a wholly owned subsidiary of Microchip Technology Inc. (Nasdaq: MCHP), offers a comprehensive portfolio of
subsidiary of Microchip Technology Inc. All semiconductor and system solutions for aerospace & defense, communications, data center and industrial markets.
rights reserved. Microsemi and the Products include high-performance and radiation-hardened analog mixed-signal integrated circuits, FPGAs, SoCs and
Microsemi logo are registered trademarks of ASICs; power management products; timing and synchronization devices and precise time solutions, setting the world's
Microsemi Corporation. All other trademarks standard for time; voice processing devices; RF solutions; discrete components; enterprise storage and communication
and service marks are the property of their solutions, security technologies and scalable anti-tamper products; Ethernet solutions; Power-over-Ethernet ICs and
midspans; as well as custom design capabilities and services. Learn more at www.microsemi.com.
respective owners.

VMDS-10506. 4.0 11/18

Contents
1 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Revision 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Revision 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Revision 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1 Major Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Functional Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Data Path Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1 Ingress Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.2 Egress Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.3 Interface Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Physical Medium Attachment (PMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2.1 VScope Input Signal Monitoring Integrated Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 WAN Interface Sublayer (WIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3.1 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3.2 Section Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.3 Line Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.4 SPE Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.5 Path Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3.6 Defects and Anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.7 Interrupt Pins and Interrupt Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.8 Overhead Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.9 Pattern Generator and Checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.4 10G Physical Coding Sublayer (64B/66B PCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4.1 Control Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4.2 Transmit Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.4.3 Receive Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.4.4 PCS Standard Test Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.5 1G Physical Coding Sublayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.6 IEEE 1588 Block Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.6.1 IEEE 1588 Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.6.2 IEEE 1588v2 One-Step End-to-End Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.6.3 IEEE 1588v2 Transparent Clock and Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.6.4 Enhancing IEEE 1588 Accuracy for CE Switches and MACs . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.6.5 MACsec Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.6.6 Supporting One-Step Boundary Clock/Ordinary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.6.7 Supporting Two-Step Boundary Clock/Ordinary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.6.8 Supporting One-Step End-to-End Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.6.9 Supporting One-Step Peer-to-Peer Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.6.10 Supporting Two-Step Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.6.11 Calculating OAM Delay Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.6.12 Supporting Y.1731 One-Way Delay Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.6.13 Supporting Y.1731 Two-Way Delay Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.6.14 Device Synchronization for IEEE 1588 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.6.15 Time Stamp Update Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.6.16 Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.6.17 Time Stamp Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
3.6.18 Time Stamp FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.6.19 Serial Time Stamp Output Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 i

 3.6.20 Rewriter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
3.6.21 Local Time Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.6.22 Serial Time of Day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
3.6.23 Programmable Offset for LTC Load Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.6.24 Adjustment of LTC Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3.6.25 Pulse per Second Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
3.6.26 Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.6.27 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.6.28 Accessing 1588 IP Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.7 MACsec Block Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.7.1 MACsec Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.7.2 MACsec Target Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.7.3 Formats, Transforms, and Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.7.4 MACsec Integration in PHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.7.5 MACsec Pipeline Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
3.7.6 Debug Fault Code in FCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
3.7.7 Capture FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
3.7.8 Flow Control Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
3.7.9 Media Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
3.8 Flow Control Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.9 Rate Compensating Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.10 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.11 Cross-Connect (Non-Hitless Operation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
3.12 Host-Side Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.12.1 RXAUI Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.13 Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.13.1 PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
3.13.2 Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
3.13.3 Synchronous Ethernet Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
3.14 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
3.14.1 10G LAN with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
3.14.2 10G LAN with 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
3.14.3 10G LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
3.14.4 10G WAN with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
3.14.5 10G WAN with 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
3.14.6 10G WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
3.14.7 1 GbE with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.14.8 1 GbE with 1588 and MACs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.14.9 1 GbE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.15 Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.15.1 MDIO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.15.2 SPI Slave Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
3.15.3 Two-Wire Serial (Slave) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
3.15.4 Two-Wire Serial (Master) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
3.15.5 Push Out SPI Master Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
3.15.6 GPIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
3.15.7 JTAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

4 Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5 Electrical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.1 DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.1.1 DC Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.1.2 Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.2 AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.2.1 Receiver Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 ii

 5.2.2 Transmitter Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5.2.3 Timing and Reference Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.2.4 Two-Wire Serial (Slave) Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.2.5 MDIO Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.2.6 Synchronous Time-of-Day Load/Save Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.2.7 SPI Slave Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.3 Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.4 Stress Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

6 Pin Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

6.1 Pin Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
6.2 Pin Identifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
6.3 Pins by Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

7 Package Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

7.1 Package Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.2 Thermal Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
7.3 Moisture Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

8 Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

8.1 1588 bypass switch should not be activated on the fly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2 Low-power mode and SerDes calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.3 Low-power mode should not be enabled when failover switching is enabled . . . . . . . . . . . . . . . . . . . 193
8.4 Flow control with failover switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.5 XAUI BIST Checker Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.6 SPI bus speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.7 GPIO as TOSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.8 10GBASE-KR auto negotiation and training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.9 Loopbacks in 10G WAN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.10 10/100M mode not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.11 Limited access to registers during failover cross-connect mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.12 Limited auto negotiation support in 1G mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.13 Limited 1G status reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.14 Timestamp errors due to IEEE 1588 reference clock interruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.15 RXCKOUT squelching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

9 Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 iii

Figures
Figure 10 VSC8491-17 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 11 SFP/SFP+ Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 12 Backplane Equalization Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 13 1588 Transparent Clock Line Card End-to-End PHY Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 14 1588 Boundary Clock Line Card Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Figure 15 10GBASE-KR Output Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 16 KR Test Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Figure 17 WIS Transmit and Receive Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 18 WIS Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 19 STS-192c/STM-64 Section and Line Overhead Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 20 Path Overhead Octets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 21 Primary Synchronization State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 22 Secondary Synchronization State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 23 16-bit Designations within Payload Pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 24 Pointer Interpreter State Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 25 TOSI Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 26 ROSI Timing Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 27 PCS Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 28 64B/66B Block Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 29 IEEE 1588 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 30 IEEE 1588 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 31 1588 Transparent Clock Line Card End-to-End PHY Application . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 32 Transparent Clock and Boundary Clock Line Card Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 33 1588 Boundary Clock Line Card Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 34 One-Step E-nd-to-End Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 35 Two-Step End-to-End Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 36 One-Step End-to-End Transparent Clock Mode A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 37 One-Step End-to-End Transparent Clock Mode B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Figure 38 Delay Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 39 One-Step Peer-to-Peer Transparent Clock Mode B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 40 Two-Step End-to-End Transparent Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 41 Y.1731 1DM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 42 Y.1731 One-Way Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Figure 43 Y.1731 DMM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 44 Y.1731 Two-Way Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 45 RFC6374 DMM/DMR OAM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 46 Draft-bhh DMM/DMR/1DM OAM PDU Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 47 PTP Packet Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 48 OAM Packet Encapsulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 49 TSU Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 50 Analyzer Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 51 Type II Ethernet Basic Frame Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 52 Ethernet Frame with SNAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 53 Ethernet Frame with VLAN Tag and SNAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 54 Ethernet Frame with VLAN Tags and SNAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 55 PBB Ethernet Frame Format (No B-Tag) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 56 PBB Ethernet Frame Format (1 B-Tag) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 57 MPLS Label Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 58 MPLS Label Stack within an Ethernet Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 59 MPLS Labels and Control Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 60 IPv4 with UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 61 IPv6 with UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 62 ACH Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 63 ACH Header with Protocol ID Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 64 IPSec Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 iv

Figure 65 IPv6 with UDP and IPSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 66 PTP Frame Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 67 OAM 1DM Frame Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 68 OAM DMM Frame Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 69 OAM DMR Frame Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 70 RFC6374 DMM/DMR OAM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 71 G8113.1/draft-bhh DMM/DMR/1DM OAM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 72 Serial Time Stamp/Frame Signature Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 73 Preamble Reduction in Rewriter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 74 Local Time Counter Load/Save Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 75 Standard PPS and 1PPS with TOD Timing Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 76 ToD Octet Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 77 MACsec Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 78 Secure Enterprise Infrastructure and WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 79 Secure Carrier Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 80 Secure Mobile Backhaul with IEEE 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 81 Untagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 82 Standard MACsec Transform of Untagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 83 Single-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 84 Standard MACsec Transform of Single-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 85 Dual-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 86 Standard MACsec Transform of Dual-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 87 Single-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 88 MACsec Transform to Single Tag Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 89 Dual-Tagged Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 90 MACsec Transform to Single and Dual Tag Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 91 EoMPLS with One Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 92 Standard and Advanced MACsec Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 93 EoMPLS with Two Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 94 Standard and Advanced MACsec Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 95 MACsec in PHY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 96 MACsec Egress Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 97 MACsec Ingress Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 98 VLAN Tag Bypass Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 99 EoMPLS Header Bypass Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 100 Capture FIFO Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 101 Line Back-Pressure by Remote Link Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 102 Host Back-Pressure by Remote Link Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Figure 103 Advanced Flow Control Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 104 MAC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Figure 105 Host-Side and Line-Side Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 106 Cross-Connect Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 107 Host-Side I/O Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 108 10G LAN with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Figure 109 10G LAN with 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 110 10G LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 111 10G WAN with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 112 10G WAN with 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 113 10G WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 114 1 GbE with 1588 and MACsec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 115 1 GbE with 1588 and MACs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 116 1 GbE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 117 SPI Single Register Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 118 SPI Multiple Register Reads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 119 SPI Multiple Register Writes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 120 SPI Read Following Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 121 SPI Write Following Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 122 SPI Slave Default Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 123 SPI Slave Fast Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 v

Figure 124 Two-Wire Serial Bus Reset Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 125 Two-Wire Serial Slave Register Address Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 126 Two-Wire Serial Write Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 127 Two-Wire Serial Read Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Figure 128 SFI Datacom Sinusoidal Jitter Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Figure 129 XAUI Receiver Input Sinusoidal Jitter Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 130 SFI Transmit Differential Output Compliance Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Figure 131 XAUI Output Compliance Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 132 XREFCK to Data Output Jitter Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 133 Two-Wire Serial Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 134 Timing with MDIO Sourced by STA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 135 Timing with MDIO Sourced by MMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Figure 136 Load/Save AC Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 137 SPI Interface Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 138 3-Pin Push-Out SPI Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 139 Pin Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Figure 140 Package Drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 vi

Tables
Table 141 Interface Data Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 142 Section Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 143 Framing Parameter Description and Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 144 Line Overhead Octets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 145 K2 Encodings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Table 146 SONET/SDH Pointer Mode Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 147 H1/H2 Pointer Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 148 Concatenation Indication Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 149 Pointer Interpreter State Diagram Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 150 STS Path Overhead Octets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 151 Path Status (G1) Byte for RDI-P Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 152 Path Status (G1) Byte for ERDI-P Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 153 RDI-P and ERDI-P Bit Settings and Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 154 PMTICK Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 155 Defects and Anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 156 TOSI/ROSI Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Table 157 Control Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Table 158 Flows Per Engine Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 159 Ethernet Comparator: Next Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 160 Comparator ID Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 161 Ethernet Comparator (Next Protocol) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 162 Ethernet Comparator (Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 163 MPLS Comparator: Next Word . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 164 MPLS Comparator: Per-Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 165 MPLS Range_Upper/Lower Label Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Table 166 Next MPLS Comparator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 167 Next-Protocol Registers in OAM-Version of MPLS Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 168 Comparator Field Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 169 IP/ACH Next-Protocol Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 170 IP/ACH Comparator Flow Verification Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 171 PTP Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Table 172 PTP Comparison: Common Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 173 PTP Comparison: Additions for OAM-Optimized Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Table 174 Frame Signature Byte Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 175 Frame Signature Address Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Table 176 LTC Time Load/Save Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 177 Output Pulse Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Table 178 Standard MACsec Frame Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 179 Advanced MACsec Frame Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table 180 MACsec Tag Parsing Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 181 Match Criteria and Maskable Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Table 182 Egress SA Flow Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Table 183 Ingress SA Flow Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table 184 Transform Record Format (Non-XPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Table 185 Context Control Word Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 186 Transform Record Format (XPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 187 Egress SA Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 188 Egress Global Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 189 Ingress SA Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 190 Ingress Global Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 191 Egress Per-User Global Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 192 IEEE 802.1AE Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Table 193 Ingress Per-User Global Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Table 194 FCS Fault Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 195 Ingress Global Stat Event Vector Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 vii

Table 196 Ingress SA Stat Event Vector Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Table 197 Egress Global Stat Event Vector Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Table 198 Egress SA Stat Event Vector Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Table 199 Host-Side Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 200 Failover and Broadcasting Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 201 Line-Side Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Table 202 RXAUI Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Table 203 Supported Reference Clock Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Table 204 XREFCK Frequency Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 205 Supported Clock Rates and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 206 MDIO Port Addresses Per Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 207 SPI Slave Instruction Bit Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Table 208 GPIO Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Table 209 JTAG Instructions and Register Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Table 210 LVTTL Input and Push/Pull Output DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Table 211 LVTTLOD Input and Open-Drain Output DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Table 212 Reference Clock DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Table 213 Line-Side 10G Receiver Input (SFI Point D 9.95328G) AC Characteristics . . . . . . . . . . . . . . . . . 159
Table 214 Line-Side SONET 10G Input Jitter AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 215 Host-Side RXAUI Receiver AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 216 Host-Side XAUI Receiver AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 217 Line-Side 1.25 Gbps SFI Input AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 218 Host-Side 1.25 Gbps (1000BASE-KX) Receiver Input AC Characteristics . . . . . . . . . . . . . . . . . . 163
Table 219 Line-Side 10G Transmitter Output (SFI Point B) AC Characteristics . . . . . . . . . . . . . . . . . . . . . . 163
Table 220 Transmitter SFP+ Direct Attach Copper Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . 164
Table 221 10 Gbps Transmitter 10GBASE-KR AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 222 Line-Side SONET 10G Output Jitter AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Table 223 Near-end RXAUI Transmitter Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Table 224 Far-end RXAUI Transmitter Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Table 225 Far-end XAUI Transmitter Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Table 226 Line-Side 1.25 Gbps SFI Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 227 Host-Side Transmitter 1000BASE-KX AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 228 Reference Clock AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Table 229 Two-Wire Serial Interface AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Table 230 MDIO Interface AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Table 231 Clock Output AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Table 232 Load/Save Setup and Hold Timing AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Table 233 SPI Slave Interface AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Table 234 3-Pin Push-Out SPI AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Table 235 Recommended Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Table 236 Stress Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 237 Pin Identifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 238 Thermal Resistances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Table 239 Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 viii

Revision History

1 Revision History

The revision history describes the changes that were implemented in the document. The changes are
listed by revision, starting with the most current publication.

1.1 Revision 4.1

Revision 4.1 was published in September 2018. In revision 4.1 of this document, the registers were
attached. For more information, see Registers, page 157.

1.2 Revision 4.0

Revision 4.0 was published in November 2017. The following is a summary of the changes in
revision 4.0 of this document.
• Low-voltage transistor-to-transistor logic (LVTTL) updated to low-voltage transistor-to-transistor logic
with open-drain output (LVTTLOD) where appropriate.
• The two-wire serial slave interface register address illustrations and 24-bit addressing scheme
details were updated. For more information, see Two-Wire Serial (Slave) Interface, page 150.
• Line-side 10G receiver input AC characteristics were updated. For more information, see Table 73,
page 159.
• Conditions for transmitter SFP+ direct attach copper output AC characteristics were updated. For
more information, see Table 80, page 164.
• Reference clock AC characteristics were updated. For more information, see Table 88, page 167.
• The SPI interface timing diagram was updated. For more information, see Figure 128, page 171.
• Some pin description information was updated. For more information, see Pins by Function,
page 175.
• Moisture sensitivity level (MSL) was corrected from 2 to 4. For more information, see Moisture
Sensitivity, page 192.

1.3 Revision 2.0

Revision 2.0 was published in September 2017. It was the first publication of this document.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 1

Overview

2 Overview

The VSC8491-17 device is a 10G/1G WAN/LAN/Backplane RXAUI/XAUI to SFP+/KR 10 GbE SerDes

PHY with VeriTime™ and Intellisec™. It supports IEEE 802.1AE, IEEE 802.3ae, and IEEE 1588v2.
The VSC8491-17 is an IEEE 1588v2-compliant device for timing-critical applications. It is also well suited
for optical module, copper Twinax cable, and backplane applications with support for a wide variety of
protocols, including 10 GbE LAN, 10 Gb WAN, and 1 Gb Legacy Ethernet.
The VSC8491-17 device offers a seamless integration between IEEE 1588v2 and the MACsec engine
with no loss of precision. The MACsec functionality in the VSC8491-17 device supports the
IEEE 802.1AE 128/256-bit MACsec protocols to meet the security requirements for protecting data
traversing Ethernet LANs, such as input classification, frame encryption/decryption, performance, and
latency monitoring.
VeriTime™ is Microsemi’s patent-pending timing technology that delivers the industry’s most accurate
IEEE 1588v2 timing implementation for Ethernet transceivers. The IEEE 1588v2 timing integrated in the
VSC8491-17 device is the most reliable and lowest-cost method of implementing the timing accuracy to
maintain existing timing-critical capabilities during the migration from TDM to packet-based architectures.
Complete Y.1731 OAM performance monitoring capabilities, master, slave, boundary, and transparent
clock configurations, and sophisticated classifications (including UDP, IPv4, IPv6 packets and VLAN, and
MPLS-TP encapsulation) are also supported.
The VSC8491-17 device meets the SFP+ limiting and linear SR/LR/ER/ZR/220MMF host requirements
in accordance with the SFF-8431 specifications. It also compensates for electrical and optical
impairments in SFP+ applications, along with imperfections of the PCB and connectors.
The VSC8491-17 device provides a complete suite of BIST functionality, including line and client
loopbacks, along with pattern generation and error detection. Highly flexible clocking options support
LAN and WAN operation using single 156.25 MHz reference clock rate inputs for seamless Synchronous
Ethernet support. The VSC8491-17 device also includes a failover switching capability for protection
routing, along with selectable lane ordering.
The serial side supports 1.25 Gbps and various 10 Gbps modes. Each channel consists of a receiver
(Rx) and a transmitter (Tx) subsection. Three programmable reference clock inputs (XREFCK, SREFCK,
and WREFCK) support the various modes along with clock and data recovery (CDR) in the Rx and Tx
subsections of all channels.
The following illustration shows a high-level block diagram for the VSC8491-17 device.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 2

 2.1
Overview

Figure 1 •

•
Host LC-PLL Clocking Network for Timing and Retiming Including SyncE Support Line LC-PLL

1G 1G
PCS PCS Switch
VSC8491-17 Block Diagram

SD6G

Major Applications
XAUI/RXAUI/ SD6G FC/ SD10G SFP/SFP+
4/2/1 Host Rate Line 10G
1 GbE XGXS WIS
SD6G MAC Comp MAC PCS

MACsec
SD6G Buffers

2x 2 × 6.25G 1 × 10G

1588
2x 4 × 3.125G
Line

1 × 1G
2x 1 × 1.25G
FC/

Host/Client
SD6G Host 10G
XGXS Rate Line WIS
MAC Comp MAC PCS
XAUI/RXAUI/ SD6G

MACsec
4/2/1 Buffers
1 GbE SD6G
SD6G
1G 1G
PCS PCS

VMDS-10506 VSC8491-17 Datasheet Revision 4.0

SPI/MDIO/ MDIO Two-Wire Serial Slave SPI Two-Wire Serial Master Two-Wire Serial
Two-Wire Serial

Multiple-port RXAUI/XAUI to SFI/SFP+ line cards or network interface controllers

3
Overview

• Carrier Ethernet networks requiring 1588v2 timing

• Secure data center-to-data center interconnects
• 10 GbE switch cards, router cards, and NICs
In addition, the VSC8491-17 device has the following MACsec-enabled applications:
• Secure access connections
• Secure client and access connections
• Secure connections across a LAN
• Secure data center interconnections across a WAN
• IEEE 1588 time-stamping on a MACsec port
The following illustrations show the various applications for the VSC8491-17 device.
Figure 2 • SFP/SFP+ Application
10 GbE Line Card or NIC
RXAUI/XAUI

10 GbE
1 × 10G
2/4 VSC8491-17 1 × 1G
Dual
10 GbE 2/4 SFP/SFP+/XFP
MAC/NIC

Figure 3 • Backplane Equalization Application

Switch Module

VSC8491-17 2/4
RXAUI/
1 × 10G/ 2/4 XAUI
1 × 1G RXAUI/ Switch
XAUI

10GBASE-KR
Backplane
Figure 4 • 1588 Transparent Clock Line Card End-to-End PHY Application
Ethernet Line Card System Card Ethernet Line Card

Linecard Control System Control

Processor Processor

1G
Ethernet Port SerDes PHY Packet Linecard Control
MAC
Processing Processor

10G
Ethernet Line Card Packet SerDes PHY Ethernet Port
MAC
Fabric Processing
Linecard Control
Processor

MAC or
Ethernet Port Fabric
Switch
Adapter

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 4

Overview

Figure 5 • 1588 Boundary Clock Line Card Application

Ethernet Line Card System Card Ethernet Line Card

Linecard Control System Control Linecard Control

Processor Processor Processor

1G 10G
Ethernet Port Packet Ethernet Port
SerDes PHY MAC Packet MAC SerDes PHY
Processing Fabric Processing

Boundary
Clock

2.2 Features and Benefits

The main features of the VSC8491-17 device are as follows:
• IEEE 1588v2/1731 OAM precision timing support at 1G and 10G
• Compliant to IEEE 802.3ae and SFF-8431 electrical (SFI) specifications
• IEEE 802.1AE MACsec with 128-bit and 256-bit encryption support
• 9.95 Gbps WAN, 10.3125 Gbps LAN, and 1.25 Gbps Ethernet support
• Supports all standard SFP+ applications
• Adaptive receive equalization with programmable, multitap transmit pre-emphasis
• Extended WIS support
• MDIO, SPI, and two-wire serial slave management interfaces
• Failover switching for protection routing, along with selectable lane ordering (non-hitless switching)
• VScope™ input signal monitoring integrated circuit
• Host-side and line-side loopbacks with BIST functions
• I/O programmability for lane swap, invert, amplitude, slew, pre-emphasis, and equalization
• Optional forward error correction (FEC)
• Flexible clocking options for Synchronous Ethernet support
• Passive copper cable compliant to SFF-8431 is supported for minimum transmission cost
• Pin-friendly with VSC8487-15

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 5

Functional Descriptions

3 Functional Descriptions

This section describes the functional aspects of the VSC8491-17 device, including the functional block
diagram, operating modes, and major functional blocks.
The VSC8491-17 device host-side interface is either four-lane XAUI, two-lane RXAUI, or one-lane
1 GbE. The line-side interface is 10G SFP+ or 1 GbE SFP.
Each lane has the following main sections:
• PMA
The PMA section contains the high-speed serial I/O interfaces, an input equalization circuit, a KR-
compliant output buffer, and a SerDes. Additionally, the PMA also generates all the line-side clocks,
including the clocks required for Synchronous Ethernet applications.
• WIS
The WIS section contains the framing and de-framing circuits and control and status registers to
convert the data to be IEEE 802.3ae WIS-compliant.
• 10G PCS
The 10G PCS section is composed of the PCS transmit, PCS receive, block synchronization, and
BER monitor processes. The PCS functions can be further broken down into encode or decode,
scramble or descramble, and gearbox functions, as well as various test and loopback modes.
• 1G PCS
The 1G PCS section describes the 1000BASE-X/SGMII coding and auto-negotiation processes.
There are two instances per channel, one for the host and one for the line.
• IEEE 1588
The IEEE 1588 section contains the local time counter, analyzer, time stamp, FIFO, and rewriter to
support both 1-step and 2-step clock timing, and to perform 1588 frame detection, time stamp
appending, header removal, and frame processing.
• MACsec
The MACsec section supports IEEE 802.1AE MACsec, which defines a set of protocols to meet the
security requirements for protecting data traversing Ethernet LANs. Tasks performed include input
classification, latency monitoring, frame encryption and decryption, and performance monitoring.
• MAC
The MAC block frames data for transmission over the network before passing the frame to the
physical layer interface, where it is transmitted as a stream of bits. In 10G mode, MAC is only
enabled along with MACsec. In 1G mode, MAC can be enabled with or without MACsec.
• FIFO
The FIFO section contains a rate-compensating FIFO between the line rate and the host rate.
• Flow Control Buffer
The flow control buffer performs rate compensation between the host and line interfaces when the
MACs are enabled.
• Cross Connect
The cross connect connects one port to the adjacent port to enable routing data/clock to and from
port 1 and 0. This cross connect only supports broadcasting from PMA to XAUI but NOT from XAUI
to PMA. The failover supported by this cross connect is not hitless.
• XGXS
The XGXS implements the PHY XGXS referenced in IEEE 802.3 Clause 47, and contains a
10GBASE-X PCS as defined in Clause 48. It provides the necessary translation between the
external XAUI interface and the on-chip XGMII interface. In addition to standard 4-lane XAUI, it also
supports 2-lane RXAUI/DDR-XAUI.
• XAUI/RXAUI
The XAUI and RXAUI section contains the parallel XAUI/RXAUI I/O interface and a SerDes.
• KR
The KR driver includes programmable equalization accomplished by a three-tap finite impulse
response (FIR) structure. Three-tap delays are achieved by three flip-flops clocked by a high-speed
serial clock (10 GHz in 10G mode; 1 GHz in 1G mode).

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 6

Functional Descriptions

• Loopback
The loopback sections describe the different loopbacks available in the VSC8491-17 device,
including system and network loopbacks. The various loopbacks enhance the engineering
debugging and manufacturing testing capability.
• Management
The management section contains the status and configuration registers and the serial management
interface logic to access them.

3.1 Data Path Overview

The following sections provide data path information for the VSC8491-17 device. Ingress and egress
data flow is relative to the line-side interface.

3.1.1 Ingress Operation

Data is received by the line-side interface (SFP+/1 GbE), processed by core logic, and transmitted from
the host-side interface (XAUI/RXAUI/1 GbE) in the ingress (or line-side receive) data path.
High-speed serial data is received by the PMA. Data can be equalized and is delivered to the clock
recovery unit (CRU). The received serial data must be a 66B/64B encoded ethernet frame at
10.3125 Gbps in 10G LAN mode, a SONET/SDH STS-192c frame at 9.953 Gbps in 10G WAN mode, or
8B/10B encoded data at 1.25 Gbps in 1 GbE mode.
In 10G WAN mode, the CRU data is processed by the WIS where 66B/64B encoded ethernet data is
extracted from SONET/SDH STS-192c frames and overhead bytes are processed. The extracted
payload data is then processed by the 10G PCS. In 10G LAN mode, the CRU data is processed by a
10G PCS. In 1G mode, the CRU data is processed by the line-side 1G PCS. The 1G/10G PCS data can
be optionally processed by the IEEE 1588, MACsec, and two MAC logic blocks.
In 10G LAN and WAN modes, data from the core is 8B/10B encoded by the XGXS logic and serialized in
the host-side SerDes. The host interface can be configured as a XAUI interface where four lanes of
3.125 Gbps data is transmitted, or as a RXAUI interface where two lanes of 6.25 Gbps data is
transmitted. Data is transmitted on XAUI lanes 0 and 2 when the host interface is configured to be
RXAUI.
In 1 GbE mode, data from the core is 8B/10B encoded by the host-side 1G PCS logic and serialized in
the host-side SerDes. 1.25 Gbps data is transmitted from the host interface on either XAUI lane 0 or 3.
When 1 GbE data is transmitted from XAUI lane 0, data received by the host interface must enter on lane
0. When 1 GbE data is transmitted from XAUI lane 3, data received by the host interface must enter on
lane 3.

3.1.2 Egress Operation

Data is received by the host-side interface (XAUI/RXAUI/1 GbE), processed by core logic, and
transmitted from the line-side interface (SFP+/1 GbE) in the egress (or line-side transmit) data path.
The host-side interface can be configured to receive XAUI or RXAUI data when in 10G LAN or 10G WAN
modes. Data enters the part on XAUI lanes 0 and 2 when using the RXAUI interface. The host-side
interface receives 1 GbE data when the VSC8491-17 device is in the 1G operating mode. XAUI lane 0 or
lane 3 may be selected to receive the 1.25 Gbps data at the host interface. When receiving data on XAUI
lane 0, 1 GbE data will be transmitted from XAUI lane 0 in the ingress data path. When receiving data on
XAUI lane 3, 1 GbE data will be transmitted from XAUI lane 3 in the ingress data path.
In 10G mode, a clock is recovered from each lane of XAUI/RXAUI data in the host-side SerDes. The data
is 8B/10B decoded and lane aligned in the XGXS logic, then optionally processed by the IEEE 1588,
MACsec, and two MAC logic blocks. The data is then 66B/64B encoded by the 10G PCS logic. The data
is serialized by the PMA in 10G LAN mode and transmitted from the line interface at 10.3125 Gbps.
When the WIS logic is enabled in 10G WAN mode, a SONET/SDH STS-192c frame is created using the
66B/64B encoded data as the frame's payload. The WIS data is serialized by the PMA and transmitted
from the line interface at 9.953 Gbps.
In 1G mode, a clock is recovered from 1 GbE data in the host-side SerDes. The data is 8B/10B decoded
by the host-side 1G PCS, then optionally processed by the IEEE 1588, MACsec, and two logic blocks.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 7

Functional Descriptions

The data is 8B/10B encoded by the line-side 1G PCS logic, serialized by the PMA, and transmitted from
the line interface at 1.25 Gbps.

3.1.3 Interface Data Rates

The following table shows the interface data rates supported by the VSC8491-17 device.

Table 1 • Interface Data Rates

Operating Mode Line-Side Datarate (Gbps) Host-Side Interface Host-Side Datarate (Gbps)
10G LAN 1 × 10.3125 XAUI 4 × 3.125
10G LAN 1 × 10.3125 RXAUI 2 × 6.25
10G WAN 1 × 9.95328 XAUI 4 × 3.125
10G WAN 1 × 9.95328 RXAUI 2 × 6.25
1 GbE 1 × 1.25 1 GbE 1 × 1.25

3.2 Physical Medium Attachment (PMA)

The VSC8491-17 PMA section consists of a receiver (Rx) and a transmitter (Tx) subsection. The receiver
accepts data from the serial data input RXIN and sends the parallel data to the WIS, 10G PCS, or 1G
PCS block. A data rate clock also accompanies the parallel data. The transmitter accepts parallel data
from the WIS or PCS block and transmits at serial data output TXOUT. A loopback at the data path is
also provided, connecting the Rx and the Tx subsection.
Serial data is pre-equalized in the input buffer, and clock and data are recovered in the deserializer,
which provides 32-bit data. A demux then deserializes the data into a parallel core data interface. A PLL
in the Rx subsection is used as reference for clock and data recovery. Locked to the incoming
datastream, a lane sync signal is derived from the PLL clock, which may be used for source synchronous
data transmission to one or multiple transmitters.
The Tx subsection is made up of the serializer, the output buffer, and the PLL. The high-speed serial
stream is forwarded to a 3-tap filter output buffer. The PLL in the Tx subsection is used to generate the
high-speed clock used in the serializer.
To support different data rates, a frequency synthesizer inside the Rx and Tx subsection takes the
reference clock input XREFCK and generates all necessary clock rates.
The PMA also has two fully programmable clock outputs, TXCKOUT and RXCKOUT, that may be used
to output various clock domains from the PMA. For more information about the reference clock, see
Reference Clock, page 141.

3.2.1 VScope Input Signal Monitoring Integrated Circuit

The VScope™ input signal monitoring integrated circuit displays the input signal before it is digitized by
the CDR. The two primary configurations are as follows:
• Unity Gain Amplifier monitors the 10 Gbps input signals before signal processing and equalization.
VScope input signal monitoring integrated circuit acts as a virtual scope to effectively observe the
received data signal before it has been processed. The autonomous adaptive filter taps must first be
disabled and the front-end receiver must be set for operation as a linear, unity gain amplifier. In this
mode, all DFE taps are set to zero. This mode does not require an adaptive algorithm.
• Link Monitor provides the link margin.
VScope input signal monitoring integrated circuit enables design engineers and system developers
to monitor signals remotely without disrupting the data integrity of a live data path. By monitoring the
health of a given link (optical or electrical), various types of signal degradation can be identified and
corrected.
Note: The VScope input signal monitoring integrated circuit feature is only available in the 10G operation
mode.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 8

Functional Descriptions

3.2.1.1 10GBASE-KR Output Driver

The high-speed output driver includes programmable equalization accomplished by a three-tap finite
impulse response (FIR) structure. The three-tap delays are achieved by three flip-flops clocked by a
high-speed serial clock, as shown in the following illustration. Coefficients C(–1), C(0) and C(+1) adjust
the pre-cursor, main-cursor, and post-cursor of the output waveform. The coefficients are independently
adjusted by control bits. The bits for each coefficient are decoded in a thermometer fashion to achieve
linear coefficient adjustment. The three delayed data streams, after being properly strength adjusted by
their coefficients, are summed by a summing amplifier. The output driver meets the requirements defined
in IEEE 802.3ap Clause 72.
Figure 6 • 10GBASE-KR Output Driver

DIN
T T T

CKIN

C –1 C0 C +1

decode decode decode

KR_COEFF_C–1 KR_COEFF_C0 KR_COEFF_C+1

VDD18TX

Slew
Control
Summing
Junction
decode

50 Ω 50 Ω
KR_SLEW[3:0]

TXOUTP

TXOUTN

The final output stage has 50 Ω back-termination with inductor peaking. The output slew rate is
controlled by adjusting the effectiveness of the inductors.
The test pattern for the transmitter output waveform is the square wave test pattern with at least eight
consecutive 1s. The following illustration shows the transmitter output waveform test, based on voltages
V1 through V6, ∆V2, and ∆V5.
Figure 7 • KR Test Pattern
V1
V3

V2

∆|V2
0V

∆|V5

V5

V6
V4

t1 t1 + T t1 + 2T t2 - 2T t2 - T t2 t2 + 2T t2 + 2T t3 - 2T t3 - T t3

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 9

Functional Descriptions

The output waveform is manipulated through the state of the coefficient C(-1), C(0), and C(+1).

3.3 WAN Interface Sublayer (WIS)

The WAN interface sublayer (WIS) is defined in IEEE 802.3ae Clause 50. The VSC8491-17 WIS block is
fully compliant with this specification. The VSC8491-17 offers additional controls, ports, and registers to
allow integration into a wider array of SONET/SDH equipment.
In addition to the SONET/SDH features addressed by WIS as defined by IEEE, most SONET/SDH
framers/mappers contain additional circuitry for implementing operation, administration, maintenance,
and provisioning (OAM&P). These framers/mappers also support special features to enable compatibility
with legacy SONET/SDH solutions. Because the VSC8491-17 WIS leverages Microsemi’s industry
leading framer/mapper technology, it contains suitable features for standard SONET/SDH equipment.
This includes the transmit/receive overhead serial interfaces (TOSI/ROSI) commonly used for network
customization and OAM&P support for SONET/SDH errors not contained in the WIS standard, support
for common legacy SONET/SDH implementations, and SONET/SDH jitter and timing quality.

3.3.1 Operation
WAN mode is enabled by asserting 2x0007.0 (SPI/MDIO/TWS) or wis_ctrl2.wan_mode. Status register
bit 1xA101.3 (SPI/MDIO/TWS) or Vendor_Specific_PMA_Status_2.WAN_ENABLED_status indicates
whether WAN mode is enabled or not. The Rx and Tx paths both have WAN mode enabled or disabled.
It is not possible to have WAN mode in the Tx path enabled while the Rx path is disabled, or vice versa.
The transmit portion of the WIS does the following:
• Maps data from the PCS through the WIS service interface and to the SONET/SDH synchronous
payload envelope (SPE)
• Generates path, line, and section overhead octets
• Scrambles the frame
• Transmits the frame to the PMA service interface
The receive portion of the WIS does the following:
• Receives data from the PMA service interface
• Delineates octet and frame boundaries
• Descrambles the frame
• Processes section, line, and path overhead information that contain alarms and parity errors
• Interprets the pointer field
• Extracts the payload for transmittal to the PCS through the WIS service interface
The following illustration shows the WIS block diagram.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 10

Functional Descriptions

Figure 8 • WIS Transmit and Receive Functions

W I S S e r v ic e I n te r fa c e
tx_ d a ta -u n it< 1 5:0 > r x _ d a ta- u n it< 1 5 :0 >

TR A N S M IT P A Y LO A D T R A N S M IT R E C E IV E R EC EIV E P A Y LO A D
MAP PIN G PR OC ESS PR O C ESS M A P P IN G

PRO CESS PATH

GENERATE PATH PRO CESS O VERHEAD
O V ER H EA D & FIX ED PATH
S TU FF DEFECT S REM O VE PATH
O VERHEAD &
IN S E R T P A T H C H E C K B 3 (B I P - 8 ) F IX E D S T U F F
O VERHEAD &
F IX E D S T U F F C O M P U T E B3 (B I P-8 ) P R O C E S S H1 , H 2
PO IN TER

R E M O V E L IN E
PRO CESS
G EN ER A T E LIN E P RO CESS LIN E O VERHEAD
LIN E
O VERHEAD O VERHEAD
D EFECT S

IN S E R T L IN E
O VERHEAD
C O M P U T E B2 (B I P-N ) C H E C K B 2 (B I P- N )

REM O VE
G EN ER A T E S ECT IO N P R O CES S S EC TIO N S E C T IO N
O VERHEAD O VERHEAD O VERHEAD
IN S E R T
S E C T IO N
O VERHEAD

X7 + X6 + 1 X7 + X6 + 1
SCRAMBLER DESCRAMBLER

C O M P U T E B1 (B I P-8 ) C H E C K B 1 (B I P - 8 )

tx _ d a ta -g r o u p< 1 5 :0 > s y n c_ b its< 1 5:0 >

P M A S e r v ic e I n te r fa c e

The following illustration shows the WIS frame structure.

Figure 9 • WIS Frame Structure

16, 704 Octets

576 Octets

Section
Overhead

Pointer
Path Overhead

Payload
Fixed Stuffing

9.58464 Gb/s

Line
Overhead

63
16, 640 Octets
Octets

The following illustration shows the positions of the section and line overhead octets within the WIS
frame.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 11

Functional Descriptions

Figure 10 • STS-192c/STM-64 Section and Line Overhead Structure

576 Octets

J0 Z0
A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 A2 A2 (C1)
(C1)

B1 E1 F1

D1 D2 D3

H1 H1 H1 H1 H1 H1 H2 H2 H2 H2 H2 H2 H3 H3 H3 H3 H3 H3
9
Octets B2 B2 B2 B2 B2 B2 K1 K2

D4 D5 D6

D7 D8 D9

D11 D12
D10

S1 Z2 E2

Bytes reserved for national use Bytes undefined/unused by IEEE802.3ae

M0 M1 Z2

The following illustration shows the path overhead octet positions.

Figure 11 • Path Overhead Octets

J1

B3

C2

G1

N in e
O c te ts F2

H4

Z 3 /F 3

Z4 /K 3

N1

3.3.2 Section Overhead

The section overhead portion of the SONET/SDH frame supports frame synchronization, a tandem
connection monitor (TCM) known as the Section Trace, a high-level parity check, and some OAM&P
octets. The following table lists each of the octets, including their function, specification, and related
information.
The VSC8491-17 device provides a mechanism to transmit a static value as programmed by the MDIO
interface. However, by definition, MDIO is not fast enough to alter the octet on a frame-by-frame basis.

Table 2 • Section Overhead

IEEE 802.3ae Recommended

Overhead Octet Function WIS Usage Value WIS Extension
A1 Frame alignment Supported 0xF6 Register (EWIS_TX_A1_A2) TOSI and
ROSI access.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 12

Functional Descriptions

Table 2 • Section Overhead (continued)

IEEE 802.3ae Recommended

Overhead Octet Function WIS Usage Value WIS Extension
A2 Frame alignment Supported 0x28 Register (EWIS_TX_A1_A2) TOSI and
ROSI access.
J0 Section trace Specified value For more A 1-byte, 16-byte, or 64-byte trace
information, see message can be sent using registers
Section Trace WIS_Tx_J0_Octets_1_0 to
(J0), page 17 WIS_Tx_J0_Octets_15_14,
EWIS_TX_MSGLEN, or
EWIS_Tx_J0_Octets_17_16 to
EWIS_Tx_J0_Octets_63_62 and
received using registers
WIS_Rx_J0_Octets_1_0 to
WIS_Rx_J0_Octets_15_14,
EWIS_RX_MSGLEN, and
EWIS_Rx_J0_Octets_17_16 to
EWIS_Rx_J0_Octets_63_62. TOSI and
ROSI access.
Z0 Reserved for Unsupported 0xCC Register EWIS_TX_Z0_E1 TOSI and
section growth ROSI access.
B1 Section error Supported Bit interleaved Using the TOSI, the B1 byte can be
monitoring parity - 8 bits, as masked for test purposes. For each B1
(Section BIP-8) specified in mask bit that is cleared to 0 on the TOSI
T1.416 interface, the transmitted bit is left
unchanged. For each B1 mask bit that is
set to 1 on the TOSI interface, the
transmitted bit is inverted.

Using the ROSI, the B1 error locations

can be extracted. Periodically latched
counter (EWIS_B1_ERR_CNT1-
EWIS_B1_ERR_CNT0) is available.
E1 Orderwire Unsupported 0x00 Register EWIS_TX_Z0_E1 TOSI and
ROSI access.
F1 Section user Unsupported 0x00 Register EWIS_TX_F1_D1 TOSI and
channel ROSI access.
D1-D3 Section data Unsupported 0x00 Register EWIS_TX_F1_D1 to
communications EWIS_TX_D2_D3 TOSI and ROSI
channel (DCC) access.

3.3.2.1 Frame Alignment (A1, A2)

The SONET/SDH protocol is based upon a frame structure that is delineated by the framing octets, A1
and A2. The framing octets are defined to be 0xF6 and 0x28 respectively. In the transmit direction, all
192 A1 octets are sourced from the TX_A1 (EWIS_TX_A1_A2.TX_A1) register while the A2 octets are
sourced from the TX_A2 (EWIS_TX_A1_A2.TX_A2) register.
In the receive direction, the frame aligner monitors the input bus from the PMA and performs word
alignment. The frame alignment architecture is composed of a primary and secondary state machine.
The selected frame alignment and synchronization pattern have implications on the tolerated input BER.
The higher the input BER, the less likely the frame boundary can be found. The chances of finding the
frame boundary are improved by reducing the number of A1/A2 bytes required to be detected (using a
smaller pattern width). According to the WIS specification, the minimum for all parameters allows a signal
with an error tolerance of 10-12 to be framed.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 13

Functional Descriptions

The following illustration shows the primary synchronization state diagram.

Figure 12 • Primary Synchronization State Diagram
power_on = TRUE + signal_fail = TRUE

HUNT

sync_start FALSE
in_HUNT TRUE

found_Hunt = FALSE
found_Hunt = TRUE

A1_ALIGN

in_HUNT FALSE

found_Presync = FALSE
found_Presync = TRUE

PRESYNC

sync_start TRUE

bad_sync_cnt = 1
bad_sync_cnt = m

SYNC

sync_start FALSE

bad_sync_cnt = n

The following table lists the variables for the primary state diagram. The variables are reflected in
registers EWIS_RX_FRM_CTRL1 and EWIS_RX_FRM_CTRL2 that can be alternately reconfigured.

Table 3 • Framing Parameter Description and Values

IEEE 802.3ae IEEE 802.3ae

Name Description Parameter Range Range Default
Sync_Pattern width Sequence of f f 2 to 192 0 to 16 2
consecutive A1s Exceptions:
followed immediately If f = 0, Sync_Pattern
by a sequence of f is A1 + 4 MSBs of
consecutive A2s. If A2.
f = 2, Sync_Pattern is If f = 1, Sync_Pattern
A1A1A2A2. is A1A1A2.
Hunt_Pattern width Sequence of i i 1 to 192 1 to 16. 4
consecutive A1s.
Presync_Pattern A1 width Presync_Pattern j 16 to 190 1 to 16 16
consists of a sequence If set to 0, behaves
of j consecutive A1s as if set to 1.
followed immediately If set to 17 to 31,
by a sequence of k behaves as if set
consecutive A2s. to 16.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 14

Functional Descriptions

Table 3 • Framing Parameter Description and Values (continued)

IEEE 802.3ae IEEE 802.3ae

Name Description Parameter Range Range Default
Presync_Pattern A2 width Presync_Pattern k 16 to 192 0 to 16 16
consists of a sequence 0 means only 4 MSB
of j consecutive A1s of A2 are used.
followed immediately If set to 17 to 31,
by a sequence of k behaves as if set
consecutive A2s. to 16.
SYNC state entry Number of consecutive m 4 to 8 1 to 15 4
frame boundaries If set to 0, behaves as
needed to be found if set to 1.
after entering the
PRESYNC state in
order to enter the
SYNC state.
SYNC state exit Number of consecutive n 1 to 8 1 to 15 4
frame boundary If set to 0, behaves as
location errors detected if set to 1.
before exiting the
SYNC state.

The following illustration shows the secondary synchronization state diagram.

Figure 13 • Secondary Synchronization State Diagram
power_on = TRUE + reset = TRUE + signal_fail = TRUE

WAIT

good_sync_cnt 0
bad_sync_cnt 0
octet_cnt 0

sync_start = TRUE

DELAY_1

in_HUNT = TRUE

in_HUNT = FALSE * in_HUNT = FALSE *

octet_cnt = (155520+f–k) * octet_cnt = (155520+f–k) *
found_Sync = TRUE found_Sync = FALSE

FOUND MISSED

bad_sync_cnt 0 good_sync_cnt 0
good_sync_cnt ++ bad_sync_cnt ++
octet_cnt 0 octet_cnt 0

UCT UCT

DELAY_2

in_HUNT = FALSE * in_HUNT = FALSE *

octet_cnt = 155520 * octet_cnt = 155520 *
found_Sync = TRUE found_Sync = FALSE

in_HUNT = TRUE

3.3.2.2 Loss of Signal (LOS)

WIS_STAT3.LOS alarm status is a latch-high register; back-to-back reads provide both the event as well
as status information. The LOS event also asserts register EWIS_INTR_PEND1.LOS_PEND until read.
This event can propagate an interrupt to either WIS_INTA or WIS_INTB based upon mask enable bits
EWIS_INTR_MASKA_1.LOS_MASKA and EWIS_INTR_MASKB_1.LOS_MASK.
There is no hysteresis on the LOS detection, and so it is recommended to have the system software to
implement a sliding window to check on the LOS before qualifying the presence of a signal. As an
alternative, Rx_LOS can be used from the optical module (through LOPC) to qualify the input signal. In

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 15

Functional Descriptions

addition to using analog detection, digital detection such as PCS_Rx_Fault is recommended to

determine if the input signal is good.
When the near-end device experiences LOS, it is possible to automatically transmit a remote defect
indication (RDI-L) to the far-end for notification purposes. The EWIS_RXTX_CTRL.TXRDIL_ON_LOS, if
asserted, overwrites the outgoing K2 bits with the RDI-L code. In the receive path, it is possible to trigger
an AIS-L state (alarm assertion plus forcing the payload to an all ones state) upon a detection of an LOS
condition. This is accomplished by asserting EWIS_RXTX_CTRL.RXAISL_ON_LOS.

3.3.2.3 Loss of Optical Carrier (LOPC)

The input pin LOPC can be used by external optic components to directly assert the loss of optical power
to the physical media device. Any change in level on the LOPC input asserts register
EWIS_INTR_PEND2.LOPC_PEND until read. The current status of the LOPC input pin can be read in
register EWIS_INTR_STAT2.LOPC_STAT. The LOPC input can be active high or active low by setting
the Vendor_Specific_LOPC_Control.LOPC_state_inversion_select bit appropriately. The LOPC_PEND
bit can propagate an interrupt to either WIS_INTA or WIS_INTB based upon mask enable bits
EWIS_INTR_MASKA_2.LOPC_MASKA and EWIS_INTR_MASKB_2.LOPC_MASKB.
When the near-end device experiences LOPC, it is possible to automatically transmit a remote defect
indication (RDI-L) to the far-end to notify it of a problem. The EWIS_RXTX_CTRL.TXRDIL_ON_LOPC
register bit, if asserted, overwrites the outgoing K2 bits with the RDI-L code. In the receive path, it is
possible to force the receive framer into an LOF state, thereby squelching subsequent alarms and invalid
payload data processing. This is accomplished by asserting EWIS_RX_ERR_FRC1.RXLOF_ON_LOPC.
Similar to the LOF condition forced upon an LOPC, the EWIS_RXTX_CTRL.RXAISL_ON_LOPC can
force the AIS-L alarm assertion, plus force the payload to an all ones state to indicate to the PCS the lack
of valid data upon an LOPC condition.

3.3.2.4 Severely Errored Frame (SEF)

Upon reset, the VSC8491-17 device Rx WIS enters the out-of-frame (OOF) state with both the severely
errored frame (SEF) and loss of frame (LOF) alarms active. The SEF state is terminated when the framer
enters the SYNC state. The framer enters the SYNC state after
EWIS_RX_FRM_CTRL2.SYNC_ENTRY_CNT plus 1 consecutive frame boundaries are identified. An
SEF state is declared when the framer enters the out-of-frame (OOF) state. The frame changes from the
SYNC state to the OOF state when EWIS_RX_FRM_CTRL2.SYNC_EXIT_CNT consecutive frames with
errored frame alignment words are detected. The SEF alarm condition is reported in WIS_STAT3.SEF.
This register latches high providing a combination of interrupt pending and status information within
consecutive reads.
An additional bi-stable interrupt pending bit SEF_PEND (EWIS_INTR_PEND1.SEF_PEND) is provided
to propagate an interrupt to either WIS_INTA or WIS_INTB based upon mask enable bits SEF_MASKA
(EWIS_INTR_MASKA_1.SEF_MASKA) and SEF_MASKB (EWIS_INTR_MASKB_1.SEF_MASKB).

3.3.2.5 Loss of Frame (LOF)

An LOF occurs when an out-of-frame state persists for an integrating period of
EWIS_LOF_CTRL1.LOF_T1 frames. To provide for the case of intermittent OOFs when not in the LOF
state, the integrating timer is not reset to zero until an in-frame condition persists continuously for
EWIS_LOF_CTRL1.LOF_T2 frames. The LOF state is exited when the in-frame state persists
continuously for EWIS_LOF_CTRL2.LOF_T3 frames. The LOF state is indicated by the
WIS_STAT3.LOF register being asserted. This register latches high, providing a combination of pending
and status information over consecutive reads.
An additional bi-stable interrupt pending bit, EWIS_INTR_PEND1.LOF_PEND, is provided to propagate
an interrupt to either WIS_INTA or WIS_INTB based upon mask enable bits
EWIS_INTR_MASKA_1.LOF_MASKA and EWIS_INTR_MASKB_1.LOF_MASKB.
When the near-end device experiences an LOF condition, it is possible to automatically transmit a
remote defect indication (RDI-L) to the far end to notify it of a problem. The
EWIS_RXTX_CTRL.TXRDIL_ON_LOF, if asserted, overwrites the outgoing K2 bits with the RDI-L code.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 16

Functional Descriptions

In the receive path, it is possible to force a AIS-L state (alarm assertion plus forcing the payload to an all
ones state) upon a detection of an LOF condition. This is accomplished by asserting
EWIS_RXTX_CTRL.RXAISL_ON_LOF.

3.3.2.6 Section Trace (J0)

The J0 octet often carries a repeating message called the Section Trace message. The default
transmitted message length is 16 octets whose contents are defined in WIS_TXJ0
(WIS_Tx_J0_Octets_1_0-WIS_Tx_J0_Octets_15_14). If no active message is being broadcast, a default
section trace message is transmitted. This section trace message consists of 15 octets of zeros and a
header octet formatted according to Section 5 of ANSI T1.269-2000. The header octet for the 15-octets
of zero is 0x89. The default values of WIS_TXJ0 (WIS_Tx_J0_Octets_1_0-WIS_Tx_J0_Octets_15_14)
do not contain the 0x89 value of the header octet, so software must write this value.
The J0 octet in the receive direction is assumed to be carrying a 16-octet continuously-repeating section
trace message. The message is extracted from the incoming WIS frames and stored in WIS_RXJ0
(WIS_Rx_J0_Octets_1_0-WIS_Rx_J0_Octets_15_14). The WIS receive process does not delineate the
message boundaries, thus the message might appear rotated between new frame alignment events.
The VSC8491-17 device supports two alternate message types, a single repeating octet and a 64-octet
message. The message type can be independently selected for the transmit and receive direction. The
transmit direction is configured using EWIS_TX_MSGLEN.J0_TXLEN, while
EWIS_RX_MSGLEN.J0_RX_LEN configures the receive path.
When the transmit direction is configured for a 64-octet message, the first 16 octets are programmed in
WIS_TXJ0 (WIS_Tx_J0_Octets_1_0-WIS_Tx_J0_Octets_15_14), while the 48 remaining octets are
programmed in EWIS_TXJ0 (EWIS_Tx_J0_Octets_17_16-EWIS_Tx_J0_Octets_63_62). Likewise, the
first 16 octets of the receive message are stored in WIS_RXJ0 (WIS_Rx_J0_Octets_1_0-
WIS_Rx_J0_Octets_15_14), while the other 48 octets are stored in EWIS_RXJ0
(EWIS_Rx_J0_Octets_17_16-EWIS_Rx_J0_Octets_63_62). The receive message is updated every
125 µs with the recently received octet. Any persistency or message matching is expected to take place
within the station manager.

3.3.2.7 Reserved for Section Growth (Z0)

The WIS standard does not support the Z0 octet and requires transmission of 0xCC in the octet
locations. A different Z0 value can be transmitted by configuring EWIS_TX_Z0_E1.TX_Z0. The TX_Z0
default is 0xCC.

3.3.2.8 Scrambling/Descrambling
The transmit signal (except for row 1 of the section overhead) is scrambled according to the standards
when register bit EWIS_TXCTRL2.SCR is asserted, which is the default state. When deasserted, the
scrambler is disabled.
The receive signal descrambler is enabled by default. The descrambler can be bypassed by deasserting
register bit EWIS_RX_CTRL1.DSCR_ENA.
Enabling loopback H4 and turning off the WIS scrambler and descrambler may yield an interesting data
point when debugging board setups. The CRU in the ingress PMA path would not have enough edge
transitions in the data to reliably recover the clock if the chip were receiving non-scrambled data. The
same would be true for any far-end device connected to the egress PMA if the scrambler were turned off.
The WIS scrambler and descrambler should be left on under normal operating conditions.

3.3.2.9 Section Error Monitoring (B1)

The B1 octet is a bit interleaved parity-8 (BIP-8) code using even parity calculated over the previous
STS-192c frame, post scrambling. The computed BIP-8 is placed in the following outgoing SONET frame
before scrambling.
In the receive direction, the incoming frame is processed, and a BIP-8 is calculated. The calculated value
is then compared with the B1 value received in the following frame. The difference between the
calculated and received octets are accumulated into the WIS_B1_CNT register. This counter rolls over
after the maximum count. This counter is cleared upon device reset.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 17

Functional Descriptions

The EWIS_B1_ERR_CNT1 and EWIS_B1_ERR_CNT0 registers provide a count of the number of

received B1 parity errors. This register is updated with the internal count value upon a PMTICK condition,
after which the internal counter is reset to zero. When the counter is nonzero, the
EWIS_INTR_PEND2.B1_NZ_PEND event register is asserted until read. A non-latch high version of this
event, EWIS_INTR_STAT2.B1_NZ_STAT, is also available. This event can propagate an interrupt to
either WIS_INTA or WIS_INTB based upon mask enable bits EWIS_INTR_MASKA_2.B1_NZ_MASKA
and EWIS_INTR_MASKB_2.B1_NZ_MASKB.
The B1_ERR_CNT can optionally be configured to increment on a block count basis, a maximum
increment of 1 per errored frame regardless of the number of errors received. This mode is enabled by
asserting EWIS_CNT_CFG.B1_BLK_MODE.

3.3.2.10 Section Orderwire (E1)

The WIS standard does not support the E1 octet and requires transmission of 0x00 in the octet location.
A different E1 value can be transmitted by configuring EWIS_TX_Z0_E1.TX_E1 (whose default is 0x00).

3.3.2.11 Section User Channel (F1)

The WIS standard does not support the F1 octet and requires transmission of 0x00 in the octet location.
A different F1 value can be transmitted by configuring EWIS_TX_F1_D1.TX_F1 (whose default is 0x00).

3.3.2.12 Section Data Communication Channel (DCC-S)

The WIS standard does not support the DCC-S octets and requires transmission of 0x00 in the octet
locations. Different DCC-S values can be transmitted by configuring EWIS_TX_F1_D1.TX_D1,
EWIS_TX_D2_D3.TX_D2, and EWIS_TX_D2_D3.TX_D3 (all of which default to 0x00).

3.3.2.13 Reserved, National, and Unused Octets

The VSC8491-17 device transmits 0x00 for all reserved, national, and unused overhead octets.

3.3.3 Line Overhead

The line overhead portion of the SONET/SDH frame supports pointer interpretation, a per channel parity
check, protection switching information, synchronization status messaging, far-end error reporting, and
some OAM&P octets.
The VSC8491-17 device provides a mechanism to transmit a static value as programmed by the MDIO
interface. However, by definition, MDIO is not fast enough to alter the octet on a frame-by-frame basis.
The following table lists each of the octets including their function, specification, and related information.

Table 4 • Line Overhead Octets

IEEE 802.3ae
Overhead Octet Function WIS Usage Recommended Value WIS Extension
H1-H2 Pointer Specified value SONET mode: Registers
STS-1: 0x62, 0x0A EWIS_TX_C2_H1.TX_H1 and
STS-n: 0x93, 0xFF SDH EWIS_TX_H2_H3.TX_H2 TOSI
mode: and ROSI access.
STS-1: 0x6A, 0x0A
STS-n: 0x9B, 0xFF
H3 Pointer action Specified value 0x00 Register
EWIS_TX_H2_H3.TX_H3 TOSI
and ROSI access.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 18

Functional Descriptions

Table 4 • Line Overhead Octets (continued)

IEEE 802.3ae
Overhead Octet Function WIS Usage Recommended Value WIS Extension
B2 Line error Supported BIP-8, as specified in Using the TOSI, the B2 bytes
monitoring (line T1.416 can be masked for test
BIP-1536) purposes. For each B2 mask bit
that is cleared to 0 on the TOSI
interface, the transmitted bit is
left unchanged. For each B2
mask bit that is set to 1 on the
TOSI interface, the transmitted
bit is inverted.
Using the ROSI, the B2 error
locations can be extracted.
Periodically latched counter
(EWIS_B1_ERR_CNT1-
EWIS_B1_ERR_CNT0) is
available.
K1, K2 Automatic Specified value For more information Register Registers
protection switch about K2 coding, see EWIS_TX_G1_K1.TX_K1 and
(APS) channel Table 5, page 21 EWIS_TX_K2_F2.TX_K2 TOSI
and line remote and ROSI access.
defect identifier
(RDI-L)
D4-D12 Line data Unsupported 0x00 Registers EWIS_TX_D4_D5
communications and EWIS_TX_D6_H4 TOSI
channel (DCC) and ROSI access.
S1 Synchronization Unsupported 0x0F Register
messaging EWIS_TX_S1_Z1.TX_S1 TOSI
and ROSI access.
Z1 Reserved for Unsupported 0x00 Register
Line growth EWIS_TX_S1_Z1.TX_Z1 TOSI
and ROSI access.
M0/M1 STS-1/N line M0 unsupported, 0x00/number of TOSI and ROSI access. The
remote error M1 supported detected B2 errors in the VSC8491-17 device supports a
indication (REI) receive path, as mode that uses only M1 to back
specified in T1.416 report REI-L
(EWIS_MODE_CTR.REI_MOD
E = 0) and another mode which
uses both M0 and M1 to back
report REI-L
(EWIS_MODE_CTR.REI_MOD
E = 1). For more information,
see Line Error Monitoring (B2),
page 20.
E2 Orderwire Unsupported 0x00 Register
EWIS_TX_Z2_E2.TX_E2 TOSI
and ROSI access.
Z2 Reserved for Unsupported 0x00 Register
Line growth EWIS_TX_Z2_E2.TX_Z2 TOSI
and ROSI access.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 19

Functional Descriptions

3.3.3.1 Line Error Monitoring (B2)

The B2 octet is a BIP-8 value calculated over each of the previous STS-1 channels excluding the section
overhead and pre-scrambling. As the B2 octet is calculated on an STS-1 basis, there are 192 B2 octets
within an STS-192/STM-64 frame. Each of the 192 calculated BIP-8 octets are then placed in the
outgoing SONET/SDH frame.
Note: For SONET mode, when the number of errors detected in the B2 octet of a receive frame is greater than
255, the total count of detected errors is transmitted in more than one frame. Even when no B2 errors are
detected in subsequent frames, the number of detected B2 errors going into an accumulator will be
limited to 255 if more than 255 errors are detected in a frame. The Tx framer pulls the REI-L count out of
the accumulator when REI-L is transmitted to be compliant with T1-105.
In the receive direction, the incoming frame is processed, a per STS-1 BIP-8 is calculated (excluding
section overhead and after descrambling), and then compared to the B2 value in the following frame.
Errors are accumulated in the WIS_B2_CNT1 and WIS_B2_CNT0 registers. This counter is non-
saturating and so rolls over after its maximum count. The counter is cleared only on device reset.
An additional 32-bit B2 error counter is provided in B2_ERR_CNT (EWIS_B2_ERR_CNT1 and
EWIS_B2_ERR_CNT0), which is a saturating counter and is latched and cleared based upon a PMTICK
event. Errors are accumulated from the previous PMTICK event. When the counter is nonzero, the
EWIS_INTR_PEND2.B2_NZ_PEND event register is asserted until read. A non-latch high version of this
event is available in EWIS_INTR_STAT2.B2_NZ_STAT. This event can propagate an interrupt to either
WIS_INTA or WIS_INTB, based on mask enable bits EWIS_INTR_MASKA_2.B2_NZ_MASKA and
EWIS_INTR_MASKB_2.B2_NZ_MASKB.
The B2_ERR_CNT can optionally be configured to increment on a block count basis, a maximum
increment of 1 per errored frame regardless of the number of errors received. This mode is enabled by
asserting EWIS_CNT_CFG.B2_BLK_MODE.
It is possible that two sets of B2 bytes (from two SONET/SDH frames) are received by the Rx WIS logic
in a period of time when only one M0/M1 octet is transmitted. In this situation, one of the two B2 error
counts delivered to the Tx WIS logic is discarded. This situation occurs when the receive data rate is
faster than the transmit data rate. Similarly, when the transmit data rate is faster than the receive data
rate, a B2 error count is not available for REI-L insertion into the M0/M1 octets of the transmitted
SONET/SDH frame. A value of zero is transmitted in this case. This behavior is achieved by using a
FIFO to transfer the detected B2 error count from the receive to transmit domains.
A FIFO overflow or underflow condition is not considered an error. Instead, it is recovered from gracefully,
as described above. A FIFO overflow or underflow eventually occurs unless the transmit and receive
interfaces are running at the same average data rate. Because the received and transmitted frames can
differ by, at most, 40 ppm (±20 ppm) and still meet the industry standards, this “slip” can happen no more
often than once every 3.1 seconds.

3.3.3.2 APS Channel and Line Remote Defect Identifier (K1, K2)
The K1 and K2 octets carry information regarding automatic protection switching (APS) and line remote
defect identifier (RDI-L). The K1 octet and the most significant five bits of the K2 octet contain the APS
channel information. The transmitted values can be configured at EWIS_TX_G1_K1.TX_K1 and
EWIS_TX_K2_F2.TX_K2. The default values of all zeros are compliant with the WIS standard.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 20

Functional Descriptions

The three least significant bits within the K2 octet carry the RDI-L encoding, as defined by section 7.4.1
of ANSI T1.416-1999 and as shown in the following table.

Table 5 • K2 Encodings

Indicator K2 Value for Bits 6, 7, 8 Interpretation

RDI-L 110 Remote error indication.
For the receive process, an RDI-L defect occurs after a
programmable number of RDI-L signals are received in contiguous
frames and is terminated when no RDI-L is received for the same
number of contiguous frames.
An RDI-L can be forced by asserting
EWIS_RX_ERR_FRC1.FRC_RX_RDIL.
For the transmit process, the WIS standard does not indicate when
or how to transmit RDI-L. VSC8491-17 provides the option of
transmitting K2 by programming it through the TOSI, by
programming it using the K2_TX MDIO register, or by programming
it based on the contents of the K2_TX register with bits 6, 7, and 8
modified depending on the status of the following: LOPC, LOS, LOF,
AIS-L and their associated transmit enable bits enable bits
TXRDIL_ON_LOPC, TXRDIL_ON_LOS, TXRDIL_ON_LOF and
TXRDIL_ON_AISL in register EWIS_RXTX_CTRL.
AIS-L 111 Alarm indication signal (line).
For the receive process, this is detected based on the settings of the
K2 byte. When AIS-L is detected, the WIS link status is down and
WIS_STAT3.AISL is set high. This also contributes to errored
second (ES) and severally errored second (SES) reports.
For standard WIS operation, this is never transmitted.
Idle 000 Unless RDI-L exists, the standard WIS transmits idle.
(normal)

Although the transmission of RDI-L is not explicitly defined within the WIS standard, the VSC8491-17
device allows the automatic transmission of RDI-L upon the detection of LOPC, LOS, LOF, or AIS-L
conditions. These features are enabled by asserting TXRDIL_ON_LOPC, TXRDIL_ON_LOS,
TXRDIL_ON_LOF and TXRDIL_ON_AISL in register EWIS_RXTX_CTRL.
Note: The RDI-L code of 110 is transmitted by the DUT only when Rx AIS-L is asserted. For example, if AIS-L
is detected by the DUT for five continuous frames in the Rx direction, then the RDI-L code is transmitted
for five frames in the Tx direction (not 20 frames as stated in the ANSI T1.105 specification).
The VSC8491-17 device can force a RDI-L condition independent of the K2 transmit value by asserting
EWIS_TXCTRL2.FRC_TX_RDI. Likewise, a AIS-L condition can be forced by asserting
EWIS_TXCTRL2.FRC_TX_AISL. If both conditions are forced, the AIS-L value is transmitted.
In the receive direction, the RDI-L alarm (K2[6:8] = 110, using SONET nomenclature) and the AIS-L
alarm (K2[6:8] = 111, using SONET nomenclature) are not asserted until the condition persists for a
programmable number of contiguous frames. This value is programmable at
EWIS_RX_ERR_FRC1.APS_THRES and is typically set to values of 5 or 10. The AIS-L is detected by
the receiver after the programmable number of frames is received, and results in the reporting of AIS-P.
The WIS standard defines WIS_STAT3.RDIL and WIS_STAT3.AISL as a read-only latch-high register, so
a read of a one in this register indicates that an error condition occurred since the last read. A second
read of the register provides the current status of the event as to whether the alarm is currently asserted.
EWIS_INTR_PEND1.RDIL_PEND and EWIS_INTR_PEND1.AISL_PEND assert whenever the RDI-L or
AIS-L state changes (assert or deassert). These interrupts have associated mask enable bits
(EWIS_INTR_MASKA_1.RDIL_MASKA, EWIS_INTR_MASKB_1.RDIL_MASKB,
EWIS_INTR_MASKA_1.AISL_MASKA and EWIS_INTR_MASKB_1.AISL_MASKB), which, if enabled,
propagate an interrupt to the WIS_INTA/B pins.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 21

Functional Descriptions

For test purposes, the VSC8491-17 device can induce a RDI-L condition in the receive direction
independent of the received K2 value by asserting EWIS_RX_ERR_FRC1.FRC_RX_RDIL. Likewise, a
AIS-L condition can be forced in the receive direction by asserting
EWIS_RX_ERR_FRC1.FRC_RX_AISL.

3.3.3.3 Line Data Communications Channel (D4 to D12)

The WIS standard does not support Line Data Communications Channel (L-DCC) octets (D4-D12) and
recommends transmitting 0x00 within these octets. The D4-D12 transmitted values can be programmed
in registers EWIS_TX_D4_D5 - EWIS_TX_D12_Z4. The register defaults are all 0x00. The receive L-
DCC octets are only accessible through the ROSI port.

3.3.3.4 STS-1/N Line Remote Error Indication (M0 and M1)

The M0 and M1 octets are used for back reporting the number of B2 errors received, known as remote
error indication (REI-L). The value in this octet comes from the B2 error FIFO, as discussed with the B2
octet. The WIS standard does not support the M0 octet and recommends transmitting 0x00 in place of
the M0 octet. However, the WIS standard supports the M1 octet in accordance with T1.416.
Two methods for back-reporting exist and are controlled by EWIS_TXCTRL2.SDH_TX_MODE. Because
a single frame can contain up to 1536 B2 errors while the M1 byte alone can only back report a maximum
of 255 errors, a discrepancy exists. When G707_2000_REIL is deasserted, only the M1 byte is used and
a maximum of 255 errors are back-reported. When G707_2000_REIL is asserted, two octets per frame
are used for back reporting- the M1 octet and the M0 octet (not the first STS-1 octet, but the second STS-
1 octet). In this mode, a total of 1536 errors can be back-reported per frame.
In the receive direction, the VSC8491-17 device detects and accumulates errors according to the
EWIS_MODE_CTRL.REI_MODE setting. The VSC8491-17 device deviates from the G.707 standard by
not interpreting REI-L values greater than 1536 as zero. The WIS standard defines a 32-bit REI-L
counter in registers WIS_REIL_CNT1 and WIS_REIL_CNT0. This counter is non-saturating and so rolls
over after its maximum count. The counter is cleared only on device reset.
An additional 32-bit REI-L counter is provided in registers EWIS_REIL_CNT1 and EWIS_REIL_CNT0,
which is a saturating counter and is latched and cleared based upon a PMTICK event. Errors are
accumulated since the previous PMTICK event. When the counter is nonzero, the
EWIS_INTR_PEND2.REIL_NZ_PEND event register is asserted until read. A non-latch high version of
this event (EWIS_INTR_STAT2.REIL_NZ_STAT) is also available. This event can propagate an interrupt
to either WIS_INTA or WIS_INTB based upon mask enable bits
EWIS_INTR_MASKA_2.REIL_NZ_MASKA and EWIS_INTR_MASKB_2.REIL_NZ_MASKB.
The REIL_ERR_CNT can optionally be configured to increment on a block count basis, a maximum
increment of 1 per errored frame regardless of the number of errors received. This mode is enabled by
asserting EWIS_CNT_CFG.REIL_BLK_MODE.

3.3.3.5 Synchronization Messaging (S1)

The S1 octet carries the synchronization status message and provides synchronization quality measures
of the transmission link in the least significant 4 bits. The WIS standard does not support the S1 octet and
requires the transmission of a 0x0F within the S1 octet. A value other than 0x0F can be programmed in
TX_S1 (2xE61F).

3.3.3.6 Reserved for Line Growth (Z1 and Z2)

The WIS standard does not support the Z1 or Z2 octets and requires the transmission of 0x00 in their
locations. Different Z1 and Z2 values can be transmitted by programming the values at
EWIS_TX_S1_Z1.TX_Z1 and EWIS_TX_Z2_E2.TX_Z2 respectively.

3.3.3.7 Orderwire (E2)

The WIS standard does not support the E2 octet and recommends transmitting 0x00 in place of the E2
octet. A value other than 0x00 can be transmitted by programming the intended value at
EWIS_TX_Z2_E2.TX_E2.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 22

Functional Descriptions

3.3.4 SPE Pointer

The H1 and H2 octets are used as a pointer within the SONET/SDH frame to locate the beginning of the
path overhead and the beginning of the synchronous payload envelope (SPE). Within SONET/SDH the
SPE can begin anywhere within the payload area. However, IEEE 802.3ae specifies that a transmitted
SPE must always be positioned solely within a single SONET/SDH frame. The constant pointer value of
522 decimal (0x20A) must be contained in the first channel’s H1 and H2 octets. Together these
conditions result in the H1 and H2 octets being 0x62 and 0x0A, respectively. These are the default
values of EWIS_TX_C2_H1.TX_H1 and EWIS_TX_H2_H3.TX_H2. Programming these registers with
alternate values does not alter the positioning of the SPE, but it might induce a loss of pointer (LOP-P) at
the far-end, or at least prevent the far-end from extracting the proper payload. Furthermore, the WIS
standard specifies the frame structure be a concatenated payload. For this reason, the H1 and H2 octets
in channels 2 through 192 contain the concatenation indicator.
The VSC8491-17 device supports forcing the loss of pointer (LOP-P) and path alarm indication signal
(AIS-P) state.
The WIS standard specifies that a 0×00 be transmitted in the H3 octet. An alternate value can be
transmitted by programming EWIS_TX_H2_H3.TX_H3.
The WIS specification does not limit the pointer position within the receive SONET/SDH frame to allow
interoperability to other SONET/SDH equipment. In addition to supporting the required SONET pointer
rules, the VSC8491-17 device pointer interpreter optionally supports SDH pointers. This is selectable
using the EWIS_MODE_CTRL.RX_SS_MODE bit. The following table shows the differences between
SONET and SDH modes.

Table 6 • SONET/SDH Pointer Mode Differences

SONET SDH
SS bits are ignored by the device pointer SS bits are set to 10 and are checked by the device pointer
interpreter and not used interpreter to determine the pointer type
All 192 bytes of H1 and H2 are checked by the The first 64 bytes are checked by the pointer interpreter to
pointer interpreter to determine the pointer type determine the pointer type (first Au-4 of an AU-4-64c)
Uses ‘8 out of 10’ GR-253-core objective Uses majority detect increment/decrement rule
increment/decrement rule

The H1 and H2 octets combine to form a word with several fields, as shown in Figure 14, page 24.

3.3.4.1 Bit Designations within Payload Pointer

The N bits [15:12] carry a new data flag (NDF). This mechanism allows an arbitrary change in the
location of the payload. NDF is indicated by at least three out of the four N bits matching the code ‘1001’
(NDF enabled). Normal operation is indicated by three out of the four N bits matching the code ‘0110’
(normal NDF).
The last ten bits of the pointer word (D bits and I bits) carry the pointer value. The pointer value has a
range from 0 to 782 that indicates the offset between the first byte after the H3 byte and the first byte of
the SPE.
The SS bits are located in bits 11 and 10, and are unused in SONET mode. In SDH mode, these bits are
compared with pattern ‘10’, and the pointer is considered invalid if it does not match.
Because the VSC8491-17 device only supports concatenated frames, only the first pair of bytes (H1, H2)
are called the primary pointer and have a normal format. The
rest of the H1/H2 bytes contain the concatenation indication (CI). The format for the CI is NDF enabled
with a pointer value of all ones.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 23

Functional Descriptions

Figure 14 • 16-bit Designations within Payload Pointer

H1 H2
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

N N N N S S I D I D I D I D I D

3.3.4.2 Pointer Types

The VSC8491-17 device supports five different pointer types, as described in the following table. A
normal pointer indicates the current pointer, a new data flag indicates a new pointer location, and an AIS
pointer indicates AIS. The pointer increment and pointer decrement mechanism adjusts the frequency
offset between the frame overhead and SPE. A pointer increment is indicated by a normal NDF that has
the currently accepted pointer with the I bits inverted. A pointer decrement is indicated by a normal NDF
that has the currently accepted pointer with D bits inverted.

Table 7 • H1/H2 Pointer Types

Pointer Type nnnn Value Pointer Value SS bits

Normal Three out of the four bits 0 to 782 Matching in SDH mode,
matching 0110 ignored in SONET mode
New data flag (NDF) Three out of the four bits 0 to 782 Matching in SDH mode,
matching 1001 ignored in SONET mode
AIS pointer 1111 1111 1111 11 11
Pointer increment Three out of the four bits Current pointer with Matching in SDH mode,
matching 0110 I bits inverted ignored in SONET mode
Pointer decrement Three out of the four bits Current pointer with Matching in SDH mode,
matching 0110 D bits inverted ignored in SONET mode

Table 8 • Concatenation Indication Types

Pointer Type nnnn Value Pointer Value SS bits

Normal concatenation indication Three out of the four 1111 1111 11 Matching in SDH mode,
bits matching 1001 ignored in SONET mode

AIS concatenation indication Pointer value, nnnn value, and SS bits are the same as the AIS pointer

Invalid concatenation indication Any other concatenation indication other than normal CI or AIS CI

3.3.4.3 Pointer Adjustment Rule

The VSC8491-17 device pointer interpreter adjusts the current pointer value according to rules listed in
Section 9.1.6 of ANSI T1.105-1995. In addition, no increment/decrement is accepted for at least three
frames following an increment/decrement or NDF operation.

3.3.4.4 Pointer Increment/Decrement Majority Rules

In SONET mode, the pointer interpreter uses more restrictive GR-253-CORE objective rules, as follows:
• An increment is indicated by eight or more bits matching non-inverted D bits and inverted I bits.
• A decrement is indicated by eight or more bits matching non-inverted I bits and inverted D bits.
In SDH mode, the majority rules are:
• An increment is indicated by three or more inverted I bits and two or fewer inverted D bits.
• A decrement is indicated by three or more inverted D bits and two or fewer inverted I bits.
• If three or more D bits are inverted and three or more I bits are inverted, no action is taken.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 24

Functional Descriptions

3.3.4.5 Pointer Interpretation States

The pointer interpreter algorithm for state transitions can be modeled as a finite state machine with three
states, as shown in the following illustration. The three states are normal (NORM), loss of pointer (LOP),
and alarm indication state (AIS).
Figure 15 • Pointer Interpreter State Diagram

a, b, e

NORM

b a, b

d c

LOP AIS

The conditions for transitions between these states are summarized in the following table

Table 9 • Pointer Interpreter State Diagram Transitions

Transitions States Description Required Persistence

a NORM  NORM <H1><H2>=<EEEESSPP><PPPPPPPP>. NDF 1 frame
AIS  NORM enabled with pointer in range (0 to 782). SS bit match
(if enabled).
b NORM  NORM <H1><H2>=<DDDDSSPP><PPPPPPPP>. NDF 3 frames
LOP  NORM disabled (NORM pointer) with the same pointer value
AIS  NORM in range (0 to 782). SS bit match (if enabled).
c NORM  AIS <H1><H2>=<11111111><11111111>. AIS pointer 3 frames
LOP  AIS (0xFFFF).
d NORM  LOP Anything other than transitions b and c or NDF 8 frames
AIS  LOP enabled (transition a) or AIS pointer when not in AIS
state or NORM pointer when not in NORM state or
NORM pointer with pointer value not equal to current
or increment/decrement or CONC pointer or SS bit
mismatch (if comparison is enabled).
e Justification Valid increment or decrement indication. 1 frame

3.3.4.6 Valid Pointer Definition for Interpreter State Diagram Transitions

During an AIS state, only an AIS pointer is a valid pointer. In NORM state, several definitions of “valid
pointer” for purpose of LOP detection are possible, according to GR-253-CORE. The VSC8491-17
device follows the GR-253-CORE intended definition, but adds a single normal pointer that exactly
matches the current valid pointer value.
Any change in the AIS state is reflected in the alarm bit WIS_STAT3.AISP. This latch-high register reports
both the event and status information in consecutive reads. The EWIS_INTR_PEND1.AISP_PEND bit
remains asserted until read. This event can propagate an interrupt to either WIS_INTA or WIS_INTB,

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 25

Functional Descriptions

based on mask enable bits EWIS_INTR_MASKA_1.AISP_MASKA and

EWIS_INTR_MASKB_1.AISP_MASKB.
Similarly, any change in the LOP state is reflected in the alarm bit WIS_STAT3.LOPP. This latch-high
register reports both the event and status information in consecutive reads. The
EWIS_INTR_PEND1.LOPP_PEND bit remains asserted until read. This event can propagate an
interrupt to either WIS_INTA or WIS_INTB, based upon the mask enable bits
EWIS_INTR_MASKA_1.LOPP_MASKA and EWIS_INTR_MASKB_1.LOPP_MASKB.

3.3.5 Path Overhead

The path overhead portion of the SONET/SDH frame supports an end-to-end trace identifier, a payload
parity check, a payload type indicator, a status indicator, and a user channel. The following table lists
each of the octets, including their function.
Note: The VSC8491-17 device provides a mechanism to transmit a static value as programmed by the MDIO
interface. However, by definition, MDIO is not fast enough to alter the octet on a frame-by-frame basis.
Extended WIS TOSI and ROSI do not support path overhead.

Table 10 • STS Path Overhead Octets

Overhead IEEE 802.3ae Recommended

Octet Function WIS Usage Value WIS Extension
J1 Path trace message Specified value For more A 1-, 16-, or 64-byte trace message
information, see can be sent using registers
Overhead Octet (EWIS_TX_MSGLEN.J1_TXLEN,
(J1), page 27 WIS_Tx_J1_Octets_1_0-
WIS_Tx_J1_Octets_15_14 and
EWIS_Tx_J1_Octets_17_16-
EWIS_Tx_J1_Octets_63_62) and
received using registers
(EWIS_RX_MSGLEN.J1_RX_LEN,
WIS_Rx_J1_Octets_1_0-
WIS_Rx_J1_Octets_15_14,
EWIS_Rx_J1_Octets_17_16-
EWIS_Rx_J1_Octets_63_62).TOSI
and ROSI access.
B3 Path error Supported Bit interleaved Both SONET and SDH mode B3
monitoring (path parity - 8 bits, as calculation is supported.
BIP-8) specified in
T1.416
C2 Path signal label Specified value 0x1A Register (EWIS_TX_C2_H1.TX_C2).
Supports persistency and mismatch
detection
(EWIS_MODE_CTRL.C2_EXP).
G1 Path status Supported As specified in Ability to select between RDI-P and
T1.416 ERDI-P formats.
F2 Path user channel Unsupported 0x00 Register (EWIS_TX_K2_F2.TX_F2).
H4 Multiframe indicator Unsupported 0x00 Register (EWIS_TX_D6_H4.TX_H4).
Z3-Z4 Reserved for path Unsupported 0x00 Register (EWIS_TX_D9_Z3.TX_Z3,
growth EWIS_TX_D12_Z4.TX_Z4).
N1 Tandem connection Unsupported 0x00 Register (EWIS_TX_N1.TX_N1).
maintenance and TOSI and ROSI access.
path data channel

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 26

Functional Descriptions

3.3.5.1 Overhead Octet (J1)

The J1 transmitted octet contains a 16-octet repeating path trace message whose contents are defined
in WIS Tx J1s (WIS_Tx_J1_Octets_1_0-WIS_Tx_J1_Octets_15_14). If no active message is being
broadcast, a default path trace message is transmitted, consisting of 15 octets of zeros and a header
octet formatted according to Section 5 of ANSI T1.269-2000. The header octet for the 15-octets of zero is
0x89. The default values of WIS Tx J1s do not contain the 0x89 value of the header octet, thus software
must write this value.
By default, the J1 octet in the receive direction is assumed to be carrying a 16-octet continuously
repeating path trace message. The message is extracted from the incoming WIS frames and presented
in WIS Rx J1s (WIS_Rx_J1_Octets_1_0-WIS_Rx_J1_Octets_15_14). The WIS receive process does
not delineate the message boundaries, thus the message might appear rotated between new frame
alignment events.
The VSC8491-17 device supports two alternate message types, a single repeating octet and a 64-octet
message. The message type can be independently selected for the transmit and receive direction. The
transmit direction is configured using EWIS_TX_MSGLEN.J1_TXLEN while
EWIS_RX_MSGLEN.J1_RX_LEN configures the receive path.
When the transmit direction is configured for a 64-octet message, the first 16 octets are programmed in
WIS_Tx_J1_Octets_1_0-WIS_Tx_J1_Octets_15_14, while the 48 remaining octets are programmed in
EWIS_Tx_J1_Octets_17_16-EWIS_Tx_J1_Octets_63_62. Likewise, the first 16-octets of the receive
message are stored in J1_RXMSG (WIS_Rx_J1_Octets_1_0-WIS_Rx_J1_Octets_15_14), while the
other 48 octets are stored in EWIS_Rx_J1_Octets_17_16-EWIS_Rx_J1_Octets_63_62. The receive
message is updated every 125 µs with the recently received octet. Any persistence or message
matching is expected to take place within the station manager.

3.3.5.2 STS Path Error Monitoring (B3)

The B3 octet is a bit interleaved parity-8 (BIP-8) code, using even parity, calculated over the previous
STS-192c SPE before scrambling. The computed BIP-8 is placed in the B3 byte of the following frame
before scrambling.
In the receive direction, the incoming frame is processed and a B3 octet is calculated over the received
frame. The calculated value is then compared with the B3 value received in the following frame. The
difference between the calculated and received octets are accumulated in block (maximum increment of
1 per errored frame) fashion into a B3 error register, WIS_B3_CNT. This counter is non-saturating and so
rolls over. The counter is cleared upon a device reset.
An additional 32-bit B3 error counter is provided at B3_ERR_CNT (EWIS_B3_ERR_CNT1 and
EWIS_B3_ERR_CNT0), a saturating counter that is latched and cleared based upon a PMTICK event.
Errors are accumulated starting from the previous PMTICK event. When the counter is nonzero, the
EWIS_INTR_PEND2.B3_NZ_PEND event register is asserted until read. A non-latch high version of this
event EWIS_INTR_STAT2.B3_NZ_STAT is also available. This event may propagate an interrupt to
either WIS_INTA or WIS_INTB, based on the mask enable bits EWIS_INTR_MASKA_2.B3_NZ_MASKA
and EWIS_INTR_MASKB_2.B3_NZ_MASKB.
The B3_ERR_CNT may optionally be configured to increment on a block count basis, a maximum
increment of 1 per errored frame regardless of the number of errors received. The
EWIS_CNT_CFG.B3_BLK_MODE control bit, if asserted, places the B3_ERR_CNT counter in block
increment mode.
It is possible that two sets of B3 bytes (from two SONET/SDH frames) are received by the Rx WIS logic
in a period of time when only one G1 octet is transmitted. In this situation, one of the two B3 error counts
delivered to the Tx WIS logic is discarded. This situation occurs when the receive data rate is faster than
the transmit data rate. Similarly, when the transmit data rate is faster than the receive data rate, a B3
error count is not available for REI-P insertion into the G1 octets of the transmitted SONET/SDH frame. A
value of zero is transmitted in this case. This behavior is achieved by using a FIFO to transfer the
detected B3 error count from the receive to transmit domains.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 27

Functional Descriptions

3.3.5.3 STS Path Signal Label and Path Label Mismatch (C2)
The C2 octet contains a value intended to describe the type of payload carried within the SONET/SDH
frame. The WIS standard calls for a 0x1A to be transmitted. This is the default value of
EWIS_TX_C2_H1.TX_C2.
As specified in T1.416, a path label mismatch (PLM-P), register WIS_STAT3.PLMP, event occurs when
the C2 octet in five consecutive frames contain a value other than the expected one. The expected value
is set in EWIS_MODE_CTRL.C2_EXP, whose default value 0x1A is compliant with the WIS standard.
When a value of 0x00 is accepted (received for five or more consecutive frames) the unequipped path
pending (EWIS_INTR_PEND2.UNEQP_PEND) event is asserted until read. A non-latch high version of
this event (EWIS_INTR_STAT2.UNEQP_STAT) is also available. This event can propagate an interrupt
to either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_2.UNEQP_MASKA and EWIS_INTR_MASKB_2.UNEQP_MASKB.
If the accepted value is not an unequipped label (0x00) and it differs from the programmed expected
value, EWIS_MODE_CTRL.C2_EXP, then a path label mismatch (WIS_STAT3.PLMP) is asserted.
Similarly the EWIS_INTR_PEND1.PLMP_PEND event is asserted until read. This event can propagate
an interrupt to either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_1.PLMP_MASKA and EWIS_INTR_MASKB_1.PLMP_MASKB.
Although PLMP is not a path level defect, it does cause a change in the setting of one of the ERDI-P
codes. For more information, see Table 13, page 29.

3.3.5.4 Remote Path Error Indication (G1)

The most significant four bits of the G1 octet are used for back reporting the number of B3 block errors
received at the near-end. This is typically known as path remote error indication (REI-P). The value in
this octet comes from the B3 error FIFO. The WIS standard defines a 16-bit REI-P counter, register
WIS_REIP_CNT. The WIS standard defines this counter to operate as a block counter as opposed to an
individual errored bit counter. This counter is non-saturating and so rolls over after its maximum count.
The counter does not clear upon a read, but instead only upon reset as defined in the WIS specification.
When the counter is nonzero, the EWIS_INTR_PEND2.REIP_PEND event register is asserted until
read. A non-latch high version of this event EWIS_INTR_STAT2.REIP_STAT is also available. This event
may propagate an interrupt to either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_2.REIP_MASKA and EWIS_INTR_MASKB_2.REIP_MASKB, respectively.
An additional 32-bit REI-P counter is provided at REIP_ERR_CNT (EWIS_REIP_CNT1 and
EWIS_REIP_CNT0), which is a saturating counter, and is latched and cleared based upon a PMTICK
event. Errors are accumulated since the previous PMTICK event. When the counter is nonzero, the
EWIS_INTR_PEND2.REIP_NZ_PEND event register is asserted until read. A non-latch high version of
this event (EWIS_INTR_STAT2.REIP_NZ_STAT) is also available. This event may propagate an
interrupt to either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_2.REIP_NZ_MASKA and EWIS_INTR_MASKB_2.REIP_NZ_MASKB,
respectively.
The REIP_ERR_CNT may optionally be configured to increment on a block count basis, a maximum
increment of 1 per errored frame, regardless of the number of errors received. This mode is enabled by
asserting EWIS_CNT_CFG.REIP_BLK_MODE.

3.3.5.5 Path Status (G1)

In addition to back-reporting the far-end B3 BIP-8 error count, the G1 octet carries status information
from the far-end device known as path remote defect indicator (RDI-P). T1.416 allows either support of 1-
bit RDI-P or 3-bit ERDI-P, but indicates ERDI-P is preferred. The VSC8491-17 device supports both
modes and may be independently configured for the Rx and Tx directions by configuring
EWIS_MODE_CTRL.RX_ERDI_MODE and EWIS_TXCTRL2.ERDI_TX_MODE. ERDI-P is the default
for both directions.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 28

Functional Descriptions

The following tables show the different structures for this octet.

Table 11 • Path Status (G1) Byte for RDI-P Mode

G1 REI (B3) RDI-P Reserved Spare

1 2 3 4 5 6 7 8
Remote Error Indicator count from B3 Remote Defect Set to 00 by Ignored by
(0–8 value) indicator transmitter receiver

Table 12 • Path Status (G1) Byte for ERDI-P Mode

G1 REI (B3) ERDI-P Spare

1 2 3 4 5 6 7 8
Remote Error Indicator count from B3 Enhanced Remote Defect Ignored by
(0–8 value) Indicator (see following table) receiver

Enhanced RDI is defined for SONET-based systems as listed in GR-253-CORE (Issue 3), reproduced
here in the following table, and as a possible enhancement of SDH-based systems (G.707/Y.1322
(10/2000) Appendix VII (not an integral part of that recommendation)).

Table 13 • RDI-P and ERDI-P Bit Settings and Interpretation

Priority of
G1 Bits 5, 6, and 7 ERDI-P Codes Trigger Interpretation
000/011 Not applicable No defects. No RDI-P defect
100/111 Not applicable Path alarm indication signal (AIS-P). The One-bit RDI-P
remote device sends all ones for H1, H2, H3, defect
and the entire STS SPE.
Path loss of pointer (LOP-P).
001 4 No defects. No ERDI-P defect
010 3 Path label mismatch (PLM-P). Path loss of code ERDI-P payload
group delineation (LCD-P). defect
101 1 Path alarm indication signal (AIS-P). The ERDI-P server
remote device sends all ones for H1, H2, H3 defect
and entire STS SPE.
Path loss of pointer (LOP-P).
110 2 Path unequipped (UNEQ-P). The received C2 ERDI-P
byte is 0x00. connectivity
Path trace identifier mismatch (TIM-P). This defect
error is not automatically generated, but can be
forced using MDIO.

In the receive direction, with EWIS_MODE_CTRL.RX_ERDI_MODE = 0, an RDI-P defect is the

occurrence of the RDI-P signal in ten contiguous frames. An RDI-P defect terminates when no RDI-P
signal is detected in ten contiguous frames. An RDI-P event asserts
EWIS_INTR_PEND2.FERDIP_PEND until read. A non-latch high version of the far-end RDI-P status can
be found in EWIS_INTR_STAT2.FERDIP_STAT. This event may propagate an interrupt to either
WIS_INTA or WIS_INTB, based on the mask enable bits EWIS_INTR_MASKA_2.FERDIP_MASKA and
EWIS_INTR_MASKB_2.FERDIP_MASKB.
When EWIS_MODE_CTRL.RX_ERDI_MODE = 1, an ERDI-P defect is the occurrence of any one of
three ERDI-P signals in ten contiguous frames. An ERDI-P defect terminates when no ERDI-P signal is
detected in ten contiguous frames.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 29

Functional Descriptions

The 010 code triggers the latch high register bit WIS_STAT3.FEPLMP_LCDP. It also asserts
EWIS_INTR_PEND1.FEPLMP_LCDP_PEND until read. This event may propagate an interrupt to either
WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_1.FEPLMP_LCDP_MASKA and
EWIS_INTR_MASKB_1.FEPLMP_LCDP_MASKB, respectively.
The 101 code triggers the latch high register bit WIS_STAT3.FEAISP_LOPP. It also asserts
EWIS_INTR_PEND1.FEAISP_LOPP_PEND until read. This event may propagate an interrupt to either
WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_1.FEAISP_LOPP_MASKA and EWIS_INTR_MASKB_1.FEAISP_LOPP_MASKB,
respectively.
The 110 code asserts the EWIS_INTR_PEND2.FEUNEQP_PEND until read. A non-latch-high version of
this register (EWIS_INTR_STAT2.FEUNEQP_STAT) is also available. This event may propagate an
interrupt to either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_2.FERDIP_MASKA and EWIS_INTR_MASKB_2.FERDIP_MASKB, respectively.

3.3.5.6 Path User Channel (F2)

The WIS standard does not support the F2 octet and recommends transmitting 0x00 in place of the F2
octet. A value other than 0x00 may be transmitted by programming the intended value at
EWIS_TX_K2_F2.TX_F2.

3.3.5.7 Multi-frame Indicator (H4)

The WIS standard does not support the H4 multi-frame octet and recommends transmitting 0x00 in place
of the H4 octet. A value other than 0x00 may be transmitted by programming the intended value at
EWIS_TX_D6_H4.TX_H4.

3.3.5.8 Reserved for Path Growth (Z3-Z4)

The WIS standard does not support the Z3-Z4 octets and recommends transmitting 0x00 in their place. A
value other than 0x00 may be transmitted by programming the intended value at
EWIS_TX_D9_Z3.TX_Z3 and EWIS_TX_D12_Z4.TX_Z4 respectively.

3.3.5.9 Tandem Connection Maintenance/Path Data Channel (N1)

The WIS standard does not support the N1 octet and recommends transmitting 0x00 in place of the N1
octet. A value other than 0x00 may be transmitted by programming the intended value at
EWIS_TX_N1.TX_N1.

3.3.5.10 Loss of Code Group Delineation

After the overhead is stripped, the payload is passed to the PCS. If the PCS block loses synchronization
and cannot delineate valid code groups, the PCS passes a loss of code group delineation (LCD-P) alarm
to the WIS. This alarm triggers the latch high register bit WIS_STAT3.LCDP. It also asserts
EWIS_INTR_PEND1.LCDP_PEND until read. This event may propagate an interrupt to either WIS_INTA
or WIS_INTB, based on the mask enable bits EWIS_INTR_MASKA_1.LCDP_MASKA and
EWIS_INTR_MASKB_1.LCDP_MASKB, respectively.
The WIS specification calls for a LCD-P defect persisting continuously for more than 3 ms to be back
reported to the far-end. Upon device reset, a LCD-P is back reported until the PCS signals that valid
code groups are being delineated. The LCD-P defect deasserts (and is not back reported) after the
condition is absent continuously for at least 1 ms.

3.3.5.11 Reading Statistical Counters

The VSC8491-17 device contains several counters that may be read using the MDIO interface. For each
error count, there are two sets of counters. The first set is the standard WIS counter implemented
according to IEEE 802.3ae, and the second set is for statistical counts using PMTICK.
To read the IEEE 802.3ae counters, the station manager must read the most significant register of the
32-bit counter first. This read action latches the internal error counter value into the MDIO readable
registers. A subsequent read of the least significant register does not latch new values, but returns the
value latched at the time of the most significant register read.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 30

Functional Descriptions

It may be difficult to get a clear picture of the timeframes in which errors were received because the IEEE
802.3ae counters are independently latched. The PMTICK counters are all latched together, thereby
providing a complete snapshot in time. When PMTICK is asserted, the internal error counter values are
copied into their associated registers and the internal counters are reset.
There are three methods of asserting PMTICK.
• The station manager may asynchronously assert EWIS_PMTICK_CTRL.PMTICK_FRC to latch the
values at a given time, regardless of the EWIS_PMTICK_CTRL.PMTICK_ENA setting.
• The VSC8491-17 device may be configured to latch and clear the statistical counters at a periodic
interval as determined by the timer (count) value in EWIS_PMTICK_CTRL.PMTICK_DUR. In this
mode, the EWIS_PMTICK_CTRL.PMTICK_SRC must be configured for internal mode and the
EWIS_PMTICK_CTRL.PMTICK_ENA bit must be asserted. The receive path clock is used to drive
the PMTICK counter, thus the periodicity of the timer can vary during times of loss of lock and loss of
frame.
• The VSC8491-17 device may be configured to latch and clear the statistical counters at the
occurrence of a rising edge detected at a GPIO pin configured as a PMTICK input pin. In this mode,
the EWIS_PMTICK_CTRL.PMTICK_SRC bit must be deasserted, and the
EWIS_PMTICK_CTRL.PMTICK_ENA must be asserted. Corresponding GPIO must be configured
as the PMTICK input pin.
Regardless of EWIS_PMTICK_CTRL.PMTICK_SRC, when the PMTICK event occurs, the
EWIS_INTR_PEND2.PMTICK_PEND is asserted until read. This event may propagate an interrupt to
either WIS_INTA or WIS_INTB, based on the mask enable bits
EWIS_INTR_MASKA_2.PMTICK_MASKA and EWIS_INTR_MASKB_2.PMTICK_MASKB, respectively.
Given the size of the error counters and the maximum allowable error counts per frame, care must be
taken in the frequency of polling the registers to ensure accurate values. All PMTICK counters saturate at
their maximum values.

Table 14 • PMTICK Counters

Maximum Maximum
Increase Increase
Count Per Count Per Time Until
Counter Name Description Registers Frame Second Overflow
B1_ERR_CNT B1 section error count EWIS_B1_ERR_CNT1 8 64,000 67,109
EWIS_B1_ERR_CNT0
B2_ERR_CNT B2 line error count EWIS_B2_ERR_CNT1 1536 12,288,000 350
EWIS_B2_ERR_CNT0
B3_ERR_CNT B3 path error count EWIS_B3_ERR_CNT1 8 64,000 67,109
EWIS_B3_ERR_CNT0
EWIS_REIP_CNT Far-end B3 path error count EWIS_REIP_CNT1 8 64,000 67,109
EWIS_REIP_CNT0
EWIS_REIL_CNT Far-end B2 line error count EWIS_REIL_CNT1 1536 12,288,000 350
EWIS_REIL_CNT0

Both individual and block mode accumulation of B1, B2, and B3 error indications are supported and
selectable using the control bits EWIS_CNT_CFG.B1_BLK_MODE, EWIS_CNT_CFG.B2_BLK_MODE,
and EWIS_CNT_CFG.B3_BLK_MODE. In individual accumulation mode 0, the counter is incremented
for each bit mismatch between the calculated B1, B2, and/or B3 error and the extracted B1, B2, and/or
B3. In block accumulation mode 1, the counter is incremented only once for any nonzero number of bit
mismatches between the calculated B1, B2, and/or B3 and the extracted B1, B2, and/or B3 (maximum of
one error per frame).

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 31

Functional Descriptions

3.3.6 Defects and Anomalies

All defects and anomalies listed in the following table can be forced and masked by the user. The
VSC8491-17 device does not automatically generate TIM-P, but does support forcing defects using
MDIO.

Table 15 • Defects and Anomalies

Defect or
Anomaly Description Type Force Bit Status Bit
Far-end PLM-P These two errors are indistinguishable when Far-end defect EWIS_RX_ER WIS_STAT3.
or LCD-P reported by the far-end through the G1 octet R_FRC2.FRC_ FEPLMP_LC
(ERDI-P), because the far-end reports both RX_FE_PLMP DP
PLM-P and LCD-P with the same error code.
Far-end AIS-P These two errors are indistinguishable when Far-end defect EWIS_RX_ER WIS_STAT3.
or LOP-P reported by the far-end through the G1 octet R_FRC2.FRC_ FEAISP_LOP
(ERDI-P), because the far-end reports both RX_FE_AISP P
AIS-P and LOP-P with the same error code.
PLM-P Path label mismatch. The detection and Near-end EWIS_RX_ER WIS_STAT3.
reporting of the PLM-P defect follows section defect; R_FRC2.FRC_ PLMP
7.5 of ANSI T1.416-1999. propagated to RX_PLMP
PCS
AIS-L Generated on LOPC, LOS, LOF, if enabled by Near-end defect The AIS-L EWIS_RX_E
EWIS_RXTX_CTRL.RXAISL_ON_LOPC, defect is only RR_FRC1.F
EWIS_RXTX_CTRL.RXAISL_ON_LOS, processed and RC_RX_AISL
EWIS_RXTX_CTRL.RXAISL_ON_LOF, or reported by the /WIS_STAT3.
when forced by user. WIS Receive AISL
process; it is
never
transmitted by
the WIS
Transmit
process,
according to
IEEE 802.3ae.
AIS-P Path alarm indication signal. Near-end EWIS_RX_ER WIS_STAT3.
defect; R_FRC1.FRC_ AISP
propagated to RX_AISP
PCS
LOP-P Path loss of pointer. Nine consecutive invalid Near-end EWIS_RX_ER WIS_STAT3.
pointers result in loss of pointer detection. See defect; R_FRC1.FRC_ LOPP
Figure 15, page 25 for the pointer interpreter propagated to RX_LOP
state machine. PCS
LCD-P Path loss of code group delineation. See Near-end defect EWIS_RX_ER WIS_STAT3.
Table 13, page 29. This is also reported to the R_FRC2.FRC_ LCDP
far-end if it persists for at least 3 ms. LCDP
LOPC Loss of optical carrier alarm. This is an input Near-end defect EWIS_RX_ER EWIS_INTR_
from the XFP module’s loss of signal output. R_FRC1.FRC_ STAT2.LOPC
The polarity can be inverted for use with other LOPC _STAT
module types. This defect can be used
independently or in place of LOS.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 32

Functional Descriptions

Table 15 • Defects and Anomalies (continued)

Defect or
Anomaly Description Type Force Bit Status Bit
LOS The PMA circuitry detects a loss of signal (LOS) Near-end defect EWIS_RX_ER WIS_STAT3.
defect if the input signal falls below the assert R_FRC1.FRC_ LOS
threshold. When a PMA LOS is declared the LOS
framer is held in reset to prevent it from looking
for a frame boundary.
SEF Severely errored frame. Generated when Near-end EWIS_RX_ER WIS_STAT3.
device cannot frame to A1 A2 pattern. SEF defect; R_FRC2.FRC_ SEF
indicates synchronization process is not in the propagated to RX_SEF
SYNC state, as defined by the state diagram of PCS
IEEE 802.3ae clause 50.4.2.
LOF Generated when SEF persists for 3 ms. Near-end defect EWIS_RX_ER WIS_STAT3.
Terminated when no SEF occurs for 1 ms to R_FRC2.FRC_ LOF
3 ms. RX_LOF
B1 PMTICK BIP-N(S) - 32-bit near-end section BIP error Near-end EWIS_RX_ER EWIS_INTR_
error count is counter is nonzero. anomaly R_FRC2.FRC_ STAT2.B1_N
nonzero RX_B1 Z_STAT
B2 PMTICK BIP-N(L) - 32-bit near-end line BIP error Near-end EWIS_RX_ER EWIS_INTR_
error count is counter is nonzero. anomaly R_FRC2.FRC_ STAT2.B2_N
nonzero RX_B2 Z_STAT
B3 PMTICK BIP-N(P) - 32-bit near-end path BIP error Near-end EWIS_RX_ER EWIS_INTR_
error count is counter is nonzero. anomaly R_FRC2.FRC_ STAT2.B3_N
nonzero RX_B3 Z_STAT
REI-L Line remote error indicator octet is nonzero. Far-end EWIS_RX_ER EWIS_INTR_
Far-end BIP-N(L). anomaly R_FRC2.FRC_ STAT2.REIL_
RX_REIL STAT
REI-L PMTICK Line remote error indicator is nonzero. Far-end Far-end EWIS_RX_ER EWIS_INTR_
error count is BIP-N(L). anomaly R_FRC2.FRC_ STAT2.REIL_
nonzero REIL NZ_STAT
RDI-L Line remote defect indicator. Far-end defect EWIS_RX_ER WIS_STAT3.
R_FRC1.FRC_ RDIL
RX_RDIL
REI-P Path remote error indicator octet is nonzero. Far-end EWIS_RX_ER EWIS_INTR_
Far-end BIP-N(P). anomaly R_FRC2.FRC_ STAT2.REIP_
RX_REIP STAT
REI-P PMTICK Path remote error indicator. Far-end BIP-N(P). Far-end EWIS_RX_ER EWIS_INTR_
error count is anomaly R_FRC2.FRC_ STAT2.REIP_
nonzero REIP NZ_STAT
UNEQ-P Unequipped path. Near-end defect EWIS_RX_ER EWIS_INTR_
R_FRC2.FRC_ STAT2.UNEQ
RX_UNEQP P_STAT
Far-end Far-end unequipped path. Far-end defect EWIS_RX_ER EWIS_INTR_
UNEQ-P R_FRC2.FRC_ STAT2.FEUN
RX_FE_UNEQ EQP_STAT
P

3.3.7 Interrupt Pins and Interrupt Masking

The VSC8491-17 device generates interrupts for each defect and anomaly. The interrupts for the BIP
error counts (B1, B2, and B3 counters) and the interrupts for the far-end error counts (REI-L and REI-P)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 33

Functional Descriptions

are generated when the PMTICK counters become nonzero. Mask enable bits propagate the interrupt
pending event to GPIO pins configured as WIS_INTA and WIS_INTB. Each event may be optionally
masked for each WIS_INTA/B pin.
The WIS_INTA and WIS_INTB signals are routed off-chip through GPIO pins. Many specialized
functions share the GPIO pins. The WIS_INTA and WIS_INTB signals do not go to dedicated pins.
For each defect or anomaly defined in IEEE 802.3ae, the VSC8491-17 device supports the standard WIS
register. In addition, the VSC8491-17 device supports another set of registers in the WIS Vendor Specific
area. These registers provide a STATUS bit to indicate the current real-time status of the event, a
PENDING bit to indicate if the STATUS bit has changed state, and two mask enable bits for each
interrupt pin (WIS_INTA and WIS_INTB). The STATUS bit is set if and only if the interrupt currently
exists. This STATUS bit does not latch.
The defects and anomalies are constructed in a hierarchy such that lower order alarms are squelched
when higher order events are detected. For more information about the dependencies between
squelches and events, see the WIS interrupt registers.

3.3.8 Overhead Serial Interfaces

The VSC8491-17 device includes provisions for off-chip processing of the critical SONET/SDH transport
overhead 9-bit words through two independent serial interfaces. The transmit overhead serial interface
(TOSI) is used to insert 9-bit words into the transmit frames, and the receive overhead serial interface
(ROSI) is used to recover the 9-bit words from the received frames. Each interface consists of three pins:
a clock output, a frame pulse output, and a data input (Tx) /output (Rx). These I/O are LVTTL compatible
for easy connection to an external device such as an FPGA.
Note: Extended WIS TOSI and ROSI do not support path overhead bytes.
The TOSI / ROSI signals are routed off-chip through GPIO pins. If the ROSI/TOSI interfaces are to be
used, there are no GPIO pins left in the design for any other function—loss-of-lock for Sync-E
applications, activity LED drivers, WIS_interrupts, or two-wire serial (slave) interface.
All references to TCLKOUT, TFPOUT, TDAIN, RCLKOUT, RFPOUT and RDAOUT are the TOSI/ROSI
signals routed through GPIO pins.

3.3.8.1 Transmit Overhead Serial Interface (TOSI)

The TOSI port enables the user to individually program 222 separate 9-bit words in the SONET/SDH
overhead. The SONET/SDH frame rate is 8 kHz as signaled by the frame pulse (TFPOUT) signal. The
TOSI port is clocked from a divided-down version of the WIS transmit clock made available on
TCLKOUT. To provide a more standard clock rate, 9-bit dummy words are added per frame, resulting in a
clock running at one five-hundred-twelfth of the line rate (or 19.44 MHz). For each 9-bit word, the external
device indicates the desire to transmit that byte by using an enable indicator bit (EIB) that is appended to
the beginning of the 9-bit word. If EIB = 0, the data on the serial interface is ignored for that overhead 9-
bit word. If EIB = 1, the serial interface data takes precedence over the value generated within the
VSC8491-17 device. The EIB is present before the 9-bit dummy words too, however its value has no
effect as the 9-bit dummy words are ignored within the device. The first EIB bit should be transmitted by
the external device on the first rising edge of TCLKOUT after TFPOUT, as shown in the following
illustration. The data should be provided with the most significant bit (MSB) first. After reception of the
TOSI data for a complete frame, the values are placed in the overhead for the next transmitted frame.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 34

Functional Descriptions

Figure 16 • TOSI Timing Diagram

TCLKOUT

TFPOUT

Padding A1 A1 A1 A1
TDAIN
Dummy Bits EIB Bit 1 Bit 2 Bit 3

Some 9-bit words are error masks, such that the transmitted 9-bit word is the XOR of the TOSI 9-bit word
and the pre-defined value within the chip if the EIB is enabled. This feature is best used for test purposes
only.
The order of the 9-bit word required by the TOSI port is summarized in the following table, where the
number of registers is the number of bytes on the serial interface and the number of bytes is the number
of STS channels on which the byte is transmitted. For H1 and H2 pointers, bytes 2 to 192 are
concatenation indication bytes consistent with STS-192c frames. There are not 192 different point
locations as in STS-192 frames.

Table 16 • TOSI/ROSI Addresses

TOSI/
ROSI
9-Bit Byte Number of Number
Byte Name Word Order Registers of Bytes Type
Frame boundary A1 0 1 192 Programmable byte that is
identical for all locations
Frame boundary A2 1 1 192 Programmable byte that is
identical for all locations
Section trace J0 2 1 1 Programmable byte
Section growth Z0 3 1 191 Programmable byte that is
identical for all locations
Dummy byte 4 1 1 Programmable byte
Section BIP-8 B1 5 1 1 TOSI inserts error mask; ROSI
extracts XOR of B1 value and
received data
Orderwire E1 6 1 1 Programmable byte
Section user channel F1 7 1 1 Programmable byte
Dummy byte 8 1 1 Programmable bytes
Section DCC 1 D1 9 1 1 Programmable byte
Section DCC 2 D2 10 1 1 Programmable byte
Section DCC 3 D3 11 1 1 Programmable byte
Dummy byte 12 1 1 Programmable byte
Pointer 1 H1 13 1 1 Programmable byte affecting the
first H1 byte

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 35

Functional Descriptions

Table 16 • TOSI/ROSI Addresses (continued)

TOSI/
ROSI
9-Bit Byte Number of Number
Byte Name Word Order Registers of Bytes Type
Pointer 2 H2 14 1 1 Programmable byte affecting the
first H2 byte
Pointer action H3 15 1 192 Programmable byte that is
identical for all locations
Dummy byte 16 1 1 Programmable byte
Line BIP-8 B2 17 to 208 192 192 TOSI inserts error mask for each
byte; ROSI extracts XOR of B2
value and received data for each
byte
Automatic protection K1 209 1 1 Programmable byte
switching (APS)
channel and remote
defect indicator (RDI)
Automatic protection K2 210 1 1 Programmable byte
switching (APS)
channel and remote
defect indicator (RDI)
Dummy byte 211 1 1 Programmable byte
Line DCC 4 D4 212 1 1 Programmable byte
Line DCC 5 D5 213 1 1 Programmable byte
Line DCC 6 D6 214 1 1 Programmable byte
Dummy byte 215 1 1 Programmable byte
Line DCC 7 D7 216 1 1 Programmable byte
Line DCC 8 D8 217 1 1 Programmable byte
Line DCC 9 D9 218 1 1 Programmable byte
Dummy byte 219 1 1 Programmable byte
Line DCC 10 D10 220 1 1 Programmable byte
Line DCC 11 D11 221 1 1 Programmable byte
Line DCC 12 D12 222 1 1 Programmable byte
Dummy byte 223 1 1 Programmable byte
Synchronization S1 224 1 1 Programmable byte
message
Growth 1 Z1 225 1 191 Programmable byte that is
identical for all locations
Growth 2 Z2 226 1 190/191 Programmable byte that is
identical for all locations;
dependent upon 2xEC40.12
STS-1 REI-L M0 227 1 1 Programmable byte
STS-N REI-L M1 228 1 1 Programmable byte
Orderwire 2 E2 229 1 1 Programmable byte
Dummy byte 230 1 1 Programmable byte

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 36

Functional Descriptions

Table 16 • TOSI/ROSI Addresses (continued)

TOSI/
ROSI
9-Bit Byte Number of Number
Byte Name Word Order Registers of Bytes Type
Padding dummy bytes 231 to 39 No function
269

3.3.8.2 Receive Overhead Serial Interface (ROSI)

The ROSI port extracts the same 222 overhead 9-bit words from the SONET/SDH frame, and consists of
the clock output (RCLKOUT), frame pulse output (RFPOUT), and data output (RDAOUT). The ROSI port
is clocked from a divided-down version of the WIS receive clock, and is valid during in-frame conditions
only. As with the TOSI port, 9-bit dummy words are provided each frame period resulting in a 19.44 MHz
RCLKOUT frequency. For each 9-bit word, including the 9-bit dummy words, an extra 0 bit is added at
the beginning of each byte so that the TOSI and ROSI clock rates are identical. The first stuff bit for each
frame is transmitted by RDAOUT on the first rising edge of RCLKOUT after the frame pulse (RFPOUT),
as shown in the following illustration.
Because the receive path overhead can be split across two frames, the VSC8491-17 device buffers the
overhead for an additional frame time so that a complete path overhead is presented. Table 16, page 35
outlines the order for each of the 9-bit words presented on the ROSI port. With the exception of the
M0/M1 9-bit words, the extracted 9-bit words are from the first channel position. In place of parity and
error 9-bit words, the VSC8491-17 device outputs the result of an XOR between the calculated BIP and
the received value. Therefore, a count of ones within each of the BIP 9-bit words should correspond with
the internal error accumulators. The following illustration shows the functional timing for the ROSI port.
Figure 17 • ROSI Timing Diagram

RCLKOUT

RFPOUT

Padding ‘0’ A1 A1 A1
RDAOUT Dummy Bits Stuff Bit 1 Bit 2 Bit 3

3.3.9 Pattern Generator and Checker

The VSC8491-17 device implements the square wave, PRBS31, and mixed-frequency test patterns as
described in section 50.3.8 of IEEE 802.3ae as well as the test signal structure (TSS) and continuous
identical digits (CID) pattern.
The square wave pattern is selected asserting WIS_CTRL2.TEST_PAT_SEL and the generator is
enabled by asserting WIS_CTRL2.TEST_PAT_GEN. When WIS_CTRL2.TEST_PAT_SEL is deasserted,
the mixed frequency test pattern is selected. The square wave frequency is configured according to
EWIS_TXCTRL2.SQ_WV_PW. The WIS_CTRL2.TEST_PAT_ANA bit is used to enable the test pattern
checker in the receive path. The checker does not operate on square wave receive traffic. Error counts
from the mixed frequency pattern are presented in the SONET/SDH BIP-8 counters, B1_CNT
WIS_B1_CNT, WIS_B2_CNT, and WIS_B3_CNT.
The VSC8491-17 device supports the PRBS31 test pattern as reflected in
WIS_STAT2.PRBS31_ABILITY. The transmitter/generator is enabled by asserting

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 37

Functional Descriptions

WIS_CTRL2.TEST_PRBS31_GEN, while the receiver/checker is enabled by asserting

WIS_CTRL2.TEST_PRBS31_ANA. Because the mixed frequency/square wave test patterns have
priority over the PRBS31 pattern, WIS_CTRL2.TEST_PAT_GEN must be disabled for the PRBS31 test
pattern to be sent. Error counts from the PRBS31 checker are available in WIS_TSTPAT_CNT. This
register does not roll over after reaching its maximum count and is cleared after every read operation.
Two status bits are available from the PRBS checker. The EWIS_PRBS31_ANA_STAT.PRBS31_ERR bit
indicates whether the error counter is nonzero. The EWIS_PRBS31_ANA_STAT.PRBS31_ANA_STATE
bit if asserted indicates that checker is synchronized and actively checking received bits. For test
purposes, the PRBS generator can inject single bit errors. By asserting
EWIS_PMTICK_CTRL.PMTICK_SRC, a single bit error is injected, resulting in three bit errors being
detected within the checker. The value of three comes from the specification, which indicates one error
should be detected for each tap within the checker.

3.4 10G Physical Coding Sublayer (64B/66B PCS)

The 10G physical coding sublayer (PCS) is defined in IEEE 802.3ae Clause 49. It is composed of the
PCS transmit, PCS receive, block synchronization, and BER monitor processes. The PCS functions can
be further broken down into encode or decode, scramble or descramble, and gearbox functions, as well
as various test and loopback modes.
The PCS is responsible for transferring data between the XAUI clock domain and the WIS/PMA clock
domain. In addition, the PCS encodes and scrambles the data for efficient transport across the given
medium.
The following illustration provides a block diagram of the 10G PCS block.
Figure 18 • PCS Block Diagram

Tx PCS and EPCS

LAN 64b/66b
Buffer 64 Encoder and 66 66 66:64 Gear Box 64
Scrambler
MAC/1588/XGXS

WIS/PMA
Rx PCS and EPCS

LAN 64b/66b
Buffer 64 Decoder and 66 66:64 Gear Box 64
Descrambler

3.4.1 Control Codes

The VSC8491-17 device supports the use of all control codes and ordered sets necessary for 10 GbE
and 10 GFC operation. The following table lists the control characters, notation, and control codes.

Table 17 • Control Codes

Control XGMII Control 10-G BASE-R 10-G BASE-R

Control Codes Character Notation1 Code Control Code O Code
8b/10b Code2 Idle /I/ 0x07 0x00
K28.0 or K28.3 or K28.5 Start /S/ 0xfb

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 38

Functional Descriptions

Table 17 • Control Codes (continued)

Control Codes Control XGMII Control 10-G BASE-R 10-G BASE-R

(continued) Character Notation1 Code Control Code O Code
Encoded by block type K27.7 Terminate /T/ 0xfd
field
Encoded by block type K29.7 Error /E/ 0xfe
field
0x1e K30.7 Sequence /Q/ 0x9c
ordered_set
Encoded by block type 0x0 K28.4 Reserved 0 /R/ 0x1c
field plus O code
0x2d K28.0 Reserved 1 0x3c
0x33 K28.1 Reserved 2 /A/ 0x7c
0x4b K28.3 Reserved 3 /K/ 0xbc
0x55 K28.5 Reserved 4 0xdc
0x66 K28.6 Reserved 5 0xf7
0x78 K23.7 Signal /Fsig/ 0x5c
ordered_set3
Encoded by block type 0xF K28.2
field plus O code

1. The codes for /A/, /K/ and /R/ are used on the XAUI interface to signal idle.
2. For information only. The 8b/10b code is specified in Clause 36. Usage of the 8b/10b code for 10 Gbps operation
is specified in Clause 4.
3. Reserved for INCITS T11 - 10 GFC µs.

3.4.2 Transmit Path

In the transmit direction, the PCS accepts data from the XGXS interface, which runs off the XAUI
recovered clock and transfers the data onto the PMA transmit clock domain, through the rate-disparity
compensating FIFO. Based on the FIFO’s fill level, idle characters are added or removed as needed.
Once in the PMA clock domain, the de-serialized XAUI input data (64-bit) is checked for validity.
Transmitted data is handled according to IEEE 802.3ae Clause 49.
The characters are then processed in a two-step manner. First, the 64 bits are encoded and a 2-bit
header is calculated to form a single 66-bit block. The two header bits are used for block delineation and
classification. The only valid header codes are 01 to indicate a payload of all data octets and 10 to
indicate the presence of one or more control characters within the payload. To maintain a DC balanced
signal on the serial line, the 64-bit encoded payload is scrambled using a self-synchronizing scrambler
that implements the polynomial G(x) = 1 + x39 + x58. The header bits are not scrambled as they are
already DC balanced. For debug purposes, the scrambler can be disabled by deasserting SCR_DIS
(3x8005.9).
The 66-bit blocks are then passed to the PMA through a 66:64 gearbox. The gearbox merely feeds the
66-bit data into the WIS/PMA’s 64-bit data path.

3.4.3 Receive Path

In the receive direction, the PCS accepts data from the WIS/PMA block and reformats it for transmission
to the XGXS interface. Because of the data path width mismatches between the WIS/PMA and the PCS,
a 64:66 gearbox is needed. The gearbox also performs block synchronization/alignment based upon the
2-bit synchronization header. When the receive logic receives 64 continuous valid sync headers, the
BLOCK_LOCK (3x0021.15) bit is asserted. This bit is a latch-low bit; therefore, a second read of the bit
returns the current status. If 16 invalid block sync headers are detected within a 125 µs period, the

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 39

Functional Descriptions

PCS_HIGHBER (3x0021.14) bit is asserted. This bit is a latch-high bit, and therefore a second read of
the bit returns the current status.
Once block synchronization is achieved, the occurrence of errored blocks are accumulated in the
PCS_ERRORED_BLOCKS (3x0021.7:0) counter. An errored block is one that has one or more of the
following defects:
• The sync field has a value of 00 or 11.
• The block type field contains a reserved value (for more information, see Table 17, page 38).
• Any control character contains an incorrect value.
• Any O code contains an incorrect value.
• The set of eight XGMII characters does not have a corresponding block format shown in the
following illustration.
Figure 19 • 64B/66B Block Formats
Input Data Sync Block Payload

Bit Position : 0 1 2 65

Data Block Format :

D0 D1 D2 D3/D4 D5 D6 D7 01 D0 D1 D2 D3 D4 D5 D6 D7

Block
Type
Control Block Formats:
Field

C0 C1 C2 C3/C4 C5 C6 C7 10 0x1e C0 C1 C2 C3 C4 C5 C6 C7
C0 C1 C2 C3/O4 D5 D6 D7 0x2d C0 C1 C2
10 C3 O4 D5 D6 D7
C0 C1 C2 C3/S4 D5 D6 D7 10 0x33 C0 C1 C2 C3 D5 D6 D7
O0 D1 D2 D3/D4 D5 D6 D7 0x66 D2
10 D1 D3 O0 D5 D6 D7

O0 D1 D2 D3/O4 D5 D6 D7 0x55
10 D1 D2 O4 D6 D7
D3 O0 D5

S0 D1 D2 D3/D4 D5 D6 D7 0x78 D2
10 D1 D3 D4 D5 D6 D7

O0 D1 D2 D3/C4 C5 C6 C7 0x4b
10 D1 D2 D3 O0 C4 C5 C6 C7

T0 C1 C2 C3/C4 C5 C6 C7 0x87
10 C1 C2 C3 C5 C6 C7
C4
0x99
D0 T1 C2 C3/C4 C5 C6 C7 10 D0 C2 C3 C4 C5 C6 C7

D0 D1 T2 C3/C4 C5 C6 C7 10 0xaa C3
D0 D1 C4 C5 C6 C7
D0 D1 D2 T3/C4 C5 C6 C7 10 0xb4
D0 D1 D2 C4 C5 C6 C7
D0 D1 D2 D3/T4 C5 C6 C7 10 0xcc
D0 D1 D2 D3 C5 C6 C7
D0 D1 D2 D3/D4 T5 C6 C7 10 0xd2
D0 D1 D2 D3 D4 C6 C7

D0 D1 D2 D3/D4 D5 T6 C7 0xe1
10 D0 D1 D2 D5 C7
D3 D4

D0 D1 D2 D3/D4 D5 D6 T7 10 0xff
D0 D1 D2 D3 D4 D5 D6

Valid blocks recover their original payload data by being descrambled. The descrambler is the same
polynomial used by the transmitter. For test purposes, the descrambler may be disabled by asserting
DSCR_DIS (3x8005.10). The data is checked for valid characters and sequencing.
The data is passed from the PMA/WIS clock domain to the XAUI clock domain through a FIFO. Based
upon the FIFO’s fill level, idle characters are added or removed as needed.

3.4.4 PCS Standard Test Modes

The PCS block offers all of the standard defined test pattern generators and analyzers. In addition, the
VSC8491-17 device supports a 64-bit static user pattern and the optional PRBS31 pattern. Two error
counters are available. Each is a saturating counter that is cleared upon a read operation. The first,
PCS_ERR_CNT, is located in the IEEE Standard area while the 32-bit
PCS_VSERR_CNT_0/PCS_VSERR_CNT_1 is located in the vendor specific area.
The IEEE specification defines two test pattern modes, a square wave generator and a pseudo-random
test pattern. The square wave generator is enabled by first selecting the square wave pattern by
asserting PCS_TSTPAT_SEL, and then enabling the test pattern generator, PCS_TSTPAT_GEN. The
period of the square wave can be controlled in terms of bit times by writing to PCS_SQPW. There is no
associated square wave checker within the VSC8491-17 device.
The pseudo-random test pattern is selected by deasserting PCS_TSTPAT_SEL. The pseudo-random
test pattern contains two data modes. When PCS_TSTDAT_SEL is deasserted, the pseudo-random

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 40

Functional Descriptions

pattern is a revolving series of four blocks with each block 128-bits in length. The four blocks are the
resultant bit sequence produced by the PCS scrambler when pre-loaded with the following seeds:
• PCS_SEEDA_0, PCS_SEEDA_1, PCS_SEEDA_2, PCS_SEEDA_3
• PCS_SEEDA invert
• PCS_SEEDB_0, PCS_SEEDB_1, PCS_SEEDB_2, PCS_SEEDB_3
• PCS_SEEDB invert
The pattern generator is enabled by asserting PCS_TSTPAT_GEN while the analyzer is enabled by
asserting PCS_TSTPAT_ANA. Errors are accumulated in the clear-on-read saturating counter,
PCS_ERR_CNT. In pseudo-random pattern mode, the error counter counts the number of errored
blocks.
Support for the optional PRBS31 pattern is indicated by PRBS31_pattern_testing_ability register whose
default is high. The PRBS31 test generator is selected by asserting PCS_PRBS31_GEN, while the
checker is enabled by asserting PCS_PRBS31_ENA. IEEE standards specify that the error counter
should increment for each linear feedback shift register (LFSR) tap that a bit is in error. Therefore, a
single bit error increments the counter by three because there are three taps in the PRBS31 polynomial.
The user-defined 64-bit static pattern can be written to PCS_USRPAT registers and enabled by asserting
PCS_USRPAT_ENA and PCS_TSTPAT_GEN. Enabling the user-defined pattern enables both the
generator and analyzer.

3.5 1G Physical Coding Sublayer

The 1G physical coding sublayer (PCS) implements 1000BASE-X as specified by IEEE 802.3 Clause 36,
and auto-negotiation as specified by IEEE 802.3 Clause 37. It provides for the encoding (and decoding)
of GMII data octets to (and from) ten-bit code-groups (8B/10B) for communication with the underlying
PMA. It also manages link control and the auto-negotiation process.
In addition to these standard 1000BASE-X functions, the 1G PCS also includes a conversion function
that maps the standard GMII data to (and from) an internal XGMII-like interface. This allows the
processing core to be largely agnostic to whether a channel is operating in 1G or 10G operation.

3.6 IEEE 1588 Block Operation

The VSC8491-17 device uses a second generation IEEE 1588 engine that is backward compatible with
the earlier version of VeriTime™ (the Microsemi IEEE 1588 time stamping engine), both stand alone and
in combination with MACsec). It is also compatible with the IEEE 1588 operations supported in
Microsemi CE switches. The following list shows the new features of the Microsemi second generation
IEEE 1588.
• MACsec support
• Higher time stamp accuracy and resolution
• Automatic clear enables after system time is read or written
• Ability to load or extract the current system time in serial format
• Full 48-bit math support for incoming correction field
• Ability to add or subtract fixed offset from system time to synchronize between slaves
• Independent control and bypass for each direction of IEEE 1588
• Support to extract frame signature in an IPv6 frame
• MPLS-TP OAM support in third analyzer engine
• Special mode where all frames traversing the system can be time stamped
The unique architecture of the MACsec and the second generation IEEE 1588 block combination
provides for the lowest latency and maximum throughput on the channel. The following illustration shows
a block diagram of the IEEE 1588 architecture in the VSC8491-17 device.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 41

Functional Descriptions

Figure 20 • IEEE 1588 Architecture

PHY 0 PHY 1

1588 insta nce

MA C 0 MAC 1

1588 insta nce

registers

P roc0 P ro c1 config

LTC0 LTC1

Egress Ingress
P ro cessor 0 P rocessor 0
deco nstructo r co nstructor a na lyzer
Time sta mp
Engine0

tsp dela y
rew riter Engine1
fifo

Engine2 Egress Ingress

P ro cessor1 P ro cessor1
Engine 0
dela y
fifo rew riter tsp
Engine 1

Engine 2

co nstructor deco nstructo r

a na lyzer

The following sections list some of the major IEEE 1588 applications.

3.6.1 IEEE 1588 Block

The IEEE 1588 engine may be configured to support one-step and two-step clocks as well as Ethernet
and MPLS OAM delay measurement. It detects the IEEE 1588 frames in both the Rx and Tx paths,
creates a time stamp, processes the frame, and updates them. It can add a 30/32-bit Rx time stamp to
the 4-bytes reserved field of the PTP packet. It can also modify the IEEE 1588 correction field and
update the CRC of changed frames. There are local time counters (reference for all time stamps) that
can be preloaded and adjusted though the register interface.
A local time counter is used to hold the local time for Rx and Tx paths. A small FIFO delays frames to
allow time for processing and modification. An analyzer detects the time stamp frames (PTP and OAM)
and a time stamp block calculates the new correction field. The rewriter block replaces the correction
field with an updated one and checks/calculates the CRC. For the Tx path, a time stamp FIFO saves Tx
event time stamp plus frame identifier for use in some modes.
The IEEE 1588 engine’s registers and time stamps are accessible through the MDIO or 4-pin SPI. To
overcome the MDIO or 4-pin SPI speed limitations, the dedicated “push-out” style SPI output bus can be
used for faster or large amounts of time stamp reads. This SPI output is used to push out time stamp
information to an external device only and does not provide read/write to the registers of the IEEE 1588
engine or registers of other blocks in the VSC8491-17 device. In addition, there is a LOAD/SAVE pin that

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 42

Functional Descriptions

is used to load the time in the PHYs and to ensure that all the PHYs are in sync. The local time counter
may come from any one of the following sources:
• Data path clock (varies according to mode)
• 250 MHz from host-side PLL
• External clock (125 MHz or 250 MHz) from CLK1588P/N pins
The local time counters contain two counters: nanosecond_counter and second_counter. The 1 PPS
(pulse per second signal) output pin can be used for skew monitoring and adjustment. The following
illustration shows an overview of a typical system using IEEE 1588 PHYs. The LOAD/SAVE and 1 PPS
pins are signals routed to the GPIO pins. The following illustration shows how the PHY is embedded in a
system.
Figure 21 • IEEE 1588 Block Diagram
Ethernet Line Card System Card Ethernet Line Card
System 1588
Linecard Control Control Linecard Control
Processor Processor Processor

Ethernet Port Packet Ethernet Port

1G
MAC Packet MAC 10G
PHY Processing Fabric Processing PHY

RefClk Timing Card RefClk

Optional Timing Optional

frequency Card frequency
conversion conversion

1 PPS Sync

The system card has to drive the REFCLK (125 MHz or 250 MHz timetick clock) to all the PHYs,
including the VSC8491-17 device. The system clock may need local frequency conversion to match the
required reference clock frequency. The system clock may be locked to a PRC by SyncE or by
IEEE 1588. If locked by IEEE 1588, the central CPU recovers the PTP timing and adjusts the frequency
of the system clock to match the PTP frequency. If the system clock is free running, the central CPU must
calculate the frequency offset between the system clock and the synchronized IEEE 1588 clock, and
program the PHYs to make internal adjustments.
The system card also provides a sync pulse to all PHYs, including the VSC8491-17 device, to the
LOAD/SAVE pin. This signal is used to load the time to the PHYs and to ensure that all the PHYs are in
sync. This may just be a centrally divided down system clock that gives a pulse at fixed time intervals.
The delay from the source of the signal to each PHY must be known and taken into account when writing
in the load time in the PHYs.
The VSC8491-17 device supports a vast variety of IEEE 1588 applications. In simple one-step end-to-
end transparent clock applications, the VSC8491-17 device can be used without any central CPU
involvement (except for initial configuration). The IEEE 1588 block inside the VSC8491-17 device
forwards Sync and Delay_req frames with automatic updates to the Correction field.
In other applications, the VSC8491-17 device enhances the performance by working with a central
processor that runs the IEEE 1588 protocol. The VSC8491-17 device performs the accurate time stamp
operations needed for all the different PTP operation modes. For example, at startup in a boundary clock
application, the central CPU receives PTP sync frames that are time stamped by the ingress PHY and
recovers the local time offset from the PTP master using the PTP protocol. It then sets the save bit in the
VSC8491-17 device connected to the PTP master and later reads the saved time. The central CPU loads
the expected time (time of the next LOAD/SAVE pulse, corrected by the offset to the recovered PTP
time) into the PHY and sets the save bit. It checks that the time offset is 0. If not, it makes small
adjustments to the time in the PHY by issuing add 1 ns or subtract 1 ns commands to the VSC8491-17
device through MDIO until the time matches the PTP master. A save command is issued to the PHY
connected to the PTP master and reads the saved time. The central CPU then writes the saved time plus
the sync pulse interval plus any sync pulse latency variation (trace length difference compared to the

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 43

Functional Descriptions

PHY connected to the PTP master) to the other PHYs and sets the load bit in these VSC8491-17
devices.
The preceding sequence may be completed in several steps. Not all PHYs need to be loaded at once.
The central CPU sets the save bit in all PHYs and reads back the values. They should all save the same
value.
The central CPU continuously detects if the system time drifts off compared to the recovered PTP time. If
needed, it can adjust each PHY for any known skew between PHYs without affecting the operation of the
device. It can program the PHYs, including the VSC8491-17 device, to automatically add 1 ns or subtract
1 ns at specific time intervals.

3.6.2 IEEE 1588v2 One-Step End-to-End Transparent Clock

The timestamp block is located in PHYs and MACs with integrated PHYs that are placed on line cards. If
Microsemi 1588 PHYs are used on all ports that support IEEE 1588 one-step end-to-end transparent
clocks, the rest of the system does not need to be 1588-aware, and there is no CPU maintenance
needed once the system is set up.
As all the PHYs in a system can be configured the same way, the system supports failover of 1588
masters without any CPU intervention.
This solution works for both blade systems and pizza boxes, where the devices placed on the system
side of the PHYs don’t need to be 1588-aware. This allows an easy migration path for systems that do
not support IEEE 1588, as this feature can be added by replacing existing PHYs with Microsemi 1588
PHYs on all ports.
Unique advantages for implementing IEEE 1588-2008 include:
• When several VSC8491-17 devices or Microsemi PHYs with integrated IEEE 1588 time stamping
blocks are used on all ports within the system that support IEEE 1588 one-step E2E TC, the rest of
the system does not need to be IEEE 1588 aware, and there is no CPU maintenance needed once
the system is set up.
• As all the PHYs in a system can be configured the same way, it supports fail-over of IEEE 1588
masters without any CPU intervention.
• VSC8491-17 and other Microsemi PHYs with integrated IEEE 1588 time stamping blocks also work
for pizza box solutions, where the switch/router can be upgraded to support IEEE 1588 E2E TC.
Requirements for the rest of the system are:
• Delivery of a synchronous global timetick clock (or reference clock) to ensure that the “local time” for
all PHYs in the system progresses at the same rate.
• Delivery of a global timetick load to synchronize the local time counters in each PHY.
• CPU access to each PHY to set up the required configuration. This can be through MDIO, two-wire
slave, or 4-pin SPI.
The following illustration shows a diagram for the transparent clock line card application.
Figure 22 • 1588 Transparent Clock Line Card End-to-End PHY Application
Ethernet Line Card System Card Ethernet Line Card

Linecard Control System Control

Processor Processor

1G
Ethernet Port SerDes PHY Packet Linecard Control
MAC
Processing Processor

10G
Ethernet Line Card Packet SerDes PHY Ethernet Port
MAC
Fabric Processing
Linecard Control
Processor

MAC or
Ethernet Port Fabric
Switch
Adapter

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 44

Functional Descriptions

3.6.3 IEEE 1588v2 Transparent Clock and Boundary Clock

This is the same system as described previously, with the addition of a central IEEE 1588 engine
(Boundary Clock). The IEEE 1588 engine is most likely a CPU system, possibly together with hardware
support functions to generate Sync frames (for BC and ordinary clock masters). The switch/fabric needs
to have the ability to redirect (and copy) PTP frames to the IEEE 1588 engine for processing.
This system uses a central 1588 engine, most likely a CPU system, together with hardware support
functions to generate sync frames (for boundary clock and ordinary clock masters). The switch fabric
needs to have the ability to redirect (and copy) PTP frames to the 1588 engine for processing. This
system also works for pizza boxes.
Figure 23 • Transparent Clock and Boundary Clock Line Card Application
Ethernet Line Card System Card Ethernet Line Card

Linecard Control System Control Linecard Control

Processor Processor Processor

Ethernet Port Packet 1G Ethernet Port

1G
MAC Packet MAC
PHY Processing Fabric Processing PHY

Boundary
Clock

This solution also works for pizza boxes. To ensure that blade redundancy works, the PHYs for the
redundant blades must have the same 1588-in-the-PHY configuration.
Requirements for the rest of the system are:
• Delivery of a synchronous global timetick clock (or reference clock) to the PHYs.
• Delivery of a global timetick load, that synchronizes the local time counters in each port.
• CPU access to each PHY to set up the required configuration. For one-step support, this can be
MDC/MDIO. For two-step support, a higher speed CPU interface (such as the SPI) might be
required (depending on the number of time stamps that are required to be read by the CPU). In
blade systems, it might be required to have a local CPU on the blade that collects the information
and sends it to the central IEEE 1588 engine by means of the control plane or the data plane. In
advanced MAC/Switch devices, this might be an internal CPU.
• Fabric must be able to detect IEEE 1588 frames and redirect them to the central IEEE 1588 engine.
The same solution can also be used to add Y.1731 delay measurement support. This does not require a
local CPU on the blade, but the fabric must be able to redirect OAM frames to a local/central OAM
processor.
The following illustration shows a diagram for the boundary clock line card application.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 45

Functional Descriptions

Figure 24 • 1588 Boundary Clock Line Card Application

Ethernet Line Card System Card Ethernet Line Card

Linecard Control System Control Linecard Control

Processor Processor Processor

1G 10G
Ethernet Port Packet Ethernet Port
SerDes PHY MAC Packet MAC SerDes PHY
Processing Fabric Processing

Boundary
Clock

3.6.4 Enhancing IEEE 1588 Accuracy for CE Switches and MACs

Connecting VSC8491-17 or other Microsemi PHYs that have integrated IEEE 1588 time stamping in
front of the CE Switches and MACs improves the accuracy of the IEEE 1588 time stamp calculation. This
is due to the clock boundary for the XAUI and SGMII/QSGMII interface. It will also add support for one-
step TC and BC on the Jaguar-1 family of devices.

3.6.5 MACsec Support

MACsec is required when the physical link between two MACs must provide secure communication.
MACsec PHYs, such as the VSC8491-17 device, are connected with CE switches to provide secure
communication. PTP and OAM frames are recognizable only before or after encryption, meaning that the
MACsec block must precede the IEEE 1588 block from the line inward.
Even though MACsec introduces large delay variation because of the insertion/removal of the MACsec
header on all encrypted frames, the VSC8491-17 device provides the same accuracy with MACsec
enabled as without. In all other aspects, the IEEE 1588 operation is as described in previous sections.

3.6.6 Supporting One-Step Boundary Clock/Ordinary Clock

In one-step boundary clock, the BC device acts as an ordinary clock slave on one port and as master on
the other ports. On the master ports, Sync frames are transmitted from the IEEE 1588 engine that holds
the Origin time stamp. These frames will have the correction field or the full Tx time stamp updated on
the way out though the PHY.
Master ports also receive Delay_req from the slaves and respond with Delay_resp messages. The
Delay_req messages are time stamped on ingress through the PHY and the IEEE 1588 engine receives
the Delay_req frame and generates a Delay_resp message. The Delay_resp messages are not event
messages, and are passed though the PHY as any other frame.
The port configured as slave receives Sync frames from its master. The Sync frames have a Rx time
stamp added in the PHY and forwarded to the IEEE 1588 engine.
The IEEE 1588 engine also generates Delay_req frames that are sent on the port configured as slave
port. Normally the transmit time for the Delay_req frames (t3) is saved in a time stamp FIFO in the PHYs,
but when using Microsemi IEEE 1588 PHYs, a slight modification can be made to the algorithm to
remove the CPU processing overhead of reading the t3 time stamp.
To modify the algorithm, the IEEE 1588 engine should send the Delay_req message with a software
generated t3 value in the origin time stamp, the sub-second value of the t3 time stamp in the reserved
bytes of the PTP header, and a correction field of 0. The software generated t3 time stamp should be
within a second before the actual t3 time. The Egress PHY should then be configured to perform E2E TC
egress operation, meaning calculate the “residence time” from the inserted t3 time stamp to the actual t3
time and insert this value in the correction field of the frame. When the local IEEE 1588 engine receives
the corresponding Delay_resp frame back, it can use the software generated t3 value because the
correction field of the Delay_resp frame contains a value that compensates for the actual t3 transmission
time.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 46

Functional Descriptions

Boundary clocks and ordinary clocks must also reply to Pdelay_req messages just as P2P TC using the
same procedure for the P2P TC. For more information, see Supporting One-Step Peer-to-Peer
Transparent Clock, page 53.
Figure 25 • One-Step E-nd-to-End Boundary Clock
PTP Sync Or Delay_req Frame
Correction Field = A
Reserved Bytes = 0

IEEE 1588
PHY

PTP Sync or Delay_req Frame PTP Pdelay_req Frame

Correction Field = A Correction Field = C
Reserved bytes = RxTimestamp PTP Sync Frame
OriginTime = F
Correction Field = E
Central Engine recovers
Packet processing and IEEE 1588 frequency from Sync
frames and controls
Switching Engine 1588 frequency
PTP Sync Frame (CPU)
Correction Field = A
PTP Sync Frame Reserved bytes = RxTimestamp +
PTP Pdelay_req Frame Origin Time = F Peer Delay
Correction Field = C Correction Field = E

IEEE 1588
IEEE
PHY1588
PHY

PTP delay_req Frame PTP Sync Frame

Correction Field = C OriginTime = TxTimestamp
(TxTimestamp saved in FIFO) Correction Field = E

3.6.6.1 Ingress
Each time the PCS/PMA detects the start of a frame, it sends a pulse to the time stamp block, which
saves the value of the Local_Time received from the Local Time counter. In the time stamp block, the
programmed value in the local_correction register is subtracted from the saved time stamp. The
local_correction register is programmed with the fixed latency from the measurement point to the place
that the start of frame is detected in the PCS/PMA logic. The time stamp block also contains a register
that can be programmed with the known link asymmetry. This value is added or subtracted from the
correction field, depending on the frame type.
When the frame leaves the PCS/PMA block, it is loaded into a small FIFO block that delays and stores
the frame data for a few clock cycles to allow for later modifications of the frame. The data is also copied
to the analyzer block that parses the incoming frame to detect whether it is a IEEE 1588 Sync or
Delay_req frame belonging to the PTP domain that the system is operating on. If so, it signals to the
ingress time stamp block in the PHY which action to perform (Write). It also delivers the write offset and
data size (location of the four reserved bytes in the PTP header, 4 bytes wide) to the rewriter block in the
PHY.
If the analyzer detects that the frame is not matched, it signals to the time stamp block and the rewriter
block to ignore the frame (NOP), which allows it to pass unmodified and flushes the saved time stamp in
the time stamp block.
If the time stamp block gets the Write action, it delivers the value of the calculated time stamp for the
frame to the rewriter block and the rewriter block adds this time stamp (ns part of it) to the four reserved
bytes in the frame and recalculates FCS.
The rewriter block takes data out of the FIFO block continuously and feeds it to the system side
PCS/PMA block using a counter to keep track of the byte positions of the frame. When the rewriter block
receives a signal from the time stamp block to rewrite a specific position in the frame (that information
comes from the analyzer block), it overwrites the position with the data from the time stamp block and

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 47

Functional Descriptions

replaces the FCS of the frame. The rewriter also checks the original FCS of the frame to ensure that a
frame that is received with a bad FCS and then modified by the rewriter is also sent out with a bad FCS.
This is achieved by inverting the new FCS. If the frame is an IPv4 frame the rewriter ensures that the IP
checksum is 0. If the frame is IPv6 the rewriter keeps track of the modifications done to the frame and
modifies a couple of bytes placed at the end of the PTP frame (for this specific purpose) so that the IP
checksum stays correct.
The following full calculations are performed:
• Sync frames: Reserved_bytes = (Raw_Timestamp_ns – Local_correction) Correction
field = Original Correction field + Asymmetry
• Delay_req frames: Reserved_bytes = (Raw_Timestamp_ns – Local_correction)

3.6.6.2 Egress
When a frame is received from the system side PCS/PMA block, it is loaded into a FIFO block that delays
and stores the frame data for a few clock cycles to allow for later modifications of the frame. The data is
also copied to the analyzer block that parses the incoming frame to detect whether it is a IEEE 1588
Sync or Delay_req frame belonging to the PTP domain that the system is operating on.
If the egress analyzer of the PHY detects that the frame is a IEEE 1588 Sync frame belonging to the PTP
domain(s) of the system, it signals to the egress time stamp block which action to perform (Write). It also
delivers the write offset and data size (location of the Tx time stamp inside the frame, 10 bytes wide) to
the rewriter.
If the egress analyzer detects that the frame is a IEEE 1588 Delay_req frame belonging to the PTP
domain(s) of the system, it signals to the time stamp block which action to perform (Write, Save). It also
delivers the write offset and data size (location of the Tx time stamp inside the frame, 10 bytes wide) to
the rewriter. It also outputs up to 16 bytes of frame identifier to the Tx time stamp FIFO, to be saved along
with the Tx time stamp. The frame identifier bytes are selected information from the frame, configured in
the analyzer.
If the time stamp block gets the (Write, Save) action it delivers the calculated time stamp and signals to
the time stamp FIFO block that it must save the time stamp along with the frame identifier data it received
from the analyzer block.
The Tx time stamp FIFO block contains a buffer memory. It simply stores the Tx time stamp values that it
receives from the time stamp block together with the frame identifier data it receives from the
analyzerblock, and has a CPU interface that allows the IEEE 1588 engine to read out the time stamp
sets (Frame identifier + New Tx time stamp).
The following full calculations are performed:
• Sync frames: OriginTimestamp = (Raw_Timestamp + Local_correction)
• Delay_req frames: OriginTimestamp = (Raw_Timestamp + Local_correction) Correction
field = Original Correction field + Asymmetry

3.6.7 Supporting Two-Step Boundary Clock/Ordinary Clock

Two-step clocks are used in systems that cannot update the correction field on-the-fly, and this requires
more CPU processing than one-step.
Each time a Tx time stamp is sent in a frame, the IEEE 1588 engine reads the actual Tx transmission
time from the time stamp FIFO and issues a follow-up message containing this time stamp. Even though
the VSC8491-17 device supports one-step operation, thereby eliminating the need to run in two-step
mode, support for this mode is provided for networks that include two-step-only implementations.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 48

Functional Descriptions

Figure 26 • Two-Step End-to-End Boundary Clock

PTP Sync Or Delay_req Frame
Correction Field = A
Reserved Bytes = 0

IEEE 1588
PHY

PTP Sync or Delay_req Frame PTP Pdelay_req Frame

Correction Field = A Correction Field = C
Reserved bytes = RxTimestamp PTP Sync Frame
OriginTime = F
Correction Field = E
Central Engine recovers
Packet processing and IEEE 1588 frequency from Sync
Switching Engine frames and controls
1588 frequency
PTP Sync Or Delay_req Frame
(CPU)
Correction Field = A
PTP Sync Frame Reserved bytes = RxTimestamp
PTP Pdelay_req Frame Origin Time = F
Correction Field = C Correction Field = E

IEEE 1588
PHY

PTP Sync Frame

PTP delay_req Frame
OriginTime = F
Correction Field = C
Correction Field = E
(TxTimestamp saved in FIFO )
(TxTimestamp saved in FIFO)

3.6.7.1 Ingress
If the ingress analyzer in the PHY detects that the frame is a IEEE 1588 Sync or Delay_req frame
belonging to the PTP domain(s) of the system, it signals to the time stamp block which action to perform
(Write). It also delivers the write offset and data size (location of the four reserved bytes in the PTP
header, 4 bytes wide) to the rewriter.
If the time stamp block gets the Write action, it delivers the calculated time stamp to the rewriter block
and the rewriter block adds this time stamp (ns part of it) to the four reserved bytes in the frame and
recalculates FCS.
Note: When secure timing delivery is required (when using IPsec authentication, for instance), the four
reserved bytes must be reverted back to 0 before performing integrity check.
The following full calculations are performed:
• Sync frames: Reserved_bytes = (Raw_Timestamp – Local_correction)
Correction field = Original Correction field + Asymmetry
• Delay_req frames: Reserved_bytes = (Raw_Timestamp – Local_correction)

3.6.7.2 Egress
If the egress analyzer detects that the frame is a IEEE 1588 Sync or Delay_req frame belonging to the
PTP domain(s) of the system, it signals to the time stamp block which action to perform (Write, Save).
The analyzer outputs up to 15 bytes of frame identifier to the Tx time stamp FIFO to be saved along with
the Tx time stamp. The frame identifier must include, at a minimum, the sequenceId field so the CPU can
match the time stamp with the follow-up frame.
If the time stamp block gets the Write, Save action it delivers the calculated time stamp to the time stamp
FIFO and signals to the time stamp FIFO block that it must save the time stamp along with the frame
identified data it received from the analyzer block.
The following full calculations are performed:
• Sync frames: FIFO = (Raw_Timestamp + Local_correction)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 49

Functional Descriptions

• Delay_req frames: FIFO = (Raw_Timestamp + Local_correction)

Correction field = Original Correction field – Asymmetry

3.6.8 Supporting One-Step End-to-End Transparent Clock

End-to-end transparent clocks add the residence time (the time it takes to traverse the system from the
input to the output port(s)) to all Sync and Delay_req frames. It does not need to have any knowledge of
the actual time, but if it is not locked to the frequency of the IEEE 1588 time, it will produce an error that
is the ppm difference in frequency times the residence time.
When the TC is frequency-locked by means of IEEE 1588 or other methods (SyncE), the error is only
caused by sampling inaccuracies.
The VSC8491-17 device supports a number of different transparent clock modes that can be divided into
two main modes, as follows.
• Mode A. Subtracts the ingress time stamp at ingress and adds the egress time stamp at egress.
This mode can run in a number of sub-modes, depending on the format of the time stamp that is
subtracted or added.
• Mode B. Saves the ingress time stamp in the reserved bytes of the PTP header (just as is done in
BC and ordinary clock modes) and performs the residence time calculation at the egress PHY where
the calculated residence time is added to the correction field of the PTP frame.
Mode B is recommended because it has a number of advantages, including the option to support TC and
BC operation in the same system and on the same traffic, and the ease of implementing syntonized TC
operation.
When an E2E TC recovers frequency using IEEE 1588 and is using Mode A, it must either have a PHY
with IEEE 1588 time stamping Mode A support or another way of adding the local time to the correction
field placed in front of the IEEE 1588 engine. The IEEE 1588 engine is then able to receive Sync frames
and adjust the local frequency to match the IEEE 1588 time.
If using Mode B, the IEEE 1588 engine can recover the frequency directly from the Sync frames because
it can extract the ingress time stamp directly from the frames. The frequency adjustment can be done by
adjusting the time counter in each PHY or by adjusting the global Timetick clock.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 50

Functional Descriptions

Figure 27 • One-Step End-to-End Transparent Clock Mode A

PTP Sync or Delay_Req Frame

Correction Field = A

IEEE 1588
PHY

PTP Sync or Delay_Req Frame

Correction Field = A – RxTimestamp

Central
Packet processing and IEEE 1588
Switching Engine
(CPU)
PTP Sync or Delay_Req Frame
Correction Field = A – RxTimestamp

IEEE 1588
IEEE
PHY1588
PHY

PTP Sync or Delay_Req Frame

Correction Field =
A – RxTimestamp + TxTimestamp

When the system works in one-step E2E TC mode Sync and Delay_req frames must be forwarded
through the system and the residence time = (Egress time stamp – Ingress time stamp) must be added
to the correction field in the frame before it leaves the system.
The following sections describe the operation in Modes A and B.

3.6.8.1 Ingress (Mode A)

If the analyzer detects that the frame is a IEEE 1588 Sync or Delay_req frame belonging to the PTP
domain(s) of the system, it signals to the time stamp block which action to perform (Subtract), along with
the correction field of the frame. It also delivers the write offset and data size (location of the correction
field inside the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Subtract action, it subtracts the time stamp converted to ns from the
original correction field of the frame and outputs the value to the rewriter block.
As a result the frame is sent towards the system with a correction field containing the value: Original
Correction field – Rx time stamp (converted to ns).
The following full calculations are performed:
• Sync frames: Internal Correction field = Original Correction field – (Raw_Timestamp_ns –
Local_correction) + Asymmetry
• Delay_req frames: Internal Correction field = Original Correction field – (Raw_Timestamp_ns –
Local_correction)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 51

Functional Descriptions

3.6.8.2 Egress (Mode A)

The egress side works that same way as ingress, but the analyzer is set up to add the active_timestamp
to the correction field.
If the analyzer detects that the frame is a IEEE 1588 Sync or Delay_req frame belonging to the PTP
domain(s) of the system, it signals to the time stamp block which action to perform (Add), along with the
correction field of the frame. It also delivers the write offset and data size (location of the correction field
inside the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is not matched, it signals the time stamp block and the rewriter
block to ignore the frame (let it pass unmodified and flush the saved time stamp in the time stamp block).
If the time stamp block gets the Add action, it adds the current value of the active_timestamp to the value
of the correction field received from the analyzer and outputs the value to the rewriter block.
When the rewriter block receives a signal from the analyzer block to rewrite a specific position in the
frame, it overwrites the position with the data received from the time stamp block and replaces the FCS
of the frame. The rewriter also checks the original FCS of the frame and ensures that a frame that is
received with a bad FCS and then modified by the rewriter is also sent out with a bad FCS. This is
achieved by inverting the new FCS.
The following full calculations are performed:
• Sync frames: Correction field = Internal Correction field + (Raw_Timestamp_ns + Local_correction)
• Delay_req frames: Correction field = Internal Correction field + (Raw_Timestamp_ns +
Local_correction) – Asymmetry
Figure 28 • One-Step End-to-End Transparent Clock Mode B

PTP Sync or Delay_Req Frame

Correction Field = A
Reserved Bytes = 0

IEEE 1588
IEEE
PHY1588
PHY

PTP Sync or Delay_Req Frame

Correction Field = A
Reserved bytes = RxTimestamp

Central
Packet processing and IEEE 1588
Switching
Engine
PTP Sync Frame
Correction Field = A (CPU)
PTP Sync or Delay_Req Frame Reserved bytes = RxTimestamp
Correction Field = A Engine recovers frequency
Reserved bytes = RxTimestamp from Sync frames and
controls 1588 frequency

IEEE 1588
PHY

PTP Sync or Delay_Req Frame

Correction Field =
A – RxTimestamp + TxTimestamp
Reserved bytes = 0

3.6.8.3 Ingress (Mode B)

In ingress mode B, all calculations are performed at the egress port.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 52

Functional Descriptions

On the ingress side, when the analyzer detects Sync or Delay_req frames, it adds the Rx time stamp to
the four reserved bytes in the PTP frame.
The following full calculations are performed:
• Sync frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction Correction field = Original
Correction field + Asymmetry
• Delay_req frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction

3.6.8.4 Egress (Mode B)

All calculations are done at the egress side. When the analyzer detects Sync or Delay_req frames, it
performs the following calculation:
• Correction field = Original Correction field + Tx time stamp – Rx time stamp
The value of the Rx time stamp is extracted from four reserved bytes in the PTP header. The four
reserved bytes are cleared back to 0 before transmission.
The result is that every Sync and Delay_req frame that belongs to the PTP domain(s) and is configured
as one-step E2E TC in the system will exit the system with a correction field that contains the following:
• Correction field = Original correction field + Tx time stamp – Rx time stamp
All this is done without any interaction with a CPU system, other than the initial setup. There is no
bandwidth expansion. Standard switching/routing tunneling can be done between the ingress and egress
PHY, provided that the analyzers in the ingress PHY and egress PHY are set up to catch the Sync and
Delay_req on both. If the PTP Sync and Delay_req frames are modified inside the system, the egress
analyzer must be able to detect the egress Sync and Delay_req frames; otherwise, the egress Sync and
Delay_req frames will have an incorrect correction field.
The following full calculations are performed:
• Sync frames: Correction field = Original Correction
field + (Raw_Timestamp_ns + Local_correction) – Reserved_bytes
• Delay_req frames: Correction field = Original Correction
field + (Raw_Timestamp_ns + Local_correction) – Reserved_bytes – Asymmetry

3.6.9 Supporting One-Step Peer-to-Peer Transparent Clock

When a Sync frame traverses a P2P TC, the correction field is updated with both the residence time and
the calculated path delay on the port that the Sync frame came in on.

3.6.9.1 Peer Link Delay Measurement

In P2P TC, the P2P TC device actively sends and receives Pdelay_req and Pdelay_resp messages, and
calculates the path delays to each neighbor node in the PTP network. The following illustration shows the
delay measurements.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 53

Functional Descriptions

Figure 29 • Delay Measurements

Master Slave
time time
Timestamps
known by slave
t1 Sy nc
t-ms
Follow_U
p
t2 t2
t1, t2
t3 t3

Req
t-sm la y_
Pd e

t4

t5 Pde la
y _Re s
p
Pdelay
_Resp
_Follo
t6 t6
w _Up t3, t4, t5, t6

Grandmaster-M S- BC -M S- OC

To calculate the path delays on a link, the IEEE 1588 engine (located somewhere in the system)
generates Pdelay_req messages on all ports. When transmitted, the actual Tx time stamp (t3) is saved
for the CPU to read.
When a P2P TC, BC, or OC receives a Pdelay_req frame, it saves the Rx time stamp (t4) and generates
a Pdelay_resp frame, which adds t5 – t4 to the correction field copied from the received Pdelay_req
frame, where t5 is the time that the Pdelay_resp leaves the port (t5).
When a P2P TC receives the Pdelay_resp frame, it saves the Rx time stamp (t6) and then calculates the
path delay as (t6 – t3 – the correction field of the frame)/2. The time stamp corrections are combined into
a single formula as follows:
• Path delay = (t6 – (t3 + (t5 – t4))/2 = (t6 – t3 – t5 + t4)/2 = ((t4 – t3) + (t6 – t5))/2
The two path delays are divided by two, but in such a way as to cancel out any timing difference between
the two devices.
A slight modification can be made to the algorithm to remove the CPU processing overhead of reading
the t3 time stamp. To modify the algorithm, the IEEE 1588 engine should send the Pdelay_req message
with a software generated t3 value in the origin time stamp, the sub-second value of the t3 time stamp in
the reserved bytes of the PTP header, and a correction field of 0. The software generated t3 time stamp
should just be within a second before the actual t3 time. The egress PHY should then be configured to
perform E2E TC egress operation, meaning calculate the “residence time” from the inserted t3 time
stamp to the actual t3 time and insert this value in the correction field of the frame. When the IEEE 1588
engine receives the corresponding Pdelay_resp frame back it can use the software generated t3 value
as the correction field of the Pdelay_resp frame will contain a value that compensates for the actual t3
transmission time.
A P2P TC adds the calculated one-way path delay to the ingress correction field, and this ensures that
the time stamp + correction field in the egress Sync frames is accurate and a slave connected to the P2P
TC only needs to add the link delay from the TC to the slave.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 54

Functional Descriptions

The following sections describe both the standard and modified methods for taking P2P measurements.
As with E2E TC operations, the VSC8491-17 device also supports the different TC modes: mode A (with
different time stamp formats) and mode B. Mode B is also the preferred method to implement P2P TC.

3.6.9.2 Ingress, Mode A

If the analyzer detects that the frame is a IEEE 1588 Sync frame belonging to the PTP domain(s) of the
system, it signals to the time stamp block which action to perform (subtract_p2p) along with the
correction field of the frame. It also delivers the write offset and data size (location of the correction field
inside the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_req or Pdelay_resp frame belonging to the
PTP domain(s) of the system, it signals to the time stamp block which action to perform (Write). It also
delivers the write offset and data size (location of the reserved 4 bytes in the PTP header that is used to
save the ns part of the Rx time stamp, 4 bytes wide) to the rewriter.
If the time stamp block gets the subtract_p2p action, it subtracts the value in the ingress time stamp from
the correction_field data, adds the configured path delay value, and delivers the result to the rewriter
block.
If the time stamp block gets the Write action, it outputs the value of the ingress time stamp register to the
rewrite block and the rewriter block writes the sub-second value to the reserved bytes in the PTP header.
The following full calculations are performed:
• Sync frames: Internal Correction field = Original Correction field – (Raw_Timestamp_ns –
Local_correction) + Path_delay + Asymmetry
• Pdelay_req frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction
• Pdelay_resp frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction
Correction Field = Original Correction field + Asymmetry

3.6.9.3 Egress, Mode A

If the analyzer detects that the frame is a IEEE 1588 Sync frame belonging to the PTP domain(s) of the
system, it signals to the time stamp block which action to perform (Add), along with the correction field of
the frame. It also delivers the write offset and data size (location of the correction field inside the frame,
8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_req frame belonging to the PTP domain(s)
of the system, it signals to the time stamp block which action to perform (Sub_add), along with the
original correction field of the frame (will have the value of 0) and the time stamp extracted from the
reserved bytes. It also delivers the write offset and data size (location of the correction field inside the
frame, 8 bytes wide) to the rewriter.
If the user prefers to use to use the normal t3 handling where the t3 time stamp is saved in a time stamp
FIFO, the following configuration should be used: If the analyzer detects that the frame is a IEEE 1588
Pdelay_req frame belonging to the PTP domain(s) of the system, it signals to the time stamp block which
action to perform (Write, Save), along with the original correction field of the frame (will have the value of
0). It also delivers the write offset and data size (0- No data is actually written into the frame) to the
rewriter. In addition, it outputs the field that holds the frame identifier (sequenceId from the PTP header)
to the time stamp FIFO, to save along with the Tx time stamp.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_resp frame belonging to the PTP domain(s)
of the system, it signals to the time stamp block which action to perform (Sub_add), along with the
original correction field of the frame (will have the value of the CF received from the Pdelay_req frame)
and the time stamp extracted from the reserved bytes. It also delivers the write offset and data size
(location of the correction field inside the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is not matched, it signals to the time stamp block and the rewriter
block to ignore the frame (let it pass unmodified and flush the saved time stamp in the time stamp block).
The following full calculations are performed:
• Sync frames: Correction field = Internal Correction field + (Raw_Timestamp_ns + Local_correction)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 55

Functional Descriptions

• Pdelay_req frames: Correction field = Internal Correction

field + (Raw_Timestamp_ns + Local_correction) – Reserved_bytes – Asymmetry
• Pdelay_resp frames: Correction field = Original Correction
field + (Raw_Timestamp_ns + Local_correction) – Reserved_bytes

3.6.9.4 Ingress, Mode B

If the analyzer detects that the frame is a IEEE 1588 Sync frame belonging to the PTP domain(s) of
system, it signals to the time stamp block which action to perform (subtract_p2p), along with the
correction field of the frame. It also delivers the write offset and data size (location of the correction field
inside the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_req frame belonging to the PTP domain(s)
of system, it signals to the time stamp block which action to perform (Write). It also delivers the write
offset and data size (location of the reserved 4 bytes in the PTP header used to save the ns part of the
Rx time stamp, 4 bytes wide) to the rewriter.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_resp frame belonging to the PTP domain(s)
of system, it signals to the time stamp block which action to perform (Write). It also delivers the write
offset and data size (location of the reserved 4 bytes in the PTP header used to save the ns part of the
Rx time stamp, 4 bytes wide) to the rewriter.
If the time stamp block gets the Subtract_p2p action, it subtracts the value in the
active_timestamp_ns_p2p register from the correction_field data, and outputs the value on the
New_Field bus to the Rewriter block.
If the time stamp block gets the Write action, it outputs the value of the active_timestamp_ns register on
the New_field bus to the Rewriter block.
The following full calculations are performed:
• Sync frames: Internal Correction field = Original Correction field – (Raw_Timestamp_ns –
Local_correction) + Path_delay + Asymmetry
• Pdelay_req frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction
• Pdelay_resp frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction + Asymmetry

3.6.9.5 Egress, Mode B

If the analyzer detects that the frame is a IEEE 1588 Sync frame belonging to the PTP domain(s) of the
system, it signals to the time stamp block which action to perform (Add), along with the correction field of
the frame. It also delivers the write offset and data size (location of the correction field inside the frame,
8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_req frame belonging to the PTP domain(s)
of system, it signals to the time stamp block which action to perform (Write, Save), along with the original
correction field of the frame (will have the value of 0). It also delivers the write offset and data size (0- No
data is actually written into the frame) to the rewriter. In addition, it outputs the field that holds the frame
identifier (sequenceId from the PTP header) to the time stamp FIFO, to save along with the Tx time
stamp.
If the analyzer detects that the frame is a IEEE 1588 Pdelay_resp frame belonging to the PTP domain(s)
of system, it signals to the time stamp block which action to perform (Add - this requires that the
IEEE 1588 engine has subtracted the Rx time stamp from the correction field), along with the original
correction field of the frame. It also delivers the write offset and data size (location of the correction field
inside the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Write, Save action, it outputs the value of the active_timestamp_ns
register on the New_field bus to the Rewriter block and sets the save_timestamp bit.
If the time stamp block gets the Add action, it adds the correction field value to the value in the
active_timestamp_ns register and outputs the value on the New_Field bus to the Rewriter block.
The Tx time stamp FIFO block contains an (implementation specific) amount of buffer memory. It simply
stores the Tx time stamp values that it receives from the time stamp block together with the frame

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 56

Functional Descriptions

identifier data it receives from the Analyzer block, and has a CPU interface that allows the IEEE 1588
engine to read out the time stamp sets (Frame identifier + New Tx time stamp).
The following full calculations are performed:
• Sync frames: Correction field = Internal Correction field + (Raw_Timestamp_ns + Local_correction)
• Pdelay_req frames: FIFO = Raw_Timestamp_ns + Local_correction – Asymmetry
• Pdelay_resp frames: Correction field = Internal Correction field +
(Raw_Timestamp_ns + Local_correction)
Figure 30 • One-Step Peer-to-Peer Transparent Clock Mode B

PTP Pdelay _req/resp Frame PTP Sync Frame

Correction Field = B Correction Field = A
Reserved Bytes = 0
Reserved Bytes = 0

Central
IEEE 1588
IEEE 1588
Engine
PHY
(CPU)
PTP Pdelay _req Frame
PTP Sync Frame
PTP Pdelay _req/resp Frame Correction Field = C
Correction Field = A
Correction Field = B Reserved bytes = RxTimestamp + PTP Pdelay _resp Frame
Reserved Bytes = RxTimestamp Peer Delay Correction Field = D
(D = B – RxTimestamp )
Central
Engine recovers
Packet processing and IEEE 1588 frequency from Sync
Switching
Engine frames and controls
1588 frequency
PTP Sync Frame (CPU)
Correction Field = A
PTP Sync Frame
Reserved bytes = RxTimestamp +
PTP Pdelay _resp Frame PTP Pdelay _req Frame Correction Field = A
Peer Delay
Correction Field = D Correction Field = C Reserved bytes = RxTimestamp +
(D = B – RxTimestamp ) Peer Delay PTP Pdelay _req/resp Frame
Correction Field = B
Reserved Bytes = RxTimestamp
Central
IEEE 1588
Engine
(CPU)
PTP Sync Frame
PTP Pdelay _resp Frame PTP Pdelay _req Frame Correction Field =
Correction Field = D + TxTimestamp Correction Field = C A – RxTimestamp + TxTimestamp
(TxTimestamp saved in FIFO ) + Peer Delay
Reserved bytes = 0

3.6.10 Supporting Two-Step Transparent Clock

In two-step transparent clocks, the Rx and Tx time stamps are saved for the IEEE 1588 engine to read,
and the follow-up message is redirected to the IEEE 1588 engine so that it can update the correction field
with the residence time.
Even though two-step transparent clocks can be used with this architecture, it is also possible to process
the frames in the same manner as a one-step TC, because the slaves are required to take both the
correction fields from the Sync frames and the follow-up frames into account. This significantly reduces
the CPU load for the TC. The following illustration shows two-step transparent clock normal operation.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 57

Functional Descriptions

Figure 31 • Two-Step End-to-End Transparent Clock

PTP Sync Or Delay_req Frame
Correction Field = A
Reserved Bytes = 0

IEEE 1588
PHY

PTP Sync or Delay_req Frame

Correction Field = A
Reserved bytes = RxTimestamp

Central Engine recovers

Packet processing and IEEE 1588 frequency from Sync
frames and controls
Switching Engine 1588 frequency
PTP Sync Or Delay_req Frame
(CPU)
Correction Field = A
PTP Sync Or Delay_req Frame Reserved bytes = RxTimestamp
Correction Field = A
Reserved bytes = RxTimestamp

IEEE 1588
PHY

PTP Sync Or Delay_req Frame

Correction Field = A
Reserved bytes = 0
TxTimestamp and RxTimestamp in
FIFO

3.6.10.1 Ingress
If the analyzer detects that the frame is a IEEE 1588 Sync or Delay_req frame belonging to the PTP
domain(s) of the system, it signals to the time stamp block which action to perform (Write). The analyzer
also delivers the write offset and data size to the rewriter (four reserved bytes in the PTP header, which
will be passed out on the egress port of the system). A changed reserved value may be significant in
security protection. This method allows the frames to be copied to the IEEE 1588 engine, so that it can
extract the Rx time stamp and knows that it needs to read the Tx time stamps to be ready for the follow
up message. It is also possible to save the Rx time stamp value along with the Tx time stamp in the Tx
time stamp FIFO.
If the time stamp block gets the Write action, it outputs the current time stamp to the rewriter and the
rewriter writes the ns part of the time stamp into the reserved bytes and recalculates FCS.
The following full calculations are performed:
• Sync frames: Reserved_bytes = (Raw_Timestamp_ns – Local_correction) Correction
field = Original Correction field + Asymmetry
• Delay_req frames: Reserved_bytes = Raw_Timestamp_ns – Local_correction

3.6.10.2 Egress
If the analyzer detects that the frame is a IEEE 1588 Sync or Delay_req frame belonging to the PTP
domain(s) of the system, it signals to the time stamp block which action to perform (Write, Save). The
analyzer also delivers the write offset and data size (but as nothing is to be overwritten the values will be
0) to the rewriter. The analyzer outputs 10 bytes of frame identifier to the Tx time stamp FIFO to be saved
along with the Tx time stamp. The frame identifier must include, at minimum, the sequenceId field so the
CPU can match the time stamp with the follow-up frame. The analyzer also outputs the offset for the
reserved fields in the PTP header to the rewriter, so that the rewriter field is reset to 0 and the temporary
Rx time stamp value is cleared.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 58

Functional Descriptions

If the time stamp block gets the Write, Save action it outputs the current time stamp value to the rewriter
(and time stamp FIFO) and sets the save_timestamp bit. The time stamp FIFO block saves the New_field
data along with the frame identifier data it received from the analyzer block. The frame identifier data that
is saved can contain the reserved field in the PTP header that was written with the Rx time stamp, so that
the CPU now can read the set of Tx and Rx time stamp from the Tx time stamp FIFO.
The following full calculations are performed:
• Sync frames: FIFO = Raw_Timestamp_ns + Local_correction (reserved_bytes containing the Rx
time stamp saved together with Tx time stamp)
• Delay_req frames: FIFO = Raw_Timestamp_ns + Local_correction – Asymmetry (reserved_bytes
containing the Rx time stamp saved together with Tx time stamp)

3.6.11 Calculating OAM Delay Measurements

Frame delay measurements can be made as one-way and two-way delay measurements. Microsemi
recommends that the delay measurement be measured before the packets enter the queues if the
purpose is to measure the delay for different priority traffic, but it can be used with time stamping in the
PHY to measure the delay through the network devices placed in the path between the measurement
points.
The function is mainly an on-demand OAM function, but it can run continuously.

3.6.12 Supporting Y.1731 One-Way Delay Measurements

One-way delay measurements require that the two peers are synchronized in time. When they are not
synchronized, only frame delay variations can be measured.
The MEP periodically sends out 1DM OAM frames containing a TxTimeStampf value in IEEE 1588
format.
The receiver notes the time of reception of the 1DM frame and calculates the delay.
Figure 32 • Y.1731 1DM PDU Format
1 2 3 4
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
1 MEL Version (0) OpCode (1DM=45) Flags (0) TLV Offset (16)
5
TxTimeStampf
9
Reserved for 1DM receiving equipment (0)
13 (for RxTimeStampf)
17
End TLV (0)
21

1. For one-way delay measurements, both MEPs must support IEEE 1588 and be in sync.
2. 1DM frame is generated by the CPU, but with an empty Tx time stamp.
3. The frame is transmitted by the initiating MEP.
4. The 1DM frame is classified as an outgoing 1DM frame by the egress PHY and the PHY rewrites the
frame with the time as TxFCf.
5. The receiving PHY classifies the incoming 1DM frame and writes the receive time stamp in reserved
place (RxTimeStampf).
6. The frame is received by the peer MEP.
7. The frame is forwarded to the CPU that can calculate the delay.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 59

Functional Descriptions

Figure 33 • Y.1731 One-Way Delay

Y.1731 1DM Message

TxTimeStampf = A
RxTimeStampf = 0

IEEE 1588
PHY

Y.1731 1DM Message

TimeStampsf = A
RxTimeStampf = RxTimestamp
Y.1731 1DM Message
TimeStampsf = 0
RxTimeStampf = 0 Central
Packet processing and
Y.1731
Switching Engine
(CPU)
Y.1731 1DM Message
Y.1731 1DM Message TimeStampsf = A
TimeStampsf = 0 RxTimeStampf = RxTimestamp
RxTimeStampf = 0

IEEE 1588
PHY

Y.1731 1DM Message

TimeStampsf = TxTimestamp
RxTimeStampf = 0

3.6.12.1 Ingress
If the analyzer detects that the frame is a Y.1731 1DM PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). The analyzer also delivers the write offset and data size
(location of the RxTimeStampf location in the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Write action, it delivers the time stamp to the rewriter block and the
rewriter block adds this time stamp to the reserved bytes in the frame and recalculates FCS.
The following calculation is performed for 1DM frames:
• RxTimeStampf = (Raw_Timestamp – Local_correction)

3.6.12.2 Egress
If the analyzer detects that the frame is a Y.1731 1DM PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). It also delivers the write offset and data size (location of
the TxTimeStampf location in the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Write action, it delivers the time stamp to the rewriter block and the
rewriter block adds this time stamp to the reserved bytes in the frame and recalculates FCS.
The following calculation is performed for 1DM frames:
• TxTimeStampf = (Raw_Timestamp + Local_correction)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 60

Functional Descriptions

3.6.13 Supporting Y.1731 Two-Way Delay Measurements

When performing two-way delay measurements, the initiating MEP transmits DMM frames containing a
TxTimeStampf value. The receiving MEP replies with a DMR frame that is the same as the DMM frame,
but with destination and source MAC address swapped and with a different OAMPDU opcode.
When the DMR frame is received back at the initiating MEP, the time of reception is noted and the total
delay is calculated.
As an option, it is allowed to include two additional time stamps in the DMR frame: RxTimeStampf and
TxTimeStampb. These contain the time that the DMM page is received for processing and the time the
responding DMR reply is sent back, both in IEEE 1588 format.
Including these time stamps allows for the exclusion of the processing time in the peer MEP, but it does
not require that the two MEPs are synchronized.
Figure 34 • Y.1731 DMM PDU Format
1 2 3 4
8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1

1 M EL Version ( 0) O p Cod e (D M M=47) Flags (0) T LV O ffset (32)

5
T xT im eStam pf
9
Reserved for D MM receiving equip m ent (0)
13 (for RxT im eStam p f)
17
Reserved for D MR ( 0)
21 (for T xT im eStam pb)
25

29 Reserved for D MR receiving equip m ent (0)

33

37
End T LV (0)

In that case, the following frame flow is needed (two-way delay measurement):
1. DMM frame is generated by the CPU (initiating MEP), but with an empty Tx time stamp.
2. In the egress PHY the DMM frame is classified as an outgoing DMM frame from the MEP and the
PHY rewrites the frame with the time as TxTimeStampf.
3. In the ingress PHY the frame is classified as an incoming DMM belonging to the MEP and the
RxTimeStampf in the frame is written (the frame has a reserved space for this).
4. The DMM frame is forwarded to the MEP (CPU).
5. The CPU processes the frame (swaps SA/DA MAC addresses, modifies the opcode to DMT) and
sends out a DMT frame.
6. The outgoing DMT frame is detected in the egress PHY and the TxTimeStampb is written into the
frame.
7. In the ingress PHY the frame is classified as an incoming DMT belonging to the MEP and the
RxTimeStampb in the frame in written (the frame has a reserved space for this).
8. The frame is forwarded to the CPU that can calculate the delays.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 61

Functional Descriptions

Figure 35 • Y.1731 Two-Way Delay

Y.1731 DMR Message Y.1731 DMM Message
TxTimeStampf = D TxTimeStampf = A
RxTimeStampf = E RxTimeStampf = 0
TxTimeStampb = F TxTimeStampb = 0
RxTimeStampb = 0 RxTimeStampb = 0

IEEE 1588 Y.1731 DMM Message

PHY TxTimeStampf = 0
RxTimeStampf = 0
Y.1731 DMR Message Y.1731 DMM Message TxTimeStampb = 0
TxTimeStampf = D TxTimeStampf = A RxTimeStampb = 0
RxTimeStampf = E RxTimeStampf = RxTimestamp
Y.1731 DMR Message
TxTimeStampb = F TxTimeStampb = 0
TxTimeStampf = B
RxTimeStampb = RxTimestamp RxTimeStampb = 0
RxTimeStampf = C
TxTimeStampb = 0
RxTimeStampb = 0 Central
Packet processing and Y.1731
Switching Engine
Y.1731 DMM Message
(CPU)
Y.1731 DMR Message Y.1731 DMM Message TxTimeStampf = A
TxTimeStampf = B RxTimeStampf = RxTimestamp
TxTimeStampf = 0
RxTimeStampf = C TxTimeStampb = 0
RxTimeStampf = 0
TxTimeStampb = 0 RxTimeStampb = 0
TxTimeStampb = 0
RxTimeStampb = 0 RxTimeStampb = 0
Y.1731 DMR Message
TxTimeStampf = D
RxTimeStampf = E
IEEE 1588 TxTimeStampb = F
PHY RxTimeStampb = RxTimestamp

Y.1731 DMR Message Y.1731 DMM Message

TxTimeStampf = B TxTimeStampf = TxTimestamp
RxTimeStampf = C RxTimeStampf = 0
TxTimeStampb = TxTimestamp TxTimeStampb = 0
RxTimeStampb = 0 RxTimeStampb = 0

3.6.13.1 Ingress
If the analyzer detects that the frame is a Y.1731 DMM PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). It also delivers the write offset and data size (location of
the RxTimeStampf location in the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a Y.1731 DMT PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). It also delivers the write offset and data size (location of
the RxTimeStampf location in the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Write action, it delivers the time stamp to the rewriter block and the
rewriter block adds this time stamp to the reserved bytes in the frame and recalculates FCS.
The following calculations are performed:
• DMM frames: RxTimeStampf = (Raw_Timestamp – Local_correction)
• DMR frames: RxTimeStampb = (Raw_Timestamp – Local_correction)

3.6.13.2 Egress
If the analyzer detects that the frame is a Y.1731 DMM PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). It also delivers the write offset and data size (location of
the TxTimeStampf location in the frame, 8 bytes wide) to the rewriter.
If the analyzer detects that the frame is a Y.1731 DMT PDU frame belonging to the MEP, it signals to the
time stamp block which action to perform (Write). It also delivers the write offset and data size (location of
the TxTimeStampb location in the frame, 8 bytes wide) to the rewriter.
If the time stamp block gets the Write action, it delivers the time stamp to the rewriter block and the
rewriter block adds the time stamp to the reserved bytes in the frame and recalculates FCS as follows:
• DMM frames: TxTimeStampf = (Raw_Timestamp + Local_correction)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 62

Functional Descriptions

• DMR frames: TxTimeStampb = (Raw_Timestamp + Local_correction)

3.6.13.3 Supporting MPLS-TP One-Way and Two-Way Delay Measurements

MPLS-TP one- and two-way delay measurement are defined in RFC6374 (G.8113.2) and G.8113.1 (draft-
bhh). These mechanisms are similar to the ones described for Y.1731 Ethernet OAM delay
measurement, except for the encapsulations. The following illustrations show the PDU formats.
Figure 36 • RFC6374 DMM/DMR OAM PDU Format

ETH (1) 14/18/22B

MPLS labels (2) 4/8/12/16B
ACH 4B
OAM PDU Header 8B

DMM/DMR OAM PDUs

Time stamp 1 8B
Time stamp 1 8B
Time stamp 1 8B
Time stamp 1 8B
padding (variable size)
FCS 4B
(1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels

Figure 37 • Draft-bhh DMM/DMR/1DM OAM PDU Formats

DMM/DMR 1DM

ETH (1) 14/18/22B ETH (1) 14/18/22B

MPLS labels (2) 4/8/12/16B MPLS labels (2) 4/8/12/16B
ACH 4B ACH 4B
1DM OAM PDUs

OAM PDU Header 8B OAM PDU Header 8B

DMM/DMR OAM PDUs

Time stamp 1 8B Time stamp 1 8B

Time stamp 1 8B Time stamp 1 8B
Time stamp 1 8B End TLV indicator 1B
Time stamp 1 8B FCS 4B
End TLV indicator 1B (1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels
FCS 4B
(1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels

3.6.14 Device Synchronization for IEEE 1588 Support

It is important to keep all the local clock blocks synchronized to the accurate time over a complete
system. To maintain ns accuracy, the signal routing and internal signal delays must be taken into account
when configuring a system.
The architecture described in this document assumes that there is a global synchronous clock available
in the system. If the system is a telecom system where the system is locked to a PRC, the system clock
can be adjusted to match the PRC, meaning that once locked, the frequency of the system clock ensures
that the local clocks are progressing (counting) with the accurate frequency. This system clock can be
locked to the PRC using IEEE 1588, SyncE, SDH, or by other means.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 63

Functional Descriptions

A global timing signal must also be distributed to all the devices. This could be a 1 pps pulse or another
slow synchronization pulse, like a 4 kHz synchronization frequency. It can also just be a one-shot pulse.
The system CPU can load each local counter with the time value that happens next time the
synchronization pulse goes high (+ the known delay of the synchronization pulse traces). It can also just
load the same approximate time value into all the local clock blocks (again + the known delay of the
synchronization pulse traces) and load them in parallel. Then the local time can be adjusted to match the
actual time by adjusting the local clock blocks using the ±1 ns function.
If the Save signal is triggered synchronously on all PHYs of the system, software can read the saved time
stamp in each PHY and correct the time accordingly. On a blade with multiple PHYs, it is possible to
connect the 1588_PPS_1 pin on one PHY to the 1588_LOAD_SAVE pin on the next PHY. If the routing
delay (both internal chip delay and trace delay) is known, Microsemi recommends that the value saved in
the next PHYs correspond to this delay.
If the global system clock is not synchronous, the PPM offset between system clock and the IEEE 1588
time progress can be calculated. This PPM offset can be used to calculate how many local-time-clocks is
takes to reach a time offset of 1 ns and this value can be programmed into each local time block. The
CPU still need to keep track of the smaller PPM offset and adjust the local time blocks with ± writes when
necessary.
By measuring the skew between the 1 pps test output from each PHY, it is possible to measure the
nominal correction values for the time counters in a system. These can be incorporated into the software
of the system. Variations from system to system and temperature variations should be minimized by
design.

3.6.15 Time Stamp Update Block

The IEEE 1588 block is also called the Time Stamp Update block (TSU) and supports the implementation
of IEEE 1588v2 and ITU-T Y.1731 in PHY hardware by providing a mechanism for time stamp update
(PTP) and time stamping (OAM).
The TSU block works with other blocks to identify PTP/OAM messages, process these messages, and
insert accurate time stamp updates/time stamps where necessary. For IEEE 1588 timing distribution, the
VSC8491-17 device supports ordinary clocks, boundary clocks, end-to-end transparent clocks, and peer-
to-peer transparent clocks in a chassis based IEEE 1588 capable system. One-step and two-step
processing is also supported. For details on the timing protocol, refer to IEEE 1588v2. For OAM details,
refer to ITU-T Y.1731 and G.8113.1/G.8113.2. The TSU block implements part of the functionality
required for full IEEE 1588 compliance.
The IEEE 1588 protocol has four different types of messages that require action by the TSU: Sync,
Delay_req, Pdelay_req, and Pdelay_resp. These frames may be encapsulated in other protocols, several
layers deep. The processor is able to detect PTP messages within these other protocols. The supported
encapsulations are as follows:
• Ethernet
• UDP over IPv4
• UDP over IPv6
• MPLS
• Pseudo-wires
• PBB and PBB-TE tunnels
OAM frames for delay measurement (1DM, DMM, and DMR) with the following supported
encapsulations:
• Ethernet (Y.1731 Ethernet OAM)
• Ethernet in MPLS pseudo-wires (Y.1731 Ethernet OAM)
• MPLS-TP (G.8113.1 (~draft-bhh-mpls-tp-oam-y1731) and G.8113.2 (RFC6374))
The following illustration shows an overview of the supported PTP encapsulations. Note that the
implementation is flexible, so encapsulations not defined here may also be covered.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 64

Functional Descriptions

Figure 38 • PTP Packet Encapsulations

E TH 1

E TH 2 M P LS

"P B B " "E TH " "P W E " " IP -M P L S "

U n ta g g e d /T a g g e d d ra ft-ie tf-ticto c- d ra ft-ie tf- tic to c-
M A C -in - M A C
P B ( Q - in -Q ) 1 5 8 8 o ve rm p ls 1 5 8 8 o ve rm p ls
E TH 2 IP /U D P

IP /U D P IP /U D P IP /U D P

P TP P TP P TP P TP P TP P TP P TP

The following illustration shows the same overview of the supported encapsulations with the focus on
OAM.
Figure 39 • OAM Packet Encapsulations
ETH 1

ETH2 M PLS

"PBB " "ETH " "PW E " "ACH "

Untagged /Tagged
MAC -in-MAC
PB (Q -in-Q )
ACH
ETH 2 (RFC -5718)

Y .1731 OAM Y.1731 OAM Y.1731 OAM G .8113.1

(~draft-bhh-m pls-tp-oam-y1731)
G .8113.2 (RFC 6374)

There is one TSU per channel in the VSC8491-17 device. The TSU detects and updates up to three
different encapsulations of PTP/OAM. Non-matching frames are transferred transparently. This includes
IFG, preamble, and SFD. For all frames, there is no bandwidth expansion/shrink.
Once these frames are detected in the receive path, they are stamped with the ingress time and
forwarded for further PTP/OAM processing. In the transmit path, the correction field of the appropriate
PTP message (or the Rx and Tx fields of the OAM frame) is updated with the correct time stamp. A local
time counter is maintained to provide the time stamps. Implementation of some of the IEEE 1588
protocol requires interaction with the TSU block over the CPU interface and external processing.
The system has an ingress processor, egress processor, and a local time counter. The ingress and
egress processing logic blocks are identical, except that the time stamp FIFO is only required in the
egress direction because the CPU needs to know the actual time stamps of some of the transmitted PTP

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 65

Functional Descriptions

frames. The CPU reads the time stamps and any associated frame information out of the time stamp
FIFO. The FIFO saves the generated time stamps along with information that uniquely identifies the
frame to be read out by the CPU.
The ingress and egress processing blocks run on the same clock as the data paths for the corresponding
directions. The local time counter is the primary reference clock for the system and it maintains the local
reference time used by the TSU logic. It should be synchronized by an external entity. The block provides
a method to load and view its value when the 1588_LOAD_SAVE pin is asserted. The block also
provides a one pulse-per-second output signal with a programmable duty cycle. The local time counter
runs at several clock frequencies.
The following illustration shows the block diagram of the TSU.
Figure 40 • TSU Block Diagram
Ingress processor

Data

SOF
Data FIFO Rewriter
detect
Data

Corr_TS

Ingress Cntrl Time stamp

External
predictor
Analyzer 1 PPS Load/
Ingress Save
timing
Adapt domain
Local Time
Counter
Adapt Egress
Time stamp timing
FIFO Sign. domain
External TS Analyzer
Egress
Serial Time stamp Cntrl predictor
time
stamps Corr_TS

Data
SOF
Rewriter FIFO Data
detect

Data

Egress processor

In both directions, the input data from the PHY layer is first fed to an SOF detect block. Data is then fed to
both the programmable time-delay FIFO and the analyzer. The FIFO delays the data by the time needed
to complete the operations necessary to update the PTP frame. That is, the data is delayed to the input
of the rewriter so that the rewriter operations are known when the frame arrives. This includes the
analyzer and time stamp processor block's functions.
The analyzer block checks the data stream and searches for PTP/OAM frames. When one is detected, it
determines the appropriate operations to be performed based on the operating mode and the type of
frame detected.
Note: The analyzer blocks of two channels share configuration registers and have identical setups.
The time stamp block waits for an SOF to be detected, captures a time stamp from the local time counter,
and builds the new time stamp that is to be written into the PTP/OAM frame. Captured time stamps can
be read by the CPU.
The rewriter block handles the actual writing of the new time stamp into the PTP/OAM frame. It is also
able to clear parts of the frame such as the UDP checksum, if required, or it can update the frame to

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 66

Functional Descriptions

ensure that the UDP checksum is correct (for IPv6 PTP frames). The block also calculates the new FCS
to be written to the PTP frame after updating the fields with the new time stamp.
The VSC8491-17 device has variable latency in the PCS block. These variations are predicted and used
to compensate/maximize the accuracy of the IEEE 1588 time stamp logic.
If the time stamp update function is not used, the block can be bypassed. When the TSU is bypassed,
the block can be configured and then enabled and taken out of bypass mode. The change in bypass
mode takes effect only when an IDLE is in the bypass register. This allows the TSU block to be switched
on without corrupting data.
Each direction of the IEEE 1588 can be bypassed individually by programming the
INTERFACE_CTL.SPLIT_BYPASS bit. Bypass is then controlled by INTRERFACE_CTL.INGR_BYPASS
and INTERFACE_CTL.EGR_BYPASS.
Pause frames pass unmodified through the TSU, but the latency may cause a violation of the allowed
pause flow-control latency limits per IEEE 802.3.

3.6.16 Analyzer
The packet analyzer parses incoming packets looking for PTP/OAM frames. It determines the offset of
the correction field within the packet for all PTP frames/for the time stamp in Y.1731 OAM frames. The
analyzer has the following characteristics:
• Can compare against two different filter sets plus one optimized for OAM
• Each filter targets PTP or OAM frames
• Flexible comparator sequence with fixed start (Ethernet/SNAP) and end (PTP/OAM) comparator.
Configurable intermediate comparators (Ethernet/SNAP, 2x IP/UDP/ACH, and MPLS)
The following illustration shows a block diagram of the analyzer.
Figure 41 • Analyzer Block Diagram
Data
SOF Data
detect SOF
Analyzer

Encap Engine A controller

Offsets &
Next protocol

Ethernet/SNAP Ethernet/SNAP IP/UDP/ACH IP/UDP/ACH MPLS PTP/OAM

Comparator 1 Comparator 2 Comparator 1 Comparator 2 Comparator Comparator
Encap A Encap A Encap A Encap A Encap A Encap A

Align
Frame
signature
Encap Engine B controller builder
Offsets &
Next protocol

Ethernet/SNAP Ethernet/SNAP IP/UDP/ACH IP/UDP/ACH MPLS PTP/OAM

Comparator 1 Comparator 2 Comparator 1 Comparator 2 Comparator Comparator
Encap B Encap B Encap B Encap B Encap B Encap B

Encap Engine C
A controller
Offsets &
Next protocol

Ethernet/SNAP Ethernet/SNAP MPLS PTP/OAM

Comparator 1 Comparator 2 Comparator Comparator
Encap CA Encap CA (OAM optimized) Encap C
A Encap C
A
A- B- A- A- A- B-
flow flow flow flow flow flow
A-flow
B-flow

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 67

Functional Descriptions

The analyzer process is divided into engines and stages. Each engine represents a particular
encapsulation stack that must be matched. There are up to six stages in each engine. Each stage uses a
comparator block that looks for a particular protocol. The comparison is performed stage-by-stage until
the entire frame header has been parsed.
Each engine has its own master enable so that it can be shut down for major reconfiguration, such as
changes in encapsulation order, without stopping traffic. Other enabled engines are not affected.
The SOF detect block searches for the SFD in the preamble and uses that to indicate the SOF position.
This information is carried along in the pipeline and also passed to the analyzer.
The first stage of the analyzer is a data path aligner that aligns the first byte of the packet (without the
preamble & SFD) to byte 0 of the analyzer data path.
The encapsulation engine handles numerous types of encapsulation stacks. These can be broken down
to their individual protocols, and a comparator is defined for each type. The order in which these are
applied is configurable. Each comparator outputs a pattern/flow match bit and an offset to the start of the
next protocol. The cumulative offset points to the time stamp field.
The sequence in which the protocol comparators are applied is determined by configuration registers
associated with each comparator, and the transfer of parameters between comparators is controlled by
the encapsulation engine controller.
It receives the pattern match and offset information from one comparator stage and feeds the start-of-
protocol position to the next comparator. This continues until the entire encapsulation stack has been
parsed and always ends with the PTP/OAM stage (or until a particular comparator stage cannot find a
match in any of its flows). If at any point along the way no valid match is found in a particular stage, the
analyzer sends the NOP communication to the time stamp block indicating that this frame does not need
modification and that it should discard its time stamp.
There are two types of engines in the analyzer, one optimized for PTP frames and the other optimized for
OAM frames. The two engine types are mostly identical, except that the IP comparators are removed
from the OAM engines. The following table shows the comparator layout per engine type and the number
of flows in each comparator. There are two PTP engines and one OAM engine in each analyzer.
Additional differences in the Ethernet and MPLS blocks are defined in their respective sections. For more
information, see Ethernet/SNAP/LLC Comparator, page 69 and MPLS Comparator, page 73.

Table 18 • Flows Per Engine Type

Number of Flows
Comparator PTP Engine OAM Engine
Ethernet 1 8 8
Ethernet 2 8 8
MPLS 8 8
IP/ACH 1 8 0
IP/ACH 2 8 0
PTP/OAM 6 6

Encapsulation matches can be set independently in each direction by setting the

ANALYZER_MODE.SPLIT_ENCAP_FLOW register. However, strict and non-strict flow cannot be set
independently for group A and group B of analyzer engine C.
Choice of strict flow or non-strict has to be made on each direction rather than on an engine by engine
basis. Valid values for INGR_ENCAP_FLOW_ENA and EGR_ENCAP_FLOW_ENA are 3'b000 or
3'b111.
Each comparator stage has an offset register that points to the beginning of the next protocol relative to
the start of the current one. The offset is in bytes, and the first byte of the current protocol counts as byte
0. As an example, the offset register for a stage would be programmed to 10 when the header to match is
10 bytes long. With the exception of the MPLS stage (offsets are automatically calculated in that stage),

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 68

Functional Descriptions

it is the responsibility of the programmer to determine the value to put in these registers. This value must
be calculated based upon the expected length of the header, and is not expected to change from frame-
to-frame when matching a given flow.

Table 19 • Ethernet Comparator: Next Protocol

Parameter Width Description

Encap_Engine_ENA 1 bit For each encapsulation engine and enable bit that turns the engine on or
off. The engine enables and disables either during IDLE (all 8 bytes must
be IDLE) or at the end of a frame. If the enable bit is changed during the
middle of a frame, the engine will wait until it sees either of those
conditions before turning on or off.
Encap_Flow_Mode 1 bit There is a separate bit for each engine. For each encapsulation engine:
1 = Strict flow matching, a valid frame must use the same flow IDs in all
comparators in the engine except the PTP and MPLS comparators.
0 = A valid frame may match any enabled flow in all comparators
If more than one encapsulation produces a match, the analyzer sends
NOP to the rewriter and sets a sticky bit.

The following table shows the ID codes comparators use in the sequencing registers. The PTP packet
target encapsulations require only up to five comparators.

Table 20 • Comparator ID Codes

ID Name Sequence
0 Ethernet Comparator 1 Must be the first
1 Ethernet Comparator 2 Intermediate
2 IP/UDP/ACH Comparator 1 Intermediate
3 IP/UDP/ACH Comparator 2 Intermediate
4 MPLS Comparator Intermediate
5 PTP/OAM Comparator Must be the last

The following sections describe the comparators. The frame format of each comparator type is described
first, followed by match/mask parameter definition. All upper and lower bound ranges are inclusive and
all match/mask registers work the same way. If the corresponding mask bit is 1, then the match bit is
compared to the incoming frame. If a mask bit is 0, then the corresponding match bit is ignored (a
wildcard).

3.6.16.1 Ethernet/SNAP/LLC Comparator

There are two such comparators in each engine. The first stage of each engine is always an
Ethernet/SNAP/LLC comparator. The other comparator can be configured to be at any point in the chain.
Ethernet frames can have multiple formats. Frames that have an actual length value in the ether-type
field (Ethernet type I) can have one of three formats: Ethernet with an EtherType (Ethernet type II),
Ethernet with LLC, or Ethernet with LLC & SNAP. Each of these formats can be compounded by having
one or two VLAN tags.

3.6.16.1.1 Type II Ethernet

Type II Ethernet is the most common and basic type of Ethernet frame. The Length/EtherType field
contains an EtherType value and either 0, 1, or 2 VLAN tags. Both VLAN can be of type S/C (with
EtherType 0x8a88/0x8100). The payload would be the start of the next protocol.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 69

Functional Descriptions

Figure 42 • Type II Ethernet Basic Frame Format

Destination Address (DA) Source Address (SA) Etype Payload

5 4 3 2 1 0 5 4 3 2 1 0 1 0

Destination Address (DA) Source Address (SA) VLAN Tag Etype Payload
5 4 3 2 1 0 5 4 3 2 1 0 3 2 1 0 1 0

Destination Address (DA) Source Address (SA) VLAN Tag 1 VLAN Tag 2 Etype Payload
5 4 3 2 1 0 5 4 3 2 1 0 3 2 1 0 3 2 1 0 1 0

3.6.16.1.2 Ethernet with LLC and SNAP

If an Ethernet frame with LLC contains a SNAP header, it always follows a three-octet LLC header. The
LLC values for DSAP & SSAP are either 0xAA or 0xAB and the control field contains 0x03. The SNAP
header is five octets long and consists of two fields, the 3-octet OUI value and the 2-octet EtherType. As
with the other types of Ethernet frames, this format can have 0, 1, or 2 VLAN tags. The OUI portion of the
SNAP header is hard configured to be 0 or 0xf8.
The following illustration shows an Ethernet frame with a length in the Length/EtherType field, an LLC
header, and a SNAP header.
Figure 43 • Ethernet Frame with SNAP
Protocol ID
Destination Address (DA) Source Address (SA) Length DSAPSSAP Ctl 0x000000 EtherType
5 4 3 2 1 0 5 4 3 2 1 0 1 0 A A/AB AA/AB 0x03 2 1 0 1 0

The following illustration shows an Ethernet frame with an LLC/SNAP header and a VLAN tag in the
SNAP header. The Ethertype in the SNAP header is the VLAN identifier and tag immediately follows the
SNAP header.
Figure 44 • Ethernet Frame with VLAN Tag and SNAP
DSAPSSAP Ctl Protocol ID
Destination Address (DA ) Source Address (SA) Length 0x000000 VLAN EType VLAN Tag ID
$ # $ # $ $ $ $ $ # $ $ # # AA/AB AA/AB 0x03 # # # # # # #

The following illustration shows the longest form of the Ethernet frame header that needs to be
supported: two VLAN tags, an LLC header, and a SNAP header.
Figure 45 • Ethernet Frame with VLAN Tags and SNAP
LLC SNAP

VLAN 1 VLAN 1 VLAN 2 VLAN 2 Protocol ID

Destination Address (DA) Source Address (SA) EtherType Tag EtherType Tag Etype DSAPSSAP Ctl Payload
5 4 3 2 1 0 5 4 3 2 1 0 1 0 1 0 1 0 1 0 1 0 AA/AB AA/AB 0x03 2 1 0 1 0

3.6.16.1.3 Provider Backbone Bridging (PBB) Support

The provider backbone bridging protocol is supported using two Ethernet comparator blocks back-to-
back. The first portion of the frame has a type II Ethernet frame with either 0 or 1 VLAN tags followed by
an I-tag. The following illustrations show two examples of the PBB Ethernet frame format.
Figure 46 • PBB Ethernet Frame Format (No B-Tag)

First Ethernet Comparator Second Ethernet Comparator

I-Tag

EtherType Rest of
Backbone Destination Address(B-DA) Backbone Source Address (B-SA) 88E7
Flags SID Customer Destination Address (C-DA) Customer Source Address (C-SA)
5 4 3 2 1 0 5 4 3 2 1 0 1 0 0 2 1 0 5 4 3 2 1 0 5 4 3 2 1 0 E-net Header

Figure 47 • PBB Ethernet Frame Format (1 B-Tag)

First Ethernet Comparator Second Ethernet Comparator

B-Tag I-Tag

EtherType EtherType Flags Rest of

Backbone Destination Address (B-DA) Backbone Source Address (B-SA) 88A8
B-VID
88E7 SID Customer Destination Address (C-DA) Customer Source Address (C-SA)
5 4 3 2 1 0 5 4 3 2 1 0 1 0 1 0 1 0 0 2 1 0 5 4 3 2 1 0 5 4 3 2 1 0
E-net Header

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 70

Functional Descriptions

3.6.16.1.4 Ethernet Comparison

The Ethernet comparator block has two forms of comparison, as follows:
• Next protocol comparison is common for all flows in the comparator. It is the single set of registers
and is used to verify what the next protocol in the encapsulated stack will be.
• Flow comparison is used to match any of the possible flows within the comparator.

3.6.16.1.5 Ethernet Next Protocol Comparison

The next protocol comparison field looks at the last EtherType field in the header (there can be multiple in
the header) to verify the next protocol. It may also look at VLAN tags and the EtherType field when it is
used as a length. Each has a pattern match/mask or range, and an offset.
The following table lists the next protocol parameters for the Ethernet comparator.

Table 21 • Ethernet Comparator (Next Protocol)

Parameter Width Description

Eth_Nxt_Comparator 3 bit Pointer to the next comparator.
Eth_Frame_Sig_Offset 5 bit Points to the start of the field used to build the frame signature.
Eth_VLAN-TPID_CFG 16 bit Globally defines the value of the TPID for an S-tag, B-tag, or
any other tag type other than a C-tag or I-tag.
Eth_PBB_ENA 1 bit Configures if the packet carries PBB or not. This configuration
bit is only present in the first Ethernet comparator block. PBB is
disabled in Ethernet comparator block 2.
Eth_Etype_Match_Enable 1 bit Configures if the Ethertype field match register is used or not.
Only valid when the packet is a type II Ethernet packet.
Eth_Etype_Match 16 bit If the packet is a type II Ethernet packet and
Eth_Etype_Match_Enable is a 1, the Ethertype field in the
packet is compared against this value.

3.6.16.1.6 Ethernet Flow Comparison

The Ethernet flow is determined by looking at VLAN tags and either the source address (SA) or the
destination address (DA). There are a configurable number of these matched sets. The following table
lists the flow parameters for the Ethernet comparator.

Table 22 • Ethernet Comparator (Flow)

Parameter Width Description

Eth_Flow_Enable 1 bit/flow 0 = Flow disabled
1 = Flow enabled
Eth_Channel_Mask 1 0 = Do not use this flow match group for this channel
bit/channel/flow 1 = Use this flow match group for this channel
Eth_VLAN_Tags 2 bit Configures the number of VLAN tags in the frame (0,
1, or 2)
Eth_VLAN_Tag1_Type 1 bit Configures the VLAN tag type for VLAN tag 1
If PBB is not enabled:
0 = C-tag, value of 0x8100
1 = S-tag, match to the value in CONF_VLAN_TPID
(global for all ports/directions)
If PBB enabled:
0 = S-tag (or B-tag), to the value in
CONF_VLAN_TPID (global for all ports/directions)
There must be 2 VLAN tags, 1 S-tag and one I-tag
1 = I-tag

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 71

Functional Descriptions

Table 22 • Ethernet Comparator (Flow) (continued)

Parameter Width Description

Eth_VLAN_Tag2_Type 1 bit Configures the VLAN tag type for VLAN tag 2
If PBB is not enabled:
0 = C-tag, value of 0x8100
1 = S-tag, match to the value in CONF_VLAN_TPID
(global for all ports/directions)
If PBB enabled:
The second tag is always an I-tag and this register
control bit is not used. The second tag in PBB is
always an I-tag.
Eth_Ethertype_Mode 1 bit 0 = Only type 2 Ethernet frames supported, no
SNAP/LLC expected
1 = Type 1 & 2 Ethernet packets supported. Logic
looks at the Ethertype/length field to determine the
packet type. If the field is a length (less than 0x0600),
then the packet is a type 1 packet and MUST include a
SNAP & 3-byte LLC header. If the field is not a length,
it is assumed to be an Ethertype and SNAP/LLC must
not be present
Eth_VLAN_Verify_Ena 1 bit 0 = Parse for presence of VLAN tags but do not check
the values. For PBB mode, the I-tag is still always
checked.
1 = Verify the VLAN tag configuration including
number and value of the tags.
Eth_VLAN_Tag_Mode 2 bit 0 = No range checking on either VLAN tag
1 = Range checking on VLAN tag 1
2 = Range checking on VLAN tag 2
Eth_Addr_Match 48 bit Matches an address field selected by
Eth_Addr_Match_Mode
Eth_Addr_Match_Select 2 bit Selects the address to match
0 = Match the destination address
1 = Match the source address
2 = Match either the source or destination address
3 = Reserved, do not use
Eth_Addr_Match_Mode 3 bits per flow Selects the address match mode. One or multiple bits
can be set in this mode register allowing any
combination of match types. For unicast or multicast
modes, only the MSB of the address field is checked
(0 = unicast; 1 = multicast). See section 3.2.3.1 of
802.3 for more details.
0 = Match the full 48-bit address
1 = Match any unicast address
2 = Match any multicast address
Eth_VLAN_Tag1_Match 12 bit Match field for the first VLAN tag (if configured to be
present).
Eth_VLAN_Tag1_Mask 12 bit Mask for the first VLAN tag. If a match set is not used,
set this register to all 0s.
Eth_VLAN_Tag2_Match 12 bit Match field for the update VLAN tag (if configured to
be present).
Eth_VLAN_Tag2_Mask 12 bit Mask for the second VLAN tag. If a match set is not
used, set this register to all 0s.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 72

Functional Descriptions

Table 22 • Ethernet Comparator (Flow) (continued)

Parameter Width Description

Eth_VLAN_Tag_Range_Upper 12 bit Upper limit of the range for one of the VLAN fields
selected by ETH_VLAN_TAG_MODE register. If PBB
mode is enabled, this register is not used for range
checking but rather is the upper 12 bit of the I-tag.
Eth_VLAN_Tag_Range_Lower 12 bit Lower limit of the range for one of the VLAN fields
selected by ETH_VLAN_TAG_MODE register. If PBB
mode is enabled, this register is not used for range
checking but rather is the lower 12 bit of the I-tag SID.
Eth_Nxt_Prot_Grp_Sel 1 bit Per flow, maps a particular flow to a next-protocol
group register set. This register only appears in the
Ethernet block in the OAM-optimized engine.

If the Ethernet block is part of the OAM optimized engine, there are two sets of next-protocol
configuration registers. Both sets are identical, except one has an _A suffix and the other has a _B suffix.
In the per-flow registers, an additional register, ETH_NXT_PROT_SEL, is included to map a particular
flow with a set of next protocol register set. This function allows the Ethernet block within the OAM-
optimized engine to act like two separate engines with a configurable number of flows assignable to each
(with a total maximum number of eight flows). It effectively allows two separate protocol encapsulation
stacks to be handled within the engine.

3.6.16.2 MPLS Comparator

The MPLS comparator block counts MPLS labels to find the start of the next protocol. The MPLS header
can have anywhere from 1 to 4 labels. Each label is 32 bit long and has the format shown in the following
illustration.
Figure 48 • MPLS Label Format
Label Class S Time To Live
19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 2 1 0 7 6 5 4 3 2 1 0

The S bit is used to indicate the last label in the stack, as follows: If S = 0, then there is another label. If
S = 1, then this is the last label in the stack.
Also, the MPLS stack can optionally be followed by a control word (CW). This is configurable per flow.
The following illustration shows a simple Ethernet packet with either one label or three labels and no
control word.
Figure 49 • MPLS Label Stack within an Ethernet Frame
CW=0 Destination Address (DA)
5 4 3 2 1 0 5
Source Address (SA)
4 3 2 1 0
Etype
1 0 3
Label (S=1)
2 1 0
Payload

CW=0 Destination Address (DA) Source Address (SA) Etype Label (S=0) Label (S=0) Label (S=1) Payload
5 4 3 2 1 0 5 4 3 2 1 0 1 0 3 2 1 0 3 2 1 0 3 2 1 0

The following illustration shows an Ethernet frame with four labels and a control word. Keep in mind that
this comparator is used to compare the MPLS labels and control words; the Ethernet portion is checked
in the first stage.
Figure 50 • MPLS Labels and Control Word
CW=1 Destination Address (DA) Source Address (SA) Etype Label (S=0) Label (S=0) Label (S=0) Label (S=1) Control Payload
5 4 3 2 1 0 5 4 3 2 1 0 1 0 3 2 1 0 3 2 1 0 3 2 1 0 3 2 1 0 3 2 1 0

There could be VLAN tags between the SA and the Etype fields and, potentially, a LLC and SNAP
header before the MPLS stack, but these would be handled in the Ethernet/LLC/SNAP comparator.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 73

Functional Descriptions

The only configuration registers that apply to all flows within the comparator are the match_mode register
and the nxt_comparator register. The match mode register determines how the match filters are used,
and there is one per stage. Each flow has it own complete set of match registers.

Table 23 • MPLS Comparator: Next Word

Parameter Width Description

MPLS_Nxt_Comparator 3 bit Pointer to the next comparator

Table 24 • MPLS Comparator: Per-Flow

Parameter Width Description

MPLS_Flow_Enable 1 bit per flow 0 = Flow disabled
1 = Flow enabled
MPLS_Channel_Mask 1 bit per channel 0 = Do not use this flow match group for this channel
per flow 1 = Use this flow match group for this channel
MPLS_Ctl_Word 1 bit Indicates if there is a 32-bit control word after the last
label. This should only be set if the control word is not
expected to be an ACH header. ACH headers are
checked in the IP block. If the control word is a non-
ACH control word, only the upper 4 bits of the control
are checked and are expected to be 0.
0 = There is no control word after the last label
1 = There is expected to be a control word after the
last label
MPLS_REF_PNT 1 bit The MPLS comparator implements a searching
algorithm to properly parse the MPLS header. The
search can be performed from either the top of the
stack or the end of the stack.
0 = All searching is performed starting from the top of
the stack
1 = All searching if performed from the end of the
stack
MPLS_STACK_DEPTH 4 bit Each bit represents a possible stack depth, as shown
in the following list.
MPLS_STACK_DEPTH Bit Allowed Stack Depth
0 1
1 2
2 3
3 4

Table 25 • MPLS Range_Upper/Lower Label Map

MPLS_REF_PNT = 0, MPLS_REF_PNT=1,
Parameter top-of-stack referenced end-of-stack referenced
MPLS_Range_Upper/Lower_0 Top label Third label before the end label
MPLS_Range_Upper/Lower_1 First label after the top label Second label before the end
label
MPLS_Range_Upper/Lower_2 Second label after the top label First label before the end label
MPLS_Range_Upper/Lower_3 Third label after the top label End label

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 74

Functional Descriptions

The offset to the next protocol is calculated automatically. It is based upon the number of labels found,
and whether a control word is configured to be present. It points to the first octet after the last label or
after the control word, if present.

Table 26 • Next MPLS Comparator

Parameter Width Description

MPLS_Range_Lower 20 bit × 4 labels Lower value of the label range when range checking
is enabled
MPLS_Range_Upper 20 bit × 4 labels Upper value of the label range when range checking
is enabled

If an exact label match is desired, set the upper and lower range values to the same value. If a label
value is a don't care, then set the upper value to the maximum value and the lower value to 0.
The MPLS comparator block used in the OAM-optimized engine differs from the one used in the PTP-
optimized engine.
Just like the Ethernet comparator block, there are two sets of next protocol blocks along with a next
protocol association configuration field per-flow. This allows two different encapsulations to occur in a
single engine.

Table 27 • Next-Protocol Registers in OAM-Version of MPLS Block

Parameter Width Description

MPLS_Nxt_Prot_Grp_Sel 1 bit per flow Maps each flow to next-protocol-register set A or B

3.6.16.3 IP/UDP/ACH Comparator

The IP/UDP/ACH comparator is used to verify one of three possible formats: IPv4, IPV6, and ACH.
Additionally, IPv4 and IPv6 can also have a UDP header after the IP header. There are two of these
comparators and they can operate at stages 2, 3, or 4 of the analyzer pipeline. Note that if there is an
IP-in-IP encapsulation, a UDP header will only exist with the inner encapsulation.

3.6.16.4 IPv4 Header Format

The following illustration shows an IPv4 frame header followed immediately by a UDP header. IPv4 does
not always have the UDP header, but the comparator is designed to work with or without it. The Header
Length field is used to verify the offset to the next protocol. It is a count of 32-bit words and does not
include the UDP header. If the IPv4 frame contains a UDP header, the Source and Destination ports are
also checked. These values are the same for all flows within the comparator. Note that IPv4 options,
extended headers, and UDP fragments are not supported.
Figure 51 • IPv4 with UDP
0 31
Octet/Bit
Version Hdr Length Differentiated Services Total Length
0/0 3 2 1 0 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Identification Flags Fragment Offset

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 2 1 0 12 11 10 9 8 7 6 5 4 3 2 1 0

Time to Live Protocol Header Checksum

IPv4 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Source Address
16/128 Destination Address
Source Port Destination Port
UDP
24/192 Length Checksum (over-write with 0)

Per flow validation is performed on the Source or Destination Address in the IPv4 header. The
comparator can be configured to indicate a match in the flow if the source, destination, or either the
source or destination fields match.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 75

Functional Descriptions

3.6.16.5 IPv6 Header Format

The following illustration shows an IPv6 frame header followed immediately by a UDP header. IPv6 does
not always have the UDP header, but the comparator is designed to work with or without it. The Next
Header field is used to verify the offset to the next protocol. It is a count of 32-bit words and does not
include the UDP header. If the IPv6 frame contains a UDP header, the Source and Destination ports are
also checked. These values are the same for all flows within the comparator.
Figure 52 • IPv6 with UDP
0 31
Octet/Bit
Version Traffic Class Flow Label
0/0 3 2 1 0 7 6 5 4 3 2 1 0 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Payload Length Next Header Hop Limit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

Source Address
IPv6

Destination Address

24/288
Source Port Destination Port
UDP 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Length Checksum
40/352 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Per flow validation is performed on the Source or Destination Address in the IPv6 header. The
comparator can be configured to indicate a match in the flow if the source, destination, or either the
source or destination fields match.
If the IPv6 frame is the inner most IP protocol, then the checksum field must be valid. This is
accomplished using a pair of pad bytes after the PTP frame. The checksum is computed using one's
compliment of the one's compliment sum of the IPv6 header, UDP header, and payload including the pad
bytes. If any of the fields in the frame are updated, the pad byte field must be updated so that the
checksum field does not have to be modified.
Note: IPv6 extension headers are not supported.

3.6.16.6 ACH Header Format

The following illustrations show ACH headers. They can appear after a MPLS label stack in place of the
control word. ACH is verified as a protocol only. There are no flows within the protocol for ACH. The ACH
header can optionally have a Protocol ID field. The protocol is verified using the Version, Channel Type,
and optional Protocol ID field.
Figure 53 • ACH Header Format
0 31
Octet/Bit
0x1 Version Reserved Channel Type
0/0 3 2 1 0 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

4/32 Protocol ID or Payload Payload

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Figure 54 • ACH Header with Protocol ID Field

Octet /Bit
0 31

0/0 0x1 Version Reserved Channel Type

3 2 1 0 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

4/32 Protocol ID
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

3.6.16.7 IPSec
IPSec adds security to the IP frame using an Integrity Check Value (ICV), a variable-length checksum
that is encoded with a special key. The key value is known by the sender and the receiver, but not any of

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 76

Functional Descriptions

the devices in between. A frame must have a correct ICV to be valid. The sequence number field is a
continuously incrementing value that is used to prevent replay attacks (resending a known good frame).
Little can be done with frames when IPSec is used, because the IEEE 1588 block cannot recalculate the
ICV and the frame cannot be modified on egress. Therefore, one-step processing cannot be performed-
only two-step processing can be done. The only task here is to verify the presence of the protocol
header. Stored time stamps in the TS FIFO are used to create follow-up messages. On ingress, the time
stamp can be added to the PTP frame by writing it into the reserved bytes or by overwriting the CRC with
it and appending a new CRC. The CPU must know how to handle these cases correctly.
The following illustration shows the format of the IPSec frame. It normally appears between the IP
header (IPv4 or IPv6) and the UDP header or at the start of the payload.
Figure 55 • IPSec Header Format
0 31
Octet/Bit
Next Header Payload Length Reserved
0/0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

31 30 29 28 27 26 25 24 23 22 21 20
Security Parameters Index (SPI)
19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Sequence Number
8/64 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Integrity Check Value (ICV)

variable # ...
of octets

There is only one set of match/mask registers associated with IPSec, and they are used to verify the
presence of the IPSec header. The following illustration shows the largest possible IP frame header with
IPv6, IPSec, and UDP.
Figure 56 • IPv6 with UDP and IPSec
0 31
Octet/Bit
0/0 3
Version
2 1 0 7 6
Traffic Class
5 4 3 2 1 0 19 18 17 16 15 14 13 12 11
Flow Label
10 9 8 7 6 5 4 3 2 1 0

Payload Length Next Header Hop Limit

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

Source Address
IPv6

Destination Address

36/288
Next Header Payload Length Reserved
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Security Parameters Index (SPI)

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

48/384 Sequence Number

31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

IPSec
Integrity Check Value (ICV)
variable #
of octets Source Port Destination Port
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
UDP
Length Checksum
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 77

Functional Descriptions

3.6.16.8 Comparator Field Summary

The following table shows a summary of the fields and widths to verify IPv4, IPv6, and ACH protocols.

Table 28 • Comparator Field Summary

Protocol Next Protocol Fields NPF Bit Widths Flow Fields Flow Bit Widths
IPv4 Header length One 4-bit field Source/ One 32-bit field
Destination
Address
UDP Source/Destination Port One 32-bit field
IPv6 Next header One 8-bit field Source/ One 128-bit field
Destination
Address
UDP Source/Destination Port One 32-bit field
ACH Entire ACH header One 64-bit field
IPSec Next Header/Payload Length/ One 64-bit field
SPI

3.6.16.8.1 IP/ACH Comparator Next Protocol

The following table shows the registers used to verify the current header protocol and the next protocol.
They are universal, and cover IPv4, IPv6, and ACH. They can also be used to verify other future
protocols.

Table 29 • IP/ACH Next-Protocol Comparison

Parameter Width Description

IP_Mode 2 bit Specifies the mode of the comparator. If IPv4 or IPv6 is selected, the
version field is automatically checked to be either 4 or 6 respectively. If
another protocol mode is selected, then the version field is not
automatically checked. In IPv4, the fragment offset field must be 0, and
the MF flag bit (LSB of the flag field) must be 0.
0 = IPv4
1 = IPv6
2 = Other protocol, 32-bit address match
3 = Other protocol, 128-bit address match
IP_Prot_Match_1 8 bit Match bit for Protocol field in IPv4 or next header field in IPv6
IP_Prot_Mask_1 8 bit Mask bits for IP_Prot_Match_1. For each bit, if it is a 1, the
corresponding match bit is valid. If it is 0, the corresponding match bit
is ignored. Disable this match/mask set by setting the mask register to
all 0’s.
IP_Prot_Offset_1 5 bit Indicates the starting position relative to the beginning of the IP frame
header to start matching for the match/mask 1 register pair.
IP_Prot_Match_2 64 bit Match bits for the IPSec header or any other desired field. For ACH,
this register should be used to match the ACH header.
IP_Prot_Mask_2 64 bit Mask bits for IP_Prot_Match_2. For each bit, if it is a 1, the
corresponding match bit is valid. If it is 0, the corresponding match bit
is ignored. Disable this match/mask set by setting the mask register to
all 0’s.
IP_Prot_Offset_2 7 bit Indicates the starting position relative to the beginning of the IP frame
header to start matching for the match/mask two-register pair.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 78

Functional Descriptions

Table 29 • IP/ACH Next-Protocol Comparison (continued)

Parameter Width Description

IP_Nxt_Protocol 8 bit Points to the start of the next protocol relative to the beginning of this
header. It is the responsibility of the programmer to determine this
offset, it is not calculated automatically. Each flow within an
encapsulation engine must have the same encapsulation order and
each header must be the same length. This field is current protocol
header length in bytes.
IP_Nxt_Comparator 3 bit Pointer to the next comparator.
0 = Reserved
1 = Ethernet comparator 2
2 = IP/UDP/ACH comparator 1
3 = IP/UDP/ACH comparator 2
4 = Reserved
5 = PTP/OAM comparator
6,7 = Reserved
IP_Flow_Offset 5 bit Indicates the starting position relative to the beginning of the IP frame
header to start matching for the flow match/mask register pair. When
used with IPv4 or 6, this will point to the first byte of the source
address. When used with a protocol other that IPv4 or 6, this register
points to the beginning of the field that will be used for flow matching.
IP_UDP_Checksum 1 bit If set, the 2-byte UDP checksum should be cleared (written with
_Clear_Ena zeroes). This would only be used for UDP in IPv4.
IP_UDP_Checksum 1 bit If set, the last two bytes in the UDP frame must be updated to reflect
_Update_Ena changes in the PTP or OAM frame. This is necessary to preserve the
validity of the IPv6 UDP checksum.
Note that IP_UDP_Checksum_Clear_Ena &
IP_UDP_Checksum_Update_Ena should never be set at the same
time.
IP_UDP_Checksum 8 bit This configuration field is only used if the protocol is IPv4. This register
_Offset points to the location of the UDP checksum relative to the start of this
header. This info is used later by the PTP/Y.1731 block to inform the
rewriter of the location of the checksum in a UDP frame. This is
normally right after the Log Message Interval field.
IP_UDP_Checksum 2 bit Specifies the length of the UDP checksum in bytes (normally 2 bytes)
_Width

The IP/ACH Comparator Flow Verification registers are used to verify the current frame against a
particular flow within the engine. When this engine is used to verify IPv4 or IPv6 protocol, the flow is
verified using either the source or destination address in the frame.
If the protocol is something other than IPv4 or IPv6, then the flow match can be used to match either a 32
or 128 bit field pointed to by the IP_Flow_Offset register. Mask bits can be used to shorten the length of
the match, but there is no concept of source or destination address in this mode.

Table 30 • IP/ACH Comparator Flow Verification Registers

Parameter Width Description

IP_Flow_Ena 1 bit per flow 0 = Flow disabled
1 = Flow enabled

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 79

Functional Descriptions

Table 30 • IP/ACH Comparator Flow Verification Registers (continued)

Parameter Width Description

IP_Flow_Match_Mode 2 bit per flow This register is only valid when the comparator block is
configured to match on IPv4 or IPv6. It allows the match
to be performed on the source address, destination
address, or either address.
0 = Match on the source address
1 = Match on the destination address
2 = Match on either the source or the destination
address
IP_Flow_Match 128 bit Match bits for source & destination address in IPv4 & 6.
Also used as the flow match for protocols other than
IPv4 or 6. When used with IPv4, only the upper 32 bits
are used and the remaining bits are not used.
IP_Flow_Mask 128 bit Mask bits for IP_Flow_Match. For each bit, if it is a 1, the
corresponding match bit is valid. If it is 0, the
corresponding match bit is ignored.
IP_Channel_Mask 1 bit per Enable for this match set for this channel
channel per
flow
IP_Frame_Sig_Offset 5 bit Points to the start of the field that will be used to build
the frame signature. This register is only present in
comparators where frame signature is supported. In
other words, if there is no frame signature FIFO in a
particular direction, this register will be removed.

3.6.16.9 PTP/OAM Comparator

The PTP/OAM comparator is always the last stage in the analyzer for each encapsulation engine. It can
validate IEEE 1588 PTP frames or OAM frames.

3.6.16.10 PTP Frame Header

The following illustration shows the header of a PTP frame.
Figure 57 • PTP Frame Layout
0 31
Octet/Bit
Tspt Spcfc Msg Type Rsvd Vrsn PTP Message Length
0/0 3 2 1 0 3 2 1 0 3 2 1 0 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Domain Number Reserved Flag Field

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Correction Field

Reserved
Source Port Identity [79:48 ]
79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

Source Port Identity [47:16 ]

47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

Source Port Identity [15 :0] Sequence ID

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

32/256 Control Field Log Message Interval

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

Unlike most of the other stages, there is no protocol validation for PTP frames; only interpretation of the
header to determine what action to take. The first eight bytes of the header are used to determine the
action to be taken. These match fields in the flow comparison registers with a corresponding set of
command registers for each flow.

3.6.16.11 Y.1731 OAM Frame Header

1DM, DMM, and DMR are the three supported Y.1731 frame headers. The following illustration shows
the header part of a 1DM Y.1731 OAM frame.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 80

Functional Descriptions

Figure 58 • OAM 1DM Frame Header Format

0 1DM Frame Header Format 31

Octet/Bit
MEG Version (0) Opcode (1DM=45) Flags (0) TLV Offset (16)
0/0 2 1 0 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

TxTimeStampf

Reserved for 1DM Receiving Equipment (0)

(for TxTimeStampf )

20/160 End TLV (0)

7 6 5 4 3 2 1 0

The following illustration shows a DMM frame header.

Figure 59 • OAM DMM Frame Header Format
0 DMM Frame Header Format 31
Octet/Bit
MEG Version (0) Opcode (1DM=47) Flags (0) TLV Offset (32)
0/0 2 1 0 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

TxTimeStampf

Reserved for DMM Receiving Equipment (0)

(for RxTimeStampf )

Reserved for DMR (0)

(for TxTimeStampb )

Reserved for DMR Receiving Equipment (0)

36/288 End TLV (0)

7 6 5 4 3 2 1 0

The following illustration shows a DMR frame header.

Figure 60 • OAM DMR Frame Header Format

Octet/Bit 0 DMR Frame Header Format 31

MEG Version Opcode (DMR=46) Flags TLV Offset
0/0 2 1 0 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

TxTimeStampf

RxTimeStampf

TxTimeStampb

Reserved for DMR Receiving Equipment (0)

(for RxTimeStampb )

36/288 End TLV (0)

7 6 5 4 3 2 1 0

As with PTP, there is no protocol validation for Y.1731 frames; only interpretation of the header to
determine what action to take. The first four bytes of the header are used to determine the action to be
taken.

3.6.16.12 Y.1731 OAM PDU

1DM, DMM, and DMR are the three supported G.8113.1 PDUs and DMM/DMR are the two supported
RFC6374 PDUs. The following illustrations show the PDU formats.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 81

Functional Descriptions

Figure 61 • RFC6374 DMM/DMR OAM PDU Format

ETH (1) 14/18/22B

MPLS labels (2) 4/8/12/16B
ACH 4B
OAM PDU Header 8B

DMM/DMR OAM PDUs

Time stamp 1 8B
Time stamp 1 8B
Time stamp 1 8B
Time stamp 1 8B
padding (variable size)
FCS 4B
(1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels

Figure 62 • G8113.1/draft-bhh DMM/DMR/1DM OAM PDU Format

DMM/DMR 1DM

ETH (1) 14/18/22B ETH (1) 14/18/22B

MPLS labels (2) 4/8/12/16B MPLS labels (2) 4/8/12/16B
ACH 4B ACH 4B
1DM OAM PDUs

OAM PDU Header 8B OAM PDU Header 8B

DMM/DMR OAM PDUs

Time stamp 1 8B Time stamp 1 8B

Time stamp 1 8B Time stamp 1 8B
Time stamp 1 8B End TLV indicator 1B
Time stamp 1 8B FCS 4B
End TLV indicator 1B (1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels
FCS 4B
(1) 0, 1, or 2 VLAN tags
(2) Up to 4 MPLS labels

As with PTP, there is no protocol validation for MPLS OAM; only interpretation of the header to determine
what action to take. The first four bytes of the header are used to determine the action to be taken.

3.6.16.13 PTP Comparator Action Control Registers

The following registers perform matching on the frame header and define what action is to be taken
based upon the match. There is one mask register for all flows, and the rest of the registers are unique
for each flow.

Table 31 • PTP Comparison

Parameter Width Description

PTP_Flow_Match 64 bit Matches bits in the PTP/Y.1731 frame starting at the
beginning of the protocol header
PTP_Flow_Mask 64 bit Mask bits for PTP_Flow_Match
PTP_Domain_Range_Lower 8 bit Lower range of the domain field to match
PTP_Domain_Range_Upper 8 bit Upper range of the domain field to match

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 82

Functional Descriptions

Table 31 • PTP Comparison (continued)

Parameter Width Description

PTP_Domain_Range_ 1 bit Enable for range checking
Enable
PTP_Domain_Offset 5 bit Pointer to the domain field, or whatever field is to be used
for range checking
PTP_Action_Command 3 bit Command
Value Mnemonic Action
0 NOP Do nothing
1 SUB New correction field =
Current correction field –
Captured local time
2 SUB_P2P New correction field =
Current correction field –
Local latency + path_delay
3 ADD New correction field =
Current correction field +
Captured local time
4 SUB_ADD New correction field =
Current correction field +
(Captured local time + Local
latency – Time storage field)
5 WRITE_1588 Write captured local time to
time storage field
6 WRITE_P2P Active_timestamp_ns =
captured local time and
path_delay written to time
storage field and correction
field (deprecated command)
7 WRITE_NS Write local time in
nanoseconds to the new field
8 WRITE_NS_ Write local time in
P2P nanoseconds + p2p_delay to
the new field and correction
field
PTP_Save_Local_Time 1 bit When set, saves the local time to the time stamp FIFO
(only valid for egress ports).
PTP_Correction_Field_Offset 5 bit Points to the location of the correction field. Location is
relative to the first byte of the PTP/OAM header.
PTP_Time_Storage_Field_ 6 bit Points to a location in a PTP frame where a time value can
Offset be stored or read.
PTP_Add_Delay_Asymmetry 1 bit When enabled, the value in the delay asymmetry register
_Enable is added to the correction field of the frame.
PTP_Subtract_Delay_ 1 bit When enabled, the value in the delay asymmetry register
Asymmetry_Enable is subtracted from the correction field of the frame.
PTP_Zero_Field_Offset 6 bit Points to a location in the PTP/OAM frame to be zeroed if
this function is enabled
PTP_Zero_Field_Byte_Count 4 bit The number of bytes to be zeroed. If this field is 0, then
this function is not enabled.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 83

Functional Descriptions

Table 31 • PTP Comparison (continued)

Parameter Width Description

PTP_Modified_Frame_Byte_ 3 bit Indicates the position relative to the start of the PTP frame
Offset in bytes where the Modified_Frame_Status bit resides.
This value is also used to calculate the offset from the
beginning of the Ethernet packet to this field for use by the
Rewriter.
PTP_Modified_Frame_Status 1 bit If set, tells the rewriter to update the value of this bit.
_Update Configuration registers inside the rewriter indicate if the bit
will be set to 0 or 1.
PTP_Rewrite_Bytes 4 bits Number of bytes in the PTP or OAM frame that must be
modified by the Rewriter for the time stamp
PTP_Rewrite_Offset 8 bits Points to where in the frame relative to the SFD that the
time stamp should be updated
PTP_New_CF_Loc 8 bits Location where the updated correction field value is
written relative to the PTP header start
PTP_Channel_Mask 1 bit per Enable for this match set for this channel
channel
per flow
PTP_Flow_Enable 1 bit When set, the fields associated with this flow are all valid

The following table shows controls that are common to all flows.

Table 32 • PTP Comparison: Common Controls

Parameter Width Description

PTP_IP_CHKSUM_Sel 1 bit 0 = Use IP checksum controls from comparator 1
1 = Use IP checksum controls from comparator 2
FSB_Adr_Sel 2 bits Selects the source of the address for use in the frame signature
builder

The following table shows the one addition, per-flow, register.

Table 33 • PTP Comparison: Additions for OAM-Optimized Engine

Parameter Width Description

PTP_NXT_Prot_Group_Mask 2 bits There are two bits for each flow. Each bit indicates if the
flow can be associated with next-protocol group A or B.
One or both bits may be set. If a bit is 1 for a particular
next-protocol group, then a flow match is valid if the prior
comparator stages also produced matches with the same
next-protocol group.

3.6.16.14 Future Protocol Compatibility

Except for MPLS, the comparators are not hardwired to their intended protocols. They can be used as
generic field and range comparators because all of the offsets or pointers to the beginning of the fields
are configurable. The IP comparator is the most generic and would probably be the first choice for
validating a new protocol.
Additionally, if there are not enough comparison resources in a single comparator block to handle a new
protocol, two comparators back-to-back can used by splitting up the comparison work. One portion can
be validated in one comparator and then handed off to another. The only restriction is that there must be

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 84

Functional Descriptions

at least one 64-bit word of separation between the start of the protocol and where the second starts to
operate.

3.6.16.15 Reconfiguration
There are three ways to perform reconfiguration:
1. Disable an entire encapsulation engine.
Once an engine has been disabled, any of the configuration registers associated with it may be
modified in any order. If other encapsulation engines are still active, they will still operate normally.
2. Disable a flow in an active engine.
Each stage in the engine has an enable bit for each flow. If a flow is disabled in a stage, its registers
may be modified. Once reconfiguration for a flow in a stage is complete, it can be enabled.
3. Disable a comparator.
Each comparator within the active encapsulation engine can be disabled. If an Ethernet header
according to the configuration Type I or Type II with SNAP/LLC is not found then subsequent flows
will not be matched. The ETH1 comparator can also be disabled so that all frames flowing through
the IEEE 1588 block are time stamped.
The disabling of engines and flows is always done in a clean manner so that partial matches do not
occur. Flows and engines are always enabled or disabled during inter-packet gaps or at the end of a
packet. This guarantees that when a new packet is received that it will be analyzed cleanly.
If strict flow matching is enabled and a flow is disabled in one of the stages, then the entire flow is
automatically disabled.
If any register in a stage that applies to all flows needs to be modified, then the entire encapsulation
engine must be disabled.

3.6.16.16 Frame Signature Builder

Along with time stamp and CRC updates, the analyzer outputs a frame signature that can be stored in
the time stamp FIFO to help match frames with other info in the FIFO. This information is used by the
CPU so that it can match time stamps in the time stamp FIFO with actual frames. The frame signature is
up to 16 bytes long and contains information from the Ethernet header (SA or DA), IP header (SA or DA),
and from the PTP or OAM frame. The frame signature is only used in the egress direction.
The PTP block contains a set of mapping registers to configure which bytes are mapped into the frame
signature. The following tables show the mapping for each byte.

Table 34 • Frame Signature Byte Mapping

Select Source Byte

0-23 PTP header byte number = (31-select)
24 PTP header byte number 6
25 PTP header byte number 4
26 PTP header byte number 0
27 Reserved
28-35 Selected address byte (select-28)

Table 35 • Frame Signature Address Source

Parameter Width Description

FSB_Map_Reg_0-15 6 bits For each byte of the frame signature, use Table 34, page 85 to
select which available byte is used. Frame signature byte 0 is the
LSB. If not all 16 bytes are needed, the frame signature should
be packed towards the LSB and the upper unused byte
configuration values do not need to be programmed.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 85

Functional Descriptions

Table 35 • Frame Signature Address Source (continued)

Parameter Width Description

FSB_Adr_Sel 2 bits Selects the source of the address for use in the frame signature
builder according to the following list
Select Value Address Source
0 Ethernet block 1
1 Ethernet block 2
2 IP block 1
3 IP block 2

Configuration registers in each comparator block supply an address to select if it is the source address or
the destination address.
A frame signature can be extracted from frames matching in all the three engines. The frame signature
address selection is limited to Ethernet Block1 because only a limited number of encapsulations are
supported in the third engine, Engine C.
Engine C has two parts: part A and part B. Part A supports ETH1, ETH2, MPLS protocols while part B
supports only ETH1 protocol. Selection of Ethernet block 1 or 2 is dependent on whether part A flow
matches or part B flow matches.
If a frame matches part A flow configuration, then the frame signature as configured in
ETH1_NXT_PROTOCOL_A and ETH2_NXT_PROTOCOL_A using FSB_ADR_SEL will be considered
in computing the frame signature.
If a frame matches part B flow configuration, then the frame signature as configured in
ETH1_NXT_PROTOCOL_A and FSB_ADR_SEL will be considered in computing the frame signature. In
this configuration if FSB_ADR_SEL is set to 1, to select ETH2 then all zeros are padded as frame
signature because ETH2 is not supported by part B.

3.6.16.17 Configuration Sharing

The analyzer configuration services both channels. Each flow within each comparator has a channel-
mask register that indicates which channels the flow is valid for. Each flow can be valid for channel A,
channel B, or both channels.
A total of eight flows can be allocated the two channels if the analyzer configuration cannot be shared.
They can each have four distinct flows (or three for the one, and five for the other, etc.).

3.6.16.18 OAM-Optimized Engine

The OAM optimized engine, Engine C, supports a fewer set of encapsulations such as ETH1, ETH2,
MPLS, and ACH. Engine C is was enhanced with an ACH comparator to support the MPLS-TP OAM
protocol. The MPLS-TP OAM protocol for Engine C is configured in the following registers.
• EGR2_ACH_PROT_MATCH_UPPER/LOWER_A
• EGR2_ACH_PROT_MASK_UPPER/LOWER_A
• EGR2_ACH_PROT_OFFSET_A
The ACH comparator will start the comparison operation right after the MPLS comparator.
In addition to the descriptions of the Ethernet and MPLS blocks in the OAM optimized engine, there is the
notion of protocol-A/protocol-B. When a match occurs in the Ethernet 1 block the status of the protocol
set that produced the match is indicated. There are two bits, one for protocol A and another for protocol
B. If both sets produce a match, then both bits are set.
These bits are then carried to the next comparison block and only allow flow matches for the protocol
sets that produced matches in the prior block. This block also produces a set of protocol match bits that
are also carried forward.
This feature is provided to prevent a match with protocol set A in the first block and protocol set B in the
second block.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 86

Functional Descriptions

3.6.17 Time Stamp Processor

The primary function of the time stamp processor block is to generate a new Timestamp_field or new
Correction_field (Transparent clocks) for the rewriter block. The time stamp block generates an output
that is either a snapshot of the corrected Local Time (struct time stamp) or a signed (two's complement)
64 bit Correction_field.
In the ingress direction, the time stamp block calculates a new time stamp for the rewriter that indicates
the earlier time when the corresponding PTP event frame entered the chip (crossed the reference plane
referred to in the IEEE 1588 standard).
In the egress direction, the time stamp block calculates a new time stamp for the rewriter in time for the
PCS block to transmit the new time stamp field in the frame. In this case, the time stamp field indicates
when the corresponding PTP event frame will exit the chip.
Transparent clocks correct PTP event messages for the time resided in the transparent clock. Peer-to-
Peer transparent clocks additionally correct for the propagation time on the inbound link (Path_delay).
The Path_delay [ns] input to the time stamp block is software programmed based upon IEEE 1588 path
delay measurements.
In general, the IEEE 1588 standard allows for a transparent clock to update the Correction_Field for both
PTP event messages as well as the associated follow up message (for two-step operation). However, the
TSP only updates PTP event messages. Also, the 1588 standard allows that end-to-end transparent
clocks correct and forward all PTP-timing messages while Peer-to-Peer transparent clocks only correct
and forward Sync and Follow_Up messages. Again, the TSP only updates PTP event messages (not
Follow_Up messages).
Internally, the time stamp block generates an Active_timestamp from the captured/time stamped Local
time (Raw_timestamp). The Active_time stamp is the Raw_timestamp corrected for the both fixed
(programmed) local chip, and variable chip latencies relative to where the Start_of_Frame_Indicator
captures the local time. The time stamp block operates on the Active_timestamp based on the Command
code.
The Active_timestamp is calculated differently in the Ingress and Egress directions and the equations are
given below.
In the ingress direction:
Active_timestamp = Raw_timestamp - Local_latency - Variable_latency
In the egress direction:
Active_timestamp = Raw_timestamp + Local_latency + Variable_latency
In addition, the following values are also calculated for use by the commands:
Active_timestamp_ns = Active_timestamp converted to nanoseconds
Active_timestamp_p2p_ns = active_timestamp_ns + path delay
The Local_latency is a programmed fixed value while the Variable_latency is predicted from the PCS
logic based upon the current state of the ingress or egress data pipeline.
For the option of Peer-to-Peer transparent clocks, the ingress Active_timestamp calculation includes an
additional Path_delay component. The path delay is always added for a transparent clock per the
standard. The path delay is always added to the correction field.
The signed 32-bit two's complement Delay Asymmetry register (bits 31–0) can be programmed by the
user. Bit 31 is the sign bit. Bits 15–0 are scaled nanoseconds just like for the CorrectionField format. The
DelayAsymmetry register (whether it be positive or negative) will be sign extended and added to the
64-bit correction field (signed add) if the Add_Delay_Asymmetry bit is set. The DelayAsymmetry register
(whether it be positive or negative) will be sign extended and subtracted from the 64-bit correction field
(signed Subtract) if the Subtract_Delay_Asymmetry bit is set.
The time stamp block keeps a shadow copy of the programmed latency values (Local_latency,
Path_delay, and Delay_Asymmetry) to protect against CPU updates.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 87

Functional Descriptions

3.6.18 Time Stamp FIFO

The time stamp FIFO stores time stamps along with frame signature information. This information can be
read out by a CPU or pushed out on a dedicated Serial Time Stamp Output Interface and used in 2-step
processing mode to create follow-up messages. The time stamp FIFO is only present in the egress data
path.
The time stamp FIFO takes a frame signature from the analyzer and the updated correction field, and the
full data set for that time stamp is saved to the FIFO. This creates an interrupt to the CPU. If the FIFO
ever overflows this is indicated with an interrupt.
The stored frame signature can be of varying sizes controlled by the
EGR_TSFIFO_CSR.EGR_TS_SIGNAT_BYTES register. Only the indicated number of signature bytes is
saved with each time stamp. The saved values are packed so that reducing the number of signature
bytes allows more time stamps to be saved.
The packing of the time stamp data is done by logic before the write occurs to the FIFO. When no
compression is used, each time stamp may contain 208 bits of information (consisting of 128 bits of
frame signature and 80 bits of time stamp data). Therefore, a full-sized time stamp is 26 bytes long.
Compressing the frame signature can reduce this to as little as 10 bytes (or 4 bytes if
EGR_TSFIFO_CSR.EGR_TS_4BYTES = 1) if no signature information is saved
(EGR_TSFIFO_CSR.EGR_TS_SIGNAT_BYTES = 0). The value to store is built up in an internal
register. When the register contains 26 valid bytes, that data is written to the time stamp FIFO. Data in
the FIFO is packed end-to-end. It is up to the reader of the data to unpack the data.
The time stamps in the FIFO are visible and accessible for the CPU as a set of 32-bit registers. Multiple
register reads are required to read a full time stamp if all bits are used. Bit 31 in register EGR_TSFIFO_0
contains the current FIFO empty flag, which can be used by the CPU to determine if the current time
stamps are available for reading. If the bit is set, the FIFO is empty and no time stamps are available.
The value that was read can be discarded because it does not contain any valid time stamp data. If the
bit is 0 (deasserted), the value contains 16 valid data bits of a time stamp. The remaining bits should be
read from the other registers in the other locations and properly unpacked to recreate the time stamp.
Care should be taken to read the time stamps one at a time, as each read of the last (7th) address will
trigger a pop of the FIFO.
Time stamps are packed into seven registers named EGR_TSFIFO_0 to EGR_TSFIFO_6. If the time
stamp FIFO registers are read to the point that the FIFO goes empty and there are remaining valid bytes
in the internal packing register, then the packing register is written to the FIFO. In this case, the registers
may not be fully packed with time stamps. Flag bits are used to indicate where the valid data ends within
the set of seven registers. The flag bits are in register EGR_TSFIFO_0.EGR_TS_FLAGS (together with
the empty flag) and are encoded as follows:
000 = Only a partial time stamp is valid in the seven register set
001 = One time stamp begins in the current seven register set
010 = Two time stamps begin in the current seven register set.
011 = Three time stamps begin in the current seven register set (4-byte mode)
100 = Four time stamps begin in the current seven register set (4-byte mode)
101 = Five time stamps begin in the current seven register set (4-byte mode)
110 = Six time stamps begin in the current seven register set (4-byte mode)
111 = The current seven register set is fully packed with valid time stamp data
The FIFO empty bit is visible in the EGR_TSFIFO_0.EGR_TS_EMPTY register so the CPU can poll this
bit to know when time stamps are available. There is also a maskable interrupt which will assert
whenever the time stamp FIFO level reaches the threshold given in
EGR_TSFIFO_CSR.EGR_TS_THRESH register. The FIFO level is also visible in the
EGR_TSFIFO_CSR.EGR_TS_LEVEL register. If the time stamp FIFO overflows, writes to the FIFO are
inhibited. The data in the FIFO is still available for reading but new time stamps are dropped.
Note: Time stamp FIFO exists only in the Egress direction. There is no time stamp FIFO in the Ingress direction

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 88

Functional Descriptions

3.6.19 Serial Time Stamp Output Interface

For each 1588 Processor 0 and 1, time stamp information stored in the Egress direction can be read
through either the register interface or through the Serial Time Stamp interface. These two ways to read
registers are mutually exclusive. While enabling/disabling the serial interface is done on a Processor
level, only one serial interface exists. This means the serial interface can be enabled for Processor 0,
while the time stamp FIFO can be read through registers for Processor 1. If the serial interface is enabled
for both Processor 0 and 1, then the serial interface will arbitrate between two Egress time stamp FIFOs
in Processor 0 and 1 and push the data out.
The time stamp FIFO serial interface block writes, or pushes, time stamp/frame signature pairs that have
been enqueued and packed into time stamp FIFOs to the external chip interface consisting of three
output pins: 1588_SPI_DO, 1588_SPI_CLK, and 1588_SPI_CS. There is one interface for all channels.
When the serial interface (SPI) is enabled, the time stamp/frame signature pairs are dequeued from time
stamp FIFO(s) and unpacked. Unpacked time stamp/frame signature pairs are then serialized and sent
one at a time to the external interface. Unpacking shifts the time stamp/frame signature into alignment
considering the configured size of the time stamps and frame signatures (a single SI write may require
multiple reads from a time stamp FIFO). The time stamp FIFO serial interface is an alternative to the
MDIO register interface described in the time stamp FIFO section. When the serial time stamp interface
is enabled in register TS_FIFO_SI_CFG.TS_FIFO_SI_ENA, data read from the time stamp FIFO
registers described in Time Stamp FIFO, page 88 are invalid.
Time stamp/Frame signature pairs from two egress time stamp FIFOs are serialized one at a time and
transmitted to the interface pins. The TS_FIFO_SI arbitrates in a round-robin fashion between the ports
that have non-empty time stamp FIFOs. The port associated with each transmitted time stamp/frame
signature pair is indicated in a serial address that precedes the data phase of the serial transmission.
Because the time stamp FIFOs are instantiated in the per port clock domains, a small single entry
asynchronous SI FIFO (per port) ensures that the time stamp/frame signature pairs are synchronized,
staged, and ready for serial transmission. When an SI FIFO is empty, the SI FIFO control fetches and/or
unpacks a single time stamp/frame signature performing any time stamp FIFO dequeues necessary. The
SI FIFO goes empty following the completion of the last data bit of the serial transmission. Enabled ports
(TS_FIFO_SI_CFG.TS_FIFO_SI_ENA) participate in the round-robin selection.
Register TS_FIFO_SI_TX_CNT accumulates the number of time stamp/frame signature pairs
transmitted from the serial time stamp interface for each channel. Register EGR_TS_FIFO_DROP_CNT
accumulates the number of time stamp/frame signature pairs that have been dropped per channel due to
a time stamp FIFO overflow.
The SPI compatible interface asserts a chip select (SPI_CS) for each write followed by a write command
data bit equal to 1, followed by a don't care bit (0), followed by an address phase, followed by a data
phase, followed by a deselect where SPI_CS is negated. Each write command corresponds to a single
time stamp/frame signature pair. The length of the data phase depends upon the sum of the configured
lengths of the time stamp and signature, respectively. The address phase is fixed at five bits. The
SPI_CLK is toggled to transfer each SPI_DO bit (as well as the command and address bits). The Time
Stamp and Frame Identifier Data from the following illustration are sent MSB first down to LSB (bit 0) in
the same format as stored in the seven registers of TS FIFO CSRs. For more information, see Time
Stamp FIFO, page 88 and Figure 63, page 90.
The frequency of the generated output 1588_SPI_CLK can be flexibly programmed from 10 MHz up to
62.5 MHz using TS_FIFO_SI_CFG to set the number of CSR clocks that the 1588_SPI_CLK is both high
and low. For example, to generate a 1588_SPI_CLK that is a divide-by-6 of the CSR clock, the CSR
register would be set such that both SI_CLK_LO_CYCS and SI_CLK_HI_CYCS equal 3. Also, the
number of CSR clocks after SPI_CS asserts before the first 1588_SPI_CLK is programmable
(SI_EN_ON_CYCS), as is the number of clocks before SI_EN negates after the last 1588_SPI_CLK
(SI_EN_OFF_CYCS). The number of clocks during which SI_EN is negated between writes is also
programmable (SI_EN_DES_CYCS). The 1588_SPI_CLK may also be configured to be inverted
(SI_CLK_POL).
Without considering de-selection between writes, if the PTP 16-byte SequenceID (frame signature) is
used as frame identifier, each 10 byte time stamp write take 2 + 55 + 10 × 8 + 16 × 8 = 265 clocks (at

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 89

Functional Descriptions

40 MHz) ~6625 ns. This corresponds to a time stamp bandwidth of > 0.15 M time stamp/second/port.
The following illustration shows the serial time stamp/frame signature output.
Figure 63 • Serial Time Stamp/Frame Signature Output
SPI_CS

SPI_Clk

SPI_ DO 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 12 9 8 7 6 5 4 3 2 1 00

Port Fram e Identifier Data Tim e stam p

(0 to 16 bytes) (4 or 10 bytes)

3.6.20 Rewriter
When the rewriter block gets a valid indication it overwrites the input data starting at the offset specified
in Rewrite_offset and replaces N bytes of the input data with updated N bytes. Frames are modified by
the rewriter as indicated by the analyzer-only PTP/OAM frames are modified by the rewriter.
The output of the rewriter block is the frame data stream that includes both unmodified frames and
modified PTP frames. The block also outputs a count of the number of modified PTP frames in
INGR_RW_MODFRM_CNT/EGR_RW_MODFRM_CNT, depending upon the direction. This counter
accumulates the number of PTP frames to which a write was performed and includes errored frames.

3.6.20.1 Rewriter Ethernet FCS Calculation

The rewriter block has to recalculate the Ethernet CRC for the PTP message to modify the contents by
writing a new time stamp or clear bytes. Two versions of the Ethernet CRC are calculated in accordance
with IEEE 802.3 Clause 3.2.9: one on the unmodified input data stream and one on the modified output
data stream. The input frame FCS is checked against the input calculated FCS and if the values match,
the frame is good. If they do not, then the frame is considered a bad or errored frame. The new
calculated output FCS is used to update the FCS value in the output data frame. If the frame was good,
then the FCS is used directly. If the frame was bad, the calculated output FCS is inverted before writing
to the frame. Each version of the FCS is calculated in parallel by a separate FCS engine.
A count of the number of PTP/OAM frames that are in error is kept in the INGR_RW_FCS_ERR_CNT or
EGR_RW_FCS_ERR_CNT register, depending upon the direction.

3.6.20.2 Rewriter UDP Checksum Calculation

For IPv6/UDP, the rewriter also calculates the value to write into the dummy blocks to correct the UDP
checksum. The checksum correction is calculated by taking the original frame's checksum, the value in
the dummy bytes, and the new data to be written; and using them to modify the existing value in the
dummy byte location. The new dummy byte value is then written to the frame to ensure a valid
checksum. The location of the dummy bytes is given by the analyzer. The UDP checksum correction is
only performed when enabled using the following register bits:
• INGR_IP1_UDP_CHKSUM_UPDATE_ENA
• INGR_IP2_UDP_CHKSUM_UPDATE_ENA
• EGR_IP1_UDP_CHKSUM_UPDATE_ENA
• EGR_IP2_UDP_CHKSUM_UPDATE_ENA
Based upon the analyzer command and the rewriter configuration, the rewriter writes the time stamp in
one of the following ways:
• Using PTP_REWRITE_BYTES to choose four bytes write to PTP_REWRITE_OFFSET. This
method is similar to other PTP frame modifications and the time stamp is typically written to the
reserved field in the PTP header.
• Using PTP_REWRITE_BYTES and RW_REDUCE_PREAMBLE to select the mode of operation
when writing Rx time stamps into the frame.
In these modes, it cannot do both a time stamp write/append and a PTP operation in the same
frame. If PTP_REWRITE_BYTES = 0xE and RW_REDUCE_PREAMBLE = 1, it does it by
overwriting the existing FCS with the time stamp in the lowest four bytes of the calculated time
stamp and generating a new FCS and appending it.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 90

Functional Descriptions

Because the rewriter cannot modify the IFG or change the size of the frame, if the original FCS is
overwritten with time stamp data a new FCS needs to be appended and the frame shortened by reducing
the preamble. The preamble length includes the /S/ character and all preamble characters up to but not
including the SFD. In this mode, it is assumed that all incoming preambles are of sufficient (5 to 7-byte)
length to delete four bytes and the preamble of every frame (not only PTP frames) will be reduced by
four bytes by deleting four bytes of the preamble. Then, the new FCS is written at the end of the matched
frame. For unmatched frames, or if the PTP_REWRITE_BYTES is anything but 0xE, the IFG is
increased by adding four IDLE (/I/) characters after the /T/ which ends the packet.
To time stamp a frame in one of the modes, the actual length of the preamble is then checked and if the
preamble is too short to allow a deletion of four bytes (if the preamble is not five bytes or more) then no
operations are performed on the preamble, the FCS is not overwritten, and no time stamp is appended.
For all such frames, a counter is maintained and every time an unsuccessful operation is encountered,
the counter is incremented. This counter is read through register
INGR_RW_PREAMBLE_ERR_CNT/EGR_RW_PREAMBLE_ERR_CNT. The following illustration shows
the deleted preamble bytes.
Figure 64 • Preamble Reduction in Rewriter

SFD SFD
Pre3
0xD5 0xD5

Pre6 Pre2 Pre6

Pre5 Pre1 Pre5

Pre4 /S/ /S/

If PTP_REWRITE_BYTES = 0xF and RW_REDUCE_PREAMBLE = 0, the rewriter replaces the FCS of

the frame with the four lowest bytes of the calculated time stamp and does not write the FCS to the
frame. In this mode, all the frames have corrupted FCSs and the MAC needs to be configured to handle
this case. In the case of a CRC error in the original frame, the rewriter writes all ones (0xFFFFFFFF) to
the FCS instead of the time stamp. This indicates an invalid CRC to the MAC because this is reserved to
indicate an invalid time stamp. In the rare case that the actual time stamp has the value 0xFFFFFFFF
and the CRC is valid, the rewriter increments the time stamp to 0x0 and writes that value instead. This
causes an error of 1 ns, but is required to reserve the time stamp value of 0xFFFFFFFF for frames with
an invalid CRC.
A flag bit may also be set in the PTP message header to indicate that the TSU has modified the frame
(when set) or to clear the bit (on egress). The analyzer sends the byte offset of the flag byte to the
rewriter in PTP_MOD_FRAME_BYTE_OFFSET and indicates whether the bit should be modified or not
using PTP_MOD_FRAME_STATUS_UPDATE. The bit offset within the byte is programmed in the
configuration register RW_FLAG_BIT. When the PTP frame is being modified, the selected bit is set to
the value in the RW_FLAG_VAL. This only occurs when the frame is being modified by the rewriter;
when the PTP frame matches and the command is not NOP.

3.6.21 Local Time Counter

The local time counter keeps the local time for the device and the time is monitored and synchronized to
an external reference by the CPU. The source clock for the counter is selected externally to be a
250 MHz, 200 MHz, 125 MHz, or some other frequency. The clock may be a line clock or the dedicated
CLK1588P/N pins. The clock source is selected in register LTC_CTRL.LTC_CLK_SEL.
To support other frequencies, a flexible counter system is used that can convert almost any frequency in
the 125–250 MHz range into a usable source clock. Supported frequencies of local time counter are 125
MHz, 156.25 MHz, 200 MHz, and 250 MHz. The frequency is programmed in terms of the clock period.
Set the LTC_SEQUENCE.LTC_SEQUENCE_A register to the clock period to the nearest whole number
of nanoseconds to be added to the local time counter on each clock cycle. Set LTC_SEQ.LTC_SEQ_E to
the amount of error between the actual clock period and the LTC_SEQUENCE.LTC_SEQUENCE_A
setting in femtoseconds. Register LTC_SEQ.LTC_SEQ_ADD_SUB indicates the direction of the error.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 91

Functional Descriptions

An internal counter keeps track of the accumulated error. When the accumulated error exceeds 1
nanosecond, an extra nanosecond is either added or subtracted from the local time counter. Use the
following as an example to program a 5.9 ns period:
LTC_SEQUENCE.LTC_SEQUENCE_A = 6 (6 ns)
LTC_SEQ.LTC_SEQ_E = 100000 (0.1 ns)
LTC_SEQ.LTC_SEQ_ADD_SUB = 0 (subtract an extra nanosecond, i.e add 5 ns)
To support automatic PPM adjustments, an internal counter runs on the same clock as the local time
counter, and increments using the same sequence to count nanoseconds. The maximum (rollover) value
of the internal counter in nanoseconds is given in register
LTC_AUTO_ADJUST.LTC_AUTO_ADJUST_NS. At rollover, the next increment of the local time counter
is increased by one additional or one less nanosecond as determined by the
LTC_AUTO_ADJUST.LTC_AUTO_ADD_SUB_1NS register. When
LTC_AUTO_ADJUST.LTC_AUTO_ADD_SUB_1NS is set to 0x1, an additional nanosecond is added to
the local time counter. When it is set to 0x2, one less nanosecond is added to the local timer counter. No
PPM adjustments are made when the register is set to 0x0 or 0x3.
PPM adjustments to the local time counter can be made on an as-needed basis by writing to the one-
shot LTC_CTRL.LTC_ADD_SUB_1NS_REQ register. One nanosecond is added or subtracted from the
local time counter each time LTC_CTRL.LTC_ADD_SUB_1NS_REQ is asserted. The
LTC_CTRL.LTC_ADD_SUB_1NS register setting controls whether the local time counter adjustment is
an addition or a subtraction.
The current time is loaded into the local time counter with the following procedure.
1. Configure the 1588_LOAD_SAVE pin.
2. Write the time to be loaded into the local time counter in registers LTC_LOAD_SEC_H,
LTC_LOAD_SEC_L and LTC_LOAD_NS.
3. Program LTC_CTRL.LTC_LOAD_ENA to a 1.
4. Drive the 1588_LOAD_SAVE pin from low to high.
The time in registers LTC_LOAD_SEC_H, LTC_LOAD_SEC_L and LTC_LOAD_NS is loaded into the
local time counter when the rising edge of the 1588 LOAD_SAVE strobe is detected. The LOAD_SAVE
strobe is synchronized to the local time counter clock domain.
When the 1588_DIFF_INPUT_CLK_P/N pins are the clock source for the local time counter, and the
LOAD_SAVE strobe is synchronous to 1588_DIFF_INPUT_CLK_P/N, the LTC_LOAD* registers are
loaded into the local time counter, as shown in the following illustration.
Figure 65 • Local Time Counter Load/Save Timing
LOAD_SAVE

CLK1588P

System generates
LOAD_SAVE here
Time loaded into Local
Device captures Time Counter here
LOAD_SAVE here

When the LOAD_SAVE strobe is not synchronous to the 1588_DIFF_INPUT_CLK_P/N pins or an

internal clock drives the local time counter, there is some uncertainty as to when the local time counter is
loaded, when higher accuracy circuit is turned off. This reduces the accuracy of the time stamping
function by the period of the local time counter clock. When higher accuracy circuit is ON, any difference
between the 1588_DIFF_INPUT_CLK_P and the rising edge of 1588_LOAD_SAVE is compensated
within an error of 1 ns. This applies to both load and save operations.
Note: There is a local time counter in each channel. The counter is initialized in both channels if the
LTC_CTRL.LTC_LOAD_ENA register in each channel is asserted when the LOAD_SAVE strobe occurs.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 92

Functional Descriptions

When LTC_CTRL.LTC_SAVE_ENA register is asserted when the 1588 LOAD_SAVE input transitions
from low to high, the state of the local time counter is stored in the LTC_SAVED_SEC_H,
LTC_SAVED_SEC_L, and LTC_SAVED_NS registers.
The current local time can be stored in registers with the following procedure.
1. Configure the 1588_LOAD_SAVE pin.
2. Program LTC_CTRL.LTC_SAVE_ENA to a 1.
3. Set SER_TOD_INTF.LOAD_SAVE_AUTO_CLR to 1 if the operation is one-time save operation.
This will clear LTC_CTRL.LTC_SAVE_ENA after the operation.
4. Drive the 1588_LOAD_SAVE pin from low to high.
5. Read the value from LTC_SAVED_SEC_H, LTC_SAVED_SEC_L, and LTC_SAVED_NS registers.
As with loading the local time counter, there is one clock cycle of uncertainty as to when the time is saved
if the LOAD_SAVE strobe is not synchronous to the clock driving the counter.

3.6.22 Serial Time of Day

In addition to loading or saving as described in the preceding sections, it is possible to load or save LTC
time in a serial fashion. For serial load, 1588_LOAD_SAVE has to send Time of Day (ToD) information in
a specific format. For serial save, when the appropriate register bits is set, then PPS will drive out the
ToD information. The following illustration shows the format for serial load and save.
Figure 66 • Standard PPS and 1PPS with TOD Timing Relationship
1PPS Cycle (1 s)

Standard
PPS Signal

High Voltage

1PPS with
ToD Signal Low Voltage

A B C D
1.0 µs 20 µs 160 µs 999819.0 µs

3.6.22.1 Pulse per Second Segment

In the preceding illustration, segment A is the pulse per second segment. The PPS signal is transmitted
with high voltage. The rising edge of the PPS signal is aligned with the rising edge of the standard PPS
signal. This segment lasts 1 µs. To obtain high accuracy, the response delay of the rising edge of the
PPS signal should be considered.

3.6.22.2 Waiting Segment

In the preceding illustration, segment B is the Waiting segment. Due to the speed of operation, this
segment is needed to make it easier for the receiver to obtain the following Time-of-Day information in
current PPS cycle. The signal is in low voltage during this segment, which lasts 20 µs.

3.6.22.3 Time-of-Day Segment

In the preceding illustration, segment C is the Time-of-Day segment. The ToD information being carried
in this segment indicates the time instant of the rising edge of the PPS signal transmitted in segment A of
the current PPS cycle. The time instant is measured using the original network clock. In this segment, the
ToD information is continuously transported and is represented in 16 octets. It consists of the following
fields:
• Second field: 6 octets. It represents the time instant of the rising edge of the PPS signal in second.
The value is defined as in IEEE 1588-2008.
• Date field: 6 octets. It represents the time instant of the rising edge of the PPS signal in year, month,
day, hour, minute, and second. Each part is represented by one octet (the format of this field is
0xYYMMDDHHMMSS). In particular, only the lowest 2 decimal digits of the year are represented.
The receiver can easily obtain the time instant of the rising edge of the PPS signal in this transparent
format without additional circuitry to translate the value of the second field. It also has the significant

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 93

Functional Descriptions

benefit of changing the value of this field when leap year or leap second occurs. (The Date field is
ignored at the serial ToD input and is not generated at the serial ToD output.)
• Reserved field: 4 octets. Reserved for future use.
The ToD information is represented in units of octet, with each octet being transmitted with the low-order
bit first. The following illustration shows an octet is transmitted between a start bit with high voltage and a
stop bit with low voltage. The other octets are transmitted in the same manner. As a result,
(1+8+1) × 1 µs = 10 µs are needed to transport one octet. This segment lasts 16 × 10 µs = 160 µs to
convey the ToD information.
Figure 67 • ToD Octet Waveform
Transmitting 1 ToD Octet (10 µs)

LSB MSB

0 0 1 0 1 0 1 1
High Voltage

Low Voltage

Start Bit Stop Bit

ToD Octet (1 Octet)

The entire Time-of-Day segment should be detected. If the second 6 octets representing the Date field
are not used by the upper layer, the Date field should still be detected and its value can be ignored.

3.6.22.4 Idle Segment

Segment D is the Idle segment in Figure 66, page 93. It follows segment C with high voltage until the end
of the PPS cycle. The duration of the Idle segment is given by the following calculation.
1 s – 0.5 µs – 20 µs – 160 µs = 999819.5 µs.
Use the following steps to enable Serial load.
1. Set SER_TOD_INTF.SER_TOD_INPUT_EN to 1
2. Set LTC_CTRL.LOAD_EN to 1.
3. Start the transmission of 1588_LOAD_SAVE conforming to the format.
4. To check the data transmission, enable serial save or save LTC time to check the registers.
5. To enable serial save, set SER_TOD_INTF.SER_TOD_OUTPUT_EN to 1.
The following table lists the different options to load or save LTC time.

Table 36 • LTC Time Load/Save Options

LTC_CTRL.LOAD SER_TOD_INTF.SER_TOD_INPUT LTC_CTR.SAVE

_EN _EN _EN Expected Operation
0 0 1 Parallel Save
0 1 1 Save
0 0 0 No operation
0 1 0 No operation
1 0 0 Parallel Load
1 1 0 Serial Load

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 94

Functional Descriptions

Table 36 • LTC Time Load/Save Options (continued)

LTC_CTRL.LOAD SER_TOD_INTF.SER_TOD_INPUT LTC_CTR.SAVE

_EN _EN _EN Expected Operation
1 0 1 Parallel Load and Save
1 1 1 Serial Load and Save

When SER_TOD_INTF.SERIAL_ToD_OUTPUT_EN is set, the PPS output is driven with a serial ToD
output based on the LTC timer value.

3.6.23 Programmable Offset for LTC Load Register

When a new LTC value is loaded into the system, a fixed offset may need to be added to the loaded
value. Program SER_TOD_INTF.LOAD_PULSE_DLY, and this value will be added to LTC counter
whenever a new load occurs either through software, load_save pin, or through serial ToD.

3.6.24 Adjustment of LTC Counter

LTC counter value can be adjusted by about a second without reloading a new LTC value. LTC value can
be programmed to tune the current value by adding or subtracting a specific value. The offset adjustment
can be positive or negative, very similar to 1 ns adjustment being positive or negative. An adjustment
every 232 ns can be performed using LTC_OFFSET_ADJ. Additionally, an adjustment every 220 ns can
be performed using LTC_AUTO_M_x.
The purpose of this register is to add/subtract a programmable offset register of 30-bit width in ns, to the
register block in order to cover the entire nanosecond portion of the 80-bit LTC. This offset control is
independent of the LTC load control. The LTC timer is adjusted - added or subtracted as per the bit
LTC_OFFSET_ADJ.LTC_ADD_SUB_OFFSET, by the value LTC_OFFSET_ADJ.LTC_OFFSET_VAL,
when a load offset command is issued by the software (assertion of
LTC_OFFSET_ADJ.LTC_OFFSET_ADJ). The hardware sets the status bit
LTC_OFFSET_ADJ_STAT.LTC_OFFSET_DONE after completing the operation. However, in case the
hardware cannot complete the operation because of the LTC value itself getting updated synchronously
due to parallel or serial LTC load at the same time, it sets the bit
LTC_OFFSET_ADJ_STAT.LTC_OFFSET_LOAD_ERR. The software, on seeing either of these status
bits set (LTC_OFFSET_ADJ_STAT.LTC_OFFSET_DONE or
LTC_OFFSET_ADJ_STAT.LTC_OFFSET_LOAD_ERR), de-asserts the control bit
(LTC_OFFSET_ADJ.LTC_OFFSET_ADJ) and might potentially retry the operation.
The maximum value in nanoseconds for the offset LTC_OFFSET_ADJ.LTC_OFFSET_VAL can be up to
109 - 1. Thus, for addition operation, the maximum carry to the seconds counter is 2 because of the clock
period addition to this maximum value present in the offset and LTC nanoseconds counter. For
subtraction operation, if the resultant subtraction is negative or underflows the LTC timer would be set to
wrong value. Therefore, such operations should never be allowed.
LTC_OFFSET_ADJ register (with LTC_OFFSET_VAL[29:0] and LTC_ADD_SUB_OFFSET) should be
updated before asserting LTC_OFFSET_ADJ bit in LTC_OFFSET_ADJ register.
LTC_OFFSET_ADJ_STAT.LTC_OFFSET_DONE and
LTC_OFFSET_ADJ_STAT.LTC_OFFSET_LOAD_ERR bits are set by the hardware and cleared by the
software by writing a zero.
Should a conflict occur between LTC update due to parallel/serial load and LTC update due to offset
adjustment, the load LTC takes precedence and the error condition is noted so that the polling software
does not hang on the offset status bit assertion.
LTC counter could be adjusted for any known drift that occurs on every second. This feature will add or
subtract one nanosecond every time LTC crosses over LTC_AUTO_ADJ_M_NS.
Example 1. If LTC_AUTO_ADJ_M_NS is 100 ns and LTC is started from reset with a value of 0 ns, then
LTC counter will be added/subtracted 1 ns every time counter rolls over 100 ns.
Example 2. If LTC_AUTO_ADJ_M_NS is 100 ns and LTC is started from reset with a value of 0 ns, then
LTC counter will be added/subtracted 1 ns every time counter rolls over. When counter is at 10 ns and

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 95

Functional Descriptions

LTC counter is loaded with 2 sec, 80 ns. Now 1 ns is adjusted when counter increments from 10 ns and
rolls over 100 ns. It does not add/subtract when LTC timer rolls over 100 ns.
Example 3. LTC_AUTO_ADJ_M_NS value is loaded with 400 ns and after some time
LTC_AUTO_ADJ_M_NS value is loaded with 500 ns. The AUTO_ADJ_M_COUNTER value when the
new value is loaded is 333 ns. Then the next adjustment happens after 177 ns after load because the
AUTO_ADJ_M_COUNTER continues to count until it reaches the newly loaded value 500 ns.
Example 4. LTC_AUTO_ADJ_M_NS value is loaded with 400 ns and after some time
LTC_AUTO_ADJ_M_NS value is loaded with 100 ns. The AUTO_ADJ_M_COUNTER value when the
new value is loaded is 333 ns. Then adjustment happens immediately because 333 > 100 and the
AUTO_ADJ_M_COUNTER is reset to zero after the adjustment
If LTC counter is loaded with a new value, set LTC_AUTO_ADJ_M_UPDATE bit to 1 and reload the
LTC_AUTO_ADJ_M_NS value.

3.6.25 Pulse per Second Output

The local time counter generates a one pulse-per-second (1PPS) output signal with a programmable
pulse width routed to GPIO pins. The pulse width of the 1PPS signal is determined by the
LTC_1PPS_WIDTH_ADJ register.
When the LTC counter exceeds the value in PPS_GEN_CNT (both are in nanoseconds), the PPS signal
is asserted. In default operation where PPS_GEN_CNT = 0 the LTC timer generates a PPS signal every
time LTC crosses the 1 sec boundary. By writing a large value (such as 109-60 ns), the 1PPS pulse
reaches its destination 60 ns away simultaneously with the LTC second wrap, thus providing time-of-day
synchronism between two systems.
The 1PPS output has an alternate mode of operation that increases the frequency of the pulses. This
mode may be used for applications such as locking an external DPLL to the IEEE 1588 frequency. In the
alternate mode, the 1PPS signal is driven directly from a single bit of the nanosecond field counter of the
local time counter. The pulse width cannot be controlled in this alternate operation mode. The alternate
mode is enabled with register LTC_CTRL.LTC_ALT_MODE_PPS_BIT.
The output frequencies that result are 1 divided by powers of 2 nanoseconds (bit 4 = 1/32 ns, bit
5 = 1/64 ns, bit 6 = 1/128 ns, …). The output pulses may jitter by the amount of the programmed
nanoseconds of the adder to the local nanoseconds counter, and any automatic or one-shot
adjustments.
The following table shows the possible output pulse frequencies (including the range of 4 kHz to 10 MHz)
usable for external applications.

Table 37 • Output Pulse Frequencies

Nanosecond Counter Bit Output Pulse Frequency

4 31.25 MHz
5 15.625 MHz
6 7.8125 MHz
7 3.90625 MHz
8 1.953125 MHz
9 976.5625 kHz
10 488.28125 kHz
11 244.140625 kHz
12 122.0703125 kHz
13 61.03515625 kHz
14 30.51757813 kHz
15 15.25878906 kHz

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 96

Functional Descriptions

Table 37 • Output Pulse Frequencies (continued)

Nanosecond Counter Bit Output Pulse Frequency

16 7.629394531 kHz
17 3.814697266 kHz

In addition to the preceding frequencies, a specific frequency can be chosen by enabling the synthesizer
on the PPS pin using the following steps.
1. Set LTC_FREQ_SYNTH.LTC_FREQ_SYNTH_EN to 1.
2. A toggle signal with the frequency specified will be pushed out onto PPS. The number of
nanoseconds the signal stays high can be specified by
LTC_FREQ_SYNTH.FREQ_HI_DUTY_CYC_NS. The number of nanoseconds the signal stays low
can be specified by LTC_FREQ_SYNTH.FREQ_LO_DUTY_CYC_NS.
3. The above nanoseconds should be exactly divisible by clock frequency, otherwise the signal may
have a jitter as high as the high duration/clock period or low duration/clock period.
4. To disable the this feature and revert back to PPS functionality, reset
LTC_FREQ_SYNTH.LTC_FREQ_SYNTH_EN to 0
For example, to output a 10 MHz signal, set the FREQ_HI_DUTY_CYC_NS to 50 ns and
FREQ_LO_DUTY_CYC_NS to 50 ns. On a 250 MHz LTC clock, this will make high time and low time of
signal shift between 48 ns and 52 ns.

3.6.26 Resolution
The IEEE 1588 processor achieves time stamp resolution in any mode of operation of 1 ns utilizing
special high-resolution circuitry. The accuracy of a device using high-resolution circuitry is improved
more than 100% over the first generation IEEE 1588 engine. High accuracy for these devices will be
supported regardless of the local time counter clock frequency supplied to the reference clock input. The
timestamp accuracy is a system-level property and may depend upon oscillator selection, port type, and
speed, system configuration, and calibration decisions. Supported frequencies of the local time counter
are 125 MHz, 156.25 MHz, 200 MHz, and 250 MHz.
There are a total of five high resolution blocks per port to improve resolution for the following events:
• One pulse-per-second (1PPS) output signal
• 1588_PPS_RI input signal
• Start-of-frame in the egress direction
• Start-of-frame in the ingress direction
• 1588_LOAD_SAVE input (strobe) signal direction
Each of these blocks can individually be enabled using ACC_CFG_STATUS. Contact Microsemi with any
questions regarding PTP accuracy calculations.

3.6.27 Loopbacks
Loopback options provide a means to measure the delay at different points to evaluate delays between
on chip wire delays and external delays down to a nanosecond.

3.6.27.1 Loopback from PPS to PPS_RI Pin

In this loopback, an external device will connect the PPS coming out of the IEEE 1588 to PPS_RI of the
IEEE 1588 device. The external device could even process the PPS signal and then loopback at a far-
end.

3.6.27.2 Loopback from LOAD_SAVE to PPS

When LOAD_SAVE_PPS_LPBK_EN is set, input load_save pin is connected to output PPS coming out
of the IEEE 1588. In this mode, input load_save pin is taken as close to the pin as possible without going
through any synchronization logic on the load_save pin.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 97

Functional Descriptions

3.6.27.3 Loopback of LOAD_SAVE Pin

When LOAD_SAVE_LPBK_EN is set, one clock cycle before the PPS is asserted, an output enable for
load_save pin is generated and PPS signal is pushed out on the load_save pin acting as an output pin.
After two cycles, output enable is brought down and load_save will behave as an input pin.

3.6.27.4 Loopback from PPS to LOAD_SAVE Pin

When PPS_LOAD_SAVE_LPBK_EN bit enabled, output pps signal is taken as close to the I/O as
possible and looped back onto load_save input pin. This is to account for any delays from PPS
generation block to the PPS output pin.

3.6.28 Accessing 1588 IP Registers

The following sections describe how the IEEE 1588 IP registers are accessed in the VSC8491-17
device.
Note: Contact Microsemi for an initialization script that supports the quick initialization of IEEE 1588 registers.

3.7 MACsec Block Operation

The VSC8491-17 device includes a high-performance streaming MACsec frame processing engine that
provides hardware acceleration for the complete MACsec frame transform along with frame classification
and statistics counter updates. The following list includes some of the major features of the MACsec
engine.
• Fully IEEE 802.1AE-2006, IEEE 802.1AEbn, and IEEE 802.1AEbw-2013 compliant.
• 64 secure associations (SA) per direction and 64 ingress consistency check rules.
• MACsec cipher suite GCM-AES-128 support.
• MACsec cipher suite GCM-AES-256 support.
• MACsec cipher suite GCM-AES-XPN-128/256 support.
• VLAN and Q-in-Q tag detection.
• MACsec tag detection and sub-classification (Untagged, Tagged, BadTag, KaY).
• Programmable “control” packet classification.
• 8-entry programmable non-match flow operation selection (drop, bypass), depending on MACsec
tag sub-classification and control packet classification.
• Programmable confidentiality offset (0 B – 127 B).
• SecTAG insertion and removal.
• Integrity Check Value (ICV) checking/removal and calculation/insertion.
• Packet number generation and checking.
• IEEE 802.1AE MACsec statistics counter support.
• Ingress path consistency checking (ICC)–64/16 entry programmable matching table with separate
drop/transfer decisions.
• MTU checking and oversize dropping dependent on VLAN User priority for VLAN frames and at
global level for non-VLAN frames.
• Advanced MACsec transformations–VLAN tag bypass and EoMPLS header bypass.
• Hardware offload for the nextPN and lowestPN update from the host(KaY).
• Support for AES-ECB, AES-CTR, and AES-GCM/GMAC transformation for FIPS certification of the
crypto core.
• Patent-pending architecture to enable use with IEEE 1588v2 with minimal and predictable delays.

3.7.1 MACsec Architecture

The MACsec block operates as a frame processing pipeline whose main function is the implementation
of the MACsec transform on Ethernet frames. The following illustration shows the MACsec data flow in
one direction.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 98

Functional Descriptions

Figure 68 • MACsec Architecture

MACSec IP Latency
Monitoring
reset_n and Control

clk

clk_en
Bypass

Crypto Engine Output

Input Packet
Packet tx_adr
Buffer M Buffer Output
Pkt Tx
Tx 128to64
U Adapter
X conv
AES- Stat. events
FIFO Pre- GCM Post- FIFO Hdr Consistency
Interf proc Core Proc Interf Byp Chekcing
with ass Engine
nAES proc
cores

Rx Input Output
Token Token
RX Pkt Input
Hdr Classification
Token M Post-
64to128 Adap Process
Bypass Engine Context U
conv ter X Engine
proc

rx_adr

Bypass
Statistics
Update
Engine

Host Control Bus

CSR System Interrupt

Handler Control Control

Transform
CSR Statistics
Records
Target RAM
RAM

Interrupt
Outputs

The following sections describe the blocks in the MACsec data flow.

3.7.1.1 PKT64to128
The Packet 64to128 block is the Rx interface of the MACsec IP with the other blocks. It converts the 64-
bit packet interface to the 128-bit packet interface with which the MACsec IP works. It also presents the
port information associated with the current frame. In the egress configuration, the PKT64to128 block
has a FIFO to temporarily handle back-pressure from the MACsec IP due to frame expansion. Based on
packet expansion within the MACsec IP, the PKT64to128 block provides flow control feedback to the flow
control buffer, which manages all data build up that occurs as a result of MACsec frame expansion.

3.7.1.2 Input Adapter

The Input Adapter manages the Input Packet interface to ensure interface protocol compliance.

3.7.1.3 Input Classification Engine

The Input Classification engine inspects the received frame data and performs the following functions:
• Control Frame Classification- A total of 29 programmable rules to classify the frame as a control
frame.
• VLAN Tag Detection- Programmable functionality to detect VLAN tags and extract information
before further classification.
• MACsec Tag Detection- Programmable functionality to detect MACsec tags and check if they are
valid (also detects special KaY packet tags).
• Default Frame Handling- Classifies packets into eight classes based on the outputs of the control
frame classification and MACsec tag detection modules, with control registers to define what to do
with a packet (drop or bypass) for each class.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 99

Functional Descriptions

• Flow Lookup Frame Classification and Frame Handling- Classifies frames based on frame
header field contents and outputs of the control frame classification, VLAN tag detection, and
MACsec tag detection modules. Flow control registers define what to do with a frame (drop, bypass,
or MACsec process) when matching entries. A programmable per-rule priority level resolves any
overlap between these rules.
• Flow Lookup/Default Classification Multiplexer- Gives priority to the decision from the flow
lookup frame classification. The default frame handling is used for a frame only if none of the flow
lookup entries match.

3.7.1.4 Latency Monitoring and Control

The Latency Monitoring and Control module monitors the latency that the first word of each frame incurs
going through the pipeline, and optionally stalls the output side until this latency matches a
programmable value. This ensures each frame incurs the same latency through the pipeline, irrespective
of any processing time differences.

3.7.1.5 MACsec Crypto Engine

The MACsec Crypto engine performs the standard MACsec encapsulation/decapsulation processing.
This engine is able to perform a MACsec transform on a frame using GCM-AES-128 according to the
IEEE 802.1AE-2006 MACsec specification and its amendment, IEEE 802.1AEbn-2011, which adds the
GCM-AES-256 cipher suite. The crypto engine also transforms a frame using GCM-AES-XPN-128/256
according to IEEE 802.1aebw-2013. This includes modifications to the Ethernet frame header,
insertion/removal of the MACsec header (SecTAG), encryption/decryption, authentication, and
authentication result insertion/verification. It does not perform MACsec header parsing, but relies on
external logic to provide a processing token that tells it how to process the incoming frame.
In addition to the MACsec specifications 0-byte, 30-byte, and 50-byte confidentiality offset, the MACsec
crypto engine supports byte-grained confidentiality offsets from 1 to 127 bytes. The MACsec crypto
engine supports one or two VLAN tag bypass operation wherein VLAN tags that bypass MACsec
processing are fully excluded from the encryption and authentication, such that the receiver side must be
able to remove the bypassed VLAN tags without breaking the MACsec packet. It also supports MPLS
header bypass wherein the MPLS link header is excluded from encryption and authentication, and the
client Ethernet frame is subjected to MACsec transformations.

3.7.1.6 Consistency Checking Engine

The Consistency Checking engine checks the contents of a frame at the output of the MACsec Crypto
engine (after any MACsec decryption) against a set of 16/64 programmable rules (depending on the
configuration) for consistency. A programmable per-rule priority level resolves any overlap between
these rules. This engine is not present in the egress configuration.

3.7.1.7 Output Post-Processing Engine

The Output Post-Processing engine checks the classification and MACsec Crypto engine processing
results against a fixed set of MACsec compliance rules, resulting in a drop decision if the rules are
violated. Additionally, it performs programmable MTU checking on the MACsec Crypto engine output
frame, with individual global and per-VLAN-user-priority MTU settings.
The engine combines these internal decisions with decisions made by the Classification and Consistency
Checking engines into a final pass/drop decision to the output adapter. Based on all the information from
the MACsec Crypto engine and the consistency checking engine available to it, the Output Post-
Processing engine also decides which statistics counters to increment.

3.7.1.8 Statistics Update Engine

The Statistics Update engine updates the statistics counter in the statistics RAM as instructed by the
Output Post-process engine. This allows updating to be scheduled with external statistics access and to
occur in parallel with the post-processing of the next frame. This engine also can be configured to skip
certain statistics counters.

3.7.1.9 Output Adapter

The Output Adapter block manages the output packet interface and ensures interface protocol
compliance by isolating the MACsec IP from this interface.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 100

Functional Descriptions

3.7.1.10 PKT128to64
The Packet 128to64 block is the interface of the MACsec IP with the other blocks. It converts the 128-bit
packet interface of MACsec IP to the 64-bit packet interface used to communicate with other blocks. It
also prepares the security fail debug code to be put into FCS field for packets failing security check.

3.7.2 MACsec Target Applications

The MACsec engine targets the following applications.
• Secure enterprise infrastructure and WAN ports
• Secure end-to-end Carrier Ethernet connections
• Secure Carrier Ethernet Mobile Backhaul, including high precision IEEE 1588v2 timing

3.7.2.1 MACsec Secured Enterprise Infrastructure and WAN Port

The following illustration shows an enterprise branch office or campus where a Local Area Network
(LAN) connected to a Wide Area Network (WAN) operated by a service provider is protected using
MACsec.
Figure 69 • Secure Enterprise Infrastructure and WAN
Service Provicer
Enterprise Branch Office or Campus Point of Presence (POP)
Hosts Enterprise
Switches
Service Edge Router
Enterprise
Branch Router
Access Link
Provider Network or
Internet

MACsec-Secured MACsec-Secured
MACsec-Secured LAN infrastructure
WAN access port Service Provider infrastructure

Each host has a dedicated physical link to an Enterprise Ethernet switch, and the switches are
connected to an enterprise branch router that also provides WAN access. In smaller configurations,
hosts can also connect directly to the branch router. All internal branch office, Ethernet ports are secured
using MACsec.
The branch router connects across an access link to a service provider’s service edge router, and this
access link is secured using MACsec. MACsec may also be used to secure the service provider's
network.
The 802.1X security protocols can be used for authentication and to automate the distribution and
management of MACsec encryption keys. The VSC8491-17 device supports 128-bit and 256-bit
encryption.

3.7.2.2 MACsec Secured Carrier Ethernet Connection

The following illustration shows a Carrier Ethernet network providing end-to-end MACsec secured WAN
connectivity for an enterprise.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 101

Functional Descriptions

Figure 70 • Secure Carrier Ethernet Connection

MACsec-secured data
over MEF EVC or MPLS

Carrier Ethernet Corporate

Network Headquarters
Branch Offices

With traditional MACsec, VLAN tags or MPLS labels are fully encrypted and hidden from the Carrier
Ethernet network, thereby limiting the enterprise to only the simplest point-to-point private line
connectivity services.
The VSC8491-17 device supports leaving the VLAN tags or MPLS labels unencrypted for use by the
Carrier Ethernet network while fully securing the enterprise's Ethernet data inside these encapsulations.
This approach uses standard, non-proprietary encapsulation formats with 128-bit and 256-bit encryption.
By enabling these features, the enterprise is able to take advantage of the latest Layer-2 (L2) VPN
services available from a Carrier Ethernet network. These L2 VPN services can be point-to-point or
multipoint, and can use standardized Metro Ethernet Forum (MEF) Carrier Ethernet and Internet
Engineering Task Force (IETF) MPLS service offerings, including multiple Virtual Private Lines per WAN
port.

3.7.2.3 MACsec Secured Mobile Backhaul with IEEE 1588

The following illustration shows a a typical mobile backhaul application where multiple network operators
collaborate to deliver mobile service. In this application, a mobile service provider uses MACsec to
secure the backhaul connections end-to-end through the network.
Figure 71 • Secure Mobile Backhaul with IEEE 1588

MACsec-secured data
through Access Operator's network
Mobile Service
Provider
Mobile Service Mobile Service
Provider NID Provider NID
Timing Access Operator
Network
Mobile Service
IEEE-1588 IEEE-1588
Provider Base Station
Slave Transparent Clock
or Boundary Clock

The mobile service provider may choose to leave VLAN tags or MPLS labels unencrypted so that the
access operator can map the virtual private line services.
In addition to backhauling data, IEEE 1588 packet-based timing technology delivers high-precision
frequency and phase synchronization to the base stations. IEEE 1588 packets may be encrypted along
with backhaul data and tunneled through the access operator network, or delivered as an unencrypted
synchronization service directly from the access operator network. To meet 4G/LTE specifications,
nanosecond-accurate time stamping of IEEE 1588 packets is required. However, such tight tolerances

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 102

Functional Descriptions

cannot be achieved using traditional MACsec, even if the IEEE 1588 packets themselves are
unencrypted.
The Microsemi IEEE 1588 time stamping engine in the VSC8491-17 device works in conjunction with the
MACsec engine to deliver 4G/LTE timing quality over Carrier Ethernet connections, while using MACsec
for end-to-end security across the access operator network.

3.7.3 Formats, Transforms, and Classification

This section shows the frame formats before and after MACsec transformation, with an overview of the
classifiable fields that can be used for SA classification for different MACsec applications. Classification
fields are selectable per SA. In depicting which fields may be used for pre-decrypt classification, it is
assumed that the confidentiality offset field is not used (all fields after SecTAG are encrypted).

3.7.3.1 Standard MACsec Formats

The following table summarizes the MACsec frame combinations in the standard MACsec mode.

Table 38 • Standard MACsec Frame Combinations

Pre-Decryption (Rx)
Unencrypted Format Pre-Encryption (Tx) Classification Fields Classification Fields
Untagged Ethernet DA, SA, Etype DA, SA, SecTAG
Single-tagged Ethernet DA, SA, TPID, VID, Etype DA, SA, SecTAG
Dual-tagged Ethernet DA, SA, TPID1, VID1, TPID2, VID2, Etype DA, SA, SecTAG

The following illustrations show each frame format before and after standard MACsec transformation.
Figure 72 • Untagged Ethernet
Classifiable Pre-Encryption

DA SA Etype Payload FCS

Figure 73 • Standard MACsec Transform of Untagged Ethernet

Classifiable pre-decryption

DA SA SecTAG Etype payload ICV FCS

Protected by ICV

Figure 74 • Single-Tagged Ethernet

Classifiable Pre-Encryption

DA SA VLAN Tag Etype Payload FCS

Figure 75 • Standard MACsec Transform of Single-Tagged Ethernet

Classifiable pre-decryption

DA SA SecTAG VLAN Tag Etype payload ICV FCS

Protected by ICV

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 103

Functional Descriptions

Figure 76 • Dual-Tagged Ethernet

Classifiable Pre-Encryption

DA SA VLAN Tag1 VLAN Tag2 Etype Payload FCS

Figure 77 • Standard MACsec Transform of Dual-Tagged Ethernet

Classifiable pre-decryption

DA SA SecTAG VLAN Tag1 VLAN Tag2 Etype payload ICV FCS

Protected by ICV

3.7.3.2 Advanced MACsec Formats

The following table summarizes the MACsec frame combinations in the advanced MACsec mode.

Table 39 • Advanced MACsec Frame Combinations

Unencrypted Encrypted Pre-Encryption (Tx) Pre-Decryption (Rx)

Format Format Classification Fields Classification Fields
Single-tagged MACsec plus DA, SA, TPID, VID, Etype DA, SA, TPID, VID, SecTAG
Ethernet single tag bypass
Dual-tagged MACsec plus DA, SA, TPID1, VID1, DA, SA, TPID1, VID1, SecTAG
Ethernet single tag bypass TPID2, VID2, Etype
Dual-tagged MACsec plus dual DA, SA, TPID1, VID1, DA, SA, TPID1, VID1, TPID2,
Ethernet tag bypass TPID2, VID2, Etype VID2, SecTAG
EoMPLS with MACsec plus C-DA, C-SA, MPLS Etype, C-DA, C-SA, MPLS Etype,
one Label EoMPLS header 32-bit Label 32-bit label, SecTAG
bypass
EoMPLS with MACsec plus C-DA, C-SA, MPLS Etype, C-DA, C-SA, MPLS Etype,
two Labels EoMPLS header 32-bit Label1, 32-bit Label2 32-bit label1, 32-bit label2,
bypass SecTAG

The following illustrations show each frame format before and after advanced MACsec transformation.
Figure 78 • Single-Tagged Ethernet
Classifiable Pre-Encryption

DA SA VLAN Tag Etype Payload FCS

Figure 79 • MACsec Transform to Single Tag Bypass

C lassifiable P re-D ecryption

DA SA V LA N Tag S ecTA G E type P ayload IC V FC S

P rotected by IC V P rotected by IC V

Figure 80 • Dual-Tagged Ethernet

Classifiable Pre-Encryption

DA SA VLAN Tag1 VLAN Tag2 Etype Payload FCS

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 104

Functional Descriptions

Figure 81 • MACsec Transform to Single and Dual Tag Bypass

MACsec plus Single Tag Bypass
Classifiable Pre-Decryption

DA SA VLAN Tag1 SecTAG VLAN Tag2 Etype Payload ICV FCS

Protected by ICV Protected by ICV

MACsec plus Dual Tag Bypass

Classifiable Pre-Decryption (may need C.O.)

DA SA VLAN Tag1 VLAN Tag2 SecTAG Etype Payload ICV FCS

Protected by ICV Protected by ICV

Figure 82 • EoMPLS with One Label

Classifiable Pre-Encryption
MPLS MPLS Optional Client_DA Client_ SA Client Payload
DA SA Etype FCS
Etype Label[S=1] CW/ ACH

Figure 83 • Standard and Advanced MACsec Transform

Standard MACsec format
Classifiable Pre-Decryption
MPLS MPLS Optional
DA SA SecTAG Client_DA Client_SA Etype Client Payload ICV FCS
Etype Label [S=1] CW/ACH

Protected by ICV

MACsec plus EoMPLS Header Bypass

Classifiable Pre-Decryption Classifiable Pre-Decryption
MPLS MPLS Optional
DA SA Client_DA Client_SA SecTAG Etype Client Payload ICV FCS
Etype Label [S=1] CW/ACH

Protected by ICV

Figure 84 • EoMPLS with Two Labels

Classifiable Pre-Encryption
MPLS MPLS MPLS Optional
DA SA Client_DA Client_SA Etype Client Payload FCS
Etype Label1 [S=0] Label2 [S=1] CW/ ACH

Figure 85 • Standard and Advanced MACsec Transform

Standard MACsec format
Classifiable Pre-Decryption
MPLS MPLS MPLS Optional
DA SA SecTAG Client_DA Client_SA Etype Client Payload ICV FCS
Etype Label1 [S=0] Label2 [S=1] CW/ACH

Protected by ICV

MACsec plus EoMPLS Header Bypass

Classifiable Pre -Decryption Classifiable Pre -Decryption
MPLS MPLS MPLS Optional
DA SA Client_DA Client_SA SecTAG Etype Client Payload ICV FCS
Etype Label1 [S=0] Label2 [S=1] CW/ACH

Protected by ICV

3.7.4 MACsec Integration in PHY

The MACsec block is designed to be integrated with a host MAC and a line MAC to form a plug-in
MACsec solution between an existing Ethernet MAC (system-side) and an existing Ethernet PHY (line-
side). MACsec adds bandwidth in egress. This increase in bandwidth is handled adding IEEE 802.3
pause flow control toward the system. The FC buffer block provides packet buffering and controls the

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 105

Functional Descriptions

IEEE 802.3 pause flow control generation to handle MACsec frame expansion. The IEEE 1588 block is
on the host-side of MACsec, and the IEEE 1588 PTP frames are also subjected to MACsec
transformations.
The following illustration shows the integration of MACsec in the PHY.
Figure 86 • MACsec in PHY
PHY with MACSec

MACSec SubSystem

xMII
xMII Host FC Line PCS +
S 1588 MACSec
PHY XS MAC Rx Buffer MAC Tx PMA
Y (Egress) (Egress)
(Egress) (Egress) (Egress) L
S I
T N
E E
M

Host FC Line
xMII 1588 MACSec PCS +
PHY XS MAC Tx Buffer MAC Rx
(Ingress) (Ingress) PMA
(Ingress) (Ingress) (Ingress) xMII

3.7.5 MACsec Pipeline Operation

MACsec ingress and egress pipeline operations are identical, except for a few situations mentioned in
the following sections. The MACsec block always operates in cut-through mode. The length of the frame
is calculated on the fly, and does not need to be known before the start of processing. This means that
MACsec egress processing encrypts (protects) all bytes of the frame fed into the MACsec core. If the
frame contains Ethernet padding, this padding is encrypted/protected by MACsec and the ICV is
appended after it. For ingress processing, the MACsec block accepts frames with Ethernet padding and
it strips Ethernet padding from short MACsec frames.
Ethernet frames are submitted to the MACsec egress/ingress block with their Ethernet header
(destination address, source address, Ethertype), but without the leading preamble and start-of-frame
bytes, and trailing 4-byte CRC (FCS). It is the responsibility of the host/line MAC to strip and check the
CRC of each incoming frame.
In the case of large frames, the first output data word of a frame may leave the MACsec pipeline before
the last input data word of a frame enters, and errors such as ICV check verification or MTU checking
may only be detected after the last byte of frame data has been processed. As a consequence, dropping
a frame is accomplished by setting the frame abort signal and not by preventing the frame from
appearing on the output. In other words, the system/line MAC transmits a frame with bad CRC. The
engine can be programmed to drop frames completely (internal drop), but only if the decision to drop has
been made by the flow lookup stage. The pipeline outputs the (processed) frames in the same order they
are input, unless the frame is dropped internally. The MACsec block can also be bypassed completely to
improve latency.
The SL field in MACsec indicates the end of the MACsec frame, which is needed to locate the ICV in
case Ethernet padding follows the ICV. For such frames, the MACsec block uses the information from the
SecTAG of the frame to calculate the actual MACsec frame length and uses this length during ingress
processing. All data that follows the ICV is removed from the data stream by the MACsec block. This
action is the de-padding action, using the MACsec protocol header. The ICV is assumed to be at the
location as indicated by the SecTAG, otherwise the frame does not pass the MACsec integrity check.
If the SL field in the MACsec frame indicates a longer frame than the packet actually received by the
MACsec block (if the frame does not pass MACsec PDU check), the MACsec block flags this situation as
an integrity check failure or packet length error, depending on the difference in length.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 106

Functional Descriptions

Note: The de-padding action is applicable only for MACsec frames that are going to be decrypted/validated by
the MACsec flow and will not change the regular MACsec processing latency. No de-padding action is
performed on bypass/drop frames.
After ingress MACsec processing, it is possible for the frame to become smaller than 64 bytes. Such
frames are then padded by the host MAC (if enabled), and the packet processing switch/system receives
64 byte frames after Ethernet padding.
In the egress direction, the MACsec core calculates and updates the SL field in the MACsec header, and
authenticates and encrypts (optionally) the frame if a frame's size (including the MACsec header and
ICV) is less than 64-bytes.
Note: This short length field indicates frame data from after the first byte of the MACsec header to byte
immediately before ICV.
For this feature to work, host MAC receiver should be configured to allow undersized frames, and line
MAC transmitter should be configured to pad frames.
Host and line MACs do not accept less than 64 byte frames (without Ethernet padding) from system/line
interfaces, and do not remove the Ethernet padding from the frames.
Each frame at input is accompanied by the following signals:
• Port Number- Two-bit signal that indicates the source port (common, reserved, controlled, or
uncontrolled) of the packet as defined in the IEEE 802.1AE standard.
• Bad CRC/Packet Error- Bits that indicate that the packet has a bad CRC/packet error.
Frames with a bad CRC or other packet errors are forwarded to the output with the same errors, unless
their classification leads to a decision to drop them. Because error signals appear at the end of a frame
and processing must start before the end of a frame is received, classification and processing is
performed, but statistics are not updated.
The source port for MAC data/control frames is configurable. Typically, egress MAC data frames are put
on the controlled port and MAC control frames are put on the uncontrolled port. All ingress frames are put
on the common port. This configuration is controlled using MAC_DATA_FRAMES_SRC_PORT and
MAC_CTRL_FRAMES_SRC_PORT in the MACSEC_CTL_CFG register. Control packet classification
determines the frames that are assumed to have come from controlled/uncontrolled ports in egress and
the frames that should go to controlled/uncontrolled ports in ingress.
LPI and fault signals that appear on the Ethernet interface can be detected by the MAC and converted
into internal status frames (single-byte frames containing the state of the signals). The MACsec block can
recognize these status frames on the input and propagate them to its output.
Status frames travel through the pipeline along with normal Ethernet frames, so they appear at the output
after the preceding Ethernet frame and before any frames that appear after the status change. However,
status frames do not take part in any operations of the pipeline. They are invisible to static classification,
flow lookup, MACsec processing, and consistency checking.
The following illustrations show the egress and ingress MACsec data flows.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 107

Functional Descriptions

Figure 87 • MACsec Egress Data Flow

Egress MACSec Core

Programmable latency
29 way
control control
control frame
classification drop/
MTU Checking and
8 entry default packet bypass
blocking module
handling registers drop/
0 bypass/
MACSec tag process
S detection drop/ MACSec crypto -core L
Y bypass/ with Vlan Tag bypass I
and MPLS header
S process N
bypass 128
T E
128 1
E VLAN tag VLAN, 64/16 entry 64/16 entry S
64/16 entry transform Static
M detection QinQ.. parameters & state bypass
flow flow
lookup packet Statistics module
packet handling
classification registers
EoMPLS header MPLS
bypass proc flow hit

Figure 88 • MACsec Ingress Data Flow

M A CS ec In gress

2 9 w ay Prog ram m ab le
con trol Drop / laten cy con trol
con trol fram e Byp ass
classification MT U C h eckin g
8 en try d efau lt p acket an d
Drop /
h an d lin g reg isters b lockin g m od u le
Byp ass /
0
Process
MAC Sec tag
d etection Drop / MAC Sec cryp to - 6 4/ 1 6 en try S
Byp ass / core w ith vlan tag p rog ram m ab l Y
L b yp ass an d MPLS e con sisten cy
Process S
I h ead er b yp ass ch eckin g 128 T
N (on ly on E
128 1 6 4/ 1 6 en try
E VLAN tag VLAN , Static
6 4 /1 6 en try 6 4 /1 6 en try S tran sform in g ress sid e ) M
d etection Q in Q.. flow flow b yp ass
p aram eters & state
looku p p acket Statistics m od u le
p acket h an d lin g
classification reg isters
E oMPLS h ead er M PLS
b yp ass p roc flow h it

The following sections describe the pipeline stages. Of these pipeline stages, the MACsec transform
stage is the only one that can modify the frame data or drop a frame completely (no frame will appear at
the output of the pipeline in that case). Other stages can only perform the following actions for frame
data:
• Inspect the frame data, such as performing a classification based on fields in a header.
• Drop the frame (which is already streaming out) by setting the frame abort signal along with the last
word of data.
Static Classification
This is the first stage of packet classification. Control packet classification, MACsec tag parsing, and
VLAN tag parsing are carried out in parallel.
Flow Lookup
Each table of 16 SA flows can match on a number of criteria. An action and a MACsec context is
associated with each flow. If the packet does not match any of these 16 flows, one of eight default actions
is selected, depending on the results of MACsec tag parsing and control packet classification.
MACsec Transform
This stage carries out the actual MACsec encryption and authentication. It uses the MACsec context
associated with the flow that was matched in the previous stage. A MACsec context is a data structure
containing all information (such as key and sequence numbers) needed to carry out a MACsec
transform. This stage can also bypass or drop certain packets.
The MACsec transform stage can be bypassed by setting MACSEC_BYPASS_ENA = 1 in the
MACSEC_ENA_CFG register. Setting the MACSEC_BYPASS_ENA = 0 and MACSEC_ENA = 1 results

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 108

Functional Descriptions

in traffic passing through the MACsec transform block. Setting the MACSEC_BYPASS_ENA and
MACSEC_ENA bits to 0 results in all traffic being dropped at the input interface of MACsec.
Ingress Consistency Checking
This stage is not present in the egress-only version of the MACsec block. It extracts information from the
decrypted packet and checks it against a table of 64/16 rules. Rules can either reject or pass certain
packets. Separate default actions can be configured for control and non-control packets (in case no
match is found in the table).
Output Postprocessor
This stage checks the results of the MACsec transform operation. It also checks that the length of a
packet does not exceed the MTU (incrementing a counter if the MTU is exceeded, and optionally tagging
the packet for deletion). Each of the eight VLAN user priorities and non-VLAN packets can have a
different MTU. This stage implements the MACsec-compliant post-processing decision tree, and updates
all MACsec statistics.

3.7.5.1 Static Classification

Control packet classification, MACsec header parsing, and VLAN tag parsing are the three static
classification operations performed in parallel to produce the following results:
• Control- Single bit that is set if the packet is classified as a control packet.
• MACsec Tag Status- One of four values: untagged, tagged, bad tag and KaY, where tagged means
the packet has a valid non-KaY MACsec SecTAG.
• VLAN Related Status Signals- VLAN valid, VLAN ID, Inner VLAN ID, VLAN User Priority, Inner
VLAN User Priority, QTAG valid, STAG valid, and QinQ valid.
• Parsed Ethertype- First non-VLAN Ethertype found in the frame.
The following sections describe the static classification operations.

3.7.5.1.1 Control Packet Classification

Control packet classification is used to identify frames from uncontrolled ports and exclude them from
MACsec processing. Frames such as the MAC control frames and MKA/EAPOL frames are forwarded
without MACsec processing because they use uncontrolled ports for transmission. MKA/EAPOL frames
are used for Key exchange and have Ethertype 0x888E.
The control packet classification logic classifies a packet as a control packet based on its destination
address and/or its Ethertype. It yields a single-bit output (control) classifying the packet either as a
control packet or not.
The control packet classification logic can match a packet based on 29 individually-enabled criterion. If
the packet matches one or more of the enabled criterion, the packet is classified as a control packet and
the control output is set to 1. If no enabled criterion is matched, the packet is not classified as a control
packet. The CTL_PACKET_CLASS_PARAMS and CTL_PACKET_CLASS_PARAMS2 registers
configure control packet classification. The match criterion are as follows.
• The fixed Ethernet destination address 01_00_0C_CC_CC_CC. The corresponding register
CP_MAC_DA_48* has this address as a reset value, but this value can be changed if needed.
• The fixed Ethernet destination address range 01_80_C2_00_00_0? (the first 44 bits must match; the
trailing 4 bits are don't care). The corresponding register CP_MAC_DA_44* has this address range
as a reset value, but this value can be changed if needed. It is always a range with 44 matching bits
and 4 don't care bits.
• One free to program Ethernet destination address range specified by the CP_MAC_DA_START and
CP_MAC_DA_END registers. Ethernet addresses are treated as unsigned 48-bit integers, as shown
in the following examples.
If CP_MAC_DA_START = 00_80_C2_00_00_00 and CP_MAC_DA_END = 00_80_C2_00_00_0F,
the matched range is identical to the range normally matched by MAC_DA_44.
If CP_MAC_DA_START = 00_00_00_00_00_00 and CP_MAC_DA_END = FF_FF_FF_FF_FF_FF,
all destination addresses are matched (every packet is classified as a control
packet).
If CP_MAC_DA_START = CP_MAC_DA_END,
then only a single address will be matched.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 109

Functional Descriptions

• Eight individual Ethernet destination addresses: CP_MAC_DA_MATCH_0 through

CP_MAC_DA_MATCH_7.
• Sixteen individual Ethertypes: CP_MAC_ET_MATCH_0 through CP_MAC_ET_MATCH_7 where
each Ethertype compare value field shares a register with two destination address compare value
bytes and CP_MAC_ET_MATCH_10 through MAC_ET_MATCH_17 registers.
• Two combinations of destination address and Ethertype: CP_MAC_DA_ET_MATCH_8 and
CP_MAC_DA_ET_MATCH_9. A packet matches only if both the destination address and the
Ethertype match.
• Even though the registers for destination addresses and Ethertypes 8 and 9 have the same format
as those for destination addresses and Ethertypes 0 to 7 and 10 to 17, they have different
semantics. Destination address 8 can only be enabled in combination with Ethertype 8, and only
packets with both a matching destination address and a matching Ethertype will match this criterion.
The same applies to destination address and Ethertype 9. On the other hand, destination addresses
0 to 7 can be enabled independent of Ethertypes 0 to 7. When both destination address 0 and
Ethertype 0 are enabled, packets that have either a matching destination address or a matching
Ethertype (or both) will be classified as control packets.
• After reset, control packet matching criteria are disabled. The registers for a matching criterion must
be programmed to enable it.
• Either the first Ethertype after the DA/SA fields or the parsed Ethertype, determined by the VLAN
parsing algorithm, is the Ethertype value (number 0 to 17, including the combined numbers 8, 9)
from the packet that can be used to compare. This selection is done using the CP_MATCH_MODE
register.
• Rules are enabled using the CP_MATCH_ENABLE register.

3.7.5.1.2 MACsec Tag Parsing

The MACsec tag parsing logic inspects MACsec tags. MACsec tags must follow the source address,
without any intervening VLAN tags- they may follow VLAN tags only in VLAN tag bypass mode. MACsec
tag parsing classifies each packet into one of four categories:
• Untagged- No MACsec tag (Ethertype differs from 0x88E5).
• Bad Tag- Invalid MACsec tag, as determined by the tag detection logic.
• KaY Tag- These packets are generated and/or handled by software and no MACsec processing is
performed on them by the hardware except for straight bypass.
• Tagged- Valid MACsec tag that is not KaY.
The following table shows the IEEE 802.1AE checks that determine the status of the MACsec tag
parsing.

Table 40 • MACsec Tag Parsing Checks

MACsec Tag (SecTAG) Check Result

Ethertype is not MACSec type Untagged
V bit = 1 Bad tag
C bit = 0 and E bit = 1 KaY
C bit =1 and E bit = 0 Bad tag
SC bit = 1 and ES bit = 1 Bad tag
SC bit = 1 and SCB bit = 1 Bad tag
SL ≥ 48 Bad tag
PN = 0 Bad tag
All other Tagged

MACsec tag parsing checks are controlled by configuring the SAM_NM_PARSING register.

3.7.5.1.3 VLAN Tag Parsing

The VLAN tag parsing logic recognizes VLAN tags that immediately follow the source address. Both
802.1Q and 802.1s tags can be recognized. Packets with two VLAN tags can also be recognized.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 110

Functional Descriptions

The VLAN tag parsing logic generates the following signals that can be used by flow lookup and other
processing stages.
• VLAN Valid- Single bit that is set when a VLAN tag (of any type) is successfully parsed.
• Stag Valid- Single bit that is set if the first valid VLAN tag is an 802.1S tag.
• Qtag Valid- Single bit that is set if the first valid VLAN tag is an 802.1Q tag.
• Q-in-Q Found- Single bit that is set if two valid VLAN tags were found.
• VLAN User Priority- Three-bit field derived from the first VLAN tag. For non-VLAN tag packets the
default user priority is returned. User priority processing can be disabled to also return the default
user priority.
• VLAN ID- Twelve-bit field taken from the first VLAN tag. Undefined for non- VLAN packets.
• Inner VLAN User Priority- Three-bit field derived from the second (inner) VLAN tag. This value is
always passed through the re-mapping table (the SAM_CP_TAG2 register), and the result value is
used in classification. Undefined for non-VLAN packets or VLAN packets without a second VLAN
tag.
• Inner VLAN ID- Twelve-bit field that is taken from the second (inner) VLAN tag. Undefined for non-
VLAN packets or VLAN packets without a second VLAN tag.
• Ethertype- Ethertype extracted from the packet after zero, one, or two VLAN tags.
VLAN parsing is controlled by configuring the SAM_CP_TAG, SAM_PP_TAGS, SAM_PP_TAGS2, and
SAM_CP_TAG2 registers.
The parsed VLAN fields (including UP) are used in SA flow classification lookup. The MACsec block also
maintains VLAN statistics on a per user priority basis. This includes dropped and oversize packets on a
user priority basis.

3.7.5.2 Flow Lookup/SA Flow Classification

The flow lookup logic associates each packet with one of the two following flows:
• A table of SA matching flows, each of which can match a packet based on a set of match criterion. If
a packet matches multiple (enabled) SA flows, the SA flow with the highest user-defined priority
value is selected. The flow specifies which action must be performed (drop the packet, pass it
unchanged, or perform a MACsec transform). Each SA flow for which a MACSec operation is
specified corresponds to exactly one MACsec context (and hence to a single MACsec SA, either
ingress or egress). In other words, all packets that are to be processed using a single MACsec SA
have to be matched by a single SA flow.
• A table of eight non-matching flows. If no enabled SA flow matches a packet, a non-matching flow is
selected based on the MACsec tag parsing result and the control bit (from the control packet
classification). For these non-matching flows, the only possible actions are bypass and drop
(MACsec operations cannot be selected here).
The output of the flow lookup is as follows:
• SA Hit- Single bit signal that is set if the packet matched an enabled SA flow.
• SA Index- Index of the SA flow being matched. If no SA flow was matched, this field is composed
from the control packet classification and MACsec tag parsing results, which identifies the non-
matching flow used.

3.7.5.2.1 SA Match Criteria

Each SA flow has a set of registers that specify the match criteria using one of two following categories:
• The four MACsec tag match bits (untagged, tagged, bad_tag, and kay_tag in the
SAM_MISC_MATCH registers). If the corresponding bit is set in the SAM_MISC_MATCH register,
packets from that category (as classified by the MACsec classification logic) can be matched if the
other criteria are also satisfied. If the corresponding bit is clear, packets from that category can not
be matched.
• The mask-able match criteria. Each of these criteria can be masked by a mask bit in the
SAM_MASK registers. If the corresponding mask bit is clear, the matching criterion is not tested and
packets may be matched regardless of actual value in the packet. If the corresponding mask bit is
set, the matching criterion is tested; if the packet has a different value from that specified in the flow,
the packet will not be matched.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 111

Functional Descriptions

The following table shows the match criteria and maskable bits.

Table 41 • Match Criteria and Maskable Bits

Egress/Ingress SA Match Classifiers Data Bits Mask Bits

MAC SA and MAC DA (mask bit per byte) 96 12
MAC Ethertype (parsed Ethertype) 16 1
VLAN class / parsing result 4 4
(vlan_valid, qtag_valid, stag_valid, qinq_found)
VLAN UP (parsed User Priority) 3 1
VLAN ID 12 1
Inner VLAN UP 3 1
(inner User Priority when Q-in-Q is detected)
Inner VLAN ID (inner VLAN ID when Q-in-Q is detected) 12 1
Source port (controlled/uncontrolled/common/reserved) 2 1
Control packet 1 1
MACsec tag classifier output 0 4
(untagged/tagged/bad tag/KaY)
MACsec SCI (compared only for MACsec tagged frames, 64 1
available only in ingress)
MACsec TCI.AN (compared only for MACsec tagged 8 8
frames, available only in ingress, individually masked)
Field_2B_16B (used in MPLS header bypass mode) 64 64
SA match priority 4 0
Entry enable 1 0

If all four MACsec tag match bits are set and none of the mask bits are set, the flow matches all possible
packets. If none of the MACsec tag match bits are set, the flow does not match any packets.
If an exact match of the MAC source address is desired, all six mac_sa_mask bits must be set. If an
exact match of the MAC destination address is desired, all six ma_da_mask bits must be set.
The SCI and TCI.AN fields are used in only in the ingress SA flow classification. The TCI.AN field match
can be masked per bit. If an exact match of the TCI.AN field is desired, all eight tci_an_mask bits must be
set. If a match on the SCI field is desired, make sure that the SCI field is expected in the packet and
match on the SC bit in the TCI field (SC bit must be set). For packets without an SCI field, the TCI field in
combination with the MAC source address determines the match criterion (as defined in the
IEEE 802.1AE standard).
The VLAN ID output can be undefined for non-VLAN packets. When matching packets on VLAN ID, also
match on vlan_valid = 1.
A packet is matched on the parsed Ethertype from the VLAN classification logic. This differs from the
Ethertype used by the control packet classification logic.
Each flow can be enabled or disabled individually. Only enabled flows are selected when they match a
frame. When multiple enabled flows match a frame, the one with the highest match_priority field (a
number from 0 to 15) will be selected; among equal priority flows the one with the lowest index will be
selected.
The match_priority field is always 4-bit wide (16 priority levels) regardless of the number of SAs
supported in the given configuration. The SA_MATCH_PARAMS registers control the SA match criteria.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 112

Functional Descriptions

3.7.5.2.2 Enabling and Disabling Flows

SA_MATCH_CTL_PARAMS registers control the enabling and disabling of matching table entries in the
main SA matching module. It is also possible to set, clear, and toggle enable bits with a single write
action.
Note: To write the match registers of an SA flow or the MACsec context, the flow must be disabled first to
ensure that all flow parameters are loaded into the engine when the flow is enabled again.
If the block supports more than 32 SAs, setting, clearing and toggling of enable bits for SA entries
beyond 32 requires two write operations. The upper flags are stored with the first write operation to
SAM_TOGGLE2, SAM_SET2, or SAM_CLEAR2 respectively. The action for all SA entries is applied and
the upper flags are cleared to zero with the second write operation to SAM_TOGGLE1, SAM_SET1, or
SAM_CLEAR1, respectively.
Each SA flow can be enabled or disabled individually. If an SA flow is disabled, it will not match any
packets.
When a previously enabled SA flow is disabled (by writing to the SAM_ENTRY_CLEAR1/2 or
SAM_ENTRY_TOGGLE1/2 registers), the hardware loads the unsafe field in SAM_IN_FLIGHT register
with the number of packets currently processed in the pipeline and the software must wait for the unsafe
field to reach zero before it writes to the MACsec context or any of the registers belonging to that SA flow.
This is necessary to make sure that all packets that might make use of the disabled flow or the
associated MACsec context have left the engine.

3.7.5.2.3 Flow Actions

Each SA flow has a SAM_FLOW_CTRL_IGR/EGR register that specifies the action that must be taken
when a frame is matched by that SA flow. The action is determined by one of the following four flow
types.
• Bypass- The frame is passed unchanged.
• Drop- The frame is dropped. The drop_action field specifies the action.
The packet can be forwarded with a corrupt CRC indication.
The packet can be forwarded with a bad packet (packet error) indication.
Note: In both cases, the frame abort signal is set towards the MAC and the drop behavior is the same.
• The packet can be dropped internally. The dropped packet does not appear on the output of the
MACsec because the drop_internal decision is taken before the end of the packet is seen. This
operation can drop packets received with CRC and/or packet errors.

3.7.5.2.4 MACsec Ingress and Egress Processing

MACsec ingress and egress processing includes performing the MACsec transform (adding/removing
SecTag, encryption/decryption, and generating/verifying ICV), post-processing steps, and updating
statistics counters. A properly configured MACsec block implements all per-packet steps of a compliant
MACsec implementation.
The flow action also specifies the destination port of the packet (as defined in the IEEE 802.1AE
standard) in a two-bit field that appears at the output of the data pipeline to PKT128to64 and will be used
for statistics.
The following table shows the egress SA flow action related to a matching entry, as defined in the
SAM_FLOW_CTRL_EGR register.

Table 42 • Egress SA Flow Actions

SA Flow Action Description Data Bits

Flow type Bypass/Drop/Egress process 2

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 113

Functional Descriptions

Table 42 • Egress SA Flow Actions (continued)

SA Flow Action Description Data Bits

Dest_port Destination port 2
00b: Common port
01b: Reserved port
10b: Controlled Port
11b: Uncontrolled port
Drop_action Defines the way drop operation is performed 2
protect_frame 1b: Enable frame protection 1
0b: Bypass frame through crypto-core
sa_in_use MACsec SA is in use for the looked up SA 1
include_sci Enables use of implicit/explicit SCI 1
use_es Enable ES bit 1
use_scb Enable SCB bit 1
Tag_bypass_size The number of allowed tags to bypass MACsec (0/1/2) 2
Confidentiality offset The number of bytes that must be authenticated but not 7
encrypted after SecTAG
Confidentiality protect Enables confidentiality protection 1

The following table shows the ingress SA flow action related to a matching entry, as defined in the
SAM_FLOW_CTRL_IGR register.

Table 43 • Ingress SA Flow Actions

SA Match Action Description Data Bits

Flow Type Bypass/Drop/Ingress process 2
Dest_port Destination port 2
00b: Common port
01b: Reserved port
10b: Controlled Port
11b: Uncontrolled port
Drop_action Defines the way drop operation is performed 2
Drop_non_reserved Perform drop_action if packet is not from the reserved port 1
Replay_protect Enable/Disable frame replay protection 1
sa_in_use MACsec SA is in use for the looked up SA 1
validate_frames Frame validation level for MACsec ingress processing 2
(disable/check/strict)
Confidentiality offset The number of bytes that must be authenticated but not 7
decrypted after SecTAG

MACsec contexts, which store the sequence number, keys, SCI, and other information, are used for
further transformation of frames for MACsec egress/ingress flow type processes.

3.7.5.2.5 Non-Matching Flows

The SAM_NM_FLOW_NCP/SAM_NM_FLOW_CP registers define how packets that did not match any
of the SA match entries are handled. This is subdivided into eight packet type categories, split by
whether or not the packet was classified as a control packet, and the output of the MACsec tag
classification logic (untagged/tagged/bad tag/KaY).

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 114

Functional Descriptions

The actions specified for each flow are a subset of those specified for SA flows (only pass and drop are
possible). Each of these flows can specify that a packet must be dropped or bypassed. It also specifies
the destination port. The way a packet must be dropped can also be specified.

3.7.5.3 VLAN Tag and EoMPLS Header Bypass Modes

VLAN tag bypass and EoMPLS header bypass are advanced MACsec processing modes with the
following classification extensions to the standard configuration.
• Handling of VLAN Tag bypass format (tag bypass).
• Handling of EoMPLS header bypass format (header bypass).
• Processing of packets with SecTAG appearing after one or two VLAN tags, where VLAN tags are not
included in the cryptographic operations (Microsemi tag bypass format).
• Processing of packets with SecTAG (and C-SA & C-DA) appearing after an Ethernet Header (SA,
DA, ET) with from 2 to 16 bytes of data, where the header and data is not included in the
cryptographic operations (Microsemi header bypass format).
• Control packet detection for packets in these proprietary formats.
• Programmable match fields used in SA lookup for packets in these proprietary formats.

3.7.5.3.1 Tag Bypass Frame Format

Tag bypass is an extension to the standard MACsec frame that allows one or two VLAN tags in front of
the SecTAG. These VLAN tags are fully excluded from MACsec protection and bypassed instead. The
following illustration shows the format of the frame.
Figure 89 • VLAN Tag Bypass Format

Original Frame (pre-encrypt, post-decrypt)

DA SA 1 or 2 VLAN Tags Rest of Payload FCS

Secure frame, TAG Bypass format

Inserted Encrypted Inserted Updated

Bypasses MACsec opt. confident. offset

DA SA 1 or 2 VLAN Tags SecTAG Rest of Payload ICV FCS

Protected by ICV

The following logic is used to process the tag bypass format.

• For egress processing, the number of bypassed VLAN tags for encryption is looked-up in the
MACsec flow action (SAM_FLOW_CTRL_EGR::TAG_BYPASS_SIZE). If this value is zero, the
standard MACsec protection is applied.
• For ingress processing, the number of bypassed VLAN tags is determined by the VLAN parser and
position of the SecTAG. The VLAN parser does not look beyond the SecTAG.
• KaY packets (to be bypassed) are detected on both egress and ingress configurations (the VLAN
parser defines SecTAG position).
• VLAN tags that bypass MACsec processing are fully excluded from the encryption and
authentication, such that the receiver side must be able to remove the bypassed VLAN tags without
breaking the MACsec packet.

3.7.5.3.2 EoMPLS Header Bypass Frame Format

EoMPLS Header Bypass is an extension to the frame handling of the standard MACsec frame format
that allows an additional proprietary header in front of the MAC frame. The following illustration shows
the format of the frame.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 115

Functional Descriptions

Figure 90 • EoMPLS Header Bypass Format

Original Frame (pre-encrypt, post-decrypt)

DA2 SA2 Etype2 2B – 16B DA SA Rest of Payload FCS

Secure frame, Header Bypass format

Inserted Encrypted Inserted Updated
Bypasses MACsec opt. confident. offset

DA2 SA2 Etype2 2B – 16B DA SA SecTAG Rest of Payload ICV FCS

Protected By ICV

The following restrictions are applied to the EoMPLS header bypass format.
• The mode is statically controlled by programming the size of the bypassed header. Size of zero
indicates absence of the bypassed header.
• No other secure format is possible on the port when header bypass is enabled.
• 2B–16B field is always one size on a port, configurable to be 2, 4, 6...16 Bytes. A static configuration
register specifies size of the field. For EoMPLS this is generally configured as multiple of 4B.
The following logic is used to process the EoMPLS header bypass format.
• Control Packet Detection- Based on Etype2 matching a configured (static) value.
If Etype2 matches, detect and process control packets using MAC_DA, MAC_SA, and parsed Etype
(after MAC_SA) to detect EAPOL/MKA transported in MPLS tunnels.
Other Etype2 values, detect and process control packets using MAC_DA2, MAC_SA2, and Etype2
to detect any other MAC control frames.
• SecTAG Position- Determined by size of 2B–16B field and located right after it.
• Egress SA Match- Uses Etype2, up to first 64 bits of the 2B–16B field, MAC_DA, and MAC_SA.
The 2B–16B match field in the SA is bit-maskable.
• Ingress SA Match- Uses Etype2, up to first 64 bits of the 2B–16B field, MAC_DA, MAC_SA, and
SecTAG fields. The 2B–16B match field in the SA is bit-maskable.

3.7.5.4 MACsec Transform

The MACsec transform carries out the actual frame transformation. For egress MACsec operations, it
inserts the SecTAG, optionally encrypts the payload data, and appends the ICV. For ingress MACsec
operations, it removes the SecTAG, optionally decrypts the payload data, and removes and validates the
ICV. The MACsec transform stage can detect error conditions (such as sequence number and
authentication errors) that cause the frame to be dropped by applying a flow define drop_action.
The MACsec transform does not detect errors in the SecTag that the MACsec classification logic can
catch. Only packets that are classified as tagged (valid non-KaY tag) may be submitted to ingress
MACsec processing.
The MACsec transform stage uses the MACsec crypto engine for the actual MACsec transform, which
operates in the following two major modes.
• In MACsec mode, the crypto engine is active and MACsec transforms can be performed.
• In static bypass mode, the crypto engine is effectively bypassed, which leads to a lower system
latency. In this mode, no MACsec transforms are possible. The classification, consistency checking,
and MTU check logic are still functional and the MACsec block may still filter (pass or drop) frames.
The MISC_CONTROL register enables static bypass, controls the latency equalization function, allows
MACsec-compliant handling of MACsec frames for which no MACsec SA is available, and controls the
maximum size of transform record.
If a MACsec SecY receives a MACsec frame on the common port for which it has no SA and the frame
payload is unchanged (authenticate-only operation, C = 0, E = 0), it can still forward the frame to the

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 116

Functional Descriptions

controlled port without checking the authentication simply by stripping the SecTAG and ICV. This will
occur if all the following conditions are met.
• The frame is classified as tagged.
• The frame is not matched by any installed MACsec SAs. The frame may either match no SA flow at
all or a non-MACsec SA flow.
• The flow type of SAM_NM_FLOW_CP/SAM_NM_FLOW_NCP (whichever is applicable to that
packet) for tagged frames is set to bypass.
• The TCI field has C = 0, E = 0.
• The nm_macsec_en bit is set.
• The validate_frames setting is either disabled or check, but not strict.

3.7.5.4.1 MACsec Context and Transform Record

The MACsec block contains an array of MACsec transform records that correspond to the number of
supported SAs. Each transform record is 20 × 32-bit words (80 bytes) in size in the ingress direction, and
24 × 32-bit words (96 bytes) in size in the egress direction, and corresponds to the SA flow with the same
index. The MACsec transform operation is fully specified by a combination of the contents of the
SAM_FLOW_CTRL_IGR/EGR register and the contents of the transform record. It corresponds to the
operation of a single MACsec SA.
Transform record refers to the data structure as stored in the array. MACsec context refers to the
information contained in a transform record. Transform record data are stored in the
XFORM_RECORD_REGS registers. The following tables show the format for each transform record.

Table 44 • Transform Record Format (Non-XPN)

128 Bit AES Keys 256 Bit AES key

128 Bit block Egress Ingress Egress Ingress
0 CTRL Word CTRL Word CTRL Word CTRL Word
Context ID Context ID Context ID Context ID
Key0 Key0 Key0 Key0
Key1 Key1 Key1 Key1
1 Key2 Key2 Key2 Key2
Key3 Key3 Key3 Key3
HashKey0 HashKey0 Key4 Key4
HashKey1 HashKey1 Key5 Key5
2 HashKey2 HashKey2 Key6 Key6
HashKey3 HashKey3 Key7 Key7
Seq Seq HashKey0 HashKey0
1
IV0 Mask1 HashKey1 HashKey1
3 IV1 IV0 HashKey2 HashKey2
(Zero) IV1 HashKey3 HashKey3
(Zero) (Zero) Seq Seq
(Zero) (Zero) IV0 Mask1
4 IV1 IV0
(Zero) IV1
(Zero) (Zero)
(Zero) (Zero)

1. For MACsec, MASK is an unsigned integer controlling a valid range of packet numbers.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 117

Functional Descriptions

Table 45 • Transform Record Format (XPN)

128 Bit AES Keys 256 Bit AES key

128 Bit block Egress Ingress Egress Ingress
0 CTRL Word CTRL Word CTRL Word CTRL Word
Context ID Context ID Context ID Context ID
Key0 Key0 Key0 Key0
Key1 Key1 Key1 Key1
1 Key2 Key2 Key2 Key2
Key3 Key3 Key3 Key3
HashKey0 HashKey0 Key4 Key4
HashKey1 HashKey1 Key5 Key5
2 HashKey2 HashKey2 Key6 Key6
HashKey3 HashKey3 Key7 Key7
Seq Low Seq Low HashKey0 HashKey0
Sec High Sec High HashKey1 HashKey1
3 DUMMY Sec Mask HashKey2 HashKey2
IS0 (Salt) IV0 (Salt) HashKey3 HashKey3
IS1 (Salt) IV1 (Salt) Seq Low Seq Low
IS2 (Salt) IV2 (Salt) Sec High Sec High
4 IV0 (SCI) DUMMY Sec Mask
IV1 (SCI) IS0 (Salt) IV0 (Salt)
IS1 (Salt) IV1 (Salt)
IS2 (Salt) IV2 (Salt)
5 IV0 (SCI)
IV1 (SCI)

All fields of the transform record must be populated by the host software before the corresponding SA
flow can be enabled. The ctx_size bit in the CONTEXT_CTRL register controls the size of the context
that must be fetched. For bypass and drop flows, the transform record is not used. The hardware only
updates the sequence number field; it does not modify the other fields during MACsec egress and
ingress processing.
The context control word is the first 32-bit word in each transform record. It specifies the type of
operation. Only those settings that are relevant for MACsec operations need to be defined. The following
table shows the fields in context control word.

Table 46 • Context Control Word Fields

Bits Name Description

3:0 ToP Type of packet
0110b: Egress
1111b: Ingress
All other values are invalid
4 Reserved Write with zero and ignore on read
5 IV0 First word of IV present in context (SCI for MACsec)
Must be set to 1b

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 118

Functional Descriptions

Table 46 • Context Control Word Fields (continued)

Bits Name Description

6 IV1 Second word of IV present in context (SCI for MACsec)
Must be set to 1b
7 IV2 Third word of IV present in context (use sequence number instead)
Must be set to 0b
12:8 Reserved Write with zero and ignore on read
13 Updated Seq Update sequence number
Must be set to 1b for MACsec
14 IV Format If set, use sequence number as part of IV
Must be set to 1b for MACsec
15 Encrypt Auth If set, encrypt ICV
Must be set to 1b for MACsec
16 Key Load crypto key from context
Must be set to 1b for MACsec
19:17 Crypto Algorithm Algorithm for data encryption
101b: AES CTR 128
111b: AES CTR 256
20 Reserved Write with zero and ignore on read
22:21 Digest Type Type of digest key
Only single digest key is supported, setting 10b
25:23 Auth Algorithm Algorithm for authentication
Only AES-GHASH is supported, setting 100b
27:26 AN The two-bit Association Number inserted in the SecTag for egress
operations
Must be kept 00b for ingress
29:28 Seq type Type of sequence number: only supported setting is 01b
Use 32-bit sequence number, on ingress use the mask as a replay
window size
30 Seq mask Sequence mask is present in context
0b: Egress
1b: Ingress
31 Context ID Context ID present: must be set to 1b

The following list shows the other fields of the transform record.
• Context ID
Unique identifier for each context. It is sufficient to give all transform records a different context ID,
possibly by assigning them a number from 0 to maximum index.
• Key 0 … Key 7
AES encryption key for the MACsec SA. Each word of the key is a 32-bit integer representing four
bytes of the key in little-endian order. The number of words depends on AES key length.
• H_Key 0, H_Key 1, H_Key 2, and H_Key 3
128-bit key for the authentication operation. It is represented in the same byte order as Key 0...Key
7. It is derived from Key 0...Key 7 as follows: H_key = E (Key, 128'h0). This means performing a
128/256 bit AES-ECB block encryption operation with Key 0...Key 7 as the key and a block of 128
zero bits as the plaintext input. The cipher-text result of the AES block encryption is the 128-bit
H_Key.
• Sequence Number
For egress MACsec, this is one less than the sequence number (PN) that is to be inserted into the
MACsec frame. For a new SA, this must be initialized to 0. After each egress packet, this field is

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 119

Functional Descriptions

incremented by 1. If it rolls over from 0xFFFFFFFF to 0, a sequence number error occurs and the
context is not updated, which means that the same error will occur again for any subsequent egress
packets with that context - the external system will forward these packets to the line with CRC/packet
error. For ingress MACsec, the sequence number must be initialized to 1.
• Mask (replay window size)
Window size for ingress sequence number checking. By default, it is 0 (strict ordering enforced). It
can be set to any integer value up to 232–1, in which case any nonzero sequence number is
accepted.
• SCI 0 and SCI 1
SCI that belongs to the specific MACsec SA. An SCI that depends on the source MAC address and
the ES and SCB bits is defined, even in modes that do not explicitly transmit or receive the SCI with
each packet. This is a 64-bit block, represented by two 32-bit integers in little-endian order. It is the
same byte order in which SAM_SCI_MATCH_HI/SAM_SCI_MATCH_LO represent an SCI.
When the sequence number of an egress SA is about to roll over, it must be replaced by a new SA with
different keys. It is not allowed to reset the sequence number of an egress SA to a lower value because
doing so generally leads to sequence number checking failures at the receiving end of the connection.
For inbound frames, the PN is compared against the sequence number (PN) from the context, resulting
in one of the following three cases:
• If the received number is above or equal to the number in the context:
{received_PN? next_PN}
In this case the context sequence number (PN) is updated (if the update_seq bit is set to 1b). The
updated value is the received number plus one.
• If the received number is below the number from the context, but within the replayWindow:
{received_PN < next_PN and received_PN ≥ (next_PN - replayWindow)
In this case no context update is required.
• If the received number is below the number from the context, and outside the replayWindow:
{received_PN < (next_PN - replayWindow)
In this case the sequence number check fails and error bit e10 is set in the result token. No context
update is done.

3.7.5.4.2 MACsec Crypto Engine Interrupt Control/Status Register

The INTR_CTRL_STATUS register provides control and status for interrupts within the MACsec crypto
engine only. The interrupt output pin controlled here is one of the inputs on the top-level Advanced
Interrupt Controller (controlled using the AIC registers).
The following main interrupts are given by the Crypto engine.
• Bit 4 Outbound Sequence Number Threshold
This interrupt is triggered if a sequence number exceeds the programmed sequence number
threshold (specified in SEQ_NUM_THRESH) due to an outbound sequence number increment.
• Bit 5 Outbound Sequence Number Roll-over
This interrupt is triggered if a sequence number rolls over (increment from maximum to zero) due to
an outbound sequence number increment.

3.7.5.5 Ingress Consistency Checking

Consistency checking is used to verify that MACsec ingress packets satisfy certain properties after
decryption. Packets are passed or dropped based on a set of rules. The number of rules is a fixed
hardware parameter. As opposed to the static classification and flow lookup stages, consistency
checking logic inspects the packet data after the MACsec transform.
Consistency checking logic contains a complete VLAN tag parser performing the same operations as the
VLAN tag parser located in the input packet classification logic. The configuration of the parser is
controlled by a separate set of registers (IG_CP_TAG, IG_PP_TAGS, IG_PP_TAGS2, and
IG_CP_TAG2) similar to the input packet VLAN tag parser. It extracts the payload Ethertype from the
second or third Ethertype location in the packet if that packet contains one and two VLAN tags,
respectively. The VLAN tag parser also extracts (and post-processes) the following fields:

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 120

Functional Descriptions

• User Priority field from the first VLAN tag it encounters, to be used by the MTU checking logic and
statistics counters update logic.
• VLAN ID and VLAN Up from the second VLAN tag in case of Q-in-Q.
Each consistency check rule can match on a set of mask-able match criteria. If the corresponding mask
bit is cleared, the match criterion is not checked and packets can satisfy the rule regardless of the value
in the packet. If the corresponding mask bit is set, a packet only satisfies the rule if the value in the packet
matches the value in the rule. The following list shows the mask-able match criteria.
• sai_hit (1b or 0b)- The packet was matched by one of the SA flows during flow lookup.
• sai_nr (range 0 to SAmax-1)- The packet was matched by the specific SA flow (or is not matched
by any SA flow and has a specific combination of control packet and MACsec tag classification). To
match packets that were matched by a specific SA flow, also match on sai_hit = 1
• vlan_valid (1b or 0b)- The packet contains a valid VLAN tag.
• vlan_id (12 bits value)- The packet has the specified VLAN ID. A match on this criterion is only
meaningful if also matched on vlan_valid = 1.
• vlan_id_inner (12 bits value)- The packet has the specified VLAN ID at second VLAN tag. A match
on this criterion is only meaningful if also matched on vlan_valid = 1 and Q-in-Q is detected.
• vlan_up_inner (3 bits value)- The packet has the specified VLAN Up at second VLAN tag. A match
on this criterion is only meaningful if also matched on vlan_valid = 1 and Q-in-Q is detected.
• etype_valid (1b or 0b)- The Ethertype is greater than cp_etype_max_len.
• payload_e_type (16 bits value)- The packet has a specific Ethertype if a VLAN packet is detected,
this value is the Ethertype following the VLAN tag.
• ctrl_packet (1b or 0b)- The packet is a control packet.
If all mask bits are cleared, the rule will match every possible packet.
Each of the consistency check rules can be enabled or disabled individually. If a rule is disabled, it will not
be selected for match checking. If more than one enabled rule is matched, the one with the highest
priority (3 bit number from 0 to 7) is picked. The lowest numbered rule is picked from equal priority rules.
The rule that is eventually selected specifies either a pass or a drop action.
If no rules match, the default action is taken (pass or drop). It is possible to define different default actions
for control and non-control packets. After reset, the default action for both of them is drop.
ICC rule configuration is controlled by the IG_CC_PARAMS and IG_CC_PARAMS2 registers.

3.7.5.6 Output Post-Processor

The final stage of the pipeline is the output post-processor. It implements the post-processing decision
tree that includes MACsec-compliant post-processing, as well as processing and MTU checking for non-
MACsec frames. It can drop the frame due to error conditions detected by the MACsec transform stage
(such as sequence number rollover and authentication failure), it checks for the correct combinations of
port numbers, it checks the frame length against the MTU, and it updates all statistics counters. For
ingress packets, the post-processor uses results of the consistency checking module's VLAN tag
detection logic instead of the VLAN parser in front of the MACsec crypto-engine.
The post-process statistics updating is done in accordance with the IEEE 802.1AE standard for secure
frame generation and secure frame verification management control and frame counters.

3.7.5.6.1 MTU Checking

Registers provide MTU limit values for VLAN tagged frames (per User Priority, as provided by the
consistency checking module) and one global MTU limit value for non-VLAN frames (detected by the
consistency checking module). The limits programmed are also used for statistics counters that rely on
an MTU value.
Ingress Frame MTU Checking
• The frame length is the size of the input frame (including header and excluding Ethernet preamble,
start-of-frame byte, and CRC).
• The VLAN User Priority is extracted from the VLAN tag as parsed (and post-processed) by the
VLAN tag parser implemented in the consistency checking logic.
Egress Frame MTU Checking

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 121

Functional Descriptions

• The frame length is the size of the output frame (including header and excluding Ethernet preamble,
start-of-frame byte, and CRC).
• The VLAN user priority is the one provided by the VLAN parsing logic in the static classification logic.
MTU checking is configured using the VLAN_MTU_CHECK and NON_VLAN_MTU_CHECK registers.

3.7.5.6.2 Statistics
The following two types of statistics counters are used.
• Per-frame counters are 40 bits wide. They overflow after about 1012 frames. A MACsec block
processing 10 Gbps traffic can process in the order of 107 frames per second so that the 40-bit
counters only saturate after 105 seconds (one day).
• Per-octet counters are 80 bits wide. They overflow after about 1024 octets. Even for a system that
processes in excess of 109 bytes per second, this means that they will never overflow during the
expected lifetime of the system.
The statistics counters can be configured to be auto-cleared on read. They can also be configured to
saturate at maximum value instead of rolling over.
There are three classes of statistics counters, as follows.
• Global Statistics- The MACsec block maintains global statistics counters to implement MACsec.
Some global statistics are maintained per-SA, so they must be obtained by accumulating (summing)
the per-SA statistics of the relevant SAs.
• Per-SA Statistics- The MACsec block maintains all per-SA statistics for ingress and egress
MACsec operations. Software maintains statistics for all four SAs that might belong to an SC. It
keeps the per-SA statistics, even for SAs that it has deleted from the SA flow table. When an SA flow
is deleted, its final SA statistics must be collected and added into the per-SA and per-SC statistics.
• Per-SC Statistics- The MACsec block does not maintain any per-SC statistics. However, the per-
SC statistics are the sum of per-SA statistics of the SAs belonging to that SC. Whenever the
software reads per-SA statistics from the hardware, it must not only add them to the per-SA statistics
administration, but to the per-SC statistics administration as well.
The following tables show the per SA (per SC), global (SecY), and per user priority egress statistics
generated. Eight sets of user priority counters are implemented. If a frame is detected as VLAN, it also
increments user priority counters in addition to per-SA/global (SecY) counters.

Table 47 • Egress SA Counters

Egress SA STAT Counters Size

sa.OutOctetsEncrypted/sa.OutOctetsProtected 80
sa.OutPktsEncrypted/sa.OutPktsProtected/sa.OutPktsHitDropReserved 40
sa.OutPktsTooLong (MTU check) 40
sa.ifOutBroadcast 40
sa.ifOutMulticast 40
sa.ifOutUnicast 40

Table 48 • Egress Global Counters

Egress Global Counters Size

global.TransformErrorPkts 80
global.OutPktsCtrl 80
global.OutPktsUnknownSA 40
global.OutOverSizePkts (MTU check) 40
global.ifOutBroadcast 40
global.ifOutMulticast 40

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 122

Functional Descriptions

Table 48 • Egress Global Counters (continued)

Egress Global Counters Size

global.ifOutUnicast 40
global.ifOutOctets 40

Table 49 • Egress Per-User Global Counters

Egress Global Counters Size

Vlan.OutOctetsUP 80
Vlan.OutPktsUP 40
Vlan.OutDroppedPktsUP 40
Vlan.OutOverSizePktsUP 40

The following tables show the per SA (per SC), global (SecY), and per user priority ingress statistics
generated. Eight sets of user priority counters are implemented. If a frame is detected as VLAN, it also
increments user priority counters in addition toper-SA/global (SecY) counters.

Table 50 • Ingress SA Counters

Ingress SA STAT Counters Size

sa.InOctetsDecrypted/sa.InOctetsValidated 80
sa.InPktsUnchecked/sa.InPktsHitDropReserved 40
sa.InPktsDelayed 40
sa.InPktsLate 40
sa.InPktsOk 40
sa.InPktsInvalid 40
sa.InPktsNotValid 40
sa.InPktsAuthFail1 40
sa.InPktsNotUsingSA 40
sa.InPktsUnusedSA 40
sa.InPktsSAMiss1 40
sa.InPktsUntaggedHit 40
sa.ifInBroadcast 40
sa.ifInMulticast 40
sa.ifInUnicast 40

1. Implemented indirectly. sa.InPktsAuthFail is reported in software by adding

sa.InPktsInvalid and sa.InPktsNotValid. sa.InPktsSAMiss is reported in software by
adding sa.InPktsNotUsingSA and sa.InPktsUnusedSA.

Table 51 • Ingress Global Counters

Ingress Global Counters Size

global.TransformErrorPkts 80
global.InPktsCtrl 80
global.InPktsNoTag 40

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 123

Functional Descriptions

Table 51 • Ingress Global Counters (continued)

Ingress Global Counters Size

global.InPktsUntagged 40
global.InPktsTagged 40
global.InPktsBadTag 40
global.InPktsUntaggedMiss 40
global.InPktsNoSCI 40
global.InPktsUnknownSCI 40
global.InPktsSCIMiss*
global.InConsistCheckControlledNotPass 40
global.InConsistCheckUncontrolledNotPass 40
global.InConsistCheckControlledPass 40
global.InConsistCheckUncontrolledPass 40
global.InOverSizePkts 40
global.ifInBroadcast 40
global.ifInMulticast 40
global.ifInUnicast 40
global.ifInOctets 40

Table 52 • Ingress Per-User Global Counters

Egress Global Counters Size

Vlan.OutOctetsUP 80
Vlan.OutPktsUP 40
Vlan.OutDroppedPktsUP 40
Vlan.OutOverSizePktsUP 40

3.7.5.7 Correlation with IEEE 802.1AE MACsec Statistics

The following table shows how the MACsec block statistics are derived from the MACsec standard.

Table 53 • IEEE 802.1AE Correlation

MACsec name (IEEE 802.1AE) Direction Type Microsemi MACsec register

Frame verification statistics (MACsec specification 10.7.9)
InPktsUntagged Ingress Global global.InPktsUntagged
InPktsNoTag Ingress Global global.InPktsNoTag
InPktsBadTag Ingress Global global.InPktsBadTag
InPktsUnknownSCI Ingress Global global.InPktsUnknownSCI
InPktsNoSCI Ingress Global global.InPktsNoSCI
InPktsOverrun Ingress Global Not implemented, condition
does not occur, report as zero.
InPktsUnchecked Ingress Per-SC sa.InPktsUnchecked
InPktsDelayed Ingress Per-SC sa.InPktsDelayed

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 124

Functional Descriptions

Table 53 • IEEE 802.1AE Correlation (continued)

MACsec name (IEEE 802.1AE) Direction Type Microsemi MACsec register

InPktsLate Ingress Per-SC sa.InPktsLate
InPktsOK Ingress Per-SC, per-SA sa.InPktsOK
InPktsInvalid Ingress Per-SC, per-SA sa.InPktsInvalid
InPktsNotValid Ingress Per-SC, per-SA sa.InPktsNotValid
InPktsNotUsingSA Ingress Per-SC, per-SA sa.InPktsNotUsingSA
InPktsUnusedSA Ingress Per-SC, per-SA sa.InPktsUnusedSA
Frame validation statistics (MACsec specification 10.7.10)
InOctetsValidated Ingress Global Accumulate over each ingress
SA with authentication only:
sa.InOctetsDecrypted/Validated
InOctetsDecrypted Ingress Global Accumulate over each ingress
SA with encryption:
sa.InOctetsDecrypted/Validated
Frame generation statistics (MACsec specification 10.7.18)
OutPktsUntagged Egress Global global.OutPktsUntagged
OutPktsTooLong Egress Global Accumulate over each egress
SA: sa.OutPktsTooLong
OutPktsProtected Egress Per-SC, per-SA sa.OutPktsEcnrypted/Protected
if the SA is authenticate only.
OutPktsEncrypted Egress Per-SC, per-SA sa.OutPktsEncrypted/Protected
if the SA uses encryption
Frame protection statistics (MACsec spec 10.7.19)
OutOctetsProtected Egress Global Accumulate over each egress
SA with authentication only:
sa.OutOctetsEncrypted/Protect
ed
OutOctetsEncrypted Egress Global Accumulate over each egress
SA with encryption:
sa.OutOctetsEncrypted/Protect
ed

3.7.5.8 Interrupts
The MACsec block can raise five interrupts from ingress and four from the egress block. The available
interrupts are as follows.

3.7.5.8.1 MACsec Crypto-Core Interrupt

Indicates several errors detected by the MACsec crypto engine block. The software must read the
INTR_CTRL_STATUS register of the MACsec crypto core to see which condition caused the interrupt.
The software must then write the same bits to INT_CTRL_STATUS to clear the interrupt condition, as
applicable.
• Input error (bit 0) may occur if the MACsec crypto core attempts to process certain malformed short
MACsec packets where the packet is shorter than indicated by the SL field.
• Output error and fatal error (bits 1 and 14) indicate a hardware error.
• Processing error (bit 2) may indicate a hardware error, but more likely the flow type in
SAM_FLOW_CTRL is inconsistent with the context control word in the transform record (MACsec
ingress versus MACsec egress).

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 125

Functional Descriptions

• Context error (bit 3) indicates an error in the transform record, probably the context control word,
especially the settings for encryption and authentication algorithms.
• Sequence number threshold (bit 4) indicates that an egress flow has exceeded its sequence number
threshold. The MACsec SA must be re-keyed to prevent a sequence number rollover. Exceeding the
sequence number threshold will not affect packet processing; it is meant to be used as a warning for
imminent sequence number rollover.
• Sequence number rollover (bit [5]) indicates that an egress flow has encountered a sequence
number rollover. The software must look in the transform record table to see which active egress SA
has a sequence number value of 0xFFFFFFFF in case of 32-bit Packet number or
0xFFFFFFFF_FFFFFFFF in case of 64-bit packet number. This egress SA flow must immediately be
disabled, and it must be re-keyed.
Use the following steps to make effective use of the sequence number threshold interrupt.
1. .Set the SEQ_NUM_THRESHOLD register to an appropriate value. A suitable value might be
0xF0000000 for a 32-bit packet number.
2. Make sure the sequence number threshold interrupt is enabled.
Use the following steps if the sequence number threshold interrupt occurs.
1. Temporarily disable the sequence number threshold interrupt, then clear that interrupt bit.
2. Check all transform records of active egress SAs for a sequence number that is either over the
threshold or close to it (any egress SA with a sequence number above 0xE0000000).
3. Start a re-keying procedure for all those SAs.
4. After re-keying has been completed (and new SAs are installed on both sides of the connection), re-
enable the sequence number threshold interrupt.

3.7.5.8.2 Classification Drop Interrupt

Raised when a packet is dropped by the flow lookup logic where either the SA flow or the non-matching
flow specifies a drop action.

3.7.5.8.3 Consistency Check Drop Interrupt (ingress only)

Raised when a packet is dropped by the ingress consistency checking logic.

3.7.5.8.4 Post-Processing Drop Interrupt

Raised when a packet is dropped by the post-processing stage for any other reason than MTU check
failure. Ingress packets with an ICV check failure or sequence number check failure raise this interrupt.

3.7.5.8.5 MTU Check Drop Interrupt

Raised when a packet is dropped due to MTU check failure.
Note: Frequent packet dropping may indicate an attack attempt, a configuration error, or a software
malfunction.

3.7.5.9 Updating the MACsec SA for Ingress

For synchronization purposes, the MACsec standard requires the lowestPN and the nextPN in an active
SA to be updated to a greater value provided by the KaY (unless it is not already reached). This is
achieved in the MACsec core by updating the sequence number in an active context to a greater value if
the sequence number in the context did not reach this value. The lowest acceptable PN is implicitly
updated assuming that the replay window size is not changed. The host must program next_pn_lower
(and next_pn_upper for XPN flow) to the desired sequence number, must specify the flow for which the
update should occur in next_pn_context_id register, and should enable the update in enable_update
register. MACsec core will clear this enable_update register once the transform record field is updated. If
the sequence number is already equal or above the configured value, then no internal update is
performed.

3.7.6 Debug Fault Code in FCS

Incrementing a counter for a packet may be a security failure in some cases. The
SA_SECFAIL_MASK/GLOBAL_SECFAIL_MASK register can be used to configure which counter
increments are regarded as security fail events. Debug functionality enables packets failing security
check to be transmitted with corrupted FCS, which consists of a debug fault code to debug the security

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 126

Functional Descriptions

failing packet. The FCS of a frame failing security check is corrupted on the output. The corrupted FCS
field contains a fault code for debugging using a frame analyzer. The fault code uses 31 bits, with the last
FCS bit reserved to make sure the FCS check fails.
The following table shows the FCS fault code for the 32 bits.

Table 54 • FCS Fault Codes

Bit Description
31 Reserved to make sure that FCS check fails
30 SA hit
29:24 SA pointer
If the SA-hit bit[30] is 0, then
bits[29:27] are reserved, bit[26] indicates if the frame is classified as control
frame, and bits[25:24] indicate the MACsec tag classification of the frame:
00b = untagged, 01b = tagged, 10b = bad tag, 11b = KaY tag
23:10 Global stat event vector
9:0 SA stat event vector

The following tables show the format of the ingress global and SA stat event vectors.

Table 55 • Ingress Global Stat Event Vector Format

Event Bit Position Ingress Global Counter

0 global.TransformErrorPkts
1 global.InPktsCtrl
2 global.InPktsNoTag
3 global.InPktsUntagged
4 global.InPktsTagged
5 global.InPktsBadTag
6 global.InPktsUntaggedMiss
7 global.InPktsNoSCI
8 global.InPktsUnknownSCI
9 global.InConsistCheckControlledNotPass
10 global.InConsistCheckUncontrolledNotPass
11 global.InConsistCheckControlledPass
12 global.InConsistCheckUncontrolledPass
13 global.InOverSizePkts
14 global.ifInUcastPkts
15 global.ifInMulticastPkts
16 global.ifInBroadcastPkts
17 global.ifInOctets

Table 56 • Ingress SA Stat Event Vector Format

Event Bit Position Ingress SA Stat Counter

0 sa.InOctetsDecrypted/InOctetsValidated

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 127

Functional Descriptions

Table 56 • Ingress SA Stat Event Vector Format (continued)

Event Bit Position Ingress SA Stat Counter

1 sa.InPktsUnchecked/InPktsHitDropReserved
2 sa.InPktsDelayed
3 sa.InPktsLate
4 sa.InPktsOk
5 sa.InPktsInvalid
6 sa.InPktsNotValid
7 sa.InPktsNotUsingSA
8 sa.InPktsUnusedSA
9 sa.InPktsUntaggedHit
10 sa.ifInUcastPkts
11 sa.ifInMulticastPkts
12 sa.ifInBroadcastPkts

The following tables show the format of the egress global and SA stat event vectors.

Table 57 • Egress Global Stat Event Vector Format

Event Bit Position Egress Global Counter

0 global.TransformErrorPkts
1 global.OutPktsCtrl
2 global.OutPktsUnknownSA
3 global.OutPktsUntagged
4 global.OutOverSizePkts (MTU check)
5 global.ifOutUcastPkts
6 global.ifOutMulticastPkts
7 global.ifOutBroadcastPkts
8 global.ifOutOctets
13:9 Reserved: zeroes

Table 58 • Egress SA Stat Event Vector Format

Event Bit Position Egress SA Stat Counter

0 sa.OutOctetsEncrypted/OutOctetsProtected
1 sa.OutPktsEncrypted/OutPktsProtected/OutPktsHitDropReserved
2 sa.OutPktsTooLong (MTU check)
3 sa.ifOutUcastPkts
4 sa.ifOutMulticastPkts
5 sa.ifOutBroadcastPkts
10:6 Reserved: zeroes

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 128

Functional Descriptions

3.7.7 Capture FIFO

A 512-byte capture FIFO can be used to capture up to first 504 bytes for packets failing any security
check. The security fail event can be used as a trigger. The FIFO can also be enabled to capture the first
packet of any given SA using the CAPT_DEBUG_TRIGGER_SA1/2 control. Multiple packets can also be
captured and the maximum size of the packet to be captured is configured using
CAPT_DEBUG_CTRL.MAX_PKT_SIZE. This FIFO can be programmed to capture frames from either
egress or ingress direction (CAPT_DEBUG_CTRL.SIDE). Frames are captured after MACsec
transformation. Software can view the FIFO as 32-bit wide and 128 deep. Each 32-bit location is
accessible to CSR using CAPT_DEBUG_DATA (0 to 127). Each packet is captured in the FIFO with a
64-bit administration header. The following illustration shows the layout of multiple packets in the capture
FIFO.
Figure 91 • Capture FIFO Layout
32-bit

ADM_HDR0

ADM_HDR1

PKT1

ADM_HDR0
128-deep ADM_HDR1

PKT2

Each stored packet is preceded by a 64-bit administration header that contains the following information.

3.7.7.1 ADM_HDR0
22 bits reserved, 1 bit truncated, 9 bit pkt_size

3.7.7.2 Truncated (1 bit)

Indicates the packet is truncated and only a part of the packet is captured. The captured packet could be
truncated because the packet could be bigger than the MAX_PKT_SIZE programmed by software to
capture.

3.7.7.3 Pkt_size (9 bits)

Indicates the size of the captured packet in bytes.

3.7.7.4 ADM_HDR1
32-bit security fail debug code, see section 4.4.1.
The status of the capture FIFO can be accessed using the CAPT_DEBUG_STATUS register
(PKT_COUNT, FULL, WR_PTR).
Use the following steps to capture frames.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 129

Functional Descriptions

1. Decide the SIDE and MAX_PKT_SIZE and program in CAPT_DEBUG_CTRL.

2. Enable the SA to capture the first packet. For enabling first packet capture on any SA, program
CAPT_DEBUG_TRIGGER_SA1/SA2 = 0xFFFFFFFF. To enable first packet capture on SA index
[0], program CAPT_DEBUG_TRIGGER_SA1 = 0x1
3. Enable the capture by programming CAPT_DEBUG_TRIGGER.ENABLE = 1.
4. Send frames.
5. Keep polling CAPT_DEBUG_STATUS to see if any frames have been captured (PKT_COUNT,
FULL, WR_PTR).
6. If PKT_COUNT > 0, then frames have been captured, read CAPT_DEBUG_TRIGGER_SA1/SA2 to
confirm if the packet for that SA has been captured. Bits will fall back to 0b automatically when a
packet is captured for the SA.
7. Stop the capture by programming CAPT_DEBUG_TRIGGER.ENABLE = 0 to enable software to
access the FIFO.
8. Read CAPT_DEBUG_DATA (0 to 127) to read the packet from the capture FIFO.

3.7.8 Flow Control Buffer

The following list provides an overview of the flow control buffer functionality in the VSC8491-17 device.
• Frame buffering in egress to handle frame expansion by MACsec and flow control back-pressure to
host/switch ASIC.
• Frame buffering in ingress to handle pause frame insertion (from host MAC) and rate adaptation.
• Cut-through mode of operation.
• Configurable pause reaction (including pause timer handling) for line received pause frames.
• Pause generation triggers to host MAC based on configurable XOFF/XON thresholds.
• Control queue and data queue with strict priority scheduling in egress with highest priority given to
control queue.
• Transmit MAC control frames irrespective of pause state.
• Rate adaptation between line and host clocks for PPM compensation.
• Rate difference between line and host clocks based on LAN/WAN modes.
• Flow control (back-pressure) feedback from MACsec block by compensating gap between frames.
• Pass link fault/LF/RF/LPI in both directions using special control word in-band with frames.
• EEE controller state machine for activating LPI and wake-up.
• 4X MTU buffering in egress.
• Ingress buffer for pause frame insertion by host MAC.
• ECC support in RAMs.
• Frame drops recorded for statistics.
• Sticky bits and interrupt.

3.7.8.1 Flow Control Handling

This section describes the basic flow control mode of operation. Buffering provided handles frame
expansion and its own latency. Buffering required for long interconnects that depend upon cable/fiber
length need to be provided separately. The following illustration shows the sequence of events when a
pause frame is received from line.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 130

Functional Descriptions

Figure 92 • Line Back-Pressure by Remote Link Partner

PHY with MACSec

FC Buffer
(Egress)
xMII
Host Line
1588 MACSec
4 MAC Rx MAC Tx
(Egress) (Egress)
(Egress) 2 (Egress) xMII
H L

Host/ OR
Switch/
MAC AND

Tx-XOFF Tx-XON

Host Line
1588 MACSec
3 MAC Tx MAC Rx
(Ingress) (Ingress)
xMII (Ingress) (Ingress) xMII
FC Buffer
(Ingress) 1

The following steps describe the sequence of events depicted in the illustration.
1. Pause frame (XOFF) is received by PHY at line MAC Rx. This frame is internally consumed by MAC.
The MAC Rx signals the Tx FC buffer with pause received indication and pause quanta.
2. The Tx FC buffer goes to pause state at the next frame boundary. Pause timer will be maintained by
Tx FC buffer and is started only after it goes to pause state, which may be immediate in some cases.
The Tx FC buffer drain rate is 0 and fill rate can be max port speed. The Tx FC buffer signals XOFF
to host MAC Tx to schedule a pause transmission upstream. This signaling is shown via the optional
OR gate. Without back-pressured from the remote link partner the Tx FC buffer uses XOFF/XON
thresholds to signal XOFF/XON to host MAC Tx to manage frame expansion due to MACsec.
3. The host MAC Tx can schedule a pause frame for transmission at the next frame boundary. The Tx
FC buffer needs to be able to hold at least one jumbo frame until XOFF pause is scheduled so that it
can continue to receive data downstream. The XOFF frame is then received by host/switch.
4. The host device can only stop transmission at next frame boundary because it may have started
transmitting a second jumbo frame.
The following configuration signals control the basic flow control mode.

3.7.8.1.1 PAUSE_REACT_ENA
Enables pause reaction and pause timer maintenance in egress flow control buffer. Set to 1.

3.7.8.1.2 PAUSE_GEN_ENA
Enables XON and XOFF pause frame signaling to host MAC based on XON and XOFF thresholds. Set
to 1.

3.7.8.1.3 INCLUDE_PAUSE_RCVD_IN_PAUSE_GEN
Enables the optional OR and AND gate. Set to 1. If not enabled, the pause gen signaling to host MAC is
purely based on XOFF/XON thresholds.
The following illustration shows the sequence of events when a pause frame is received from host.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 131

Functional Descriptions

Figure 93 • Host Back-Pressure by Remote Link Partner

PHY with MACSec

3
CRTL Queue

2 5
FC Buffer
(Egress)
xMII xMII
Host 4 Line
1588 MACSec
1 MAC Rx MAC Tx
(Egress) (Egress)
Host/ (Egress) (Egress)
Switch/
MAC

Host Line
1588 MACSec
MAC Tx MAC Rx
(Ingress) (Ingress)
xMII (Ingress) (Ingress) xMII
FC Buffer
(Ingress)

The following steps describe the sequence of events depicted in the illustration.
1. Host experiences congestion in ingress and sends pause (XOFF) to line.
2. Host MAC Rx receives pause frame. It is not enabled to react on received pause frames, so it
passes the pause frame to Tx FC buffer.
3. Tx FC buffer maintains two logical queues, one for data and one for MAC control frames. If a data
frame is already scheduled and in progress, it passes on MAC control frames at the next boundary
to quickly relay MAC control frames to line, despite the presence of other data frames in the data
queue.
4. Tx FC buffer transmits any or all control frames in the control queue.
5. Pause frame passes through the MACsec block. The MACsec egress block detects frame as a
control frame and does not encrypt it. Frame eventually passes through the line MAC Tx block and
the rest of the PHY blocks.
TX_CTRL_QUEUE_ENA determines if the control queue is enabled in the egress flow control buffer.
This should be set to 1 in basic flow control mode. The physical memory of egress FC buffer can be
partitioned between data and control queues using TX_CTRL_QUEUE_START/END and
TX_DATA_QUEUE_START/END configuration fields.

3.7.8.2 Advanced Flow Control Handling

The following illustration shows the sequence of events when the PHY is configured to the advanced flow
control mode of operation. PAUSE_GEN_ENA needs to be set to 1, and other configuration bits of FC
buffer (such as PAUSE_REAhT_ENA, INCLUDE_PAUSE_RCVD_IN_PAUSE_GEN and
TX_CTRL_QUEUE_ENA) need to be set to 0. All other configurations for this mode are part of line MAC
and host MAC.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 132

Functional Descriptions

Figure 94 • Advanced Flow Control Handling

Tx-XOFF/
XON PHY with MACSec

FC Buffer
xMII (Egress)
Host Line
1588 MACSec
4 MAC Rx MAC Tx
(Egress) (Egress)
(Egress) (Egress) xMII
H L
2

Host/ Pause
Switch/
MAC

Tx-XOFF Tx-XOFF Tx-XON

Host Line
1588 MACSec
3 MAC Tx MAC Rx
(Ingress) (Ingress)
xMII (Ingress) (Ingress) xMII
FC Buffer
(Ingress) 1

The following steps describe the sequence of events depicted in the illustration.

3.7.8.2.1 PHY Back-Pressured by Remote Link Partner

1. Pause frame (XOFF) is received by PHY at line MAC Rx. This frame is internally consumed by MAC.
Line MAC Rx signals line MAC Tx with pause received indication and pause quanta.
2. Line MAC Tx goes to pause state at the next frame boundary. Line MAC Tx stalls to pause the
pipeline. Pause timer maintained by line MAC Tx is started only after it goes to pause state. The Tx
FC buffer signals XOFF/XON to host MAC Tx based on XOFF/XON threshold.

3.7.8.2.2 Host Back-Pressuring Remote Link Partner

3. System pause is consumed by host MAC Rx. Pause timer maintained in host MAC Rx (instead of
Tx) for egress direction to generate XOFF/XON pause gen signal for line MAC Tx.
4. Line MAC Tx stalls to send pause frame (either XOFF or XON). This path will work irrespective of
whether line MAC is in pause state.

3.7.8.3 Frame Drop Statistics

The following 32-bit counters provide frame drop statistics. These counters roll over to 0 when the
maximum value is reached.

3.7.8.3.1 TX_CTRL_QUEUE_OVERFLOW_DROP_CNT
Number of control frame drops due to overflow in the control queue of the egress flow control buffer.

3.7.8.3.2 TX_CTRL_QUEUE_UNDERFLOW_DROP_CNT
Number of control frame drops due to underflow in the control queue of the egress flow control buffer.

3.7.8.3.3 TX_CTRL_UNCORRECTED_FRM_DROP_CNT
Number of control frames aborted due to ECC check fail during reading from RAM in egress flow control
buffer.

3.7.8.3.4 TX_DATA_QUEUE_OVERFLOW_DROP_CNT
Number of data frame drops due to overflow in the data queue of the egress flow control buffer.

3.7.8.3.5 TX_DATA_QUEUE_UNDERFLOW_DROP_CNT
Number of data frame drops due to underflow in the data queue of the egress flow control buffer.

3.7.8.3.6 TX_DATA_UNCORRECTED_FRM_DROP_CNT
Number of data frames aborted due to ECC check fail during reading from RAM in egress flow control
buffer.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 133

Functional Descriptions

3.7.8.3.7 RX_OVERFLOW_DROP_CNT
Number of frame drops due to overflow in the ingress flow control buffer.

3.7.8.3.8 RX_UNDERFLOW_DROP_CNT
Number of frame drops due to underflow in the ingress flow control buffer.

3.7.8.3.9 RX_UNCORRECTED_FRM_DROP_CNT
Number of frames aborted due to ECC check fail during reading from RAM in ingress flow control buffer.

3.7.9 Media Access Control

This section describes the media access control sub layer (MAC) block. There are two instances of MAC
block in each channel. One instance, which interfaces with MACsec and PCS/PMA, is called Line MAC,
and the other instance that interfaces with FC Buffer and PHY XS is called Host MAC.
The MAC is defined in IEEE 802.3 clauses 3 and 4. The purpose of the MAC is to control the MACsec
block access to the physical layer. In other words, it takes frames from the MACsec and converts those to
a continuous byte stream on the xMII interface. In doing so, it is responsible for frame CRC generation
and checking, preamble insertion and extraction, and pause frame generation and detection. The MAC
block also contains the counters for an SNMP management information base (MIB) statistics module.
The MAC block supports frame sizes up to 10240 bytes in both receive and transmit directions. The
maximum frame size is controlled by the host. The maximum frame size can also be set to the standard
1518 bytes or 1522 bytes, if desired. Maximum frame length restrictions are not enforced in the transmit
direction. The following illustration shows the block diagram of MAC.
Figure 95 • MAC Block Diagram
Rx Clock Domain MAC
mac_pause_frm

Early Pause
Detector

WRAPPER

KERNEL
Host I/ F to Packet Rx I /F
Packet I/F
Pause Converter Pause frame Indication
xMII Rx I /F Frame
RX-MAC Detector

LF/ RF Status CW
LPI Detect Generator

Pause State
Early Pause Detect

Packet Tx I/F
Packet /I F to
Host I/F Pause gen Signalling
Converter
MAC ready Indication
xMII Tx I /F Pause
TX- MAC Frame
Generator
Force
LF/ RF/ LPI
CW Detect

Tx Clock Domain

Configuration, Status, Counters( CSR)

Interface

3.7.9.1 MAC Transmit

The transmit section of the MAC contains three blocks, packet interface wrapper, pause frame generator,
and MAC Tx kernel. All three blocks operate off the same clock, TX_MAC_CLK.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 134

Functional Descriptions

The MAC Tx kernel block handles the reconciliation sublayer functions as per IEEE 802.3.
• Calculates the CRC for pause frames generated by the pause frame generator.
• Converts MAC frames to the xMII format and adds control characters for framing as required by
IEEE 802.3.
• Generates the interframe gap (IFG) on the xMII using the deficit idle count algorithm to achieve an
average IPG of 12 bytes.
• Shapes all the traffic to go out with an average IPG of 12 bytes after MACsec frame expansion.
• Analyzes each packet and increments statistical counters used for RMON support.
The Pause Frame Generator (PFG) block performs the following two major functions.
• Requests packets from the upstream blocks, when packets are present and the Tx direction is not in
the pause state (because a pause frame has been received in the Rx direction). They are forwarded
to the MAC Tx kernel block for further processing.
• Generates flow control packets. Pause frames are generated based upon seeing the
MAC_PAUSE_FRM_GEN signal. For the Host MAC, this signal is generated by the FC buffer based
upon programmable XOFF/XON threshold values in the FC buffer. In advance flow control mode of
operation, the line MAC can also generate pause frames based on MAC_PAUSE_FRM_GEN signal
from Host MAC to relay pause frames that are deleted in Host MAC in this mode.
When the pause frame generator sees the MAC_PAUSE_FRM_GEN signal asserted, it generates pause
frames using settings in configuration registers. Part of the pause frame is the pause value, which
specifies how long the link partner (the network entity that the pause frame is destined for) stops sending
traffic. The pause value specifies the requested delay in bit times and uses the equation 512 ×
PAUSE_VALUE.
After the PFG starts generating pause frames, it continues to generate pause frames at specified
intervals until the de-assertion of the MAC_PAUSE_FRM_GEN signal. When this signal is deasserted,
the PFG does one of two things, depending upon the configuration in MAC_TX_PAUSE_MODE. In
normal mode, the PFG stops sending pause frames. This causes the link partner to start sending frames
again after its pause frame timer has expired. In XON mode, the PFG generates a single pause frame
with a pause value of 0 and sends it to the link partner. This causes the link partner to start sending
frames again right away.
The PFG contains a configurable pause frame interval register, MAC_TX_PAUSE_INTERVAL. This
register controls the time between generated pause frames when the FC buffer continues to request that
pause frames be generated.
The packet interface wrapper handles the following functions:
• Provides the packet interfacing support to MACsec and FC buffer blocks. On this packet interface,
frames are transported without preamble and FCS.
• Supports LF/RF/LPI generation on xMII interface through special control word received on packet
interface. This special control word is received on packet interface if relaying of LF/RF/LPI is desired
in MACsec subsystem.
• Padding of frames whose length is less than 64 bytes. This is required for padding of MACsec short
length frames whose length is less than 64 bytes. This padding is enabled by configuring
ENABLE_TX_PADDING in host MAC.
• Standard preamble insertion.
• FCS insertion.

3.7.9.2 MAC Receive

The receive section of the MAC contains three blocks: MAC Rx kernel, pause frame detector, and packet
interface wrapper. All three blocks operate off the same clock, RX_MAC_CLK.
The MAC Rx kernel receives the byte stream from the xMII interface and handles the reconciliation sub
layer processing to convert them to frames sent over the host interface. It checks the CRC of each frame
for validity, and abort marks any frame with an invalid CRC. A variety of length checks are performed,
including looking for short frames (less than 64 bytes), oversized, and jabber frames (longer than the
configured maximum). VLAN tagging is supported up to three VLAN tags. Length checks are adjusted
accordingly when VLAN tags are encountered. The Rx kernel supports counters in support of RMON
statistics.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 135

Functional Descriptions

The pause frame detector (PFD) detects and reacts to valid pause frames received by the MAC from the
xMII interface. The PFD reacts to PAUSE frames with a DMAC equal to either the multicast address (01-
80-c2-00-00-01) or the address of the MAC (MAC_ADDRESS_LSB/MSB register value), in accordance
with IEEE 802.3-2008, Annex 31B. Pause frames that are too short, or have invalid CRC, are abort
marked and ignored by the PFD. Pause frames carry a pause value that indicates the desired pause time
in units of pause quanta, where 1 pause-quantum equals 512 bit times. Because the data path in the
MAC is 8 bytes (or 64 bits) wide, the extracted pause value is multiplied by 8 and stored in the pause
counter. A signal from the PFG indicates if a packet is currently being transmitted.
After the current packet has completed or if there is no packet, the PFD tells the PFG to stop requesting
packets (XOFF) and the pause counter is decremented by one for each MAC Rx clock cycle. When the
counter reaches 0, the PFG is instructed that it may resume requesting packets from the upstream
blocks. Pause frames must have a destination address equal to either the multicast address (01-80-c2-
00-00-01) or the address of the MAC (MAC_ADDRESS_LSB/MSB register value). If there is no match,
then the pause frame is ignored. If a pause frame is received while the Tx direction is already being
paused (because a valid pause frame was already received and the pause counter had not yet counted
down to 0), the pause counter is simply updated with the new value. If the received pause value is 0, then
the state machine transitions immediately to END_PAUSE and frames are again requested from the
upstream blocks.
The packet interface wrapper handles the following functions:
• Provides the packet interfacing support to MACsec and FC buffer blocks. On this packet interface,
frames are transported without preamble and FCS.
• Supports LF/RF/LPI indication on packet interface through special control word. This special control
word is relayed to other MAC if relaying of LF/RF/LPI is desired.
• Preamble strip on packet interface.
• FCS check and strip.

3.7.9.3 RMON Statistical Counters

The following counters count the number of bytes or frames received or transmitted. The counters count
continuously and are only cleared if the device is reset or the counter is written with 0 through the CPU
interface. These counters roll-over to 0 when the maximum value is reached. Unless specified otherwise,
each counter is 32 bits.
• RX_IN_BYTES_CNT (40 bits) counts the total bytes received including preamble
• RX_OK_BYTES_CNT (40 bits) counts the number of bytes received in valid frames
• RX_BAD_BYTES_CNT counts the number of bytes received in invalid frames
• TX_OUT_BYTES_CNT (40 bits) counts the total number of bytes transmitted including preamble
• TX_OK_BYTES_CNT (40 bits) counts the number of bytes in successfully transmitted frames
The following counters are based on the type of frame received or transmitted.
• RX_PAUSE_CNT counts the number of pause frames received
• RX_UNSUP_OPCODE_CNT counts the number of control frames received with unsupported
opcodes
• RX_UC_CNT counts the number of unicast frames received
• RX_MC_CNT counts the number of multicast frames received
• RX_BC_CNT counts the number of broadcast frames received
• TX_PAUSE_CNT counts the number of pause frames transmitted
• TX_UC_CNT counts the number of unicast frames transmitted
• TX_MC_CNT counts the number of multicast frames transmitted
• TX_BC_CNT counts the number of broadcast frames transmitted
The following error counters are provided.
• RX_SYMBOL_ERR_CNT counts the number of symbol errors received
• RX_CRC_ERR_CNT counts the number of frames received with CRC errors
• RX_UNDERSIZE_CNT counts the number of undersized frames received with valid CRC
• RX_FRAGMENTS_CNT counts the number of undersized frames received with invalid CRC
• RX_IN_RANGE_LENGTH_ERR_CNT counts the number of frames where the length field does not
match the frame length

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 136

Functional Descriptions

• RX_OUT_OF_RANGE_LENGTH_ERR_CNT counts the number of frames with an illegal length

field
• RX_OVERSIZE_CNT counts the number of oversize frames with valid CRC
• RX_JABBERS_CNT counts the number of oversize frames with an invalid CRC
• RX_XGMII_PROT_ERR_CNT counts the number of XGMII protocol errors detected.
The following size histogram counters are provided for both transmit and receive directions.
• Frames with 64-byte payloads
• Frames with 65-byte to 127-byte payloads
• Frames with 128-byte to 255-byte payloads
• Frames with 256-byte to 511-byte payloads
• Frames with 512-byte to 1023-byte payloads
• Frames with 1024-byte to 1518-byte payloads
• Frames with 1519-byte to maximum size payloads
Frame size counters also count invalid frames, as long as they are not short frames, fragments, long
frames, or jabber frames. Long frames are defined as those greater than MAX_LEN bytes.

3.8 Flow Control Buffers

Flow control buffers are used in the data paths when the MACs are enabled. Ethernet frames are stored
in the buffers. When a buffer is close to being full, the MAC will issue a pause frame to the device
sending data to the VSC8491-17 device. This is done to prevent the data path's flow control buffer from
overflowing.
The flow control feedback is particularly common for the host interface when in 10G WAN mode due to
the transmitted line WAN data rate being less than the received host LAN data rate. The feedback is also
necessary to address ethernet frame size expansion in the egress path when MACsec frame encryption
is enabled. For more information, see Flow Control Buffer, page 130.

3.9 Rate Compensating Buffers

Rate compensating buffers are used in the data paths when the MACs are disabled. The rate
compensating buffers add and drop idle characters between ethernet packets when necessary to
address clock rate differences between the line-side and host-side interfaces. Rate offsets from ideal
frequencies measured in ppm (not MHz) can be tolerated.
The maximum data throughput on the line interface is less in 10G WAN mode than 10G LAN mode. The
line's data rate is reduced to 9.953 Gbps from 10.3125 Gbps. Part of that bandwidth includes
SONET/SDH frame overhead data.
Note: Care must be taken by the device sending data to the host interface in the egress data path to ensure the
rate compensating buffer does not overflow.

3.10 Loopback
The VSC8491-17 device has several options available for routing traffic between the host-side and the
line-side. The following table shows the name and location of the loopback modes. These modes may be
extremely useful for both test and debug purposes.

Table 59 • Host-Side Loopbacks

Name Location Line-Side Tx Notes

H2 XAUI-PHY interface (1G and 10G) Mirror XAUI data
H3 PCS after the gearbox (10G) 0xFF00 repeating IEEE PCS system loopback
H4 WIS-PMA interface (10G) 0xFF00 repeating IEEE WIS system loopback

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 137

Functional Descriptions

Table 60 • Line-Side Loopbacks

Name Location Host-Side Tx Notes

L1 XAUI loopback (10G) Mirror SFP+ data IEEE PHY-XS network loopback ()
L2 XGMII interface (10G) Mirror SFP+ data
L3 PMA interface (1G and 10G) Mirror SFP+ data

The following illustration shows the host and line-side loopbacks.

Figure 96 • Host-Side and Line-Side Loopbacks

Host Line TXDOUT

Tx
XRX[3:0] XAUI 10G 1588 MACsec 10G PCS WIS PMA
XGXS
MAC MAC

L1 H2 L2 H3 H4 L3

Host Line TXDIN

Tx
XTX[3:0] XAUI 10G 1588 MACsec 10G PCS WIS PMA
XGXS
MAC MAC

3.11 Cross-Connect (Non-Hitless Operation)

The VSC8491-17 device features a cross-connect between the two adjacent ports to support protection-
switching applications and failover capabilities. It supports cross-connect and line broadcast (bridge and
select) to host-side between the two adjacent ports.
The VSC8491-17 device supports failover and SFI to XAUI broadcasting. The SFI data coming from
either XAUI of channel_0 or channel_1 can be routed to XAUI of channel_0 or XAUI of channel_1, or
broadcast to XAUI of both channel_0 and channel_1. Network traffic is also switchable between XAUI
channel 0 and 1.
For example, in normal operation, the XAUI of channel_0 is routed to SFI. If there is a problem at the
MAC interfacing to the XAUI of channel_0, re-route the SFI data to XAUI of channel_1. Broadcasting
from SFI to both XAUI ports enables the passing of traffic between XAUI of channel_0 and SFI, and to
use XAUI of channel_1 to snoop the incoming data from SFI, if so desired.
The following table lists the available settings for failover/broadcasting modes.

Table 61 • Failover and Broadcasting Modes

Setting Mode
1Ex0003 =0x00 XAUI channel_0 to/from SFI interface
XAUI channel_1 from SFI interface
1Ex0003 = 0x01 XAUI channel_0 from SFI interface
XAUI channel_1 to/from SFI interface
1Ex0003 =0x20 XAUI channel_0 to/from SFI interface
Datapath clock to channel_1 WIS, PCS
XAUI channel_1 output data is local faults
1Ex0003 =0x11 Datapath clock to channel_0 WIS, PCS
XAUI channel_0 output data is local faults
XAUI channel_1 data to/from SFI interface

The following illustration shows the cross-connect configurations.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 138

Functional Descriptions

Figure 97 • Cross-Connect Configuration

BROADCAST FROM SFI0 : Data_Switches_Clock_Control = 0x00 or 0x01

XRX0[3:0] /4 1 PMA
XAUI RX CORE TX TXDOUT0
0 TX

Channel 0

XTX0[3:0] /4 XAUI 1 PMA RX RXDIN0

CORE RX 0
TX

XAUI0_DOUT_SRC = 0
PMA_DOUT_SRC = 0 or 1

XRX1[3:0] /4
XAUI RX CORE TX

Channel 1

XTX1[3:0] /4 XAUI 1
CORE RX 0
TX

XAUI1_DOUT_SRC = 0

3.12 Host-Side Interface

The XAUI, RXAUI, and 1 GbE host interfaces in the VSC8491-17 device support the following rates:
• XAUI: 4 × 3.125 Gbps
• RXAUI: 2 × 6.25 Gbps
• 1 GbE: 1 × 1.25 Gbps
In RXAUI mode, the two RXAUI lanes are XAUI lane 0 and lane 2. XAUI lane 0 is the RXAUI lane 0 and
XAUI lane 2 is RXAUI lane 1. The LSB are sent on lane 0, while MSB are sent on late 1. In 1 GbE mode,
the 1 GbE lanes may be either XAUI lane 0 or lane 3. The following illustration shows the host-side I/O
interface.
The XAUI lane order could be swapped through register 4xF002, where bit 2 is to map lane 0 on 3, lane
1 on 2, lane 2 on 1, and lane 3 on 0 of the XAUI output. Bit 0 of same register is to map lane 0 on 3, lane
1 on 2, lane 2 on 1, and lane 3 on 0 of the XAUI input. Furthermore, bit 2 of 4xF002 could be used to
invert the polarity of the differential pairs of all four XAUI outputs, and bit 1 of 4xF002 could be used to
invert the polarity of the differential pairs of all four XAUI inputs. There is an API function call to assist
with setting the lane swap and polarity inversion.
Note: Use AC-coupling for the receive and transmit sides of the host-side interface. For optional DC-coupling,
contact your Microsemi representative.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 139

Functional Descriptions

Figure 98 • Host-Side I/O Interface

XAUI RXAUI 1 GbE

XRX_0 XRX_0 1G_RX NC

XRX_1 NC NC NC
XRX_2 XRX_1 NC NC

2x 6.25 Gbps

1x 1.25 Gbps

1x 1.25 Gbps
4x 3.125 Gbps

XRX_3 NC NC 1G_RX
OR
XTX_0 XTX_0 1G_TX NC
XTX_1 NC NC NC
XTX_2 XTX_1 NC NC
XTX_3 NC NC 1G_TX

3.12.1 RXAUI Interoperability

The RXAUI implementation is fully interoperable with the Dune network mode 1 and mode 2 RXAUI
specification, as summarized in the following table.

Table 62 • RXAUI Interoperability

Mode1 Mode2
De-interleaving uses XAUI ||A|| column
(align column).
Transmitter: No internal logic modification. Transmitter: Replaces some |K| code groups with
Two 10b characters are presented to one other code groups to allow receiver to perform
physical lane at a time. de-interleaving (comma replacement).
Receiver: Separates two characters in
double rate lane into two physical standard
rate lanes. Lane byte ordering block
ensures first |A| character mapped to first
logical lane and |A| column aligned for the
deskew block.
Obeys 6.25 Gbps disparity rules. Obeys 6.25 Gbps disparity rules.

A host-side SerDes macro (SD6G) is used by each XAUI lane. The SerDes macros are automatically
configured to send/receive the proper data rate when the host interface changes between the
XAUI/RXAUI/1 GbE modes. The appropriate lanes are also powered down when not in use. For
example, XAUI lanes 1 and 3 are powered down when the RXAUI interface is in use.

3.13 Clocking
The following sections describe the clocking functionality of the VSC8491-17 device.

3.13.1 PLL
The VSC8491-17 device includes two PLLs, one on the line-side and another on the host-side. The line-
side PLL uses either XREFCK or WREFCK as its reference clock. The host-side PLL uses XREFCK. The
following table shows the supported reference clock frequencies.

Table 63 • Supported Reference Clock Frequencies

Clock Applications Frequencies

XREFCK Mainly LAN mode 125 MHz and 156.25 MHz
WREFCK LAN or WAN mode Synchronous Ethernet 155.52 MHz and 161.13 MHz

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 140

Functional Descriptions

Table 63 • Supported Reference Clock Frequencies (continued)

Clock Applications Frequencies

SREFCK Synchronous Ethernet 125 MHz, 155.52 MHz, and 156.25 MHz

3.13.2 Reference Clock

The VSC8491-17 device uses three differential input CML level reference clocks: XREFCK, WREFCK,
and SREFCK. The XREFCK is required all the time and may be either 156.25 MHz or 125 MHz.
The VSC8491-17 device features an internal frequency synthesizer that enables operation in 10G
LAN/10G WAN/1G LAN modes using a single reference clock input (XREFCK). The host-side PLL is
always driven by XREFCK. It is recommended to have the line-side PLL be driven by XREFCK.
For backward compatibility with previous generation PHY chips, WREFCK may be used to drive the line-
side PLL. For Synchronous Ethernet applications with non-hitless XREFCK, SREFCK could be used to
drive the line-side PLL.
The XREFCK frequency has to be decided before power up, and is selected using the MODE1 and
MODE0 pins. The following table shows the MODE pin settings for the various XREFCK frequencies.

Table 64 • XREFCK Frequency Selection

MODE1 Pin MODE0 Pin XREFCK Frequency

0 0 156.25 MHz (default)
0 1 Reserved
1 0 125 MHz
1 1 Reserved

The following table shows the supported clock rates and modes.

Table 65 • Supported Clock Rates and Modes

Mode XREFCK WREFCK SREFCK Tx CMU REF Rx CMU REF

10.3125G LAN single ref 156.25 MHz XREFCK XREFCK
9.95328G WAN single ref 156.25 MHz XREFCK XREFCK
1.25G LAN single ref 156.25 MHz XREFCK XREFCK
10.3125G LAN single ref 125 MHz XREFCK XREFCK
9.95328G WAN single ref 125 MHz XREFCK XREFCK
1.25G LAN single ref 125 MHz XREFCK XREFCK
10.3125G Sync-E LAN single ref 156.25 MHz XREFCK XREFCK
(Hitless)
10.3125G Sync-E LAN dual ref 156.25 MHz 161.13 MHz SREFCK XREFCK
156.25 MHz 156.25 MHz SREFCK XREFCK
156.25 MHz 125 MHz SREFCK XREFCK
9.95328G Sync-E WAN single ref 156.25 MHz XREFCK XREFCK
(Hitless)
9.95328G Sync-E WAN dual ref 156.25 MHz 155.52 MHz SREFCK XREFCK
9.95328G Sync-E WAN dual ref 156.25 MHz 155.52 MHz WREFCK WREFCK
1.25G Sync-E LAN single ref 156.25 MHz XREFCK XREFCK
(Hitless)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 141

Functional Descriptions

Table 65 • Supported Clock Rates and Modes (continued)

Mode XREFCK WREFCK SREFCK Tx CMU REF Rx CMU REF

1.25G Sync-E LAN dual ref 156.25 MHz 125 MHz SREFCK XREFCK

3.13.3 Synchronous Ethernet Support

The VSC8491-17 device supports several synchronous Ethernet configurations for 1G and 10G modes
of operation. In synchronous Ethernet applications, only one master at a time may be selected from one
of the internal line-side Rx or the SREFCK.
• Single device, internal master: in this configuration, the line-side Rx captures the serial data input
and generates a lane-synchronization signal that contains information about the incoming data
rates. The signal is then distributed to all ports of the line-side Tx to form a source-synchronous
operation.
• Single clock LAN, external master: in this configuration, the XREFCK is gradually changed to the
externally generated synchronous Ethernet clock using an external clock distribution chip. The
change has to be hitless to avoid data corruption. The XREFCK source may come from one of the
port recovered clocks through the RXCKOUT pin.
• Dual clock LAN, external master: in this configuration, the XREFCK remains connected to the
stable 156.25 MHz system clock or crystal. All the line-side transmits are then synchronized to
SREFCK. The F to delta F block accepts the SREFCK clock from external synchronous Ethernet
master and generates the lane Sync signal to effectively synchronize all the line-side Tx to this
external clock. SREFCK must be 156.25 MHz.
• Dual clock WAN, external master: in this configuration, the XREFCK remains connected to the
stable 156.25 MHz system clock or crystal. The XREFCK is configured to drive the host-side PLL,
while the WREFCK is configured to drive the line-side PLL. The synchronous Ethernet clock is then
routed through the SREFCK clock to synchronize all the line-side transmits. SREFCK must be
155.52 MHz.

3.14 Operating Modes

The VSC8491-17 device has three main operation modes: LAN, WAN, and 1 GbE. Each mode may have
the 1588 and MACsec blocks on or off.

3.14.1 10G LAN with 1588 and MACsec

In 10G LAN mode with 1588 and MACsec, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI
(2 × 6.250 Gbps), and the line interface is LAN SFP+ (10.3125 Gbps). A single reference clock input pin,
XREFCK, is used by both the line-and host-side interfaces to transmit appropriate rates. For more
information about supported reference clock frequencies, see Table 65, page 141. MACs are part of the
data path when MACsec is enabled.
Figure 99 • 10G LAN with 1588 and MACsec

SerDes

SerDes Flow
Host Line 10G TXOUT
XRX[3:0] XGXS
MAC
Control 1588 MACsec
MAC PCS
SerDes
SerDes Buffer

SerDes

HOST LINE
XAUI/RXAUI SFP+/KR
XAUI: 4x 3.125 Gbps LAN: 10.3125 Gbps
RXAUI: 2x 6.25 Gbps (Ln0 and Ln2)

SerDes

SerDes Flow
Host Line 10G RXIN
XTX[3:0] XGXS
MAC
Control 1588 MACsec
MAC PCS
SerDes
SerDes Buffer

SerDes

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 142

Functional Descriptions

3.14.2 10G LAN with 1588

In 10G LAN mode with 1588, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI (2 × 6.250 Gbps),
and the line interface is LAN SFP+ (10.3125 Gbps). A single reference clock input pin, XREFCK, is used
by both the line-and host-side interfaces to transmit appropriate rates. For more information about
supported reference clock frequencies, see Table 65, page 141. Because the MACsec block is off, the
rate compensation is done in the FIFO.
Figure 100 • 10G LAN with 1588

SerDes

SerDes 10G
XRX[3:0] XGXS FIFO 1588 SerDes TXOUT
PCS
SerDes

SerDes

HOST LINE
XAUI/RXAUI SFP+/KR
XAUI: 4x 3.125 Gbps LAN: 10.3125 Gbps
RXAUI: 2x 6.25 Gbps (Ln0 and Ln2)

SerDes

SerDes 10G
XTX[3:0] XGXS FIFO 1588 SerDes TXIN
PCS
SerDes

SerDes

3.14.3 10G LAN

In 10G LAN mode, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI (2 × 6.250 Gbps), and the line
interface is LAN SFP+ (10.3125 Gbps). A single reference clock input pin, XREFCK, is used by both the
line-and host-side interfaces to transmit appropriate rates. For more information about supported
reference clock frequencies, Table 65, page 141. Because the MACsec block is off, the rate
compensation is done in the FIFO.
Figure 101 • 10G LAN

SerDes

SerDes 10G
XR X [3 :0] XGXS FIFO SerDes TXOUT
PCS
SerDes

SerDes

HO ST LIN E
XAUI /R XAUI SFP+ /K R
XAUI : 4 x 3 .125 Gbps LAN : 10 .3125 Gbps
R XAUI : 2x 6.25 Gbps (Ln 0 and Ln2 )

SerDes

SerDes 10G
XTX [3:0 ] XGXS FIFO SerDes TXIN
PCS
SerDes

SerDes

3.14.4 10G WAN with 1588 and MACsec

In 10G WAN mode with 1588 and MACsec, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI
(2 × 6.250 Gbps), and the line interface is SONET/SDH STS-192c (9.95328 Gbps). A single reference
clock input pin, XREFCK, is used by both the line-and host-side interfaces to transmit appropriate rates.
For more information about supported reference clock frequencies, see Table 65, page 141. Optionally,
WREFCK may be used as the 155.52 MHz reference clock for the line interface. A 622 MHz WREFCK
reference frequency is not supported. MACs are part of the data path when MACsec is enabled.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 143

Functional Descriptions

Figure 102 • 10G WAN with 1588 and MACsec

SerDes

SerDes Flow
Host Line 10G
XRX[3:0] XGXS Control 1588 MACsec WIS SerDes TXOUT
MAC MAC PCS
SerDes Buffer

SerDes

HOST LINE
XAUI/RXAUI SONET/SDH STS-192c

XAUI: 4x 3.125 Gbps WAN: 9.95328 Gbps

RXAUI: 2x 6.25 Gbps (Ln0 and Ln2)

SerDes

SerDes Flow
Host Line 10G RXIN
XTX[3:0] XGXS
MAC
Control 1588 MACsec
MAC PCS
WIS SerDes
SerDes Buffer

SerDes

3.14.5 10G WAN with 1588

In 10G WAN mode with 1588, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI (2 × 6.250 Gbps),
and the line interface is SONET/SDH STS-192c (9.95328 Gbps). A single reference clock input pin,
XREFCK, is used by both the line-and host-side interfaces to transmit appropriate rates. For more
information about supported reference clock frequencies, see Table 65, page 141. Optionally, WREFCK
may be used as the 155.52 MHz reference clock for the line interface. A 622 MHz WREFCK reference
frequency is not supported. Because the MACsec block is off, the rate compensation is done in the FIFO.
Figure 103 • 10G WAN with 1588

SerDes

SerDes 10G
XRX[3:0] XGXS FIFO 1588 WIS SerDes TXOUT
PCS
SerDes

SerDes

HOST LINE
XAUI/RXAUI SONET/SDH STS-192c

XAUI: 4x 3.125 Gbps WAN: 9.95328 Gbps

RXAUI: 2x 6.25 Gbps (Ln0 and Ln2)

SerDes

SerDes 10G
XTX[3:0] XGXS FIFO 1588 WIS SerDes RXIN
PCS
SerDes

SerDes

3.14.6 10G WAN

In 10G WAN mode, the host interface is XAUI (4 × 3.125 Gbps) or RXAUI (2 × 6.250 Gbps), and the line
interface is SONET/SDH STS-192c (9.95328 Gbps). A single reference clock input pin, XREFCK, is
used by both the line-and host-side interfaces to transmit appropriate rates. For more information about
supported reference clock frequencies, see Table 65, page 141. Optionally, WREFCK may be used as
the 155.52 MHz reference clock for the line interface. A 622 MHz WREFCK reference frequency is not
supported. Because the MACsec block is off, the rate compensation is done in the FIFO.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 144

Functional Descriptions

Figure 104 • 10G WAN

SerDes

SerDes 10G
XRX[3:0] XGXS FIFO WIS SerDes TXOUT
PCS
SerDes

SerDes

HOST LINE
XAUI /RXAUI SONET/SDH STS -192c
XAUI: 4x 3.125 Gbps WAN: 9.95328 Gbps
RXAUI: 2x 6.25 Gbps (Ln0 and Ln2)

SerDes

SerDes 10G
XTX[3:0] XGXS FIFO WIS SerDes RXIN
PCS
SerDes

SerDes

3.14.7 1 GbE with 1588 and MACsec

In 1 GbE mode with 1588 and MACsec, one XAUI lane on the host interface services the 1 GbE signal
(1.25 Gbps). A single reference clock input pin, XREFCK, is used by both the line-and host-side
interfaces to transmit appropriate rates. For more information about supported reference clock
frequencies, see Table 65, page 141. MACs are part of the data path when MACsec is enabled.
Figure 105 • 1 GbE with 1588 and MACsec

XRX[3] Flow
Host Line
or SerDes 1G PCS Control 1588 MACsec 1G PCS SerDes TXOUT
MAC MAC
XRX[0] Buffer

HOST LINE
1 GbE SFP

1G/SGMII 1.25 Gbps 1G/SGMII 1.25 Gbps

XTX[3] Flow
Host Line RXIN
or SerDes 1G PCS Control 1588 MACsec 1G PCS SerDes
MAC MAC
XTX[0] Buffer

3.14.8 1 GbE with 1588 and MACs

In 1 GbE mode with 1588 and MACs, one XAUI lane on the host interface services the 1 GbE signal
(1.25 Gbps). A single reference clock input pin, XREFCK, is used by both the line-and host-side
interfaces to transmit appropriate rates. For more information about supported reference clock
frequencies, see Table 65, page 141. MACs should be enabled to meet the pause turn around time spec,
as defined in the IEEE specifications.
Figure 106 • 1 GbE with 1588 and MACs

XRX[3] Flow
or Host Line
SerDes 1G PCS Control 1588 1G PCS SerDes TXOUT
MAC MAC
XRX[0] Buffer

HOST LINE
1 GbE SFP
1G/SGMII 1.25 Gbps 1G/SGMII 1.25 Gbps

XTX[3] Flow
Host Line TXIN
or SerDes 1G PCS Control 1588 1G PCS SerDes
MAC MAC
XTX[0] Buffer

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 145

Functional Descriptions

3.14.9 1 GbE
In 1 GbE mode, one XAUI lane on the host interface services the 1 GbE signal (1.25 Gbps). A single
reference clock input pin, XREFCK, is used by both the line-and host-side interfaces to transmit
appropriate rates. For more information about supported reference clock frequencies, see Table 65,
page 141. MACs should be enabled to meet the pause turn around time spec, as defined in the IEEE
specifications.
Figure 107 • 1 GbE

XRX[3] Flow
Host Line
or SerDes 1G PCS Control 1G PCS SerDes TXOUT
MAC MAC
XRX[0] Buffer

HOST LINE
1 GbE SFP

1G/SGMII 1.25 Gbps 1G/SGMII 1.25 Gbps

XTX[3] Flow
Host Line TXIN
or SerDes 1G PCS Control 1G PCS SerDes
MAC MAC
XTX[0] Buffer

3.15 Management Interfaces

This section contains information about the low-speed serial interfaces of the VSC8491-17 device. The
primary control and monitor interfaces in the design are as follows:
• MDIO
• SPI slave
• Two-wire serial (slave)
• Two-wire serial (master)
• Push out SPI master for IEEE 1588 time stamp data
• GPIO
• JTAG
The VSC8491-17 device supports three different interfaces for accessing status and configuration
registers: MDIO, SPI slave, and two-wire serial slave. Only one of the interfaces can be active at a time.
The VSC8491-17 device doesn't arbitrate between these interfaces.
Note: Users must exercise caution, and ensure that multiple interfaces are not active at the same time. The SPI
slave interface is the recommended interface for accessing the status and configuration registers of the
1588 block, the IEEE 1588 time stamp data, and the MACsec key and classification updates.

3.15.1 MDIO Interface

The MDIO interface in the VSC8491-17 device complies with IEEE 802.3ae Clause 45. For more
information, see the IEEE standard. The MDIO management interface consists of a bi-directional data
path (MDIO) and a clock reference (MDC).
MDIO instructions can be used to read registers, write registers, and perform
post-read-increment-address instructions. Due to its slow bandwidth and high latency, the MDIO
interface is not recommended as the only interface to access the VSC8491-17 device.
Note: The maximum data rate of the MDIO interface is 2.5 Mbps.
The PADDR[4:1] pins select the MDIO port addresses to which the VSC8491-17 device will respond. A
single VSC8491-17 device requires the use of two MDIO port addresses, one for each channel. The port
address transmitted in MDIO read/write commands to access registers in a particular VSC8491-17
channel is shown in the following table. The port address is a function of the PADDR pins and a

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 146

Functional Descriptions

pre-programmed number indicating the channel number. Up to sixteen VSC8491-17 devices can be
controlled by a single MDIO host.

Table 66 • MDIO Port Addresses Per Channel

Channel Number Channel’s Port Address

1 {PADDR[4:1], 1}
0 {PADDR[4:1], 0}

3.15.1.1 Accessing 32-Bit Data Registers

Even though the MDIO interface is defined to access 16-bit data registers, 32-bit configuration and status
registers are present in the line and host MACs, MACsec, 1588, and line-side SerDes. Use the following
steps when accessing registers in 32-bit blocks.

3.15.1.1.1 Write to 32-Bit Register

1. Issue address instruction specifying the MDIO address for bits [31:16].
2. Issue write instruction to write data to register bits [31:16].
3. Issue address instruction specifying the MDIO address for bits [15:0].
4. Issue write instruction to write data to register bits [15:0].
Note: Writing to the two halves of the 32-bit register in the opposite order is not permitted. Nor is it possible to
write to only one-half of the register. All four MDIO instructions must be issued to write to a 32-bit
register.

3.15.1.1.2 Read 32-Bit Register

1. Issue address instruction specifying the MDIO address for bits [15:0].
2. Issue read-increment instruction. The data read is the contents of register bits [15:0].
3. Issue read instruction. The data read is the contents of register bits [31:16].
Note: Perform all three steps to read a 32-bit register even when reading consecutive addresses. Issuing back-
to-back read-increment instructions to read consecutive 32-bit register addresses is not supported.
Register addresses listed for the line and host MACs, MACsec, 1588, and line-side SerDes apply to the
SPI slave and two-wire serial slave interfaces, which support direct access to 32-bit data registers. There
are two MDIO addresses for each of these 32-bit data registers: one address to access data bits [31:16]
and one address to access data bits [15:0]. Contact Microsemi for support using the MDIO interface to
access line and host MACs, MACsec, 1588, and line-side SerDes registers.

3.15.1.2 MDIO Device and Register Addresses

The VSC8491-17 device registers are arranged according to the MDIO devices as defined in IEEE 802.3
clause 45, as shown in the following list:
• Device 1: PMA and line-side interface registers
• Device 2: WIS registers
• Device 3: 10G PCS, 1G PCS, FC buffers, line MAC, and host MAC registers
• Device 4: XGXS PCS and host-side interface registers
• Device 1E: Global, SFP+, PLLs, and 1588 registers
• Device 1F: MACsec registers

3.15.2 SPI Slave Interface

The VSC8491-17 device supports the serial parallel interface (SPI) for reading and writing registers for
high bandwidth tasks such as reading IEEE 1588 time stamp data and performing MACsec key and
classification updates for all secure associations (SAs) in a timely manner. The SPI interface is also
capable of accessing all status and configuration registers. The SPI slave port consists of a clock input
(SCK), data input (MOSI), data output (MISO), and slave select input (SSN).
Note: The SPI slave interface is the recommended interface to access status and configuration registers for the
rest of the device.
Drive the SSN pin low to enable the interface. The interface is disabled when SSN is high and MISO is
placed into a high impedance state. The VSC8491-17 device captures the state of the MOSI pin on the
rising edge of SCK. 56 data bits are captured on the MOSI pin and transmitted on the MISO pin for each

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 147

Functional Descriptions

SPI instruction. The serial data bits consist of 1 read/write command bit, 23 address bits and 32 register
data bits.
The 23-bit addressing scheme consists of a 2-bit channel number, a 5-bit MDIO device number, and a
16-bit register number. For example, the 23-bit register address for accessing the
GPIO_0_Config_Status register in channel 1 (device number is 0x1E and register number is 0x0100) is
0x3E0100. The notion of device number conforms to MDIO register groupings. For example, device 2 is
assigned to WIS registers.
The following table shows the order in which the bits are transferred on the interface. Bit 55 is transferred
first, and bit 0 is transferred last. This sequence applies to both the MOSI and MISO pins.

Table 67 • SPI Slave Instruction Bit Sequence

Bit Name Description

55 Read/Write 0: Read
1: Write
54:53 Port/Channel Number 00: Port/Channel 0
01: Port/Channel 1
10, 11: Reserved
52:48 Device Number 5 bit device number
Bit 4 corresponds to SPI instruction bit 52
Bit 0 corresponds to SPI instruction bit 48
47:32 Register Number 16 bit register number
Bit 15 corresponds to SPI instruction bit 47
Bit 0 corresponds to SPI instruction bit 32
31:0 Data 32 bit data
Bit 31 corresponds to SPI instruction bit 31
Bit 0 corresponds to SPI instruction bit 0

The register data received on the MOSI pin during a write operation is the data value to be written to a
VSC8491-17 register. Register data received on the MOSI pin during a read operation is not used, but
must still be delivered to the device.
The VSC8491-17 device SPI slave has a pipelined read process. Two read instructions must be sent to
read a single register. The first read instruction identifies the register address to be read. The MISO data
transmitted on the second read instruction contains the register contents from the address specified in
the first instruction. While a pipelined read implementation is not the most efficient use of bandwidth to
read a single register, it is very efficient when performing multiple back-to-back reads (as would be the
case when reading 1588's TSFIFO_* registers). The second read instruction contains the address for the
second register to be read, plus the data read from the first register. The third read instruction contains
the address for the third register to be read, plus the data read from the second register. Register reads
can continue in this fashion indefinitely. The following illustrations show the situations where back-to-
back read instructions are issued.
Figure 108 • SPI Single Register Read

(Don t (Don t
MOSI R ADDR A R ADDR B
care) care)

Depends on previous Read

MISO R ADDR A
instruction DATA A

SPI Read
SPI Read
Instruction
Instruction #2
#1

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 148

Functional Descriptions

Figure 109 • SPI Multiple Register Reads

(Dont (Dont (Dont (Dont
MOSI R ADDR A R ADDR B R ADDR C R ADDR D
care) care) care) care)

Depends on previous Read Read Read

MISO R ADDR A R ADDR B R ADDR C
instruction DATA A DATA B DATA C

The SPI read instruction illustrations also point out the read/write state and address bits on the MISO
output match the information received in the previous instruction. The SPI master could use this data to
verify the device captured the previous instruction properly, or simply ignore the data. The following
illustration shows the MISO output during write instructions reporting the previous instruction's read/write
state, address, and register write data.
Figure 110 • SPI Multiple Register Writes
Write Write Write
MOSI W ADDR A W ADDR B W ADDR C
DATA A DATA B DATA C

Depends on previous Write Write

MISO W ADDR A W ADDR B
instruction DATA A DATA B

The following illustration shows that when a read instruction followings a write instruction, the MISO data
during the read instruction is the data field from the previous write.
Figure 111 • SPI Read Following Write
Write Write (Don t
MOSI W ADDR A W ADDR B R ADDR C
DATA A DATA B care)

Depends on previous Write Write

MISO W ADDR A W ADDR B
instruction DATA A DATA B

The following illustration shows that when a write instruction followings a read instruction, the MISO data
during the write instruction is not pipelined read data. MISO contains all 0's in the data field.
Figure 112 • SPI Write Following Read
(Don t (Don t Write
MOSI R ADDR A R ADDR B W ADDR C
care) care) DATA C

Depends on previous Read

MISO R ADDR A R ADDR B 0's
instruction DATA A

Some VSC8491-17 registers are made up of less than 32 data bits. Any bits not defined for a register will
return a 0 when the register is read. Reading an invalid register address will return 0x0.
There is one hazard condition to be aware of when issuing two read instructions to read a single clear-
on-read register. Issuing two read instructions internally fetches data twice, even though valid read data
is present only in the second instruction. Fetching data also resets a clear-on-read register. The address
specified in the second read instruction should be something other than the clear-on-read register
address. This prevents an event causing register re-assertion occurring between the two read
instructions from being cleared and never detected. The address in the second instruction can be any
register not having a clear-on-read function. Device_ID is one example. The same address can be used
in each read instruction when continuously polling a clear-on-read register. This works because
subsequently fetched data is transmitted from the interface, allowing assertion between reads to be
detected. Only the last read instruction where fetched data is not transmitted, should some other address
in the instruction be used.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 149

Functional Descriptions

3.15.2.1 MISO Output Timing Modes

MISO changes state when SCK transitions from high to low in the default SPI operating mode. This aids
in meeting hold time at the SPI master, assuming the master captures the data on the rising SCK edge.
The SPI port can run up to a maximum of 30 Mbps, depending upon the VSC8491-17 device SCK-to-
MISO timing, SCK duty cycle, the board layout, and the external SPI master's interface timing
requirements. For more information about SPI timing, see Table 93, page 171.
The SPI slave port has an alternate operating mode that allows the interface to run faster. Setting register
bit SPI_CTRL.FAST_MODE=1 configures the SPI slave such that MISO changes state when SCK
transitions from low to high. Thus, data is both transmitted from the SPI slave and captured by the SPI
master on a rising SCK edge. The interface can run faster in this mode by using the entire SCK clock
period instead of half the period to transfer data from the slave to the master. Care must be taken to
ensure the SPI master's hold time requirement is met. The maximum data transfer rate for the SPI slave
in this mode is 30 Mbps. The following illustrations show MISO timing in the default and slave modes.
Figure 113 • SPI Slave Default Mode
SSN

MOSI R/W ADDR[22] ... ADDR[0] DATA[31] ... DATA[1] DATA[0]

SCK ... ...

MISO R/W ADDR[22] ADDR[21] ... DATA[31] DATA[30] ... DATA[0] R/W

MISO data based on previous

instruction

R/W data matches this instruction and carries over to next instruction

Figure 114 • SPI Slave Fast Mode

SSN

MOSI R/W ADDR[22] ... ADDR[0] DATA[31] ... DATA[1] DATA[0]

SCK ... ...

MISO R/W ADDR[22] ADDR[21] ... DATA[31] DATA[30] ... DATA[0] R/W

MISO data based on previous

instruction

R/W data matches this instruction and carries over to next instruction

MISO output timing is the only difference between the two SPI modes. Sampling of MOSI on the rising
SCK clock edge remains the same, so writing to the VSC8491-17 device registers is identical in both
modes. Thus, the SPI_CTRL.FAST_MODE register setting may be modified using the SPI slave port to
change the port's MISO output timing.

3.15.3 Two-Wire Serial (Slave) Interface

The VSC8491-17 device registers may be read and written using a two-wire serial slave interface. The
two-wire serial slave SCL and SDA pins are multifunction general purpose I/O (GPIO) pins, GPIO_3 and
GPIO_2, respectively. The GPIO pins are configured to serve SCL and SDA functions following device
reset.
The slave address assigned to the VSC8491-17 device is a function of four fixed values and the MDIO
port address pins. The 7-bit slave address is {1000, PADDR4, PADDR3, PADDR2}. The use of the port
address pins allows multiple VSC8491-17 devices to be serviced by a single two-wire serial (master).
The maximum data transfer rate for the interface is 400 kbps.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 150

Functional Descriptions

Note: The two-wire serial slave interface does not work with two-wire serial masters using 10-bit slave
addresses.
A valid START condition is generated by a two-wire serial master device by transitioning the SDA line
from high to low while the SCL line is high. Data is then transferred on the SDA line, most significant bit
(MSB) first, with the SCL line clocking data. Data transitions during SCL low periods are valid (read) or
latched (write) when SCL pulses high then low. Data transfers are acknowledged (ACK) by the receiving
device for data writes and by the master for data reads. An acknowledge is signaled by holding the SDA
signal low while pulsing SCL high then low. The master terminates data transfer by generating a STOP
condition by transitioning SDA low to high while SCL is high.
Note: If the external two-wire serial master device gets out of sync with the two-wire serial slave interface, the
master device must issue a bus reset sequence. This puts the two-wire serial slave interface back into a
state that allows it to receive future two-wire serial instructions. The external two-wire serial master
device and the two-wire serial slave interface can become out-of-sync and freeze the bus if either device
is reset during an instruction.
The following illustration shows a two-wire serial bus reset sequence. The reset sequence consists of a
START symbol, nine SCK clock pulses while SDA is high, another START symbol, and a STOP symbol.
Figure 115 • Two-Wire Serial Bus Reset Sequence

Nine Clock Pulse

START START STOP

1 2 8 9
SCL

SDA

Registers in the VSC8491-17 device are accessed using the 24-bit addressing scheme. The first 8 bits
consist of one logic LOW, the channel number (00, 01, 10, 11), and the 5-bit MDIO device number of the
register to be accessed. The next 16 bits are the register number. For example, the 24-bit register
address for accessing the GPIO_0_Config_Status register in channel 1 (device number 0x1E and
register number 0x0100) is 0x3E0100. The notion of device number conforms to MDIO register
groupings. For example, device 2 is assigned to WIS registers. The following illustration shows the 24-bit
addressing scheme used to access registers.
Figure 116 • Two-Wire Serial Slave Register Address Format

S slv_addr[6:0], W “0”, ch[1:0], dev[4:0] reg_addr[15:8] reg_addr[7:0]

An illegal two-wire serial slave read instruction to an invalid channel number, device number, or register
address will return a read value of 0x0000 when the slave address matches this device.
Four bytes of data are transferred on the two-wire serial bus after the address when a register is read or
written. Data register bits [31:24] are transferred first, followed by bits [23:16], bits [15:8] and finally bits
[7:0]. An ACK symbol is sent between each byte of data. Any bits not defined in a register will return a 0
when the register is read.
The following illustration shows the data transferred on the SDA pin during a register write operation. The
R/W bit following the slave address is set to logic low to specify a write operation.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 151

Functional Descriptions

Figure 117 • Two-Wire Serial Write Instruction

S W
T R
A I Register Address
R T
T Slave Address E

1 0 0 0 0 0

R A A A A
/ C C C C
W K K K K

S
T
O
P

B A A A B A
I C C C I C
T K K K T K

3 0
1

Data Written to Register

The register address to be accessed is specified by initiating a write operation. After the slave address
and three register address bytes are sent to the VSC8491-17 device, a START condition must be re-
sent, followed by the slave address with the read/write bit set to logic high. The four-byte data register
contents are then transmitted from the VSC8491-17 device. The two-wire serial (master) sends NO ACK
after the fourth data byte to indicate it has finished reading data. The following illustration shows data
transferred on the SDA pin during a register read operation.
Figure 118 • Two-Wire Serial Read Instruction
S W S
T R T R
A I Register Address A E
R T R A
T Slave Address E T Slave Address D

1 0 0 0 0 0 0 1 0 0 0 1

R A A A A R A
/ C C C C / C
W K K K K W K

Dummy Write to set Read Address

S
T
O
P

B A A A B N
I C C C I O
T K K K T
A
3 0 C
1 K

Data Read from Register

The two-wire serial slave interface supports sequential read and sequential write instructions.

3.15.4 Two-Wire Serial (Master) Interface

A two-wire serial master interface is available for SFP+/XFP module management. Two-wire serial
interface instructions used to access optics module registers are initiated by writing to VSC8491-17
registers. The two-wire serial interface busses are brought out through GPIO pins. The two-wire serial
interface is enabled by configuring GPIO_6 to function as SDA and GPIO_7 to function as SCL.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 152

Functional Descriptions

The two-wire serial master interface must be configured before initiating any instructions. The slave ID to
be transmitted in the first byte of every instruction is selectable in the SLAVE_ID register. The default
setting is 0x50. The interface's data rate is determined by the PRESCALE register. The default data rate
is 400 kbps.
The two-wire serial master transmits instructions for slave devices with 8-bit data registers and 256
register addresses per slave ID. Always read register I2C_BUS_STATUS.I2C_BUS_BUSY or
I2C_READ_STATUS_DATA.I2C_BUS_BUSY to verify the previous instruction has finished prior to
initiating a new instruction. Instructions initiated when the interface is busy will be ignored. Both registers
report the same interface busy status. The same busy status is reported in two registers for user
convenience.
The two-wire serial master initiates a write instruction when the I2C_WRITE_CTRL register is written.
The value written to I2C_WRITE_CTRL.WRITE_ADDR is the register address to be modified in the slave
device. The value written to I2C_WRITE_CTRL.WRITE_DATA is the data to be written to the slave
device's register. The I2C_BUS_STATUS register reports the status of the write instruction.
I2C_BUS_STATUS.I2C_BUS_BUSY indicates when the instruction has finished.
I2C_BUS_STATUS.I2C_WRITE_ACK=1 means the two-wire serial master received ACKs from the slave
at appropriate times. I2C_BUS_STATUS.I2C_WRITE_ACK is cleared each time a new instruction is
issued. If the two-wire serial master did not receive ACKs from the slave at appropriate times
(I2C_BUS_STATUS.I2C_WRITE_ACK=0), the interface is likely stuck in a state waiting for the ACK.
Writing a 1 to the BLOCK_LEVEL_RESET1.I2CM_RESET register will reset the two-wire serial master
and release it from its stuck state. The slave device should then be put into a known state by writing any
value to the I2C_RESET_SEQ register. The two-wire serial master issues a bus reset sequence when
this register is written. For more information, see Two-Wire Serial (Slave) Interface, page 150.
The two-wire serial master initiates a read instruction when the I2C_READ_ADDR register is written. The
value written to I2C_READ_ADDR.READ_ADDR is the register address to be accessed in the slave
device. I2C_READ_STATUS_DATA.READ_DATA contains the data read from the slave device.
READ_DATA is not valid until I2C_READ_STATUS_DATA.I2C_BUS_BUSY=0 to indicate the instruction
completed. The two-wire serial master does not support read-increment instructions.

3.15.5 Push Out SPI Master Interface

To overcome MDIO speed limitations for faster or large amounts of time stamp reads, the VSC8491-17
device supports a push out SPI master interface. The SPI output is used to push out time stamp
information to an external device only, and does not provide read/write to the rest of the status and
configuration registers. For more information, see Serial Time Stamp Output Interface, page 89.
The push out SPI master interface consist of an SPI clock output (SPI_CLK), an SPI data output
(SPI_DO), and an SPI chip select output, (SPI_CS).

3.15.6 GPIO
General purpose input/output (GPIO) pins in the VSC8491-17 device serve multiple functions. The GPIO
pins are bidirectional where the driver portion is an open-drain buffer. The following table shows the
functions that each pin supports and the registers used to configure the pin functions. Leave GPIO pins

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 153

Functional Descriptions

unconnected when not in use. When configured as output, they are open-drained and a pull-up is
required.

Table 68 • GPIO Functions

Pin Configuration Registers Functions

GPIO_0 GPIO_0_Config_Status Traditional I/O (default)
GPIO_0_Config2 Observed internal signals
MOD_ABS_Channel_0
PMTICK
ROSI frame pulse 0
Tx Activity LED
WIS_INTB
1588-1PPS channel 0
Leave unconnected when not used
GPIO_1 GPIO_1_Config_Status Traditional I/O (default)
GPIO_1_Config2 Observed internal signals
ROSI_CLK_0
Rx Activity LED
WIS_INTA
1588-Load/Save
Leave unconnected when not used
GPIO_2 GPIO_2_Config_Status Traditional I/O
GPIO_2_Config2 Observed internal signals
Slave two-wire serial - SDA (default)
ROSI_DATA_0
Tx Activity LED
WIS_INTB
GPIO_3 GPIO_3_Config_Status Traditional I/O
GPIO_3_Config2 Observed internal signals
Slave two-wire serial - SCL (default)
TOSI_FRAME_PULSE_0
Rx Activity LED
WIS_INTB
GPIO_4 GPIO_4_Config_Status Traditional I/O (default)
GPIO_4_Config2 Observed internal signals
TOSI_CLK_0
Tx Activity LED
WIS_INTB
1588-1PPS channel 1
GPIO_5 GPIO_5_Config_Status Traditional I/O (default)
GPIO_5_Config2 Observed internal signals
TOSI_INPUT_0
Rx Activity LED
WIS_INTA
1588-PPS RI
Leave unconnected when not used
GPIO_6 GPIO_6_Config_Status Traditional I/O (default)
GPIO_6_Config2 Observed internal signals
Ch0 SFP I2C SDA
ROSI_FRAME_PULSE_1
Tx Activity LED
WIS_INTB

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 154

Functional Descriptions

Table 68 • GPIO Functions (continued)

Pin Configuration Registers Functions

GPIO_7 GPIO_7_Config_Status Traditional I/O (default)
GPIO_7_Config2 Observed internal signals
Ch0 SFP I2C SCL
ROSI_CLK_1
Rx Activity LED
WIS_INTA
GPIO_8 GPIO_8_Config_Status Traditional I/O (default)
GPIO_8_Config2 Observed internal signals
MOD_ABS_Channel_0
PMTICK
ROSI_DATA_1
Tx Activity LED
WIS_INTA
GPIO_9 GPIO_9_Config_Status Traditional I/O (default)
GPIO_9_Config2 Observed internal signals
Mod_ABS channel 1
PMTICK
TOSI_FRAME_PULSE_1
Rx Activity LED
WIS_INTA
1588-1PPS channel 1
GPIO_10 GPIO_10_Config_Status Traditional I/O (default)
GPIO_10_Config2 Observed internal signals
Ch1 SFP I2C SDA
TOSI_CLK_1
Tx Activity LED
WIS_INSTB
GPIO_11 GPIO_11_Config_Status Traditional I/O (default)
GPIO_11_Config2 Observed internal signals
Ch1 SFP I2C SCL
TOSI_INPUT_1
Rx Activity LED
WIS_INTA
1588-1PPS channel 1
GPIO_12 GPIO_12_Config_Status Traditional I/O (default)
GPIO_12_Config2 Observed internal signals
Tx Activity LED
WIS_INTA
GPIO_13 GPIO_13_Config_Status Traditional I/O (default)
GPIO_13_Config2 Observed internal signals
Rx Activity LED
WIS_INTA
GPIO_14 GPIO_14_Config_Status Traditional I/O (default)
GPIO_14_Config2 Observed internal signals
Tx Activity LED
WIS_INTA
GPIO_15 GPIO_15_Config_Status Traditional I/O (default)
GPIO_15_Config2 Observed internal signals
Rx Activity LED
WIS_INTA

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 155

Functional Descriptions

When a GPIO pin is programmed to be a traditional I/O, the pin may be driven high or low. It may also
serve as an input and an LED driver capable of blinking at various rates. An interrupt pending register
may optionally be asserted when the pin is in input mode and the pin changes state. All of these
functions are configured using the pin configuration register settings shown in the preceding table.
The GPIO pin's output driver is automatically enabled when the pin function is set to observe internal
signals. The second configuration register listed for each pin selects which internal signal is transmitted
from the pin.

3.15.7 JTAG
The VSC8491-17 device has a IEEE 1149.1–2001 compliant JTAG interface. The following table shows
the supported instructions and corresponding instruction register codes. The code's least significant bit is
shifted into TDI first when loading an instruction (the 0 is shifted in first when loading the IDCODE
instruction).

Table 69 • JTAG Instructions and Register Codes

Instruction Register Code Notes

IDCODE 111111111111111111111110
BYPASS 111111111111111111111111
EXTEST 111111111111111111101000
EXTEST_PULSE 111111101111111111101000
EXTEST_TRAIN 111111011111111111101000
SAMPLE 111111111111111111111000
PRELOAD 111111111111111111111000
LV_HIGHZ 111111111111111111001111 Provides the ability to place outputs in a high
impedance state to facilitate manufacturing
test and PC board diagnostics. The XAUI
and SFP+ serial data outputs are not put into
the high impedance state when this
instruction is loaded in the JTAG TAP
controller.
CLAMP 111111111111111111101111 Provides the ability to place all outputs in a
predefined state when the scan process is
being used to test other devices on a PC
board.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 156

Registers

4 Registers

Information about the registers for this product is available in the attached Adobe Acrobat file. To view or
print the information, double-click the attachment icon.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 157

Electrical Specifications

5 Electrical Specifications

This section provides the DC characteristics, AC characteristics, recommended operating conditions,

and stress ratings for the VSC8491-17 device.

5.1 DC Characteristics
This section contains the DC specifications for the VSC8491-17 device.

5.1.1 DC Inputs and Outputs

The following table lists the DC specifications for the LVTTL inputs and outputs for the VSC8491-17
device. The LVTTL inputs are 3.3 V tolerant.

Table 70 • LVTTL Input and Push/Pull Output DC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Output high voltage, VOH_TTL 1.8 VDDTTL V VDDTTL = 2.5 V and
LVTTL IOH = –4 mA
Output low voltage, VOL 0.5 V VDDTTL/VDDMDIO = 2.5 V
LVTTL and IOL = 4 mA
Input high voltage VIH 1.7 VDDTTL V VDDTTL/VDDMDIO = 2.5 V
Input low voltage VIL 0.8 V VDDTTL/VDDMDIO = 2.5 V
Input high current IIH 500 µA VIH = VDDTTL/VDDMDIO
Input low current IIL –100 µA VIL = 0 V

Table 71 • LVTTLOD Input and Open-Drain Output DC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Output high voltage, VOH_OD See note1 VDDTTL V VDDTTL/VDDMDIO = 2.5 V
open drain and IOH = –4 mA
Input high leakage IOZH 100 µA
current, open drain
Output low voltage, VOL 0.5 V VDDTTL/VDDMDIO = 2.5 V
open drain and IOL = 4 mA
Input high voltage VIH 1.7 VDDTTL V VDDTTL/VDDMDIO = 2.5 V
Input low voltage VIL 0.8 V VDDTTL/VDDMDIO = 2.5 V
Input high current IIH 500 µA VIH = VDDTTL/VDDMDIO
Input low current IIL –100 µA VIL = 0 V

1. Determined by the loading current of the other devices connecting to this pin, the IOZH current of this pin, and
the value of the pull-up resistor used.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 158

Electrical Specifications

5.1.2 Reference Clock

The following table lists the DC specifications for the reference clock for the VSC8491-17 device.

Table 72 • Reference Clock DC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

XREFCK/WREFCK ∆VI_DIFF_LOW 200 1200 mVP-P CML reference
differential input swing, low1 clock input
XREFCK/WREFCK ∆VI_DIFF_HIGH 1100 2400 mVP-P LVPECL
differential input swing, high1 reference clock
input
SREFCK differential input ∆VI_DIFF 200 2400 mVP-P
swing

1. An API call is used to set the input swing to be high or low.

5.2 AC Characteristics
This section contains the AC specifications for the VSC8491-17 device. The specifications apply to all
channels. All the XAUI/RXAUI/SFI I/Os should be AC-coupled and work in differential.

5.2.1 Receiver Specifications

The specifications in the following table correspond to line-side 10G receiver input, SFI point D. Point D
assumes that the input is from a compliant point C output and a compliant SFI or XFI channel according
to the SFP+ standard (SFF-8431) or the XFP multisource agreement (INF-8077i). The measurement is
done with a 9 dB channel loss unless stated otherwise. The jitter and amplitude measurements are
calibrated at point C”, as specified in SFF-8431 revision 4.1.

Table 73 • Line-Side 10G Receiver Input (SFI Point D 9.95328G) AC Characteristics

Parameter Symbol Minimum Typical Maximum Unit Condition

RXIN input data rate, 9.95328 – 10.3125 10.3125 + 100 pp Gbps 10 Gbps LAN/WAN
10 Gbps 100 ppm m mode
RXIN linear mode ∆VRXINLINEAR 180 600 mV Voltage modulation
differential input data amplitude (VMA)
swing
RXIN limiting mode ∆VRXINLIMITING 300 850 mV Measured
differential input data peak-to-peak
swing
RXIN AC VCM 15 mVRMS
common-mode
voltage
Differential return loss RLSDD11 –12 dB 0.01 GHz to 2.0 GHz
Differential return loss RLSDD11 –6.68 + dB 2.0 GHz to 11.1 GHz
12.1 x log10(f/5.5)
Reflected differential RLSCD11 –10 dB 0.1 GHz to 11.1 GHz
to common-mode
conversion
99% jitter 99%JIT_p-p 0.42 UI
Pulse width shrinkage DDPWSJIT_p-p 0.3 UI
jitter
Total jitter tolerance TOLJIT_P-P 0.70 UI

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 159

Electrical Specifications

Table 73 • Line-Side 10G Receiver Input (SFI Point D 9.95328G) AC Characteristics (continued)

Parameter Symbol Minimum Typical Maximum Unit Condition

Eye mask X1 X1 0.35 UI
Eye mask Y1 Y1 150 mV
Eye mask Y2 Y2 425 mV
Waveform distortion WDPc 9.3 dBe BER 1E–12. This
penalty parameter of DAC is
measured with 7 dB
SFI channel loss.
Voltage modulation VMA 180 mV BER 1E–12. This
amplitude parameter of DAC is
measured with 7 dB
SFI channel loss.
Optical sensitivity SB2B –24 dBm BER 1E–12, PRBS31
(ROP), back-to-back, and 10 GbE frame,
10.3 Gbps 5.76 dB SFI channel
loss.
Optical sensitivity SFIBER –21 dBm 95 km single-mode
(ROP), with fiber fiber, BER 1E–12,
plant, 10.3 Gbps PRBS31 and 10 GbE
frame, 5.76 dB SFI
channel loss.
Chromatic dispersion FCDP 1.5 3 dB 1600 ps/nm, 5.76 dB
penalty SFI channel loss.
OSNR vs BER with OSNRFEC 16 dB 95 km single-mode
fiber plant, 10.3 Gbps fiber, BER 7E–4,
5.76 dB SFI channel
loss.

The following illustration shows the sinusoidal jitter tolerance for the SFI datacom.
Figure 119 • SFI Datacom Sinusoidal Jitter Tolerance
Sinusoidal Jitter Tolerance (UIp-p)

–20 dB/Dec
5.0

0.05

0.04 0.4 4 40

Frequency (MHz)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 160

Electrical Specifications

The following table lists the 10G input jitter specifications for the VSC8491-17 device.

Table 74 • Line-Side SONET 10G Input Jitter AC Characteristics

Parameter Symbol Minimum Typical Maximum Unit Condition

RXIN input data rate, 9.95328 – 9.95328 9.95328 + 100 ppm Gbps
10 Gbps WAN 100 ppm
Sinusoidal jitter tolerance, SJT 1.5x jitter GR-253 according
9.95 Gbps mask to SONET OC-192
standard

The host-side 6.25 Gbps receiver operating in RXAUI mode complies with the AC characteristics
specified for CEI-6G-SR interfaces according to OIF-CEI-02.0.

Table 75 • Host-Side RXAUI Receiver AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 6.25 – 100 ppm 6.25 + 100 ppm Gbps
Differential peak-to-peak VI_DIFF 125 750 mV AC-coupled, measured
input voltage peak-to-peak each side
(both sides driven)
Differential input return loss RLISDD11 –8 dB 100 MHz to 4.6875 GHz
Differential input return loss RLISDD11 –8 + 16.6 x dB 4.6875 GHz to 6.25 GHz
log(f/4.6875)
Common-mode return loss RLSCC11 –6 dB 100 MHz to 4.6875 GHz
Random jitter RJ 0.15 UIP-P
Uncorrelated bounded high- UBHPJ 0.15 UIP-P
probability jitter
Correlated bounded high- CBHPJ 0.30 UIP-P
probability jitter
Total jitter TJ 0.60 UIP-P
Eye mask X1 R_X1 0.30 UIP-P
Eye mask Y1 R_Y1 62.5 mV
Eye mask Y2 R_Y2 375 mV

The following table lists the host-side 3.125 Gbps receiver characteristics when operating in XAUI mode
following IEEE 802.3 clauses 47, 54, and 71.

Table 76 • Host-Side XAUI Receiver AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 3.125 – 3.125 + Gbps
100 ppm 100 ppm
Differential peak-to-peak VI_DIFF 75 1600 mV AC-coupled, measured
input voltage peak-to-peak each side
(both sides driven)
Differential input return loss RLISDD11 –10 dB 100 MHz to 2.5 GHz
Common-mode return loss RLSCC11 –6 dB 100 MHz to 2.5 GHz
Random jitter RJ 0.18 UIP-P

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 161

Electrical Specifications

Table 76 • Host-Side XAUI Receiver AC Characteristics (continued)

Parameter Symbol Minimum Maximum Unit Condition

Deterministic jitter DJ 0.37 UIP-P
Total jitter tolerance1 TJ 0.65 UIP-P

1. Total jitter includes sinusoidal jitter according to IEEE 802.3 clause 47.3.4.6.

The following illustration shows the sinusoidal jitter tolerance for the XAUI receiver input.
Figure 120 • XAUI Receiver Input Sinusoidal Jitter Tolerance
Sinusoidual Jitter Amplitude (UIp-p)

8.5

0.1

22.1 k 1.875 M 20 M

Frequency (Hz)

The following table lists the line-side 1.25 Gbps SFI input specifications for the VSC8491-17 device.

Table 77 • Line-Side 1.25 Gbps SFI Input AC Characteristics

Parameter Symbol Minimum Typical Maximum Unit Condition

RXIN input 1.25 – 1.25 1.25 + 100 ppm Gbps 1.25 Gbps mode
data rate, 100 ppm
1.25 Gbps
Differential RLISDD11 –10 dB 50 MHz to 625 MHz
input return
loss
Differential RLISDD11 –10 + 10 x dB 625 MHz to 1250 MHz
input return log(f/625 MHz)
loss
Total jitter TJT 0.749 UI Jitter above 637 kHz
tolerance (IEEE 802.3 clause
38.5)
Deterministic DJ 0.462 UIP-P Jitter above 637 kHz
jitter (IEEE 802.3 clause
38.5)
Eye mask Y1 Y1 125 mV
Eye mask Y2 Y2 600 mV

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 162

Electrical Specifications

The host-side 1.25 Gbps receiver operating in 1000BASE-KX mode complies with IEEE 802.3 clause 70.

Table 78 • Host-Side 1.25 Gbps (1000BASE-KX) Receiver Input AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 1.25 – 100 ppm 1.25 + 100 ppm Gbps
Differential input RLISDD11 –10 dB 50 MHz to 625 MHz
return loss
Differential input RLISDD11 –10 + 10 x dB 625 MHz to 1250 MHz
return loss log(f/625 MHz)
Total jitter TOLTJ 0.749 UI Measured according to
tolerance1 IEEE 802.3 clause
38.5
Deterministic jitter TOLDJ 0.462 UI Measured according to
tolerance1 IEEE 802.3 clause
38.5

1. Jitter requirements represent high-frequency jitter (above 637 kHz) and not low-frequency jitter or wander.

5.2.2 Transmitter Specifications

This section includes the transmitter specifications.
The specifications in the following table correspond to line-side 10G transmitter output, SFI point B. Point
B is after a standard-compliant SFI or XFI channel, as defined in the SFP+ standard (SFF-8431) or the
XFP multisource agreement (INF-8077i). The measurement is done with a 9 dB channel loss unless
stated otherwise.

Table 79 • Line-Side 10G Transmitter Output (SFI Point B) AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Termination mismatch ∆ZM 5 %
AC common-mode voltage VOCM_AC 15 mVRMS
Differential return loss SDD22 –12 dB 0.01 GHz to 2.0 GHz
1
Differential return loss SDD22 See note dB 2.0 GHz to 11.1 GHz
2
Common-mode return loss SCC22 See note db 0.01 GHz to 2.5 GHz
Common-mode return loss SCC22 –3 db 2.5 GHz to 11.1 GHz
Total jitter TJ 0.28 UI
Data-dependent jitter DDJ 0.1 UI
Pulse shrinkage jitter DDPWS 0.055 UI
Uncorrelated jitter UJ 0.023 UIRMS
Eye mask X1 X1 0.12 UI
Eye mask X2 X2 0.33 UI
Eye mask Y1 Y1 95 mV
Eye mask Y2 Y2 350 mV

1. Reflection coefficient given by the equation SDD22(dB) = –6.68 + 12.1 Log10(f/5.5), with f in GHz.
2. S-parameter equation SCC22(dB) = -7 + 1.6 × f, with f in GHz.

The following illustration shows the compliance mask associated with the Tx SFI transmit differential
output.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 163

Electrical Specifications

Figure 121 • SFI Transmit Differential Output Compliance Mask

Y2

Y1

Voltage
0
–Y1

–Y2

0.0 X1 X2 1–X2 1–X1 1.0

Normalized Time (UI)

The following table shows the transmit path output specifications for SFI point B with 7 dB SFI channel
loss.

Table 80 • Transmitter SFP+ Direct Attach Copper Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

SFP+ direct attach VMA 300 mV See SFF-8431 section D.7.
copper voltage
modulation
amplitude, peak-to-
peak
SFP+ direct attach QSQ 63.1 See SFF-8431 section D.8.
copper transmitter
QSQ
SFP+ direct attach 12 mV See SFF-8431 section D.15.
copper output AC (RMS)
common-mode
voltage
SFP+ direct attach TWDPc 10.7 dB Electrical output measured
copper host output using SFF-8431 Appendix G,
TWDPc including copper direct attach
stressor.

The following table shows that the 10 Gbps transmitter operating in 10GBASE-KR mode complies with
IEEE 802.3 clause 72.7.

Table 81 • 10 Gbps Transmitter 10GBASE-KR AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Signalling speed TBAUD 10.3125 – 100 ppm 10.3125 + 100 ppm Gbps
Differential output RLOSDD22 9 dB 50 MHz to 2.5 GHz
return loss 9 – 12 x log(f/2.5) 2.5 GHz to 7.5 GHz
RL = 100 Ω ± 1%
Common mode RLOCM 6 dB 50 MHz to 2.5 GHz
return loss 6 – 12 x log(f/2.5) 2.5 GHz to 7.5 GHz
RL = 100 Ω ± 1%
Transition time TR, TF 24 47 ps 20% to 80%

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 164

Electrical Specifications

Table 81 • 10 Gbps Transmitter 10GBASE-KR AC Characteristics (continued)

Parameter Symbol Minimum Maximum Unit Condition

Random jitter RJ 0.15 UI BER 1E–12
Deterministic jitter DJ 0.15 UI
Duty cycle distortion DCD 0.035 UI
(part of DJ)
Total jitter TJ 0.28 UI

The following table shows the transmit path SONET jitter specifications for point A, measured with
register optimization and using a clock rate of 156.25 MHz or 155.52 MHz.

Table 82 • Line-Side SONET 10G Output Jitter AC Characteristics

Parameter Symbol Maximum Unit

Total jitter, 20 kHz to 80 MHz TJ 150 mUI
Total jitter, 4 MHz to 80 MHz TJ 80 mUI

The near-end 6.25 Gbps transmitter output operating in RXAUI mode complies with the AC
characteristics specified for CEI-6G-SR interfaces according to OIF-CEI-02.0.

Table 83 • Near-end RXAUI Transmitter Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 6.25 – 100 ppm 6.25 + 100 ppm Gbps
Differential output return loss RLOSDD22 –8 dB 100 MHz to 4.6875 GHz
Differential output return loss RLOSDD22 –8 + 16.6 x dB 4.6875 GHz to 6.25 GHz
log(f/4.6875)
Common-mode output return RLOSCC22 –6 dB 100 MHz to 4.6875 GHz
loss
Rise time and fall time tR, tF 30 130 ps 20% to 80%
Uncorrelated bounded high- UBHPJ 0.15 UIP-P
probability jitter
Duty cycle distortion DCD 0.05 UIP-P
Total jitter TJ 0.30 UIP-P
Eye mask X1 X1 0.15 UIP-P
Eye mask X2 X2 0.40 UIP-P
Eye mask Y1 Y1 200 mV
Eye mask Y2 Y2 375 mV

The far-end 6.25 Gbps transmitter output operating in RXAUI mode complies with the AC characteristics
specified for CEI-6G-SR interfaces according to OIF-CEI-02.0.

Table 84 • Far-end RXAUI Transmitter Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Uncorrelated bounded high- UBHPJ 0.15 UIP-P
probability jitter

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 165

Electrical Specifications

Table 84 • Far-end RXAUI Transmitter Output AC Characteristics (continued)

Parameter Symbol Minimum Maximum Unit Condition

Correlated bounded high- CBHPJ 0.30 UIP-P
probability jitter
Total jitter TJ 0.60 UIP-P
Eye mask X1 R_X1 0.30 UIP-P
Eye mask Y1 R_Y1 62.5 mV
Eye mask Y2 R_Y2 375 mV

The following table lists the far-end XAUI output specifications for the VSC8491-17 device.

Table 85 • Far-end XAUI Transmitter Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 3.125 – 100 ppm 3.125 + 100 ppm Gbps
Differential output VOUT_DIFF 600 1600 mV Near-end
voltage
Differential output RLOSDD11 –10 dB 312.5 MHz to
return loss 625 MHz
Differential output RLOSDD11 –10 + 10 x dB 625 MHz to
return loss log(f/625 MHz) 3.125 GHz
Rise time and fall tR, tF 60 130 ps 20% to 80%
time
Total jitter TJ 0.55 UI
Deterministic jitter DJ 0.37 UI
Eye mask X1 X1 0.275 UI
Eye mask X2 X2 0.4 UI
Eye mask A1 A1 100 mV
Eye mask A2 A2 800 mV

The following illustration shows the compliance mask for the XAUI output.
Figure 122 • XAUI Output Compliance Mask
Differential Signal Amplitude (V)

A2

A1

−A1

−A2

0 X1 X2 1-X2 1-X1 1

Normalized Bit Time (UI)

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 166

Electrical Specifications

The following table lists the line-side 1.25 Gbps SFI output specifications for the VSC8491-17 device.

Table 86 • Line-Side 1.25 Gbps SFI Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Differential output RLOSDD22 –10 dB 50 MHz to 625 MHz
return loss
Differential output RLOSDD22 –10 + 10 x dB 625 MHz to 1250 MHz
return loss log(f/625 MHz)
Common mode RLOCM –6 dB 50 MHz to 625 MHz
return loss
Deterministic jitter DJ 0.1 UI Measured according to
IEEE 802.3 clause 38.5
Total jitter TJ 0.24 UI Measured according to
IEEE 802.3 clause 38.5
Eye mask Y1 Y1 150 mV SFF-8431 1G
specification
Eye mask Y2 Y2 500 mV SFF-8431 1G
specification

The host-side transmitter operating in 1000BASE-KX mode complies with IEEE 802.3 clause 70.

Table 87 • Host-Side Transmitter 1000BASE-KX AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

Data rate 1.25 – 100 ppm 1.25 + 100 ppm Gbps
Differential output RLOSDD22 –10 dB 50 MHz to 625 MHz
return loss
Differential output RLOSDD22 –10 + 10 x dB 625 MHz to
return loss log(f/625 MHz) 1250 MHz
Random jitter RJ 0.15 UIP-P At BER 10 –12
Deterministic jitter DJ 0.10 UIP-P
Total jitter TJ 0.25 UIP-P

5.2.3 Timing and Reference Clock

The following table lists the reference clock specifications (XREFCK, SREFCK, WREFCK, and
CLK1588) for the VSC8491-17 device.

Table 88 • Reference Clock AC Characteristics

Parameter Symbol Minimum Typical Maximum Unit Condition

XREFCK, SREFCK, and ƒREFCLK 120 156.25 MHz
WREFCK frequency1
XREFCK, SREFCK, and ƒR – 100 ppm 100 ppm MHz
WREFCK frequency accuracy1
Rise time and fall time t R , tF 0.4 ns Within ± 200 mV
relative to VDD x 2/3
XREFCK and WREFCK Clock DC 40 60 % At 50% threshold
duty cycle

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 167

Electrical Specifications

Table 88 • Reference Clock AC Characteristics (continued)

Parameter Symbol Minimum Typical Maximum Unit Condition

SREFCK Clock duty cycle DCSREFCK 45 55 % At 50% threshold
Jitter tolerance for XREFCLK, JTLXREF 0.7 ns For frequency 2 KHz to
WREFCLK, and SREFCLK 20 MHz
Jitter tolerance for CLK1588 JTLCLK_1588 200 ps
2
Frequency for CLK1588 ƒCLK_1588 125 250 MHz
Duty cycle for CLK1588 DC1588CLK 40 50 60 %

1. XREFCK (LAN mode applications) frequency may be set to 125 MHz or 156.25 MHz. WREFCK (LAN or WAN mode Synchronous
Ethernet applications) frequency may be set to 155.52 MHz. SREFCK (LAN mode Synchronous Ethernet applications) frequency
is 156.25 MHz.
2. Contact your Microsemi representative for other frequencies.

The following illustration shows the worst-case clock jitter transfer characteristic for the XREFCK input.
Figure 123 • XREFCK to Data Output Jitter Transfer
3.0 dB

0 dB

-3.0 dB

-6.0 dB

-9.0 dB
gain

-12.0 dB

-15.0 dB

-18.0 dB

-21.0 dB

-24.0 dB

.01 MHz .1 MHz 1.0 MHz 10.0 MHz 100.0 MHz

frequency

5.2.4 Two-Wire Serial (Slave) Interface

This section contains information about the AC specifications for the two-wire serial slave interface for
the VSC8491-17 device.

Table 89 • Two-Wire Serial Interface AC Characteristics

Standard Fast Mode

Parameter Symbol Minimum Maximum Minimum Maximum Unit
Serial clock frequency ƒSCL 100 400 kHz
Hold time START condition tHD:STA 4.0 0.6 µs
after this period, the first
clock pulse is generated
Low period of SCL tLOW 4.7 1.3 µs
High period of SCL tHIGH 4.0 0.6 µs
Data hold time tHD:DAT 0 3.45 0 0.9 µs

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 168

Electrical Specifications

Table 89 • Two-Wire Serial Interface AC Characteristics (continued)

Standard Fast Mode

Parameter Symbol Minimum Maximum Minimum Maximum Unit
Data setup time tSU:DAT 250 100 ns
Rise time for SDA and SCL tR 1000 300 ns
Fall time for SDA and SCL tF 300 300 ns
Setup time for STOP tSU:STO 4.0 0.6 µs
condition
Bus free time between a tBUF 4.7 1.3 µs
STOP and START
Capacitive load for SCL CB 400 330 pF
and SDA bus line
External pull-up resistor1 RP 900 8 x 10–7/CB 900 3 x 10–7/CB Ω

1. Minimum value is determined from IOL and internal reliability requirements. Maximum value is determined by
load capacitance. Microsemi recommends 10 kΩ for typical applications in which capacitance loads are
below the specified minimums.

Figure 124 • Two-Wire Serial Interface Timing

SDA

tF tLOW tR tSU;DAT tF tHD;STA tR tBUF

SCL

tHD;STA tHD;DAT tSU;STA tSU;STO

S tHIGH Sr P S

S = START, P = STOP, and Sr = repeated START .

5.2.5 MDIO Interface

This section contains information about the AC specifications for the MDIO interface for the VSC8491-17
device.

Table 90 • MDIO Interface AC Characteristics

Parameter Symbol Minimum Maximum Unit

MDIO data hold time tHOLD 10 ns
MDIO data setup time tSU 10 ns
Delay from MDC rising edge to MDIO data change tDELAY 300 ns
MDC clock rate ƒ 2.5 MHz

The following illustration shows the timing with the MDIO sourced by STA.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 169

Electrical Specifications

Figure 125 • Timing with MDIO Sourced by STA

VIH (MIN)

MDC
VIH (MIN)

VIH (MIN)

MDIO
VIH (MIN)

10 ns minimum
10 ns minimum

The following illustration shows the timing with the MDIO sourced by MMD.
Figure 126 • Timing with MDIO Sourced by MMD
VIH (MIN)
MDC
VIH (MIN)

VIH (MIN)
MDIO
VIH (MIN)

0 ns Minimum
300 ns Maximum

The following table lists the clock output specifications (RX0CKOUT, RX1CKOUT, TX0CKOUT,
TX1CKOUT) for the VSC8491-17 device.

Table 91 • Clock Output AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

RX0CKOUT, RX1CKOUT, TX0CKOUT, and JGC64 10 psRMS from
TX1CKOUT jitter generation 10 KHz to
10 MHz
RX0CKOUT, RX1CKOUT, TX0CKOUT, and ∆V 650 900 mVP-P
TX1CKOUT differential output swing

5.2.6 Synchronous Time-of-Day Load/Save Timing

When the 1588 Load/Save strobe (GPIO_1 pin) is applied to the device synchronous to CLK1588P/N,
the setup and hold (minimum) times shown in the following table must be satisfied.

Table 92 • Load/Save Setup and Hold Timing AC Characteristics

Parameter Symbol Minimum Unit

1588 LOAD/SAVE setup time tSETUP 1.1 ns
1588 LOAD/SAVE hold time tHOLD 0.1 ns

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 170

Electrical Specifications

The following illustration shows the LOAD/SAVE AC timing.

Figure 127 • Load/Save AC Timing
1588P 1588P

Load/Save Load/Save

thold tsetup

5.2.7 SPI Slave Interface

This section contains information about the AC specifications for the four-pin SPI slave interface used to
read and write registers. The maximum clock rate is 30 MHz and it is configurable.

Table 93 • SPI Slave Interface AC Characteristics

Parameter Symbol Minimum Maximum Unit Condition

MOSI data setup time tSU, MOSI 10 ns
MOSI data hold time tHD, MOSI 10 ns
SSN data setup time tSU, SSN 15 ns SSN transition low to
enable interface
SSN data hold time tHD, SSN SCK clock ns SSN transition high to
period + 15.0 enable interface
SSN transition low to tON, MISO 17 ns
MISO valid
SSN transition high to tOFF, MISO 18 ns
MISO high impedance
Falling SCK to valid MISO tDLY, NORM 14 30 ns Maximum capacitance
data, normal mode loading of 5 pF
Rising SCK to valid MISO tDLY, FAST 14 30 ns Maximum capacitance
data, fast mode loading of 5 pF

The following illustration shows the SPI interface timing.

Figure 128 • SPI Interface Timing
tSU,SSN tHD,SSN

SSN

MOSI

tSU,MOSI tHD,MOSI

SCK

tDLY,NORM
MISO,
Normal
Mode
tON,MISO tDLY,FAST tOFF,MISO
MISO,
Fast
Mode

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 171

Electrical Specifications

The following table lists the AC characteristics for the 3-pin push-out SPI.

Table 94 • 3-Pin Push-Out SPI AC Characteristics

Parameter Symbol Minimum Maximum Unit

SPI_DO to tDO, CLK –1 6.5 ns
SPI_CLK delay
SPI_CS to tCS, CLK 0.5 8 ns
SPI_CLK delay

The following illustration shows the 3-pin push-out SPI timing.

Figure 129 • 3-Pin Push-Out SPI Timing

SPI_CLK

SPI_DO

SPI_CS

5.3 Operating Conditions

To ensure that the control pins remain set to the desired configured state when the VSC8491-17 device
is powered up, perform a reset using the reset pin after power-up and after the control pins are steady for
1 ms.

Table 95 • Recommended Operating Conditions

Parameter Symbol Minimum Typical Maximum Unit Condition

1.0 V power supply voltage VDDAH 0.95 1.0 1.05 V
VDDAL
VDDL
VSC8491-17 1.0 V power IDD 1.6 2.25 A XAUI to
supply current 10G in LAN
mode.
1.2 V power supply voltage VDDHSL 1.14 1.2 1.26 V
1.2 V power supply current IDD12 98 150 mA
2.5 V TTL I/O power supply VDDTTL 2.375 2.5 2.625 V
voltage VDDMDIO
TTL I/O power supply current IDDTTL 40 mA
VSC8491-17 power PDD_LAN 1.9 2.65 W XAUI to XFI
consumption, 10G LAN in 10G LAN.
VSC8491-17 power PDD_WAN 2.0 2.75 W XAUI to XFI
consumption, 10G WAN in 10G
WAN.
Operating temperature1 T –40 110 °C

1. Minimum specification is ambient temperature, and the maximum is junction temperature.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 172

Electrical Specifications

5.4 Stress Ratings

This section contains the stress ratings for the VSC8491-17 device.
Warning Stresses listed in the following table may be applied to devices one at a time without causing
permanent damage. Functionality at or exceeding the values listed is not implied. Exposure to these
values for extended periods may affect device reliability

Table 96 • Stress Ratings

Parameter Symbol Minimum Maximum Unit

1.0 V power supply voltage, potential to ground VDDAH –0.3 1.1 V
VDDAL
VDDL
1.2 V power supply voltage, potential to ground VDDHSL –0.3 1.32 V
2.5 V TTL I/O power supply voltage VDDTTL –0.3 2.75 V
VDDMDIO
Storage temperature TS –55 125 °C
Electrostatic discharge voltage, charged device VESD_CDM –250 250 V
model
Electrostatic discharge voltage, human body model VESD_HBM See note1 V

1. This device has completed all required testing as specified in the JEDEC standard JESD22-A114,
Electrostatic Discharge (ESD) Sensitivity Testing Human Body Model (HBM), and complies with a Class 2
rating. The definition of Class 2 is any part that passes an ESD pulse of 2000 V, but fails an ESD pulse of
4000 V.

Warning This device can be damaged by electrostatic discharge (ESD) voltage. Microsemi
recommends that all integrated circuits be handled with appropriate precautions. Failure to observe
proper handling and installation procedures may adversely affect reliability of the device.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 173

Pin Descriptions

6 Pin Descriptions

The VSC8491-17 device has 196 pins, which are described in this section.
The pin information is also provided as an attached Microsoft Excel file, so that you can copy it
electronically. In Adobe Reader, double-click the attachment icon.

6.1 Pin Diagram

The following illustration is a representation of the VSC8491-17 device, as seen from the top view.
Figure 130 • Pin Diagram
1 2 3 4 5 6 7 8 9 10 11 12 13 14
A GND GND XTX0_3P XTX0_2P XTX0_1P XTX0_0P TDIOP RX0CKOUTN GND TX0CKOUTN GND GND GND GND

B GND GND XTX0_3N XTX0_2N XTX0_1N XTX0_0N TDION RX0CKOUTP GND TX0CKOUTP GND GND RXIN0N RXIN0P

C XRX0_0P XRX0_0N VDDTTL GND GND RESETN VDDMDIO PADDR2 VDDTTL GPIO_12 GPIO_13 GND GND GND

D XRX0_1P XRX0_1N GND GPIO_0 GPIO_1 LOPC0 MDC CLK1588P SSN PADDR1 SC K GND TXOUT0P TXOUT0N

E XRX0_2P XRX0_2N GND GPIO_2 GPIO_3 PADDR4 MDIO CLK1588N MOSI PADDR3 MISO GND GND GND

F XRX0_3P XRX0_3N GND GPIO_4 GPIO_5 GND VDDAL GND VDDHSL VDDHSL GND GND XREFCKP XREFCKN

G GND GND GND VDDAH VDDAH GND VDDAL GND VDDAL VDDHSL GND GND GND GND

H XTX1_0P XTX1_0N GND VDDL VDDL GND VDDL GND VDDAL VDDHSL GND SREFCKP GND WREFCKP

J XTX1_1P XTX1_1N GND VDDAH VDDAH GND VDDAL GND VDDHSL VDDHSL GND SREFCKN GND WREFCKN

K XTX1_2P XTX1_2N GND GPIO_6 GPIO_7 GPIO_8 SPI_CLK TDO TC K TRSTB MODE0 GND GND GND

L XTX1_3P XTX1_3N GND GPIO_9 GPIO_10 GPIO_11 SPI_DO TDI SCAN_EN SPI_CS RCOMPP GND NC NC

M GND GND GND GND TMS VDDTTL NC NC MODE1 GND RCOMPN GND GND GND

N GND XRX1_0P XRX1_1P XRX1_2P XRX1_3P GND NC GND NC GND GPIO_14 GND NC NC

P GND XRX1_0N XRX1_1N XRX1_2N XRX1_3N GND NC GND NC GND GPIO_15 GND GND GND

6.2 Pin Identifications

This section contains the pin descriptions for the device, sorted according to their functional group.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 174

Pin Descriptions

The following table lists the definitions for the pin type symbols.

Table 97 • Pin Identifications

Symbol Pin Type Description

A Analog I/O Analog input for sensing variable voltage levels.
I Input Input signal.
O Output Output signal.
B Bidirectional Bidirectional input or output signal.
CML Current mode logic
NC No connect
LVTTL Low voltage transistor-to-transistor logic
LVTTLOD Low-voltage transistor-to-transistor logic with
open-drain output

6.3 Pins by Function

This section contains the functional pin descriptions for the VSC8491-17 device.
Note: All the differential clock signals and differential data signals should be AC-coupled. A cap of 0.1 uF would
be sufficient.

Functional Group Name Number Type Level Description

1588 CLK1588N E8 I CML 1588 logic clock input, complement
1588 CLK1588P D8 I CML 1588 logic clock input, true
1588 SPI_CLK K7 O LVTTL Pushout SPI clock output for 1588 timestamp
1588 SPI_CS L10 O LVTTL Pushout SPI chip select output for 1588 timestamp
1588 SPI_DO L7 O LVTTL Pushout SPI data output for 1588 timestamp
Selectable clock output channel 0, complement. See
Clock Signal RX0CKOUTN A8 O CML
register device 1, address A008.
Selectable clock output channel 0, true. See register
Clock Signal RX0CKOUTP B8 O CML
device 1, address A008.
Clock Signal SREFCKN J12 I CML SyncE reference clock input, complement
Clock Signal SREFCKP H12 I CML SyncE reference clock input, true
Selectable clock output channel 0, complement. See
Clock Signal TX0CKOUTN A10 O CML
register device 1, address A009.
Selectable clock output channel 0, true. See register
Clock Signal TX0CKOUTP B10 O CML
device 1, address A009.
Clock Signal WREFCKN J14 I CML WAN reference clock input, complement
Clock Signal WREFCKP H14 I CML WAN reference clock input, true
Clock Signal XREFCKN F14 I CML Reference clock input, complement
Clock Signal XREFCKP F13 I CML Reference clock input, true

JTAG TCK K9 I LVTTL Boundary scan, test clock input. Internally pulled high.

JTAG TDI L8 I LVTTL Boundary scan, test data input. Internally pulled high.

JTAG TDO K8 O LVTTL Boundary scan, test data output.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 175

Pin Descriptions

JTAG TMS M5 I LVTTL Boundary scan, test mode select. Internally pulled high.

JTAG TRSTB K10 I LVTTL Boundary scan, test reset input. Internally pulled high.

MDIO MDC D7 I LVTTL MDIO clock input

MDIO MDIO E7 B LVTTLOD MDIO data I/O
Miscellaneous GPIO_0 D4 B LVTTLOD General purpose I/O 0
Miscellaneous GPIO_1 D5 B LVTTLOD General purpose I/O 1
Miscellaneous GPIO_2 E4 B LVTTLOD General purpose I/O 2
Miscellaneous GPIO_3 E5 B LVTTLOD General purpose I/O 3
Miscellaneous GPIO_4 F4 B LVTTLOD General purpose I/O 4
Miscellaneous GPIO_5 F5 B LVTTLOD General purpose I/O 5
Miscellaneous GPIO_6 K4 B LVTTLOD General purpose I/O 6
Miscellaneous GPIO_7 K5 B LVTTLOD General purpose I/O 7
Miscellaneous GPIO_8 K6 B LVTTLOD General purpose I/O 8
Miscellaneous GPIO_9 L4 B LVTTLOD General purpose I/O 9
Miscellaneous GPIO_10 L5 B LVTTLOD General purpose I/O 10
Miscellaneous GPIO_11 L6 B LVTTLOD General purpose I/O 11
Miscellaneous GPIO_12 C10 B LVTTLOD General purpose I/O 12
Miscellaneous GPIO_13 C11 B LVTTLOD General purpose I/O 13
Miscellaneous GPIO_14 N11 B LVTTLOD General purpose I/O 14
Miscellaneous GPIO_15 P11 B LVTTLOD General purpose I/O 15
Miscellaneous MODE0 K11 I LVTTL Mode select input bit 0
Miscellaneous MODE1 M9 I LVTTL Mode select input bit 1
Miscellaneous PADDR1 D10 I LVTTL MDIO port address bit 1. Internally pulled low.
Miscellaneous PADDR2 C8 I LVTTL MDIO port address bit 2. Internally pulled low.
Miscellaneous PADDR3 E10 I LVTTL MDIO port address bit 3. Internally pulled low.
Miscellaneous PADDR4 E6 I LVTTL MDIO port address bit 4. Internally pulled low.
Miscellaneous RCOMPN M11 Analog Resistor comparator, complement
Miscellaneous RCOMPP L11 Analog Resistor comparator, truth
Miscellaneous RESETN C6 I LVTTL Reset. Low= reset. Internally pulled high.
Scan enable input, factory test purposes only. Keep
Miscellaneous SCAN_EN L9 I LVTTL
connected to Ground.
Miscellaneous TDION B7 Analog Temperature diode, complement
Miscellaneous TDIOP A7 Analog Temperature diode, truth

Power and Ground GND A1 P GND Ground

Power and Ground GND A2 P GND Ground

Power and Ground GND A9 P GND Ground

Power and Ground GND A11 P GND Ground

Power and Ground GND A12 P GND Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 176

Pin Descriptions

Power and Ground GND A13 P GND Ground

Power and Ground GND A14 P GND Ground

Power and Ground GND B1 P GND Ground

Power and Ground GND B2 P GND Ground

Power and Ground GND B9 P GND Ground

Power and Ground GND B11 P GND Ground

Power and Ground GND B12 P GND Ground

Power and Ground GND C4 P GND Ground

Power and Ground GND C5 P GND Ground

Power and Ground GND C12 P GND Ground

Power and Ground GND C13 P GND Ground

Power and Ground GND C14 P GND Ground

Power and Ground GND D3 P GND Ground

Power and Ground GND D12 P GND Ground

Power and Ground GND E3 P GND Ground

Power and Ground GND E12 P GND Ground

Power and Ground GND E13 P GND Ground

Power and Ground GND E14 P GND Ground

Power and Ground GND F3 P GND Ground

Power and Ground GND F6 P GND Ground

Power and Ground GND F8 P GND Ground

Power and Ground GND F11 P GND Ground

Power and Ground GND F12 P GND Ground

Power and Ground GND G1 P GND Ground

Power and Ground GND G2 P GND Ground

Power and Ground GND G3 P GND Ground

Power and Ground GND G6 P GND Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 177

Pin Descriptions

Power and Ground GND G8 P GND Ground

Power and Ground GND G11 P GND Ground

Power and Ground GND G12 P GND Ground

Power and Ground GND G13 P GND Ground

Power and Ground GND G14 P GND Ground

Power and Ground GND H3 P GND Ground

Power and Ground GND H6 P GND Ground

Power and Ground GND H8 P GND Ground

Power and Ground GND H11 P GND Ground

Power and Ground GND H13 P GND Ground

Power and Ground GND J3 P GND Ground

Power and Ground GND J6 P GND Ground

Power and Ground GND J8 P GND Ground

Power and Ground GND J11 P GND Ground

Power and Ground GND J13 P GND Ground

Power and Ground GND K3 P GND Ground

Power and Ground GND K12 P GND Ground

Power and Ground GND K13 P GND Ground

Power and Ground GND K14 P GND Ground

Power and Ground GND L3 P GND Ground

Power and Ground GND L12 P GND Ground

Power and Ground GND M1 P GND Ground

Power and Ground GND M2 P GND Ground

Power and Ground GND M3 P GND Ground

Power and Ground GND M4 P GND Ground

Power and Ground GND M10 P GND Ground

Power and Ground GND M12 P GND Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 178

Pin Descriptions

Power and Ground GND M13 P GND Ground

Power and Ground GND M14 P GND Ground

Power and Ground GND N1 P GND Ground

Power and Ground GND N6 P GND Ground

Power and Ground GND N8 P GND Ground

Power and Ground GND N10 P GND Ground

Power and Ground GND N12 P GND Ground

Power and Ground GND P1 P GND Ground

Power and Ground GND P6 P GND Ground

Power and Ground GND P8 P GND Ground

Power and Ground GND P10 P GND Ground

Power and Ground GND P12 P GND Ground

Power and Ground GND P13 P GND Ground

Power and Ground GND P14 P GND Ground

Power and Ground VDDAH G4 P Supply 1.0 V power supply for host side analog

Power and Ground VDDAH G5 P Supply 1.0 V power supply for host side analog

Power and Ground VDDAH J4 P Supply 1.0 V power supply for host side analog

Power and Ground VDDAH J5 P Supply 1.0 V power supply for host side analog

Power and Ground VDDAL F7 P Supply 1.0 V power supply for line side analog

Power and Ground VDDAL G7 P Supply 1.0 V power supply for line side analog

Power and Ground VDDAL G9 P Supply 1.0 V power supply for line side analog

Power and Ground VDDAL H9 P Supply 1.0 V power supply for line side analog

Power and Ground VDDAL J7 P Supply 1.0 V power supply for line side analog

Power and Ground VDDHSL F9 P Supply 1.2 V power supply for line side IOs

Power and Ground VDDHSL F10 P Supply 1.2 V power supply for line side IOs

Power and Ground VDDHSL G10 P Supply 1.2 V power supply for line side IOs

Power and Ground VDDHSL H10 P Supply 1.2 V power supply for line side IOs

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 179

Pin Descriptions

Power and Ground VDDHSL J9 P Supply 1.2 V power supply for line side IOs

Power and Ground VDDHSL J10 P Supply 1.2 V power supply for line side IOs

Power and Ground VDDL H4 P Supply 1.0 V power supply for chip core

Power and Ground VDDL H5 P Supply 1.0 V power supply for chip core

Power and Ground VDDL H7 P Supply 1.0 V power supply for chip core

Power and Ground VDDMDIO C7 P Supply MDIO power supply

Power and Ground VDDTTL C3 P Supply LVTTL power supply

Power and Ground VDDTTL C9 P Supply LVTTL power supply

Power and Ground VDDTTL M6 P Supply LVTTL power supply

Receive and
LOPC0 D6 I LVTTL Loss of optical carrier, channel 0. Internally pulled high.
Transmit Path
Receive and
RXIN0N B13 I CML Receive channel 0 input data, complement
Transmit Path
Receive and
RXIN0P B14 I CML Receive channel 0 input data, true
Transmit Path
Receive and
TXOUT0N D14 O CML Transmit channel 0 output data, complement
Transmit Path
Receive and
TXOUT0P D13 O CML Transmit channel 0 output data, true
Transmit Path
Reserved/No
NC L13 No connect
Connect
Reserved/No
NC L14 No connect
Connect
Reserved/No
NC M7 No connect (could also be grounded)
Connect
Reserved/No
NC M8 No connect (formerly labeled as ANATEST)
Connect
Reserved/No
NC N7 No connect
Connect
Reserved/No
NC N9 No connect
Connect
Reserved/No
NC N13 No connect
Connect
Reserved/No
NC N14 No connect
Connect
Reserved/No
NC P7 No connect
Connect
Reserved/No
NC P9 No connect
Connect
SPI MISO E11 O LVTTL SPI slave data output
SPI MOSI E9 I LVTTL SPI slave data input
SPI SCK D11 I LVTTL SPI slave clock input
SPI SSN D9 I LVTTL SPI slave chip select input

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 180

Pin Descriptions

XAUI channel 0, Rx path lane 0, serial data input,

XAUI Channel XRX0_0N C2 I CML
complement
XAUI Channel XRX0_0P C1 I CML XAUI channel 0, Rx path lane 0, serial data input, true
XAUI channel 0, Rx path lane 1, serial data input,
XAUI Channel XRX0_1N D2 I CML
complement
XAUI Channel XRX0_1P D1 I CML XAUI channel 0, Rx path lane 1, serial data input, true
XAUI channel 0, Rx path lane 2, serial data input,
XAUI Channel XRX0_2N E2 I CML
complement
XAUI Channel XRX0_2P E1 I CML XAUI channel 0, Rx path lane 2, serial data input, true
XAUI channel 0, Rx path lane 3, serial data input,
XAUI Channel XRX0_3N F2 I CML
complement
XAUI Channel XRX0_3P F1 I CML XAUI channel 0, Rx path lane 3, serial data input, true
XAUI channel 1, Rx path lane 0, serial data input,
XAUI Channel XRX1_0N P2 I CML
complement
XAUI Channel XRX1_0P N2 I CML XAUI channel 1, Rx path lane 0, serial data input, true
XAUI channel 1, Rx path lane 1, serial data input,
XAUI Channel XRX1_1N P3 I CML
complement
XAUI Channel XRX1_1P N3 I CML XAUI channel 1, Rx path lane 1, serial data input, true
XAUI channel 1, Rx path lane 2, serial data input,
XAUI Channel XRX1_2N P4 I CML
complement
XAUI Channel XRX1_2P N4 I CML XAUI channel 1, Rx path lane 2, serial data input, true
XAUI channel 1, Rx path lane 3, serial data input,
XAUI Channel XRX1_3N P5 I CML
complement
XAUI Channel XRX1_3P N5 I CML XAUI channel 1, Rx path lane 3, serial data input, true
XAUI channel 0, Tx path lane 0, serial data output,
XAUI Channel XTX0_0N B6 O CML
complement
XAUI Channel XTX0_0P A6 O CML XAUI channel 0, Tx path lane 0, serial data output, true
XAUI channel 0, Tx path lane 1, serial data output,
XAUI Channel XTX0_1N B5 O CML
complement
XAUI Channel XTX0_1P A5 O CML XAUI channel 0, Tx path lane 1, serial data output, true
XAUI channel 0, Tx path lane 2, serial data output,
XAUI Channel XTX0_2N B4 O CML
complement
XAUI Channel XTX0_2P A4 O CML XAUI channel 0, Tx path lane 2, serial data output, true
XAUI channel 0, Tx path lane 3, serial data output,
XAUI Channel XTX0_3N B3 O CML
complement
XAUI Channel XTX0_3P A3 O CML XAUI channel 0, Tx path lane 3, serial data output, true
XAUI channel 1, Tx path lane 0, serial data output,
XAUI Channel XTX1_0N H2 O CML
complement
XAUI Channel XTX1_0P H1 O CML XAUI channel 1, Tx path lane 0, serial data output, true
XAUI channel 1, Tx path lane 1, serial data output,
XAUI Channel XTX1_1N J2 O CML
complement

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 181

Pin Descriptions

XAUI Channel XTX1_1P J1 O CML XAUI channel 1, Tx path lane 1, serial data output, true
XAUI channel 1, Tx path lane 2, serial data output,
XAUI Channel XTX1_2N K2 O CML
complement
XAUI Channel XTX1_2P K1 O CML XAUI channel 1, Tx path lane 2, serial data output, true
XAUI channel 1, Tx path lane 3, serial data output,
XAUI Channel XTX1_3N L2 O CML
complement
XAUI Channel XTX1_3P L1 O CML XAUI channel 1, Tx path lane 3, serial data output, true

Functional Group Name Number Type Level Description

Selectable clock output channel 0, complement. See
Clock Signal RX0CKOUTN A8 O CML
register device 1, address A008.
Selectable clock output channel 0, true. See register
Clock Signal RX0CKOUTP B8 O CML
device 1, address A008.
Selectable clock output channel 1, complement. See
Clock Signal RX1CKOUTN P7 O CML
register device 1, address A008.
Selectable clock output channel 1, true. See register
Clock Signal RX1CKOUTP N7 O CML
device 1, address A008.
Clock Signal SREFCKN J12 I CML SyncE reference clock input, complement
Clock Signal SREFCKP H12 I CML SyncE reference clock input, true
Selectable clock output channel 0, complement. See
Clock Signal TX0CKOUTN A10 O CML
register device 1, address A009.
Selectable clock output channel 0, true. See register
Clock Signal TX0CKOUTP B10 O CML
device 1, address A009.
Selectable clock output channel 1, complement. See
Clock Signal TX1CKOUTN P9 O CML
register device 1, address A009.
Selectable clock output channel 1, true. See register
Clock Signal TX1CKOUTP N9 O CML
device 1, address A009.
Clock Signal WREFCKN J14 I CML WAN reference clock input, complement
Clock Signal WREFCKP H14 I CML WAN reference clock input, true
Clock Signal XREFCKN F14 I CML Reference clock input, complement
Clock Signal XREFCKP F13 I CML Reference clock input, true
Boundary scan, test clock input. Internally pulled
JTAG TCK K9 I LVTTL
high.

JTAG TDI L8 I LVTTL Boundary scan, test data input. Internally pulled high.

JTAG TDO K8 O LVTTL Boundary scan, test data output.

Boundary scan, test mode select. Internally pulled
JTAG TMS M5 I LVTTL
high.
Boundary scan, test reset input. Internally pulled
JTAG TRSTB K10 I LVTTL
high.
MDIO MDC D7 I LVTTL MDIO clock input

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 182

Pin Descriptions

MDIO MDIO E7 B LVTTLOD MDIO data I/O

Miscellaneous GPIO_0 D4 B LVTTLOD General purpose I/O 0
Miscellaneous GPIO_1 D5 B LVTTLOD General purpose I/O 1
Miscellaneous GPIO_2 E4 B LVTTLOD General purpose I/O 2
Miscellaneous GPIO_3 E5 B LVTTLOD General purpose I/O 3
Miscellaneous GPIO_4 F4 B LVTTLOD General purpose I/O 4
Miscellaneous GPIO_5 F5 B LVTTLOD General purpose I/O 5
Miscellaneous GPIO_6 K4 B LVTTLOD General purpose I/O 6
Miscellaneous GPIO_7 K5 B LVTTLOD General purpose I/O 7
Miscellaneous GPIO_8 K6 B LVTTLOD General purpose I/O 8
Miscellaneous GPIO_9 L4 B LVTTLOD General purpose I/O 9
Miscellaneous GPIO_10 L5 B LVTTLOD General purpose I/O 10
Miscellaneous GPIO_11 L6 B LVTTLOD General purpose I/O 11
Miscellaneous GPIO_12 C10 B LVTTLOD General purpose I/O 12
Miscellaneous GPIO_13 C11 B LVTTLOD General purpose I/O 13
Miscellaneous GPIO_14 N11 B LVTTLOD General purpose I/O 14
Miscellaneous GPIO_15 P11 B LVTTLOD General purpose I/O 15
Miscellaneous MODE0 K11 I LVTTL Mode select input bit 0
Miscellaneous MODE1 M9 I LVTTL Mode select input bit 1
Miscellaneous PADDR1 D10 I LVTTL MDIO port address bit 1. Internally pulled low.
Miscellaneous PADDR2 C8 I LVTTL MDIO port address bit 2. Internally pulled low.
Miscellaneous PADDR3 E10 I LVTTL MDIO port address bit 3. Internally pulled low.
Miscellaneous PADDR4 E6 I LVTTL MDIO port address bit 4. Internally pulled low.
Miscellaneous RCOMPN M11 Analog Resistor comparator, complement
Miscellaneous RCOMPP L11 Analog Resistor comparator, truth
Miscellaneous RESETN C6 I LVTTL Reset. Low= reset. Internally pulled high.
Scan enable input, factory test purposes only. Keep
Miscellaneous SCAN_EN L9 I LVTTL
connected to Ground.
Miscellaneous TDION B7 Analog Temperature diode, complement
Miscellaneous TDIOP A7 Analog Temperature diode, truth
Power and
GND A1 P GND Ground
Ground
Power and
GND A2 P GND Ground
Ground
Power and
GND A9 P GND Ground
Ground
Power and
GND A11 P GND Ground
Ground
Power and
GND A12 P GND Ground
Ground
Power and
GND A13 P GND Ground
Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 183

Pin Descriptions

Power and
GND A14 P GND Ground
Ground
Power and
GND B1 P GND Ground
Ground
Power and
GND B2 P GND Ground
Ground
Power and
GND B9 P GND Ground
Ground
Power and
GND B11 P GND Ground
Ground
Power and
GND B12 P GND Ground
Ground
Power and
GND C3 P GND Ground
Ground
Power and
GND C4 P GND Ground
Ground
Power and
GND C5 P GND Ground
Ground
Power and
GND C12 P GND Ground
Ground
Power and
GND C13 P GND Ground
Ground
Power and
GND C14 P GND Ground
Ground
Power and
GND D3 P GND Ground
Ground
Power and
GND D12 P GND Ground
Ground
Power and
GND E3 P GND Ground
Ground
Power and
GND E12 P GND Ground
Ground
Power and
GND E13 P GND Ground
Ground
Power and
GND E14 P GND Ground
Ground
Power and
GND F3 P GND Ground
Ground
Power and
GND F6 P GND Ground
Ground
Power and
GND F8 P GND Ground
Ground
Power and
GND F11 P GND Ground
Ground
Power and
GND F12 P GND Ground
Ground
Power and
GND G1 P GND Ground
Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 184

Pin Descriptions

Power and
GND G2 P GND Ground
Ground
Power and
GND G3 P GND Ground
Ground
Power and
GND G6 P GND Ground
Ground
Power and
GND G8 P GND Ground
Ground
Power and
GND G11 P GND Ground
Ground
Power and
GND G12 P GND Ground
Ground
Power and
GND G13 P GND Ground
Ground
Power and
GND G14 P GND Ground
Ground
Power and
GND H3 P GND Ground
Ground
Power and
GND H6 P GND Ground
Ground
Power and
GND H8 P GND Ground
Ground
Power and
GND H11 P GND Ground
Ground
Power and
GND H13 P GND Ground
Ground
Power and
GND J3 P GND Ground
Ground
Power and
GND J6 P GND Ground
Ground
Power and
GND J8 P GND Ground
Ground
Power and
GND J11 P GND Ground
Ground
Power and
GND J13 P GND Ground
Ground
Power and
GND K3 P GND Ground
Ground
Power and
GND K12 P GND Ground
Ground
Power and
GND K13 P GND Ground
Ground
Power and
GND K14 P GND Ground
Ground
Power and
GND L3 P GND Ground
Ground
Power and
GND L12 P GND Ground
Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 185

Pin Descriptions

Power and
GND M1 P GND Ground
Ground
Power and
GND M2 P GND Ground
Ground
Power and
GND M3 P GND Ground
Ground
Power and
GND M4 P GND Ground
Ground
Power and
GND M10 P GND Ground
Ground
Power and
GND M12 P GND Ground
Ground
Power and
GND M13 P GND Ground
Ground
Power and
GND M14 P GND Ground
Ground
Power and
GND N1 P GND Ground
Ground
Power and
GND N6 P GND Ground
Ground
Power and
GND N8 P GND Ground
Ground
Power and
GND N10 P GND Ground
Ground
Power and
GND N12 P GND Ground
Ground
Power and
GND P1 P GND Ground
Ground
Power and
GND P6 P GND Ground
Ground
Power and
GND P8 P GND Ground
Ground
Power and
GND P10 P GND Ground
Ground
Power and
GND P12 P GND Ground
Ground
Power and
GND P13 P GND Ground
Ground
Power and
GND P14 P GND Ground
Ground
Power and
VDDAH G4 P Supply 1.0 V power supply for host side analog
Ground
Power and
VDDAH G5 P Supply 1.0 V power supply for host side analog
Ground
Power and
VDDAH J4 P Supply 1.0 V power supply for host side analog
Ground
Power and
VDDAH J5 P Supply 1.0 V power supply for host side analog
Ground

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 186

Pin Descriptions

Power and
VDDAL F7 P Supply 1.0 V power supply for line side analog
Ground
Power and
VDDAL G7 P Supply 1.0 V power supply for line side analog
Ground
Power and
VDDAL G9 P Supply 1.0 V power supply for line side analog
Ground
Power and
VDDAL H9 P Supply 1.0 V power supply for line side analog
Ground
Power and
VDDAL J7 P Supply 1.0 V power supply for line side analog
Ground
Power and
VDDHSL F9 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDHSL F10 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDHSL G10 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDHSL H10 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDHSL J9 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDHSL J10 P Supply 1.2 V power supply for line side IOs
Ground
Power and
VDDL H4 P Supply 1.0 V power supply for chip core
Ground
Power and
VDDL H5 P Supply 1.0 V power supply for chip core
Ground
Power and
VDDL H7 P Supply 1.0 V power supply for chip core
Ground
Power and
VDDMDIO C7 P Supply MDIO power supply
Ground
Power and
VDDTTL C9 P Supply LVTTL power supply
Ground
Power and
VDDTTL M6 P Supply LVTTL power supply
Ground
Receive and Loss of optical carrier, channel 0. Internally pulled
LOPC0 D6 I LVTTL
Transmit Path high.
Receive and Loss of optical carrier, channel 1. Internally pulled
LOPC1 M7 I LVTTL
Transmit Path high.
Receive and
RXIN0N B13 I CML Receive channel 0 input data, complement
Transmit Path
Receive and
RXIN0P B14 I CML Receive channel 0 input data, true
Transmit Path
Receive and
RXIN1N L14 I CML Receive channel 1 input data, complement
Transmit Path
Receive and
RXIN1P L13 I CML Receive channel 1 input data, true
Transmit Path
Receive and
TXOUT0N D14 O CML Transmit channel 0 output data, complement
Transmit Path

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 187

Pin Descriptions

Receive and
TXOUT0P D13 O CML Transmit channel 0 output data, true
Transmit Path
Receive and
TXOUT1N N13 O CML Transmit channel 1 output data, complement
Transmit Path
Receive and
TXOUT1P N14 O CML Transmit channel 1 output data, true
Transmit Path
Reserved/No
NC D8 No connect
Connect
Reserved/No
NC E8 No connect
Connect
Reserved/No
NC K7 No connect
Connect
Reserved/No
NC L7 No connect
Connect
Reserved/No
NC L10 No connect
Connect
Reserved/No
NC M8 No connect (formerly labeled as ANATEST)
Connect
SPI MISO E11 O LVTTL SPI slave data output
SPI MOSI E9 I LVTTL SPI slave data input
SPI SCK D11 I LVTTL SPI slave clock input
SPI SSN D9 I LVTTL SPI slave chip select input
XAUI channel 0, Rx path lane 0, serial data input,
XAUI Channel XRX0_0N C2 I CML
complement
XAUI channel 0, Rx path lane 0, serial data input,
XAUI Channel XRX0_0P C1 I CML
true
XAUI channel 0, Rx path lane 1, serial data input,
XAUI Channel XRX0_1N D2 I CML
complement
XAUI channel 0, Rx path lane 1, serial data input,
XAUI Channel XRX0_1P D1 I CML
true
XAUI channel 0, Rx path lane 2, serial data input,
XAUI Channel XRX0_2N E2 I CML
complement
XAUI channel 0, Rx path lane 2, serial data input,
XAUI Channel XRX0_2P E1 I CML
true
XAUI channel 0, Rx path lane 3, serial data input,
XAUI Channel XRX0_3N F2 I CML
complement
XAUI channel 0, Rx path lane 3, serial data input,
XAUI Channel XRX0_3P F1 I CML
true
XAUI channel 1, Rx path lane 0, serial data input,
XAUI Channel XRX1_0N P2 I CML
complement
XAUI channel 1, Rx path lane 0, serial data input,
XAUI Channel XRX1_0P N2 I CML
true
XAUI channel 1, Rx path lane 1, serial data input,
XAUI Channel XRX1_1N P3 I CML
complement
XAUI channel 1, Rx path lane 1, serial data input,
XAUI Channel XRX1_1P N3 I CML
true

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 188

Pin Descriptions

XAUI channel 1, Rx path lane 2, serial data input,

XAUI Channel XRX1_2N P4 I CML
complement
XAUI channel 1, Rx path lane 2, serial data input,
XAUI Channel XRX1_2P N4 I CML
true
XAUI channel 1, Rx path lane 3, serial data input,
XAUI Channel XRX1_3N P5 I CML
complement
XAUI channel 1, Rx path lane 3, serial data input,
XAUI Channel XRX1_3P N5 I CML
true
XAUI channel 0, Tx path lane 0, serial data output,
XAUI Channel XTX0_0N B6 O CML
complement
XAUI channel 0, Tx path lane 0, serial data output,
XAUI Channel XTX0_0P A6 O CML
true
XAUI channel 0, Tx path lane 1, serial data output,
XAUI Channel XTX0_1N B5 O CML
complement
XAUI channel 0, Tx path lane 1, serial data output,
XAUI Channel XTX0_1P A5 O CML
true
XAUI channel 0, Tx path lane 2, serial data output,
XAUI Channel XTX0_2N B4 O CML
complement
XAUI channel 0, Tx path lane 2, serial data output,
XAUI Channel XTX0_2P A4 O CML
true
XAUI channel 0, Tx path lane 3, serial data output,
XAUI Channel XTX0_3N B3 O CML
complement
XAUI channel 0, Tx path lane 3, serial data output,
XAUI Channel XTX0_3P A3 O CML
true
XAUI channel 1, Tx path lane 0, serial data output,
XAUI Channel XTX1_0N H2 O CML
complement
XAUI channel 1, Tx path lane 0, serial data output,
XAUI Channel XTX1_0P H1 O CML
true
XAUI channel 1, Tx path lane 1, serial data output,
XAUI Channel XTX1_1N J2 O CML
complement
XAUI channel 1, Tx path lane 1, serial data output,
XAUI Channel XTX1_1P J1 O CML
true
XAUI channel 1, Tx path lane 2, serial data output,
XAUI Channel XTX1_2N K2 O CML
complement
XAUI channel 1, Tx path lane 2, serial data output,
XAUI Channel XTX1_2P K1 O CML
true
XAUI channel 1, Tx path lane 3, serial data output,
XAUI Channel XTX1_3N L2 O CML
complement
XAUI channel 1, Tx path lane 3, serial data output,
XAUI Channel XTX1_3P L1 O CML
true

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 189

Package Information

7 Package Information

The VSC8491YJU-17 package is a lead-free (Pb-free), 196-pin, flip chip ball grid array (FCBGA) with a
15 mm × 15 mm body size, 1 mm pin pitch, and 1.4 mm maximum height.
Lead-free products from Microsemi comply with the temperatures and profiles defined in the joint IPC
and JEDEC standard IPC/JEDEC J-STD-020. For more information, see the IPC and JEDEC standard.
This section provides the package drawing, thermal specifications, and moisture sensitivity rating for the
VSC8491-17 device.

7.1 Package Drawing

The following illustration shows the package drawing for the VSC8491-17 device. The drawing contains
the top view, bottom view, side view, dimensions, tolerances, and notes.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 190

Package Information

Figure 131 • Package Drawing

Top View Bottom View
Pin A1 corner Pin A1 corner
14 13 12 11 10 9 8 7 6 5 4 3 2 1

B
C
e
D
E
F
G
D D1
H
J
K
L
M
N
P

e
B
E1

A E

0.20 (4×) Øb
Ø 0.10 M C
Ø 0.25 M C A B
0.35 C

Side View
0.20 C

Dimensions and Tolerances

Reference Minimum Nominal Maximum
Seating plane A 1.40
C A1 A
A1 0.31 0.41
D 15.00
E 15.00
D1 13.00
Notes E1 13.00
1. All dimensions and tolerances are in millimeters (mm). e 1.00
2. Radial true position is represented by typical values. b 0.50

7.2 Thermal Specifications

Thermal specifications for this device are based on the JEDEC JESD51 family of documents. These
documents are available on the JEDEC Web site at www.jedec.org. The thermal specifications are
modeled using a four-layer test board with two signal layers, a power plane, and a ground plane (2s2p

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 191

Package Information

PCB). For more information about the thermal measurement method used for this device, see the
JESD51-1 standard.

Table 98 • Thermal Resistances

Symbol °C/W Parameter

θJCtop 3.35 Die junction to package case top
θJB 13.3 Die junction to printed circuit board
θJA 22.74 Die junction to ambient
θJMA at 1 m/s 18.6 Die junction to moving air measured at an air speed of 1 m/s
θJMA at 2 m/s 17.03 Die junction to moving air measured at an air speed of 2 m/s

To achieve results similar to the modeled thermal measurements, the guidelines for board design
described in the JESD51 family of publications must be applied. For information about applications using
FCBGA packages, see the following:
• JESD51-2A, Integrated Circuits Thermal Test Method Environmental Conditions, Natural Convection
(Still Air)
• JESD51-6, Integrated Circuit Thermal Test Method Environmental Conditions, Forced Convection
(Moving Air)
• JESD51-8, Integrated Circuit Thermal Test Method Environmental Conditions, Junction-to-Board
• JESD51-9, Test Boards for Area Array Surface Mount Package Thermal Measurements

7.3 Moisture Sensitivity

This device is rated moisture sensitivity level 4 as specified in the joint IPC and JEDEC standard
IPC/JEDEC J-STD-020. For more information, see the IPC and JEDEC standard.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 192

Design Considerations

8 Design Considerations

This section provides information about design considerations for the VSC8491-17 device.

8.1 1588 bypass switch should not be activated on the fly

When the 1588 bypass switch is activated on the fly and traffic is flowing, one packet in the system is
corrupted. Thereafter, the system recovers and the packets are processed normally. Disabling the
bypass switch at any time has no impact on traffic.
Because the 1588 engine does not distinguish between PTP and any other traffic from the traffic flow
standpoint, the system should prevent 1588 from being turned off when any traffic is flowing. However, if
one packet corruption is acceptable to the system design, then the bypass switch can be enabled when
traffic is flowing.

8.2 Low-power mode and SerDes calibration

SerDes re-initialization and re-calibration is required when the PHY comes out of the low power mode.
Use the API to enable the required low power and re-calibration functionality instead of the low power
enabling bits at 1x0000.11, 2x0000.11, 3x0000.11, or 4x0000.11, which force a reset of the SerDes
registers.

8.3 Low-power mode should not be enabled when failover

switching is enabled
The device design was not intended to support the low power mode of operation when the failover switch
is enabled. When low power mode is enabled in one channel, the data flow of the other channel could be
adversely affected if the failover switch is enabled, leading to data errors.
Do not enable the low power mode when the failover switch is enabled.

8.4 Flow control with failover switching

Both Tx and Rx data paths of the channel have to be switched at the same time when flow control is
enabled. The Tx data path of one channel in one direction and the Rx data path of another channel in the
opposite direction cannot be mixed.

8.5 XAUI BIST Checker Compatibility

The XAUI BIST checker fails when checking the mixed frequency test pattern. This mixed frequency test
pattern is optional in the IEEE802.3ae specifications.

8.6 SPI bus speeds

The maximum speed enabled on the 4-pin slave SPI bus is 15.4 MHz in normal mode and 30 MHz in fast
mode. The maximum speed for the 3-pin push out only SPI is 40 MHz.

8.7 GPIO as TOSI

A small value pull-up is needed when a GPIO pin is used as TOSI. For more information, contact your
Microsemi representative.

8.8 10GBASE-KR auto negotiation and training

10GBASE-KR negotiation and training (IEEE802.3 Clause 72 and Clause 73) is only available for 10G. It
is not available for 1G.

8.9 Loopbacks in 10G WAN mode

Loopbacks L1, L2, and L2C are not available in 10G WAN mode if jumbo frames are used.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 193

Design Considerations

8.10 10/100M mode not supported

The PHY does not support modes of 10/100M in CuSFP. The autoneg feature is only supported in
1000BASE-X mode but not in SGMII mode. When interfacing with 1G SGMII mode (such as with
CuSFP), the autoneg feature has to be turned off.

8.11 Limited access to registers during failover cross-

connect mode
The following register bits should not be used if failover cross-connect is enabled (that is, if PMA0 is
connected to channel_1 and PMA1 I connected to channel_0).
• 1x0001.2
• 1x0008.10
• 1x000A.0
• 1x9003.4
• 1x0008.11
• 1x9004.4

8.12 Limited auto negotiation support in 1G mode

In 1G mode, the device is specified to support basic auto negotiation for 1000BASE-X (optical interface)
only. For an SGMII interface employed in interfacing CuSFP, auto negotiation is not supported.
Otherwise, auto negotiation must be disabled on both the device and the CuSFP in order to have the
data link be established.

8.13 Limited 1G status reporting

In 1G mode, the 1G status signal from the 1G PCS block is driven by a sticky bit rather than a latched bit,
and so is useful only for link down (and not useful for link up conditions). Also, in 1000BASE-X mode, the
link up indicator does not include AN done status.

8.14 Timestamp errors due to IEEE 1588 reference clock

interruption
After 1588 clock interruption, a local time counter reload using the Unified API is required.

8.15 RXCKOUT squelching

RXCKOUT (positive and negative) can be squelched by varying link status (LOPC, PCS_Fault) in the
device through the use of the API.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 194

Ordering Information

9 Ordering Information

The VSC8491YJU-17 package is a lead-free (Pb-free), 196-pin, flip chip ball grid array (FCBGA) with a
15 mm × 15 mm body size, 1 mm pin pitch, and 1.4 mm maximum height.
Lead-free products from Microsemi comply with the temperatures and profiles defined in the joint IPC
and JEDEC standard IPC/JEDEC J-STD-020. For more information, see the IPC and JEDEC standard.
The following table lists the ordering information for the VSC8491-17 device.

Table 99 • Ordering Information

Part Order Number Description

VSC8491YJU-17 Lead-free, 196-pin FCBGA with a 15 mm × 15 mm body size, 1 mm pin
pitch, and 1.4 mm maximum height. The operating temperature is
–40 °C ambient to 110 °C junction.

VMDS-10506 VSC8491-17 Datasheet Revision 4.0 195