256 OS CLI User Guide For Junos OS - Juniper

2y ago
17 Views
2 Downloads
1.57 MB
495 Pages
Last View : 2m ago
Last Download : 2m ago
Upload by : Asher Boatman
Transcription

Junos OSCLI User Guide for Junos OSPublished2021-12-14

iiJuniper Networks, Inc.1133 Innovation WaySunnyvale, California 94089USA408-745-2000www.juniper.netJuniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc.in the United States and other countries. All other trademarks, service marks, registered marks, or registered servicemarks are the property of their respective owners.Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the rightto change, modify, transfer, or otherwise revise this publication without notice.Junos OS CLI User Guide for Junos OSCopyright 2021 Juniper Networks, Inc. All rights reserved.The information in this document is current as of the date on the title page.YEAR 2000 NOTICEJuniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-relatedlimitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.END USER LICENSE AGREEMENTThe Juniper Networks product that is the subject of this technical documentation consists of (or is intended for usewith) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User LicenseAgreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using suchsoftware, you agree to the terms and conditions of that EULA.

iiiTable of ContentsAbout This Guide xiv1OverviewAbout the CLI Guide 2CLI Overview 2Introducing the Command-Line Interface 3CLI Modes, Commands, and Statement Hierarchies—An Overview 5Other Tools to Configure and Monitor Juniper Networks Devices 7Configure Junos OS in a FIPS Environment 72Getting StartedGetting Started: A Quick Tour of the CLI 10Get Started with the Command-Line Interface 10Switch Between Operational Mode and Configuration Mode 12Use Keyboard Sequences to Navigate and Edit the CLI 14Configure a User Account on a Juniper Networks Device 16Use the CLI Editor in Configuration Mode 19Check the Status of a Juniper Networks Device 22Roll Back Configuration Changes 25Configure a Routing Protocol 27Shortcut 28Longer Configuration 28Make Changes to a Routing Protocol Configuration 31Online Help in the CLI 35Get Online Help from the Command-Line Interface 35CLI Online Help Features 39CLI Explorer Overview 41

ivCLI Environment Settings 42Customize the CLI Environment 42Set the CLI Screen Length and Width 46Enable Configuration Breadcrumbs 473Using Configuration Statements to Configure a DeviceCLI Configuration Mode Overview 51Understanding CLI Configuration Mode 51Enter and Exit CLI Configuration Mode 58Relative Configuration Mode Commands 61Command Completion in Configuration Mode 61Notational Conventions Used in Configuration Hierarchies 64Overview of the Configure Command 65Forms of the configure Command 65How to Use the configure Command 67How to Use the configure exclusive Command 68How to Work with the Correct Configuration 71Modify the Configuration of a Device 71Display Users Currently Editing the Configuration 72How to Modify the Juniper Networks Device Configuration 73How to Add Configuration Statements and Identifiers 74How to Delete a Statement from a Device Configuration 76Example: Delete a Statement from the Device Configuration 79Copy a Statement in the Configuration 81Example: Copy a Statement in the Configuration 81Requirements 81Overview 82Configuration 82

vExample: Replace a Configuration 85Requirements 85Overview 85Configuration 86Insert a New Identifier in a Device Configuration 92Example: Insert a New Identifier in a Device Configuration 92Requirements 93Overview 94Configuration 94Deactivate and Reactivate Statements and Identifiers in a Device Configuration 97Example: Deactivate and Reactivate Statements and Identifiers in a Device Configuration 98Requirements 98Overview 98Configuration 98How to Make Global Changes in the Device Configuration 100Common Regular Expressions to Use with the replace Command 101Example: How to Use Global Replace in a Device Configuration—the \n Back Reference 103Requirements 103Overview 104Configuration 105Example: Global Replace in a Device Configuration—Replacing an Interface Name 106Requirements 107Overview 107Configuration 107Example: Global Replace in a Device Configuration—the upto Option 109Add Comments in a Device Configuration 112Add Comments in the CLI 112Add Comments in a File 113Example: Include Comments in a Device Configuration by Using the CLI 114Requirements 115

viOverview 115Configuration 116Use Configuration Groups to Quickly Configure Devices 118Configuration Groups Overview 119Create a Configuration Group 120How to Apply a Configuration Group 122Example: Create and Apply Configuration Groups 123Example: Disable Inheritance of a Configuration Group 125Example: Use the junos-defaults Configuration Group 127Example: Use Wildcards with Configuration Groups 128How to Improve Commit Time When Using Configuration Groups 131Example: Configure Sets of Statements with Configuration Groups 132Example: Configure Interfaces Using Configuration Groups 134Example: Use Configuration Groups to Configure a Consistent IP Address for the ManagementInterface 137Example: Use Configuration Groups to Configure Peer Entities 138Example: Use Configuration Groups to Establish Regional Configurations 140Example: Configure Wildcard Configuration Group Names 142Example: Reference the Preset Statement from the Defaults Group 144Example: View Default Statements That Have Been Applied to the Configuration 145Set Up Routing Engine Configuration Groups 145How to Use Conditions to Apply Configuration Groups 148Example: Configure Conditions for Applying Configuration Groups 148Requirements 148Overview 148Configuration 149View the Configuration 152Display the Current Configuration 152

viiExample: Display the Current Configuration 154Display Additional Information About the Configuration 155Display set Commands from the Configuration 159Verify the Device Configuration 161Commit the Configuration 162The Commit Model for Configurations 162Commit a Device Configuration 164Commit Operation When Multiple Users Configure the Software 165Commit Preparation and Activation Overview 166Commit Device Configurations in Two Steps: Preparation and Activation 168Activate a Device Configuration with Confirmation 170Schedule a Commit Operation 171Monitor the Commit Process 173Add a Comment to Describe the Committed Configuration 174Batch Commits Overview 175Example: Configure Batch Commit Server Properties 176Requirements 176Overview 176Configuration 177Verification 180Back Up the Committed Configuration on the Alternate Boot Drive 1874Managing ConfigurationsConfiguration Files Overview 189Configuration Files Overview 189Device Configuration Storage Overview 191Managing Configurations 191The show compare display xml Command Output 192

viiiReturning to the Most Recently Committed Configuration 201Returning to a Previously Committed Configuration 202Example of Returning to a Previous Configuration 202Example of Displaying Previous Configurations 202About Comparing Configuration Versions 204Saving a Configuration to a File 206About Compressing the Current Configuration File 207Free Up System Storage Space 209Clean Up Files with the CLI 210Autoinstallation of Configuration Files Overview 212Configuration File Autoinstallation—An Overview 212Configuring Autoinstallation of Configuration Files (CLI Procedure) 215Loading Configuration Files 217Examples for Loading a Configuration from a File or the Terminal 218How Character Encoding Works on Juniper Networks Devices 221About Specifying Statements and Identifiers 222About Loading a Configuration from a File 227Upload a Configuration File 230Backing Up Configurations to an Archive Site 231Configuring the Transfer of the Currently Active Configuration 231Factory Default Configuration Overview 233Restore the Default Factory Configuration 234Rescue Configuration 235Creating and Returning to a Rescue Configuration 235Encrypt and Decrypt Configuration Files 236Encrypt Configuration Files 237Decrypt Configuration Files 238

ixModify the Encryption Key 239Synchronizing Configurations Across Routing Engines 240Routing Engine Synchronization Overview 240Configure Multiple Routing Engines to Synchronize Committed Configurations Automatically 2445Using Operational Commands to Monitor DevicesCLI Operational Mode Overview 248CLI Operational Mode Command Overview 248Display Options of the show Command—An Overview 251Interface Naming Conventions Used in Operational Commands 252About Group Interface Names Using Wildcard Characters 254Using Operational Commands to Monitor a Device 255CLI Command Completion Example 256Operational Mode Commands: Overview of Controlling the Scope 257Viewing Files and Directories on a Device 259Directories on the Device 259List Files and Directories 260Filenames and URLs 263Display Operating System Information 265Managing Programs and Processes Using Operational Mode Commands 265Show Software Processes 266Restart the Software Process 267Stop the Software 268Reboot the Software 269CLI Comment Character # for Operational Mode Commands 270Filtering Operational Command Output 271About Using the Pipe ( ) Symbol to Filter Command Output 271Example: Use Regular Expressions with the Pipe ( ) Symbol to Filter Command Output 272Example: Pipe ( ) Filter Functions in the Command-Line Interface 274

