Technical Documentation

M-series and MX-series Device Configuration Settings Supported in NSM

You can configure JUNOS software features in NSM. Although the configuration screens rendered in NSM look different than the JUNOS command-line interface (CLI), the top-level configuration elements mostly correspond to commands in the CLI.

Note: For detailed information about configuring specific features for M-series and MX-series devices, see the appropriate JUNOS software configuration guide.

Note: Because the NSM device-side configuration guides are not updated on the same release schedule as the JUNOS releases, consult the JUNOS Software Documentation for information about configuration settings that might occur in NSM and not in the device-side configuration guides or vice versa.

Table 1 provides a general guideline of the CLI hierarchy levels that are supported in the NSM configuration tree. For the exact parameters available, double-click the device in the Device Manager and select the Configuration tab. The configuration tree appears in the main display area with all parameters viewable or configurable from NSM.

Table 1: The JUNOS Configuration Hierarchy and the NSM Configuration Tree

Hierarchy Level

Available in the NSM Configuration Tree

edit access

Yes

edit accounting-options

Yes

edit applications

Yes

edit bridge domains

Yes

edit chassis

Yes

edit class-of-service

Yes

edit dynamic profiles

Yes

edit ethernet-switching-options

No

edit event-options

Yes

edit firewall

Yes

edit forwarding-options

Yes

edit groups

Yes

edit interfaces

Yes

edit logical-systems

Yes

edit multicast-snooping-options

Yes

edit poe

No

edit policy-options

Yes

edit protocols

Yes.

edit routing-instances]

Yes

edit routing-options

Yes

edit schedulers

No

edit security

Yes

edit services

Yes

edit snmp

Yes

edit switch-options

Yes

edit system

Yes

edit virtual-chassis

No

edit vlans

No

When you use NSM to edit the software configuration on the device, you initially make the changes to a device object that models the device in NSM. When you are satisfied with your configuration changes, you use the Update Device directive to push the configuration from the device object in NSM to the device itself. At that point, the edited configuration becomes active.

Note: If you import an existing device configuration, NSM automatically imports all objects defined in that configuration.

For more information about editing device configurations, using device templates, using configuration groups, and using configuration groups with templates, see “Configuring Devices” in the Network and Security Manager Administration Guide.


Published: 2009-08-23