Question a bout Ospf & eigrp

Guys,
I would like to have more over view to the following:-
1- what is the exact functionality of (DR/BDR) on ospf tobology.
2- what is the point of using (auto-summary) command on eigrp, and when we should use it?
3- also I am alittle bit confused about using Ospf ABR type 3 LSA filtering with different areas, when should be applied?Is any difference between configuring normal OSPF comparing To ABR, what should I consider when configuring Type 3 ABR?
Thanks

Hi,
1. One of the major reasons for the DR/BDR concept is to reduce unnecessary flooding. If there wasn't such a concept, each router on a LAN would have to have an adjacency with every other router on a LAN. For example, on a LAN with 10 routers, that would mean 45 adjacencies !! Using a DR/BDR, that same LAN now has only 17 adjacencies. Now, OSPF floods LSAs over adjacencies so the more of those you have, the greater the flooding traffic. And most of this would have been unnecessary since the routers would have already seen the LSAs from some other neighbor.
2. This feature was more of a using in the days of classful routing, where you would not have wanted more specific routes of a classful network from leaking out of that network. These days, it is disabled by default and it should be kept that way !
3. One application of this is when using stub (not totally) areas with multiple ABRs. In such a case, you could filter out some type-3 LSAs from being generated by one of the ABRs. The other ABR would still advertise them and so all traffic for these networks would exit out of this ABR. The ABR on which you did the filtering would still advertise the type-3 default so if the other ABR dies, all traffic will now exit out of this ABR.
Pls do remember to rate the post..
Paresh

