FatPipe Can Enhance your Customer's MPLS/Private and Public WANs
This month's FatPipe Reseller Newsletter spotlights how FatPipe works with pure Multi-Protocol Label Switching (MPLS) networks and hybrid networks of MPLS/Private and Public WANs.
We all know that MPLS is reliable and fast, and capable of running voice, video, and data. However, the last mile access
to it remains vulnerable. Your customers are at risk of losing that last mile connection due to a failed data line, or they might face either a loss in service from your ISP, or a failure of their router or other components.
FatPipe transcends these challenges by providing router and access redundancy of the last mile to the provider's edge
router. FatPipe IPVPN achieves this by aggregating two or more MPLS connections or MPLS and public lines for the speed a
reliability your clients need. FatPipe provides seamless interoperability between two separate and autonomous MPLS network service providers or between an MPLS network and one or more public lines without the need for BGP.
View a diagram Click here.
You can use multiple and diverse Data/Internet connections to accomplish WAN redundancy, and ensure your network applications are always available.
Featured FAQs
Q: How do I setup Unit Failover?
A: Go here to view complete instructions on how to setup Unit Failover.
Please make sure that both FatPipe units are using the identical software version. Using different versions may cause
problems when settings are cloned between the units.
FatPipe recommends utilizing a Hub/Switch per Ethernet Interface used on the FatPipe as described in the diagram
located on the instruction sheet provided.
Q: Can I setup Unit Failover using a VLAN?
A: Some customers would rather use a VLAN setup with one Switch. If this is the case, you will need to make sure VLAN
tagging is not used. Also, verify that Multicast UDP port 5002 and 5003 are being allowed as that is the port FatPipe uses to
maintain unit failover between the two devices. (Verification of ports should not be needed on a standard Layer 2
Switch).
Q: is there any issue using Spanning Tree while setup in Unit Failover mode?
A: If your LAN switch uses Spanning Tree Protocol, you must configure "spanning-tree portfast" for each interface on the
switch that is connected to a FatPipe LAN interface. Another option is to use a serial cable between the units for out-of-band heartbeat communication. This is enabled by selecting Serial as your Heartbeat Mode on the Unit Failover page.
Now Shipping
FatPipe is currently shipping Version 5.1 on the products listed below. Contact your FatPipe Account Manager today to
schedule an upgrade.
- MPVPN, IPVPN, WARP, and XTREME- 5.1.2r12
- KOMPRESSOR - 5.1.2r2
- SYMPHONY - 5.1.2r12
|
