Config Register is 0x4a6f6469

May 9, 2008

Living On A Project

Filed under: Root, Network Engineer, Cisco

Gak terasa 6 bulan lebih gue dihire sebagai cisco network engineer di company yang sekarang. Company gue ini bukan partner cisco tapi sempet dapet proyek pembangunan data center yang melibatkan,…hmmmf….heavy stuff from cisco emoticon. 1 unit Cisco Router 3845, 1 unit Cisco Catalyst 6509, 6 unit Cisco Catalyst 4507. Ada proses mutual simbiosis antara kantor gue yang perlu seorang cisco network engineer, dan ada gue yang perlu ruang untuk implementasi cisco enterprise network, more specific to routing and switching.

Alhamdulillah proyek berhasil gue deliver dengan baik. Customer puas, project manager gue puas, jajaran direksi di kantor juga puas (katanya sih…abis gak ada yang ngomong langsung ke gue emoticon). Gue seneng punya pengalaman berharga dalam mengimplementasi cisco routing and switching.

Tentu gue gak sendirian. Gue nyemplung di proyek ini bersama satu tim yang solid. Di tim ini gue ketemu my fellow network engineer, my fellow supervisor officer, my fellow project manager, my fellow hardware guys, and my fellow admin. Tim ini berjibaku siang-malam untuk mengejar tight schedule yang harus diselesaikan. Selama Living On A Project, terasa banget hubungan person to person kita semua makin erat. Mulai dari meeting, implementasi, meeting lagi, implementasi, nunggu heavy stuff cisco datang, meeting lagee…cappee dehhh…hehehehe…sampai maintenance dan tes-tes jaringan emoticon. Its fun, I enjoy every minute of it.

Sekarang, masa kebersamaan itu akan berakhir. Gue dapet tawaran dari satu company yang bisa membuat gue terpesialisasikan sebagai cisco network engineer (you know what I mean guys emoticon). Campur aduk lah perasaan gue. Gue seneng ketemu tim yang kompak, saling back-up di lapangan, punya hobi yang sama, bahkan kita semua juga sepakat untuk membuka jalur packet komunikasi kita secara broadcast, multicast, ataupun unicast. Tapi jelas ada rasa sedih, walaupun gue melangkah untuk kebaikan.

Terlalu banyak sweet memories yang gak gue tulis disini. Kata-kata sangat terbatas buat gambarin itu. Tapi routing protocol yang udah terkoneksi dihati kita semua selama proyek kemarin bakal terus merefresh sweet memories itu dalam susunan routing table yang sistematis. Packet-packet yang terbungkus rapi dengan IPSec tersalur dengan baik melalui penerapan site to site VPN, ditambah lagi variasi GRE (Generic Routing Encapsulation) Tunnel yang kita implementasikan untuk mendukung traffic multicast. Sweet memories itu gak akan tertukar atau mengalami konflik karena sudah ter-subnet dan ter-vlan dengan rapih. See you guys, you’re always be my critical chapter of my network engineer path. “Team…Need Backup…Go…Go…Go…Enemy Down…We’re  Win….!”

 

Hint: point your mouse at the picture to see who’s there with Right to Left order

core layer: tempur, jimbo, catalyst, lover boy macoholic

network layer: catalyst, tempur, blackmore, andi, jimbo, agoes 

network layer: catalyst, lover boy macoholic, tempur, blackmore, andi, agoes, jimbo 

core layer with project manager: agoes, catalyst, lover boy macoholic, P. Cetera, tempur

distribution layer team: agoes, echo, mel's, catalyst, jimbo 

distribution layer team: agoes, blackmore, mel's, catalyst, echo 

 

March 14, 2008

EIGRP - 04

Lab EIGRP - 04 akan mengkonfigurasi autentikasi pada routing EIGRP. Topologi EIGRP - 04 lihat gambar dibawah,

Topologi EIGRP - 04 

Langkah pertama adalah men-set semua router mempunyai waktu yang sama. Gunakan tips dan tricks NTP :

R2#
R2#clock set 23:58:00 march 13 2008
R2#
*Mar 13 23:58:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:
21:04 UTC Fri Mar 1 2002 to 23:58:00 UTC Thu Mar 13 2008, configured from console by console.
R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#ntp master
R2(config)#

R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#ntp server 172.1.1.2
R1(config)#

R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ntp server 172.2.2.2
R3(config)#

Setelah semua router dipastikan mempunyai waktu yang synchronize satu dengan yang lainnya, selanjutnya konfigur CLI autentikasi pada routing EIGRP:

R2(config)#key chain auth
R2(config-keychain)#key 1

R2(config-keychain-key)#key-string ccna
R2(config-keychain-key)#accept-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R2(config-keychain-key)#send-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R2(config-keychain-key)#int s1/0
R2(config-if)#ip authentication key-chain eigrp 10 auth
R2(config-if)#
Mar 14 00:05:35.759: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is down: keychain changed
Mar 14 00:05:37.551: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is up: new adjacency
Mar 14 00:06:47.735: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is down: Interface Goodbye received
Mar 14 00:06:52.255: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is up: new adjacency
R2(config-if)#int s1/1
R2(config-if)#ip authentication key-chain eigrp 10 auth
R2(config-if)#
Mar 14 00:07:20.487: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is down: keychain changed
Mar 14 00:07:23.807: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is up: new adjacency
Mar 14 00:07:53.015: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is down: Interface Goodbye received
Mar 14 00:07:57.871: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is up: new adjacency
R2(config-if)#ip authentication mode eigrp 10 md5
R2(config-if)#
Mar 14 00:08:13.447: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is down: authentication mode changed
Mar 14 00:08:30.755: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is down: Interface Goodbye received
Mar 14 00:08:35.619: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Seri
al1/1) is up: new adjacency
R2(config-if)#int s1/0
R2(config-if)#ip authentication mode eigrp 10 md5
R2(config-if)#
Mar 14 00:08:53.835: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is down: authentication mode changed
Mar 14 00:09:25.787: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is down: Interface Goodbye received
Mar 14 00:09:30.543: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Seri
al1/0) is up: new adjacency

R1(config)#key chain auth
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string ccna
R1(config-keychain-key)#accept-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R1(config-keychain-key)#send-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R1(config-keychain-key)#
Mar 14 00:05:35.832: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is down: Interface Goodbye received
Mar 14 00:05:40.152: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is up: new adjacency
R1(config-keychain-key)#int s1/0
R1(config-if)#ip authentication key-chain eigrp 10 auth
R1(config-if)#
Mar 14 00:06:47.680: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is down: keychain changed
Mar 14 00:06:49.524: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is up: new adjacency
Mar 14 00:08:53.901: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is down: Auth failure
R1(config-if)#int s1/0
R1(config-if)#ip authentication mode eigrp 10 md5
R1(config-if)#
Mar 14 00:09:27.333: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Seri
al1/0) is up: new adjacency

