Difference between revisions of "Node certification"
From CTWUG Wiki
(→Interfaces) |
|||
Line 11: | Line 11: | ||
==Interfaces== | ==Interfaces== | ||
− | *Comments should be in the form of | + | *Comments should be in the form of a;b;c |
+ | Where A is the interfaec, 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-Sektor | **example2: client;512;Mammon-Sektor |
Revision as of 16:35, 4 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.
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-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
Interfaces
- Comments should be in the form of a;b;c
Where A is the interfaec, 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-Sektor