There are two forms of the command to create a static route:
IP ROUTE a.b.c.d m.m.m.m ga.gb.gc.gd
IP ROUTE a.b.c.d m.m.m.m interface
In the first instance, you provide the net/subnet (and mask) of the target network (a.b.c.d m.m.m.m) the next hop address (ga.gb.gc.gd) and an optional metric (for cases when you want a "floating static" to cover a path in case the primary link drops, for example).
The router determines the interface automatically, based on the interface's address ... the "next hop" would be in the same net/subnet as the router's egress interface.
In the second instance, you explicitely tell the router to send all traffic for the target net/subnet out a particular interface (and an optional metric, for the same reasons as the first instance).
The router doesn't know or care what's on the other side ... you have directed it to pump all the traffic for a.b.c.d with a mask of m.m.m.m to the specified interface ... .whether it's valid or not, that's where the traffic will go.
The advantage of one over the other relates to how the routing table reacts when the path becomes invalid, I believe.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...