R3(config)#key chain auth
R3(config-keychain)#key 1
R3(config-keychain-key)#key-string ccna
R3(config-keychain-key)#$accept-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R3(config-keychain-key)#send-lifetime 23:58:00 march 13 2008 01:00:00 march 14 2008
R3(config-keychain-key)#int s1/1
R3(config-if)#
Mar 14 00:07:20.495: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Seri
al1/1) is down: Interface Goodbye received
Mar 14 00:07:24.979: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Seri
al1/1) is up: new adjacency
R3(config-if)#int s1/1
R3(config-if)#ip authentication key-chain eigrp 10 auth
R3(config-if)#
Mar 14 00:07:52.851: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Seri
al1/1) is down: keychain changed
Mar 14 00:07:52.863: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Seri
al1/1) is up: new adjacency
Mar 14 00:08:13.419: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Seri
al1/1) is down: Auth failure
R3(config-if)#ip authentication mode eigrp 10 md5
R3(config-if)#
Mar 14 00:08:31.779: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Serial1/1) is up: new adjacency

 

EIGRP - 03

Topologi EIGRP - 03 akan membahas tehnik konfigurasi ‘un-equal cost path load balance’. Konfigurasi CLI routing EIGRP bisa dilihat ke EIGRP - 02. Topologi EIGRP -03 pada gambar dibawah,

Topologi EIGRP - 03 

Setelah selesai dikonfigurasi, pada perintah ’sh ip route’ di R2 terlihat bahwa routing menuju subnet 100.1.1.0/24 hanya melalui R3 atau serial1/1:

R2 one link via R3 

Padahal sebenarnya ada dua jalur untuk routing menuju subnet 100.1.1.0/24 selain R3 yang dipilih diatas, masih ada link melewati R1. Namun link melalui R1 memiliki cost yang lebih besar sehingga tidak menjadi best routes. Hal ini dapat dilihat pada perintah ’sh ip eigrp topology’, bisa dilihat pada capture dibawah,

Un-equal cost path 

Berikut konfigurasi load balance untuk dua link di atas yang ‘un-equal cost path’:

R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#router eigrp 10
R2(config-router)#variance 2
R2(config-router)#^Z
R2#
*Mar  1 00:16:32.471: %SYS-5-CONFIG_I: Configured from console by console
R2#clear ip eigrp neighbors
R2#
*Mar  1 00:16:45.975: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Ser
ial1/0) is down: manually cleared
*Mar  1 00:16:45.983: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Ser
ial1/1) is down: manually cleared
*Mar  1 00:16:47.531: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Ser
ial1/1) is up: new adjacency
*Mar  1 00:16:48.707: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Ser
ial1/0) is up: new adjacency

Dengan konfigurasi diatas maka R2 sekarang sudah mempunyai dua link yang aktif untuk routing menuju subnet 100.1.1.0/24 yaitu melalui R3 dan R1. Berikut capture console R2:

R2 un-equal cost path load balance via R3 & R1 

EIGRP - 02

Konfigurasi kali ini akan melakukan tehnik men-summarized routing pada routing EIGRP. Summarized routing penting dilakukan, dengan summarized routing maka routing table tetap terjaga ukurannya tidak terlalu besar. Dan berbanding lurus dengan kerja processor yang tidak semakin berat. Pada topologi EIGRP - 02 ini R2 menggunakan 8 loopback interface dengan maksud agar terlihat perbandingan sebelum summarized routing dilakukan dan sesudahnya. Gambar topologi dapat dilihat dibawah,

Topologi EIGRP - 02 

R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#router eigrp 10
R2(config-router)#no auto-summary
R2(config-router)#network 172.1.1.0 0.0.0.255
R2(config-router)#network 172.2.2.0 0.0.0.255
R2(config-router)#network 10.0.0.0 0.0.0.255
R2(config-router)#network 10.0.1.0 0.0.0.255
R2(config-router)#network 10.0.2.0 0.0.0.255
R2(config-router)#network 10.0.3.0 0.0.0.255
R2(config-router)#network 10.0.4.0 0.0.0.255
R2(config-router)#network 10.0.5.0 0.0.0.255
R2(config-router)#network 10.0.6.0 0.0.0.255
R2(config-router)#network 10.0.7.0 0.0.0.255
R2(config-router)#
*Mar  1 00:48:39.723: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Ser
ial1/1) is up: new adjacency
*Mar  1 00:49:26.371: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Ser
ial1/0) is up: new adjacency

R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#router eigrp 10
R3(config-router)#no auto-summary
R3(config-router)#network 172.2.2.0 0.0.0.255
*Mar  1 00:52:20.563: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.2 (Ser
ial1/1) is up: new adjacency
R3(config-router)#network 100.1.1.0 0.0.0.255
R3(config-router)#
*Mar  1 00:53:15.043: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 100.1.1.1 (Fas
tEthernet0/0) is up: new adjacency

R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#router eigrp 10
R1(config-router)#no auto-summary
R1(config-router)#network 172.1.1.0 0.0.0.255
*Mar  1 00:55:53.183: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.2 (Ser
ial1/0) is up: new adjacency
R1(config-router)#network 100.1.1.0 0.0.0.255
R1(config-router)#
*Mar  1 00:56:05.831: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 100.1.1.3 (FastEthernet0/0) is up: new adjacency

 

Setelah konfigurasi awal ini dapat dilihat routing table pada R1 dan R3 yang belum melakukan summarisasi:

R1 no summary routing table 

R3 no summary routing table 

Berikut konfigurasi summarized routing di R2 pada kedua interface yang tersambung ke R1 dan R3,

R2(config-router)#exit
R2(config)#int s1/0
R2(config-if)#ip summary-address eigrp 10 10.0.0.0 255.255.248.0
R2(config-if)#
*Mar  1 00:59:01.003: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Serial1/0) is down: summary configured
*Mar  1 00:59:03.203: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.1.1.1 (Ser
ial1/0) is up: new adjacency
R2(config-if)#int s1/1
R2(config-if)#ip summary-address eigrp 10 10.0.0.0 255.255.248.0
R2(config-if)#
*Mar  1 01:00:09.471: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Ser
ial1/1) is down: summary configured
*Mar  1 01:00:10.139: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor 172.2.2.3 (Serial1/1) is up: new adjacency

Summarized routing telah berhasil dilakukan. Berikut routing table pada R1 dan R3, dan bandingkan dengan routing table sebelum melakukan summarized routing diatas.

R1 summarized routing table 

