Log On/Register  

855.838.5028

JUNIPER - Junos Troubleshooting in the NOC

Duration: 3 Days
Course Price: $2,100

Course Overview

After successfully completing this training course, you should be able to:

  • Reduce the time it takes to identify and isolate the root cause of an issue impacting your network.
  • Gain familiarity with Junos products as they pertain to troubleshooting.
  • Become familiar with online resources valuable to Junos troubleshooting.
  • Gain familiarity with Junos tools used in troubleshooting.
  • Identify and isolate hardware issues.
  • Troubleshoot problems with the control plane.
  • Troubleshoot problems with interfaces and other data plane components.
  • Describe the staging and acceptance methodology.
  • Troubleshoot routing protocols.
  • Describe how to monitor your network with SNMP, RMON, JFlow, and port mirroring.
  • Become familiar with JTAC procedures.

Course Content

This three-day training course is designed to provide introductory troubleshooting skills for engineers in a network operations center (NOC) environment. Key topics within this training course include troubleshooting methodology, troubleshooting tools, hardware monitoring and troubleshooting, interface monitoring and troubleshooting, troubleshooting the data plane and control plane on devices running the Junos operating system, staging and acceptance methodology, troubleshooting routing protocols, monitoring the network, and working with JTAC. This course is based on Junos OS Release 12.2R2.5.

Course Overview

After successfully completing this training course, you should be able to:

  • Reduce the time it takes to identify and isolate the root cause of an issue impacting your network.
  • Gain familiarity with Junos products as they pertain to troubleshooting.
  • Become familiar with online resources valuable to Junos troubleshooting.
  • Gain familiarity with Junos tools used in troubleshooting.
  • Identify and isolate hardware issues.
  • Troubleshoot problems with the control plane.
  • Troubleshoot problems with interfaces and other data plane components.
  • Describe the staging and acceptance methodology.
  • Troubleshoot routing protocols.
  • Describe how to monitor your network with SNMP, RMON, JFlow, and port mirroring.
  • Become familiar with JTAC procedures.

Course Content

This three-day training course is designed to provide introductory troubleshooting skills for engineers in a network operations center (NOC) environment. Key topics within this training course include troubleshooting methodology, troubleshooting tools, hardware monitoring and troubleshooting, interface monitoring and troubleshooting, troubleshooting the data plane and control plane on devices running the Junos operating system, staging and acceptance methodology, troubleshooting routing protocols, monitoring the network, and working with JTAC. This course is based on Junos OS Release 12.2R2.5.

Who should attend

The course content is aimed at operators of devices running the Junos OS in a NOC environment. These operators include network engineers, administrators, support personnel, and reseller support personnel.

Prerequisites

JTNOC is an introductory-level course. You should have basic networking knowledge and an understanding of the Open Systems Interconnection (OSI) reference model and the TCP/IP protocol suite and also attend the Introduction to the Introduction to the Junos Operating System (IJOS)course or have equivalent experience prior to attending this class.

Day 1
Chapter 1: Course Introduction
Chapter 2: Troubleshooting as a Process
  • Before You Begin
  • The Troubleshooting Process
  • Special Challenges
  • Lab 1: The Troubleshooting Process
Chapter 3: Junos Product Families
  • The Junos OS
  • Control Plane and Data Plane
  • Field-Replaceable Units
  • Junos Product Families
  • Lab 2: Identifying Hardware Components
Chapter 4: Troubleshooting Toolkit
  • Troubleshooting Tools
  • Best Practices
  • Online Resources
  • Lab 3: Monitoring Tools and Establishing a Baseline
Day 2
Chapter 5: Hardware and Environmental Conditions
  • Hardware Troubleshooting Overview
  • Memory and Storage
  • Boot Monitoring
  • Hardware-Related System Logs
  • Chassis and Environmental Monitoring
  • Lab 4: Monitoring Hardware and Environmental Conditions
Chapter 6: Control Plane
  • Control Plane Review
  • System and User Processes
  • Routing Tables and Protocols
  • Monitoring Bridging
  • Monitoring the Address Resolution Protocol
  • Lab 5: Control Plane Monitoring and Troubleshooting
Chapter 7: Data Plane: Interfaces
  • Interface Properties
  • General Interface Troubleshooting
  • Ethernet Interface Troubleshooting
  • Lab 6: Monitoring and Troubleshooting Ethernet Interfaces
Chapter 8: Data Plane: Other Components
  • Definition of a Data Plane Problem
  • Data Plane Components
  • Data Plane Forwarding
  • Load-Balancing Behavior
  • Firewall Filters and Policers
  • Data Plane Troubleshooting Case Study
  • Lab 7: Isolate and Troubleshoot PFE Issues
Day 3
Chapter 9: Staging and Acceptance Testing
  • Physical Inspection and Power-on
  • General System Checks
  • Interface Testing
Chapter 10: Troubleshooting Routing Protocols
  • Troubleshoot OSPF
  • Troubleshoot BGP
  • Troubleshoot Routing Loops
  • Troubleshoot Route Oscillation
  • Lab 8: Troubleshooting Routing Protocols
Chapter 11: High Availability
  • Graceful Routing Engine Switchover
  • Graceful Restart
  • Nonstop Active Routing
  • Nonstop Bridging
  • Unified In-service Software Upgrade
Chapter 12: Network Monitoring
  • SNMPv2c
  • SNMPv3
  • RMON
  • Inline JFlow
  • Inline Port Mirroring
  • Lab 9: Monitoring the Network
Chapter 13: JTAC Procedures
  • Support Cases
  • Support Tools
  • Transferring Files to JTAC
Appendix A: Interface Troubleshooting
  • Troubleshooting Serial Interfaces
  • Troubleshooting
  • Troubleshooting T1, E1, T3, E3 Interfaces
  • Troubleshooting SONET Interfaces
  • Troubleshooting ATM Interfaces
  • Troubleshooting Aggregated Interfaces
Learn More
Please type the letters below so we know you are not a robot (upper or lower case):