- 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!
Guidelines for Configuring IP Multicast Adjustment for QoS
When you specify the IP multicast bandwidth adjustment application, the following considerations apply:
- You must specify a controlled-interface type.
- You cannot specify any instance-interface types or subscriber-interface types. By default, the system assigns a default instance-interface type of ip.
- When you specify the IP multicast bandwidth adjustment application, the parameter definition is hierarchical. You must specify the hierarchical keyword with the application keyword.
- The system prevents you from defining more than one parameter
definition with the ip-multicast application
specified. For example:host1(config)#qos-parameter-define vpShaper application ip-multicast hierarchical host1(config-qos-parameter-define)#controlled-interface-type ip host1(config-qos-parameter-define)#exit host1(config)#qos-parameter-define bar application ip-multicast hierarchical % there cannot be more than one parameter defined with this property
- Parameter instances associated with the IP multicast bandwidth adjustment application are not stored in non-volatile storage (NVS). (Parameter definitions are stored in NVS.) Because the application is activated based on IGMP joins and leaves received on an interface, the system removes the instances when you turn off or reset the router, then re-creates it based on new messages received on an interface.
