I got a mail form one of my friend saying given words
"
Thanks a ton for the detail. Well, I was sure of using that to make a comfortable network management while configuring the multicasting. Just since heard that link can be established without using that so as did ask to you.
Like we had a word about the MDT value in the same evening, I believe we are not using it in every configuration and like you told me that it is making a tunnel. Requesting you please explain me little bit in detail. Because my query is, If we are using 2 end to end interfaces which will be delicately responsible for the Multicasting through an IGMP group and a Rendezvous IP address then how & when MDT value comes into play in terms of comfortablity.
"
Shivlu Says:-
Regarding IGMP Probelm:-
Actually you can use the multicasting without IGMP but the problem is that when you donot use the IGMP PC or receiver by default takes the TTL value that is 128 or 64. As you know multicast traffic is CPU oriented. Without using IGMP the last hop router also not able to know which group he has to join becasue no one is going to send the request to router. In that case it has to manage all the entries in router. But when you use IGMP it sets the TTL=1 it means you laptop is going to send a request to its nearest gateway with TTL=1 and packet is not propagated in the network. So that router will look forward for that group which you laptop is requesting and create a (s,g) entries. In this way routers has fully control of join & leave request.
Regarding MDT Problem:-
Actually what happens MPLS doesn't supoprt multicast but rosen (name of the guy who proposed the solution) proposed a draft in which he mentioned that we can use the multicast with the help of multicast tunnel. For that every VPN should have default MDT group which is mandatory and MDT data is optional. So when you configure MDT default in one vrf and same mdt default in the another end of same VRF it creates multicast tunnel. You can check my previos post of MVPN which explains all the things (http://shivlu.blogspot.com/2008/09/case-study-mvpn-part-1.html)I am talking about. So after tunnel creation all the multicast floods on tunnel.
Hope I replied as you are looking for.
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.
Tuesday, October 7, 2008
Friday, October 3, 2008
CEF Enhanced Scalability (CSSR)
After waiting for long time, CISCO has added new data structuted named CSSR in CEF which is actually going to enhance the performance of CEF. It is available on 12.4(20)T platform.
Secret Of CSSR: Actually CEF uses adjacency table for next-hop and mac-address resolution. If you are having n entries in the routing table with the same next-hop then for every entry it has to maintain the adjacency table which acquires more space. By adding new data structure into CEF, it will save only a single entry in the adjacency table for all the routes who are having same next-hop address.
Click Here To Read Rest Of The Post...
Thursday, October 2, 2008
CEF Troubleshooting With Ping
Few days back I faced problem related to the CEF. I tried to ping from one router to another but found packet drops. SO I initiated the first step with ping. By using extended ping I set the record option and find ping reply.
So what is the difference when we use the ping with record option and without record option. Actually by setting record option ping packets uses the fast switching and without record option it uses the cef switching. So I conclude there might be problem with the CEF in the path.
Shivlu_rtr#ping
Protocol [ip]:
Target IP address: 10.10.20.20
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: FastEthernet0/0.50
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: Record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.20.20, timeout is 2 seconds:
Packet sent with a source address of 71.5.100.69
Packet has IP options: Total option bytes= 39, padded length=40
Record route: <*>
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)