In our critical sites we typically have 1 internet circuit and a AT&T AVPN (MPLS) private circuit used more for failover. What type of circuit would be a good replacement for MPLS and still have good resiliency in our sites? MPLS is expensive.
We had built a ipsec site to site VPN between 2 firewalls but had problems when the load gets above a certain threshold. When a certain load was reached almost no traffic was able to get through the tunnel.Site1 <mtu 1492> ---------Internet----------...
I'm new to ipv6 ip addressing and have a few questions:What type of ipv6 addresses would a company with global offices in each continent assign? The sites need to send traffic to internet and all other sites within the company (internal). I'm assum...
I have an issue with FTD not mapping the nics correctly in ESXi. It looks like the Management and diagnostic nics use one virtual nic. In the FTD console I cannot get the outside and inside nics online. THe status shows disconnected in red. I cannot...
I'm installing a new instance of Cisco FMC 7.3.0 in the latest version of GNS3 but get "System initialization in progress. Please stand by. " immediately after login in the first time. It's been running for hours. I've tried using more memory and cpu...
Your response is much appreciated.Yep, MPLS, or other non-Internet bandwidth, is often much more expensive than Internet bandwidth. Again, though, the former will often guarantee bandwidth, the latter doesn't.There is such a thing as dedicated intern...
- Have to ask, are there any benefits having MPLS over other types of circuit (I can only think of better end to end QOS and having a private circuit using private ip addresses). It's so expensive compared to an internet circuit, might not give us va...
One thing I have a hard time wrapping my mind around is, isn't fragmentation going to happen anyway (from client endpoints) no matter if you reduce the MTU size or not? And what would happen if you adjusted MTU/MSS on the nearest switch instead (clos...
Companies with global offices might assign global unicast addresses from the `2000::/3` range for their networks. Each office could be allocated a specific subnet within this global address space.Networks in different regions would not be contiguous ...
THanks all. What resolved it was just deploying it without powering on the FTD, then removing all virtual nics and adding them all back before powering it back on. When the nics are added back they will be e1000 nics, not vmnetx3. That did the trick...
