Cisco - Tag - Fryguy's Blog

New Network Tools Section

Fryguy — Sun, 12 Apr 2026 21:29:42 +0000

I have been meaning to put together some network tools for a while now, and I finally got around to it. I added a new Network Tools section to the site with eight tools that I find myself needing on a regular basis. They all run in the browser – nothing gets sent to a server, they either do the math locally or call a public API directly.

Cisco Champion of Data Center

Fryguy — Fri, 13 Dec 2013 13:05:11 +0000

Some time ago, not sure how long ago, Cisco started a Cisco Champion program for people who are passionate about Cisco and active on social media ( twitter, Facebook, Google Plus, etc). I am glad to say that I and flattered and honored to be called a Cisco Champion Data Center.

Taking some words from the Champion site – http://www.cisco.com/web/about/facts_info/champions.html#~overview, , the Cisco Champion program is:

Passionate Experts, Global Champions for Change

What makes a Cisco Champion? Passion, plus a desire to share their perspectives with the community. There are Cisco Champions all over the world. They represent a variety of segments across the IT industry. And they offer their time to help others learn about Cisco and connect with Cisco in unique ways.

In addition to sharing their insights and expertise, Cisco Champions make a difference by:

Supporting their peers in social communities, forums, and networks
Sharing their relevant experiences and thoughts on Cisco blogs
Providing valuable feedback directly to Cisco
And more

Cisco Live 2012 Recap

Fryguy — Tue, 19 Jun 2012 12:15:00 +0000

Well, the time for Cisco Live 2012 has come and it has gone. I have now been home a few days and have almost recovered, I said almost recovered. Cisco Live is a long week for anyone, there are endless after-hour “meetings” that occur with different vendors; there is the World of Solutions that you can spend endless time in collecting spiff and learning about vendor products; there is the John Chambers CCIE/CCDE NetVet reception and the CCIE Party, the CAE, etc etc etc. Add all that together and add in a 3 hour time zone difference (for me at least), and it takes a few days for the body and mind to recover. Tom, being his normal self, already has his post done at NetworkingNerd – guess that is what happens when you take a few days off! 🙂
Well, now it is time for a nice recap of the week and its associated events, as well as the highlights.

Nexus 7009 – More information

Fryguy — Tue, 19 Jul 2011 12:00:38 +0000

A few months ago I did a quick post on the Nexus 7009 when it was pseudo announced (here ). When I was attending Cisco Live 2011 last week in Las Vegas I found out that they had a Nexus 7009 in their Data Center booth in World of Solutions for all to see. So, I figured I would post some updated information that I was able to gather or figure out. All this information was being openly spoken in the booth, nothing here was gathered from any other resource then what I was able to hear. To recap, below is a picture of the new family member, the 7009 along side its big brothers the 7010 and the 7018. As you can see there are some nice size differences. The Nexus 7009 us 14RU, the 7010 21RU, and the 7018 25RU. [][2]

Cisco Live Attendee Expectations

Fryguy — Tue, 21 Jun 2011 08:00:56 +0000

A few months ago (wow, has it been that long) I did a post on Cisco Live 2011 – Why you should go… and wanted to now follow that up with what you should expect while you are there as well as what you should bring with you. If this is your first time I hope that this helps, if this is your 2nd, 3rd, etc time – please post in the comments with suggestions. Each and every one of us experiences the event a little different, so sharing is always helpful and appreciated.
What do you need to bring with you for this event and what should you do to prepare? Pack a good size suitcase and leave room! You have the chance to get so many shirts, bags, whiz bangs, and other nick-knacks at World of Solutions you will need the space. Not to mention if you shop at the Cisco Store there and get shirts, books, golf balls, pens, etc – you will need a place to take all that stuff back with you. The first few years I would up shipping things back, and that does get expensive real quick!

Network Warrior – 2nd Edition

Fryguy — Mon, 13 Jun 2011 18:12:34 +0000

Network Warrior – 2nd Edition

