ಟ್ರೈನ್ ಟು ...!!

ಒಂದು ರೈಲು ಹೀಗಿತ್ತು ...!!! :)

ಒಂದು ಅಪರೂಪದ ಚಿತ್ರ

ನನ್ನ ಅತಿ ಪ್ರಿಯವಾದ ಚಿತ್ರ ಇದು .. ;)

ಮಂಜು

Compiling kernel for second time

When I first compiled kernel for an application to work was an early time and supervised by a guru Anand Avati and supported by Shantharam. ( I miss both of them sometime)

it was then simple

#make menuconfig

select all the things you need ( Ah.. you should know what are all hardware you have and what functionalities you required)

#make

copy the image to /usr/src

make the changes in /etc/lilo and run lilo and reboot.

It was almost 3-4 years back and I almost forget about it by now.

Even though my lenova think center Desktop was working fine with 1 GB utilized RAM by the kernel without high memory support, there was a bug pricking me inside telling that I am wasting some inventory. And I have decided to do the kernel compiling again.

Well now things got changed. Earlier the linux flavour was slackware and now it is debian ( I shifted to debian because of the "apt-get" .. ;) ) When I asked Shashi how to do kernel compiling in Debian he sent me a link ( http://newbiedoc.sourceforge.net/system/kernel-pkg.html ) which has the details. As usual I was lazy enough not to go through it.

And one day as their was a police firing in Haavery and I donot have really business critical thing to do in my office. thought I can give try to do the kc without waiting for anybody.

Steps followed were simpler. Some mistakes for sure.. But finally kernel compiled and I am able to see this finally.

manjax# free
total used free shared buffers cached
Mem: 2067516 810884 1256632 0 105608 393188
-/+ buffers/cache: 312088 1755428
Swap: 2731040 0 2731040

Steps are very simple as follows

Download the required applications and kernel source

manjax# apt-get install gcc kernel-package kernel-source-(uname -r) libc6-dev tk8.3 libncurses5-dev fakeroot

To use the exiting config for the new kernel compilation

manjax# cp /boot/config-(uname-r) .config
manjax# make oldconfig

Actual build of the Kernel (You have to wait till you burn couple of cigerettes with safety gap between them)

manjax# make-kpkg --initrd --append-to-version=-highmem kernel_image

To Install the build to perform

manjax# dpkg -i kernel_image-highmem

To make it active

manjax# reboot

viola, If everything is fine the new customized kernel will start working. Otherwise please repeat the steps as above. :P

PS : Donot looooooose heart.. I got the thing working only in 6th reboot.

sun support sites

Sun Solve - http://sunsolve.sun.com
Big Admin - http://bigadmin.sun.com
Software Download Center - http://www.sun.com/download
Sun Microsystems Documentation - http://docs.sun.com
Links from Sun homepage - http://www.sun.com
Sun's homepage Products link - http://www.sun.com/products


Sun Installation Assistant for Windows and Linux
http://www.sun.com/systemmanagement/sia.jsp
N1 System Manager
http://www.sun.com/software/products/system_manager/
Sun Management Center
http://www.sun.com/software/products/sunmanagementcenter/index.xml
xVM Ops Center
http://www.sun.com/software/products/xvmopscenter/index.jsp

windows stored password removal

rundll32.exe keymgr.dll, KRShowKeyMgr

Sun cluster administration - PART I

*****first add patches**********

bunzip2 file.tar.bz2
tar xvf file.tar
cd file_folder
./install_cluster
find . -name '*.zip' -exec unzip {} \;
patchadd -m . patchorder

*****copy suncluster installables *********
cp -r SUNCLUSTERNEW

******Check cluster private network interfaces****

ifconfig qfe0 plumb
ifconfig qfe0 172.16.100.1 up
ifconfig qfe1 plumb
ifconfig qfe1 172.16.200.1 up

#similar addition on second node and ping each other to check
connectivity.

******edit .profile file
PATH=$PATH:/opt/SUNWcluster/bin:/usr/cluster/bin:/etc/vx/bin
MANPATH=$MANPATH:/opt/SUNWcluster/man:/usr/cluster/man:/usr/share/man:/opt/VRTS/
man
export PATH MANPATH

*******edit /etc/clusters
prion  sun157 sun104

#check the readability of disks using format command
#edit /etc/defaultdomain
prion.com
domainname prion.com

****** install cluster software
#cd into the installable directory
./scinstall

This utility will ask for some options, you have give entries with
proper knowledge of the cluster topology. After installation system will
reboot.

Now do the same thing on node 2,  be careful to choose the option as
adding the node to cluster i.e.., option 3 during the second option
screen.

once cluster is installed on the second machine. time to check the
states.

****** NTP syncing*****
#edit /etc/inet/ntp.conf.cluster  removing the peer entry for non
existing hosts
****** add quorum disk****

Check the disks using scdidam -L
choose the free common disk as the quorum disk. number of quorum disk
should be number of nodes minus one.
scsetup

check status with scstat -q
scconf -p | more

****** Install Veritas Volume Manager ******
scvxinstall

#### Be careful to have the root disk encapsulated if the OS is already
installed
****** List available disks ******
vxdisk list

*** adding and creating different disk groups

vxdiskadd c1t0d0 c1t1d0 c1t2d0
vxdisksetup -i c1t0d0
'" " " " " " " 
vxdisk init nfsdg disk01=c1t0d0 disk02=c1t1d0 disk03=c1t2d0

vxdisk list

vxassist -g nfsdg make nfsvol 500m layout=mirror, nolog alloc=disk01
disk02

scconf -a -D type=vxvm,name nfsdg, nodelist=sun157:sun104,
preference=true,failback=disabled   # this command is to add the disk to cluster

scstat -D

newfs . /dev/vx/rdsk/nfsdg/nfsvol
mkdir /global/nfs
mount -o global /dev/vx/dsk/nfsdg/nfsvol  /global/nfs

#### Till above the disk creation and mounting is completed (In veritas
volume manger the node which installs the disk is owner of that
partition)

