Core layer switches IP address for routing

For routing process I add a IP address of each Vlans subnet that active on each Access and Distribution switches (Have a port with that Vlan on the switch) to the corresponding Vlan Interface of them.
Which IP address should I add to the Core switch for routing?
Should I add a IP of each vlan that in the LAN to each vlan interface of Core layer switch?
I want run OSPF routing protocol on the LAN.

Hello Reza,
>> Which IP address should I add to the Core switch for routing?
if you want to implement a L3 routed core every link betweeen core device and a distribution device is a L3 link with its own IP subnet.
For example if you have 16 distribution pairs and two core switches:
10.10.10.0/30 dis11 to core1
10.10.10.4/30 di12 to core2
10.10.10.8/30 dis21 to core1
10.10.10.12/30 di22 to core2
10.10.10.128/30 disF1 to core1
10.10.10.132/30 disF2 to core2
this under the idea to have not a full mesh between core routers and distribution devices
then you need also a L3 link between the two cores (at least one)
Each L3 device should also have a loopback interface to be used as OSPF router-id and for management purposes (telnet and so on)
you can use /32 loopbacks taken from same block for example
10.255.254.1/32 core1
10.255.254.2/32 core2
10.255.254.3/32 dis11
10.255.254.4/32 dis12
to make the routing function the core switches have to talk OSPF on all links to distribution nodes
router ospf 10
router-id 10.255.254.1
network 10.10.10.0 0.0.0.255 area 0
network 10.255.254.1 0.0.0.0 area 0
network area commands work like ACL statements and first statement starts OSPF on each interface whose ip address belongs to 10.10.10/24 space
Second command is used to advertise its own loopback.
router-id command allows to define the OSPF router-id.
Distribution nodes have to advertise client Vlans and to take part in OSPF communication on point to point link.
if you use a L2 access layer design client vlans are served by distribution nodes.
if you use a L3 access layer design the access layer switches take part in OSPF and have to advertise their own client vlans.
Hope to help
Giuseppe

