Connecting two cisco ESW 500 series switches.

Hi Experts,
I have a basic knowledge of network and need some help.
I have two cisco ESW 500 series switches and i want to connect them together.
Q1 # Which type of cable i should use to connect these two switches CrossOver or fiber...What is the advantage of using Fiber over CrossOver. ?
Q2 # What are the marked ports in the image used for...???

tech spec,
Traditionally you would use crossover to connect switches. Most modern network devices have Auto-MDIX which allows the device to connect using either crossover or straight through.
The ports on the right can be used for uplink or as regular network ports. On the 10/100 versions the ports on the right are usually Gigabit, thus making them more suitable for uplink to another switch, etc.
Please mark this thread as answered or reply if you have any additional questions.
- Marty

Similar Messages

  • How to erase all configuration in Cisco ESW 500 Series Switches

    Hi anybody,
    Anyone show me how to erase or remove  configuration file from ESW 500 Series Switches?
    Thanks
    Thuc

    Hi Thuc,
    The restart / reset function will allow for local or remote reset of the  the unit to Factory defaults, see screen capture below. ;
    Alternatively, the Switch can be reset by inserting a paper clip into the RESET opening on the friont of the switch.
    Pressing the manual reset for 0 to 10 seconds only  reboots the switch.
    Pressing the manual reset for longer than 10 seconds results in the switch being reset to factory defaults.
    does this answer your question, not exactly sure it does ?
    regards Dave

  • I want your valuabale opininon on ESW 500 series switches

    In my offiec i want to connect 8 accesspoints and 8 smart boad and 8 pcs to a switch the access points are cisco 1240g series and controlled by a wlan controller.
    this switch should be connected to a core switch 4507 using fiber.
    can i use these esw switches for this

    Not sure what you mean by 8 smart boad - can you be more clear on that?
    Couple of comments:
    - Please note that we recommend the ESW in a Cisco Small Business type deployment with products such as UC500, SR500, AP500. Also, management is via a configuration utility GUI or CCA, not CLI as you would use for the Cisco Catalyst switches. Check this discussion which has a PDF that goes over positioning of the switches- https://www.myciscocommunity.com/message/8385#8385
    - Please check the POE requirements you need against the ESW switches - check the question on at Q & A
    Q. How many devices can the Cisco ESW 500 Series PoE switches power?

  • Cisco 500 series switches

    Dear support,
    Can Cisco 500 series switches deliver 24V on the access port for POE operation?
    Best Regards

    I belive the 802..2F and 802.2at poe standard is strictly 48v.  I haven't found anything to the contrary.  There are inline convertes 48v-24v or something like this that can be used with a non poe switch: http://www.digital-loggers.com/poe24.html but that means all conected device would be off the same access port / vlan. 

  • Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

    Welcome to the Cisco® Support Community Ask the Expert conversation.  This is an opportunity to learn and ask questions about Cisco® NX-OS.
    The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
    vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
    This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
    Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
    Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
    Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response. 
    Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Gustavo
    Please see my responses to your questions:
    Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
    Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
    Now for Data Plane we have two types of traffic – Unicast and Multicast.
    The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
    Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
    For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
    The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
    Similarity: For both products, loop avoidance is possible due to VSL bit
    The VSL bit is set in the DBUS header internal to the Nexus.
    It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
    This mechanism is used for loop prevention within the chassis.
    The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
    Differences:  In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
    It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
    For more details please see below presentation:
    https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
    DCI Scenario:  If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
    But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
    Let us know if you have further questions.
    Thanks,
    Vishal

  • I need online Configuration Guide for Catalyst Express 500 Series Switches

    Hi Mates,
    Please is there an online help page for 500 series catalyst
    I have this one for IOS 12.2(25)FY http://www.cisco.com/en/US/products/ps6545/products_configuration_example09186a00806da6c9.shtml
    but I need more detailes like IOS 12.3(7)JA for Aironet 1300 http://www.cisco.com/en/US/products/ps5861/products_configuration_guide_book09186a00804ebd50.html
    Regards
    Saher

    I'm afraid there is not such document for IOS 12.2(25)FY since the Catalyst Express 500 Series switches are manageable through the GUI Device Manager or Cisco Network Assistant.
    I have also found key features and standards supported for that release:
    http://www.cisco.com/en/US/products/sw/iosswrel/ps5012/prod_bulletin0900aecd8033b8b3.html
    Hope this helps

  • Cisco CSS 11150 Series switch and DNS Sticky

    Hi,
    I have currently have two internet independent facing CSS11154 switches with two web server farm environment across both of them.
    I have a single URL that round robins between my internet facing links for these server farms.
    The application is based on ssl connectivity to a web farm, because of the application and need to maintain session transactions, I have needed to use “advanced-balance stick-srcip”.
    When using one leg (internet link) it works fine, no problem and visa versa.
    However, when I turn both of them on my application fails.
    Would I need to incorporate DNS Sticky to resolve my issue ?
    This is one of the configs from one of the CSS Switches, the other has a similar config different servers.
    !*************************** GLOBAL ***************************
    acl enable
    date european-date
    dns-server
    app
    app session 10.1.1.1 14 authChallenge ebe encryptMd5hash
    !************************** SERVICE **************************
    service Server01
    ip address 10.140.80.45
    port 443
    protocol tcp
    active
    service Server02
    port 443
    protocol tcp
    ip address 10.140.80.47
    active
    service Server03
    port 443
    protocol tcp
    ip address 10.140.80.53
    active
    service Server04
    ip address 10.140.80.54
    port 443
    protocol tcp
    active
    !*************************** OWNER ***************************
    owner HOME
    dns both
    content www-home.com
    vip address 192.168.0.1
    add dns www.home.com
    add service Server01
    add service Server02
    add service Server03
    add service Server04
    advanced-balance sticky-srcip
    active
    Many Thanks !
    Any view would be most helpful

    looks like you will need dns sticky indeed.
    To be 100% sure you should capture a sniffer trace of a failure.
    But most probably this is a dns sticky problem.
    Follow this link for sample configuration of dns sticky.
    http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_configuration_guide_chapter09186a0080176f6f.html
    Regards,
    Gilles.

  • Can we monitor Catalyst 500 series Switches?

    Dear All,
    I am having Catalyst 500 switches in my Networking Environment. I want to monitor those switches by using snmp. Please advise whether this can be done and what are the kinds of traps we can enable? Also please suggest some links or pdf's of this Cat500 series switches. 
    Also these switches are having the below iOS.
    12.2(25)FY
    12.2(25)SEG6
    Thanks,
    Ashis

    Hi Ashis,
    Please check this link to get more info about SNMP configuration.
    Krishna

  • Connecting two Cisco 2950 switches to a 2600 router

    Hello,
    I'm trying to have two LANs connected to 2950 switch each, connect to a 2600 router and have the two LANs communicate with each other...i can't seem to get it working...any help...thanks
    LAN 1 192.168.10.1/20
    LAN 2 192.168.12.1/21
    Thanks again

    Alright, these are only basic configs here:
    Router
    hostname Router
    int fastethernet0/0
    description Network 1
    ipaddress 192.168.10.65 255.255.255.192
    int fastethernet0/1
    description Network 2
    ip address 192.168.10.129 255.255.255.192
    end
    Switch 1 (the one connecting to f0/0)
    hostname SwitchNet1
    int f0/1
    description Host 1 Net 1
    no ip address
    no shut
    int f0/2
    description Host 2 Net 1
    no ip address
    no shut
    int f0/3
    description Host 3 Net 1
    no ip address
    no shut
    int f0/4
    description Host 4 Net 1
    no ip address
    no shut
    int range f0/5 - 23
    no description
    no ip address
    shut
    int f0/24
    description UPLINK to Router
    no ip address
    no shut
    int vlan 1
    ip address 192.168.10.66 255.255.255.192
    no shut
    default-gateway 192.168.10.1
    end
    Switch 2 (the one connecting to f0/1)
    hostname SwitchNet2
    int f0/1
    description Host 1 Net 2
    no ip address
    no shut
    int f0/2
    description Host 2 Net 2
    no ip address
    no shut
    int f0/3
    description Host 3 Net 2
    no ip address
    no shut
    int f0/4
    description Host 4 Net 2
    no ip address
    no shut
    int range f0/5 - 23
    no description
    no ip address
    shut
    int f0/24
    description UPLINK to Router
    no ip address
    no shut
    int vlan 1
    ip address 192.168.10.130 255.255.255.192
    no shut
    default-gateway 192.168.10.129
    end
    This config assumes only ports f0/1 - f0/4 will be used on each switch. If that is not the case, you will need to modify the interface configs accordingly. You may want to use descriptions more suited than to your network on the switchports. Also, this config assumes the router is connected to port f0/24 on each switch as well.
    The default-gateway for the hosts and the switches is going to be the router IP address for the subnet they are attached to. The hosts/switches attached to f0/0 use 192.168.10.65 as their gateway. The hosts/switches attached to f0/1 use 192.168.10.129 as their gateway.
    You do not need to configure a port on the switch as the default-gateway. The default-gateway is an IP address the host/switch uses to direct all traffic from itself out past the router. In fact, if you don't need the switch to talk to devices on the other subnet, you don't even need to configure a default-gateway on the switches (but I would anyway).

  • 10.0.0.0 range not allowed on 500 series switch

    I effectively now have a paper weight. I have 10,000 devices with IP addresses in the 10 range. Yet my switch does not allow an IP in this range. Does anyone know of a way to fix this design flaw?

    By "not supporting it," do you mean that you can't put an administrative address on it for management, or that it doesn't pass traffic that carries a "10. " address?
    Because if you're saying that it won't pass the traffic, then I'd say you have a dead switch, because L2 switches don't know (or care) what the L3 address is.
    If you're saying that you can't use "10. " addresses for management ... I'd also have to say that it's unlikely, and you have a config problem or a dead switch.
    The express 500s are L2 switches, so there's no such thing as layer 3 (IP addressing) from the switch's point of view.
    Try posting your config.
    Good Luck
    Scott

  • Como configurar SPA941 no Cisco Unified 500 Series - UC500

                     Comprei Um UC 500 mas não consigo configurar aparelhos do Modelo SPA 941, no modelo SPA502G configura corretamete, verifiquei que tem como fazer upload de outros modelos de telefone mas não encontro em lugar algum, alquem tem ideia onde posso encontrar, configurar esses aparelhos 941 ?

    You have to look for "third party SIP phone" examples, as there is no direct support for SPA 9xx in UC500.

  • Cisco ISA 500 Series - Intervlan routing via 801.2q (Router on a stick)

    Hello to everyone,
    I am considering the ISA 550 for a customer who has multiple VLANs on his network.  In order to avoid purchase a layer3 switch, I was thinking that we could perhaps create a 802.1q trunk link from a switch to the ISA500 and perform Inter-VLAN routing through that. In addition, we would use access lists to prevent communications between specific VLANs.
    My question is if this setup model can be done on the ISA 550.  I haven't used it before, so I am not sure if it can support this setup.
    Any information or help is much appreciated.
    Many thanks,
    Chris.

    Chris, ISA550 can support the configuration you described.

  • Cisco 2950 MT-RJ ports - Connect two switches?

    Hi Everyone,
    I'm wondering if I can connect two cisco 2950s together via the two MT-RJ ports they have?
    Basically, I'd like the fibre ports to be the trunk between the two switches if possible
    I have two of these: 
    Thanks!

    Hi,
    Yes, that is possible. As long as your fiber patch cable is good there should be no issues.
    HTH

  • Catalyst Express 500 series connection problems

    Hello! our company is currently using two 500 series switch connected to eachother using the g1/1000mbits port, a cisco router is also plugged in to one of the switches for broadband internet access. After deployment the following problems came up, we are unable to use our wireless access point even when the port is set up as being "access point" using the smartports feature, we simply cant ping the access point no matter what port type we set on the switch and we keep having the error message on the router that it has denied connection from that device, my feeling is that for some reason i'm not aware of the router is blocking certain devices to transfer data no matter what type of port we define on the smartports feature. I cant find anyway or option on the router software to disable this blocking or filtering of the data in order to connect any devices i want normally without any restrictions. for some reason the switch is not accepting connections from the access point...
    Any help would be much appreciated.
    Fernando - London - UK

    Hi, well, i did disabled STP but it didnt help, i'm going to post the network topology more exactely and the settings being used so its easier to get any help as i think i missed some points about our network :) ....so here it goes :
    1. All the devices and client computers are using fixed ip addresses on the range 192.168.254.x
    2. Topology :
    Switch number 1 connected devices:
    17 client computers connected
    1 printer
    1 cisco router (with dhcp disabled and using fixed ip too)
    1 Netgear AP using set with DHCP
    Switch number 2 connected devices:
    10 client computer connected
    Switch 1 and 2 are connected using the G1/1000mbits uplink port
    Settings being used on BOTH switches (they are both catalyst 500,same software version) :
    - default vlan1 is set and enabled
    - STP enabled
    - IGMP snooping enabled
    - all ports are enabled and set to auto mode for speed and duplex
    - port Gi1 that is used to connect both switches is set as "Switch" type with smartports.
    - gateway (cisco router) ip address set
    - security set to "low"
    - STP settings on switch 1:
    currents roots: VLAN1 , priority:32768 , root port: fa24 (where the router is connected), route path:38
    - STP settings on switch 2:
    currents roots: VLAN1 , priority:32768 , root port: Gi1 (uplink to switch 1), route path:42
    switch 1 specific settings:
    - the port where the AP is connected is set using smartports as "Access Point" and the port where the printer is connected is set as "Printer" also using smartports on the switch device manager software.
    - the port where the cisco router is connected is set as "router" with smartports
    Facts:
    - I am able to ping all the devices on the network from any computers connected to both switches.
    - I am able to ping the printer from any computer connected to both switches as well.
    - When AP is connected directly to the cisco router wireless clients have access to internet with no problems
    - all wired client computers on both switches connect to the internet using the router without problems.
    Issues:
    - Cannot ping the AP from any client computer on the network
    - When printing from Switch 1 clients everything goes well, but when i print from clients on Switch 2 i am unable to print as its unable to connect to the printer, however i can ping the printer on the command-line !
    - When i try to plug in the network cable from the AP to its designated port on Switch 1 the network crashes !
    Error messages:
    When trying to print from clients on Switch 2 or when try to connect and use AP on switch 1 i get or "access denied to device connecting to portxx" or i get an STP blocking error .
    Hope the picture is clearer now.
    thanks once more.
    Fernando.

  • Cisco 500 Series 802.1x Requirements

    Hello,
    Does anyone have a guide on how to setup 802.1x on the Cisco 500 Series Switches.
    I have done the whole implamentation in the past with Catalysts and ACS.
    But would like to see a guide for the 500 series.
    Do we need the Cisco ACS or can we use RADIUS on Windows?

    Hi Peter, you may use IAS or any radius you prefer. To my knowledge the admin guide is the only documentation. You may check the Cisco knowledgd base as well.

Maybe you are looking for