xFilter Operational Mode Command Output in a QFabric System 2886Configuration Statementsapply-groups 292apply-groups-except 293archival 295autoinstallation 297commit activate 299commit prepare 301export-format 303groups 305no-hidden-commands 309server (Batch Commits) 311synchronize 313traceoptions (Batch Commits) 3167CLI Commandsactivate 322annotate 323clear log 325clear system commit 327clear system commit prepared 330commit 332configure 339copy 342deactivate 343delete 345

xiedit 347exit 348file 350help 351insert 353load 355 (pipe) 358protect 363quit 365rename 366replace 368request 370request system commit server pause 372request system commit server queue cleanup 374request system commit server start 376request system configuration rescue delete 377request system configuration rescue save 379restart 381rollback 398run 400save 401set 404set cli complete-on-space 406set cli directory 408set cli idle-timeout 409

xiiset cli prompt 411set cli restart-on-upgrade 413set cli screen-length 415set cli screen-width 416set cli terminal 418set cli timestamp 420set date 422show 424show cli 425show cli authorization 428show cli directory 434show cli history 435show configuration 436show display inheritance 441show display omit 444show display set 446show display set relative 448show groups junos-defaults 450show system commit 452show system commit server queue 457show system commit server status 462show system configuration archival 464show system configuration rescue 466show system rollback 468status 471

xiiitest configuration 472top 474unprotect 475up 477update 478wildcard delete 480

xivAbout This GuideThe Junos OS command-line interface (CLI) is a command shell specific to Juniper Networks. Thiscommand shell runs on top of the FreeBSD UNIX-based operating system kernel for Junos OS. Usingindustry-standard tools and utilities, the CLI provides a powerful set of commands that you can use tomonitor and configure Juniper Networks devices running Junos OS. This guide contains informationabout the CLI for Junos OS.RELATED DOCUMENTATIONDay One: Exploring the Junos CLIDay One: Junos for IOS Engineers

1CHAPTEROverviewAbout the CLI Guide 2CLI Overview 2

2About the CLI GuideThe Junos OS CLI Guide explains how to use the command-line interface (CLI). This guide also describesadvanced concepts and device configuration when working with Juniper Networks devices runningJunos OS.In this guide, you will learn about: Using configuration statements to configure network devices Managing device configurations Using operational commands to monitor devices Syntax for configuration statements, operational commands, and environmental commandsFor a basic introduction to Junos OS, see the Getting Started Guide for Junos OS. It provides a high-leveldescription of Junos OS, describes how to access devices, and provides simple step-by-step instructionsfor initial device configuration.For a technical and detailed exploration of Junos OS, see the Overview for Junos OS. It further explainshow Junos OS works and describes the security, configuration, monitoring, and management of networkdevices.Another useful learning resource is Day One: Exploring the Junos CLI.CLI OverviewIN THIS SECTIONIntroducing the Command-Line Interface 3CLI Modes, Commands, and Statement Hierarchies—An Overview 5Other Tools to Configure and Monitor Juniper Networks Devices 7Configure Junos OS in a FIPS Environment 7

