Differences

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

--- menu:design:ip_plans:ipv6_plans [2022/04/29 09:05] – yspeerte
+++ menu:design:ip_plans:ipv6_plans [2024/07/03 12:31] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+{{indexmenu_n>7}}
+===== IPv6 plans =====
+IP plans are at the heart of each IP network. The first step after creating a  [[menu:design:client_types|Client type]] is the modeling of the IP plans.
+{{menu:design:ip_plans:ipv6_plans.png?nolink1000|}}
+Within the current version of netYCE both [[wp>IPv4|IPv4]] and [[wp>IPv6|IPv6]] are supported. This page details the creation of IPv6 plans.
+===== IP plans =====
+IP plans are essentially supernets with a reference number and a subnet mask. The supernet will be divided into one or more subnets (segments). A [[menu:inventory:main:main|client]] can have one or more supernets associated. This applies for both IPv4 subnets and IPv6 subnets. The two types are not linked, and can be used completely independently.
+===== Client types =====
+{{menu:design:ip_plans:ipv4plans_clienttypes.png?nolink600}}
+A single IPv6 plan can be used with multiple clients. Changing an IPv6 plan should be done with extreme caution. The client types section of the form will show the client types associated with the selected IP-plan.
+===== Subnets =====
+{{menu:design:ip_plans:create_ipv6_subnet_range.png?nolink800}}
+With the subnets section of the form, the IPv6 plans can be segmented.
+Using the New button {{general:new.png?nolink}}sign the IPv6 plan subnet add form is opened and one or more ip subnets can be added.
+By default, the subnets will be added with a 24 bits subnet. This can be changed by typing the prefix, or using the arrows.
+Each subnet must have a name. A good practice is to make a reference to the function of the subnet, such as management, voice, data, ppp etc. When needed a remark can be added.
+With **'Minimum offset' ** you can select the starting point of your (first) subnet. You can offset this with the single arrows of the offset size per click. If you need to take bigger steps, you can use the double arrows, to make steps increase by a number of bits, equal to the number in the Step_size field.
+With **'Maximum offset'** you select the end-point of your (last) subnet. The single arrows take sequential steps, the double arrows take exponential steps, in order to get to your maximum offset.
+The offset fields are intentionally not editable, this makes sure that no crazy offsets can be chosen. To overcome lots of clicking when a big free space exists in the plan, create as big as possible 'Free' ranges so that the first free offset is near the requested one. After creating the latter subnets you can remove the [[menu:design:ip_plans#segments|segments]] of the 'Free' subnets.
+==== Subnet plan ====
+In the Subnet plan tab, the subnet can be modeled. Here the Default-gateway, VLAN ID etc can be defined. By clicking {{general:new.png?nolink}}the IPv6 Subnet Plan add form will be opened.
+{{menu:design:ip_plans:create_ipv6_subnet_plan.png?nolink800}}
+=== IPv6 address offset ===
+When adding an  IPv6 address parameter, NetYCE will use an offset from the subnet address. So for example, if the subnet address is ''<nowiki>::1</nowiki>'' and the offset is ''<nowiki>::1</nowiki>'', then the resulting address will be ''<nowiki>::2</nowiki>''.
+=== Loopback ===
+Loopback will add two parameters. The first is the offset of ''<nowiki>::</nowiki>'' which means 0 bits offset from the subnet IP and number two is a topology position of **L**. This topology position will be assigned to the port.
+=== Gateway ===
+Gateway will add one parameter. An IP offset of ''<nowiki>::1</nowiki>''
+=== Point-to-point ===
+Point-to-point will add 8 parameters. Two parameters will have an IP offset of ''<nowiki>::1</nowiki>'' and two will have an IP offset of ''<nowiki>::2</nowiki>''. Also topology positions A (left), B (right), N (north) and S (south) will be added.
+=== Four-corners ===
+=== Vlan ===
+VLAN will add two parameters. The scope of the VLAN whether it should be Site specific, Client specific or Service specific. The other parameter is the VLAN template. Here a VLAN [[guides:reference:templates:porttemplate|configuration template]] can be used.
+When adding a VLAN, the user must make a choice whether to have a range or a fixed VLAN ID.
+== Range ==
+When choosing //Range//, two parameters will be added. The minimum- and maximum offset of the VLAN ID. The maximum offset must be higher than the minimum. The range is between 1 and 4094.
+== Fixed ==
+When choosing //Fixed//, one parameter will be added. This is the VLAN ID.
+=== Loopback reference ===
+It is possible to make a named reference to the loopback address. This is useful when using [[menu:design:service_types|Service types]] and using [[menu:build:templates:template_edit|Templates]]
+=== Management reference ===
+In order to force a specific IP address (or range of addresses) it is possible to use a named reference. This reference can be used in the same way as the loopback reference.
+== Range ==
+The //Range// will add the //Scope// parameter, the //Topology// parameter and a minimum- maximum offset parameter. The Topology parameter can't be modified. The Scope can be Site (default) and Global.
+== Fixed ==
+The //Fixed// will add the //Scope// parameter, the //Topology// parameter and a fixed offset parameter. The Topology and Site parameter are the same as the Range setting.