Juniper Networks M10, M5 Document Organization, Documentation Conventions, General Conventions

Documentation Conventions

network configuration. Any detailed discussion of these concepts is beyond the scope of this manual.

Document Organization

This manual is divided into several parts:

•Preface "About This Manual" (this chapter), provides a brief description of the contents and organization of this manual and describes how to contact customer support.

•Part 1, "Product Overview," provides an overview of the router, describing its hardware components, the JUNOS Internet software, and the system architecture.

•Part 2, "Initial Installation," describes how to prepare your site for router installation, and how to unpack, install, and power on the router. It describes requirements and specifications for the installation site, power source, rack, wiring, and cabling. It also provides detailed safety guidelines and warnings.

•Part 3, "Hardware Maintenance, Replacement, and Troubleshooting Procedures," describes how to maintain, replace, and troubleshoot router components.

This manual also contains a complete index.

Documentation Conventions

General Conventions

This manual uses the following text conventions:

•Router and router component labels are shown in a sans serif font. In the following example, ETHERNET is the label for the Ethernet management port on the router:

The 10/100-Mbps Ethernet RJ-45 connector is used for out-of-band management of the router and is labeled ETHERNET.

•Statements, commands, filenames, directory names, IP addresses, and configuration hierarchy levels are shown in a sans serif font. In the following example, stub is a statement name and [edit protocols ospf area area-id]is a configuration hierarchy level:

To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level.

•In examples, text that you type literally is shown in bold. In the following example, you type the words show chassis alarms:

For example, you can use the following command to get information about the source of an alarm condition:

user@host> show chassis alarms

xviM5 and M10 Internet Routers Hardware Guide