for the Controlstation networking you can use /usr/sbin/traceroute

On the data mover unfortunately there isnt a traceroute - all you can do is server_ping
or look at the routes through "server_netstat server_x -r"

By looking at the interface counters with "server_netstat server_x -i" you can get at least
an idea which interfaces are actually used in- and outbound

when checking data mover routing dont forget that normally packet reflect is configured
so replies that the data mover sends for a client request dont use the routing table

see the following excerpt from the "Configuring and Managing Celerra Networking" manual:

Packet Reflect
Packet Reflect ensures that outbound (reply) packets always exit through the same
interface that inbound (request) packets entered. Since the majority of network
traffic on a Data Mover, including all file system I/O, is client-initiated, the Data
Mover uses Packet Reflect to reply to client requests. With Packet Reflect, there is
no need to determine the route to use to send the reply packets.

Packet Reflect works as follows:

◆ When Packet Reflect is enabled, the Data Mover doesn¿t examine the route and
ARP tables when sending outbound packets from established connections. The
Data Mover uses the same interface and the same next-hop MAC address as
the request.

◆ When Packet Reflect is disabled, the Data Mover examines the route and ARP
tables when sending outbound packets from established connections.

By default Packet Reflect is enabled.