3The CLI is the software interface used to access your device. You use the CLI to configure the device,monitor its operations, and adjust the configuration as needed. You access the CLI through a consoleconnection interface or through a network connection.Introducing the Command-Line InterfaceIN THIS SECTIONKey Features of the CLI 3The Junos OS CLI is a command shell specific to Juniper Networks that runs on top of the operatingsystem kernel. Through industry-standard tools and utilities, the CLI provides a powerful set ofcommands that you can use to monitor and to configure devices running Junos OS.The CLI has two modes: Operational mode—Use this mode to display the current status of the device. In operational mode,you enter commands to monitor and to troubleshoot the network operating system, devices, andnetwork connectivity. Configuration mode—Use this mode to configure the device. In this mode, you enter statements toconfigure all properties of the device, including interfaces, general routing information, routingprotocols, user access, and several system and hardware properties. Junos OS stores a configurationas a hierarchy of configuration statements.When you enter configuration mode, you are viewing and changing a file called the candidateconfiguration. You use the candidate configuration file, you make configuration changes withoutcausing operational changes to the current operating configuration, called the active configuration.The device does not implement the changes you added to the candidate configuration file until youcommit the changes. Committing the configuration changes activates the revised configuration onthe device. Candidate configurations enable you to alter your configuration without damaging yourcurrent network operations.Key Features of the CLIThe CLI commands and statements follow a hierarchical organization and have a regular syntax. The CLIprovides the following features to simplify CLI use:

4 Consistent command names—Commands that provide the same type of function have the samename, regardless of the specific device type on which you are operating. For example, all showcommands display software information and statistics, and all clear commands erase various types ofsystem information. Lists and short descriptions of available commands—The CLI provides information about availablecommands t each level of the command hierarchy. If you type a question mark (?) at any level, yousee a list of the available commands along with a short description of each. This means that if you arealready familiar with Junos OS or with other routing software, you can use many of the CLIcommands without referring to the documentation. Command completion—Command completion for command names (keywords) and for commandoptions is available at each level of the hierarchy. To complete a command or option that you havepartially typed, press the Tab key or the Spacebar. If the partially typed letters begin a string thatuniquely identifies a command, the complete command name appears. Otherwise, a beep indicatesthat you have entered an ambiguous command, and the CLI displays possible completions.Completion also applies to other strings, such as filenames, interface names, usernames, andconfiguration statements.If you have typed the mandatory arguments for executing a command in operational mode orconfiguration mode, the CLI displays [Enter] as one of the choices when you type a question mark(?). This output indicates that you have entered the mandatory arguments and can execute thecommand at that level without specifying any further options. Likewise, the CLI also displays [Enter] when you reach a specific hierarchy level in the configuration mode and do not need to enter anymore mandatory arguments or statements. Industry-standard technology—With FreeBSD UNIX as the kernel, a variety of UNIX utilities areavailable on the CLI. For example, you can: Use regular expression matching to locate and to replace values and identifiers in a configuration,to filter command output, and to examine log file entries. Use Emacs-based key sequences to move around on a command line and scroll through therecently executed commands and command output. Store and archive Junos OS device files on a UNIX-based file system.Use standard UNIX conventions to specify filenames and paths.Exit the CLI environment and create a UNIX C shell or Bourne shell to navigate the file system,manage router processes, and so on.

5CLI Modes, Commands, and Statement Hierarchies—An OverviewIN THIS SECTIONCLI Command Hierarchy 5Configuration Statement Hierarchy 5Move Among Hierarchy Levels 6The Junos OS CLI commands and statements are organized under two command modes and varioushierarchies. The following sections provide an overview of the CLI command modes and the commandand statement hierarchies.CLI Command HierarchyCLI commands are organized in a hierarchy. Commands that perform a similar function are groupedtogether under the same level of the hierarchy. For example, all commands that display informationabout the system and the system software are under the show system command. All commands thatdisplay information about the routing table are under the show route command.To execute a command, enter the full command name, starting at the top level of the hierarchy. Forexample, to display a brief view of the routes in the routing table, use the command show route brief.Configuration Statement HierarchyThe configuration statement hierarchy has two types of statements: Container statements, which arestatements that contain other statements, and leaf statements, which do not contain other statements.All the container statements and leaf statements together form the configuration hierarchy.The following illustration shows a part of the hierarchy tree. The protocols statement is a top-levelstatement at the trunk of the configuration tree. The ospf, area, and interface statements are allsubordinate container statements of a higher statement; that is, they are branches of the hierarchy tree.The hello-interval statement is a leaf on the tree.Figure 1: Configuration Statement Hierarchy Example

