web-archive-net.com » NET » M » MAJORNETWORK.NET

Total: 263

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Nexus 5000 Tips for Catalyst Admins – Majornetwork
    you are doing Check the docs docs sh fex xxx detail obviously shows you even more information and sh fex xxx transceiver shows you which kind of optics copper you have on the FEX because the normal sh int status sh int transceiver switch commands don t show the fabric ports at the FEX end If and when you are using vPC you need to use the sh vpc command variants to verify that your vPC configurations are working as you expected For example sh vpc brief shows if you have any consistency problems with your vPCs In case of problems you need to use sh vpc consistency parameters vpc xxx to show more information What else would you recommend to Nexus newbies Cisco Nexus 5000 Series documentation is found here http www cisco com en US products ps9670 tsd products support series home html Updated January 15 2012 20 36 Tags fabric extender fex nexus 5000 nexus 5500 vpc Previous Post Next Post 11 Comments Add a Comment Minimal January 15 2012 at 21 51 Markku this is a great site Glad to see all the Nexus content If you are running FEX s in a dual homed active active setup use sh run include switch profile to show the separation between the standard config and what was entered in your config sync switch profile I even modified rancid to backup my configs this way Reply Mat January 22 2013 at 18 23 HI Markku A bit off topic did you use the cisco xr profile to get the config from your N5k I am struggling to get Rancid configured with Nexus Reply Markku Leiniö January 16 2012 at 19 00 Minimal that s a good point The configuration entered in switch profile is shown in normal sh run output but sh run include switch profile or even sh run switch profile helps to identify the configuration applied with the switch profile Thanks Reply Ian Erikson January 16 2012 at 19 04 sh run int all Shows all config including Nexus defaults sh int status fex 10x nice way to narrow down sh int status to a single fex when using ping or while ftp tftp using vrf s management ping 1 2 3 4 vrf management sh install all impact kickstart system good way to see what impact new IOS brings I agree sh vpc consistency parameters vpc xxx this is a great command to know when you are wondering why your vlan vpc arent working Reply Ron Fuller Cisco January 17 2012 at 02 21 These URLs might be handy to have as well http docwiki cisco com wiki Category Nexus 5000 Design Best Practices http docwiki cisco com wiki Cisco Nexus 7000 NX OS IOS Comparison Tech Notes Reply Markku Leiniö January 19 2012 at 20 02 Thanks Ron Reply Markku Leiniö February 4 2012 at 17 12 Good hints from Ian as well above One of the biggest hints is this You can use the

    Original URL path: https://majornetwork.net/2012/01/nexus-5000-tips-for-catalyst-admins/?replytocom=327 (2016-04-25)
    Open archived version from archive


  • Nexus 5000 Tips for Catalyst Admins – Majornetwork
    you are doing Check the docs docs sh fex xxx detail obviously shows you even more information and sh fex xxx transceiver shows you which kind of optics copper you have on the FEX because the normal sh int status sh int transceiver switch commands don t show the fabric ports at the FEX end If and when you are using vPC you need to use the sh vpc command variants to verify that your vPC configurations are working as you expected For example sh vpc brief shows if you have any consistency problems with your vPCs In case of problems you need to use sh vpc consistency parameters vpc xxx to show more information What else would you recommend to Nexus newbies Cisco Nexus 5000 Series documentation is found here http www cisco com en US products ps9670 tsd products support series home html Updated January 15 2012 20 36 Tags fabric extender fex nexus 5000 nexus 5500 vpc Previous Post Next Post 11 Comments Add a Comment Minimal January 15 2012 at 21 51 Markku this is a great site Glad to see all the Nexus content If you are running FEX s in a dual homed active active setup use sh run include switch profile to show the separation between the standard config and what was entered in your config sync switch profile I even modified rancid to backup my configs this way Reply Mat January 22 2013 at 18 23 HI Markku A bit off topic did you use the cisco xr profile to get the config from your N5k I am struggling to get Rancid configured with Nexus Reply Markku Leiniö January 16 2012 at 19 00 Minimal that s a good point The configuration entered in switch profile is shown in normal sh run output but sh run include switch profile or even sh run switch profile helps to identify the configuration applied with the switch profile Thanks Reply Ian Erikson January 16 2012 at 19 04 sh run int all Shows all config including Nexus defaults sh int status fex 10x nice way to narrow down sh int status to a single fex when using ping or while ftp tftp using vrf s management ping 1 2 3 4 vrf management sh install all impact kickstart system good way to see what impact new IOS brings I agree sh vpc consistency parameters vpc xxx this is a great command to know when you are wondering why your vlan vpc arent working Reply Ron Fuller Cisco January 17 2012 at 02 21 These URLs might be handy to have as well http docwiki cisco com wiki Category Nexus 5000 Design Best Practices http docwiki cisco com wiki Cisco Nexus 7000 NX OS IOS Comparison Tech Notes Reply Markku Leiniö January 19 2012 at 20 02 Thanks Ron Reply Markku Leiniö February 4 2012 at 17 12 Good hints from Ian as well above One of the biggest hints is this You can use the

    Original URL path: https://majornetwork.net/2012/01/nexus-5000-tips-for-catalyst-admins/?replytocom=332 (2016-04-25)
    Open archived version from archive

  • FEX Pre-provisioning – Majornetwork
    N55 M16P Cisco 16x10G Ethernet Expansion Module N55 M16UP Cisco 16x10G Flexible Ethernet Expansion Module N55 M8P8FP Cisco 8 Port 1 2 4 8G FC 8 Port 10G Ethernet Expansion Module N5K M1008 Cisco 8 Port Fiber Channel Expansion Module 8 x SFP N5K M1060 Cisco 6 Port Fiber Channel Expansion Module 6 x SFP N5K M1404 Expansion Module 4 x 10GBase T LAN 4 x Fiber Channel N5K M1600 Cisco 6 port 10 Gigabit Ethernet SFP Module 6 x SFP nexus5596 config slot provision model n2k n2224TP nexus5596 config slot exit nexus5596 config sh run int e101 1 1 Command show running config interface Ethernet101 1 1 Time Wed Nov 9 17 02 57 2011 version 5 0 3 N2 2a interface Ethernet101 1 1 nexus5596 config As you can see after pre provisioning the FEX with the slot and provision model commands the interface appears in the configuration empty interface configuration and you can start configuring the port As a side note the model list above also includes a FEX that has not yet been officially announced N2K C2248GV P Fabric Extender 48x1G 4x10G POE Module Updated January 8 2012 13 03 Tags fabric extender fex nexus 5000 nexus 5500 nx os Previous Post Next Post 4 Comments Add a Comment ian erikson November 9 2011 at 19 39 this will be very useful to us thanks for posting Reply Miguel January 8 2012 at 12 40 the Enabling NPV mode URL you ve posted above is now dead new URL is now http www cisco com en US docs switches datacenter nexus5000 sw san switching Cisco Nexus 5000 Series NX OS SAN Switching Configuration Guide chapter5 html task 1550221 BTW Thanks for posting Keep it up Reply Markku Leiniö January 8 2012 at 13 04 Thanks Miguel

    Original URL path: https://majornetwork.net/2011/11/fex-pre-provisioning/?replytocom=75 (2016-04-25)
    Open archived version from archive

  • FEX Pre-provisioning – Majornetwork
    SFP N55 M16P Cisco 16x10G Ethernet Expansion Module N55 M16UP Cisco 16x10G Flexible Ethernet Expansion Module N55 M8P8FP Cisco 8 Port 1 2 4 8G FC 8 Port 10G Ethernet Expansion Module N5K M1008 Cisco 8 Port Fiber Channel Expansion Module 8 x SFP N5K M1060 Cisco 6 Port Fiber Channel Expansion Module 6 x SFP N5K M1404 Expansion Module 4 x 10GBase T LAN 4 x Fiber Channel N5K M1600 Cisco 6 port 10 Gigabit Ethernet SFP Module 6 x SFP nexus5596 config slot provision model n2k n2224TP nexus5596 config slot exit nexus5596 config sh run int e101 1 1 Command show running config interface Ethernet101 1 1 Time Wed Nov 9 17 02 57 2011 version 5 0 3 N2 2a interface Ethernet101 1 1 nexus5596 config As you can see after pre provisioning the FEX with the slot and provision model commands the interface appears in the configuration empty interface configuration and you can start configuring the port As a side note the model list above also includes a FEX that has not yet been officially announced N2K C2248GV P Fabric Extender 48x1G 4x10G POE Module Updated January 8 2012 13 03 Tags fabric extender fex nexus 5000 nexus 5500 nx os Previous Post Next Post 4 Comments Add a Comment ian erikson November 9 2011 at 19 39 this will be very useful to us thanks for posting Reply Miguel January 8 2012 at 12 40 the Enabling NPV mode URL you ve posted above is now dead new URL is now http www cisco com en US docs switches datacenter nexus5000 sw san switching Cisco Nexus 5000 Series NX OS SAN Switching Configuration Guide chapter5 html task 1550221 BTW Thanks for posting Keep it up Reply Markku Leiniö January 8 2012 at 13 04 Thanks

    Original URL path: https://majornetwork.net/2011/11/fex-pre-provisioning/?replytocom=284 (2016-04-25)
    Open archived version from archive

  • Dual-layer vPC on Nexus 5000 – Majornetwork
    configuration simplicity Say you are configuring 2 ports for a new server With VPC d 2k s for example you are configuring ports e100 1 1 and e101 1 1 on BOTH 5k s You have to note somewhere that fex 100 and fex 101 are a pair when it comes time to upgrade fex code and it needs a reboot With straight through fex s You know the fex s are a pair because they will share the same fex number on each 5k And when it comes to configuration you can just configure e100 1 1 on each 5k you do want to use vpc orphan port suspend command though thanks Ian Reply Markku Leiniö November 3 2011 at 22 05 Thanks for your comments Ian You have very valid points there For your first point I need to say that times have somewhat changed on the redundancy On Catalyst times we could run the same IOS for ages and not cause any disturbance due to the upgrades for the single connected server NICs Nowadays I have a feeling that the switches need to be upgraded all the time or at least more often than in the old days That s why I want to reserve the right to ISSU the Nexus 5500 at any time About the port configuration it really is a serious operational issue or it may become an issue at some point later so FEX numbering scheme is something that needs careful consideration Can you open up your meaning about suspending the orphan ports here Reply Ian Erikson November 3 2011 at 22 18 I agree about code upgrades I think best practice is moving towards staying at the latest code level This is probably because the complexity is increasing rapidly I find the fex numbering issue becomes a problem as you transition your catalyst friendly tech staff to nexus support As far as orphan ports go If you lose the vPC peer link it shuts down all vPC on the vPC secondary switch This includes the uplink Now with uplink down crosslink down but downstream port channels and links UP you are black holing your hosts Your straight through FEX s stay up So a server doesn t see a link down and continues to send traffic over that link I have found most NIC teaming software HP for instance eventually does a Rx Tx health check and noticed it can t get to the gateway and shuts down use of that NIC You can t really vouch for every server s NIC teaming method so I find its best to apply the vpc orphan port suspend command to make sure they get links down you can do a show vpc orphan ports to see ports at risk Reply Markku Leiniö November 3 2011 at 22 28 Right I read the context again and realized what you meant Yes I agree on the orphan port setting I think that sometimes the NIC teaming

    Original URL path: https://majornetwork.net/2011/11/dual-layer-vpc-on-nexus-5000/?replytocom=64 (2016-04-25)
    Open archived version from archive

  • nexus 2000 – Majornetwork
    ps10110 data sheet c78 568589 ps9670 Products Data Sheet html As a bonus sector data sheet for the 10G SFP modules is found in http www cisco com en US prod collateral modules ps5455 data sheet c78 455693 html Read Post Search for Markku Leiniö Senior Network Architect Senior Technology Consultant and CCIE 26438 Routing Switching in Finland Majornetwork on Twitter Markku Leiniö on Google Your IPv4 IPv6 Status You are using IPv4 address 81 198 240 36 Recent Posts majornetwork net Is Now TLS Enabled IPsec VPN Tunnel between F5 BIG IP and Juniper SRX SoftEther VPN with a VPN Address Pool Juniper SRX IPsec LAN to LAN VPN Part 2 Juniper SRX IPsec LAN to LAN VPN Part 1 Tags 15 0SY 15 1SY ba bridge assurance cat6500 catalyst 6500 cisco cli cmp console cygwin dual homed esxi fabric extender fabricpath fast hello fex hypervisor ios ipsec ipv6 issu juniper junos lacp linux nexus 5000 nexus 5500 nexus 7000 nx os private vlan pvlan qsfp srx srx100 sup2t sup32 sup720 switch profile sxi sxj vmware vpc vpn vsphere Archives October 2015 July 2015 May 2015 February 2015 January 2015 December 2014 November 2014 August 2014 June 2014 May

    Original URL path: https://majornetwork.net/tag/nexus-2000/ (2016-04-25)
    Open archived version from archive

  • twinax – Majornetwork
    data sheet c78 568589 ps9670 Products Data Sheet html As a bonus sector data sheet for the 10G SFP modules is found in http www cisco com en US prod collateral modules ps5455 data sheet c78 455693 html Read Post Search for Markku Leiniö Senior Network Architect Senior Technology Consultant and CCIE 26438 Routing Switching in Finland Majornetwork on Twitter Markku Leiniö on Google Your IPv4 IPv6 Status You are using IPv4 address 81 198 240 36 Recent Posts majornetwork net Is Now TLS Enabled IPsec VPN Tunnel between F5 BIG IP and Juniper SRX SoftEther VPN with a VPN Address Pool Juniper SRX IPsec LAN to LAN VPN Part 2 Juniper SRX IPsec LAN to LAN VPN Part 1 Tags 15 0SY 15 1SY ba bridge assurance cat6500 catalyst 6500 cisco cli cmp console cygwin dual homed esxi fabric extender fabricpath fast hello fex hypervisor ios ipsec ipv6 issu juniper junos lacp linux nexus 5000 nexus 5500 nexus 7000 nx os private vlan pvlan qsfp srx srx100 sup2t sup32 sup720 switch profile sxi sxj vmware vpc vpn vsphere Archives October 2015 July 2015 May 2015 February 2015 January 2015 December 2014 November 2014 August 2014 June 2014 May 2014

    Original URL path: https://majornetwork.net/tag/twinax/ (2016-04-25)
    Open archived version from archive

  • modular – Majornetwork
    switchover between the supervisors You need to reload the whole switch Source CSCsb07831 Cisco login required Apparently the standby supervisor will keep reloading if you try the switchover method Read Post Search for Markku Leiniö Senior Network Architect Senior Technology Consultant and CCIE 26438 Routing Switching in Finland Majornetwork on Twitter Markku Leiniö on Google Your IPv4 IPv6 Status You are using IPv4 address 81 198 240 36 Recent Posts majornetwork net Is Now TLS Enabled IPsec VPN Tunnel between F5 BIG IP and Juniper SRX SoftEther VPN with a VPN Address Pool Juniper SRX IPsec LAN to LAN VPN Part 2 Juniper SRX IPsec LAN to LAN VPN Part 1 Tags 15 0SY 15 1SY ba bridge assurance cat6500 catalyst 6500 cisco cli cmp console cygwin dual homed esxi fabric extender fabricpath fast hello fex hypervisor ios ipsec ipv6 issu juniper junos lacp linux nexus 5000 nexus 5500 nexus 7000 nx os private vlan pvlan qsfp srx srx100 sup2t sup32 sup720 switch profile sxi sxj vmware vpc vpn vsphere Archives October 2015 July 2015 May 2015 February 2015 January 2015 December 2014 November 2014 August 2014 June 2014 May 2014 September 2013 August 2013 July 2013 June 2013 April

    Original URL path: https://majornetwork.net/tag/modular/ (2016-04-25)
    Open archived version from archive



  •