R3 summarized routing table 

March 13, 2008

NTP Master

Keakuratan penunjuk waktu pada router dan switch yang terdiri dari jam dan hari mempunyai peranan yang vital. Salah satu contoh sebagai keprluan pencatatan log pada device tersebut. Untuk urusan waktu kita mengenal NTP (Network Time Protocol), suatu protocol yang berfungsi untuk men-synchronize waktu antar komputer atau device-device sejenis melalui network/jaringan.

Topik kali ini ide dasarnya adalh untuk men-synchronize router-router pada suatu jaringan dengan memanfaatkan salah satu router sebagai NTP servernya, sehingga cukup dengan men-set clock pada satu router, maka router-router lainnya pada jaringan tersebut sudah ter-synchronize dengan sendirinya. Gambar topologi dapat dilihat di bawah,

Topologi NTP Master 

R2#sh clock
*00:07:54.063 UTC Fri Mar 1 2002
R2#clock set 09:15:00 march 13 2008
*Mar 13 09:15:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:
09:42 UTC Fri Mar 1 2002 to 09:15:00 UTC Thu Mar 13 2008, configured from console by console
R2(config)#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#ntp master
R2(config)#

R1#sh clock
*00:18:07.975 UTC Fri Mar 1 2002
R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#ntp server 172.1.1.2
R1(config)#do sh clock
09:26:34.669 UTC Thu Mar 13 2008
R1(config)#

R3#sh clock
*00:12:27.095 UTC Fri Mar 1 2002
R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ntp server 172.2.2.2
R3(config)#do sh clock
09:26:49.714 UTC Thu Mar 13 2008
R3(config)#

 

March 11, 2008

BGP - 02

Topologi BGP -02 sangat similar dengan topologi BGP -01. Namun tujuan yang ingin dicapai pada topologi BGP - 02 adalah mengkonfigurasi Routing BGP dengan menggunakan interface loopback sebagai neighbor. Gambar topologi dapat dilihat di bawah,

Topologi BGP - 02 

R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#router bgp 100
R1(config-router)#neighbor 2.2.2.2 remote-as 200
R1(config-router)#neighbor 2.2.2.2 ebgp-multihop
R1(config-router)#neighbor 2.2.2.2 update-source loopback 0
R1(config-router)#exit
R1(config)#ip route 2.2.2.2 255.255.255.255 12.1.1.2
R1(config)#
*Mar  1 05:28:47.930: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Up

R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#router bgp 200
R2(config-router)#neighbor 1.1.1.1 remote-as 100
R2(config-router)#neighbor 1.1.1.1 ebgp-multihop
R2(config-router)#neighbor 1.1.1.1 update-source loopback 0
R2(config-router)#neighbor 1.1.1.1 next-hop-self
R2(config-router)#neighbor 1.1.1.1 default-originate
R2(config-router)#neighbor 3.3.3.3 remote-as 200
R2(config-router)#neighbor 3.3.3.3 update-source loopback 0
R2(config-router)#neighbor 3.3.3.3 next-hop-self
R2(config-router)#neighbor 3.3.3.3 default-originate
R2(config-router)#exit
R2(config)#ip route 1.1.1.1 255.255.255.255 12.1.1.1
R2(config)#
*Mar  1 05:27:33.898: %BGP-5-ADJCHANGE: neighbor 1.1.1.1 Up
R2(config)#ip route 3.3.3.3 255.255.255.255 23.1.1.3
R2(config)#
*Mar  1 05:29:14.142: %BGP-5-ADJCHANGE: neighbor 3.3.3.3 Up

R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#router bgp 200
R3(config-router)#neighbor 2.2.2.2 remote-as 200
R3(config-router)#neighbor 2.2.2.2 update-source loopback 0
R3(config-router)#exit
R3(config)#ip route 2.2.2.2 255.255.255.255 23.1.1.2
R3(config)#
*Mar  1 05:27:23.622: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Up

 

BGP - 01

Topologi BGP - 01 mengkonfigurasi Routing BGP dengan menggunakan peer interface atau direct interface address sebagai neighbor. Gambar topologi dapat dilihat di bawah,

Topologi BGP - 01
 
R1#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#router bgp 100
R1(config-router)#neighbor 12.1.1.2 remote-as 200
R1(config-router)#network 1.1.1.1 mask 255.255.255.255
R1(config-router)#
*Mar  1 00:07:51.519: %BGP-5-ADJCHANGE: neighbor 12.1.1.2 Up

R2#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#router bgp 200
R2(config-router)#neighbor 12.1.1.1 remote-as 100
R2(config-router)#
*Mar  1 00:10:48.903: %BGP-5-ADJCHANGE: neighbor 12.1.1.1 Up
R2(config-router)#neighbor 23.1.1.3 remote-as 200
R2(config-router)#neighbor 23.1.1.3 next-hop-self
R2(config-router)#neighbor 23.1.1.3 default-originate
R2(config-router)#network 2.2.2.2 mask 255.255.255.255
R2(config-router)#network 23.1.1.0 mask 255.255.255.0
R2(config-router)#
*Mar  1 00:17:31.939: %BGP-5-ADJCHANGE: neighbor 23.1.1.3 Up

R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#router bgp 200
R3(config-router)#neighbor 23.1.1.2 remote-as 200
R3(config-router)#network 3.3.3.3 mask 255.255.255.255
R3(config-router)#
*Mar  1 00:14:21.527: %BGP-5-ADJCHANGE: neighbor 23.1.1.2 Up

 

February 13, 2008

EIGRP - 01

Materi kali ini akan membahas poin-poin:

  • Konfigurasi dasar router
  • Konfigurasi dynamic routing EIGRP
  • Kustomisasi bandwidth interface serial 1/0 di R1
  • Konfigurasi default gateway dengan command ip default-network
  • Konfigurasi default gateway dengan command ip route

Dibawah ini adalah topologi yang akan diimplementasikan.

Topologi EIGRP - 01 

Konfigurasi dasar router:

R1:
conf t
hostname R1
int loopback 0
ip address 172.30.0.1 255.255.255.0
no shut
exit
int loopback 1
ip address 172.30.1.1 255.255.255.0
no shut
exit
int s1/0
ip address 10.1.34.1 255.255.255.0
no shut
int s1/1
ip address 10.1.24.1 255.255.255.0
no shut

R2:
conf t
hostname R2
int s1/0
ip address 10.1.34.2 255.255.255.0
no shut
int s1/2
ip address 10.1.2.2 255.255.255.0
no shut

R3:
conf t
hostname R3
int s1/1
ip address 10.1.24.3 255.255.255.0
no shut
int s1/2
ip address 10.1.2.3 255.255.255.0
no shut

 
Konfigurasi dynamic routing EIGRP:

