Difference between revisions of "Node certification"
From CTWUG Wiki
| Line 6: | Line 6: | ||
* Routerboards must be named in sequency as rb, rb2, rb3, ect | * Routerboards must be named in sequency as rb, rb2, rb3, ect | ||
** This means that if you have one routerboard it would be called rb.node.ctwug.za.net, if you have another it would be called rb2.node.ctwug.za.net | ** This means that if you have one routerboard it would be called rb.node.ctwug.za.net, if you have another it would be called rb2.node.ctwug.za.net | ||
| − | * OSPF link names Must be in the format of 'link-remotenodename.localnodename.ctwug.za.net' | + | * OSPF link names Must be in the format of 'link-to-remotenodename.localnodename.ctwug.za.net' |
* Network and Broadcast IPs must be filled in aswell. For example network.thefox.ctwug.za.net and broadcast.thefox.ctwug.za.net | * Network and Broadcast IPs must be filled in aswell. For example network.thefox.ctwug.za.net and broadcast.thefox.ctwug.za.net | ||
* All IPS should be given a DNS name, those without hosts on, should be called unusedX where the X is an increasing number starting with 1. | * All IPS should be given a DNS name, those without hosts on, should be called unusedX where the X is an increasing number starting with 1. | ||
| Line 12: | Line 12: | ||
==RouterOS Config== | ==RouterOS Config== | ||
===General Setup=== | ===General Setup=== | ||
| − | *Identity should | + | *Identity should follow the dns name convention |
| − | **example1: | + | **example1: rb.cervantes |
| − | **example2: | + | **example2: rb14.tfyre |
| + | |||
===Interfaces=== | ===Interfaces=== | ||
*Comments should be in the form of a;b;c | *Comments should be in the form of a;b;c | ||
| − | Where A is the | + | Where A is the interface, bb or client, B is the speed the queue should be, ex: 128, 512, 1024, and C is the rest of the comment. |
**example1: bb;1024;TheFox-Mammon-link | **example1: bb;1024;TheFox-Mammon-link | ||
| − | **example2: client;512;Mammon- | + | **example2: client;512;Mammon-Sector |
| + | |||
| + | This is critical to make game time work correctly. | ||
=Hardware Section= | =Hardware Section= | ||
Revision as of 21:11, 30 September 2012
The Idea behind this is so we can get some form of quality control on our node setups. From wind to routerOS configuration. There are a lot of variances on how we do things, and hopefully we can come to a obvious and logical setup. It must also be functional.
Contents
Software Section
DNS Names
- Routerboards must be named in sequency as rb, rb2, rb3, ect
- This means that if you have one routerboard it would be called rb.node.ctwug.za.net, if you have another it would be called rb2.node.ctwug.za.net
- OSPF link names Must be in the format of 'link-to-remotenodename.localnodename.ctwug.za.net'
- Network and Broadcast IPs must be filled in aswell. For example network.thefox.ctwug.za.net and broadcast.thefox.ctwug.za.net
- All IPS should be given a DNS name, those without hosts on, should be called unusedX where the X is an increasing number starting with 1.
RouterOS Config
General Setup
- Identity should follow the dns name convention
- example1: rb.cervantes
- example2: rb14.tfyre
Interfaces
- Comments should be in the form of a;b;c
Where A is the interface, bb or client, B is the speed the queue should be, ex: 128, 512, 1024, and C is the rest of the comment.
- example1: bb;1024;TheFox-Mammon-link
- example2: client;512;Mammon-Sector
This is critical to make game time work correctly.
