<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Nexus - Category - Fryguy's Blog</title><link>https://hugo.fryguy.net/categories/nexus/</link><description>Nexus - Category - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 03 Oct 2013 12:01:15 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/categories/nexus/" rel="self" type="application/rss+xml"/><item><title>Nexus 9000 (MIB Hunting!)</title><link>https://hugo.fryguy.net/2013/10/03/nexus-9000-mib-hunting/</link><pubDate>Thu, 03 Oct 2013 12:01:15 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2013/10/03/nexus-9000-mib-hunting/</guid><description><![CDATA[<p align="center">
  
</p>
<p align="left">
  Back at Cisco Live 2013, there was some chatter around the Insieme deal and the potential to see a new switch from Cisco during the event.  I think even Greg over at EtherealMind was hoping for some more juicy Insieme announcements at Cisco Live as well ( see post –  <a href="http://etherealmind.com/musing-predicting-what-insieme-might-announce-at-cisco-live/" target="_blank" rel="noopener noreferrer">http://etherealmind.com/musing-predicting-what-insieme-might-announce-at-cisco-live/</a> )Well, what we actuall got at Cisco Live was the Nexus 7700 switch and the Gold Cisco 6608 Catalyst Switches, not the hoped for Insieme switch.
</p>
<p align="left">
  Then today I saw that there an article posted over on NetworkWorld ( <a href="http://www.networkworld.com/news/2013/100213-interop-cisco-insieme-274455.html" target="_blank" rel="noopener noreferrer">http://www.networkworld.com/news/2013/100213-interop-cisco-insieme-274455.html</a> ) in regards to the Insieme Nexus 9K and Hardware Defined Networking that caught my attention. There is another article there –  <a href="http://www.networkworld.com/community/blog/cisco-nexus-9000-aimed-40g" target="_blank" rel="noopener noreferrer">http://www.networkworld.com/community/blog/cisco-nexus-9000-aimed-40g</a> –  that has some output from a 9508 switch as well.
</p>
<p align="left">]]></description></item><item><title>Author Series – Ron Fuller</title><link>https://hugo.fryguy.net/2013/03/26/author-series-ron-fuller/</link><pubDate>Wed, 27 Mar 2013 02:55:00 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2013/03/26/author-series-ron-fuller/</guid><description><![CDATA[<p class="MsoNoSpacing" style="margin: 0in 0in 0pt; text-align: center;">
  <span style="font-family: 'times new roman', times;"></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="color: #000000; font-size: medium; font-family: 'times new roman', times;">Time to continue the Author Series of posts, this time with Ron Fuller, CCIE 5851.   It is the intention of these interviews to bring a human side to the technical author.  I feel that each author has a story to share , and I wanted to provide them a way to share that story.</span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-family: 'times new roman', times;"> </span>
</p>
<h2 style="margin: 10pt 0in 0pt;">
  <span style="font-size: large; font-family: 'times new roman', times;"><span style="color: #4f81bd;"><br /> <!--?xml:namespace prefix ="" o ns ="" "urn:schemas-microsoft-com:office:office" ?--></span></span>
</h2>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-size: medium; font-family: 'times new roman', times;"><strong><em>Author Name:</em></strong> <span style="color: #0000ff;"><strong>Ron Fuller</strong></span></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-size: medium; font-family: 'times new roman', times;"><strong><em>Book Title:</em> <span style="color: #0000ff;">NX-OS and Cisco Nexus Switching – Next-Generation Data Center Architectures 2<sup>nd</sup> Edition</span></strong></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-size: medium; font-family: 'times new roman', times;"><strong><em>Book Publisher:</em> </strong><span style="color: #0000ff;"><strong>CiscoPress</strong></span></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <span style="font-size: medium; font-family: 'times new roman', times;"><strong><em>Author Social Media Handle/Web Site/Public Contact:</em></strong><span style="color: #0000ff;"><strong><a href="http://www.twitter.com/ccie5851" target="_blank" rel="noopener noreferrer"> @ccie5851</a> <a href="http://ccie5851.blogspot.com" target="_blank" rel="noopener noreferrer">ccie5851.blogspot.com</a></strong></span></span>
</p>
<p class="MsoNoSpacing" style="margin: 0in 0in 0pt;">
  <strong><em><span style="font-size: medium; font-family: 'times new roman', times;">Other books authored:</span></em></strong>
</p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;">
  <span style="color: #0000ff;"><em><strong><span style="font-size: medium; font-family: 'times new roman', times;">NX-OS and Cisco Nexus Switching – Next-Generation Data Center Architectures 1<sup>st</sup> Edition</span></strong></em></span>
</p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;">
  <span style="color: #0000ff;"><em><strong><span style="font-size: medium; font-family: 'times new roman', times;">Building Cisco Wireless LANs</span></strong></em></span>
</p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;">
  <span style="color: #0000ff;"><em><strong><span style="font-size: medium; font-family: 'times new roman', times;">Cisco QoS</span></strong></em></span>
</p>
<p class="MsoNormal" style="margin: 0in 0in 10pt;">
  <span style="font-family: 'times new roman', times;"> </span>