Recently, O’Reilly published the long awaited Network Warrior 2nd Edition by Gary Donahue (aka GAD). This was a much anticipated update since technology has changed since the original publication back in 2007. I am glad to see the inclusion of the Cisco ASA, Cisco Nexus, and IPv6, and Voice – as well as a few others. Most (if not all) of the examples in the book are shown in different Cisco languages – CatOS, IOS, and also NX-OS. These examples are great for helping the ready to understand and see the differences ( as well as the evolution ) of the codes.

Cisco Archive and Configure

Fryguy — Mon, 06 Jun 2011 08:15:36 +0000

There has been some interesting discussions on configuration differences with IOS and JUNOS on Twitter the past few days. One of the biggest things has been the inclusion of a Rollback command in JUNOS; and to be perfectly honest, that has to be one of the best commands that JUNOS has!
In case you are not familiar with it, in JUNOS if you submit a change and then enter commit confirm (default 10 minutes), the router will not “save” the configuration change until you commit the change again. This way if you make a change, lock yourself out of the device, it will revert to the previous configuration and you should have your access back.
(some housekeeping)
Router/Switch Output
Commands
Notes

[edit]
user@host# commit confirmed
commit confirmed will be automatically rolled back in 10 minutes unless confirmed
commit complete
#commit confirmed will be rolled back in 10 minutes
By entering commit again, the change will become permenant
[edit]
user@host# commit

Now, what about IOS? Well, typically we do the reload in x command before we make a change, but is there another way? Well, yes there is! We have the archive command and the config replace command string that will perform a similar function to to the JUNOS command and less drastic then the reload in command.
So, lets first cover the archive command.
The archive command allows you to make an archive of the config either over a time-period (say 1440 minutes) or when the write-memory command is initiated. The archive can be stored in flash, tftp, ftp, or a few other places. To setup archiving:
Rack1R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
To enter the archive config, enter the archive command
Rack1R2(config)#archive
From there, you need to tell it 1) where to store the file and 2) what to call it.
Here it will be flash:/archive with a name of Rollback
Rack1R2(config-archive)#path flash:/archive/Rollback
Here I tell it to archive the previous config whenever the write-memory command is executed
Rack1R2(config-archive)#write-memory
Also, I might as well make sure that we back it up once a day at a minimum. Range is from 1 minute to 525600 minutes (1 year)
Rack1R2(config-archive)#time-period ?
<1-525600> Number of minutes to wait between archive creation
Rack1R2(config-archive)#time-period 1440
Rack1R2(config-archive)#
Now, if we look at the flash:/archive/ folder, what will we see? Lets look (I already have some saved in memory)
Rack1R2#dir flash:archive
Directory of flash:/archive/
17 -rw-        1806   Jun 3 2011 19:34:16 +00:00 Rollback-2
18 -rw-        1806   Jun 3 2011 19:35:02 +00:00 Rollback-3
16 -rw-        1744   Jun 3 2011 19:31:54 +00:00 Rollback-1
512057344 bytes total (328622080 bytes free)
Rack1R2#
As you can see, we have a few files there, each appended with a number (call it revision with highest being most recent). To check, use the show archive command
Rack1R2#show archive
There are currently 4 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-4
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3 <- Most Recent
4
5
6
7
8
9
10
11
12
13
14
Rack1R2#
So, what does all this mean and how does this relate to the commit confirm command in Junos? Good question! Here we go!
So, when you need to do a change, just execute the archive config command prior to the change. That will create a snapshot of the existing config in the archive directory.
Rack1R2#archive config

Lets take a look and see what revision we have saved:
Rack1R2#show archive
There are currently 5 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-5
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3
4       flash:/archive/Rollback-4 <- Most Recent
5
6
7
8
9
10
11
12
13
14
Rack1R2#
Now, there is another command that we need to know about – its the configure replace command! We can use that similar to the commit confirm command because of the archive command.
Rack1R2#configure replace flash:archive/Rollback-4 time 60
That is all good – lets test the command!

I have R1 and R2 configured like the diagram below, connected via Frame-Relay and all interfaces are in RIPv2

