Wired Intelligent Edge

last person joined: 17 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

IP routing

This thread has been viewed 7 times
  • 1.  IP routing

    Posted Oct 05, 2018 03:14 PM

    I have below routes on a layer 3 switch, can you tell me what this means and how it works:

     

    ip route 0.0.0.0 0.0.0.0 10.10.10.1

    ip route 10.10.20.0 255.255.255.0 10.10.10.30

    ip route 10.10.30.0 255.255.255.0 10.10.10.30

    ip route 10.10.40.0 255.255.255.0 10.10.10.30

    ip route 10.10.50.0 255.255.255.0 10.10.10.30

     

    As 0.0.0.0 0.0.0.0 has default gateway to 10.10.10.1, how the below routes will work? What they do?



  • 2.  RE: IP routing

    Posted Oct 05, 2018 03:22 PM

    They only indicate the next router to get all the networks mentioned.

    e.g:

    ip route 10.10.20.0 255.255.255.0 10.10.10.30

    Means if you want to get to network 10.10.20.X, the packet must be routed thru gateway 10.10.10.30

     

    The same idea for the other static routes

     

    The default route is used when you want to get to other networks different from 10.10.20.x, 10.10.30.x, 10.10.40.x and 10.10.50.x,

    Regards

    Pedro

     

    PS: If this helps, do not forget to give me some kudos



  • 3.  RE: IP routing

    Posted Oct 05, 2018 03:43 PM

    Let say I have below scenario, how to setup routes:

     

    CoreSW is the main Core at HQ which is connected to the firewall and going out to the internet. So it has ip route 0.0.0.0 0.0.0.0 10.10.10.2(fw)

     

    CoreSW ip is 10.10.10.1/24

    The vlans are:

    vlan 3(data): 10.10.3.1/24

    vlan 4(voice): 10.10.4.1/24

    vlan 5(security): 10.10.5.1/24

     

    There are 5 campus locations with below MDF and IPs:

    C1MDF1 - 10.10.10.11

    C2MDF1 - 10.10.10.12

    C3MDF1 - 10.10.10.13

    C4MDF1 - 10.10.10.14

    C5MDF1 - 10.10.10.15

     

    All 5 campus MDF connected to the CoreSW at HQ, so it is hub and spoke topology. Can you list the IP route statements for the core and all 5 campus swithes?

     

    Thanks.

     



  • 4.  RE: IP routing

    Posted Oct 05, 2018 03:54 PM

    It will depend on the distribution of your routers towards each of the 5 MDFs.

    I need s  picture of your topology.

    You say there are 5 remote sites, one for a MDF, right?, if so, there should be 5 different networks for each MDF, and in your deployment, all MDFs seem to be in the same network: 10.10.10.X ... it is important to define the mask of each network for each MDF.

    How do you connect each remote site to the HQ ?

    Topology would help do define the static routes yoe need

    Regards

     

    Pedro

     

    PS: I sent you an internal message, read your inbox



  • 5.  RE: IP routing

    Posted Oct 05, 2018 04:16 PM

    Yes all the remote site MDF's should point to the CoreSW at HQ



  • 6.  RE: IP routing

    Posted Oct 05, 2018 04:58 PM

    What is the IP address (IP and mask) of the local router (in HQ) that leads to the five remote sites where the MDFs are?

    Please, send me the mask of the IP adresses of your 5 MDFs.



  • 7.  RE: IP routing

    Posted Oct 12, 2018 11:01 AM

    CoreSW IP: 10.10.10.1/24

    all campus sw MDF mask is /24