Product Details
Place of Origin: China
Brand Name: NetTAP®
Certification: CCC, CE, RoHS
Model Number: MATRIX-TCA-CG; NT-FTAP-32QCX
Payment & Shipping Terms
Minimum Order Quantity: 1 SET
Price: Can Discuss
Packaging Details: Outer Carton plus Inner Foam
Delivery Time: 1-3 Working Days
Payment Terms: L/C, D/A, D/P, T/T, Western Union, MoneyGram
Supply Ability: 100 sets per month
Tunneling Protocols: |
GTP, GRE, PPTP, L2TP And PPPOE |
GRE Tunneling: |
Generic Routing Encapsulation |
Optimize: |
Route The Right Traffic To Right Tools |
VXLAN Headers: |
Support Stripping VXLAN Headers Off |
Applications: |
Data Center Of Telecom, Broadcasting, Government, Etc |
Security: |
Data Protection, Prevent Leakage |
Tunneling Protocols: |
GTP, GRE, PPTP, L2TP And PPPOE |
GRE Tunneling: |
Generic Routing Encapsulation |
Optimize: |
Route The Right Traffic To Right Tools |
VXLAN Headers: |
Support Stripping VXLAN Headers Off |
Applications: |
Data Center Of Telecom, Broadcasting, Government, Etc |
Security: |
Data Protection, Prevent Leakage |
GRE Tunneling Protocol Identify Technology in Network Packet Broker and Network TAP
GRE Tunneling Protocol Identify Technology in Network Packet Broker
Supported automatically identify various tunneling protocols such as GTP / GRE / PPTP / L2TP / PPPOE. According to the user configuration, the traffic output strategy can be implemented according to the inner or outer layer of the tunnel
What is GRE Tunneling Protocol?
GRE(Generic Routing Encapsulation)can encapsulate Data packets of some network layer protocols (such as IPX, ATM, IPv6, AppleTalk, etc.) so that these encapsulated data packets can be transmitted in another network layer protocol (such as IPv4).GRE provides a mechanism for encapsulating messages of one protocol in another. It is a three-layer tunneling technique that allows messages to be transmitted transparently through the GRE tunnel, solving the transmission problem of heterogeneous networks.
GRE implementation mechanism is simple, the tunnel at both ends of the equipment burden.The GRE tunnel can connect to the local network of various network protocols through the IPv4 network, effectively utilizing the original network architecture and reducing the cost.The GRE tunnel extends the scope of hop-limited network protocols to enable flexible enterprise network topologies.The GRE tunnel can encapsulate multicast data and ensure the security of voice, video and other multicast services when combined with IPSec.GRE tunnel support enables MPLS LDP. GRE tunnel is used to carry MPLS LDP messages, LDP LSP is established, and MPLS backbone network is interoperable.The GRE tunnel connects discrete subnets and is used to set up VPNS for secure connections between corporate headquarters and branches.
GRE Implementation Process
Message transmission in the GRE tunnel includes two processes: encapsulation and unencapsulation.
As shown in the figure above, if an X protocol message is transmitted from Ingress PE to Egress PE, it is encapsulated on Ingress PE and unsealed on Egress PE.The path through which the encapsulated datagram travels through the network is called the GRE tunnel.
(1) Encapsulation
(2) Decapsulation
(3) GRE message format
The message structure of the GRE package is shown in the figure above.
(1) Passenger Protocol
The message before packaging is called net load, and the message protocol before packaging is called passenger protocol.
(2) Encapsulation Protocol
The GRE Header is completed and populated by an encapsulation Protocol, also known as the Carrier Protocol.
(3) Transport Protocol or Delivery Protocol
The protocol responsible for forwarding encapsulated packets is called the transport protocol.
| GRE header | Fields Explain |
| C |
Check and verify bits The position 1, indicates that the GRE header inserts the Checksum field The position 0, indicates that the GRE header does not contain checksum fields |
| K |
Keyword bits. The position 1, indicates that the GRE header is inserted with a Key field The position 0, indicates that the GRE header does not contain keyword fields |
| Recursion |
Represents the number of encapsulated layers of a GRE message. Add 1 to this field after completing a GRE package. Discard the text if the number of packages is greater than 3.The purpose of this field is to prevent messages from being encapsulated an infinite number of times.
RFC1701 specifies that the default value for this field is 0.RFC2784 specifies that no exception will be raised if the field is inconsistent between the sender and receiver, and the receiver must ignore the field.
When the device is implemented, this field is only used as the number of nested layers in the tag tunnel when adding the encapsulated message. This field is not perceived when GRE unpacks the message, so it will not affect the processing of the message. |
| Flags | Reserved fields. Must be set to 0 currently |
| Version | Version field. It has to be 0 |
| Protocol Type | Identifies the protocol type of passenger agreement. The common passenger protocol is the IPv4 protocol with the protocol code 0x0800 |
| Checksum | Checksum fields for GRE headers and their loads. |
| Key | Keyword field, the tunnel receiver is used to verify the received message. |
What kind Network Packet Broker and Network Taps support Tunneling Protocol Identify Technology?
Network Packet Broker Specification and Module Type
| Component type | Product Model | Basic Parameter | Remarks |
| Chassis | NTCA-CHS-7U7S-DC | Height:7U,7 slots, ATCA Chassis, double star 100G backplane, 3 high voltage DC(240VDC~280VDC) input,3* 2+1 redundant 3000W power modular | Must choose one |
| NTCA-CHS-7U7S-AC | Height:7U,7 slots, ATCA Chassis, double star 100G backplane, 3 high voltage AC(240VDC~280VDC) input,3* 2+1 redundant 3000W power modular | ||
| Service card | NT-TCA-SCG10 | 100G exchange card,10*QSFP28 interface | Choose according to actual business needs |
| NT-TCA-CG10 | 100G service card,10*QSFP28 interface | ||
| NT-TCA-XG24 | 10G service card,24*SFP+ interface | ||
| NT-TCA-RTM-CG10 | 100G RTM card,10*QSFP28 interface | ||
| NT-TCA-RTM-EXG24 | 10G RTM card,24*SFP+ interface | ||
| TCA Visibility Embedded software system | NT-TCA-SOFT-PKG | must |
