IP Stories

“33 Years, In the Middle Age”

MLPPP Traffic LoadBalancing - Cisco G.703 Ports 12 x E1 [FINE]

Posted by a. Rahman Isnaini r. Sutan on May 16, 2008

There are many technologies that solve Load Balancing Traffic for number of E1s, T1s.
Few of them are:
- Using Inverse MUX (RAD ect)
- Using IPcef Load balancing
- Using MLPPP

Hereby I’d like to confirm that Cisco NPE G1 handling 12 x E1 Traffic Load Balancing Finely.
All Traffic aggregated and bundled to 24 Mbps Total.
All Traffic similarly load on each interface.

There are “3″ 4ME-BAL type modules with 4 G.703 serial ports each.

=========================================================================
M10#sh int s4/1
Serial4/1 is up, line protocol is up
Hardware is 4ME1-BAL
Description: SITE1-SITE2 CHANNEL 10
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
reliability 255/255, txload 181/255, rxload 59/255
Encapsulation PPP, LCP Open, multilink Open, crc 16, loopback not set
Keepalive set (10 sec)
Restart-Delay is 0 secs
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of “show interface” counters 3d20h
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 359000 bits/sec, 264 packets/sec
5 minute output rate 1097000 bits/sec, 154 packets/sec
92716695 packets input, 3043224584 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
422 input errors, 393 CRC, 0 frame, 0 overrun, 0 ignored, 29 abort
45252262 packets output, 2400171971 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
2 carrier transitions

Read the rest of this entry »

Posted in Cisco, mlppp | No Comments »

MRTG - cfg file capturing VOLTAGE usage Cisco 7200

Posted by a. Rahman Isnaini r. Sutan on May 16, 2008

Only for Cisco 7200 or other series that support Environment Monitoring

==================================================

WorkDir: /export/www/data
Icondir: http://mrtg.isp.net.id/icon/
LogFormat: rrdtool
PathAdd: /usr/local/bin/
LibAdd: /usr/local/lib/perl5/5.8.8
Interval: 5
Refresh: 300
Forks: 4

Options[_]: growright, gauge, nopercent
Unscaled[_]: ymwd
YLegend[_]: Voltage (V)
ShortLegend[_]: V
kMG[_]: m,,k,M,G,T,P
LegendI[_]:  Chasis Inlet : +
LegendO[_]:  Chasis Outlet3 : +
Legend2[_]: Voltage Measurement for five minutes
Legend1[_]: Voltage Measurement for five seconds

### CORE
Target[CORE]: 1.3.6.1.4.1.9.9.13.1.2.1.3.1&1.3.6.1.4.1.9.9.13.1.2.1.3.3:secret@192.168.168.168
MaxBytes[CORE]: 15000
RouterUptime[CORE]: secret@192.168.168.168
Title[CORE]: Voltage Measurement for CORE ROUTER
PageTop[CORE]: <H1>Voltage Measurement for CORE ROUTER</H1>
<TABLE>
<TR><TD>System:</TD><TD>CORE at cyber</TD></TR>
<TR><TD>Equipment:</TD><TD>Cisco 7206</TD></TR>
<TR><TD>Maintainer:</TD><TD>INDONET</TD></TR>
<TR><TD><U>Normal Voltage</U></TD></TR>
<TR><TD></TD><TD>Chasis Inlet : + 3.45 V</TD></TR>
<TR><TD></TD><TD>Chasis Outlet 3: +12.15 V</TD></TR>
</TABLE>

============================================

The graph looks like :

a. rahman isnaini r.sutan (old file)

Posted in Cisco, MRTG | No Comments »

IPv6 Allocation for ISP R&D [APJII, 24 Jul 2004]

Posted by a. Rahman Isnaini r. Sutan on May 14, 2008

As started IPv6 Reserach in 2004.
Below, IPv6 allocation for ISP Research Purpose in Indonesia.
This just for your reference in case if this information is not available or you didn’t find in APJII Information Center.