Similar Messages

  • Is it recommended to use HSRP or multiple default between Core Layer Switch and Customer Edge Router?

    My client is asking me for following
    Client is using Router as edge device. 2  WAN links from different service provider ( each 20 Mbps)  are getting terminated on the router. There are internal servers present in the network. Client want to make setup such that even if one wan link fails  internet users should be able to access web server. Moreover if the edge router fails there should be secondary edge device so that there is device redundancy ?
    As per my understanding, in this scenario we need to do static one - to - one natting(belonging to WAN interface subnet). If we use two routers as Customer edge ans if we connect core layer switch to these two router, is it recommended to use HSRP/VRRP/GLBP or two default route on core switch pointing to two routers with equal ad value. we will also track the wan link with help of ip sla.
    which is recommended solution  Router redundancy protocol or Default routes.?

    Just had another read of this post and some other points have come up.
    1) I assumed your secondary link was for redundancy but you talk about terminating both SP links on the same router in your first paragraph.
    Did you mean this or are you going to be terminating a link per router ?
    2) are you using the second router purely for backup ?
    3) something you didn't ask about but is relevant is the IP addressing. Are you using provider independent addressing or does each SP provide you with an address block.
    If it is the second then you are going to have an issue with the web server. The problem is which provider's IP do you use for the web server ie.
    if you use the primary provider IP then that will be the DNS record on the internet. If the primary router fails then the IP address will change on the secondary router but DNS will still be handing out the primary IP.
    If you enter both IPs (primary and secondary) into DNS then you would get load balancing but this means both links will be used and the secondary would not just be backup.
    In addition if one of the links fails then DNS does not know this so it will still be handing out the failed address as well as the address that is still up which means some connections will work and some won't.
    Jon

  • Creating Vlans at Core layer switches ?

    Is there a need to create vlans at core layer switches ? If yes what are the pros and cons for this practice ?
    Actually i have seen some networks doing that!

    Well this is the topology that i'm working on.
    we have implemented the 3 layer approach.
    1. At access layer: Switches are all L2 (for sure :) )
    2. At distribution layer: All switches are L3 are routes for incoming data.
    3. At core we have 2 6500 switches. One is configured as L3 and all vlans are created in it. Second is just as regular L2 device.
    and ofcourse there are some switch blocks for server farms and the likes.
    My issue is
    1. why don't we create vlans at distribution layer switches.
    2. Why one core switch is acting as L2 and other is acting as L3. What will happen in case of failure to the one acting as L3.
    Ps: the second issue just came up in my mind.

  • Airport utility 6.1 change ip address for router

    Hi there,
    I want to change the IP address for the router from 192.... to 10.....?  It doesn't seem possible with the new version of the aiport utility.
    Any help would be greatly appreciated.

    You can change the IP address range that the AirPort Extreme provides as follows:
    Open Macintosh HD > Applications > Utilities > AirPort Utility
    Click directly on the AirPort Exteme icon
    Click Edit in the next small window that appears
    Click Network at the top of the next window
    Click Network Options at the bottom of the window
    Here, you can changet the iPv4 IP address range from 192.168.x.x to 10.0.x.x
    Click Save and then click Update to restart the AirPort Extreme
    IF....the Network Options button is grayed out, this indicates that the AirPort Extreme is in Bridge Mode. In that type of setup, you have another modem/router or gateway "upstream" on your network.  That is is the device that is providing the 192.168.x.x. IP addresses.
    The AirPort Exteme simply passes through that network information to connected devices in Bridge Mode, since you only want one router on the network providing IP addresses.
    You will need to check with the support folks for your modem/router or gateway if you want to modify the settings on that device.

  • Cant find ip address for router

    When I try to access the setup page for my router, 192.168.1.1 does not work and neither does 192.168.1.2 any way to find out what the address is. when I type in those address is comes up no such website ect.

    Check first what ip address your router is getting. Open your command prompt. All you need to do is click on the START button at the bottom left of your screen. Click on RUN and type in lower case cmd and press enter. Then you will have a black screen or your command prompt. You will see a blinking cursor all you need to do is type in ipconfig and press enter. You will then know what ip address your getting. The default gateway is the address you need to use for you to access your router set-up page.

  • IP address for router

    I am a new mac user. I bought a mac book pro and and airport device. I"m attempting to set up and I"m getting the flashing amber light. THe diagnostic says my router does't have an IP address. Any suggestions on where to find it?

    Hello from the UK.
    I am also a new Mac owner and had the same trouble setting up my Time Capsule. Eventually phoned Apple Help Desk which sorted out my problem.
    The TC needs to read the IP address from your router. To let it do this you need to power off your router and TC. Wait at least two minutes, longer if you have the patience, and then power up your router, wait until all the lights are on on your router, once you are sure that is stabilised switch on your TC. Now open the airport programme on your MacPro and when it sees your time capsule it should automatically obtain the IP address it needs. Putting in a manual IP address does not seem to work, not for me anyway. This procedure was given to me by Apple Help Desk and it worked first time.
    Hope this helps a little.
    Best Regards

  • Seperate IP address for router?

    I am trying to connect Wi-Fi between my cell phone and computer.  To manually connect the two I must enter an IP address.  My computer IP ends in .2.  The IP address that my cell phone tells me to enter is .3.  Neither address wosrks to connect.  I have two Airport routers.  Do they also haved IP addresses, like .4and .5? Perhaps it is the IP addresss of the applicable router that I should be entering?  If so, how do I determine what the IPs are?

    Thank you for your reply.  They are both connected via Router A.  In fact, my cell phone says that it is connected.  But my Wi-Fi sycing app is not communcating.  The phone"s IP address is shown as unreachable on the app on my computer.  I have tried pinging, with no response. I have tried connecting my cell phone via cable to Router A  The app's technical support says it must be my network configuration that is the pronlem  My netwok consists only of my computer, my daughter's computer, my cell phone and two Airports.  My configuration works fine with my other Wi-Fi app (Router A), as well as my daughter's laptop (Router B).

  • Route or switch on the core Layer

                       I am working on a new network design for my company with four buildings, I have used building distribution method for all buildings, my design seems to be functioning properly, I have configured vlans and eigrp routing on the distribution switches as you can see on the diagram, but used the four core layer switches just for switching not routing and I did not configure any routing on them, I would like to know if this is good design or do I need to configure routing on the Core Layer as well

    There is no right or wrong answer to this. Originally the recommendation was to switch in the core ie. use only L2 because L2 switching as fast and L3 routing was slow.  But then L3 switches appreared and the recommendation was to use L3 to connect to the core.
    But both are just recommendations. You don't have to follow the guidelines slavishly.
    Having said that, looking at your design there are a lot of redundant paths between switches. This means lots of loops and using L2 will mean blocked paths in the core and potentially blocked paths to and from the core. If you used L3 connections from the distrbution to the core and between the cores you would be able to utilise all the links and hence get more bandwidth.
    In addition if a link failed you would not be reliant on STP to bring up a redundant path as all paths would be in use (although you should still run STP).
    Couple of other points -
    1) you have 4 switches in the core - what is the reasoning behind this ? is it distance limitations between buildings ?
    2) your addressing. Ideally you would want to be able to summarise from one building to the other so it would make more sense to have all the 192.168.x.x networks in one building and all the 10.x.x.x networks in the other. Actually it would make more sense to decide on an IP range ie. 10.x.x.x or 192.168.x.x (not both) and then use summarised ranges for each building.
    Jon

  • 3845 or 7600 for routing+switching design

    Hi there,
    I need to build a network architecture for 100 serveurs with 1 to 4 IP physical interfaces (10/100/1000 Eth.). Each interface belongs to different LAN/WAN/MAN, on each several VLAN have been created. The goal of this new design is to build a new switching/routing architecture. Question is simple: i've got to options 3845/3825 or 7600 routers ? But do i need to add switches before these routeurs as i'll need hundreds of ports ? How do i managed the connectivity between stacks of switches and the routeurs ? Thanks in advance for your info.

    Hi,
    Good Day!
    For your query, if you're looking for resiliency and high-availability since you seem to be setting up a server farm, you can use a Cat6500-E multi-layer switch (capable of both routing and switching). C7600 is also a good option but quite high end if these servers would be deployed to different sites. Most modules and controller cards can be used to both C7600 and Cat6500.
    Smaller routers would be beneficial for small nodes. You can use the 3800 series but you have to determine how many switch ports (module) you would require.
    If these are critical servers, always put in mind high-availability and reliability. Look for equipment that are designed for these and as much as possible eliminate single points of failure. Have a separate switch to aggregate all your servers, then use a router to route traffic to other nodes.
    Hope this helps.
    Regards,
    Albert

  • Switches for Access, Distribution, and Core Layer

    I have this case study in school and we are tasked to build a network in a school. So we've decided to use the three layer hierarchical model. I'm not sure about what switch is best for these layers but I've decided that I'll use 3750 for the Access layer, 4500E for the Distribution layer, 6500 for the Core layer. Are these the ideal switches for each layer? If not, could you suggest any switch that is better than the current? Need your suggestions or thoughts about this. Thanks in advance!

    Hi Seb, thanks for replying. My groupmates and I have already decided that we're going to have a distribution layer. So basically, is 3750 enough to be the backbone/core of the network? We're configuring the to have a Layer 3 design so that makes me choose on 3750 on distrib and core rathen than 2960 switches cause I think that's better than Layer 2 though I don't know specifically what makes it better. Do you know? So I could have a thorough explanation when I present it to my professor. As for the budget, the case study didn't give us any limit so I think layer 3 would be a better choice than layer 3. Thanks Sib, appreciate it.

  • Sinkhole routing rfc1918 on the core/distribution switch (6500)

    Hi guys,
    I am planning on getting rid of packets going to unrouted nonexistent rfc1918 networks in our DC environment going into internet facing firewall from our core/distribution switch via default route. I am thinking on setting a bunch of rfc1918 static routes to Null0 on the core/distro switches so they will kill all the packets destined to unused rfc1918 networks into Null0. Wondering if that would be a good solution to this.
    Thanks!

    I am not sure quite what you have in mind when you talk about a bunch of rfc1918 static routes. I could see doing a route for 10.0.0.0 range, for 172.16.0.0 range, and for 192.168.0.0 range. Is 3 a bunch? If you had more in mind what would they be?
    If you do static routes to Null0 for the summarized spaces then it would allow routing to any private addresses used inside your network to work since they should have more specific entries in your routing table and it would discard traffic with destination addresses in private address space. Be aware that if you have any site to site VPN tunnels from the firewall or any address translations on the firewall that use private addresses that your plan may very well have negative consequences for them.
    HTH
    Rick

  • Why assign IP addresses to router/switch interfaces?

    I get why I would ever want to assign a IP address to a router or switch, for remote login and IP for hosts to reach it. But why assign IP addresses to the interfaces? Is it so the router/switch knows which port to send the packet out? Route summation? But I thought they do that through the routing table, like " that address is out this port".
    So why would we ever need to assign IP addresses to specific port interfaces?

    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
    You normally assign IP addresses to L3 interfaces so other L3 devices have an IP address to forward traffic to.  (L2 IP address are generally only used for management.)
    Suppose you had Host (192.168.1.5/24) <> R1 <> R2 <> (192.168.2.8/24) Host, and you want the two hosts to intercommunicate.  How would you get this to work?
    You might started by providing interface IPs on the router interfaces facing the host, such as:
    Host (192.168.1.5/24) <> (192.168.1.1/24) R1 <> R2 (192.168.2.1/24) <> (192.168.2.8/24) Host
    You then configure "gateway" IPs on both hosts:
    Host (192.168.1.5/24 - GW 192.168.1.1) <> (192.168.1.1/24) R1 <> R2 (192.168.2.1/24) <> (192.168.2.8/24 - GW 192.168.2.1) Host
    Now each hosts "knows" to send all its off local subnet, traffic physically to the GW IP.  So, for example, if 192.168.1.5 want to sent to 192.168.2.8, it would forward the traffic to the GW IP, 192.168.1.1.  This is a example of why you want an IP on the router's L3 interface.
    Next we want R1 to forward the packet to R2, but it too needs a "next hop" IP address, so we assign addresses on the link between the two router, e.g.:
    Host (192.168.1.5/24 - GW 192.168.1.1) <> (192.168.1.1/24) R1 (192.168.3.1/24) <> (192.168.3.2/24) R2 (192.168.2.1/24) <> (192.168.2.8/24 - GW 192.168.2.1) Host
    R1 then needs to "know" where to send packets with an destination IP network of 192.168.2.0/24, in this case, it need to "know" to send the to IP 192.168.3.2.  When it does, R2, having and interface with 192.168.2.1, will also know 192.168.2.8 can be reached by sending the packet out that interface.
    Hopefully, the above will show why IP addresses on router L3 interfaces are needed.
    BTW, normally for the R1<>R2 link, you would assign a /30 or /31 network or you might use "unnumbered" interfaces (which "borrow" IPs from another interface).

  • I have an Airport Extreme as my router and am using time capsule to extend the network in my new house. My ISP is only providing me 4-5 ip addresses and wants me to set up my router to issue out new ip addresses for all my devices.How do I fix this?Help

    I have an Airport Extreme as my router and am using time capsule to extend the network in my new house. My ISP is only providing me 4-5 ip addresses and wants me to set up my router to issue out new ip addresses for all my devices.How do I fix this?Help.
    They said I need to change my settings to NAT settings. I haven't been able to figure out or find anything. I have also spoken to Apple Support on the phone for hours without being able to figure out how to do this ( i don't think he knew much either lol.) Please help me because I've got about 15-20 devices in my house that require to be connected to the internet and this is just making things ridiculously slow and painful for me.
    Thanks!

    It is on DHCP & NAT under router mode yet my isp is still the one issuing ip addresses to my devices instead of the router issuing them

  • Why does my Airport Express say "self assigned IP address"?  No IP address for the ethernet, and it is not connecting to my cable router any longer...

    Why does my Airport Express say "self assigned IP address"?  No IP address for the ethernet, and it is not connecting to my cable router any longer...

    Some cable providers.....like mine, a well known company......seem to take anywhere from a few moments to sometimes up to 30 minutes to allow their equipment back at the cable company to fully reset and issue a new fresh connection.
    So, it would not hurt to leave things powered down for 15-20 minutes or more when you perform the reset that John Galt suggests.

  • TS3988 I switched ISP so no longer have access to the email address for my iCloud account how do I change it. Why isn't it as easy as changing my Apple ID.?

    I switched ISP so no longer have access to the email address for my iCloud account how do I change it. Why isn't it as easy as changing my Apple ID.?

    Hi dawn192,
    Welcome to the Support Communities!
    The articles below may be able to help you with this issue.
    Click on the links to see more details and screenshots. 
    Frequently asked questions about Apple ID
    http://support.apple.com/kb/HT5622
    Apple ID: Changing your Apple ID
    http://support.apple.com/kb/HT5621?viewlocale=en_US
    Cheers,
    - Judy

Maybe you are looking for