How you choose to employ sites when modeling your network may vary depending on the nature of your organization, but generally a site will equate to a building or campus. For example, a chain of banks might create a site to represent each of its branches, a site for its corporate headquarters, and two additional sites for its presence in two colocation facilities.
The site's unique name.
A unique URL-friendly identifier. (This value can be used for filtering.)
The site's operational status.
Additional statuses may be defined by setting
Site.status under the
FIELD_CHOICES configuration parameter.
The parent region to which the site belongs, if any.
Data center or facility designation for identifying the site.
Each site can have multiple AS numbers assigned to it.
The site's local time zone. (Time zones are provided by the zoneinfo library.)
The site's physical address, used for mapping.
The address to use for deliveries destined for the site.
You can also designate points of contact for each site to provide additional contact details.
Latitude & Longitude
GPS coordinates of the site for geolocation.