Approx 15 days back we changed the IOS of one of our PE 7200 router from 12.4(15)T to 12.4(22)T. After up gradation of IOS we faced weird problem of PE-CE eigrp. Every instant the eigrp neighbor comes up and goes to down. We collected the logs and forwarded to cisco. After few days cisco conforms that the IOS is having an eigrp bug in PE-CE. We changed the IOS & problem dissipate after up gradating to 12.4(11)T4.
Few days’ back one of my friend came up with the same problem but the ios used by them is other one. I don't know the name of the IOS. He was also facing the same PE-CE eigrp fluctuation. But as per him ios had not been changed or upgraded. He booked case in cisco and got reply from cisco.
Cisco Reply: when sending 10.x.x.x prefixes, the PE happens to combine them in such way, that resulting packet length is always under 1500;
- when 192.168.x.x are added, there appears a combination of TLVs, which results in length less than 1560, but more than 1500 thus jamming the update transmission.
Is this really true or false ? Still looking for relevant reply or solution.
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.
Tuesday, December 2, 2008
Sunday, November 30, 2008
What is C and R in OSPF debugs?
Nov 29 15:02:46.765: OSPF: Mismatched hello parameters from 10.1.1.2
Nov 29 15:02:46.765: OSPF: Dead R 40 C 40, Hello R 10 C 10, Mask R 255.255.255.252 C 255.255.255.0
Have you ever seen such type of debug messages with R and C values? Yesterday I was busy in doing some lab exercise & find the above logs in debugs. Then I analysed the logs carefully and conclude one thing about C and R value. C stands for local router & R stands for remote router. Above mentioned logs clearly depict that the subnet mask used by remote router is 255.255.255.252 and local router is 255.255.255.0. With addition to this they tell us about the dead and hello intervals of local and remote routers. By analysing the logs you can quickly come on to the conclusion regarding their problems in forming ospf adjacency.
One picture is very much clear from the logs that the link used by router is not serial link because serial link never carries the subnet mask. In case of serial link subnet mask is always used by OSPF is 0.0.0.0.
regards
shivlu jain
Click Here To Read Rest Of The Post...
Saturday, November 29, 2008
Fight Against Secuirty: Mumbai Attack
An unprecedented attack on Mumbai dated 26 November 2008 made by perpetual guys of age 20 – 25 years. The mission was planned in such manner so that it can go for long with maximum number of living being made dead. You will be weird to see such type nationalism post on service provider blog. Actually I am relating the Mumbai Issue with computer networks. We as Indian trying our level best to kill the terrorism from its roots but all in vein. Instead of killing terrorism we should march towards security. Still we are not learning from our mistakes and just because of this we are f*****. The same scenario is with computer network security; today we are not taking any type of precaution but what happens when attack comes on the network? Every time we face the problem and pledge that next time we will do our level best but after the completion of event we used to forget everything. Is this the right approach, “ask yourself”.
If you want to see the approach then tries to learn from Nation Security Guard (NSG). The approach followed by them is really splendid. Why I am commenting on their approach because they make a plan first of their target and who can be affected with that. Target is militants in case of computer networks target is virus or hacker & civilians are affected in case of computer networks simple data packets will be affected. So NSG decided to go via roof instead of ground floor because they know that the militants sitting on top storey can fire them easily and civilians will be affected. The same when we the network is hacked or behaving like hell try to think like cool never do the things in hurry which creates mesh for you ahead.
Another thing which we need to learn from NSG is patience. Why I am talking about patience because sometimes we lose our patience during network attacks & did the things blindly. So never do such type of mistakes during network attacks; tries to collect the data; I know at that time your network is on stake and you are stakeholder. But mind one thing if you are not able to get the roots, roots can be collected in terms of data then the same can be happened at any time and at time you will not have any work around. In this way may be a small problem will get in your nerves and let your network down for long or short time.
One thing which I liked the most i.e. behaviour of politicians which was totally different. Instead of blaming to each other which they used to do but this time they come up as a single group and with one word need to save India. Really very realistic & patriotic approach. We as network operators or service providers need to follow the same approach instead of saying that my network is secure and I have nothing to do with other networks.
Now the time has come we need to pull up the reins of security instead of fighting with terror or network attacks. If you checked the major incidents they happened just because of lack of security. So we need to design the security model in such a way so that the risk of terrorism or network attacks should be minimized. What we are facing today it is just because of our mistakes?
At last I would like to say one thing never fight against terror always try to fight against security and get it implemented as soon as possible without losing our beloved ones or computer data.
Regards
shivlu jain
Click Here To Read Rest Of The Post...
Subscribe to:
Posts (Atom)