Technical documentation

User Tools

Site Tools

Trace:
menu:design:ip_plans:ipv4_plans

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
menu:design:ip_plans:ipv4_plans [2022/04/29 08:23] – yspeertemenu:design:ip_plans:ipv4_plans [2024/07/03 12:31] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +{{indexmenu_n>6}}
 +
 +===== IPv4 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:ipv4_plans.png?nolink1000|}}
 +
 +Within the current version of netYCE both [[wp>IPv4|IPv4]] and [[wp>IPv6|IPv6]] are supported.
 +
 +===== 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.
 +
 +
 +===== Client types =====
 +
 +{{menu:design:ip_plans:ipv4plans_clienttypes.png?600}}
 +
 +An IP plan can be used with multiple clients. Changing an IP 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_ipv4_subnet_range.png?nolink600}}
 +
 +With the subnets section of the form, the IP plans can be segmented.
 +
 +Using the New button {{general:new.png?nolink}} sign the IP 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.
 +
 +With **Maximum offset** you select the end-point of your (last) subnet.
 +
 +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:ipplans#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 IP subnetplan add form will be opened.
 +
 +{{menu:design:ip_plans:create_ipv4_subnet_plan.png?nolink700}}
 +
 +
 +=== IP address offset ===
 +
 +When adding an  IP address parameter, netYCE will use an offset from the subnet address. When the subnet address is ''<nowiki>192.168.0.0</nowiki>'' with a netmask of ''<nowiki>255.255.255.0</nowiki>'' and the offset is ''<nowiki>0.0.0.2</nowiki>'' the resulting address will be ''<nowiki>192.168.0.2</nowiki>''. When the offset is ''<nowiki>0.0.0.-1</nowiki>'' the resulting address will be the highest available address ''<nowiki>192.168.0.254</nowiki>''.
 +
 +=== Loopback ===
 +
 +Loopback will add two parameters. The first is the offset of ''<nowiki>0.0.0.0</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>0.0.0.1</nowiki>''
 +=== Point-to-point ===
 +
 +Point-to-point will add 8 parameters. two parameters will have an IP offset of ''<nowiki>0.0.0.1</nowiki>'' and two will have an IP offset of ''<nowiki>0.0.0.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:servicetypes|Service tasks]]. This allows you to specify IP ranges within the subnet to be assigned, giving the opportunity to skip certain addresses.
 +
 +{{:menu:design:ip_plans:loopback_range.png?nolink700|}}
 +
 +Which will look like this:
 +
 +{{:menu:design:ip_plans:loopback_subnet_plan.png?nolink1000|}}
 +
 +When using this in the Service type, the reference 'loopback' can be used for IP address assignments. A partial service type is shown that does a locate on the subnet and address.
 +
 +{{:menu:design:ip_plans:loopback_st.png?nolink1000|}}
 +
 +
 +=== 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.
 +
 +In the picture below, it is seen that the subnet range has been specified to start at 0.0.0.4 till 0.0.0.-1 (which means the last address minus 1).
 +
 +{{:menu:design:ip_plans:management_subnetplan.png?nolink1000|}}
 +
 +The service type shows a partial set of commands to use the reference. 
 +
 +{{:menu:design:management_st.png?direct|}}
 +
 +The output of this partial service type is shown below. Where you see the last address is used according to the service type usage.
 +
 +{{:menu:design:ip_plans:management_subnet_output.png?nolink1000|}}
 +
 +== 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.
 +
 +
 +==== Segments ====
 +
 +When selecting a subnet in the //Subnets// section, all the subnets will be listed in the //Segments// section. Individual segments can be deleted. It is possible to delete multiple segments in one action, by selecting multiple entries.
 +
 +Using the //Reindex// button it is possible re-index the segments for a continuous numbering starting at 0.
 +
  
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki