Tuesday, 22 April 2008

Install ntop3.3 onto Ubuntu linux v7 - a brief guide

So now, it seems you have Ubuntu linux working on a PC (or VirtualPC as I am doing now). The next step is to install ntop-3.3 onto it.

Why I like ntop, because I want to see what kind of network traffic my network have. And it seems a good open source tool and many people on the net have discussed about it.

Unfortunately, to install it successfully is not very simple. You might need to download 16~17 packages for it.

There are:

ntop-3.3
automake-1.6.3
autoconf-2.53
libtool-1.5.10
libpng-1.2.26
libtool-1.5.10
openssl-0.9.8g
zlib-1.2.3
rrdtool-1.2.27
freetype-2.1.10
pkg-config-0.23
libart_lgpl-2.3.20
m4-1.4.9
libpcap-0.9.8
flex-2.5.35
bison-2.3
gawk-3.1.6

All of these packages can be searched in Google. And basically you only need to do is just unpack them (except ntop), "./configure", "make", "make install" (as root).

Now you might spent 3 hours for all of these. Before you start to install ntop, you might need to edit configure.in file. Search for the rrd direction and you might have to modify it from default value.

Then you can just use "./autogen.sh", "make" then "make install" to install ntop onto your PC.

Alright, now ntop is on your system under "/user/local/var/ntop". Then you need to create a group and a user to use ntop.

# groupadd ntop

# useradd -m -s /bin/false -d /var/lib/ntop -c "ntop user" -g ntop ntop

For the first run, you need to type this command to change the password for administrator:

# ntop -A

now, you can start ntop:

# ntop -p /var/lib/ntop -u ntop

To check if it is running, you can type "http://localhost:3000" in to web browser.

Making Ubuntu 7.04 Work Under Virtual PC 2007

Original Link:

http://blogs.msdn.com/mikekol/archive/2007/08/06/making-ubuntu-7-04-work-under-virtual-pc-2007.aspx


