I get that you define the NHRP group on the Hub and select it from the spoke with "ip nhrp group xxxx", but I assume from the examples that is just to control the download traffic from the hub --> spoke. For the return spoke-to-hub traffic, no example is given.
Is it just your everyday plain jane QoS applied to the tunnel interface on the spoke, like any other GRE tunnel? Is that it? I'm surprised in the examples (like the link above + others) that they forgo the return QoS traffic, especially since in a common asymmetric DSL implementation, it's the smaller upload bandwidth that usually kills quality of service. Or am I completely wrong and that hub defined policy is used for both directions? I didn't think it pushed a policy down the tunnel, but I suppose I should ask first. It wasn't clear.
ProblemTaking a snapshot of ISE virtual machines is not supported but it still happens occasionally due to administrators taking a snapshot manually or an integrated technology that automatically takes snapshots to back up VMs. When taking a snapsho...
Hi all, Is it available on Stealthwatch 7 Client or web interface the ability to import the Netflow Exporters names? I found only the possibility to configure manually the name of each Netflow Exporter, but not a bulk configuration.
User Experience Enhancements
As part of Cisco Customer Experience program, we are working towards a more uniform user experience and terminology harmonization. This program runs across all Cisco security products.
We are ali...
Join us on Thursday, October 10 at 10 am PT to meet the CEO and Founder of Cisco's most recent security investment.
In today’s cybersecurity arms race, how does Cisco stay one step ahead in the battle against attackers? One key strategy is keeping tabs on...