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".
  • cleur – Majornetwork
    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 2013

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


  • orphan port – Majornetwork
    in the vPC primary switch This means that if you have non vPC connected hosts on your vPC secondary switch then those ports are left up and traffic 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/orphan-port/ (2016-04-25)
    Open archived version from archive

  • Configuring vPC to Suspend Orphan Ports – Majornetwork
    Jun 28 12 09 28 n5k 1 ETHPORT 5 SPEED Interface Ethernet100 1 45 operational speed changed to 1 Gbps 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF DUPLEX Interface Ethernet100 1 45 operational duplex mode changed to Full 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF RX FLOW CONTROL Interface Ethernet100 1 45 operational Receive Flow Control state changed to off 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF TX FLOW CONTROL Interface Ethernet100 1 45 operational Transmit Flow Control state changed to on 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF UP Interface Ethernet100 1 45 is up in mode access So if you want to configure orphan ports to suspend do that before deploying the ports or prepare for some maintenance time Updated June 28 2012 12 35 Tags cisco nexus 5000 nexus 5500 orphan port vpc Previous Post Next Post 5 Comments Add a Comment Ian Erikson June 29 2012 at 08 38 Nice that you put together a post for this this is key for people with the straight through active active FEX design Reply Markku Leiniö June 29 2012 at 08 45 Thanks Ian and you are so right Yes basically these are the general rules if you are not using vPC to your end hosts all ports in the straight through single homed FEXes are orphan ports none of the ports in active active dual homed FEXes are orphan ports How many of you have configured the single homed FEX ports with vpc orphan port suspend for hosts that are not connected with vPC Again this all depends on your topology ie how you have connected your N5k pair to the upstream network If you use vPC on the N5k pair

    Original URL path: https://majornetwork.net/2012/06/configuring-vpc-to-suspend-orphan-ports/?replytocom=1732 (2016-04-25)
    Open archived version from archive

  • Configuring vPC to Suspend Orphan Ports – Majornetwork
    Jun 28 12 09 28 n5k 1 ETHPORT 5 SPEED Interface Ethernet100 1 45 operational speed changed to 1 Gbps 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF DUPLEX Interface Ethernet100 1 45 operational duplex mode changed to Full 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF RX FLOW CONTROL Interface Ethernet100 1 45 operational Receive Flow Control state changed to off 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF TX FLOW CONTROL Interface Ethernet100 1 45 operational Transmit Flow Control state changed to on 2012 Jun 28 12 09 28 n5k 1 ETHPORT 5 IF UP Interface Ethernet100 1 45 is up in mode access So if you want to configure orphan ports to suspend do that before deploying the ports or prepare for some maintenance time Updated June 28 2012 12 35 Tags cisco nexus 5000 nexus 5500 orphan port vpc Previous Post Next Post 5 Comments Add a Comment Ian Erikson June 29 2012 at 08 38 Nice that you put together a post for this this is key for people with the straight through active active FEX design Reply Markku Leiniö June 29 2012 at 08 45 Thanks Ian and you are so right Yes basically these are the general rules if you are not using vPC to your end hosts all ports in the straight through single homed FEXes are orphan ports none of the ports in active active dual homed FEXes are orphan ports How many of you have configured the single homed FEX ports with vpc orphan port suspend for hosts that are not connected with vPC Again this all depends on your topology ie how you have connected your N5k pair to the upstream network If you use vPC on the N5k pair

    Original URL path: https://majornetwork.net/2012/06/configuring-vpc-to-suspend-orphan-ports/?replytocom=1747 (2016-04-25)
    Open archived version from archive

  • mst – Majornetwork
    Name test Revision 0 Instances configured 3 Instance Vlans mapped 0 1000 4094 1 1 100 2 101 999 These secondary vlans are not mapped 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 March

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

  • mstp – Majornetwork
    Name test Revision 0 Instances configured 3 Instance Vlans mapped 0 1000 4094 1 1 100 2 101 999 These secondary vlans are not mapped 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 March

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

  • promiscuous – Majornetwork
    existed a long time in Cisco switches but still there are some known and unknown limitations in using it Let s talk about PVLANs First the basics 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/promiscuous/ (2016-04-25)
    Open archived version from archive

  • Private VLANs on Nexus 5000 Series – Majornetwork
    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 association

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



  •