VMOTION between the VLAN

Similar Questions

• 4240, blocking some of the traffic between the VLANS local

  I have an IPS 4240 in interface mode inline between our firewall switches and kernel in the periphery. This connection is a trunk with 2 port VLAN, lets call them A and b. everything works fine 100% between the VLANS (the firewall makes routing inter - vlan) except for SSH/telnet of VLAN A VLAN B, which is a big problem.

  Everything works fine, including:

  Web/443/TFTP from A to B

  SSH/Telnet from B to a.

  SSH/Telnet to nowhere A share around the world

  SSH/Telnet from other networks to B

  I removed the IPS of the equation, and everything is back to normal, so something must be up with the PPE.

  This is a new deployment... so the sensor uses its default configuration. I don't see anything stuck. About the only thing that has been set up are the interfaces. I tried different values in the field VLAN by default in menu interface configuration does not, and I don't think it's related to the configuration of VLANS since https/web and everything works fine.

  What I'm missing here? Any ideas?

  Thanks AOT

  There were a few [normalizer engine] signatures that will drop the traffic without alerting. I don't know if they still do, but check for active sigs that use the normalizer engine and is not an alert action.

• a vSwitch does support internal traffic between the VLANS configured on the same vswitch?

  Hey gurus - I know that the virtual machines on the same port group will communicate internally - but a vSwitch will support internal communications between virtual machines on different VLANS configured on the same vSwitch?  Looking for definitive answers only.

  gman

  Welcome to the MSFN - no traffic is not internal when communicating through different VLAN-

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

• Not able to communicate between the VLANS on SG300-10

  Please take a look at my crude drawing of how I want my network to work:

  SG300-10
  __________________________________________
  | 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
  |_|___|__________________________________|
  |   |_________________________________
  |_________________                   |
  __________________  _______|_________  _______|_________
  |-VLAN 1-|  | - VLAN 10-|  | - VLAN 20-|
  |   Management |  | 192.168.10.1 |  | 192.168.20.1.
  | 192.168.1.250 |  |               |  |               |
  |________________|  | Internet router |  |   Devices.
  | 192.168.10.2.  | Box of physics |
  |_______________|  | 192.168.20.2 |
  | Server 2008R2.
  | DNS, DHCP, AD DC |
  |               |
  | Physical boxes |
  | 192.168.20.x |
  | W7 Workstations |
  |_______________|

  I put a static IP address on the server 2008R2 host and Internet router.  I have configured my VLAN and I put each VLAN IP (as shown above), I put a 0.0.0.0 route to the Internet router, but also routes for each range of IP VLAN x.x.x.0 and I put the gateway on all host on VLAN 20 to be 192.168.20.1.

  I'm unable to access the Internet, ping the router or access the webpage switch management of any host on VLAN 20 unless I manually set the IP address on the host VLAN 20 on the same IP range as the machine I'm trying to get. As such:

  If I manually set the IP host address to 192.168.1.50, I can access the administration of the switch, but then not RDP in or ping any host on VLAN 20 or ping the router Internet on VLAN 10.

  If I manually set the IP host address to 192.168.10.50, I can ping the router Internet but cannot RDP into or ping any device on VLAN 20, nor can I access the Switch Management page.

  If I let DHCP assign the IP 192.168.20.5, I can RDP in and ping all devices VLAN 20, but I can't ping all devices on VLAN 10 or access the administration of the switch to VLAN 1.

  I know I'm missing something simple, and I worked on it for about 30 hours now but can't seem to get this to work. Someone could possibly help?  Thanks in advance.

  Just to be sure, is the SG300 mode switching L3 / L2 switching?

• server traffic between the VLANS (broadcast)?

  Hello

  I have a SGE2010, implemented with different VLANS for use on a LAN.

  I have clients with vlan10 vlan20.

  Vlan30 and admin on vlan40 servers.

  vlan10 = 172.0.1.0/24 gw 172.0.1.1

  vlan20 = 172.0.2.0/24 gw 172.0.2.1

  vlan30 = 172.0.3.0/24 gw 172.0.3.1

  vlan40 = 172.0.4.0/24 gw 172.0.4.1

  But to say that I'm running a server counter-strike. What should I do on the switch for the clients get the server up in the "server list" in the game?

  I read something on the multicast and 'IP helper. " But may not know how to do...

  Hi Torbjeorn, correct to support ip is used, called udp relay on this unit.

  http://www.Cisco.com/en/us/docs/switches/LAN/CSBMs/SFE2000/Administration/Guide/SFE-SGE2xxx_Admin_Guide.PDF

  from page 210.

  -Tom
  Please mark replied messages useful

