My Linux

Using Zebra Routers with Looking Glass The syntax for the Zebra Router is provided with the configuration file. Adding devices is very simple- vim /var/www/html/lg/lg.conf <!-- Zebra Router Section --> <Router Name="Zebra-1 " OSType = "Zebra"> <Title>Zebra-1</Title> <URL>telnet://pass@IP:port </URL> <!--EXAMPLE <URL>telnet://login:123456@192.168.1.1:2601,2605</URL> --> </Router> Issues with Trace and Ping  I was not able to use Trace or Ping using Zebra router as the commands are not built in with Zebra. However, the BGP commands should work without any problems. Ping Using Zebra Trace Using Zebra  Hope this helps :)

Setting Up Looking Glass  Background  A looking glass is a server that allows someone from outside the network to get information about the how traffic is routed through the network backbone of an organization. For example, suppose Alpha Corp. has one router in the US and another in Australia. An outside user wants to know how traffic towards Japan is routed from both of these Routers. As the user does not have credentials to the Routers, he cannot run traceroutes. The solution: a Looking Glass. If Alpha Corp. has a looking glass, the user can query about ping, trace, BGP and other information through the web-based looking glass without needing to authenticate to the actual router. Setting Up  Before we start please make sure SELinux is disabled. Also, iptables should allow the required ports, from the top of my head – 23, 2601, 2605, 80.  Phase 1: Working YUM Server  Make sure that your server has access to a good yum server, preferably repoforge. In...

Finding proper documentation on OTRS has been difficult for me so far. Maybe the reason behind this is, OTRS supports tons of great features, and to document everything that can be done is difficult. Nonetheless, OTRS is a fantastic software. Recently, our company needed to add some columns in the OTRS backend database. As I work in a company that deals with the Internet, we needed to integrate customer bandwidth and prefix information to OTRS database. After some stumbling and trial and error, here's what can be done - Part 1: Creating the columns mysql -p mysql> use otrs; mysql> ALTER TABLE customer_user ADD bandwidth VARCHAR (50); mysql> ALTER TABLE customer_user ADD prefix VARCHAR (250); mysql> quit; Part 2: Tuning OTRS vim /opt/otrs/Kernel/Config/Defaults.pm ## And we add the following lines [ 'UserBandwidth', 'Bandwidth', 'bandwidth', 1, 0, 'var', '', 0 ], [ 'UserPrefix', 'Prefix', ...

Recently, I have setup an observium server for our office. After about two weeks of operation, here's what I think of them- Observium Pros: Has thousands of templates. Auto discovers which templates are applicable for a host Comparatively better interface Cons: Comparatively more processor intensive. Does not work without DNS (/etc/hosts tuning is helpful) Adding users and controlling view can be tricky The bandwidth graph of cacti is better I could not find any "zoom" feature for the graphs Cacti Pros: Very good for bandwidth graphs. Very good for user portals and controlling user views. Easily customizable graph trees Cons: No auto discovery feature Adding new templates can be tricky, very tricky. Needs 64 bit counters for bandwidth graphs over 100 Mbps. Learnt it the hard way.