LDAP: couldn't connect to LDAP server

Differences

This shows you the differences between two versions of the page.

--- menu:build:mpls_vpns [2019/12/23 11:53] – external edit 127.0.0.1
+++ menu:build:mpls_vpns [2022/05/20 16:17] (current) – [MPLS_type] yspeerte
@@ Line 1: / Line 1: @@
+{{indexmenu_n>5}}
+====== MPLS vpns ======
+Within the [[wp>Multi-protocol_Label_Switching|MPLS]] VPN form, it is possible to define MPLS VPN's. Instead of fixed values, it's possible to use [[menu:build:templates:template_edit|parameterized]] values. \\
+Although the term MPLS is used, this form and the information stored can also be used as a [[wp>Virtual_Routing_and_Forwarding#Simple_implementation|VRF lite]] configuration.
+{{menu:build:mpls:mpls_vpns_definitions.png?nolink&1000}}
+===== VRF id =====
+The [[wp>Virtual_Routing_and_Forwarding|VRF]] id is used as a reference value within the system. It is possible to use this parameter within the configuration. This id is not the individual id for a VRF on a device, but the ID for this type of VRF on all devices.
+===== VRF name =====
+The actual name of the VRF. This can be parameterized, so it will have a name related to the device it is provisioned on.
+===== Client type =====
+The [[menu:design:client_types|Client type]] where this VRF can be used.
+===== VRF AS =====
+The [[wp>Autonomous_System_|Autonomous System]] number which will be used within the VRF configuration.
+===== VRF Route distinguisher =====
+The [[wp>Route_distinguisher|Route distinguisher]] used for this configuration. When using a VRF lite configuration, this setting is not necessary. We would recommend ''<nowiki>global.unique.ipv4.address.pe+vrf_id</nowiki>'' (([[http://blog.ipspace.net/2012/07/bgp-route-replication-in-mplsvpn-pe.html|http://blog.ipspace.net/2012/07/bgp-route-replication-in-mplsvpn-pe.html]])) as the route distinguisher. This setting had the highest probability of being global unique.
+===== VRF Route target =====
+The [[http://packetlife.net/blog/2013/jun/10/route-distinguishers-and-route-targets/|route target]] used for this configuration. Again, when using VRF lite, this setting is not necessary.
+===== MPLS option 1 =====
+Additional MPLS options, which is free format. This could be used for any value. Such as maximum route statements, or additional route target import or exports.
+===== MPLS option 2 =====
+Same as MPLS option 1.
+===== MPLS_management =====
+Set this option to 1 in case this VRF will be used for management, NetYCE will use the name entered at the //VRF name// field when transferring files for the following vendors: HP Comware 7, Huawei.
+===== MPLS_type =====
+To assist creating categories of Node VRFs, Mpls_types and Vrf_types can be used. These values are set in the [[menu:admin:setup:settings|General settings]].
+The values for these attributes are defined in the 'Lookup' using the 'Mpls_type' variable of the 'Translation' class. As many entries as desired can be created using this lookup variable. These values will be presented as drop-down menu lists from which one value can be selected.