• The vlan vmotion should join him vlan management for vmotion work?

  Host 1

  Management network is a vswitch. IP VLAN 350 172.31.250.201

  vMotion network is on an another vswitch. VLAN 500 IP 192.168.1.1

  Host 2

  Management network is a vswitch. IP VLAN 350 172.31.250.202

  vMotion network is on an another vswitch. VLAN 500 IP 192.168.1.2

  Running Cisco UCS, the vNIC for vmotion are the vlan 500 but vmotion works only when they have access to the vlan 350 the management vlan.

  Sorry for the question noob but not vmotion need access to the vlan management in order to work?

  Thank you

  No, what you're doing - vMotion running in a dedicated subnet - is actually recommended to do this. Ensure that the UCS switch ports are configured correctly, allowing the VLANS required.

  André

• VMotion between 2 remote hosts on the same site

  Hey everybody. I am new to a company that owns 2 Server vCenter, one in each data center, and we have a few servers standa-only (no not a cluster) in some places.

  All hosts are registered with several Enterprise. Let me draw the locations, you will have an idea:

  VCenter1

  -Datacenter1 (remote domain controller 01)

  * Host1

  ...

  * Host15

  2 VCenter
  

  -Datacenter2 (remote domain controller 01)

  * Host16

  ...

  * Host30

  -Data Center 3 (LAN)

  * HostLocal1

  * HostLocal2

  That make sense, as I have 15 guests on data center 1 and 2. We use 2 VCenter to manage the HostLocal1 and HostLocal2, but we don't group them together and we do not have vMotion among them, because all vMotion traffic must go to vCenter, then on the second host, is this right? Is there a way to prevent this?

  Let me rephrase: VMotion traffic would be like this:

  HostLocal1-> VCenter 2-> HostLocal2

  Or:

  HostLocal1-> HostLocal2.

  Wrote this question down make realize me that my hypothesis is incorrect, vMotion traffic has nothing to do with VCenter, activities stems from these 2 servers. Can anyone confirm?

  Thank you very much for your time.

  We use 2 VCenter to manage the HostLocal1 and HostLocal2, but we don't group them together and we do not have vMotion among them, because all vMotion traffic must go to vCenter, then on the second host, is this right? Is there a way to prevent this?

  Let me rephrase: VMotion traffic would be like this:

  HostLocal1--> VCenter 2---> HostLocal2

  Or:

  HostLocal1--> HostLocal2.

  vMotion traffic runs only between the source and the destination host ESX (i). The assumption that the traffic flows via vCenter's vMotion is downright bad. vCenter is simply required to initiate/control the vMotion between the hosts, but it is completely left out the data transferred between the host to move the virtual machine.

  The assumption that you need a cluster for vMotion object or clustering automatically implies vMotion won't as well.

• Routing between two VLANs on a switch in series SG300

  I've seen a lot of messages from people with problems of traffic between the two routing VLANS with some complex examples.  Can someone show a simple example for a SG300 switch (in layer 3 mode) to set up the two VLAN and send the traffic between VLANS without an external router?

  VLAN1 10.10.10.0

  VLAN2 10.10.20.0

  I tried to do through the UI and can't seem to make it work.  It seems that it must be very simple, so maybe I'm missing something in the GUI.

  Hi Chris,

  I did 5 minutes of recording that showed how I configured the two VLAN on my SG300 switch and layer 3-switched between the VLANS.

  You have no trouble getting to the GUI, so you will have no difficulty to setup in a few minutes...

  • Be sure to use the latest version of the SG300 package, with a bearable CLI.
  • to save your changes to the configuration at the end of the process.
  • the IP addresses that you create will be the address of default gateway for PC hosts on VLANs specified.
  • Recording can be interrupted at any time to perform configuration operations.

  Recording is now available on the website of the WebEx service. Click on the link below to read:

  https://Cisco.WebEx.com/ciscosales/LSR.php?at=PB&SP=MC&rID=55688352&RKEY=05e1fc5fff0d05da

  Configuration of VLAN

  Monday, October 24, 2011 11:02 New York time

  5 minutes

  Have fun

  Best regards, Dave

