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".
  • Designing Nexus 5500 for Distribution Layer – Majornetwork
    reboots to load the new software The reboot takes something like 80 seconds to complete While the control plane reboots the switch is unable to send or receive anything control plane related frames And while this is the case it may or may not have some effect on the neighboring devices If the conditions are not right then NX OS refuses to do ISSU and reverts back to old style just reboot all method which obviously works but causes some traffic interrupts About the cases I mentioned above they all create some exceptions for the ISSU Connecting access switches As the Nexus switch is unable to send BPDUs normally during the ISSU it is directly specified that if you have any STP designated ports on the switch other than the vPC peer link then ISSU is not supported And that would be the case if you connect access switches on your Nexus 5500 and your STP root is somewhere in your Nexus 5500s or upstream from that Access switches rarely are STP roots aren t they Using LACP fast hellos Since an LACPDU is expected by the other party in 3 seconds at most using LACP fast hellos is not compatible with ISSU Using BA Again since the BPDUs are regularly expected by the other party using BA is not compatible with ISSU BA can be used in the vPC peer link however because the vPC switches communicate with each other about the ISSU What can you do I will be connecting access switches to Nexus 5500s in vPC for sure and I would like to use ISSU as well so I have some ideas For connecting the access switches with LACP the rule for using LACP fast hellos is quite clear don t Just use the normal timers and ISSU will be possible because the Nexus 5500 is back online in 80 seconds or so before the LACP keepalive timers expire on the neighboring devices About using BA it is also better not to use it for access switch connections at all Not all access switches even support it I guess About the STP designated port limitation You could always disable STP altogether because there is only a single logical link port channel between the switches but I really don t recommend that RSTP MSTP in the background provides a safety measure for some incorrect physical connections so let s keep that running Updated 09 Jan 2012 Now this is totally incorrect information starting here Instead before starting the ISSU just go and shutdown the ports on Nexus 5500 that are connecting to the downstream access switches This assumes that all the access switches are properly connected with port channels to two Nexus 5500 at the same time During the uplink port shutdown the access switches will continue to use the other member of the port channel uplink and no harm is done end of bullshit That is not the case Even if you shutdown the other uplink port

    Original URL path: https://majornetwork.net/2011/08/designing-nexus-5500-for-distribution-layer/?replytocom=1574 (2016-04-25)
    Open archived version from archive


  • nexus – Majornetwork
    make sense A FEX is a device that looks like a data center LAN switch but it is not designated as a switch FEX needs a 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 2013

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

  • smart install – Majornetwork
    make sense A FEX is a device that looks like a data center LAN switch but it is not designated as a switch FEX needs a 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 2013

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

  • catalyst 4500 – Majornetwork
    There aren t really many cases you can go wrong operationally with it in general purpose data center or even campus environments But if you think they cost 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/catalyst-4500/ (2016-04-25)
    Open archived version from archive

  • catalyst 4500-x – Majornetwork
    There aren t really many cases you can go wrong operationally with it in general purpose data center or even campus environments But if you think they cost 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/catalyst-4500-x/ (2016-04-25)
    Open archived version from archive

  • Choosing Your Core Switches – Majornetwork
    to cluster two switches together If your access layer is not very wide you could run your core with Cat4500 X Catalyst 3750 X Why am I continuing this list I m really entering a territory I don t handle stacking switches I just haven t liked them Too much dependencies between the switches and horror stories everywhere But maybe you could stack two Catalyst 3750 X s together and run your small core on those Cat3k family is restricted on VLANs and MAC addresses when compared to the options above And then there is more DC grade stuff Nexus 3000 L2 L3 10G switch but more oriented to low latency implementations with no special feature requirements Catalyst 4948 Catalyst 4900M and so on The features are similar to Catalyst 4500 but in smaller box with limited number of interfaces available There is one buzzword that I didn t mention above FabricPath That is something that I m really interested in at the moment And that is FabricPath especially with Nexus 5500 switches How cool would it be to easily implement L2 topologies with selected service and routing entities connected to the leaf nodes meaning that there really needn t to be any separate core in every case The truth is that I don t exactly know Yet Updated February 10 2012 22 42 Tags cat6500 catalyst 4500 catalyst 4500 x catalyst 6500 fabric extender fabricpath fex nexus 5500 nexus 7000 Previous Post Next Post 7 Comments Add a Comment Ryan Malayter April 9 2012 at 17 01 As someone who inherited a design with a 3750 stack in the core of a small DC all I can say is just don t You can t do software upgrades without taking down the whole stack and the inevitable IOS bugs also usually take down the whole stack Stack master failover only seems to really work only in a power cut scenario Reply Mr Nam March 22 2013 at 11 31 Dear Ryan Malayter Now i m doing a desgin for Migration of a campus network Current my system is using 2 core switch C4506 and be linked by ethernet channel Now i want to recommend a replacement 2 coreswitch C4506 to C4506 E because we have over 1000 users but my friend want to use stack solution by 2 switch stack 3570X I think that if using Stack switch will not guarantee for current network requirements because it limit with performance bandwitch Could you comment to help me I actually want to know pros con between 2 this solution Thank Reply rmalayter April 5 2013 at 17 26 I don t think the bandwidth on the interconnect are likely to be your problem Indeed assuming you are buying new switches the new 3850 which replaces the 3750 series has ample bandwidth on the stack interconnect for almost all scenarios 128 Gbps as I recall The problem is that there is just one software image management and control planes actually running

    Original URL path: https://majornetwork.net/2012/02/choosing-your-core-switches/?replytocom=857 (2016-04-25)
    Open archived version from archive

  • Choosing Your Core Switches – Majornetwork
    to cluster two switches together If your access layer is not very wide you could run your core with Cat4500 X Catalyst 3750 X Why am I continuing this list I m really entering a territory I don t handle stacking switches I just haven t liked them Too much dependencies between the switches and horror stories everywhere But maybe you could stack two Catalyst 3750 X s together and run your small core on those Cat3k family is restricted on VLANs and MAC addresses when compared to the options above And then there is more DC grade stuff Nexus 3000 L2 L3 10G switch but more oriented to low latency implementations with no special feature requirements Catalyst 4948 Catalyst 4900M and so on The features are similar to Catalyst 4500 but in smaller box with limited number of interfaces available There is one buzzword that I didn t mention above FabricPath That is something that I m really interested in at the moment And that is FabricPath especially with Nexus 5500 switches How cool would it be to easily implement L2 topologies with selected service and routing entities connected to the leaf nodes meaning that there really needn t to be any separate core in every case The truth is that I don t exactly know Yet Updated February 10 2012 22 42 Tags cat6500 catalyst 4500 catalyst 4500 x catalyst 6500 fabric extender fabricpath fex nexus 5500 nexus 7000 Previous Post Next Post 7 Comments Add a Comment Ryan Malayter April 9 2012 at 17 01 As someone who inherited a design with a 3750 stack in the core of a small DC all I can say is just don t You can t do software upgrades without taking down the whole stack and the inevitable IOS bugs also usually take down the whole stack Stack master failover only seems to really work only in a power cut scenario Reply Mr Nam March 22 2013 at 11 31 Dear Ryan Malayter Now i m doing a desgin for Migration of a campus network Current my system is using 2 core switch C4506 and be linked by ethernet channel Now i want to recommend a replacement 2 coreswitch C4506 to C4506 E because we have over 1000 users but my friend want to use stack solution by 2 switch stack 3570X I think that if using Stack switch will not guarantee for current network requirements because it limit with performance bandwitch Could you comment to help me I actually want to know pros con between 2 this solution Thank Reply rmalayter April 5 2013 at 17 26 I don t think the bandwidth on the interconnect are likely to be your problem Indeed assuming you are buying new switches the new 3850 which replaces the 3750 series has ample bandwidth on the stack interconnect for almost all scenarios 128 Gbps as I recall The problem is that there is just one software image management and control planes actually running

    Original URL path: https://majornetwork.net/2012/02/choosing-your-core-switches/?replytocom=1782 (2016-04-25)
    Open archived version from archive

  • cisco live – Majornetwork
    in this world class Cisco event the first time was in Networkers 2008 in Barcelona This time we were four network specialists and architects attending from our 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/cisco-live/ (2016-04-25)
    Open archived version from archive



  •