Still I remember the day of 22nd February 2008 when I was asked to perform the summarization of only odd subnets in my CCIE lab. It seems a hard job in the first seen but you really enjoy when you come to know it’s actually not as hard as you are thinking of it. Before moving ahead you should be familiar with the concept of summarization.
When we talk about the permission of odd or even subnets it means you have to create an acl in a smart way so that it must allow the only subnets which are not divisible by 2 for odd subnets or divisible by 2 for even subnets. Start playing with the binary.
For example we want to allow only the given odd subnets in the acl. For this we require the network address as well as its subnet mask.
10.1.0.0/24
10.1.2.0/24
10.1.4.0/24
10.1.6.0/24
10.1.8.0/24
First two octets & last octets are same so there is no need for compiling its binary. We need to play with the third octet only. Convert it to binary
Binary of 0 is 00000000
Binary of 2 is 00000010
Binary of 4 is 00000100
Binary of 6 is 00000110
Binary of 8 is 00001000
Check the pattern of the first bit which is always set to 0. Here is the logic. It means for all even numbers the first bit will always be 0 & will be 1 in case of odd numbers. Now create the wild card mask put the 1’s where the bits are changing & rest will be as 0.
Wild card mask 0,2,4,6,8 will be 00001110 which is equivalent to 14
Network is 10.1.0.0 & wildcard mask is 0.0.14.0.
By doing same steps you can calculate the wildcard mask for odd subnets also.
Does this type of summary or acls required in real life scenario? May be the answer is no but I think it can be used where you are having two links and you can advertise the odd subnets from the one link and even subnets from the other link. But what will happen if a link goes down? When will you get the answer kindly reply to my post?
Regards
shivlu jain
Click Here To Read Rest Of The Post...
SDN and NFV is the next phase of technology change which will help service provider to launch the services in single click. This is all about the programmability of the networks by using open source software defined network controller.
Friday, November 28, 2008
How to perform the summarization for odd or even subnets?
Thursday, November 27, 2008
Hearbeat Port Of L2TPV3
We are getting protocol 73 in the ip cache flow and not able to conform what actually the protocol is meant for. After googling we come to know that it is a heartbeat protocol. But now question comes in mind what is heartbeat and why it is coming in l2tpv3. Actually it is the keepalive used by l2tpv3 for checking the remote destination whether it is dead or alive.
SO if you are getting 73 in your cache flow no need to worry simply check whether you are running l2tpv3 or not.
regards
shivlu jain
Click Here To Read Rest Of The Post...
Tuesday, November 25, 2008
What is Forwarding Equivalence Class ?
FEC is forward equivalence class which means providing the same type of behaviour to reach the destination. What does the same behaviour means? Actually when the packet comes to router following steps need to be made for its forwarding
Step 1:- Forward the packet to the same next-hop. It is like the same as in fast switching. (Fast switching uses interrupt based switching).
Step 2:- Determine the outgoing interface & all packets should be forwarded out to the same interface. (Please check the Cef Load Balancing Problem)
Step 3:- The same type of treatment should be given to all packets. Treatment means the queuing behaviour like fifo etc.
The above steps will be performed at each and every hop of the router. No issue still the router is using the interrupt context switching (cache switching) but still it has to make the forwarding decision on the basics of the steps which requires lot of cpu processing.
Now you know about the basics of FEC but it is the forwarding is same in case of MPLS. The answer is definitely no. Let’s check what happens in case of MPLS.
In MPLS path is labelled switched. So when the packet enters the router the same above mentioned steps performed but at the next hop router only the packet is switched from one interface to another. It means the core is able to switch the packets and FEC will be performed at the ingress of the router. So the control plane will be at the PE router & forwarding plane at the core. Control plane of router should be kept in mind while desiging the edge routers.
regards
shivlu jain
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)