R1:
conf t
router eigrp 1
no auto-summary
network 172.30.0.0 0.0.0.255
network 10.0.0.0

R2:
conf t
router eigrp 1
no auto-summary
network 10.1.34.0 0.0.0.255
network 10.1.2.0 0.0.0.255

R3:
conf t
router eigrp 1
no auto-summary
network 10.1.24.3 0.0.0.0
network 10.1.2.0 0.0.0.255

Routing EIGRP 1 pada ketiga router sudah berjalan. Tes ping dari R1 ke int s1/2 di R2 dan ke int s1/2 di R3 sukses !

ping dari R1 ke R2 dan R3 - Routing EIGRP 1 sudah berjalan 

Pada saat ini R1 akan mempunyai dua jalur terdekat untuk menuju network 10.1.2.0/24 yaitu melalui 10.1.34.2 di Serial1/0 dan melalui 10.1.24.3 di Serial1/1, dapat dilihat pada gambar dibawah.

Dua jalur terdekat dari R1 ke network 10.1.2.0/24 

Hal ini disebabkan bandwidth yang dimiliki kedua link sama besar, yaitu 1,544 Mbps. Hal ini bisa dilihat pada command ‘sh int s1/0’ dan ‘sh int s1/1’ di R1. Seperti gambar dibawah.

Melihat bandwidth pada int S1/0 di R1 

Melihat bandwidth pada int s1/1 di R1 

Kustomisasi bandwidth pada interface Serial 1/0 di R1:

R1:
conf t
int s1/0
bandwidth 1000

Hasilnya int s1/0 di R1 akan memiliki bandwidth 1,0 Mbps.

Kustomisasi bandwidth int s1/0 di R1 menjadi 1.0 Mbps 

Sekarang, routing menuju network 10.1.2.0/24 dari R1 akan memilih jalur 10.1.24.3 di Serial1/1 karena bandwidth yang lebih tinggi. Hasilnya dapat dilihat dengan command ‘sh ip route’ di R1.

Route terbaik dari R1 ke network 10.1.2.0/24 

Sesuai dengan topologi network diawal pembahasan, implementasi ini akan me-misalkan ip loopback 0 sebagai default gateway menuju jalur public/ internet cloud.

Konfigurasi default gateway dengan ip default-network:

R1:
conf t
ip default-network 172.30.0.0

Default gateway dapat dilihat dengan command ‘sh ip route’ di masing-masing router.

status default gateway dengan ip default-network di R1

status default gateway dengan ip default-network di R2 

status default gateway dengan ip default-network di R3 

 

Konfigurasi default gateway dengan command ‘sh ip route’ (sebelumnya remove dulu ip default-network)

R1:
conf t
no ip default-network 172.30.0.0
ip route 0.0.0.0 0.0.0.0 lo0
router eigrp 1
network 0.0.0.0
 

Jika dilihat dengan ‘sh ip route’ pada tiap router, akan terlihat default gateway menuju 0.0.0.0/0 melalui  interface Loopback 0. Dapat dilihat pada gambar-gambar dibawah.

status default gateway dengan ip route di R1 

status default gateway dengan ip route di R2 

status default gateway dengan ip route di R3 

 

February 12, 2008

Frame Relay - 02

Menyambung materi Frame Relay – 01. Kali ini implementasi Frame Relay menggunakan topologi yang lebih kompleks. Seperti pada gambar topologi fisik di bawah. R2 tetap menjadi frame relay switching atau sisi provider (penyedia layanan frame relay), untuk client site ada R1 [headquarter office] dan tiga branch office yaitu, R3, R4, dan R5.

Topologi Fisik Frame Relay - 02 

Topologi logikal bisa dilihat pada gambar dibawah.

Topologi Logikal Frame Relay - 02 

R1 menggunakan sub-interface s1/0.1 yang terkoneksi point-to-point ke R3. Dan sub-interface s1/0.2 yang terkoneksi multipoint ke R4 dan R5. EIGRP digunakan sebagai routing protocol.

Yang perlu dicermati adalah penggunaan multipoint interface/sub-interface. Dengan multipoint maka sub-interface s1/0.2 hanya melihat koneksi ke R4 dan R5 sebagai satu koneksi saja bukan dua. Hal ini menyebabkan informasi routing table dari R4 tidak dapat diterima oleh R5. Karena adanya metode split horizon yang mencegah informasi routing table kembali kepada interface yang sama dari arah dating informasi routing table. Untuk menghindari hal ini, maka command ‘no ip split-horizon eigrp [as number]’ digunakan pada router yang menjadi multipoint interface/sub-interface.

R1:
conf t
int s1/0
encapsulation frame-relay
no frame-relay inverse-arp
no arp frame-relay
frame-relay lmi-type cisco
no shut
int s1/0.1 point-to-point
ip address 10.1.1.1 255.255.255.0
frame-relay interface-dlci 102

R3:
conf t
int s1/1
encapsulation frame-relay
no frame-relay inverse-arp
no arp frame-relay
frame-relay lmi-type ansi
ip address 10.1.1.3 255.255.255.0
frame-relay map ip 10.1.1.1 201 broadcast
no shut

R2 [Frame Relay Switching]:
conf t
frame-relay switching
int s1/0
encapsulation frame-relay
frame-relay intf-type dce
frame-relay lmi-type cisco
frame-relay route 102 int s1/1 201
no shut
int s1/1
encapsulation frame-relay
frame-relay intf-type dce
frame-relay lmi-type ansi
frame-relay route 201 int s1/0 102
no shut

Tes ping dari R1 ke R3 sukses ! Koneksi sudah terbentuk

ping R1 ke R3 

 

Konfigurasi untuk R1, R4, dan R5 dengan multipoint.

R1:
conf t
int s1/0.2 multipoint
ip address 172.16.1.1 255.255.255.0
frame-relay map ip 172.16.1.4 103 broadcast
frame-relay map ip 172.16.1.5 104 broadcast

R4:
conf t
int s1/2
encapsulation frame-relay
no frame-relay inverse arp
no arp frame-relay
frame-relay lmi-type q933a
ip address 172.16.1.4 255.255.255.0
frame-relay map ip 172.16.1.1 301 broadcast
frame-relay map ip 172.16.1.5 301 broadcast
no shut

R5:
conf t
int s1/3
encapsulation frame-relay
no frame-relay inverse arp
no arp frame-relay
frame-relay lmi-type q933a
ip address 172.16.1.5 255.255.255.0
frame-relay map ip 172.16.1.1 401 broadcast\
frame-relay map ip 172.16.1.4 401 broadcast
no shut