• Creation of the VLAN between Powerconnect 5548 and F10 s4810...

  In the coming months we will replace our network equipment.  I was able to get their hands on the new gear at the beginning, and if I'm not traditionally a guy from the network, the project has been given to me and I started playing.  The first thing that I wanted to work on was implemented VLANs.  I have configured the switches like the picture below:

  

  When I have IP every PC connected to the same subnet and apply VLAN10 to their respective ports, they aren't to pings within the same stack or between cells.  My basic understanding is that they are, do they not?  Did I miss something in my understanding of VLANS or is there a problem with my configs?  I posted the configs below.

  RTTMOACCESS01 config:

  database of VLAN
  VLAN 10,20,30,40,50
  output
  Add a voice vlan Yes-table Nortel___ 000181
  Add a voice vlan Yes-table 0001e3 Siemens_AG_phone___
  Add a voice vlan Yes-table 00036 b Cisco_phone___
  Add a voice vlan Yes-table 00096e Avaya___
  Add a voice vlan Yes-table 000fe2 H3C_Aolynk___
  Add a voice vlan Yes-table Shoretel___ 001049
  Add a voice vlan Yes-table 0060 b 9 Philips_and_NEC_AG_phone
  VLAN voice Yes-table add 00907 Polycom/Veritel_phone___
  Add a voice vlan Yes-table 00e0bb 3Com_phone___
  860 port address 0.0.0.0 iSCSI target
  port 3260 address 0.0.0.0 iSCSI target
  port 9876 address 0.0.0.0 iSCSI target
  port 20002 address 0.0.0.0 iSCSI target
  20003 port address 0.0.0.0 iSCSI target
  port 25555 address 0.0.0.0 iSCSI target
  hostname rttmoaccess01
  no console logging
  privilege 15
  !
  interface vlan 10
  Name IT
  !
  interface vlan 20
  name UserPCs
  !
  interface vlan 30
  name UserTCs
  !
  interface vlan 40
  the voice name
  !
  interface vlan 50
  Name printers
  !
  gigabitethernet1/0/1 interface
  switchport access vlan 10
  !
  tengigabitethernet1/0/1 interface
  switchport mode general
  switchport general allowed vlan add 10 tag
  switchport general allowed vlan add 20 tag
  switchport general allowed vlan add 30 tag
  switchport general allowed vlan add 40 tag
  switchport general allowed vlan add 50 tag
  !
  gigabitethernet2/0/1 interface
  switchport access vlan 10
  !
  tengigabitethernet2/0/1 interface
  switchport mode general
  switchport general allowed vlan add 10 tag
  switchport general allowed vlan add 20 tag
  switchport general allowed vlan add 30 tag
  switchport general allowed vlan add 40 tag
  switchport general allowed vlan add 50 tag

  !
  Default settings:
  Service etiquette: 76BYTS1
   
  SW version 4.1.0.8 (28 August 2012 time 11:17:36)
   
  Gigabit Ethernet ports
  =============================
  Speed 1000
  full duplex
  negotiation
  flow control
  Auto MDIX
  no back pressure
   
  interface vlan 1
  interface port-channel 1-32
   
  spanning tree
  spanning tree mode RSTP
   
  basis of QoS
  QoS trust cos
  Enable IAS

  RTTMOACCESS02 config:

  database of VLAN
  VLAN 10,20,30,40,50
  output
  Add a voice vlan Yes-table Nortel___ 000181
  Add a voice vlan Yes-table 0001e3 Siemens_AG_phone___
  Add a voice vlan Yes-table 00036 b Cisco_phone___
  Add a voice vlan Yes-table 00096e Avaya___
  Add a voice vlan Yes-table 000fe2 H3C_Aolynk___
  Add a voice vlan Yes-table Shoretel___ 001049
  Add a voice vlan Yes-table 0060 b 9 Philips_and_NEC_AG_phone
  VLAN voice Yes-table add 00907 Polycom/Veritel_phone___
  Add a voice vlan Yes-table 00e0bb 3Com_phone___
  860 port address 0.0.0.0 iSCSI target
  port 3260 address 0.0.0.0 iSCSI target
  port 9876 address 0.0.0.0 iSCSI target
  port 20002 address 0.0.0.0 iSCSI target
  20003 port address 0.0.0.0 iSCSI target
  port 25555 address 0.0.0.0 iSCSI target
  hostname rttmoaccess01
  no console logging
  privilege 15
  !
  interface vlan 10
  Name IT
  !
  interface vlan 20
  name UserPCs
  !
  interface vlan 30
  name UserTCs
  !
  interface vlan 40
  the voice name
  !
  interface vlan 50
  Name printers
  !
  gigabitethernet1/0/1 interface
  switchport access vlan 10
  !
  tengigabitethernet1/0/1 interface
  switchport mode general
  switchport general allowed vlan add 10 tag
  switchport general allowed vlan add 20 tag
  switchport general allowed vlan add 30 tag
  switchport general allowed vlan add 40 tag
  switchport general allowed vlan add 50 tag
  !
  gigabitethernet2/0/1 interface
  switchport access vlan 10
  !
  tengigabitethernet2/0/1 interface
  switchport mode general
  switchport general allowed vlan add 10 tag
  switchport general allowed vlan add 20 tag
  switchport general allowed vlan add 30 tag
  switchport general allowed vlan add 40 tag
  switchport general allowed vlan add 50 tag
  !
  Default settings:
  Service etiquette: 76BYTS1
   
  SW version 4.1.0.8 (28 August 2012 time 11:17:36)
   
  Gigabit Ethernet ports
  =============================
  Speed 1000
  full duplex
  negotiation
  flow control
  Auto MDIX
  no back pressure
   
  interface vlan 1
  interface port-channel 1-32
   
  spanning tree
  spanning tree mode RSTP
   
  basis of QoS
  QoS trust cos
  Enable IAS

  Config RTTMOCORE

  ! Version 8.3.12.0
  ! Last modification of the configuration to Fri Jun 14 13:31:58 2013 default
  ! Startup-config updated Fri Jun 14 13:32:40 2013 default
  !
  start the primary system battery-unit 0: A:
  start a system secondary battery-unit 0: B:
  start the system stack-unit 0 default: A:
  start the primary system battery-unit 1: A:
  start a system secondary battery-unit 1: B:
  start the system default stack-unit 1: A:
  !
  redundancy full automatic synchronization
  !
  Hardware watchdog
  !
  no console logging
  !
  hostname rttmocore
  !
  disposal of battery-unit 0 S4810
  !
  stack-unit 0 battery-group 14
  !
  stack-unit 0 battery-group 15
  !
  interface TenGigabitEthernet 0/46
  no ip address
  switchport
  FlowControl rx tx off
  no downtime
  !
  interface TenGigabitEthernet 0/47
  no ip address
  switchport
  FlowControl rx tx off
  no downtime

  disposal of battery-unit 1 S4810
  !
  stack stack-unit 1-group 14
  !
  stack stack-unit 1-group 15
  !
  interface TenGigabitEthernet 1/46
  no ip address
  switchport
  FlowControl rx tx off
  no downtime
  !
  interface TenGigabitEthernet 1/47
  no ip address
  switchport
  FlowControl rx tx off
  no downtime
  !
  !
  interface Vlan 1
  !
  interface Vlan 10
  Description IT
  Name IT
  no ip address
  Tagged TenGigabitEthernet 0/46-47
  Tagged TenGigabitEthernet 1/46-47
  Shutdown
  !
  interface Vlan 20
  Description UserPCs
  name UserPCs
  no ip address
  Shutdown
  !
  interface Vlan 30
  Description UserTCs
  name UserTCs
  no ip address
  Shutdown
  !
  interface Vlan 40
  Speech description
  the voice name
  no ip address
  Shutdown
  !
  interface Vlan 50
  Printers description
  Name printers
  no ip address
  Shutdown
  !
  Lldp Protocol
  !
  0 line console
  line vty 0
  line vty 1
  line vty 2
  line vty 3
  line vty 4
  line vty 5
  line vty 6
  line vty 7
  line vty 8
  line vty 9
  !
  end

  I would say lets start with one side and obtain communication of work between the two computers on the same stack at RTTMOACCESS01. The port settings for the 1/01 and 2/01 look great both in access mode for VLAN 10. Which IP addresses and subnets you assign to computers?

  5548 to battery power battery connection 10 also appear to not be in a LAG, then we run two connections like that and they aren't in a SHIFT, we create a loop and a single connection will enter a blocking state.

  For the connections between the 5548 and force 10, I suggest to turn them into a GAP. The command should look like this.

  Console > activate

  Console # configure

  Console (config) # (config) # interface tengigabitethernet 1/0/1

  Console (config) # port - 1 automatic mode group

  output console #.

  Console (config) #.

  Do the same for Te2/0/1

  Then we set up this OFFSET to set it up, and I would try to use the trunk instead of general mode mode.

  Console (config) # interface port-channel 1

  console switchport mode trunk #.

  console # permit trunk switchport vlan add 10,20,30,40,50 tag

  The same should be done for the Force switch 10.

  Te0/46.1/46 in a SHIFT

  Te0/47.1/47 in another SHIFT

  Put in the trunk and let the VLANS on the trunk.

  Allows to study these settings and see if we can make any progress.

  Thank you

