Comments for CCIEZone.com http://www.cciezone.com Ramblings of networking & programming experiences, the occasional hardware tweaks and other errata. Mon, 02 Aug 2010 01:48:03 -0700 http://wordpress.org/?v=abc hourly 1 Comment on BGP Security Features… by Cciezone http://www.cciezone.com/?p=170&cpage=1#comment-4004 Cciezone Mon, 02 Aug 2010 01:48:03 +0000 http://www.cciezone.com/?p=170#comment-4004 <strong>Cciezone...</strong> [...] something about cciezone[...]... Cciezone…

[...] something about cciezone[...]…

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Tim http://www.cciezone.com/?p=210&cpage=1#comment-2767 Tim Mon, 29 Mar 2010 15:06:19 +0000 http://www.cciezone.com/?p=210#comment-2767 Yes - this is true, DTP is no longer supported in NX-OS. See my post at http://www.cciezone.com/?p=293 for a short list of some of the "biggie" protocols that are retired in NX-OS. Yes – this is true, DTP is no longer supported in NX-OS. See my post at http://www.cciezone.com/?p=293 for a short list of some of the “biggie” protocols that are retired in NX-OS.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Tim http://www.cciezone.com/?p=210&cpage=1#comment-2764 Tim Mon, 29 Mar 2010 14:45:02 +0000 http://www.cciezone.com/?p=210#comment-2764 It depends on the environment (requirements). If FCoE is on the roadmap, NX-OS is the only option. In multi-tenant environments (such as IAAS providers), the ability to carve out VDCs on a N7k can be an instant differentiator. Likewise, virtualization on Nexus 7000s and Catalyst 6500s are fundamentally different - VSS combines two physical switches into a single logical switch, while the N7k takes a physical box and segments it into multiple logical boxes. If we need to support service-modules (ACE, FWSM, WiSM, etc.), we'll need to have 6500s somewhere in the network (aggregation layer typically), so we might want to use them instead of Nexus in the core of the network. Although the oversubscription rates are the same between the Catalyst 6500 and N7k (4:1 in shared mode), the N7k does offer greater concentration of 10Gbps interfaces, making the N7k a more viable option (or only option if we have enough 10Gbps interfaces that we can't squeeze into a 6509E chassis) in instances where we are heavily relying on 10Gbps. I personally like the direction that NX-OS is going, in that it's going in a standards direction (getting rid of a lot of the proprietary legacy Cisco protocols), is finally offering CIDR notation (welcome to the 20th century!) and many other improvements. NX-OS and IOS are both great solutions - there's no one-size-fits-all answer as to which is best - depends on the drivers within the environment. It depends on the environment (requirements). If FCoE is on the roadmap, NX-OS is the only option. In multi-tenant environments (such as IAAS providers), the ability to carve out VDCs on a N7k can be an instant differentiator. Likewise, virtualization on Nexus 7000s and Catalyst 6500s are fundamentally different – VSS combines two physical switches into a single logical switch, while the N7k takes a physical box and segments it into multiple logical boxes. If we need to support service-modules (ACE, FWSM, WiSM, etc.), we’ll need to have 6500s somewhere in the network (aggregation layer typically), so we might want to use them instead of Nexus in the core of the network.

Although the oversubscription rates are the same between the Catalyst 6500 and N7k (4:1 in shared mode), the N7k does offer greater concentration of 10Gbps interfaces, making the N7k a more viable option (or only option if we have enough 10Gbps interfaces that we can’t squeeze into a 6509E chassis) in instances where we are heavily relying on 10Gbps.

I personally like the direction that NX-OS is going, in that it’s going in a standards direction (getting rid of a lot of the proprietary legacy Cisco protocols), is finally offering CIDR notation (welcome to the 20th century!) and many other improvements. NX-OS and IOS are both great solutions – there’s no one-size-fits-all answer as to which is best – depends on the drivers within the environment.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by cisco sfp http://www.cciezone.com/?p=210&cpage=1#comment-2726 cisco sfp Sat, 27 Mar 2010 06:54:45 +0000 http://www.cciezone.com/?p=210#comment-2726 So which one you would recommend to go with NX - OS or IOS. So which one you would recommend to go with NX – OS or IOS.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by T http://www.cciezone.com/?p=210&cpage=1#comment-2554 T Wed, 10 Mar 2010 23:17:27 +0000 http://www.cciezone.com/?p=210#comment-2554 Also, not that in a discrepancy with IOS, at least in N5K's, ports are either trunk/on, or they are access. There is no dynamic/desirable anymore, or at least not yet. Also, not that in a discrepancy with IOS, at least in N5K’s, ports are either trunk/on, or they are access.

There is no dynamic/desirable anymore, or at least not yet.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Nusrat http://www.cciezone.com/?p=210&cpage=1#comment-2435 Nusrat Wed, 24 Feb 2010 16:55:56 +0000 http://www.cciezone.com/?p=210#comment-2435 On Nexus 7000 system: version 4.2(3), show feature works great. On Nexus 7000 system: version 4.2(3), show feature works great.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Tim http://www.cciezone.com/?p=210&cpage=1#comment-1896 Tim Fri, 12 Feb 2010 14:14:26 +0000 http://www.cciezone.com/?p=210#comment-1896 Thank you for confirming this on the Nexus 7000! I've tested the <em>show feature</em> command on the latest NX-OS for the Nexus 5000 (NX-OS 4.1(3)N2(1a)) and it works as well. It sounds like it was on the NX-OS development path, but not integrated into the earlier versions of NX-OS and that the tech writers (whoever handles the NX-OS documentation) hadn't received notice that it wasn't implemented. Having this command available is pretty handy, as a lot of features are just that - features that need to be enabled. Thank you for confirming this on the Nexus 7000! I’ve tested the show feature command on the latest NX-OS for the Nexus 5000 (NX-OS 4.1(3)N2(1a)) and it works as well. It sounds like it was on the NX-OS development path, but not integrated into the earlier versions of NX-OS and that the tech writers (whoever handles the NX-OS documentation) hadn’t received notice that it wasn’t implemented. Having this command available is pretty handy, as a lot of features are just that – features that need to be enabled.

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Jim Baug http://www.cciezone.com/?p=210&cpage=1#comment-1881 Jim Baug Thu, 11 Feb 2010 21:45:16 +0000 http://www.cciezone.com/?p=210#comment-1881 If you use the command show feature it will show the features enabled on version 4.2(2a). If you use the command show feature it will show the features enabled
on version 4.2(2a).

]]> Comment on A Primer on Some of the Differences Between IOS and NX-OS by Some NX-OS features can’t be manually enabled | CCIEZone.com http://www.cciezone.com/?p=210&cpage=1#comment-1877 Some NX-OS features can’t be manually enabled | CCIEZone.com Wed, 10 Feb 2010 18:42:22 +0000 http://www.cciezone.com/?p=210#comment-1877 [...] this command doesn’t exist today in NX-OS (at least the versions that I’ve worked with). See this article for more [...] [...] this command doesn’t exist today in NX-OS (at least the versions that I’ve worked with). See this article for more [...]

]]> Comment on Methods for connecting FEXs by Why EtherChannels should be used for FEX interfaces | CCIEZone.com http://www.cciezone.com/?p=235&cpage=1#comment-1863 Why EtherChannels should be used for FEX interfaces | CCIEZone.com Mon, 08 Feb 2010 18:40:41 +0000 http://www.cciezone.com/?p=235#comment-1863 [...] the same example environment that we’ve been using (see this article), FEX 100 is up, using [...] [...] the same example environment that we’ve been using (see this article), FEX 100 is up, using [...]

]]>