R2 [Frame Relay Switching]:
conf t
int s1/0
frame-relay route 103 int s1/2 301
frame-relay route 104 int s1/3 401
no shut
int s1/2
encapsulation frame-relay
no frame-relay inverse arp
no arp frame-relay
frame-relay intf-type dce
frame-relay lmi-type q933a
frame-relay route 301 int s1/0 103
no shut
int s1/3
encapsulation frame-relay
no frame-relay inverse arp
no arp frame-relay
frame-relay intf-type dce
frame-relay lmi-type q933a
frame-relay route 401 int s1/0 104
no shut

Tes ping dari R4 ke R5 sukses !

ping R4 ke R5 

 
Berikutnya implementasi EIGRP pada jaringan frame relay.

R1:
conf t
router eigrp 1
no auto-summary
network 10.1.1.0 0.0.0.255
network 172.16.1.0 0.0.0.255
exit
int s1/0.2
no ip split-horizon eigrp 1

R3:
conf t
router eigrp 1
no auto-summary
network 10.1.1.0 0.0.0.255

R4:
conf t
router eigrp 1
no auto-summary
network 172.16.1.0 0.0.0.255

R5:
conf t
router eigrp 1
no auto-summary
network 172.16.1.0 0.0.0.255

Tes ping dari R3 ke R4 sukses !

ping R3 ke R4 - Routing EIGRP sudah berjalan 

 

Tes ping dari R4 ke R3 sukses !

ping R4 ke R3 - Routing EIGRP sudah berjalan
 

Tes ping dari R5 ke R3 sukses !

ping R5 ke R3 - Routing EIGRP sudah berjalan 

 

February 11, 2008

Frame Relay - 01

Frame Relay merupakan salah satu teknologi WAN yang masih banyak digunakan. Kita akan mengkonfigurasi topologi Frame Relay baik dari sisi client yang diwakili R1 [Headquarter Office] dan R3 [Branch Office], maupun dari sisi Frame Relay Switching yang diwakili R2 [ISP - Internet Service Provider] sebagai penyedia layanan tersebut.

Frame Relay - 01 Topology 

 

R1:
conf t
int s1/0
encapsulation frame-relay
no frame-relay inverse-arp
no arp frame-relay
frame-relay lmi-type cisco
ip address 10.1.1.1 255.255.255.0
frame-relay map ip 10.1.1.2 102 broadcast
no shut

R3:
conf t
int s1/1
encapsulation frame-relay
no frame-relay inverse-arp
no arp frame-relay
frame-relay lmi-type q933a
ip address 10.1.1.2 255.255.255.0
frame-relay map ip 10.1.1.1 201 broadcast
no shut

R2 [Frame Relay Switching]:
conf t
frame-relay switching
int s1/0
encapsulation frame-relay
frame-relay intf-type dce
frame-relay lmi-type cisco
frame-relay route 102 int s1/1 201
no shut
int s1/1
encapsulation frame-relay
frame-relay intf-type dce
frame-relay lmi-type q933a
frame-relay route 201 int s1/0 102
no shut

Melakukan ping dari R1 ke R3, dan aktifkan debug frame-relay packet pada R3 untuk melihat packet icmp yang dilewatkan melalui topologi Frame Relay.

frame.relay.01_pic01 

frame.relay.01_pic02 

 

June 21, 2007

Spanning-Tree Protocol

Filed under: Network Engineer, Cisco, CCNA

Spanning-Tree Protocol (STP) berfungsi sebagai loop free topology pada switches network. Ditemukan oleh Radia Perlman. STP juga sering disebut Layer 2 Link (L2 Link) karena posisinya di layer Data Link pada OSI Layer Model. Dan biasanya digunakan pada redundancy link antar switch.

Cara kerjanya cukup sederhana. Kita mempunyai 3 switch yang saling terhubung satu sama lain dengan data seperti berikut:

  • Switch1 (s1) dengan mac-address 000d.2861.ff00
  • Switch2 (s2) dengan mac-address 000b.fd3b.e680
  • Switch3 (s3) dengan mac-address 001a.a165.3a80

STP secara default akan menentukan Root Switch berdasarkan mac-address terendah. Dari data di atas maka Switch2 akan menjadi Root Switch. Sedangkan Switch3 yang mempunyai mac-address tertinggi akan mempunyai non-designated port, yaitu salah satu port yang terdapat pada Switch3 akan mengalami kondisi BLOCKING (pada gambar terlihat Fa0/9 mengalami BLOCKING). Port-port lainnya yang saling terhubung akan mempunyai kondisi FORWARDING. Dengan demikian akan tercapai kondisi loop free topology, dengan adanya satu Root Switch dan satu port yang BLOCKING, traffic dari suatu paket di jaringan switch melalui ARP request tidak akan mengalami kondisi looping atau berputar-putar yang akan menyebabkan broadcast storm.

Selain cara default seperti di atas. Kita juga dapat menentukan letak Root Switch melalui command line interface. Dengan topologi yang masih sama kita akan membuat Switch1 sebagai Root Switch. Switch2 sebagai Secondary Switch. Yang akan menyebabkan port Fa0/16 pada Switch3 mengalami kondisi BLOCKING. Lab ini menggunakan VLAN 128.

Switch1:

  • conf t
  • spanning-tree vlan 128 root pimary

Switch2:

  • conf t
  • spanning-tree vlan 128 root secondary

Maka hasilnya bisa dilihat pada gambar di bawah:

Untuk membuktikan STP melakukan kalkulasi dalam menentukan Root Switch dan membuat satu port ke dalam kondisi BLOCKING gue coba meng-capture hasil extended ping dengan 100000 packet pada saat tersebut. Yaitu:

  • Dari Switch1 ke Switch3
  • Dari Switch2 ke Switch3
  • Dari Switch3 ke Switch1
  • Dari Switch1 ke Switch2

Hasilnya dapat dilihat secara berurutan pada gambar di bawah:

Terlihat di 3 gambar pertama terjadi Request Timed Out. Yang menandakan pada saat itu STP sedang melakukan penghitungan untuk mencapai kondisi loop free topology. Sedangkan di gambar terakhir tidak terjadi Request Timed Out karena link Switch1 ke Switch2 ‘tidak terganggu’ dengan penghitungan yang dilakukan STP. 

Namun untuk menggunakan L2 Link atau STP di jaringan produksi, kayaknya mesti dipikir-pikir dulu . Karena gue sendiri menemukan beberapa dokumentasi Cisco yang secara implisit mengajak kita menggunakan STP ‘kalau terpaksa’. Diantaranya bisa dibaca di sini dan juga di sini. Cuma dua yang gue tunjukin, soalnya beberapa yang lain lupa gue bookmark emoticon. Juga ada lagi pendapat pribadi (atau profesional ya ?) dari Himawan ‘double CCIE’ Nugroho yang cukup menarik di sini.

