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 > RADIUS and Profile Configuration for Hierarchical Policies
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

  • Hierarchical Policies for Interface Groups Overview
 

RADIUS and Profile Configuration for Hierarchical Policies

You can use profiles to configure policy parameters. There is currently no RADIUS VSA support for policy parameters. Each reference to an external parent group and the chain of references from that group to other parent groups in a series requires one parent group resource for each reference and each attachment of the policy containing these references.

The rule that applies to external parent group resource count is: one resource per (interface, policy attachment type, policy name, external parent group name, parameter name) tuple; interface is the interface where the policy is attached and policy attachment type is the type of policy attachment.

A rate-limit instance for the external parent groups is created for each hierarchical aggregation node, which is a combination of (slot, direction, parent group name, parameter value) tuple; where slot is the slot number, direction is ingress or egress. A rate-limit resource will be consumed for each instance created.

If at least one policy attachment that uses an external parent group reference has statistics enabled, then statistics for the rate-limit configured within the external parent group is enabled. Each hierarchical aggregation node requires five statistics resources.

 

Related Documentation

  • Hierarchical Policies for Interface Groups Overview
 

Published: 2012-06-21

 
  • 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