topic So is the P2P link going to in Routing and SD-WAN

how to redistribute static route into ospf

rfuentes1111 — Tue, 05 Mar 2019 11:36:51 GMT

HI Guys,

I need some help on this I want to redistribute static route into ospf, but i want to do it on a layer 3 switch which is connected to another cisco switch which is the vendor switch but i don't want them to see all my routes just the one that I want to distribut. I'm new on the routing but i.m familiar with the commands. I don't know if this can be possible to do on layer 3 switch.

here is my example.

interface Vlan2

ip address 192.168.193.1 255.255.255.0

interface Vlan3

ip address 192.168.100.1 255.255.255.0

router ospf 2

log-adjacency-changes

redistribute static subnets

network 192.168.193.0 0.0.0.255 area 0

network 192.168.100.0 0.0.0.255 area 0

network 150.150.150.0 0.0.0.0 area 0

ip classless

ip route 10.10.10.0 255.255.255.255 192.168.100.2

There are things about your

Richard Burts — Mon, 21 Mar 2016 18:49:54 GMT

There are things about your environment that we do not know and which might change our advice. But based on the limited information provided this might work. You might create a second OSPF process and in that second process you could put a network statement for the interface that connects to the vendor switch and then redistribute static into that second process. That way the vendor switch would see the redistributed switch but not the other OSPF routes.

HTH

Rick

Here is my company sw config

rfuentes1111 — Mon, 21 Mar 2016 20:10:56 GMT

Here is my company sw config but I'm not able to see the 0 E2 on the company switch or the vendor pc,

this is a project that working on and I don't want to share my routes but they need to be on our network.

also they will be doing inter vlan routing so we have to provide them with a subnet mask that meets that requirements to create 4 subnets any help I will a preciates.

Company sw

interface Vlan2

ip address 192.168.193.1 255.255.255.0

interface Vlan3

ip address 192.168.100.1 255.255.255.0

router ospf 2

log-adjacency-changes

redistribute static subnets

network 192.168.193.0 0.0.0.255 area 0

network 192.168.100.0 0.0.0.255 area 0

network 150.150.150.0 0.0.0.0 area 0

ip classless

ip route 10.10.10.0 255.255.255.255 192.168.100.2

Vendor SW

interface Vlan150
ip address 150.150.150.1 255.255.255.0
!
interface Vlan217
ip address 172.25.217.2 255.255.255.0
!
router ospf 2
log-adjacency-changes
network 10.10.10.0 0.0.0.0 area 0
!
ip classless
ip route 192.168.193.0 255.255.255.0 192.168.100.1

Rick's suggestion is the

Jon Marshall — Mon, 21 Mar 2016 20:41:11 GMT

Rick's suggestion is the right one.

You need another OSPF process on your switch so the vendor only sees the static route.

Do you have any clients in the 192.168.100.0/24 subnet or is that just used to connect to the vendor switch ?

The vendor switch configuration does not show an interface in the 192.168.100.x subnet, did you just not include it ?

Not sure what you are asking about the subnet mask ?

Please answer all of the above.

Jon

We are trying to do a point

rfuentes1111 — Mon, 21 Mar 2016 21:13:11 GMT

We are trying to do a point to point connection sorry I'm new into the routing portion trying to be detail as much as i can. The vendor is using a 3750x switch and need to connect to our network but we don't now where to do the termination if into our Core switch or to one of our IDF closets. We need to provide them with one sunbet mask then they will be doing inter vlan switching inside their own switches. I don't knof if i been help full on this.

interface Vlan2
ip address 192.168.193.1 255.255.255.0
!
interface Vlan3
ip address 192.168.100.1 255.255.255.0
!
router ospf 2
log-adjacency-changes
redistribute static subnets
network 172.25.193.0 0.0.0.255 area 0
network 172.25.217.0 0.0.0.255 area 0
network 10.10.10.0 0.0.0.0 area 0
!
ip classless
ip route 10.10.10.0 255.255.255.255 192.193.100.2

vendor sw

interface Vlan50
ip address 10.10.10.1 255.255.255.0
!
interface Vlan3
ip address 192.168.100.2 255.255.255.0
!
router ospf 2
log-adjacency-changes
network 150.150.150.0 0.0.0.0 area 0
!
ip classless

So is the P2P link going to

Jon Marshall — Mon, 21 Mar 2016 21:19:25 GMT

So is the P2P link going to use 192.168.100.0/24 ?

If so are there no end clients in that IP subnet ?

That is the key question really and if you can answer it we can provide a configuration for you.

Jon

In terms of where to

Jon Marshall — Mon, 21 Mar 2016 21:21:24 GMT

In terms of where to terminate it, you can terminate the link on a L2 or L3 switch but the configuration will be on the L3 switch.

So is the connection going directly to your L3 switch or not ?

Jon

Yes there is clients on 192

rfuentes1111 — Mon, 21 Mar 2016 21:27:39 GMT

