Netgate TNSR High-Performance Edge Routing Features
High-performance routers will be needed at the network edge, in network cores, from premise-to-cloud direct connect infrastructure (where available) and even between public or private Virtual Private Clouds (VPCs).
-
Bridging
Bridging connects two networks so that they act as if they are one network. This is commonly used to connect interfaces across different types of links, e.g., Ethernet to VXLAN, or to enable filtering between two segments of the same network.
-
Static Routing
Static routing relies upon a manually-configured routing entry rather than information from a dynamic routing protocol. Static routing and dynamic routing are not mutually exclusive.
-
Dynamic Routing
Dynamic routing enables routers to select paths based upon real-time logical network layout changes. Popular dynamic routing protocols include Border Gateway protocol (BGP), Open Shortest Path First (OSPF), and Routing Information Protocol (RIP).
-
BGP
Border Gateway Protocol (BGP), the routing protocol used by the global internet, finds the best route path by weighing the latest network conditions based on reachability and routing information.
-
OSPF
Open Shortest Path First (OSPF) is an interior gateway protocol that uses a link state routing algorithm to find the best path between a source and destination router. TNSR supports both OSPF v2 (OSPF) and OSPF v3 (OSPF6).
-
ECMP
Equal-cost multi-path (ECMP) is a dynamic routing technique where packet forwarding to a single destination can occur over multiple best paths with equal routing priority.
-
Static ARP
Static Address Resolution Protocol (Static ARP) can be used to manually map an IPv4 network address to a MAC address that will not be removed after a period of non-use.
-
BFD
Bidirectional Forwarding Detection (BFD) is a protocol that can detect link failures within milliseconds, or even microseconds.
-
VRF-Lite
Virtual Routing and Forwarding (VRF) is a feature which uses isolated L3 domains with alternate routing tables for specific interfaces and dynamic routing purposes.
With this configuration, two units act as an “active/passive” cluster with the primary node working as the master unit and the secondary node in a backup role, taking over as needed if the primary node fails.
What is TNSR High-Performance Edge and Core Routing ?
The need for router speeds will only increase. But fixed-configuration, proprietary, hardware-centric edge networking solutions are a thing of the past. The modern world will be connected with high-performance network function virtualized (NFV) software routers at the edge and in the core. TNSR software provides 5, 10, 40, even 100 Gbps, or more routing via "ASIC-speed" software on commercial-off-the-shelf (COTS) hardware. Get advantage of Vector Packet Processing (VPP) technology & Data Plane Development Kit (DPDK)
A Netgate TNSR Edge routers is on root level & working with your downstream pfsense firewall clusters...
Netgate TNSR is a ultra high-performance Edge router, capable 1G, 10G, 100G ~100G WAN traffic
- Ideal for enterprise-class businesses, educational institutions, government agencies, and service providers
- High-performance router and site-to-site VPN solution
- Extraordinary scale due to the power of Vector Packet Processing (VPP) and Data Plane Development Kit (DPDK)
- Automated management via RESTCONF API or CLI
- Cloud / IDC / server clusters deployment
Netgate TNSR Appliances : Netgate 6100, Netgate 8200, Netgate 1537, Netgate 1541
TNSR is an outstanding high-performance software router with industry-leading price-performance and scalability
- Ideal for demanding edge, campus, data center and cloud connectivity environments where high-speed routing and encrypted traffic handling are required
- Software scalable to 10, 25, 40, 100 Gbps and beyond
- Vector Packet Processing enables up to two orders of magnitude speed gain over traditional kernel-based packet processing solutions
- Suitable for edge and core routing, site-to-site VPN, cloud connectivity, large scale NAT applications
- Managed through CLI and/or RESTCONF API
Cases Study ...