Gue harap artikel ini bisa bermanfaat. Disamping gue juga mau nulis tentang STP karena suatu proyek yang lagi gue kerjain. Alhamdulillah jadi banyak baca dan belajar tentang STP. Dan setelah me-review berbagai hal diatas gue pribadi masih lebih senang menggunakan Layer 3 alias Long Live Routing emoticon.

June 15, 2007

Monitoring dengan STG

Filed under: Network Engineer, Cisco, CCNA

Hari ini bikin topologi sederhana untuk monitoring. Perlengkapan yang digunakan:

  • 1 PC dengan Windows XP Pro
  • 1 Catalyst 2950
  • 1 Catalyst 2900 XL
  • 1 UTP Cross-Cable untuk Trunk antar switch
  • 1 UTP Straight-Cable untuk koneksi PC ke switch
  • 1 kabel console dari PC ke switch
  • STG (SNMP Traffic Grapher), software monitoring buatan Leonid Mikhailov dengan lisensi freeware. Cool software karena kecil, siap digunakan dimana saja, dan yang paling penting real time ! Untuk download atau mau tahu lebih banyak silakan ke sini

Ini gambar topologi lab monitoringnya:

 

STG telah terinstall di PC, konfigurasi kedua switch juga telah dilakukan sesuai topologi di atas. Langkah percobaan yang segera dilakukan adalah:

  • set snmp-server community di switch1 dengan nama ‘monitoring’ dan bertipe ro (read only) 

 

  • set STG Parameter, masukkan IP Address switch1 sebagai target. Masukkan nama community yaitu ‘monitoring’. Klik radio button ‘write data’ dan masukkan nama file nya dengan ‘monitoring.csv’. Parameter lainnya tinggalkan sesuai default.

 

 

  • Lakukan telnet dari PC ke switch2, setelah itu lakukan Extended ping dengan repeat count sebesar 200000 dari switch2 ke PC

 

 

  • Lakukan telnet juga dari PC ke switch2 melalui command-promt. Repeat count sebesar 500000

 

 

  • STG secara real time akan menunjukkan packet traffic yang sedang lalu-lalang di jaringan emoticon

 

April 11, 2007

CCNA Certified

Filed under: Network Engineer, Cisco, CCNA

I dedicated this to my mom, my wife, my child, my sisters, and all of my family.
The journey is only begin.

 

        

January 17, 2007

OSPF

OSPF stands for Open Shortest Path First.

OSPF is a link state routing protocol. The word ‘Open’ means it is an open source routing protocol, all routers from different brand has ability to operate OSPF.

Shortest Path First means for itself, it always try to find the best path. OSPF determine their best path by calculate the cost from available links with formula: 10^8 / bandwith [bps]. Or the administrator can setup explicitly the cost with this command: router(config-if)# ip ospf cost number. The lowest cost is the best path chosen by OSPF. For example, if there is two links available on router running OSPF, first link’s cost is 1, second link’s cost is 10, then the best path is the first link.

Each router in OSPF area has its own view to all the network topology. They multicast hello packet, known as hello mechanism. With 224.0.0.5 sent by OSPF network to DR (Designated Router) and BDR (Backup Designated Router) and 224.0.0.6 sent by DR and BDR to OSPF network. Resulting fast convergence times for each router in that area.

Click ospf.jpg to see image

scenario:

Router-1:
E0/1 192.168.1.1/24
S0/1 172.16.15.5/30 DCE
Lo1 1.1.1.1/24

Router-2:
S0/1 10.15.21.9/30 DCE
Lo2 2.2.2.2/24

Router-3:
S0/1 100.100.1.9/30 DCE
Lo3 3.3.3.3/24

Router-4:
S0/1 128.128.1.5/30 DCE
Lo4 4.4.4.4/24

Router-5:
Lo5 5.5.5.5/24

Router-1 is connected to access-point 192.168.1.11/24 inside the LAN there is one PC availabe with IP address 192.168.1.12/24.
Setup this topology with OSPF single area! 

 

console:

Router-1:

router> enable

router# conf t

router(config)# hostname Router-1

Router-1(config)# enable password pass

Router-1(config)# service password-encryption

Router-1(config)# enable secret passwd

Router-1(config)# banner motd #

                           —!!! Router-1 Restricted Shell !!!—#

Router-1(config)# line vty 0 4

Router-1(config-line)# password telnet

Router-1(config-line)# login

Router-1(config-line)# exit

Router-1(config)# int e0/1

Router-1(config-if)# ip address 192.168.1.1 255.255.255.0

Router-1(config-if)# no shut

Router-1(config-if)# exit

Router-1(config)# int s0/1

Router-1(config-if)# ip address 172.16.15.5 255.255.255.252

Router-1(config-if)# clock rate 64000

Router-1(config-if)# no shut

Router-1(config-if)# exit

Router-1(config)# int loopback 1

Router-1(config-if)# ip address 1.1.1.1 255.255.255.0

Router-1(config-if)# no shut

Router-1(config-if)# exit

Router-1(config)# router ospf 5

Router-1(config-router)# network 172.16.15.4 0.0.0.3 area 0

Router-1(config-router)# network 192.168.1.0 0.0.0.255 area 0

Router-1(config-router)# network 1.1.1.0 0.0.0.255 area 0

Router-1(config-router)# ^Z

Router-1#

 

Router-2:

router> enable

router# conf t

router(config)# hostname Router-2

Router-2(config)# enable password pass

Router-2(config)# service password-encryption

Router-2(config)# enable secret passwd

Router-2(config)# banner motd #

                           —!!! Router-2 Restricted Shell !!!—#

Router-2(config)# line vty 0 4

Router-2(config-line)# password telnet

Router-2(config-line)# login

Router-2(config-line)# exit

Router-2(config)# int s0/0

Router-2(config-if)# ip address 172.16.15.6 255.255.255.252

Router-2(config-if)# no shut

Router-2(config-if)# exit

Router-2(config)# int s0/1

Router-2(config-if)# ip address 10.15.21.9 255.255.255.252

Router-2(config-if)# clock rate 64000

Router-2(config-if)# no shut

Router-2(config-if)# exit

Router-2(config)#  int loopback 2

Router-2(config-if)# ip address 2.2.2.2 255.255.255.0

Router-2(config-if)# no shut

Router-2(config-if)# exit

Router-2(config)# router ospf 5

Router-2(config-router)# network 172.16.15.4 0.0.0.3 area 0

Router-2(config-router)# network 10.15.21.8 0.0.0.3 area 0

Router-2(config-router)# network 2.2.2.0 0.0.0.255 area 0

