Similar Questions

• Dynamic assignment of the NAC to the same vlan came on and off strip

  Hello

  Pls forgive my ignorance, I'm fresh in the biz of the NAC.

  I have a requirement for a client, very large high rising with numerous hospital, they want to assign MDs to the same vlan, if he or she uses the Office at out clinic, which would be OOB Layer 3, and even he or she uses the Tablet PC/PDA wireless during the round room.

  The question is whether this is something achievable. A little trick how to do it would be very useful.

  Appreciate your expertise.

  Thank you

  Saami

  By user role VLAN can be activated for OOB.

  The VIRTUAL LAN is configured on the role and setting up OOB, there is a check box that you need to activate so that the user receives the vlan configured on the role (I don't remember the exact section now..).

  With that, whenever a user who belongs to a specific role connects, he will receive the same VLAN according to what is set up on its role.

  I hope this helps.

• Cannot ping hosts on the same vlan on the 2 switches.

  Hey guys so I create my own network in Packet Tracer 6.3. While the hosts can ping others on the same switch 2960 and VLAN, they are unable to ping a host on another switch in the same VLAN. For example. Josh PC on S1 (192.168.10.10) cannot ping PC Doge on S2 (192.168.10.13). I'm sure that they are on the same subnet, so I thing it is a problem of junction...

  S1:

  S1 #show ip int br

  Interface IP-Address OK? Method State Protocol

  FastEthernet0/1 unassigned YES manual up up

  FastEthernet0/2 unassigned YES manual up up

  FastEthernet0/3 unassigned YES manual up up

  FastEthernet0/4 unassigned YES manual up up

  FastEthernet0/5 unassigned YES manual administratively down down

  FastEthernet0/6 unassigned YES manual administratively down down

  FastEthernet0/7 unassigned YES manual administratively down down

  FastEthernet0/8 unassigned YES manual administratively down down

  FastEthernet0/9 unassigned YES manual administratively down down

  FastEthernet0/10 unassigned YES manual administratively down down

  FastEthernet0/11 unassigned YES manual administratively down down

  FastEthernet0/12 unassigned YES manual administratively down down

  FastEthernet0/13 unassigned YES manual administratively down down

  FastEthernet0/14 unassigned YES manual administratively down down

  FastEthernet0/15 unassigned YES manual administratively down down

  FastEthernet0/16 unassigned YES manual administratively down down

  FastEthernet0/17 unassigned YES manual administratively down down

  FastEthernet0/18 unassigned YES manual administratively down down

  FastEthernet0/19 unassigned YES manual administratively down down

  FastEthernet0/20 unassigned YES manual administratively down down

  FastEthernet0/21 unassigned YES manual administratively down down

  FastEthernet0/22 unassigned YES manual administratively down down

  FastEthernet0/23 unassigned YES manual administratively down down

  FastEthernet0/24 unassigned YES manual administratively down down

  GigabitEthernet0/1 unassigned YES manual down down

  GigabitEthernet0/2 unassigned YES manual down down

  Vlan1 unassigned YES manual administratively down down

  Vlan2 unassigned YES manual downwards upwards

  Vlan10 unassigned YES manual up up

  S1 #show interface f0/1 switchport

  Name: Fa0/1

  Switchport: enabled

  Administrative mode: trunk

  Operational mode: trunk

  Encapsulation of administrative circuits: dot1q

  Operational Trunking encapsulation: dot1q

  Trunking negotiation: Off

  The VIRTUAL LAN access mode: (default) 1

  Native mode VLAN Trunking: 2 (native)

  The voice of VLAN: no

  Private-vlan host association Directors: no

  Mapping of private - vlan management: no

  Private-vlan trunk administration VLAN native: no

  Private - vlan administration trunk encapsulation: dot1q

  Private-vlan trunk administration VLAN normal: no

  Private-vlan trunk administration private VLAN: no

  Private-vlan operational: no

  VLAN Trunking enabled: ALL

  Pruning VLANS enabled: 2-1001

  Capture Mode disabled

  Capture VLAN allowed: ALL

  Protected: false

  The unit trust: no

  S1 #show vlan br

  Ports of status for the name of VLAN

  ---- -------------------------------- --------- -------------------------------

  1 by default active Fa0/5, Fa0/6, Fa0/7, Fa0/8

  Fa0/9, Fa0/10, Fa0/11, Fa0/12

  FA0/13, Fa0/14, Fa0/15, Fa0/16

  FA0/17, Fa0/18, Fa0/19, Fa0/20

  FA0/21, Fa0/22, Fa0/23 and Fa0/24

  Gig0/1, Gig0/2

  2 active native

  5 active

  10 active VLAN0010 Fa0/2, Fa0/3, Fa0/4

  active by default fddi 1002

  assets of token-ring-default 1003

  1004 fddinet - default active

  1005 trnet - default active

  Trunk interface #show S1

  VLAN Mode Encapsulation native port State

  FA0/1 on 802. 1 trunking q 2

  Port VLAN allowed on trunk

  5,10,20 FA0/1

  Port VLAN authorized and active in the field of management

  FA0/1 5,10

  VLAN port extending on transmission State and no tree pruned

  FA0/1 5,10

  S1 #show mac-address-table

  Mac address table

  -------------------------------------------

  VLAN Mac Address Type Ports

  ---- ----------- -------- -----

  5 00d0.d37a.ed01 DYNAMICS Fa0/1

  S2:

  S2 #show ip int br

  Interface IP-Address OK? Method State Protocol

  FastEthernet0/1 unassigned YES manual up up

  FastEthernet0/2 unassigned YES manual up up

  FastEthernet0/3 unassigned YES manual up up

  FastEthernet0/4 unassigned YES manual up up

  FastEthernet0/5 unassigned YES manual administratively down down

  FastEthernet0/6 unassigned YES manual administratively down down

  FastEthernet0/7 unassigned YES manual administratively down down

  FastEthernet0/8 unassigned YES manual administratively down down

  FastEthernet0/9 unassigned YES manual administratively down down

  FastEthernet0/10 unassigned YES manual administratively down down

  FastEthernet0/11 unassigned YES manual administratively down down

  FastEthernet0/12 unassigned YES manual administratively down down

  FastEthernet0/13 unassigned YES manual administratively down down

  FastEthernet0/14 unassigned YES manual administratively down down

  FastEthernet0/15 unassigned YES manual administratively down down

  FastEthernet0/16 unassigned YES manual administratively down down

  FastEthernet0/17 unassigned YES manual administratively down down

  FastEthernet0/18 unassigned YES manual administratively down down

  FastEthernet0/19 unassigned YES manual administratively down down

  FastEthernet0/20 unassigned YES manual administratively down down

  FastEthernet0/21 unassigned YES manual administratively down down

  FastEthernet0/22 unassigned YES manual administratively down down

  FastEthernet0/23 unassigned YES manual administratively down down

  FastEthernet0/24 unassigned YES manual administratively down down

  GigabitEthernet0/1 unassigned YES manual down down

  GigabitEthernet0/2 unassigned YES manual down down

  Vlan1 unassigned YES manual administratively down down

  Vlan2 unassigned YES manual downwards upwards

  Vlan5 unassigned YES manual up up

  Vlan10 unassigned YES manual up up

  Vlan20 unassigned YES manual up up

  Vlan99 unassigned YES manual administratively down down

  S2 #show interface f0/1 switchport

  Name: Fa0/1

  Switchport: enabled

  Administrative mode: trunk

  Operational mode: trunk

  Encapsulation of administrative circuits: dot1q

  Operational Trunking encapsulation: dot1q

  Trunking negotiation: on

  The VIRTUAL LAN access mode: (default) 1

  Native mode VLAN Trunking: 2 (native)

  The voice of VLAN: no

  Private-vlan host association Directors: no

  Mapping of private - vlan management: no

  Private-vlan trunk administration VLAN native: no

  Private - vlan administration trunk encapsulation: dot1q

  Private-vlan trunk administration VLAN normal: no

  Private-vlan trunk administration private VLAN: no

  Private-vlan operational: no

  VLAN Trunking enabled: ALL

  Pruning VLANS enabled: 2-1001

  Capture Mode disabled

  Capture VLAN allowed: ALL

  Protected: false

  The unit trust: no

  S2 #show vlan br

  Ports of status for the name of VLAN

  ---- -------------------------------- --------- -------------------------------

  1 by default active Fa0/5, Fa0/6, Fa0/7, Fa0/8

  Fa0/9, Fa0/10, Fa0/11, Fa0/12

  FA0/13, Fa0/14, Fa0/15, Fa0/16

  FA0/17, Fa0/18, Fa0/19, Fa0/20

  FA0/21, Fa0/22, Fa0/23 and Fa0/24

  Gig0/1, Gig0/2

  2 active native

  5 active

  10 VLAN0010 active Fa0/4

  20 VLAN0020 active Fa0/2, Fa0/3

  active by default fddi 1002

  assets of token-ring-default 1003

  1004 fddinet - default active

  1005 trnet - default active

  S2 #show mac-address-table

  Mac address table

  -------------------------------------------

  VLAN Mac Address Type Ports

  ---- ----------- -------- -----

  2 0030.f2c1.94e5 STATIC Fa0/1

  2 0060.5c83.3401 STATIC Fa0/1

  10 0002.4ae9.6964 STATIC Fa0/4

  10 0060.5c83.3401 STATIC Fa0/1

  20 0009.7c9a.a134 STATIC Fa0/2

  ----------------------------------------------------------------------------------

  Let me know what I missed here. All connections are made with a straight through cable.

  See you soon

  Josh

  Try to remove the S2 switchport port-security:

  interface FastEthernet0/1
   no switchport port-security

• Tagged management VLAN and the virtual machines on the same VLAN

  I'm faced with a problem related to our Brocade switches newly acquired and get the private VLAN to work on trunk connections to our ESX servers.  Every time I try something different, he creates a new problem.

  In our configuration, our management of VLAN is not tag and we have a VLAN for this management network that is placed on our switches VLAN no marked native.  We also have virtual machines hosted on those same ESX servers that are on the same VLAN and everything works fine.  However, when I change the ESX management to carry a label on this VLAN and change the switchports accordingly (IE no untagged VLAN native), management work, but hosted on the ESX Server machines that are on the same VLAN can get no network connectivity.

  Is it possible to have a management network labeled and also the host of virtual machines on the same VLAN or is it totally impossible?  I'm not very familiar with networking behind ESX, so I apologize if this is a dumb question with an obvious answer.

  Thank you

  Mark J.

  Is it possible to have a management network labeled and also the host of virtual machines on the same VLAN or is it totally impossible?

  Yes, it is possible... why it doesn't work for you I don't know, but try the following:

  1. set up the Group of ports of VMS to use VLAN;

  2 configure the interface of management VMkernel port group use VLAN;

  3 configure the physical switch port to allow to this VLAN and put the default VLAN natively for these interfaces.

• network stream between 2 virtual machines in the same vlan and host using DVS

  Hi experts, so 2 virtual machines on the same vlan / subnet and on the same esxi host using VDS need to talk to each other, that they get switched by the VDS internally or they headed north for network switches and come back?

  Welcome to the community - it will stay internal to the ESXi host.

• Install ESXi on the same VLAN as VM traffic

  I know it is advisable to separate your network management, but in this case we do not have a VLAN additional to devote to this.

  What to look out for when you use the same VLAN to install ESXi (network management) like some of my virtual machines?

  Also, I downloaded ESXi installable 4.1; I still need the local disks on my correct server install?

  The reason of VLAN in your example would be more for safety. Using a separate physical NIC for different traffic (management, vmotion, etc.) is more about performance, although a separate network offers security. If all goes well in your network design, you create a secure network that isolates the management and storage of regular network traffic traffic.

  ESXi can be installed directly on a USB flash drive. It's a support install destination from the installation CD.

• Two servers in the same vlan, DMZ can be firewall with each other?

  I have a Windows server vm on a DMZ, and I need to add another soon.  We need to separate these two servers so that neither can see the other, but they must be on the same vlan.  I'm looking for in vShield, but do not have this installer again.  VShield will be able to separate them, or someone has a better suggestion?

  Hello

  Ah, your physical switch uses VLAN private for your guests. If you use a distributed virtual switch, you can configure one by VM PVLAN allowing entrants but no communication between the nodes.

  If you are using VMsafe you can achieve the same thing using the policy that denies the communication to the VM in VM virtual machines via subnet blocks but allows access from your firewall.

  VMsafe and vShield Zones are two distinctly different firewall technologies. vShield Zones is a firewall device VMsafe-net is located just before the vNIC on penetration or just after on the output of the vNIC. Each of the different problems, but for this use case, VMsafe can be the best way to go.

  If you do not have an Enterprise Plus license then you cannot use the virtual distributed switches so PVLANs may not work for you.

  Best regards
  Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

  Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

  Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

  Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

• WAP321 two Pat same SSID on the same piece with the installation of single point / cluster

  Hello!

  It has bought several WAP321.

  We have a room which has about 40 books, so I will deploy the two Pat in there (according to recommended 20 clients per WAP on specifications).

  I configured the first WAP, created a cluster and the SSID, then joined the second WAP to the same cluster with the installation of single point, he received the same cluster radio settings (SSID, WPA2 key, etc.)

  My requirements are:

  1: configure all laptops with the same unique SSID created on the WAP (which has spread to the second WAP via single point of installation/cluster)

  2: having the laptop connect automatically to one of the Pat.

  3: If a WAP fails, the laptop can connect automatically to the other.

  Is this possible?

  If Yes, are the measures taken are correct, or is there something else? (and how does the cell know what WAP to connect if two WAPS is configured with the same SSID?)

  Thank you very much!

  Hello

  Thanks for posting your question on the forums.

  Setup you had set up will work fine for your application, I highly recommend to make sure that you have two AP running on different statically assigned channels, you can put one on channel 1 and the other on Channel 6 or 11. This will prevent them to conflict with each other.

  Now, there is no real way to select what AP you connect or even know that you you already connected to without special software, in fact, when a device gets on the network and seeking to connect to the radio will connect to the first point of access that meets the demand, if it is no longer available then it forwards the request again and it will connect to one who works.

  I hope this helps. Please let us know if you have any other questions

• Inter communication VM in two ESXi using the same VLAN ID

  Hello

  I am creating a lab in my server ESXi (192.168.1.10). The default VLAN (VMNetwork) connected to ESXi is VLAN 1. If the virtual machines with 192.168.1.xx IP. able to communicate to the external network.

  But I created a new 25 VLAN in my ESXi and added two virtual machines in that ESXi. Communication between these two VMs is perfect.

  My question is, what should I do if I need these 2 VMs to connect a computer virtual hosted in an another ESXi with 25 VLAN?

  Thank you

  Nithin

  Well lets go back to the original question:

  But I created a new 25 VLAN in my ESXi and added two virtual machines in that ESXi. Communication between these two VMs is perfect.

  My question is, what should I do if I need these 2 VMs to connect a computer virtual hosted in an another ESXi with 25 VLAN?

  If you don't want your VM in 25 a VLAN on a HOST to speak to other virtual machines in the VLAN 25 to HOST B, you will need to configure it as the attached picture:

  

  Your psyhical switch should the Tag VLAN on ports so that he knows how to route traffic.  Now I guess that your fault WHAT VLAN on all your switches is 1 as it is pretty standard.  VLAN 1 is also past reguardless so you will probably just tag with 25 ports VLAN.  Once the ports are all stamped this VLAN, they will be able to talk with success.  Now what happens, it's your 2 VMS in the vSwitch can talk because they are both on the same vSwitch with VLAN Tag on it, however, when you try to talk to another virtual machine to another host the package arrives at your psyhical pass and does not see a label on this port if it falls.  The only ports that you need to add this tag VLANS are the your NIC psyhical on the host with that vSS is connected.

  I hope that this has helped or made things clearer

• One of the virtual machine gets the APIPA address after you have configured with a static IP address, where the other VMS works very well with same vlan with static IP

  We have deployed 3 VMs with the same vlan where one virtual machine gets APIPA address, even after the configuration of the IP address manually.

  We do not have servers DHCP and other VMs 2 find with the same vlan

  No IP address is not used by another system and another IP address works

  Meanwhile, I just googled and got a God save the link that helped me in the question of fixing

  http://lyngtinh.blogspot.in/2011/12/how-to-disable-Autoconfiguration-IPv4.html

• Two groups of ports with same VLAN on the same Vswitch?

  I'm doing a consolidation.  We had two different people put up two closed different of Vsphere and different network labels were used.   Of course the network labels must exactly match vmotion without losing connectivity.    So I was hoping that I could just create groups in double port on my vswitch for VLAN do not match them.  I know I could just migrate them and move quickly from the network label, but some of them are essential and may not fall.

  For example, on a cluster, I might have a port for Vlan ID 88 group that says 'Web DMZ'.  But the other cluster has "WWW" VLan ID 88.    Can I just create a second group of ports on the first group which also used Vlan ID 88 with the name 'WWW' and I started?    Which will cause problems with switching (loops, etc.)?

  Hope it makes sense.  Guess the short answer is can I I have two groups of different ports on a vswitch using the same VLAN ID tag without causing problems?

  Creation of several groups of ports with the same VLAN ID should not cause any problem. This is only marking/close the traffic to and from the virtual machine, is nothing like that of loops,... to be afraid of.

  André

• Two VLANs in the same network bubble?

  Hi all!

  I do not know very well of networking, and don't know my VMware network guy, so I hope that someone here might be able to answer my question. Thank you!

  I'm testing the conversion of some of our production servers. Since they have the same name, they are all in a bubble of network on the same host. So I have a vSwitch called "Bubble Network Test" which has several virtual machines, but who doesn't have an uplink (no associated physical map). So far, this has worked very well. So that users to test, I also have two XP machines to also live in this bubble. However, we will have performance issues. In our test of D/R one a few months ago, we found that the application performed very bad when the customer was in the same VLAN as the server; change the client to a VLAN different fixed performance.

  So, I would do it here in the hope that it will improve performance. However, I do not know how to do it. Can anyone offer any tips/advice on how to have more than one VLAN in the same network bubble? I have to make two vSwitches and then connect them somehow?

  Thank you!

  As long as you stay internal to the ESX Server then Yes you will need virtual switches - you will have then a virtual machine that will span two switches, acting as a router routing traffic between VLANS.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Several groups of PS in the same subnet

  Is there something wrong with having two PS series groups (and, therefore, their members) in the same 24 subnet and the same VLAN?  We have a PS Group in the same place we are moving to another site that already has a PS Group.  We would like to just take advantage of the networking and configuration of VLAN, that we have so I just want to check that it is not a problem to do this.

  Thank you

  Bryan

  Hello Bryan,

  The only limits are the IP addresses available, switch ports available and that the switch can handle the load increases.  Especially if you share the SAN and LAN traffic to the same switch.  Also the link between the switches might need to increase as well.

  There is nothing inherit in the design to prevent it.   In my lab, I have quite a bit on the same subnet.

  Kind regards

• Extend the L2 VLAN multi-site WAN

  Hello

  I have several sites connected over a MPLS network provider, everything works as expected, have full connectivity L3 in all these sites.

  I now need to establish layer 2 connectivity (VLAN) on the 21 sites. Ideally, I would intend to attach additional routers behind routers of THIS (don't have no access to these suppliers or PEs, but provider may re - configure BGP on the CE peer with our device) and use a port on these routers as port Lan Layer 2, but do not know which technology to use

  1. L2TPv3 comes to mind, but can L2TPv3 works in a multipoint configuration? Can I have a site as a hub and others like rays and talk through the hub? Traditional using L2TPV3 config, how do I use multiple Xconnects for the same VLAN on the same interface?
  2. Worse, I can run on (also our new routers VPLS PEs) MPLS VPLS, but seems like overkill.

  What you guys say is the most simple/more elegant solution for this puzzle?

  L2TPv3 does not support multitouch.  It can perform point to point.

  VPLS does support multitouch, but you need much more expensive kit to do.

  I have just a brainwave!  You only use the IP protocol for this network of layer 2?  If so, use LISP.  It works on the same lower end kit of Cisco.  I would like to convert your entire network to him.

  In particular, you must activate the LISP mobility.

  General information of LISP:

  http://Lisp.Cisco.com/

  An example of an extension of the continuous complex layer 2 using LISP with full redundancy.  You don't want something this complex, but it shows what you want to do, and the massive power that LISP has.

  http://www.Cisco.com/c/en/us/TD/docs/solutions/Enterprise/Data_Center/DCI/5-0/LISPmobility/DCI_LISP_Host_Mobility/LISPmobile_4.html

• Problem with FWSM and the same L3 interface switch

  I have two 6513 s with a 802. 1 q trunk linking them. Each switch is redundant Sup720s running in native mode, worm IOS 12.2 (18) SXF (that they were running out of SXD3). A FWSM (ver 2.3 (3), routed mode, unique context) is in each switch, Setup in failover mode.

  I can't get a PC in a virtual LAN that has the defined layer 3 interface on the switch with the active FWSM in this document, to communicate with the devices 'behind' the FWSM. If I move the configuration of layer 3 to this vlan to the other 6513, everything works fine.

  The MSFCs are inside the firewall, they have a configured layer 3 interface in the same vlan as the FWSM 'inside' interface. Several "same security level" interfaces are defined on the FWSM and used to protect the farms. I use OSPF on the MSFCs and FWSM and the routing table is correct.

  The FWSM generates connections to the attempts made by the PC with interface layer 3 defined on the same switch as the active FWSM very well, so this isn't a problem with FWSM ACL.

  A ping of the FWSM "inside" interface from a PC with the defined layer 3 interface on the same switch as the active FWSM fails, although debug icmp trace on the FWSM demand and response shows. A the packet capture, using the NAM-2, only shows the request packets. I captured on the vlan common and FWSM port channel interface bottom of basket.

  Just to add to the confusion, if I capture in the same places, but do the ping of a PC which is in a VLAN with the interface of layer 3 defined in the 6513 which does not contain the active FWSM, that works very well, I see the request and response on the capture of vlan common, but only on demand on the capture of the port channel.

  This problem has been there since the beginning of this implementation and has not changed with IOS and FWSM software upgrades. I had this experience with all the VLANS that I tried to define the interface of layer 3 to on the switch with the active FWSM. I turned on MLS.

  If anyone has experienced this and solved, or knows what is happening, I would be grateful for any ideas.

  Thank you.

  Keith

  Keith, are you running etherchannel distributed on of your 6513?