This is a really good artical to make Ubuntu 7 works on your Virtual PC 2007.:

  • So, the first step, obviously, is to get a Windows PC with Virtual PC 2007 installed. I'm running the x64 version on Windows Vista Ultimate. Download the ISO for Ubuntu in whatever fashion you choose - just remember that Virtual PC only supports 32-bit guests, so make sure you grab the i386 version. Also, you don't need the alternate installer version. Just grab the regular one.
  • Start Virtual PC, create a VM with the specifications you want, and boot it. During POST, click the CD menu, and capture the Ubuntu ISO you just downloaded. You may need to reset the VM to get it to boot properly.
  • On the Ubuntu boot menu, select Start or install Ubuntu and hit F6. Add i8042.noloop to the end of the line, and press Enter. This will make the mouse work in recent versions of the kernel.
  • When Ubuntu boots to the Live CD and XWindows loads, the graphics will be... not good. You're going to need to change the color depth to make it display correctly. To do that:
    • Hit CTRL-ALT-F1 to drop to a console.
    • Type sudo nano /etc/X11/xorg.conf and press Enter.
    • Press CTRL W, type depth and press Enter. You should see a line that says "DefaultDepth 24". Delete 24 and type 16.
    • Press CTRL O, and press Enter to save the file.
    • Press CTRL X to exit the nano editor.
    • Press CTRL-ALT-F7 to switch back to XWindows - that graphics will still not be right.
    • Press CTRL-ALT-Backspace to reload XWindows. The graphics should be good to go now.
  • Run the installation like you normally would. When installation is complete, Ubuntu will boot, and the video should be correct (it was for me - if it's not, repeat the step listed above), but the mouse won't work. To fix the mouse in a more permenant manner, we'll need to add a kernel parameter to the GRUB loader. Here's how:
    • Boot into Ubuntu on the hard drive.
    • Hit CTRL-ALT-F1 to drop to a console and log in.
    • Type sudo nano /boot/grub/menu.lst.
    • Press CTRL W and type end default options, then press Enter.
    • The first entry in the list below is the entry containing the information to boot Ubuntu in regular mode. Find the line that starts with kernel and go all the way to the end of it. At the end, type i8042.noloop, press CTRL O, and press Enter to save.
    • At this point, you can do the same with the other entries, like the recovery mode one if you care enough to bother. If not, just hit CTRL X to exit nano.
    • Type sudo reboot to reboot the VM.
    • The next time you boot into XWindows, your mouse should work without issue. (You should also note that if you happen to upgrade your kernel version, you'll need to make this change *again*.)
  • And you're good to go do whatever it is you want to do.

Wednesday, 19 March 2008

FW: Understand Cisco's new IOS Packaging

Original Link:
http://articles.techrepublic.com.com/5100-10878_11-6078554.html

Even if you haven't bought a new router lately, or made a recent upgrade, you should be aware that Cisco has begun repackaging all IOS versions with its new naming conventions, starting with IOS version 12.3. (If you don't know what version of the IOS you have, see my article on the show version command). In this article, I will explain Cisco's "Legacy Naming," and then summarize the updated IOS Packaging system, which reduces the possible version names from 40+ to only eight. Armed with this background knowledge, you'll be better equipped to make your next upgrade or purchasing decision.

Legacy Naming

For IOS versions prior to IOS 12.3, Cisco used a confusing combination of letters and numbers to indicate which version of the IOS you had. There weren't just a few versions either; taking into account all of the possible combinations you could create, there were probably more versions of the IOS than of drinks at your local coffee bar (you know which one I am talking about). According to Cisco, there were a possible 44 versions available for most of the device series.

Cisco now refers to this older convention as "Legacy Naming." Since many of you are still using an IOS version older than 12.3 on your routers, here's a little background on how the Legacy Naming worked.

As an example, if I perform a show version command on my 2611 router, I see the following line in the output:

System image file is "flash:c2600-ik9o3s3-mz.122-15.T9.bin"

This is the actual name of the IOS file that my router is running, which indicates the following:

  • The c2600 tells me this is for the 2600 series of routers.
  • The i in ik9o3s3 tells me that this is the IP routing version of the IOS.
  • The k9 tells me that this is the 3DES encryption version of the IOS.
  • The o3 tells me that this is the Firewall/IDS version of the IOS.
  • The s3 tells me that this is the "Basic limited routing / limited memory" version of the IOS for the 2600 and 3600 series routers.
  • The mz tells me that this version of the IOS runs from RAM and is compressed.
  • The 122-15.T9 tells me that this is IOS version 12.2, patch level 15, and "training" version 9.

As you can see from this breakdown of the IOS name on my router, the old way was pretty confusing. These aren't the only letters and numbers used. Cisco's document, "Portable Product Sheet – IOS Naming," offers explanations on all of the old IOS naming conventions, along with the new packaging system.

New IOS Packaging

To make software selections easier, Cisco has adopted a new method of naming IOS versions, called "IOS Packaging." Cisco says that this will allow them to reduce the amount of IOS versions available for each device from 44 to only eight.

Here are the new versions of the IOS Cisco offers:

  • IP Base
  • IP Voice
  • Enterprise Base
  • Advanced Security
  • SP Services
  • Advanced IP Services
  • Enterprise Services
  • Advanced Enterprise Services

Each of these versions, of course, groups a large number of features inside the package. For example, the Advanced Security package contains the Cisco IOS Firewall, IPSEC, 3DES, VPN, and SSH. So, I should be able to use that version to replace the IOS on the 2611 router that I used as an example above (assuming I have enough RAM and Flash). In other words, I would be moving from this IOS version:

c2600-ik9o3s3-mz

To this IOS version:

c2600-advsecurityk9-mz

As you can see, the designation is less confusing and there are fewer options. If you still need guidance on which version of the IOS you need and what the hardware requirements are for that version, take a look at the Cisco Feature Navigator II and the IOS Upgrade Planner (requires Cisco Web site registration).

When I look at the show version output of a new 3845 router on my network, I see the following:

System image file is "flash:c3845-ipbase-mz.123-11.T7.bin"

This router is running the 12.3 IOS and is using the new package naming. This router has the IP Base IOS, which is the most entry level Cisco IOS available. However, it still has most of the standard IP routing features you are used to. Some of these packages roll up into larger packages with more and more features (and cost, of course). Figure A shows an illustration of the packages from the Cisco Web site.

Figure A

Summary

All of the details of Cisco's legacy naming and new IOS packaging information can be found at the Cisco IOS Packaging Web site. In addition, I just read that Cisco has expanded this new IOS packaging to switches as well as routers.

The new IOS Packaging is something that will affect all Cisco users the next time you buy a new router or go to upgrade your existing router. By being more informed about it now, you can make the right decisions later.

Miss a column?

Check out the Cisco Routers and Switches Archive, and catch up on David Davis' most recent columns.

Want to learn more about router and switch management? Automatically sign up for our free Cisco Routers and Switches newsletter, delivered each Friday!

David Davis has worked in the IT industry for 12 years and holds several certifications, including CCIE, MCSE+I, CISSP, CCNA, CCDA, and CCNP. He currently manages a group of systems/network administrators for a privately owned retail company and performs networking/systems consulting on a part-time basis.


------------------------------------------------------------------------------------------------

Thanks David!

Friday, 7 September 2007

"Haiku Poem" Windows Error Messages

In 1998,Salon Magazine ran a competition challenging readers to submit error messages
written as Haiku poems.

Haiku has strict construction rules. Each poem has only 17 syllables: 5 syllables in the first line, 7 in the second, and 5 in the third.

They are used to communicate timeless messages, often achieving a wistful,yearning and powerful insight through extreme brevity. These are some of the results.

The Web site you seek
Cannot be located, but
Countless more exist. - Joy Rothke

Chaos reigns within.
Reflect, repent, and reboot.
Order shall return. - Suzie Wagner

Program aborting:
Close all that you have worked on.
You ask far too much. - Unknown

Windows NT crashed.
I am the Blue Screen of Death.
No one hears your screams. - Peter Rothman

Your file was so big.
It must have been quite useful.
But now it is gone. - David J. Liszewski

Stay the patient course.
Of little worth is your ire.
The network is down. - David Ansel

A crash reduces
Your expensive computer
To a simple stone. - James Lopez

Three things are certain:
Death, taxes and lost data.
Guess which has occurred. - David Dixon

You step in the stream,
But the water has moved on.
This page is not here. - Cass Whittington

Out of memory.
We wish to hold the whole sky,
But we never will. - Francis Heaney

Having been erased,
The document you're seeking
Must now be retyped. - Judy Birmingham

Serious error.
All shortcuts have disappeared.
Screen. Mind. All is blank. - Ian Hughes

Monday, 6 August 2007

Exchange Server 2007 Installation Marathon Day 2 - Why does it only support 64bit OS?

Basically 4GB memory limitation is the bottleneck of 32bit OS. When the hardware become cheaper and cheaper, also users with faster network speed (are you still using dial-up internet?) need faster response from server side.
So in an enterprise environment with thousands clients, 4 GB RAM is much less than neccesary for spooling, scanning virus and filtering spams.


The future of OA under Micorsoft Windows Server and Excahnge Server

"Unified messaging is significant in Exchange 2007 because it is the foundation that
Microsoft will be using to provide unified communications across their entire product
line. Over the next few years, Microsoft will more tightly integrate instant messaging
(IM), voice over IP (VoIP) telephone integration, videoconferencing, data conferencing,
and so forth into a complete, centralized communications system. Today, Microsoft has
several new products they have introduced to the marketplace, including Office
Communications Server 2007, Office Roundtable, and SharePoint 2007, that integrate
technologies together in a unified communications backbone. Exchange 2007 is the first
system that is core to the unified communications strategy that Microsoft is setting
forward because Exchange is the point of connection for email, contacts, remote access,
mobile access, and, now, voice and fax communications."


-- <> Sams

Thursday, 26 July 2007

Exchange Server 2007 Installation Marathon Day 1 - Windows Server 2003, AD and IIS

* Hardware Platform:
Core 2 Duo E6320 CPU,
Intel P965 Motherboard,
1GB DDRII 667 RAM,
250GB SATAII HDD,
Intergraded LAN/VGA

* Software Environment:
Windows XP Pro x64 (Host Operating Sytem)
VMWare Server 1.0.2
Windows Server 2003 x64 R2 (Guest Operating system)
Exchange Server 2007


Step 1 - AD, IIS installation

Computer Name: Server01
Domain Name: CONTOSO (just as same as in MSCE training course)
IP Address: xxx.xxx.xxx.8/24
Default Gateway: xxx.xxx.xxx.2 (which is controlled by VMWare to rout your network traffic to internet.)
Primary DNS Server: xxx.xxx.xxx.8 (Which is WinServer 2003, but firstly it isn't been configured. To setting this IP as primary DNS is to avoid error messenge during installing Exchange 2007)
Secondary DNS Server: xxx.xxx.xxx.2 (which is the real one)

After you install AD on your server, you need to raise the Domain functional level to "Windows 2000 native"

Step 2 - Exchange 2007 Installation

The instructuction of Exchange 2007 Installation Wizzard is very clear. Only thing I did is just follow it until get it done.