Cisco Design Best Practices for Data Center

This tool is provided to help users gain access to design and test informatio in and intuitive, interactive way.

To find the network design guidance you need for a specific data center project, go to the CVD-I tab and navigate the topology.

To access the test descriptions, results, and device configuration of the latest fully test data center network architecture, go to the CVD-II tab.

Navigate the topology to find the test and configurations associated with any specific solution or device.

http://www.cisco.com/cdc_content_elements/flash/dcap3/

Ipv6 Overlapping Errors?

R2(config)#int lo0
R2(config-if)#ipv addr fec0::2:1/112
% FEC0::2:1/112 can not be configured on Loopback0, overlapping
R2(config-if)# ipv addr FEC0::12:3/112
% FEC0::12:3/112 can not be configured on Loopback0, overlapping
R2(config-if)# ipv addr FEC0::222:1/112
R2(config-if)# ipv addr FEC0::2:1/112  

R2(config-if)#do sh ver | i IOS
Cisco IOS Software, 3600 Software (C3640-JS-M), Version 12.4(18), RELEASE SOFTWARE (fc1)

Why am I getting these overlapping errors?

IPv6 at the 2008 Olympics

In my previous post I threw out a few thoughts about the idea of enticing users to switch to IPv6 – a sort of variation on the long-running “we need an IPv6 killer app” argument – and the contradictions such enticement efforts would present: Mainly that IP of any version should be transparent to end-users who only care about services, not how those services are delivered. Any enticements bring IPv6 into the spotlight, where it should not be (except for routing and infrastructure geeks like me).

Looking at the other side of this transparency issue, just getting IPv6 rolled out brings unwanted attention to it: Users might have to upgrade operating systems, and might encounter problems reaching some destinations and services as the public Internet becomes split between an IPv4 world and an IPv6 world.

Read more from IPv6 at the 2008 Olympics by Jeff Doyle.