Access different subnet through management

[hpatel23]

I have a Cisco ISR4451-X/K9. I set up interface GigabitEthernet0/0/1.1, secondary IP address as 10.19.194.1/24. I am connected to two nodes in a mesh connection with one port with IP 10.19.194.50 on first node connected to router and another port on first node with IP 10.19.193.2/24 which is part of different subnet. 

On the cisco router I added a static route that has destination as 10.19.193.0/24 with next hop as IP 10.19.194.50. And I am able to ping 10.19.193.2 from cisco router. But if the port with 10.19.193.2/24 is connected to port on second node with IP 10.19.193.3/24, I am not able to pin 10.19.193.3 from Cisco router. 

What are the configuration that I need to have on Cisco router to access a different subnet thats not part of the cisco router? 

[Flavio Miranda]

Got confuse, would help if you draw a simple topology but it seems to me that will not work this way.  Actually, you dont need the static router if the interface is directly connected. 

If the three devices are routing and you want to create a physical full mesh topology, you need to use differentes ports. 

You can use subinterfaces, which will be a logical full mesh topology but this will required a layer 2 device in the midle with trunk.

[hpatel23]

Hi Flavio,

Sorry for the confusion. Please see diagram attached. 

Node 1 and Node 2 are not routers but they are WDM devices having routing capabilities. My question is that I am able to access Node 1 since it is been connected directly to the cisco router and set as its default gateway. And I have added following static route on the cisco router: 

ip route 10.19.193.0 255.255.255.0 10.19.194.50

So with the help of that static route I am able to access Node 1 using 10.19.193.2 IP address as well. But I am not able to access Node 2. What else do I need to configure on the cisco router so that it is able to reach 10.19.193.3 IP address. 

Node 1 and Node 2 are able to ping each other. Also, Node 2 can ping Cisco router. But for some reason cisco router can't ping Node 2. 

[Flavio Miranda]

Node 1 needs to have routing capability and forward traffic to router when Node 2 tries to reach the router.

Node 1 is actually a router as it is in netween two networks and need to act as such.

[hpatel23]

Node 1 and Node 2 both have routing capabilities. Both are able to ping each other. Default gateway set on Node 1 is 10.19.194.1 while there is no default gateway set on Node 2.  Configuration between Node 1 and Node 2 is good. Their routing tables are up to date and able to discover each other. 

There is a static route on Node 2 as well :

ip route 10.19.194.0 255.255.255.0 10.19.193.2

But router is still not able to ping 10.19.193.3

What are my options from router perspective? 

[Flavio Miranda]

Can you share more details about those device? They are DWDM, rith? which vendor and model?

[hpatel23]

Node 1 and Node 2 are ADVA FSP3000 C Optical device. 

[Flavio Miranda]

On the Data Sheet they mention:

OSPF-based DCN routing and constraint-based traffi c routing

Just for curiosity, could you enable OSPF on those boxes and router? 

[Georg Pauwen]

Hello,

--> Node 1 and Node 2 are not routers but they are WDM devices having routing capabilities.

What devices are these exactly ? Are they Windows based ? Can you post a picture ?

[hpatel23]

Node 1 and Node 2 are ADVA F8 devices. They are able to see each other fine. I am trying to access Node 2 without setting the default gateway and use a different subnet other than the one set for Node 1. I have picture attached. And trying to access 10.19.193.3 from the cisco router but its not pinging. 

[Georg Pauwen]

Hello,

I did some research but could not find anything on how to configure these boxes. So what does the configuration of these F8 devices look like ?

[hpatel23]

For a F8 device, there is one port that is connected to a switch. In our case on Node 1 that port is connected to the router with default Gateway set to 10.19.194.1/24 and IP address 10.19.194.50. Also through back plane there are two other ports on the device where you can you set up management access. And from that, one port which is P2 connected to Node 2 and the IP has been set to 10.19.193.2/24 which is completely different subnet. 

Proxy ARP set to false on both the nodes. 

Node 1 routes: 

ipv4-routes table:

destination-ip-address/mask next-hop interface metric protocol status
0.0.0.0/0 10.19.194.1 P1 10 static route-status-active
10.19.193.0/24 0.0.0.0 P2 0 connected route-status-active
10.19.194.0/24 0.0.0.0 P1 0 connected route-status-active

Node 2 routes: 

ipv4-routes table:

destination-ip-address/mask next-hop interface metric protocol status
10.19.193.0/24 0.0.0.0 P2 0 connected route-status-active
10.19.194.0/24 10.19.193.12 P2 20 static route-status-active

Cisco Router Config:

On Interface: 

ip address 10.19.194.1 255.255.255.0 secondary

Route added: 
ip route 10.19.193.0 255.255.255.0 10.19.194.50

[Jon Marshall]

On node 2 is the next hop IP for 10.19.194.0/24 meant to be 10.19.193.12 (or 10.19.193.2) ? 

Jon

[hpatel23]

@Jon Marshall  Next Hop IP is 10.19.193.2 

[Jon Marshall]

No problem, just checking as the configuration you posted shows 10.19.93.12 that's all. 

Jon