- Download
Software
- Research a
Problem - Case Management
- Communities and Forums
- Contract & Product Management
- Technical Documentation Advanced Search
- Documentation Feedback Form
- Documentation Symbols Key
- End-of-Life Products
- Guidelines and Policies
- Security Resources
Juniper was the first North American IP routing vendor to achieve the prestigious TL 9000 certification by the Quality of Excellence for Suppliers of Telecommunications (QuEST) Forum in the router category, for design, development, provision and service and support.
What is J-Care?
It's the world-class service and support that you expect from a company that delivers the industry's best infrastructure and security products. With J-Care, you now have the confidence knowing that Juniper will do our part to keep you on top of the world!
Configuring Shadow Nodes
Before you configure shadow nodes:
- Configure the traffic classes.
- Configure the queuing hierarchy.
See Configuring Queue Profiles to Manage Buffers and Thresholds.
- Configure the scheduler hierarchy and shaping with scheduler profiles.
To add a shadow node to a QoS profile:
- Create a QoS profile and enter QoS Profile Configuration
mode.host1(config)#qos-profile shadowNode host1(config-qos-profile)#
- Configure a scheduler node for each interface of the specified
type. host1(config-qos-profile)#atm node scheduler-profile default
- Configure a shadow node for each interface of the specified
type.host1(config-qos-profile)#atm shadow-node scheduler-profile default
- Configure a queue for interfaces in the specified traffic
class.host1(config-qos-profile)#atm queue traffic-class strict-priority scheduler-profile scheduler1
- (Optional) Configure a traffic-class group and reference
a scheduler profile in the QoS profile.host1(config-qos-profile)#atm group default scheduler-profile default
The router creates the shadow node when the following conditions are met:
- After all the nodes and group nodes are created.
- If the queues are not at the required scheduler level.
- When a node of the same interface type has existed in the same group of the scheduler hierarchy.