• Channel Port LACP with VMWare ESXi IP hash Message: % SW_MATM-4-MACFLAP_NOTIF: < MAC > host in the vlan 1 is flapping between port

  Hello

  Currently I have a VMWare ESXi host with 2 network including 6 cards (3 of each) ports are connected to a X 3750.  I configured LACP on the switch and the Port of vDS group road based on IP Hash (802.3ad), my looks of config as follows:-

  src-dst-ip port-channel load-balance

  Interface Port-channel15

  switchport trunk encapsulation dot1q

  switchport mode trunk

  !

  interface GigabitEthernet1/0/15

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  !

  interface GigabitEthernet1/0/16

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  !

  interface GigabitEthernet1/0/17

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  !

  interface GigabitEthernet1/0/18

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  !

  interface GigabitEthernet1/0/19

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  !

  interface GigabitEthernet1/0/20

  switchport trunk encapsulation dot1q

  switchport mode trunk

  bandwidth share SRR-queue 10 70 25 5

  form of bandwidth SRR-queue 10 0 0 0

  priority queue

  MLS qos trust dscp

  spanning tree portfast

  channel-protocol lacp

  active in mode channel-group 15

  Currently I see many MAC beat in the log of the switch.  From my understanding, I expect the MAC address out all ports, because that's what'd ESXi when you use 'route based on the hash of the IP.  I'm worried about the impact this might have on the CPU / switch.

  August 6, 09:42:05.700 TSB: % SW_MATM-4-MACFLAP_NOTIF: 0050.569e.0939 to host in the vlan 1 is flapping between port gi1/0/16 and article gi1/0/15

  August 6, 09:42:16.479 TSB: % SW_MATM-4-MACFLAP_NOTIF: 0050.569e.28e4 to host in the vlan 1 is flapping between port gi1/0/20 and 0/article gi1/17

  August 6, 09:42:18.719 TSB: % SW_MATM-4-MACFLAP_NOTIF: 0050.569e.7f6a to host in the vlan 1 is flapping between port gi1/0/19 and article gi1/0/20

  August 6, 09:42:20.766 TSB: % SW_MATM-4-MACFLAP_NOTIF: 0050.569e.0939 to host in the vlan 1 is flapping between port gi1/0/16 and article gi1/0/15

  Is it by design, if so can I disable the message?  If this isn't the case, please can you advise where I can check/change the configuration?

  Thank you

  Peter

  It is really gud who... .you mentioned your solution here.

  Can you please mark this question as answered, thatâ so it can help the other guys.

  Concerning

  Please rate if this can help.