Here is the routing table and interface status on R2:
Rack1R2#sh ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route
Gateway of last resort is not set
150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
R       150.1.1.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
C       150.1.12.0/24 is directly connected, Serial4/0.1
R       150.1.11.0/24 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
R       150.1.111.1/32 [120/1] via 150.1.12.1, 00:00:23, Serial4/0.1
150.2.0.0/32 is subnetted, 3 subnets
C       150.2.222.2 is directly connected, Loopback2
C       150.2.22.2 is directly connected, Loopback1
C       150.2.2.2 is directly connected, Loopback0
Rack1R2#sh ip int br | ex un
Interface                  IP-Address      OK? Method Status                Protocol
Serial4/0.1                150.1.12.2      YES manual up                    up
Loopback0                  150.2.2.2       YES manual up                    up
Loopback1                  150.2.22.2      YES manual up                    up
Loopback2                  150.2.222.2     YES manual up                    up
Rack1R2#
Here is the same information for R1
Rack1R1#sh ip route
Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route
Gateway of last resort is not set
150.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
C       150.1.1.1/32 is directly connected, Loopback0
C       150.1.12.0/24 is directly connected, Serial4/0.1
C       150.1.11.0/24 is directly connected, Loopback1
C       150.1.111.1/32 is directly connected, Loopback2
150.2.0.0/32 is subnetted, 3 subnets
R       150.2.222.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1
R       150.2.22.2 [120/1] via 150.1.12.2, 00:00:12, Serial4/0.1
R       150.2.2.2 [120/1] via 150.1.12.2, 00:00:13, Serial4/0.1
Rack1R1#sh ip int br | ex un
Interface                  IP-Address      OK? Method Status                Protocol
Serial4/0.1                150.1.12.1      YES manual up                    up
Loopback0                  150.1.1.1       YES manual up                    up
Loopback1                  150.1.11.1      YES manual up                    up
Loopback2                  150.1.111.1     YES manual up                    up
Rack1R1#
Lets test the connectivity by PINGing R2 Loopback 2 from R1 Loopback2
Rack1R1#ping 150.2.222.2 so lo2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/60 ms
Rack1R1#
Good, now lets test the config replace command (IOS Rollback)
First, we will archive the config
Rack1R2#archive config
Now lets see what archives we have:
Rack1R2#sh archive
There are currently 6 archive configurations saved.
The next archive file will be named flash:/archive/Rollback-6
Archive # Name

1       flash:/archive/Rollback-1
2       flash:/archive/Rollback-2
3       flash:/archive/Rollback-3
4       flash:/archive/Rollback-4
5       flash:/archive/Rollback-5 <- Most Recent
[– SNIP –]

Ok, Rollback-5 is the most recent.
Now on R1 we will start a 1000 packet ping
Rack1R1#ping 150.2.222.2 so lo2 repeat 100
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Now that we have that started, lets move on
Now, on R2 we will execute the configure replace command, set the timer to 60 seconds, then shut down the Serial 4/0 (frame-relay) interface
Rack1R2#configure replace flash:/archive/Rollback-5 time 60
Timed Rollback: Backing up to flash:/archive/Rollback-7
It will now ask you to make sure you want to do this – checks and balances
This will apply all necessary additions and deletions
to replace the current running configuration with the
contents of the specified configuration file, which is
assumed to be a complete configuration, not a partial
configuration. Enter Y if you are sure you want to proceed. ? [no]: Y
Total number of passes: 0
Rollback Done
*Jun 3 21:43:22.026: Rollback:Acquired Configuration lock.
Rack1R2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rack1R2(config)#int ser 4/0
Rack1R2(config-if)#shut
Rack1R2(config-if)#
*Jun 3 21:43:28.274: %LINK-5-CHANGED: Interface Serial4/0, changed state to administratively down
*Jun 3 21:43:29.274: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to down
Rack1R2(config-if)
Hmm, if we look at the ping that we have going on R1 we see that it can no longer PING R2
Rack1R1#ping 150.2.222.2 so lo2 repeat 1000
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….
……..
Lets wait…. there, the config just rolled back on R2 and R1 can PING again!
Rack1R1#ping 150.2.222.2 so lo2 repeat 1000
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 150.2.222.2, timeout is 2 seconds:
Packet sent with a source address of 150.1.111.1
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!………………………….
…………………!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 94 percent (948/1000), round-trip min/avg/max = 56/57/240 ms
Rack1R1#
So what happened on R2? Here is the output on the console:
Rack1R2(config-if)#Timed Rollback: rolling to:flash:/archive/Rollback-7
!Pass 1
Neat, it will show you the commands it is about to enter!