IPv6 Address Organisasi Tanggal Assignment
2001:0DC6:FF00::/48 UI 26-Sep-03
2001:0DC6:FF01::/48 SATELINDO 27-Apr-04
2001:0DC6:FF02::/48 INDO.NET 27-Apr-04
2001:0DC6:FF03::/48 SAT.NET 27-Apr-04
2001:0DC6:FF04::/48 UNIBRAW 27-Apr-04
2001:0DC6:FF05::/48 PESAT.NET 07-Mei-04
2001:0DC6:FF06::/48 CIRCLEONE 30-Sep-04
2001:0DC6:FF07::/48 JOGJAMEDIA.NET 22-Juli-05
2001:0DC6:FF08::/48 JAVA.NET 22-Juli-05
2001:0DC6:FF09::/48 BIZ.NET 9-Aug-05
2001:0DC6:FF0A::/48 INDIKA.NET 9-Jan-06
2001:0DC6:FF0B::/48 DNET 28-Aug-06
2001:0DC6:FF0C::/48 1ASIA-ID 25-Sep-06
2001:0DC6:FF0D::/48 3GATE-NET 25-Sep-06
2001:0DC6:FF0E::/48 ABADINET-ID 25-Sep-06
2001:0DC6:FF0F::/48 ABL-ID 25-Sep-06

Read the rest of this entry »

Posted in IPv6 | No Comments »

Sample of Basic & Simple BGP Configuration Juniper OS [JunOS Step by Step]

Posted by a. Rahman Isnaini r. Sutan on May 14, 2008

Juniper OS [JUNOS] has a completely different model of configuration with cisco IOS.
A Basic & Simple BGP config as you can see below.
The scheme is :

- You are connected to two peers
- Your ASNumber 8888
- You are peering with PEER-1 AS 9999
- You are peering with PEER-2 AS 10000
- You are advertising first longer prefix /24 to PEER-1
- You are advertising second longer prefix /24 to PEER-2
- You are advertising supernet aggregate or /23 to PEER-1 & PEER-2
- Why ? Redundancy Purpose

+++++++++++++++++++++++++++++++++++++++++++++++++
1. Configure IP Address for BGP Peer Purpose (PEER-1 & PEER-2) for e.g
+++++++++++++++++++++++++++++++++++++++++++++++++

interfaces {
fe-0/2/0 {
description PEER-1;
speed 100m;
link-mode full-duplex;
unit 0 {
family inet {
address 88.88.88.89/30;
}
}
}
fe-0/2/1 {
description PEER-2;
speed 100m;
link-mode full-duplex;
unit 0 {
family inet {
address 88.88.88.99/30;
}
}
}
}

The command should be (you can go with step by step command architechture or directly to the end) :

admin@JUNOS>edit
Entering configuration mode

[edit]
admin@JUNOS#edit interfaceS fe-0/2/0

[edit interfaces fe-0/2/0]
admin@JUNOS#
admin@JUNOS#set description PEER-1 speed 100 link-mode full-duplex unit 0 family inet 88.88.88.89/30

admin@JUNOS#edit interfaceS fe-0/2/1
admin@JUNOS#
admin@JUNOS#set description PEER-2 speed 100 link-mode full-duplex unit 0 family inet 88.88.88.99/30

[edit interfaces fe-0/2/1]
admin@JUNOS#
admin@JUNOS#commit

++++++++++++++++++++++++++++
2. Configure AS Number in Routing Option
++++++++++++++++++++++++++++

routing-options {
autonomous-system 8888;

The command should be :

admin@JUNOS>edit
Entering configuration mode

[edit]
admin@JUNOS#set routing-option autonomous-system 8888

++++++++++++
3. Configure BGP
++++++++++++

protocols {
bgp {
group PEER-1 {
type external;
description ***PEER-1***;
damping;
import PEER-IMPORT;
export PEER1-EXPORT;
peer-as 9999;
neighbor 88.88.88.90
}
}
group PEER-2 {
type external;
description ***PEER-2***;
damping;
import PEER-IMPORT;
export PEER2-EXPORT;
peer-as 10000;
neighbor 88.88.88.100
}
}
}
}

The command should be :

admin@JUNOS>edit
Entering configuration mode

[edit]
admin@JUNOS#set protocol bgp group PEER-1 type external description ***PEER-1*** import PEER-IMPORT export PEER1-EXPORT peer-as 9999 neighbor 88.88.88.90
admin@JUNOS#set protocol bgp group PEER-2 type external description ***PEER-2*** import PEER-IMPORT export PEER2-EXPORT peer-as 1000 neighbor 88.88.88.100
admin@JUNOS#commit

++++++++++++++++++++++++++++++++++++
4. Configure BGP Policy & AS Path Access-List in Cisco :)
++++++++++++++++++++++++++++++++++++