• Communication between 2 SG300 - 28 p with an OFFSET of the VLAN

  Hello

  I have 2 SG300 - 28 p without a router used for the use of the backbone.

  The switches are configured in L2.

  I want to configure on the two switches:

  • The default VLAN Id 90
  • A VLAN with 80 Id to access databases
  • A VLAN Id 70 to access the backup server
  • An agregate with port 25, 26, 27, 28
  • The ports 1 to 8, 13 and 20 with VLAN 80 (90UP/80 t)
  • 9 to 12 ports, 21 to 24 with VLAN 70 (70UP)

  Computers that connect to the VLAN 70 won't be intended for the VLAN 70.

  I would like to use the mode of access ports in VLAN 70.

  Computers that connect to the VLAN 80 will not be intended for 80 of VLAN.

  It seems that servers on the local network VIRTUAL 80 switch 1 can communicate with servers on the 80 VLAN on switch 2.

  My problem is that the servers on the VLAN switch 70 1 access to the servers on VLAN 70 on switch 2.

  I guess it is because the 90UP of LAG 25/26/27/28 configured.

  Any idea to solve this problem?

  The OFFSET is like any other link. It is configurable. You should be able to connect to the CLI

  config t

  PO1 int

  switchport mode trunk

  switchport trunk vlan native 90

  switchport trunk allowed vlan add 70,80

  -Tom
  Please evaluate the useful messages