Yes there is clients on 192.168.100.0/24 but when I do the test on a built lab which I have 3 cisco switch 3750 one the switches does not redistribute the static it will only show O not O E2.

Ye, is going to terminate on

rfuentes1111 — Mon, 21 Mar 2016 21:28:52 GMT

Ye, is going to terminate on a layer 3 switch

Okay, well you need to use a

Jon Marshall — Mon, 21 Mar 2016 21:35:27 GMT

Okay, well you need to use a new IP subnet for the P2P connection because you are going to use another OSPF process on your L3 switch and so you cannot have the 192.168.100.0/24 subnet in both processes.

If the link from the vendor switch is going to connect directly into your L3 switch then you just need a /30 IP subnet for the link.

As an example using 192.168.3.0 255.255.255.252 (but you can use anything), on your L3 switch -

int <x/y> <--- this connects to vendor switch
no switchport
ip address 192.168.3.1 255.255.255.252

router ospf 3 <-- this is in addition to your other OSPF process ie. it is not a replacement
network 192.168.3.0 0.0.0.3 area 0
redistribute static subnets

then give the vendor the IP address 192.168.3.2 with the correct subnet mask.

Jon

Can you be clear about which

Richard Burts — Mon, 21 Mar 2016 21:37:11 GMT

Can you be clear about which switch in your lab is doing redistribution and where you are looking for the O E2 route? You will not see O E2 on the router that is doing redistribution but will see O E2 on the neighbor router to which it is advertised (the vendor router in this case).

HTH

Rick

Can you provide a

rfuentes1111 — Mon, 21 Mar 2016 21:42:16 GMT

Can you provide a configuration so i can see it i will appreciate that thank you

Before you do that in your

Jon Marshall — Mon, 21 Mar 2016 21:42:37 GMT

Before you do that in your lab can you be specific about what subnets you want advertised and where.

Your diagram suggests the vendor is using 10.10.10.0/24 but your latest configuration doesn't.

What do you want to advertise to the vendor and what subnets is the vendor using ?

Do you have any control over the vendor switches in terms of configuration ?

Jon

Rick

Jon Marshall — Mon, 21 Mar 2016 21:45:22 GMT

Rick

I am getting a bit confused myself.

Your idea is the right one I think but I am unclear what should be advertised where.

The configuration posted below will advertise to the vendor but obviously the vendor's networks need to be advertised back and I'm not sure where they need to be propagated within the network.

Apologies for confusing the issue.

Jon

Can this be done if they use

rfuentes1111 — Mon, 21 Mar 2016 21:50:37 GMT

Can this be done if they use a layer 3 switch as well on they need to do it on a router. We need to get this done on a switchport not on a router port because they need to be on a specific vlan.

I did, at the end of this

Jon Marshall — Mon, 21 Mar 2016 21:51:46 GMT

I did, at the end of this thread but it is not clear at the moment what you want to advertise where.

What exactly are you trying to advertise to the vendor ie. you are using a static pointing to which subnet and where is that subnet in relation to your L3 switch ?

And what subnet is the vendor using.

Bear in mind if you advertise a static to the vendor then wherever that subnet is the L3 devices in your network need to know how to get back to the vendor subnet so you need to advertise that as well.

Jon

Why do they need to be on a

Jon Marshall — Mon, 21 Mar 2016 21:54:29 GMT

Why do they need to be on a vlan ?

If it is a Cisco switch you can simply use L3 routed ports.

Before you do anything can you read the thread again especially the recent posts because it is not clear what you are trying to do.

You want to advertise a static route into OSPF for the vendor.

What is that static route and where does it point to ?

What subnet is the vendor using and how are you going to advertise that subnet in your network ?

Jon

we are not going to have any

rfuentes1111 — Mon, 21 Mar 2016 21:54:59 GMT

we are not going to have any control on the vendor configuration we are only providing the connection and a sunbet mask for 1000 systems this is for future grow.

Jon

Richard Burts — Mon, 21 Mar 2016 21:57:49 GMT

Jon

No apology needed. I agree that the issue is confused but you are not providing the confusion. The confusion is that we have gone back and forth between the live environment and a lab environment and because there have been confusing statements about the topology of the network and lack of clarity about what needs to be advertised to whom. So I suggest that first of all that we focus on the lab environment and worry about the live environment after the lab is working.

I think it would be very helpful if the original poster would post a new diagram which clearly identifies which switch is his company switch, which switch is the vendor switch, and what subnet is on what interface. Then a clear description of what needs to be advertised from his switch to the vendor and what needs to be advertised from the vendor to him and clarifying about what is redistributed.

HTH

Rick

I do not know what you are

Jon Marshall — Mon, 21 Mar 2016 21:59:09 GMT

I do not know what you are trying to do to be honest.

I thought I did but the more I ask the more confused I get.

Trying to help but can't really unless you provide a full explanation of exactly what you want to do in terms of network layout, IP addressing etc.

Jon