!List of Commands:
interface Serial4/0
no shutdown
end
Total number of passes: 1
Rollback Done
*Jun 3 21:44:22.218: Rollback:Acquired Configuration lock.
Rack1R2(config-if)#
*Jun 3 21:44:22.778: %PARSER-3-CONFIGNOTLOCKED: Unlock requested by process ’21’. Configuration not locked.
Rack1R2(config-if)#
*Jun 3 21:44:24.586: %LINK-3-UPDOWN: Interface Serial4/0, changed state to up
*Jun 3 21:44:25.586: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial4/0, changed state to up
Rack1R2(config-if)#
If all is good after your change and you need to not roll-back, just issue the command configure confirm and it will cancel the rollback._
_
Rack1R2#configure confirm

If you already issued that command, you will get the following output:
Rack1R2#configure confirm
%No timed rollback pending
Rack1R2#
Not as simple as the JUNOS commands, but is still valuable in the IOS world!

R1 Config Here
R2 Config Here

Cisco Press :: IPv6 for Enterprise Networks

Fryguy — Fri, 06 May 2011 12:38:55 +0000

We have all been hearing about IPv6 for a few years now. There have been numerous white papers published, blog posts, audio podcasts, as well as the normal twitter chatter on the topic. Lately this topic has come to the forefront more and more since the RIR have handed out the last of the IPv4 /8 networks to the regional registrars. So what does all this mean to you and I? Well, if you have not fully embraced IPv6, the time has definitely come.
Luckily Cisco Press has recently released IPv6 for Enterprise Networks (Networking Technology) for our reading pleasure. Originally I was going to wait until Cisco Live 2011 to get this book, but I just could not wait and my friend, Jamie, was able to help me get it sooner. I am glad that I did not wait! This book is a great read and will help the reader to understand IPv6 as well as help to design and deploy a network.
The book consists of 12, well formatted chapters. They take you from the market drivers, to designing and services, deployment, and all the way to the data center and testing. What is nice about this book is the progression on the topics. You do not really need to know IPv6 to read this book, it will actually guide you through the whys and hows then onto the how to as well as testing. It is nice to have a book that will cover most of the topics that one will experience in an Enterprise design.
The first two chapters in the book talk about the market drivers for IPv6, these are some of the whys that people are wondering. This is a pretty quick chapter as the killer application is not really out there yet, but is sure to be coming (my best guess will be Asian/Pac e-commerce). What this chapter does elude to is that this is a good time to be able to restructure your network in a more efficient design. Consider this, you probably inherited your current network and the design that is currently in place. With a transition to IPv6, you now have the opportunity to reconsider what was done and determine were you should take it. The first chapter does good at giving you some points to consider as you read on and helps you to understand some of the underlying design scenarios.
The next two chapters, 3 and 4, start to go over how IPv4 and IPv6 will co-exist in the network and some of the ways to approach this challenge. There are dual-stacking, 6-to-4 tunnels, MPLS, and the good old duct tape of the network – GRE. It also continues to talk about services and some of the routing options that one has to consider. Service such as multicast and QoS are discussed for a decent amount of pages. These tend to be some of the more important items in an enterprise network. These chapters also discuss the different routing protocol options – OSPFv3, EIGRPv6, and IS-IS with a mention of BGP. What does surprise me, there is no discussion on LISP 🙂 Ok, that might have been asking for a bit much, but I do like LISP.
I think that Chapter 5 is a really important chapter in some ways. This is the chapter where Planning an IPv6 Deployment is discussed. This is a topic that should not be taken lightly but one that should be a primary focus. After all the technology and numbers, all that you really have to stand upon is good design. As i mentioned before, what is nice with IPv6 is that you do not have to base your new design on the existing design, you can actually rethink everything and start fresh. For instance, if you are currently running EIGRP but want to move to OSPF, deploying IPv6 is the time to start that move. The two protocols (v4 and v6) are separate from each other.
The next chapters, 6 through 10, are the heart of this book. Discussed in some good detail is deploying IPv6 in Campus, Virtualized, WAN/Branch, Data Centers as well as Remote Access. Each of these topics has a good chapter dedicated to it and there are many things that one needs to consider with each of these deployment scenarios. Again, it all comes down to the choices made during the design and testing phase.
Chapter 11 is a nice chapter on the aspects of Managing IPv6 Networks. It covers the different ways to monitor and secure various parts of the network. It is nice to actually see a chapter dedicated to some of the stuff that is quickly overlooked during a design an deployment – how to manage and support all the work that you have done. Most of this stuff is usually figured out near the end of a project when we hand off things to the NOC – and they say IPvWhat?
The final chapter in the book was a welcomed surprise to me. This chapter actually talks about how to setup a lab to test IPv6. It gives some good sample setups that should help the person be able to play with the protocol as well as test different scenarios. Granted, some of the hardware suggested might be a bit out of reach for most of us (VSS, ISR, etc) – but it is a good starting point to see what you can do. One can easily see ways to substitute certain hardware for other hardware so one can learn and develop. If you are going to roll some of this into production, test hardware is invaluable for knowing the problems before they are experienced in a live network.
Overall it is a good read and one that should be handy to those who are working with IPv6 right now. Not only can you use the information within the book for your own knowledge, but it gives you information on how you can explain it to others. One of the most difficult things that I come across in an enterprise is explaining difficult topics. This book helps me to find ways to explain things in ways that others might be able to understand.

Cisco Live 2011 Schedule

Fryguy — Wed, 20 Apr 2011 15:22:21 +0000

Figured I would put up a quick post with my current Cisco Live class schedule. This is my schedule as of today and, as always, is subject to change. All times are in Vegas time!

Saturday
	Fly and check in at Mandalay Bay as well as register for the event

Sunday
	8:00 – 17:00	TECDCT-8001	Next Generation Data Center Infrastructure

Monday	9:30 – 11:30	BRKARC-3470	Cisco Nexus 7000 Switch Architecture
	12:30 – 14:30	BRKARC-3471	Cisco NXOS Software – Architecture
	15:00 – 17:00	BRKRST-2335	IS-IS Network Design and Deployment

Tuesday	8:00 – 9:30	BRKRST-3045	LISP – A Next Generation Networking Architecture
	10:00 – 11:00	GENKEY-4700	Keynote and Welcome Address
	12:30 – 14:30 15:00 – 15:30	BRKCOM-1005 GENNOC-9190	UCS Systems Architecture Overview Cisco Live NOC Tour (CCIE/NetVet)
	16:00 – 18:00	BRKCRS-3144	Troubleshooting Cisco Nexus 7000 Series Switches

Wednesday
	8:00 – 10:00	BRKCOM-2006	UCS Reference Architecture for Enterprise Applications
	10:30 – 11:30	GENKEY-4701	Cisco Technology Keynote
	12:30 – 14:30	BRKDCT-2121	Virtual Device Context (VDC) Designing and Implementation Considerations with Nexus
	16:00 – 18:00	BRKVIR-3013	Deploying and Troubleshooting the Nexus 1000V virtual switch

Thursday
	8:00 – 10:00	BRKCOM-1002	Data Center Architectures and Virtual Private Data Centers with UCS
	10:30 – 11:30	GENDCT-4642	Town Hall: Data Center
	12:00 – 14:00	BRKARC-3472	NX-OS Routing & Layer 3 Switching
	14:30 – 15:30	GENKEY-4702	Closing Keynote: William Shatner
	16:00 – 17:30	BRKMPL-2108	Global WAN Redesign Case Study

Friday
	Fly home!

The Nexus 7009 – and what is this, Nexus 7006?!??!?!?!

Fryguy — Mon, 04 Apr 2011 12:00:52 +0000

Since Cisco posted that picture the other day, you know this one:

Well, since that picture was posted there has been some buzz around the chassis in the twitter feeds. Not much is officially know about this box – but the picture above proves it does exist. Not only that, I recall seeing a picture from Cisco Live 2011 – London where the EMC booth had one of these Nexus 7009 looking switches in their booth. Well here is some additional information that I have located using the assumed part number of N7K-C7009
On Cisco’s website they have a MIB posted called CISCO-ENTITY-VENDORTYPE-OID-MIB.my (clicking on that MIB will allow you to view/download it – original link here ). From what I can gather in the MIB – the Nexus 7009 will have the new Fabric-2 cards, no Fab-1 cards are even listed for this chassis. When you search the MIB, you can find the following information:
cevChassisN7Kc7009              OBJECT IDENTIFIER ::= { cevChassis 932 } — N7K-C7009 nexus-9-slot chassis
cevBackplaneN7Kc7009                    OBJECT IDENTIFIER ::= { cevBackplane 57 }       — MosPort9 N7K-C7009 Nexus-9-slot-backplane
cevFanN7Kc7009FanTray           OBJECT IDENTIFIER ::= { cevFan 129 } — N7K-C7009-FAN Trinacria-fan-nexus9slot
cevN7Kc7009Fab2         OBJECT IDENTIFIER ::= { cevModuleN7KType 14 }           — dijon9 N7K-C7009-FAB2 Fabric for Nexus7000 9slot boxster
Bonus information contained within the MIB is information on the, yet unannounced, Nexus 7006!
Granted, this is only speculation and such – but the MIB information matches what the 7009 has as well. Only time will tell if this is true.
cevChassisN7Kc7006              OBJECT IDENTIFIER ::= { cevChassis 1054 } — Nexus7000 6slot elsie n7k chassis N7K-C7006
cevBackplaneN7Kc7006                    OBJECT IDENTIFIER ::= { cevBackplane 60 }       — Nexus7000 6slot elsie n7k backplane N7K-C7006
cevFanN7Kc7006FanTray           OBJECT IDENTIFIER ::= { cevFan 147 } — N7K-C7006-FAN fan for nexus 6slot-chassis
I also did some searching and found this list of Nexus 7009 Part Numbers, and my assumed descriptions (in blue) of what they are.
N7K-C7009-ACC-KIT    Nexus 7009 Accessory Kit
N7K-C7009-BSK             Nexus 7009 Bottom Support Kit
N7K-C7009-CAB-TOP    Nexus 7009 Top section Cable Management?
N7K-C7009-CM-BLK      Nexus 7009 Cable Management Blank? Unknown
N7K-C7009-F-BLANK Nexus 7009 Fabric Blank Interface ?
N7K-C7009-FAB-2        Nexus 7009 Fabric 2 Card
N7K-C7009-FAN            Nexus 7009 Fan Tray
N7K-C7009-FD-MB       Nexus 7009 Front Dook Kit
N7K-C7009-L                  Nexus 7009 License
N7K-C7009-RMK           Nexus 7009 Rack Mount Kit
N7K-C7009-SHPPKG    Nexus 7009 Shipping package
N7K-C7009-XL       Nexus 7009 XL
L-N7K-C7009-XL           Nexus 7009 Scalable Feature License (allows XL featuers without requiring a hardware module change)
Another part-number that I have found that is NOT referenced on the Cisco site is this 5.6KW power supply. Wonder if the 7009 can support a smaller power supply, or this is for the Nexus 7006
N7K-AC-5.6KW         5.6kW AC Power Supply