NETS header NETS Homepage UCAR Homepage NCAR Homepage CISL Homepage NETS Homepage About NETS Work requests & support
 (what is this?)
 (what is this?) 

The NETS Reserved Address Standard - 08/17/11


This document provides guidelines for the gateway and router addresses defined for each subnet. Having a standard to follow eases troubleshooting and general network management.

NETS uses Hot Standby Routing Protocol (HSRP) as one way to improve network availability. This protocol provides network redundancy by ensuring that user traffic immediately and transparently recovers from first hop failures in network edge devices or access circuits.

HSRP works by sharing an IP address and a MAC (Layer 2) address with two or more routers, allowing a group of routers to act as a single 'virtual' router. The members of this virtual router group continually exchange status messages. This way, one router can assume the routing responsibility of another, should it go out of commission for either planned or unplanned reasons. Hosts continue to forward IP packets to a consistent IP and MAC address, and the changeover of devices doing the routing is transparent.

For more information on this topic
http://www.networksorcery.com/enp/protocol/hsrp.htm

Some existing subnets use 'grandfathered' addresses. All new subnets will be created using this standard. Documentation of the defined gateway for specific subnets is found on the vlans and subnets pages.

NETS reserved addresses

For the purposed of routing, NETS reserves the following addresses within a /24 subnet:

If these addresses are not available, NETS will work with the division to determine appropriate settings. The router addresses will then be documented on the vlans and subnets pages.

Other addresses in a subnet with specific functions:

Router DNS entries

NETS also requests DNS entires for these addresses using this convention:

(campus)router-n(subnetnumber).ucar.edu

These examples are for a subnet on the Mesa

DNS Contact

The information provided in the DNS contact field for the vlans and subnets pages is pulled directly from DNS per UCAR conventions. Specifically by querying the SOA record for the subnet using 'dig'.

For example:

dig soa -x 128.117.45.0

; <<>> DiG 9.2.4 <<>> soa -x 128.117.45.0
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3579
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;0.45.117.128.in-addr.arpa. IN SOA

;; AUTHORITY SECTION:
117.128.in-addr.arpa. 0 IN SOA dns.ucar.edu. postmaster.ucar.edu. 200706121 28800 14400 604800 172800

;; Query time: 1 msec
;; SERVER: 128.117.64.11#53(128.117.64.11)
;; WHEN: Fri Jun 15 09:59:34 2007
;; MSG SIZE rcvd: 102


Address comments or questions about this Web page to the Network Engineering & Telecommunications Section (NETS) at nets-www@ncar.ucar.edu. The NETS is part of the Computational & Information Systems Laboratory (CISL) of the National Center for Atmospheric Research (NCAR), which is sponsored by the National Science Foundation (NSF). Any opinions, findings and conclusions or recommendations expressed in this publication are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. NCAR is managed by the University Corporation for Atmospheric Research (UCAR). This website follows the UCAR General Privacy Policy and the NCAR/UCAR/UCP Terms of Use.