• Confused on what I should do to the extent of the VLAN PVID vs

  I have a complicated image it's crazy to watch, but I hope I can explain it enough:

  I have currently a Powerconnect 2716 connected two Poweredge 2950's particular race as long as ESXi Hypervisors, and their data warehouses are on a MD3000i iSCSI SAN (the main use of the switch is the iSCSI san, servers have connections of backup for the client/guest network access).

  

  Hypervisors vmnic config was hokey at best because we did not have the second gigabit switch to have enough ports to run everything and have redundancy, so I ended up using a lot of 10/100 ports on my Catalyst 3750 PoE switch for guest computers and my iSCSI on the 2716 traffic.

  I now have the second 2716 and crosses the configs on the old switch, I realized that I had taken my comments machine network inside out vlan1 and iSCSI ports using the pvid.

  Here's my dilemma, I want the network traffic between the two switches for multiple VLANs, but not others.

  My proposed solution is

  

  (4) VLANS 1, 10, 130, 139.

  (3) GAL: 1 (2-4 ports), 2 (7, 8 ports) 3 (ports 14.14)

  belonging to a VLAN will be:

  

  

  

  -VLAN1 is for managing the switch, I will have my switches addressed as 192.168.1.1 and 192.168.1.2 and I want trunk VLAN1 LAG1 through so I can handle both switches and either: plug to switch to port 1 with a laptop or use a remote VM guest with shared resources in on LAG2 VLAN

  -VLAN10 is for my vMotion, just a 10.x.x.x and me planned to redirect it on the LAG even as my machine comments traffic

  -VLAN130 is my iSCSI SAN

  -VLAN139 is my Machine/vSphere Client/visitor access

  What I fear is VLAN139 traffic with the filtering of capture off the coast and out without label on 16 port which could cross the trunk of LAG 1 (ports 2,3,4) (via VLAN1) and which causes a loop since the 2716 does not support STP.

  

  I want to master the iSCSI, management switch and vMotion across two switches Dell but I want computers invited to climb their respective uplinks of switches. I can't have curls if not all my client/server traffic will cross through a Dell for the other Dell to find the uplink of work when the cisco STP auto disable one of the ports

  Can I do this, even if by default, all ports are in VLAN1 unidentified? Or I'll have to this redesign and PVID allows to separate the ports 10-16 and put my VLAN10 on LAG2 as well as iSCSI traffic?

  Can VLAN 10 exist on PVID 2 while the trunk between the 2716 is in 1 PVID and always pass traffic between switches?

  Have I fried the brain of everyone with my images and my knowledge "just enough to be dangerous?

  Thanks in advance! :)

  PVID 1 is the default, but if you change it on an interface, page 52 ftp://ftp.dell.com/Manuals/all-products/esuprt_ser_stor_net/esuprt_powerconnect/powerconnect-2708_User%27s%20Guide_en-us.pdf , then it will use the PVID you set to no marked traffic. So if you put LAG3 PVID 139, untagged traffic goes to 139 and tagged will go to VLAN 10. If Cisco is down not signposted in 139 with a PVID of 139, then everything should work correctly with your configuration and do what you want it to do.

