Navigation
Related Documentation
- EX, J, M, MX, PTX, T Series
- Understanding the Junos Configuration Groups
- Example: Configuring Peer Entities
Establishing Regional Configurations
In this example, one group is populated with configuration data that is standard throughout the company, while another group contains regional deviations from this standard:
[edit]user@host# show groups {standard {interfaces {<t3-*> {t3-options {compatibility-mode larscom subrate 10;idle-cycle-flag ones;}}}}northwest {interfaces {<t3-*> {t3-options {long-buildout;compatibility-mode kentrox;}}}}}apply-groups standard;interfaces {t3-0/0/0 {apply-groups northwest;}}[edit]user@host# show | display inheritance interfaces {t3-0/0/0 {#### "t3-options" was inherited from group "northwest"##t3-options {#### "long-buildout" was inherited from group "northwest"##long-buildout;#### "kentrox" was inherited from group "northwest"##compatibility-mode kentrox;#### "ones" was inherited from group "standard"##idle-cycle-flag ones;}}}
Related Documentation
- EX, J, M, MX, PTX, T Series
- Understanding the Junos Configuration Groups
- Example: Configuring Peer Entities
Published: 2012-11-27
Related Documentation
- EX, J, M, MX, PTX, T Series
- Understanding the Junos Configuration Groups
- Example: Configuring Peer Entities