So far... this is my configuration file for dns...
$TTL 18600ngn.com. IN SOA fir.ngn.com. root.fir.ngn.com.
ngn.com. IN NS fir
ngn.com. IN A 195.10.10.200
fir IN A 195.10.10.200
www IN A 195.10.10.200
BR1 IN A 10.1.1.1
BR2 IN A 10.1.1.2
AR2 IN A 10.1.1.3
AR1 IN A 10.1.1.4
mail IN A 195.10.10.200
ngn.com. IN MX 10 fir
DNS has been pointed to my eth1 ip address which is static...
ip address of 195.10.10.200
eth0 is still dhcp.
Wednesday, April 29, 2009
NFSEN
The NFsen is running successfully now. It is now able to show and track the flows in each switches. (BR1, BR2, AR1, AR2)
Traffic and packet flows in the form of bits per second and packets per second respectively are plotted with the form of graph.
All the information is being captured from BR1, BR2, AR1, AR2. Individual data is edited and entered into the "nfsen.conf' file.
%sources = (
'BR1' => { 'port' => '9999', 'col' => '#0000ff', 'type' => 'netflow' },
);
some useful sites for the configuration of NFSen : http://www.oneunified.net/blog/OpenSource/Debian/Monitoring/nfsen.article
A look of how the NFSen looks like
In the next few days, we'll be continuing working on additional add-ons into our server like tacacs, nagios etc..Wednesday, April 22, 2009
The NFSen has already been setup. However, the full graph still hasn't showed up correctly due to some unknown reasons which we are still trying to figure out.
Here are some websites which we've refered to: http://nfsen.sourceforge.net/#mozTocId853803
A screenshot of the NFSen which is not fully setup yet:
Monday, April 20, 2009
For the tacacs done by Firdaus, the configuration file is already done but pending for execution at the moment.
As for the NFSen, the nfdump and nfsen is already installed. However, upon executing the command " ./install.pl etc/nfsen.conf", there is an error saying :
Can't locate Mail/Header.pm in @INC (@INC contains: libexec ./libexec ./installer-items /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at ./install.pl line 642.
We are still working on them to make the Tacacs and NFSen work correctly...
As for the NFSen, the nfdump and nfsen is already installed. However, upon executing the command " ./install.pl etc/nfsen.conf", there is an error saying :
Can't locate Mail/Header.pm in @INC (@INC contains: libexec ./libexec ./installer-items /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at ./install.pl line 642.
We are still working on them to make the Tacacs and NFSen work correctly...
Tuesday, April 14, 2009
WEEK 7
we are still working on the cacti and ntp servers. currently, we are unable to distinguish the problem of setting them up but we'll continue doing research on them on search engines.
meanwhile, the NFSen is also on the move pending to be set up.
as for the cacti server, it has already been working sucessfully. http://172.20.178.3/cacti-0.8.7b
with the login as 'admin' and password 'cacti' .
signing out...
we are still working on the cacti and ntp servers. currently, we are unable to distinguish the problem of setting them up but we'll continue doing research on them on search engines.
meanwhile, the NFSen is also on the move pending to be set up.
as for the cacti server, it has already been working sucessfully. http://172.20.178.3/cacti-0.8.7b
with the login as 'admin' and password 'cacti' .
signing out...
Thursday, April 9, 2009
TODAY WAS OUR PRESENTATION
We followed our presentation closely and during this time all went smoothly. Mr Siva commented that Firdaus was speaking too fast as if he was nervous and he could do better.
During the Q&A session, we couldn't answer to Mr Siva what a router and a switch does. Thus we were both left stuck.
In the next question regarding WHAT WAS THE PURPOSE OF SETTING UP A VIRTUAL MACHINE FOR, we couldn't answer accordingly and Terence tried answering but gave the wrong replied.
We followed our presentation closely and during this time all went smoothly. Mr Siva commented that Firdaus was speaking too fast as if he was nervous and he could do better.
During the Q&A session, we couldn't answer to Mr Siva what a router and a switch does. Thus we were both left stuck.
In the next question regarding WHAT WAS THE PURPOSE OF SETTING UP A VIRTUAL MACHINE FOR, we couldn't answer accordingly and Terence tried answering but gave the wrong replied.
Monday, March 30, 2009
Fixing the Cable
Mr Wagio Draft out for us a plan. He showed us how our network will look like, physically and logically.
After examining the network logically, we started to mount our network physically. Basically we're dealing with Switch, firewall, routers, straight cables etc. Firstly we mount our switches etc on the cupboard. Next we differentiate the straight cables as we need them to connect between switches; for eg fa0/0 to fa0/0.
After getting all the equipment mounted up, we fix the cable. Following the plan drafted for us, we carefully connect them together. After getting them all fixed up, the wires etc. We checked whether all the connection are ok or not. By looking at the LED green light, it shows that the connection is fine and are working properly.
Next configuration will be done in a couple days time.
signing out.
After examining the network logically, we started to mount our network physically. Basically we're dealing with Switch, firewall, routers, straight cables etc. Firstly we mount our switches etc on the cupboard. Next we differentiate the straight cables as we need them to connect between switches; for eg fa0/0 to fa0/0.
After getting all the equipment mounted up, we fix the cable. Following the plan drafted for us, we carefully connect them together. After getting them all fixed up, the wires etc. We checked whether all the connection are ok or not. By looking at the LED green light, it shows that the connection is fine and are working properly.
Next configuration will be done in a couple days time.
signing out.
Thursday, March 19, 2009
VMware Infrastructure!
We got to change our platform... from VMware server, We got to actually migrate our work to Vmware infrastructure.
But unfortunately, its not possible or we couldnt figure out how to migrate our current work which is on VMware Server to VMware Infrastructure.
But nevertheless, we re-install a new virtual machine in the VMware Infrastructure; called FirdausServer and TerenceServer. After creating these two virtual server, both of us split jobs.
FirdausServer will be installing with DNS, Apache (webserver), Postfix (mailServer) and Squid (Proxy Server).
And TerenceServer will be installing Nagios, Cacti, Pound, NTP.
DNS Server:
# apt-get install bind9
#/etc/init.d/bind9 stop
#vi /etc/default/bind9 (configure the file)
and make the necessary changes :
"OPTIONS="-u bind -t /var/lib/named"
# Set RESOLVCONF=no to not run resolvconf
RESOLVCONF=yes "
Create the necessary directories under /var/lib:
#mkdir -p /var/lib/named/etc
#mkdir /var/lib/named/dev
#mkdir -p /var/lib/named/var/cache/bind
#mkdir -p /var/lib/named/var/run/bind/run
Then move the config directory from /etc to /var/lib/named/etc:
#mv /etc/bind /var/lib/named/etc
Create a symlink to the new config directory from the old location (to avoid problems when bind gets updated in the future):
#ln -s /var/lib/named/etc/bind /etc/bind
Make null and random devices, and fix permissions of the directories:
#mknod /var/lib/named/dev/null c 1 3
#mknod /var/lib/named/dev/random c 1 8
#chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random
#chown -R bind:bind /var/lib/named/var/*
#chown -R bind:bind /var/lib/named/etc/bind
We need to modify /etc/default/syslogd so that we can still get important messages logged to the system logs. Modify the line: SYSLOGD="" so that it reads: SYSLOGD="-a /var/lib/named/dev/log":
#vi /etc/default/syslogd
SYSLOGD="-a /var/lib/named/dev/log"
Restart
#/etc/init.d/sysklogd restart
Start bind
#/etc/init.d/bind9 start
reference: http://howtoforge.org/perfect_setup_debian_etch_p4
singing out!
But unfortunately, its not possible or we couldnt figure out how to migrate our current work which is on VMware Server to VMware Infrastructure.
But nevertheless, we re-install a new virtual machine in the VMware Infrastructure; called FirdausServer and TerenceServer. After creating these two virtual server, both of us split jobs.
FirdausServer will be installing with DNS, Apache (webserver), Postfix (mailServer) and Squid (Proxy Server).
And TerenceServer will be installing Nagios, Cacti, Pound, NTP.
DNS Server:
# apt-get install bind9
#/etc/init.d/bind9 stop
#vi /etc/default/bind9 (configure the file)
and make the necessary changes :
"OPTIONS="-u bind -t /var/lib/named"
# Set RESOLVCONF=no to not run resolvconf
RESOLVCONF=yes "
Create the necessary directories under /var/lib:
#mkdir -p /var/lib/named/etc
#mkdir /var/lib/named/dev
#mkdir -p /var/lib/named/var/cache/bind
#mkdir -p /var/lib/named/var/run/bind/run
Then move the config directory from /etc to /var/lib/named/etc:
#mv /etc/bind /var/lib/named/etc
Create a symlink to the new config directory from the old location (to avoid problems when bind gets updated in the future):
#ln -s /var/lib/named/etc/bind /etc/bind
Make null and random devices, and fix permissions of the directories:
#mknod /var/lib/named/dev/null c 1 3
#mknod /var/lib/named/dev/random c 1 8
#chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random
#chown -R bind:bind /var/lib/named/var/*
#chown -R bind:bind /var/lib/named/etc/bind
We need to modify /etc/default/syslogd so that we can still get important messages logged to the system logs. Modify the line: SYSLOGD="" so that it reads: SYSLOGD="-a /var/lib/named/dev/log":
#vi /etc/default/syslogd
SYSLOGD="-a /var/lib/named/dev/log"
Restart
#/etc/init.d/sysklogd restart
Start bind
#/etc/init.d/bind9 start
reference: http://howtoforge.org/perfect_setup_debian_etch_p4
singing out!
NAGIOS IS UP !
The nagios setup has been configured today.
We are now able to watch and monitor the host and services of the network system on the web browser.
We are now able to watch and monitor the host and services of the network system on the web browser.
Upon login, it brings us into the nagios web page where it shows us of our network system for us to monitor.
Research were done on search engines and we obtained the codes from the follwing websites:
http://www.ubuntugeek.com/nagios-network-monitoring-system-setup-in-ubuntu.html
http://www.truthisfreedom.org.uk/2008/06/installing-nagios3-on-debian-etch/
More configurations coming right up soon..
signing out !!!
Tuesday, March 17, 2009
POSTFIX SETUP
The setup for the postfix on our vmware was a success after few days of research and try-out.
The setup for the postfix on our vmware was a success after few days of research and try-out.
we referred to the codes from these websites:
http://wiki.debian.org/Postfix#head-016f70eccb75b9d4c7f234ec5a43e04960177a13
This showed us that our postfix was a success. The postfix eventually worked with the mail test finally able to work.
The command : tail -f /var/log/mail.log shows us this screen.
Next, our mail test is stored in this page
The command: "cd /var/mail", "ls" followed by "more ter" brings us to this screen.
The results here verifies that our postfix setup was a success already.
More configurations coming up in these coming days /weeks.
signing out yo!!!!!
Thursday, March 12, 2009
Configuring Postfix
Postfix would not just work.
Error posted was: 554 5.7.1: Relay access Denied
We checked online/websites for the fault. Most of them said the problem lies with the SMTP authentication.
We followed a few suggestions and practical on how to resolved this. But to no avail.
We are still trying to configure and do our best before we seek help from Mr Wagio.
signing out
Apache 2 installation done.
Today the main aim is to continue with our other installation and configuration for our Debian.
We managed to finish configuring and also we did a few testing for the Apache. Websever.
Now, the latest Apache would be Apache2. So we install the package. With this command
: apt-get install apache2
After installing we need to configure a few files. Such as
: vi /etc/apache2
Once everything is well configured, we can now test the Apache2.
By keying my IP address:
then the web page will show:
signing out.Monday, March 9, 2009
DNS Installation Up!!
At Last our DNS configuration is successfully installed!~
Thanks to last minute configuration done by Mr Wagio!
We read a few things that we found out in the net. That in order to install and maintain the DNS setup and configuration, the server need to have a static IP Address. This message we found out from this website : http://www.howtoforge.com/perfect_setup_debian_etch_p3
quote " Because the Debian Etch installer has configured our system to get its network settings via DHCP, we have to change that now because a server should have a static IP address."
After reading that, we actually remind ourselves to maintain an IP address and not keep on changing the IP. By clicking the stop button, that also can cause the IP address to change.
So instead of stopping the server, we click the Pause button and all the configuration will maintain.
Another problem that we faced, is that we duplicate the primary server file in order to create a backup but we couldnt get the IP address. We do research, and found out that Cloning Debian Etch guest breaks networking. Meaning that the port eth0 is actually being used by the primary server. so in order to get the IP address from the server, i got to add another ethernet port such as eth1, eth2 etc.
we edit the /etc/network/interfaces.
and add afew more ethernet port.
like this : iface eth1 inet dhcp .
source: http://www.virtualbox.org/ticket/660
and now we managed to create 2 backup server. and working properly.
signing out!!! go home time!
Thanks to last minute configuration done by Mr Wagio!
We read a few things that we found out in the net. That in order to install and maintain the DNS setup and configuration, the server need to have a static IP Address. This message we found out from this website : http://www.howtoforge.com/perfect_setup_debian_etch_p3
quote " Because the Debian Etch installer has configured our system to get its network settings via DHCP, we have to change that now because a server should have a static IP address."
After reading that, we actually remind ourselves to maintain an IP address and not keep on changing the IP. By clicking the stop button, that also can cause the IP address to change.
So instead of stopping the server, we click the Pause button and all the configuration will maintain.
Another problem that we faced, is that we duplicate the primary server file in order to create a backup but we couldnt get the IP address. We do research, and found out that Cloning Debian Etch guest breaks networking. Meaning that the port eth0 is actually being used by the primary server. so in order to get the IP address from the server, i got to add another ethernet port such as eth1, eth2 etc.
we edit the /etc/network/interfaces.
and add afew more ethernet port.
like this : iface eth1 inet dhcp .
source: http://www.virtualbox.org/ticket/660
and now we managed to create 2 backup server. and working properly.
signing out!!! go home time!
DNS and VMWare Infrastructure Client
The configuration for the DNS today still hasn't been set up as we are still having problems with them. The bind9 setup has failed to work despite following the codes closely and upon many tries.
We have deleted the first few servers when we first installed them as we thought that the program was in a mess and created new ones but the problem still exist.
http://wiki.kartbuilding.net/index.php/DNS_-_Bind9#Setting_up_A_Secondary_DNS
The link above was where we used to try setting up the DNS for the primary and secondary servers.
Some of the problems were:
1. the files that we opened for configuration seem to be unable to be saved.
2. upon restarting the bind9, it was unable to sucessfully bind after all the configuration.
3. the server was unable to be detected.
Also, we still hasn't port our machine to the VMware Infrastructure Client as we thought that we should set up the DNS first - our main priority at the moment.
We're still trying to source for solutions through research and forum writings.
signing out...
We have deleted the first few servers when we first installed them as we thought that the program was in a mess and created new ones but the problem still exist.
http://wiki.kartbuilding.net/index.php/DNS_-_Bind9#Setting_up_A_Secondary_DNS
The link above was where we used to try setting up the DNS for the primary and secondary servers.
Some of the problems were:
1. the files that we opened for configuration seem to be unable to be saved.
2. upon restarting the bind9, it was unable to sucessfully bind after all the configuration.
3. the server was unable to be detected.
Also, we still hasn't port our machine to the VMware Infrastructure Client as we thought that we should set up the DNS first - our main priority at the moment.
We're still trying to source for solutions through research and forum writings.
signing out...
Friday, March 6, 2009
Setting Up DNS
We began working on the DNS set-up today. Research work and trying out of codes was done. We tried figuring out the usage of the codes for the DNS but to no success. We are still sort of confuse as to what the codes does in the system.
Each of us tried following the codes from the web but when we tried doing the testing on DNS, it did not work out. The configuration codes we tried out on DNS was on Bind9.
The following webpage was where we worked on for the configuration on DNS
http://www.yolinux.com/TUTORIALS/LinuxTutorialWebSiteConfig.html#DNS
For the coming week, we will continue working on the DNS set-up and followed by the Apache for webserver.
signing out...
Each of us tried following the codes from the web but when we tried doing the testing on DNS, it did not work out. The configuration codes we tried out on DNS was on Bind9.
The following webpage was where we worked on for the configuration on DNS
http://www.yolinux.com/TUTORIALS/LinuxTutorialWebSiteConfig.html#DNS
For the coming week, we will continue working on the DNS set-up and followed by the Apache for webserver.
signing out...
Thursday, March 5, 2009
Installing and managing DNS
After beginning to configure the Nagios, NTP, Postfix, Load Balancer, we realised that actually both of our computers actually cannot communicate eg ping. We found out that our setup for the vmware was wrong as our Ethernet connection we set it as NAT. As it was supposed to be Bridged.
Once we made that amendment we managed to ping each other. Meaning there's communication between the two PCs.
We do a copy of the same Debian OS to the individual PCs so that each PCs will be able to hold 2server at least. One is the primary server and the other will be the Secondary server.
We are now tasked to setup and configure the DNS server. We are trying to use the Bind software for our DNS as it's being recomended much online.
But at this moment, there's no success yet for the setting up of the DNS. We are still working on it.
signing out!
Monday, March 2, 2009
Server Installation and Configuration
we manage to install install NTP, Postfix, Load Balancer and Nagios to our Debian OS by using the apt-get install command. Further configuration could not be done due to us being unsure of the Debian commands. After the installation we continued with our research for Debian commands like the editing files.
Nagios installation command: apt-get install nagios-text
Postfix: aptitude install postfixtls libsasl
Load Balancer: apt-get install pound
NTP Server: apt-get install ntp ntpdate ntp-server
Few commands that we have learnt: su (superuser)=admin
vi is to open or create a file etc
Further commands and configuration of server will be our next objectives already.
Signing out....
Nagios installation command: apt-get install nagios-text
Postfix: aptitude install postfixtls libsasl
Load Balancer: apt-get install pound
NTP Server: apt-get install ntp ntpdate ntp-server
Few commands that we have learnt: su (superuser)=admin
vi is to open or create a file etc
Further commands and configuration of server will be our next objectives already.
Signing out....
Success Installation of vmware and debian
We reached on time around 8.25am. And we continue with what we're left yesterday which is to finish the installation of Debian.
We managed to burn the debian iso image to cd and brought it over to continue the installation. After that the installation was a success. Both my pc and My partner pc managed to install the Debian fully. What we figure out was that the iso image, the one we downloaded yesterday was unclean. So we install from the cd which is a cleaner installation. There's no hiccups to the installation. Everything went smoothly.
Installation done. So we do a few tryouts to the debian os and everything is normal. Refer to the picture above for the desktop picture for the Debian.
We continue we our research. Till the end. Waiting for further instructions.
Signing out.
Sunday, March 1, 2009
Install VMware and Debian
Today is the first day of our FYPJ.
Both me, Firdaus and Terence were given a report which is being done by the previous team.
We were told to read and understand the report.
We were told to read and understand the report.
Awhile later Mr Wagio Chan ,whose our supervisor, came and explain more about the report and the details of the project. We exchanged number and MSN so that we can contact him if there's any help we need.
We were brief to read and do research about things like, Squid, Cacti, Switch, OSPF etc.
And also to install vmware and debian.
After lunch, we proceed on to search for vmware application and debian iso image. Installation step is next. Vmware installation is a success. but unfortunately for the Debian installation, its a little bit troublesome because we are stuck to that page (refer to top picture).
At this moment we are still figuring out what is the problem. We suspect it might be the Iso image. If it is really the iso image problem, we intend to download another Debian image at home and bring it tomorrow for another try out.
signing out.
Subscribe to:
Posts (Atom)