Greetings,I'm inheriting a large number of old Cat 2960 switches, half of which the IOS is not crypto capable. All the switches were initially deployed in "install" mode, so all the subdirectory structures and such are in place on those devices. Si...
Greetings and thank you for your time, To summarize/simplify my issue, we have two ISP to which we need to conditionally advertise our public subnet to ISP 1 but not the ISP 2, unless ISP 1 is down. We don't want to use AS prepend to ISP 2, we simpl...
Greetings and I apologize if this is the wrong place to ask, but I need help on an ESM script approach.In short, I have a multiservice router with wireless and call manager that puts everything in one huge syslog file. I want to be able to separate ...
Hi Paul,Here is how I was able to make it work in CML: The "IP SLA Injector" router monitors the public IP address of the DDoS provider (Lumen) used for GRE tunnel destination by the "Border" router. The SLA Injector has a static route to Null0 for...
Thank you for the response.As I mentioned before, we do not want to use EMM as a solution as it is hard to support for junior administrators. Additionally, as I previously mentioned, we need to maintain our BGP neighbor relationship up with ISP2. I...
Hi Paul, Understood about engaging ISP 2, however I'm trying to investigate a solution that we control ourselves at the source. The approach with the secondary router would be: - have the secondary router perform the IP SLA validation to the public I...
Hi Paul, As described in the updates scenario, we already send everying outbound towards ISP 2 (the true ISP). The issue is not the oubound traffic (we never route through the DDoS provider), the issue is controlling the inbound traffic and making ...
Hi Georg, thanks for your time. I'll be lazy and simply paste my response to another contributor. Essentially to give you the bigger picture, “ISP 1” is our DDoS provider and ISP 2 is our true “here’s your circuit” Internet service provider. On t...
