Configure SG 200-08 switch behaves as a hub

Similar Questions

• MS NLB Multicast configuration on Cisco Bladecenter switches mode

  We seek to MS NLB Multicast configuration on Cisco Bladecenter switches mode. We are adding static ARP and CAM entries for each port on the switches kernel that

  the Bladecenters are connected to, or just the port of the virtual machine arrives at

  push traffic at this time here? If we add it to a single port,

  How vmotion will work... because it seems that we have to manually

  transfer the arp from one port to the other entry.

  We add the static ARP entry to the entire Cisco switch. If you can VMotion VMs NLB to another host that is physically connected to another switch, then this switch have thus added ARP entry. We have not tested the configuration only on the specified ports. But if you do, make sure that you include all the ports connected to the physical switch (if for DS you have four natachasery configured in a vSwitch...).

  Here's a guide to how we have configured it several times in our society.

  http://www.VI-tips.com/2009/04/NLB-in-VMware.html

• Can I configure NISE with a switch of party - if the switch is not installed?

  I've never used NOR Switch before Executive - we hope to use it on a new project.

  We do not have equipment at the moment - we will use a Pickering 40-540-021 '132 x 4' switch.

  I would like to configure NI Switch Executive before Pickering delivered cards, is it possible? I get an error when I create the NI Switch Executive virtual device. Seems that MAX is trying to communicate with the switch card before allowing me to configure routes/exclusions/groups etc..

  Here's what I've done so far:

  -Install the drivers of Pickering.

  -To the MAX (v5) I have setup a session driver IVI and logical name.

  When I try to create a new NI Switch Executive peripheral virtual, I add the logical name of the switch, click [next] and get the NISE error...

  "An error occurred so they were trying to access the devices PROJECTSWITCH. The primary error: unknown status code (Hex 0xBFFA400C).

  I see that a virtual device is created with no logical switch assigned. I get the error even if I try and add a logical switch manually to the virtual device NISE.

  Is it because the switch Board is not available for the system? Can I configure the routing/groups/exclusions without the device being mounted physically switch?

  Thank you

  Alan

  Alan.

  
  Seems that MAX is trying to communicate with the switch card before allowing me to configure routes/exclusions/groups etc..

  This should be the expected behavior. NEITHER Switch Executive tries to communicate with the instrument before allowing you to configure routes to ensure that there is no problem that would affect the operation of the Switch Executive. In your case the pilot trying to communicate with a non-existent device.

  I would like to configure NI Switch Executive before Pickering delivered cards, is it possible? Can I configure the routing/groups/exclusions without the device being mounted physically switch?

  It is possible that all compatible IVI devices should have the ability to simulate.

  It seems that you have configured your session of IVI driver incorrectly for a simulated device. I try and make sure that in the session driver, under the 'Général' tab, select the drop down menu to "Simulate with" and select 'Specific driver' and then click 'Save the IVI Configuration'. This will return the Pickering driver selected in the 'software' tab and simulate a device. This should allow you to create a virtual device NI Switch Executive and develop and test the code on the simulated instruments.

  I would like to know if you have any other questions.

