The post Worth Reading: Ethernet Getting back on Moore’s Law appeared first on rule 11 reader.
Modern data centers employ IT automation to cut costs and inject agility
In response to my article about what would cause a directly connected route to be overridden, Matt Love (@showflogi) made a good observation:
Good stuff – LPM rule can be a useful tool if you want to manipulate paths without mucking with metrics, esp if using multiple protocols
— Matt Love (@showflogi) July 13, 2017
What Matt is saying is that longest prefix match (LPM) is a mechanism that can be used to steer traffic around the network in order to meet a technical or business need. This type of traffic steering is called traffic engineering (TE).
LPM refers to how route lookups work on a Layer 3 device: the longest, most-specific match is always chosen. Like I explained in the prior post, if the routing table contains 10.10.10.0/24 and 10.10.10.64/26, the latter route will be used to forward traffic to 10.10.10.100 (as an example) because a /26 is longer (ie, has a longer prefix length) and is therefore more specific. We can use this behavior to direct traffic towards 10.10.10.100 over a specific interface or via a specific path (ie, a path with Continue reading
It’s like Microsoft Azure Stack, but on Oracle hardware and software.
Artificial intelligence is coming. Is your data center ready?
Know an amazing woman or girl in tech who’s working for access, skills, or leadership? Why not shine the light on them and nominate them for an EqualsInTech Award!
Equals is an initiative delivered by a committed partnership of ITU, UN Women, GSMA, ITC, and UN University joined by the Internet Society and over 20 corporate leaders, governments, non-profit organizations, communities, and individuals around the world working together to bridge the digital gender divide – by bringing women to tech, and tech to women.
Peter Welcher offers tips for expanding your design skills and discusses campus network segmentation options.
Is engineering talent disappearing from the enterprise? Our panel thinks so, and has a conversation about the implications for both businesses and individuals. This episode was recorded at Cisco Live 2017 in Las Vegas, NV.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Audio Only Podcast Feed:
The post Off The Cuff – Engineering In The Enterprise appeared first on Network Collective.
Is engineering talent disappearing from the enterprise? Our panel thinks so, and has a conversation about the implications for both businesses and individuals. This episode was recorded at Cisco Live 2017 in Las Vegas, NV.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
Audio Only Podcast Feed:
The post Off The Cuff – Engineering In The Enterprise appeared first on Network Collective.
The use of geolocation is fairly obvious in monitoring networks with Firepower Management Center. What may be less obvious is that Continents and Countries can also be specified as the source or destination of connections in an Access Control Policy. Basically, this geographical information becomes one more match criteria that can be used to identify traffic for a block or allow action.
To get to this capability, open the Access Control Policy that is in use by the Firepower device. Within the policy, open or create an applicable rule. On the network tab (where you configure the source and destination addresses) a Geolocation tab can also be found. Clicking on this tab exposes Continents and Countries. These can be added as sources and/or destinations.
As can be seen in the diagram above, I am creating a rule to block traffic to France. Before I save and deploy the policy changes to the device, I will confirm reachability to an IP address that exists in that part of Europe.
Last login: Mon Jul 17 11:48:29 on ttys000 PAULS:~ pauls$ Continue reading