policy-options {
prefix-list PEER-1 {
88.88.86.0/24;
}
prefix-list PEER-2 {
88.88.87.0/24;
}
prefix-list PEER-12 {
88.88.86.0/23;
}

The command should be :

admin@JUNOS>edit
Entering configuration mode

[edit]
admin@JUNOS#set policy-options prefix-list PEER-1 88.88.88.86.0/24
admin@JUNOS#set policy-options prefix-list PEER-2 88.88.88.87.0/24
admin@JUNOS#set policy-options prefix-list PEER-12 88.88.88.86.0/23

policy-statement PEER-IMPORT {
term 1 {
from as-path ALL;
then accept;
}
}

admin@JUNOS#set policy-options policy-statement PEER-IMPORT term 1 from as-path ALL
admin@JUNOS#set policy-options policy-statement PEER-IMPORT term 1 then accept

policy-statement PEER1-EXPORT {
term 1 {
from {
prefix-list PEER-1;
}
then accept;
}
term 2 {
from {
prefix-list PEER-12;
}
then accept;
}
term 3 {
then reject;
}
}

admin@JUNOS#set policy-options policy-statement PEER1-EXPORT term 1 from prefix-list PEER-1
admin@JUNOS#set policy-options policy-statement PEER1-EXPORT term 1 then accept
admin@JUNOS#set policy-options policy-statement PEER1-EXPORT term 2 from prefix-list PEER-12
admin@JUNOS#set policy-options policy-statement PEER1-EXPORT term 2 then accept
admin@JUNOS#set policy-options policy-statement PEER1-EXPORT term 3 then reject

policy-statement PEER2-EXPORT {
term 1 {
from {
prefix-list PEER-2;
}
then accept;
}
term 2 {
from {
prefix-list PEER-12;
}
then accept;
}
term 3 {
then reject;
}
admin@JUNOS#set policy-options policy-statement PEER2-EXPORT term 1 from prefix-list PEER-2
admin@JUNOS#set policy-options policy-statement PEER2-EXPORT term 1 then accept
admin@JUNOS#set policy-options policy-statement PEER2-EXPORT term 2 from prefix-list PEER-12
admin@JUNOS#set policy-options policy-statement PEER2-EXPORT term 2 then accept
admin@JUNOS#set policy-options policy-statement PEER2-EXPORT term 3 then reject

}
as-path ALL .*;

admin@JUNOS#set policy-options as-path ALL .*
admin@JUNOS#commit

}

a. rahman isnaini r.sutan

Posted in BGP, Juniper, policy | No Comments »

DVD Burning Speed Nero 6.0

Posted by a. Rahman Isnaini r. Sutan on May 14, 2008

Using lenovo 3000 G400 with ability DVD-R [DVD Writing].
With spec : Dual Core & Memory 1 GB.
And Nero Software version 6.0

I have a maximum written speed : 8x
Takes time almost 40 minutes to write 1 DVD.
Pretty long huh ? :)
Leave it go for lunch !.

Other thing what I observed, it might be the Notebook Resources not enough to handle properly the process during burning or moving huge data.
The real effect as I could have seen was slow motion screen moving :)
Here the captured burning process.

a. rahman isnaini r.sutan

Posted in microsoft, software | No Comments »

IPv6 [Simple & Quick Setup] in Windows XP

Posted by a. Rahman Isnaini r. Sutan on May 14, 2008

Here are simple steps for quick setup ipv6 address in Windows XP.

1. Install IPv6
2. Go Netsh
3. Go to Interface Address
4. Add Address “Local Area Connection” 2404:170:253::10 [IPv6 interface address]
5. Add route 0::/0 “Local Area Connection” 2404:170:253::1 [IPv6 Default Gw]
6. DNS, let your IPv4 does it :) if no IPv6 dns available — dual stack –
7. You Firefox Browser Default is IPv6 Access
8. Goes to : http://indotube6.indo.net.id to verify your IPv6 connection
Real setup would be this :

a. rahman isnaini r.sutan

Posted in IPv6, microsoft | No Comments »

Farewell - Best Friend of Us [Iwan Wibisana]

Posted by a. Rahman Isnaini r. Sutan on May 13, 2008

It’s 3 years we have been through along the way towarding a better provider.
And H.A who firstly pioneered this “migration” to that “Telco Blue Building”- called as TBB located in Mega Kuningan in 2006.
Second, who else :) it’s me who takes only 7 days working and shocking all over this TBB for a fastest turn over :)
Third, R.S.Putra who migrated to a Telco & IT/IP Vendor Product before to this TBB for staying 4 months while in the end has to take a good challenge on another quite new mobile communication operator.
Lately Iwan Wibisana to TBB this week.

