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".
  • Private VLANs on Nexus 5000 Series – Majornetwork
    why would we then want to prune the isolated VLAN from the trunk It goes there automatically If you want to prune it then just don t configure the PVLAN association at all If I would need more PVLANs trunked to the same server because it is a member of several PVLANs I can do that as well n5k 1 config if vlan 111 n5k 1 config vlan private vlan isolated n5k 1 config vlan vlan 110 n5k 1 config vlan private vlan primary n5k 1 config vlan private vlan association 111 n5k 1 config vlan int e100 1 9 n5k 1 config if switchport private vlan association trunk 110 111 n5k 1 config if sh run int e100 1 9 interface Ethernet100 1 9 switchport mode private vlan trunk secondary switchport private vlan trunk allowed vlan 30 switchport private vlan association trunk 100 101 switchport private vlan association trunk 110 111 n5k 1 config if sh int e100 1 9 switchport Name Ethernet100 1 9 Switchport Enabled Switchport Monitor Not enabled Operational Mode Private vlan trunk secondary Access Mode VLAN 1 default Trunking Native Mode VLAN 1 default Trunking VLANs Allowed 1 3967 4048 4093 Voice VLAN none Extended Trust State not trusted COS 0 Administrative private vlan primary host association none Administrative private vlan secondary host association none Administrative private vlan primary mapping none Administrative private vlan secondary mapping none Administrative private vlan trunk native VLAN 1 Administrative private vlan trunk encapsulation dot1q Administrative private vlan trunk normal VLANs 30 Administrative private vlan trunk private VLANs 100 101 110 111 Operational private vlan 100 101 110 111 Unknown unicast blocked disabled Unknown multicast blocked disabled Let s return to our PVLAN promiscuous trunk again port e1 2 n5k 1 config if sh run int e1 2 interface Ethernet1 2 switchport mode private vlan trunk promiscuous switchport private vlan mapping trunk 100 101 I just added the VLANs 110 and 111 above so I ll configure the router to route those as well and configure the switch port accordingly n5k 1 config if int e1 2 n5k 1 config if switchport private vlan mapping trunk 1 3967 4048 4093 Primary private VLAN n5k 1 config if switchport private vlan mapping trunk 110 1 3967 4048 4093 Secondary VLAN IDs add Add a VLAN to private VLAN list remove Remove a VLAN from private VLAN list n5k 1 config if switchport private vlan mapping trunk 110 111 n5k 1 config if sh run int e1 2 interface Ethernet1 2 switchport mode private vlan trunk promiscuous switchport private vlan mapping trunk 100 101 switchport private vlan mapping trunk 110 111 Note that there is add remove syntax as well In this version of NX OS 5 1 3 N2 1a there is however no difference in using the add keyword or not Let me show that n5k 1 config if vlan 102 n5k 1 config vlan private vlan community n5k 1 config vlan vlan 100 n5k 1 config vlan private vlan

    Original URL path: https://majornetwork.net/2012/06/private-vlans-on-nexus-5000-series/ (2016-04-25)
    Open archived version from archive


  • NX-OS and IOS Default Configuration Differences – Majornetwork
    read documents for those who are migrating routing from good old Catalyst 6500 to Nexus 7000 In the document there is also a link to the IOS NX OS Migration Tool on cisco com Updated November 18 2011 21 14 Tags cat6500 catalyst 6500 cli ios nexus 7000 nx os Previous Post Next Post Leave a Reply Cancel reply 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

    Original URL path: https://majornetwork.net/2011/11/nx-os-and-ios-default-configuration-differences/ (2016-04-25)
    Open archived version from archive

  • Using Cygwin to Boost Your Toolkit – Majornetwork
    lynx wget wput After finishing the installation I start the Cygwin CLI and do some tweaking with vi of course you can use some other editor if you like just select it from the Editors package selection In the current directory my home directory home markku I edit the bashrc file with some extra settings export HISTCONTROL ignoredups to remove identical lines from the command line history export LESS M to get less to show me more in the prompts export PS1 u h w to change the shell prompt to one liner from the default alias snmpwalk snmpwalk v 2c c mydefaultcommunity to get decent default parameters for my snmpwalk commands function sciscoserial this function shows the name and serial number of the host given in the command line for Cisco devices snmpwalk O qv sysname snmpwalk O qv 1 3 6 1 4 1 9 3 6 3 function shpserial this function shows the name and serial number of the host given in the command line for HP switches snmpwalk O qv sysname snmpwalk O qv 1 3 6 1 4 1 11 2 36 1 1 2 9 snmpwalk is part of Net SNMP package Now with Cygwin I can run all my favorite command line goodies like grep awk sed any kind of shell scripts and so on All shown in above is just a small start Check also the post from Mike Kantowski on Packet Pushers Updated December 6 2012 15 48 Tags cli cygwin unix Previous Post Next Post 1 Comment Add a Comment Pingback Internets of Interest 2 Sep 2011 My Etherealmind Leave a Reply Cancel reply 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

    Original URL path: https://majornetwork.net/2011/09/using-cygwin-to-boost-your-toolkit/ (2016-04-25)
    Open archived version from archive

  • Cat6500 Sup2T CMP Note – Majornetwork
    attach to the supervisor route processor You might think that you are accessing the supervisor console with the attach command That is not true however The attach command takes you to aux 0 port of the supervisor What is the difference The important difference is that via the aux port you cannot enter the enable mode if your supervisor does not have enable password secret configured With the real console port con 0 you can always enter the enable mode even without any passwords configured But with the aux port it is not possible So if you erase the configuration file in your Sup2T you will still need to use the console cable or your serial console server to access the switch and to configure the enable password before continuing via the CMP Maybe there is a workaround by uploading a stub startup config file via the CMP somehow I ll need to investigate that later That startup config could then include the enable secret command or more of the configuration Added Sup2T management and monitoring white paper http www cisco com en US prod collateral switches ps5718 ps708 white paper c11 663635 html Updated October 20 2011 19 52 Tags cat6500 cmp console sup2t Previous Post Next Post Leave a Reply Cancel reply 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

    Original URL path: https://majornetwork.net/2011/10/cat6500-sup2t-cmp-note/ (2016-04-25)
    Open archived version from archive

  • Importing Configuration in the Switch Profile – Majornetwork
    s Following commands failed mutual exclusion checks interface Ethernet100 1 45 switchport access vlan 30 It said that there was problem with the peer Well I configured it as well n5k 2 conf sync Enter configuration commands one per line End with CNTL Z n5k 2 config sync switch profile SWITCH PROFILE Switch Profile started Profile ID is 1 n5k 2 config sync sp import int e100 1 45 n5k 2 config sync sp import commit Failed Verify Failed n5k 2 config sync sp import sh switch profile status switch profile SWITCH PROFILE Start time 501759 usecs after Wed Jun 20 15 54 23 2012 End time 869233 usecs after Wed Jun 20 15 54 24 2012 Profile Revision 2 Session type Import Commit Session subtype Peer triggered No Profile status Local information Status Verify Success Error s Peer information IP address 192 168 77 11 Sync status In sync Status Verify Failure Error s Following commands failed mutual exclusion checks interface Ethernet100 1 45 switchport access vlan 30 Now it said that the first switch was having mutex failures This went on for a while when I was trying everything And then it struck to me In the configuration guide Nexus 5000 Series System Management Configuration Guide it says in this order Ensure configurations are the same on both switches Configure the switch profile with same name on both switches Enter the import running config command on both switches Enter the switch profile name buffer command to ensure all configurations are correctly imported on both switches Remove unwanted configuration settings by editing the buffer Enter the commit command on both switches Enter the sync peers destination IP address command to configure the peer switch on both switches Enter the switch profile name status command to ensure both switches are synchronized You see what I missed I configured the sync peers before the import and commit That s just because I had the switch profile in use already Let s remove sync peers and try again n5k 1 config sync sp import exit n5k 1 config sync switch profile SWITCH PROFILE Switch Profile started Profile ID is 1 n5k 1 config sync sp import no sync peers destination 192 168 77 12 n5k 1 config sync sp import commit Verification successful Proceeding to apply configuration This might take a while depending on amount of configuration in buffer Please avoid other configuration changes during this time Commit Successful It worked Now I just had to repeat that for the other switch and then restore the sync peers commands Here is the successful switch profile after the operations n5k 1 config sync sh run switch profile switch profile SWITCH PROFILE sync peers destination 192 168 77 12 interface Ethernet100 1 44 description This is for testing interface Ethernet100 1 45 switchport access vlan 30 By the way When configuring dual homed FEX ports it is essential that the FEX port configuration on both Nexus switches is identical otherwise the port may be

    Original URL path: https://majornetwork.net/2012/06/importing-configuration-in-the-switch-profile/ (2016-04-25)
    Open archived version from archive

  • Dual-homed FEXes and Switch Profiles – Majornetwork
    might take a while depending on amount of configuration in buffer Please avoid other configuration changes during this time Commit Successful N5k 1 config sync Now the commands have been applied to both of the switches The switch profile buffer is automatically emptied after committing the configuration N5k 1 config sync sh switch profile buffer switch profile PROFILE Seq no Command N5k 1 config sync Use the exit command to leave the config sync mode Show switch profile status can be useful if the situation is somehow unclear with the switch profiles N5k 1 config sync sh switch profile status switch profile PROFILE Start time 496010 usecs after Sat Jan 7 13 38 44 2012 End time 647451 usecs after Sat Jan 7 13 38 46 2012 Profile Revision 2 Session type Commit Session subtype Peer triggered No Profile status Sync Success Local information Status Commit Success Error s Peer information IP address 10 5 2 2 Sync status In sync Status Commit Success Error s N5k 1 config sync In the previous output you can see the local and peer status information that can be useful when troubleshooting switch profile problems Show run switch profile can be used to show which commands have actually been entered with the switch profile instead of the direct conf t configuration You can read more about switch profiles in the Cisco Nexus 5000 Series NX OS System Management Configuration Guide http www cisco com en US docs switches datacenter nexus5000 sw system management 513 n1 1 b Cisco n5k system mgmt cg rel 513 n1 1 chapter 011 html All the current Cisco Nexus 5000 Series Configuration Guides can be found in http www cisco com en US products ps9670 products installation and configuration guides list html Update There is also a Q and A list about configuration synchronization in the Cisco Nexus 5548P documentation http www cisco com en US prod collateral switches ps9441 ps9670 qa c67 618605 ps9670 Products Q and A Item html wp9000151 Updated January 8 2012 16 19 Tags dual homed fabric extender fex nexus 5000 nexus 5500 nx os switch profile vpc Previous Post Next Post 12 Comments Add a Comment Pingback Importing Configuration in the Switch Profile Majornetwork pa1 June 30 2012 at 00 06 Did you see any issues with config sync between the devices can you please let me know if you have went through issues Thanks in Advance Pa1 Reply Markku Leiniö June 30 2012 at 21 41 I don t remember seeing any real issues with config sync I d still recommend testing using it outside of any production as with any new feature that affects your day to day operations Reply sitweak December 14 2012 at 10 21 Thanks for this easy tutorial Reply Ryan L June 3 2013 at 20 45 Hi Markku Thanks for the guide Regarding the pre provisioning I currently have dual homed FEX modules with manual config on both of them to keep them synced up

    Original URL path: https://majornetwork.net/2012/01/dual-homed-fexes-and-switch-profiles/ (2016-04-25)
    Open archived version from archive

  • Nexus 5000 Tips for Catalyst Admins – Majornetwork
    understand what 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

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

  • FEX Pre-provisioning – Majornetwork
    x 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

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



  •