# Element \ Two main funcitons, "input packet process" and "link pairs". ## Attribute

Attribute	Description	Type	Default (* must have)
id	Specifies a unique id for an element	Interger	*
name	Specifies a name for an element	String
type	action type	String	input-packet-process or linkpairs

## Example ```xml P0 vlan ``` ## Elements in Action ### input-packet-process type ### \ Defines input port(must have). It has a start tag \ and an end tag \. ```xml P0 ``` ### \ Defines vlan tagging. It has a start tag \ and an end tag \. ```xml P0 10 ``` ### \ Defines vlan layer 2 tagging. It has a start tag \ and an end tag \. ```xml P0 20 ``` ### \ Defines stripping. It has a start tag \ and an end tag \. #### support type * payload * vlan * mpls * gre * vxlan * gre-erspan * gtp * grism * mpls-in-udp * mpls-in-gre ```xml P0 vlan ``` ### \ Defines tagging. It has a start tag \ and an end tag \. #### support type * timestamp * gtp * gtp2 * grism ```xml P0 grism ``` ### \ Defines packet max length. It has a start tag \ and an end tag \. ```xml P0 64 ``` ### linkpairs type If portA down, force portB down, and vice versa. ```xml P1 P2 ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://arraynetworks.gitbook.io/array-xml/readme/action.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.