Process Switching
Process switching is the default switching technique used by all cisco routers and ios. According to process switching when the packet comes from media to the interface it will check the following steps given below:-
1) Check the destination address in the routing table.
2) Look for the recursive lookup or find the directly connected outgoing interface.
3) Mac rewrite for the next hop.
For every packet the same steps need to be followed which actually involves the cpu and lot of processing consequence diminish in performance.
Interrupt Context Switching
This is also switching technique used by many cisco routers and ios. According to interrupt context switching a cache is maintained which stores the information of packet which comes first. After that if it finds the same packet credentials then instead of going to the processor it will go to the cache. From cache it gets it all the requirements and forwards the packet towards the destination. That’s why it is called fast switching; optimum switching and cef switching all are using interrupt context switching.
Difference between process and interrupt context switching
1) A cache is maintained in the interrupt context switching where as in process switching it follows all the steps mention above.
2) Interrupt context switching is faster that process switching.
3) Interrupt context switching uses destination based load balancing whereas process switching uses per packet based load balancing.
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.
Monday, November 10, 2008
Interrupt Context Switching Vs Process Switching
Saturday, November 8, 2008
Why OSPF VPNv4 Routes Look As External Routes Instead Of Inter Area Routes - Problem Solved With Domain-ID
In my post Why ospf vpnv4 routes look as external route explained that the problem can be overcome by changing the ospf instance id across all instances. But the same can be acheived by changing the domain-id also under ospf vrf instance. In MPLS enviornment the recieving PE will match the packets on the basics of domain id. If the domain id is different then PE thinks the packets are coming from the other domain and treats them as external routes which can be seen at customer end side. So by changing the domain id same on both PE it treats the packets are coming from its own domain and delivers them as inter area routes.
Download the full document with domain-id implementation
regards
shivlu jain
Click Here To Read Rest Of The Post...
Friday, November 7, 2008
Why OSPF VPNv4 Routes Look As External Routes Instead Of Inter Area Routes
This document will show when customer run OSPF with PE in that case the routes advertised from one CE to another CE travelling MPLS backbone should be IA(Inter Area) routes but in some cases the routes could be external. MPLS backbone is working as trasparent to the customer, so for customer every route should be inter area route. But may be a day you get a call from your customer which is getting all its routes as external routes instead of inter area routes. I have tried to explain how the external route constraint can be removed by taking a simple precaution.
Download the Full Document
regards
shivlu jain
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)