• VMotion traffic isolation, vlan trunking

  We have 2 full length M910 blade servers sitting in the dell blade enclosure. Installed esxi 5.0 on the two blades and joined them to the cluster.

  Each server blade full length a 8 network cards.  2 ports double aboard the card NETWORK and 2-port Ethernet mezzanine card.  All are connected to the internal cisco switch 3130 installed on the module e/s A1, A2, B1 and B2. all the internal switches are stacked together by the network team. and there is a link to internal switch (uplink) and an external switch (ports) that are on the vlan 137

  All the ports that are connected to the esxi host are configured as trunk on the switches of internal physical cisco blade by the network team. in our total case 16 ports (8 cards x 2 servers) are fixed to the internal trunk on cisco switch and there is internal cisco switch uplink and our external switch (located on vlan 137)

  On esxi5.0, we set up a big flat switch affecting all physical network cards to Vswitch 0.
  Please refer page for groups of ports configured.
  
  To isolate the vmotion traffic, we have configured tag (150) vlan different for vmotion. but vmotion does not work. Unable to ping of vmotion ips with each other.  But if I change brand VLAN to 137. vmkping works on the other and work of vmotion.

  If I change brand VLAN other than 137 to any group of ports (for example, management or virtual machine), I'm losing connection to the corresponding port group.

  
  I think that missing configure something on the blade switches internal cisco (3130). Please advise on what needs to be configured. I know that kind of why trunking is required. If you could explain the exact purpose of why the necessary circuits for esx would be great.

  What is advised to configure a virtual switch, such as a large flat switch or multiple switches
  Assigning to each switch port group. recommended configuration to enable balancing the increased load of incoming and outgoing and fail over.  detailed explanation would be really useful for non admins networks

  I will try to describe one of the possible configurations.

  First some facts/support:

  • 2 ESXi hosts
  • 4 blade switches
  • 1 external switch
  • 8 NICs in each server Blade (2 NICs for each of the switches)
  • vmnic0 and vmnic4 are connected to two different switches
  • different subnets / VLAN for vMotion (100), management (101) and VM networks (102,...)
  • all VLANS represent them different IP subnets

  Virtual network configuration:

  • 2 vSwitches: 1 for management, 1 for VM networks and vMotion
  • vSwitch0 for management and vMotion (vmnic0 + vmnic4)
    --> Management ports (VLAN 101) Group: vmnic0 (active), vmnic4 (at rest)
    -> vMotion Port Group: (VLAN 100): vmnic4 (active), vmnic0 (at rest)
  • vSwitch1: VM networks (vmnic1.. 3 + vmnic5...) 7)
    -> VM 1 (VLAN 101) port group
    -> Port VM 2 (VLAN 102) group
    -> ...

  Blade switches:

  • all the VLANS configured in the virtual network are present
  • all ports of downlink to the ESXi hosts are configured to trunk mode, all the VLANS allowed
  • at least 2 uplinks and the external switch configured as a trunk, EtherChannel (LACP)
  • ports of rising and descending liaison (on each of the switches) are a group of track link state

  External switch:

  • all the VLANS configured in the virtual network are present
  • four channels of Port/EtherChannels (LACP), one to each switch blade

  You can configure the VLANS on switches separately or by VTP. In any case, all the VLANS should be present on the switches of. If you need to route traffic between some VLANs, you must either set up a router on your network, or - in the case where the switches support and are properly authorized - configure routing ip (Inter VLAN routing).

  André