</p>
<p class="MsoListParagraphCxSpFirst" style="text-indent: -0.25in; margin: 0in 0in 0pt 0.5in; mso-list: l0 level1 lfo1;">
  <span style="font-family: 'times new roman', times;"><strong><em><span style="font-size: medium;">1.</span><span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal;">       </span><span style="font-size: medium;">Tell us a little background on yourself; is there anything unique about you that you would like to share that people might not be aware of?</span></em></strong></span>
</p>
<p class="MsoListParagraphCxSpMiddle" style="margin: 0in 0in 0pt 0.5in;">
  <span style="font-family: 'times new roman', times;">]]></description></item><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, its official.</title><link>https://hugo.fryguy.net/2012/03/20/ccie-data-center-its-official/</link><pubDate>Tue, 20 Mar 2012 15:14:24 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2012/03/20/ccie-data-center-its-official/</guid><description><![CDATA[<p align="center">
  
</p>
<p>Recently Cisco officially announces the CCIE Data Center on their The Cisco Learning Network website – <a href="https://learningnetwork.cisco.com/community/certifications/ccie_data_center" target="_blank" rel="noopener noreferrer">LINK</a>. This certification track has been long rumored – probably for about 1-2 years now some of us have been waiting for the announcement.<br>
A complete list of the written exam topics in PDF format can be found here – <a href="http://dl.dropbox.com/u/5753029/CCIEDCBLOG/CCIE%20Data%20Center%20Written%20Exam%20Topics%20March2012.pdf" target="_blank" rel="noopener noreferrer">LINK</a>. The Beta exam of the written will be available at Cisco Live San Diego this year if you are interested in taking it during the event, if not – you can take the beta beginning May 1 through June 14 at a cost of $50. If you pass the beta, you will recertify your existing CCIE (like any CCIE level written will) and you will be qualified to take the lab (same deal). <em>My advice on this would be to not take it at Live, you get a free test – use the coupon wisely. If you want to take this test at Cisco Live, invest the $50</em>. If you would rather wait for the go-live of the exam, that will be September 3, 2012.</p>]]></description></item><item><title>Future Nexus 7000 Line Cards (Sup2/ASA/NAM/WAN)</title><link>https://hugo.fryguy.net/2011/08/02/future-nexus-7000-line-cards-sup2asanamwan/</link><pubDate>Tue, 02 Aug 2011 12:09:42 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/08/02/future-nexus-7000-line-cards-sup2asanamwan/</guid><description><![CDATA[<p style="text-align: center;">
  <a href="/wp-content/uploads/2011/07/crystal-ball.jpg"></a>
</p>
<p style="text-align: left;">
  Let me preface this post with a quick word &#8211; all the information presented here is pure speculation with a little bit of evidence to back up my speculation.  By no means is any of this a guarantee nor a near-time release for any of these modules.  This is me just presenting the information that I am able to find and sharing it with you.  Now, I am excited for some of this &#8211; and it definitely shows where the Nexus 7000 is going &#8211; so I hope that this type of information can help keep you informed on where this platform is going.  The future looks bright.
</p>
<p style="text-align: left;">
  While I was doing the research on the track names for the Nexus line cards I came across a few things.  Things that we have all either assumed or have heard rumors of, but I guess now we know what is coming in the future for the Nexus 7000. First this is a listing for Silverstone &#8211; Supervisor 2 module, a little curious for sure.
</p>
<p style="text-align: left;">
  The second thing that I came across was a bit more interesting to me &#8211; its a Service Module &#8211; N7K-SVC-APP-HW-1 &#8211; named after the Indian God, Agni.  What is curious is that Agni is a messenger from and to the other gods (modules), so it is aptly named.  I am guessing that this will be a 2-port module (Agni has 2-heads) similar to what the WS-X6582-2PA adapter is to the 6500. @matthewnorwood just also suggested perhaps this is an Application Load Balancer similar to the ACE30 on the Cat6k, I actually think that might be a more realistic option.(continued)
</p>
<p style="text-align: left;">]]></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>CCIE Data Center – Rumored</title><link>https://hugo.fryguy.net/2011/07/05/ccie-data-center-rumored/</link><pubDate>Tue, 05 Jul 2011 12:12:17 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2011/07/05/ccie-data-center-rumored/</guid><description><![CDATA[  
With Networkers, err Cisco Live, coming up quickly in less then a week the rumor mill is a buzzing with some good rumors.  There is a rumor that a new little brother in the Nexus line is coming, but the one that has my attention is perhaps a new CCIE level certification &#8211; might even be retiring one that has overlapping technologies (storage).  Over on 2bccie.com, there is a post in regards to the CCIE Data Center track being discussed on day during the CCIE Lunch at Cisco Live Melbourne  &#8211; <a href="http://www.2bccie.com/2011/04/02/ccie-data-centre-track.html/comment-page-1" target="_blank" rel="noopener noreferrer">link</a>.  
While that is all still rumors, here is what I can gather by researching available resources and taking some educated guesses on what would be on the lab.  I will also admit that this was briefly discussed at Cisco Live 2010 and that was in a session that would have the knowledge about the topic, so much of this comes from what I can read from my chicken scratch notes.  Obviously, Cisco has been working on this for some time and the maturity of the line is finally at the stage and market saturation where this certification makes sense.]]></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 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>