Cisco and Juniper Interoperability : MPLS Layer 3 Virtual Private Network Between Cisco and Juniper
Ogenda, Dancun (2016)
Metropolia Ammattikorkeakoulu
2016
creative commons attribution 1.0 finland
Julkaisun pysyvä osoite on
https://urn.fi/urn:nbn:fi:amk-201605168024
https://urn.fi/urn:nbn:fi:amk-201605168024
Tiivistelmä
The goal of this project was to design, implement and verify a MPLS Layer 3 Virtual Private Network. The task included building a functioning MPLS Network that consists of the MPLS Backbone together with a Customer Edge and the Customer Site equipment’s. The MPLS Backbone was to consist of the Provider Devices and the Provider Edge devices, which is used as a connection point to the Customer Edge devices. The MPLS was to only function inside the MPLS Backbone and the Provider devices were to be connected using internal BGP. For the connection between the Provider Edge and the Customer Edge, external BGP protocol was to be used.
MPLS is basically a standard used in the speeding of the delivery of packets across different platforms. By using MPLS, the area that is in the MPLS Backbone is connected using the internal BGP. This is the only area that the MPLS information is to be communicated. For the area between the Provider Edge and the Customer Edge, external BGP protocols is to be used and does not need any MPLS information or configuration. Then it is needed for an MPLS Layer 3 VPN to be built above the MPLS network; which is normally from the Service Provider. This Layer 3 VPN is used to deliver and ensure connectivity between different customers in varied geographical locations. The next task is to assume that either of two PE equipment is running the Juniper´s JunOS or Cisco IOS. This then necessitates the configuration to make the two, which can either be a router and a switch to communicate with each other and thus allow flow of packets between them.
The result of the project was that after the configurations, it was possible to get a connection from the Switch/Router running JunOS and the Switch/Router running the Cisco IOS. The goal of the project was further to delve into and achieve an end-to-end connectivity between the L3VPN´s configured on either side of the CE. This goes to prove that even though different entities might be using different networking equipment from different vendors, it is possible to make the devices communicate with or to each other and thus provide a seamless flow of traffic/packets as if the same producer made them.
MPLS is basically a standard used in the speeding of the delivery of packets across different platforms. By using MPLS, the area that is in the MPLS Backbone is connected using the internal BGP. This is the only area that the MPLS information is to be communicated. For the area between the Provider Edge and the Customer Edge, external BGP protocols is to be used and does not need any MPLS information or configuration. Then it is needed for an MPLS Layer 3 VPN to be built above the MPLS network; which is normally from the Service Provider. This Layer 3 VPN is used to deliver and ensure connectivity between different customers in varied geographical locations. The next task is to assume that either of two PE equipment is running the Juniper´s JunOS or Cisco IOS. This then necessitates the configuration to make the two, which can either be a router and a switch to communicate with each other and thus allow flow of packets between them.
The result of the project was that after the configurations, it was possible to get a connection from the Switch/Router running JunOS and the Switch/Router running the Cisco IOS. The goal of the project was further to delve into and achieve an end-to-end connectivity between the L3VPN´s configured on either side of the CE. This goes to prove that even though different entities might be using different networking equipment from different vendors, it is possible to make the devices communicate with or to each other and thus provide a seamless flow of traffic/packets as if the same producer made them.