Similar Messages

  • VPLS - Which protocol, BGP, OSPF, EIGRP

    Hi Community,
    I am trying to figure out which protocol to use on a flat layer 2 VPLS.
    We have a flat layer 2 to connect 10 offices and some other point to point links to connect to other offices. We currently use EIGRP but going forward we want to control the routnig and the path the traffic takes. I was planning on using BGP to peer between the offices using a hub and spoke topology, instead of a full mesh. I know OSFP is better for a layer 2 VPLS as it alows the full lan to be used effectively.
    Can anyone suggest why we shouldn't use BGP on a VPLS from a provider?
    Regards
    D.

    Hi Dinesh
    In my personal opinion using BGP in a LAN environment will not provide any benefit as it will add to the BGP Session overhead per LAN Node owing to the Full Mesh requirement which is definitely not scalable.OSPF as an IGP is good choice to be run on the LAN in broadcast Mode which will help keep optmial design using DR/BDR.As far as the Routing Control is concerned BGP should be used for external traffic outside OSPF domain and mutually controlled redistribution between the external Routing Protocol and OSPF should be used.
    But if we intend to use Hub and Spoke Topology using P2MP Broadcast Ethernet ie VPLS I think this will not be possible to achieve in OSPF Broadcast Mode neither in BGP using IBGP in Hub and Spoke Fashion among the sites because of BGP Split-Horizon Rule nor using dedicated EBGP Sessions between Hub and Spokes because of 3rd Party Next-Hop feature . So in this scenario of using VPLS for any to any communication in L2 Mode between the sites and then considering Hub and Spoke topology will not be possible to achieve either in OSPF or using BGP and also it defies the basic VPLS connectivity taken to connect the diffent sites in P2MP mode.
    This is my personal take on this scenario and hope this helps you something in your design considerations.
    Regards
    Varma

  • DMVPN Question on NHRP and EIGRP neighbor relations

    First of all thank you for your answer, in a DMVPN network, running EIGRP over GRE, will a spoke consider another spoke an EIGRP neighbor? or will it just consider the hub to be an EIGRP neighbor when it comes to sending/receiving eigrp queries/updates? given that in dmvpn setup one spoke can establish a direct tunnel with another spoke.

    If you are running EIGRP, under EIGRP type in
    no split-horizon eigrp ; where x is the as #.
    Also, if your dmvpn routers have default routes ie 0.0.0.0/0 pointing to the ISP on all routers that is ok. IF you have specific static routes for DMVPN hub public on DMVPN spoke router, you would also need to add a static route for the other dmvpn spoke public address on your first dmvpn spoke and vice versa. Hope this helps.

  • Big question here bout Netboot\install

    i would like to do both
    I have os x 10.1 10.2 10.3 10.4 and 10.5 to do netinstall's
    do do net boots i would like to do os 9 10.1 10.2 10.3 10.4
    At the moment i have server 10.3.9 i have just set it up, can some one help me here? just to tell you all i am doing this so i can get my older imacs i got from school to run, there cd\dvd rom drives have been trashed, (also 10.5 install for my mac book,)thanks I hope i sound like a noob as im one when it comes to servers , By the way i'm 15 years old

    Hi Jake
    Did they netboot these old machines? This is an important question, because they'll only netboot if their firmware is up-to-grade. If it isn't you'll need to boot them differently to install the upgrade. Which would mean you'd have to tear them apart if there's no OS installed now.
    Here's a good resource how to set up NetInstall: http://www.gips.org/Technology/netbootclass.pdf
    Also make sure you read through the invaluable articles here: http://bombich.com/
    You'll also find the tool mentioned in the first PDF there.
    But, before getting ready to netboot, you need a Mac OS X Server with DHCP set up (or a router that is able to serve BootP plus a PPC machine with firewire to create your image from.
    You're heading to take a very (very, very) steep learning curve here if you have never done something similar before. It's repaying, but you still might want to talk to an electrical engineer how you can prevent yourself from getting electrocuted when you attempt to disassemble all-in-ones.
    (BTW it's great you know it's the TFTs that make the iMacs more dangerous than other computers, as they can have very high residual voltage for many hours after taking them off the grid. That said, getting your hands on the HDD does not involve touching the tube).
    Kind regards
    --greg

  • Question about OSPF to BGP redistribution

    I have some static routes on a router where OSPF and BGP are also running. I have redistributed the static routes into OSPF (showing in OSPF database). I also want to have the static routes into the BGP routing table. Understand this can be done by using a prefix list permiting all the static routes, however I was thinking a simpler way just redistributing whatever is in the OSPF routing tabel into BGP (permit 0.0.0.0/0 le 32).
    My question is if OSPF really redistributes those routes. Those routes are shown as "static" in "sh ip route" even though they are also in OSPF database. I have heard that OSPF only redistributes the routes showing as "OSPF routes", not what's in its database.
    Thanks for any help.
    Gary

    Hi Gary,
    The thing to understand here is that the use of redistribution does not change anything in the routing table of the router on which you are configuring it.
    As you have observed, static routes do not become OSPF routes when you redistribute them into OSPF. This can be generalised to the following: when you redistribute protoclol1 into protocol2, the router will scan the routing table for routes installed by protocol1 and will then do one of the following, depending on the protocol it is being redistributed into:
    - if it is a Link state protocol like OSPF, it will originate LSAs appropriate to the route being redistributed. These LSAs will be subsequently flooded to other routers which will install them as routes in their routing table. The only change on the redistributing router is the installation of additional LSAs; the routing table does not change
    - if it is a distance vector protocol like IGRP, the router will take the protocol1 routes and advertise them via IGRP update packets every time an update packet is sent. Once again, there is no change on the routing table of the redistributing router.
    Note the other important point: when redistributing is carried out, the only routes that are redistributed are those that are in the routing table and installed there by the source protocol, which could be quite different to the contents of link-state databases.
    Hope that helps.
    Pls remember to rate posts.
    Paresh.

  • OSPF and VLANs

    Scope of Inquiry:
    I've supported heterogeneous networks for merely a decade, but never quite big enough to expose me to Enterprise routing/switching concepts in real-time. I've supported numerous Metro Ethernet hub and spoke topologies, as well as a few racks in a datacenter environment ... however, once again ... no real application of OSPF, EIGRP, etc. 
    I'm learning some of the fundamental concepts of OSPF, adjacency, LSA types, etc... but one thing that has me tripped up is whether or not/how VLANs would be leveraged in a real-world scenario, in an OSPF environment.
    Can anyone kindly give me a very clear and concise explanation/high-level explanation of the contextual application of VLANs in an OSPF network, including whether or not tags would exist in each area, etc. * Please do not pontificate --- that is to overstate a simple explanation with extraneous details that are outside the scope of a basic/real-world explanation. Hope that wasn't too terse, but I'm trying to gain a working knowledge of the protocol and its nuances quickly. 
    Thanks!
    -Data-

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Hmm, don't know if I can briefly provide such a description.  Currently, I work in a large company (about 100,000 employees [with about 5,000 Enterprise switches and routers]) and my purview is about 10% of our Enterprise's switches and routers.  My sites range is size from just supporting a few hosts to thousands of hosts, equipment "sizes" range from Cisco 800 series ISRs, up to 6500s in VSS pairs.
    From a VLAN standpoint, VLANs generally provide subnets for hosts which also range is size from a /29 up to a /23.  VLAN/subnets are defined principally for like hosts and sized for the number of like hosts.  However, generally like host VLANs/subnets are split into multiple like VLANs/subnets once you get up to about a /24.
    A VLAN/subnet might only be hosted on one large chassis (4510 or 6509/6513) or it might be hosted on multiple L2 switches (2Ks/3Ks).  Generally (but not always) VLANs/subnets do not span multiple sites.
    At the moment, all sites with a region, generally one or more adjacent US States, are grouped into the same OSPF area.  I.e. such a region might have 50 to a couple of hundred OSPF "routers" in the same area.
    Originally area zero was used to tie the region areas together, but currently BGP is used with the WAN core (between regions).
    OSPF, per area, of course has all the subnets being hosted by VLANs and also all the (numbered) p2p links (per region/OSPF-area networks can run into a couple of hundred).
    LAN designs are generally just 1 or 2 layers, this because you can host so much on a large chassis or stack.  For example, at one of my larger sites, my user edge devices are 3 6509s with 96 port line cards.  As the users ports support both VoIP and data VLANs, a single data or VoIP VLAN spans two line cards (i.e. 192 ports).  So with 7 user line cards, the chassis hosts 4 data VLANs/subnets(/24) and 4 VoIP VLANs/subnets(/24).  As the 6509 has a L3 sup, the 8 chassis subnets are included in that device's OSPF router section and advertized to the rest of the OSPF area (via a dual gig, L3 Etherchannel, uplinked to a site core 6509 - the latter having two 10g SM off-site OSPF p2p fiber links).
    At a small (old technology) branch, I might have a "ring" of several 2K series switches.  For routing I'll have some 3K switch with an off-site gig link and a connection to one of the 2K switches.  I might also have a small ISR with a VPN tunnel, for off-site, with a connection to a different 2K switch.  There will be one to several VLANs/subnets defined on the 2K switches and 3K switch.  The ISR will indirectly have access to the VLANs via .q subinterfaces.  The 3K and ISR provide the subnet getways and include the VLAN/subnets into OSPF.  The also generally will run HSRP for the VLAN/subnet gateway IP.
    At a small (newer technology) branch, may have a L3 stack and an ISR.  One stack member has the high speed off-site gig link, the ISR connects to a different stack member.  However, the ISR now has a L3 routed p2p link to the L3 stack; there's no HSRP.  Yet, VLANs/subnets are pretty much as the above (paragraph).
    Hopefully the above gives you a view into some real world, large scale, with VLANs and OSPF.
    If you have additional questions, feel free to ask.

  • VLANs in OSPF network?

    Scope of Inquiry:
    I've supported heterogeneous networks for merely a decade, but never quite big enough to expose me to Enterprise routing/switching concepts in real-time. I've supported numerous Metro Ethernet hub and spoke topologies, as well as a few racks in a datacenter environment ... however, once again ... no real application of OSPF, EIGRP, etc. 
    I'm learning some of the fundamental concepts of OSPF, adjacency, LSA types, etc... but one thing that has me tripped up is whether or not/how VLANs would be leveraged in a real-world scenario, in an OSPF environment.
    Can anyone kindly give me a very clear and concise explanation/high-level explanation of the contextual application of VLANs in an OSPF network, including whether or not tags would exist in each area, etc. * Please do not pontificate --- that is to overstate a simple explanation with extraneous details that are outside the scope of a basic/real-world explanation. Hope that wasn't too terse, but I'm trying to gain a working knowledge of the protocol and its nuances quickly. 
    Thanks!
    -Data-

    Hi, I am afraid you chose the wrong forum. This one is mostly about contact centers. You might have to send your question to Routing&Switching section.
    G.

  • Hi all, need advice on OSPF and private vlans

    Hi all.
    I have a project to complete and need some help on the possible solution I can use.
    Basically we have ospf area 0 and the users in question are in ospf area 7 and is a stub.
    I need to route the traffic from these users out through area 0 through 3 core devices, onto an external firewall interface to be placed onto the vpn that sits on it. The firewall is not included in the ospf domain.
    My thinking was that the firewall has a default route back into the ospf domain so dont need to worry about traffic coming in, however my job is to segregate these users and take them out of our core network and place them onto an external network via this vpn.
    Not sure how to achieve this apart from static routing redistributed but surely this does not seperate their traffic only points the route to ospf?!
    I was thinking I might have to use private vlans or policy routing but when I try policy routing the policy gets ignored due to normal forwarding.
    Any help and advice would be greatly appreciated.
    Cheers
    Steve

    Steve
    Thanks, that helps.
    GRE is defintely out because apart from the 6500 GRE tunneling is not supported on the Cisco switches.
    It's good that area 7 is only for these users and not mixed up with other users.
    So if i understand correcty the 4500 interface connecting to the 6500 is in area 0 and the interface connecting to the 3550 is in area.
    Or is the 3550 connected to both areas and the 4500 totally in area 0 ?
    Can you confirm the above ?
    In terms of keeping them separate there are 2 possible choices. You can either -
    1) use VRF-LIte, although i'm not sure whether the HP switch would support this. With VRF-Lite you are in effect creating virtual devices on the same physical device. This means each virtual device has it's own routing and forwarding table so it is quite secure because you would only populate the routing table with the routes needed so there would be no way for users to jump to thes rest of your networks.
    The downside is that is can become quite complex to configure. If the 4500 is only used to connect are 7 to area 0 then that would not be a problem but the connection from the 6500 to the HP could and i don't even know whether the HP supports VRF-Lite functionality let alone how to configure it on that switch.
    But it would, at least from the 4500 to 6500 to HP provide complete separation in terms of routing and forwarding. Once it got to the HP it wouldn't but that might not be an issue.
    2) Use PBR (possibly together with acls). This is easier to configure ie. you configure PBR on the 4500 and the 6500 to get the traffic to the HP switch. But you do not get the actual separation you get with VRF-Lite ie. the traffic simply overrides the existing routing tables.
    The other thing to bear in mind with PBR is that you also have to configure the return traffic as well so each device would need multiple PBR configs.
    Again i don't know whether the HP supports PBR but it may not be an issue depending on what the routing is on the HP.
    You could also use a combination of the above ie VRF-Lite between the Cisco switches and then PBR for the last hop to the HP device.
    I should say i don't have a huge amount of experience with VRF-Lite but that should not necessarily stop you using it if it is what you need. There are lots of other people on here so i'm sure there will be other people who can help if i can't.
    It still depends on how much separation is required. VRF-Lite is definitely seen as a way to separate traffic running across a shared infrastructure, PBR is not really seen in the same way.  So it may well be worth going back to find out exactly what "segregating" user traffic means.
    I don't want to confuse the issue but it's still not entirely clear what the actual requirement is.
    Jon

  • DOES EIGRP USE AS NUMBER/process number as it's PORT NUMBER between the routers in the same AS/group?

    in this posthttps://supportforums.cisco.com/discussion/9805551/eigrp-port-number  there is an answer which seems a little weird, the question asks about the EIGRP port number, and someone answers that "The port number is the EIGRP AS."
    I goggled all over the net but could not find any single clue about it!! is that really so, I mean DOES EIGRP USE AS NUMBER AS PORT NUMBER?
    I know stuff about routing, EIGRP,RTP and so on, please don't state the obvious and just give some link to some document on Cisco, about this subject.
    BTW there's a link under the mentioned post but it doesn't load, I don't know, anyway thank you

    in this posthttps://supportforums.cisco.com/discussion/9805551/eigrp-port-number  there is an answer which seems a little weird, the question asks about the EIGRP port number, and someone answers that "The port number is the EIGRP AS."
    I goggled all over the net but could not find any single clue about it!! is that really so, I mean DOES EIGRP USE AS NUMBER AS PORT NUMBER?
    I know stuff about routing, EIGRP,RTP and so on, please don't state the obvious and just give some link to some document on Cisco, about this subject.
    BTW there's a link under the mentioned post but it doesn't load, I don't know, anyway thank you

  • Bgp neighborship question

    Hi.
    one question.
    why  bgp neighborship doesn"t establish when no dynamic routing protocol is enabled?
    there four router.
    A--------B-------C-------D
    they all can ping. 
    No dynamic routing
    static routing only enabled.
    Configured bgp as 100 with A and D but bgp neighborshi didn"t establish.
    am i missing something??

    From A side :
    R1#ping 1.1.34.4
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 1.1.34.4, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 80/127/164 ms
    R1#show ip route
         1.0.0.0/24 is subnetted, 1 subnets
    C       1.1.12.0 is directly connected, FastEthernet0/0
    S*   0.0.0.0/0 [1/0] via 1.1.12.2
    R1#ping 1.1.34.4
    R1#sh ip bgp summary
    BGP router identifier 1.1.12.1, local AS number 10
    BGP table version is 1, main routing table version 1
    Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    1.1.34.4        4    10       0       0        0    0    0 never    Active
    =======================================================
    From D side :
    R4#sh ip bgp summary
    BGP router identifier 1.1.34.4, local AS number 10
    BGP table version is 1, main routing table version 1
    Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
    1.1.12.1        4    10       0       0        0    0    0 never    Active
    R4#
    there's no special log. i tested in my GNS3 and i can open 179 both side by using telnet
    weird thing is that when i enabled ospf for all of this topology, BGP neighborship was established.  that's why i asked this question. 
    router ospf 1
    net 0.0.0.0 0.0.0.0 a 0

  • Subnet question

    hi all, can anyone answer this for me, If im using 192.168.1.253/30, can I still use the full 192.168.1.0/24 somewhere else ?

    You can, as long as 'ip classless' is enabled on your router _and_ /30 networks are advertised by some classless routing protocol (RIPv2, OSPF, EIGRP, but not classfull RIPv1 or IGRP) _and_ they're not summarized. Sometimes such situation is result of (auto)aggregation with discontigous subnets, will work but not necessarily a good thing and I'd try to avoid this whenever possible.

  • Out-Of-Band Management over IPSec and OSPF Area Design

    Hello,
    i'm planning to implement Out of band management over OSPF over IPSec Tunnel and i have a question about the OSPF area design (please see attached figure).
    As network administrator our NOC is sitting in OFFICE (OSPF Area 1). Internet access is guarenteed over our DCs (Multihomed BGP peering).
    Additionally we have a second internet access at OFFICE where i want to use for IPSec Tunnel and building a OSPF neighboring to our Out-of-Band Firewall, which they too have theire own internet access.
    I'm planning to declare this IPSec Tunnel as OSPF AREA 3 and AREA 4 respectively for DC1 and DC2. There are no subnet overlapping.
    My Question is if I should connect both areas 3 and 4 at OFFICE to the backbone area over a virtual-link or not? Would be an disadvantage if i wont use the virtual-link?
    Thx for any reply

    1.The AUX port on Cisco routers is either RJ-45 or DB-25. If the AUX port is RJ-45, use a flat-satin rolled RJ-45--RJ-45 cable (part number CAB-500RJ= ), which is usually provided with every Cisco router for console connections. You also need an RJ-45 to DB-25 adapter marked "MODEM" (part number CAB-25AS-MMOD) to connect the rolled cable to the DB-25 port on the modem.
    2. if your router has a DB-25 AUX port, use a straight-through DB-25Female - DB25Male RS-232 cable to connect the modem to the router.
    Use this document.
    http://www.cisco.com/en/US/tech/tk801/tk36/technologies_tech_note09186a0080094bbc.shtml

  • The difference between SSO/NSF(GR) and NSR

    Hello
    I have question about the differnce between SSO/NSR(GR) and NSR.
    In my understanding SSO/NSR is stateful switchover from Active to Backup
    Mainly take over teh startup configuration and FIB TCAM table and so on.
    But this protocol need to re-establish the routing table and topology database etc.
    But if NSR functions when stateful switchover happens then it takes over routing table
    and toplogy database etc. right? 
    If so, I think BGP peer down/up (flapping) , OSPF/EIGRP neighbor state change does not happen right?

    ITS is used for accessing R/3 through browser....to implement SSO from Portal to access backend R/3 systems over ITS you need to follow certains step ...
    1. Create RFC Destination in J2EE Engine RFC JCo Provider
    2. Create RFC Destination in the R/3   Transaction: SM59
    3. Maintain Portal Server Settings for the Portal
    4. Maintain Single Sign-On in the R/3 System
    5. Export  R/3 Certificate to the Portal System
    6. Import  R/3 Certificate to the Portal
    7. Create  R/3 System in the Portal
    8. Configure User Management in the Portal
    9. Export Portal Certificate from Portal
    10. Import Portal Certificate to the R/3 System
    11. Set Up Repository Manager for R/3 in the Portal
    12. Maintain User management as SAP Logon Ticket in the Portal
    Hope I have answered your query in proper way.......
    If you want step by step details pl s let me know
    Swapnil

  • New LAN Design Help

    I'm new to Cisco and hoping to implement a large Cisco solution. Unfortunately we're not in the position to hire an expert so I'm seeking some much needed advice!
    The general plan for phase 1 would be:
    A router with 9 interface cards, that will have a 4Gbps trunk to an Internal Network Switch, 1gbps to DMZ switch, 1gbps to WLAN router, 1gbps to identical router for HSRP, 1gbps to WAN switch, and 100mbps to Internet router
    The router will need to participate in OSPF, HSRP and do trunking. It needs to do IPSEC vpn tunnels
    The Internal Network Switch would have about 40 Vlans to individual departments. Each department uplink to the Internal Network Switch would be 100mbps. Eventually this switch will be doubled up for redundancy.
    There would be about 1000 clients going through it via the Internal Network Switch, and through the Router, using the DMZ servers as well as the Internet.
    So I have a few questions regarding this setup:
    1/ Which type of router should I use?
    2/ Which type of switch should I use?
    3/ Is the network schema at all correct or would there be a better way of doing it?
    Hoping for some help!

    1) I recommend going with Cisco 2800 ISR for the IPSec VPN http://www.cisco.com/en/US/products/ps5854/index.html
    2) I recommend going with Cisco 3750G for the DMZ, WLAN, WAN switch connections. This switch provides (with the right image) HSRP, OSPF, EIGRP services.
    http://www.cisco.com/en/US/products/hw/switches/ps5023/index.html
    3) Drop all connections down to the 3750G (all ports support up to 1Gb speed) and perform all the routing there as well as layer2 VLANs.
    Nice, clean and inexpensive solution.
    In addition, 3750s support stackwise cabling so if you purchase more than one switch for port density, in the config it looks like a single switch.

  • Cisco Network Assistant, unable to add a switch

    I have a network running some 20 switches, two controllers and many AP's.  All the devices that should be able to connect to cisco network assistant can successfully.  However there is one switch that will show in neighbours but will give the message of “unable to connect to device” when I try and add it to the topology. 
    As far as I can see the config is identically to all other similar switches in the network.  I can telnet from a switch (management VLAN) to the switch in question.  However when I try to ping or telnet from the PC running network assistant (different subnet) I am unsuccessful.  However I can ping/telnet to all other cisco device from this PC. 
    The switch is a WS-C3560-48TS and I have included the config for firstly the switch in question and another switch of the same model and config that works correctly.  Any help would be greatly appreciated, thank you.    
    sho run
    Building configuration...
    Current configuration : 7363 bytes
    version 12.2
    no service pad
    service timestamps debug datetime localtime
    service timestamps log datetime localtime
    service password-encryption
    hostname wc3_switch_1
    enable secret 5 $1$Fn0U$2rG6DadA8JSUzQzSNmMc4/
    enable password 7 1511021F0725
    username dis privilege 15 secret 5 $1$b3d.$S43CM1xtXyEtO5Rsil6Bn1
    username admin privilege 15 password 7 0811185C224C543341
    no aaa new-model
    ip subnet-zero
    ip routing
    no ip domain-lookup
    no file verify auto
    spanning-tree mode pvst
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    interface FastEthernet0/1
    description ### Connected to Parkside-AP05 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/2
    description ### Connected to Parkside-AP06 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/3
    description ### Connected to Parkside-AP07 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/4
    description ### Connected to Parkside-AP08 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/5
    description ### Connected to Parkside-AP12 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/6
    description ### Connected to Parkside-AP13 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/7
    description ### Connected to Parkside-AP20 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/8
    description ### Connected to Parkside-AP21 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/9
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/10
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/11
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/12
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/13
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/14
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/15
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/16
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/17
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/18
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/19
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/20
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/21
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/22
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/23
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/24
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/25
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/26
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/27
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/28
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/29
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/30
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/31
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/32
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/33
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/34
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/35
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/36
    description ### Connected to Parkside-AP36 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/37
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/38
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/39
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/40
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/41
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/42
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/43
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/44
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/45
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/46
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/47
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/48
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface GigabitEthernet0/1
    description *** Connected to WC2A_Core_Switch ***
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface GigabitEthernet0/2
    description *** Connected to wc3_switch_2 ***
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface GigabitEthernet0/3
    shutdown
    interface GigabitEthernet0/4
    shutdown
    interface Vlan1
    ip address 10.0.0.31 255.255.255.0
    ip default-gateway 10.0.0.254
    ip classless
    ip http server
    control-plane
    line con 0
    password 7 144711185D07
    logging synchronous
    login local
    line vty 0 4
    password 7 144711185D07
    logging synchronous
    login local
    line vty 5 15
    password 7 094F471A1A0A
    no login
    end
    wc3_switch_2#sho run
    Building configuration...
    Current configuration : 7239 bytes
    version 12.2
    no service pad
    service timestamps debug datetime localtime
    service timestamps log datetime localtime
    service password-encryption
    hostname wc3_switch_2
    enable secret 5 $1$Sfoj$a6AdO7PI0bP8ERhpWl3OP.
    username dis privilege 15 secret 5 $1$D9c6$16yFzETOxBNHiPdTEqkxQ1
    username admin privilege 15 password 7 133543002059550E78
    no aaa new-model
    ip subnet-zero
    no ip domain-lookup
    no file verify auto
    spanning-tree mode pvst
    spanning-tree extend system-id
    vlan internal allocation policy ascending
    interface FastEthernet0/1
    description ### Connected to Parkside-AP24 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/2
    description ### Connected to Parkside-AP27 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/3
    description ### Connected to Parkside-AP28 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/4
    description ### Connected to Parkside-AP30 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/5
    description ### Connected to Parkside-AP31 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/6
    description ### Connected to Parkside-AP32 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/7
    description ### Connected to Parkside-AP33 ###
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/8
    description *** Curric4 VLAN Port ***
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface FastEthernet0/9
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/10
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/11
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/12
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/13
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/14
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/15
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/16
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/17
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/18
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/19
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/20
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/21
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/22
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/23
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/24
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/25
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/26
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/27
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/28
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/29
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/30
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/31
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/32
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/33
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/34
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/35
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/36
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/37
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/38
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/39
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/40
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/41
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/42
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/43
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/44
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/45
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/46
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/47
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface FastEthernet0/48
    description *** Curric4 VLAN Port ***
    switchport access vlan 6
    spanning-tree portfast
    interface GigabitEthernet0/1
    description *** Connected to wc3_switch_1 ***
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface GigabitEthernet0/2
    description *** Connected to wc3_switch_3 ***
    switchport trunk encapsulation dot1q
    switchport mode trunk
    spanning-tree portfast
    interface GigabitEthernet0/3
    shutdown
    interface GigabitEthernet0/4
    shutdown
    interface Vlan1
    ip address 10.0.0.32 255.255.255.0
    ip default-gateway 10.0.0.254
    ip classless
    ip http server
    control-plane
    line con 0
    password 7 135514015A0F
    logging synchronous
    login local
    line vty 0 4
    password 7 135514015A0F
    logging synchronous
    login local
    line vty 5 15
    no login
    end

    The switch configurations look pretty straightforward and mostly correct.
    I notice that the problem switch has "ip routing" global command. Why is that necessary? You are only using it as a L2 switch, yes?  If you use "ip routing" and have no routing process (ospf, eigrp, etc.) running you would need to add a static default route (ip route 0.0.0.0 etc.) and not use the "ip default-gateway" command. Otherwise the switch itself (the SVI) does not know how to leave the management VLAN routing-wise since it is the only L3 interface defined.
    (I might also add "ip http authentication local" on each and I'd definitely disable telnet in favor of ssh)

Maybe you are looking for