6PE command for IOS and XR
Hi, I was trying command mpls ipv6 source-interface on SRE3 code, look like there is no command like that on SRE. This command is important for locally generated packets. Have someone used this command? Also what is the command on XR 4.0.1 to achieve the same? Regards, Vikas
link-local address calculation
Hi, How to get link-local address from BIA. I have seen some information on Internet but it is not working for all. = The BIA in this case is cc00.0bfc.. The rules for the modified EUI-64 addressing are: •FFFE will be put in between the vendor-id (3 most significant bytes) and the extension-id (3 least significant bytes), which will lead to cc00.0bFF.FEfc. •Thereafter the seventh bit, known as universal/local bit, gets inverted. So first change the cc00 from hex to binary, which leads to 110011 0 0 and then invert the seventh bit (here a 0): 110011 1 0. Moved back to hex this will give CE00 •At last, change all points ‘.’ to colons ‘:’ and delete all leading zeros, then you got your link-local IPv6 address: FE80::CE00:BFF:FEFC:0 So if your BIA is 0008.209a.081b (bia 0008.209a.081b), how link-local be calculated. This is the link-local on router = IPv6 is enabled, link-local address is FE80::208:20FF:FE9A:81B Also on XR below is the link local address Loopback6 is Up, ipv6 protocol is Up, Vrfid is default (0x6000) IPv6 is enabled, link-local address is fe80::884c:2dff:fe84:8d75 I can not see any interface with BIA ending with 75 ... Can someone explain me this? Regards, Vikas
Re: Ipv6 addressing for Core network
HI Geroge, Thanks for the input. Appreciate some more info wrt TCAM usuage if possible. Another thought, I agree ip schema is individual preference, but I want to know the best practise (vague term best practice). Personally even I am in favor of /64 p-t-p. Regards, Vikas On Wed, Feb 9, 2011 at 12:11 PM, George Bonser gbon...@seven.com wrote: I am looking for the recommendation for core interfaces IP addressing schema for Ipv6. Some different views are (PE- P - PE, point to point link) as below - 1- Use Public Ipv6 with /122 and do not advertise to Internet 2- Use Public Ipv6 with /127 and do not advertise to Internet 3- Use Unique local ipv6 address 4- Use Public Ipv6 with /64 Also I am interested to understand the impact on TCAM ... Regards, Vikas I would use a /64 with ND turned off and static neighbors configured. TCAM impact will depend on vendor. Some vendors give you the option of storing the first 64 bits of a V6 IP or the entire address. Using a /64 means your CAM usage might be less depending on your vendor. If the addresses on the point-to-point links never accept or source direct traffic to/from outside your net, you can use whatever you want on them. ULA might be ok there. I am using public IPs but I filter traffic destined for them at the edge but to each their own choice. But if you use ULA you aren't going to be able to ping anything outside your net if you source the pings from the ULA interface. Just something to keep in mind. What you are asking is a matter of individual preference.
Ipv6 addressing for Core network
Hi, I am looking for the recommendation for core interfaces IP addressing schema for Ipv6. Some different views are (PE- P - PE, point to point link) as below - 1- Use Public Ipv6 with /122 and do not advertise to Internet 2- Use Public Ipv6 with /127 and do not advertise to Internet 3- Use Unique local ipv6 address 4- Use Public Ipv6 with /64 Also I am interested to understand the impact on TCAM ... Regards, Vikas
