Filter
Top Products
Intel
®
IXP400 Software
Access-Layer Components: NPE-Downloader (IxNpeDl) API
Programmer’s Guide IXP400 Software Version 2.0 April 2005
Document Number: 252539, Revision: 007 223
14.5 Custom Usage Example
Using a custom image is the second option for starting an NPE. This feature is only useful to those
parties that have NPE microcode development capabilities, and thus does not apply to most users.
The majority of users will use the Intel-provided NPE library.
This allows the use of an external library of images, if needed. External libraries come in the form
of a header file. The header file defines the image library as a single array of type UINT32, and it is
that array symbol that should be used as the imageLibrary parameter for that function.
Here is the function used for this procedure:
14.6 IxNpeDl Uninitialization
After the first NPE has been started using one of the above methods, IxNpeDl will be initialized
and the specified NPEs will begin execution.
IX_NPEDL_NPEIMAGE_NPEC_ETH_SPAN_FIREWALL_VLA
N_QOS_HDR_CONV
NPE Image ID for NPE-C with Basic Ethernet Rx/Tx, which
includes:
•SPANNING_TREE
• FIREWALL
•VLAN/QoS
• 802.3/802.11 Frame Header Conversion
IX_NPEDL_NPEIMAGE_NPEC_CRYPTO_ETH_LEARN_FILT
ER_SPAN_FIREWALL
NPE Image ID for NPE-C with Basic Crypto and Basic Ethernet
Rx/Tx, which includes:
• MAC_FILTERING
• MAC_LEARNING
•SPANNING_TREE
• FIREWALL
For Crypto, it supports DES, SHA-1, MD5.
IX_NPEDL_NPEIMAGE_NPEC_CRYPTO_AES_ETH_LEARN
_FILTER_SPAN_FIREWALL
NPE Image ID for NPE-C with AES Crypto and Basic Ethernet
Rx/Tx, which includes:
• MAC_FILTERING
• MAC_LEARNING
•SPANNING_TREE
• FIREWALL
For Crypto, it supports AES, DES, SHA-1, MD5. AES-CCM mode
is not supported.
IX_NPEDL_NPEIMAGE_NPEC_CRYPTO_AES_CCM_ETH
NPE Image ID for NPE-C with AES & AES-CCM Crypto and
Basic Ethernet Rx/Tx. For Crypto, it supports AES, CCM, DES,
SHA-1, MD5.
Table 44. NPE-C Images (Sheet 2 of 2)
Image Name Description
ixNpeDlCustomImageNpeInitAndStart(UINT32 *imagelibrary, UINT32 npeImageId);