On server A, you enter the following command to add a static route to serverA route -p add -host 192.168.1.101 192.168.1.101 -static. What is the purpose of this command?

Question

Options

• Ato temporarily bypass IP Filter rules
• Bto specify an IPMP target IP address to in.mpathd
• Cto specify routing to an adjacent network when in.rdisc is not used
• Dto specify routing to an adjacent network when in.routed is not used
• Eto ensure the IP address for serverB is not flushed from the ARP cache
• Fto optimize link aggregation using a direct connection between two systems

• A
  3% (1)
• B
  83% (24)
• C
  3% (1)
• E
  10% (3)

Explanation

Option B is correct because in Solaris, the in.mpathd daemon (which manages IP Network Multipathing / IPMP) needs probe target addresses to send ICMP echo requests to detect interface failures. The -static flag on a host route is specifically how Solaris signals to in.mpathd that this address should be used as a probe target - without it, in.mpathd ignores the route entirely.

Why the distractors are wrong:

• A - IP Filter (ipf) rules are managed via ipf/ipfstat, not the route command.
• C & D - Those describe adding a network gateway route when routing daemons aren't running, but this command adds a host (-host) route to itself, which makes no sense for network routing purposes.
• E - ARP cache is managed with arp, not route; the -static flag has no ARP implications.
• F - Link aggregation (trunking) is configured via dladm, not route.

Memory tip: Associate -static with IPMP probing by thinking: "STATIC routes are IPMP's stethoscope" - in.mpathd listens for failures by probing the host addresses marked with -static, so whenever you see a persistent host route pointing to itself, think IPMP probe target, not routing.

No community discussion yet for this question.