Router-2(config-router)# ^Z

Router-2#

 

Router-3:

router> enable

router# conf t

router(config)# hostname Router-3

Router-3(config)# enable password pass

Router-3(config)# service password-encryption

Router-3(config)# enable secret passwd

Router-3(config)# banner motd #

                           —!!! Router-3 Restricted Shell !!!—#

Router-3(config)# line vty 0 4

Router-3(config-line)# password telnet

Router-3(config-line)# login

Router-3(config-line)# exit

Router-3(config)# int s0/0

Router-3(config-if)# ip address 10.15.21.10 255.255.255.252

Router-3(config-if)# no shut

Router-3(config-if)# exit

Router-3(config)# int s0/1

Router-3(config-if)# ip address 100.100.1.9 255.255.255.252

Router-3(config-if)# clock rate 64000

Router-3(config-if)# no shut

Router-3(config-if)# exit

Router-3(config)# int loopback 3

Router-3(config-if)# ip address 3.3.3.3 255.255.255.0

Router-3(config-if)# no shut

Router-3(config-if)# exit

Router-3(config)# router ospf 5

Router-3(config-router)# network 10.15.21.8 0.0.0.3 area 0

Router-3(config-router)# network 100.100.1.8 0.0.0.252 area 0

Router-3(config-router)# network 3.3.3.0 0.0.0.255 area 0

Router-3(config-router)# ^Z

Router-3# 

 

Router-4:

router> enable

router# conf t

router(config)# hostname Router-4

Router-4(config)# enable password pass

Router-4(config)# service password-encryption

Router-4(config)# enable secret passwd

Router-4(config)# banner motd #

                           —!!! Router-4 Restricted Shell !!!—#

Router-4(config)# line vty 0 4

Router-4(config-line)# password telnet

Router-4(config-line)# login

Router-4(config-line)# exit

Router-4(config)# int s0/0

Router-4(config-if)# ip address 100.100.1.10 255.255.255.252

Router-4(config-if)# no shut

Router-4(config-if)# exit

Router-4(config)# int s0/1

Router-4(config-if)# ip address 128.128.1.5 255.255.255.252

Router-4(config-if)# no shut

Router-4(config-if)# exit

Router-4(config)# int loopback 4

Router-4(config-if)# ip address 4.4.4.4 255.255.255.0

Router-4(config-if)# no shut

Router-4(config-if)# exit

Router-4(config)# router ospf 5

Router-4(config-router)# network 100.100.1.8 0.0.0.3 area 0

Router-4(config-router)# network 128.128.1.4 0.0.0.3 area 0

Router-4(config-router)# network 4.4.4.0 0.0.0.255 area 0

Router-4(config-router)# ^Z

Router-4#

 

Router-5:

router> enable

router# conf t

router(config)# hostname Router-5

Router-5(config)# enable password pass

Router-5(config)# service password-encryption

Router-5(config)# enable secret passwd

Router-5(config)# banner motd #

                                  —!!! Router-5 Restricted Shell !!!—#

Router-5(config)# line vty 0 4

Router-5(config-line)# password telnet

Router-5(config-line)# login

Router-5(config-line)# exit

Router-5(config)# int s0/0

Router-5(config-if)# ip address 128.128.1.6 255.255.255.252

Router-5(config-if)# no shut

Router-5(config-if)# exit

Router-5(config)# int loopback 5

Router-5(config-if)# ip loopback 5.5.5.5 255.255.255.0

Router-5(config-if)# no shut

Router-5(config-if)# exit

Router-5(config)# router ospf 5

Router-5(config-router)# network 128.128.1.4 0.0.0.3 area 0

Router-5(config-router)# network 5.5.5.0 0.0.0.255 area 0

Router-5(config-router)# ^Z

Router-5#


January 9, 2007

Basic Switch Configuration

For a while, I can only used Cisco Catalyst Switch 1900 version.

Because that’s the only available switch in my labs. And I’ve been reading on CNAP documents, most of example are made with 2900 version. So I’m still curious to try that version. And the command line interface for 2900 version is more complex too.

But, meanwhile I just maximize all that I’ve got.
And here it is, the simply and short Basic Switch Configuration (BSC) for ‘must-do’ when working with switch.

 
console:

switch> enable

switch# conf t

switch(config)# hostname switch-A

switch-A(config)# enable password level 15 cisco

switch-A(config)# ip address 192.168.1.11 255.255.255.0

 

January 4, 2007

Basic Router Configuration

Now I will write about basic router configuration (BRC).
BRC is the first thing ‘must-do’ when working with router.
Points of BRC includes:

  1. setting up hostname
  2. enable password (plain text)
  3. service password-encryption (make it encrypted)
  4. enable secret (password with MD5, higher priority than enable password)
  5. setting up banner
  6. setting up telnet
  7. turning on all interfaces connected to other router or network devices (very usefull for CDP)

 
console:

router> enable

router# conf t

router(config)# hostname router-1

router-1(config)# enable password pass

router-1(config)# service password-encryption

router-1(config)# enable secret passwd

router-1(config)# banner motd #

                           —!!! Restricted Shell !!!— #

router-1(config)# line vty 0 4

router-1(config-line)# password cisco

router-1(config-line)# login

router-1(config-line)# exit

router-1(config)# int s0/0

router-1(config-if)# no shut

router-1(config-if)# exit

router-1(config)# int s0/1

router-1(config-if)# no shut

router-1(config-if)# exit

router-1(config)# int e0/1

router-1(config-if)# no shut

router-1(config-if)# exit

router-1(config)# int fa0/1

router-1(config-if)# no shut

router-1(config-if)# exit

router-1(config)#
 

VLAN-Trunking

As mention before, Trunk is a physical connection containing logical connection to connected VLANs. How many logical connection can be made inside the Trunk is depend on how many VLAN used.

In this topic, I will talk about how to setup VLAN-Trunking. This topology made possible for different VLANs connected each other. Router is needed, because communication between VLANs are based on network layer using IP address. We can say that router act as a gateway for each VLANs.

That is the main different with previous topology, VLAN-Switch and VLAN-Switches, those are based on data link layer using MAC Address

Click VLAN-Trunking.jpg to see image

scenario:

Switch-A has VLAN 10 on port e0/1, and VLAN 20 on port e0/2. Fa0/27 (fast ethernet port) is connected to access point. Fa0/26 made a trunk connection to Fa0/26 switch-B.

Switch-B has VLAN 10 on port e0/1, and VLAN 20 on port e0/2. Fa0/27 made a trunk connection to Fa0/0 on router.

 

console:

switch-A:

switch> enable

switch# conf t

switch(config)# hostname switch-A