6Move Among Hierarchy LevelsThe following table shows the CLI commands you use to navigate the levels of the configurationstatement hierarchy.Table 1: CLI Configuration Mode Navigation CommandsCommandDescriptionedit hierarchy-levelMoves to an existing configuration statement hierarchy or creates a hierarchy and movesto that level.exitMoves up the hierarchy to the previous level where you were working. This command is,in effect, the opposite of the edit command. Alternatively, you can use the quit command.The exit command and the quit command are interchangeable.upMoves up the hierarchy one level at a time.topMoves directly to the top level of the hierarchy.

7Other Tools to Configure and Monitor Juniper Networks DevicesApart from the CLI, Junos OS also supports the following applications, scripts, and utilities that enableyou to configure and monitor Juniper Networks devices: J-Web GUI—Available on select Juniper Networks devices, the J-Web GUI enables you to monitor,configure, troubleshoot, and manage the device by means of a browser with HTTP or HTTPSenabled. For more information, see the J-Web Interface User Guide. Junos XML management protocol—The Junos XML management protocol enables you to monitorand configure Juniper Networks devices. Juniper Networks provides a Perl module with the API tohelp you more quickly and easily develop custom Perl scripts for configuring and monitoring devices.For more information, see the Junos XML Management Protocol Developer Guide. NETCONF API—You can also use the NETCONF XML management protocol to monitor andconfigure Juniper Networks routers. For more information, see the NETCONF XML ManagementProtocol Developer Guide. Junos OS commit scripts and self-diagnosis features—You can define scripts to enforce customconfiguration rules, use commit script macros to provide simplified aliases for frequently usedconfiguration statements, and configure diagnostic event policies and actions associated with eachpolicy. For more information, see the Junos OS Automation Scripting User Guide. MIBs—You can use enterprise-specific and standard MIBS to retrieve information about the hardwareand software components on a Juniper Networks device. For more information about MIBs, see theJunos OS Network Management Administration Guide for Routing Devices.Configure Junos OS in a FIPS EnvironmentWith Junos-FIPS you can configure a network of Juniper Networks devices in a FIPS 140-2environment.The Junos-FIPS software environment requires the installation of FIPS software by a Crypto Officer. InJunos-FIPS, some Junos OS commands and statements have restrictions and some additionalconfiguration statements are available. For more information, see the following resources: Common Criteria and FIPS Certifications—Provides links to guidelines for configuring JuniperNetworks devices so the secure environment complies with the requirements of public sectorcertifications such as Common Criteria and FIPS certification. Compliance Advisor—A Web application that provides regulatory compliance information aboutCommon Criteria, FIPS, Homologation, ROHS2, and USGv6 for Juniper Networks products.

8SEE ALSOIPsec Requirements for Junos-FIPSConfiguring IPsec for Enabling Internal Communications Between Routing Engines for Junos OS inFIPS Mode

2CHAPTERGetting StartedGetting Started: A Quick Tour of the CLI 10Online Help in the CLI 35CLI Environment Settings 42

10Getting Started: A Quick Tour of the CLIIN THIS SECTIONGet Started with the Command-Line Interface 10Switch Between Operational Mode and Configuration Mode 12Use Keyboard Sequences to Navigate and Edit the CLI 14Configure a User Account on a Juniper Networks Device 16Use the CLI Editor in Configuration Mode 19Check the Status of a Juniper Networks Device 22Roll Back Configuration Changes 25Configure a Routing Protocol 27The following topics can help you (the network administrator) get started with the Junos OS CLI toperform configuration changes, switch between operational mode and configuration mode, create a useraccount, and execute some of the basic commands.NOTE: If you need a basic introduction to Junos OS, see the Getting Started Guide for Junos OS.For more in-depth information, as well as to learn how to use Junos OS with Juniper Networksdevices, see the Overview for Junos OS.This Junos OS CLI Guide assumes that you are familiar with Junos OS concepts and operationprinciples.Get Started with the Command-Line InterfaceThis topic shows you how to start the Junos OS CLI, view the command hierarchy, and make minorconfiguration changes.

