Skip to content
Snippets Groups Projects
Verified Commit 46747917 authored by Karel van Klink's avatar Karel van Klink :smiley_cat:
Browse files

Add node provisioning

parent 5b536769
No related branches found
No related tags found
2 merge requests!6[2023-07-14] publish docs,!3Add documentation contents
...@@ -67,7 +67,7 @@ peer-reviewed and approved. ...@@ -67,7 +67,7 @@ peer-reviewed and approved.
- - - - - -
## Orchestration and service DB ## Orchestration and service database
All services offered can be summarised in the following four categories. Some examples are given in the table below. All services offered can be summarised in the following four categories. Some examples are given in the table below.
......
# Glossary of terms # Glossary of terms
{.glossary} {.glossary}
BGP
: Border Gateway Protocol
CFS CFS
: Customer Facing Service : Customer Facing Service
eBGP
: External {term}`BGP`
GA GA
: Access Port : Access Port
GAN GAN
: Access Node : Access Node
GAP
: GÉANT Automation Platform
GP GP
: Physical Port : Physical Port
iBGP
: Internal {term}`BGP`
IFS IFS
: Interface Facing Service : Interface Facing Service
...@@ -22,5 +34,8 @@ MPLS ...@@ -22,5 +34,8 @@ MPLS
MTTR MTTR
: Mean Time To Repair : Mean Time To Repair
PoP
: Point of Presence
SDP SDP
: Service Delivery Point : Service Delivery Point
# GÉANT Automation Platform (GAP) # GÉANT Automation Platform ({term}`GAP`)
Welcome to the documentation of the GÉANT Automation Platform, or GAP for short. \ Welcome to the documentation of the GÉANT Automation Platform, or {term}`GAP` for short. \
The focus of this platform is configuration management and service orchestration for the GÉANT IP/MPLS network. The focus of this platform is configuration management and service orchestration for the GÉANT IP/{term}`MPLS` network.
## Table of contents ## Table of contents
```{toctree} ```{toctree}
overview/index.md overview/index.md
architecture/index.md architecture/index.md
processes/node_provisioning.md
processes/deploy_router.md
glossary.md glossary.md
``` ```
# Node provisioning
This section describes the mechanics for deploying a new node in the GÉANT network. A node can either be a router, a
switch, or a terminal server.
In general -- as laid out more extensively
[here](https://wiki.geant.org/display/NETENG/001+-+Topology+and+physical+layout) (behind login) -- a {term}`PoP`
consists of:
* One or two routers
* One switch
* One terminal server
Globally, the workflow for a new site is as follows:
1. Deploy terminal server:
1. Generate base configuration from GitLab
2. Ship the device to its location
3. Verify reachability and insert in LibreNMS
2. Deploy {term}`PoP` router in a 'core' fashion
1. Rack it up and configure the hardware
2. Connect the router to the terminal server via both a console connection, and FXP
3. Deploy base configuration using {term}`GAP`
3. Deploy {term}`PoP` switch
1. Rack it up and configure the hardware
2. Connect the switch to the terminal server via both a console connection, and FXP
3. Deploy base configuration using {term}`GAP`
4. Deploy the {term}`PoP` interconnect between router and switch
1. Set up a physical connection between router and switch
2. Deploy configuration using {term}`GAP`
5. Deploy IP trunks to connect the router to the rest of the network
1. Set up a physical connection
2. Deploy configuration using {term}`GAP`
6. Update the {term}`iBGP` mesh to include the new router, promoting it to an edge router
1. Deploy configuration using {term}`GAP`
2. Using {term}`GAP`, insert the devices in LibreNMS
In the context of the automation platform, the {term}`PoP` interconnects mentioned are modeled as separate objects.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment