03-22-2013 12:08 AM - edited 03-07-2019 12:25 PM
Hi Team,
Device Name :ASR1002
Problem Description : When we add static route for below subnet we got a error like " %Inconsistent address and mask"
ip route 10.122.171.0 255.255.240.0 10.122.0.39
Error : %Inconsistent address and mask
After change the subnet like ip route 10.122.170.0 255.255.240.0 10.122.0.39 It was fine.
What is the problem on that subnet? ( It's not takeing 10.122.171.0/20 only accept 10.122.170.0/20.
Can you please explain.
Thanks...
Regards,
Kannan
Solved! Go to Solution.
03-22-2013 01:38 AM
Hello Kannan,
the router should check if the proposed prefix address is in accordance with the proposed subnet mask/prefix length
A subnet mask of 255.255.255.240.0 means a prefix length of 20 -> 12 host bits from rightmost less significant bit
The prefix base address must have all host bits set to 0, that is last 12 bits of the address must be zero.
If you look at the two proposed subnet addresses
10.122.171.0 and 10.122.170.0 you see that in the third octect the first violates the rule because there multiple bits set to 1 in 171 but also the second one violates the rule!
171 in binary is
1010||1011
170 in binary is
1010||1010
note : with || I'm indicating the network part to host part boundary that is in the middle of the third byte (the interesting octect)
the prefix base address is 10.122.160.0/20 and so also 10.122.170/20 should be rejected by router CLI.
This looks like to be a bug in my opinion. Are you sure you have typed 10.122.170.0 in second attempt?
Hope to help
Giuseppe
03-22-2013 01:38 AM
Hello Kannan,
the router should check if the proposed prefix address is in accordance with the proposed subnet mask/prefix length
A subnet mask of 255.255.255.240.0 means a prefix length of 20 -> 12 host bits from rightmost less significant bit
The prefix base address must have all host bits set to 0, that is last 12 bits of the address must be zero.
If you look at the two proposed subnet addresses
10.122.171.0 and 10.122.170.0 you see that in the third octect the first violates the rule because there multiple bits set to 1 in 171 but also the second one violates the rule!
171 in binary is
1010||1011
170 in binary is
1010||1010
note : with || I'm indicating the network part to host part boundary that is in the middle of the third byte (the interesting octect)
the prefix base address is 10.122.160.0/20 and so also 10.122.170/20 should be rejected by router CLI.
This looks like to be a bug in my opinion. Are you sure you have typed 10.122.170.0 in second attempt?
Hope to help
Giuseppe
03-22-2013 02:44 AM
Thanks, Yea you are right...
The Ip address is 10.122.160.0/20 (typo error) not 10.122.170.0/20.
Thanks for update.
Regards,
Senthilkumar
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide