<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Nexus - Tag - Fryguy's Blog</title><link>https://hugo.fryguy.net/tags/nexus/</link><description>Nexus - Tag - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 19 Apr 2012 14:10:18 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/tags/nexus/" rel="self" type="application/rss+xml"/><item><title>Cisco Nexus Show Tech-Support – aka TAC-PAC</title><link>https://hugo.fryguy.net/2012/04/19/cisco-nexus-show-tech-support-aka-tac-pac/</link><pubDate>Thu, 19 Apr 2012 14:10:18 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/04/19/cisco-nexus-show-tech-support-aka-tac-pac/</guid><description><![CDATA[<p align="center">
  
</p>
<p>The inevitable TAC call and the request for a Show Tech to help with the support. Normally this is not a big problem on most systems, but if you ever try this on somehting like a Nexus 7000 – it takes a loooooong time and pulls well over 100 megs of information in that file. Capturing this output to a terminal is a test of patience (lets not mention console), or even if you redirect it to the bootflash it can still take some time. Then, there is getting a 100+ meg file copied from the bootflash to your computer, etc etc etc. I did do a quick post some time ago about using GZip to compress the file – you can find that post <a href="/2011/01/25/nexus-7000-and-the-show-tech-command-gzip-too/" target="_blank" rel="noopener noreferrer">here</a>.<br>
But that is not what this post is about, this post is about a command called TAC-PAC. TAC-PAC seems to be a little known command to most people who have never run into a problem and had to pull a show tech of a N7K, of for that matter any NX-OS platform. I was able to confirm this command on Nexus 7000, 5000, and 1000 as well as the SAN MDS.<br>
So, what is TAC-PAC? It is a single command that redirects the output of show tech-support details to a file, and then automatically compresses it for you. One command – nice and simple. The only thing that you will still have to do is pull the file via FTP or so.</p>]]></description></item><item><title>CCIE Data Center Hardware Cost Estimate</title><link>https://hugo.fryguy.net/2012/03/20/ccie-data-center-hardware-cost-estimate/</link><pubDate>Tue, 20 Mar 2012 17:20:36 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/03/20/ccie-data-center-hardware-cost-estimate/</guid><description>&lt;p align="center">
  
&lt;/p>
&lt;p>That picture about describes the cost of the new CCIE Data Center Hardware. Keep in mind, that this is list price – and my best uneducated guess at what we will see on the lab in the terms of hardware and quantity.  Regardless, I think I will nickname this new certification – The Million Dollar CCIE!&lt;/p></description></item><item><title>Nexus 7000 Modules and their Racing Heritage</title><link>https://hugo.fryguy.net/2011/08/01/nexus-7000-modules-and-their-racing-heritage/</link><pubDate>Mon, 01 Aug 2011 12:08:42 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/08/01/nexus-7000-modules-and-their-racing-heritage/</guid><description><![CDATA[<p><a href="/wp-content/uploads/2011/07/Nurburgring.jpg" rel=""></a><br>
I figured I would take a few moments and blog about the different Nexus 7000 I/O modules families – the M1 and F1 (formerly D1).  It is my understanding that the M in M1 stands for Multifuction and the F in F1 stands for Fabric/FCOE (or fast, depending on who you ask) .  So, can you sense a car theme here with this line-up?  M1?  F1?  Well, it only gets better – read on!<br>
(Update 8/7/2012) – Barry Reyes <a href="http://twitter.com/r0ckwell" target="_blank" rel="noopener noreferrer">(Twitter)</a> posted a picture on twitter about Formula 1 Racking and the Nexus line cards.  Below is that picture:<br>
<a href="/wp-content/uploads/2011/08/RaceCars.jpg" rel=""></a><br>
 <br>
First lets start with the M1 line cards – the N7K-M108X2-12L, N7K-M132XP-12, N7K-M148GT/S, N7K-M148GT/S-11L, N7K-M102CF-22L and N7K-M106FQ-23L.  Some of the common features to all the M1 series of line cards is that they are L2/L3 capable, will support LISP as well as OTV.<br>
 </p>
  
The N7K-M108X2-12L is a 8-port 10G line card that uses the X2 series of GBICs.  The X2 GBICs that are supported include the SR, LR, LRM, ER, ZR, LX4 and the CX4.  This card was named after the <a href="http://en.wikipedia.org/wiki/Adelaide_Street_Circuit" target="_blank" rel="noopener noreferrer">Adelaide Street Circuit </a>in South Australia.  Some of the specs of this card are:]]></description></item><item><title>Nexus 7009 – More information</title><link>https://hugo.fryguy.net/2011/07/19/nexus-7009-more-information/</link><pubDate>Tue, 19 Jul 2011 12:00:38 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/07/19/nexus-7009-more-information/</guid><description>  
&amp;nbsp;  
A few months ago I did a quick post on the Nexus 7009 when it was pseudo announced (&lt;a href="http://blog.fryguy.net/2011/04/04/the-nexus-7009-and-what-is-this-nexus-7006/" target="_blank" rel="noopener noreferrer">here&lt;/a> ).  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]</description></item><item><title>Cisco Live 2011 – Sunday – Next Gen Data Center Infrastructure</title><link>https://hugo.fryguy.net/2011/07/11/cisco-live-2011-sunday-next-gen-data-center-infrastructure/</link><pubDate>Mon, 11 Jul 2011 04:04:00 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/07/11/cisco-live-2011-sunday-next-gen-data-center-infrastructure/</guid><description><![CDATA[<p style="text-align: center;">
  <a href="/wp-content/uploads/2011/07/Sunday.jpg"></a>
</p>
<p style="text-align: left;">
  Well, Day two of Cisco Live 2011 for me (for some this is your first day as you are still arriving).
</p>
<p style="text-align: left;">
  For me, I am taking an 8 hour Techtorial on Next Generation Data Center Infrastructure TECDCT-8001.  This is a paid seminar that has covered some great material &#8211; and probably help to generate some future blog posts as well!
</p>
<p style="text-align: left;">
  Mike Herbert took the first part of the class and did a great review of some of the changes that have happened in the data center over the past few years. From the evolving 3-tier architecture with Spanning Tree and such all the way to Fabric Path and TRILL.  Nothing was really in depth but was a great setting of the stage for the day.  Some of the things that I liked was the discussion on the Data Center Standards and where different things are in the flow.  Another nice discussion was data center cabling and the potential future of cabling.  From the traditional home-run cabling that many of us use today to the discussion of top of rack (TOR) and end of row (EOR) drivers with regards to 10g and beyond cabling.  Problems discussed where primarily the cost of running those lengths of cables to the cross-talk potentials due to the power required to drive the data.  Oh yeah, Mike gets some bonus points for mentioning LISP during the presentation as well.
</p>
<p style="text-align: left;">]]></description></item><item><title>Cisco Live 2011 Schedule</title><link>https://hugo.fryguy.net/2011/04/20/cisco-live-2011-schedule/</link><pubDate>Wed, 20 Apr 2011 15:22:21 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/04/20/cisco-live-2011-schedule/</guid><description><![CDATA[  
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!
<table border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="97" valign="top">
<strong>Saturday</strong>
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td colspan="3" width="528" valign="top">
Fly and check in at Mandalay Bay as well as register for the event
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Sunday</strong>
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
8:00 – 17:00
</td>
<td width="129" valign="top">
TECDCT-8001
</td>
<td width="295" valign="top">
Next Generation Data Center Infrastructure
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Monday</strong>
</td>
<td width="103" valign="top">
9:30 – 11:30
</td>
<td width="129" valign="top">
BRKARC-3470
</td>
<td width="295" valign="top">
Cisco Nexus 7000 Switch Architecture
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
12:30 – 14:30
</td>
<td width="129" valign="top">
BRKARC-3471
</td>
<td width="295" valign="top">
Cisco NXOS Software – Architecture
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
15:00 – 17:00
</td>
<td width="129" valign="top">
BRKRST-2335
</td>
<td width="295" valign="top">
IS-IS Network Design and Deployment
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Tuesday</strong>
</td>
<td width="103" valign="top">
8:00 – 9:30
</td>
<td width="129" valign="top">
BRKRST-3045
</td>
<td width="295" valign="top">
LISP – A Next Generation Networking Architecture
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
10:00 – 11:00
</td>
<td width="129" valign="top">
GENKEY-4700
</td>
<td width="295" valign="top">
Keynote and Welcome Address
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
12:30 – 14:30<br /> 15:00 &#8211; 15:30
</td>
<td width="129" valign="top">
BRKCOM-1005<br /> GENNOC-9190
</td>
<td width="295" valign="top">
UCS Systems Architecture Overview<br /> Cisco Live NOC Tour (CCIE/NetVet)
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
16:00 – 18:00
</td>
<td width="129" valign="top">
BRKCRS-3144
</td>
<td width="295" valign="top">
Troubleshooting Cisco Nexus 7000 Series Switches
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Wednesday</strong>
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
8:00 – 10:00
</td>
<td width="129" valign="top">
BRKCOM-2006
</td>
<td width="295" valign="top">
UCS Reference Architecture for Enterprise Applications
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
10:30 – 11:30
</td>
<td width="129" valign="top">
GENKEY-4701
</td>
<td width="295" valign="top">
Cisco Technology Keynote
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
12:30 – 14:30
</td>
<td width="129" valign="top">
BRKDCT-2121
</td>
<td width="295" valign="top">
Virtual Device Context (VDC) Designing and Implementation Considerations with Nexus
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
16:00 – 18:00
</td>
<td width="129" valign="top">
BRKVIR-3013
</td>
<td width="295" valign="top">
Deploying and Troubleshooting the Nexus 1000V virtual switch
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Thursday</strong>
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
8:00 – 10:00
</td>
<td width="129" valign="top">
BRKCOM-1002
</td>
<td width="295" valign="top">
Data Center Architectures and Virtual Private Data Centers with UCS
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
10:30 – 11:30
</td>
<td width="129" valign="top">
GENDCT-4642
</td>
<td width="295" valign="top">
Town Hall: Data Center
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
12:00 – 14:00
</td>
<td width="129" valign="top">
BRKARC-3472
</td>
<td width="295" valign="top">
NX-OS Routing & Layer 3 Switching
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
14:30 – 15:30
</td>
<td width="129" valign="top">
GENKEY-4702
</td>
<td width="295" valign="top">
Closing Keynote: William Shatner
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
16:00 – 17:30
</td>
<td width="129" valign="top">
BRKMPL-2108
</td>
<td width="295" valign="top">
Global WAN Redesign Case Study
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
<strong>Friday</strong>
</td>
<td width="103" valign="top">
</td>
<td width="129" valign="top">
</td>
<td width="295" valign="top">
</td>
</tr>
<tr>
<td width="97" valign="top">
</td>
<td colspan="3" width="528" valign="top">
Fly home!
</td>
</tr>
</table>]]></description></item><item><title>The Nexus 7009 – and what is this, Nexus 7006?!??!?!?!</title><link>https://hugo.fryguy.net/2011/04/04/the-nexus-7009-and-what-is-this-nexus-7006/</link><pubDate>Mon, 04 Apr 2011 12:00:52 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/04/04/the-nexus-7009-and-what-is-this-nexus-7006/</guid><description><![CDATA[<p>Since Cisco posted that picture the other day, you know this one:<br>
<a href="/wp-content/uploads/2011/03/5571204273_18e550b292_o.jpg" rel=""></a><br>
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<br>
On Cisco’s website they have a MIB posted called <a href="http://dl.dropbox.com/u/5753029/CISCO-ENTITY-VENDORTYPE-OID-MIB.my" title="MIB Link" target="_blank" rel="noopener noreffer ">CISCO-ENTITY-VENDORTYPE-OID-MIB.my</a> (clicking on that MIB will allow you to view/download it – original link <a href="http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=CISCO-ENTITY-VENDORTYPE-OID-MIB" target="_blank" rel="noopener noreferrer">here </a>).  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:<br>
cevChassisN7Kc7009              OBJECT IDENTIFIER ::= { cevChassis 932 }  — N7K-C7009 nexus-9-slot chassis<br>
cevBackplaneN7Kc7009                    OBJECT IDENTIFIER ::= { cevBackplane 57 }       — MosPort9 N7K-C7009 Nexus-9-slot-backplane<br>
cevFanN7Kc7009FanTray           OBJECT IDENTIFIER ::= { cevFan 129 } — N7K-C7009-FAN  Trinacria-fan-nexus9slot<br>
cevN7Kc7009Fab2         OBJECT IDENTIFIER ::= { cevModuleN7KType 14 }           — dijon9 N7K-C7009-FAB2 Fabric for Nexus7000 9slot boxster<br>
<strong><span style="color:#0000ff;">Bonus information contained within the MIB is information on the, yet unannounced,</span> <span style="color:#ff0000;">Nexus 7006!</span></strong><br>
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.<br>
cevChassisN7Kc7006              OBJECT IDENTIFIER ::= { cevChassis 1054 } — Nexus7000 6slot elsie n7k chassis N7K-C7006<br>
cevBackplaneN7Kc7006                    OBJECT IDENTIFIER ::= { cevBackplane 60 }       — Nexus7000 6slot elsie n7k backplane N7K-C7006<br>
cevFanN7Kc7006FanTray           OBJECT IDENTIFIER ::= { cevFan 147 } — N7K-C7006-FAN  fan for nexus 6slot-chassis<br>
I also did some searching and found this list of Nexus 7009 Part Numbers, and my assumed descriptions <span style="color:#0000ff;">(in blue) </span>of what they are.<br>
N7K-C7009-ACC-KIT    <span style="color:#0000ff;">Nexus 7009 Accessory Kit</span><br>
N7K-C7009-BSK              <span style="color:#0000ff;">Nexus 7009 Bottom Support Kit</span><br>
N7K-C7009-CAB-TOP    <span style="color:#0000ff;">Nexus 7009 Top section Cable Management?</span><br>
N7K-C7009-CM-BLK      <span style="color:#0000ff;">Nexus 7009 Cable Management Blank?  Unknown</span><br>
N7K-C7009-F-BLANK  <span style="color:#0000ff;">Nexus 7009 Fabric Blank Interface ?</span><br>
N7K-C7009-FAB-2        <span style="color:#0000ff;">Nexus 7009 Fabric 2 Card</span><br>
N7K-C7009-FAN            <span style="color:#0000ff;">Nexus 7009 Fan Tray</span><br>
N7K-C7009-FD-MB       <span style="color:#0000ff;">Nexus 7009 Front Dook Kit</span><br>
N7K-C7009-L                   <span style="color:#0000ff;">Nexus 7009 License</span><br>
N7K-C7009-RMK           <span style="color:#0000ff;">Nexus 7009 Rack Mount Kit</span><br>
N7K-C7009-SHPPKG     <span style="color:#0000ff;">Nexus 7009 Shipping package</span><br>
N7K-C7009-XL               <span style="color:#0000ff;">Nexus 7009 XL</span><br>
L-N7K-C7009-XL           <span style="color:#0000ff;">Nexus 7009 Scalable Feature License (allows XL featuers without requiring a hardware module change)</span><br>
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<br>
N7K-AC-5.6KW         <span style="color:#0000ff;">5.6kW AC Power Supply</span></p>]]></description></item><item><title>Nexus 7009</title><link>https://hugo.fryguy.net/2011/03/30/nexus-7009/</link><pubDate>Thu, 31 Mar 2011 01:12:40 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/03/30/nexus-7009/</guid><description><![CDATA[<p>Well, today we can welcome the Cisco Nexus 7009 to the Nexus family.  It joins its big brothers the 7010 and 7018 as you can see below.</p>
<p style="text-align:center;">
  <a href="/wp-content/uploads/2011/03/5571204273_18e550b292_o.jpg"></a>
</p>
<p style="text-align:left;">
  So, what does this new chassis give us over its bigger brothers?  Well for one thing, SPACE!  The Nexus 7009 is only 14RU compared to the 7010 at 21RU and the 7018 at 25RU. What does that actually mean, well if you look at a standard 6509 / 6509E chassis &#8211; they are 15RU.  This new Nexus 7009 is actually 1RU smaller, nice!  One of the biggest complaints with the Nexus is that it is difficult to install if you are replacing an existing 6509 chassis with one, the 7010 is bigger and &#8211; as we all know &#8211; space in a data center is very precious!
</p>]]></description></item><item><title>Nexus 7000 and the Show Tech command (gzip too)</title><link>https://hugo.fryguy.net/2011/01/25/nexus-7000-and-the-show-tech-command-gzip-too/</link><pubDate>Tue, 25 Jan 2011 13:18:24 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/01/25/nexus-7000-and-the-show-tech-command-gzip-too/</guid><description><![CDATA[<p>Recently I have experience some interesting first-level support from our Cisco VAR.  They are not too familiar with the Nexus 7000 and insisted on us sending them a SHOW TECH from the switch.  If you are not familiar with a Nexus 7000, let me tell you – the show tech from this box can be over 100 Megs!  So, when they asked for that I was like – are you sure?  really really sure? I just have to say – thank you <a title="If you click this referral link, we each get increased space." href="http://db.tt/a1Siz1R" target="_blank" rel="noopener noreferrer">DropBox </a>and public folders!  I used DropBox place the file and then send the support the public link.  Not sure that most e-mail systems would appreciate that large of a file!<br>
So, if the Show Tech Support is so big, how do you get the information that support needs?  Well, instead of running a complete show tech, you run it for the sections you need!<br>
Here is a list of what you can append to a Show Tech-Support command: (show tech-support <em>option</em>)<br>
<span style="color:#ff0000;">N7K1-CoreSwitch1# <span style="color:#0000ff;">sh tech-support ?</span></span><br>
<span style="color:#ff0000;"><CR> </span><br>
<span style="color:#ff0000;">&gt;               Redirect it to a file</span><br>
<span style="color:#ff0000;">&raquo;              Redirect it to a file in append mode</span><br>
<span style="color:#ff0000;">aaa             Display aaa information</span><br>
<span style="color:#ff0000;">aclmgr          ACL commands</span><br>
<span style="color:#ff0000;">adjmgr          Display Adjmgr information</span><br>
<span style="color:#ff0000;">arp             Display ARP information</span><br>
<span style="color:#ff0000;">ascii-cfg       Show ascii-cfg information for technical support personnel</span><br>
<span style="color:#ff0000;">assoc_mgr       Gather detailed information for assoc_mgr troubleshooting</span><br>
<span style="color:#ff0000;">bgp             Display BGP status and configuration</span><br>
<span style="color:#ff0000;">bootvar         Gather detailed information for bootvar troubleshooting</span><br>
<span style="color:#ff0000;">brief           Display the switch summary</span><br>
<span style="color:#ff0000;">callhome        Callhome troubleshooting information</span><br>
<span style="color:#ff0000;">cdp             Gather information for CDP trouble shooting</span><br>
<span style="color:#ff0000;">cert-enroll     Display certificates information</span><br>
<span style="color:#ff0000;">cfs             Gather detailed information for cfs troubleshooting</span><br>
<span style="color:#ff0000;">cli             Gather information for parser troubleshooting</span><br>
<span style="color:#ff0000;">clis            Gather information for CLI Server troubleshooting</span><br>
<span style="color:#ff0000;">commands        Show commands executed as part of show tech-support commands</span><br>
<span style="color:#ff0000;">details         Gather detailed information for troubleshooting</span><br>
<span style="color:#ff0000;">dhcp            Gather detailed information for dhcp troubleshooting</span><br>
<span style="color:#ff0000;">eem             Show EEM tech-support information</span><br>
<span style="color:#ff0000;">eigrp           Display EIGRP status and configuration</span><br>
<span style="color:#ff0000;">eltm            Eltm debug info</span><br>
<span style="color:#ff0000;">ethpm           Gather detailed information for ETHPM troubleshooting</span><br>
<span style="color:#ff0000;">forwarding      Forwarding debug information</span><br>
<span style="color:#ff0000;">ha              Gather detailed information for HA troubleshooting</span><br>
<span style="color:#ff0000;">hsrp            Show hsrp tech-support information</span><br>
<span style="color:#ff0000;">icmpv6          Display Icmpv6 information</span><br>
<span style="color:#ff0000;">im              Gather detailed information for IM troubleshooting</span><br>
<span style="color:#ff0000;">include-time    Gather tech-support and capture time taken to execute each</span><br>
<span style="color:#ff0000;">command </span><br>
<span style="color:#ff0000;">interface-vlan  Gather detailed information for interface-vlan</span><br>
<span style="color:#ff0000;">troubleshooting </span><br>
<span style="color:#ff0000;">internal        Gather internal info for troubleshooting</span><br>
<span style="color:#ff0000;">ip              Display IP information</span><br>
<span style="color:#ff0000;">ipqos           IP QoS Manager</span><br>
<span style="color:#ff0000;">ipv4            Display IP information</span><br>
<span style="color:#ff0000;">ipv6            Display IPV6 information</span><br>
<span style="color:#ff0000;">l2fm            L2fm debug info</span><br>
<span style="color:#ff0000;">l2pt            Gather information for l2pt troubleshooting</span><br>
<span style="color:#ff0000;">l3vm            Display VRF information</span><br>
<span style="color:#ff0000;">lacp            Gather detailed information for LACP component</span><br>
<span style="color:#ff0000;">license         Display licensing information</span><br>
<span style="color:#ff0000;">logging         Show information on logging for technical support staff</span><br>
<span style="color:#ff0000;">m2fib           Gather detailed information for M2FIB troubleshooting</span><br>
<span style="color:#ff0000;">m2rib           Gather detailed information for M2RIB troubleshooting</span><br>
<span style="color:#ff0000;">mfwd            Display MCASTFWD status and configuration</span><br>
<span style="color:#ff0000;">module          Gather info related to a module</span><br>
<span style="color:#ff0000;">monitor         Gather detailed information for monitor troubleshooting</span><br>
<span style="color:#ff0000;">multicast       Display V4 Multicast information</span><br>
<span style="color:#ff0000;">netflow         Show NetFlow tech-support information</span><br>
<span style="color:#ff0000;">netstack        Gather information for NETSTACK troubleshooting</span><br>
<span style="color:#ff0000;">npacl           Display npacl information</span><br>
<span style="color:#ff0000;">pixm            Gather detailed information for PIXM troubleshooting</span><br>
<span style="color:#ff0000;">pixmc           PIXMC Information</span><br>
<span style="color:#ff0000;">pktmgr          Display Packet Manager information</span><br>
<span style="color:#ff0000;">port-channel    Gather detailed information for port channel troubleshooting</span><br>
<span style="color:#ff0000;">port-profile    Gather information for troubleshooting port-profiles</span><br>
<span style="color:#ff0000;">port-security   Port security related command</span><br>
Ok, color code again:<br>
<span style="color:#ff0000;">Red – Router Output</span><br>
<span style="color:#0000ff;">Blue – Commands</span><br>
<span style="color:#339966;">Green – Notes</span><br>
Traditionally when we have done show tech-support, we have always done terminal length to 0, set the capture buffer on our terminal application, and then executed the command – like this:<br>
First we set the length to 0<br>
<span style="color:#ff0000;">FryGuyR1#<span style="color:#0000ff;">terminal length 0</span></span><br>
Then we configure our terminal to capture the data</p>]]></description></item><item><title>Static ARP entries on NX-OS</title><link>https://hugo.fryguy.net/2010/10/28/static-arp-entries-on-nx-os/</link><pubDate>Thu, 28 Oct 2010 13:55:10 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2010/10/28/static-arp-entries-on-nx-os/</guid><description><![CDATA[<p>Oh the joys of Microsoft Network Load Balancing (NLB).  One of the wonderful ways that it is usually configured is using a Multicast MAC address utilizing a Unicast IP address.  Needless to say, most network devices do not like that and thus have problems when devices outside the local LAN attempt to connect to the NLB address.  In order to work around this problem you need to configure a static ARP entry on the gateway so that the devices know how to get to the server.<br>
On IOS, this is not so hard as you configure the a static ARP entry (<strong>arp 10.1.1.99 0300.5e11.1111</strong>).  That command there on the gateway will usually get things working. You may also need to define where that MAC address lives – and the command to do that would be <strong>mac-address-table static 0300.5e11.1111 vlan 200 interface fa2/3 fa2/4</strong> This information was obtained from a Cisco document can be found here if you need more information – <a href="http://www.cisco.com/en/US/products/hw/switches/ps708/products" target="_blank" rel="noopener noreffer ">http://www.cisco.com/en/US/products/hw/switches/ps708/products</a>_configuration_example09186a0080a07203.shtml<br>
Now, on the NX-OS it is a little different as you need to configure the static ARP entry under the VLAN interface in order for it to work:<br>
interface Vlan100<br>
no shutdown<br>
description [—-[ Standard VM VLAN ]—-]<br>
no ip redirects<br>
ip address 10.1.1.2/24<br>
ip arp 10.1.1.99 0300.5e11.1111<br>
N7K1# sh ip arp | inc 1111<br>
10.1.1.99       –      0300.5e11.1111   Vlan100</p>]]></description></item></channel></rss>