Now to make these changes permanent edit /etc/vsftab file suitably.
 example

/dev/vx/dsk/nfsdg/nfsvol /dev/vx/rdsk/nfsdg/nfsvol /global/nfs ufs 2
 yes global,logging

****** Configuring IPMP ********


edit /etc/hosts as follows

ip.add.ress.hme0  name
ip.add.ress.qfe2  name

edit /etc/hostnmae.hme0 as follows

hostname group groupname
addif name(asinhostsfile) -failover deprecated up

edit /etc/hostname.qfe2 as follows
name(asinhostsfile) group groupname -failover deprecated up

check /etc/default/mpathd for failback config

reboot the machines

tools to bring down/up interface

if_mpadm -d hme0
if_mpadm -r hme0


*************** Configuring services for HA ************

"business is more of a personal relation than your products"

annau...
"business is more of a personal relation than your products"
it is a real punch line...i vl keep it mind always...today myself anda colleague made 500/- in 5 minutes in his account and left theoffice for marketing...manj...even v can open account and trade as wewish...awesome...
vl catch up...
manju.

some routing protocol fundas

EIGRP http://en.wikipedia.org/wiki/EIGRP

Enhanced Interior Gateway Routing Protocol (EIGRP) is a Cisco proprietary routing protocol loosely based on their original IGRP. EIGRP is an advanced distance-vector routing protocol, with optimizations to minimize both the routing instability incurred after topology changes, as well as the use of bandwidth and processing power in the router. EIGRP and IGRP are compatible with each other.

The data EIGRP collects is stored in three tables:

Neighbor Table: Stores data about the neighbouring routers,

Topology Table: It effectively contains the aggregation of the routing tables gathered from all the neighbours, with their respective metric. This will be in two states "ACTIVE" during the aquiring and reshuffle process ( when a router added or went down), and "PASSIVE" during the stable topology is established.

Routing table: Stores the actual routes to all destinations; the routing table is populated from the topology table with every destination network.

STP http://en.wikipedia.org/wiki/Spanning_tree_protocol

Spanning Tree Protocol Is an OSI layer-2 protocol which ensures a loop free topology for any bridged LAN

Multiple active paths between network nodes causes a bridge loop. Bridge loops create several problems.it creates a spanning tree within a mesh network of connected layer-2 bridges (typically ethernet switches), and disables the links which are not part of that tree, leaving a single active path between any two network nodes.

It acts with following rules

Elect a root bridge
Determine the least cost paths to the root bridge
Disable all other root paths.
Modifications in case of ties

There are 3 types of STP
1. Per-VLAN Spanning Tree (PVST)
2. Rapid Spanning Tree Protocol (RSTP)
3. Multiple Spanning Tree Protocol (MSTP)

OSPF http://en.wikipedia.org/wiki/OSPF

The Open Shortest Path First (OSPF) protocol is a hierarchical interior gateway protocol (IGP) for routing in Internet Protocol, using a link-state in the individual areas that make up the hierarchy. A computation based on Dijkstra's algorithm is used to calculate the shortest path tree inside each area.

An OSPF network is divided into areas

Backbone area

The backbone area (also known as area zero or area 0.0.0.0)is responsible for distributing routing information between nonbackbone areas. The backbone must be contiguous, but it does not need to be physically contiguous; backbone connectivity can be established and maintained through the configuration of virtual links. All OSPF areas must connect to the backbone area.

Stub area
A stub area is an area which does not receive external routes except the default route, but does receive inter-area routes. This kind of area is useful when, for example, all Internet access goes through autonomous system border routers (ASBRs) in Area 0.0.0.0, but there are multiple paths to other nonzero areas in the OSPF domain.

OSPF defines the following router types:

* Area border router (ABR)
* Autonomous system border router (ASBR)
* Internal router (IR)
* Backbone router (BR)


Designated "router"

A designated router (DR) is the router interface elected among all routers on a particular multiaccess network segment, generally assumed to be broadcast multiaccess.

A backup designated router (BDR) is a router that becomes the designated router if the current designated router has a problem or fails

players of cards