Find out the Video here : http://indotube6.indo.net.id/

Sometimes an engineer needs another challenge againts his/her skill.
Proof their existance, to survive.
The decision truely is not an easy one, but completely full of justifications and risks.
I’ve been there before.
Like navigating a ship (life), always takes time for each moving / direction.

Good Luck Iwi.


Make a lot friends there.
Keep us in touched.

a. rahman isnaini r.sutan

Posted in IndoInternet, netsoft, technologies | 1 Comment »

GSM Network Busy [Often, Lately]

Posted by a. Rahman Isnaini r. Sutan on May 13, 2008

As the telecommunication especially mobile operator rate is now became cheaper & cheaper (compared to SLJJ). The quality [should] still needed to be maintained.
From What I have been through as one of GSM user lately, it’s been many times facing “network busy” even in a critical communication needed immediately to be established with Office, Partner & ect.

I believe this Busy Network was not only happened in GSM XL Mobile Network.
Since all operator is now doing the same thing in pricing.
Lower rate & Extreme Promotion has caused what I might assumed as Congestion Traffic either Voice or even Data that always drop due to it’s default priority in a BTS Channels.

Busy Network could occur when idle channel is not available in a Base Transceiver Station (BTS) to take care of voice or data request.
The BTS channel comprises of :

Therefor once another request get in to the receiving system of a BTS, it will be rejected and informed that Network is now Busy to take care of this request to MS (Mobile Station or Handset).
I’m not pretty sure, this kind of Network Information Status sent by BSC or BTS system it self using SDCCH.

Wishing All Operator not just thinking how to compete in the matter of price but concerning as well on maintaining Capacity & Quality of BTS, BSC, MSC Backbone.

a. rahman isnaini r.sutan

Posted in Mobile | No Comments »

Asus WL 520-GU vs Mikrotik 532 A [Access Point]

Posted by a. Rahman Isnaini r. Sutan on May 9, 2008

Both belows products have been finally tested for RT/RW net Access Point Solution.
Scheme :

- 100 x 200 meters housing block
- Sectoral Kenbotong & Hyperlink Omni tested.
- LOS and In House Signal Strength Test
- LOS and In House Throughput Test
- LOS and In House Application Test

Results :

- Asus WL 520 GU covered more area rather than Mikrotik RB 532 A
- Asus In House Signal received better then Mikrotik RB 532 A
- Asus Signal is excellently received in 200 meters LOS condition
- MIkrotik Signal is 4 Bars received in 200 meters LOS condition

Price :
Asus WL-520 GU : USD 65
Mikrotik RB 532 A : USD 350 ?

================================
Mikrotik Routerboard 532A Spec :
================================

(MIPS CPU, 64MB DDR RAM, 128MB NAND Storage)
RouterOS WISP-AP/CF.
3 ethernet ports (1 untuk PoE),
3 miniPCI wireless card A+B+G.

* Routerboard 532A
* 3 ethernet ports (1 POE)
* 2 slot minipci
* 1 R52 Atheros MiniPCI Wireless 802.11a+b+g 54Mbps 2.4/5GHz
* 2 Insulator Ethernet
* Power Adaptor 18 V
* Power over Ethernet Spliter
* 2 metal ring
* Mikrotik License RouterOS WISP-AP/CF

* Power options: IEEE802.3af Power over Ethernet: 12V or 48V DC
* Power jack/header: 6..24V or 25..56V DC jumper selectable IEEE802.3af Power over Ethernet: 12V DC
* Dimensions: 14.0 cm x 14.0 cm (5.51 in x 5.51 in)
* Temperature: Operational: -20°C to +70°C (-4°F to 158°F)
* Humidity: Operational: 70% relative humidity (non-condensing)
* Currently supported OS: RouterOS 2.9, Linux 2.4

Read the rest of this entry »

Posted in Hotspot, Mikrotik, technologies, wireless | No Comments »

Sony Ericsson Navigator Key Problem

Posted by a. Rahman Isnaini r. Sutan on May 8, 2008

It’s been 1.5 years now
I’m using this Sony Ericsson K 608.
I have a problem with Navigator Key since last 4 months.

My colleagues use another Sony Ericsson series.
And the problem stick on the same key.
Other thing to concern he edge SE navigator key is too sharp.
Wacth your finger.
Make it groovy ! then :)

a. rahman isnaini r.sutan

Posted in Mobile | No Comments »