(Side note, this blog post was written and then forgotten about quite a while ago, So I’ve finished it off, it was halfway done.)
While on holiday in the evenings with downtime to spare, I had realised that
This blog post outlines what “MPLS VPNs over mGRE” is all about as well as provide an example of such a configuration.
So what is “MPLS VPNs over mGRE”? – Well, basically its taking regular MPLS VPN’s and using it over an IP only core network. Since VPN’s over MPLS is one of the primary drivers for implementing an MPLS network in the first place, using the same functionality over an IP-only core might be very compelling for some not willing/able to run MPLS label switching in the core.
Instead of using labels to switch the traffic from one PE to another, mGRE (Multipoint GRE) is used as the encapsulation technology instead.
Be advised that 1 label is still being used however. This is the VPN label that’s used to identify which VRF interface to switch the traffic to when its received by a PE. This label is, just as in regular MPLS VPN’s, assigned by the PE through MP-BGP.
So how is this actually performed? – Well, lets take a look at an example.
The topology I will be using is as follows:
Topology for MPLS VPN’s over mGRE
** Note: I ran into an issue with VIRL, causing Continue reading
You cannot promote the (true) idea that security research benefits humanity while defending research that endangered hundreds of innocents— Alex Stamos (@alexstamos) May 16, 2015I would like to take the opportunity to let you all know that Keeping It Classless will be moving to a different blogging platform in the near future. For the vast majority of you, this will not be a problem. My intent is to keep as much as possible consistent between moves.
However, some of you subscribe to my blog using some WordPress-specific features such as email subscription, as well as following me through the WordPress service itself. After the move, these services will have no way of being updated. If this applies to you, please check out the following options:
Eric in a mitre. Cricket protein. Micro wind turbines. Stash your cash. Blue crude. RF into power. Wikimedia's money. Carly for POTUS. A racing simulator that can kill you. All this and more on this week's Citizens of Tech.
The post Citizens of Tech 003 – Racing Cricket Phone Turbines appeared first on Packet Pushers.
Eric in a mitre. Cricket protein. Micro wind turbines. Stash your cash. Blue crude. RF into power. Wikimedia's money. Carly for POTUS. A racing simulator that can kill you. All this and more on this week's Citizens of Tech.
The post Citizens of Tech 003 – Racing Cricket Phone Turbines appeared first on Packet Pushers Podcast and was written by Ethan Banks.
I would like to take the opportunity to let you all know that Keeping It Classless will be moving to a different blogging platform in the near future. For the vast majority of you, this will not be a problem. My intent is to keep as much as possible consistent between moves.
However, some of you subscribe to my blog using some WordPress-specific features such as email subscription, as well as following me through the WordPress service itself. After the move, these services will have no way of being updated. If this applies to you, please check out the following options:
I will continue to link to each new blog post to my social media accounts, such as Twitter, Facebook, Google+, and LinkedIn. Follow me at whichever you prefer, and you’ll get all new posts in the relevant news feed. I will continue to provide an RSS feed at http://keepingitclassless.net/feed/. Currently this redirects to feedburner, which is likely what you have in your RSS reader, if you’ve already done this. The transition away from WordPress will break this automatic redirection, but don’t worry – feedburner will continue to deliver post updates to you, at least until I move off Continue reading
This week’s lesson: Be consistent with your vendor naming when working with HP IMC Custom Device Adapters. When you create the new adapter directory, use exactly the same vendor name as used within the UI. Otherwise IMC may not recognise your new adapter. Case matters too, even on Windows!
HP IMC ships with a set of “Device Adapters” that define functions such as backups, configuration deployment, firmware upgrades, etc. These adapters are sets of XML, TCL and Perl files. They define which devices are supported, for what functions, and how to execute those functions.
Obviously HP can’t support every device ever made. But they’re quite happy for you to write your own adapters, or extend the ones they have. So if you’ve got a few unsupported switches, and they have some sort of sensible interface, you can write your own adapters.
These are stored at /server/conf/adapters/ICC/. Under there, you have a set of folders for each vendor. Under each vendor folder is an adapter-index.xml file, which maps SNMP sysOIDs to adapters. You must have a mapping in the adapter-index.xml file for your sysOID. (nb you can use wildcards). If those XML files change, you need to restart IMC.
Giddy up, news! It's time for the SDxCentral roundup!
The Rayno Report and Oracle are teaming up for an exclusive webinar on SDxCentral. Don't miss out -- sign up now!
