Campus lan with 6500

Hi
At the moment we plan a new network with 2 6506 and sup720. I am not shure if hsrp is enough or better to use eigrp. Or does somebody has another idea

Hi,
Both HSRP and EIGRP has a differnt use on the Chassis.
HSRP is a protocol which is used for gateway readundency by providing a virtual IP as a gateway for the hosts. If one of the active gateway or the router goes down, the other gateway starts forwarding the packet.
EIGRP is a dynamic routing protocol which is used for routing between the 2 destination networks.
You have to impelemt HSRP on your LAN, that's for sure for the gateway redundency. If you have few other sites getting connectted to this site then you can run EIGRP or other routing protocol to share the routes and hence route the traffic.
Please Check the follwing links.
HSRP
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_6_3/confg_gd/redund.htm
EIGRP
http://www.cisco.com/en/US/partner/tech/tk365/technologies_white_paper09186a0080094cb7.shtml
HTH,
-amit singh

Similar Messages

  • Pop/Imap retrieving and redistribute in LAN with OsX Server

    It's possible to download mail accounts hosted in my isp and redistribut'em in my lan with OsX Server with it's own mail server?
    The scope is not to have a local server mail because we have ADSL and sometimes the line broke up...
    We prefere have mail hosted more securely in our external isp.
    But an internal mail server is a commodity very useful...
    Sorry if the questions is answered before...
    Thanks in advance.

    Maybe not easy but should work:
    http://www.macosxhints.com/article.php?story=2002052509542613
    man fetchmail

  • LAN with TCP/IP doesn't work

    Hello,
      I have a problem with my laptop IdeaPad S10e 4187-5PG: LAN with TCP/IP doesn't work, after I have updated all the drivers to the latest ones form the Lenovo site (except BIOS update). I tried to check if LAN worksby sending a ping to the IP address and that is OK, but when Isend a ping to the default gateway it failes. A ping to the DNS server also fails.Could you please help me because I tried everythinh and I can't getthe LAN to work.
    Thank you very much

    Perhaps you could describe you network in a little more detail.
    Is this a Workgroup home network or are you connected to a Domain server?
    If this is a workgroup are you connecting to the internet via a cable or DSL router?
    Do other computers on your network connect OK?
    Has your S10e ever worked properly on the network?
    Are you connecting via a wireless access point or LAN cable? 
    What do you Ping on and from where?
    Can you Ping OK on another networked computer?
    Open up a DOS Prompt (aka command prompt, DOS Box). and type IPCONFIG  /ALL <enter>. Do you get a compatible IP address and subnet mask? You should also get the gateway IP address.

  • Campus cluster with storage replication

    Hi all..
    we are planning to implement a campus cluster with storage replication over a distance of 4km using remote mirror feature of sun storagetek 6140.
    Primary storage ( the one where quorum resides ) and replicated secondary storage will be in separate sites interconnected with dedicated single mode fiber.
    The nodes of the cluster will be using primary storage and the data from primary will be replicated to the second storage using remote mirror.
    Now in case the primary storage failed completely how the cluster can continue operation with the second storage? what is the procedure ? how does the initial configuration look like?
    Regards..
    S

    Hi,
    a high level overview with a list of restrictions can be found here:
    http://docs.sun.com/app/docs/doc/819-2971/6n57mi28m?q=TrueCopy&a=view
    More details how to set this up can be found at:
    http://docs.sun.com/app/docs/doc/819-2971/6n57mi28r?a=view
    The basic setup would be to have 2 nodes, 2 storageboxes, TrueCopy between the 2 boxes but no crosscabling. The HAStoragePlus resource being part of a service resource group would use a device that had been "cldevice replicate"ed by the administrator. so that the "same" device could be used on both nodes.
    I am not sure how a failover is triggered if the primary storage box failed. But due to the "replication" mentioned above, SC knows how to reconfigure the replication in the case of a failover.
    Unfortunately, due to lack of HDS storage in my own lab, I was not able to test this setup; so this is all theory.
    Regards
    Hartmut
    PS: Keep in mind, that the only replication technology integrated into SC today is HDS TrueCopy. If you're thinking of doing manual failovers anyway, you could have a look at the Sun Cluster Geographic Edition which is more a disaster recovery like configuration that combines 2 or more clusters and is able to failover resource groups including replication; this product already supports more replication technologies and will even more in the future. Have a look at http://docsview.sfbay.sun.com/app/docs/coll/1191.3

  • Is it possible to enable to VSS with 6500 chassis when only one chassis have the WISM ?

    is it possible to enable to VSS with 6500 chassis when only one chassis have the WISM ?

    thank you very much for the reply, that mean both the chassis no need to have the same modules installed on both the chassis . 

  • [solved] Cannot activate wake on lan with systemd

    I have activated successfully wake on lan with systemd, following these guidelines :
    https://wiki.archlinux.org/index.php/Wol#With_systemd
    My [email protected] is:
    [Unit]
    Description=Wake-on-LAN for %i
    Requires=network.target
    After=network.target
    [Service]
    ExecStart=/usr/bin/ethtool -s %i wol g
    Type=oneshot
    [Install]
    WantedBy=multi-user.target
    It worked nicely until I recently had to reinstall my server (following a disk replacement). Since then systemd fails to activate wake on lan.
    Output from systemctl status wol@enp0s4 :
    ● [email protected] - Wake-on-LAN for enp0s4
    Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
    Active: inactive (dead) since ven. 2014-07-25 11:21:28 CEST; 23min ago
    Process: 181 ExecStart=/usr/bin/ethtool -s %i wol g (code=exited, status=0/SUCCESS)
    Main PID: 181 (code=exited, status=0/SUCCESS)
    Output from ethtool enp0s4|grep "Wake" :
    Supports Wake-on: pg
    Wake-on: d
    If I explicitly start the service with systemctl start wol@enp0s4, then ethtool enp0s4|grep "Wake" shows:
    Supports Wake-on: pg
    Wake-on: g
    My guess is that the service does not start at the correct timing at boot.
    I have also tried wol-systemd package from the AUR without success.
    Last edited by elb (2014-07-25 15:02:21)

    After a fiew tries and reading docs, I found that replacing network.target with multi-user.target in [email protected] seems to work for me.

  • Laserjet P2015 on LAN with different Windows

    I've been running my P2015 on our home LAN with both computers on Windows XP.  The printer was connected to computer A , and printer B saw it as belonging to A.  Now I have changed computer A to Windows 7 and I can't get computer B to find it.
    I think the problem is related to drivers, because Windows7 contains its own drivers.  I guess computer B now needs a driver to run the printer, but I don't know which driver, where to find it, and where to put it on B when I get it.
    Or maybe it's another problem.
    All help appreciated.
    oldrafe

    I would recommend installing the software again, here is a link to that: 
    http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?lang=en&cc=us&taskId=135&prodTypeId...
    Let me know how this goes! Happy Holidays! 

  • WLC DHCP issue with 6500

    Hi,
    I configured WLC as DHCP server and is working fine when connected to 3750 core switch. The AP's and clients are getting IP address.
    When the same WLC is connected to 6500 , the DHCP is not working from WLC . The same port of 6500 switch  is verified by connecting a 3750 switch as dhcp server and AP as well as clients are getting IP.
    DHCP snooping and port security is not enabled in the 6500 and the configuration is simple. The WLC is untagged and the 6500 port is a trunk port with 242 as native VLAN.
    Please help

    Dear Surendra,
    Please see the answers in line.
    1.As per your previous post, if we connect WLC to 3750 core everything works fine.. so in this case, i assume that we have INTERFACE VLAN on the switch and then the management interafce on the WLC are in the same subnet?? correct??
    "Yes , All are in the same Vlan . Interface VLAN and management interface are in same subnet."
    2. Similarly, if we swap the 3750 with 6500, it doesnt work.. in this case.. have you created the interface vlan on the 6500 in the same subnet as that of management interface of the WLC??
    " Yes, the 6500 has vlan interface without IP. The same way we configured 3750 "
    Or
    3.are we not swapping the 6500 and we are connecting the WLC to the WLC to the 6500 and then this 6500 to the 3750??
    "We connected WLC LAP to 3750 and the dhcp of wlc is working fine.. When WLC & AP connected to 6500 , the WLC DHCP is not working. We verified the 6500 port by coonecting 3750 as DHCP server and WLC is connected to 3750 and all were working fine. When WLC is directly connected to 6500 , the LAP is not joing to WLC. When static IP is given to LAP, the LAP joined WLC but the clients were not getting IP."
    4.Layer 2 means... interface VLAN on the switch and the WLC management and the AP DHCP pool are all in the same subnet. correct?
    "Yes all are in the same subnet"
    Thanks for your efforts.
    Regards,
    Savad

  • H-REAP vs Local mode on LAN with a single WLC

    Hi
    I have a question about H-REAP vs Local mode on a LAN with a single WLC.
    We use EAP-TLS with Cisco ACS for authentication of wireless clients.
    Up and until controller version 4.2 it was not possible to authenticate using 802.1x when a H-REAP AP went into standalone mode.
    Code above 4.2 can now support this. According to the documentation all you need to do is configure the RADIUS IP addresses on the H-REAP AP.
    Usually I would use H-REAP with central authentication and local switching for AP’s that are separated from the WLC via a WAN link.
    However, a colleague has suggested that we could configure H-REAP (central authentication\local switching) AP’s at the same site as the controller. This would give us the advantage that if we lost the controller (we only have 1) then at least the AP’s could still authenticate users.
    I am trying to see the “cons” of this solution. I guess roaming would be affected when the AP’s went to standalone mode as each roam would require complete re-authentication. But this is still better that a hard down state. Are there any cons to this approach during normal operation (e.g. when the controller is up)?
    What about RRM limitations?
    I seem to recall that a H-REAP AP was unable to increase its power output to address coverage holes?
    Layer 3 roaming not supported on locally switched WLAN’s?
    I would appreciate any thoughts\feedback
    Thanks,
    Andy

    My 2 cents :
    -I don't recall the HREAP APs having any RRM limitations in recent code.
    -No layer 3 roaming when you are locally switching. If the APs are dropping traffic locally at their switchport, you can't tunnel through WLCs like it happens when you usually do l3 roaming.
    -There are a number of features not supported when you do H-REAP. WGB is one of them for example. Fancy features like directstream and others.
    -The best answer in your case would be to have a second WLC where the APs can failover to. But I know it's not always possible.
    Nicolas

  • Boot a pc on lan with actionscript 3

    Hello:
    Can you tell me how can I boot one or more pc's over a Lan with AS3?
    I think this is call WOL.
    thank you very much

    I have never used the asUDP xtra, but after a quick read of the documentation it looks like it might work. You will probably need to use the accompanying BytesXtra as well. The structure of the Magic Packet is described in this wikipedia article http://en.wikipedia.org/wiki/Wake-on-LAN.
    It is an interesting project. Please post updates of your progress.

  • Boot a pc on lan with Lingo

    Hello:
    Can you tell me how can I boot one or more pc's over a Lan with Lingo?
    I think this is call WOL.
    Do I need any Xtras for this?
    Have you any sample code?
    thank you very much

    I have never used the asUDP xtra, but after a quick read of the documentation it looks like it might work. You will probably need to use the accompanying BytesXtra as well. The structure of the Magic Packet is described in this wikipedia article http://en.wikipedia.org/wiki/Wake-on-LAN.
    It is an interesting project. Please post updates of your progress.

  • MSI K8N Neo2 Platinum (WAKE On Lan with Realtek)?

    Hello can the MSI K8N Neo2 Platinum (BIOS 1.B) WAKE On Lan with the Realtek card?
    It does not appear to work for me and there is nothing in the BIOS.
    My WOL packets wake up other PC's.
    Please Help.

    Hello !
    Go into Bios Setup, Integrated Periphals, and disable the nvidia Lan, but let the Onboard LAN enabled.
    Now go to PCI Configuration, Wakeup Events, and enable wakeup on PCI event and wake on LAN.
    Check in Boot Order Menu if you can select the realtek onboard Lan as first booting device, push it in first place.
    Another Option could be using the nvidia Lan, its reported to work with wakeon lan.
    Greetz

  • Need help with Campus LAN building design

    Hey everyone,
    I'm currently studying in a program at College call Internet Communications Technology. I am working on a final project in my Physical layer class. Basically the final project is to design the telecom closets and network infastructure for a 3 level building.
    We never really covered the capabilities of certain cisco hardware so I'm looking for a little guidance in what to select.
    Basically we have between 300 - 400 people on each level. So we require 1148 cables. We need an additional 134 PoE connections for our phones and WAP's  I was going to VLAN each floor and then use VLANS on the floors themselves.
    On the main floor we will accept the fiber from the main section of the campus for the internet access and branch that out to the other telecom closets in the building using a single mode fiber cable.
    I was taking a look at some gear and this is where I am confused. I will require 1 fiber input from the campus and then I need 3 switches on each floor accepting fiber as there are 3 major areas on each floor. So each end of the floor has an auditorium with 170 people and then the middle.
    I was looking at using the Cisco Catalyst 2960-48PST-L - switch - 48 ports - managed - rack-mountable for our access layer switches in the telecom closets at the end... But I'm not really sure what to use for our core/distribution gear so I believe I would need 1 router on the main floor which can do all the interVLAN routing via fiber links between floors but then I would require a router on both floors 2 and 3 for the interVLAN routing on each floor. I would then need 3 main distribution switches on each floor. The switches I'm thinking could be smaller port based like a 12 or 24 port based switch as they would really just be there for accepting the fiber link from the main router on the first floor and branching that to the other telecom closets on the floor.
    Just looking for a little guidance here.
    Thanks everyone,
    Mike

    I'd recommend you have a look at the Cisco Smart Business Architecture designs: http://www.cisco.com/en/US/netsol/ns982/networking_solutions_program_home.html#lan
    Specifically see the LAN Deployment Guidefor advice on choosing the right type fo switch for the various layers.
    As a general guideline, I don't see anyone these days putting in routing away from the core in a campus (nor would I generally recommend it).

  • CAPWAP Wireless VLAN in Routed Campus LAN

    I am configuring CISCO Wireless LAN Controller in College campus. we have the following components
     1. CISCO 4510R as core switch and a centralized WLC is connected to Core Switch
     2. CISCO 3560 L3 switch at Distribution Layer Switch
     3. CISCO LWAP 1142
    I want to configure Wireless VLAN in a college campus. Wireless LAN.  The requirement is to configure Distribution switch as L3 so that VLAN will not reach till the Core Switch. That is the Link between Distribution and Core Switch will be Layer 3 routed link and not a Trunk Link.
    Since it is a routed back bone environment, VLAN is configured only in distribution layer switches. So, these configured VLAN will not reach core
    switch.
    With that said, is it technically possible to achieve the Wireless VLAN in this above proposed setup.?
    Do I have to configure Trunk between Distribution Switch (APs are connected) and Core Switch (WLC is connected), to pass the Wireless VLAN in the trunk link?
    Advance Thanks for reading and helping to get it clarified
    SAIRAM

    We are in the process of moving to a mostly routed Campus, and had similar questions and a few more. We will be using only EIGRP, with each enclave set-up as a stub. I was wondering if I can modify our wireless network to be strictly routed, and remove all the trunk/access configurations from the switch ports facing  theAPs, and hard code (static) all of them to IP routed ports. We only have one WLC active, with one back-up. The WLC is facing our core switches in a LAG set-up. The network was originally set-up with all the dynamic interfaces for each AP set-up in a GLBP fashion between our two cores. Each AP had a dynamic interface created in the WLC and added to one AP group. All of our APs are now connected via ethernet to the wired infrastructure, so none of our APs are in true MESH fashion anymore. We use Microsoft DHCP to issue out IPs to our APs.
    I was wondering if I can remove the dynamic interfaces from the WLC, and use EIGRP to sort of the routing of our wireless network. I would create L3 SVIs (multiple in some cases) on all the switches that APs are attached too, and modify each Microsoft DHCP scope to point to whatever AP model was used and to point to the WLC. Now, what I'm unsure on, how would this behave with no Native Vlan/User Vlans configured on trunk ports pointing toward the AP. I was thinking of using what was once used at the Native Vlan (subnet info), and using that same subnet to create a IP routed port facing the AP and modify the AP IP via the WLC to select static assign. I can place IP helper addresses under the routed port to face our DHCP server (not sure if this really matters, if I already place them under the user L3 SVIs). Before, I had a DHCP scope for the native and user subnet. Would the AP still be able to connect to the WLC correctly, if I delete the scope (used before for the native vlan), since it usually resolved the WLC IP via option 43 (it can use DNS instead). I would imagine so, since I will be placing these networks under EIGRP to advertise within our Campus, which has L3 reachability to the WLC. And under the user subnets, I would still configure the Microsoft DHCP scope to face the AP model and controller IP. There just woundn't be a scope for the subnet that use to be for the Native Vlan. For any new set-up, I would pre-provision the AP under a user subnet access port, and then hard code it within the controller a static IP, to deploy later at the new site. For routed networks, are dynamic interfaces really necessary on the WLC? As long as L3 is working as intended, and the user switch has reachability to the Microsoft DHCP server, then users should be able to pull IPs fine through, correct? I've tested already with a PTP bridge we have, and hardcoded the ports to IP routed ports, and advertised it via EIGRP, and haven't noticed any issues with the customers pulling new IPs. I wanted to gather more information before deploying this for across the board to our other types of wireless set-ups. I'm not using FlexConnect. I've moved most of our 1552e APs over to local mode recently, which have wired connections to the LAN.

  • VRF-Lite with 6500 w/ Sup720

    I am working with a customer who would like to utilize path isolation in their network using VRF-Lite. I am currently debating between the use of GRE tunnels vs. VLANs between 3 core switches they currently have in place today. This is going to be overlay network on top of what they currently have. The core is all L2 today with 802.1q trunks between each of 3 cores in a ring topology. Closets are single homed into the core throughout.
    My question is regarding GRE vs. VLANs. Currently, we are looking at having to deploy 12 VRFs to support 12 seperate network types they would like to isolate. The Access layer switches will trunk to the cores where the core will apply VRFs to specific VLANs based on their role.
    Which is going to be a more scalable solution from a performance and adminstration standpoint. GRE, VLANs, or MPLS?
    Currently the GRE implementation is going to require that we configure many loopbacks and tunnels on each core in order to get the VRFs talking to each other in each core. The VLAN approach will require 24 VLANs per core (assuming we would go with PTP vs Multipoint for routing inside the VRF).
    Any thoughts on which way to proceed? From what i have read GRE is more appropriate when you have multiple hops between VRF tables, which in this case we do not. I am just concerned with loopbacks,tunnels, and then routing on top of that the GRE solution will lack scalability as they add more VRFs. A PTP VLAN will pose a similar problem without the need for loopbacks which should simplify the solution.
    Can we use MPLS here and just do PE to PE MPLS and still get the VRF segmentation we need between cores?
    I would like eventually migrate the entire core to L3 completely but today we are stuck with having to support legacy networks (DEC/LAT/SNA) and have to keep some L2 in place.
    Whats the best approach here?

    Shine,
    I actually ended up with basically the same design you are talking about here except that I ended up adding a couple 6500 +FWSM and NAC L3/L2 CAM/CAS into the mix.
    Here is the high level overview
    1. Every Closet had a minimum of 6 VLANs - unique to the stack or closet switch - Subnets were created for each VLAN as well - no spanning of L2 VLANs across switch stacks.
    2. VLANs were assigned for - Voice, Data, LWAPP VLAN, Guest/Unauthorized, Switch/Device Management, and at least 1 special purpose VLAN - (Lab, Building Controls, Security, etc).
    3. Then we trunked all the VLANs back to 1 of 3 cores - 6509s with Sup-720s
    4. Each Core 6509 was configured for each L2 VLAN with a L3 SVI (The VLANs configured here were not configured on any other cores - we didn't have available fiber runs to do any type of redundant pathing across multiple cores so it wasn't valid in this design to configure VLAN SVIs on more than one core).
    5. Each L3 SVI was assigned to the appropriate VRF based on use - Voice, Data, LWAPP, etc
    6. Spanning-Tree Roots for all VLANs trunked to a core were specific to that core - they did not trunk between Cores - no loops
    7. Each Core was connected via a L2 Trunk that carried Point to Point VLANs for VRFs traffic - We had an EIGRP AS assigned to each VRF on the link - so we had 6 VRFs and 6 EIGRP AS per trunk.
    8. This design occurred on each core x2 as it connected to the other cores in a triangle core fashion.
    9. Each of the Cores had a trunk to to 6500 with a FWSM configured - VRF/L3 PTP VLAN design continued here as well
    10. The 6500+FWSM was configured with multiple SVIs and VRFs - we had to issue mult-vlan mode on the FWSM to get it to work.
    11. Layer 2 NAC was configured with VLAN translation coming into the Core 6500/FWSM for Wireless in L2 InBand Mode - the L3 SVIs were configured on the clean side of the NAC CAM so traffic was pulled through the CAM from from the dirty side - where the controller mapped host SSIDs to appropriate VLANs. We only had to configure a couple host VLANs here - Guest and Private so this was not much of an issue - Private was NAC enabled, Guest VLAN/SVI was mapped to a DMZ on the firewall
    12. For Layer 3 NAC we justed used an out of band CAM configurations with ACLs on the Unauthorized VLAN
    It worked like a charm.
    If I had to do it all over again I would go with MPLS/BGP for more scalability. Configuring trunks between the cores and then having the mulitple EIGRP AS/PTP VLANs works well in networks this small but it doesn't scale indefinately. It sounds like your network is quite large. I would look into MPLS between a set of at least 3-4 Core PE/CE devices. Do you plan on building a pure MPLS core for tagged switched traffic only? Is your campus and link make up significant enough to benefit from such a flexible design?

Maybe you are looking for