Monitoring the System
This section provides basic system commands that allow you to display information about the system's state. The show configuration command, for example, allows you to display the system's entire configuration.
baseline show-delta-counts
- Use to configure the system to always display statistics relative to the most recent appropriate baseline.
- The system collects many statistics during its operation. Various show commands are available to display these statistics. Baselining allows the user to identify a point in time relative to which such statistics can be reported.
- Typically, the optional delta keyword is used with show commands to specify that baselined statistics are to be shown. This command applies the "delta" function implicitly.
- Example
host1#baseline show-delta-countsshow configuration
- Use to display the system's current configuration.
- You can create a configuration script from the output by saving it as a file with the .scr extension.
- You can exclude information about a particular type of interface.
- This command was formerly documented as show config; that abbreviation is still supported.
- You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See Chapter 2, Command Line Interface, for details.
- This command is available only if the system is in Automatic Commit mode.
- Example - see the description on page 4-12.
show environment
- Use to display information on the system's physical environment, such as voltage or temperature.
- Optionally, specify the all keyword to view both the system environment information and the detailed temperature status table, or specify the table keyword to view only the temperature status table.
- The system displays a message if the voltage or temperature exceeds normal operating limits.
- The system enters thermal protection mode if the temperature exceeds maximum operating limits. For information about thermal protection mode, see ERX Installation and User Guide, Chapter 8, Troubleshooting.
- Field descriptions
- midplaneId14Slot - 5 Gbps, 14 slot midplane
- midplaneId7Slot - 5 Gbps, 7 slot midplane
- midplaneIdRx1400 - 10 Gbps ASIC compatible, 12 line card slots, 2 SRP slots for ERX-1400 series
- midplaneIdRx700 - 10 Gbps ASIC compatible, 5 line card slots, 2 SRP slots for ERX-700 series
- fabric - capacity and hardware revision of fabric
- fans - status of fans
- nvs - capacity of NVS and amount of space used
- power - states of power feeds
- srp redundancy - availability of a redundant SRP card
- slots: cards missing or offline - status of each slot
- width - number of slots the redundant midplane covers
- spare - slot that contains spare line module
- primary - slot that contains the primary line module
- primary - type and status of the primary timing signal
- secondary - type and status of the secondary timing signal
- tertiary - type and status of the tertiary timing signal
- auto-upgrade - status of the auto-upgrade parameter, which enables the system to revert to a higher-priority timing source after switching to a lower-priority timing source.
- system operational - status of system
- slot - number of the slot in which the module resides
- processor temperature - temperature of line or SRP module
- processor temperature status - temperature condition of the line module
- normal - temperature is in normal range
- too hot - module is too hot; system will go into thermal protection mode if temperature of any module exceeds 80° C
- too cold - module is too cold; system will go into thermal protection mode if temperature of any module drops below -5° C
- IOA temperature - temperature of corresponding I/O module
- IOA temperature status - temperature condition of the corresponding module
- normal - temperature is in normal range
- too hot - module is too hot; system will go into thermal protection mode if temperature of any module exceeds 80° C
- too cold - module is too cold; system will go into thermal protection mode if temperature of any module drops below -5° C
host1#show environment allchassis: 14 slot (id 0x3, rev. 0x0)fabric: 5 Gbps (rev. 1)fans: oknvs: ok (81MB flash disk, 54% full)power: A ok, B not presentsrp redundancy: none*** slots: cards missing or offlineonline: 6 9standby: 8offline: 2empty: 0 1 3 4 5 7 10 11 12 13line redundancy: 1 redundancy group(s)width 6, spare 8, primary 9temperature: oktiming: primaryprimary: internal SC oscillator (ok)secondary: internal SC oscillator (ok)tertiary: internal SC oscillator (ok)auto-upgrade enabled*** system operational: noprocessor processor IOA IOAtemperature temperature temperature temperatureslot (10C - 70C) status (10C - 70C) status---- ----------- ----------- ----------- -----------0 31 normal 30 normal3 31 normal 30 normal5 31 normal 30 normal7 31 normal 30 normalprocessor temperature rangesbelow -5C is too coldabove 80C is too hotlow temperature warning below 10Chigh temperature warning above 70CIOA temperature rangesbelow -5C is too coldabove 80C is too hotlow temperature warning below 10Chigh temperature warning above 70Cshow hosts
- name - name of the host
- ip address - IP address of the host
- type of host - type of host, for example ftp means an FTP server
host1#show hostsStatic Host Table-----------------name ip address type---- ----------- ----host1 10.2.0.124 ftpshow processes
- Use to show amount of resources used by the system processes.
- Use no keywords or use the cpu keyword to display the CPU utilization.
- Use the memory keyword to display amount of memory used. Field descriptions
- name - name of process
- bytes allocated - bytes of memory allocated to the process
- bytes free - bytes of memory freed by the process, regardless of who originally allocated it
- blocks allocated - amount of memory currently allocated to the process
- blocks free - amount of memory freed by the process
- max free block - number of bytes in the one largest free block
- task name - name of process
- times invoked - number of times process has been invoked
- invocations per second - frequency of process invocation
- total running time (msec) - time the process has been running
- percent running time - percentage of total running time attributable to this process
- average time per invocation (usec) - average number of microseconds per invocation of this process
- 5 second utilization (%) - CPU utilization by process for the last 5 seconds
- 1 minute utilization (%) - CPU utilization by process for the last minute
- 5 minute utilization - CPU utilization by process for the last 5 minutes
host1#show processes memoryHeap Statistics---------------maxbytes bytes blocks blocks freename allocated free allocated free block--------------------- --------- -------- --------- ------ --------system 110430808 84680416 5284 256 84530744file system 207600 303776 621 145 7216Crldp.osHeap 1 10120 252008 9 1 252008IpTemplateMgr General 104 2097032 2 2 2096992Lsm.osHeap 134872 127256 21 2 127216Rsvp.networkBuffers 1 0 32752 0 1 32752Rsvp.osHeap 1 637536 411000 14 2 364832...radius-rx* 0 39984 0 1 39984radius-tx* 0 39984 0 1 39984rip * 0 32752 0 1 32752router buffer 0 524272 0 1 524272ssscHeap 0 2097136 0 1 2097136host1#show processes cpuProcess Statistics------------------totalinvocations running percenttimes per time runningtask name invoked second (msec) time--------------------- ------- ----------- -------- -------aaaAtm1483Config 1 0 0 0%aaaServer 52 0 260 0%agent1 399 0 3600 0%ar1EthHelp 362856 4 590 0%...templateMgr 48 0 540 0%timerd 2346566 32 0 0%~GONE~ 405202 5 184700 0%~IDLE~ 0 0 360 0%~INTERRUPT~ 8840490 121 51050 0%averagetime 5 1 5per second minute minuteinvocation utilization utilization utilizationtask name (usec) (%) (%) (%)--------------------- ---------- ----------- ----------- -----------aaaAtm1483Config 0 0 0 0aaaServer 5000 0 0 0agent1 9022 0 0 0ar1EthHelp 1 0 0 0...templateMgr 11250 0 0 0timerd 0 0 0 0~GONE~ 455 0 1 0~IDLE~ --- 0 0 0~INTERRUPT~ 5 0 0 0show reboot-history
- Use to display the history of system and module resets.
- You can display the current reboot.hty file or a saved reboot history file.
- If you have a redundant system, it can be convenient to copy the redundant module's reboot.hty file to another filename for viewing with this command.
- Field descriptions
- Entry - number of entry in reboot history; numbers range from lowest (most recent reset) to highest (oldest reset)
- time of reset - timestamp for reset
- run state - state of system at reset
- image type - type of image running when the record is written
- boot - module is running the boot file
- diagnostics - module is running the diagnostics file
- application - module is running the software file
host1#show reboot-history*** Entry 1 ***time of reset: TUE APR 10 2001 20:25:59 UTCrun state: unknownimage type: diagnosticslocation: slot (7)build date: 0x3abf4337 MON MAR 26 2001 13:25:11 UTCreset type: user reboot, task "scheduler", reason "not specified"*** Entry 2 ***time of reset: TUE APR 10 2001 20:25:44 UTCrun state: unknownimage type: diagnosticslocation: slot (8)build date: 0x3abf5d5f MON MAR 26 2001 15:16:47 UTCreset type: user reboot, task "scheduler", reason "not specified"*** Entry 3 ***time of reset: TUE APR 10 2001 20:25:03 UTCrun state: unknownimage type: diagnosticslocation: slot (4)build date: 0x3abf3ee0 MON MAR 26 2001 13:06:40 UTCreset type: user reboot, task "scheduler", reason "not specified"show version
- Use to display the configuration of the system hardware and the software version.
- Field descriptions
- Model identification
- Copyright - copyright details for the system software
- System Release - filename, version, and date of the system software currently running on the system
- System running for - time elapsed since the last boot of the system, date and time of last boot
- slot - physical slot that contains the line module
- state - status of the line module
- booting - line module is booting
- disabled (assessing) - system is evaluating the status of this line module
- disabled (admin) - line module disabled via slot disable command
- disabled (cfg error) - use of the line module in this slot violates the permitted configuration for the system. For example, the fabric cannot supply sufficient bandwidth to the line module in this position.
- disabled (image error) - software for this line module is missing or corrupted
- disabled (mismatch) - line module in this slot is a different type from that specified in the software. Correct the condition by inserting the original module, or use the slot accept command to find information about the new module.
- hardware error - line module has a hardware fault
- inactive - either the I/O module is not present, or this primary line module is fully booted and ready to resume operation. In the latter case, the spare is currently providing services.
- initializing - transitional state before the line module proceeds to the online, standby, or inactive state; diagnostics are complete, module is initializing software
- online - line module is operating
- not present - line module configured for this slot is missing
- not responding - line module has a hardware or ROM problem
- standby - spare line module or SRP module is fully booted and ready to operate if the primary line module or active SRP module fails
- unknown - transitional state while the SRP is initializing
- type - kind of module; an "e" at the end of an SRP module type (for example, SRP-5Ge) indicates that the module includes error checking code (ECC)
- admin - status of the slot in the software
- spare - line module is a spare for line module redundancy
- running release - software that is running on the line module
- The following symbols and notices may be displayed at the end of the report:
- # This release is a result of a subsystem override
- * This release is a result of a "boot slot" override
- # The running or armed release on the slot is the same as the armed release for a subsystem. A subsystem is all the line modules of one type, such as OC3.
- * This release reflects whichever release the system is armed with at startup.
- slot uptime - length of time for which the module has been operational; a value of --- indicates that the module is not available.
host1#show versionJuniper Networks Edge Routing Switch ERX-700Copyright (c) 1999-200X Juniper Networks, Inc. All rights reserved.System Release: rx x-y-z.relVersion: x.y.z (November 28, 200X 10:22)System running for: 17 days, 17 hours, 15 minutes, 25 seconds(since THU NOV 30 200X 03:44:36 UTC)runningslot state type admin spare release slot uptime---- ------ ------- ------- ----- ---------- -------------0 online SRP-10G enabled --- mc_341.rel 0d00h:12m:52s1 --- --- --- --- --- ---2 --- --- --- --- --- ---3 online CT3 enabled --- mc_341.rel 0d00h:12m:33s4 --- --- --- --- --- ---5 online GE enabled --- mc_341.rel ---6 --- --- --- --- --- ---