Le Wiki Koumbit
This server does routing for the main cabinet. It is connected to sw2-canix2.koumbit.net.
It also has reliability issues and is being reconsidered as a router, it might become a node in the LoadBalancing pool. In the meantime, we're rebuilding a new rtr2-canix2.koumbit.net. -- TheAnarcat 2008-04-14 17:04:36 EST
Contents
Name 
Le serveur doit avoir un nom, préférablement en respect de la ConventionDeNoms.
Hardware specifications
Casing: 1U Mendax 1035
Motherboard: Intel server S3000AHLX (S300AH series)
- CPU
- Celeron D
- Core memory
- 512 MB
- 512 MB
- ? empty sockets?
- PCI, 1 free PCI socket
- IDE channel 1: 2x160G
- power supply: ?
- available hard drive room: ?
- fans: noisy, at least 3 by the looks of the BIOS
vu de derrière, l'interface de droite, au dessus des ports USB, est em0. L'autre, à gauche, est em1.
Technical details
- Name
- rtr1-canix2.koumbit
- Function
- routing for the main cabinet
- Location
- IP externe
- 64.15.66.18
- IP interne
- 209.44.112.1, 209.44.112.65/26, 209.44.112.129
- Customer
- Koumbit
- Status
- Activation
- 2007-11-15 18:17:13 EST
- Photo
- Cost
- $1,063.78CAD
- OS
- OpenBSD 4.2
- Configuration management
See 8955 for the process of buying the server.
Configuration details
Some of the configuration was originally in Puppet but we're actually phasing that out since it's a so simple/critical piece of infrastructure.
Networking
The external interface (em0) takes the netelligent routing ip (64.15.66.18).
The "internal" (em1) interface is configured as 209.44.112.1. We have two VLANs configured on top of that: vlan 1 and 60. rtr1 grabs 209.44.112.65 on vlan1 and .129 on vlan60. vlan2 (209.44.112.1) is "native" so it,s not encapsulated (hence directly on the em1 interface.
Packet filtering
See PF.
Load balancing
rtr1 also performs load balancing for our services. It's currently not working. It is configured through /etc/hoststated.conf.
Voir LoadBalancingService.
Puppet deployment/conversion
Since puppet is in the cabinet, and our router is configure to route those addreses locally, I hacked a static route to allow the router to find the machine:
route add 209.44.112.80 -host 72.0.207.113
This route is now configured in puppet.
A network module was written for puppet that supports VLAN configuration.
Configuration du BIOS
- POST Error Pause
- disabled
- After power failure
- Power on
- Advanced > IDE Controller > Configure SATA as RAID
- disabled
- Boot options > Boot timeout
- 3
Notable default configurations
- Execute Disable Bit
- Enabled
- SATA Mode
- Enhanced
- Auto Fan Control
- on
Misc information
Network controllers
- Intel 82573E GbE
- Intel 82541PI GbE
Hardware sensors
read in the small office where it is quite cold:
- CPU
- 34C
- System
- 29C
- DIMM
- 18
- Fan2
- 6659 rpm
- Fan3
- 7356 rpm
- Fan4
- 12272 rpm
I spare you the voltages. The machine is quite noisy.
Console redirection
It seems the BIOS supports some kind of serial console redirection.
Serial numbers
- Motherboard
- Manufacture
- Intel
- Product name
- S3000AHLX
- Version
- D40858-207
- Serial number
- AZAX71700612
- Box: MDX-6355
Backups
dump(8)/restore(8) backups being configured.
Configuration
The backups are configured in /etc/crontab to mirror all partitions to backup.koumbit.net every first of the month and to incremental every first day of the week. The script is in /root/bin/sync.sh and is fairly trivial.
The funky crontab is a bit less trivial and relies on a special algorithm (taken from this manpage to record only minimal incremental changes.
# backups # monthly 0 4 1 * * /root/bin/sync.sh 0 # weekly 0 3 * * 0 /root/bin/sync.sh 1 # dailys # tower of hanoi algorithm: 3 2 5 4 7 6 9 8 0 3 * * 1 /root/bin/sync.sh 3 0 3 * * 2 /root/bin/sync.sh 2 0 3 * * 3 /root/bin/sync.sh 5 0 3 * * 4 /root/bin/sync.sh 4 0 3 * * 5 /root/bin/sync.sh 7 0 3 * * 6 /root/bin/sync.sh 6
Restore
Backups can be accessed using the restore utility:
# env RSH=ssh restore -i -f backup-rtr1-canix2@backup.koumbit.net:/backup/rtr1-canix2.koumbit.net/dump/root.0
restore > ls
.:
.cshrc boot dev/ root/ tftpboot/
.profile bsd etc/ sbin/ tmp/
altroot/ bsd.original home/ stand/ usr/
bin/ bsd.rd mnt/ sys@ var/
restore > ?
Available commands are:
ls [arg] - list directory
cd arg - change directory
pwd - print current directory
add [arg] - add `arg' to list of files to be extracted
delete [arg] - delete `arg' from list of files to be extracted
extract - extract requested files
setmodes - set modes of requested directories
quit - immediately exit program
what - list dump header information
verbose - toggle verbose flag (useful with ``ls'')
help or `?' - print this list
If no `arg' is supplied, the current directory is used
restore > what
Dump date: Tue Mar 18 13:40:02 2008
Dumped from: the epoch
Level 0 dump of / on rtr1-canix2.koumbit.net:/dev/raid0a
Label: none
restore > cd etc
restore > add motd
restore > extract
You have not read any tapes yet.
Unless you know which volume your file(s) are on you should start
with the last volume and work towards the first.
Specify next volume #: 1
set owner/mode for '.'? [yn] n
restore > quit
Reboot times
- boot with a wake-on-lan: 88 secondes avant le ping
Services
Historique
- 2007-11-15 13:30:13 EST Réception à la bande passante
- 2007-11-15 18:00:27 EST configuration du BIOS
- 2007-11-15 18:23:27 EST
- 2007-11-16 18:52:12 EST
Applied the two first security patches found in the 4.2 Errata
- 2007-11-22
switching to /root/ChangeLog for those notes
Interventions
Hardware
Software
Subpages
| /ToDo |