This website has been translated by machine translation software and has not been subsequently revised by translators. Further information at: link. Hide
the accesskey _ mod _ content
-

Routing Plan and interconnection of networks in the administration

  • Functional description

    Para lograr la coordinación entre las AAPP se generarán unas tablas con los rangos de dirección IP asignados a cada Administración.

    Technical Description

    Solution:

    The Routing Plan and interconnection of networks in the administration se basa en el establecimiento de un directorio de direcciones de red IP, a partir del cual cada entidad u organismo pueda establecer de manera independiente sus planes de numeración IP, en función de su infraestructura de red, o distribución orgánica o departamental, pero manteniendo una coordinación que evite el uso de direcciones duplicadas. Las consideraciones básicas que se han tomado como punto de partida son:
     

    1. The routing plan takes into account the forecast that medio-largo run all units of the administration could count on local networks. Each local network of a centre will operate as a subnet inside the global network of administration.
    2. Set a routing system according To Class, adopting the range of addresses 10.0.0.0 to 10.255.255.255 - private use of the administration as recommended in the document RFC 1597.
    3. To simplify the configuration of networks and routing procedures you can choose to use network masks 24-bit, with which it is possible to define separate subnets 64516 with capacity equivalent to that type (C networks can connect up to 254 10 nodes by segment. With this approach the netmask that uses any equipment would be 255.255.255.0 regardless of their physical location. However since most current teams on the use of masks variables, it is recommended reading detailed RFC-1219 "on the assignement of please numbers (April 1991)" presenting the concepts of bits of growth (grouth bits) whose application allows routing plans very flexible. It is also important to take into account the concepts of aggregation of networks "superneting" when distributing the numbering in each centre, according to the actual topology to simplify network routing tables.
    4. The initial distribution of routing space is centrally by the secretariat of the High Council of E-government depending on the needs of each centre Manager taking into account criteria of organization, flexibility and streamlining. Once assigned a range of addresses will be the responsibility of the center determine how to use them and establish a plan of routing own that takes into account the characteristics of your IT infrastructure and communications.
    5. The last group of bits allocated to the identification of the Host (typically 8 in class (C) will be used ascending to allow potential "subnetings" future in areas not yet assigned (RFC 1219).
       

    To facilitate the management of teams are recommended to book addresses values low for servers and communications equipment.

    The numbering of the user equipment, typically personal computers and workstations, will begin above that value.

    For example, if you are using a subneting 8 bits attached to the direction of node (former class (C) a recommendation could be the allocation of decimal number "10" the router main communications network and descending from there (9, 8, 7) for other special teams, leaving the numbers 1 to 5 to host that offer comprehensive services. The allocation to the rest of the teams to begin in the number "11" ascending.

    This tool allows you to fill in the allocation the first addresses within the range and make free recent groups of directions for possible segmentation and use in other networks that need it.

    In order to ensure a correct network administration, it is necessary to permanently monitor numbering plan in each subnet and updating the documentation of changes that occur in the same for this, it is recommended to develop a table similar to the collection in this document, through the collected regularly, and for each unit, the allocation of directions done in each subnet.

    Standards:

    • RFC 1597
    • RFC 1219
Maintainer

Interesting links Solutions