Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > Shadow Node Overview
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • Shadow Nodes and Scheduler Behavior
  • Configuring Shadow Nodes
 

Shadow Node Overview

The frame forwarding ASIC (FFA) and the 10-Gigabit Ethernet forwarding ASIC (TFA) require that all queues be above the port scheduler node with two additional scheduler nodes. The router implicitly creates phantom nodes when you do not specify two scheduler nodes above the port interface. Phantom nodes cannot be monitored using show commands.

Phantom nodes have the same weight as the associated queues and are not shaped, which preserves the behavior of the queues as if they are at their original level.

Figure 1 compares a scheduler hierarchy with and without phantom nodes.

Figure 1: Phantom Nodes

Phantom Nodes

The first scheduler hierarchy displayed in Figure 1 shows Queue A, Queue B, and Node C at the same scheduler level and with the same weight of 8. They equally share the bandwidth available to the level 1 node.

The second scheduler hierarchy in Figure 1 shows the phantom nodes the router added for Queue A and Queue B. It also shows the weight associated with Queue A and Queue B. As the result, Phantom A, Phantom B, and Node C share the bandwidth of the level 1 node. The phantom nodes do not change the behavior of Queue A and Queue B.

 

Related Documentation

  • Shadow Nodes and Scheduler Behavior
  • Configuring Shadow Nodes
 

Published: 2012-06-19

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out