11NOTE: Before you begin, make sure that your device hardware is set up and Junos OS isinstalled. You must have a direct console connection to the device or network access using SSHor Telnet. If your device is not set up, follow the installation instructions provided with the devicebefore proceeding.To log in to a device and start the CLI:1. Log in as root.The root login account has superuser privileges, with access to all commands and statements.2. Start the CLI:root# cliroot@ The command prompt shows that you are in operational mode. Later, when you enter configurationmode, the prompt will change to #.NOTE: If you are using the root account for the first time on the device, remember that thedevice ships with no password required for root. The first time you commit a configuration, youmust set a root password. Root access is not allowed over a telnet session. To enable root accessover an SSH connection, you must configure the system services ssh root-login allow statement.CLI commands can vary by platform and software release. The CLI includes several ways to get helpabout available commands. This section demonstrates some examples showing how to get help:1. Type ? to show the top-level commands available in operational mode.root@ ?Possible completions:clearClear information in the systemconfigureManipulate software configuration informationdiagnoseInvoke diagnose scriptfilePerform file operationshelpProvide help informationmonitorShow real-time debugging informationmtraceTrace multicast path from source to receiverpingPing remote targetquitExit the management session

eMake system-level requestsRestart software processSet CLI properties, date/time, craft interface messageShow system informationStart secure shell on another hostStart shellTelnet to another hostPerform diagnostic debuggingTrace route to remote host2. Type file ? to show all possible completions for the file command.root@ file ?Possible completions: [Enter] ce-address Execute this commandArchives files from the systemCalculate file checksumCompare filesCopy files (local or remote)Delete files from the systemList file informationRename filesShow file contentsLocal address to use in originating the connectionPipe through a command3. Type file archive ? to show all possible completions for the file archive command.root@ file archive ?Possible completions:compressdestinationsourceCompresses the archived file using GNU gzip (.tgz)Name of created archive (URL, local, remote, or floppy)Path of directory to archiveSwitch Between Operational Mode and Configuration ModeWhen you monitor and configure a device running Junos OS, you may need to switch between modes .When you switch between operational mode and configuration mode, the command prompt also