• SWITCH Cisco/Linksys SLM224G: Problem with the VLAN

  Hello!

  I'm trying to set up a VLAN in my baskets. I have some knowledge about VLANs, but I still can not configure in my path.

  My situation:

  I have PC that contains two virtual machines, which works as a router between three networks: LAN, WAN, LAN2. It's a bit complicated, but I'll try to draw:

                                                   |-------------||----------------------------|                   |           e1|-to-eth1-VM2-----WAN|VirtualMachine 1        eth0|---trunk-VLAN1&2---|g1         e2|-to-eth0-VM2-----LAN2|eth0=VLAN1 eth1=VLAN2       |                   |           e3|-to-eth0-VM2-----LAN2 etc.|                         PC |                   |   SWITCH  e4||VirtualMachine 2            |                   |           e5|-to-eth1-VM1---wire-to-LAN2|eth0=VLAN3 eth1=VLAN4   eth1|---trunk-VLAN3&4---|g2         e6|-to-eth0-VM1-----LAN1|----------------------------|                   |           e7|-to-eth0-VM1-----LAN1 etc.                                                 |-------------|
  
  gX = Gigabit portseX = 100Mbit portsVMX = Virtual machine numberwire-to = patch-cord connection between ports on the switch
  
  Schema of routing and logical visibility:
  
  LAN1---VM1-----VM2---WAN              |LAN2----------|
  

  Important note is that LAN1 and LAN2 must be separated (visible only through routers). WAN must be visible through VM2 to LAN2 and through by VM1 and VM2 to LAN1. It seems easy, but VLAN that I did on this passage seems doesn't work.

  I do it like this:

  Step 1: Management of VLANS / create a VLAN...

  Creation of VLANS 1, 2, 3, 4 (numbers meters right now - I have now this number 1 is restricted to the switch).

  Step 2: Management of VLAN / Port to VLAN...

  Setting up VLAN1 with ports g1, e5 (the two labelled or not identified?-I have not seen any difference)

  Implementation VLAN2 with ports g1, e6, e7, etc...

  Implementation VLAN3 with ports g2, e2, e3, etc...

  Setting up VLAN4 with g2, e1 ports

  Step 3: Management of VLAN / Port setting...

  Implementation of ports e1 to PVID4 (chassis type = all I guess, but with "capture filter"?)

  Setting up port e2 at PVID3

  Setting up port PVID3 e3

  etc...

  Setting up port e5 for PVID1

  Setting up port e6 at PVID2

  Setting up port e7 for PVID2

  etc...

  Thus, on this configuration and that the switch it does not work for me

  I know that the switch is to see Mac since VLAN which is carried out by PC, because when I arrive in "Admin / dynamic address" I see pimps on the correct ports, with good VLAN ID. So the problem is to transmit a VLAN for their ports, then clear frames of ID and let the packets to go (and return: clear packages, add the VLAN ID and send to their Gigabit ports).

  Show the configuration is one of the many I tried :/ but I think this one is the best.

  Or maybe I don't know VLAN as I think and this scheme is impossible? Please tell me.

  Concerning

  and waiting for any suggestions,

  READ

  Hello.

  These products are processed by the Cisco Small Business Support Community.

  * If my post answered your question, please mark it as "acceptable Solution".

  * Do not forget to give a 'congratulations '. Thank you!

• Help with the VLAN and RVS4000

  I am trying to Setup VLAN on a RVS4000 to share our Internet connection with another office but do not allow access to our network of the other network. We have a BEFSX41 connected to Internet and also connected to our other site via a virtual private network to another BEFSX41. Port 1 on the BEFSX41 connects to Port 1 on an EZXS88W switch.

  The other company has provided the RVS4000 and also provides a WRT54GS router. I want to connect 2 ports on the BEFSX41 to Port 1 on the RVS4000 and 2 ports on the RVS4000 to track 1 on the WRT54GS.

  Port 1 on the RVS4000 is member of the default VLAN1 and Port 2 will be a member of VLAN2.

  Our IP network is 192.168.20.0/24

  BEFSX41 is 192.168.20.1

  The DHCP service is disabled

  The RVS4000 has a static IP address of 192.168.20.254 and is configured as a router

  DHCP is also disabled

  The wireless network is as follows:

  IP network is 192.168.21.0/24

  The address IP of WRT54GS is 192.168.21.254 and is static and also configured as a router.

  I don't know how to actually Setup the VLAN from here and the instructions are not useful. My questions are:

  1 port 1 on the RVS4000 must be safe, with label or Untagged?

  2 If the interval routing disabled?

  3. If so, how do I route between the RVS4000 and WRIGHT so the two networks have access to the Internet, but not to other networks?

  The befsx41 should be one that is connected to the internet so that your final point so that the vpn tunnel work. The wan port on the wrt54g must be connected to the lan of the befsx41 port.

  If your server is located behind the befsx41, you should be able to port forwarding. If your server is located behind the wrt54g you may experience the problem with the redirect because you need to forward ports on both routers and according to me, there are some applications that do not work on double NAT.

  If you want to have access to the internet on both VLAN of the rvs4000, it should work as a router so its internet port must be connected to the port the befsx41 lan.