I'm struggeling with something I think should be a very simple configuration.
I have my unified nodes configured on an out-of-band network for management functions (1GbE, 192.168.132.0/24, one host address for each node, and a VIP address for the active node). Now I've attached the 10GbE interfaces, and want to serve FTP and NFS trough these. So in the "Settings - Network - Public Networks" I define a new network:
subnet = 192.168.138.64/26
gateway = 192.168.138.65
Interface nodes IP address pool = 192.168.138.68, 192.168.138.69 (should there be more addresses here for any reason?)
Interface = ethX1 (10GbE)
This works fine if all nodes that are going to access this service lives in the same subnet, but unfortunately they don't. So how can I configure a static route to 192.168.1.0/24 to go over this same ethX1 interface, instead of trough the default gateway which is used for out-of-band management and various other infrastructure services (NTP, LDAP, ssh)?
This topic has been locked.
3 replies Latest Post - 2012-11-21T17:18:47Z by eJones
Pinned topic Network routes on the storwize unified ?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-21T17:18:47Z at 2012-11-21T17:18:47Z by eJones
janfrode 1000003QSC17 Posts
SystemAdmin 110000D4XK4779 PostsACCEPTED ANSWER
Re: Network routes on the storwize unified ?2012-11-20T08:48:07Z in response to janfrodeThis is available through the GUI. The "Additional gateways" list is the list of extra routes.
In your example this would be a new line in that list with:
- Subnet: 18.104.22.168/26
- IP Addresses: 192.168.138.65
eJones 120000AM5N5 PostsACCEPTED ANSWER
Re: Network routes on the storwize unified ?2012-11-21T17:18:47Z in response to janfrodeAre you running the v1.4.0 codelevel?
There are some interesting enhancements to network routing, according to the release_note_V3:
"In this Storwize V7000 Unified 22.214.171.124 release, improvements have been made to the back-end that configures public network routing.
Previously, for a given node that directly supports NAS functions, there was a limitation that only one network default route (or gateway of last resort) could be set on that node."
"The new function in this release will now apply additional default routes through policy routing technology.
After the upgrade, for any remote client connecting to a hosted IP for either Management (Service IP's or GUI) or Data, they will now have return routing provided by these new routing policies.
This addresses the single default route limit and allows for each network definition (Management, or each data network) to have their own default route within a given node."