13changes. The operational mode prompt is a right-angle bracket ( ). The configuration mode prompt is apound or hash sign (#).To switch between operational mode and configuration mode:1. When you log in to the device and type the cli command and press Enter, you are automatically inoperational mode:---JUNOS 17.2B1.8 built 2018-05-09 23:41:29 UTC% cliuser@host 2. To enter configuration mode, type the configure command or the edit command in CLI operationalmode. The prompt in brackets ([edit]), also known as a banner, shows that you are in configurationmode at the top of the hierarchy. For example:user@host configureEntering configuration mode[edit]user@host#The CLI prompt changes from user@host to user@host#, showing that you are in configuration mode,and a banner appears to indicate the hierarchy level.3. You can exit configuration mode and return to operational mode in one of the following ways: To commit the configuration and exit:[edit]user@host# commit and-quitcommit completeExiting configuration modeuser@host To exit without committing:[edit]user@host# exit

14Exiting configuration modeuser@host When you exit configuration mode, the CLI prompt changes from user@host# to user@host , and thebanner no longer appears. You can enter or exit configuration mode as many times as you wishwithout committing your changes.4. To display the output of an operational mode command such as show while in configuration mode,issue the run configuration mode command. Then, specify the operational mode command:[edit]user@host# run operational-mode-commandFor example, to display the currently set priority value of the Virtual Router Redundancy Protocol(VRRP) primary device while you are modifying the VRRP configuration for a backup device:[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]user@host# showvirtual-address [ 192.168.1.15 ];[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]user@host# run show vrrp detailPhysical interface: xe-5/2/0, Unit: 0, Address: 192.168.29.10/24Interface state: up, Group: 10, State: backupPriority: 190, Advertisement interval: 3, Authentication type: simplePreempt: yes, VIP count: 1, VIP: 192.168.29.55Dead timer: 8.326, Master priority: 201, Master router: 192.168.29.254[edit interfaces xe-4/2/0 unit 0 family inet vrrp-group 27]user@host# set priority .Use Keyboard Sequences to Navigate and Edit the CLIYou can use keyboard sequences in the Junos OS CLI to navigate and edit the command line. You canalso use keyboard sequences to scroll through a list of recently executed commands. The following tablelists some of the CLI keyboard sequences. They are the same as those used in Emacs.

15Table 2: CLI Keyboard ShortcutsKeyboard sequenceActionCtrl bMove the cursor back one

xiv. Overview. About the CLI Guide. 2. CLI Overview. 2. Introducing the Command-Line Interface. 3. CLI Modes, Commands, and Statement Hierarchies\204An Overview. 5. Other Tools to Configure and Monitor Juniper Networks Devices. 7. Configure Junos OS in a FIPS Environment. 7. Getting Start

Related Documents:

5 Mark Rodgers AL. A&M Univ. Physical Facility Department mark.rodgers@aamu.edu 256-372-7223 256-372-7223 6 Phil Horne DCI phil@dunlapcontracting.com 256-541-7011 256-541-7011 7 Heath Roeber Fite Building Co. Inc. hroeber@fitebuilding.com 256-683-5325 256-683-5325 8 Jerry Holland Graber Costruction Co. Inc. jerry@grabercc.com 256-881-9995 256 .

1 DELL EMC UNITY ALL-FLASH STORAGE . 1,000 1,500 2,000 6,000 Max LUN Size 256 TB 256 TB 256 TB 256 TB Max file systems per Array 1000 1500 2000 4000 Max File System Size 256 TB 256 TB 256 TB 256 TB . Fail-Safe Networkin

AWS CLI Cheat sheet - List of All CLI commands Setup Install AWS CLI AWS CLI is an common CLI tool for managing the AWS resources. With this single tool we can manage all the aws resources sudo apt-get install -y python-dev python-pip sudo pip install awscli aws --version aws configure Bash one-liners cat file # output a file

coronal t1 fs hip 470 23 180 180 2.5 0.3 256 256 s/i 2 p- a axial t1 fs obl hip 700 23 180 180 2.5 0.3 256 256 a/p 2 s- i angle parallel to the neck of the hip sagittal pd fs hip 2600 40 180 180 3 0.5 320 256 s/i 1 l- r coronal vibe fs hip 12.30 7.38 200 200 0.80 0 256 256 s/i 1 p- a straight coronal

Jul 02, 2017 · Javier Ramirez, Deacon c: 256-345-1721 Dennis Kobs, Deacon h: 256-232-1426 Patrick Lappert, Deacon Read: h: 256-351-7061 Sister Teresa Walsh, Pastoral Associate H3 256-353-2667 Ext: 107 h: 256-351-0922 teresawalsh@annunlord.com Jan Gile, DRE 256-353-2667 Ext: 108 h: 256-355-

Commands for Analytics developers. Help for Salesforce CLI Commands The -h --help parameter shows details about Salesforce CLI topics and their commands. CLI Deprecation Policy Salesforce deprecates CLI commands and parameters when, for example, the underlying API changes. analytics Namespace Commands for Analytics developers. analytics:enable

Generating and serving an Angular project via a development server 2 Angular CLI - The Basic Steps 3 Chapter 2: angular-cli project deployment on apache tomcat 8.0.14 server 4 Introduction 4 Examples 4 Neccessary steps taken before deploying the angular-cli project for production build. 4 Angular-cli build command to build project bundle for .

Introduction Description logics (DLs) are a prominent family of logic-based formalisms for the representation of and reasoning about conceptual knowledge (Baader et al. 2003). In DLs, concepts are used to describe classes of individuals sharing common properties. For example, the following concept de-scribes the class of all parents with only happy children: Personu has-child.Personu has .