• Aggregation of links ESXi requires the configuration of the physical switch?

  Hello

  I have two physical servers that I'll put up with ESXi. Each server has eight physical network cards. My plan is on each server to use:
  -2 management - connected to vSwitch0
  -2 for VMotion - connected to vSwitch1
  -2 for iSCSI - connected to vSwitch2 (I'll use a SAN)
  -2 to access VM network - connected to vSwitch3

  For each pair, a cable should be connected to switch1 and the second would be plugged into switch2.

  The switches are HP A5120 which are stacked into a big switch with RFID. for example I have a 'big' switch which, if one of the two physical switches dies or is turned off, would cause the 'great' switch to lose half of its ports. In this way, all four networks are expected to continue to operate even if a switch "dies."

  All the information I found online said that ESXi can have two physical cards attached to a unique vSwitch and can then do things smart for redundancy (in which case a physical NETWORK card dies) and load balanacing.

  However, while all the guides tell me how to configure it on ESXi, I'm still not sure if I should combine the two cables on the physical switches.

  So, my questions are:

  (1) in order to get the NIC or balancing working in ESXi, redundancy do I have to combine two physical ports that will connect connect two physical ports that connect to the vSwitch?

  (2) with the consolidation of NETWORK cards, I see how to have an active adapter for the management network, and an auxiliary card works fine, but for the iSCSI network, I wouldn't have only two active adapters for double the bandwidth?

  Any ideas would be much appreciated.

  Thank you.

  (1) in order to get the NIC or balancing working in ESXi, redundancy do I have to combine two physical ports that will connect connect two physical ports that connect to the vSwitch?

  No, there is no need to configure etherchannel/LACP but this will depend on the type of load balancing, you click on the ESXi host - if you use by default, you don't need to configure Etehrchannel/LACP since traffic for each virtual network interface will be only com ove a single physical port, but you will always have the reiciliency to the case where if one of the physical NIC fails traffic then released the remaining port

  If you select the hash of the IP load balancing, you must then implement Etherchannel/LACP on your physical switch since traffice can come form any physical port in the team.

  (2) with the consolidation of NETWORK cards, I see how to have an active adapter for the management network, and an auxiliary card works fine, but for the iSCSI network, I wouldn't have only two active adapters for double the bandwidth?

  Onece well once again it will depend on the Load Balancing method, you select, but you will never be able to create links physical ports to get all of the 2 GB =

  I also moved it to a more appropriate forum-

• -> Dropbox configuration backup not work - switching market automatically switches back to Off

  My system is 102 ReadyNAS with firmware 6.4.2.

  I would use the backup--> feature of Dropbox, but when I click on the switch to change from Off to on, it stays on for maybe a second, and then rebascule off automatically. Also the button never Authroize becomes available.

  If someone has encountered this problem previously have any recommendation on how to solve this problem? I have restarted the unit several times and still no luck.

  Thank you

  Make sure the NAS server has a good internet connection. Check the default gateway and the DNS server, add 8.8.8.8 (google DNS) DNS server for the test settings

• Configure access ssh_key based switch MXL. Not "based on the host."

  I have read the documentation and cannot get to a cohesive whole procedure in order to get the simple key-based authentication to work.

  The docs separate this task in a wide variety of measures in order to activate authentication "host-based", but I don't want to.  I use two laptops and 2 different offices in various locations.  "Host-based" is not going to work for me.  I need an authentication of purely "function key".  You need an example of what involved specific steps and the order to execute them.  I find that this process is pretty simple on the HP based including the new Arubas switches.  But this MXL documentation is difficult to decipher.

  It seems as it is a one-at-a-time operation, but it is more advanced and allows you to better separate, and so I'm happy with it so far.

  1. create the user with administrator privileges
  SN - MXL (conf) "JUtilisateur" somepass privilège 15 password #username

  2 enable authentication rsa
  SN - MXL (conf) ssh rsa authentication #ip activate

  3. copy your public key in the MXL (pull)
  SN - MXL #copy scp: flash:
  Address or name of the host remote []: 172.16.11.10
  Port number of the server [22]:
  Source file name []:.ssh/juser_rsa.pub
  User name to host remote login: "JUtilisateur"
  Password to the remote to connect host:
  The destination [juser_rsa.pub] file name:
  !!
  403 bytes copied successfully

  4. now log in as user, and run:
  SN - MXL #ip ssh juser_rsa.pub my authorized key of rsa authentication
  RSA keys added to the list of authorized Keys user.
  Delete the juser_rsa.pub file: (yes/no)? Yes

  5. I had to create the file ~.ssh/config with the following statement:

  host mxl
  Host name 172.16.11.1
  The user juser
  IdentityFile ~/.ssh/juser_rsa

  This means that the PRIVATE key is referenced.  Note: Make sure that your config file is has 644 permissions.

  6 test

  $ ssh mxl

  The option of SupportAssist EULA acceptance has not been selected. SupportAssist
  can be activated once the EULA of SupportAssist has been accepted. Use of the:
  command "Activate support-assist" to accept the EULA and activate SupportAssist.

  MON-MXL #.

  And I am.  Either way, I want to get rid of that little nag, as this MXL stack is not in a country supported by DELL.  Anyone know how to remove the horse?

• Configuration of the L3 Switch to send the traffic to Palo Alto

  

  Please forgive my ignorance when it comes to Palo Alto. This is the first time that I do business with them. We need to ensure one VLAN located behind the Palo Alto. I am including a diagram to show a simulation of what we seek to do. We have by default VLAN1 which is our default data VLAN. We have 19 VLAN is VLAN we want it secure. The VLAN1 SVI IP is 10.1.1.1 and VLAN19 SVI IP is 10.1.2.1. On the Palo Alto, we have an IP interface was like 10.1.1.2 for default data VLAN and 10.1.2.2 for the VLAN secure. There are also a pair of HA with IPS 10.1.1.3 and 10.1.2.3 respectively. We have EIGRP that announces the network default VLAN1. Here's what we want to do. Anything from the 10.1.1.x network, go to the 10.1.2.x network, must pass through the Palo Alto. Whatever either from the 10.1.2.x network, must go through the Palo Alto as well. Nothing to any other network 10.1.1.x, takes the route by default (and), and anything from 10.1.2.x to anything else on 10.1.2.x should stay local to the LAN (not pass through Palo Alto. Need just for the MAC address arp). My question is, how do I tell my L3 switch to send all traffic created in the 10.1.2.x, through the Palestinian Authority? I can't do an IP route because from the local network VIRTUAL lives on these L3 switches and is a directly connected route. Really, I can't do the ACB on the switch, because that is really meant to routers. I can put a long match, for everything on the 10.1.2.x network (i.e. the route ip 10.1.2.7 255.255.255.255 10.1.1.2), but for some reason when do whatsoever of 10.1.2.x another thing goes on 10.1.2.x through the palo alto so. Anyone have any suggestions on what would be the best practice, from a network perspective, on how to do this? Thanks for any help!

  Looks like you want all traffic to and from the secure virtual local network to pass through the firewall of your description?

  I'm not familiar with Palo Alto firewall is so I don't know how they work in HA, IE. with other devices do you want to simply talk to a VIP which is responsible for two firewalls?

  In your example the two firewalls have an IP address per vlan, but always just use you one IP addresses for the end-end connectivity. I'll assume that you do, you may need to change, but when I say that I mean the one that reminds you of the devices for routing etc..

  So for all the traffic to and from the network 10.1.2.0/24 to go through the firewall, you must-

  (1) remove the battery switch the IVR for vlan 19. You need the firewall to be routing vlan not secure the 3750 s. You leave vlan 19 in the database for vlan.

  (2) point them vlan 19 customers as default gateway

  (3) addition of a route on the stack of 3750 for the network 10.1.2.0/24-

  IP route 10.1.2.0 255.255.255.0

  (4) if the 10.1.2.0/24 network needs to talk to other that 10.1.1.0/24 remote subnets, then for each of these networks the firewall should be a route. The syntax will not be IOS, but this should give you an idea-

  IP 10.1.1.1 road

  etc... for each remote network

  That means foregoing is all the traffic going and coming from 10.1.2.x customers to other subnets must go through the firewall. The customer traffic in the vlan secured to other clients in the vlan safe doesn't have to go the firewalls.

  Jon

• Policy Based Routing Configurations 6500 and 4948 Switches

  Hello!

  I'm looking for good examples of the strategy for the 6509 and 4948-based routing Configuration.

  I have installation of base ACB, but can not find good IPSLA configurations to pair with them.

  The 4948 has IPSLA, but doesn't seem to have orders to attach it to the ACB roadmap.

  I'm not find effective IPSLA configurations for the 6500 as well.

  My hope is that someone has config IPSLA I can use, or direct me to an example of configuration is complete.

  This is for the redirection of a WAN accelerator to monitor.

  What I have so far for the 4948:

  interface GigabitEthernet1/11
  Description to_dis_pri:g2/0/11
  No switchport
  IP 11.11.11.10 255.255.255.252
  political ownership intellectual-card route Silverpeak
  Speed 1000
  full duplex

  SilverpeakACL extended IP access list
  IP enable any 12.12.12.0 0.0.0.255

  ALS IP 99
  ICMP echo - 14.14.14.14
  Timeout 2000
  frequency 10
  Annex IP SLA 99 life never start-time now

  Silverpeak allowed 10 route map
  corresponds to the IP SilverpeakACL
  IP 14.14.14.14 jump according to the value

  I don't see how this will stop Policy Based Routing in the event where the WAN Accelerator dies.

  If you know where I can get the config, or give it here, I would be very happy!

   Hi Ganesh, It did take that command, and this is the output:: #sho track 99 Track 99 IP SLA 99 reachability Reachability is Up 1 change, last change 00:00:16 Latest operation return code: OK Latest RTT (millisecs) 1 Will this tie it all together? Also, will this be the same config for the 6509?

  Hello

  I think that you apply IP SLA on edge device where you want automatic failover, if she applies then the 6509.

  Once this output is ok then apply the command track with map of the route according to the first post.

  It could be that useful...

  -GI

  Rate if this can help...

• change the virtual switch to the virtual hub

  Hallo,

  all the networkadapters are virtual switch. How can I change to a hub? I'd like to sniff my networktraffic with a guestsystem, but that only works with a hub. Or can I change some settings to do this with esxi?

  version: ESX Server 3i, 3.5.0 110271

  MfG

  Mario

  You can set it on a vSwitch or Portgropup

  Click Edit, switch or PG-> Security-> Promiscous Mode-> accept

  Take a look at the Config Guide http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_3_server_config.pdf

  If you also want traffic on your pSwitch, you create a mirror on your pSwitch port.

• configuration of VLAN and routing problem 6224 switch

  I, m having a problem accessing internet to vlan 10. I can ping everything of all the VLANS. My internet router/firewall is on ethernet 1/g11 and has an ip address of 192.168.5.254. I have no problem accessing internet to vlan 20. I add a static route to my router/firewall. What Miss me? This is my first configure a layer 3 switch.

  Configure
  database of VLAN
  VLAN 10.20
  output
  battery
  1 1 member
  output
  IP 10.10.10.1 255.255.255.0
  default IP gateway - 10.10.10.254
  IP routing
  IP route 0.0.0.0 0.0.0.0 192.168.5.254
  interface vlan 10
  Routing
  IP 192.168.100.1 address 255.255.255.0
  output
  interface vlan 20
  Routing

  192.168.5.1 IP address 255.255.255.0
  output

  !
  interface ethernet 1/g1
  switchport mode general
  pvid switchport General 10
  No switchport acceptable-framework-type general tag only
  VLAN allowed switchport General add 10
  output
  !
  interface ethernet 1/g2
  switchport mode general
  pvid switchport General 10
  No switchport acceptable-framework-type general tag only
  VLAN allowed switchport General add 10
  output
  !
  interface ethernet 1/g11
  switchport mode general
  switchport General pvid 20

  No switchport acceptable-framework-type general tag only
  VLAN allowed switchport General add 20
  output
  !
  interface ethernet 1/g12
  switchport mode general
  switchport General pvid 20
  No switchport acceptable-framework-type general tag only
  VLAN allowed switchport General add 20
  output
  !
  interface ethernet 1/g13
  switchport mode general
  switchport General pvid 20
  No switchport acceptable-framework-type general tag only
  VLAN allowed switchport General add 20
  output
  output

  Route ip console #show

  The traffic code: R - RIP derived, O - OSPF derived, C - connected, S - static
  B - BGP derived, IA - OSPF Inter zone
  E1 - OSPF external Type 1, E2 - OSPF external Type 2
  N1 - OSPF NSSA external Type 1, N2 - OSPF NSSA external Type 2

  S 0.0.0.0/0 [1/0] via 192.168.5.254, vlan 20
  C 192.168.5.0/24 [0/0], directly connected, vlan 20
  192.168.100.0/24 C [0/0], directly connected, vlan 10

  Console #.

  
  

• 200 series Smart Switch does not, DHCP blocked

  I have a network of SMEs small and simple.  There are 2 switches: a switch 8 ports connected to my main Windows Server (which is the DHCP provider for the network) and a switch of 24 ports that is plugged into the switch 8 ports.

  I replaced these switches (Dell unmanaged switches) with intelligent switches in the Cisco 200 series (models 8 or 26-port).  When I plug the 26-port switch into switch 8 ports, it is impossible to obtain the DHCP in Windows server address.  Also, any device plugged into the 26-port switch cannot communicate with another, and all the lights of the port ethernet flash simultaneously at the same frequency - quite a light show!

  If I plug the Server Windows DIRECTLY into the 26-port switch, it receives a DHCP address.

  I tried a 2nd swtich 26-port Cisco and it does the same thing, so I guess this isn't a hardware problem.

  What is the solution to this problem?

  Louis,

  
  

  Try this, go to the first 200 series switch that is connected to the server and go to the tab covering tree.

  
  

  Under the properties of spanning tree tab, set the priority of bridge to 0.  This puts the root of the tree cover.

  
  

  Try this and see if the second switch traffic and that it receives the ip address.

• vNetwork Standard Configuration of switch

  Hello

  We have 3 guests ESXi 5.0.

  I configured the network as below that we have only 4 NICs per host;

  All the IPS below are in a VLAN. And what a vlan is configured on a physical switch.

  ESXi 5.0

  vSwitch0

  The VM network

  Networking - same vlan ip

  VMkernel_vMotion - same vlan ip

  2 NICs (active/active)

  vSwitch1

  VMkernal_iSCSI - same ip vlan (our IP storage is a different subnet, but it can communicate with the ip subnet of vlan.) This is when the creation of this port, there is no option to 'check' designed to 'storage', then how iSCSI traffic will pass through this port ONLY?

  2 NICs (active/active)

  I want to know if this configuration is ok?

  OR

  Suggest me a better option than this.

  Thank you

  Mihir

  Easy answer. You don't assign it a gateway to VMkernel iSCSI ports. If you use IP addresses in the same subnet as the storage system, you don't need a gateway. VMware does not support iSCSI traffic routed anyway.

  Now that you have found a VLAN / subnet dedicated to iSCSI traffic, I suggest you research a little more, maybe you are lucky enough to find a dedicated VLAN / subnet for vMotion too.

  André

• Best configuration of switch for 4 natachasery - 5 ESXi

  So, I need to tell my boys to network how I want the configuration of ports (Cisco switches) for 4 natachasery connection to my HP DL 360. I need the vSwitch VM access to 3 different VLAN. I'm NOT going to use vMotion for this.

  I guess, I see 2 possibilities and does not entirely undesrstand pros / cons...

  First of all, I thought I would split the enet to 2 separate switches cables, but I was told that if I chose that this channel of ports 1 route would be active and 2nd would be Eve. Basically can not paste all 4 cards and divide them. This could reduce the bandwidth, but give me a redundancy using 2 physical switches.

  Or I can have all 4 enet cables go to the same switch (etherchannel), but if this switch would die I'm dead in the water, AND I think that EtherChannel mode WE (my network guy preferred LACP) should stay and LACP cannot be used. According... http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1004048 I think I should also use 'Hash IP' if EtherChannel is used.

  So what is the advantage or disadvantages of each channel? Thank you!

  This article describes the aggregation of ESX/ESXi links:

  • ESX/ESXi host only supports grouping NETWORK adapters on a single physical switch or stacked switches.
  • Aggregation of links is never supported on disparate networks switches.
  • The switch must be set to perform 802.3ad aggregation of links in static mode WE and the virtual switch must have its defined route based on the IP hashload balancing method.  Ensure that participants of the network adapters are connected to the ports configured on the same physical switch.
  • Allowing each route based on the IP hash without 802.3ad aggregation or vice versa disrupts networking, so you must make the changes to the virtual switch first. In this way, the service console is not available, but the physical switch management interface is, so you can activate the aggregation on the affected ports to restore network.
  • For more information on ESX networking concepts, see the VMware Virtual Networking Concepts.
  • For more information on configuring a VLAN for NIC teaming, see Configuration of VLAN Virtual Switch, switch physical and virtual machines (1003806).
  • To set up the consolidation of NETWORK cards on ESX and a physical switch, see example configuration of EtherChannel / link aggregation with ESX/ESXi and Cisco/HP switches (1004048).
  • The only option for switch vSwitch or vDistributed that can be used with balancing EtherChannel is HASH IP.
  • Do not use tag with IP HASH load balancing.
  • Do not uplinks configure standby or not well obliterated with IP HASH load balancing.
  • VMware takes support only a single Etherchannel by vSwitch or distributed vNetwork (vDS).

  heybuzzzz wrote:

  In my case with no vMotion and just management and 3 VLAN all about 1 vSwitch I should put them all to active?

  Yes, they should all be active, there is really no need passive adapters (that I'm aware of your configuration).

  On your physical switches, you don't need to do anything more than what allows a VLAN correct, i.e.: should all etherchannel or a similar montage. Side vSwitch, you must use the default 'Port ID' nic teaming strategy.

• VMware vNetwork Distributed Switch Configuration

  Hello

  Please suggest... As I intend to configure VMware vNetwork Distributed Switch, I have question if my vCenter comes down to will my vm to communicate with the external network or not?

  Thank you

  Hello

  very good question, yes even your virtual machines can communicate with external networks because ESX/ESXi contain hidden vSwitch,

  For more information the article below

  http://www.google.co.in/#sclient=psy&hl=en&source=hp&q=How+VMware+vNetwork+Distributed+Switch+work+if+vCenter+fail+site%3A+blog.srinfotec.com&pbx=1&oq=How+VMware+vNetwork+Distributed+Switch+work+if+vCenter+fail+site:+blog.srinfotec.com&aq=f&aqi=&aql=&gs_sm=s&gs_upl=1070l6889l2l9388l13l13l0l0l0l2l440l2757l0.8.4.0.1l13l0&bav=on.2,or.r_gc.r_pw.&fp=b2a44f43975a6a66&biw=1366&bih=647

  or

  http://blog.srinfotec.com/?p=326

  concerning

  Kardous

• How to set up the virtual switch vmnet0 so in fact, it behaves like a switch.

  Hello

  I have a problem:

  My configuration is:

  host of CentOS 5.3 using vmware server 1.06

  3 clients (all centos 5.3 with vmware tools) installed

  web01

  DB01

  backup01

  The three guests have public ip and use the bridged (vmnet0) network

  The backup01 backups web01 and db01 every night.

  My supplier can see that traffic on its poort switch that connects the host to the internet, and he wants to charge me for it.

  The three guests (and host) are all on the same subnet. It is the local subnet traffic that does not use a gateway.

  It seems the traffic between hosts is diffuse on my physical eth0 on the host. When I have some files between guests, it also appears on the page from my supplier of PCs followed AY. (Just likecommunication between 2 physical host computers are on the local network when you use a hub instead of a switch)

  I thought it was probably the only way to vmware would work when using network bridges. Because the host doesn't know anyting on the clients ip numbers.

  But when googleling abot this I found several docuemtents (for vmware server 2) telling me that vmnet0 is actually a sort of virtual switch.

  If this is true this virtualswitch should know other mac adressess clients (arp who a..) and she must stop the internal traffic to leave the material.

  Is not what is happinging. It looks more like a virtualhub instead of virtual switch.

  So I was wondering if there are ways to configure the vmnet0 somehow. I was hot, but I can't find anything about it.

  I don't want to change the bridged mode or coz internal use of the intellectual property of the plan is to spit the separate web01 and db01 to vmware guests in the furture.

  Does anyone have any suggestions?

  My idea was to put an additional physical switch between me and my switch to suppliers, but that seems to be a ridiculous solution.

  Any help is welcome.

  Concerning

  Hans Groot

  VMserver don't use virtual switches: it uses virtual hubs. They are mislabeled - probably because "virtual switch" sounds more sexy than "virtual hub".

  You can't change their behavior to be more like a switch

  ___________________________________

  VMX-settings- VMware-liveCD - VM-infirmary