Home

Troubleshooting and Monitoring on the QFX Series

Contents

1. Management interfaces meO or vmeO Fibre Channel interfaces Routed VLAN interfaces When packet copies are sent out the output interface they are not modified for any changes that are normally applied on egress such as CoS rewriting QFX3000 QFabric switch only If you configure a QFabric analyzer to mirror egress traffic and the input and output interfaces are on different Node devices the mirror copies will have incorrect VLAN IDs This limitation does not apply if you configure a QFabric analyzer to mirror egress traffic and the input and output interfaces are on the sarne Node device In this case the mirror copies will have the correct VLAN IDs as long as you do not configure more than 2000 VLANs on the QFabric switch Remote Port Mirroring Only The following constraints and limitations apply to remote port mirroring with the QFX Series The output VLAN cannot be a private VLAN or VLAN range An output VLAN cannot be shared by multiple analyzer statements An output VLAN interface cannot be a member of any other VLAN An output VLAN interface cannot be an aggregated Ethernet interface LAG Onthe source monitored switch only one interface can be a member of the analyzer VLAN Egress Port Mirroring with VLAN Translation 70 Problem Solution Related Documentation If you create a port mirroring configuration that mirrors customer VLAN CVLAN traffic on egress and the traffic un
2. List of files to delete Size Date Jul 26 20 Aug 4 18 Jul 26 20 Jun 3 14 Aug 4 18 Jul 26 21 Jun 25 13 Aug 4 18 Aug 3 11 15 Aug 4 18 04 Jul 29 22 54 Jun 30 16 32 Jun 3 14 36 Jun 3 14 37 11B 124B 1301B 387B 4920B 20 0K 16 3K 804B 16 8K 487B 855B 920B 94B 353 2K 55 05 42 37 05 00 45 05 Name var jail tmp alarmd ts var log default log messages 0 gz var log install 0 gz var log install 1 gz var log messages 0 gz var log messages 1 gz var log messages 2 gz var log security 0 gz var log security 1 gz var log wtmp 0 gz var log wtmp 1 gz var log wtmp 2 gz var log wtmp 3 gz var sw pkg j loader qfx 11 2120110303_1117_dc bui lder tgz 124 0K OB OB 12 0K 2688 0K 132 0K 2048 0K 155B OB Jun 3 Apr 14 Apr 14 Jul 26 Jul 26 Jul 26 Jul 26 Jul 26 Jul 26 1400 6K Aug 3 10 13 1398 9K Aug 3 17 01 Delete these files 14 30 16 20 17 37 20 55 20 55 20 55 20 55 20 55 20 55 2 Enter yes to delete the files 3 Reboot the switch var tmp gres tp env dat var tmp gres tp lock var tmp if rtsdb env lck var tmp if rtsdb env mem var tmp if rtsdb shm_usr1 mem var tmp if rtsdb shm_usr2 mem var tmp if rtsdb trace mem var tmp krt gencfg filter txt var tmp rtsdb if rtsdb var tmp sfid core 0 gz var tmp sfid core 1 gz yes no no Q BEST PRACTICE We recommend that you regularly request a system file storage cleanup to optimize the performance of the switc
3. Loading a Previous Configuration File on page 47 e Reverting to the Default Factory Configuration on page 48 e Reverting to the Rescue Configuration on page 48 e Performing a Recovery Installation on a QFX3500 Device and QFX3008 I Interconnect Device on page 44 Root password is lost or forgotten Recover the root password See Recovering the Root Password on page 41 Network interfaces An aggregated Ethernet interface is down See Troubleshooting an Aggregated Ethernet Interface on page 59 Interface on built in network port is down See Troubleshooting Network Interfaces on page 59 Interface on port in which SFP or SFP transceiver is installed inan SFP uplink module is down Ethernet switching A MAC address entry in the Ethernet switching See Troubleshooting Ethernet Switching on table is not updated after the device with that page 51 MAC address has been moved from one interface to another on the switch Firewall filter Firewall configuration exceeded available See Troubleshooting Firewall Filter Configuration Ternary Content Addressable Memory TCAM on page 63 space Copyright O 2012 Juniper Networks Inc 7 Troubleshooting on the QFX Series 8 Copyright O 2012 Juniper Networks Inc CHAPTER2 Alarms Understanding Alarms on page 9 Chassis Alarm Messages on a QFX3500 Device on page 10 Interface Alarm Messages on page 12 Understanding Alarms QFX Series
4. Field Description Name The device configuration name Interfaces Link to the view of physical interfaces for the device OS Version Operating system firmware version running on the device Platform Model number of the device IP Address IP address of the device Connection Status Connection status of the device in Junos Space e up Device is connected to Junos Space When connection status is up the managed status is Out of Sync Synchronizing In Sync or Sync Failed e down Device is not connected to Junos Space When Connection status is down the managed status is None or Connecting Copyright O 2012 Juniper Networks Inc 29 Troubleshooting on the QFX Series Table 10 Fields in the Manage Devices Table continued Field Description Managed Status Current status of the managed device in Junos Space Connecting Junos Space has sent connection RPC and is waiting for first connection from device e n Sync Sync operation has completed successfully and Junos Space and the device are synchronized e None Device is discovered but Junos Space has not yet sent connection RPC e Out of Sync Device has connected to Junos Space but the sync operation has not been initiated or an out of band configuration change on the device was detected and auto resync is disabled or has not yet started e Synchronizing Sync operation has started because of device discovery a manual re sync operat
5. since the command was issued or since the counters last returned to zero Copyright O 2012 Juniper Networks Inc 23 Troubleshooting on the QFX Series Displaying Real Time Statistics About an Interface on the Router or Switch switch Junos OS CLI operational mode command user host gt monitor interface interface name user host gt monitor interface so 0 0 1 Display real time statistics about traffic passing through an interface on the router or To display traffic passing through an interface on the router or switch use the following Next n Quit q or ESC Freeze f Thaw t Clear c Interface i Interface so 0 0 1 Enabled Link is Up Encapsulation PPP Keepalives Speed OC3 Traffic statistics Input bytes Output bytes Input packets Output packets capsulation statistics Input keepalives Output keepalives LCP state Opened ror statistics Input errors Input drops Input framing errors Input runts Input giants Policed discards L3 incompletes L2 channel errors L2 mismatch timeouts Carrier transitions Output errors Output drops Aged packets Purpose Action Sample Output R1 En Er Ac Ac SO SO Re Meaning None None tive alarms tive defects NET error counts seconds LOS count LOF count SEF count ES S SES S NET statistics BIP B1 BIP B2 REI L BIP B3 REI P ceived SONET overhead 5856541 88 bps 6271468 96 bps
6. 157629 0 pps 157024 0 pps 42353 42320 ooorooooc coo0 oo Mo NN PPR oooo 0 0x00 JO OxZ The sample output shows the input and output packets for a particular SONET interface so 0 0 1 The information can include common interface failures such as SONET SDH 24 Copyright 2012 Juniper Networks Inc Pinging Hosts Purpose Action Sample Output Chapter 3 Routine Monitoring Using the CLI and T3 alarms loopbacks detected and increases in framing errors For more information see Checklist for Tracking Error Conditions To control the output of the command while it is running use the keys shown in Table 8 on page 25 Table 8 Output Control Keys for the monitor interface Command Action Key Display information about the next interface The monitor interface command N scrolls through the physical or logical interfaces in the same order that they are displayed by the show interfaces terse command Display information about a different interface The command prompts you l for the name of a specific interface Freeze the display halting the display of updated statistics F Thaw the display resuming the display of updated statistics T Clear zero the current delta counters since monitor interface was started It C does not clear the accumulative counter Stop the monitor interface command Q See the Junos OS System Basics and Services Command Reference for details
7. number Configuration to return to Range O through 49 The most recently saved configuration is number O and the oldest saved configuration is number 49 Default O To return to a configuration prior to the most recently committed one 1 Specify the rollback number here 1 is entered and the configuration returns to the previously committed configuration edit user switch rollback 1 load complete 2 Activate the configuration you have loaded edit user switch commit Copyright 2012 Juniper Networks Inc 47 Troubleshooting on the QFX Series Related Documentation Configuration File Terms Reverting to the Default Factory Configuration Related Documentation If for any reason the current active configuration fails you can revert to the default factory configuration The default factory configuration contains the basic configuration settings This is the first configuration of the switch and it is loaded when the switch is first installed and powered on The load factory default command is a standard Junos OS configuration command This configuration command replaces the current active configuration with the default factory configuration To revert the switch to the rescue configuration 1 edit user switch load factory default edit user switch delete system commit factory settings edit user switch commit Understanding Configuration Files Loading a Previous Configuration
8. user switch set system root authentication plain text password At the following prompt enter the new root password For example New password juniperl Retype new password At the second prompt reenter the new root password After you have finished configuring the password commit the configuration root host commit commit complete Exit configuration mode in the CLI Exit operational mode in the CLI 20 At the prompt enter y to reboot the switch Related Documentation 42 Reboot the system y n y Configuring the Root Password Copyright O 2012 Juniper Networks Inc Chapter 5 Junos OS Basics Creating an Emergency Boot Device for a QFX Series Device If Junos OS on your QFX Series device is damaged in some way that prevents the software from loading properly you can use an emergency boot device to repartition the primary disk and load a fresh installation of Junos OS Use the following procedure to create an emergency boot device Before you begin you need to download the installation media image for your device and Junos OS release from http www juniper net customers support NOTE The following procedure assumes that you are creating the device on a QFX3500 switch You can create the emergency boot device on another Juniper Networks switch or router or any PC or laptop that supports Linux The steps you take to create the emergency boot device vary depending on the device To cre
9. 12 consecutive seconds You decide to set a maximum rate of 7 Gbps on the strict high priority queue to ensure that at least 3 Gbps of the port bandwidth is available to service other queues Table 13 on page 80 shows the topology for this example Table 13 Components of the Rate Shaping Troubleshooting Example Component Settings Affected interface shpnode xe 0 0 10 Scheduler strict high priority Name shp sched scheduler Shaping rate 7g Priority strict high NOTE This example assumes that the scheduler already exists and has been configured as strict high priority but that rate shaping to prevent the strict high priority traffic from using all of the port bandwidth has not been applied Scheduler map Name shp map Forwarding class to associate with the shp sched scheduler strict high NOTE This example assumes that a strict high priority forwarding class has been configured and assigned the name strict high Traffic control profile Name shp tcp NOTE This example does not describe how to define a complete traffic control profile Forwarding class set Name shp pg To configure the scheduler map it to the strict high priority forwarding class and apply it to interface shpnode xe 0 0 10 using the CLI 1 Specify the scheduler for the strict high priority queue shp sched with a maximum bandwidth of 7 Gbps edit class of service schedulers user switch set shp sched shaping rate 7g 2 Configure a
10. Add sufficient bandwidth to your calculations to account for the preamble and IFG so that the port bandwidth is sufficient to handle the combined maximum data rate shaping rate and the preamble and IFG Ifthe maximum bandwidth measured at the egress port exceeds the amount of bandwidth that you want to allocate to the queue reduce the shaping rate for that queue Copyright O 2012 Juniper Networks Inc 75 Troubleshooting on the QFX Series Related Documentation shaping rate Example Configuring Maximum Output Bandwidth Example Configuring Queue Schedulers Understanding CoS Output Queue Schedulers Troubleshooting Egress Bandwidth That Exceeds the Configured Minimum Bandwidth 76 Problem Cause Solution Related Documentation The minimum bandwidth of a queue or a priority group when measured at the egress port exceeds the minimum bandwidth configured for the queue transmit rate or for the priority group guaranteed rate When you configure bandwidth for a queue or a priority group the switch accounts for the configured bandwidth as data only The switch does not include the preamble and the interframe gap IFG associated with frames so the switch does not account for the bandwidth consumed by the preamble and the IFG in its minimum bandwidth calculations The measured egress bandwidth can exceed the configured minimum bandwidth when small packet sizes 64 or 128 bytes are transmitted because the prea
11. Bandwidth Impacted by Congestion Problem Cause Solution Related Documentation Congestion on an egress port causes egress queues to receive less bandwidth than expected Egress port congestion can impact the amount of bandwidth allocated to queues on the congested port and in some cases on ports that are not congested Egress queue congestion can cause the ingress port buffer to fill above a certain threshold and affect the flow to the queues on the egress port One queue receives its configured bandwidth but the other queues on the egress port are affected and do not receive their configured share of bandwidth The solution is to configure a drop profile to apply weighted random early detection WRED to the queue or queues on the congested ports Configure a drop profile on the queue that is receiving its configured bandwidth This queue is preventing the other queues from receiving their expected bandwidth The drop profile prevents the queue from affecting the other queues on the port To configure a tail drop profile using the CLI Name the drop profile and set the drop start point drop end point minimum drop rate and maximum drop rate for the drop profile edit class of service user switch set drop profile drop profile name interpolate fill level percentage fill level percentage drop probability O drop probability percentage drop profile Example Configuring Tail Drop Profiles Example Configuring Co
12. Copyright 2012 Juniper Networks Inc Troubleshooting on the QFX Series Table 6 QFX3500 Chassis Alarm Messages continued Component Alarm Type CLI Message Recommended Action Temperature Major red sensor location Temp Sensor Fail Check the system log for the following sensors message and report it to customer support Temp sensor sensor number failed where sensor number may range from 1 through 10 sensor location Temp Sensor Too Hot Check environmental conditions and alarms on other devices Ensure that environmental factors such as hot air blowing around the equipment are not affecting the temperature sensor If the condition persists the device may shut down Minor yellow sensor location Temp Sensor Too Warm For information only Check environmental conditions and alarms on other devices Ensure that environmental factors such as hot air blowing around the equipment are not affecting the temperature sensor Related Front Panel of a QFX3500 Device Documentation Configuring the Junos OS to Determine Conditions That Trigger Alarms on Different Interface Types alarm Interface Alarm Messages Interface alarms are alarms that you configure to alert you when an interface is down By default interface alarms are not configured To configure an interface link down condition to trigger a red or yellow alarm or to configure the link down condition to be ignored use the alarm statement at the
13. Device Inventory Fields 0 0 0 ete eee 33 Table 12 Physical Interfaces COIUMNS 0 0 eee eee 34 Troubleshooting Wr ffic Management os uaa ons Rome sse ase Ria ta E exar qund tO Ebr a t 75 Table 13 Components of the Rate Shaping Troubleshooting Example 80 Copyright O 2012 Juniper Networks Inc ix Troubleshooting on the QFX Series x Copyright 2012 Juniper Networks Inc About the Documentation Documentation and Release Notes on page xi Supported Platforms on page xi Using the Examples in This Manual on page xi Documentation Conventions on page xiii Documentation Feedback on page xv Requesting Technical Support on page xv Documentation and Release Notes To obtain the most current version of all Juniper Networks technical documentation see the product documentation page on the Juniper Networks website at http www juniper net techpubs If the information in the latest release notes differs from the information in the documentation follow the product Release Notes Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts These books go beyond the technical documentation to explore the nuances of network architecture deployment and administration The current list can be viewed at http www juniper net books Supported Platforms For the features described in this document the following platforms are supported QFX Series Usi
14. File on page 47 e Reverting to the Rescue Configuration on page 48 Reverting to the Rescue Configuration 48 Related Documentation If someone inadvertently commits a configuration that denies management access to a QFX Series product and the console port is not accessible you can overwrite the invalid configuration and replace it with the rescue configuration The rescue configuration is a previously committed valid configuration To revert the switch to the rescue configuration 1l Enter the load override command edit user switch load override filename 2 Commit your changes edit user switch commit filename Setting or Deleting the Rescue Configuration Reverting to the Default Factory Configuration on page 48 Configuration File Terms Copyright O 2012 Juniper Networks Inc Chapter 6 Configuration and File Management Cleaning Up the System File Storage Space Problem the problem The system file storage space on the switch is full Rebooting the switch does not solve The following error message is displayed during a typical operation on the switch after the file storage space is full user switch cli user switch gt configure var write failed filesystem is full Solution Clean up the file storage on the switch by deleting system files 1 Request to delete system files on the switch user switch gt request system storage cleanup The list of files to be deleted is displayed
15. basic operations that are equivalent to Junos OS CLI configuration mode commands Client applications use the protocol operations to display edit and commit configuration statements among other operations just as administrators use CLI configuration mode commands such as show set and commit to perform those operations NETCONF XML Management Protocol Guide SNMP MIBs and traps MIBs enable the monitoring of network devices from a central location For example use the Traceroute MIB to monitor devices remotely e Juniper Networks Enterprise Specific MIBs e Juniper Networks Enterprise Specific SNMP Version 1 Traps e Juniper Networks Enterprise Specific SNMP Version 2 Traps e Using the Traceroute MIB for Remote Monitoring Devices Running Junos OS Al Scripts and Advanced Insight Manager AIM Al Scripts installed on the switch can automatically detect and monitor faults on the switch and depending on the configuration on the AIM application send notifications of potential problems and submit problem reports to Juniper Support Systems Advanced Insight Scripts Al Scripts Release Notes Junos Space Service Now This application enables you to display and manage information about problem events When problems are detected on the switch by Advanced Insight Scripts Al Scripts that are installed on the switch the data is collected and sent to Service Now for your review and action Junos Space Se
16. blinking See Chassis Status LEDs on a QFX3500 Device amber Chassis status LED for the fan on the Replace the management board as soon as possible management board is blinking amber See Chassis Status LEDs on a QFX3500 Device Copyright 2012 Juniper Networks Inc Ul Troubleshooting on the QFX Series Table 4 Troubleshooting on the QFX Series continued Problem Category Port configuration Symptom or Problem Cannot configure a port as a Gigabit Ethernet port Recommended Action Check whether the port is a valid Gigabit Ethernet port 6 through 41 See QFX3500 Device Overview Cannot configure a port as a Fibre Channel port Check whether the port is a valid Fibre Channel port O through 5 and 42 through 47 See QFX3500 Device Overview Cannot configure a port as a 10 Gigabit Ethernet port If the port is not a 40 Gbps QSFP interface check whether the port is in the range of O through 5 or 42 through 47 If one of the ports in that block O through 5 or 42 through 47 is configured as a Fibre Channel port then all ports in that block must also be configured as Fibre Channel ports If the port is a 40 Gbps QSFP interface make sure the configuration does not exceed the interface limit Each 40 Gbps QSFP interface can be split into four 10 Gigabit Ethernet interfaces but because port O is reserved so you can only configure an additional fifteen 10 Gigabit Ethernet interfaces See Q
17. damaged in some way that prevents the software from loading correctly you may need to perform a recovery installation using an emergency boot device for example a USB flash drive to restore the default factory installation Once you have recovered the software you need to restore the device configuration You can either create a new configuration as you did when the device was shipped from the factory or if you saved the previous configuration you can simply restore that file to the device If at all possible you should try to perform the following steps before you perform the recovery installation 1 Ensure that you have an emergency boot device to use during the installation 2 Copy the existing configuration in the file config juniper conf gz from the device to a remote system such as a server or to an emergency boot device For extra safety you can also copy the backup configurations the files named config juniper conf n where n is a number from O through 9 to a remote system or to an emergency boot device A WARNING The recovery installation process completely overwrites the entire contents of the internal flash storage 3 Copy any other stored files to a remote system as desired To reinstall Junos OS 1 Insert the emergency boot device into the device 2 Reboot the switch NOTE Do not power off the device if it is already on edit system user switch gt request system reboot Copyright 2012 Junipe
18. destined to a unicast MAC address or multicast group MAC address that was learned on a community VLAN These are expected behaviors Egress Firewall Filters with Private VLANs Problem The following behaviors occur if you apply a firewall filter to a private VLAN in the output direction Copyright O 2012 Juniper Networks Inc 53 Troubleshooting on the QFX Series Solution Related Documentation Ifyou apply an egress filter to a primary VLAN the filter is also applied to traffic egressing from downstream community and isolated ports If you apply an egress filter to a community VLAN and traffic arrives from an upstream promiscuous port and later egresses from the community VLAN the filter is not applied to this traffic because forwarding is based on primary VLAN not the community VLAN If you apply an egress filter to a community VLAN the filter also applies to packets with the community VLAN tag when they egress an upstream promiscuous port The filter does not apply to packets with the primary VLAN tag when they egress the promiscuous port These are expected behaviors They occur only if you apply a firewall filter to a private VLAN in the output direction and do not occur if you apply a firewall filter to a private VLAN in the input direction Understanding Private VLANs Creating a Private VLAN on a Single Switch Creating a Private VLAN Spanning Multiple Switches Troubleshooting Q in Q and VLAN Tran
19. devices support different alarm types and severity levels Table 5 on page 9 provides a list of alarm terms and definitions that may help you in monitoring the switch Table 5 Alarm Terms and Definitions Term Definition Alarm Signal alerting you to conditions that might prevent normal operation On the switch alarm indicators include the LCD panel and LEDs on the front The LCD panel displays the chassis alarm message count Blinking amber LEDs indicate yellow alarm conditions for chassis components Alarm condition Failure event that triggers an alarm Alarm severity Seriousness of the alarm The level of severity can be either major red or minor yellow levels e Major red Indicates a critical situation on the switch that has resulted from one of the following conditions A red alarm condition requires immediate action One or more hardware components have failed Oneor more hardware components have exceeded temperature thresholds An alarm condition configured on an interface has triggered a critical warning e Minor yellow or amber Indicates a noncritical condition on the switch that if left unchecked might cause an interruption in service or degradation in performance A yellow alarm condition requires monitoring or maintenance For example a missing rescue configuration generates a yellow system alarm Alarm types Alarms include the following types e Chassis alarm Predefined alarm triggered by
20. edit chassis hierarchy level You can specify the ethernet fibre channel or management ethernet interface type Related Understanding Alarms on page 9 Documentation alarm 12 Copyright O 2012 Juniper Networks Inc PART 2 Administration Routine Monitoring Using the CLI on page 15 Routine Monitoring in Junos Space on page 27 Copyright O 2012 Juniper Networks Inc 13 Troubleshooting on the QFX Series 14 Copyright 2012 Juniper Networks Inc CHAPTER 3 Routine Monitoring Using the CLI Monitoring SNMP on page 15 Tracing SNMP Activity on a Device Running Junos OS on page 17 Monitoring RMON MIB Tables on page 20 Displaying a Log File from a Single Chassis System on page 21 Monitoring System Log Messages on page 22 Monitoring Traffic Through the Router or Switch on page 23 Pinging Hosts on page 25 Monitoring SNMP There are several commands that you can access in Junos OS operational mode to monitor SNMP information Some of the commands are showsnmphealth monitor which displays the health monitor log and alarm information show snmp mib which displays information from the MIBs such as device and system information show snmp statistics which displays SNMP statistics such as the number of packets silent drops and invalid output values show snmp rmon which displays the RMON alarm event history and log information The following example provid
21. interfaces xe 0 0 24 unit O rewrite rules ieee 802 1 custom rw Copyright O 2012 Juniper Networks Inc Related Documentation Chapter 14 Traffic Management interfaces e rewrite rules Defining CoS Rewrite Rules Monitoring CoS Rewrite Rules Troubleshooting a Port Reset on QFabric Systems When a Queue Stops Transmitting Traffic Problem Cause Solution In QFabric systems if any queue that contains outgoing packets does not transmit packets for 12 consecutive seconds the port automatically resets Failure of a queue to transmit packets for 12 consecutive seconds may be due to Astrict high priority queue consuming all of the port bandwidth Several queues consuming all of the port bandwidth Any queue or port receiving continuous priority based flow control PFC or 802 3x Ethernet PAUSE messages received PFC and PAUSE messages prevent a queue or a port respectively from transmitting packets because of network congestion Otherconditions that prevent a queue from obtaining port bandwidth for 12 consecutive seconds If the cause is a strict high priority queue or other queues consuming all of the port bandwidth you can use rate shaping to configure a maximum rate for the queues that are using all of the port bandwidth and preventing other queues from obtaining bandwidth on the port You configure a maximum rate by creating a scheduler using a scheduler map to apply it to a forwarding class whic
22. on page 9 Copyright O 2012 Juniper Networks Inc Troubleshooting on the QFX Series 2 Copyright 2012 Juniper Networks Inc CHAPTER 1 General Troubleshooting Understanding Troubleshooting Resources on page 3 Troubleshooting Overview on page 5 Understanding Troubleshooting Resources This topic describes some of the troubleshooting resources available for the OFX Series These resources include tools such as the Junos OS CLI Junos Space applications and the Advanced Insight Scripts Al Scripts Table 3 on page 3 provides a list of some of the troubleshooting resources Table 3 Troubleshooting Resources on the QFX Series Troubleshooting Resource Description Documentation Chassis alarms Chassis alarms indicate a failure on the switch or one of its components A chassis alarm count is displayed on the LCD panel on the front of the switch Chassis Alarm Messages on a QFX3500 Device on page 10 Chassis Status LEDs and Fan Tray LEDs A blinking amber Power Fan or Fan Tray LED indicates a hardware component error A blinking amber Status LED indicates a Software error Chassis Status LEDs on a QFX3500 Device Interface alarms A predefined alarm red or yellow for an interface type is triggered when an interface of that type goes down Interface Alarm Messages on page 12 System alarms A predefined alarm is triggered by a missing rescue configuration or problem wit
23. on using match conditions with the monitor traffic command Use the CLI ping command to verify that a host can be reached over the network This command is useful for diagnosing host and network connectivity problems The switch sends a series of Internet Control Message Protocol ICMP echo ping requests to a specified host and receives ICMP echo responses To use the ping command to send four requests ping count to host3 ping host count number ping host3 count 4 user switch gt ping host3 count 4 PING host3 site net 176 26 232 111 56 data bytes 64 bytes from 176 26 232 111 icmp seq 0 ttl 122 time 0 661 ms 64 bytes from 176 26 232 111 icmp seq 1 ttl 122 time 0 619 ms 64 bytes from 176 26 232 111 icmp seq 2 ttl 122 time 0 621 ms 64 bytes from 176 26 232 111 icmp seq 3 ttl 122 time 0 634 ms host3 site net ping statistics 4 packets transmitted 4 packets received 0 packet loss round trip min avg max stddev 0 619 0 634 0 661 0 017 ms Copyright O 2012 Juniper Networks Inc 25 Troubleshooting on the QFX Series 26 Meaning The ping results show the following information Size of the ping response packet in bytes IP address of the host from which the response was sent Sequence number of the ping response packet You can use this value to match the ping response to the corresponding ping request Time to live ttl hop count value of the ping response packet Total time between the sending of t
24. that connects to an FCoE device includes a native VLAN Configure a native VLAN on all 10 Gigabit Ethernet interfaces that connect to FCoE devices To configure a native VLAN on an interface 1 Set the interface port mode to tagged access if you have not already done so Copyright O 2012 Juniper Networks Inc 73 Troubleshooting on the QFX Series edit user switch set interfaces interface unit unit family ethernet switching port mode tagged access For example to set the port mode to tagged access for interface xe 0 0 6 0 edit user switch set interfaces xe 0 0 6 unit O family ethernet switching port mode tagged access 2 Configure a native VLAN on the interface edit user switch setinterfaces interface unit unit family ethernet switching native vlan id vlan id For example to set the native VLAN ID to 1 for interface xe 0 0 6 0 edit user switch set interfaces xe 0 0 6 unit O family ethernet switching native vlan id 1 3 Configure the native VLAN if it does not already exist edit user switch set vlans vlan name vlan id vlan id For example to name the native VLAN native and use the VLAN ID 1 edit user switch set vlans native vlan id 1 Related interfaces Documentation e vlans Understanding FIP Functions 74 Copyright O 2012 Juniper Networks Inc CHAPTER 14 Traffic Management Troubleshooting Egress Bandwidth That Exceeds the Configured Maximum Bandwidth on page 75 e T
25. the navigation ribbon select the Devices workspace 2 From the navigation ribbon select the Manage Devices icon The inventory page displays thumbnails of managed devices by name and IP address Above each thumbnail an icon indicates whether the device is connected up or down Table 9 on page 28 describes the connection status icons Copyright O 2012 Juniper Networks Inc 27 Troubleshooting on the QFX Series Table 9 Device Connection Status Icon Icon Description Q Connection is up The device is connected to Junos Space and is running properly NOTE Before you can update a device from Junos Space deploy service orders the device connection must be up Out of sync The device is connected to Junos Space but the device configuration in the Junos Space database is out of sync with the physical device Connection is down The device is not currently connected to Junos Space or an event has occurred either manually by an administrator or automatically by the flow of a type of traffic that has stopped the device from running C 3 View information about devices as follows e To restrict the display of devices enter a search criterion of one or more characters in the Search bar and press Enter All devices that match the search criterion are shown in the main display area To view summary information for a device select the device in the inventory page and drag the zoom slider to the rightmost posi
26. the number and size of trace files by including the following statements at the edit snmp traceoptions hierarchy level edit snmp traceoptions file files number size size For example set the maximum file size to 2 MB and the maximum number of files to 20 When the file that receives the output of the tracing operation filename reaches 2 MB filename is renamed filename O and a new file called filename is created When the new filename reaches 2 MB filename O is renamed filename and filename is renamed filename O This process repeats until there are 20 trace files Then the oldest file filename 19 is overwritten by the newest file filename O The number of files can be from 2 through 1000 files The file size of each file can be from 10 KB through 1 gigabyte GB Configuring Access to the Log File By default log files can be accessed only by the user who configured the tracing operation To specify that any user can read all log files include the file world readable statement at the edit snmp traceoptions hierarchy level edit snmp traceoptions file world readable To explicitly set the default behavior include the file no world readable statement at the edit snmp traceoptions hierarchy level edit snmp traceoptions file no world readable Configuring a Regular Expression for Lines to Be Logged By default the trace operation output includes all lines relevant to the logged activities You canrefine the
27. with the following features Find CSC offerings http www juniper net customers support Search for known bugs http www2 juniper net kb Find product documentation http www juniper net techpubs Find solutions and answer questions using our Knowledge Base http kb juniper net Download the latest versions of software and review release notes http www juniper net customers csc software Search technical bulletins for relevant hardware and software notifications https www juniper net alerts Copyright 2012 Juniper Networks Inc XV Troubleshooting on the QFX Series Join and participate in the Juniper Networks Community Forum http www juniper net company communities Open a case online in the CSC Case Management tool http www juniper net cm To verify service entitlement by product serial number use our Serial Number Entitlement SNE Tool https tools juniper net SerialNumberEntitlementSearch Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone Use the Case Management tool in the CSC at http www juniper net cm Call 1 888 314 JTAC 1 888 314 5822 toll free in the USA Canada and Mexico For international or direct dial options in countries without toll free numbers see http www juniper net support requesting support html xvi Copyright O 2012 Juniper Networks Inc PART 1 Overview General Troubleshooting on page 3 Alarms
28. C Read failed for device number where number may be from 123 to 125 e PSnumber Transitioning from online to offline where power supply PS number may be lor 2 PEM pem number is not powered For information only Check the power cord connection and reconnect it if necessary PEM pem number is not supported Indicates a power supply problem or the power supply is not supported on the device Report the problem to customer support PEM pem number Not OK Indicates a problem with the incoming AC or outgoing DC power Replace the power supply Minor yellow PEM pem number Absent For information only Indicates the device was powered on with two power supplies installed but now one is missing The device can continue to operate witha single power supply If you wish to remove this alarm message reboot the device with one power supply PEM pem number Power Supply Type Mismatch For information only Indicates that an AC power supply and DC power supply have been installed in the same chassis If you wish to remove this alarm message reboot the device with two AC power supplies or two DC power supplies PEM pem number Removed For information only Indicates the device was powered on with two power supplies installed but one has been removed The device can continue to operate witha single power supply If you wish to remove this alarm message reboot the device with one power supply
29. FP or SFP modules You must configure the operating mode of the SFP or SFP module to match the type of transceiver you want to use For SFP transceivers configure 10 Gigabit Ethernet operating mode 60 Copyright O 2012 Juniper Networks Inc CHAPTER 10 Layer 3 Protocols Troubleshooting Virtual Routing Instances on page 61 Troubleshooting Virtual Routing Instances Direct Routes Not Leaked Between Routing Instances on page 61 Direct Routes Not Leaked Between Routing Instances Problem Solution Related Documentation Direct routes are not exported leaked between virtual routing instances For example consider the following scenario QFX switch with two virtual routing instances e Routing instance 1 connects to downstream device through interface xe O 0 1 Routing instance 2 connects to upstream device through interface xe 0 0 2 If you enable route leaking between the routing instances by using the rib group statement for example the downstream device cannot connect to the upstream device because the QFX switch connects to the upstream device over a direct route and these routes are not leaked between instances However indirect routes are leaked between routing instances so the downstream device can connect to any upstream devices that are connected to the QFX switch over indirect routes This is expected behavior Understanding Virtual Router Routing Instances Configuring Virtual Router Rout
30. FX3500 Device Overview Cannot configure a 40 Gbps QSFP interface The 40 Gbps QSFP interfaces can only be used as 10 Gigabit Ethernet interfaces Each 40 Gbps QSFP interface can be split into four 10 Gigabit Ethernet interfaces using a breakout cable However port O is reserved so you can only configure an additional fifteen 10 Gigabit Ethernet interfaces See QFX3500 Device Overview External devices USB devices Upgrading software from a USB device results in an upgrade failure and the system enters an invalid state Unplug the USB device and reboot the switch Initial device configuration Cannot configure management Ethernet ports Configure the management ports from the console port You cannot configure the management ports by directly connecting to them NOTE The management ports are on the front panel of the QFX3500 switch They are labeled CO and C1 on the front panel In the CLI they are referred to as meO and mel See Configuring a QFX3500 Device Copyright O 2012 Juniper Networks Inc Chapter 1 General Troubleshooting Table 4 Troubleshooting on the QFX Series continued Problem Category Symptom or Problem Recommended Action Software upgrade Failed software upgrade See Recovering from a Failed Software Installation and configuration on page 40 Active partition becomes inactive after upgrade Problem with the active configuration file See the following topics
31. Inventory Service Information eee eee 32 Figure 8 Device Inventory Physical Interfaces 0 0 cee eee 34 Figure 9 View JMB Dialog BOX za uocum hs bor EIS SENE RU E REGERE oe 36 Copyright O 2012 Juniper Networks Inc vii Troubleshooting on the QFX Series viii Copyright O 2012 Juniper Networks Inc List of Tables Part 1 Chapter 1 Chapter 2 Part 2 Chapter 3 Chapter 4 Part 3 Chapter 14 About the Documentation llle hn xi Table 1 Notice ICONS 2a a due be RR REIVRRR aaeee wows S hace REV NEST xiii Table 2 Text and Syntax Conventions 0000 eh xiii Overview General Troubleshooting 0 00 cece eee eens 3 Table 3 Troubleshooting Resources on the QFX SerieS 1 6 2 eee eee 3 Table 4 Troubleshooting on the OFX Series 0 ee 5 AlatETieicdio nep gees a a Sega ree eta at d eui ceti coeds Seeded geese ees 9 Table 5 Alarm Terms amd Definitions ssi xax 22 o56 x EROS ERR BEA es kehonas 9 Table 6 QFX3500 Chassis Alarm Messages llle eere 10 Administration Routine Monitoring Using the CLlI llle eene 15 Table 7 SNMP Tracing Flags 222 rue Spe TA FP SOCIAL YT ueeiee rGe hows 19 Table 8 Output Control Keys for the monitor interface Command 25 Routine Monitoring in Junos Space ce eene 27 Table 9 Device Connection Status ICON 6 eee 28 Table 10 Fields in the Manage Devices Table nuuanu nannaa arran 29 Table 11
32. JU Per NETWORKS Troubleshooting on the QFX Series Published 2012 03 21 Copyright O 2012 Juniper Networks Inc Juniper Networks Inc 1194 North Mathilda Avenue Sunnyvale California 94089 USA 408 745 2000 www juniper net This product includes the Envoy SNMP Engine developed by Epilogue Technology an Integrated Systems Company Copyright 1986 1997 Epilogue Technology Corporation All rights reserved This program and its documentation were developed at private expense and no part of them is in the public domain This product includes memory allocation software developed by Mark Moraes copyright 1988 1989 1993 University of Toronto This product includes FreeBSD software developed by the University of California Berkeley and its contributors All of the documentation and software included in the 4 4BSD and 4 4BSD Lite Releases is copyrighted by the Regents of the University of California Copyright 1979 1980 1983 1986 1988 1989 1991 1992 1993 1994 The Regents of the University of California All rights reserved GateD software copyright 1995 the Regents of the University All rights reserved Gate Daemon was originated and developed through release 3 0 by Cornell University and its collaborators Gated is based on Kirton s EGP UC Berkeley s routing daemon routed and DCN s HELLO routing protocol Development of Gated has been supported in part by the National Science Foundation Portion
33. P statistics Input Packets 0 Bad versions 0 Bad community names 0 Bad community uses 0 ASN parse errors 0 Too bigs 0 No such names 0 Bad values 0 Read onlys 0 General errors 0 Total request varbinds 0 Total set varbinds 0 Get requests 0 Get nexts 0 Set requests 0 Get responses 0 Traps O Silent drops 0 Proxy drops 0 Commit pending drops 0 Throttle drops 0 Duplicate request drops 0 Output Packets 0 Too bigs 0 No such names O Bad values 0 General errors 0 Get requests 0 Get nexts 0 Set requests O0 Get responses 0 Traps 0 health monitor show snmp mib show snmp statistics Copyright 2012 Juniper Networks Inc Chapter 3 Routine Monitoring Using the CLI Tracing SNMP Activity on a Device Running Junos OS SNMP tracing operations track activity for SNMP agents and record the information in log files The logged error descriptions provide detailed information to help you solve problems faster By default Junos OS does not trace any SNMP activity If you include the traceoptions statement at the edit snmp hierarchy level the default tracing behavior is Important activities are logged in files located in the var log directory Each log is named after the SNMP agent that generates it Currently the following log files are created in the var log directory when the traceoptions statement is used e chassisd craftd ilmid mib2d rmopd
34. S Hierarchical Port Scheduling ETS Understanding CoS Tail Drop Profiles Troubleshooting an Unexpected Rewrite Value Problem Cause Traffic from one or more forwarding classes on an egress port is assigned an unexpected rewrite value If you configure a rewrite rule for a forwarding class on an egress port but you do not configure a rewrite rule for every forwarding class on that egress port then the forwarding classes that do not have a configured rewrite rule are assigned random rewrite values For example 1 Configure forwarding classes fel fc2 and fc3 Copyright O 2012 Juniper Networks Inc 77 Troubleshooting on the QFX Series 78 Solution 2 Configure rewrite rules for forwarding classes fc1 and fc2 but not for forwarding class fc3 3 Assign forwarding classes fcl fc2 and fc3 to a port When traffic for these forwarding classes flows through the port traffic for forwarding Classes fel and fc2 is rewritten correctly However traffic for forwarding class fc3 is assigned a random rewrite value If any forwarding class on an egress port has a configured rewrite rule then all forwarding classes on that egress port must have a configured rewrite rule Configuring a rewrite rule for any forwarding class that is assigned a random rewrite value solves the problem Q TIP If you want the forwarding class to use the same code point value assigned to it by the ingress classifier specify that value as the rewr
35. Serviced snmpd When a trace file named filename reaches its maximum size it is renamed filename O then filename and so on until the maximum number of trace files is reached Then the oldest trace file is overwritten For more information about how log files are created see the Junos OS System Log Messages Reference Log files can be accessed only by the user who configured the tracing operation You cannot change the directory var log in which trace files are located However you can customize the other trace file settings by including the following statements at the edit snmp hierarchy level edit snmp traceoptions f file files number match regular expression size size world readable no world readable flag flag no remote trace These statements are described in the following sections Configuring the Number and Size of SNMP Log Files on page 18 Configuring Access to the Log File on page 18 Configuring a Regular Expression for Lines to Be Logged on page 18 Configuring the Trace Operations on page 18 Copyright O 2012 Juniper Networks Inc 17 Troubleshooting on the QFX Series Configuring the Number and Size of SNMP Log Files By default when the trace file reaches 128 kilobytes KB in size it is renamed filename O then filename and so on until there are three trace files Then the oldest trace file filename 2 is overwritten You can configure the limits on
36. Switch on page 24 Displaying Real Time Statistics About All Interfaces on the Router or Switch Purpose Display real time statistics about traffic passing through all interfaces on the router or switch Action To display real time statistics about traffic passing through all interfaces on the router or switch user host gt monitor interface traffic Sample Output user host gt monitor interface traffic host name Interface so 1 0 0 so 1 1 0 so 1 1 1 so 1 1 2 so 1 1 3 t3 1 2 0 t3 1 2 1 t3 1 2 2 t3 1 2 3 so 2 0 0 so 2 0 1 so 2 0 2 so 2 0 3 so 2 1 0 so 2 1 1 so 2 1 2 so 2 1 3 at 2 3 0 at 2 3 1 Link Down Down Down Down Down Down Down Down Down Up Seconds 15 Input packets 0 oooooo o 0 211035 192753 211020 211029 189378 0 0 0 0 0 pps 0 0 0 0 0 0 0 0 0 1 QD 1 1 QD 0 0 0 0 0 Time 12 31 09 Output packets 0 oooooo o 36778 36782 36779 36776 36349 18747 16078 80338 0 0 pps 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Bytes b Clear c Delta d Packets p Quit q or ESC Rate r Up AU Down AD Meaning Thesample output displays traffic data for active interfaces and the amount that each field has changed since the command Started or since the counters were cleared by using theC key In this example the monitor interface command has been running for 15 seconds
37. VLAN tag on egress This is expected behavior Copyright O 2012 Juniper Networks Inc Chapter 7 Ethernet Switching Related Understanding Q in Q Tunneling and VLAN Translation Documentation Example Setting Up Q in Q Tunneling Copyright O 2012 Juniper Networks Inc 55 Troubleshooting on the QFX Series 56 Copyright O 2012 Juniper Networks Inc CHAPTER 8 High Availability Troubleshooting VRRP on page 57 Troubleshooting VRRP Problem If you configure multiple VRRP groups on an interface using multiple VLANS traffic for some of the groups might be briefly dropped if a failover occurs This can happen because the new master must send gratuitous ARP replies for each VRRP group to update the ARP tables in the connected devices and there is a short delay between each gratuitous ARP reply Traffic sent by devices that have not yet received the gratuitous ARP reply is dropped until the device receives the reply and learns the MAC address of the new master Solution Configure a failover delay so that the new master delays sending gratuitous ARP replies for the period that you set This allows the new master to send the ARP replies for all of the VRRP groups simultaneously Related failover delay Documentation Copyright O 2012 Juniper Networks Inc 57 Troubleshooting on the QFX Series 58 Copyright O 2012 Juniper Networks Inc CHAPTER 9 Interfaces Troubleshooting an Aggregated Ethernet In
38. a physical condition on the switch such as a power supply failure or excessive component temperature e Interface alarm Alarm you configure to alert you when an interface link is down Applies to ethernet fibre channel and management ethernet interfaces You can configure a red major or yellow minor alarm for the link down condition or have the condition ignored e System alarm Predefined alarm triggered by a missing rescue configuration or failure to install a license for a licensed software feature Copyright O 2012 Juniper Networks Inc 9 Troubleshooting on the QFX Series Related Chassis Alarm Messages on a QFX3008 I Interconnect Device Documentation Chassis Alarm Messages on a QFX3500 Device on page 10 Interface Alarm Messages on page 12 Chassis Alarm Messages on a QFX3500 Device Chassis alarms indicate a failure on the device or one of its components Chassis alarms are preset and cannot be modified The chassis alarm message count is displayed on the LCD panel on the front of the device To view the chassis alarm message text remotely use the show chassis lcd CLI command Chassis alarms on QFX3500 devices have two severity levels e Major red Indicates a critical situation on the device that has resulted from one of the conditions described in Table 6 on page 10 A red alarm condition requires immediate action Minor yellow or amber Indicates a noncritical condition on the device that if le
39. ate an emergency boot device from a QFX3500 switch 1 Use FTP to copy the installation media image into the var tmp directory on the switch 2 Insert a USB device into the USB port 3 From the Junos OS command line interface CLI start the shell user switch gt start shell 4 Switch to the root account using the su command SU Password password e NOTE The password is the root password for the switch If you logged in to the switch as root you do not need to perform this step 5 Enter the following command root switch dd if var tmp filename of dev dal bs 16k The switch writes the installation media image to the USB device root switch dd if var tmp install media qfx3500 junos 11 1 of dev dal bs 16k 1100641 records in 11006 1 records out 180332544 bytes transferred in 71 764266 secs 2512846 bytes sec 6 Log out of the shell root switch exit Copyright O 2012 Juniper Networks Inc 43 Troubleshooting on the QFX Series Related Documentation exit user switch gt USB Port Specifications for the QFX Series Performing a Recovery Installation on a QFX3500 Device and OFX3008 I Interconnect Device on page 44 Performing a QFabric Switch Recovery Installation on the Director Group Performing a Recovery Installation of the Director Group on page 45 Performing a Recovery Installation on a QFX3500 Device and QFX3008 I Interconnect Device 44 If Junos OS on your device is
40. atus Encapeulation Link Type f Table 12 on page 34 describes the information displayed for the physical Interfaces Table 12 Physical Interfaces Columns Field Description Device Name Device configuration name 34 Copyright 2012 Juniper Networks Inc Chapter 4 Routine Monitoring in Junos Space Table 12 Physical Interfaces Columns continued Field Description Interface Name Standard information about the interface in the format type fpc pic port where type is the media type that identifies the network device for example ge 0 0 6 IP Address IP address for the interface Operational Status Operational status of the interface up or down Admin Status Admin status of the interface up or down Encapsulation Encapsulation used on the physical interface Link Type Physical interface link type full duplex or half duplex Speed Mbps Speed at which the interface is running MTU Maximum transmission unit size on the physical interface Related Documentation 5 Click Return to Inventory View at the top of the inventory page Viewing Managed Devices on page 27 Viewing Hardware Inventory for Devices on page 31 Viewing and Exporting Device License Inventory Viewing Device Snapshot Details When Service Now receives iJMBs only selected information appears on the Manage Device Snapshots page You can display the entire content of the JMB using th
41. c About the Documentation Documentation Feedback We encourage you to provide feedback comments and suggestions so that we can improve the documentation You can send your comments to techpubs comments juniper net or fill out the documentation feedback form at https www juniper net cgi bin docbugreport If you are using e mail be sure to include the following information with your comments Document or topic name URL or page number Software release version if applicable Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center JTAC If you are a customer with an active J Care or JNASC support contract or are covered under warranty and need post sales technical support you can access our tools and resources online or open a case with JTAC JTAC policies For a complete understanding of our JTAC procedures and policies review the JTAC User Guide located at http www juniper net us en local pdf resource guides 7100059 en pdf Product warranties For product warranty information visit http www juniper net support warranty JTAC hours of operation The JTAC centers have resources available 24 hours a day 7 days a week 365 days a year Self Help Online Tools and Resources For quick and easy problem resolution Juniper Networks has designed an online self service portal called the Customer Support Center CSC that provides you
42. ces table If Service Now is not installed or if the table contains no data this column is not displayed EOL Status Indicates whether end of life EOL data is available for the part This data is populated by the Service Insight Exposure Analyzer table If Service Insight is not installed or if the table contains no data this column is not displayed EOL Replacement Part Part number for the replacement part identified by the Juniper Networks support organization This is the same information that would be published in an EOL announcement bulletin For an example see PSN 2011 07 315 This data is populated by the Service Insight Exposure Analyzer table If Service Insight is not installed or if the table contains no data this column is not displayed EOL Date End of sale date reported in the EOL announcement bulletin For an example see PSN 2011 07 315 This data is populated by the Service Insight Exposure Analyzer table If Service Insight is not installed or if the table contains no data this column is not displayed Description Description of the component or FRU Click Return to Inventory View to return to the device inventory page Click Export at the top of the inventory page to export the table in CSV format The Export Inventory Job Status dialog box appears displaying the progress of the job and the job ID Go to the Job Manager and click the download link to access the file Co
43. ck rogue devices on employee vlan user switch set vlans employee vlan filter input new ingress vlan rogue block Commit the changes edit user switch commit To apply a new firewall filter and overwrite the existing binding but not delete the original filter 1 2 3i 64 Configure a firewall filter with fewer terms than the original filter edit user switch set firewall family ethernet switching filter new ingress vlan rogue block Apply the firewall filter to the port VLAN or Layer 3 interfaces to overwrite the binding of the original filter for example edit user switch setvlans employee vlan description smaller filter to block rogue devices on employee vlan user switch set vlans employee vlan filter input new ingress vlan rogue block Because you can apply no more than one firewall filter per VLAN per direction the binding of the original firewall filter to the VLAN is overwritten with the new firewall filter new ingress vlan rogue block Commit the changes edit user switch commit Copyright O 2012 Juniper Networks Inc Chapter 11 Security O NOTE The original filter is not deleted and is still available in the configuration Filter Counts Previously Dropped Packet Problem If you configure two or more filters in the same direction for a physical interface and one of the filters includes a counter the counter will be incorrect if the following circumstances apply You
44. component director group reboot command and specify the name of the software package request system software add jinstall qfabric 11 3R1 4 rom component director group reboot The Director group copies the software from the external USB device occasionally displaying status messages Copying the software can take up to 10 minutes Remove the external USB device when prompted and then press Enter The Director group then reboots from the internal flash storage on which the software was just installed When the reboot is complete the Director group displays the login prompt Create a new configuration as you did when the Director group was shipped from the factory or restore the previously saved configuration file to the Director group Copyright O 2012 Juniper Networks Inc CHAPTER 6 Configuration and File Management Loading a Previous Configuration File on page 47 Reverting to the Default Factory Configuration on page 48 e Reverting to the Rescue Configuration on page 48 Cleaning Up the System File Storage Space on page 49 Loading a Previous Configuration File You can use the rollback number command to return to a previously committed configuration file A switch saves the last 50 committed configurations including the rollback number date time and name of the user who issued the commit configuration command Syntax rollback number Options none Return to the most recently saved configuration
45. configure the filter that is applied to packets first to discard certain packets For example imagine that you have a VLAN filter that accepts packets sent to 10 10 1 0 24 addresses and implicitly discards packets sent to any other addresses You apply the filter to the admin VLAN in the output direction and interface xe 0 0 1 is a member of that VLAN You configure a subsequent filter to accept and count packets that are dropped by the first filter In this example you have a port filter that accepts and counts packets sent to 192 168 1 0 24 addresses that is also applied to xe 0 0 1 in the output direction The egress VLAN filter is applied first and correctly discards packets sent to 192 168 1 0 24 addresses The egress port filter is applied next and counts the discarded packets as matched packets The packets are not forwarded but the counter displayed by the egress port filter is incorrect Remember that the order in which filters are applied depends on the direction in which they are applied as indicated here Ingress filters 1 Port Layer 2 filter 2 VLAN filter 3 Router Layer 3 filter Egress filters 1 Router Layer 3 filter 2 VLAN filter 3 Port Layer 2 filter Solution This is expected behavior Matching Packets Not Counted Problem If you configure two egress filters with counters for a physical interface and a packet matches both of the filters only one of the counters includes that packet For exa
46. cuous port These are expected behaviors They occur only if you apply a firewall filter to a private VLAN in the output direction and do not occur if you apply a firewall filter to a private VLAN in the input direction Egress Filtering of L2PT Traffic Not Supported Problem Solution Related Documentation Egress filtering of L2PT traffic is not supported on the QFX3500 switch That is if you configure L2PT to tunnel a protocol on an interface you cannot also use a firewall filter to filter traffic for that protocol on that interface in the output direction If you commit a configuration for this purpose the firewall filter is not applied to the L2PT tunneled traffic This is expected behavior Configuring Firewall Filters Verifying That Firewall Filters Are Operational Troubleshooting Policer Configuration Incomplete Count of Packet Drops on page 67 Egress Policers on QFX3500 Might Allow More Throughput Than is Configured on page 68 Incomplete Count of Packet Drops Problem Solution Under certain circumstances Junos OS might display a misleading number of packets dropped by an ingress policer If packets are dropped because of ingress admission control policer statistics might not show the number of packet drops you would expect by calculating the difference between ingress and egress packet counts This might happen if you apply an ingress policer to multiple interfaces and the aggregate ingress ra
47. d variable jnxOperatingCPU 9 1 0 0 value 5 Time 2010 07 10 11 34 17 PDT The display shows that an alarm has been defined to monitor jnxRmon MIB object jnxOperatingCPU which represents the CPU utilization of the Routing Engine The alarm is configured to generate an event that sends an SNMP trap and adds an entry to the logTable in the RMON MIB The log table shows that two occurrences of the event have been generated one for rising above a threshold of 90 percent and one for falling below athreshold of 75 percent Configuring RMON Alarms and Events Show snmp rmon Copyright O 2012 Juniper Networks Inc Chapter 3 Routine Monitoring Using the CLI show snmp rmon history Clear snmp statistics Clear snmp history Displaying a Log File from a Single Chassis System To display a log file stored on a single chassis system such as the QFX3500 switch enter Junos OS CLI operational mode and issue the following commands user switch gt show log log filename user switch gt file show log file pathname By default the commands display the file stored on the local Routing Engine The following example shows the output from the show log messages command userQswitchl show log messages Nov 4 11 30 01 switchl newsyslog 2283 logfile turned over due to size gt 128K Nov 4 11 30 01 switchl newsyslog 2283 logfile turned over due to size gt 128K Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed
48. d to the forwarding Class set to which the fcoe queue belongs Use the show configuration class of service schedulers scheduler name operational command specify the scheduler for FCoE traffic as the scheduler name to see the minimum guaranteed bandwidth transmit rate and maximum bandwidth shaping rate for the queue Use the show configuration class of service traffic control profiles traffic control profile operational command specify the traffic control profile used for FCoE traffic as the traffic control profile to see the minimum guaranteed bandwidth guaranteed rate and maximum bandwidth shaping rate for the forwarding class set See Example Configuring CoS PFC for FCoE Traffic for step by step instructions on how to configure PFC for FCoE traffic including classifier interface congestion notification profile PFC and bandwidth scheduling configuration show class of service classifier show class of service congestion notification show class of service forwarding class set show class of service traffic control profile Example Configuring CoS PFC for FCoE Traffic Troubleshooting Fibre Channel Interface Deletion 72 Problem Cause You deleted a Fibre Channel FC interface at the edit interfaces hierarchy level but the commit check fails so the interface is not deleted You must first delete the FC interface from the FC fabric on the QFX Series before you can delete the FC interface at the edit interfaces hie
49. dergoes VLAN translation before being mirrored the VLAN translation does not apply to the mirrored packets That is the mirrored packets retain the service VLAN SVLAN tag that should be replaced by the CVLAN tag on egress The original packets are unaffected on these packets VLAN translation works properly and the SVLAN tag is replaced with the CVLAN tag on egress This is expected behavior Understanding Port Mirroring Example Configuring Port Mirroring for Local Analysis Example Configuring Port Mirroring for Remote Analysis Copyright 2012 Juniper Networks Inc CHAPTER 13 Storage Troubleshooting Dropped FCoE Traffic on page 71 Troubleshooting Fibre Channel Interface Deletion on page 72 Troubleshooting Dropped FIP Traffic on page 73 Troubleshooting Dropped FCoE Traffic Problem Fibre Channel over Ethernet FCoE traffic for which you want guaranteed delivery is dropped Cause There are several possible causes of dropped FCoE traffic 1 Priority based flow control PFC is not enabled on the FCoE priority IEEE 802 1p code point 2 The FCoE traffic is not classified correctly at the ingress interface FCoE traffic should be mapped to the lossless fcoe forwarding class and to the correct IEEE 802 1p code point 3 The congestion notification profile that enables PFC for the FCoE priority is not attached to the interface 4 The forwarding class set priority group used for guaranteed deliver
50. e VLANs Use the following information to troubleshoot a private VLAN configuration Limitations of Private VLANs on page 53 Forwarding with Private VLANs on page 53 Egress Firewall Filters with Private VLANs on page 53 Limitations of Private VLANs The following constraints apply to private VLAN configurations IGMP snooping is not supported with private VLANs Routed VLAN interfaces are not supported on private VLANs Routing between secondary VLANs in the same primary VLAN is not supported Forwarding with Private VLANs Problem Solution When isolated VLAN or community VLAN tagged traffic is received on a PVLAN trunk port MAC addresses are learned from the primary VLAN This means that show ethernet switching table output will show that MAC addresses are learned from the primary VLAN and replicated to secondary VLAN s This behavior has no affect on forwarding decisions Ifa packet with a secondary VLAN tag is received on a promiscuous port it is accepted and forwarded If a packet is received on a PVLAN trunk port and meets both of the conditions listed below it is dropped The packet has a community VLAN tag The packet is destined to a unicast MAC address or multicast group MAC address that was learned on an isolated VLAN f a packet is received on a PVLAN trunk port and meets both of the conditions listed below it is dropped The packet has an isolated VLAN tag The packet is
51. e View JMB action in Service Now To view the details of an JMB 1 From the Service Now task ribbon select Service Central gt Information gt Device Snapshots The Manage Device Snapshots page appears 2 Select the organization whose iJMB contents you want to view and select View JMB from either the Actions panel or the right click menu The View JMB dialog box displays links to the original and the filtered MBs as shown in Figure 9 on page 36 The information in the filtered JMB is classified by the settings on your Global Settings page Copyright O 2012 Juniper Networks Inc 35 Troubleshooting on the QFX Series Related Documentation Figure 9 View JMB Dialog Box View JMB View JMB for hummer Read error 3 Click a link to view the iJMB details Device Snapshots Overview Exporting Device Data into HTML Deleting Device Snapshots Messages Overview Scanning a Message for Impact 36 Related Documentation You can use Service Now to view the devices impacted by the vulnerabilities described in the information message To scan i JMBs and view the impacted devices 1 From the Service Now task ribbon select Service Central gt Information gt Messages The Manage Messages page appears 2 Select the message that you want to scan for impact and select Scan for Impact from either the Actions panel or the right click menu The Scan for Impact Results page displays the list of devices
52. eboot request system reboot request system halt request system power off Connecting a OFX Series Device to a Management Console Recovering from a Failed Software Installation 40 Problem Solution If the Junos OS appears to have been installed but the CLI does not work or if the switch has no software installed you can use this recovery installation procedure to install the Junos OS If a Junos OS image already exists on the switch you can either install the new Junos OS package in a separate partition in which case both Junos OS images remain on the switch or you can remove the existing Junos OS image before you start the new installation process To perform a recovery installation 1 Power on the switch The loader script starts 2 After the message Loading boot defaults loader conf appears you are prompted with the following message Hit Enter to boot immediately or space bar for command prompt Press the Spacebar to enter the manual loader The loader gt prompt appears 3 Enter the following command loader install format external source where format Enables you to erase the installation media before installing the installation package If you do not include this option the system installs the new Junos OS in a different partition from that of the most recently installed Junos OS external Installs the installation package onto external media a USB stick for e
53. een Routing Instances suus 61 iv Copyright O 2012 Juniper Networks Inc Chapter 11 SS OG rA TRAN TORRES 63 Troubleshooting Firewall Filter Configuration llle 63 Firewall Filter Configuration Returns a No Space Available in TCAM WMESSA SCs on pag ncmatate cua d seen cites eee dais elena a OW R36 deed 63 Filter Counts Previously Dropped Packet 0 00 00 c cee eee eee 65 Matching Packets Not Counted 0 0 0 0 eee eee 65 Cannot Include loss priority and policer Actions in Same Term 66 Cannot Egress Filter Certain Traffic Originating on QFX Switch 66 Firewall Filter Match Condition Not Working with Q in Q Tunneling 66 Egress Firewall Filters with Private VLANS ll 66 Egress Filtering of L2PT Traffic Not Supported 0 0000 67 Troubleshooting Policer Configuration llle 67 Incomplete Count of Packet Drops lle 67 Egress Policers on QFX3500 Might Allow More Throughput Than is COMMUN CO as egrets eat aa gy Oe age Bane TIERE 68 Chapter 12 SEOTUICOS usd sioe dade ERE d ated adc raar e ous A nie wrest ea TA 69 Troubleshooting Port Mirroring 2 6 eee ena 69 Port Mirroring Constraints and Limitations 0 0 0 0c cece eee 69 Local and Remote Port Mirroring llle 69 Remote Port Mirroring Only eens 70 Egress Port Mirroring with VLAN Translation 00002 cece eee 70 Chapter 13 SEOL Ages oodd nes evoethbdoe d
54. eral Troubleshooting 0 ccc cece eens 3 Understanding Troubleshooting Resources 0 0 eee 3 Tro bleshooting OVelVIeW e lt cica bes cawe dase dcanadiawbadactduhie fed Pp ed 5 IANS sui vue knees Ce oee Kom Kui qam RIA RUE see FREE IMS 9 Understanding Alartus usw 020 ek mac em aree Re he RR e eT dua 9 Chassis Alarm Messages on a QFX3500 Device 0 cee ee 10 Interface Alarm Messages 6 hh eens 12 Administration Routine Monitoring Using the CLI 0 cee ee 15 Montone SNMP st ies ota Jaan do a wie dd ed CORP ak CDU NE GIES M 15 Tracing SNMP Activity on a Device Running Junos OS 0 0 000 cee 17 Configuring the Number and Size of SNMP Log Files 0 18 Configuring Access to the Log File 0 0 0 00 eee 18 Configuring a Regular Expression for Lines to Be Logged 18 Configuring the Trace Operations 0 suauu aaura aara 18 Monitoring RMONUMIB Tables 2caccxwoke nt cde ote daaseandeoh Quschewaner 20 Displaying a Log File from a Single Chassis SysteM 0 00 0000 eee 21 Monitoring System Log MeSSAS S 1 eee eee 22 Monitoring Traffic Through the Router or Switch 2 0 0 0 0c eee eee 23 Displaying Real Time Statistics About All Interfaces on the Router or e P m 23 Displaying Real Time Statistics About an Interface on the Router or SWIG P Cr 24 PINSINE FIOSES uoce MOSES ted ge feodo rbd ati heh a id us d X e 25 C
55. erfaces by issuing the clear ethernet switching table command the entry for the moved device in the Ethernet switching table is not updated Set up the switch to handle unattended MAC address switchovers 1 Reduce the system wide ARP aging timer By default the ARP aging timer is set at 20 minutes The range of the ARP aging timer is from 1 through 240 minutes edit system arp user switch setaging timer 3 2 Set the MAC aging timer to the same value as the ARP timer By default the MAC aging timer is set to 300 seconds The range is 15 to 1 000 000 seconds edit vlans user switch set vlans sales mac table aging time 180 The ARP entry and the MAC address entry for the moved device expire within the times specified by the aging timer values After the entries expire the switch sends a new ARP Copyright 2012 Juniper Networks Inc 51 Troubleshooting on the QFX Series Related Documentation message to the IP address of the device The device responds to the ARP message thereby refreshing the entries in the switch s ARP cache table and Ethernet switching table arp mac table aging time Troubleshooting Layer 2 Protocol Tunneling Drop Threshold Statistics Might Be Incorrect on page 52 Egress Filtering of L2PT Traffic Not Supported on page 52 Drop Threshold Statistics Might Be Incorrect Problem Solution L2PT processing is done by the CPU and L2PT traffic to the CPU is rate limited to a maxim
56. ernet Switching 2 23 025 062 s20m2 LI Sq ei pREGO tiae a aed Seka Se 51 Troubleshooting Ethernet Switching 000s 5 Troubleshooting Layer 2 Protocol Tunneling 1 0 2 0 cee eee 52 Drop Threshold Statistics Might Be Incorrect lille ees 52 Egress Filtering of L2PT Traffic Not Supported 0 000000 52 Troubleshooting Private VLANS 0 cc ee eee teens 53 Limitations of Private VLANS 0 0 0 0 53 Forwarding with Private VLANS 0 0 00 cece eens 53 Egress Firewall Filters with Private VLANS 0 000000 RR 53 Troubleshooting Q in Q and VLAN Translation Configuration 54 Firewall Filter Match Condition Not Working with Q in Q Tunneling 54 Egress Port Mirroring with VLAN Translation aasa auau 000000 eee 54 Chapter 8 High Avanabilitys 22352222 0c cmdincada ie aoecdeoetiaeade mend debi sess 57 Troubleshooting VRRP ai c8a5 oasis EIS EOTUR dees eos sede eS Re oS suere 57 Chapter 9 interfaces cars dames iem x Seo acr weed 939 S8 3 COUR CO ATRLE GUN Snc ae as 018 59 Troubleshooting an Aggregated Ethernet Interface 0 2 0 cee 59 Troubleshooting Network Interfaces 0 ccc eee ee ee 59 The interface on the port in which an SFP or SFP transceiver is installed in an SFP or SFP module is dOWN 6 eee 59 Chapter 10 Layer 3 Protocols 99x ana bedonia ke view cneme idee IE Ra P 61 Troubleshooting Virtual Routing Instances 0 ee 61 Direct Routes Not Leaked Betw
57. es sample output from the show snmp health monitor command user switch gt show snmp health monitor Alarm Index Variable description Value State 32768 Health Monitor root file system utilization jnxHrStoragePercentUsed 1 58 active 32769 Health Monitor config file system utilization jnxHrStoragePercentUsed 2 0 active 32770 Health Monitor RE O CPU utilization jnxOperatingCPU 9 1 0 0 0 active 32773 Health Monitor RE 0 Memory utilization Copyright O 2012 Juniper Networks Inc 15 Troubleshooting on the QFX Series Related Documentation jnxOperatingBuffer 9 1 0 0 35 active 32775 Health Monitor jkernel daemon CPU utilization Init daemon 0 active Chassis daemon 50 active Firewall daemon 0 active Interface daemon 5 active SNMP daemon 11 active MIB2 daemon 42 active The following example provides sample output from the show snmp mib command user switch gt show snmp mib walk system sysDescr 0 Juniper Networks Inc qfx3500s internet router kernel JUNOS 11 1 20100926 0 0 2010 09 26 06 17 38 UTC builder abc juniper net volume bui 1d junos 11 1 production 20100926 0 obj x1r bsd sys compi 1e JUNIPER xxxxx Build date 2010 09 26 06 00 10 U sysObjectID 0 jnxProductQFX3500 sysUpTime O 24444184 sysContact 0 J Smith sysName 0 Lab QFX3500 sysLocation 0 Lab sysServices 0 4 The following example provides sample output from the show snmp statistics command user switch gt show snmp statistics SNM
58. est system reboot Possible completions Enter Execute this command at Time at which to perform the operation in Number of minutes to delay before operation media Boot media for next boot message Message to display to all users Pipe through a command user switch gt request system reboot Reboot the system yes no no yes Rebooting switch Similarly to halt the switch issue the request system halt command A CAUTION Before entering this command you must have access to the switch s console port in order to bring up the Routing Engine user switch gt request system halt Possible completions Enter Execute this command at Time at which to perform the operation in Number of minutes to delay before operation media Boot media for next boot message Message to display to all users Pipe through a command Copyright O 2012 Juniper Networks Inc 39 Troubleshooting on the QFX Series Related Documentation e NOTE When you issue this command onan individual component in a QFabric system you will receive a warning that says Hardware based members will halt Virtual Junos Routing Engines will reboot If you want to halt only one member use the member option You cannot issue this command from the QFabric CLI Issuing the request system halt command on the switch halts the Routing Engine To reboot a Routing Engine that has been halted you must connect through the console Clear system r
59. etworks hardware and software products are Year 2000 compliant Junos OS has no known time related limitations through the year 2038 However the NTP application is known to have some difficulty in the year 2036 END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of or is intended for use with Juniper Networks software Use of such software is subject to the terms and conditions of the End User License Agreement EULA posted at http www juniper net support eula html By downloading installing or using such software you agree to the terms and conditions of that EULA ii Copyright O 2012 Juniper Networks Inc Table of Contents Part 1 Chapter 1 Chapter 2 Part 2 Chapter 3 About the Doctmebtstlior xo inso x ux RR dr US VEN ES As b bessisbesius Xi Documentation and Release NoteS 0 cece eee xi Supported PlatlonmMs eero eoi Se acad ee aware cece a con eo as dh ge ed ote xi Using the Examples in This Manual 2 0 0 0 cece eee xi Merging a Full Exarmiple s2iu42 zweier a ta E AUR EGRE MERE REALES xii Merging a Snippet siccozas ka dusk kg 3A dor Por Sore xA xii Documentation CONVENTIONS ocd uou aac urea iom puce dor Qo aud oan RA Os xiii Documentation Feedback 6 een XV Requesting Technical Support 00 eee eee XV Self Help Online Tools and Resources eee XV Opening a Case With JTAC a ae Rest dod RERUMS eae ee xvi Overview Gen
60. evices inventory page displays the devices managed in Junos Space 3 Double click a device to display its inventory Figure 5 on page 32 shows the device inventory page for a single device Copyright O 2012 Juniper Networks Inc 3l Troubleshooting on the QFX Series Figure 5 Device Inventory Single Chassis Return to Inventory View Serial Number Description JN111BEBEAFA CHAS BP M R 0 JN111BEBEAFA M CRAFT M 7 9 xl 330 ront Panel Display rer Distribution Module 1 71 00 uting Engine Q BUILTIN 740 01 740 01 740 01 740 01 740 01 740 01 740 013111 REV 01 740 013111 REV 01 740 013111 REV 02 740 013111 REV 01 lt gt Figure 6 on page 32 shows the device inventory for SRX Series chassis cluster devices This inventory record shows information for both the primary and secondary device Figure 6 Device Inventory Chassis Cluster Return to Inventory View Item Model Number Part Number Serial Number Description E aster E mii srx3400 bottom SRX3400 4428084D0015 Chassis node1 SRX3400 CHAS 710 015748 4428084D0015 SRX 3400 E Ba srx3400 top SRX3400 AA2808AD0013 F Chassis nodeO SRX3400 CHAS 710 015748 AA2808AD0013 SRX 3400 Figure 7 on page 32 shows the device inventory for a Junos Space Network Application Platform installation that includes Service Now and Service Insight This inventory record includes columns related to service contracts and end of life status Figure 7 Device Inventory Se
61. f space available in the TCAM table The filter is not applied but the commit operation for the firewall filter configuration is completed in the CLI module When a firewall filter configuration exceeds the amount of available TCAM table space you must configure a new firewall filter with fewer filter terms so that the space requirements for the filter do not exceed the available space in the TCAM table You can perform either of the following procedures to correct the problem Copyright O 2012 Juniper Networks Inc 63 Troubleshooting on the QFX Series To delete the filter and its binding and apply the new smaller firewall filter to the same binding 1 Delete the filter and its binding to ports VLANs or Layer 3 interfaces For example edit user switch delete firewall family ethernet switching filter ingress vlan rogue block user switch delete vlans employee vlan description filter to block rogue devices on employee vlan user switch delete vlans employee vlan filter input ingress vlan rogue block Commit the changes edit user switch commit Configure a smaller filter with fewer terms that does not exceed the amount of available TCAM space For example edit user switch set firewall family ethernet switching filter new ingress vlan rogue block Apply bind the new firewall filter to a port VLAN or Layer 3 interface For example edit user switch set vlans employee vlan description filter to blo
62. ft unchecked might cause an interruption in service or degradation in performance A yellow alarm condition requires monitoring or maintenance Table 6 on page 10 describes the chassis alarm messages on QFX3500 devices Table 6 QFX3500 Chassis Alarm Messages Component Alarm Type CLI Message Recommended Action Fans Major red Fan Blower Absent The fan is missing Install a fan Fan Failure Replace the fan and report the failure to customer support Fan I2C Failure Check the system log for one of the following messages and report the error message to customer support e CM ENV Monitor Get fan speed failed Fan number is NOT spinning correct speed where fan number may be 1 2 or 3 Fan fan number Not Spinning Remove and check the fan for obstructions and then reinsert the fan If the problem persists replace the fan 10 Copyright 2012 Juniper Networks Inc Table 6 QFX3500 Chassis Alarm Messages continued Component Alarm Type Power supplies Major red CLI Message PEM pem number Airflow not matching Chassis Airflow Chapter 2 Alarms Recommended Action The power supply airflow direction is the opposite of the chassis airflow direction Replace the power supply with a power supply that supports the same airflow direction as the chassis PEM pem number I2C Failure Check the system log for one of the following messages and report the error message to customer support 2
63. gement device Connect the other end of the Ethernet rollover cable to the console port on the switch Turn on the power to the management device On the management device start your asynchronous terminal emulation application such as Microsoft Windows Hyperterminal and select the appropriate COM port to use for example COMI Configure the port settings as follows Bits per second 9600 Data bits 8 e Parity None Copyright 2012 Juniper Networks Inc 41 Troubleshooting on the QFX Series 18 19 e Stop bits 1 e Flow control None Power on the switch by if necessary plugging the power cords into the QFX3500 switch power supply or turning on the power to the device or switch by switching on the AC power outlet the device is plugged into The terminal emulation screen on your management device displays the switch s boot sequence When the following prompt appears press the Spacebar to access the switch s bootstrap loader command prompt Hit Enter to boot immediately or space bar for command prompt Booting kernel in 9 seconds At the following prompt enter boot s to start up the system in single user mode ok boot s Atthe following prompt enter recovery to start the root password recovery procedure Enter full pathname of shell or recovery for root password recovery or RETURN for bin sh recovery Enter configuration mode in the CLI Set the root password For example
64. h Copyright O 2012 Juniper Networks Inc 49 Troubleshooting on the QFX Series Related request system storage cleanup Documentation 50 Copyright O 2012 Juniper Networks Inc CHAPTER7 Ethernet Switching Troubleshooting Ethernet Switching on page 51 Troubleshooting Layer 2 Protocol Tunneling on page 52 Troubleshooting Private VLANs on page 53 Troubleshooting Q in Q and VLAN Translation Configuration on page 54 Troubleshooting Ethernet Switching Problem Solution Sometimes a MAC address entry in the switch s Ethernet switching table is not updated after the device with that MAC address has been moved from one interface to another on the switch Typically the switch does not wait for a MAC address expiration when a MAC move operation occurs As soon as the switch detects the MAC address on the new interface it immediately updates the table Many network devices send a gratuitous ARP packet when switching an IP address from one device to another The switch updates its ARP cache table after receipt of such gratuitous ARP messages and then it also updates its Ethernet switching table Sometimes silent devices such as syslog servers or SNMP trap receivers that receive UDP traffic but do not return acknowledgment ACK messages to the traffic source fail to send gratuitous ARP packets when a device moves If such a move occurs when the system administrator is not available to explicitly clear the affected int
65. h maps to an output queue and applying the scheduler map to the port using a forwarding class set and a traffic control profile To configure rate shaping using the CLI 1 Name the existing scheduler or create a scheduler and define the maximum bandwidth asarate or as a percentage edit class of service user switch set schedulers scheduler name shaping rate rate percent percentage 2 Configure a scheduler map to associate the scheduler with the forwarding class queue that is consuming all of the port bandwidth edit class of service user switch set scheduler maps scheduler map name forwarding class forwarding class name scheduler scheduler name 3 Associate the scheduler map with a traffic control profile edit class of service Copyright 2012 Juniper Networks Inc 79 Troubleshooting on the QFX Series user switch set traffic control profiles traffic control profile name scheduler map scheduler map name 4 Associate the traffic control profile and thus the scheduler map that contains the rate shaping queue scheduler with a forwarding class set and apply them to the interface that is being reset edit class of service user switch set interfaces interface name forwarding class set fc set name output traffic control profile traffic control profile name For example a strict high priority queue is using all of the bandwidth on interface shpnode xe 0 0 10 and preventing other queues from transmitting for
66. h the software license Understanding Alarms on page 9 System log messages The system log includes details of system and user events including errors Specify the severity and type of system log messages you wish to view or save and configure the output to be sent to local or remote hosts Overview of Single Chassis System Logging Configuration e Junos OS System Log Configuration Statements Copyright O 2012 Juniper Networks Inc Troubleshooting on the QFX Series Table 3 Troubleshooting Resources on the QFX Series continued Troubleshooting Resource Description Documentation Junos OS operational mode commands Operational mode commands can be used to monitor switch performance and current activity on the network For example use the traceroute monitor command to locate points of failure in a network e Monitoring System Process Information e Monitoring System Properties e traceroute monitor Junos OS automation scripts event scripts Event scripts can be used to automate network troubleshooting and management tasks Junos OS Configuration and Operations Automation Guide Junos OS XML operational tags XML operational tags are equivalent in function to operational mode commands in the CLI which you can use to retrieve status information for a device Junos XML API Operational Reference NETCONF XML management protocol The NETCONF XML management protocol defines
67. he ping request packet and the receiving of the ping response packet in milliseconds This value is also called round trip time Number of ping requests probes sent to the host Number of ping responses received from the host Packet loss percentage Round trip time statistics minimum average maximum and standard deviation of the round trip time Copyright O 2012 Juniper Networks Inc CHAPTER 4 Routine Monitoring in Junos Space Viewing Managed Devices on page 27 Viewing Hardware Inventory for Devices on page 31 Viewing Physical Interfaces for Devices on page 34 Viewing Device Snapshot Details on page 35 Scanning a Message for Impact on page 36 Viewing Managed Devices You can view operating system platform IP address license and connection status information for all the managed devices in your network Device information can be viewed graphically or in a table By default Junos Space displays thumbnail representations of devices You can also view managed devices from the Network Monitoring workspace via the Node List see Viewing the Node List The Network Monitoring workspace also enables you to resync your managed devices see Resyncing Nodes Viewing Devices as Graphics on page 27 Viewing Devices in a Table on page 29 Viewing Devices as Graphics You can view thumbnails summary information and detailed information about the devices managed by Junos Space To view the managed devices 1 From
68. iim eL HNPE ds Edda erbe diee mera 71 Troubleshooting Dropped FCoE Traffic 0 ess 71 Troubleshooting Fibre Channel Interface Deletion llle 72 Troubleshooting Dropped FIP Traffic csse RR 73 Chapter 14 Traffic Manasement 3 22 9 023 uh variance PA ce Dar qoi Mir OA aa 75 Troubleshooting Egress Bandwidth That Exceeds the Configured Maximum Bani duces voe EUNT dE debe tfe dx dide y RS qure RT EBORE 75 Troubleshooting Egress Bandwidth That Exceeds the Configured Minimum BanGWiGh PEPERIT ERI ch cusd path ate ede TIL aue Tee 76 Troubleshooting Egress Queue Bandwidth Impacted by Congestion 727 Troubleshooting an Unexpected Rewrite Value leere Ju Troubleshooting a Port Reset on QFabric Systems When a Queue Stops Transmitting ITabTle 2d 22 eure oe PSOCTSIMCROIPODUSQRD eA IP TU 79 Copyright O 2012 Juniper Networks Inc v Table of Conte nts Troubleshooting on the QFX Series vi Copyright O 2012 Juniper Networks Inc List of Figures Part 2 Administration Chapter 4 Routine Monitoring in Junos Space eseleeee eren 27 Figure 1 Inventory Page SRX ChassisCluster llle eee 28 Figure 2 Table ICON eee RR RR RR 29 Figure 3 Device Table 6 ee teen ene 29 Figure 4 Selecting Columns 0 00 eee eee eee 30 Figure 5 Device Inventory Single Chassis 0 0 0 cece eee eee 32 Figure 6 Device Inventory Chassis Cluster 0 0 0 0 0 eee 32 Figure 7 Device
69. ilter on input to a trunk port that participates in a service VLAN the match condition does not work if the Q in Q Ethertype is not Ox8100 When Q in Q tunneling is enabled trunk interfaces are assumed to be part of the service provider or data center network and therefore participate in service VLANS This is expected behavior To set the Q in Q Ethertype to Ox8100 enter the statement set dotlq tunneling ethertype Ox8100 at the edit ethernet switching options hierarchy level You must also configure the other end of the link to use the same Ethertype Egress Firewall Filters with Private VLANs Problem 66 The following behaviors occur if you apply a firewall filter to a private VLAN in the output direction Copyright O 2012 Juniper Networks Inc Solution Chapter 11 Security Ifyou apply an egress filter to a primary VLAN the filter is also applied to traffic egressing from downstream community and isolated ports If you apply an egress filter to a community VLAN and traffic arrives from an upstream promiscuous port and later egresses from the community VLAN the filter is not applied to this traffic because forwarding is based on primary VLAN not the community VLAN If you apply an egress filter to a community VLAN the filter also applies to packets with the community VLAN tag when they egress an upstream promiscuous port The filter does not apply to packets with the primary VLAN tag when they egress the promis
70. ing Instances rib group Copyright O 2012 Juniper Networks Inc 61 Troubleshooting on the QFX Series 62 Copyright O 2012 Juniper Networks Inc CHAPTER 11 Security Troubleshooting Firewall Filter Configuration on page 63 e Troubleshooting Policer Configuration on page 67 Troubleshooting Firewall Filter Configuration Use the following information to troubleshoot a firewall filter configuration e Firewall Filter Configuration Returns a No Space Available in TCAM Message on page 63 Filter Counts Previously Dropped Packet on page 65 e Matching Packets Not Counted on page 65 e Cannot Include loss priority and policer Actions in Same Term on page 66 Cannot Egress Filter Certain Traffic Originating on OFX Switch on page 66 Firewall Filter Match Condition Not Working with Q in Q Tunneling on page 66 Egress Firewall Filters with Private VLANs on page 66 Egress Filtering of L2PT Traffic Not Supported on page 67 Firewall Filter Configuration Returns a No Space Available in TCAM Message Problem Solution When a firewall filter configuration exceeds the amount of available Ternary Content Addressable Memory TCAM space the system returns the following syslogd message No space available in tcam Rules for filter filter name will not be installed A switch returns this message during the commit operation if the firewall filter that has been applied to a port VLAN or Layer 3 interface exceeds the amount o
71. ion or an autornatic re sync operation Sync Failed Sync operation failed Device Family not displayed Device family of the selected device by default Serial Number not displayed Serial number of the device chassis by default 3 Sort the table by mousing over the column header for the data you want to sort by and clicking the down arrow Select Sort Ascending or Sort Descending 4 Show columns not in the default table view or hide columns as follows a Mouse over any column header and click the down arrow b Select Columns from the menu as shown in the following example Figure 4 Selecting Columns Manage Devices Name ha OS Version Platform IP Address Connection Statu Managed Status 1 Sort Ascending Z Sort Descending GUJE Columns Interfaces 4 OS Version J Device Family Platform IP Address Connection Status Managed Status S S S S Serial Number c Select the check boxes for columns that you want to view Clear the check boxes for columns that you want to hide 5 View information about devices as follows To restrict the display of devices enter a search criterion of one or more characters in the Search bar and press Enter 30 Copyright O 2012 Juniper Networks Inc Chapter 4 Routine Monitoring in Junos Space All devices that match the search criterion are shown in the main display area e To view hardware inventory information for a device double click the
72. is 65 percent for Fan 1 Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed is 65 percent for Fan 2 Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed is 65 percent for Fan 3 Nov 4 11 52 53 switchl snmpd 944 SNMPD HEALTH MON INSTANCE Health Monitor jroute daemon memory usage Management process new instance detected variable sysApplElmtRunMemory 5 6 2293 Nov 4 11 52 53 switchl snmpd 944 SNMPD HEALTH MON INSTANCE Health Monitor jroute daemon memory usage Command line interface new instance detected variable sysApplElmtRunMemory 5 8 2292 Nov 4 12 08 30 switchl rpdf 957 task connect task BGP 100 10 10 1 6 179 addr 10 10 1 6 179 Can t assign requested address Nov 4 12 08 30 switchl rpdf 957 bgp connect start connect 10 10 1 6 Internal AS 100 Can t assign requested address Nov 4 12 10 24 switchl mgd 2293 UI CMDLINE READ LINE User jsmith command exit Nov 4 12 10 27 switchl mgd 2293 UI DBASE LOGOUT EVENT User jsmith exiting configuration mode Nov 4 12 10 31 switchl mgd 2293 UI CMDLINE READ LINE User jsmith command show log messages The following example shows the output from the file show command The file in the pathname var log processes has been previously configured to include messages from the daemon facility userQswitchl file show var log processes Feb 22 08 58 24 switchl snmpd 359 SNMPD TRAP WARM START trap generate warm SNMP trap
73. ite rule value For example if a forwarding class has the IEEE 802 1 ingress classifier code point value OTI configure a rewrite rule for that forwarding class that uses the IEEE 802 1p code point value 011 Q NOTE There are no default rewrite rules You can bind one rewrite rule for each type DSCP and IEEE 802 1 to a given interface A rewrite rule can contain multiple forwarding class to rewrite value associations l Assign a rewrite value to a forwarding class Add the new rewrite value to the same rewrite rule as the other forwarding classes on the port edit class of service rewrite rules user switch set dscp ieee 802 1 rewrite name forwarding class class name loss priority priority code point alias bits For example if the other forwarding classes on the port use rewrite values defined in the rewrite rule custom rw the forwarding class fcoe is being randomly rewritten and you want to use IEEE 802 1 code point OTI for the fcoe forwarding class edit class of service rewrite rules user switch set ieee 802 1 custom rw forwarding class fcoe loss priority high code point 011 2 Enable the rewrite rule on an interface if it is not already enabled on the desired interface edit user switch set class of service interfaces interface name unit unit rewrite rules dscp ieee 802 1 rewrite rule name For example to enable the rewrite rule custom rw on interface xe 0 0 24 0 edit user switch set class of service
74. mble and the IFG are a larger percentage of the total traffic For larger packet sizes the preamble and IFG overhead are a small portion of the total traffic and the effect on egress bandwidth is minor e NOTE The sum of the queue transmit rates in a priority group should not exceed the guaranteed rate for the priority group You cannot guarantee a minimum bandwidth for the queues that is greater than the minimum bandwidth guaranteed for the entire set of queues When you calculate the bandwidth requirements for queues and priority groups on which you expect a significant amount of traffic with small packet sizes consider the transmit rate and the guaranteed rate as the minimum bandwidth for the data only Add sufficient bandwidth to your calculations to account for the preamble and IFG so that the port bandwidth is sufficient to handle the combined minimum data rate and the preamble and IFG If the minimum bandwidth measured at the egress port exceeds the amount of bandwidth that you want to allocate to a queue or to a priority group reduce the transmit rate for that queue and reduce the guaranteed rate of the priority group that contains the queue guaranteed rate transmit rate Example Configuring Minimum Guaranteed Output Bandwidth Example Configuring Queue Schedulers Copyright O 2012 Juniper Networks Inc Chapter 14 Traffic Management Understanding CoS Output Queue Schedulers Troubleshooting Egress Queue
75. me policer on egress to multiple interfaces in these groups each group is rate limited at 1 Gbps For example if you apply the policer to xe 0 0 0 through xe 0 0 4 five interfaces and xe 0 0 24 through xe 0 0 33 ten interfaces each group is rate limited at 1 Gbps for a total allowed throughput of 2 Gbps Here is another example If you apply the policer to xe 0 0 0 through xe 0 0 4 and xe 0 1 1 through xe 0 1 5 a total of ten interfaces that group is rate limited at 1 Gbps in aggregate If you also apply the policer to xe 0 0 24 that one interface is rate limited at 1 Gbps while the other ten are still rate limited at 1 Gbps in aggregate Interfaces xe O 1 1 through xe 0 1 15 are physically located on the QSFP uplink ports according to the following scheme xe 0 1 1 through xe 0 1 3 are on QO xe 0 1 4 through xe 0 1 7 are on QI e xe 0 1 8 through xe 0 1 1l are on Q2 xe O 1 2 through xe 0 1 15 are on Q3 This behavior occurs only if the policer is applied in the output direction If you configure a policer as described above but apply it in the input direction the total allowed throughput for all interfaces is 1 Gbps This is expected behavior Copyright O 2012 Juniper Networks Inc CHAPTER 12 Services Troubleshooting Port Mirroring on page 69 Troubleshooting Port Mirroring Port Mirroring Constraints and Limitations on page 69 Egress Port Mirroring with VLAN Translation on page 70 Port Mirroring Co
76. meouts Log SNMP response timeouts Off routing socket Log routing socket calls Off server Log communication with processes that are Off generating events subagent Log subagent restarts Off timer Log internal timer events Off Copyright 2012 Juniper Networks Inc Troubleshooting on the QFX Series Related Documentation Table 7 SNMP Tracing Flags continued Flag Description Default Setting varbind error Log variable binding errors Off To display the end of the log for an agent issue the show log agentd last operational mode commana edit user host run show log agentd last where agent is the name of an SNMP agent Configuring SNMP on a Device Running Junos OS Configuration Statements at the edit snmp Hierarchy Level Example Tracing SNMP Activity Configuring SNMP Monitoring RMON MIB Tables 20 Purpose Action Meaning Related Documentation Monitor remote monitoring RMON alarm event and log tables To display the RMON tables user switch gt show snmp rmon Alarm Index Variable description Value State 5 monitor jnxOperatingCPU 9 1 0 0 5 falling threshold Event Index Type Last Event 1 log and trap 2010 07 10 11 34 17 PDT Event Index 1 Description Event 1 triggered by Alarm 5 rising threshold 90 crossed variable jnxOperatingCPU 9 1 0 0 value 100 Time 2010 07 10 11 34 07 PDT Description Event 1 triggered by Alarm 5 falling threshold 75 crosse
77. mple Copyright O 2012 Juniper Networks Inc 65 Troubleshooting on the QFX Series Solution You configure an egress port filter with a counter for interface xe O 0 1 You configure an egress VLAN filter with a counter for the adminVLAN and interface xe 0 0 1 is a member of that VLAN A packet matches both filters In this case the packet is counted by only one of the counters even though it matched both filters This is expected behavior Cannot Include loss priority and policer Actions in Same Term Problem Solution You cannot include both of the following actions in the same firewall filter term in a QFX Series switch e loss priority e policer If you do so you see the following error message when you attempt to commit the configuration cannot support policer action if loss priority is configured This is expected behavior Cannot Egress Filter Certain Traffic Originating on QFX Switch Problem Solution On a QFX Series switch you cannot filter certain traffic with a firewall filter applied in the output direction if the traffic originates on the QFX switch This limitation applies to control traffic for protocols such as ICMP ping STP LACP and so on This is expected behavior Firewall Filter Match Condition Not Working with Q in Q Tunneling Problem Solution If you create a firewall filter that includes a match condition of dotiq tag or dotlq user priority and apply the f
78. ng the Examples in This Manual If you want to use the examples in this manual you can use the load merge or the load merge relative command These commands cause the software to merge the incoming configuration into the current candidate configuration The example does not become active until you commit the candidate configuration If the example configuration contains the top level of the hierarchy or multiple hierarchies the example is a full example In this case use the load merge command Copyright O 2012 Juniper Networks Inc xi Troubleshooting on the QFX Series If the example configuration does not start at the top level of the hierarchy the example is a snippet In this case use the load merge relative command These procedures are described in the following sections Merging a Full Example To merge a full example follow these steps 1 Fromthe HTML or PDF version of the manual copy a configuration example into a text file save the file with a name and copy the file to a directory on your routing platform For example copy the following configuration to a file and name the file ex script conf Copy the ex script conf file to the var tmp directory on your routing platform system scripts f commit f file ex script xsl interfaces fxpO f disable unit O family inet f address 10 0 0 1 24 2 Merge the contents of the file into your routing platform configuration by issuing the l
79. nitor jroute daemon memory usage Management process new instance detected variable sysApplEImtRunMemory 5 6 2293 Nov 4 11 52 53 switchl snmpd 944 SNMPD HEALTH MON INSTANCE Health Monitor jroute daemon memory usage Command line interface new instance detected variable sysApplElImtRunMemory 5 8 2292 Nov 4 12 10 24 switchl mgd 2293 UI CMDLINE READ LINE User jsmith command exit Nov 4 12 10 27 switchl mgd 2293 UI DBASE LOGOUT EVENT User jsmith exiting configuration mode Nov 4 12 10 31 switchl mgd 2293 UI CMDLINE READ LINE User jsmith command show log messages The sample output shows the following entries in the messages file Anew log file was created when the previous file reached the maximum size of 128 kilobytes KB The fan speed for Fan 1 2 and 3 is set at 65 percent Health monitoring activity is detected CLI commands were entered by the user jsmith Copyright O 2012 Juniper Networks Inc Monitoring Traffic Through the Router or Switch Chapter 3 Routine Monitoring Using the CLI To help with the diagnosis of a problem display real time statistics about the traffic passing through physical interfaces on the router or switch To display real time statistics about physical interfaces perform these tasks 1 Displaying Real Time Statistics About All Interfaces on the Router or Switch on page 23 2 Displaying Real Time Statistics About an Interface on the Router or
80. nstall the QFabric software on this Director device type install and then press the ENTER key To perform a network installation on this Director device type network ENTER To reinstall the software on the Director group type install and then press Enter The Director group copies the software from the external USB device occasionally displaying status messages Copying the software can take up to 10 minutes Remove the external USB device when prompted and then press Enter The Director group then reboots from the internal flash storage on which the software was just installed When the reboot is complete the Director group displays the login prompt Create a new configuration as you did when the Director group was shipped from the factory or restore the previously saved configuration file to the Director group This procedure describes how to boot and reinstall Junos OS on a Director group with access to the QFabric system default partition Ensure that you have an emergency boot device external USB device to use during the installation Log in to the QFabric system default partition To download the software from the external USB device issue the request system software download command and specify the path and the package name on the external USB device request system software download media usbdisk jinstall qfabric T1 3R1 4 rpm To install the software issue the request system software add package name
81. nstraints and Limitations Local and Remote Port Mirroring on page 69 Remote Port Mirroring Only on page 70 Local and Remote Port Mirroring The following constraints and limitations apply to local and remote port mirroring with the QFX Series You can create a total of four port mirroring configurations on OFX Series switches subject to the following limits e There can be no more than two configurations that mirror ingress traffic There can be no more than two configurations that mirror egress traffic You cannot configure local and remote port mirroring with the same port mirroring configuration That is you cannot use the interface and vlan options in one set analyzer nameoutput statement If you configure Junos OS to mirror egress packets do not configure more than 2000 VLANs on a QFX3500 or QFabric switch If you do so some VLAN packets might contain incorrect VLAN IDs This applies to any VLAN packets not only the mirror copies The ratio and loss priority options are not supported e Packets with physical layer errors are filtered out and are not sent to the output port or VLAN If you use sFlow monitoring to sample traffic it does not sample the mirror copies when they egress from the output interface Copyright O 2012 Juniper Networks Inc 69 Troubleshooting on the QFX Series You cannot mirror packets exiting or entering the following ports Dedicated Virtual Chassis interfaces
82. oad merge configuration mode command edit user host load merge var tmp ex script conf load complete Merging a Snippet To merge a snippet follow these steps 1 From the HTML or PDF version of the manual copy a configuration snippet into a text file save the file with a name and copy the file to a directory on your routing platform For example copy the following snippet to a file and name the file ex script snippet conf Copy the ex script snippet conf file to the var tmp directory on your routing platform commit file ex script snippet xsl 1 2 Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command xii Copyright O 2012 Juniper Networks Inc About the Documentation edit user host edit system scripts edit system scripts 3 Merge the contents of the file into your routing platform configuration by issuing the load merge relative configuration mode command edit system scripts user host load merge relative var tmp ex script snippet conf load complete For more information about the load command see the Junos OS CLI User Guide Documentation Conventions Table 1 on page xiii defines notice icons used in this guide Table 1 Notice Icons o Informational note Indicates important features or instructions Caution Indicates a situation that might result in loss of data or hardware damage Warning Alerts you to the risk of pers
83. onal injury or death Laser warning Alerts you to the risk of personal injury from a laser Table 2 on page xiii defines the text and syntax conventions used in this guide Table 2 Text and Syntax Conventions Convention Description Examples Bold text like this Represents text that you type To enter configuration mode type the configure command user host gt configure Fixed width text like this Represents output that appears on the user host gt show chassis alarms terminal screen No alarms currently active Copyright O 2012 Juniper Networks Inc xiii Troubleshooting on the QFX Series Table 2 Text and Syntax Conventions continued Convention Description Examples Italic text like this e Introduces important new terms e A policy term is a named structure e Identifies book names that defines match conditions and gi actions e Identifies RFC and Internet draft titles e Junos OS System Basics Configuration Guide e RFC1997 BGP Communities Attribute Italic text like this Represents variables options for which Configure the machine s domain name you substitute a value in commands or configuration statements edit root set system domain name domain name Text like this Represents names of configuration statements commands files and directories interface names configuration hierarchy levels or labels on routing platform components To configure a stub area include the stub
84. onfiguration file to the device Related Creating an Emergency Boot Device for a OFX Series Device on page 43 Documentation Performing a Recovery Installation of the Director Group If Junos OS on your Director group is damaged in some way that prevents the software from loading correctly you may need to perform a recovery installation using an emergency boot device external USB flash drive to restore the default factory installation Once you have recovered the software you need to restore the Director group configuration You can either create a new configuration as you did when the Director group was shipped from the factory or if you saved the previous configuration you can simply restore that file to the Director group You canreinstall Junos OS with or without access to the QFabric system default partition This procedure describes how to boot and reinstall Junos OS on a Director group with no access to the QFabric system default partition 1 Ensure that you have an emergency boot device external USB device with Junos OS installed to use during the installation 2 Insert the external USB device in the USB port A menu like the following appears once you are connected to the Director group Copyright O 2012 Juniper Networks Inc 45 Troubleshooting on the QFX Series 46 Juniper Networks QFabric Director Install Recovery Media To boot from the USB device wait 10 seconds or press the ENTER key To rei
85. opyright O 2012 Juniper Networks Inc iii Troubleshooting on the QFX Series Chapter 4 Routine Monitoring in Junos Space lseeeeee eren 27 Viewing Managed Devices llli ra 27 Viewing Devices as Graphics lise eee eee 27 Viewing Devicesin a Tables sies xa rer erc ban pr r EDERE a 29 Viewing Hardware Inventory for Devices 31 Viewing Physical Interfaces for Devices ua saana eee 34 Viewing Device Snapshot Details lssleeee e 35 Scanning a Message for Impact c aseesesc ito eIe m ree er SE YES 36 Part 3 Troubleshooting Chapter 5 Junas OS BaSiCS 4 04 3 637293 73 a9 a rcs fuera ta Ro a Te e e T Gn S 39 Rebooting and Halting a OFX Series Product 6 0 ccc eee 39 Recovering from a Failed Software Installation ills 40 Recovering the Root PaSSword 6 eects 4 Creating an Emergency Boot Device for a QFX Series Device 43 Performing a Recovery Installation on a QFX3500 Device and QFX3008 I Interconnect JeVIGG s 3 udo ded Ad E eorr dead BUD dade enews dus 44 Performing a Recovery Installation of the Director Group 00 45 Chapter 6 Configuration and File Management leen 47 Loading a Previous Configuration File llle 47 Reverting to the Default Factory Configuration 0 0 0 0 cc eee eee 48 Reverting to the Rescue Configuration 1 2 eee 48 Cleaning Up the System File Storage Space ene 49 Chapter 7 Eth
86. output by including the match statement at the edit snmp traceoptions file filename hierarchy level and specifying a regular expression regex to be matched edit snmp traceoptions file filename match regular expression Configuring the Trace Operations By default only important activities are logged You can specify which trace operations are to be logged by including the following flag statement with one or more tracing flags at the edit snmp traceoptions hierarchy level edit snmp traceoptions flag f 18 Copyright O 2012 Juniper Networks Inc all configuration database events general interface stats nonvolatile sets pdu policy protocol timeouts routing socket server subagent timer varbind error Chapter 3 Routine Monitoring Using the CLI Table 7 on page 19 describes the meaning of the SNMP tracing flags Table 7 SNMP Tracing Flags Flag Description Default Setting all Log all operations Off configuration Log reading of the configuration at the Off edit snmp hierarchy level database Log events involving storage andretrievalinthe Off events database events Log important events Off general Log general events Off interface stats Log physical and logical interface statistics Off nonvolatile set Log nonvolatile SNMP set request handling Off pdu Log SNMP request and response packets Off policy Log policy processing Off protocol ti
87. pyright O 2012 Juniper Networks Inc 33 Troubleshooting on the QFX Series Related Displaying Service Contract and EOL Data in the Physical Inventory Table Documentation Viewing Managed Devices on page 27 Viewing Physical Interfaces for Devices on page 34 Resynchronizing Managed Devices e Viewing and Exporting Device License Inventory Understanding How Junos Space Automatically Resynchronizes Managed Devices Viewing Physical Interfaces for Devices Junos Space displays physical interfaces by device name based on the device information in its database You can view the operational status and admin status of physical interfaces for one or more devices to troubleshoot problems Sorting is disabled for the physical interfaces view to preserve the natural slot order of the devices If the interface status changes on the managed device the data is not updated in Junos Space until the device is resynchronized with the Junos Space database To view the physical interfaces for devices 1 From the navigation ribbon select the Devices workspace 2 From the navigation ribbon select the Manage Devices icon 3 In the Manage Device inventory page select the device for which you want to view the physical interfaces 4 In the Actions drawer click View Interfaces Junos Space displays the status of the physical interfaces for a device Figure 8 Device Inventory Physical Interfaces MC Address Operational Sta Admin St
88. r Networks Inc Chapter 5 Junos OS Basics 3 When the software prompts you with the following question type y WARNING The installation will erase the contents of your disk Do you wish to continue y n y 4 The device copies the software from the emergency boot device occasionally displaying status messages Copying the software can take up to 10 minutes When the device is finished copying the software you are presented with the following prompt Mon Mar 21 21 08 41 UTC 2011 Installation successful Please select one of the following options Reboot to installed Junos after removing install media default 1 Reboot to installed Junos by disabling install media 2 Exit to installer debug shell cece eee eee eee eee 3 Install Junos to alternate slice 1 eee eee ee 4 Your choice 4 NOTE System installer will now install Junos to alternate slice Do not power off or remove the external installer media or interrupt the installation mechanism 5 Select 4 to install Junos OS to the alternate slice of the partition and then press Enter 6 Remove the emergency boot device when prompted and then press Enter The device then reboots from the internal flash storage on which the software was just installed When the reboot is complete the device displays the login prompt 7 Create anew configuration as you did when the device was shipped from the factory or restore the previously saved c
89. rarchy level You must perform both operations to delete a FC interface Copyright O 2012 Juniper Networks Inc Chapter 13 Storage Solution First delete the interface from the FC fabric and then delete the interface from the QFX Series 1 Delete the FC interface from the FC fabric to which it belongs edit user switch delete fc fabrics fabric name interface interface name For example to delete the FC interface fc 0 0 3 0 from an FC fabric named sanfabl edit user switch delete fc fabrics sanfabl interface fc 0 0 3 0 2 Delete the FC interface at the edit interfaces hierarchy level edit user switch delete interfaces interface name For example to delete the interface fc 0 0 3 0 from the switch edit user switch delete interfaces fc 0 0 3 0 Related fc fabrics Documentation interface interfaces Understanding Interfaces on an FCoE FC Gateway Troubleshooting Dropped FIP Traffic Problem Fibre Channel over Ethernet FCoE Initialization Protocol FIP traffic such as FIP VLAN discovery and notification frames is dropped on the QFX Series Cause Theinterface on which the FIP traffic is dropped does not have a native VLAN configured FIP VLAN discovery and notification messages are exchanged as untagged packets on the native VLAN After the FCoE session with the Fibre Channel switch is established FCoE traffic uses the FCoE VLAN Solution Check to ensure that every 10 Gigabit Ethernet interface
90. roubleshooting Egress Bandwidth That Exceeds the Configured Minimum Bandwidth on page 76 Troubleshooting Egress Queue Bandwidth Impacted by Congestion on page 77 Troubleshooting an Unexpected Rewrite Value on page 77 Troubleshooting a Port Reset on QFabric Systems When a Queue Stops Transmitting Traffic on page 79 Troubleshooting Egress Bandwidth That Exceeds the Configured Maximum Bandwidth Problem The maximum bandwidth of a queue when measured at the egress port exceeds the maximum bandwidth shaping rate configured for the queue Cause When you configure bandwidth for a queue or a priority group the switch accounts for the configured bandwidth as data only The switch does not rate shape the preamble and the interframe gap IFG associated with frames so the switch does not account for the bandwidth consumed by the preamble and the IFG in its maximum bandwidth calculations The measured egress bandwidth can exceed the configured maximum bandwidth when small packet sizes 64 or 128 bytes are transmitted because the preamble and the IFG are a larger percentage of the total traffic For larger packet sizes the preamble and IFG overhead are a small portion of the total traffic and the effect on egress bandwidth is minor Solution When you calculate the bandwidth requirements for queues on which you expect a significant amount of traffic with small packet sizes consider the shaping rate as the maximum bandwidth for the data only
91. rvice Information Return to Inventory V ModelNumber Part Number SerialNumber Service SKU ContractEnd EOL Status EOL Replacemer EOL Date Description AJ4410AA0031 710 023875 AJ4410AA0031 P F 07 31 2011 09 30 2011 uting Engine FPC O 750 026182 REV 08 AACY9792 DAR 07 31 2011 SRX600 PWR 64 740 024283 Rev 03 UHO9309 Table 11 on page 33 describes the information displayed in the device inventory page 32 Copyright O 2012 Juniper Networks Inc Chapter 4 Routine Monitoring in Junos Space Table 11 Device Inventory Fields Field Description Item Chassis component Depending on the device type can include the midplane backplane power supplies fan trays Routing Engine front panel module board PDM CIP PEM SCG CB FPCs and PICs Model Number Model number for the chassis component Part Number Part number and revision level of the component FRU BUILTIN indicates the component is not a FRU Serial Number Serial number of the component FRU BUILTIN indicates the component is not a FRU Service SKU Stock keeping unit SKU identifier for the service contract associated with the part This data is populated by the Service Now Devices table If Service Now is not installed or if the table contains no data this column is not displayed Contract End End date for the service contract associated with the part This data is populated by the Service Now Devi
92. rvice Now User Guide Copyright O 2012 Juniper Networks Inc Chapter 1 General Troubleshooting Table 3 Troubleshooting Resources on the QFX Series continued Troubleshooting Resource Description Documentation Junos Space Service Insight This application helps in accelerating Junos Space Service Insight User Guide operational analysis and managing the exposure to known issues You can identify devices that are nearing their End Of Life EOL and also discover and prevent issues that could occur in your network The functionality of Service Insight is dependent on the information sent from Service Now Juniper Networks Knowledge Base You can search in this database for Juniper http kb juniper net Networks product information including alerts and troubleshooting tips Troubleshooting Overview This topic provides a general guide to troubleshooting some typical problems you may encounter on your QFX Series product Table 4 on page 5 provides a list of problem categories summary of the symptom or problem and recommended actions with links to the troubleshooting documentation Table 4 Troubleshooting on the QFX Series Problem Category Symptom or Problem Recommended Action Switch hardware LCD panel shows a chassis alarm count See Chassis Alarm Messages on a QFX3500 Device components on page 10 Fan tray LED is blinking amber See Fan Tray LED on a QFX3500 Device Chassis status LED for the power is
93. s of the GateD software copyright 1988 Regents of the University of California All rights reserved Portions of the GateD software copyright 1991 D L S Associates This product includes software developed by Maker Communications Inc copyright O 1996 1997 Maker Communications Inc Juniper Networks Junos Steel Belted Radius NetScreen and ScreenOS are registered trademarks of Juniper Networks Inc in the United States and other countries The Juniper Networks Logo the Junos logo and JunosE are trademarks of Juniper Networks Inc All other rademarks service marks registered trademarks or registered service marks are the property of their respective owners Juniper Networks assumes no responsibility for any inaccuracies in this document Juniper Networks reserves the right to change modify ransfer or otherwise revise this publication without notice Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks U S Patent Nos 5 473 599 5 905 725 5 909 440 6 192 051 6 333 650 6 359 479 6 406 312 6 429 706 6 459 579 6 493 347 6 538 518 6 538 899 6 552 918 6 567902 6 578 186 and 6 590 785 Troubleshooting on the QFX Series 12 1 Copyright 2012 Juniper Networks Inc All rights reserved The information in this document is current as of the date on the title page YEAR 2000 NOTICE Juniper N
94. scheduler map shp map that associates the scheduler shp sched with the forwarding class strict high edit class of service scheduler maps 80 Copyright 2012 Juniper Networks Inc Chapter 14 Traffic Management user switch set shp map forwarding class strict high scheduler shp sched 3 Associate the scheduler map shp map with a traffic control profile shp tcp edit class of service traffic control profiles user switch set shp tcp scheduler map shp map 4 Associate the traffic control profile shp tcp with a forwarding class set shp pg and the affected interface shpnode xe 0 0 10 edit class of service user switch set interfaces shpnode xe 0 0 10 forwarding class set shp pg output traffic control profile shp tcp Related gt Understanding CoS Output Queue Schedulers Documentation Defining CoS Queue Scheduling Priority Example Configuring Queue Schedulers Example Configuring Traffic Control Profiles Priority Group Scheduling Example Configuring Forwarding Class Sets Example Configuring CoS Hierarchical Port Scheduling ETS Copyright O 2012 Juniper Networks Inc 81 Troubleshooting on the QFX Series 82 Copyright O 2012 Juniper Networks Inc
95. slation Configuration Firewall Filter Match Condition Not Working with Q in Q Tunneling on page 54 Egress Port Mirroring with VLAN Translation on page 54 Firewall Filter Match Condition Not Working with Q in O Tunneling Problem Solution If you create a firewall filter that includes a match condition of dotlq tag or dotlq user priority and apply the filter on input to a trunk port that participates in a service VLAN the match condition does not work if the Q in Q Ethertype is not Ox8100 When Q in Q tunneling is enabled trunk interfaces are assumed to be part of the service provider or data center network and therefore participate in service VLANS This is expected behavior To set the Q in Q Ethertype to Ox8100 enter the statement set dotlq tunneling ethertype Ox8100 at the edit ethernet switching options hierarchy level You must also configure the other end of the link to use the same Ethertype Egress Port Mirroring with VLAN Translation 54 Problem Solution If you create a port mirroring configuration that mirrors customer VLAN CVLAN traffic on egress and the traffic undergoes VLAN translation before being mirrored the VLAN translation does not apply to the mirrored packets That is the mirrored packets retain the service VLAN SVLAN tag that should be replaced by the CVLAN tag on egress The original packets are unaffected on these packets VLAN translation works properly and the SVLAN tag is replaced with the C
96. statement at the edit protocols ospf area area id hierarchy level Theconsole port is labeled CONSOLE angle brackets Enclose optional keywords or variables stub default metric metric gt pipe symbol Indicates a choice between the mutually exclusive keywords or variables on either side of the symbol The set of choices is often enclosed in parentheses for clarity broadcast multicast string string2 string3 pound sign Indicates a comment specified on the same line asthe configuration statement to which it applies rsvp Required for dynamic MPLS only square brackets Enclose a variable for which you can substitute one or more values community name members community ids Indention and braces Identify a level in the configuration hierarchy semicolon J Web GUI Conventions Bold text like this Identifies a leaf statement at a configuration hierarchy level Represents J Web graphical user interface GUI items you click or select edit routing options static route default f nexthop address retain e Inthe Logical Interfaces box select All Interfaces e To cancel the configuration click Cancel gt bold right angle bracket Separates levels in a hierarchy of J Web selections In the configuration editor hierarchy select Protocols Ospf xiv Copyright O 2012 Juniper Networks In
97. table row for the device or select the row for the device and click View Physical Inventory from the Actions drawer To view the physical interfaces for a device select the row for the device and click View Interfaces from the Actions drawer Related Viewing Device Statistics Documentation Viewing Hardware Inventory for Devices on page 31 Viewing and Exporting Device License Inventory e Viewing Physical Interfaces for Devices on page 34 Discovering Devices Viewing the Node List Resyncing Nodes Viewing Hardware Inventory for Devices Hardware inventory information shows the slots that are available for a device and provides information about power supplies chassis cards fans part numbers and so forth Junos Space displays hardware inventory by device name based on data that Junos Space retrieves both from the device during discovery and resync operations and from the data stored in the hardware catalog For each managed device the Junos Space hardware catalog provides descriptions for field replaceable units FRUS part numbers model numbers and the pluggable locations from which empty slots are determined Sorting is disabled for the hardware inventory page to preserve the natural slot order of the devices To view hardware inventory for devices that Junos Space manages 1 From the navigation ribbon select the Devices workspace 2 From the navigation ribbon select the Manage Devices icon The Manage D
98. te of those interfaces exceeds the line rate of a common egress interface In this case packets might be dropped from the ingress buffer These drops are not included in the count of packets dropped by the policer which causes policer statistics to underreport the total number of drops This is expected behavior Copyright O 2012 Juniper Networks Inc 67 Troubleshooting on the QFX Series Egress Policers on QFX3500 Might Allow More Throughput Than is Configured Problem Solution 68 If you configure a policer to rate limit throughput and apply it on egress to multiple interfaces on a QFX3500 switch or node the measured aggregate policed rate might be twice the configured rate depending on which interfaces you apply the policer to This occurs if you apply a policer to multiple interfaces and both of the following are true There is at least one policed interface in the range xe 0 0 0 to xe 0 0 23 or the range xe O 1 1 to xe 0 1 7 There is at least one policed interface in the range xe 0 0 24 to xe 0 0 47 or the range xe 0 1 8 to xe O 1 15 For example if you configure a policer to rate limit at 1 Gbps and apply the policer by using a firewall filter to xe O 0 0 and xe 0 0 24 in the output direction each interface is rate limited at 1 Gbps for a total allowed throughput of 2 Gbps The same behavior occurs if you apply the policer to xe O 1 1 and xe 0 0 24 each interface is rate limited at 1 Gbps If you apply the sa
99. terface on page 59 Troubleshooting Network Interfaces on page 59 Troubleshooting an Aggregated Ethernet Interface Problem Solution Related Documentation The show interfaces terse command shows that the LAG is down Check the following Verify that there is no configuration mismatch e Verify that all member ports are up e Verify that a LAG is part of family ethernet switching Layer 2 LAG or family inet Layer 3LAG Verify that the LAG member is connected to the correct LAG at the other end Verify that the LAG members belong to the same switch Verifying the Status of a LAG Interface Example Configuring Link Aggregation Between a OFX Series Product and an Aggregation Switch Troubleshooting Network Interfaces The interface on the port in which an SFP or SFP transceiver is installed in an SFP or SFP module is down Problem Cause The OFX Series has an SFP or SFP module installed The interface on the port in which an SFP or SFP transceiver is installed is down When you check the status with the CLI command show interfaces interface name the disabled port is not listed By default the SFP or SFP module operates in the 10 Gigabit Ethernet mode and supports only SFP or SFP transceivers The operating mode for the module is incorrectly set Copyright O 2012 Juniper Networks Inc 59 Troubleshooting on the QFX Series Solution Only SFP or SFP transceivers can be installed in S
100. that are impacted by the selected message If no devices are impacted by the selected message the following message appears No impacted devices found Device Snapshots Overview e Assigning Ownership Flagging a Message to Users Deleting a Message Assigning a Message to a Connected Member e Viewing Messages Assigned to a Connected Member Messages Overview Copyright O 2012 Juniper Networks Inc PART 3 Troubleshooting Junos OS Basics on page 39 Configuration and File Management on page 47 e Ethernet Switching on page 51 High Availability on page 57 Interfaces on page 59 Layer 3 Protocols on page 61 e Security on page 63 e Services on page 69 Storage on page 71 Traffic Management on page 75 Copyright O 2012 Juniper Networks Inc 37 Troubleshooting on the QFX Series 38 Copyright O 2012 Juniper Networks Inc CHAPTER 5 Junos OS Basics Rebooting and Halting a OFX Series Product on page 39 Recovering from a Failed Software Installation on page 40 Recovering the Root Password on page 41 Creating an Emergency Boot Device for a OFX Series Device on page 43 Performing a Recovery Installation on a QFX3500 Device and QFX3008 I Interconnect Device on page 44 Performing a Recovery Installation of the Director Group on page 45 Rebooting and Halting a QFX Series Product To reboot the switch issue the request system reboot command user switch gt requ
101. tion Junos Space displays information about the selected device including OS version platform IP address connection status and managed status For SRX Series devices that are configured as a chassis cluster Junos Space displays a cluster icon and indicates whether the device is the primary or secondary device as shown in the following example Figure T Inventory Page SRX Chassis Cluster Name Name srx3400 SA ary srx3400 OS Versio 10 0R2 9 Platform Connection Status Ip Managed Status Managed Status In Sync In Sync Cluster Peer Cluster Peer rx3400 HA1 srx3400 S4 28 Copyright 2012 Juniper Networks Inc Chapter 4 Routine Monitoring in Junos Space e To view hardware inventory information for a device double click the thumbnail or select the device and click View Physical Inventory from the Actions drawer Viewing Devices in a Table To view configuration and run time information for devices in a table 1 From the navigation ribbon select the Devices workspace 2 Click the Table icon in the filter bar as shown in the following example Figure 2 Table Icon Manage Devices Junos Space displays a table of devices in the inventory page Figure 3 Device Table Manage Devices Tnterfaces OS Version Platform i Connection Status Managed Status View B View View Table 10 on page 29 describes the fields displayed in the inventory window Table 10 Fields in the Manage Devices Table
102. um of 1000 pps If traffic is received at a rate faster than this limit the rate limit will cause the traffic to be dropped before it hits the threshold and the dropped packets will not be reported in L2PT statistics This can also occur if you configure a drop threshold that is less than 1000 pps but traffic is received at a faster rate For example if you configure a drop threshold of 900 pps and the VLAN receives traffic at rate of 1100 pps L2PT statistics will show that 10O packets were dropped The 100 packets dropped because of the rate limit will not be reported Similarly if you do not configure a drop threshold and the VLAN receives traffic at rate of 1100 pps the 100 packets dropped because of the rate limit will not be reported This is expected behavior Egress Filtering of L2PT Traffic Not Supported Problem Solution Related Documentation 52 Egress filtering of L2PT traffic is not supported on the QFX3500 switch That is if you configure L2PT to tunnel a protocol on an interface you cannot also use a firewall filter to filter traffic for that protocol on that interface in the output direction If you commit a configuration for this purpose the firewall filter is not applied to the L2PT tunneled traffic This is expected behavior Understanding Layer 2 Protocol Tunneling Configuring Layer 2 Protocol Tunneling Copyright O 2012 Juniper Networks Inc Chapter 7 Ethernet Switching Troubleshooting Privat
103. warm start Feb 22 20 35 07 switchl snmpd 359 SNMPD THROTTLE QUEUE DRAINED trap throttle timer handler cleared all throttled traps Feb 23 07 34 56 switchl snmpd 359 SNMPD TRAP WARM START trap generate warm SNMP trap warm start Feb 23 07 38 19 switchl snmpd 359 SNMPD TRAP COLD START trap generate cold Copyright O 2012 Juniper Networks Inc 21 Troubleshooting on the QFX Series Related Documentation SNMP trap cold start Interpreting Messages Generated in Standard Format Interpreting Messages Generated in Structured Data Format Monitoring System Log Messages Purpose Action Sample Output Meaning 22 Display system log messages about the QFX Series By looking through a system log file for any entries pertaining to the interface that you are interested in you can further investigate a problem with an interface on the switch To view system log messages user Qswitchl show log messages Nov 4 11 30 01 switchl newsyslog 2283 logfile turned over due to size gt 128K Nov 4 11 30 01 switchl newsyslog 2283 logfile turned over due to size gt 128K Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed is 65 percent for Fan 1 Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed is 65 percent for Fan 2 Nov 4 11 30 06 switchl chassism 952 CM ENV Monitor set fan speed is 65 percent for Fan 3 Nov 4 11 52 53 switchl snmpd 944 SNMPD HEALTH MON INSTANCE Health Mo
104. xample Copyright O 2012 Juniper Networks Inc Chapter 5 Junos OS Basics source Represents the name and location of the Junos OS package either on a server on the network or as a file on an external media as shown in the following two examples e Network address of the server and the path on the server for example tftp 192 17 1 28 junos jinstall qfx 11 1R1 5 domestic signed tgz e Junos OS package on a USB device commonly stored in the root drive as the only file for example file jinstall qfx 11 1R1 5 domestic signed tgz The installation now proceeds normally and ends with a login prompt Recovering the Root Password If you forget the root password for the QFX3500 switch you can use the password recovery procedure to reset the root password NOTE The root password cannot be recovered on a QFabric switch NOTE You need console access to the switch to recover the root password To recover the root password 1 Power off the switch by switching off the AC power outlet of the device or if necessary by pulling the power cords out of the QFX3500 switch power supplies Turn off the power to the management device such as a PC or laptop computer that you want to use to access the CL I Plug one end of the Ethernet rollover cable supplied with the switch into the RJ 45 to DB 9 serial port adapter supplied with the switch Plug the RJ 45 to DB 9 serial port adapter into the serial port on the mana
105. y traffic does not include the fcoe forwarding class 5 Insufficient bandwidth has been allocated for the FCoE queue or for the forwarding class set to which the FCoE queue belongs The listed numbers of the possible causes correspond to the listed numbers of the solutions in the Solutions section Copyright O 2012 Juniper Networks Inc 7 Troubleshooting on the QFX Series Solution Related Documentation 1 Check the congestion notification profile to see if PFC is enabled on the FCoE priority the correct IEEE 802 1p code point Use the show class of service congestion notification operational command to show the code points that are enabled for PFC in each congestion notification profile Check the classifier to see if the incoming FCoE traffic is assigned to the correct code point Use the show class of service classifiers ieee 802 1p operational command to verify that the FCoE forwarding class is mapped to the correct IEEE 802 1p code point Ensure that the congestion notification profile and classifier are attached to the correct ingress interface Use the operational command show configuration class of service interfaces interface name Check that the forwarding class set includes the fcoe forwarding class Use the operational command show configuration class of service forwarding class sets to show the configured priority groups and their forwarding classes Verify the amount of bandwidth allocated to the fcoe queue an

Download Pdf Manuals

Related Search

Related Contents

NX-5200 NX-5300 NX-5400  380 Series Manual  Kenroy Home 32561GRPH Installation Guide  SB13-8 - Continental Motors  Acer Aspire X1300  FireplaceXtrordinair FPX 564 User's Manual  Fujitsu AH532 User's Manual  

Copyright © All rights reserved. Failed to retrieve file