An update to your organization's network security requirements document requires management traffic to be isolated in a non-default routing-instance. You want to implement this requirement on your…

Question

Options

• Aset routing--instances mgmtjunoa interface ge-0/0/0.0
• Bset routing--instances mgmt_junos interface em1
• Cset system management--instance
• Dset routing--instances mgmt_junos

• A
  10% (7)
• B
  4% (3)
• C
  85% (58)

Explanation

To isolate management traffic in a non-default routing-instance on Junos-based devices, you can use the set system management-instance and set routing-instances mgmt_junos commands. set system management-instance: This command associates the management interface (usually named fxp0 or em0 for Junos OS, or re0:mgmt-* or re1:mgmt-* for Junos OS Evolved) with the non- default virtual routing and forwarding (VRF) instance. After you configure the non-default management VRF instance, management traffic no longer has to share a routing table with other control traffic or protocol traffic. set routing-instances mgmt_junos: This command creates a new routing instance named mgmt_junos. The name of the dedicated management VRF instance is reserved and hardcoded as mgmt_junos; you cannot configure any other routing instance by the name mgmt_junos. Therefore, options C and D are correct. Options A and B are not correct because they attempt to assign an interface to the mgmt_junos routing instance, which is not necessary for isolating management traffic.

No community discussion yet for this question.