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".
  • unix – Majornetwork
    made it possible to automate certain things easily That concept also extends to other environments and Cygwin is one of my favorite tools on Windows computers because 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 2013 March

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


  • config sync – Majornetwork
    it is possible to import existing configurations into the switch profiles Now I was really attempting it in practice When importing configurations I constantly struck myself to the 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 2013

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

  • Importing Configuration in the Switch Profile – Majornetwork
    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 disabled When

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

  • Importing Configuration in the Switch Profile – Majornetwork
    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 disabled When

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

  • Importing Configuration in the Switch Profile – Majornetwork
    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 disabled

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

  • Dual-homed FEXes and Switch Profiles – Majornetwork
    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 I

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

  • Dual-homed FEXes and Switch Profiles – Majornetwork
    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 I just

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

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

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



  •