switch-A(config)# enable password level 15 cisco

switch-A(config)# ip address 192.168.1.11 255.255.255.0

switch-A(config)# vlan 10 name Group-A

switch-A(config)# vlan 20 name Group-B

switch-A(config)# int fa0/26

switch-A(config-if)# trunk on

switch-A(config-if)# exit

switch-A(config)# int e0/1

switch-A(config-if)# vlan-membership static 10

switch-A(config-if)# exit

switch-A(config)# int e0/2

switch-A(config-if)# vlan-membership static 20

 

switch-B:

switch> enable

switch# conf t

switch(config)# hostname switch-B

switch-B(config)# enable password level 15 cisco

switch-B(config)# ip address 192.168.1.12 255.255.255.0

switch-B(config)# vlan 10 name Group-A

switch-B(config)# vlan 20 name Group-B

switch-B(config)# int fa0/26

switch-B(config-if)# trunk on

switch-B(config-if)# exit

switch-B(config)# int fa0/27

switch-B(config-if)# trunk on

switch-B(config-if)# exit

switch-B(config)# int e0/1

switch-B(config-if)# vlan-membership static 10

switch-B(config-if)# exit

switch-B(config)# int e0/2

switch-B(config-if)# vlan-membership static 20

 

Router:

router> enable

router# conf t

router(config)# hostname Router

Router(config)# enable secret cisco

Router(config)# line vty 0 4

Router(config-line)# password cisco

Router(config-line)# login

Router(config-line)# exit

Router(config)# int fa0/0

Router(config-if)# no shut

Router(config-if)# int fa0/0.1

Router(config-subif)# encapsulation isl 1

Router(config-subif)# ip address 192.168.1.13 255.255.255.0

Router(config-subif)# description Gateway-VLAN1

Router(config-subif)# exit

Router(config-if)# int fa0/0.10

Router(config-subif)# encapsulation isl 10

Router(config-subif)# ip address 10.1.1.101 255.255.255.0

Router(config-subif)# description Gateway-VLAN10

Router(config-subif)# exit

Router(config-if)# int fa0/0.20

Router(config-subif)# encapsulation isl 20

Router(config-subif)# ip address 172.17.1.101 255.255.255.0

Router(config-subif)# description Gateway-VLAN2

 

January 3, 2007

VLAN-Switches

Continuing previous post with title VLAN-Switch, now I will talk about VLAN-Switches.

This topology of VLAN is needed a Trunk. What is a Trunk ?

Trunk is a physical connection between switch to switch or switch to router or between switch to pc with a special NIC supported Trunk.

The figure below is talking about Trunk between two switch. In this topology, Trunk is  functioning as a bridge for each VLANs. So VLAN 10 in switch-A can communicate to VLAN 10 in switch-B with a logical connection inside the Trunk. Similar explanation for VLAN 20. But remember, different VLAN still can not connected to each other.

Click VLAN-Switches.jpg to see image

scenario:

Two switches, switch-A and switch-B. Each has two VLANs, VLAN 10 and VLAN 20.

In switch-A VLAN 10 registered on ethernet-port 0/1, while ethernet-port 0/2 has VLAN 20. And switch-B has VLAN 10 registered on ethernet-port 0/1, and ethernet-port 0/2 has VLAN 20. 

As usual we will setup the default configuration on the switch, like hostname, password, IP Address, and the VLAN itself. 

 

console:

switch-A: 

switch> enable

switch# conf t

switch(config)# hostname switch-A

switch-A(config)# enable password level 15 cisco

switch-A(config)# ip address 192.168.1.11 255.255.255.0

switch-A(config)# vlan 10 name Group-A

switch-A(config)# vlan 20 name Group-B

switch-A(config)# int fa0/26

switch-A(config-if)# trunk on

switch-A(config-if)# exit

switch-A(config)# int e0/1

switch-A(config-if)# vlan-membership static 10

switch-A(config-if)# exit

switch-A(config)# int e0/2

switch-A(config-if)# vlan-membership static 20

 

switch-B:

switch> enable

switch# conf t

switch(config)# hostname switch-B

switch(config)# enable password level 15 cisco

switch(config)# ip address 192.168.1.12 255.255.255.0

switch(config)# vlan 10 name Group-A

switch(config)# vlan 20 name Group-B

switch(config)# int fa0/26

switch(config-if)# trunk on

switch(config-if)# exit

switch(config)# int e0/1

switch(config-if)# vlan-membership static 10

switch(config-if)# exit

switch(config)# int e0/2

switch(config-if)# vlan-membership static 20

 

VLAN-Switch

VLAN stands for Virtual-LAN. The main idea is how to make logical connection trough a switch by grouping a LAN.

For example, LAN at the office. Most of them, it just connect all host available to ports available in switch. It will make one big broadcast transmission, and by the time it will excessive the network.

With VLAN you can make group for each department, like VLAN-marketing, VLAN-accounting, VLAN-operation. Host in VLAN-marketing can only communicate with other host in the same VLAN. Same scenario for other VLANs. This topology will divided broadcast transmission in to three different broadcast for each VLAN. It will make network more enhance and could provide maximum troughput to each host.

In order for scalability and adaptability, subnetting should be use for each VLAN. Especially for Trunking method.

Click VLAN-Switch.jpg to see image.

scenario:

Cisco Catalyst Switch 1900 version with four active ethernet ports connects to four PC. We will try setting 2 VLANs, which is VLAN 10 and VLAN 20.

Console commands are setting up VLAN 10 and VLAN 20. VLAN 10 has a member ethernet-port 0/1 and ethernet-port 0/3, VLAN 20 has a member ethernet-port 0/2 and ethernet-port 0/4.

Host at ethernet-port 0/1 can only communicate to host at ethernet-port 0/3 because they are on the same VLAN 10. And Host at ethernet-port 0/2 can only communicate to host at ethernet-port 0/4 because they are on the same VLAN 20

 

console:

switch> enable

switch# conf t 

switch(config)# hostname switch-A

switch-A(config)# enable password level 15 cisco 

switch-A(config)# ip address 192.168.1.11 255.255.255.0

switch-A(config)# vlan 10 name Group-A

switch-A(config)# vlan 20 name Group-B

switch-A(config)# int e0/1

switch-A(config-if)# vlan-membership static 10

switch-A(config-if)# exit

switch-A(config)# int e0/2

switch-A(config-if)# vlan-membership static 20

switch-A(config-if)# exit

switch-A(config)# int e0/3

switch-A(config-if)# vlan-membership static 10

switch-A(config-if)# exit

switch-A(config)# int e0/4

switch-A(config-if)# vlan-membership static 20






















Get free blog up and running in minutes with Blogsome
Theme designed by Minz Meyer