in bound management setup

[mariangcisco]

Hello, when I use setup command I can configure vsan 1 ip interface without a problem and sh ip route shows it like

Gateway of last resort is 10.1.3.1

C 192.168.1.0/24 is directly connected, vsan1

C 10.1.3.0/24 is directly connected, mgmt0

But I am not able to create such direct connection from CLI, can do only static route using ip route command. Any hint in that ? Thank you

[tblancha]

I am unsure what you mean by create such direct connection from CLI. I think what you're looking for is to have all devices in vsan 1 default gateway to the vsan1 IP address. You should have ip routing configured on the MDS as well. Then if the default gateway of the MDS is to 10.1.3.X, where X is the next hop router, then devices on vsan should be able to ping to this next hop address. This router should be advertising via a routing protocol the 192.168.1.0/24 address and have a static route for the 192.168.1.0/24 address via the MDS mgmt's IP address so other devices in the network will route properly.

[mariangcisco]

I would like to know how to create vsan ip interface and set routing for it so that it looks like the one I quoted. When I create interface in CLI it doesn't show up in 'sh ip route' and I can create only static route. I would like to see what commands are actualy used when I enter all parameters through setup command. I am in no way IP routing expert and when I create static route it just doesn't ping. When I set the same through setup command, it works :(

[tblancha · Accepted solution]

Ok, to config IP on a vsan is like this:

RTP9216# config t

Enter configuration commands, one per line. End with CNTL/Z.

RTP9216(config)# interface vsan 200

RTP9216(config-if)# ip address 192.168.1.1 255.255.255.0

RTP9216(config-if)# no shut

RTP9216(config-if)# exit

RTP9216(config)# exit

RTP9216# sh ip route

Codes: C - connected, S - static

Default gateway is 172.18.172.1

C 192.168.1.0/24 is directly connected, vsan200

C 172.18.172.0/24 is directly connected, mgmt0

To route between these subnets you should add: ip routing to the configuration as well.

[mariangcisco]

This is exactly what I did. But now when I know it was right I investigated a little more and found I got vsan 1 isolation when configured interface vsan 1.(funny, it ddin't happen when used setup) Did several shut/noshut etc and finaly it started to work. I will try it later on clean unconfigured box to find out what was wrong. Anyhow, thank you for your help.