Ocnos Dc Openconfig Cmdref

OpenConfig Command Reference
November 2024
IP Infusion Inc. Proprietary

© 2024 IP Infusion Inc. All Rights Reserved.
This documentation is subject to change without notice. The software described in this document and this documentation
are furnished under a license agreement or nondisclosure agreement. The software and documentation may be used or
copied only in accordance with the terms of the applicable agreement. No part of this publication may be reproduced,
stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and
recording for any purpose other than the purchaser's internal use without the written permission of IP Infusion Inc.
IP Infusion Inc.
3979 Freedom Circle
Suite 900
Santa Clara, California 95054
http://www.ipinfusion.com/
For support, questions, or comments via E-mail, contact:

support@ipinfusion.com
Trademarks:
IP Infusion and OcNOS are trademarks or registered trademarks of IP Infusion. All other trademarks, service marks,
registered trademarks, or registered service marks are the property of their respective owners.
Use of certain software included in this equipment is subject to the IP Infusion, Inc. End User License Agreement at http://
www.ipinfusion.com/license. By using the equipment, you accept the terms of the End User License Agreement.
IP Infusion Inc. Proprietary 2

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
IP Maestro Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Migration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Feature Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Feature Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
OpenConfig Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Network-instance Object Values for “type” Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Enable OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
OpenConfig Optical-Channel and Terminal Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Enable OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Enable Coherent modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Host Interface, Network Interface, and Logical Channels . . . . . . . . . . . . . . . . . . . . . . . 32
Optical-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Logical-Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Optical-channel and Logical-channel behavior on OcNOS. . . . . . . . . . . . . . . . . . . . . . . . . 33
Loopback-type on Host Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Validation with Netconf get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Unconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Loopback-type on Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Disable Coherent-Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Operational-Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
© 2024 IP Infusion Inc. Proprietary 3

Contents
Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Soft-tx-disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
tx-laser-freq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
tx-output-power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ISIS OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Operation create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Deletion of AFI-SAFI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Create IS-IS instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
OpenConfig NetConf Payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
OcNOS CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
OcNOS NetConf Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configure global parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configure level traffic-engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configure AF IPv6 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configure metric parameter on AF IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Configure Global Timers parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Configure Global Transport parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configure LSP-BIT parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure Inter-level Propagation Policies parameter . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configure Graceful Restart parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configure Metric Style parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure Authentication parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure Interface IS-IS Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configure Interface Authentication Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configure Interface IGP-LDP-SYNC Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configure Interface Circuit-type Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configure Primary IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Configure Interface Passive Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Configure Interface IPv6 AF Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configure Interface BFD Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configure Interface Priority Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configure Interface Timers Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
BGP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Create BGP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Validation with NetConf get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Create BGP Global with default VRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
OcNOS CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
OcNOS NetConf Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Validation with NetConf get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Create BGP Global with User-defined VRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
OpenConfig NetConf Payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Create BGP Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Configure eBGP Neighbor with TTL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Contents
Create BGP Peer-groups with Default VRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Create BGP Peer-groups with User-defined VRFs . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Configure Update-source on Neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Double Link in Load Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Delete BGP Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
BGP RIB Counters IPv4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
BGP RIB Counters IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Contents
OSPFv2 Openconfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Create OSPF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
OpenConfig NETCONF Payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Create OSPF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
OcNOS NETCONF Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Validation with NETCONF get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Interface Configuration OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Configure Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configure Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configure MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Configure Primary IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Configure Secondary IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Configure IPv6 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Configure Duplex-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Configure Port-Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Configure Ethernet Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Configure Sub-interface with Primary and Secondary Addresses . . . . . . . . . . . . . . . 271
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
LACP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Create Static LAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Create Dynamic LAG Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Tunnel Interfaces OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Create Tunnel Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Static Route OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Create a static route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Create a Static Route with Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Create a Static Route with Active/Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Platform OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
FAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
OpenConfig Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Contents
Get OpenConfig Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Get OcNOS Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
RAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Hard-disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
PSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Get OpenConfig return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Get OpenConfig return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
OpenConfig get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
System OpenConfig Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
OcNOS CLI command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Unconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Contents
Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
TimeZone Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Rsyslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Logging Remote Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Logging Remote Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Get OpenConfig Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
OcNOS CLI show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
VLAN OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

Match Single Tagged VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Match single tagged VLAN range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Match double tagged VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Match double tagged with outer and inner VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Ingress-mapping actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Trunk VLANs in interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Trunk interface with native VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Access VLAN in interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Trunk VLANs in link aggregation interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Contents
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Trunk LAG with native VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Creation of a cross connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Deletion of a cross connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Configure Bridge Domain and associate L2 Subinterfaces . . . . . . . . . . . . . . . . . . . . . 478
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Deletion of a Bridge Domain instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Creation of a VLAN bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

Contents
LLDP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

Enable Management Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Configure chassis-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Configure suppress advertisement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Configure system name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Enable LLDP on an interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
LLDP get Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495

Contents
Neighbors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Neighbors name and description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Neighbors chassis-id, type and ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Neighbors port-id, type and description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Neighbors custom TLVs type/subtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Neighbors custom TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Neighbors capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
OcNOS get result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
ACL OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518

Enable Management Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Create IPv4 Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Create IPv6 Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Create Interfaces Egress for IPv4/IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Create Interfaces Ingress for IPv4/IPv6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Create Interfaces Egress for L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Create Interfaces Ingress for L2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
QoS OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

Enable QoS on OcNOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Enable QoS Profile on OcNOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

Contents

Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Create Classifiers Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Create Forwarding-groups Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Create Queues and Queue-Management-profiles Entries . . . . . . . . . . . . . . . . . . . . . 548
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Create Scheduler-policies Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Create Scheduler-policies entries without leaf max-queue-depth-bytes . . . . . . . . . . 552
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Create Scheduler-policies Entries with leaf max-queue-depth-bytes . . . . . . . . . . . . 565
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Create Interfaces Classifier Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580

Contents
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Create Interfaces Scheduler-policies Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
EVPN Openconfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

Configure EVPN-MAC with inter-instance-policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Configure EVPN-VPLS type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Initial Configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Configure EVPN-VPWS type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Initial Configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
OpenZR+ OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

General Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Operation create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Operation merge and create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Laser frequency configuration in OpenZR+ media channel . . . . . . . . . . . . . . . . . . . . . . . 640
Disable/enable OpenZR+ transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

Contents
Disable configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

Enable configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Configure OpenZR+ optical channel operational mode . . . . . . . . . . . . . . . . . . . . . . . . 642
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Configure OpenZR+ optical channel target output power . . . . . . . . . . . . . . . . . . . . . . 644
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Configure OpenZR+ optical channel frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Configure OpenZR+ loopback mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Validate OpenZR+ module state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Contents

Validate OpenZR+ transceiver state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Validate OpenZR+ transceiver thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Severity CRITICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Severity MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Validate OpenZR+ transceiver physical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Validate OpenZR+ transceiver optical channel state . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Validate OpenZR+ logical channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Optical channel assignment type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Logical channel assignment type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Configure OpenZR+ port-breakout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Validate OpenZR+ port-breakout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
PYANG Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

module: openconfig-acl. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
module: openconfig-bfd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
module: openconfig-if-aggregate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

Contents
module: openconfig-if-ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

module: openconfig-interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
module: openconfig-lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
module: openconfig-lldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
module: openconfig-network-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
module: openconfig-platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
module: openconfig-qos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
module: openconfig-routing-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
module: openconfig-system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
module: openconfig-terminal-device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
module: openconfig-terminal-device-properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
module: ipi-oc-if-deviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

Preface
Preface
This guide contains OpenConfig commands for OcNOS.
Note: OcNOS DC 6.5 no longer supports MPLS-based or MPLS-related features.
IP Maestro Support
Monitor devices running OcNOS Release 6.3.4-70 and above using IP Maestro software.
Audience
This guide is intended for network operators who configure and manage multi-vendor networks.
Conventions
Table 3.1 shows the conventions used in this guide.
Table 3.1: Conventions
Convention Description
Italics Emphasized terms; titles of books
Note: Special instructions, suggestions, or warnings
monospaced type Code elements such as commands, functions, parameters, files, and directories
Related Documentation
For information about installing OcNOS, see the Installation Guide for your platform.
Migration Guide
Check the Migration Guide for configuration changes to make when migrating from one version of OcNOS to another.
Feature Availability
The features described in this document are available depending upon the OcNOS SKU that you purchased. See the
Feature Matrix for a description of the OcNOS SKUs.

Preface
Support
For support-related questions, contact support@ipinfusion.com.
Comments
If you have comments, or need to report a problem with the content, contact techpubs@ipinfusion.com.

Introduction
Overview
OpenConfig Translation feature is designed to enable NETCONF clients to interact with OcNOS (a network operating
system) using standardized YANG models, particularly OpenConfig. This feature involves translating data between
OpenConfig and OcNOS data models, primarily for edit-config, get-config, get, and notification
operations. A Translation Framework has been developed to facilitate these translations.
Feature Characteristics
It is primarily designed to work with OpenConfig 2.0.0 and uses the latest models available at the time of
implementation.
The feature targets network operators who wish to manage their multi-vendor network using a standardized interface,
reducing operational costs and complexity.
Benefits
The OpenConfig Translation benefits are listed below:
Standardization: Allows network operators to manage OcNOS products using standardized YANG models, promoting
consistency and simplifying network management.
Multi-Vendor Support: Facilitates the management of multi-vendor networks through a unified interface.
Flexibility: Supports the translation of both OpenConfig and OcNOS data models, offering flexibility to network
administrators.
Error Reporting: Enables error reporting using OpenConfig paths, enhancing troubleshooting and diagnostics.
Prerequisites
Here are the prerequisites for OpenConfig Translation:
• The feature depends on using OpenConfig or OcNOS data models in the NETCONF client.
• The OcNOS NetConf server needs to be restarted and configured with translation enabled.
• The translation is based on OpenConfig release 2.0.0.
Troubleshooting
• Error reporting is done using OpenConfig paths; unknown or unsupported leafs are ignored.
• The translation may lead to the rejection of configuration if unsupported parts are encountered.
• Ensure that the correct data models are used, and translations are properly configured.

Introduction
Limitations
• Certain operations such as "replace" and "create" might not be supported on all nodes.
• Not all network configurations may be visible through NetConf if they are not supported by the translation.
• Support for RPCs and notifications in OpenConfig models are not supported.
OpenConfig Configurations
This document describes the OpenConfig configurations and state attributes supported by OcNOS SP and RON
versions 4.2, 5.0, 5.1, 6.1 and 6.2, as well the limitations that apply to some of the paths.
Network-instance Object Values for “type” Attribute

Several protocols are configured inside the Network-instance object, and what distinguishes them is the value of the /
network-instances/network-instance/config/type attribute. Additionally, for some protocols, it is
necessary to configure the leaf /network-instances/network-instance/ encapsulation/config/
encapsulation-type.
Below, there is a table listing all the values used for the current translated protocols.
OcNOS Network Instance (NI) type Open Config NI type

xpath: /network-instances/network-instance/ xpath: /network-instances/network-instance/
instance-type config/type
vrf L3VRF || DEFAULT_INSTANCE
mac-vrf L2L3 + leaf /network-instances/network-instance/

encapsulation/config/encapsulation-type as
“MPLS”
l2ni (bridge) L2L3
vpls L2VSI + leaf /network-instances/network-instance/

“MPLS”
vpws L2P2P + leaf /network-instances/network-instance/

“MPLS”
evpn L2L3 + leaf /network-instances/network-instance/

“VXLAN”
cross-connect L2P2P
bridge-domain L2VSI

Introduction
Enable OpenConfig Translation

The OpenConfig feature is disabled by default and must be enabled using the following CLI command in the OcNOS
shell:
OcNOS>enable
OcNOS#configure terminal
OcNOS(config)#netconf translation openconfig
OcNOS(config)#commit
OcNOS#show running-config netconf translation
!
netconf translation openconfig
!
Or use the equivalent NetConf:
<netconf-server xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-management-
server">
<netconf-translation>
<config>
<translation-mode>openconfig</translation-mode>
</config>
</netconf-translation>
</netconf-server>
The translation is disabled using the following CLI command in the OcNOS shell:
OcNOS>enable
OcNOS(config)#no netconf translation
OcNOS#show running-config netconf translation
OcNOS#
To get the OpenConfig data, the corresponding namespace must be given:
yangcli ocnos@localhost> sget-config /netconf-server source=running
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<netconf-server xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-
management-server">
<netconf-translation>
<config>
</config>
<state>
</state>
</netconf-server>
</data>
</rpc-reply>

OpenConfig Optical-Channel and Terminal Device
Overview
This document describes the OpenConfig configurations for Optical-Channel and Terminal Device and states the
attributes supported by OcNOS versions 5.0 and 5.1 and the limitations which apply for some of the paths.
This section used to be dedicated to Optical Transport Network (OTN), but with additional OpenZR/ZR+ support in
OcNOS release 6.5.0, this section applies to all platforms which support similar optical features.
Enable OpenConfig Translation

The OpenConfig feature is disabled by default and must be enabled using the following CLI command on the OcNOS
shell.
OcNOS#cml netconf translation (disable|openconfig)
Or using the equivalent NETCONF RPC:
<netconf-translation xmlns="http://ipinfusion.com/ns/zebmcli">
<status>disable|openconfig</status>
Once enabled, the user is still able to get data in OcNOS format by specifying the required namespace:
yangcli ocnos@localhost> sget-config /ipi-interface:interfaces source=running
This generates the following RPC:
<get-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<source>
<running/>
</source>
<filter type="subtree">
<interfaces xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-interface"/>
</filter>
</get-config>
To get OpenConfig data, the corresponding namespace must be given:
yangcli ocnos@localhost> sget-config /oc-if:interfaces source=running
<get-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<source>
<running/>
</source>
<interfaces xmlns="http://openconfig.net/yang/interfaces"/>
</filter>
</get-config>
If OpenConfig is enabled and no filter is provided, all the supported OpenConfig models are retrieved in OpenConfig
format. The OcNOS models for which no translation is supported will be retrieved in OcNOS format.

Enable Coherent modules

It is mandatory to enable the module previously for all other configurations.
Configuration
This XML configuration snippet is used to enable coherent modules (slot 6 and slot 3).
OpenConfig Netconf Payload:

Here is a sample OpenConfig NetConf Payload to enable coherent modules.
<components xmlns="http://openconfig.net/yang/platform">
<component>
<name>SLOT-6</name>
<linecard xmlns="http://openconfig.net/yang/platform/linecard">
<config>
<power-admin-state>oc-platform-types:POWER_ENABLED</power-admin-state>
</config>
</linecard>
</component>
<component>
<name>SLOT-3</name>
<config>
<power-admin-state>oc-platform-types:POWER_ENABLED</power-admin-state>
</config>
</linecard>
</component>
</components>
OcNOS CLI Command

The below CLI command is used to enable coherent modules.
OcNOS#conf t
Enter configuration commands, one per line. End with CNTL/Z.
OcNOS(config)#coherent-module 6
OcNOS(config-module)#enable
OcNOS(config-module)#commit
OcNOS Netconf Payload

Here is a sample OcNOS NetConf Payload to enable coherent modules.
<terminal-device xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform-
terminal-device">
<coherent-module>
<slot-index>3</slot-index>
<config>
<service-enable/>
</config>
</coherent-module>
<coherent-module>
<config>

<service-enable/>
</config>
</coherent-module>
</terminal-device>
Validation
Get OpenConfig Payload
This filter for the Get operation results in the Get OpenConfig Return output shown below:
<filter >
<component>
<name>SLOT-6</name>
<state>
</state>
</linecard>
</component>
</components>
</filter>
Get OpenConfig Return

This validation response provides information on the configuration and runtime for enabling coherent modules.
<component>
<name>SLOT-6</name>
<state>
<power-admin-state>POWER_ENABLED</power-admin-state>
<slot-id>6</slot-id>
</state>
</linecard>
<state xmlns:oc-platform-types="http://openconfig.net/yang/platform-
types">
<name>SLOT-6</name>
<equipment-failure xmlns="http://openconfig.net/yang/alarms">false</
equipment-failure>
<temperature>
<alarm-status>false</alarm-status>
</temperature>
<id>SLOT-6</id>
<parent>CHASSIS</parent>
<oper-status xmlns:ipi-oc-platform-types-deviations="http://
www.ipinfusion.com/yang/ocnos/ipi-oc-platform-types-deviations">oc-platform-
types:ACTIVE</oper-status>
<removable>true</removable>
<part-no>TRB200DAA-01</part-no>
<serial-no>VCD19330008</serial-no>
<software-version>NA</software-version>
<firmware-version>1.5</firmware-version>
<hardware-version>NA</hardware-version>
<description>NA</description>
<mfg-name>LUMENTUM</mfg-name>

<location>6</location>
<type xmlns:ipi-oc-platform-types-deviations="http://
types:LINECARD</type>
</state>
<subcomponents xmlns="http://openconfig.net/yang/platform">
<subcomponent>
<name>PORT-coherent-6</name>
<state>
</state>
</subcomponent>
<subcomponent>
<name>PORT-ce27</name>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
</subcomponents>
</component>
</components>
Host Interface, Network Interface, and Logical Channels

Host interface Loopback-type and Network interface prbs-type are translated to logical channels. The correlation is
shown in the image below:
Optical-channel
The optical channel contains the following:
• frequency
• operational mode
• output-power

The network interface is translated to an Optical channel and has the same value as a coherent module slot. (i.e. slot 6/
network interface 0→ och-6/0).
Logical-Channel
The logical channel contains the following:
• loopback-type
• prbs-type
The network interface is translated to logical channels. The index is represented by a 8 digits hexa number, where:
• 2 digits for slot
• 2 digits for network interface
• 2 digits for host interface
To avoid ambiguity, 1 is added to the desired interface.
For example:
Slot 6, host-interface 1 is represented by 0x060002. In OpenConfig, this number is translated to decimal 393218.
Slot 4, network-interface 0 is represented by 0x040100. In OpenConfig, this number is translated to decimal 262400.
Optical-channel and Logical-channel behavior on OcNOS

Both optical-channel and logical-channel are mapped to /terminal-device/coherent-module/network-
interfaces/network-interface on OcNOS. Hence, some specific information about configuration and
unconfiguration are necessary.
Here is the mapping:
OcNOS XPATH OpenConfig XPATH

/terminal-device/coherent-module/network-interfaces/ /components/component[name=OCH-X/Y]/optical-channel/
interface/config/frequency config/frequency
interface/config/operational-mode config/operational-mode
interface/config/target-output-power config/target-output-power
/terminal-device/coherent-module/network-interfaces/ /terminal-device/logical-channels/channel[index]/config/
interface/config/soft-tx-disable admin-state
/terminal-device/coherent-module/network-interfaces/ /terminal-device/logical-channels/channel[index]/config/
interface/config/loopback-type loopback-mode
When the user creates optical-channel or logical-channel for the first time, it already creates the structure of /
terminal-device/coherent-module/network-interfaces/interface/.
When the user wants to delete the entire component OCH or logical-channels/channel, it tries to delete /terminal-
device/coherent-module/network-interfaces/interface/. So it is important to delete only one of them.
It is recommended to delete network-interfaces through component OCH.
Here are some examples:
<component operation="delete">
<name>OCH-1/0</name>

<channel operation=”delete”>
<index>393218</index>
To delete the network-interfaces/interface in OcNOS, there is a restriction that it must be empty and not have any
configuration under it. So, if the user wants to delete on that level, the other configurations must be deleted one by one.
Loopback-type on Host Interface

This configuration is used to configure loopback type on the host interface.
The two possible values are: FACILITY (shallow in Netconf mode) and TERMINAL (deep in Netconf mode).
Configuration
Configure slot 6, Host-interface 1 loopback -type to shallow.
OpenConfig Netconf Payload

Here is a sample OpenConfig NetConf Payload to configure loopback type on host interface.
<terminal-device xmlns="http://openconfig.net/yang/terminal-device">
<logical-channels>
<channel>
<config>
<loopback-mode>oc-opt-types:FACILITY</loopback-mode>
</config>
</channel>
</logical-channels>
</terminal-device>
OcNos CLI Command

The below CLI command is used to configure loopback type on host interface.
OcNOS#conf t
OcNOS(config-module)#host-interface 1
OcNOS(config-hostif)#loopback-type shallow
OcNOS(config-hostif)#commit
OcNOS(config-hostif)#

Here is a sample OcNOS NetConf Payload to configure loopback type on host interface.
terminal-device">
<coherent-module>
<host-interfaces>
<interface>
<host-index>1</host-index>
<config>
<host-index>1</host-index>
<loopback-type>shallow</loopback-type>

</config>
</interface>
</host-interfaces>
</coherent-module>
</terminal-device>
Validation with Netconf get

Get Openconfig Payload
This filter for the Get operation results in the Get OpenConfig Return output shown below.
<logical-channels>
<channel>
<state/>
</channel>
</logical-channels>
</terminal-device>
</filter>

This validation response provides information on the configuration and runtime for configuring loopback type on host
interface.
<logical-channels>
<channel xmlns:oc-opt-types="http://openconfig.net/yang/transport-types">
<state>
<logical-channel-type>oc-opt-types:PROT_ETHERNET</logical-channel-
type>
<trib-protocol>oc-opt-types:PROT_ODU4</trib-protocol>
<description>preset</description>
<loopback-mode>FACILITY</loopback-mode>
</state>
<ethernet>
<state>
<out-block-errors>0</out-block-errors>
<out-pcs-bip-errors>0</out-pcs-bip-errors>
<in-block-errors>0</in-block-errors>
<in-pcs-bip-errors>2</in-pcs-bip-errors>
</state>
</ethernet>
</channel>
</logical-channels>
</terminal-device>
Unconfiguration
Use the delete operation remove this configuration, as shown below:

<logical-channels>
<channel>
<config>
<loopback-mode operation='delete'/>
</config>
</channel>
</logical-channels>
</terminal-device>
Loopback-type on Network Interface

This configuration is used to configure loopback type on the network interface.
The two possible values are: FACILITY (shallow in NetConf mode) and TERMINAL (deep in NetConf mode).
Configuration
Configuration of deep mode at slot 6, Network interface 0, loopback-type to deep.

Here is a sample OpenConfig NetConf Payload to configure loopback type on the network interface.
<logical-channels>
<channel>
<config>
<loopback-mode>oc-opt-types:TERMINAL</loopback-mode>
</config>
</channel>
</logical-channels>
</terminal-device>
OcNos CLI Command

The below CLI command is used to configure loopback type on the network interface.
OcNOS#conf t
OcNOS(config-module)#network-interface 0
OcNOS(config-netif)#loopback-type deep
OcNOS(config-netif)#commit

Here is a sample OcNOS NetConf Payload to configure loopback type on the network interface.
terminal-device">
<coherent-module>
<network-interfaces>

<interface>
<net-index>0</net-index>
<config>
<loopback-type>deep</loopback-type>
</config>
</interface>
</network-interfaces>
</coherent-module>
</terminal-device>

This filter for the Get operation results in the Get OpenConfig Return output shown below
<logical-channels>
<channel>
<state/>
</channel>
</logical-channels>
</terminal-device>
</filter>

This validation response provides information on the configuration and runtime for configuring loopback type on the
network interface.
<logical-channels>
<channel xmlns:oc-opt-types="http://openconfig.net/yang/transport-types">
<state>
<admin-state>ENABLED</admin-state>
<logical-channel-type>oc-opt-types:PROT_OTN</logical-channel-type>
<trib-protocol>oc-opt-types:PROT_OTU4</trib-protocol>
<loopback-mode>TERMINAL</loopback-mode>
</state>
<logical-channel-assignments>
<assignment>
<index>1</index>
<state>
<index>1</index>
<assignment-type>OPTICAL_CHANNEL</assignment-type>
<optical-channel>OCH-6/0</optical-channel>
</state>
</assignment>
</logical-channel-assignments>
<otn>
<state>

<q-value>
<instant>2.60</instant>
</q-value>
<fec-uncorrectable-blocks>0</fec-uncorrectable-blocks>
<errored-blocks>0</errored-blocks>
</state>
</otn>
</channel>
</logical-channels>
</terminal-device>
Unconfiguration
Use the delete operation to remove this configuration, as shown below:
<logical-channels>
<channel>
<config>
<loopback-mode operation='delete'/>
</config>
</channel>
</logical-channels>
</terminal-device>
Disable Coherent-Modules
Configuration
This configuration is used to disable coherent module 6.

Here is a sample NetConf Payload to disable coherent module 6.
<component>
<name>SLOT-6</name>
<config>
<power-admin-state>oc-platform-types:POWER_DISABLED</power-admin-state>
</config>
</linecard>
</component>
</components>
OcNos CLI Command

The below CLI command is used to disable coherent module 6
OcNOS#conf t

OcNOS(config-module)#disable
OcNOS(config-module)#commit

Here is a sample NetConf Payload to disable coherent module 6.
terminal-device">
<coherent-module>
<config>
<service-enable operation='delete'/>
</config>
</coherent-module>
</terminal-device>

<filter >
<component>
<name>SLOT-6</name>
<state>
</state>
</linecard>
</component>
</components>
</filter>

This validation response provides information on the configuration and runtime for disabling coherent module 6.
<component>
<name>SLOT-6</name>
<state>
<power-admin-state>POWER_DISABLED</power-admin-state>
<slot-id>6</slot-id>
</state>
</linecard>
types">
<name>SLOT-6</name>
<equipment-failure xmlns="http://openconfig.net/yang/alarms">false</
equipment-failure>
<temperature>
</temperature>
<id>SLOT-6</id>

types:INACTIVE</oper-status>
<part-no>NA</part-no>
<serial-no>NA</serial-no>
<firmware-version>NA</firmware-version>
<mfg-name>NA</mfg-name>
<type xmlns:ipi-oc-platform-types-deviations="http://www.ipinfusion.com/
yang/ocnos/ipi-oc-platform-types-deviations">oc-platform-types:LINECARD</type>
</state>
<subcomponents xmlns="http://openconfig.net/yang/platform">
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
</subcomponents>
</component>
</components>
Operational-Mode
This XML configuration snippet is used to select the operational modes.
Each mode configures specific modulation-format, fec-mode, speed, and grid-spacing.
Configuration
Configure operational-mode 6 at slot 6, interface 0.

Here is a sample OpenConfig NetConf Payload to select the operational modes.
<component>
<optical-channel xmlns="http://openconfig.net/yang/terminal-device">

<config>
<operational-mode>6</operational-mode>
</config>
</optical-channel>
</component>
</components>
OcNos CLI Command

The below CLI command is used to select the operational modes.
OcNOS#conf t
OcNOS(config-netif)#operational-mode 6
OcNOS(config-netif)#
OcNOS NetConf Payload

Here is a sample OcNOS NetConf Payload to select the operational modes.
terminal-device">
<coherent-module>
<interface>
<config>
</config>
</interface>
</coherent-module>
</terminal-device>

<component>
<state>
<operational-mode/>
</state>
</optical-channel>
</component>
</components>
</filter>


This validation response provides information on the configuration and runtime for selecting the operational modes.
<component>
<state>
</state>
</optical-channel>
types">
<id>OCH-6/0</id>
<parent>PORT-coherent-6</parent>
types:INACTIVE</oper-status>
<removable>false</removable>
yang/ocnos/ipi-oc-platform-types-deviations">oc-opt-types:OPTICAL_CHANNEL</
type>
</state>
</component>
</components>
Unconfiguration
<component>
<config>
<operational-mode operation='delete'/>
</config>
</optical-channel>
</component>
</components>
Restriction
The acceptable values range is 1-6.

Soft-tx-disable
This XML configuration snippet is used to disable the transmission of data on a network interface.
Configuration
Disable transmission of slot 6, network interface 0.

Here is a sample OpenConfig NetConf Payload to disable the transmission of data on a network interface.
<logical-channels>
<channel>
<config>
<admin-state>oc-opt-types:DISABLED</admin-state>
</config>
</channel>
</logical-channels>
</terminal-device>
OcNos CLI Command

The below CLI command is used to disable the transmission of data on a network interface.
OcNOS#conf t
OcNOS(config-netif)#soft-tx-disable

Here is a sample OcNOS NetConf Payload to disable the transmission of data on a network interface.
terminal-device">
<coherent-module>
<interface>
<config>
<soft-tx-disable/>
</config>
</interface>
</coherent-module>
</terminal-device>


<logical-channels>
<channel>
<state>
<admin-state/>
</state>
</channel>
</logical-channels>
</terminal-device>
</filter>

This validation response provides information on the configuration and runtime for disabling the transmission of data on
a network interface.
<logical-channels>
<channel xmlns:oc-opt-types="http://openconfig.net/yang/transport-
types">
<state>
<admin-state>DISABLED</admin-state>
<logical-channel-type>oc-opt-types:PROT_OTN</logical-channel-type>
<trib-protocol>oc-opt-types:PROT_OTU4</trib-protocol>
</state>
<assignment>
<index>1</index>
<state>
<index>1</index>
</state>
</assignment>
</channel>
</logical-channels>
</terminal-device>
Unconfiguration
<logical-channels>
<channel>

<config>
<admin-state operation='delete'>
</config>
</channel>
</logical-channels>
</terminal-device>
tx-laser-freq
This XML configuration snippet is used to set the laser frequency for a network interface in Hz, THz, GHz, and MHz.
Configuration
Configure the frequency 196100GHz at slot 6 network interface 0.

Here is a sample OpenConfig NetConf Payload to set the laser frequency for a network interface in Hz, THz, GHz, and
MHz.
<component>
<config>
<frequency>196100000.000000</frequency>
</config>
</optical-channel>
</component>
</components>
OcNos CLI Command

Here is a sample CLI command used to set the laser frequency for a network interface.
OcNOS#conf t
OcNOS(config-netif)#tx-laser-freq 196100000000000Hz

Here is a sample OcNOS NetConf Payload to set the laser frequency for a network interface.
terminal-device">
<coherent-module>
<interface>
<config>

<frequency>196100000.000000MHz</frequency>
</config>
</interface>
</coherent-module>
</terminal-device>

<component>
<state>
<oper-status/>
</state>
</optical-channel>
</component>
</components>
</filter>

This validation response provides information on the configuration and runtime for setting the laser frequency for a
network interface.
<component>
<state>
<frequency xmlns:ipi-oc-terminal-device-deviations="http://
www.ipinfusion.com/yang/ocnos/ipi-oc-terminal-device-deviations">191250000</
frequency>
<line-port>PORT-coherent-6</line-port>
</state>
</optical-channel>
types">
<id>OCH-6/0</id>
types:DISABLED</oper-status>

type>
</state>
</component>
<component>
<name>CFP-6</name>
<transceiver xmlns="http://openconfig.net/yang/platform/transceiver">
<physical-channels>
<channel>
<index>1</index>
<state>
<index>1</index>
<output-frequency xmlns:ipi-oc-platform-transceiver-
deviations="http://www.ipinfusion.com/yang/ocnos/ipi-oc-platform-transceiver-
deviations">191250000</output-frequency>
</state>
</channel>
</physical-channels>
</transceiver>
</component>
</components>
Unconfiguration
<component>
<config>
<frequency operation='delete'/>
</config>
</optical-channel>
</component>
</components>
Restriction
The permitted range is correlated to module brand.
tx-output-power
This XML configuration snippet is used to set the output power of the network interface in dBm.
Configuration
Configure tx-output-power to 1.0dBm at Slot 6, network-interface 0.

Here is a sample OpenConfig NetConf Payload to set the output power of the network interface in dBm.

<component>
<config>
<target-output-power>1.0</target-output-power>
</config>
</optical-channel>
</component>
</components>
OcNos CLI Command

The below CLI command is used to set the output power of the network interface in dBm.
OcNOS#conf t
OcNOS(config-netif)#tx-output-power 1.00

Here is a sample OcNOS NetConf Payload to set the output power of the network interface in dBm.
<component>
<config>
</config>
</optical-channel>
</component>
</components>

<component>
<state>
<target-output-power/>
</state>
</optical-channel>
</component>
</components>
</filter>


This validation response provides information on the configuration and runtime for setting the output power of the
network interface in dBm.
<component>
<state>
</state>
</optical-channel>
types">
<id>OCH-6/0</id>
type>
</state>
</component>
</components>
Unconfiguration
<component>
<config>
<target-output-power operation='delete'/>
</config>
</optical-channel>
</component>
</components>

ISIS OpenConfig Translation
General Restrictions
Operation create
• NETCONF’s operation="create" is only supported at objectlist elements. For example: /network-
instances/network-instance/protocols/protocol/isis/interfaces/interface[interface-
id]. Payloads with this operation on other elements have undefined behavior.
Deletion of AFI-SAFI
By default AF-IPv4 is always present on IS-IS global configuration and cannot be deleted. Deletion of this entry affects
only its children configuration, if any. No error message is expected otherwise.
When deleting /oc-netinst:network-instances/network-instance/protocols/protocol/isis/
global/afi-safi or /oc-netinst:network-instances/network-instance/protocols/protocol/
isis/global/afi-safi/af, the following occurs:
• Operation=”delete” will be placed at the supported attribute’s nodes.
• If AF-IPv6 is configured, it will remove the entire element from af object-list.
Create IS-IS instance

This XML configuration snippet is used to configure an IS-IS instance.
Release
This configuration was introduced in OcNOS version 6.4.1.
OpenConfig NetConf Payload

Here is a sample OpenConfig NetConf Payload to configure an IS-IS instance.
<network-instances xmlns="http://openconfig.net/yang/network-instance">
<network-instance>
<name>default</name>
<protocols>
<protocol>
<identifier
xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">oc-pol-
types:ISIS</identifier>
<name>ABC</name>
<isis>
<global>
<afi-safi>

<af>
<afi-name
xmlns:oc-isis-types="http://openconfig.net/yang/isis-
types">oc-isis-types:IPV4</afi-name>
<safi-name
types">oc-isis-types:UNICAST</safi-name>
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</global>
</isis>
<config>
<identifier
xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">oc-
pol-types:ISIS</identifier>
<name>ABC</name>
<enabled>true</enabled>
</config>
</protocol>
</protocols>
</network-instance>
</network-instances>
OcNOS CLI Command

The below CLI command is used to configure an IS-IS instance.
router isis ABC

Here is a sample OcNOS NetConf Payload to configure an IS-IS instance.
<isis xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-isis">
<isis-instances>
<isis-instance>
<instance>ABC</instance>
<config>
<vrf-name>default</vrf-name>
</config>
</isis-instance>
</isis-instances>
</isis>
Restrictions
• An instance without AF-IPv4 support cannot be configured.

• AF-IPv4 cannot be deleted.

• Only safi-name UNICAST is supported.
• operation="create" is not supported on the objectlist isis/global/afi-safi/af.
Configure global parameters

This XML configuration snippet is used to configure the following IS-IS global parameters:
• metric
• level-capability
• maximum-area-addresses
• net
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS global parameters.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
<metric>10</metric>
</config>
</af>
</afi-safi>
<config>

<level-capability>LEVEL_2</level-capability>
<maximum-area-addresses>5</maximum-area-addresses>
<net>49.0000.0000.0001.00</net>
</config>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI is used to configure IS-IS global parameters.
router isis ABC
distance 10
is-type level-2-only
max-area-address 5
net 49.0000.0000.0001.00

Here is a sample OcNOS NetConf Payload to configure IS-IS global parameters.
<isis-instances>
<isis-instance>
<config>
<distance>10</distance>
<level-capability>level-2-only</level-capability>
<maximum-area-addresses>5</maximum-area-addresses>
</config>
<network-entity-title>
<config>
<net>49.0000.0000.0001.00</net>
</config>
</network-entity-title>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None

Configure level traffic-engineering

This XML configuration snippet is used to configure IS-IS level traffic-engineering.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS level traffic-engineering.
<network-instance>
<protocols>
<protocol>
<identifier xmlns:oc-pol-types="http://openconfig.net/yang/policy-
types">oc-pol-types:ISIS</identifier>
<name>ABC</name>
<isis>
<levels >
<level >
<level-number>1</level-number>
<config >
<metric-style>WIDE_METRIC</metric-style>
</config>
<traffic-engineering >
<config>
<ipv4-router-id operation='delete' />
</config>
</traffic-engineering>
</level>
<level >
<config>
</config>
<traffic-engineering>
<config>
<ipv4-router-id />
</config>
</level>
</levels>
</isis>
<config>
<identifier xmlns:oc-pol-types="http://openconfig.net/yang/policy-
types">oc-pol-types:ISIS</identifier>
<name>ABC</name>

</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS level traffic-engineering.
router isis ABC
mpls traffic-eng router-id 10.10.0.23
router isis ABC

mpls traffic-eng ipv6 router-id 10.10.0.23

Here is a sample OcNOS NetConf Payload to configure IS-IS level traffic-engineering.
<isis-instances>
<isis-instance>
<config>
</config>
<metric>
<style>wide</style>
<level-number>level-1-2</level-number>
<config>
<style>wide</style>
<level-number>level-1-2</level-number>
</config>
</metric>
<traffic-engineering>
<config>
<ipv4-router-id>10.10.0.11</ipv4-router-id>
</config>
<mpls-traffic-engg>
<config>
<enable-level-1 />
<enable-level-2 />
</config>
</mpls-traffic-engg>
</isis-instance>
</isis-instances>
</isis>
Restrictions
• When configuring traffic-engineering on the OcNOS side, the router-id will be set up at both levels (level-1 and
level-2) on the OpenConfig side.

• The configuration on the OpenConfig side must have the same router-ids for both levels.
• Deletion will only work if the router-ids for both levels are deleted.
Configure AF IPv6 support

This XML configuration snippet is used to configure IS-IS instance with IPv6 support.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS instance with IPv6 support.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABCv6</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
<af>
<afi-name
<safi-name
<config>
<afi-name

<safi-name
</config>
</af>
</afi-safi>
</global>
</isis>
<config>
<identifier
<name>ABCv6</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS instance with IPv6 support.
router isis ABCv6
address-family ipv6

Here is a sample OcNOS NetConf Payload to configure IS-IS instance with IPv6 support.
<isis-instances>
<isis-instance>
<instance>ABCv6</instance>
<config>
</config>
<address-family-ipv6>
<config>
<afi-name>ipv6</afi-name>
</config>
</address-family-ipv6>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None

Configure metric parameter on AF IPv6

This XML configuration snippet is used to configure IS-IS global parameter metric on AF IPv6.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS global parameter metric on AF IPv6.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABCv6</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
<metric>20</metric>

</config>
</af>
</afi-safi>
</global>
</isis>
<config>
<identifier
<name>ABCv6</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS global parameter metric on AF IPv6.
router isis ABCv6
address-family ipv6
distance 20
exit-address-family

Here is a sample OcNOS NetConf Payload to configure IS-IS global parameter metric on AF IPv6.
<isis-instances>
<isis-instance>
<config>
</config>
<config>
<afi-name>ipv6</afi-name>
<administrative-distance>20</administrative-distance>
</config>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None

Configure Global Timers parameters

This XML configuration snippet is used to configure the following IS-IS global timers parameters:
• lsp-refresh-interval
• lsp-lifetime-interval
• spf-first-interval
• spf-second-interval
• lsp-max-wait-interval
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS global timers parameters.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<timers>
<config>
<lsp-refresh-interval>1</lsp-refresh-interval>
<lsp-lifetime-interval>350</lsp-lifetime-interval>
</config>
<spf>

<config>
<spf-first-interval>0</spf-first-interval>
<spf-second-interval>2147483647</spf-second-interval>
</config>
</spf>
<lsp-generation>
<config>
<lsp-max-wait-interval>40</lsp-max-wait-interval>
</config>
</lsp-generation>
</timers>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS global timers parameters.
router isis ABC
lsp-gen-interval 40
lsp-refresh-interval 1
max-lsp-lifetime 350
spf-interval-exp 0 2147483647

Here is a sample OcNOS NetConf Payload to configure IS-IS global timers parameters.
<isis-instances>
<isis-instance>
<config>
</config>
<timers>
<config>
<lsp-refresh-interval>1</lsp-refresh-interval>
<lsp-lifetime-interval>350</lsp-lifetime-interval>
</config>
</timers>
<spf-levels>
<spf-level>
<level>level-1-2</level>

<spf-delay>
<spf-min-delay>0</spf-min-delay>
<spf-max-delay>2147483647</spf-max-delay>
<config>
<spf-min-delay>0</spf-min-delay>
<spf-max-delay>2147483647</spf-max-delay>
</config>
</spf-delay>
<config>
</config>
</spf-level>
</spf-levels>
<levels>
<level>
<type>level-1-2</type>
<config>
<lsp-max-wait-interval>40</lsp-max-wait-interval>
</config>
</level>
</levels>
</isis-instance>
</isis-instances>
</isis>
Restrictions
The following timer parameters are supported only in OcNOS level-1-2.
• spf-interval-exp
• max-lsp-lifetime
• lsp-max-wait-interval
Configure Global Transport parameter

This XML configuration snippet is used to configure IS-IS global transport parameter lsp-mtu-size.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS global transport parameter lsp-mtu-size.
<network-instance>
<protocols>
<protocol>
<identifier

<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<transport>
<config>
<lsp-mtu-size>600</lsp-mtu-size>
</config>
</transport>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS global transport parameter lsp-mtu-size.
router isis ABC
lsp-mtu 600

Here is a sample OcNOS NetConf Payload to configure IS-IS global transport parameter lsp-mtu-size.
<isis-instances>
<isis-instance>

<config>
</config>
<levels>
<level>
<config>
<lsp-mtu-size>600</lsp-mtu-size>
</config>
</level>
</levels>
</isis-instance>
</isis-instances>
</isis>
Restrictions
The parameter lsp-mtu-size is only supported on OcNOS level-1-2.
Configure LSP-BIT parameter

This XML configuration snippet is used to configure IS-IS global parameter LSP-BIT’s set-bit and set-bit-on-boot.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS global parameter LSP-BIT’s set-bit and set-bit-on-
boot.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name

<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<lsp-bit>
<overload-bit>
<config>
<set-bit>true</set-bit>
<set-bit-on-boot>true</set-bit-on-boot>
</config>
<reset-triggers>
<reset-trigger>
<reset-trigger
types">oc-isis-types:WAIT_FOR_BGP</reset-trigger>
<config>
<reset-trigger
types">oc-isis-types:WAIT_FOR_BGP</reset-trigger>
</config>
</reset-trigger>
</reset-triggers>
</overload-bit>
</lsp-bit>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS global parameter LSP-BIT’s set-bit and set-bit-on-boot.
router isis ABC
set-overload-bit on-startup wait-for-bgp

Here is a sample OcNOS NetConf Payload to configure IS-IS global parameter LSP-BIT’s set-bit and set-bit-on-boot.
<isis-instances>

<isis-instance>
<config>
</config>
<lsp-over-load>
<config>
<enabled/>
<set-bit-on-boot>wait-for-bgp</set-bit-on-boot>
</config>
</lsp-over-load>
</isis-instance>
</isis-instances>
</isis>
Restrictions
• When set-bit-on-boot is set, reset-trigger is always oc-isis-types: WAIT_FOR_BGP.
• operation="create" is not supported on objectlist lsp-bit/overload-bit/reset-triggers/reset-
trigger.
Configure Inter-level Propagation Policies parameter

This XML configuration snippet is used to configure the foloowing IS-IS inter-level propagation policies:
• level1-to-level2
• level2-to-level1
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS inter-level propagation policies.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name

<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<inter-level-propagation-policies>
<level1-to-level2>
<config>
<default-import-policy>ACCEPT_ROUTE</default-import-policy>
</config>
</level1-to-level2>
<level2-to-level1>
<config>
</config>
</level2-to-level1>
</inter-level-propagation-policies>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS inter-level propagation policies.
router isis ABC
redistribute isis level-1 into level-2
redistribute isis level-2 into level-1

Here is a sample OcNOS NetConf Payload to configure IS-IS inter-level propagation policies.
<isis-instances>
<isis-instance>
<config>

</config>
<redistribute-level-1-into-2>
<enable/>
<config>
<enable/>
</config>
</redistribute-level-1-into-2>
<redistribute-level-2-into-1>
<enable/>
<config>
<enable/>
</config>
</redistribute-level-2-into-1>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None
Configure Graceful Restart parameter

This XML configuration snippet is used to configure IS-IS graceful restart parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS graceful restart parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name

<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<graceful-restart>
<config>
<enabled>false</enabled>
</config>
</graceful-restart>
</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS graceful restart parameter.
router isis ABC
no capability restart graceful

Here is a sample NetConf Payload to configure IS-IS graceful restart parameter.
<isis-instances>
<isis-instance>
<config>
<disable-gr-capability/>
</config>
</isis-instance>
</isis-instances>
</isis>

Restrictions
• IS-IS Graceful Restart is enabled by default on OcNOS.
Configure Metric Style parameter

This XML configuration snippet is used to configure IS-IS metric-style parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS metric-style parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<levels>
<level>
<config>
</config>
</level>
</levels>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>

</global>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS metric-style parameter.
router isis ABC
metric-style wide level-1

Here is a sample OcNOS NetConf Payload to configure IS-IS metric-style parameter.
<isis-instances>
<isis-instance>
<metric>
<style>wide</style>
<level-number>level-1</level-number>
<config>
<style>wide</style>
<level-number>level-1</level-number>
</config>
</metric>
<config>
</config>
</isis-instance>
</isis-instances>
</isis>
Restrictions
• When configuring metric-style parameter on both levels together, both the values must match.
Configure Authentication parameter

This XML configuration snippet is used to configure IS-IS instance authentication.

Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS instance authentication.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<global>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</global>
<levels>
<level>
<authentication>
<config>
<auth-password>A-PWD</auth-password>
</config>
</authentication>
<config>
</config>
</level>
<level>
<authentication>
<config>
<auth-password>D-PWD</auth-password>
</config>
</authentication>

<config>
</config>
</level>
</levels>
</isis>
<config>
<identifier
<name>ABC</name>
</config>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS instance authentication.
router isis ABC
area-password A-PWD
domain-password D-PWD

Here is a sample OcNOS NetConf Payload to configure IS-IS instance authentication.
<isis-instances>
<isis-instance>
<config>
</config>
<area-authentication>
<config>
<area-password>A-PWD</area-password>
</config>
</area-authentication>
<domain-authentication>
<config>
<domain-password>D-PWD</domain-password>
</config>
</domain-authentication>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None

Configure Interface IS-IS Parameter

This XML configuration snippet is used to associate an interface to an IS-IS instance:
• interface-id
• hello-padding.
Release

Here is a sample OpenConfig NetConf Payload to associate an interface to an IS-IS instance.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-id>eth2</interface-id>
<interface-ref>
<config>
<interface>eth2</interface>
</config>
</interface-ref>
<config>
<hello-padding>STRICT</hello-padding>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>

</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to associate an interface to an IS-IS instance.
interface eth2
ip address 22.22.22.10/24
ip router isis ABC

Here is a sample OcNOS NetConf Payload to associate an interface to an IS-IS instance.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<interface-parameters>
<config>
<ipv4-instance-tag>ABC</ipv4-instance-tag>
</config>
</interface-parameters>
</interface>
</interfaces>
</isis>
Restrictions
• There is a deviation to make oc-netinst:isis/interfaces/interface/afi-safi/af mandatory when
oc-netinst:isis/interfaces/interface is being configured.
• On OcNOS, IS-IS interface-related configuration can be applied even if the IS-IS instance is not yet created. In this
case, edit operations using OpenConfig namespace will not work.
Configure Interface Authentication Parameter

This XML configuration snippet is used to configure IS-IS interface authentication.
Release


Here is a sample OpenConfig NetConf Payload to configure IS-IS interface authentication.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<levels>
<level>
<config>
</config>
<hello-authentication>
<config>
<auth-password>ABCDEFGHIJ</auth-password>
</config>
</hello-authentication>
</level>
</levels>
</interface>

</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS interface authentication.
interface eth2
ip address 22.22.22.10/24
ip router isis ABC
isis password ABCDEFGHIJ level-1

Here is a sample OcNOS NetConf Payload to configure IS-IS interface authentication.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
</config>
<level-infos>
<level-info>
<level>level-1</level>
<config>
<password>ABCDEFGHIJ</password>
</config>
</level-info>
</level-infos>
</interface>
</interfaces>
</isis>
Restrictions
None
Configure Interface IGP-LDP-SYNC Parameter

This XML configuration snippet is used to configure IS-IS igp-ldp-sync parameter.

Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS igp-ldp-sync parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<mpls>
<igp-ldp-sync>
<config>
</config>
</igp-ldp-sync>
</mpls>
</interface>
</interfaces>

</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS igp-ldp-sync parameter.
interface eth2
mpls ldp-igp sync isis level-1-2

Here is a sample OcNOS NetConf Payload to configure IS-IS igp-ldp-sync parameter.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
</config>
<igp-ldp-sync>
<config>
<hold-timer>70000</hold-timer>
</config>
</igp-ldp-sync>
</interface>
</interfaces>
</isis>
Restrictions
• When igp-ldp-sync is configured, OcNOS will use a default hold-timer value of 70000.
• This parameter is only supported on OcNOS level-1-2.
Configure Interface Circuit-type Parameter

This XML configuration snippet is used to configure IS-IS interface’s circuit-type parameter.
Release


Here is a sample OpenConfig NetConf Payload to configure IS-IS interface’s circuit-type parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
<circuit-type>POINT_TO_POINT</circuit-type>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS interface’s circuit-type parameter.

interface eth2
isis network point-to-point

Here is a sample OcNOS NetConf Payload to configure IS-IS interface’s circuit-type parameter.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
<network-type>point-to-point</network-type>
</config>
</interface>
</interfaces>
</isis>
Restrictions
None
Configure Primary IP Address

This XML configuration snippet is used to configure IS-IS hello-padding parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS hello-padding parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>

<interface-ref>
<config>
</config>
</interface-ref>
<config>
<hello-padding>DISABLE</hello-padding>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS hello-padding parameter.
interface eth2
no isis hello padding

Here is a sample OcNOS NetConf Payload to configure IS-IS hello-padding parameter.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
<disable-padding/>
</config>

</interface>
</interfaces>
</isis>
Restrictions
• IS-IS hello-padding is enabled by default on OcNOS.
• Only OpenConfig’s DISABLE value is supported.
Configure Interface Passive Parameter

This XML configuration snippet is used to configure IS-IS passive parameter.
Note: On OcNOS, this attribute is configured at the instance mode, whereas on OpenConfig, it’s at interface.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS passive parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<config>
<passive>true</passive>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<afi-safi>
<af>
<afi-name
<safi-name

<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS passive parameter.
router isis ABC
passive-interface eth2

Here is a sample OcNOS NetConf Payload to configure IS-IS passive parameter.
<isis-instances>
<isis-instance>
<config>
</config>
<passive-interfaces>
<passive-interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
</passive-interface>
</passive-interfaces>
</isis-instance>
</isis-instances>
</isis>
Restrictions
None

Configure Interface IPv6 AF Parameter

This XML configuration snippet is used to configure IS-IS IPv6 support parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS IPv6 support parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABCv6</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
</interface>
</interfaces>
</isis>

</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS IPv6 support parameter.
interface eth3
ipv6 router isis ABCv6

Here is a sample OcNOS NetConf Payload to configure IS-IS IPv6 support parameter.
<interfaces>
<interface>
<name>eth3</name>
<config>
<name>eth3</name>
</config>
<config>
<ipv6-instance-tag>ABCv6</ipv6-instance-tag>
</config>
</interface>
</interfaces>
</isis>
Restrictions
None
Configure Interface BFD Parameter

This XML configuration snippet is used to configure IS-IS enable-bfd parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS enable-bfd parameter.
<network-instance>
<protocols>

<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<enable-bfd>
<config>
</config>
</enable-bfd>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS enable-bfd parameter.
interface eth2
isis bfd


Here is a sample OcNOS NetConf Payload to configure IS-IS enable-bfd parameter.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
</config>
<bfd>
<config>
<enable/>
</config>
</bfd>
</interface>
</interfaces>
</isis>
Restrictions
None
Configure Interface Priority Parameter

This XML configuration snippet is used to configure IS-IS priority parameter.
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS priority parameter.
<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>

<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<levels>
<level>
<config>
<priority>50</priority>
</config>
</level>
</levels>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to configure IS-IS priority parameter.
interface eth2
isis priority 50 level-1

Here is a sample OcNOS NetConf Payload to configure IS-IS priority parameter.

<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
</config>
<level-infos>
<level-info>
<config>
</config>
</level-info>
</level-infos>
</interface>
</interfaces>
</isis>
Restrictions
• The OcNOS level-1-2 value for level-info is not supported by OpenConfig.
• /isis/interfaces/interface/interface-parameters/level-infos/level-info
• The XPath related to interfaces level-number below can only have values "1" or "2".
1. /oc-netinst:network-instances/network-instance[name]/protocols/
protocol[identifier][name]/isis/interfaces/interface[interface-id]/levels/
level[level-number]/level-number
level[level-number]/config/level-number
Configure Interface Timers Parameter

This XML configuration snippet is used to configure the following IS-IS parameters:
• hello-interval
• hello-multiplier
Release

Here is a sample OpenConfig NetConf Payload to configure IS-IS parameters hello-interval and hello-multiplier.

<network-instance>
<protocols>
<protocol>
<identifier
<name>ABC</name>
<isis>
<interfaces>
<interface>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
</config>
<afi-safi>
<af>
<afi-name
<safi-name
<config>
<afi-name
<safi-name
</config>
</af>
</afi-safi>
<levels>
<level>
<config>
</config>
<timers>
<config>
<hello-interval>1</hello-interval>
</config>
</timers>
</level>
<level>
<config>
</config>
<timers>

<config>
<hello-multiplier>2</hello-multiplier>
</config>
</timers>
</level>
</levels>
</interface>
</interfaces>
</isis>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLi command is used to configure IS-IS parameters hello-interval and hello-multiplier.
interface eth2
isis hello-interval 1 level-1
isis hello-multiplier 2 level-2

Here is a sample OcNOS NetConf Payload to configure IS-IS parameters hello-interval and hello-multiplier.
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<config>
</config>
<level-infos>
<level-info>
<config>
</config>
</level-info>
<level-info>
<config>
<hello-multiplier>2</hello-multiplier>
</config>
</level-info>
</level-infos>
</interface>
</interfaces>

</isis>
Restrictions
• The OcNOS level-1-2 value for level-info is not supported by OpenConfig.
• /isis/interfaces/interface/interface-parameters/level-infos/level-info
• The XPath related to interfaces level-number below can only have values "1" or "2".
level[level-number]/level-number
level[level-number]/config/level-number

BGP OpenConfig Translation
Create BGP Instance

This XML configuration snippet is used to initiate a BGP process with the associated autonomous system number and
router ID.
Release
This configuration was introduced in OcNOS version 4.2.

Here is the sample OpenConfig NetConf Payload for configuring a BGP process within a network instance. It sets the
BGP autonomous system number (AS) and specifies the router ID.
<network-instance>
<protocols>
<protocol xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">
<identifier>oc-pol-types:BGP</identifier>
<name>100</name>
<config>
<name>100</name>
</config>
<bgp>
<global>
<config>
<as>100</as>
<router-id>1.2.3.4</router-id>
</config>
</global>
</bgp>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to configure a BGP process with the AS number and set the BGP router ID.
router bgp 100
bgp router-id 1.2.3.4


Here is a sample OcNOS NetConf Payload used to configure a network instance with the name and type. It also
configures a BGP instance with an AS number and sets the BGP router ID.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-network-
instance">
<network-instance>
<instance-name>default</instance-name>
<instance-type>vrf</instance-type>
<config>
</config>
<vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vrf">
<config>
</config>
</vrf>
</network-instance>
<bgp xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-bgp">
<bgp-instances>
<bgp-instance>
<bgp-as>100</bgp-as>
<config>
</config>
</bgp-instance>
</bgp-instances>
</bgp>
Validation with NetConf get

Here is a NetConf validation response that provides information about the enabled state and identifiers, as well as
details about the BGP global configuration, including the AS number and router ID.
<network-instances xmlns="http://openconfig.net/yang/network-
instance">
<network-instance>
<config>
<type
xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-
types">oc-ni-types:DEFAULT_INSTANCE</type>
</config>
<state>
<type
types">oc-ni-types:L3VRF</type>
</state>
<protocols>
<protocol>
<identifier

pol-types:DIRECTLY_CONNECTED</identifier>
<name>DIRECTLY_CONNECTED</name>
<config>
<identifier
xmlns:oc-pol-types="http://openconfig.net/yang/policy-
types">oc-pol-types:DIRECTLY_CONNECTED</identifier>
</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
pol-types:BGP</identifier>
<name>100</name>
<config>
<identifier
types">oc-pol-types:BGP</identifier>
<name>100</name>
</config>
<bgp>
<global>
<config>
<as>100</as>
</config>
<state>
<as>100</as>
</state>
<global>
<state>
</state>
</global>
</global>
</bgp>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
</network-instance>

Restrictions
Address families supported:
The OpenConfig datamodel does not support all the address-family types that OcNOS datamodel contains. The
address-family values are defined on identity AFI_SAFI_TYPE on OpenConfig file public/release/models/bgp/
openconfig-bgp-types.yang at master · openconfig/public.
The table below shows all the address-family types that are supported. The address-family types that are not listed are
translated as “UNDEFINED” on NETCONF GET/SGET operations.
OcNOS Address-family type OpenConfig Address-family type

ipv4_unicast IPV4_UNICAST
ipv4_multicast IPV4_MULTICAST
ipv4_labeled-unicast IPV4_LABELED_UNICAST
ipv4_vpn-unicast L3VPN_IPV4_UNICAST
ipv6_unicast IPV6_UNICAST
ipv6_labeled-unicast IPV6_LABELED_UNICAST
ipv6_vpn-unicast L3VPN_IPV6_UNICAST
l2vpn_evpn L2VPN_EVPN
link-state_link-state LINKSTATE
BGP naming rule:

For BGP instances, the leaf /network-instances/network-instance/protocols/protocol/name must
have the same number of the /network-instances/network-instance/protocols/protocol/bgp/
global/config/as.
Create BGP Global with default VRF

This XML configuration snippet is used to set up BGP Global configuration with default VRF data from the OpenConfig
perspective.
Ensure that the AFI-SAFI container is present in the applied configuration to facilitate the configuration of address
families.
Release

Here is the sample OpenConfig NetConf Payload to define BGP settings for the default network instance, including
global BGP parameters, neighbor configurations, and address family tables.
<network-instance>
<config>
<type

</config>
<protocols>
<protocol>
<identifier
types:DIRECTLY_CONNECTED</identifier>
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
types:BGP</identifier>
<name>100</name>
<bgp>
<global>
<afi-safis>
<afi-safi>
<afi-safi-name
xmlns:oc-bgp-types="http://openconfig.net/yang/bgp-
types">oc-bgp-types:IPV4_UNICAST</afi-safi-name>
<config>
<afi-safi-name
</config>
<add-paths>
<config>
<receive>true</receive>
<send>true</send>
<send-max>2</send-max>
</config>
</add-paths>
<use-multiple-paths>
<ibgp>
<config>
<maximum-paths>7</maximum-paths>
</config>
</ibgp>
</use-multiple-paths>
</afi-safi>
</afi-safis>
<confederation>
<config>
<member-as>48</member-as>
<identifier>600</identifier>
</config>
</confederation>
<config>

<as>100</as>
</config>
<route-selection-options>
<config>
<enable-aigp>false</enable-aigp>
<ignore-as-path-length>true</ignore-as-path-length>
<external-compare-router-id>true</external-compare-router-id>
</config>
</route-selection-options>
<graceful-restart>
<config>
<restart-time>100</restart-time>
<stale-routes-time>300.00</stale-routes-time>
<helper-only>false</helper-only>
</config>
</graceful-restart>
</global>
<neighbors>
<neighbor>
<neighbor-address>10.1.1.2</neighbor-address>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
<peer-as>100</peer-as>
</config>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>100</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol
types:DIRECTLY_CONNECTED</protocol>
<address-family

xmlns:oc-types="http://openconfig.net/yang/openconfig-types">oc-
types:IPV4</address-family>
<config>
<protocol
pol-types:DIRECTLY_CONNECTED</protocol>
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
types:BGP</protocol>
<address-family
<config>
<protocol
pol-types:BGP</protocol>
<address-family
</config>
</table>
</tables>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to configure BGP settings for a specified AS number on a networking device. They
define critical attributes of the BGP process, including the router ID, confederation settings, best path selection criteria,
graceful restart behavior, and neighbor configuration. Additionally, the commands enable support for IPv4 unicast
address families and specify advanced options like additional path handling and maximum path selection for internal
BGP peers. The neighbor statement establishes a BGP neighbor relationship with an adjacent router using the IP
address and assigns it to a specified AS number.
router bgp 100

bgp confederation identifier 600

bgp confederation peers 48
bgp bestpath as-path ignore
bgp bestpath aigp ignore
bgp bestpath compare-routerid
bgp graceful-restart restart-time 100
bgp graceful-restart stalepath-time 300
bgp graceful-restart graceful-reset
neighbor 10.1.1.2 remote-as 100
!
address-family ipv4 unicast
bgp additional-paths send-receive
bgp additional-paths select best 2
max-paths ibgp 7
neighbor 10.1.1.2 activate
exit-address-family
!

Here is a sample OcNOS NetConf Payload for configuring BGP settings on a network device. It defines a BGP
instance with AS number and sets its router ID, graceful restart parameters, route selection options, and address family
settings. Specifically, it configures BGP to operate with IPv4 unicast address families, allowing for the exchange of IPv4
unicast routing information. Additionally, the payload specifies additional path handling, maximum path selection for
internal BGP peers, and establishes a BGP neighbor relationship with an adjacent router using the IP address.
<bgp-instances>
<bgp-instance>
<config>
<ignore-aigp-for-bestpath />
</config>
<graceful-restart>
<config>
<stale-path-max-retention-time>300</stale-path-max-
retention-time>
<graceful-reset />
</config>
</graceful-restart>
<route-selection>
<config>
<ignore-as-path-length />
<external-compare-router-id />
</config>
</route-selection>
<address-families>
<address-family>
<afi>ipv4</afi>
<safi>unicast</safi>
<config>
<afi>ipv4</afi>

<additional-paths-best-select-count>2</additional-
paths-best-select-count>
<additional-paths-mode>receive send</additional-paths-
mode>
</config>
<maximum-paths>
<config>
<ibgp-max-path>7</ibgp-max-path>
</config>
</maximum-paths>
</address-family>
</address-families>
<peers>
<peer>
<peer-address>10.1.1.2</peer-address>
<address-families>
<address-family>
<afi>ipv4</afi>
<config>
<afi>ipv4</afi>
<activate />
</config>
</address-family>
</address-families>
<config>
<confederation-identifier>600</confederation-
identifier>
<peer-as-number>48</peer-as-number>
</config>
</peer>
</peers>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response indicates the successful validation of a network configuration specified in a
NetConf payload. In this specific response, it verifies the correctness of the configuration for a specified network
instance with associated protocols and interfaces. The validation ensures that the configuration adheres to the defined
network instance types, policy types, and address families. All relevant elements, such as the BGP instance, its
parameters, and the associated interfaces, are validated against the specified OpenConfig model.
<network-instance>
<config>
<type
</config>
<state>

<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
<add-paths>
<config>
<send>true</send>
</config>
<state>

<send>true</send>
</state>
</add-paths>
<ibgp>
<config>
</config>
<state>
</state>
</ibgp>
</afi-safi>
</afi-safis>
<confederation>
<config>
</config>
<state>
</state>
</confederation>
<config>
<as>100</as>
</config>
<config>
</config>
<state>
</state>
<state>
<as>100</as>
<total-prefixes>0</total-prefixes>
</state>
<graceful-restart>
<config>
</config>
<state>

</state>
</graceful-restart>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>
<state>
</state>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>100</name>
</config>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol

<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family

</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
<interfaces>
<interface>
<id>eth0</id>
<config>
<id>eth0</id>
</config>
</interface>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
</interface>
<interface>
<id>eth2</id>
<config>
<id>eth2</id>
</config>
</interface>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
</interface>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
</interface>
<interface>
<id>eth5</id>
<config>
<id>eth5</id>
</config>
</interface>
<interface>
<id>eth6</id>
<config>

<id>eth6</id>
</config>
</interface>
<interface>
<id>eth7</id>
<config>
<id>eth7</id>
</config>
</interface>
<interface>
<id>eth8</id>
<config>
<id>eth8</id>
</config>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
<interface>lo</interface>
</config>
</interface>
</interfaces>
</network-instance>
Restrictions
• On the first time /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
global paths are configured, those configuration need that respective AFI-SAFI configuration must be present
to indicate AFI type:
/oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/afi-
safis
This information is necessary for the OcNOS model to generate the following paths:
/ipi-bgp:bgp/bgp-instances/bgp-instance/address-families
/ipi-bgp:bgp/bgp-instances/bgp-instance/peer-groups/peer-group/address-families
/ipi-bgp:bgp/bgp-instances/bgp-instance/address-family-vrfs
• After the /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global
paths are configured on equipment, on the further configurations on those paths the user does not need to indicate
the AFI-SAFI, the translation will look for this information on the equipment database.
• For multiple paths configuration, the Open Config path /oc-netinst:network-instances/network-
instance/protocols/protocol/bgp/global/use-multiple-paths is not support, all the multiple paths
configurations are done on Open Config path /oc-netinst:network-instances/network-instance/
protocols/protocol/bgp/global/afi-safis/afi-safi/use-multiple-paths.This is because the
OcNOS datamodel only handle multiple paths is one place.
• The containers graceful-restart and route-selection-options are configurable only by network-
instance instance named “default”.
• The Open Config attributes:

/oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/
graceful-restart/state/helper-only
/oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/route-
selection-options/config/enable-aigp
Have their logic inverted, so a "false" value on open-config means a "true" value on OcNOS datamodel.
Create BGP Global with User-defined VRFs

This XML configuration snippet uses the payloads provided in this section to configure BGP Global with user-defined
VRF data from the Open Config perspective.
The AFI-SAFI container must be available on the configuration applied to help configure address-families.
Release

Here is the sample OpenConfig NetConf Payload used to configure network instances with BGP Global settings. This
payload includes configuration for both the default network instance and a custom network instance named red.
In the default instance, BGP Global settings such as the AS number, router ID, route selection options, and graceful
restart parameters are configured.
In the red network instance, in addition to the common BGP Global settings, specific AFI-SAFI settings are configured,
including the number of maximum paths for both eBGP and iBGP. This example demonstrates how the payload can be
adapted to configure different network instances with unique BGP configurations.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier

<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<config>
</config>
<graceful-restart>
<config>
</config>
</graceful-restart>
</global>
</bgp>
<config>
<identifier
<name>100</name>
</config>
</protocol>
</protocols>
</network-instance>
<network-instance>
<name>red</name>
<config>
<name>red</name>
<type
<route-distinguisher>100:200</route-distinguisher>
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>

<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<ebgp>
<config>
</config>
</ebgp>
<ibgp>
<config>
</config>
</ibgp>
</afi-safi>
</afi-safis>
<confederation>
<config>
</config>
</confederation>
</global>
</bgp>
<config>
<identifier
<name>100</name>
</config>
</protocol>
</protocols>
</network-instance>

OcNOS CLI Command

The below CLI commands are used to configure an IP VRF with a route distinguisher. In addition, the router BGP is
configured with various BGP settings, including router ID, bestpath options, graceful restart parameters, and
confederation settings. Inside the address-family IPv4 VRF context, the maximum paths for eBGP and iBGP are set.
The BGP confederation is also configured with an identifier and peers.
ip vrf red
rd 100:200
!
router bgp 100
bgp bestpath as-path ignore
bgp bestpath aigp ignore
bgp bestpath compare-routerid
bgp graceful-restart restart-time 100
bgp graceful-restart stalepath-time 300
bgp graceful-restart graceful-reset
!
address-family ipv4 vrf red
max-paths ebgp 10
max-paths ibgp 15
bgp confederation identifier 600
bgp confederation peers 48
exit-address-family
!

Here is a sample OcNOS NetConf Payload to configure a BGP instance with AS number, a router ID, and settings to
ignore AIGP for bestpath selection. It also includes graceful restart parameters with a restart time and a stale path max
retention time. Additionally, the payload configures route selection options to ignore AS path length and perform
external comparisons based on router IDs. Inside the address-family VRF context for IPv4 unicast, it sets the
confederation identifier and the peer AS number. Maximum path settings are configured for both eBGP and iBGP
paths.
<bgp-instances>
<bgp-instance>
<config>
<ignore-aigp-for-bestpath />
</config>
<graceful-restart>
<config>
<stale-path-max-retention-time>300</stale-path-max-
retention-time>
<graceful-reset />
</config>
</graceful-restart>
<route-selection>
<config>
<ignore-as-path-length />

<external-compare-router-id />
</config>
</route-selection>
<address-family-vrfs>
<address-family-vrf>
<afi>ipv4</afi>
<vrf-name>red</vrf-name>
<confederation>
<peer-as-number>48</peer-as-number>
</confederation>
<config>
<afi>ipv4</afi>
<vrf-name>red</vrf-name>
</config>
<maximum-paths>
<config>
<ebgp-max-path>10</ebgp-max-path>
<ibgp-max-path>15</ibgp-max-path>
</config>
</maximum-paths>
</address-family-vrf>
</address-family-vrfs>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response for configuring settings for the default network instance and a network instance.
It also includes configurations for protocols, under network instances. Additionally, there are table configurations for
IPv4 and IPv6 address families.
<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>

<identifier
</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<config>
</config>
<state>
</state>
<state>
<as>100</as>
</state>
<graceful-restart>
<config>
</config>
<state>
</state>
</graceful-restart>
</global>
</bgp>
<config>

<identifier
<name>100</name>
</config>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol

<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
</tables>
</network-instance>
<network-instance>
<name>red</name>
<config>
<name>red</name>
<type
</config>
<state>
<name>red</name>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier

</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
<ebgp>
<config>
</config>
<state>
</state>
</ebgp>
<ibgp>
<config>
</config>
<state>
</state>
</ibgp>
</afi-safi>
</afi-safis>
<confederation>
<config>
</config>
<state>

</state>
</confederation>
<state>
<as>100</as>
</state>
</global>
</bgp>
<config>
<identifier
<name>100</name>
</config>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol

<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
</network-instance>
Restrictions
• The /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/
afi-safis/afi-safi/add-paths are available only on network-instance instance named “default”.
• The container /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
global/graceful-restart are available only on network-instance instance named “default”.
• The container /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
global/route-selection-options are available only on network-instance instance named “default”.
global paths are configured, those configuration needs the respective AFI-SAFI configuration that be present to
indicate AFI type: /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
global/afi-safis
• The above information is necessary for the OcNOS model to generate the following paths:

• After the /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global
paths are configured on equipment, on the further configurations on those paths the user does not need to indicate
the AFI-SAFI, the translation will look for this information on the equipment database.
Create BGP Neighbors

This XML configuration snippet is used to configure neighbors in non-default VRF of BGP.
Release

Here is the sample OpenConfig NetConf Payload to configure network instances, specifically two instances: default
and VRF1. It also configures BGP settings within these network instances, including neighbors and address families.
Additionally, it configures tables for IPv4 and IPv6 address families within the network instances.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
<name>123</name>
<bgp>
<global>
<afi-safis>

<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
<as>123</as>
</config>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<config>
<send-default-route>true</send-default-route>
</config>
<prefix-limit>
<config>
<max-prefixes>5</max-prefixes>
<warning-threshold-pct>60</warning-threshold-pct>
</config>
</prefix-limit>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<graceful-restart>
<config>
</config>
</graceful-restart>
</afi-safi>
</afi-safis>
<config>
<remove-private-as
types">oc-bgp-types:PRIVATE_AS_REMOVE_ALL</remove-private-as>
<local-as>300</local-as>
</config>
<enable-bfd>

<config>
</config>
</enable-bfd>
<transport>
<config>
<local-address>eth1</local-address>
</config>
</transport>
<timers>
<config>
<keepalive-interval>30.00</keepalive-interval>
<hold-time>120.00</hold-time>
</config>
</timers>
<ebgp-multihop>
<config>
<multihop-ttl>5</multihop-ttl>
</config>
</ebgp-multihop>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
<prevent-teardown>true</prevent-teardown>
</config>
</prefix-limit>
</ipv4-unicast>
<apply-policy>
<config>
<import-policy>rmap1</import-policy>
<export-policy>rmap1</export-policy>
</config>
</apply-policy>
<config>
<afi-safi-name
</config>
<add-paths>
<config>
<send>true</send>
</config>
</add-paths>
</afi-safi>

</afi-safis>
<config>
</config>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>123</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>

<protocol
<address-family
</config>
</table>
</tables>
</network-instance>
<network-instance>
<name>VRF1</name>
<config>
<name>VRF1</name>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-
instance-types">oc-ni-types:L3VRF</type>
<route-distinguisher>1.2.3.4:56</route-distinguisher>
</config>
<protocols>
<protocol>
<identifier xmlns:oc-pol-types="http://openconfig.net/yang/
policy-types">oc-pol-types:DIRECTLY_CONNECTED</identifier>
<config>
<identifier xmlns:oc-pol-types="http://openconfig.net/
yang/policy-types">oc-pol-types:DIRECTLY_CONNECTED</identifier>
</config>
</protocol>
<protocol>
policy-types">oc-pol-types:BGP</identifier>
<name>123</name>
<bgp>
<global>
<config>
<as>123</as>
</config>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name xmlns:oc-bgp-types="http://
openconfig.net/yang/bgp-types">oc-bgp-types:IPV4_UNICAST</afi-safi-name>
<config>
<afi-safi-name xmlns:oc-bgp-
types="http://openconfig.net/yang/bgp-types">oc-bgp-types:IPV4_UNICAST</afi-
safi-name>
</config>
<apply-policy>
<config>
<import-policy>rmap2</import-
policy>
<export-policy>rmap2</export-
policy>

</config>
</apply-policy>
<ipv4-unicast>
<config>
<send-default-route>true</send-default-
route>
</config>
</ipv4-unicast>
</afi-safi>
</afi-safis>
<config>
<remove-private-as xmlns:oc-bgp-types="http://
openconfig.net/yang/bgp-types">oc-bgp-types:PRIVATE_AS_REMOVE_ALL</remove-
private-as>
<description>ebgp_VRF1</description>
</config>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
xmlns:oc-bgp-types="http://openconfig.net/
yang/bgp-types">oc-bgp-types:IPV4_UNICAST</afi-safi-name>
<ipv4-unicast>
<prefix-limit>
<config>
<warning-threshold-pct>80</warning-
threshold-pct>
</config>
</prefix-limit>
</ipv4-unicast>
<config>
<afi-safi-name
xmlns:oc-bgp-types="http://openconfig.net/
yang/bgp-types">oc-bgp-types:IPV4_UNICAST</afi-safi-name>
</config>
<graceful-restart>
<config>
</config>
</graceful-restart>
</afi-safi>
</afi-safis>
<config>
</config>
</neighbor>
</neighbors>
</bgp>

<config>
yang/policy-types">oc-pol-types:BGP</identifier>
<name>123</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol xmlns:oc-pol-types="http://openconfig.net/yang/
policy-types">oc-pol-types:DIRECTLY_CONNECTED</protocol>
<address-family xmlns:oc-types="http://openconfig.net/yang/
openconfig-types">oc-types:IPV4</address-family>
<config>
<address-family xmlns:oc-types="http://openconfig.net/
yang/openconfig-types">oc-types:IPV4</address-family>
</config>
</table>
<table>
<config>
</config>
</table>
<table>
policy-types">oc-pol-types:BGP</protocol>
<config>
</config>
</table>
</tables>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to configure a BGP setup with two address families: global ipv4 unicast and
ipv4 vrf VRF1. It includes various neighbor configurations, prefix limits, route maps, and other BGP parameters to
control BGP behavior in both the global and VRF contexts.
ip vrf VRF1
rd 100:200
exit
router bgp 123


neighbor 10.1.1.1 local-as 300
neighbor 10.1.1.1 fall-over bfd
neighbor 10.1.1.1 ebgp-multihop 5
neighbor 10.1.1.1 update-source eth1
neighbor 10.1.1.1 timers 30 120
!
neighbor 10.1.1.1 remove-private-AS
neighbor 10.1.1.1 maximum-prefix 5 60
neighbor 10.1.1.1 capability graceful-restart
neighbor 10.1.1.1 default-originate
neighbor 11.1.1.1 additional-paths send-receive
neighbor 11.1.1.1 maximum-prefix 7 70 warning-only
neighbor 11.1.1.1 route-map rmap1 in
neighbor 11.1.1.1 route-map rmap1 out
exit-address-family
!
address-family ipv4 vrf VRF1
neighbor 20.1.1.2 local-as 300
neighbor 20.1.1.2 remove-private-AS
neighbor 20.1.1.2 route-map rmap2 in
neighbor 20.1.1.2 route-map rmap2 out
neighbor 20.1.1.2 default-originate
neighbor 21.1.1.2 maximum-prefix 5 80 warning-only
neighbor 21.1.1.2 capability graceful-restart
neighbor 20.1.1.2 description ebgp_VRF1
exit-address-family
!

Here is a sample OcNOS NetConf Payload to configure BGP settings with VRF support and address-families in an
OcNOS network device using the IPI YANG models. It defines BGP peering relationships, specify BGP attributes, and
apply route maps within the context of both the global BGP instance and the VRF VRF1.
instance">
<network-instance>
<instance-name>VRF1</instance-name>
<config>
</config>
<config>
<vrf-name>VRF1</vrf-name>
</config>
<bgp-vrf xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-bgp-vrf">

<config>
<rd-string>100:200</rd-string>
</config>
</bgp-vrf>
</vrf>
</network-instance>
<bgp-instances>
<bgp-instance>
<config>
</config>
<address-families>
<address-family>
<afi>ipv4</afi>
<config>
<afi>ipv4</afi>
</config>
</address-family>
</address-families>
<peers>
<peer>
<address-families>
<address-family>
<afi>ipv4</afi>
<maximum-prefixes>
<prefix-count>5</prefix-count>
<config>
<threshold-percentage>60</threshold-
percentage>
</config>
</maximum-prefixes>
<config>
<afi>ipv4</afi>
<activate />
<peer-remove-private-as />
<capability-graceful-restart />
<default-peer-route-map-name />
</config>
</address-family>
</address-families>
<config>
<enable-peer-bfd />
<peer-local-as>300</peer-local-as>
<source-identifier>eth1</source-identifier>
</config>
<timers>

<config>
<keep-alive>30</keep-alive>
<hold-time>120</hold-time>
</config>
</timers>
<ebgp-multihop>
<config>
<maximum-hop-count>5</maximum-hop-count>
<enabled />
</config>
</ebgp-multihop>
</peer>
<peer>
<address-families>
<address-family>
<afi>ipv4</afi>
<maximum-prefixes>
<maximum-prefix>
<config>
percentage>
<warning-only />
</config>
</maximum-prefix>
</maximum-prefixes>
<route-map-filters>
<route-map-filter>
<route-map-direction>in</route-map-
direction>
<config>
direction>
<route-map-name>rmap1</route-map-name>
</config>
</route-map-filter>
<route-map-filter>
<route-map-direction>out</route-map-
direction>
<config>
direction>
</config>
</route-map-filter>
</route-map-filters>
<config>
<afi>ipv4</afi>
<additional-paths-mode>receive send</
additional-paths-mode>
<activate />
</config>
</address-family>
</address-families>

<config>
</config>
</peer>
</peers>
<afi>ipv4</afi>
<vrf-peers>
<vrf-peer>
<route-map-filters>
<route-map-filter>
direction>
<config>
direction>
</config>
</route-map-filter>
<route-map-filter>
direction>
<config>
direction>
</config>
</route-map-filter>
<config>
<activate />
<peer-remove-private-as />
</config>
</vrf-peer>
<vrf-peer>
<maximum-prefixes>
<maximum-prefix>
<config>
percentage>
<warning-only />
</config>
</maximum-prefix>
</maximum-prefixes>
<config>

<activate />
<capability-graceful-restart />
</config>
</vrf-peer>
</vrf-peers>
<config>
<afi>ipv4</afi>
</config>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response to configure payload for BGP settings in a network instance, including global
BGP settings and BGP neighbors.
instance">
<network-instance>
<protocols>
<protocol>
<identifier
<name>123</name>
<bgp>
<global>
<config>
<as>123</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>

<afi-safi-name
<ipv4-unicast>
<config>
</config>
<prefix-limit>
<config>
</config>
</prefix-limit>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<graceful-restart>
<config>
</config>
</graceful-restart>
</afi-safi>
</afi-safis>
<config>
<remove-private-as
</config>
<enable-bfd>
<config>
</config>
</enable-bfd>
<ebgp-multihop>
<config>
</config>
</ebgp-multihop>
<transport>
<config>
<local-address>eth1</local-address>
</config>
</transport>
<timers>
<config>
</config>

</timers>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>
</ipv4-unicast>
<apply-policy>
<config>
</config>
</apply-policy>
<config>
<afi-safi-name
</config>
<add-paths>
<config>
<send>true</send>
</config>
</add-paths>
</afi-safi>
</afi-safis>
<config>
</config>
</neighbor>
</neighbors>
</bgp>
</protocol>
</protocols>
</network-instance>
<network-instance>
<name>management</name>
</network-instance>
<network-instance>
<name>VRF1</name>
<protocols>
<protocol>
<identifier

<name>123</name>
<bgp>
<global>
<config>
<as>123</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<apply-policy>
<config>
</config>
</apply-policy>
<ipv4-unicast>
<config>
</config>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<apply-policy>
<config>
</config>
</apply-policy>
<config>

<remove-private-as
</config>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<graceful-restart>
<config>
</config>
</graceful-restart>
</afi-safi>
</afi-safis>
<config>
</config>
</neighbor>
</neighbors>
</bgp>
</protocol>
</protocols>
</network-instance>
Restrictions
• The leaf /network-instances/network-instance/protocols/protocol/bgp/neighbors/
neighbor/config/remove-private-as must have the OpenConfig value PRIVATE_AS_REMOVE_ALL
• The below leaf was not supported by the current implementation, but this feature is supported at the AFI-SAFI level
of each neighbor.

/network-instances/network-instance/protocols/protocol/bgp/neighbors/neighbor/
apply-policy
• The below leaf was not supported by the current implementation at the neighbor level, but this feature is supported
at the AFI-SAFI level of each neighbor, as well as at the global level (/network-instances/network-
instance/protocols/protocol/bgp/global/graceful-restart).
graceful-restart
• The below leaf was not supported by the current implementation at the neighbor level, but this feature is supported
at the global level (/network-instances/network-instance/protocols/protocol/bgp/global/afi-
safis/afi-safi/use-multiple-paths).
use-multiple-paths
• The below leaf is limited to 32 characters and must have the format <interface>.<subinterface>, e.g.,
eth2.10.
/network-instances/network-instance/interfaces/interface/config/id
neighbor paths are configured, those configuration needs the respective AFI-SAFI configuration that be present
to indicate AFI type:
/oc-netinst:network-instances/network-instance/protocols/protocol/bgp/neighbors/
neighbor/afi-safis
/ipi-bgp:bgp/bgp-instances/bgp-instance/peer-groups/peer-group/address-
families
/ip.i-bgp:bgp/bgp-instances/bgp-instance/address-family-vrfs
• After the /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
neighbors paths are configured on equipment, on the further configurations on those paths the user does not
need to indicate the AFI-SAFI, the translation will look for this information on the equipment database.
Configure eBGP Neighbor with TTL

This XML configuration snippet defines the eBGP neighbor with a Time-to-Live (TTL) value.
Release

Here is the sample OpenConfig NetConf Payload that defines a network instance named VRF1 with various
configurations, including the route distinguisher, protocols, and tables. Specifically, it sets up BGP protocol with a global
AS number and a neighbor with an AS number. The eBGP-multihop feature is enabled for this neighbor with a TTL
value.
Additionally, the payload defines three tables, one for directly connected IPv4 routes, one for directly connected IPv6
routes, and one for BGP IPv4 routes.
<network-instance>
<name>VRF1</name>
<config>

<name>VRF1</name>
</config>
<protocols>
<protocol>
<config>
</config>
</protocol>
<protocol>
policy-types">oc-pol-types:BGP</identifier>
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<config>
safi-name>
</config>
</afi-safi>
</afi-safis>
<config>
</config>
<ebgp-multihop>
<config>
</config>
</ebgp-multihop>
</neighbor>
</neighbors>
</bgp>
<config>
yang/policy-types">oc-pol-types:BGP</identifier>

<name>100</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<config>
</config>
</table>
<table>
<config>
</config>
</table>
<table>
<config>
</config>
</table>
</tables>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to configure a BGP neighbor relationship in the VRF1, allowing the BGP router with
AS number 100 to communicate with a neighbor at IP address 1.1.1.2, which has AS number 200, and the
configuration ensures that the session can be established even if the TTL is set to a higher value, in this case, 20.
router bgp 100
!
address-family ipv4 vrf VRF1
neighbor 1.1.1.2 ebgp-multihop 20

exit-address-family
!

Here is a sample OcNOS NetConf Payload that defines a VRF instance named VRF1 with the associated BGP
settings. The VRF is set to use IPv4 unicast address-family. Within this VRF, a BGP peering session is established with
a remote neighbor having the IP address 1.1.1.2 and AS number 200. To ensure the BGP session can be established,
the ebgp-multihop feature is enabled with a maximum hop count of 20, allowing the BGP router to communicate
with a neighbor that might be multiple hops away. The BGP configuration also specifies a route distinguisher (RD) of
1.2.3.4:56 for the VRF. This configuration is essential for routing and forwarding traffic within the VRF while
maintaining isolation from other VRFs or the global routing table.
instance">
<network-instance>
<config>
</config>
<config>
</config>
<config>
<rd-string>1.2.3.4:56</rd-string>
</config>
</bgp-vrf>
</vrf>
</network-instance>
<bgp-instances>
<bgp-instance>
<config>
</config>
<afi>ipv4</afi>
<vrf-peers>
<vrf-peer>
<config>
</config>
<ebgp-multihop>
<config>

</enabled>
</config>
</ebgp-multihop>
</vrf-peer>
</vrf-peers>
<config>
<afi>ipv4</afi>
</config>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response for the network instance VRF1 and its associated BGP settings indicates that the
provided configuration is compliant with the expected structure and format defined in the YANG data model for network
instances and BGP protocols. This validation response affirms that there are no errors or inconsistencies in the
configuration, affirming its readiness for application to the network device. It verifies that the specified parameters, such
as route distinguisher, autonomous system numbers, and address families, are correctly defined and align with the
defined standards, ensuring smooth and accurate operation within the network infrastructure.
instance">
<network-instance>
<name>VRF1</name>
<config>
<name>VRF1</name>
<type
</config>
<state>
<name>VRF1</name>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>

<identifier
</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<state>
<as>100</as>
</state>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
</config>
<ebgp-multihop>
<config>
</config>
<state>
</state>
</ebgp-multihop>
<state>
</state>

</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>100</name>
</config>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
types">oc-pol-types:BGP</protocol>
<address-family
xmlns:oc-types="http://openconfig.net/yang/openconfig-
types">oc-types:IPV4</address-family>
</config>
</table>
</tables>
</network-instance>
Restrictions
• The leaf /network-instances/network-instance/protocols/protocol/bgp/neighbors/
neighbor/config/peer-type is not supported.
neighbor paths are configured, those configuration needs the respective AFI-SAFI configuration that be present
to indicate AFI type /oc-netinst:network-instances/network-instance/protocols/protocol/
bgp/neighbors/neighbor/afi-safis

• After the /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/

neighbors paths are configured on equipment, on the further config urations on those paths the user does not
Create BGP Peer-groups with Default VRF

This XML configuration snippet is used to specify that BGP peer-groups should be created within the default VRF. Peer
groups are configurations that can be used elsewhere without the need to repeat them.
Release

Here is the sample OpenConfig NetConf Payload to configure BGP settings within the default network instance. It
defines various BGP parameters and peer groups for the specified AFI-SAFI combinations, including IPv4 unicast,
IPv4 labeled unicast, IPv6 labeled unicast, and L3VPN IPv6 unicast. This configuration includes authentication
passwords, timers, route reflector settings, and more for different peer groups such as ABC, peer1, and peer2.
<network-instance>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<config>
<enable-aigp>true</enable-aigp>
</config>
<state>
</state>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>

<afi-safi>
<afi-safi-name
types">oc-bgp-types:IPV4_LABELED_UNICAST</afi-safi-name>
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
types">oc-bgp-types:L3VPN_IPV6_UNICAST</afi-safi-name>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<peer-groups>
<peer-group>
<peer-group-name>ABC</peer-group-name>
<config>
<auth-password>0x9603e78694ace534ea912b9ab53f8a55</auth-
password>
<description>Non VRF peer-group configs</description>
</config>
<enable-bfd>
<config>
</config>
</enable-bfd>
<timers>
<config>
<connect-retry>300.00</connect-retry>
<minimum-advertisement-interval>20.00</minimum-
advertisement-interval>
</config>

</timers>
<transport>
<config>
<local-address>10.1.1.1</local-address>
<passive-mode>true</passive-mode>
</config>
</transport>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>
<config>
</config>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<apply-policy>
<config>
<import-policy>in-map</import-policy>
<export-policy>out-map</export-policy>
</config>
</apply-policy>
</afi-safi>
</afi-safis>
<route-reflector>
<config>
<route-reflector-client>true</route-reflector-client>
</config>
</route-reflector>
</peer-group>
<peer-group>
<peer-group-name>peer1</peer-group-name>
<config>
<auth-password>0x9a20ef22549ad84b</auth-password>
</config>
<ebgp-multihop>
<config>
</config>
</ebgp-multihop>
<afi-safis>

<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</peer-group>
<peer-group>
<config>
<auth-password>0x9603e78694ace534e74f24019f5bfeb5</auth-
password>
</config>
<enable-bfd>
<config>
</config>
</enable-bfd>
<ebgp-multihop>
<config>
</config>
</ebgp-multihop>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv6-labeled-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>
</ipv6-labeled-unicast>
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
<l3vpn-ipv6-unicast>
<prefix-limit>

<config>
</config>
</prefix-limit>
</l3vpn-ipv6-unicast>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI commands configure various BGP parameters and policies for different neighbors and address families
within AS number 100.
!
router bgp 100
neighbor ABC peer-group
neighbor ABC remote-as 100
neighbor ABC fall-over bfd multihop
neighbor peer1 peer-group
neighbor peer1 remote-as 200
neighbor peer2 peer-group
neighbor peer2 remote-as 300
neighbor peer2 fall-over bfd
neighbor ABC description Non VRF peer-group configs
neighbor ABC passive
neighbor ABC update-source 10.1.1.1
neighbor ABC authentication-key 0x9603e78694ace534ea912b9ab53f8a55
neighbor ABC advertisement-interval 20
neighbor ABC timers 300 8200
neighbor ABC timers connect 300
neighbor peer1 ebgp-multihop
neighbor peer1 authentication-key 0x9a20ef22549ad84b
neighbor peer2 ebgp-multihop 10
neighbor peer2 authentication-key 0x9603e78694ace534e74f24019f5bfeb5
!
neighbor ABC activate
neighbor ABC route-reflector-client
neighbor ABC default-originate
neighbor ABC maximum-prefix 4294967295 100 warning-only
neighbor ABC route-map in-map in
neighbor ABC route-map out-map out
exit-address-family
!

address-family ipv4 labeled-unicast

neighbor peer1 activate
exit-address-family
!
address-family vpnv6 unicast
neighbor peer2 allow-ebgp-vpn
neighbor peer2 maximum-prefix 12345
exit-address-family
!
address-family ipv6 labeled-unicast
neighbor peer2 maximum-prefix 1 warning-only
exit-address-family
!

Here is a sample OcNOS NetConf Payload to set up BGP peering and routing policies within the given AS number
(100) and defines parameters for various address families and peer groups.
<bgp-instances>
<bgp-instance>
<config>
</config>
<state>
<version>4</version>
<table-version>1</table-version>
<router-run-time-ip-address>0.0.0.0</router-run-time-ip-
address>
<scan-remain-time>49</scan-remain-time>
</state>
<rib>
<address-family>
<safi>link-state</safi>
<afi>link-state</afi>
<state>
</state>
</address-family>
</rib>
<address-families>
<address-family>
<afi>ipv4</afi>
<config>
<afi>ipv4</afi>
</config>
<state>
<afi>ipv4</afi>

</state>
</address-family>
<address-family>
<afi>ipv4</afi>
<safi>labeled-unicast</safi>
<config>
<afi>ipv4</afi>
</config>
<state>
<afi>ipv4</afi>
</state>
</address-family>
<address-family>
<afi>ipv6</afi>
<config>
<afi>ipv6</afi>
</config>
<state>
<afi>ipv6</afi>
</state>
</address-family>
<address-family>
<afi>ipv6</afi>
<safi>vpn-unicast</safi>
<config>
<afi>ipv6</afi>
</config>
<state>
<afi>ipv6</afi>
</state>
</address-family>
</address-families>
<peer-groups>
<peer-group>
<peer-group-tag>ABC</peer-group-tag>
<bgp-passwords>
<bgp-password>
<password>0x9603e78694ace534ea912b9ab53f8a55</
password>
<config>
password>
<auth-key-encrypt>1</auth-key-encrypt>
</config>
<state>
password>
</state>

</bgp-password>
</bgp-passwords>
<config>
<peer-group-range>static</peer-group-range>
<enable-peer-bfd />
<enable-peer-bfd-multihop />
<peer-description>Non VRF peer-group configs</peer-
description>
<peer-connect-interval>300</peer-connect-interval>
<min-route-advertisement-interval>20</min-route-
<source-identifier>10.1.1.1</source-identifier>
<neighbor-passive />
</config>
<state>
<enable-peer-bfd />
<peer-description>Non VRF peer-group configs</peer-
description>
<peer-connect-interval>300</peer-connect-interval>
<min-route-advertisement-interval>20</min-route-
</state>
<timers>
<config>
</config>
<state>
</state>
</timers>
<address-families>
<address-family>
<afi>ipv4</afi>
<maximum-prefixes>
<maximum-prefix>
<config>
<prefix-count>4294967295</prefix-
count>
percentage>
<warning-only />
</config>
<state>
<prefix-count>4294967295</prefix-
count>

percentage>
<warning-only />
</state>
</maximum-prefix>
</maximum-prefixes>
<config>
<afi>ipv4</afi>
<activate />
<peer-route-reflector />
</config>
<state>
<afi>ipv4</afi>
<activate />
</state>
<route-map-filters>
<route-map-filter>
direction>
<config>
direction>
<route-map-name>in-map</route-map-
name>
</config>
<state>
direction>
<route-map-name>in-map</route-map-
name>
</state>
</route-map-filter>
<route-map-filter>
direction>
<config>
direction>
<route-map-name>out-map</route-map-
name>
</config>
<state>
direction>
<route-map-name>out-map</route-map-
name>
</state>
</route-map-filter>
</address-family>
</address-families>
</peer-group>
<peer-group>
<peer-group-tag>peer1</peer-group-tag>

<bgp-passwords>
<bgp-password>
<password>0x9a20ef22549ad84b</password>
<config>
</config>
<state>
</state>
</bgp-password>
</bgp-passwords>
<config>
</config>
<state>
</state>
<ebgp-multihop>
<config>
<enabled />
</config>
<state>
<enabled />
</state>
</ebgp-multihop>
<address-families>
<address-family>
<afi>ipv4</afi>
<config>
<afi>ipv4</afi>
<activate />
</config>
<state>
<afi>ipv4</afi>
<activate />
</state>
</address-family>
</address-families>
</peer-group>
<peer-group>
<bgp-passwords>
<bgp-password>
<password>0x9603e78694ace534e74f24019f5bfeb5</
password>
<config>
password>

</config>
<state>
password>
</state>
</bgp-password>
</bgp-passwords>
<config>
<enable-peer-bfd />
</config>
<state>
<enable-peer-bfd />
</state>
<ebgp-multihop>
<config>
<enabled />
</config>
<state>
<enabled />
</state>
</ebgp-multihop>
<address-families>
<address-family>
<afi>ipv6</afi>
<maximum-prefixes>
<maximum-prefix>
<config>
<maximum-prefix-warning />
</config>
<state>
</state>
</maximum-prefix>
</maximum-prefixes>
<config>
<afi>ipv6</afi>
<activate />
</config>
<state>
<afi>ipv6</afi>
<activate />

</state>
</address-family>
<address-family>
<afi>ipv6</afi>
<maximum-prefixes>
<maximum-prefix>
<config>
</config>
<state>
</state>
</maximum-prefix>
</maximum-prefixes>
<config>
<afi>ipv6</afi>
<activate />
<peer-allow-ebgp-vpn />
</config>
<state>
<afi>ipv6</afi>
<activate />
<peer-allow-ebgp-vpn />
</state>
</address-family>
</address-families>
</peer-group>
</peer-groups>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response that defines several aspects of BGP, including global BGP configuration, peer
groups, and AFI-SAFIs for different address families. The configuration also includes authentication settings, timers,
transport settings, and route reflection.
<network-instance>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>

<config>
</config>
<state>
</state>
<state>
<as>100</as>
</state>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>

<peer-groups>
<peer-group>
<config>
password>
</config>
<state>
password>
</state>
<enable-bfd>
<config>
</config>
<state>
</state>
</enable-bfd>
<timers>
<config>
</config>
<state>
</state>
</timers>
<transport>
<config>
</config>
<state>
</state>
</transport>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>

<config>
</config>
<state>
</state>
</prefix-limit>
<config>
</config>
<state>
</state>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
<apply-policy>
<config>
</config>
<state>
</state>
</apply-policy>
</afi-safi>
</afi-safis>
<route-reflector>
<config>
</config>
<state>
</state>
</route-reflector>
</peer-group>
<peer-group>
<config>

</config>
<state>
</state>
<ebgp-multihop>
<config>
</config>
<state>
</state>
</ebgp-multihop>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</peer-group>
<peer-group>
<config>
password>
</config>
<state>
password>
</state>
<enable-bfd>
<config>
</config>
<state>
</state>
</enable-bfd>
<ebgp-multihop>
<config>

</config>
<state>
</state>
</ebgp-multihop>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv6-labeled-unicast>
<prefix-limit>
<config>
</config>
<state>
</state>
</prefix-limit>
</ipv6-labeled-unicast>
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
<afi-safi>
<afi-safi-name
<l3vpn-ipv6-unicast>
<prefix-limit>
<config>
</config>
<state>
</state>
</prefix-limit>
</l3vpn-ipv6-unicast>
<config>
<afi-safi-name
</config>

<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
Restrictions
• The first time /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
peer-groups and /oc-netinst:network-instances/network-instance/protocols/protocol/
bgp/neighbors paths are configured, those configuration needs the respective AFI-SAFI configuration that is
present to indicate AFI type:
neighbor/afi-safis
/oc-netinst:network-instances/network-instance/protocols/protocol/bgp/peer-groups/
peer-group/afi-safis
The above information is necessary for the OcNOS model to generate the following paths:
• After the /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/peer-
groups and /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
neighbors paths are configured on equipment, on the further configurations on those paths the user does not
Create BGP Peer-groups with User-defined VRFs

This XML configuration snippet is used to configure BGP Peer-groups with user-defined VRFs. Peer groups are
configurations that can be used elsewhere without the need to repeat them.
Release


Here is the sample OpenConfig NetConf Payload that provides a structured representation of the settings for various
BGP configurations, such as Autonomous System (AS) numbers, Address Family Identifier and Subsequent Address
Family Identifier (AFI-SAFI) settings, authentication, timers, and more.
<network-instance>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<config>
</config>
<state>
</state>
</global>
</bgp>
</protocol>
</protocols>
</network-instance>
<network-instance>
</network-instance>
<network-instance>
<name>vrfA</name>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name

</config>
</afi-safi>
</afi-safis>
</global>
<peer-groups>
<peer-group>
<peer-group-name>peerA</peer-group-name>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>
<config>
</config>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
password>
<description>VRFA peer-group configs</description>
</config>
<transport>
<config>
</config>
</transport>
<timers>
<config>
</config>
</timers>
<enable-bfd>

<config>
</config>
</enable-bfd>
<route-reflector>
<config>
</config>
</route-reflector>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
<network-instance>
<name>vrfB</name>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<peer-groups>
<peer-group>
<peer-group-name>peerB</peer-group-name>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv6-unicast>
<prefix-limit>
<config>
</config>
</prefix-limit>

<config>
</config>
</ipv6-unicast>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
<description>VRFB peer-group configs</description>
</config>
<enable-bfd>
<config>
</config>
</enable-bfd>
<ebgp-multihop>
<config>
</config>
</ebgp-multihop>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to setup the VRF instances and BGP settings within a network infrastructure.
VRFs allow for the segmentation of the network, enabling the isolation of routing domains. In this configuration, two
VRFs, named vrfA and vrfB, are defined with unique Route Distinguisher (RD) values, indicating their separation.
Within the BGP configuration, specific address families for IPv4 and IPv6 are defined, each associated with a
corresponding VRF. Peer-groups, neighbors, authentication keys, timers, and various other BGP parameters are
configured to facilitate routing and peering relationships in the network.
!
ip vrf vrfA
rd 1:1
!
ip vrf vrfB
rd 1:2
!
!
router bgp 100

!
address-family ipv4 vrf vrfA
neighbor peerA peer-group
neighbor peerA remote-as 100
neighbor peerA fall-over bfd
neighbor peerA activate
neighbor peerA authentication-key 0x9603e78694ace534ea912b9ab53f8a55
neighbor peerA route-reflector-client
neighbor peerA default-originate
neighbor peerA maximum-prefix 2331 100 warning-only
neighbor peerA description VRFA peer-group configs
neighbor peerA passive
neighbor peerA update-source 2.2.2.2
neighbor peerA advertisement-interval 65535
neighbor peerA timers 100 300
neighbor peerA timers connect 900
exit-address-family
!
address-family ipv6 vrf vrfB
neighbor peerB peer-group
neighbor peerB remote-as 200
neighbor peerB local-as 300
neighbor peerB fall-over bfd multihop
neighbor peerB activate
neighbor peerB authentication-key 0x9a20ef22549ad84b
neighbor peerB default-originate
neighbor peerB maximum-prefix 3123 warning-only
neighbor peerB description VRFB peer-group configs
neighbor peerB ebgp-multihop 100
exit-address-family
!

Here is a sample OcNOS NetConf Payload that illustrates a comprehensive BGP configuration. The configuration is
divided into specific sections, each addressing different aspects of BGP operation, security, and peering.
Within this payload, two distinct AFI and SAFI contexts are defined for IPv4 and IPv6 in separate VRF instances named
vrfA and vrfB. Each VRF is associated with specific BGP peer groups, peers, and a range of configurations that
dictate the behavior of BGP in these contexts.
The configuration also includes authentication keys, prefix limits, timers, route reflection settings, BFD configuration,
and other essential parameters that ensure the proper functioning of BGP in the specified VRFs.
<bgp-instances>
<bgp-instance>
<config>
</config>
<state>

<router-run-time-ip-address>0.0.0.0</router-run-time-ip-
address>
</state>
<rib>
<address-family>
<state>
</state>
</address-family>
</rib>
<afi>ipv4</afi>
<vrf-name>vrfA</vrf-name>
<config>
<afi>ipv4</afi>
</config>
<state>
<afi>ipv4</afi>
</state>
<peer-groups>
<peer-group>
<peer-group-tag>peerA</peer-group-tag>
<bgp-passwords>
<bgp-password>
<password>0x9603e78694ace534ea912b9ab53f8a55</password>
<config>
</config>
<state>
</state>
</bgp-password>
</bgp-passwords>
<maximum-prefixes>
<maximum-prefix>
<config>
percentage>
<warning-only />
</config>
<state>

percentage>
<warning-only />
</state>
</maximum-prefix>
</maximum-prefixes>
<config>
<peer-connection-interval>900</peer-
connection-interval>
<min-route-advertisement-interval>65535</min-
route-advertisement-interval>
<peer-description>VRFA peer-group configs</
peer-description>
<enable-peer-bfd />
<activate />
</config>
<state>
<peer-connection-interval>900</peer-
connection-interval>
<min-route-advertisement-interval>65535</min-
route-advertisement-interval>
<peer-description>VRFA peer-group configs</
peer-description>
<enable-peer-bfd />
<activate />
</state>
<timers>
<config>
</config>
<state>
</state>
</timers>
</peer-group>
</peer-groups>
<afi>ipv6</afi>
<vrf-name>vrfB</vrf-name>

<config>
<afi>ipv6</afi>
</config>
<state>
<afi>ipv6</afi>
</state>
<peer-groups>
<peer-group>
<peer-group-tag>peerB</peer-group-tag>
<bgp-passwords>
<bgp-password>
<config>
<password>0x9a20ef22549ad84b</
password>
</config>
<state>
<password>0x9a20ef22549ad84b</
password>
</state>
</bgp-password>
</bgp-passwords>
<maximum-prefixes>
<maximum-prefix>
<config>
</config>
<state>
</state>
</maximum-prefix>
</maximum-prefixes>
<config>
<peer-description>VRFB peer-group configs</
peer-description>
<enable-peer-bfd />
<activate />
</config>
<state>

<peer-description>VRFB peer-group configs</
peer-description>
<enable-peer-bfd />
<activate />
</state>
<ebgp-multihop>
<config>
<enabled />
</config>
<state>
<enabled />
</state>
</ebgp-multihop>
</peer-group>
</peer-groups>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response that specifies different network instances, including the default, management,
vrfA, and vrfB instances.
<network-instance>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<config>
</config>
<state>
</state>
<state>
<as>100</as>
</state>

</global>
</bgp>
</protocol>
</protocols>
</network-instance>
<network-instance>
</network-instance>
<network-instance>
<name>vrfA</name>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<state>
<as>100</as>
</state>
</global>
<peer-groups>
<peer-group>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<prefix-limit>
<config>
</config>

<state>
</state>
</prefix-limit>
<config>
</config>
<state>
</state>
</ipv4-unicast>
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
password>
</config>
<state>
password>
</state>
<transport>
<config>
</config>
<state>
</state>
</transport>
<timers>
<config>

</config>
<state>
</state>
</timers>
<enable-bfd>
<config>
</config>
<state>
</state>
</enable-bfd>
<route-reflector>
<config>
</config>
<state>
</state>
</route-reflector>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
<network-instance>
<name>vrfB</name>
<protocols>
<protocol>
<identifier
<name>100</name>
<bgp>
<global>
<config>
<as>100</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name

</state>
</afi-safi>
</afi-safis>
<state>
<as>100</as>
</state>
</global>
<peer-groups>
<peer-group>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv6-unicast>
<prefix-limit>
<config>
</config>
<state>
</state>
</prefix-limit>
<config>
</config>
<state>
</state>
</ipv6-unicast>
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>
<state>

</state>
<enable-bfd>
<config>
</config>
<state>
</state>
</enable-bfd>
<ebgp-multihop>
<config>
</config>
<state>
</state>
</ebgp-multihop>
</peer-group>
</peer-groups>
</bgp>
</protocol>
</protocols>
</network-instance>
Restrictions
• The first time /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/
bgp/neighbors paths are configured, those configuration needs the respective AFI-SAFI configuration that is
neighbor/afi-safis
The above information is necessary for the OcNOS model to generate the following paths:
neighbors paths are configured on equipment, on the further configurations on those paths the user need not
indicate the AFI-SAFI as the translation will look for this information on the equipment database.

Configure Update-source on Neighbor

This XML configuration snippet is used to specify the configuration of the update-source parameter on a neighbor in
the context of a network device configuration. This XML configuration allows internal BGP sessions to use any
operating interface for TCP connections.
Release

Here is the sample OpenConfig NetConf Payload that specifies the configuration of a network instance named
default with BGP. Within this network instance, a BGP peer or neighbor is configured to establish a connection with
the IP address 1.1.1.1 and share IPv4 unicast routing information.
In this payload, various parameters such as the local address, peer AS, and AFI-SAFI are configured to enable
communication and routing between BGP neighbors.
This XML configuration allows internal BGP sessions to use any available operating interface for establishing TCP
connections.
<network-instance>
<protocols>
<protocol xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">
<name>100</name>
<config>
<name>100</name>
</config>
<bgp>
<global>
<config>
<as>100</as>
</config>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<config>
</config>
</afi-safi>
</afi-safis>
<config>

</config>
<transport>
<config>
</config>
</transport>
</neighbor>
</neighbors>
</bgp>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI commands are to configure a BGP neighbor relationship within the BGP process running on a router
with AS number 100. Specifically, it configures a BGP neighbor with the IP address 1.1.1.1, assigns it the same AS
number (AS 100), and specifies that the local address for establishing the BGP connection should be 2.2.2.2. This
update-source parameter ensures that the BGP sessions between the local router and the neighbor use the
specified source IP address (2.2.2.2) for their TCP connections.
router bgp 100
neighbor 1.1.1.1 update-source 2.2.2.2
!

Here is a sample OcNOS NetConf Payload for a BGP instance with AS number 100 is defined. Within this instance, a
BGP peer relationship is established with a neighbor having the IP address 1.1.1.1. The payload further specifies
that the local router should use the source IP address 2.2.2.2 when communicating with this BGP peer, ensuring
proper BGP session establishment and communication.
<bgp-instances>
<bgp-instance>
<config>
</config>
<peers>
<peer>
<config>
</config>
</peer>
</peers>
</bgp-instance>
</bgp-instances>
</bgp>


Here is a NetConf validation response describing the default network instance, along with its associated protocols.
Notably, the response includes information about a BGP instance with an AS number of 100, illustrating its global and
neighbor-specific settings. The BGP neighbor relationship is established with an IP address of 1.1.1.1 and is
configured to use a local address of 2.2.2.2 for communication.
instance">
<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<config>
<identifier
<name>100</name>
</config>
<bgp>
<global>

<config>
<as>100</as>
</config>
<state>
<as>100</as>
</state>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<config>
</config>
</afi-safi>
</afi-safis>
<config>
</config>
<transport>
<config>
</config>
<state>
</state>
</transport>
<state>
</state>
</neighbor>
</neighbors>
</bgp>
<state>
<identifier
<name>100</name>
</state>
</protocol>
</protocols>
</network-instance>
Restrictions
None

Double Link in Load Balance

In this XML configuration snippet, two links are used to ensure service availability, and all traffic is routed through both
links simultaneously. If either of these links experiences a failure, all traffic is automatically redirected to the remaining
available link.
Release

Here is the sample OpenConfig NetConf Payload to indicate the configuration of a network instance named TEST_A9
with associated BGP protocols and peer groups. In this scenario, two peer groups, PPAL_BGP_L3 and BCK_BGP_L3,
are defined within BGP, each with its specific settings. The configuration also specifies the use of multiple paths for
external BGP (eBGP) sessions and enables IPv4 unicast address families for these peer groups. Furthermore, it
outlines neighbor configurations, including their addresses, peer group associations, and additional parameters like
local and peer AS numbers.
<network-instance>
<name>TEST_A9</name>
<config>
<type>L3VRF</type>
</config>
<protocols>
<protocol>
<identifier>BGP</identifier>
<name>65000</name>
<config>
<identifier>BGP</identifier>
<name>65000</name>
</config>
<bgp>
<peer-groups>
<peer-group>
<afi-safis>
<afi-safi>
<config>
safi-name>
</config>
</afi-safi>
</afi-safis>
<peer-group-name>PPAL_BGP_L3</peer-group-name>
<config>

</config>
</peer-group>
<peer-group>
<afi-safis>
<afi-safi>
<config>
safi-name>
</config>
</afi-safi>
</afi-safis>
<peer-group-name>BCK_BGP_L3</peer-group-name>
<config>
</config>
</peer-group>
</peer-groups>
<global>
<config>
<as>65000</as>
</config>
<config>
</config>
<ebgp>
<config>
</config>
</ebgp>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<config>
safi-name>
</config>
</afi-safi>
</afi-safis>
<config>
<peer-group>PPAL_BGP_L3</peer-group>
<neighbor-address>172.17.30.2</neighbor-
address>

<description>PPAL_SESSION</description>
</config>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<config>
safi-name>
</config>
</afi-safi>
</afi-safis>
<config>
<peer-group>BCK_BGP_L3</peer-group>
<neighbor-address>172.17.40.2</neighbor-
address>
<description>BCK_SESSION</description>
</config>
</neighbor>
</neighbors>
</bgp>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI commands are used to create a specific VRF instance named TEST_A9 with a unique route
distinguisher (RD) of 65000:100. Within the BGP configuration for AS number 65000, two address families, IPv4 and
IPv6, are defined for the TEST_A9 VRF, each allowing up to two paths for eBGP (external BGP) sessions.
The configuration also includes the setup of neighbor relationships, with peers grouped into PPAL_BGP_L3 and
BCK_BGP_L3 peer groups. Each neighbor is associated with the appropriate peer group, and their remote AS numbers
and descriptions are specified.
!
ip vrf TEST_A9
rd 65000:100
!
router bgp 65000
!
address-family ipv4 vrf TEST_A9
max-paths ebgp 2
neighbor BCK_BGP_L3 peer-group
neighbor BCK_BGP_L3 remote-as 18010
neighbor BCK_BGP_L3 activate
neighbor PPAL_BGP_L3 peer-group
neighbor PPAL_BGP_L3 remote-as 18746

neighbor PPAL_BGP_L3 activate

neighbor 172.17.30.2 peer-group PPAL_BGP_L3
neighbor 172.17.40.2 peer-group BCK_BGP_L3
neighbor 172.17.30.2 description PPAL_SESSION
neighbor 172.17.40.2 description BCK_SESSION
exit-address-family
!
address-family ipv6 vrf TEST_A9
max-paths ebgp 2
exit-address-family
!

Here is a sample OcNOS NetConf Payload illustrating the configuration of a network instance with associated BGP
settings. This configuration is designed to establish BGP sessions within the specified VRF instance and configure
BGP-related parameters.
In this payload, the VRF instance type, BGP AS, BGP peering configurations for both IPv4 and IPv6 address families,
and the maximum number of paths allowed for eBGP (external BGP) sessions are configured.
instance">
<network-instance>
<instance-name>TEST_A9</instance-name>
<config>
</config>
<config>
<vrf-name>TEST_A9</vrf-name>
</config>
<config>
<rd-string>65000:100</rd-string>
</config>
</bgp-vrf>
</vrf>
</network-instance>
<bgp-instances>
<bgp-instance>
<config>
</config>
<afi>ipv4</afi>
<vrf-peers>

<vrf-peer>
<config>
<peer-description>PPAL_SESSION</peer-
description>
<mapped-peer-group-tag-af>PPAL_BGP_L3</mapped-
peer-group-tag-af>
</config>
</vrf-peer>
<vrf-peer>
<config>
<peer-description>BCK_SESSION</peer-
description>
<mapped-peer-group-tag-af>BCK_BGP_L3</mapped-
peer-group-tag-af>
</config>
</vrf-peer>
</vrf-peers>
<config>
<afi>ipv4</afi>
</config>
<maximum-paths>
<config>
</config>
</maximum-paths>
<peer-groups>
<peer-group>
<peer-group-tag>BCK_BGP_L3</peer-group-tag>
<config>
<peer-group-tag>BCK_BGP_L3</peer-group-tag>
<activate />
</config>
</peer-group>
<peer-group>
<peer-group-tag>PPAL_BGP_L3</peer-group-tag>
<config>
<peer-group-tag>PPAL_BGP_L3</peer-group-tag>
<activate />
</config>
</peer-group>
</peer-groups>
<afi>ipv6</afi>

<config>
<afi>ipv6</afi>
</config>
<maximum-paths>
<config>
</config>
</maximum-paths>
</bgp-instance>
</bgp-instances>
</bgp>

Here is a NetConf validation response about the network instance's configuration, the BGP AS number, BGP peering
details, and protocol tables for both IPv4 and IPv6 address families.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
<name>65000</name>
<bgp>
<global>
<config>
<as>65000</as>
</config>

<config>
</config>
<ebgp>
<config>
</config>
</ebgp>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
<description>PPAL_SESSION</description>
<peer-group>PPAL_BGP_L3</peer-group>
</config>
</neighbor>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
<description>BCK_SESSION</description>
<peer-group>BCK_BGP_L3</peer-group>
</config>
</neighbor>

</neighbors>
<peer-groups>
<peer-group>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
</config>
</peer-group>
<peer-group>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
</config>
</peer-group>
</peer-groups>
</bgp>
<config>
<identifier
<name>65000</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol

<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>

</table>
</tables>
</network-instance>
Restrictions
bgp/neighbors paths are configured, those configuration needs the respective AFI-SAFI configuration that be
neighbor/afi-safis
The above information is necessary on OcNOS model to generate the follow paths:
neighbors paths are configured on equipment, on the further configurations on those paths the user do not need
to indicate the AFI-SAFE, the translation will look for this information on equipment database.
Delete BGP Instance

In this XML configuration snippet, BGP instances are configured on network-instance on OpenConfig and on container
BGP on OcNos side. Due this difference the delete process need to handle if the operation is trying to delete one VRF
instance or the entire BGP instance.
When using OpenConfig, the BGP object on OcNOS database is only deleted by the delete on "default" network-
instance. When the delete is execute on VRF network-instance it only deletes the given VRF instance.
If there are VRF instances configured and a delete operation is executed on "default" network-instance, it going to
clean only entries configured on "default" network-instance. To remove VRF instances, the user needs to apply a
operation delete on VRF instances.
Release

Here is a sample NetConf Payload to delete BGP instance.
Delete VRF instance:
<network-instance>
<name>VRF1</name>

<protocols>
<protocol operation="delete">
<identifier
<name>100</name>
</protocol>
</protocols>
</network-instance>
Delete default instance:

<network-instance>
<protocols>
<protocol operation="delete">
<identifier
<name>100</name>
</protocol>
</protocols>
</network-instance>

Here is a sample OcNOS NetConf Payload to delete BGP instance.
Delete VRF instance:
<bgp-instances>
<bgp-instance>
<address-family-vrf operation="delete">
<afi>ipv4</afi>
</bgp-instance>
</bgp-instances>
</bgp>
Delete default instance:

<bgp-instances>
<bgp-instance operation="delete">
</bgp-instance>
</bgp-instances>
</bgp>

Restrictions
On OpenConfig BGP datamodel the container global do not have any key to identify a single BGP instance, but the
BGP AS information is placed under xpath /oc-netinst:network-instances/network-instance/
protocols/protocol/bgp/global/config/as.
On IPI BGP datamodel, the BGP AS information is a key for BGP container, and it does not allow the delete on xpath /
ipi-bgp:/bgp/bgp-instances/bgp-instance/config/bgp-as to avoid delete its own instance key.
In this case, when translation framework detects a delete or remove operation on following OpenConfig xpaths:
1. /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global
2. /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/config
3. /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/global/config/
as
It will trigger an error message to NETCONF client and do not execute the delete operation.
To avoid this issue, when user needs to delete or remove a configuration under OpenConfig xpath /oc-
netinst:network-instances/network-instance/protocols/protocol/bgp/global/config, user
must adds a "delete" or "remove" operation directly on the leaf or leaves desired to be removed, rather than delete the
entire container.
BGP RIB Counters IPv4

The BGP RIB (Routing information base) is a set of counters to retrieve information about routes from neighbors. This
section gives details on BGP RIB IPv4.
The containers related to RIB are only the status on both Open Config and OcNOS datamodels, and there are no
configuration related to this.
On OcNOS, the containers are available only after the BGP negotiate routers, the tables are empty before and cannot
be retrieved.
The table below displays each table information:.
OcNOS CLI OcNOS XPath Open Config XPath

show ip bgp neighbors /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/network-
<IP-address> routes instance/rib/address-family/ instance/protocols/protocol/bgp/rib/afi-
routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
routes/route
show ip bgp neighbors For default VRF instances: /ipi- /oc-netinst:network-instances/network-
<IP-address> received- bgp:bgp/bgp-instances/bgp- instance/protocols/protocol/bgp/rib/afi-
routes instance/rib/address-family/ safis/afi-safi/ipv4-unicast/neighbors/
routes/route/next-hop neighbor/adj-rib-in-post/routes/route
For non-default VRF instances: /ipi-
bgp:bgp/bgp-instances/bgp-
instance/peers/peer/address-
families/address-family/peer-
adj-in-route/next-hop

OcNOS CLI OcNOS XPath Open Config XPath

show ip bgp neighbors For default VRF instances: /ipi- /oc-netinst:network-instances/network-
<IP-address> advertised- bgp:bgp/bgp-instances/bgp- instance/protocols/protocol/bgp/rib/afi-
routes instance/address-family-vrfs/ safis/afi-safi/ipv4-unicast/neighbors/
address-family-vrf/vrf-peers/ neighbor/adj-rib-out-post/routes/route
peer-adj-out-route/next-hop
families/address-family/peer-
adj-out-route/next-ho
To get “last update” /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/network-
information: instance/rib/address-family/ instance/protocols/protocol/bgp/rib/afi-
show ip bgp <IP-address> routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
routes/route
show ip bgp ipv4 unicast /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/network-
<IP-address> instance/rib/address-family/ instance/protocols/protocol/bgp/rib/afi-
routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
routes/route
When have user-defined /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/network-
VRF: instance/rib/address-family/ instance/protocols/protocol/bgp/rib/afi-
show ip bgp vrf <VRF routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
name> routes/route
show ip bgp vpnv4 vrf routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
<VRF name> routes/route
show ip bgp vpnv4 vrf routes/route/next-hop safis/afi-safi/ipv4-unicast/loc-rib/
<VRF name> <IP- routes/route
address>
Release

N/A
OcNOS CLI Command

The below CLI command is an example to illustrate the indicated counters.
To have a complete BGP RIB scenario, it needs more than one equipment configured to work with BGP.
router bgp 200
!
redistribute connected
redistribute static

neighbor 10.10.10.11 soft-reconfiguration inbound

exit-address-family
!

Here is a sample OcNOS NetConf Payload to illustrate the BGP RIB Counters IPv4.
<bgp-instances>
<bgp-instance>
<config>
</config>
<state>
<router-run-time-ip-address>192.168.122.61</router-run-time-
ip-address>
</state>
<rib>
<address-family>
<afi>ipv4</afi>
<state>
<afi>ipv4</afi>
</state>
<routes>
<route>
<route-distinguisher>0</route-distinguisher>
<network-address>10.10.10.0/24</network-address>
<next-hop>
<next-hop-address>0.0.0.0</next-hop-address>
<state>
<next-hop-address>0.0.0.0</next-hop-
address>
<peer-network-weight>32768</peer-network-
weight>
<bgp-as-path-string>Local</bgp-as-path-
string>
<bgp-as-path-4-byte-origin>incomplete</
bgp-as-path-4-byte-origin>
<ibgp-metric-route>0</ibgp-metric-route>
<route-local-preference>100</route-local-
preference>
<last-update-route>2022-12-04T17:50:28Z</
last-update-route>
<reflector-client-route>false</reflector-
client-route>
<route-dampening-active>false</route-
dampening-active>
<history-route>false</history-route>

<nexthop-valid-route>true</nexthop-valid-
route>
<med-flag-type-route>false</med-flag-type-
route>
<valid-route>true</valid-route>
<stale-route>false</stale-route>
<route-type>sourced</route-type>
<ecmp-multi-candidate-route>false</ecmp-
multi-candidate-route>
<multi-installed-route>false</multi-
installed-route>
<atomic-aggregate-route>false</atomic-
aggregate-route>
<selected-route>true</selected-route>
<bgp-tx-path-id>-1</bgp-tx-path-id>
<bgp-rx-path-id>-1</bgp-rx-path-id>
</state>
</next-hop>
<next-hop>
address>
<state>
address>
weight>
string>
preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>

<network-address>10.10.10.0/24</network-
address>
</state>
</route>
<route>
<network-address>192.168.122.0</network-address>
<next-hop>
<next-hop-address>0.0.0.0</next-hop-address>
<state>
address>
weight>
string>
preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<next-hop>
address>
<state>
address>
weight>
string>

preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
<network-address>192.168.122.0</network-
address>
</state>
</route>
</routes>
</address-family>
<address-family>
<state>
</state>
</address-family>
</rib>
<address-families>
<address-family>
<afi>ipv4</afi>
<config>
<afi>ipv4</afi>
</config>
<state>
<afi>ipv4</afi>
</state>
<route-redistribute-lists>
<route-redistribute-list>

<protocol-type>connected</protocol-type>
<config>
</config>
<state>
</state>
</route-redistribute-list>
<protocol-type>static</protocol-type>
<config>
</config>
<state>
</state>
</route-redistribute-lists>
</address-family>
</address-families>
<peers>
<peer>
<address-families>
<address-family>
<afi>ipv4</afi>
<peer-adj-out-route>
address>
<next-hop>
address>
<state>
<next-hop-address>10.10.10.10</next-
hop-address>
<peer-network-weight>32768</peer-
network-weight>
<bgp-as-path-string>Local</bgp-as-
path-string>
<bgp-as-path-4-byte-
origin>incomplete</bgp-as-path-4-byte-origin>
<ibgp-metric-route>0</ibgp-metric-
route>
<route-local-preference>100</route-
local-preference>
<last-update-route>2022-12-
04T17:50:28Z</last-update-route>
<reflector-client-route>false</
reflector-client-route>
dampening-active>
<med-flag-type-route>false</med-flag-
type-route>

<ecmp-multi-candidate-route>false</
ecmp-multi-candidate-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
address>
</state>
</peer-adj-out-route>
address>
<next-hop>
address>
<state>
hop-address>
network-weight>
path-string>
route>
local-preference>
dampening-active>
type-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>

address>
</state>
<peer-adj-in-route>
address>
<next-hop>
address>
<state>
hop-address>
weight>
<bgp-as-path-string>300</bgp-as-path-
string>
route>
<network-remote-address-
route>192.168.122.60</network-remote-address-route>
<route-peer-address>10.10.10.11</
route-peer-address>
local-preference>
dampening-active>
<nexthop-valid-route>false</nexthop-
valid-route>
type-route>
<route-type>external</route-type>
installed-route>
aggregate-route>
<bgp-tx-path-id>0</bgp-tx-path-id>
<bgp-rx-path-id>0</bgp-rx-path-id>
</state>
</next-hop>
<state>
address>
</state>
</peer-adj-in-route>
<peer-adj-in-route>
address>

<next-hop>
address>
<state>
hop-address>
weight>
string>
route>
<route-peer-address>10.10.10.11</
route-peer-address>
local-preference>
dampening-active>
valid-route>
type-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
address>
</state>
<config>
<afi>ipv4</afi>
<activate />
<soft-reconfig-inbound />
</config>
<state>
<afi>ipv4</afi>
<activate />

<community-count>0</community-count>
<address-family-capability>advertise-receive</
address-family-capability>
<ipv6-next-hop-global>::</ipv6-next-hop-
global>
<ipv6-next-hop-local>::</ipv6-next-hop-local>
<remote-port>179</remote-port>
<remote-address>10.10.10.11</remote-address>
<local-host>10.10.10.10</local-host>
<ipv4-next-hop>10.10.10.10</ipv4-next-hop>
<local-port>40394</local-port>
<peer-address-family-table-version>1</peer-
address-family-table-version>
<address-family-table-version>1</address-
family-table-version>
<send-prefix-count>2</send-prefix-count>
<count>1</count>
<connection-type>non_shared</connection-type>
<connection-established-count>1</connection-
established-count>
<graceful-restart-time>0</graceful-restart-
time>
<bgp-established-up-time>00:02:24</bgp-
established-up-time>
<last-read-time>00:00:23</last-read-time>
<bgp-peer-state>established</bgp-peer-state>
<link-type>external</link-type>
<advertisement-interval>30</advertisement-
interval>
<calculated-hold-time>90</calculated-hold-
time>
<calculated-keepalive>30</calculated-
keepalive>
<route-refresh-capability>advertised-and-
received-old-and-new</route-refresh-capability>
<counters>
<keepalive-in-messages>6</keepalive-in-
messages>
<keepalive-out-messages>6</keepalive-out-
messages>
<open-messages-in>1</open-messages-in>
<open-messages-out>1</open-messages-out>
<as-path-count>2</as-path-count>
<update-message-in>1</update-message-in>
<update-message-out>1</update-message-out>
<received-packet-count>8</received-packet-
count>
<notification-in>0</notification-in>
<notification-out>0</notification-out>
<packet-in-queue>0</packet-in-queue>
<packet-out-queue>0</packet-out-queue>
<sent-packet-count>8</sent-packet-count>
<refresh-received-packet-count>0</refresh-
received-packet-count>
<refresh-sent-packet-count>0</refresh-
sent-packet-count>
</counters>

</state>
<peer-index>
<state>
<peer-index>1</peer-index>
<offset>0</offset>
<mask>0x2</mask>
</state>
</peer-index>
</address-family>
</address-families>
<config>
</config>
<state>
</state>
</peer>
</peers>
</bgp-instance>
</bgp-instances>
</bgp>

<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier

</state>
</protocol>
<protocol>
<identifier
<name>200</name>
<bgp>
<global>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
<as>200</as>
</config>
<state>
<as>200</as>
</state>
</global>
<rib>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv4-unicast>
<loc-rib>
<routes>
<route>
<prefix>10.10.10.0/24</prefix>
<origin>0.0.0.0</origin>
<path-id>0</path-id>
<state>
<last-modified>1670176228</last-modified>

</state>
</route>
<route>
<prefix>192.168.122.0</prefix>
<state>
</state>
</route>
</routes>
</loc-rib>
<neighbors>
<neighbor>
<state>
</state>
<adj-rib-out-post>
<routes>
<route>
<state>
</state>
</route>
<route>
<state>
</state>
</route>
</routes>
</adj-rib-out-post>
<adj-rib-in-post>
<routes>
<route>
<state>

</state>
</route>
<route>
<state>
</state>
</route>
</routes>
</adj-rib-in-post>
</neighbor>
</neighbors>
</ipv4-unicast>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</rib>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>
<state>
</state>

</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>200</name>
</config>
<state>
<identifier
<name>200</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>

<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
<table-connections>
<table-connection>
<src-protocol
types:DIRECTLY_CONNECTED</src-protocol>
<dst-protocol
types:BGP</dst-protocol>
<address-family
<config>
<dst-protocol
pol-types:BGP</dst-protocol>
<address-family
<dst-instance xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-ni-
augments">200</dst-instance>
<src-protocol
pol-types:DIRECTLY_CONNECTED</src-protocol>
</config>

</table-connection>
<table-connection>
<src-protocol
types:STATIC</src-protocol>
<dst-protocol
<address-family
<config>
<dst-protocol
<address-family
<src-protocol
pol-types:STATIC</src-protocol>
</config>
</table-connection>
</table-connections>
</network-instance>
Restrictions
The containers related to RIB are status only on both Open Config and OcNOS datamodels, and there are no
On OcNOS the containers are available only after the BGP negotiate routers, before it this tables are empty and could
not be retrieved.
The paths /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/rib/afi-
safi/afi-safi/ipv4-unicast/loc-rib/routes/route and /oc-netinst:network-instances/
network-instance/protocols/protocol/bgp/rib/afi-safi/afi-safi/ipv6-unicast/loc-rib/
routes/route have some keys with fixed values, the table below show the values. Note the “X” indicate that is valid
for IPv4 and IPv6 containers.
OpenConfig XPath OcNOS XPath

/oc-netinst:network-instances/network- Use fixed value:
instance/protocols/protocol/bgp/rib/afi- • IPV4: “0.0.0.0”
• IPV6: “0::0”
safis/afi-safi/ipvX-unicast/loc-rib/routes/
route/origin

/oc-netinst:network-instances/network- Fixed value “0”

instance/protocols/protocol/bgp/rib/afi-
safis/afi-safi/ipvX-unicast/loc-rib/routes/
route/path-id
/oc-netinst:network-instances/network- /ipi-bgp:bgp/bgp-instances/
instance/protocols/protocol/bgp/rib/afi- bgp-instance/rib/address-
safis/afi-safi/ipvX-unicast/loc-rib/routes/ family/routes/route/network-
route/prefix address
BGP RIB Counters IPv6

The BGP RIB (Routing information base) is a set of counters to retrieve information about routes from neighbors. This
section gives details on BGP RIB IPv6.
The containers related to RIB are only the status on both Open Config and OcNOS datamodels, and there are no
On OcNOS, the containers are available only after the BGP negotiate routers, the tables are empty before and cannot
be retrieved.
The table below displays each table information:.
OcNOS CLI OcNOS XPath OpenConfig XPath

show bgp ipv6 neighbors /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/
<IP-address IPv6> routes instance/rib/address-family/ network-instance/protocols/protocol/
routes/route/next-hop bgp/rib/afi-safis/afi-safi/ipv6-
unicast/loc-rib/routes/route
show bgp ipv6 neighbors For default VRF instances: /ipi- /oc-netinst:network-instances/
<IP-address IPv6> bgp:bgp/bgp-instances/bgp- network-instance/protocols/protocol/
received-routes instance/address-family-vrfs/ bgp/rib/afi-safis/afi-safi/ipv6-
address-family-vrf/vrf-peers/vrf- unicast/neighbors/neighbor/adj-rib-
peer/peer-adj-in-route/next-hop in-post/routes/route
families/address-family/peer-adj-
in-route/next-hop
show bgp ipv6 neighbors For default VRF instances: /ipi- /oc-netinst:network-instances/
<IP-address IPv6> bgp:bgp/bgp-instances/bgp- network-instance/protocols/protocol/
advertised-routes instance/address-family-vrfs/ bgp/rib/afi-safis/afi-safi/ipv6-
address-family-vrf/vrf-peers/vrf- unicast/neighbors/neighbor/adj-rib-
peer/peer-adj-out-route/next-hopp out-post/routes/route
families/address-family/peer-adj-
out-route/next-hop
To get “last update” /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/
information: instance/rib/address-family/ network-instance/protocols/protocol/
show bgp ipv6 <IP-address routes/route/next-hop bgp/rib/afi-safis/afi-safi/ipv6-
IPv6> unicast/loc-rib/routes/route

show bgp ipv6 unicast <IP- /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/

address IPv6> instance/rib/address-family/ network-instance/protocols/protocol/
When have user-defined /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/
VRF, to get “last update” instance/rib/address-family/ network-instance/protocols/protocol/
information: routes/route/next-hop bgp/rib/afi-safis/afi-safi/ipv6-
show ip bgp vpnv6 vrf <VRF unicast/loc-rib/routes/route
name>
When have user-defined /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/
VRF, to get “last update” instance/rib/address-family/ network-instance/protocols/protocol/
information: routes/route/next-hop bgp/rib/afi-safis/afi-safi/ipv6-
show ip bgp vpnv6 vrf <VRF unicast/loc-rib/routes/route
name> <IP-address IPv6>
show bgp ipv6 summary /ipi-bgp:bgp/bgp-instances/bgp- /oc-netinst:network-instances/
instance/rib/address-family/ network-instance/protocols/protocol/
Release

N/A
OcNOS CLI Command

The below CLI command is an example to illustrate the indicated counters.
To have a complete BGP RIB scenario, it needs more than one equipment configured to work with BGP.
interface eth1
ipv6 address f0ca::11/48
!
router bgp 200
neighbor f0ca::10 remote-as 300
!
redistribute connected
redistribute static
neighbor f0ca::10 activate
neighbor f0ca::10 soft-reconfiguration inbound
exit-address-family
!

Here is a sample OcNOS NetConf Payload to illustrate the BGP RIB Counters IPv6.
<bgp-instances>
<bgp-instance>

<config>
</config>
<state>
<router-run-time-ip-address>192.168.122.60</router-run-time-
ip-address>
</state>
<rib>
<address-family>
<afi>ipv6</afi>
<state>
<afi>ipv6</afi>
</state>
<routes>
<route>
<network-address>b0b0::/64</network-address>
<next-hop>
<next-hop-address>::</next-hop-address>
<state>
weight>
string>
preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>

</state>
</next-hop>
<next-hop>
<next-hop-
address>f0ca::10(fe80::5054:ff:fe78:1f3)</next-hop-address>
<state>
<next-hop-
weight>
string>
preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
</state>
</route>
<route>
<network-address>f0ca::/24</network-address>
<next-hop>
<next-hop-
<state>
<next-hop-
weight>

<bgp-med-value>0</bgp-med-value>
string>
<originator-id-route>192.168.122.52</
originator-id-route>
<route-peer-address>f0ca::10</route-peer-
address>
preference>
last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
</state>
</route>
<route>
<next-hop>
<state>
weight>
string>
preference>

last-update-route>
client-route>
dampening-active>
route>
route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
</state>
</route>
</routes>
</address-family>
<address-family>
<state>
</state>
</address-family>
</rib>
<address-families>
<address-family>
<afi>ipv6</afi>
<config>
<afi>ipv6</afi>
</config>
<state>
<afi>ipv6</afi>
</state>
<route-redistribute-lists>
<config>

</config>
<state>
</state>
<config>
</config>
<state>
</state>
</route-redistribute-lists>
</address-family>
</address-families>
<peers>
<peer>
<peer-address>f0ca::10</peer-address>
<address-families>
<address-family>
<afi>ipv6</afi>
<next-hop>
<next-hop-
address>f0ca::11(fe80::5054:ff:fed0:8295)</next-hop-address>
<state>
<next-hop-
network-weight>
path-string>
route>
local-preference>
dampening-active>
type-route>
installed-route>

aggregate-route>
</state>
</next-hop>
<state>
<network-address>b0b0::/64</network-
address>
</state>
<next-hop>
<next-hop-
<state>
<next-hop-
network-weight>
path-string>
route>
local-preference>
dampening-active>
type-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
<network-address>f0ca::/48</network-
address>
</state>
<peer-adj-in-route>

<next-hop>
<next-hop-
<state>
<next-hop-
weight>
string>
route>
<route-peer-address>f0ca::10</route-
peer-address>
local-preference>
dampening-active>
valid-route>
type-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
<network-address>b0b0::/64</network-
address>
</state>
<peer-adj-in-route>
<next-hop>
<next-hop-
<state>
<next-hop-
weight>

string>
route>
<route-peer-address>f0ca::10</route-
peer-address>
local-preference>
dampening-active>
valid-route>
type-route>
installed-route>
aggregate-route>
</state>
</next-hop>
<state>
<network-address>f0ca::/24</network-
address>
</state>
<config>
<afi>ipv6</afi>
<activate />
</config>
<state>
<afi>ipv6</afi>
<activate />
<community-count>0</community-count>
<ipv6-next-hop-global>f0ca::11</ipv6-next-hop-
global>
<ipv6-next-hop-local>fe80::5054:ff:fed0:8295</
ipv6-next-hop-local>
<remote-port>54786</remote-port>
<remote-address>f0ca::10</remote-address>

<local-host>f0ca::11</local-host>
<ipv4-next-hop>192.168.122.60</ipv4-next-hop>
<local-port>179</local-port>
<peer-address-family-table-version>2</peer-
address-family-table-version>
<address-family-table-version>2</address-
family-table-version>
<send-prefix-count>2</send-prefix-count>
<count>1</count>
<connection-type>shared</connection-type>
<connection-established-count>1</connection-
established-count>
<graceful-restart-time>0</graceful-restart-
time>
<bgp-established-up-time>00:00:33</bgp-
established-up-time>
<last-read-time>00:00:05</last-read-time>
<bgp-peer-state>established</bgp-peer-state>
<link-type>external</link-type>
<advertisement-interval>30</advertisement-
interval>
<calculated-hold-time>90</calculated-hold-
time>
<calculated-keepalive>30</calculated-
keepalive>
<route-refresh-capability>advertised-and-
received-old-and-new</route-refresh-capability>
<capability-ipv6-unicast>advertised-and-
received</capability-ipv6-unicast>
<counters>
<keepalive-in-messages>2</keepalive-in-
messages>
<keepalive-out-messages>2</keepalive-out-
messages>
<open-messages-in>1</open-messages-in>
<open-messages-out>2</open-messages-out>
<as-path-count>2</as-path-count>
<update-message-in>1</update-message-in>
<update-message-out>1</update-message-out>
<received-packet-count>4</received-packet-
count>
<notification-in>0</notification-in>
<notification-out>0</notification-out>
<packet-in-queue>0</packet-in-queue>
<packet-out-queue>0</packet-out-queue>
<sent-packet-count>5</sent-packet-count>
<refresh-received-packet-count>0</refresh-
received-packet-count>
<refresh-sent-packet-count>0</refresh-
sent-packet-count>
</counters>
</state>
<peer-index>
<state>
<peer-index>1</peer-index>
<offset>0</offset>
<mask>0x2</mask>

</state>
</peer-index>
</address-family>
</address-families>
<config>
</config>
<state>
</state>
</peer>
</peers>
</bgp-instance>
</bgp-instances>
</bgp>

<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier
</state>
</protocol>
<protocol>

<identifier
<name>200</name>
<bgp>
<global>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
<as>200</as>
</config>
<state>
<as>200</as>
</state>
</global>
<rib>
<afi-safis>
<afi-safi>
<afi-safi-name
<ipv6-unicast>
<loc-rib>
<routes>
<route>
<prefix>b0b0::/64</prefix>
<origin>0::0</origin>
<state>
</state>
</route>
<route>
<prefix>f0ca::/24</prefix>

<state>
</state>
</route>
<route>
<state>
</state>
</route>
</routes>
</loc-rib>
<neighbors>
<neighbor>
<neighbor-address>f0ca::10</neighbor-address>
<state>
</state>
<adj-rib-out-post>
<routes>
<route>
<state>
</state>
</route>
<route>
<state>
</state>
</route>
</routes>
</adj-rib-out-post>
<adj-rib-in-post>
<routes>
<route>

<state>
</state>
</route>
<route>
<state>
</state>
</route>
</routes>
</adj-rib-in-post>
</neighbor>
</neighbors>
</ipv6-unicast>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</rib>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>

<state>
</state>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>200</name>
</config>
<state>
<identifier
<name>200</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol

<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
<interfaces>
<interface>
<id>eth0</id>
<config>
<id>eth0</id>
</config>
</interface>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
</interface>
<interface>
<id>eth2</id>
<config>

<id>eth2</id>
</config>
</interface>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
</interface>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
</interface>
<interface>
<id>eth5</id>
<config>
<id>eth5</id>
</config>
</interface>
<interface>
<id>eth6</id>
<config>
<id>eth6</id>
</config>
</interface>
<interface>
<id>eth7</id>
<config>
<id>eth7</id>
</config>
</interface>
<interface>
<id>eth8</id>
<config>
<id>eth8</id>
</config>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
</interface>
</interfaces>
<table-connections>
<table-connection>
<src-protocol

types:DIRECTLY_CONNECTED</src-protocol>
<dst-protocol
<address-family
<config>
<dst-protocol
<address-family
<src-protocol
pol-types:DIRECTLY_CONNECTED</src-protocol>
</config>
</table-connection>
<table-connection>
<src-protocol
types:STATIC</src-protocol>
<dst-protocol
<address-family
<config>
<dst-protocol
<address-family
<src-protocol
pol-types:STATIC</src-protocol>
</config>
</table-connection>
</table-connections>
</network-instance>
<network-instance>
<config>
<type
</config>
<state>

<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family

<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
</network-instance>
Restrictions
The containers related to RIB are status only on both Open Config and OcNOS datamodels, and there are no
On OcNOS the containers are available only after the BGP negotiate routers, before it this tables are empty and could
not be retrived.
The paths /oc-netinst:network-instances/network-instance/protocols/protocol/bgp/rib/afi-
safi/afi-safi/ipv4-unicast/loc-rib/routes/route and /oc-netinst:network-instances/
network-instance/protocols/protocol/bgp/rib/afi-safi/afi-safi/ipv6-unicast/loc-rib/
routes/route have some keys with fixed values, the table below show the values. Note the “X” indicate that is valid
for IPv4 and IPv6 containers.
OpenConfig XPath OcNOS XPath
/oc-netinst:network-instances/network-instance/ Use fixed value:
protocols/protocol/bgp/rib/afi-safis/afi-safi/ • IPV4: “0.0.0.0”
ipvX-unicast/loc-rib/routes/route/origin • IPV6: “0::0”
/oc-netinst:network-instances/network-instance/ Fixed value “0”
protocols/protocol/bgp/rib/afi-safis/afi-safi/
ipvX-unicast/loc-rib/routes/route/path-id
/oc-netinst:network-instances/network-instance/ /ipi-bgp:bgp/bgp-instances/bgp-
protocols/protocol/bgp/rib/afi-safis/afi-safi/ instance/rib/address-family/
ipvX-unicast/loc-rib/routes/route/prefix routes/route/network-address

OSPFv2 Openconfig Translation
Create OSPF Process

This XML configuration snippet is used to create OSPF process.
Release
OpenConfig NETCONF Payload

Here is a sample OpenConfig NetConf Payload to create OSPF process.
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-
type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<ipv4 xmlns="http://openconfig.net/yang/interfaces/ip">
<addresses>
<address>
<ip>10.10.10.1</ip>
<config>
<ip>10.10.10.1</ip>
<prefix-length>24</prefix-length>
</config>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
<network-instance>
<protocols>
<protocol xmlns:oc-pol-types="http://openconfig.net/yang/policy-
types">

<identifier>oc-pol-types:OSPF</identifier>
<name>100</name>
<config>
yang/policy-types">oc-pol-types:OSPF</identifier>
<name>100</name>
</config>
<ospfv2>
<global>
<config>
</config>
</global>
<areas>
<area>
<identifier>0.0.0.0</identifier>
<config>
</config>
<interfaces>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
<network-type xmlns:oc-ospf-
types="http://openconfig.net/yang/ospf-types">oc-ospf-
types:NON_BROADCAST_NETWORK</network-type>
<authentication-type>simple</
authentication-type>
</config>
<interface-ref>
<config>
<interface>xe2</interface>
</config>
</interface-ref>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to create OSPF process.
ospf area-interface-config-mode
router ospf 100
ospf router-id 2.2.2.2
area 0.0.0.0 interface xe2
area 0.0.0.0 interface xe2 passive
area 0.0.0.0 interface xe2 network-type non-broadcast

area 0.0.0.0 interface xe2 authentication

!

Here is a sample OcNOS NetConf Payload to create OSPF process.
<interfaces xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-interface">
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
<ipv4 xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-ip">
<config>
<primary-ip-addr>10.10.10.1/24</primary-ip-addr>
</config>
</ipv4>
</interface>
</interfaces>
instance">
<network-instance>
<config>
</config>
<config>
</config>
</vrf>
<bridge xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-bridge">
<config>
<protocol>ieee-vlan-bridge</protocol>
</config>
</bridge>
</network-instance>
<ospfv2 xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-ospf">
<processes>
<process>
<ospf-id>100</ospf-id>
<config>
</config>
<areas>
<area>
<area-id>0.0.0.0</area-id>
<config>
</config>
<interfaces>
<interface>

<name>xe2</name>
<config>
<name>xe2</name>
<network-type>non-broadcast</network-type>
<passive />
<authentication-type>simple</authentication-
type>
</config>
</interface>
</interfaces>
</area>
</areas>
</process>
</processes>
<global>
<config>
<area-interface-config-mode />
</config>
</global>
</ospfv2>

Here is a NetConf validation response that provides detailed information about creating OSPF process.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
pol-types:OSPF</identifier>
<name>100</name>
<ospfv2>
<global>
<config>
</config>
</global>
<areas>
<area>
<config>
</config>
<state>
</state>
<interfaces>
<interface>

<id>xe2</id>
<config>
<id>xe2</id>
<network-type
xmlns:oc-ospf-types="http://openconfig.net/yang/
ospf-types">oc-ospf-types:NON_BROADCAST_NETWORK</network-type>
<authentication-type>simple</authentication-type>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
<id>xe2</id>
<network-type
ospf-types">oc-ospf-types:NON_BROADCAST_NETWORK</network-type>
<authentication-type>simple</authentication-type>
</state>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
<config>
<identifier
types">oc-pol-types:OSPF</identifier>
<name>100</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol
pol-types:OSPF</protocol>
<address-family
<config>
<protocol
types">oc-pol-types:OSPF</protocol>
<address-family
</config>
</table>
</tables>
</network-instance>
<network-instance>
<config>

<type
</config>
</network-instance>
Restrictions
Area /network-instances/network-instance/protocols/protocol/ospfv2/areas/area
must always be set with at least one interface /network-instances/network-instance/protocols/
protocol/ospfv2/areas/area/interfaces/interface.
Create OSPF Process

This XML configuration snippet is used to create OSPF process.
Release

Here is a sample OpenConfig NetConf Payload to create OSPF process.
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>10.10.10.1</ip>
<config>
<ip>10.10.10.1</ip>
</config>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>

</interface>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>20.20.20.1</ip>
<config>
<ip>20.20.20.1</ip>
</config>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
<network-instance>
<protocols>
types">
<identifier>oc-pol-types:OSPF</identifier>
<name>100</name>
<config>
yang/policy-types">oc-pol-types:OSPF</identifier>
<name>100</name>
</config>
<ospfv2>
<global>
<config>
<log-adjacency-changes>true</log-adjacency-
changes>
<summary-route-cost-mode>RFC1583_COMPATIBLE</
summary-route-cost-mode>
</config>
<mpls>
<config>
<traffic-engineering-extensions>false</
traffic-engineering-extensions>
</config>
</mpls>

<graceful-restart>
<config>
</config>
</graceful-restart>
<timers>
<max-metric>
<config>
<set>true</set>
<include>MAX_METRIC_INCLUDE_STUB</include>
</config>
</max-metric>
<lsa-generation>
<config>
<initial-delay>100</initial-delay>
<maximum-delay>100</maximum-delay>
</config>
</lsa-generation>
<spf>
<config>
</config>
</spf>
</timers>
</global>
<areas>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
<network-type xmlns:oc-ospf-
types="http://openconfig.net/yang/ospf-types">oc-ospf-
types:POINT_TO_POINT_NETWORK</network-type>
<authentication-type>message-digest</
<metric>65535</metric>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<enable-bfd>
<config>
</config>
</enable-bfd>
<lsa-filter>

<config>
<all>true</all>
</config>
</lsa-filter>
<mpls>
<config>
<traffic-engineering-metric>1</
traffic-engineering-metric>
</config>
<igp-ldp-sync>
<config>
<post-session-up-delay>1000</
post-session-up-delay>
</config>
</igp-ldp-sync>
</mpls>
<timers>
<config>
<dead-interval>2</dead-interval>
<retransmission-interval>1</
retransmission-interval>
</config>
</timers>
</interface>
</interfaces>
</area>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth2</id>
<config>
<id>eth2</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
<virtual-links>
<virtual-link>
<remote-router-id>10.143.74.1</remote-
router-id>
<config>
<remote-router-id>10.143.74.1</remote-
router-id>
</config>
</virtual-link>
</virtual-links>
</area>
</areas>

</ospfv2>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

The below CLI command is used to create OSPF process.
router ospf 100
max-metric router-lsa include-stub
compatible rfc1583
log-adjacency-changes detail
no capability restart graceful
timers spf exp 400 4000
timers throttle lsa all 100 100 100
area 0.0.0.0 interface eth1
area 0.0.0.0 interface eth1 passive
area 0.0.0.0 interface eth1 cost 65535
area 0.0.0.0 interface eth1 network-type point-to-point
area 0.0.0.0 interface eth1 priority 255
area 0.0.0.0 interface eth1 authentication message-digest
area 0.0.0.0 interface eth1 bfd
area 0.0.0.0 interface eth1 database-filter all out
area 0.0.0.0 interface eth1 te-metric 1
area 0.0.0.0 interface eth1 mpls ldp-igp sync ospf holddown-timer 1
area 0.0.0.0 interface eth1 dead-interval 2
area 0.0.0.0 interface eth1 hello-interval 1
area 0.0.0.0 interface eth1 retransmit-interval 1
area 1.1.1.1 virtual-link 10.143.74.1
no capability traffic-engineering
no capability cspf
!
OcNOS NETCONF Payload

Here is a sample OcNOS NetConf Payload to create OSPF process.
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<config>
</config>
</ipv4>
</interface>
<interface>
<name>eth2</name>

<config>
<name>eth2</name>
</config>
<config>
</config>
</ipv4>
</interface>
</interfaces>
instance">
<network-instance>
<config>
</config>
<config>
</config>
</vrf>
<config>
</config>
</bridge>
</network-instance>
<ospfv2 xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-ospf">
<processes>
<process>
<config>
</config>
<capability>
<config>
<disable-traffic-engineering />
<disable-graceful-restart />
</config>
</capability>
<max-metric>
<config>
<enable-max-router-lsa />
<include-stub />
</config>
</max-metric>
<timers>
<lsa>
<delays>
<delay>
<start-delay>100</start-delay>
<min-delay>100</min-delay>

<max-delay>100</max-delay>
<config>
<start-delay>100</start-delay>
</config>
</delay>
</delays>
</lsa>
<spf>
<delay>
<config>
</config>
</delay>
</spf>
</timers>
<areas>
<area>
<config>
</config>
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
<passive/>
<network-type>point-to-point</network-type>
<authentication-type>message-digest</
<cost>65535</cost>
</config>
<enable-bfd>
<config>
<enabled>enable</enabled>
</config>
</enable-bfd>
<lsa-filter>
<config>
<filter-out/>
</config>
</lsa-filter>
<mpls>
<config>
<traffic-engineering-metric>1</traffic-
engineering-metric>
</config>
<igp-ldp-sync>
<config>
<ldp-igp-sync-enable/>
<holddown-timer>1</holddown-timer>
</config>
</igp-ldp-sync>

</mpls>
<timers>
<config>
<retransmission-interval>1</
retransmission-interval>
</config>
</timers>
</interface>
</interfaces>
</area>
<area>
<config>
</config>
<interfaces>
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
</interface>
</interfaces>
<virtual-links>
<virtual-link>
<remote-router-id>10.143.74.1</remote-router-id>
<config>
<remote-router-id>10.143.74.1</remote-router-
id>
</config>
</virtual-link>
</virtual-links>
</area>
</areas>
</process>
</processes>
<global>
<config>
<area-interface-config-mode/>
</config>
</global>
</ospfv2>
Validation with NETCONF get

Here is a NetConf validation response that provides detailed information about creating OSPF process.
<network-instance>
<config>
<type

</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
<name>100</name>
<ospfv2>
<global>
<config>
<summary-route-cost-mode>RFC1583_COMPATIBLE</summary-route-
cost-mode>
<log-adjacency-changes>true</log-adjacency-changes>
</config>
<mpls>
<config>
<traffic-engineering-extensions>false</traffic-
engineering-extensions>
</config>
</mpls>
<graceful-restart>
<config>
</config>
</graceful-restart>
<timers>
<lsa-generation>
<config>
</config>
</lsa-generation>
<spf>
<config>
</config>
</spf>
<max-metric>
<config>
<set>true</set>
<include
xmlns:oc-ospf-types="http://openconfig.net/yang/ospf-
types">oc-ospf-types:MAX_METRIC_INCLUDE_STUB</include>

</config>
</max-metric>
</timers>
</global>
<areas>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
<metric>65535</metric>
<network-type
ospf-types">oc-ospf-types:POINT_TO_POINT_NETWORK</network-type>
<authentication-type>message-digest</authentication-
type>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<enable-bfd>
<config>
</config>
</enable-bfd>
<lsa-filter>
<config>
<all>true</all>
</config>
</lsa-filter>
<mpls>
<config>
<traffic-engineering-metric>1</traffic-engineering-
metric>
</config>
<igp-ldp-sync>
<config>
<post-session-up-delay>1000</post-session-up-
delay>
</config>
</igp-ldp-sync>
</mpls>
<timers>
<config>
<retransmission-interval>1</retransmission-interval>

</config>
</timers>
</interface>
</interfaces>
</area>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth2</id>
<config>
<id>eth2</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
<virtual-links>
<virtual-link>
<config>
</config>
</virtual-link>
</virtual-links>
</area>
</areas>
</ospfv2>
<config>
<identifier
<name>100</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family

</config>
</table>
</tables>
</network-instance>
<network-instance>
<config>
<type
</config>
</tables>
</network-instance>
Restrictions
In OpenConfig, for path /network-instances/network-instance/protocols/protocol/ospfv2/areas/
area/interfaces/interface/mpls/igp-ldp-sync/config/post-session-up-delay, only steps of 1000
by 1000 should be configured. The values are rounded in Get operation in order to prevent broken values from being
configured and presented.

Interface Configuration OpenConfig Translation
Configure Interfaces
This XML configuration snippet is used to define and configure network interfaces.
Release

Here is the sample OpenConfig NetConf Payload for Interface Configuration.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
<description>Test desc for the interface</description>
<tpid xmlns="http://openconfig.net/yang/vlan" xmlns:oc-vlan-
types="http://openconfig.net/yang/vlan-types">oc-vlan-types:TPID_0X88A8</tpid>
</config>
<ethernet xmlns="http://openconfig.net/yang/interfaces/ethernet">
<config>
<duplex-mode>FULL</duplex-mode>
<auto-negotiate>false</auto-negotiate>
<port-speed xmlns:oc-eth="http://openconfig.net/yang/interfaces/
ethernet">oc-eth:SPEED_1GB</port-speed>
</config>
</ethernet>
<subinterfaces>
<subinterface>
<index>2</index>
<config>
<index>2</index>
<description>Test subinterface double tagged</description>
</config>
<addresses>
<address>
<ip>30.1.1.1</ip>
<config>
<ip>30.1.1.1</ip>

</config>
</address>
<address>
<ip>40.10.10.10</ip>
<config>
<ip>40.10.10.10</ip>
</config>
</address>
</addresses>
</ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI commands are used for Interface Configuration.
interface xe10
description "Test desc for the interface"
speed 1g
duplex full
mtu 1450
switchport dot1q ethertype 0x88A8
no shutdown
interface xe10.2
description "Test subinterface double tagged"
ip address 30.1.1.1/24
ip address 40.10.10.10/24 secondary
no shutdown
encapsulation dot1ad 10 inner-dot1q 200

Here is the sample OcNOS NetConf Payload for Interface Configuration.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
</config>
<extended xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-
extended">
<config>
<dot1q-ether-type>0x88A8</dot1q-ether-type>
</config>
</extended>
<ethernet xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-
ethernet">
<config>

<duplex-mode>full</duplex-mode>
<port-speed>1g</port-speed>
</config>
</ethernet>
</interface>
<interface>
<name>xe10.2</name>
<config>
<name>xe10.2</name>
<description>Test subinterface double tagged</description>
</config>
<secondary-addresses>
<ip-address>40.10.10.10/24</ip-address>
<config>
</config>
</secondary-addresses>
<config>
</config>
</ipv4>
</interface>
</interfaces>

Here is a NetConf validation response for interface configuration, providing details about the current state of the
specified interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
types="http://openconfig.net/yang/vlan-types">oc-vlan-types:TPID_0X8100</tpid>
<type
xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-
</config>
<state>
<name>xe10</name>
<mtu>1450</mtu>
<tpid xmlns="http://openconfig.net/yang/vlan-types">TPID_0X8100</
tpid>
<logical>false</logical>
<last-change>0</last-change>
<oper-status>DOWN</oper-status>
<admin-status>UP</admin-status>
<ifindex>10010</ifindex>
<counters>
<last-clear>0</last-clear>

<out-errors>0</out-errors>
<out-discards>0</out-discards>
<out-multicast-pkts>0</out-multicast-pkts>
<out-broadcast-pkts>0</out-broadcast-pkts>
<out-unicast-pkts>0</out-unicast-pkts>
<out-pkts>0</out-pkts>
<out-octets>0</out-octets>
<in-fcs-errors>0</in-fcs-errors>
<in-errors>0</in-errors>
<in-discards>0</in-discards>
<in-multicast-pkts>0</in-multicast-pkts>
<in-broadcast-pkts>0</in-broadcast-pkts>
<in-unicast-pkts>0</in-unicast-pkts>
<in-pkts>0</in-pkts>
<in-octets>0</in-octets>
</counters>
<type
</state>
<config>
<port-speed
xmlns:oc-eth="http://openconfig.net/yang/interfaces/
</config>
<state>
<port-speed
<negotiated-port-speed
ethernet">oc-eth:SPEED_1GB</negotiated-port-speed>
<negotiated-duplex-mode>FULL</negotiated-duplex-mode>
<hw-mac-address>b86a.9729.abc5</hw-mac-address>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<mtu>1450</mtu>
</config>
</ipv4>
<config>
<index>0</index>
</config>
<config>
<mtu>1450</mtu>
</config>
</ipv6>
</subinterface>

</subinterfaces>
</interface>
</interfaces>
Restrictions
The leaf mentioned below has been restricted to a maximum of 32 characters.
/interfaces/interface/name
As a general restriction, interface names must have valid OcNOS naming conventions, such as 'eth,' 'xe,'
'ce,' 'so,' 'po,' etc. This naming convention is not configurable.
Configure Description
This XML configuration snippet is used to assign a description to a given interface.
Release

Here is the sample OpenConfig NetConf Payload to configure interface description.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used for configuring interface descriptions.
interface xe10
description "Test desc for the interface"
no shutdown

Here is the sample OcNOS NetConf Payload for configuring interface descriptions.
<interface>
<name>xe10</name>
<config>

<name>xe10</name>
</config>
</interface>
</interfaces>

Here is a NetConf validation response for configuring interface descriptions, providing details about the current state of
the specified interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
tpid>
<counters>
</counters>
<type
</state>

<state>
<hw-mac-address>b86a.97c3.6447</hw-mac-address>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Configure MTU
This XML configuration snippet is used to set the Maximum Transmission Unit (MTU) for an interface.
Release

Here is the sample OpenConfig NetConf Payload to set the MTU for an interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
</config>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to set the MTU for an interface.

interface xe10
mtu 1450
no shutdown

Here is the sample OcNOS NetConf Payload to set the MTU for an interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
</config>
</interface>
</interfaces>

Here is a NetConf validation response for setting the MTU for an interface, providing details about the current state of
the specified interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<mtu>1450</mtu>
<type
</config>
<state>
<name>xe10</name>
<mtu>1450</mtu>
tpid>
<counters>

</counters>
<type
</state>
<state>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<mtu>1450</mtu>
</config>
</ipv4>
<config>
<index>0</index>
</config>
<config>
<mtu>1450</mtu>
</config>
</ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
The leaf mentioned below is used only to configure the physical interface.
/interfaces/interface/config/mtu
Configure Primary IP Address

This XML configuration snippet is used to specify that an IP address and prefix length will be used by the interface.

Release

Here is the sample OpenConfig NetConf Payload to indicate that the interface will use an IP address and a prefix
length.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>30.1.1.1</ip>
<config>
<ip>30.1.1.1</ip>
</config>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure an IP address and prefix length for an interface.
interface xe10
no shutdown

Here is a sample OcNOS NetConf Payload for assigning a primary IP address and prefix length to an interface.
<interface>
<name>xe10</name>

<config>
<name>xe10</name>
</config>
<config>
</config>
</ipv4>
</interface>
</interfaces>

Here is a NetConf validation response for assigning a primary IP address and prefix length to an interface, providing
details about the current state of the specified interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
tpid>
<counters>
</counters>
<type

</state>
<state>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>30.1.1.1</ip>
<config>
<ip>30.1.1.1</ip>
</config>
<state>
<ip>30.1.1.1</ip>
</state>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
The first entry on the below list will be used as the primary address, as OpenConfig does not have this concept.
/interfaces/interface/subinterfaces/subinterface/ipv4/addresses/address
Configure Secondary IP Address

This XML configuration snippet specifies the use of a secondary IP address and prefix length for an interface. It's
important to note that the secondary address cannot be configured if there is no primary IP address present.

Release

Here is a sample OpenConfig NetConf payload that specifies the configuration for an interface. This configuration
includes the interface type, subinterface details, and IPv4 addresses with their respective prefix lengths.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>10.10.10.1</ip>
<config>
<ip>10.10.10.1</ip>
</config>
</address>
<address>
<ip>11.11.11.1</ip>
<config>
<ip>11.11.11.1</ip>
</config>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure an interface with both a primary and a secondary IP address.
interface xe10
ip address 10.10.10.1/24
no shutdown


Here is a sample OcNOS NetConf Payload for configuring interface with both a primary and a secondary IP address.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<config>
</config>
<config>
</config>
</ipv4>
</interface>
</interfaces>

Here is a NetConf validation response providing details about the current state of the specified interface, as configured
in the OpenConfig YANG model.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
tpid>
<counters>

</counters>
<type
</state>
<state>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>10.10.10.1</ip>
<config>
<ip>10.10.10.1</ip>
</config>
<state>
<ip>10.10.10.1</ip>
</state>
</address>
<address>
<ip>11.11.11.1</ip>
<config>
<ip>11.11.11.1</ip>
</config>
<state>
<ip>11.11.11.1</ip>
</state>
</address>
</addresses>
</ipv4>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>

</interface>
</interfaces>
Restrictions
All leaves of the below list, excluding the first entry, will be treated as secondary addresses.
Configure IPv6 Addresses

This XML configuration snippet is used to set the IPv6 addresses of an interface.
Release

Here is the sample OpenConfig NetConf Payload for configuring IPv6 addresses on an interface.
<interface>
<name>xe11</name>
<config>
<name>xe11</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<addresses>
<address>
<ip>ad0f::ac0f:ab0f</ip>
<config>
<ip>ad0f::ac0f:ab0f</ip>
</config>
</address>
<address>
<ip>ae0f::ad0f:ac0f</ip>
<config>
<ip>ae0f::ad0f:ac0f</ip>
</config>
</address>
<address>
<ip>f0ca:bebe::cafe</ip>
<config>

<ip>f0ca:bebe::cafe</ip>
</config>
</address>
</addresses>
</ipv6>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure an interface with multiple IPv6 addresses and enable the interface.
interface xe11
ipv6 address ad0f::ac0f:ab0f/64
ipv6 address ae0f::ad0f:ac0f/64
ipv6 address f0ca:bebe::cafe/64
no shutdown
!

Here is a sample OcNOS NetConf Payload for configuring an interface with multiple IPv6 addresses.
<interface>
<name>xe11</name>
<config>
<name>xe11</name>
</config>
<addresses>
<ipv6-address>ad0f::ac0f:ab0f/64</ipv6-address>
<config>
<ipv6-address>ad0f::ac0f:ab0f/64</ipv6-address>
</config>
</addresses>
<addresses>
<ipv6-address>ae0f::ad0f:ac0f/64</ipv6-address>
<config>
<ipv6-address>ae0f::ad0f:ac0f/64</ipv6-address>
</config>
</addresses>
<addresses>
<ipv6-address>f0ca:bebe::cafe/64</ipv6-address>
<config>
<ipv6-address>f0ca:bebe::cafe/64</ipv6-address>
</config>
</addresses>
</ipv6>
</interface>

</interfaces>

The below NetConf validation response provides details about the current state of the specified interface configured
with multiple IPv6 addresses using OpenConfig YANG data model elements.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
tpid>
<counters>
</counters>
<type
</state>
<config>
</config>
<state>

</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Configure Duplex-mode
This XML configuration snippet is used to configure the duplex mode for an interface.
Release

Here is the sample OpenConfig NetConf Payload to configure interface with the FULL duplex mode enabled.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<config>
</config>
</ethernet>
</interface>
</interfaces>

OcNOS CLI Command

The below CLI command is used to configure an interface with full duplex mode enabled and with no shutdown.
interface xe10
duplex full
no shutdown

Here is a sample OcNOS NetConf Payload to configure interface with full duplex mode enabled and ensures that the
interface is in the enabled state.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
ethernet">
<config>
<duplex-mode>full</duplex-mode>
</config>
</ethernet>
</interface>
</interfaces>

Here is a NetConf validation response provides comprehensive information about the current state of an interface,
including its operational and administrative status, traffic counters, and Ethernet configuration details.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
<counters>

</counters>
<type
</state>
<config>
<port-speed
</config>
<state>
<port-speed
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Default
By default, the duplex mode for an interface is set to full duplex.

Configure Port-Speed
This XML configuration snippet is used to set the link speed of the interface.
Release

Here is the sample OpenConfig NetConf Payload that specifies the configuration for an interface. It sets the interface's
state to enabled (true) and defines it as an Ethernet interface (ianaift:ethernetCsmacd). Additionally, it specifies
that auto-negotiation for link speed is disabled (false) and sets the port speed for a specified Ethernet interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<config>
<port-speed xmlns:oc-eth="http://openconfig.net/yang/interfaces/
</config>
</ethernet>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure an interface for a speed of 1 gigabit and enable it.
interface xe10
speed 1g
no shutdown

Here is a sample OcNOS NetConf Payload that enables an interface and sets its speed.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
ethernet">

<config>
<port-speed>1g</port-speed>
</config>
</ethernet>
</interface>
</interfaces>

Here is a NetConf validation response to set the speed of an interface, providing details about the current state of the
specified interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
tpid>
<counters>
</counters>
<type
</state>
<state>

</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
This leaf can only be used when the auto-negotiate leaf (../auto-negotiate) is set to false.
/interfaces/interface/ethernet/config/port-speed
Configure Ethernet Type

This XML configuration snippet is used to specify the Ethernet type for an interface.
Release

Here is the sample OpenConfig NetConf Payload that sets the Ethernet Type for an interface.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<tpid xmlns="http://openconfig.net/yang/vlan" xmlns:oc-vlan-types="http://
openconfig.net/yang/vlan-types">oc-vlan-types:TPID_0X88A8</tpid>
</interface>
</interfaces>

OcNOS CLI Command

The below CLI command configures VLAN tagging with Ethernet Type on an interface and ensures that the interface is
not in shutdown mode.
interface xe10
switchport dot1q ethertype 0x88a8
no shutdown

Here is a sample OcNOS NetConf Payload that enables an interface and configures it to use a dot1q Ethernet Type
for VLAN tagging.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
extended">
<config>
<dot1q-ether-type>0x88a8</dot1q-ether-type>
</config>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response for the specified interface, providing comprehensive details about its current
state, including operational and administrative statuses, traffic counters, Ethernet configuration, and VLAN tagging
settings.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
<type
</config>
<state>
<name>xe10</name>
<tpid xmlns="http://openconfig.net/yang/vlan-types">TPID_0X88a8</
tpid>
<counters>

</counters>
<type
</state>
<state>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Configure Sub-interface with Primary and Secondary Addresses

This XML configuration snippet sets both primary and secondary IP addresses, each with its corresponding prefix
length, for use by a sub-interface.

Release

Here is the sample OpenConfig NetConf Payload for configuring sub-interface with two IPv4 addresses, each having
the specified prefix length. This payload specifies the IP addresses to be used by the sub-interface with the specified
index.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<subinterfaces>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<addresses>
<address>
<ip>20.21.22.23</ip>
<config>
<ip>20.21.22.23</ip>
</config>
</address>
<address>
<ip>24.25.26.27</ip>
<config>
<ip>24.25.26.27</ip>
</config>
</address>
</addresses>
</ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure a sub-interface with both a primary and a secondary IPv4 address.
interface xe10.10
ip address 20.21.22.23/24
!


Here is a sample OcNOS NetConf Payload for configuring a sub-interface with both a primary and a secondary IPv4
address.
<interface>
<name>xe10.10</name>
<config>
</config>
<config>
</config>
<config>
</config>
</ipv4>
</interface>
</interfaces>

Here is a NetConf validation response for configuring a sub-interface with two IPv4 addresses, each with a specified
prefix length. The response provides information about the current state of the specified sub-interface, including its
operational status, interface index, and traffic counters.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<subinterfaces>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<state>
<logical>true</logical>
<counters>
</counters>
</state>

<addresses>
<address>
<ip>20.21.22.23</ip>
<config>
<ip>20.21.22.23</ip>
</config>
<state>
<ip>20.21.22.23</ip>
</state>
</address>
<address>
<ip>24.25.26.27</ip>
<config>
<ip>24.25.26.27</ip>
</config>This configuration was introduced
<state>
<ip>24.25.26.27</ip>
</state>
</address>
</addresses>
</ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
The first entry on the below list will be used as the primary address, as OpenConfig does not have this concept.
When using OpenConfig translation, use the sub-interface name in the format <ifname>.<id>, as OpenConfig does
not support the <ifname>.<id>.<id> format, even though it is allowed by OcNOS CLI.
/interfaces/interface/subinterfaces/subinterface/index

LACP OpenConfig Translation
Create Static LAG Interface

This XML configuration snippet is used to create a static Link Aggregation Group (LAG) interface with a specified name
and configure its settings for a network device.
Release

Here is a sample OpenConfig NetConf Payload that configures two Ethernet interfaces to be part of a LAG. The LAG
uses the Link Aggregation Control Protocol (LACP) in ACTIVE mode, and it requires a minimum of two member links to
be up for the LAG to be operational. Additionally, set the system priority.
<interface>
<name>sa10</name>
<config>
<name>sa10</name>
type">ianaift:ieee8023adLag</type>
</config>
<aggregation xmlns="http://openconfig.net/yang/interfaces/aggregate">
<config>
<min-links>2</min-links>
<lag-type>STATIC</lag-type>
</config>
</aggregation>
</interface>
<interface>
<name>xe6</name>
<config>
<name>xe6</name>
</config>
<config>
<aggregate-id xmlns="http://openconfig.net/yang/interfaces/
aggregate">sa10</aggregate-id>
<lacp-mode xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-if-
deviations">ACTIVE</lacp-mode>
</config>
</ethernet>
</interface>
<interface>
<name>xe7</name>

<config>
<name>xe7</name>
</config>
<config>
</config>
</ethernet>
</interface>
</interfaces>
<lacp xmlns="http://openconfig.net/yang/lacp">
<config>
<system-priority>2</system-priority>
</config>
</lacp>
OcNOS CLI Command

The below CLI commands are used to configure a static LAG interface with a system priority and a minimum required
member link count. Ethernet interfaces are also assigned to the static LAG group with the specified identifier.
lacp system-priority 2
!
interface sa10
port-channel min-links 2
!
interface xe6
static-channel-group 10
!
interface xe7
static-channel-group 10
!

Here is a sample OcNOS NetConf Payload that configures two Ethernet interfaces to be part of a static LAG with the
specified identifier. The LAG requires a minimum of two member links to be operational and uses the LACP mode
ACTIVE. Additionally, it sets the system priority for LACP.
This payload includes configurations for both OpenConfig and OcNOS YANG models to ensure compatibility between
the two.
<interface>
<name>sa10</name>
<config>
<name>sa10</name>
</config>
<config>

</config>
</aggregation>
</interface>
<interface>
<name>xe6</name>
<config>
<name>xe6</name>
</config>
<config>
<lacp-mode xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-
if-deviations">ACTIVE</lacp-mode>
</config>
</ethernet>
</interface>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>
<config>
</config>
</ethernet>
</interface>
</interfaces>
<config>
</config>
</lacp>
<interface>
<name>sa10</name>
<config>
<name>sa10</name>
</config>
<aggregator xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-
aggregate">
<config>
</config>
</aggregator>
</interface>
<interface>
<name>xe6</name>

<config>
<name>xe6</name>
</config>
ethernet">
<config />
</ethernet>
<member-aggregation xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-
if-aggregate">
<config>
<agg-type>static</agg-type>
<aggregate-id>10</aggregate-id>
<lacp-mode>active</lacp-mode>
</config>
</member-aggregation>
</interface>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>
ethernet">
<config />
</ethernet>
if-aggregate">
<config>
<agg-type>static</agg-type>
</config>
</interface>
</interfaces>
<lacp xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-lacp">
<global>
<config>
</config>
</global>
</lacp>

Here is a NetConf validation response defines three interfaces, including a static LAG type that requires a minimum
of two member links and has an operational status of UP. Both of the Ethernet interfaces are part of this LAG, and they
also have UP operational status. The LAG uses LACP in ACTIVE mode, and it sets the system priority for LACP.
<interface>
<name>sa10</name>
<config>
<name>sa10</name>
<type

</config>
<state>
<name>sa10</name>
<oper-status>UP</oper-status>
<counters>
</counters>
<type
</state>
<state>
ethernet">oc-eth:SPEED_UNKNOWN</negotiated-port-speed>
<hw-mac-address>b86a.9729.abf2</hw-mac-address>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
<config>
</config>
<state>
</state>
</aggregation>

</interface>
</interfaces>
<interface>
<name>xe6</name>
<config>
<name>xe6</name>
<type
</config>
<state>
<name>xe6</name>
<counters>
</counters>
<type
</state>
<state>
</state>
<config>
</config>
</ethernet>
<subinterfaces>

<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
<type
</config>
<state>
<name>xe7</name>
<counters>
</counters>
<type
</state>
<state>
</state>

<config>
</config>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
<global>
<config>
</config>
<state>
<system-id>b8-6a-97-82-11-ba</system-id>
</state>
</global>
</lacp>
Restrictions
The interface name for a static LAG interface should begin with the text sa, followed by a number, such as sa3.
The data type of the below leaf has been modified to uint8.
/interfaces/interface/aggregation/config/min-links
The below leaf was not in a supported state.
/lacp/interfaces/interface/config/lacp-mode
Create Dynamic LAG Interface

This XML configuration snippet is used to create a dynamic Link Aggregation Group (LAG) interface with a specified
name and configure its settings for a network device.
Release


Here is a sample OpenConfig NetConf Payload that configures an Ethernet interfaces to be a part of a LAG with a
specified identifier. The LAG uses the LACP in ACTIVE mode, and it requires a minimum of two member links to be
operational. Additionally, it sets the system priority for LACP.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<ethernet xmlns="http://openconfig.net/yang/interfaces/ethernet">/oc-
if:interfaces/oc-if:interface/oc-if:config/oc-if:name
<config>
aggregate">po2</aggregate-id>
</config>
</ethernet>
</interface>
<interface>
<name>po2</name>
<config>
<name>po2</name>
</config>
<config>
<lag-type>LACP</lag-type>
</config>
</aggregation>
</interface>
</interfaces>
<config>
</config>
<interfaces>
<interface>
<name>xe10</name>
</interface>
</interfaces>
</lacp>
OcNOS CLI Command

The below CLI commands are used to configure a dynamic LAG interface with a system priority and a minimum
required member link count. Ethernet interface is also assigned to the dynamic LAG group with the specified identifier
and sets the LACP mode as ACTIVE.
lacp system-priority 2

!
interface po2
port-channel min-links 2
!
interface xe10
channel-group 2 mode active
!

Here is a sample OcNOS NetConf Payload that configures a dynamic LAG interface with a minimum required member
link count and assigns an Ethernet interface to the LAG group with LACP mode ACTIVE. Additionally, it sets the
system priority for LACP.
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
if-aggregate">
<config>
<agg-type>lacp</agg-type>
</config>
</interface>
<interface>
<name>po2</name>
<config>
<name>po2</name>
</config>
<aggregator xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-
aggregate">
<config>
</config>
</aggregator>
</interface>
</interfaces>
<global>
<config>
</config>
</global>
</lacp>

Here is a NetConf validation response provides detailed information about the dynamic LAG interface status and
configuration, which includes dynamic link aggregation using LACP, minimum member link requirements, operational
status, and system priority settings.

<rpc-reply xmlns="urn:ietf:params:xml:ns:NETCONF:base:1.0">
<data>
<interface>
<name>po2</name>
<config>
<name>po2</name>
<type
</config>
<state>
<name>po2</name>
<counters>
</counters>
<type
</state>
<state>
<negotiated-duplex-mode>HALF</negotiated-duplex-mode>
<hw-mac-address>b86a.9729.abf2</hw-mac-address>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>

<config>
</config>
<state>
</state>
</aggregation>
</interface>
</interfaces>
</data>
</rpc-reply>
Restrictions
The interface name for a dynamic LAG interface should begin with the text po, followed by a number, such as po2.
The data type of the below leaf has been modified to uint8.
/interfaces/interface/aggregation/config/min-links
The below leaf was not in a supported state.
/lacp/interfaces/interface/config/lacp-mode

Tunnel Interfaces OpenConfig Translation
Create Tunnel Interface

This XML configuration snippet is used to specify the configuration for an OpenConfig interface with a tunnel type,
source and destination IP addresses.
Release

Here is the sample OpenConfig NetConf Payload configures an OpenConfig interface as a tunnel type with specific
source and destination IP addresses and Time to Live (TTL) settings.
<interface>
<name>Tunnel30</name>
<config>
type">ianaift:tunnel</type>
</config>
<tunnel xmlns="http://openconfig.net/yang/interfaces/tunnel">
<ipv4>
<addresses>
<address>
<ip>40.1.1.1</ip>
<config>
<ip>40.1.1.1</ip>
</config>
</address>
</addresses>
</ipv4>
<config>
<src>20.2.2.1</src>
<dst>20.2.2.2</dst>
<ttl>250</ttl>
</config>
</tunnel>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure an interface with an IP address, a tunnel source and destination
addresses, and a tunnel TTL value.

interface Tunnel30
tunnel source 20.2.2.1
tunnel destination 20.2.2.2
tunnel ttl 250

Here is a sample OcNOS NetConf Payload that configures a Tunnel Interface with the specified source and destination
addresses, and a TTL value. It also includes a secondary IPv4 address for the interface.
<interface>
<config>
</config>
<tunnel xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-
extended">
<config>
<src>20.2.2.1</src>
<dst>20.2.2.2</dst>
<ttl>250</ttl>
</config>
</tunnel>
<config>
</config>
</ipv4>
</interface>
</interfaces>

Here is a NetConf validation response provides an information about the configuration and status of the Tunnel
Interface.
<interface>
<config>
<type
</config>
<state>

<type
</state>
<state>
<negotiated-duplex-mode>HALF</negotiated-duplex-mode>
<hw-mac-address>0000.0000.0000</hw-mac-address>
</state>
</ethernet>
<tunnel xmlns="http://openconfig.net/yang/interfaces/tunnel">
<ipv4>
<addresses>
<address>
<ip>40.1.1.1</ip>
<config>
<ip>40.1.1.1</ip>
</config>
<state>
<ip>40.1.1.1</ip>
</state>
</address>
</addresses>
</ipv4>
<config>
<src>20.2.2.1</src>
<dst>20.2.2.2</dst>
<ttl>250</ttl>
</config>
<state>
<src>20.2.2.1</src>
<dst>20.2.2.2</dst>
<ttl>250</ttl>
</state>
</tunnel>
</interface>
</interfaces>
Restrictions
Tunnel interfaces must begin with Tunnel followed by a numerical value, such as Tunnel30.
The tunnel configuration parameters src and dst do not have support for IPv6.
/interfaces/interface/tunnel/config/dst
/interfaces/interface/tunnel/config/src
The data type of the ttl leaf has been updated from uint8 to uint16.
/interfaces/interface/tunnel/config/ttl
The primary IP address is determined by the first configured address, and it is not possible to delete the primary
address without removing the other addresses.

/interfaces/interface/tunnel/ipv4/addresses/address/config/ip

Static Route OpenConfig Translation
Create a static route

This XML configuration snippet is used to specify the destination prefix and mask for the network and create a gateway
statically.
Release

Here is a sample OpenConfig NetConf Payload to specify the destination prefix and mask for the network and create a
gateway statically.
<network-instance>
<config>
</config>
<protocols>
<protocol>
<config>
</config>
</protocol>
<protocol>
policy-types">oc-pol-types:STATIC</identifier>
<name>static-routes</name>
<config>
yang/policy-types">oc-pol-types:STATIC</identifier>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<next-hops>
<next-hop>

<index>172.17.30.2</index>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.30.2</index>
<next-hop>172.17.30.2</next-hop>
</config>
</next-hop>
</next-hops>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
</static>
</static-routes>
</protocol>
</protocols>
<tables>
<table>
<config>
</config>
</table>
<table>
<config>
</config>
</table>
<table>
policy-types">oc-pol-types:STATIC</protocol>
<config>
</config>
</table>
</tables>
<interfaces>

<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
</interfaces>
</network-instance>
OcNOS CLI Command

This CLI command is used to specify the destination prefix and mask for the network and create a gateway statically.
interface xe2
ip vrf forwarding TEST_A9
!
ip route vrf TEST_A9 192.168.0.0/24 172.17.30.2 xe2 10

Here is a sample OcNOS NetConf Payload to specify the destination prefix and mask for the network and create a
gateway statically.
instance">
<network-instance>
<config>
</config>
<config>
</config>
<static-routes xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-
rib-vrf">
<ipv4>
<route>
<destination-prefix>192.168.0.0/24</destination-
prefix>
<gateway-address>172.17.30.2</gateway-address>
<gateway-interface-route>
<interface-name>xe2</interface-name>
<config>
</config>
</gateway-interface-route>
<config>
prefix>
</config>

</route>
</ipv4>
</static-routes>
</vrf>
</network-instance>
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about destination prefix and mask for the
network and create a gateway statically.
<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
pol-types:STATIC</identifier>
<config>
<identifier

types">oc-pol-types:STATIC</identifier>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<next-hops>
<next-hop>
<index>172.17.30.2</index>
<interface-ref>
<config>
</config>
<state>
</state>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.30.2</index>
</config>
<state>
<metric>10</metric>
<index>172.17.30.2</index>
</state>
</next-hop>
</next-hops>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
<state>
<prefix>192.168.0.0/24</prefix>
</state>
</static>
</static-routes>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
types">oc-pol-types:DIRECTLY_CONNECTED</protocol>
<address-family
</config>
</table>
<table>

<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
pol-types:STATIC</protocol>
<address-family
<config>
<protocol
types">oc-pol-types:STATIC</protocol>
<address-family
</config>
</table>
</tables>
<interfaces>
<interface>
<id>lo.TEST_A9</id>
<config>
<interface>lo.TEST_A9</interface>
<id>lo.TEST_A9</id>
</config>
</interface>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
</interfaces>
</network-instance>
Restrictions
/network-instances/network-instance/protocols/protocol/static-routes/static/next-hops/
next-hop
It is necessary to have at least one entry in this list of next hops

next-hop/index
Whenever config/next-hop leaf is configured, the index must have the same value as the next-hop. If not, the
index must match the interface name built from interface-ref/config/interface and interface-ref/config/subinterface. For
example xe1”, “xe2.100” and so on.
Create a Static Route with Load Balancing

This XML configuration snippet is used to create two paths to a specified destination prefix and mask for the network
and a gateway working in load balancing scenario. With these two links, it is possible to guarantee the service
availability. All traffic should be routed throughout both links at the same time and if any of them has a failure, all traffic
must be routed through the available link.
Release

Here is a sample OpenConfig NetConf Payload to create a static route with load balancing.
<network-instance>
<config>
</config>
<protocols>
<protocol>
<config>
</config>
</protocol>
<protocol>
policy-types">oc-pol-types:STATIC</identifier>
<config>
yang/policy-types">oc-pol-types:STATIC</identifier>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<next-hops>

<next-hop>
<index>172.17.30.2</index>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.30.2</index>
</config>
</next-hop>
<next-hop>
<index>172.17.31.2</index>
<interface-ref>
<config>
</config>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.31.2</index>
</config>
</next-hop>
</next-hops>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
</static>
</static-routes>
</protocol>
</protocols>
<tables>
<table>
<config>
</config>
</table>
<table>
<config>
</config>

</table>
<table>
<config>
</config>
</table>
</tables>
<interfaces>
<interface>
<id>xe1</id>
<config>
<id>xe1</id>
</config>
</interface>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
</interfaces>
</network-instance>
OcNOS CLI Command

This CLI command is used to create a static route with load balancing.
interface xe1
!
interface xe2
!

Here is a sample OcNOS NetConf Payload to create a static route with load balancing.
instance">
<network-instance>
<config>

</config>
<config>
</config>
rib-vrf">
<ipv4>
<route>
prefix>
<config>
</config>
<config>
prefix>
</config>
</route>
<route>
prefix>
<config>
</config>
<config>
prefix>
</config>
</route>
</ipv4>
</static-routes>
</vrf>
</network-instance>

Here is a NetConf validation response that provides detailed information about creating a static route with load
balancing.
<network-instance>

<config>
<type xmlns:oc-ni-types="http://openconfig.net/yang/network-instance-
</config>
<state>
</state>
<protocols>
types">
<identifier>oc-pol-types:DIRECTLY_CONNECTED</identifier>
<config>
</config>
</protocol>
types">
<identifier>oc-pol-types:STATIC</identifier>
<config>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<next-hops>
<next-hop>
<index>172.17.30.2</index>
<interface-ref>
<config>
</config>
<state>
</state>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.30.2</index>
</config>
<state>
<metric>10</metric>
<index>172.17.30.2</index>
</state>
</next-hop>
<next-hop>
<index>172.17.31.2</index>
<interface-ref>

<config>
</config>
<state>
</state>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.31.2</index>
</config>
<state>
<metric>10</metric>
<index>172.17.31.2</index>
</state>
</next-hop>
</next-hops>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
<state>
<prefix>192.168.0.0/24</prefix>
<prefix>192.168.0.0/24</prefix>
</state>
</static>
</static-routes>
</protocol>
</protocols>
<tables xmlns:oc-types="http://openconfig.net/yang/openconfig-types">
<table xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">
<protocol>oc-pol-types:DIRECTLY_CONNECTED</protocol>
<address-family>oc-types:IPV4</address-family>
<config>
</config>
</table>
<config>
</config>
</table>
<protocol>oc-pol-types:STATIC</protocol>
<config>
</config>
</table>
</tables>
<interfaces>

<interface>
<id>lo.TEST_A9</id>
<config>
<id>lo.TEST_A9</id>
</config>
</interface>
<interface>
<id>xe1</id>
<config>
<id>xe1</id>
</config>
</interface>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
</interfaces>
</network-instance>
Restrictions
next-hop
It is necessary to have at least one entry in this list of next hops
next-hop/index
Whenever config/next-hop leaf is configured, the index must have the same value as the next-hop. If not, the index
must match the interface name built from interface-ref/config/interface and interface-ref/config/subinterface. For
example, “xe1”, “xe2.100” and so on.
Create a Static Route with Active/Standby

This XML configuration snippet is used to create two paths to a specified destination prefix and mask for the network
and a gateway working in active/standby scenario. With these two links, it is possible to guarantee the service
availability. All the traffic must be routed throughout the active link while the passive link must be configured to receive
the traffic in case of any failure in the active link.
Release

Here is a sample OpenConfig NetConf Payload to create a static route with active/standby.


<network-instance>
<config>
<type>L3VRF</type>
</config>
<interfaces>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
<interface>
<id>xe4</id>
<config>
<id>xe4</id>
</config>
</interface>
</interfaces>
<protocols>
<protocol>
<identifier>STATIC</identifier>
<name>static-route</name>
<config>
<identifier>STATIC</identifier>
<name>static-route</name>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
<next-hops>
<next-hop>
<index>172.17.30.2</index>
<config>
<index>172.17.30.2</index>
<metric>10</metric>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</next-hop>
<next-hop>
<index>172.17.40.2</index>
<config>
<index>172.17.40.2</index>

<metric>30</metric>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</next-hop>
</next-hops>
</static>
</static-routes>
</protocol>
</protocols>
</network-instance>
OcNOS CLI Command

This CLI command is used to create a static route with active/standby.
interface xe2
!
interface xe4
!
!

Here is a sample OcNOS NetConf Payload to create a static route with active/standby.
<network-instances xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-
network-instance">
<network-instance>
<config>
</config>
<config>
</config>
rib-vrf">
<ipv4>
<route>
<destination-prefix>192.168.0.0/24</destination-prefix>
<config>

</config>
<config>
</config>
</route>
<route>
<config>
</config>
<config>
</config>
</route>
</ipv4>
</static-routes>
</vrf>
</network-instance>
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
</interface>
<interface>
<name>xe4</name>
<config>
<name>xe4</name>
</config>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about creating a static route with active/
standby.
<network-instance>
<config>

</config>
<state>
</state>
<protocols>
types">
<config>
</config>
</protocol>
types">
<config>
</config>
<static-routes>
<static>
<prefix>192.168.0.0/24</prefix>
<next-hops>
<next-hop>
<index>172.17.30.2</index>
<interface-ref>
<config>
</config>
<state>
</state>
</interface-ref>
<config>
<metric>10</metric>
<index>172.17.30.2</index>
</config>
<state>
<metric>10</metric>
<index>172.17.30.2</index>
</state>
</next-hop>
<next-hop>
<index>172.17.40.2</index>
<interface-ref>
<config>

</config>
<state>
</state>
</interface-ref>
<config>
<metric>30</metric>
<index>172.17.40.2</index>
</config>
<state>
<metric>30</metric>
<index>172.17.40.2</index>
</state>
</next-hop>
</next-hops>
<config>
<prefix>192.168.0.0/24</prefix>
</config>
<state>
<prefix>192.168.0.0/24</prefix>
<prefix>192.168.0.0/24</prefix>
</state>
</static>
</static-routes>
</protocol>
</protocols>
<tables xmlns:oc-types="http://openconfig.net/yang/openconfig-types">
<config>
</config>
</table>
<config>
</config>
</table>
<config>
</config>
</table>
</tables>
<interfaces>
<interface>
<id>lo.TEST_A8</id>

<config>
<id>lo.TEST_A8</id>
</config>
</interface>
<interface>
<id>xe2</id>
<config>
<id>xe2</id>
</config>
</interface>
<interface>
<id>xe4</id>
<config>
<id>xe4</id>
</config>
</interface>
</interfaces>
</network-instance>
Restrictions
next-hop
It is necessary to have at least one entry in this list of next hops.
next-hop/index
Whenever config/next-hop leaf is configured, the index must have the same value as the next-hop. If not, the index
must match the interface name built from interface-ref/config/interface and interface-ref/config/subinterface. For
example, “xe1”, “xe2.100” and so on.
Use Cases
In this chapter, there are scenarios that can be accomplished using OpenConfig configuration XML files, showing
complex interactions between different objects.

Platform OpenConfig Translation
Description
The read-only state attributes listed here are valid for the platform Edgecore 5912-54X-O-AC-F.
FAN
This platform type displays the fan status of the boards.
OpenConfig Filter
Here is the OpenConfig filter for the get operation that results in the Get OpenConfig Return output shown below.
<component>
<state>
<type>oc-platform-types:FAN</type>
</state>
<fan></fan>
</component>
</components>
</filter>

Here is a NetConf validation response that provides detailed information on the configuration and runtime.
<component xmlns:oc-opt-types="http://openconfig.net/yang/transport-
types">
<name>FAN-1/1</name>
types">
<id>FAN-1/1</id>
<parent>FAN_TRAY-1</parent>
www.ipinfusion.com/yang/ocnos/ipi-oc-platform-types-deviations">ipi-oc-
platform-types-deviations:NA</oper-status>

types:FAN</type>
</state>
<fan>
<state>
<speed xmlns="http://openconfig.net/yang/platform/fan">9800</speed>
</state>
</fan>
</component>
types">
types">
<id>FAN-1/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-2/1</id>

types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-2/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-3/1</id>

types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-3/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-4/1</id>

types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-4/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-5/1</id>

types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-5/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-6/1</id>

types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
types">
types">
<id>FAN-6/2</id>
types:FAN</type>
</state>
<fan>
<state>
</state>
</fan>
</component>
Get OcNOS Result

Here is the NetConf response in IPI datamodel representation.
<components xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<component>
<state>
<product-name>NA</product-name>

<oper-status>NA</oper-status>
<type>fan</type>
</state>
<fan>
<state>
<fan-location>front</fan-location>
<fan-status>running</fan-status>
<maximum-rpm>21500</maximum-rpm>
<minimum-rpm>10000</minimum-rpm>
<rpm>9800</rpm>
<fan-index>1</fan-index>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<fan-location>rear</fan-location>
<rpm>8300</rpm>
</state>
</fan>
</component>
<component>
<state>

<type>fan</type>
</state>
<fan>
<state>
<rpm>10400</rpm>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>8700</rpm>
</state>
</fan>
</component>
<component>
<state>

<type>fan</type>
</state>
<fan>
<state>
<rpm>10300</rpm>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>8700</rpm>
</state>
</fan>
</component>
<component>
<state>

<type>fan</type>
</state>
<fan>
<state>
<rpm>10200</rpm>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>8600</rpm>
</state>
</fan>
</component>
<component>

<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>10000</rpm>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>8400</rpm>
</state>
</fan>
</component>
<component>

<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>10100</rpm>
</state>
</fan>
</component>
<component>
<state>
<type>fan</type>
</state>
<fan>
<state>
<rpm>8500</rpm>
</state>
</fan>
</component>

Show command
Here is Show command output that displays the hardware information for the fan.
OcNOS#show hardware-information fan
Codes : R - Rear Fan, F - Front Fan, U - Unknown

----------------------------------------------------------
FAN TRAY FAN RPM MINRPM MAXRPM
----------------------------------------------------------
1 1(F) 9800 10000 21500
1 2(R) 8300 8500 18000
2 1(F) 10400 10000 21500
2 2(R) 8700 8500 18000
3 1(F) 10300 10000 21500
3 2(R) 8700 8500 18000
4 1(F) 10100 10000 21500
4 2(R) 8600 8500 18000
5 1(F) 10000 10000 21500
5 2(R) 8400 8500 18000
6 1(F) 10100 10000 21500
6 2(R) 8500 8500 18000
RAM
This platform type displays the memory information of the boards.
OpenConfig Filter
<component>
<name>RAM</name>
</component>
</components>
</filter>

types">
<name>RAM</name>
types">
<id>RAM</id>
<name>RAM</name>

platform-types-deviations:RAM</type>
<memory>
<utilized>1118830592</utilized>
<available>16792944640</available>
</memory>
</state>
</component>
</components>
OcNOS get result

<component>
<name>RAM</name>
<state>
<name>RAM</name>
<type>ram</type>
<memory>
</memory>
</state>
<ram>
<state>
<usage-alert-threshold>90</usage-alert-threshold>
<usage-critical-threshold>80</usage-critical-threshold>
<unit-size>1</unit-size>
<available-high-memory>0</available-high-memory>
<total-high-memory>0</total-high-memory>
<current-process-count>214</current-process-count>
<free-swap>0</free-swap>
<total-swap>0</total-swap>

<buffers>18</buffers>
<shared-memory>8</shared-memory>
<available-memory>14948</available-memory>
<used-memory>1066</used-memory>
<total-memory>16015</total-memory>
</state>
</ram>
</component>
</components>
Show command
Here is Show command output that displays the hardware information for the RAM.
OcNOS#show hardware-information memory
-------------------------------------------------------
RAM INFORMATION
-------------------------------------------------------
Total : 16015 MB
Used : 1067 MB (7 %)
Free : 14947 MB (93 %)
Shared : 8 MB
Buffers : 17 MB
Total Swap : 0 MB
Free Swap : 0 MB
Current Processes : 217
Total High Memory : 0 MB
Available High Memory : 0 MB
Unit Size : 1 Bytes
Alert Threshold : 90 %
Critical Threshold : 80 %
-------------------------------------------------------
HARD DISK INFORMATION
-------------------------------------------------------
Serial Number : F929740043

Model Number : TS32GMSA370
Firmware Revision : P1225CH1TS32GMSA370
Cylinders : 16383
Heads : 16
Sectors : 62533296
Unformatted Bytes/Track : 0
Unformatted Bytes/Sector : 0
Revision No : 1008.0
Usage Alert Threshold : 90 %
Usage Critical Threshold : 80 %
----------------------------------------------------------
Filesystem Total Used Free Use%
----------------------------------------------------------
/ 22000 6446 15554 29%
/cfg 476 90 386 19%
/installers 4911 282 4629 6%
----------------------------------------------------------

Hard-disk
This platform type displays hard-disk information of the boards.
OpenConfig Filter
<component>
<name>HARD-DISK</name>
</component>
</components>
</filter>

types">
types">
<id>HARD-DISK</id>
platform-types-deviations:STORAGE</type>
<memory>
</memory>
</state>
</component>
</components>
OcNOS get result


<component>
<state>
<type>storage</type>
<memory>
</memory>
</state>
<storage>
<state>
<usage-alert-threshold>90</usage-alert-threshold>
<usage-critical-threshold>80</usage-critical-threshold>
<free-memory>15554</free-memory>
<used-memory>6446</used-memory>
<total-memory>22000</total-memory>
<revision-number>1008.0</revision-number>
<unformatted-bytes-or-sector>0</unformatted-bytes-or-sector>
<unformatted-bytes-or-track>0</unformatted-bytes-or-track>
<sector-count>62533296</sector-count>
<head-count>16</head-count>
<cylinder-count>16383</cylinder-count>
<firmware-revision>P1225CH1TS32GMSA370 </firmware-
revision>
<model-number>TS32GMSA370 </model-number>
<serial-number>F929740043 </serial-number>
</state>
<mounted-filesystems>
<mounted-filesystem>
<mount-point>/</mount-point>
<state>
<mount-point>/</mount-point>
<usage>29</usage>
<free>15554</free>
<used>6446</used>
<total>22000</total>
</state>
</mounted-filesystem>
<mount-point>/cfg</mount-point>
<state>
<mount-point>/cfg</mount-point>
<usage>19</usage>

<free>386</free>
<used>90</used>
<total>476</total>
</state>
<mount-point>/installers</mount-point>
<state>
<mount-point>/installers</mount-point>
<usage>6</usage>
<free>4629</free>
<used>282</used>
<total>4911</total>
</state>
</mounted-filesystems>
</storage>
</component>
</components>
Show command
Here is Show command output that displays the hardware information of the hard-disk.
OcNOS#show hardware-information memory
-------------------------------------------------------
RAM INFORMATION
-------------------------------------------------------
Total : 16015 MB
Used : 1067 MB (7 %)
Free : 14947 MB (93 %)
Shared : 8 MB
Buffers : 17 MB
Total Swap : 0 MB
Free Swap : 0 MB
Current Processes : 217
Total High Memory : 0 MB
Available High Memory : 0 MB
Unit Size : 1 Bytes
Alert Threshold : 90 %
Critical Threshold : 80 %
-------------------------------------------------------
HARD DISK INFORMATION
-------------------------------------------------------
Serial Number : F929740043

Model Number : TS32GMSA370
Firmware Revision : P1225CH1TS32GMSA370
Cylinders : 16383
Heads : 16
Sectors : 62533296
Unformatted Bytes/Track : 0
Unformatted Bytes/Sector : 0
Revision No : 1008.0
Usage Alert Threshold : 90 %
Usage Critical Threshold : 80 %

----------------------------------------------------------
Filesystem Total Used Free Use%
----------------------------------------------------------
/ 22000 6446 15554 29%
/cfg 476 90 386 19%
/installers 4911 282 4629 6%
----------------------------------------------------------
PSU
This platform type displays Power Supply Unit (PSU) information.
OpenConfig Filter
<component>
<state>
<type>oc-platform-types:POWER_SUPPLY</type>
</state>
<power-supply/>
</component>
</components>
</filter>

types">
<name>PSU-1</name>
types">
<id>PSU-1</id>
<name>PSU-1</name>
<part-no>YM-2651Y</part-no>
<serial-no>TA100V582031000097</serial-no>
<mfg-name>3Y POWER</mfg-name>
types:POWER_SUPPLY</type>

</state>
<power-supply>
<state>
<output-current xmlns="http://openconfig.net/yang/platform/
psu">8.88</output-current>
<output-voltage xmlns="http://openconfig.net/yang/platform/
psu">11.81</output-voltage>
<output-power xmlns="http://openconfig.net/yang/platform/
psu">104.00</output-power>
<enabled xmlns="http://openconfig.net/yang/platform/psu">true</
enabled>
</state>
</power-supply>
</component>
types">
<name>PSU-2</name>
types">
<id>PSU-2</id>
<name>PSU-2</name>
types:POWER_SUPPLY</type>
</state>
<power-supply>
<state>
<enabled xmlns="http://openconfig.net/yang/platform/psu">false</
enabled>
</state>
</power-supply>
</component>
</components>
OcNOS get result

<component>
<name>PSU-1</name>
<state>
<name>PSU-1</name>

<part-no>YM-2651Y</part-no>
<serial-no>TA100V582031000097</serial-no>
<mfg-name>3Y POWER</mfg-name>
<type>power-supply</type>
</state>
<power-supply>
<state>
<supported-parameters>volt-in volt-out curr-in curr-out power-in
power-out temp-1 temp-2 fan-1 fan-2</supported-parameters>
<output-power-status>good</output-power-status>
<input-power-status>good</input-power-status>
<fan1-rpm>26688</fan1-rpm>
<temperature-sensor2>31.00</temperature-sensor2>
<output-current>8.88</output-current>
<output-voltage>11.81</output-voltage>
<power-consumption>105.00</power-consumption>
<hot-swap-state>unknown</hot-swap-state>
<operational-status>running</operational-status>
</state>
</power-supply>
</component>
<component>
<name>PSU-2</name>
<state>
<name>PSU-2</name>
<type>power-supply</type>
</state>
<power-supply>
<state>
<supported-parameters>volt-in volt-out curr-in curr-out power-in
power-out temp-1 temp-2 fan-1 fan-2</supported-parameters>
<output-power-status>fail</output-power-status>
<input-power-status>fail</input-power-status>
<hot-swap-state>unknown</hot-swap-state>
<operational-status>faulty</operational-status>

</state>
</power-supply>
</component>
<component>
<name>POWER-RAIL</name>
<state>
<name>POWER-RAIL</name>
<type>power-rail</type>
</state>
<power-rail>
<state>
<power-supply-2-ac-alert-power-rail>fail</power-supply-2-ac-alert-
power-rail>
<power-supply-1-ac-alert-power-rail>good</power-supply-1-ac-alert-
power-rail>
<power-supply-2-v12-power-rail>fail</power-supply-2-v12-power-rail>
<power-supply-1-v12-power-rail>good</power-supply-1-v12-power-rail>
</state>
</power-rail>
</component>
</components>
Show command
Here is Show command output that displays the hardware information for the power supply unit.
OcNOS#show hardware-information power
-----------------------------------------------------
System Power Information
-----------------------------------------------------
CMM_PS1_12V_PG : GOOD
CMM_PS2_12V_PG : FAIL
CMM_PS1_AC_ALERT : GOOD
CMM_PS2_AC_ALERT : FAIL
Codes: * Not Supported by device NA Not Applicable
PSU VOLT-IN VOLT-OUT CURR-IN CURR-OUT PWR-IN PWR-OUT

TEMP-1 TEMP-2 FAN-1 FAN-2 PWR_OUT_MAX
(Volt) (Volt) (Ampere) (Ampere) (Watt) (Watt)
(Celsius) (Celsius) (Rpm) (Rpm)

------------------------------------------------------------------------------
-----------------------------------------------------
1 NA 11.82 NA 8.80 NA 104.00
27.00 31.00 26688 NA* NA*
Temperature
This platform type displays temperature sensor information of the boards.
OpenConfig Filter
<component>
<state>
<temperature/>
</state>
</component>
</components>
</filter>
Get OpenConfig return

types">
<name>TEMPERATURE-SENSOR1</name>
types">
<id>TEMPERATURE-SENSOR1</id>
<temperature xmlns="http://openconfig.net/yang/platform">
<alarm-severity>oc-alarm-types:UNKNOWN</alarm-severity>
<alarm-threshold>0</alarm-threshold>
<interval xmlns:oc-types="http://openconfig.net/yang/openconfig-
types">60000000000</interval>
<avg xmlns:oc-platform-types="http://openconfig.net/yang/platform-
types">29.98</avg>
<max xmlns:oc-platform-types="http://openconfig.net/yang/platform-
types">30.00</max>
<min xmlns:oc-platform-types="http://openconfig.net/yang/platform-
types">29.00</min>
<instant xmlns:oc-platform-types="http://openconfig.net/yang/
platform-types">30.00</instant>
</temperature>
</state>
</component>
types">

types">
types">28.98</avg>
types">29.00</max>
types">28.00</min>
</temperature>
</state>
</component>
types">
types">
types">28.07</avg>
types">29.00</max>
types">28.00</min>
</temperature>
</state>
</component>
types">
<name>TEMPERATURE-BCM Chip</name>
types">
<id>TEMPERATURE-BCM Chip</id>
types">48.49</avg>

types">49.60</max>
types">45.70</min>
</temperature>
</state>
</component>
</components>
OcNOS get result

<component>
<state>
<temperature>
<maximum-critical-temperature>60.00</maximum-critical-temperature>
<minimum-critical-temperature>10.00</minimum-critical-temperature>
<maximum-alert-temperature>65.00</maximum-alert-temperature>
<minimum-alert-temperature>5.00</minimum-alert-temperature>
<maximum-emergency-temperature>70.00</maximum-emergency-temperature>
<minimum-emergency-temperature>0.00</minimum-emergency-temperature>
<alarm-severity>indeterminate</alarm-severity>
<alarm-threshold>0.00</alarm-threshold>
<sensor-index>0</sensor-index>
<sensor-name>TEMPERATURE-SENSOR1</sensor-name>
<interval>60</interval>
<avg>29.98</avg>
<max>30.00</max>
<min>29.00</min>
</temperature>
</state>
</component>
<component>
<state>
<temperature>

<avg>28.98</avg>
<max>29.00</max>
<min>28.00</min>
</temperature>
</state>
</component>
<component>
<state>
<temperature>
<avg>28.07</avg>
<max>29.00</max>
<min>28.00</min>
</temperature>
</state>
</component>
<component>
<state>
<temperature>
<sensor-name>TEMPERATURE-BCM Chip</sensor-name>
<avg>48.49</avg>
<max>49.60</max>
<min>45.70</min>
</temperature>
</state>
</component>
</components>

Show command
Here is Show command output that displays the hardware information for Temperature.
OcNOS#show hardware-information temperature
Board Temp Sensors Temperature in Degree C

------------------------------------------------------------------------------
------------------------
SENSOR TYPE CURR EMER ALRT CRIT CRIT ALRT EMER MIN-
TEMP MAX-TEMP AVG-TEMP
TEMP MIN MIN MIN MAX MAX MAX
(Monitored since 00 hour,59 min)
------------------------------------------------------------------------------
------------------------
SENSOR1 30.00 0 5 10 60 65 70 29.00
30.00 29.98
SENSOR2 29.00 0 5 10 60 65 70 28.00
29.00 28.98
SENSOR3 28.00 0 5 10 60 65 70 28.00
29.00 28.07
BCM Chip 48.10 0 10 14 75 80 95 45.70
49.60 48.48
BCM Chip Internal Temperature

------------------------------------------
TEMP MONITOR CURRENT TEMP PEAK TEMP
(Degree C) (Degree C)
------------------------------------------
1 48.10 49.10
2 48.10 50.10
3 42.70 45.20
4 47.70 50.60
Transceiver
This platform type displays transceiver presence status and the supported list of transceivers.
OpenConfig Filter
<component>
<state>
<type>oc-platform-types:TRANSCEIVER</type>
</state>
<transceiver/>
</component>
</components>
</filter>

Get OpenConfig return

types">
<name>SFP-1</name>
types">
<id>SFP-1</id>
<name>SFP-1</name>
<parent>PORT-xe1</parent>
types:TRANSCEIVER</type>
</state>
<state xmlns:ipi-oc-transport-types-deviations="http://
www.ipinfusion.com/yang/ocnos/ipi-oc-transport-types-deviations">
<date-code>150908</date-code>
<serial-no>CN0V250M58V91KC </serial-no>
<vendor-rev>C </vendor-rev>
<vendor-part>616740001 </vendor-part>
<vendor>Amphenol </vendor>
<connector-type>ipi-oc-transport-types-
deviations:COPPER_PIGTAIL_CONNECTOR</connector-type>
<form-factor>oc-opt-types:SFP_PLUS</form-factor>
<present>PRESENT</present>
</state>
</transceiver>
</component>
types">
<name>SFP-2</name>
types">
<id>SFP-2</id>
<name>SFP-2</name>

</state>
<serial-no>CN0V250M5BB2NMD </serial-no>
</state>
</transceiver>
</component>
types">
<name>SFP-3</name>
types">
<id>SFP-3</id>
<name>SFP-3</name>
</state>
<serial-no>CN0V250M5BB2NEE </serial-no>

</state>
</transceiver>
</component>
types">
<name>SFP-4</name>
types">
<id>SFP-4</id>
<name>SFP-4</name>
</state>
<serial-no>CN0V250M58V91K9 </serial-no>
</state>
</transceiver>
</component>
types">
<name>SFP-5</name>
types">
<id>SFP-5</id>
<name>SFP-5</name>

</state>
<present>NOT_PRESENT</present>
</state>
</transceiver>
</component>
types">
<name>SFP-6</name>
types">
<id>SFP-6</id>
<name>SFP-6</name>
</state>
<serial-no>CN0V250M58V920E </serial-no>
</state>
</transceiver>
</component>
types">
<name>SFP-7</name>
types">

<id>SFP-7</id>
<name>SFP-7</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-8</name>
types">
<id>SFP-8</id>
<name>SFP-8</name>
</state>
</state>
</transceiver>
</component>
types">

<name>SFP-9</name>
types">
<id>SFP-9</id>
<name>SFP-9</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-10</name>
types">
<id>SFP-10</id>
<name>SFP-10</name>
</state>
<serial-no>J11836008016 </serial-no>
<vendor-rev>01 </vendor-rev>

<vendor-part>ET5402-DAC-3M </vendor-part>
<vendor>Edgecore </vendor>
</state>
</transceiver>
</component>
types">
<name>SFP-11</name>
types">
<id>SFP-11</id>
<name>SFP-11</name>
</state>
<serial-no>NCI80T1328 </serial-no>
<vendor-rev>1.0 </vendor-rev>
<vendor-part>SFP-T </vendor-part>
<vendor>OEM </vendor>
<ethernet-pmd>ipi-oc-transport-types-deviations:ETH_1000BASE_T</
ethernet-pmd>
<connector-type>oc-opt-types:LC_CONNECTOR</connector-type>
</state>
</transceiver>
</component>
types">
<name>SFP-12</name>
types">
<id>SFP-12</id>
<name>SFP-12</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-13</name>
types">
<id>SFP-13</id>
<name>SFP-13</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-14</name>
types">

<id>SFP-14</id>
<name>SFP-14</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-15</name>
types">
<id>SFP-15</id>
<name>SFP-15</name>
</state>
</state>
</transceiver>
</component>
types">

<name>SFP-16</name>
types">
<id>SFP-16</id>
<name>SFP-16</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-17</name>
types">
<id>SFP-17</id>
<name>SFP-17</name>
</state>
</state>
</transceiver>

</component>
types">
<name>SFP-18</name>
types">
<id>SFP-18</id>
<name>SFP-18</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-19</name>
types">
<id>SFP-19</id>
<name>SFP-19</name>
</state>

</state>
</transceiver>
</component>
types">
<name>SFP-20</name>
types">
<id>SFP-20</id>
<name>SFP-20</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-21</name>
types">
<id>SFP-21</id>
<name>SFP-21</name>
</state>

</state>
</transceiver>
</component>
types">
<name>SFP-22</name>
types">
<id>SFP-22</id>
<name>SFP-22</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-23</name>
types">
<id>SFP-23</id>
<name>SFP-23</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-24</name>
types">
<id>SFP-24</id>
<name>SFP-24</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-25</name>
types">
<id>SFP-25</id>
<name>SFP-25</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-26</name>
types">
<id>SFP-26</id>
<name>SFP-26</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-27</name>
types">
<id>SFP-27</id>
<name>SFP-27</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-28</name>
types">
<id>SFP-28</id>
<name>SFP-28</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-29</name>
types">
<id>SFP-29</id>
<name>SFP-29</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-30</name>
types">
<id>SFP-30</id>
<name>SFP-30</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-31</name>
types">
<id>SFP-31</id>
<name>SFP-31</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-32</name>
types">
<id>SFP-32</id>
<name>SFP-32</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-33</name>
types">

<id>SFP-33</id>
<name>SFP-33</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-34</name>
types">
<id>SFP-34</id>
<name>SFP-34</name>
</state>
</state>
</transceiver>
</component>
types">

<name>SFP-35</name>
types">
<id>SFP-35</id>
<name>SFP-35</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-36</name>
types">
<id>SFP-36</id>
<name>SFP-36</name>
</state>
</state>
</transceiver>

</component>
types">
<name>SFP-37</name>
types">
<id>SFP-37</id>
<name>SFP-37</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-38</name>
types">
<id>SFP-38</id>
<name>SFP-38</name>
</state>

</state>
</transceiver>
</component>
types">
<name>SFP-39</name>
types">
<id>SFP-39</id>
<name>SFP-39</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-40</name>
types">
<id>SFP-40</id>
<name>SFP-40</name>
</state>

</state>
</transceiver>
</component>
types">
<name>SFP-41</name>
types">
<id>SFP-41</id>
<name>SFP-41</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-42</name>
types">
<id>SFP-42</id>
<name>SFP-42</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-43</name>
types">
<id>SFP-43</id>
<name>SFP-43</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-44</name>
types">
<id>SFP-44</id>
<name>SFP-44</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-45</name>
types">
<id>SFP-45</id>
<name>SFP-45</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-46</name>
types">
<id>SFP-46</id>
<name>SFP-46</name>

</state>
</state>
</transceiver>
</component>
types">
<name>SFP-47</name>
types">
<id>SFP-47</id>
<name>SFP-47</name>
</state>
</state>
</transceiver>
</component>
types">
<name>SFP-48</name>
types">
<id>SFP-48</id>
<name>SFP-48</name>

</state>
</state>
</transceiver>
</component>
types">
<name>QSFP-49</name>
types">
<id>QSFP-49</id>
<parent>PORT-ce49</parent>
</state>
<serial-no>CN05NP8R57Q7T6J </serial-no>
<ethernet-pmd>oc-opt-types:ETH_40GBASE_CR4</ethernet-pmd>
deviations:NO_SEPARABLE_CONNECTOR</connector-type>
<form-factor>oc-opt-types:QSFP_PLUS</form-factor>
</state>

<physical-channels xmlns="http://openconfig.net/yang/platform/
transceiver">
<channel>
<index>1</index>
<state>
<index>1</index>
<laser-bias-current xmlns="http://openconfig.net/yang/platform/
transceiver">
<instant xmlns:oc-types="http://openconfig.net/yang/
openconfig-types">0.000</instant>
</laser-bias-current>
transceiver">
</output-power>
<input-power xmlns="http://openconfig.net/yang/platform/
transceiver">
</input-power>
</state>
</channel>
<channel>
<index>2</index>
<state>
<index>2</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>
</state>
</channel>
<channel>
<index>3</index>
<state>
<index>3</index>
transceiver">
transceiver">
</output-power>
transceiver">

</input-power>
</state>
</channel>
<channel>
<index>4</index>
<state>
<index>4</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>
</state>
</channel>
</transceiver>
</component>
types">
types">
<id>QSFP-50</id>
</state>
</state>

transceiver">
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</transceiver>
</component>
types">
types">
<id>QSFP-51</id>
</state>
<serial-no>J11836008038 </serial-no>
<vendor-rev>01</vendor-rev>
<vendor-part>ET7402-100DAC-1M</vendor-part>
<vendor>Edgecore </vendor>
<ethernet-pmd>oc-opt-types:ETH_100GBASE_CR4</ethernet-pmd>
deviations:NO_SEPARABLE_CONNECTOR</connector-type>
<form-factor>oc-opt-types:QSFP28</form-factor>
</state>
transceiver">
<channel>

<index>1</index>
<state>
<index>1</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>
</state>
</channel>
<channel>
<index>2</index>
<state>
<index>2</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>
</state>
</channel>
<channel>
<index>3</index>
<state>
<index>3</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>

</state>
</channel>
<channel>
<index>4</index>
<state>
<index>4</index>
transceiver">
transceiver">
</output-power>
transceiver">
</input-power>
</state>
</channel>
</transceiver>
</component>
types">
types">
<id>QSFP-52</id>
</state>
</state>
transceiver">
<channel>
<index>1</index>

</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</transceiver>
</component>
types">
types">
<id>QSFP-53</id>
</state>
</state>
transceiver">
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</transceiver>

</component>
types">
types">
<id>QSFP-54</id>
</state>
</state>
transceiver">
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</transceiver>
</component>
</components>
OcNOS get result

<component>
<name>SFP-1</name>
<state>
<name>SFP-1</name>

<type>transceiver</type>
</state>
<transceiver>
<state>
<ddm-type>no</ddm-type>
<vendor-manufacturing-date>150908 </vendor-manufacturing-date>
<vendor-serial-number>CN0V250M58V91KC </vendor-serial-number>
<minimum-signalling-rate>0</minimum-signalling-rate>
<maximum-signalling-rate>0</maximum-signalling-rate>
<nominal-signalling-rate>103</nominal-signalling-rate>
<extended-check-code>0x4d</extended-check-code>
<check-code>0xdf</check-code>
<vendor-revision-number>C </vendor-revision-number>
<vendor-part-number>616740001 </vendor-part-number>
<vendor-ieee-id>0x78 0xa7 0x14</vendor-ieee-id>
<vendor-name>Amphenol </vendor-name>
<om4-link-length>1</om4-link-length>
<link-length-meter>0</link-length-meter>
<link-length-kilometer>0</link-length-kilometer>
<serial-encoding-algorithm>enc-unspecified</serial-encoding-
algorithm>
<fiber-channel-transmission-media>twinaxial-pair</fiber-channel-
transmission-media>
<fiber-channel-transmission-technology>electricalInter-Enclosure
electricalIntra-Enclosure</fiber-channel-transmission-technology>
<fiber-channel-link-length>short</fiber-channel-link-length>
<connector-type>copper-pigtail</connector-type>
<transceiver-identifier>sfp-or-sfpplus-or-sfp28</transceiver-
identifier>
<channel-count>1</channel-count>
<type>sfp</type>
<presence>Present</presence>
<port-no>1</port-no>
</state>
<sfp>
<state>
<sfp-plus-cable-technology>passive</sfp-plus-cable-technology>
<sfp-infiniband-compliance-code>ibc-1xcopperpassive</sfp-
infiniband-compliance-code>
<fiber-channel-sfp-speed>fcs-800mbps fcs-400mbps fcs-200mbps fcs-
100mbps</fiber-channel-sfp-speed>
<sfp-options-implemented>power-level1</sfp-options-implemented>

<sfp-identifier>gbic-or-sfp-definedby-twowire-interfaceid-only</
sfp-identifier>
<recieve-loss-status>NA</recieve-loss-status>
<transmit-status>on</transmit-status>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-2</name>
<state>
<name>SFP-2</name>
</state>
<transceiver>
<state>
<vendor-serial-number>CN0V250M5BB2NMD </vendor-serial-number>
<extended-check-code>0x57</extended-check-code>
algorithm>
transmission-media>
identifier>
<type>sfp</type>

</state>
<sfp>
<state>
sfp-identifier>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-3</name>
<state>
<name>SFP-3</name>
</state>
<transceiver>
<state>
<vendor-serial-number>CN0V250M5BB2NEE </vendor-serial-number>

algorithm>
transmission-media>
identifier>
<type>sfp</type>
</state>
<sfp>
<state>
sfp-identifier>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-4</name>
<state>
<name>SFP-4</name>
</state>
<transceiver>
<state>
<vendor-serial-number>CN0V250M58V91K9 </vendor-serial-number>

algorithm>
transmission-media>
identifier>
<type>sfp</type>
</state>
<sfp>
<state>
sfp-identifier>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-5</name>
<state>
<name>SFP-5</name>

</state>
<transceiver>
<state>
<type>sfp</type>
<presence>Not-Present</presence>
</state>
<sfp>
<state>
<transmit-status>off</transmit-status>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-6</name>
<state>
<name>SFP-6</name>
</state>
<transceiver>
<state>
<vendor-serial-number>CN0V250M58V920E </vendor-serial-number>
algorithm>

transmission-media>
identifier>
<type>sfp</type>
</state>
<sfp>
<state>
sfp-identifier>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-7</name>
<state>
<name>SFP-7</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>

</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-8</name>
<state>
<name>SFP-8</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-9</name>
<state>
<name>SFP-9</name>
</state>
<transceiver>
<state>

<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-10</name>
<state>
<name>SFP-10</name>
</state>
<transceiver>
<state>
<vendor-serial-number>J11836008016 </vendor-serial-number>
<check-code>0x6d</check-code>
<vendor-revision-number>01 </vendor-revision-number>
<vendor-part-number>ET5402-DAC-3M </vendor-part-number>
<vendor-ieee-id>0x70 0x72 0xcf</vendor-ieee-id>
<vendor-name>Edgecore </vendor-name>
algorithm>
identifier>

<type>sfp</type>
</state>
<sfp>
<state>
sfp-identifier>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-11</name>
<state>
<name>SFP-11</name>
</state>
<transceiver>
<state>
<vendor-serial-number>NCI80T1328 </vendor-serial-number>
<check-code>0x82</check-code>
<vendor-revision-number>1.0 </vendor-revision-number>
<vendor-part-number>SFP-T </vendor-part-number>
<vendor-ieee-id>0x0 0x0 0x0</vendor-ieee-id>
<vendor-name>OEM </vendor-name>
<serial-encoding-algorithm>enc-8b-or-10b</serial-encoding-algorithm>
<ethernet-compliance-code>ec-1000base-t</ethernet-compliance-code>
<connector-type>lucent-connector</connector-type>

identifier>
<type>sfp</type>
</state>
<sfp>
<state>
sfp-identifier>
<recieve-loss-status>on</recieve-loss-status>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-12</name>
<state>
<name>SFP-12</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-13</name>
<state>
<name>SFP-13</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-14</name>
<state>
<name>SFP-14</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>

</sfp>
</transceiver>
</component>
<component>
<name>SFP-15</name>
<state>
<name>SFP-15</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-16</name>
<state>
<name>SFP-16</name>
</state>
<transceiver>
<state>

<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-17</name>
<state>
<name>SFP-17</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-18</name>
<state>
<name>SFP-18</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-19</name>
<state>
<name>SFP-19</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-20</name>
<state>

<name>SFP-20</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-21</name>
<state>
<name>SFP-21</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>

</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-22</name>
<state>
<name>SFP-22</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-23</name>
<state>
<name>SFP-23</name>
</state>

<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-24</name>
<state>
<name>SFP-24</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-25</name>
<state>
<name>SFP-25</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-26</name>
<state>
<name>SFP-26</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>

<component>
<name>SFP-27</name>
<state>
<name>SFP-27</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-28</name>
<state>
<name>SFP-28</name>
</state>
<transceiver>
<state>
<type>sfp</type>

</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-29</name>
<state>
<name>SFP-29</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-30</name>
<state>
<name>SFP-30</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-31</name>
<state>
<name>SFP-31</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-32</name>
<state>
<name>SFP-32</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-33</name>
<state>
<name>SFP-33</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>

</sfp>
</transceiver>
</component>
<component>
<name>SFP-34</name>
<state>
<name>SFP-34</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-35</name>
<state>
<name>SFP-35</name>
</state>
<transceiver>
<state>

<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-36</name>
<state>
<name>SFP-36</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-37</name>
<state>
<name>SFP-37</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-38</name>
<state>
<name>SFP-38</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-39</name>
<state>

<name>SFP-39</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-40</name>
<state>
<name>SFP-40</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>

</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-41</name>
<state>
<name>SFP-41</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-42</name>
<state>
<name>SFP-42</name>
</state>

<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-43</name>
<state>
<name>SFP-43</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-44</name>
<state>
<name>SFP-44</name>

</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-45</name>
<state>
<name>SFP-45</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>

<component>
<name>SFP-46</name>
<state>
<name>SFP-46</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-47</name>
<state>
<name>SFP-47</name>
</state>
<transceiver>
<state>
<type>sfp</type>

</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<name>SFP-48</name>
<state>
<name>SFP-48</name>
</state>
<transceiver>
<state>
<type>sfp</type>
</state>
<sfp>
<state>
</state>
</sfp>
</transceiver>
</component>
<component>
<state>

</state>
<transceiver>
<state>
<maximum-case-temperature>70.00</maximum-case-temperature>
<vendor-serial-number>CN05NP8R57Q7T6J </vendor-serial-number>
<extended-check-code>0x7c</extended-check-code>
algorithm>
transmission-media>
<ethernet-compliance-code>ec-40gbase-cr4</ethernet-compliance-code>
<connector-type>no-separable-connector</connector-type>
<transceiver-identifier>qsfpplus-or-later</transceiver-identifier>
<type>qsfp</type>
</state>
<qsfp>
<state>
<qsfp-options-implemented>tx-cdr-on-or-off-fixed rx-cdr-on-or-off-
fixed rateselect-fixed</qsfp-options-implemented>
<fiber-channel-qsfp-speed>fcs-800mbps fcs-400mbps fcs-200mbps fcs-
100mbps</fiber-channel-qsfp-speed>
<qsfp-identifier>powerclass1-1dot5wmax</qsfp-identifier>
<lane4-recieve-loss>off</lane4-recieve-loss>
<lane4-transmission-loss>off</lane4-transmission-loss>
<lane4-transmission>on</lane4-transmission>
<power>High</power>
<reset-status>Normal</reset-status>
</state>

</qsfp>
<channels>
<channel>
<index>1</index>
<state>
<index>1</index>
<laser-bias-current>0.000</laser-bias-current>
<output-power>0.000</output-power>
<input-power>0.000</input-power>
</state>
</channel>
<channel>
<index>2</index>
<state>
<index>2</index>
</state>
</channel>
<channel>
<index>3</index>
<state>
<index>3</index>
</state>
</channel>
<channel>
<index>4</index>
<state>
<index>4</index>
</state>
</channel>
</channels>
</transceiver>
</component>
<component>
<state>

</state>
<transceiver>
<state>
<type>qsfp</type>
</state>
<qsfp>
<state>
<lane4-transmission>off</lane4-transmission>
<power>Low</power>
<reset-status>Reset</reset-status>
</state>
</qsfp>
<channels>
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</channels>
</transceiver>
</component>
<component>
<state>

</state>
<transceiver>
<state>
<maximum-case-temperature>70.00</maximum-case-temperature>
<vendor-serial-number>J11836008038 </vendor-serial-number>
<vendor-revision-number>01</vendor-revision-number>
<vendor-part-number>ET7402-100DAC-1M</vendor-part-number>
<vendor-ieee-id>0x70 0x72 0xcf</vendor-ieee-id>
<vendor-name>Edgecore </vendor-name>
algorithm>
<extended-ethernet-compliance-code>eec-100gbase-cr4-or-25gbase-crca-
l</extended-ethernet-compliance-code>
<connector-type>no-separable-connector</connector-type>
<transceiver-identifier>qsfp28-or-later</transceiver-identifier>
<type>qsfp</type>
</state>
<qsfp>
<state>
<qsfp-options-implemented>tx-cdr-on-or-off-fixed rx-cdr-on-or-off-
fixed rateselect-fixed</qsfp-options-implemented>
<qsfp-identifier>powerclass1-1dot5wmax</qsfp-identifier>
<power>High</power>
<reset-status>Normal</reset-status>
</state>
</qsfp>
<channels>
<channel>
<index>1</index>

<state>
<index>1</index>
</state>
</channel>
<channel>
<index>2</index>
<state>
<index>2</index>
</state>
</channel>
<channel>
<index>3</index>
<state>
<index>3</index>
</state>
</channel>
<channel>
<index>4</index>
<state>
<index>4</index>
</state>
</channel>
</channels>
</transceiver>
</component>
<component>
<state>
</state>
<transceiver>
<state>

<type>qsfp</type>
</state>
<qsfp>
<state>
<power>Low</power>
</state>
</qsfp>
<channels>
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</channels>
</transceiver>
</component>
<component>
<state>
</state>

<transceiver>
<state>
<type>qsfp</type>
</state>
<qsfp>
<state>
<power>Low</power>
</state>
</qsfp>
<channels>
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</channels>
</transceiver>
</component>
<component>
<state>

</state>
<transceiver>
<state>
<type>qsfp</type>
</state>
<qsfp>
<state>
<power>Low</power>
</state>
</qsfp>
<channels>
<channel>
<index>1</index>
</channel>
<channel>
<index>2</index>
</channel>
<channel>
<index>3</index>
</channel>
<channel>
<index>4</index>
</channel>
</channels>
</transceiver>
</component>
</components>
Show command
Here is Show command output that displays the hardware information for the transceiver.
OcNOS#show hardware-information transceiver
TX : Transmit status
RX-Los : Receive status
RESET : Normal (Out of reset), Reset (In reset)
POWER : Power level Low/High
- : NotApplicable

SFP:[1-48]
----------------------------------------------
PORT PRESENCE Tx Rx-Los
----------------------------------------------
1 Present On -
2 Present On -
3 Present On -
4 Present On -
5 Not Present Off -
6 Present On -
7 Not Present Off -
8 Not Present Off -
9 Not Present Off -
10 Present On -
11 Present On On
12 Not Present Off -
QSFP:[49-54]
------------------------------------------------------------------------------
--------------
PORT PRESENCE RESET POWER LANE

------------------------------------------------------------------------------
--------------
1 2
3 4
------------------------------------------------------------------------------
--------------
49 Present Normal High Tx on on
on on
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
50 Not Present Reset Low Tx off off
off off
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
51 Present Normal High Tx on on
on on
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
off off
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
off off
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
off off
Rx-Los Off Off
Off Off
Tx-Los Off Off
Off Off
EEPROM
This platform type displays board EEPROM details.
OpenConfig Filter
<component>
<state>
<name>CHASSIS</name>
</state>
</component>

</components>
</filter>
OpenConfig get result

types">
types">
<id>CHASSIS</id>
<parent>NA</parent>
<part-no>FP3ZZ5654000A</part-no>
<serial-no>591254X1849052</serial-no>
<software-version>EC_AS5912-54X-OcNOS-5.0.137a-SP_MPLS-S0-P0</
software-version>
<description>EC_AS5912-54X</description>
<mfg-date xmlns="http://openconfig.net/yang/platform">2020-08-
18T21:58:52Z</mfg-date>
<mfg-name>Accton</mfg-name>
types:CHASSIS</type>
</state>
</component>
</components>
OcNOS get result

<component>
<state>
<parent>NA</parent>
<product-name>5912-54X-O-AC-F</product-name>
<oper-status>active</oper-status>
<part-no>FP3ZZ5654000A</part-no>
<serial-no>591254X1849052</serial-no>
<software-version>EC_AS5912-54X-OcNOS-5.0.137a-SP_MPLS-S0-P0</
software-version>
<description>EC_AS5912-54X</description>

<mfg-date>2020-08-18T21:58:52Z</mfg-date>
<mfg-name>Accton</mfg-name>
<type>chassis</type>
</state>
<subcomponents>
<subcomponent>
<subcomponent-name>HARD-DISK</subcomponent-name>
<state>
<subcomponent-name>HARD-DISK</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>RAM</subcomponent-name>
<state>
<subcomponent-name>RAM</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>CPU</subcomponent-name>
<state>
<subcomponent-name>CPU</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>TEMPERATURE-SENSOR1</subcomponent-name>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>TEMPERATURE-BCM Chip</subcomponent-name>
<state>
<subcomponent-name>TEMPERATURE-BCM Chip</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>POWER-RAIL</subcomponent-name>
<state>
<subcomponent-name>POWER-RAIL</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>PSU-1</subcomponent-name>
<state>

</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>FAN_TRAY-1</subcomponent-name>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>PORT-lo</subcomponent-name>
<state>
<subcomponent-name>PORT-lo</subcomponent-name>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>PORT-eth0</subcomponent-name>
<state>
<subcomponent-name>PORT-eth0</subcomponent-name>
</state>
</subcomponent>

<subcomponent>
<subcomponent-name>PORT-xe1</subcomponent-name>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>

</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>

<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>

</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>

<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>

</state>
</subcomponent>
<subcomponent>
<subcomponent-name>PORT-ce49</subcomponent-name>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<state>
</state>
</subcomponent>
<subcomponent>
<subcomponent-name>PORT-lo.management</subcomponent-name>
<state>
<subcomponent-name>PORT-lo.management</subcomponent-name>
</state>
</subcomponent>
</subcomponents>
<chassis>
<state>
<supported-switch-chip-revision>BCM88370_B0</supported-switch-chip-
revision>
<supported-label-revision>R0BB</supported-label-revision>
<fan-board-id>Reserved</fan-board-id>
<switch-chip-revision>BCM88370_B0</switch-chip-revision>
<cyclic-redundancy-32bit-value>0x797A6D84</cyclic-redundancy-32bit-
value>
<diagnostic-version>0.0.5.9</diagnostic-version>
<vendor-name>Edgecore</vendor-name>

<onie-version>2018.05.00.04</onie-version>
<platform-name>x86_64-accton_as5912_54x-r0</platform-name>
<chassis-100g-ethernet-count>6</chassis-100g-ethernet-count>
<chassis-fast-ethernet-count>0</chassis-fast-ethernet-count>
<power-supplies-count>2</power-supplies-count>
<fan-tray-count>6</fan-tray-count>
<country-code>TW</country-code>
<label-revision>R02B</label-revision>
<mac-address>B8:6A:97:A7:47:3C</mac-address>
<up-time>517700</up-time>
</state>
</chassis>
</component>
</components>
Show command
Here is Show command output that displays the hardware information for the board.
OcNOS#show system-information board-info
System Board Information

========================
Product Name : 5912-54X-O-AC-F
Part Number : FP3ZZ5654000A
Serial Number : 591254X1849052
Base MAC Address : B8:6A:97:A7:47:3C
Manufacture Date : 08/18/2020 21:58:52
Label Revision : R02B
Platform Name : x86_64-accton_as5912_54x-r0
ONIE Version : 2018.05.00.04
MAC Addresses : 256
Manufacturer : Accton
Country Code : TW
Vendor Name : Edgecore
Diag Version : 0.0.5.9
CRC-32 : 0x797A6D84
Switch Chip Revision : BCM88370_B0
CPLD 1 Board Info : ES5654BQ
Fan Board Id : Reserved
CPLD 1 PCB version ID : Reserved
CPLD 1 Version : 9
CPLD 2 Version : 6
Fan CPLD Version : 2
CPU
This platform type displays CPU load information.

OpenConfig Filter
<component>
<state>
<name>CPU</name>
</state>
</component>
</components>
</filter>

types">
<name>CPU</name>
types">
<id>CPU</id>
<name>CPU</name>
types:CPU</type>
</state>
</component>
</components>
OcNOS get result

<component>
<name>CPU</name>
<state>
<name>CPU</name>

<type>cpu</type>
</state>
<cpu>
<state>
<cpu-utilization-critical>50</cpu-utilization-critical>
<cpu-utilization-alert>90</cpu-utilization-alert>
<cpu-utilization>3.02</cpu-utilization>
<cpu-15min-alert-threshold>50</cpu-15min-alert-threshold>
<cpu-1min-critical-threshold>40</cpu-1min-critical-threshold>
<cpu-15min-load-percentage>3.89</cpu-15min-load-percentage>
<processor-count>4</processor-count>
</state>
</cpu>
</component>
</components>
Show command
Here is Show command output that displays the hardware information for the CPU load.
OcNOS#show system-information cpu-load
System CPU-Load Information

===========================
Uptime : 0 Days 1 Hours 29 Minutes 2 Seconds
Load Average(1 min) : 5.93% (Crit Thresh : 40%, Alert Thresh : 50%)
Load Average(5 min) : 4.06% (Crit Thresh : N/A, Alert Thresh : 50%)
Load Average(15 min) : 3.28% (Crit Thresh : N/A, Alert Thresh : 50%)
Avg CPU Usage : 3.02%

CPU core 1 Usage : 3.74% (Crit Thresh : 50%, Alert Thresh : 90%)

System OpenConfig Translation
Host
This XML configuration snippet is used to set the network name for the device that OcNOS uses in system prompts
and default configuration filenames.
Using this command to set a network name also sets the host name in the Kernel.
Release

Here is a sample OpenConfig NetConf Payload to set the network name for the device.
<system xmlns="http://openconfig.net/yang/system">
<config>
<hostname>host123</hostname>
</config>
</system>
OcNOS CLI command

This CLI command is used to set the network name for the device.
OcNOS#conf t
OcNOS(config)#hostname host123

Here is a sample OcNOS NetConf Payload to set the network name for the device.
<system-info xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-system">
<config>
</config>
</system-info>
Validation
Here is a NetConf validation response that provides detailed information about setting the network name for the device.


<config/>
<state/>
</system>

This validation response provides information on the configuration and runtime for setting a network name for the
device.
<config>
</config>
<state>
<current-datetime>2021-11-18T12:36:44Z</current-datetime>
</state>
</system>
Unconfiguration
Use operation='delete'to unconfigure the configuration of network name on the device. Once unconfigured, the
host name returns to the default name “OcNOS”.

Here is a sample OpenConfig NetConf Payload to unconfigure.
<config>
<hostname operation="delete" />
</config>
</system>
Restriction
As per RFC 952 and RFC 1123, a host name string can contain only the special characters period (“.”) and hyphen (“-
”). These special characters cannot be at the start or end of a host name. The host name must be between 1 and 63
characters.
TimeZone Clock
This XML configuration snippet is used to set the system time zone.
Release

Here is a sample OpenConfig NetConf Payload to set the system time zone.

<clock>
<config>
<timezone-name>Pacific</timezone-name>
</config>
</clock>
</system>
OcNOS CLI command

This CLI command is used to set the system time zone.
OcNOS#conf t
OcNOS(config)#clock timezone Pacific

Here is a sample OcNOS NetConf Payload to set the system time zone.
<clock>
<config>
</config>
</clock>
</system>
Validation
Here is a NetConf validation response that provides detailed information about setting system time zone.

<clock/>
</system>

This validation response provides information on the configuration and runtime for setting system time zone.
<clock>
<config>
</config>
<state>
</state>
</clock>
</system>

Restrictions
The names allowed to be used for the time zone can be queried using the show timezone <macro region> CLI
command.
There is currently no provision to query this list through OpenConfig.
Rsyslog
This XML configuration snippet is used to change the Virtual Routing and Forwarding (VRF) of Rsyslog log processing
system.
Release

Here is a sample OpenConfig NetConf Payload to change the VRF of Rsyslog.
<logging>
<remote-servers>
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-sys-
deviations">
<vrf>management</vrf>
</config>
</remote-servers>
</logging>
</system>
OcNOS CLI command

This CLI command is used to change the VRF of Rsyslog.
OcNOS#conf t
OcNOS(config)#feature rsyslog vrf management

Here is a sample OcNOS NetConf Payload to change the VRF of Rsyslog.
<logging xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-logging">
<rsyslog>
<config>
</config>
</rsyslog>
</logging>

Validation
Here is a NetConf validation response that provides detailed information about changing VRF of Rsyslog.

<logging/>
</system>

This validation response provides information on the configuration and runtime for changing VRF for Rsyslog.
<logging>
<remote-servers>
deviations">
</config>
<state xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-sys-
deviations">
</state>
</remote-servers>
</logging>
</system>
Restrictions
The leaf system/logging/remote-servers/config/vrf accepts only default or management.
Logging Remote Server

This XML configuration snippet is used to set a syslog server.
OcNOS supports logging messages to a syslog server in addition to logging to a file or the console (local or ssh/telnet
console). Messages can be logged to a local syslog server (the machine on which OcNOS executes) as well as one or
more remote syslog servers.
Release

Here is a sample OpenConfig NetConf Payload to set a syslog server.
<logging>
<remote-servers>

deviations">
</config>
<remote-server>
<host>2.2.2.3</host>
<config>
</config>
<selectors>
<selector>
<severity>DEBUG</severity>
<config>
</config>
</selector>
</selectors>
</remote-server>
</remote-servers>
</logging>
</system>
OcNOS CLI command

This CLI command is used to set a syslog server.
OcNOS#conf t
OcNOS(config)#logging remote server 2.2.2.3 7 vrf management

Here is a sample OcNOS NetConf Payload to set a syslog server.
<logging xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-logging">
<rsyslog>
<remote-servers>
<remote-server>
<address>2.2.2.3</address>
<config>
<address>2.2.2.3</address>
<severity>7</severity>
</config>
</remote-server>
</remote-servers>
<config>
<vrf>default</vrf>
<enable-rsyslog>rsyslog</enable-rsyslog>
</config>
</rsyslog>
</logging>

Validation
Here is a NetConf validation response that provides detailed information about setting a syslog server.

<logging/>
</system>

This validation response provides information on the configuration and runtime for setting a syslog server.
<logging>
<remote-servers>
deviations">
</config>
deviations">
</state>
<remote-server>
<config>
</config>
<selectors>
<selector>
<config>
</config>
<state>
</state>
</selector>
</selectors>
<state>
</state>
</remote-server>
</remote-servers>
</logging>
</system>
Restrictions
• When configuring /system/logging/remote-servers/remote-server/selectors/selector/
config/facility leaf, it is mapped on IPI data model as /logging/global/config/remote-server-
facility leaf, which is a single and global configuration. To avoid issues during configuration, the value of
OpenConfig facility leaf must be the same on all facility leaves indicated on Payload. Otherwise, IPI

chooses one facility value among all the values present on payload for the configuration of all facility
leaves.
• When the delete operation is set on OpenConfig path /system/logging/remote-servers, it triggers the
deletion of IPI data model /logging/global/config/remote-server-facility leaf.
• When the OpenConfig objects/system/logging/remote-servers/remote-server are deleted
individually, it will not trigger the deletion of IPI datamodel /logging/global/config/remote-server-
facility leaf. In this case, this leaf will not be shown on NetConf Get output, but will be shown on show
running-config CLI.
Logging Remote Facility

This XML configuration snippet is used to set a syslog servers facility.
OcNOS supports logging messages to one or more remote syslog servers, but the same facility is used for all the
servers.
Use the number form of this command to apply the default facility value, which is local7.
Release
This configuration was introduced in OcNOS version 5.0

Here is a sample OpenConfig NetConf Payload to set syslog servers facility.
<logging>
<remote-servers>
deviations">
</config>
<remote-server>
<config>
</config>
<selectors>
<selector>
<facility>oc-log:LOCAL5</facility>
<config>
</config>
</selector>
</selectors>
</remote-server>
</remote-servers>
</logging>
</system>

OcNOS CLI command

The below CLI command is used to set syslog servers facility.
OcNOS#conf t
OcNOS(config)#logging remote facility local5

Here is a sample OcNOS NetConf Payload to set syslog servers facility.
<logging>
<remote-servers>
deviations">
</config>
<remote-server>
<config>
</config>
<selectors>
<selector>
<config>
</config>
</selector>
</selectors>
</remote-server>
</remote-servers>
</logging>
Validation
Here is a NetConf validation response that provides detailed information about setting a syslog servers facility.

<logging/>
</system>

This validation response provides information on the configuration and runtime for setting a syslog servers facility.
<logging>
<remote-servers>

deviations">
</config>
deviations">
</state>
<remote-server>
<config>
</config>
<selectors>
<selector>
<config>
</config>
<state>
</state>
</selector>
</selectors>
<state>
</state>
</remote-server>
</remote-servers>
</logging>
</system>
Restrictions
• The facility leaf can only be added using OpenConfig to a configured remote server, as it is a part of the
object’s key on the path /system/logging/remote-servers/remote-server/selectors/selector.
• When configuring /system/logging/remote-servers/remote-server/selectors/selector/
config/facility leaf, it is mapped on IPI data model as /logging/global/config/remote-server-
facility leaf, which is a single and global configuration. To avoid issues during configuration, the value of
OpenConfig facility leaf must be the same on all facility leaves indicated on Payload. Otherwise, IPI
chooses one facility value among all the values present on payload for the configuration of all facility
leaves.
• When the delete operation is set on OpenConfig path /system/logging/remote-servers, it triggers the
deletion of IPI data model /logging/global/config/remote-server-facility leaf.
• When the OpenConfig objects/system/logging/remote-servers/remote-server are deleted
individually, it will not trigger the deletion of IPI datamodel /logging/global/config/remote-server-
facility leaf. In this case, this leaf will not be shown on NetConf Get output, but will be shown on show
running-config CLI.

Alarms
Alarms do not have a configuration on OpenConfig. It is a runtime attribute, and when some event triggers the alarm, it
can be viewed on OpenConfig.
Use the following CLI command to enable Alarms:
OcNOS(config)#fault-management enable
To enable Alarms., it is necessary to change the logging levels to 4 or more using the following command:
OcNOS(config)#logging level all 4
Release

<alarms/>
</system>

This validation response provides information on the configuration and runtime for enabling the alarm.
<alarms>
<alarm>
<id>IFMGR_IF_DOWN:ce2/1</id>
<state>
<id>IFMGR_IF_DOWN:ce2/1</id>
<type-id>EQPT</type-id>
<severity xmlns:oc-alarm-types="http://openconfig.net/yang/alarms/
types">oc-alarm-types:MAJOR</severity>
<alarm-reported-timestamp xmlns="http://www.ipinfusion.com/yang/ocnos/
ipi-oc-sys-deviations">Thu Dec 16 2021 20:31:28 UTC</alarm-reported-timestamp>
<time-created>1639686688</time-created>
<text>OcNOS [IFMGR_IF_DOWN] Interface ce2/1 changed state to down</
text>
<resource>ce2/1</resource>
</state>
</alarm>
</alarms>
</system>

OcNOS CLI show command

This OcNOS CLI show command is used to enable the alarm.
OcNOS#show alarm active
Active Alarms received:-
Active Alarm Count: 2
Severity Status Alarm Description
MAJOR Active OcNOS [IFMGR_IF_DOWN] Interface ce2/1 changed state to
down
Restrictions
The alarms get generated only for some events as mentioned in the list here:
https://jira-ipi.atlassian.net/wiki/spaces/IPI/pages/741900306/Alarms+Datamodel+Design+Document#3.1.3--List-of-
supported%2Fregistered-alarms-in-OcNOS-5.1
https://jira-ipi.atlassian.net/wiki/spaces/IPI/pages/741900306/Alarms+Datamodel+Design+Document#3.1.2--List-of-
supported%2Fregistered-alarms-in-OcNOS-5.0

VLAN OpenConfig Translation
Match Single Tagged VLAN

This XML configuration snippet is used to set a single tag VLAN match.
Release

Here is a sample OpenConfig NetConf Payload to set a single tag VLAN match.
<interface>
<name>xe24</name>
<config>
<name>xe24</name>
</config>
<subinterfaces>
<subinterface>
<index>20</index>
<config>
<index>20</index>
</config>
<vlan xmlns="http://openconfig.net/yang/vlan">
<match>
<single-tagged-list>
<config>
<vlan-ids>6</vlan-ids>
</config>
</single-tagged-list>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to set a single tag VLAN match.
interface xe24.20
encapsulation dot1q 6


Here is a sample OcNOS NetConf Payload to set a single tag VLAN match.
<interface>
<name>xe24</name>
<config>
<name>xe24</name>
</config>
</interface>
<interface>
<config>
</config>
extended">
<subinterface-encapsulation>
<single-tag-vlan-matches>
<single-tag-vlan-match>
<encapsulation-type>dot1q</encapsulation-type>
<config>
<outer-vlan-id>6</outer-vlan-id>
</config>
</single-tag-vlan-match>
</single-tag-vlan-matches>
</subinterface-encapsulation>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that gives a detailed information about the single tagged VLAN match.
<interface>
<name>xe24</name>
<config>
<name>xe24</name>
</config>
<match>
<config>
</config>
<state>
</state>
</match>
</vlan>

</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
None
Match single tagged VLAN range

This XML configuration snippet is used to set a single tag VLAN range in a subinterface.
Release

Here is a sample OpenConfig NetConf Payload to set a single tag VLAN range in a subinterface.
<interface>
<name>xe26</name>
<subinterfaces>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<match>
<single-tagged-range>
<config>
<low-vlan-id>10</low-vlan-id>
<high-vlan-id>20</high-vlan-id>
</config>
</single-tagged-range>
</match>
<ingress-mapping>
<config>
<vlan-stack-action>PUSH</vlan-stack-action>
<vlan-id>15</vlan-id>
<tpid xmlns:oc-vlan-types="http://openconfig.net/yang/
vlan-types">oc-vlan-types:TPID_0X88A8</tpid>
</config>
</ingress-mapping>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>

OcNOS CLI Command

The below CLI command is used to set a single tag VLAN range in a subinterface.
interface xe26.10 switchport
encapsulation dot1q 10-20
rewrite push 0x88a8 15

Here is a sample OcNOS NetConf Payload to set a single tag VLAN range in a subinterface.
<interface>
<name>xe26</name>
<config>
<name>xe26</name>
</config>
</interface>
<interface>
<config>
<enable-switchport />
</config>
extended">
<config>
<outer-vlan-id>10-20</outer-vlan-id>
</config>
<rewrite>
<config>
<vlan-action>push</vlan-action>
<push-outer-vlan-id>15</push-outer-vlan-id>
<push-tpid>0x88a8</push-tpid>
</config>
</rewrite>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about the single tag VLAN range in a
subinterface.
<interface>

<name>xe26</name>
<config>
<name>xe26</name>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<state>
<counters>
</counters>
</state>
<ingress-mapping>
<config>
<tpid>TPID_0X88A8</tpid>
</config>
<state>
<tpid>TPID_0X88A8</tpid>
</state>
</ingress-mapping>
<match>
<single-tagged-range>
<config>
</config>
<state>
</state>
</single-tagged-range>
</match>
</vlan>

</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
If OcNOS “switchport” parameter has not been set previously on subinterface, VLAN range match needs to be
configured along with ingress-mapping or added in the cross-connect network-instance.
Match double tagged VLAN

This XML configuration snippet is used to set an outer VLAN match in a subinterface.
Release

Here is a sample OpenConfig NetConf Payload to set an outer VLAN match in a subinterface.
<interface>
<name>xe37</name>
<config>
<name>xe37</name>
</config>
<subinterfaces>
<subinterface>
<index>100</index>
<config>
<index>100</index>
</config>
<match>
<double-tagged-outer-list>
<config>
<outer-vlan-ids>400</outer-vlan-ids>
</config>
</double-tagged-outer-list>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>

OcNOS CLI Command

The below CLI command is used to set an outer VLAN match in a subinterface.
interface xe37.100
encapsulation dot1ad 400

Here is a sample OcNOS NetConf Payload to set an outer VLAN match in a subinterface.
<interface>
<name>xe37</name>
<config>
<name>xe37</name>
</config>
</interface>
<interface>
<config>
</config>
extended">
<encapsulation-type>dot1ad</encapsulation-type>
<config>
</config>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about the outer VLAN match in a subinterface.
<interface>
<name>xe37</name>
<config>
<name>xe37</name>
</config>
<subinterfaces>
<subinterface>
<index>100</index>
<config>
<index>100</index>
</config>

<state>
<counters>
</counters>
</state>
<match>
<double-tagged-outer-list>
<config>
</config>
<state>
</state>
</double-tagged-outer-list>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Double-tagged-outer-list does not support the inner-vlan-id configuration.
Match double tagged with outer and inner VLAN

This XML configuration snippet is used to set outer and inner VLAN match in a subinterface.
Release

Here is a sample OpenConfig NetConf Payload to set outer and inner VLAN match in a subinterface.
<interface>
<name>xe25</name>
<config>
<name>xe25</name>

</config>
<subinterfaces>
<subinterface>
<index>20</index>
<config>
<index>20</index>
</config>
<match>
<double-tagged>
<config>
<inner-vlan-id>30</inner-vlan-id>
</config>
</double-tagged>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to set outer and inner VLAN match in a subinterface.
interface xe25.20
encapsulation dot1ad 40 inner-dot1q 30

Here is a sample OcNOS NetConf Payload to set outer and inner VLAN match in a subinterface.
<interface>
<name>xe25</name>
<config>
<name>xe25</name>
</config>
</interface>
<interface>
<config>
</config>
extended">
<double-tag-vlan-matches>
<double-tag-vlan-match>
<config>

</config>
</double-tag-vlan-match>
</double-tag-vlan-matches>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about the outer and inner VLAN match in a
subinterface.
<interface>
<name>xe25</name>
<config>
<name>xe25</name>
</config>
<subinterfaces>
<subinterface>
<index>20</index>
<config>
<index>20</index>
</config>
<state>
<counters>
</counters>
</state>
<match>
<double-tagged>
<config>
</config>
<state>
</state>
</double-tagged>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>

Restrictions
None
Ingress-mapping actions
This XML configuration snippet is used to configure an ingress-mapping with VLAN actions. The allowed actions are
PUSH, POP and SWAP.
Release

Here is a sample OpenConfig NetConf Payload to configure an ingress-mapping with VLAN actions.
<interface>
<name>xe32</name>
<config>
<name>xe32</name>
</config>
<subinterfaces>
<subinterface>
<index>100</index>
<config>
<index>100</index>
</config>
<match>
<config>
</config>
</match>
<ingress-mapping>
<config>
<vlan-stack-action>SWAP</vlan-stack-action>
<tpid>TPID_0X8100</tpid>
</config>
</ingress-mapping>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>

OcNOS CLI Command

The below CLI command is used to configure an ingress-mapping with VLAN actions.
rewrite translate 1-to-1 0x8100 100

Here is a sample OcNOS NetConf Payload to configure an ingress-mapping with VLAN actions.
<interface>
<name>xe32</name>
<config>
<name>xe32</name>
</config>
</interface>
<interface>
<config>
</config>
extended">
<config>
</config>
<rewrite>
<config>
<vlan-action>translate</vlan-action>
<rewrite-translate-action>1-to-1</rewrite-translate-action>
<dot1q-dot1ad-tpid>0x8100</dot1q-dot1ad-tpid>
</config>
</rewrite>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about ingress-mapping with VLAN actions,
PUSH, POP and SWAP.

<interface>
<name>xe32</name>
<config>
<name>xe32</name>
</config>
<subinterfaces>
<subinterface>
<index>100</index>
<config>
<index>100</index>
</config>
<state>
<counters>
</counters>
</state>
<ingress-mapping>
<config>
<tpid
xmlns:oc-vlan-types="http://openconfig.net/yang/vlan-
types">oc-vlan-types:TPID_0X8100</tpid>
</config>
<state>
<tpid
xmlns:oc-vlan-types="http://openconfig.net/yang/vlan-
types">oc-vlan-types:TPID_0X8100</tpid>
</state>
</ingress-mapping>
<match>
<config>
</config>
<state>
</state>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>

Restrictions
Match is optional only for VLAN action PUSH. If not used, it will set encapsulation default in OcNOS.
Trunk VLANs in interface

This XML configuration snippet is used to configure a trunk VLAN range in an interface.
Release

Here is a sample OpenConfig NetConf Payload to configure a trunk VLAN range in an interface.
<network-instance>
<name>1</name>
<config>
<name>1</name>
types">oc-ni-types:L2L3</type>
<bridge-protocol xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-oc-
ni-augments">ieee-vlan-bridge</bridge-protocol>
</config>
<vlans>
<vlan>
<config>
<status>ACTIVE</status>
</config>
</vlan>
<vlan>
<config>
</config>
</vlan>
<vlan>
<config>
</config>
</vlan>
</vlans>
<interfaces>
<interface>
<id>xe7</id>
<config>

<id>xe7</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
<tpid xmlns="http://openconfig.net/yang/vlan">TPID_0X8100</tpid>
</config>
<switched-vlan xmlns="http://openconfig.net/yang/vlan">
<config>
<interface-mode>TRUNK</interface-mode>
<trunk-vlans>350..352</trunk-vlans>
</config>
</switched-vlan>
</ethernet>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure a trunk VLAN range in an interface.
bridge 1 protocol ieee vlan-bridge
!
vlan database
vlan 350-352 bridge 1 state enable
!
interface xe7
switchport
dot1ad ethertype 0x8100
bridge-group 1
switchport mode trunk
switchport trunk allowed vlan add 350-352

Here is a sample OcNOS NetConf Payload to configure a trunk VLAN range in an interface.
network-instance">
<network-instance>
<instance-name>1</instance-name>
<instance-type>l2ni</instance-type>
<config>
</config>
<vlans xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-vlan">

<vlan>
<config>
</config>
<customer-vlan>
<config>
<state>enable</state>
</config>
</customer-vlan>
</vlan>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
</vlans>
<bridge-ports>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>
</interface>
</bridge-ports>
</bridge>
<config>
</config>
</network-instance>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
<dot1ad-ether-type>0x8100</dot1ad-ether-type>
</config>

<port-vlan xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-port-
vlan">
<switched-vlan>
<interface-mode>trunk</interface-mode>
<config>
</config>
<allowed-vlan>
<config>
<allowed-vlan-id>350-352</allowed-vlan-id>
</config>
</allowed-vlan>
</switched-vlan>
</port-vlan>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about the trunk VLAN range in an interface.
<network-instance>
<name>1</name>
<config>
<name>1</name>
<type
</config>
<state>
<name>1</name>
<type
</state>
<fdb>
<config>
<mac-learning>true</mac-learning>
</config>
</fdb>
<interfaces>
<interface>
<id>xe7</id>
<config>
<id>xe7</id>
</config>
<state>
<id>xe7</id>
</state>
</interface>
</interfaces>
<vlans>

<vlan>
<config>
</config>
<state>
</state>
<members>
<member>
<state>
</state>
</member>
</members>
</vlan>
<vlan>
<config>
</config>
<state>
</state>
<members>
<member>
<state>
</state>
</member>
</members>
</vlan>
<vlan>
<config>
</config>
<state>
</state>
<members>
<member>
<state>
</state>
</member>
</members>
</vlan>
</vlans>
</network-instance>

<interface>
<name>xe7</name>
<config>
<name>xe7</name>
<type
</config>
<state>
<name>xe7</name>
<counters>
</counters>
<type
</state>
<state>
<hw-mac-address>b8:6a:97:c3:64:44</hw-mac-address>
<counters>
<in-crc-errors>0</in-crc-errors>
<in-jabber-frames>0</in-jabber-frames>
<in-fragment-frames>0</in-fragment-frames>
<in-oversize-frames>0</in-oversize-frames>
</counters>
</state>
<config>

</config>
<state>
</state>
</switched-vlan>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
VLANs associated to trunk interface must also be created and bridge must be associated to the interface.
Trunk interface with native VLAN
Release

Here is a sample OpenConfig NetConf Payload to configure a native VLAN for a trunk VLAN interface.
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>
<config>
<native-vlan>351</native-vlan>
</config>
</switched-vlan>
</ethernet>
</interface>

</interfaces>
OcNOS CLI Command

The below CLI command is used to configure a native VLAN for a trunk VLAN interface.
interface xe7
switchport
bridge-group 1
switchport trunk allowed vlan add 350-352
switchport trunk native vlan 351

Here is a sample OcNOS NetConf Payload to configure a native VLAN for a trunk VLAN interface.
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>
vlan">
<switched-vlan>
<config>
</config>
<allowed-vlan>
<config>
<allowed-vlan-id>350-352</allowed-vlan-id>
</config>
</allowed-vlan>
<vlans>
<config>
<native-vlan-id>351</native-vlan-id>
</config>
</vlans>
</switched-vlan>
</port-vlan>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about native VLAN for trunk VLAN inerface.
<interface>
<name>xe7</name>
<config>

<name>xe7</name>
<type
</config>
<state>
<name>xe7</name>
<counters>
</counters>
<type
</state>
<state>
<hw-mac-address>b8:6a:97:c3:64:44</hw-mac-address>
<counters>
</counters>
</state>
<config>
</config>

<state>
</state>
</switched-vlan>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
Access VLAN in interface

This XML configuration snippet is used to configure an access VLAN in an interface.
Release

Here is a sample OpenConfig NetConf Payload to configure an access VLAN in an interface.
<network-instance>
<name>1</name>
<config>
<name>1</name>
</config>
<vlans>
<vlan>
<config>
</config>
</vlan>
</vlans>

<interfaces>
<interface>
<id>xe16</id>
<config>
<id>xe16</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>xe16</name>
<config>
<name>xe16</name>
<type
</config>
<config>
<interface-mode>ACCESS</interface-mode>
<access-vlan>300</access-vlan>
</config>
</switched-vlan>
</ethernet>
</interface>
</interfaces>
OcNOS CLI command

The below CLI command is used to configure an access VLAN in an interface.
interface xe16
switchport
bridge-group 1
switchport mode access
switchport access vlan 300

Here is a sample OcNOS NetConf Payload to configure an access VLAN in an interface.
<network-instance>
<config>
</config>
<vlan>
<config>

</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
</vlans>
<bridge-ports>
<interface>
<name>xe16</name>
<config>
<name>xe16</name>
</config>
</interface>
</bridge-ports>
</bridge>
<config>
</config>
</network-instance>
<interface>
<name>xe16</name>
<config>
<name>xe16</name>
</config>
vlan">
<switched-vlan>
<interface-mode>access</interface-mode>
<config>
<interface-mode>access</interface-mode>
</config>
<vlans>
<config>
</config>
</vlans>
</switched-vlan>
</port-vlan>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about configuring an access VLAN in an
interface.
<interface>
<name>xe16</name>
<config>

<name>xe16</name>
<type
</config>
<state>
<name>xe16</name>
<counters>
</counters>
<type
</state>
<state>
<hw-mac-address>b8:6a:97:c3:64:4d</hw-mac-address>
<counters>
</counters>
</state>
<config>
</config>
<state>
</state>

</switched-vlan>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
Restrictions
VLAN associated to access interface must also be created and bridge must be associated to the interface.
Trunk VLANs in link aggregation interface

This XML configuration snippet is used to configure a trunk VLAN range in a link aggregation interface.
Release

Here is a sample OpenConfig NetConf Payload to configure a trunk VLAN range in a link aggregation interface.
<network-instance>
<name>1</name>
<config>
<name>1</name>
</config>
<fdb>
<config>
</config>
</fdb>
<vlans>
<vlan>
<config>
</config>
</vlan>
</vlans>

<interfaces>
<interface>
<id>sa3</id>
<config>
<interface>sa3</interface>
<id>sa3</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>sa3</name>
<config>
<name>sa3</name>
</config>
<config>
<trunk-vlans>300</trunk-vlans>
</config>
</switched-vlan>
<config>
</config>
</aggregation>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure a trunk VLAN range in a link aggregation interface.
interface sa3
switchport
bridge-group 1
switchport trunk allowed vlan add 300

Here is a sample OcNOS NetConf Payload to configure a trunk VLAN range in a link aggregation interface.
.
network-instance">
<network-instance>
<config>

</config>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
</vlans>
<bridge-ports>
<interface>
<name>sa3</name>
<config>
<name>sa3</name>
</config>
</interface>
</bridge-ports>
</bridge>
<config>
</config>
</network-instance>
<interface>
<name>sa3</name>
<config>
<name>sa3</name>
</config>
vlan">
<switched-vlan>
<config>
</config>
<allowed-vlan>
<config>
<allowed-vlan-id>300</allowed-vlan-id>
</config>
</allowed-vlan>
</switched-vlan>
</port-vlan>
</interface>
</interfaces>


Here is a NetConf validation response that provides detailed information about configuring trunk VLAN range in a link
aggregation interface.
.
<interface>
<name>sa3</name>
<config>
<name>sa3</name>
<type
</config>
<state>
<name>sa3</name>
<counters>
</counters>
<type
</state>
<state>
<hw-mac-address>0e:00:00:00:00:01</hw-mac-address>
<counters>
</counters>

</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
<config>
</config>
<state>
</state>
</switched-vlan>
<config>
</config>
<state>
</state>
</aggregation>
</interface>
</interfaces>
Restrictions
VLANs associated to trunk LAG must also be created and bridge must be associated to the LAG.
Trunk LAG with native VLAN

This XML configuration snippet is used to configure a native VLAN for a trunk VLAN link aggregation.
Release

Here is a sample OpenConfig NetConf Payload to configure a native VLAN for a trunk VLAN link aggregation.
<network-instance>
<name>1</name>
<config>
<name>1</name>

</config>
<fdb>
<config>
</config>
</fdb>
<vlans>
<vlan>
<config>
</config>
</vlan>
</vlans>
<interfaces>
<interface>
<id>po1</id>
<config>
<interface>po1</interface>
<id>po1</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>po1</name>
<config>
<name>po1</name>
</config>
<config>
</config>
</switched-vlan>
<config>
</config>
</aggregation>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure a native VLAN for a trunk VLAN link aggregation.

interface po1
switchport
bridge-group 1
switchport trunk allowed vlan add 300
switchport trunk native vlan 300

Here is a sample OcNOS NetConf Payload to configure a native VLAN for a trunk VLAN link aggregation.
network-instance">
<network-instance>
<config>
</config>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
</vlans>
<bridge-ports>
<interface>
<name>po1</name>
<config>
<name>po1</name>
</config>
</interface>
</bridge-ports>
</bridge>
<config>
</config>
</network-instance>
<interface>
<name>po1</name>
<config>
<name>po1</name>
</config>

vlan">
<switched-vlan>
<config>
</config>
<vlans>
<config>
<native-vlan-id>300</native-vlan-id>
</config>
</vlans>
<allowed-vlan>
<config>
<allowed-vlan-id>300</allowed-vlan-id>
</config>
</allowed-vlan>
</switched-vlan>
</port-vlan>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information about configuring a native VLAN for a trunk
VLAN link aggregation.
<interface>
<name>po1</name>
<config>
<name>po1</name>
<type
</config>
<state>
<name>po1</name>
<counters>

</counters>
<type
</state>
<state>
<hw-mac-address>0e:00:00:00:00:01</hw-mac-address>
<counters>
</counters>
</state>
</ethernet>
<subinterfaces>
<subinterface>
<index>0</index>
<config>
<index>0</index>
</config>
</subinterface>
</subinterfaces>
<config>
</config>
<state>
</state>
</switched-vlan>
<config>
</config>
<state>
</state>
</aggregation>
</interface>
</interfaces>

Restrictions
Creation of a cross connect

This XML configuration snippet is used to create a cross connect between 2 subinterfaces.
Release

Here is a sample OpenConfig NetConf Payload to create a cross connect between 2 subinterfaces.
<network-instance>
<name>test3</name>
<config>
<name>test3</name>
types">L2P2P</type>
<description>Test XConnection</description>
</config>
<interfaces>
<interface>
<id>xe7.10</id>
<config>
<id>xe7.10</id>
<subinterface>10</subinterface>
</config>
</interface>
<interface>
<id>xe8.20</id>
<config>
<id>xe8.20</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>xe7</name>
<config>
<name>xe7</name>
</config>

<subinterfaces>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<match>
<config>
</config>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
<interface>
<name>xe8</name>
<config>
<name>xe8</name>
</config>
<subinterfaces>
<subinterface>
<index>20</index>
<config>
<index>20</index>
</config>
<match>
<config>
</config>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to create a cross connect between 2 subinterfaces.
!
!
cross-connect test3
description Test XConnection

interface xe7.10
interface xe8.20

Here is a sample OcNOS NetConf Payload to create a cross connect between 2 subinterfaces.
instance">
<network-instance>
<instance-name>test3</instance-name>
<instance-type>cross-connect</instance-type>
<config>
</config>
<cross-connect xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-cross-
connect">
<config>
<xc-name>test3</xc-name>
</config>
<cross-connect-interfaces>
<cross-connect-interface>
<endpoint-if>eth7.10</endpoint-if>
<config>
</config>
</cross-connect-interface>
<cross-connect-interface>
<config>
</config>
</cross-connect-interface>
</cross-connect-interfaces>
</cross-connect>
</network-instance>
<interface>
<name>eth7.10</name>
<config>
<enable-switchport/>
</config>
<extended xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-if-extended">
<config>
</config>

</extended>
</interface>
<interface>
<config>
</config>
<config>
</config>
</extended>
</interface>
</interfaces>

Here is a NetConf validation response that provides detailed information on creating a cross connect between 2
subinterfaces.
<network-instance>
<name>test3</name>
<config>
<name>test3</name>
<type
types">oc-ni-types:L2P2P</type>
</config>
<state>
<name>test3</name>
<type
types">oc-ni-types:L2P2P</type>
</state>
<interfaces>
<interface>
<id>xe7.10</id>
<config>
<id>xe7.10</id>
</config>
<state>

<id>xe7.10</id>
</state>
</interface>
<interface>
<id>xe8.20</id>
<config>
<id>xe8.20</id>
</config>
<state>
<id>xe8.20</id>
</state>
</interface>
</interfaces>
</network-instance>
Restrictions
• Exactly 2 subinterfaces must be configured along with network-instance creation.
• The old path for Open Config /network-instances/network-instance/config/enabled is not
supported after Open Config v1.0.0, and without this path the Cross-Connect feature is lost in the translation for IPI
path /network-instances/network-instance/cross-connect/config/admin-disable.
Deletion of a cross connect

This XML configuration snippet is used to delete a cross connect.
Release

Here is a sample OpenConfig NetConf Payload to delete a cross connect.
<network-instance operation="delete">
<name>test3</name>
</network-instance>
OcNOS CLI Command

The below CLI command is used to delete a cross connect.


OcNOS(config)#no cross-connect test3
OcNOS#show running-config cross-connect
!

Here is a sample OcNOS NetConf Payload to delete a cross connect.
network-instance">
</network-instance>

Here is a NetConf validation response that provides information on deleting a cross connect.
<data/>
Restrictions
None
Configure Bridge Domain and associate L2 Subinterfaces

This XML configuration snippet is used to configure L2 Subinterface and attach to Bridge Domain.
Note: The subinterfaces are set to L2 implicitly by Bridge Domain instance translation. As a result, the subinterfaces
must either be created in the same transaction as Bridge Domain or created as L2 from CLI or IPI datamodel. If
the subinterfaces are created as L3, this would result in error while assiging them to a Bridge Domain instance.
Release

Here is a sample OpenConfig NetConf Payload to configure L2 Subinterface and attach to Bridge Domain.
<network-instance>
<name>1</name>
<config>
<name>1</name>
types">L2VSI</type>
<description>Test Bridge Domain</description>
</config>

<interfaces>
<interface>
<id>xe9.10</id>
<config>
<id>xe9.10</id>
</config>
</interface>
<interface>
<id>xe10.20</id>
<config>
<id>xe10.20</id>
</config>
</interface>
</interfaces>
</network-instance>
<interface>
<name>xe9</name>
<config>
<name>xe9</name>
</config>
<subinterfaces>
<subinterface>
<index>10</index>
<config>
<index>10</index>
</config>
<match>
<config>
</config>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
<subinterfaces>
<subinterface>
<index>20</index>
<config>

<index>20</index>
</config>
<match>
<config>
</config>
</match>
</vlan>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
OcNOS CLI Command

The below CLI command is used to configure L2 Subinterface and attach to Bridge Domain.
!
!
bridge-domain 1
description Test Bridge Domain
interface xe9.10
interface xe10.20
!

Here is a sample OcNOS NetConf Payload to configure L2 Subinterface and attach to Bridge Domain.
instance">
<network-instance>
<instance-type>bridge-domain</instance-type>
<config>
</config>
<bridge-domain xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-bridge-
domain">
<config>
<domain-id>1</domain-id>
<description>Test Bridge Domain</description>
<member-interfaces>xe9.10</member-interfaces>
<member-interfaces>xe10.20</member-interfaces>
</config>
</bridge-domain>
</network-instance>

<interface>
<name>xe9.10</name>
<config>
<name>xe9.10</name>
</config>
<config>
</config>
</extended>
</interface>
<interface>
<config>
</config>
<config>
</config>
</extended>
</interface>
<interface>
<name>xe9</name>
<config>
<name>xe9</name>
</config>
</interface>
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
</interface>
</interfaces>

Restrictions
Bridge Domain instance name must be an integer in the range 1-2147483647.
Deletion of a Bridge Domain instance

This XML configuration snippet is used to delete a Bridge Domain instance.
Release

Here is a sample OpenConfig NetConf Payload to delete a Bridge Domain instance.
<network-instances xmlns="<http://openconfig.net/yang/network-instance">>
<name>1</name>
</network-instance>
OcNOS CLI Command

The below CLI is used to delete a Bridge Domain instance.
OcNOS(config)#no bridge-domain 1
OcNOS#show running-config bridge-domain
!

Here is a sample OcNOS NetConf Payload to delete a Bridge Domain instance.
<network-instances xmlns="<http://www.ipinfusion.com/yang/ocnos/ipi-network-
instance">>
</network-instance>

Here is a NetConf validation response that provides information about deletion of a Bridge Domain instance.
<data/>

Restrictions
None
Creation of a VLAN bridge

This XML configuration snippet is used to create a VLAN bridge and assign VLANs to it.
Release

Here is a sample OpenConfig NetConf Payload to create a VLAN bridge and assign VLANs to it.
<network-instance>
<name>1</name>
<config>
<name>1</name>
</config>
<vlans>
<vlan>
<config>
<name>VLAN-401</name>
</config>
</vlan>
<vlan>
<config>
</config>
</vlan>
</vlans>
</network-instance>
OcNOS CLI Command

The below CLI command is used to create a VLAN bridge and assign VLANs to it.
bridge 1 protocol ieee vlan-bridge
!
vlan database
vlan 401 bridge 1 name VLAN-401 state enable

vlan 501 bridge 1 name VLAN-501 state enable

Here is a sample OcNOS NetConf Payload to create a VLAN bridge and assign VLANs to it.
network-instance">
<network-instance>
<config>
</config>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
<vlan>
<config>
</config>
<customer-vlan>
<config>
</config>
</customer-vlan>
</vlan>
</vlans>
</bridge>
<config>
</config>
</network-instance>

Here is a NetConf validation response that provides information about creating a VLAN bridge and assigning VLANs.
<network-instance>
<name>1</name>

<config>
<name>1</name>
<type
</config>
<state>
<name>1</name>
<type
</state>
<fdb>
<config>
</config>
</fdb>
<vlans>
<vlan>
<config>
</config>
<state>
</state>
</vlan>
<vlan>
<config>
</config>
<state>
</state>
</vlan>
</vlans>
</network-instance>
Restrictions
The network-instance used for bridge must have a name being a number between 1 and 32.

LLDP OpenConfig Translation
Enable Management Attributes

This XML configuration snippet is used to enable LLDP and all the management TLV attributes.
Release

Here is a sample OpenConfig NetConf Payload to enable LLDP and all the management TLV attributes.
<lldp xmlns="http://openconfig.net/yang/lldp">
<config>
</config>
</lldp>
OcNOS CLI command

The below CLI command is used to enable LLDP and all the management TLV attributes.
lldp run
lldp tlv-select basic-mgmt port-description
lldp tlv-select basic-mgmt system-name
lldp tlv-select basic-mgmt system-capabilities
lldp tlv-select basic-mgmt system-description
lldp tlv-select basic-mgmt management-address

Here is a sample OcNOS NetConf Payload to enable LLDP and all the management TLV attributes.
<lldp xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-lldpv2">
<global>
<global-tlv-control>
<global-basic-management>
<config>
<port-description>true</port-description>
<management-address>true</management-address>
<system-capabilities>true</system-capabilities>
<system-description>true</system-description>
<system-name>true</system-name>
</config>
</global-basic-management>
</global-tlv-control>

<config>
<enable>true</enable>
</config>
</global>
</lldp>

Here is a NetConf validation response that provides detailed information about enabling LLDP and all the management
TLV attributes.
<config>
</config>
<state>
<counters>
<entries-aged-out>0</entries-aged-out>
<frame-discard>0</frame-discard>
<frame-out>0</frame-out>
<frame-in>0</frame-in>
</counters>
<system-name>OcNOS</system-name>
</state>
</lldp>
Restrictions
None
Configure chassis-id
This XML configuration snippet is used to set the locally assigned chassis name for the LLDP interface.
Release

Here is a sample OpenConfig NetConf Payload to set the locally assigned chassis name for the LLDP interface.
<config>
<chassis-id>host7028_AS5912-54X</chassis-id>
</config>
</lldp>
OcNOS CLI command

The below CLI command is used to set the locally assigned chassis name for the LLDP interface.

set lldp chassis locally-assigned host7028_AS5912-54X

Here is a sample OcNOS NetConf Payload to set the locally assigned chassis name for the LLDP interface.
<global>
<management-if>
<config>
<locally-assigned-chassis-id>host7028_AS5912-54X</locally-
assigned-chassis-id>
</config>
</management-if>
</global>
</lldp>

Here is a NetConf validation response that provides detailed information about setting the locally assigned chassis
name for the LLDP interface.
<config>
<chassis-id-type>MAC_ADDRESS</chassis-id-type>
</config>
<state>
<counters>
</counters>
</state>
</lldp>
Restrictions
The chassis type MAC_ADDRESS is fixed and assumed by default.
Configure suppress advertisement

This XM configuration snippet is used to configure suppress TLV advertisement for one or more attributes.
Release


Here is a sample OpenConfig NetConf Payload to configure suppress TLV advertisement for one or more attributes.
<config>
<suppress-tlv-advertisement>SYSTEM_DESCRIPTION</suppress-tlv-advertisement>
</config>
</lldp>
OcNOS CLI command

The below CLI command is used to configure suppress TLV advertisement for one or more attributes.
no lldp tlv-select basic-mgmt system-description

Here is a sample OcNOS NetConf Payload to configure suppress TLV advertisement for one or more attributes.
<global>
<global-tlv-control>
<global-basic-management>
<config>
<system-description>false</system-description>
</config>
</global-basic-management>
</global-tlv-control>
</global>
</lldp>

Here is a NetConf validation response that provides detailed information about configuring suppress TLV
advertisement for one or more attributes
<config>
<suppress-tlv-advertisement
xmlns:oc-lldp-types="http://openconfig.net/yang/lldp/types">oc-lldp-
types:SYSTEM_DESCRIPTION</suppress-tlv-advertisement>
</config>
<state>
<counters>
</counters>
<suppress-tlv-advertisement

xmlns:oc-lldp-types="http://openconfig.net/yang/lldp/types">oc-lldp-
types:SYSTEM_DESCRIPTION</suppress-tlv-advertisement>
</state>
</lldp>
Restrictions
By default, all basic tlvs are disabled and can be configured using this leaf. The default behavior is 'suppressed', so this
leaf-list will only show up if at least one advertisement is enabled.
As OpenConfig and OcNOS have a reverse logic for the TLV (suppress vs enable), when the suppress is present on
OpenConfig, the translation forces deletion of the attribute on the Ocnos side. This is equivalent to deleting a
configuration that does not exist, in which case, an error may be returned.
Configure system name

This XMl configuration snippet is used to configure the system-name (hostname).
Release

Here is a sample OpenConfig NetConf Payload to configure the system-name (hostname).
<config>
<system-name>host7028</system-name>
</config>
</lldp>
OcNOS CLI command

This CLI command is used to configure the system-name (hostname).
hostname host7028

Here is a sample OcNOS NetConf Payload to configure the system-name (hostname).
<config>
</config>
</system-info>


Here is a NetConf validation response that provides detailed information about configuring the system name
(hostname).
Filter:
<get xmlns="urn:ietf:params:xml:ns:NETCONF:base:1.0">
<config>
<hostname />
</config>
</system-info>
</filter>
</get>
Result:
<config>
</config>
</system>
Restrictions
The configuration is same as system hostname, so both are modified when applied.
The same restrictions as for system hostname apply:
Per RFC 952 and RFC 1123, a hostname string can contain only the special characters period (“.”) and hyphen (“-”).
These special characters cannot be at the start or end of a hostname. The number of characters in the hostname must
be between 1 and 63 characters.
Enable LLDP on an interface

This XML configuration snippet is used to enable LLDP on an interface.
Release

Here is a sample OpenConfig NetConf Payload to enable LLDP on an interface.
<interfaces>
<interface>
<name>xe10</name>
<config>
</config>
</interface>

</interfaces>
</lldp>
OcNOS CLI command

The blow CLI command is used to enable LLDP on an interface.
interface xe10
lldp-agent
set lldp enable txrx

Here is a sample OcNOS NetConf Payload to enable LLDP on an interface.
<interfaces>
<interface>
<name>xe10</name>
<agent>
<agent-type>default</agent-type>
<config>
<enable-tx-rx>txrx</enable-tx-rx>
</config>
</agent>
</interface>
</interfaces>
</lldp>

Here is a NetConf validation response that provides detailed information about enabling LLDP on an interface.
<interfaces>
<interface>
<name>xe10</name>
<config>
<name>xe10</name>
</config>
</interface>
</interfaces>
</lldp>
Restrictions
When enabled = true, the configuration mode is tx-rx in OcNOS. When enabled = false, the OcNOS mode is set as rx-
only.
LLDP get Attributes

The following attributes are read-only (runtime) for LLDP.

Counters
This command is used to display LLDP counters.
OpenConfig Filter
<filter>
<state>
<counters/>
</state>
</lldp>
</filter>

<state>
<counters>
</counters>
</state>
</lldp>
OcNOS get result

<global>
<state>
<counters>
<remote-ageouts>0</remote-ageouts>
<remote-drops>0</remote-drops>
<remote-deletes>0</remote-deletes>
<remote-inserts>1</remote-inserts>
</counters>
</state>
</global>
</lldp>
Restrictions
Only the counters remote-ageouts, remote-drops, remote-deletes, and remote-inserts are supported.

Interface counters
This command is used to display LLDP interface counters.
OpenConfig Filter
<filter>///<lldp xmlns="http://openconfig.net/yang/lldp">
<interfaces>
<interface>
<name>ce50</name>
<state>
<counters/>
</state>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<state>
<counters>
</counters>
</state>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<agent>
<transmit>
<state>
<tx-fast-init>2</tx-fast-init>
<tx-credit-max>9</tx-credit-max>

<message-fast-tx>222</message-fast-tx>
<message-tx-hold-multiplier>88</message-tx-hold-multiplier>
<message-tx-interval>999</message-tx-interval>
<reinit-delay>6</reinit-delay>
<tx-ttl>65535</tx-ttl>
<counters>
<frames-out>14</frames-out>
</counters>
</state>
</transmit>
</agent>
</interface>
</interfaces>
</lldp>
Restrictions
Only the counter frame-out is supported.
Neighbors
This command is used to display neighbors.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<name>ce50</name>
<neighbors>
<neighbor>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>

<id>b86a.97be.193e</id>
<state><id>b86a.97be.193e</id><system-description>Hardware
Model:EC_AS5912-54X</system-description>1<ttl>121</ttl><port-id-
type>MAC_ADDRESS</port-id-type><port-description>xe1</port-description><port-
id>b86a.97be.193e</port-id><chassis-id-type>NETWORK_ADDRESS</chassis-id-
type><chassis-id>10.12.89.136</chassis-id><system-name>7031</system-
name><management-address>b86a.97a7.253c</management-address><management-
address-type>MAC Address</management-address-type></state>
<capabilities xmlns:oc-lldp-types="http://openconfig.net/yang/
lldp/types">
<capability>
<name>oc-lldp-types:MAC_BRIDGE</name>
<state>
</state>
</capability>
<capability>
<name>oc-lldp-types:ROUTER</name>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<oui-subtype>4</oui-subtype>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1518</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>11654</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>

</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
lldp/types">
<capability>
<state>
</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>

<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1518</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
Neighbors name and description

This command is used to display neighbors' name and description.

OpenConfig Filter
<filter>
<interfaces>
<interface>
<neighbors>
<neighbor>
<name>ce50</name>
<state>
<system-name/>
<description/>
<id/>
<ttl/>
</state>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>eth0</name>
<config>
<name>eth0</name>
</config>
<neighbors>
<neighbor>
<id>08f1.ea53.dbf2</id>
<state>
<system-description>HPE OfficeConnect Switch 1920S 24G 2SFP
JL381A PD.01.05 Linux 3.6.5-ac96795c U-Boot 2012.10-00118-g3773021 (Oct 11
2016 - 15:39:54)</system-description>
<system-name>LAB1-SW13</system-name>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193f</id>
<state>

<id>b86a.97be.193f</id>
<system-description>Hardware Model:EC_AS5912-54X</system-
description>
<system-name>7031</system-name>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
<state>
<id>b86a.97be.193e</id>
description>
</state>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<mac-address>b86a.97be.193e</mac-address>
<state>
<system-capabilties-enabled>Bridge Router</system-capabilties-enabled>
<system-capabilties>Bridge Router</system-capabilties>
<system-description>Hardware Model:EC_AS5912-54X</system-description>
<max-frame-size>1518</max-frame-size>
<link-aggregate-capability>Capable</link-aggregate-capability>
<operational-mau-type>54</operational-mau-type>
<auto-negotiation-capability>16</auto-negotiation-capability>
<auto-negotiation-support>1</auto-negotiation-support>
<management-vlan>0</management-vlan>
<vid-usage-digest>0</vid-usage-digest>

<pp-vlanid>0</pp-vlanid>
<port-vlan-id>0</port-vlan-id>
<ttl>121</ttl>
<port-sub-type>3</port-sub-type>
<port-description>xe1</port-description>
<port-id>b86a.97be.193e</port-id>
<chassis-id-type>5</chassis-id-type>
<chassis-component>10.12.89.136</chassis-component>
<management-list>
<address>b86a.97a7.253c</address>
<oid>0</oid>
<interface-number>10001</interface-number>
<interface-number-sub-type>ifindex</interface-number-sub-type>
<address-sub-type>MAC Address</address-sub-type>
</management-list>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>
Neighbors chassis-id, type and ttl

This command is used to display neighbors' chassis-id, type and ttl.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<neighbors>
<neighbor>
<name>ce50</name>
<state>
<chassis-id/>
<chassis-id-type/>
<id/>
<ttl/>
</state>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>


<interfaces>
<interface>
<name>eth0</name>
<config>
<name>eth0</name>
</config>
<neighbors>
<neighbor>
<state>
<chassis-id>08f1.ea53.dbf0</chassis-id>
<ttl>120</ttl>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193f</id>
<state>
<id>b86a.97be.193f</id>
<chassis-id>b86a.97a7.253c</chassis-id>
<ttl>121</ttl>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
<state>
<id>b86a.97be.193e</id>
<chassis-id>10.12.89.136</chassis-id>
<chassis-id-type>NETWORK_ADDRESS</chassis-id-type>
<ttl>121</ttl>
</state>
</neighbor>
</neighbors>
</interface>

</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<state>
<system-capabilties-enabled>Bridge Router</system-
capabilties-enabled>
description>
<link-aggregate-capability>Capable</link-aggregate-
capability>
<auto-negotiation-capability>16</auto-negotiation-
capability>
<ttl>121</ttl>
<management-list>
<oid>0</oid>
<interface-number-sub-type>ifindex</interface-number-sub-
type>
</management-list>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>

Neighbors port-id, type and description

This is used to display neighbors' port-id, port-id-type and port-description.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<neighbors>
<neighbor>
<name>ce50</name>
<state>
<port-id/>
<port-id-type/>
<port-description/>
<management-address/>
<management-address-type/>
</state>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>eth0</name>
<config>
<name>eth0</name>
</config>
<neighbors>
<neighbor>
<state>
<port-id>08f1.ea53.dbf2</port-id>
<port-id-type>MAC_ADDRESS</port-id-type>
<port-description>19</port-description>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe2</name>

<config>
<name>xe2</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193f</id>
<state>
<id>b86a.97be.193f</id>
<port-id>b86a.97be.193f</port-id>
</state>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
<state>
<id>b86a.97be.193e</id>
</state>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<state>
<system-capabilties-enabled>Bridge Router</system-
capabilties-enabled>
description>

<link-aggregate-capability>Capable</link-aggregate-
capability>
<auto-negotiation-capability>16</auto-negotiation-
capability>
<ttl>121</ttl>
<management-list>
<oid>0</oid>
<interface-number-sub-type>ifindex</interface-number-sub-
type>
</management-list>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>
Neighbors custom TLVs type/subtype

This command is used to display neighbors' custom TLVs type/subtype.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<neighbors>
<neighbor>
<custom-tlvs>
<tlv>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<config/>
</state>
</tlv>

</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>eth0</name>
<config>
<name>eth0</name>
</config>
<neighbors>
<neighbor>
<state><id>08f1.ea53.dbf2</id><system-description>HPE
OfficeConnect Switch 1920S 24G 2SFP JL381A PD.01.05 Linux 3.6.5-ac96795c U-
Boot 2012.10-00118-g3773021 (Oct 11 2016 - 15:39:54)</system-
description>0<ttl>120</ttl><port-id-type>MAC_ADDRESS</port-id-type><port-
description>19</port-description><port-id>08f1.ea53.dbf2</port-id><chassis-id-
type>MAC_ADDRESS</chassis-id-type><chassis-id>08f1.ea53.dbf0</chassis-
id><system-name>LAB1-SW13</system-name><management-address>10.12.89.123</
management-address><management-address-type>IP Address</management-address-
type></state>
lldp/types">
<capability>
<state>
</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>0</value>

</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>000</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe2</name>
<config>
<name>xe2</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193f</id>
<state><id>b86a.97be.193f</id><system-description>Hardware
id>b86a.97be.193f</port-id><chassis-id-type>MAC_ADDRESS</chassis-id-
type><chassis-id>b86a.97a7.253c</chassis-id><system-name>7031</system-
lldp/types">
<capability>

<state>
</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1518</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>

</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
lldp/types">
<capability>
<state>
</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1518</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>

</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<state>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>

Neighbors custom TLVs

This command is used to display neighbors' custom TLVs.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<name>ce50</name>
<neighbors>
<neighbor>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>0-80-C2</oui>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
lldp/types">
<capability>
<state>

</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1518</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>

</neighbors>
</interface>
</interfaces>
</lldp>
OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<state>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>
Neighbors capabilities
This command is used to display neighbors' capabilities.
OpenConfig Filter
<filter>
<interfaces>
<interface>
<name>ce50</name>
<neighbors>
<neighbor>
<capabilities>
<capability>
<name/>
<config/>
<state/>
</capability>
</capabilities>
</neighbor>
</neighbors>
</interface>

</interfaces>
</lldp>
</filter>

<interfaces>
<interface>
<name>xe1</name>
<config>
<name>xe1</name>
</config>
<neighbors>
<neighbor>
<id>b86a.97be.193e</id>
name><management-address>b86a.97be.193e</management-address><management-
lldp/types">
<capability>
<state>
</state>
</capability>
<capability>
<state>
</state>
</capability>
</capabilities>
<custom-tlvs>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>
<state>
<type>127</type>
<oui>00-12-0F</oui>
<value>1522</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-12-0F</oui>

<state>
<type>127</type>
<oui>00-12-0F</oui>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>Rapid-Spanning-Tree-Protocol</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>0</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>1</value>
</state>
</tlv>
<tlv>
<type>127</type>
<oui>00-80-C2</oui>
<state>
<type>127</type>
<oui>00-80-C2</oui>
<value>1default</value>
</state>
</tlv>
</custom-tlvs>
</neighbor>
</neighbors>
</interface>
</interfaces>
</lldp>

OcNOS get result

<interfaces>
<interface>
<name>xe1</name>
<neighbors>
<agent>
<neighbor>
<state>
</state>
</neighbor>
</agent>
</neighbors>
</interface>
</interfaces>
</lldp>

ACL OpenConfig Translation
Enable Management Attributes

This XML configuration snippet is used to create an Access Control List (ACL) entry to operate over L2 data traffic.
Release

Here is a sample OpenConfig NetConf Payload to enable management attributes.
<acl xmlns="http://openconfig.net/yang/acl">
<acl-sets>
<acl-set>
<name>ACL_OC_L2</name>
<type
xmlns:oc-acl="http://openconfig.net/yang/acl">oc-acl:ACL_L2</type>
<config>
<type
<description>ACL L2 CFG Test</description>
</config>
<acl-entries>
<acl-entry>
<sequence-id>1</sequence-id>
<config>
</config>
<l2>
<config>
<destination-mac>00BB.CCDD.EEFF</destination-mac>
<destination-mac-mask>AC00.0000.0000</destination-mac-mask>
<ethertype>ETHERTYPE_IPV4</ethertype>
<source-mac>0000.CCDD.EEFF</source-mac>
<source-mac-mask>AABB.0000.0000</source-mac-mask>
</config>
</l2>
<actions>
<config>
<forwarding-action
xmlns:oc-acl="http://openconfig.net/yang/acl">oc-acl:ACCEPT</
forwarding-action>
<log-action>LOG_SYSLOG</log-action>
</config>
</actions>
</acl-entry>

</acl-entries>
</acl-set>
</acl-sets>
</acl>
OcNOS CLI Command

This CLI command is used to enable management attributes.
mac access-list ACL_OC_L2
remark ACL L2 CFG Test
1 permit 0000.CCDD.EEFF AABB.0000.0000 00BB.CCDD.EEFF AC00.0000.0000 ipv4 log
!

Here is a sample OcNOS NetConf Payload to enable management attributes.
<acl xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-acl">
<acl-sets>
<acl-set>
<type>mac</type>
<config>
<type>mac</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<mac>
<config>
<destination-mac-address>0000.0000.0000</destination-mac-
address>
<destination-mac-mask>AA32.CCDD.EE10</destination-mac-mask>
<ethertype>ipv4</ethertype>
<source-mac-address>0000.0000.00EE</source-mac-address>
<source-mac-mask>AABB.CCDD.EE11</source-mac-mask>
<forwarding-action>permit</forwarding-action>
<monitor-action>log</monitor-action>
</config>
</mac>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>

Here is a NetConf validation response that provides detailed information about enabling management attributes.

<acl-sets>
<acl-set>
<type
<config>
<type
xmlns:oc-acl="http://openconfig.net/yang/acl">oc-acl:ACL_L2</
type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<mac>
<config>
<source-mac>0000.CCDD.EEFF</source-mac>
<source-mac-mask>AABB.0000.0000</source-mac-mask>
<ethertype>ETHERTYPE_IPV4</ethertype>
<destination-mac>00BB.CCDD.EEFF</destination-mac>
<destination-mac-mask>AC00.0000.0000</destination-mac-mask>
</config>
</mac>
<actions>
<config>
<forwarding-action
xmlns:oc-acl="http://openconfig.net/yang/acl">oc-
acl:ACCEPT</forwarding-action>
<log-action
acl:LOG_SYSLOG</log-action>
</config>
</actions>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
Restrictions
The leaf /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/actions/config/log-action is
only valid on DC platform. Other leaves are valid on all the platforms.
Create IPv4 Entries

This XML configuration snippet is used to create an ACL entry to operate over IPv4 data traffic.

Release

Here is a sample OpenConfig NetConf Payload to create IPv4 entries.
<acl-sets>
<acl-set>
<name>ACL_OC_IPV4</name>
<type
xmlns:oc-acl="http://openconfig.net/yang/acl">oc-acl:ACL_IPV4</
type>
<config>
<type
type>
<description>ACL TFW Test</description>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<source-address>1.1.1.0/24</source-address>
<destination-address>2.2.2.0/24</destination-address>
<dscp>18</dscp>
<protocol>6</protocol>
</config>
</ipv4>
<actions>
<config>
<forwarding-action
</config>
</actions>
<transport>
<config>
<explicit-tcp-flags
xmlns:oc-pkt-match-types="http://openconfig.net/yang/
packet-match-types">oc-pkt-match-types:TCP_SYN</explicit-tcp-flags>
<source-port>22</source-port>
<destination-port>80</destination-port>
</config>
</transport>
</acl-entry>
</acl-entries>
</acl-set>

</acl-sets>
</acl>
OcNOS CLI Command

This CLI command is used to create IPv4 entries.
ip access-list ACL_OC_IPV4
remark ACL TFW Test
10 permit tcp 1.1.1.0/24 2.2.2.0/24 dscp af21 syn log
!

Here is a sample OcNOS NetConf Payload to create IPv4 entries.
<acl-sets>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>18</dscp>
<protocol-tcp />
<tcp-source-port>22</tcp-source-port>
<tcp-destination-port>80</tcp-destination-port>
<tcp-flags>syn</tcp-flags>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>

Here is a NetConf validation response that provides detailed information about creating IPv4 entries.

<acl-sets>
<acl-set>
<type
type>
<config>
<type
type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>18</dscp>
</config>
</ipv4>
<actions>
<config>
<forwarding-action
<log-action
</config>
</actions>
<transport>
<config>
<explicit-tcp-flags
xmlns:oc-pkt-match-types="http://openconfig.net/yang/
packet-match-types">oc-pkt-match-types:TCP_SYN</explicit-tcp-flags>
</config>
</transport>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
Restrictions
• The leaf /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/actions/config/log-action is
only valid on DC platform.
• The Open Config leaf /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry[sequence-id]/
transport/config/tcp-flags was named in version 2.0.0. It is now renamed as explicit-tcp-flags. The new

XPath is /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/transport/config/explicit-
tcp-flags.
• OpenConfig leaves /acl/acl-sets/acl-set/acl-entries/acl-entry/transport/config/
explicit-tcp-flags and /acl/acl-sets/acl-set/acl-entries/acl-entry/transport/state/
explicit-tcp-flags have the following mapping:
OpenConfig XPath /oc-acl:acl/acl-sets/

acl-set/acl-entries/acl-entry/ OcNOS XPath /acl/acl-sets/acl-set/acl-
transport/config/explicit-tcp-flags entries/acl-entry/ipv4/config/tcp-flags
TCP_ACK ack
TCP_FIN fin
TCP_PSH psh
TCP_RST rst
TCP_SYN syn
TCP_URG urg
TCP_IPI_ESTABLISHED established
Note: This value has been add by OcNOS through
deviation file ipi-oc-acl-
deviations.yang)
Create IPv6 Entries

This XML configuration snippet is used to create an Access Control List (ACL ) entry to operate over IPv6 data traffic.
Release

Here is a sample OpenConfig NetConf Payload to create IPv6 entries.
<acl-sets>
<acl-set>
<type
type>
<config>
<type
type>
</config>
<acl-entries>
<acl-entry>
<config>

</config>
<ipv6>
<config>
<source-address>2000::/8</source-address>
<destination-address>2001::/16</destination-address>
<dscp>23</dscp>
</config>
</ipv6>
<actions>
<config>
<forwarding-action
acl:REJECT</forwarding-action>
</config>
</actions>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
OcNOS CLI Command

This CLI command is used to create IPv6 entries.
ipv6 access-list ACL_OC_IPV6
remark ACL TFW Test
11 deny tcp 2000::/8 2001::/16 dscp 23
!

Here is a sample OcNOS NetConf Payload to create IPv6 entries.
<acl-sets>
<acl-set>
<type>ipv6</type>
<config>
<type>ipv6</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv6>
<config>

<dscp>23</dscp>
<protocol-tcp />
<forwarding-action>deny</forwarding-action>
</config>
</ipv6>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>

Here is a NetConf validation response that provides detailed information about creating IPv6 entries.
<acl-sets>
<acl-set>
<type
type>
<config>
<type
type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv6>
<config>
<dscp>23</dscp>
</config>
</ipv6>
<actions>
<config>
<forwarding-action
acl:REJECT</forwarding-action>
<log-action
</config>
</actions>
</acl-entry>
</acl-entries>

</acl-set>
</acl-sets>
</acl>
Restrictions
• The leaf /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/actions/config/log-action is
only valid on DC platform.
• The old Open Config leaf /oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/transport/
config/tcp-flags was renamed on Open Config v2.0.0, now it is named explicit-tcp-flags. The new xpath is
/oc-acl:acl/acl-sets/acl-set/acl-entries/acl-entry/transport/config/explicit-tcp-
flags.
• OpenConfig leaves /acl/acl-sets/acl-set/acl-entries/acl-entry/transport/config/
explicit-tcp-flags and /acl/acl-sets/acl-set/acl-entries/acl-entry/transport/state/
explicit-tcp-flags have the following mapping:
OpenConfig XPath /oc-acl:acl/acl-sets/

acl-set/acl-entries/acl-entry/ OcNOS XPath /acl/acl-sets/acl-set/acl-
transport/config/explicit-tcp-flags entries/acl-entry/ipv6/config/tcp-flags
TCP_ACK ack
TCP_FIN fin
TCP_PSH psh
TCP_RST rst
TCP_SYN syn
TCP_URG urg
TCP_IPI_ESTABLISHED established
Note: This value has been added by OcNOS through
deviation file ipi-oc-acl-
deviations.yang
Create Interfaces Egress for IPv4/IPv6

This XML configuration snippet is used to associate an Access Control List (ACL) entry type IPv4/IPv6 to an interface
on egress direction.
The interface can associate only one ACL entry at a time.
Release

Here is a sample OpenConfig NetConf Payload to create interfaces egress for IPv4/IPv6.
<interfaces>
<interface>

<id>eth1</id>
<config>
<id>eth1</id>
</config>
<egress-acl-sets>
<egress-acl-set>
<type
acl:ACL_IPV4</type>
<set-name>ACL_OC_IPV4</set-name>
<config>
<type
acl:ACL_IPV4</type>
</config>
</egress-acl-set>
</egress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
OcNOS CLI Command

This CLI command is used to create interfaces egress for IPv4/IPv6.
remark ACL TFW Test
10 permit tcp 1.1.1.0/24 2.2.2.0/24 dscp af21 syn
!
interface eth1
ip access-group ACL_OC_IPV4 out

Here is a sample OcNOS NetConf Payload to create interfaces egress for IPv4/IPv6.
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<egress-acl-sets>
<egress-acl-set>
<acl-type>ip</acl-type>
<access-groups>
<access-group>
<acl-name>ACL_OC_IPV4</acl-name>
<config>

</config>
</access-group>
</access-groups>
<config>
</config>
</egress-acl-set>
</egress-acl-sets>
</interface>
</interfaces>
</acl>

Here is a NetConf validation response that provides detailed information about creating interfaces egress for IPv4/IPv6.
<interfaces>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
<egress-acl-sets>
<egress-acl-set>
<type
acl:ACL_IPV4</type>
<config>
<type
acl:ACL_IPV4</type>
</config>
</egress-acl-set>
</egress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
Restrictions
• Only one ACL entry can be associated on the interface in egress direction.
• The leaf /acl/interfaces/interface/id must have the format “<interface>.<subinterface>”. For example,
xe10.2, and must be limited to 32 characters.

Create Interfaces Ingress for IPv4/IPv6

This XML configuration snippet is used to associate an Access Control List entry type IPv4/IPv6 to an interface on
ingress direction.
Release

Here is a sample OpenConfig NetConf Payload to create interfaces ingress for IPv4/IPv6.
<interfaces>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<type
acl:ACL_IPV4</type>
<config>
<type
acl:ACL_IPV4</type>
</config>
</ingress-acl-set>
</ingress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
OcNOS CLI Command

This CLI command is used to create interfaces ingress for IPv4/IPv6.
remark ACL TFW Test
10 permit tcp 1.1.1.0/24 2.2.2.0/24 dscp af21 syn
!
interface eth1

ip access-group ACL_OC_IPV4 in

Here is a sample OcNOS NetConf Payload to create interfaces ingress for IPv4/IPv6.
<interfaces>
<interface>
<name>eth1</name>
<config>
<name>eth1</name>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<access-groups>
<access-group>
<config>
</config>
</access-group>
</access-groups>
<config>
</config>
</ingress-acl-set>
</ingress-acl-sets>
</interface>
</interfaces>
</acl>

Here is a NetConf validation response that provides detailed information about creating interfaces ingress for IPv4/
IPv6.
<interfaces>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<type
acl:ACL_IPV4</type>
<config>
<type
acl:ACL_IPV4</type>
</config>

</ingress-acl-set>
</ingress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
Restrictions
• Only one ACL entry can be associated on the interface in ingress direction.
Create Interfaces Egress for L2

This XML configuration snippet is used to associate an Access Control List (ACL) entry type L2 to an interface on
egress direction.
Release

Here is a sample OpenConfig NetConf Payload to create interfaces egress for L2.
<interfaces>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
<egress-acl-sets>
<egress-acl-set>
<type
type>
<set-name>ACL_OC_L2</set-name>
<config>
<type
acl:ACL_L2</type>
</config>
</egress-acl-set>
</egress-acl-sets>

<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
OcNOS CLI Command

This CLI command is used to create interfaces egress for L2.
1 permit 0000.CCDD.EEFF AABB.0000.0000 00BB.CCDD.EEFF AC00.0000.0000 ipv4
!
interface eth3
mac access-group ACL_OC_L2 out
!

Here is a sample OcNOS NetConf Payload to create interfaces egress for L2.
<interfaces>
<interface>
<name>eth3</name>
<config>
<name>eth3</name>
</config>
<egress-acl-sets>
<egress-acl-set>
<acl-type>mac</acl-type>
<access-groups>
<access-group>
<acl-name>ACL_OC_L2</acl-name>
<config>
</config>
</access-group>
</access-groups>
<config>
</config>
</egress-acl-set>
</egress-acl-sets>
</interface>
</interfaces>
</acl>

Here is a NetConf validation response that provides detailed information about creating interfaces egress for L2.

<interfaces>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
<egress-acl-sets>
<egress-acl-set>
<type
type>
<config>
<type
acl:ACL_L2</type>
</config>
</egress-acl-set>
</egress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
Restrictions
• Only one ACL entry can be associated on the interface in egress direction.
Create Interfaces Ingress for L2

This XML configuration snippet is used to associate an Access Control List (ACL) entry type L2 to an interface on
ingress direction.
Release

Here is a sample OpenConfig NetConf Payload to create interfaces ingress for L2.
<interfaces>

<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<type
type>
<config>
<type
acl:ACL_L2</type>
</config>
</ingress-acl-set>
</ingress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
OcNOS CLI Command

This CLI command is used to create interfaces ingress for L2.
1 permit 0000.CCDD.EEFF AABB.0000.0000 00BB.CCDD.EEFF AC00.0000.0000 ipv4
!
interface eth3
mac access-group ACL_OC_L2 in
!

Here is a sample OcNOS NetConf Payload to create interfaces ingress for L2.
<interfaces>
<interface>
<name>eth3</name>
<config>
<name>eth3</name>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<access-groups>
<access-group>

<config>
</config>
</access-group>
</access-groups>
<config>
</config>
</ingress-acl-set>
</ingress-acl-sets>
</interface>
</interfaces>
</acl>

Here is a NetConf validation response that provides detailed information about creating interfaces ingress for L2.
<interfaces>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
<ingress-acl-sets>
<ingress-acl-set>
<type
type>
<config>
<type
acl:ACL_L2</type>
</config>
</ingress-acl-set>
</ingress-acl-sets>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</acl>
Restrictions
• Only one ACL entry can be associated on the interface in ingress direction.

QoS OpenConfig Translation
Enable QoS on OcNOS

The below configuration is used to enable QoS on OcNOS.
Release
Configuration
The QoS protocol is enabled by default in OcNOS version 6.5.0. However, the QoS protocol needs to be enabled in the
older versions before configuring QoS features.
Note that there is no equivalent configuration to enable/disable QoS protocol in OpenConfig model.

There is no equivalent configuration in OpenConfig model.
OcNOS CLI command

The below CLI command is used to enable QoS on OcNOS.
OcNOS(config)#qos enable

Here is a sample OcNOS NetConf Payload to enable QoS on OcNOS.
<qos xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-qos">
<global>
<config>
<enable-qos>enable</enable-qos>
</config>
</global>
</qos>

There is no equivalent configuration.

Restrictions
• In OcNOS version 6.5.0, the QoS protocol is already enabled by default.
• In OcNOS versions earlier than 6.5.0, the QoS protocol needs to be enabled before configuring QoS features.
Enable QoS Profile on OcNOS
Release
Configuration
The QoS feature on OcNOS model needs the Hw profile to be enabled on DC Hardware types.
Note that there is no equivalent configuration on OpenConfig model.

OcNOS CLI command

The below CLI command is used to enable QoS Profile on OcNOS.
hardware-profile filter ingress-ipv4-qos enable

Here is the OcNOS NetConf Payload to enable QoS Profile on OcNOS.
<profiles xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<hardware-profile xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<filters xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<config xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<ingress-ipv4-qos/>
</config>
</filters>
</hardware-profile>
</profiles>

Restrictions
None.

Create Classifiers Profiles
Release
Configuration
The OpenConfig QoS Classifiers is a profile responsible for handling data traffic classification.
This configuration does not have a direct equivalent object on OcNOS model. To configure classifier on OcNOS model,
it needs to be translated to Access Control List (ACL), class-maps and policy-maps objects.

Here is a sample OpenConfig NetConf Payload to create Classifiers profiles.
<qos xmlns="http://openconfig.net/yang/qos">
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
<queue-id>0</queue-id>
</config>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
</queue>
</queues>
<queue-management-profiles>
<queue-management-profile>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>
<config>
<min-threshold>128000</min-threshold>
<max-threshold>256000</max-threshold>
</config>
</uniform>
</wred>
</queue-management-profile>
<name>q1</name>
<config>
<name>q1</name>

</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
</queue-management-profiles>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
<output-queue>q0</output-queue>
</config>
</forwarding-group>
</forwarding-groups>
<classifiers>
<classifier>
<name>IN_CUSTOMERIF</name>
<config>
<type>IPV4</type>
</config>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<conditions>
<ipv4>
<config>
<destination-address>2.2.2.2/24</destination-
address>
<dscp>af21</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
<target-group>q0</target-group>
</config>
</actions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<conditions>
<ipv4>
<config>

address>
<dscp>26</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
</config>
</actions>
</term>
</terms>
</classifier>
</classifiers>
</qos>
OcNOS CLI command

The below CLI command is used to create Classifiers profiles for handling data traffic classification.
qos enable
!
ip access-list IN_CUSTOMERIF$10
1 permit tcp 1.1.1.0/24 2.2.2.0/24 dscp af21
!
class-map type qos match-any IN_CUSTOMERIF$10
match access-group IN_CUSTOMERIF$10
!
!
policy-map type qos IN_CUSTOMERIF
class type qos IN_CUSTOMERIF$10
set queue 0
exit
set queue 1
exit
!

Here is a sample OcNOS Netconf Payload to create Classifiers profiles for handling data traffic classification.
<acl-sets>
<acl-set>
<name>IN_CUSTOMERIF$10</name>
<type>ip</type>
<config>
<type>ip</type>

</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>af21</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>af31</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
<global>
<config>
</config>
<class-maps>
<class-map>
<config>
<type>qos</type>

<match-criteria>match-any</match-criteria>
</config>
<match-any-conditions>
<config>
<access-control-list-name>IN_CUSTOMERIF$10</access-control-
list-name>
</config>
</match-any-conditions>
</class-map>
<class-map>
<config>
<type>qos</type>
</config>
<config>
list-name>
</config>
</class-map>
</class-maps>
<policy-maps>
<policy-map>
<policy-map-name>IN_CUSTOMERIF</policy-map-name>
<config>
<type>qos</type>
</config>
<classes>
<class>
<class-map-name>IN_CUSTOMERIF$10</class-map-name>
<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
<class>
<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
</classes>

</policy-map>
</policy-maps>
</global>
</qos>

Here is the NetConf validation response that provides detailed information about creating Classifiers profiles.
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<state>
<type>IPV4</type>
</state>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<state>
<id>10</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>18</dscp>
</config>
<state>
<dscp>18</dscp>
</state>
</ipv4>
</conditions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>

</config>
<state>
<id>20</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>26</dscp>
</config>
<state>
<dscp>26</dscp>
</state>
</ipv4>
</conditions>
</term>
</terms>
</classifier>
</classifiers>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
<wred>
<uniform>
<config>
</config>
<state>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>

<state>
<name>q1</name>
</state>
<wred>
<uniform>
<config>
</config>
<state>
</state>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
</queue>
</queues>
</qos>

Restrictions
All the paths mentioned below have restrictions:
• /qos/interfaces/interface/output/classifiers
This association is not supported on OcNOS model.
• /qos/classifiers/classifier/terms/term/actions/remark
• Path /qos/queue-management-profiles is available on OpenConfig versions above 1.0.0.
• Path /qos/queues was restructured on OpenConfig versions above 1.0.0.
Create Forwarding-groups Profiles
Release
Configuration
The OpenConfig profile Forwarding-group does not have an equivalent model on OcNOS model, so this object is
stored inside Translation Auxiliary Database.
The object name on OpenConfig format allows any string value. However on OcNOS, all forwarding-profiles have fixed
names that follow the pattern q[0-7]. Hence, the Forwarding-groups leaf name must follow this pattern.

Here is a sample OpenConfig NetConf Payload to create Forwarding-groups profiles.
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
<output-queue>q0</output-queue>iority>
</config>
</forwarding-group>
</qos>
OcNOS CLI command




Here is a NetConf validation response that provides detailed information about creating Forwarding-groups profiles.
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>
</qos>
Restrictions
• Paths /qos/forwarding-groups/forwarding-group/name and /qos/forwarding-groups/
forwarding-group/config/name have fixed names that follow the pattern q[0-7].
Create Queues and Queue-Management-profiles Entries
Release
Configuration
The OpenConfig profiles Queues and Queue-Management-Profiles do not have an equivalent model on OcNOS, so
this object is stored inside Translation Auxiliary Database.
These OpenConfig profiles are used to configure on OcNOS model random-detect configuration from policy-map type
queuing object.
The object name on OpenConfig format allows any string value. However on OcNOS, they have fixed names that
follow the pattern q[0-7]. Hence the Queues and Queue-Management-Profiles leaf name must follow this pattern.

Here is a sample OpenConfig NetConf Payload to create Queues and Queue-Management-profiles entries.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>

</config>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
</qos>
OcNOS CLI command




Here is the NetConf response that gives detailed information about creating Queues and Queue-Management-profiles
entries.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
<wred>
<uniform>
<config>
</config>
<state>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
<wred>
<uniform>
<config>
</config>
<state>

</state>
</uniform>
</wred>
</qos>
Restrictions
• Path /qos/queues was restructured on OpenConfig versions above 1.0.0.
• The path /qos/interfaces/interface/output/queues have its association that is not supported on
OcNOS models.
• The path /qos/interfaces/interface/input/queues/queue[name]/config/queue-management-
profile have its association that is not supported on OcNOS models.
• The paths below have fixed leaf names that follow the pattern q[0-7].
• /qos/queues/queue/name
• /qos/queues/queue/config/name
• /qos/queue-management-profiles/queue-management-profile/name
• /qos/queue-management-profiles/queue-management-profile/config/name
Create Scheduler-policies Entries
Release
Configuration
On DC platforms, there are limitations to configure QoS WRED and tail-drops data together. Hence, the Scheduler-
policies entries is divided into ones configured with leaf /openconfig-qos:qos/scheduler-policies/
scheduler-policy/schedulers/scheduler/one-rate-two-color/config/max-queue-depth-bytes
container, and the ones that do not have this leaf.
The scheduler-policies without leaf /openconfig-qos:qos/scheduler-policies/scheduler-policy/
schedulers/scheduler/one-rate-two-color/config/max-queue-depth-bytes, configures the WRED
configuration on OcNOS and sets data based on OpenConfig queue-management-profiles container.
The scheduler-policies with leaf /openconfig-qos:qos/scheduler-policies/scheduler-policy/
schedulers/scheduler/one-rate-two-color/config/max-queue-depth-bytes,configures the tail-drops
configuration on OcNOS. It is based on data set OpenConfig leaf /openconfig-qos:qos/scheduler-policies/
to configure OcNOS leaf /ipi-qos:qos/global/policy-maps/policy-map/classes/class/queue-mode/
tail-drops/tail-drop/config/max-threshold.
The scheduler-policies input configuration for OpenConfig XPath /oc-qos:qos/scheduler-policies/
scheduler-policy/schedulers/scheduler/inputs/input/config now has its leaf queue as mandatory in
operations "create", "delete", "remove" and "merge". This is because the translation mapping done on OcNOS

datamodel to XPath /qos/global/policy-maps/policy-map/classes/class and the queue leaf points to

class-map-name leaf on OcNOS. If this condition is not addressed, the Translation Framework throws an error when
the OpenConfig payload is applied.
Create Scheduler-policies entries without leaf max-queue-depth-

bytes
Release
Configuration
The scheduler-policies without leaf /openconfig-qos:qos/scheduler-policies/scheduler-policy/
schedulers/scheduler/one-rate-two-color/config/max-queue-depth-bytes, configures the WRED
configuration on OcNOS and sets data based on OpenConfig queue-management-profiles container.

Here is a sample OpenConfig NetConf Payload to create Scheduler-policies entries without leaf max-queue-depth-
bytes.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>

<config>
</config>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
</forwarding-group>
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<conditions>
<ipv4>
<config>
address>
<dscp>af21</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>

</config>
</actions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<conditions>
<ipv4>
<config>
address>
<dscp>26</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
</config>
</actions>
</term>
</terms>
</classifier>
</classifiers>
<scheduler-policies>
<scheduler-policy>
<name>SCHEDULER_POLICY_1</name>
<config>
</config>
<schedulers>
<scheduler>
<sequence>10</sequence>
<config>
<type>oc-qos-
types:QOS_SCHEDULER_TYPE:ONE_RATE_TWO_COLOR</type>
<priority>STRICT</priority>
</config>
<inputs>
<input>
<id>SCHEDULER_POLICY_AF1</id>
<config>
<input-type>QUEUE</input-type>
<queue>q0</queue>
<weight>5</weight>
</config>
</input>
</inputs>
</scheduler>
</schedulers>
</scheduler-policy>
</scheduler-policies>

</qos>
OcNOS CLI command

The below CLI command is used to create Scheduler-policies entries without leaf max-queue-depth-bytes.
qos enable
!
!
!
!
set queue 0
exit
set queue 1
exit
!
policy-map type queuing default SCHEDULER_POLICY_1
class type queuing default q0
wrr-queue weight 5
random-detect min-threshold 128000 max-threshold 256000 bytes drop-
probability 80
exit
!

Here is a sample OcNOS NetConf Payload to create Scheduler-policies entries without leaf max-queue-depth-bytes.
<acl-sets>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>

<dscp>af21</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>af31</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
<global>
<config>
<statistics-enabled/>
</config>
<class-maps>
<class-map>
<config>
<type>qos</type>
</config>
<config>
<access-control-list-name>IN_CUSTOMERIF$10</access-control-list-
name>
</config>

</class-map>
<class-map>
<config>
<type>qos</type>
</config>
<config>
name>
</config>
</class-map>
</class-maps>
<policy-maps>
<policy-map>
<config>
<type>qos</type>
</config>
<classes>
<class>
<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
<class>
<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
</classes>
</policy-map>
<policy-map>
<policy-map-name>SCHEDULER_POLICY_1</policy-map-name>
<config>
<type>queuing-default</type>
</config>
<classes>

<class>
<class-map-name>q0</class-map-name>
<config>
</config>
<queue-mode>
<config>
<weighted-round-robin-queue-weight>5</weighted-round-robin-
queue-weight>
</config>
<red>
<wred>
<config>
<threshold-unit>bytes</threshold-unit>
<drop-probability>80</drop-probability>
</config>
</wred>
</red>
</queue-mode>
</class>
</classes>
</policy-map>
<policy-map>
<policy-map-name>subif-default-out-policy</policy-map-name>
<config>
</config>
<classes>
<class>
<config>
</config>
<queue-mode>
<config>
<priority-level>0</priority-level>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>

<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>

</queue-mode>
</class>
</classes>
</policy-map>
</policy-maps>
</global>
</qos>

Here is the NetConf response that gives detailed information about creating Scheduler-policies entries without leaf
max-queue-depth-bytes.
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<state>
<type>IPV4</type>
</state>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<state>
<id>10</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>18</dscp>
</config>
<state>
<dscp>18</dscp>
</state>
</ipv4>
</conditions>

</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<state>
<id>20</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>26</dscp>
</config>
<state>
<dscp>26</dscp>
</state>
</ipv4>
</conditions>
</term>
</terms>
</classifier>
</classifiers>
<scheduler-policy>
<config>
</config>
<state>
</state>
<schedulers>
<scheduler>
<config>
<type
xmlns:oc-qos-types="http://openconfig.net/yang/qos-types">oc-
qos-types:ONE_RATE_TWO_COLOR</type>
</config>
<inputs>
<input>

<config>
<queue>q0</queue>
<weight>5</weight>
</config>
<state>
<weight>5</weight>
<queue>q0</queue>
</state>
</input>
</inputs>
<state>
<type
</state>
</scheduler>
</schedulers>
</scheduler-policy>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
<wred>
<uniform>
<config>
<weight>20</weight>
</config>
<state>
<weight>20</weight>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>

<name>q1</name>
</state>
<wred>
<uniform>
<config>
<weight>10</weight>
</config>
<state>
<weight>10</weight>
</state>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
<fabric-priority>128</fabric-priority>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>

</queue>
</queues>
</qos>
Restrictions
• Path /qos/queues has been restructured on OpenConfig versions above 1.0.0.
• The only valid value for path /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/
config/priority is STRICT.
• The leaf name for path /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/
inputs/input/config/queue have fixed names that follow the pattern q[0-7].
• The scheduler-policies input configuration for OpenConfig XPath /oc-qos:qos/scheduler-policies/
scheduler-policy/schedulers/scheduler/inputs/input/config now has its leaf queue as
mandatory in operations "create", "delete", "remove" and "merge". This is because the translation mapping done
on OcNOS datamodel to XPath /qos/global/policy-maps/policy-map/classes/class and the queue
leaf points to class-map-name leaf on OcNOS. If this condition is not addressed, the Translation Framework
throws an error when the OpenConfig payload is applied.
• All the paths mentioned below have restrictions:
• /qos/interfaces/interface/input/scheduler-policy
This association is not valid on OcNOS and is not supported.
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/output
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/one-rate-two-color/
config/bc
config/cir-pct
This association is not valid on OcNOS and is not supported..
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler
This list has a fixed max-element as one entry.
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/type
This configuration has a fixed value: ONE_RATE_TWO_COLOR.
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/
config/input-type
This configuration has a fixed value: QUEUE.
config/cir-pct-remaining
config/queuing-behavior
This configuration has a fixed value: SHAPE.
config/max-queue-depth-packets

config/max-queue-depth-percent
conform-action
exceed-action
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/two-rate-three-
color
Create Scheduler-policies Entries with leaf max-queue-depth-bytes
Release
Configuration
The scheduler-policies with leaf /openconfig-qos:qos/scheduler-policies/scheduler-policy/
schedulers/scheduler/one-rate-two-color/config/max-queue-depth-bytes,configures the tail-drops
configuration on OcNOS. It is based on data set OpenConfig leaf /openconfig-qos:qos/scheduler-policies/
to configure OcNOS leaf /ipi-qos:qos/global/policy-maps/policy-map/classes/class/queue-mode/
tail-drops/tail-drop/config/max-threshold.

Here is a sample OpenConfig NetConf Payload to create Scheduler-policies entries with leaf max-queue-depth-bytes.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>

</config>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<wred>
<uniform>
<config>
</config>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
</forwarding-group>
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<conditions>
<ipv4>

<config>
address>
<dscp>af21</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
</config>
</actions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<conditions>
<ipv4>
<config>
address>
<dscp>26</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
</config>
</actions>
</term>
</terms>
</classifier>
</classifiers>
<scheduler-policy>
<config>
</config>
<schedulers>
<scheduler>
<config>
<type
xmlns:oc-qos-types="http://openconfig.net/yang/qos-
types">oc-qos-types:ONE_RATE_TWO_COLOR</type>
</config>
<inputs>
<input>

<config>
<queue>q0</queue>
<weight>5</weight>
</config>
</input>
<input>
<config>
<queue>q1</queue>
<weight>14</weight>
</config>
</input>
</inputs>
<one-rate-two-color>
<config>
<max-queue-depth-bytes>64000</max-queue-depth-bytes>
<cir>256000000</cir>
<queuing-behavior>SHAPE</queuing-behavior>
</config>
</one-rate-two-color>
</scheduler>
</schedulers>
</scheduler-policy>
</qos>
OcNOS CLI command

The below CLI command is used to create Scheduler-policies entries with leaf max-queue-depth-bytes.
qos enable
!
!
!
!
set queue 0
exit
set queue 1
exit
!

shape 256000000 kbps

wrr-queue weight 5
queue-limit 64000 bytes
exit
shape 256000000 kbps
wrr-queue weight 14
queue-limit 64000 bytes
exit
!

Here is a sample OcNOS NetConf Payload to create Scheduler-policies entries with leaf max-queue-depth-bytes.
<acl-sets>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>af21</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
<acl-set>
<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>

<dscp>af31</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
<global>
<config>
<statistics-enabled/>
</config>
<class-maps>
<class-map>
<config>
<type>qos</type>
</config>
<config>
name>
</config>
</class-map>
<class-map>
<config>
<type>qos</type>
</config>
<config>
name>
</config>
</class-map>
</class-maps>
<policy-maps>
<policy-map>
<config>
<type>qos</type>
</config>
<classes>
<class>

<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
<class>
<config>
<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
</classes>
</policy-map>
<policy-map>
<config>
</config>
<classes>
<class>
<config>
</config>
<queue-mode>
<config>
queue-weight>
</config>
<tail-drops>
<tail-drop>
<max-threshold-type>bytes</max-threshold-type>
<config>
</config>
</tail-drop>
</tail-drops>
<shapes>
<shape>
<rate-value>256000000</rate-value>
<rate-unit>kbps</rate-unit>

<config>
</config>
</shape>
</shapes>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
queue-weight>
</config>
<tail-drops>
<tail-drop>
<config>
</config>
</tail-drop>
</tail-drops>
<shapes>
<shape>
<config>
</config>
</shape>
</shapes>
</queue-mode>
</class>
</classes>
</policy-map>
<policy-map>
<config>
</config>
<classes>
<class>
<config>
</config>
<queue-mode>

<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>

</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
<class>
<config>
</config>
<queue-mode>
<config>
</config>
</queue-mode>
</class>
</classes>
</policy-map>
</policy-maps>
</global>
</qos>

Here is the NetConf response that gives detailed information about creating Scheduler-policies entries with leaf max-
queue-depth-bytes.
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<state>
<type>IPV4</type>
</state>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<state>
<id>10</id>
</state>
<actions>
<config>
</config>

<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>18</dscp>
</config>
<state>
<dscp>18</dscp>
</state>
</ipv4>
</conditions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<state>
<id>20</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>26</dscp>
</config>
<state>
<dscp>26</dscp>
</state>
</ipv4>
</conditions>
</term>
</terms>
</classifier>
</classifiers>
<scheduler-policy>
<config>

</config>
<state>
</state>
<schedulers>
<scheduler>
<config>
<type
</config>
<inputs>
<input>
<config>
<queue>q0</queue>
<weight>5</weight>
</config>
<state>
<weight>5</weight>
<queue>q0</queue>
</state>
</input>
<input>
<config>
<queue>q1</queue>
<weight>14</weight>
</config>
<state>
<weight>14</weight>
<queue>q1</queue>
</state>
</input>
</inputs>
<state>
<type
</state>
<one-rate-two-color>
<state>

<cir>256000000</cir>
</state>
<config>
<cir>256000000</cir>
</config>
</one-rate-two-color>
</scheduler>
</schedulers>
</scheduler-policy>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
<wred>
<uniform>
<config>
<weight>20</weight>
</config>
<state>
<weight>20</weight>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
<wred>
<uniform>
<config>
<weight>10</weight>
</config>
<state>

<weight>10</weight>
</state>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
</queue>
</queues>
</qos>
Restrictions
• The path /qos/queue-management-profiles is available on Open Config versions above 1.0.0.
• The path /qos/queues has been restructured on Open Config versions above 1.0.0.
• The only valid value for path /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/
config/priority is STRICT.

• The leaf name for path /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/

inputs/input/config/queue must have fixed names that follow the pattern q[0-7].
• The scheduler-policies input configuration for OpenConfig XPath /oc-qos:qos/scheduler-policies/
scheduler-policy/schedulers/scheduler/inputs/input/config now has its leaf queue as
mandatory in operations "create", "delete", "remove" and "merge". This is because the translation mapping done
on OcNOS datamodel to XPath /qos/global/policy-maps/policy-map/classes/class and the queue
leaf points to class-map-name leaf on OcNOS. If this condition is not addressed, the Translation Framework
throws an error when the OpenConfig payload is applied.
• All the paths shown below have restrictions:
• /qos/interfaces/interface/input/scheduler-policy
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/output
config/bc
config/cir-pct
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler
This list has a fixed max-element as one entry.
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/type
This configuration has a fixed value as ONE_RATE_TWO_COLOR.
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/
config/input-type
This configurations has a fixed value as QUEUE.
config/cir-pct-remaining
config/queuing-behavior
This configuration has a fixed value as SHAPE.
config/max-queue-depth-packets
config/max-queue-depth-percent
conform-action

exceed-action
• /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/two-rate-three-
color
Create Interfaces Classifier Association
Release
Configuration
On OpenConfig model, the classifier profile can be associated to an interface on egress and ingress direction, and a list
of classifiers can be associated to an interface. But on OcNOS model, the interface only allows one classifier object,
and the association is in ingress direction.
On OcNOS model, the association between QoS ingress interface and QoS classifier profile needs the hardware-
profile ingress-ipv4-qos to be enabled before the association. The translation adds the hardware-profile
ingress-ipv4-qos configuration during translation on XPath /oc-qos:qos/interfaces/interface/input/
classifiers/classifier/config/name.

Here is a sample OpenConfig NetConf Payload to create an interfaces classifier association.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>
<config>
<weight>20</weight>

<max-drop-probability-percent>90</max-drop-
probability-percent>
</config>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
<output-queue>q0</output-queue
</config>
</forwarding-group>
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<conditions>
<ipv4>
<config>
address>
<dscp>af21</dscp>
</config>
</ipv4>
</conditions>
<actions>
<config>
</config>
</actions>
</term>
</terms>
</classifier>
</classifiers>
<interfaces>
<interface>
<config>
</config>
<interface-ref>
<config>

</config>
</interface-ref>
<input>
<classifiers>
<classifier>
<type>IPV4</type>
<config>
<type>IPV4</type>
</config>
</classifier>
</classifiers>
</input>
</interface>
</interfaces>
</qos>
OcNOS CLI command

hardware-profile filter ingress-ipv4-qos enable
qos enable
!
!
!
set queue 0
exit
set queue 1
exit
!
interface eth2
service-policy type qos input IN_CUSTOMERIF
!

<profiles xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-
platform">
<hardware-profile>
<filters>
<config>
<ingress-ipv4-qos/>
</config>
</filters>
</hardware-profile>
</profiles>
<acl-sets>
<acl-set>

<type>ip</type>
<config>
<type>ip</type>
</config>
<acl-entries>
<acl-entry>
<config>
</config>
<ipv4>
<config>
<dscp>af21</dscp>
<protocol-tcp/>
</config>
</ipv4>
</acl-entry>
</acl-entries>
</acl-set>
</acl-sets>
</acl>
<global>
<config>
</config>
<class-maps>
<class-map>
<config>
<type>qos</type>
</config>
<config>
list-name>
</config>
</class-map>
</class-maps>
<policy-maps>
<policy-map>
<config>
<type>qos</type>
</config>
<classes>
<class>
<config>

<type>qos</type>
</config>
<qos-mode>
<config>
</config>
</qos-mode>
</class>
</classes>
</policy-map>
</policy-maps>
</global>
<interfaces xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-qos-if">
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<service-policy>
<ingress>
<config>
<type-qos-policy-map-name>IN_CUSTOMERIF</type-qos-policy-map-
name>
</config>
</ingress>
</service-policy>
</interface>
</interfaces>

<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<state>
<type>IPV4</type>
</state>
<terms>
<term>
<id>10</id>
<config>
<id>10</id>
</config>
<state>
<id>10</id>
</state>
<actions>
<config>
</config>

<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>18</dscp>
</config>
<state>
<dscp>18</dscp>
</state>
</ipv4>
</conditions>
</term>
<term>
<id>20</id>
<config>
<id>20</id>
</config>
<state>
<id>20</id>
</state>
<actions>
<config>
</config>
<state>
</state>
</actions>
<conditions>
<ipv4>
<config>
<dscp>26</dscp>
</config>
<state>
<dscp>26</dscp>
</state>
</ipv4>
</conditions>
</term>
</terms>
</classifier>
</classifiers>
<interfaces>
<interface>
<config>

</config>
<input>
<classifiers>
<classifier>
<config>
<type>IPV4</type>
</config>
<type>IPV4</type>
<state>
<type>IPV4</type>
</state>
<terms>
<term>
<id>10</id>
<state>
<id>10</id>
<matched-packets>0</matched-packets>
<matched-octets>0</matched-octets>
</state>
</term>
<term>
<id>20</id>
<state>
<id>20</id>
<matched-packets>0</matched-packets>
<matched-octets>0</matched-octets>
</state>
</term>
</terms>
</classifier>
</classifiers>
</input>
<interface-ref>
<config>
</config>
<state>
</state>
</interface-ref>
<state>
</state>
</interface>
</interfaces>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>

<wred>
<uniform>
<config>
<weight>20</weight>
</config>
<state>
<weight>20</weight>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
<wred>
<uniform>
<config>
<weight>10</weight>
</config>
<state>
<weight>10</weight>
</state>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>

<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
</queue>
</queues>
</qos>
Restrictions
• The translation of XPath /oc-qos:qos/interfaces/interface/input/classifiers/classifier/
config/name adds the OcNOS hardware-profile ingress-ipv4-qos configuration.
• Path /qos/queues has been restructured on Open Config versions above 1.0.0.
• All the paths shown below have restrictions:
• /qos/interfaces/interface/input/classifiers
Only one entry can be inserted on this list.
• /qos/interfaces/interface/output/classifiers
• /qos/interfaces/interface/interface-id
This leaf must have the format “<interface>.<subinterface>”, e.g., xe10.2, and it is limited to 32 characters.
Create Interfaces Scheduler-policies Association
Release

Configuration
On OpenConfig model, the Scheduler-policies profile can be associated to an interface on egress and ingress
direction.
But on OcNOS model, the interface only allows one scheduler-policies object, and the association is in ingress
direction.

Here is a sample OpenConfig NetConf Payload to create interfaces scheduler-policies association.
<queues>
<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
</queue>
</queues>
<name>q0</name>
<config>
<name>q0</name>
</config>
<wred>
<uniform>
<config>
<weight>20</weight>
<max-drop-probability-percent>90</max-drop-
probability-percent>
</config>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
</forwarding-group>
<scheduler-policy>
<config>
</config>
<schedulers>

<scheduler>
<config>
<type>ONE_RATE_TWO_COLOR</type>
</config>
<inputs>
<input>
<config>
<queue>q0</queue>
<weight>5</weight>
</config>
</input>
</inputs>
</scheduler>
</schedulers>
</scheduler-policy>
<interfaces>
<interface>
<config>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<output>
<scheduler-policy>
<config>
</config>
</scheduler-policy>
</output>
</interface>
</interfaces>
</qos>
OcNOS CLI command

The below CLI command is used to create interfaces scheduler-policies association.
qos enable
!
wrr-queue weight 5
random-detect min-threshold 128000 max-threshold 256000 bytes drop-
probability 80
exit
!

interface eth2
service-policy type queuing output SCHEDULER_POLICY_1
!

Here is a sample OcNOS NetConf Payload to create interfaces scheduler-policies association.
<global>
<config>
</config>
<policy-maps>
<policy-map>
<config>
</config>
<classes>
<class>
<config>
</config>
<queue-mode>
<config>
<weighted-round-robin-queue-weight>5</weighted-round-
robin-queue-weight>
</config>
<red>
<wred>
<config>
<threshold-unit>bytes</threshold-unit>
<drop-probability>80</drop-probability>
</config>
</wred>
</red>
</queue-mode>
</class>
</classes>
</policy-map>
</policy-maps>
</global>
<interfaces xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-qos-if">
<interface>
<name>eth2</name>
<config>
<name>eth2</name>
</config>
<service-policy>
<egress>
<config>

<type-queuing-policy-map-name>SCHEDULER_POLICY_1</type-
queuing-policy-map-name>
</config>
</egress>
</service-policy>
</interface>
</interfaces>
</qos>

Here is a NetConf validation response that provides detailed information about creating interfaces scheduler-policies
association.
<scheduler-policy>
<config>
</config>
<state>
</state>
<schedulers>
<scheduler>
<config>
<type
</config>
<inputs>
<input>
<config>
<queue>q0</queue>
<weight>5</weight>
</config>
<state>
<weight>5</weight>
<queue>q0</queue>
</state>
</input>
</inputs>
<state>
<type

</state>
</scheduler>
</schedulers>
</scheduler-policy>
<interfaces>
<interface>
<config>
</config>
<output>
<scheduler-policy>
<config>
</config>
<state>
</state>
<schedulers>
<scheduler>
<state>
<conforming-octets>0</conforming-octets>
<conforming-pkts>0</conforming-pkts>
<exceeding-octets>0</exceeding-octets>
<exceeding-pkts>0</exceeding-pkts>
</state>
</scheduler>
</schedulers>
</scheduler-policy>
</output>
<interface-ref>
<config>
</config>
<state>
</state>
</interface-ref>
<state>
</state>
</interface>
</interfaces>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
<wred>
<uniform>

<config>
<weight>20</weight>
</config>
<state>
<weight>20</weight>
</state>
</uniform>
</wred>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
<wred>
<uniform>
<config>
<weight>10</weight>
</config>
<state>
<weight>10</weight>
</state>
</uniform>
</wred>
<forwarding-groups>
<forwarding-group>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</forwarding-group>
<queues>

<queue>
<name>q0</name>
<config>
<name>q0</name>
</config>
<state>
<name>q0</name>
</state>
</queue>
<queue>
<name>q1</name>
<config>
<name>q1</name>
</config>
<state>
<name>q1</name>
</state>
</queue>
</queues>
</qos>
Restrictions
• The path /qos/queue-management-profiles is available on Open Config versions above 1.0.0.
• The path /qos/queues has been restructured on OpenConfig versions above 1.0.0.
• The path /qos/interfaces/interface/interface-id has the following restriction:
• It must be in the format <interface>.<subinterface> For example: xe10.2, and limited to 32 characters.

EVPN Openconfig Translation
Configure EVPN-MAC with inter-instance-policies

This XML configuration snippet is used to configure EVPN-MAC with inter-instance-policies.Use the below commands
to configure only the MAC-VRF entry with route-target configured.
Release

Here is a sample OpenConfig NetConf Payload to configure only the MAC-VRF entry with route-target configured.
<network-instance>
<name>object-test</name>
<config>
</config>
<encapsulation>
<config>
<encapsulation-type>MPLS</encapsulation-type>
</config>
</encapsulation>
<inter-instance-policies>
<import-export-policy>
<config>
<export-route-target>6:6</export-route-target>
<import-route-target>6:6</import-route-target>
</config>
</import-export-policy>
</inter-instance-policies>
</network-instance>
OcNOS CLI Command

The below CLI is used to configure only the MAC-VRF entry with route-target configured.
mac vrf object-test
router-id 102.143.73.1
rd 102.143.73.1:2

route-target export 3:3

route-target both 6:6
!

Here is a sample of OcNOS NetConf Payload to configure only the MAC-VRF entry with route-target configured.
instance">
<network-instance>
<instance-name>object-test</instance-name>
<instance-type>mac-vrf</instance-type>
<config>
<instance-name>object-test</instance-name>
</config>
<config>
<vrf-name>object-test</vrf-name>
</config>
<config>
</config>
<route-target>
<rt-rd-string>3:3</rt-rd-string>
<config>
<direction>export</direction>
</config>
</route-target>
<route-target>
<config>
<direction>import export</direction>
</config>
</route-target>
</bgp-vrf>
</vrf>
</network-instance>

Here is a NetConf validation response that provides information about configuring only the MAC-VRF entry with route-
target configured.
<network-instance>
<config>
<type

</config>
<encapsulation>
<config>
<encapsulation-type
types">oc-ni-types:MPLS</encapsulation-type>
</config>
<state>
<encapsulation-type
</state>
</encapsulation>
<state>
<type
</state>
<config>
</config>
<state>
</state>
</network-instance>
Restrictions
• MAC-VRF entry cannot be configured by OpenConfig without route-target.
• The leaves mentioned below must be configured:
• network-instances/network-instance/config/router-id
• network-instances/network-instance/config/route-distinguisher
Configure EVPN-VPLS type

This XML configuration snippet is used to configure EVPN-VPLS type.

Release
Initial Configuration:
Here is the initial configuration necessary to be implemented before applying EVPN-VPLS configuration.
router ldp
!
interface lo
!
interface eth4
ip address 10.255.128.8/31
label-switching
enable-ldp ipv4
!
interface eth2.1001 switchport
!
router ospf 100
area 0.0.0.0 interface lo
OcNOS CLI Command

The below CLI command is used to configure EVPN-VPLS type.
evpn mpls enable
!
mac vrf vpls1001
router-id 10.143.73.1
rd 10.143.73.1:1001
!
evpn mpls vtep-ip-global 10.143.73.1
!
evpn mpls id 1001
host-reachability-protocol evpn-bgp vpls1001
!
access-if-evpn
map vpn-id 1001
!
router bgp 65010
neighbor 10.143.73.3 update-source lo
!
address-family l2vpn evpn
exit-address-family


Here is a sample OcNOS NetConf Payload to configure EVPN-VPLS type.
instance">
<network-instance>
<config>
</config>
</vrf>
<config>
</config>
</network-instance>
<network-instance>
<instance-name>vpls1001</instance-name>
<config>
<instance-name>vpls1001</instance-name>
</config>
<config>
<vrf-name>vpls1001</vrf-name>
</config>
<config>
</config>
<route-target>
<config>
</config>
</route-target>
</bgp-vrf>
</vrf>
</network-instance>
<bgp-instance>
<config>
</config>
<peer>
<config>
<source-identifier>lo</source-identifier>

</config>
<address-family>
<afi>l2vpn</afi>
<safi>evpn</safi>
<config>
<afi>l2vpn</afi>
<safi>evpn</safi>
<activate />
</config>
</address-family>
</peer>
<address-family>
<afi>l2vpn</afi>
<safi>evpn</safi>
<config>
<afi>l2vpn</afi>
<safi>evpn</safi>
</config>
</address-family>
</bgp-instance>
</bgp>
<evpn-mpls xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-evpn-mpls">
<mpls-tenant>
<tenant-identifier>1001</tenant-identifier>
<config>
<vrf-name>vpls1001</vrf-name>
</config>
</mpls-tenant>
<global>
<config>
<enable-evpn-mpls />
<vtep-ipv4>10.143.73.1</vtep-ipv4>
</config>
</global>
</evpn-mpls>
<evpn xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-ethernet-vpn">
<interfaces>
<interface>
<config>
</config>
<access-interfaces>
<access-interface>
<access-if>access-if-evpn</access-if>
<config>
<evpn-identifier>1001</evpn-identifier>
</config>
</access-interface>
</access-interfaces>
</interface>
</interfaces>
</evpn>
<interface>

<config>
</config>
</interface>
</interfaces>

Here is a sample OpenConfig NetConf Payload to configure EVPN-VPLS type.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
</protocol>
<protocol>
<identifier
<name>100</name>
<ospfv2>
<global>
<config>
<log-adjacency-changes>false</log-adjacency-changes>
</config>
</global>
<areas>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>

</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
<config>
<identifier
<name>100</name>
</config>
</protocol>
<protocol>
<identifier
<name>65010</name>
<bgp>
<global>
<config>
<as>65010</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
types">oc-bgp-types:L2VPN_EVPN</afi-safi-name>
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<neighbors>
<neighbor>

<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
</config>
<transport>
<config>
<local-address>lo</local-address>
</config>
</transport>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>65010</name>
</config>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family

<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>

<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
types:MPLS</address-family>
<config>
<protocol
<address-family
types">oc-types:MPLS</address-family>
</config>
</table>
</tables>
</network-instance>
<network-instance>
<name>vpls1001</name>
<config>
<type

</config>
<encapsulation>
<config>
<encapsulation-type
</config>
</encapsulation>
<config>
</config>
<connection-points>
<connection-point>
<connection-point-id>1001</connection-point-id>
<config>
</config>
<endpoints>
<endpoint>
<endpoint-id>1001</endpoint-id>
<config>
</config>
<local>
<config>
</config>
</local>
<remote/>
</endpoint>
</endpoints>
</connection-point>
</connection-points>
<evpn>
<evpn-instances>
<evpn-instance>
<evi>1001</evi>
<config>
<evi>1001</evi>
<encapsulation-type
xmlns:oc-ni-types="http://openconfig.net/yang/network-
instance-types">oc-ni-types:MPLS</encapsulation-type>
</config>
</evpn-instance>
</evpn-instances>
</evpn>
</network-instance>


Here is a NetConf validation response that provides detailed information about configuring EVPN-VPLS type.
<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
types:OSPF</identifier>
<name>100</name>
<ospfv2>
<global>
<config>
</config>
<state>
</state>
</global>
<areas>
<area>

<config>
</config>
<state>
</state>
<interfaces>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
<id>eth4</id>
</state>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
<id>lo</id>
</state>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
<config>
<identifier
<name>100</name>
</config>
</protocol>
<protocol>
<identifier
<name>65010</name>
<bgp>
<global>
<config>
<as>65010</as>

</config>
<state>
<as>65010</as>
</state>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<add-paths>
<state>
<receive>false</receive>
<send>false</send>
</state>
</add-paths>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>

<transport>
<config>
</config>
<state>
</state>
</transport>
<state>
</state>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>65010</name>
</config>
<state>
<identifier
<name>65010</name>
</state>
</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>

<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
types:STATIC</protocol>
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
types:OSPF</protocol>

<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>

<state>
<protocol
<address-family
</state>
</table>
</tables>
<interfaces>
<interface>
<id>eth0</id>
<config>
<id>eth0</id>
</config>
<state>
<id>eth0</id>
</state>
</interface>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
<state>
<id>eth1</id>
</state>
</interface>
<interface>
<id>eth2</id>
<config>
<id>eth2</id>
</config>
<state>
<id>eth2</id>
</state>
</interface>
<interface>
<id>eth2.1001</id>
<config>
<id>eth2.1001</id>
</config>
<state>
<id>eth2.1001</id>
</state>
</interface>

<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
<state>
<id>eth3</id>
</state>
</interface>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
<state>
<id>eth4</id>
</state>
</interface>
<interface>
<id>eth5</id>
<config>
<id>eth5</id>
</config>
<state>
<id>eth5</id>
</state>
</interface>
<interface>
<id>eth6</id>
<config>
<id>eth6</id>
</config>
<state>
<id>eth6</id>
</state>
</interface>
<interface>
<id>eth7</id>
<config>
<id>eth7</id>
</config>
<state>
<id>eth7</id>
</state>
</interface>
<interface>
<id>eth8</id>

<config>
<id>eth8</id>
</config>
<state>
<id>eth8</id>
</state>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
<state>
<id>lo</id>
</state>
</interface>
</interfaces>
<mpls>
<signaling-protocols>
<ldp>
<interface-attributes>
<interfaces>
<interface>
<config>
</config>
<address-families>
<address-family>
<afi-name>IPV4</afi-name>
<config>
</config>
</address-family>
<address-family>
<config>
</config>
</address-family>
</address-families>
</interface>
</interfaces>
</interface-attributes>
</ldp>
</signaling-protocols>
<global>
<interface>
<config>

<mpls-enabled>true</mpls-enabled>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
</state>
</interface>
</global>
</mpls>
</network-instance>
<network-instance>
<config>
<type
</config>
<encapsulation>
<config>
<encapsulation-type
</config>
<state>
<encapsulation-type
</state>
</encapsulation>
<state>
<type
</state>
<config>
</config>
<state>
</state>

<connection-points>
<connection-point>
<config>
</config>
<endpoints>
<endpoint>
<config>
</config>
<state>
</state>
<local>
<config>
</config>
<state>
</state>
</local>
<remote/>
</endpoint>
</endpoints>
<state>
</state>
</connection-point>
<evpn>
<evpn-instances>
<evpn-instance>
<evi>1001</evi>
<config>
<evi>1001</evi>
<encapsulation-type
</config>
<state>
<evi>1001</evi>
<encapsulation-type
</state>
</evpn-instance>
</evpn-instances>
</evpn>
</network-instance>

Restrictions
• The paths mentioned below do not have a translation from OpenConfig model to OcNOS model. If you try to apply
a configuration using only these paths, it will not be applied on OcNOS side.
/network-instances/network-instance/connection-points
/network-instances/network-instance/connection-points/connection-point/endpoints
Those containers are used only to handle “virtual-circuit-identifier” attribute and “local” container, and the
configuration is translated only when those attributes are configured.
• /network-instances/network-instance/connection-points
The deletion of this attribute only deletes the configurations of "virtual-circuit-identifier" and "local" container. To
delete all configuration from "evpn-mpls" container, the delete operation must be placed on the path:
/network-instances/network-instance/evpn/evpn-instances/evpn-instance[evi].
Configure EVPN-VPWS type

This XML configuration snippet is used to configure EVPN-VPWS type.
Release
Initial Configuration:
Here is the initial configuration necessary to be implemented before configuring EVPN-VPWS type.
router ldp
!
interface lo
!
interface eth4
ip address 10.255.128.8/31
label-switching
enable-ldp ipv4
!
!
router ospf 100
area 0.0.0.0 interface lo
OcNOS CLI Command

The below CLI command is used to configure EVPN-VPWS type.
evpn mpls enable
!
mac vrf vrf2

router-id 10.143.73.1
rd 10.143.73.1:2
!
evpn mpls vtep-ip-global 10.143.73.1
!
evpn mpls id 2 xconnect target-mpls-id 252
host-reachability-protocol evpn-bgp vrf2
!
access-if-evpn
map vpn-id 2
!
router bgp 65010
neighbor 10.143.73.3 update-source lo
!
address-family l2vpn evpn
exit-address-family

Here is a sample OcNOS NetConf Payload to configure EVPN-VPWS type.
instance">
<network-instance>
<config>
</config>
</vrf>
<config>
</config>
</network-instance>
<network-instance>
<instance-name>vrf2</instance-name>
<config>
<instance-name>vrf2</instance-name>
</config>
<config>
<vrf-name>vrf2</vrf-name>
</config>
<config>
</config>
<route-target>

<config>
</config>
</route-target>
</bgp-vrf>
</vrf>
</network-instance>
<bgp-instance>
<config>
</config>
<peer>
<config>
<source-identifier>lo</source-identifier>
</config>
<address-family>
<afi>l2vpn</afi>
<safi>evpn</safi>
<config>
<afi>l2vpn</afi>
<safi>evpn</safi>
<activate />
</config>
</address-family>
</peer>
<address-family>
<afi>l2vpn</afi>
<safi>evpn</safi>
<config>
<afi>l2vpn</afi>
<safi>evpn</safi>
</config>
</address-family>
</bgp-instance>
</bgp>
<evpn-mpls xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-evpn-mpls">
<mpls-tenant>
<config>
<vrf-name>vrf2</vrf-name>
<vpws-identifier>252</vpws-identifier>
</config>
</mpls-tenant>
<global>
<config>
<enable-evpn-mpls />
<vtep-ipv4>10.143.73.1</vtep-ipv4>
</config>

</global>
</evpn-mpls>
<evpn xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-ethernet-vpn">
<interfaces>
<interface>
<name>eth2.2</name>
<config>
<name>eth2.2</name>
</config>
<access-interfaces>
<access-interface>
<config>
<evpn-identifier>2</evpn-identifier>
</config>
</access-interface>
</access-interfaces>
</interface>
</interfaces>
</evpn>
<interface>
<name>eth2.2</name>
<config>
</config>
</interface>
</interfaces>NetConf

Here is a sample OpenConfig NetConf Payload to configure EVPN-VPWS type.
<network-instance>
<config>
<type
</config>
<protocols>
<protocol>
<identifier
<config>
<identifier
</config>

</protocol>
<protocol>
<identifier
<name>100</name>
<ospfv2>
<global>
<config>
</config>
</global>
<areas>
<area>
<config>
</config>
<interfaces>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
<config>
<identifier
<name>100</name>
</config>
</protocol>
<protocol>
<identifier

<name>65010</name>
<bgp>
<global>
<config>
<as>65010</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
</global>
<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
</afi-safi>
</afi-safis>
<config>
</config>
<transport>
<config>
</config>
</transport>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>65010</name>
</config>

</protocol>
</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>

<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol

<address-family
<config>
<protocol
<address-family
</config>
</table>
</tables>
</network-instance>
<network-instance>
<name>vrf2</name>
<config>
<name>vrf2</name>
<type
</config>
<encapsulation>
<config>
<encapsulation-type
</config>
</encapsulation>
<config>
</config>
<connection-points>
<connection-point>
<config>
</config>
<endpoints>
<endpoint>
<config>
</config>
<local>
<config>
</config>

</local>
<remote>
<config>
<virtual-circuit-identifier>252</virtual-circuit-identifier>
</config>
</remote>
</endpoint>
</endpoints>
</connection-point>
<evpn>
<evpn-instances>
<evpn-instance>
<evi>2</evi>
<config>
<evi>2</evi>
<encapsulation-type
</config>
</evpn-instance>
</evpn-instances>
</evpn>
</network-instance>

Here is a NetConf validation response that provides detailed information about configuring EVPN-VPWS type.
<network-instance>
<config>
<type
</config>
<state>
<type
</state>
<protocols>
<protocol>
<identifier
<config>
<identifier

</config>
<state>
<identifier
</state>
</protocol>
<protocol>
<identifier
<name>100</name>
<ospfv2>
<global>
<config>
</config>
<state>
</state>
</global>
<areas>
<area>
<config>
</config>
<state>
</state>
<interfaces>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
<id>eth4</id>
</state>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>
<interface-ref>
<config>

</config>
</interface-ref>
<state>
<id>lo</id>
</state>
</interface>
</interfaces>
</area>
</areas>
</ospfv2>
<config>
<identifier
<name>100</name>
</config>
</protocol>
<protocol>
<identifier
<name>65010</name>
<bgp>
<global>
<config>
<as>65010</as>
</config>
<state>
<as>65010</as>
</state>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<add-paths>
<state>
<receive>false</receive>
<send>false</send>
</state>
</add-paths>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
</global>

<neighbors>
<neighbor>
<afi-safis>
<afi-safi>
<afi-safi-name
<config>
<afi-safi-name
</config>
<state>
<afi-safi-name
</state>
</afi-safi>
</afi-safis>
<config>
</config>
<transport>
<config>
</config>
<state>
</state>
</transport>
<state>
</state>
</neighbor>
</neighbors>
</bgp>
<config>
<identifier
<name>65010</name>
</config>
<state>
<identifier
<name>65010</name>
</state>
</protocol>

</protocols>
<tables>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
<table>
<protocol
<address-family
<config>
<protocol

<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol

<address-family
<config>
<protocol
<address-family
</config>
</table>
<table>
<protocol
<address-family
<config>
<protocol
<address-family
</config>
<state>
<protocol
<address-family
</state>
</table>
</tables>
<interfaces>
<interface>
<id>eth0</id>
<config>
<id>eth0</id>
</config>
</interface>
<interface>
<id>eth1</id>
<config>
<id>eth1</id>
</config>
</interface>
<interface>
<id>eth2</id>
<config>
<id>eth2</id>
</config>

</interface>
<interface>
<id>eth2.2</id>
<config>
<id>eth2.2</id>
</config>
</interface>
<interface>
<id>eth3</id>
<config>
<id>eth3</id>
</config>
</interface>
<interface>
<id>eth4</id>
<config>
<id>eth4</id>
</config>
</interface>
<interface>
<id>eth5</id>
<config>
<id>eth5</id>
</config>
</interface>
<interface>
<id>eth6</id>
<config>
<id>eth6</id>
</config>
</interface>
<interface>
<id>eth7</id>
<config>
<id>eth7</id>
</config>
</interface>
<interface>
<id>eth8</id>
<config>
<id>eth8</id>
</config>
</interface>
<interface>
<id>lo</id>
<config>
<id>lo</id>
</config>

</interface>
</interfaces>
<mpls>
<signaling-protocols>
<ldp>
<interfaces>
<interface>
<config>
</config>
<address-families>
<address-family>
<config>
</config>
</address-family>
<address-family>
<config>
</config>
</address-family>
</address-families>
</interface>
</interfaces>
</ldp>
</signaling-protocols>
<global>
<interface>
<config>
</config>
<interface-ref>
<config>
</config>
</interface-ref>
<state>
</state>
</interface>
</global>
</mpls>
</network-instance>
<network-instance>
<name>vrf2</name>
<config>

<name>vrf2</name>
<type
</config>
<encapsulation>
<config>
<encapsulation-type
</config>
<state>
<encapsulation-type
</state>
</encapsulation>
<state>
<name>vrf2</name>
<type
</state>
<config>
</config>
<state>
</state>
<connection-points>
<connection-point>
<config>
</config>
<endpoints>
<endpoint>
<config>
</config>
<state>
</state>
<local>
<config>

</config>
<state>
</state>
</local>
<remote>
<config>
</config>
<state>
</state>
</remote>
</endpoint>
</endpoints>
<state>
</state>
</connection-point>
<evpn>
<evpn-instances>
<evpn-instance>
<evi>2</evi>
<config>
<evi>2</evi>
<encapsulation-type
</config>
<state>
<evi>2</evi>
<encapsulation-type
</state>
</evpn-instance>
</evpn-instances>
</evpn>
</network-instance>
Restrictions
• Since there is no equivalent in OpenConfig, and there is no obligation to have the configuration set in any case for
the leaf /evpn-mpls/global/config/vtep-ipv4 this leaf (vtep-ipv4) is no longer supported in the
translation. If you want to set the configuration, you must use the OcNOS namespace.
• The paths mentioned below do not have a translation from OpenConfig model to OcNOS model. If you try to apply
a configuration using only these paths, it will not be applied on OcNOS side.
• /network-instances/network-instance/connection-points
• /network-instances/network-instance/connection-points/connection-point/endpoints
Those containers are used only to handle virtual-circuit-identifier attribute and local container, and the
configuration is translated only when those attributes are configured.

• /network-instances/network-instance/connection-point
The deletion of this attribute only deletes the configurations of virtual-circuit-identifier and local container. To
delete all configuration from evpn-mpls container, the delete operation must be placed on the path:
/network-instances/network-instance/evpn/evpn-instances/evpn-instance

OpenZR+ OpenConfig Translation
General Restrictions
Operation create
NETCONF’s operation="create" only supports objectlist elements, for example: components/
component[name]or /terminal-device/logical-channels/channel[index].
Payloads with this operation on other elements have undefined behavior.
Operation merge and create

• It is not possible to create or merge a single instance of an OpenConfig component for OpenZR+ (module or
optical channel) without some other valid configuration as OcNOS does not accept it.
• The creation or merging of the OpenConfig logical-channel instance for OpenZR+ must also be accompanied by
the configuration of loopback-mode.
Laser frequency configuration in OpenZR+ media channel

• It is not possible to separately configure the grid, channel and fine-tune-frequency for laser configuration in a media
channel for OpenZR+ in OpenConfig. The configuration of only the total frequency value is possible.
• In this way the central frequency is fixed at 193.1 THz and the grid is fixed at 100 GHz. With these values it is
possible to calculate the channel and fine-tune-frequency for OcNOS.
Disable/enable OpenZR+ transceiver

This XML configuration snippet is used to disable/enable OpenZR+ transceiver.
Release
Disable configuration
Here are the configuration details to disable OpenZR+ transceiver.

Here is a sample OpenConfig NetConf Payload to disable OpenZR+ transceiver.
<config>
<component>

<name>CMIS-MODULE-50</name><config>
<name>CMIS-MODULE-50</name>
</config>
<config>
</config>
</transceiver>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to disable OpenZR+ transceiver.
qsfp-dd 50
service-disable

Here is a sample OcNOS NetConf Payload to disable OpenZR+ transceiver.
<qsfp-dds xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-platform">
<qsfp-dd>
<fp-port>50</fp-port>
<config>
<service-disable />
</config>
</qsfp-dd>
</qsfp-dds>
Enable configuration
Here are the configuration steps to enable OpenZR+ transceiver.

Here is a sample OpenConfig NetConf Payload to enable OpenZR+ transceiver.
<config>
<component>
<name>CMIS-MODULE-50</name><config>
</config>
<config>
</config>
</transceiver>
</component>
</components>
</config>

OcNOS CLI Command

The below CLI command is used to enable OpenZR+ transceiver.
qsfp-dd 50
no service-disable

Here is a sample OcNOS NetConf Payload to enable OpenZR+ transceiver.
<qsfp-dd>
<config>
<service-disable operation="delete" />
</config>
</qsfp-dd>
</qsfp-dds>
Configure OpenZR+ optical channel operational mode

This XML configuration snippet is used to configure OpenZR+ optical channel operational mode.
Release

Here is a sample OpenConfig NetConf Payload to configure OpenZR+ optical channel operational mode.
<config>
<component>
<config>
</config>
<optical-channel>
<config>
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI is used to configure OpenZR+ optical channel operational mode.

qsfp-dd 50
application 10

Here is a sample OcNOS NetConf Payload to configure OpenZR+ optical channel operational mode.
<qsfp-dd>
<config>
<application>10</application>
</config>
</qsfp-dd>
</qsfp-dds>
Unconfiguration
Here are the commands to unconfigure OpenZR+ channel operational mode.

Here is a sample OpenConfig NetConf Payload to unconfigure OpenZR+ optical channel operational mode.
<config>
<component>
<optical-channel>
<config>
<operational-mode operation="delete" />
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI is used to unconfigure OpenZR+ optical channel operational mode.
qsfp-dd 50
no application

Here is a sample OcNOS NetConf Payload to unconfigure OpenZR+ optical channel operational mode.
<qsfp-dd>
<config>
<application operation="delete" />
</config>

</qsfp-dd>
</qsfp-dds>
Configure OpenZR+ optical channel target output power

This XML configuration snippet is used to configure OpenZR+ optical channel target output power.
Release

Here is a sample OpenConfig NetConf Payload to configure OpenZR+ optical channel target output power.
<config>
<component>
<config>
</config>
<optical-channel>
<config>
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to configure OpenZR+ optical channel target output power.
qsfp-dd 50
media-lane 1
laser output-power 1.00

Here is a sample OcNOS NetConf Payload to configure OpenZR+ optical channel target output power.
<qsfp-dd>
<config>
</config>
<media>
<lanes>
<lane>
<lane-number>1</lane-number>

<laser>
<config>
</config>
</laser>
</lane>
</lanes>
</media>
</qsfp-dd>
</qsfp-dds>
Unconfiguration
Here are the commands to unconfigure OpenZR+ channel target output power.

Here is a sample OpenConfig NetConf Payload to unconfigure OpenZR+ optical channel target output power.
<config>
<component>
<optical-channel>
<config>
<target-output-power operation="delete" />
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to unconfigure OpenZR+ optical channel target output power.
qsfp-dd 50
media-lane 1
no laser output-power

Here is a sample OcNOS NetConf Payload to unconfigure OpenZR+ optical channel target output power.
<qsfp-dd>
<media>
<lanes>
<lane>
<laser>
<config>
<output-power operation="delete" />
</config>

</laser>
</lane>
</lanes>
</media>
</qsfp-dd>
</qsfp-dds>
Configure OpenZR+ optical channel frequency

This XML configuration snippet is used to configure OpenZR+ optical channel frequency.
Release

Here is a sample OpenConfig NetConf Payload to configure OpenZR+ optical channel frequency.
<config>
<component>
<config>
</config>
<optical-channel>
<config>
<frequency>191300005</frequency>
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to configure OpenZR+ optical channel frequency.
qsfp-dd 50
media-lane 1
laser grid 100
laser channel -18
laser fine-tune-freq 0.005

Here is a sample OcNOS NetConf Payload to configure OpenZR+ optical channel frequency.
<qsfp-dd>
<config>

</config>
<media>
<lanes>
<lane>
<laser>
<config>
<channel>-18</channel>
<grid>100</grid>
<fine-tune-freq>0.005</fine-tune-freq>
</config>
</laser>
</lane>
</lanes>
</media>
</qsfp-dd>
</qsfp-dds>
Unconfiguration
Here are the commands to unconfigure OpenZR+ optical channel frequency.

Here is a sample OpenConfig NetConf Payload to unconfigure OpenZR+ optical channel frequency.
<config>
<component>
<optical-channel>
<config>
<frequency operation="delete" />
</config>
</optical-channel>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to unconfigure OpenZR+ optical channel frequency.
qsfp-dd 50
media-lane 1
no laser grid
no laser channel
no laser fine-tune-freq

Here is a sample OcNOS NetConf Payload to unconfigure OpenZR+ optical channel frequency.

<qsfp-dd>
<media>
<lanes>
<lane>
<laser>
<config>
<channel operation="delete" />
<grid operation="delete" />
<fine-tune-freq operation="delete" />
</config>
</laser>
</lane>
</lanes>
</media>
</qsfp-dd>
</qsfp-dds>
Configure OpenZR+ loopback mode

This XML configuration snippet is used to configure OpenZR+ loopback mode.
Release

Here is a sample OpenConfig NetConf Payload to configure OpenZR+ loopback mode.
<config>
<logical-channels>
<channel>
<config>
<loopback-mode>TERMINAL</loopback-mode>
</config>
</channel>
</logical-channels>
</terminal-device>
</config>
OcNOS CLI Command

The below CLI command is used to configure OpenZR+ loopback mode.
qsfp-dd 50
loopback in media


Here is a sample OcNOS NetConf Payload to configure OpenZR+ loopback mode.
<qsfp-dd>
<config>
</config>
<media>
<loopback>
<config>
<type>in</type>
</config>
</loopback>
</media>
</qsfp-dd>
</qsfp-dds>
Unconfiguration
Here are the commands to unconfigure OpenZR+ loopback mode.

Here is a sample OpenConfig NetConf Payload to unconfigure OpenZR+ loopback mode.
<config>
<logical-channels>
<channel>
<config>
<loopback-mode operation="delete" />
</config>
</channel>
</logical-channels>
</terminal-device>
</config>
OcNOS CLI Command

The below CLI command is used to unconfigure OpenZR+ loopback mode.
qsfp-dd 50
no loopback media

Here is a sample OcNOS NetConf Payload to unconfigure OpenZR+ loopback mode.
<qsfp-dd>

<media>
<loopback>
<config>
<type operation="delete" />
</config>
</loopback>
</media>
</qsfp-dd>
</qsfp-dds>
Validate OpenZR+ module state

Use these commands to validate OpenZR+ module state.
Release

<config>
<component>
<state />
</component>
</components>
</config>

This validation response provides information on the configuration and runtime for validating OpenZR+ module state.
<component>
<state>
<id>CMIS-MODULE-50</id>
<type>oc-platform-types:TRANSCEIVER</type>
<mfg-name>SmartOptics</mfg-name>
<mfg-date>2022-03-18</mfg-date>
<description>CMIS Transceiver</description>
<hardware-version>49.48</hardware-version>
<firmware-version>61.20</firmware-version>
<serial-no>214156344</serial-no>
<part-no>SO-TQSFPDD4CCZRP</part-no>
<oper-status

xmlns:oc-platform-types="http://openconfig.net/yang/platform-
types">oc-platform-types:INACTIVE</oper-status>
<parent>PORT-QSFP-50</parent>
<empty>false</empty>
<allocated-power>0</allocated-power>
<temperature>
</temperature>
</state>
</component>
</components>
Validate OpenZR+ transceiver state

Use these commands to validate OpenZR+ transceiver state.
Release

<config>
<component>
<transceiver>
<state />
</transceiver>
</component>
</components>
</config>

This validation response provides information on the configuration and runtime for validating OpenZR+ transceiver
state.
<component>
<state>
<form-factor
xmlns:oc-opt-types="http://openconfig.net/yang/transport-types">oc-
opt-types:QSFP56_DD_TYPE1</form-factor>
<connector-type
opt-types:LC_CONNECTOR</connector-type>
<vendor>SmartOptics</vendor>
<vendor-part>SO-TQSFPDD4CCZRP</vendor-part>
<vendor-rev>A</vendor-rev>

<serial-no>214156344</serial-no>
<supply-voltage>
</supply-voltage>
</state>
</transceiver>
</component>
</components>
Validate OpenZR+ transceiver thresholds

Use these commands to validate OpenZR+ transceiver thresholds.
Release
Severity CRITICAL
The below commands are used to validate the thresholds with critical severity.

<config>
<component>
<transceiver>
<thresholds>
<threshold>
<severity>CRITICAL</severity>
</threshold>
</thresholds>
</transceiver>
</component>
</components>
</config>

thresholds.
<component xmlns:oc-opt-types="http://openconfig.net/yang/transport-types">
<thresholds>
<threshold>

<state>
<input-power-upper>101.000000</input-power-upper>
<input-power-lower>8.000000</input-power-lower>
</state>
</threshold>
</thresholds>
</transceiver>
</component>
</components>
Severity MAJOR
The below commands are used to validate thresholds with major severity.

<config>
<component>
<transceiver>
<thresholds>
<threshold>
<severity>MAJOR</severity>
</threshold>
</thresholds>
</transceiver>
</component>
</components>
</config>

This validation response provides information on the configuration and runtime for validating the OpenZR+ transceiver
thresholds with major severity.
<component xmlns:oc-opt-types="http://openconfig.net/yang/transport-types">
<thresholds>
<threshold>
<state>
<input-power-upper>96.000000</input-power-upper>
<input-power-lower>9.000000</input-power-lower>
</state>
</threshold>
</thresholds>
</transceiver>
</component>

</components>
Validate OpenZR+ transceiver physical channels

Use these commands to validate OpenZR+ transceiver physical channels.
Release

<config>
<component>
<transceiver>
<physical-channels />
</transceiver>
</component>
</components>
</config>

channels.
<component>
<physical-channels>
<channel>
<index>1</index>
<state>
<laser-temperature>
</laser-temperature>
<index>1</index>
<laser-age>0</laser-age>
</state>
</channel>
</transceiver>
</component>
</components>

Validate OpenZR+ transceiver optical channel state

Use these commands to validate OpenZR+ transceiver optical channel state.
Release

<config>
<component>
<optical-channel>
<state />
</optical-channel>
</component>
</components>
</config>

optical channel state.
<component>
<optical-channel>
<state>
<input-power>
</input-power>
<output-power>
</output-power>
<laser-bias-current>
<pre-fec-ber>
<min>0.00</min>
<max>0.00</max>
<avg>0.00</avg>
</pre-fec-ber>
<post-fec-ber>
<min>0.00</min>
<max>0.00</max>
<avg>0.00</avg>

</post-fec-ber>
<modulator-bias-xi>
</modulator-bias-xi>
<modulator-bias-xq>
</modulator-bias-xq>
<modulator-bias-yi>
</modulator-bias-yi>
<modulator-bias-yq>
</modulator-bias-yq>
<modulator-bias-x-phase>
</modulator-bias-x-phase>
<modulator-bias-y-phase>
</modulator-bias-y-phase>
<chromatic-dispersion>
<max>0.00</max>
<min>0.00</min>
</chromatic-dispersion>
<polarization-mode-dispersion>
<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</polarization-mode-dispersion>
<second-order-polarization-mode-dispersion>
</second-order-polarization-mode-dispersion>
<polarization-dependent-loss>
<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</polarization-dependent-loss>
<osnr>
<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</osnr>
<esnr>
<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</esnr>
<carrier-frequency-offset>
<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</carrier-frequency-offset>
<sop-roc>

<avg>0.00</avg>
<min>0.00</min>
<max>0.00</max>
</sop-roc>
<fec-uncorrectable-blocks>
<instant>0</instant>
</fec-uncorrectable-blocks>
<frequency>193100000</frequency>
</state>
</optical-channel>
</component>
</components>
Validate OpenZR+ logical channels

Use these commands to validate OpenZR+ transceiver logical channels.
Release
Optical channel assignment type

The index value in the Openconfig datamodel is shown in ASCII bytes format.
Transforming the index value to the hexadecimal, it is in the format 0xFFSSMMHH, where:
• FF is fp-port (in hexadecimal format);
• SS is slot index, fixed to 0 in case of CMIS modules (in hexadecimal format);
• MM is the optical channel media lane (in hexadecimal format);
• HH is the host lane to which the data-path is assigned (in hexadecimal format).
For example, to calculate the index for an optical channel assignment type:
• fp-port 50 (0x32 in hexadecimal);
• slot-index 0 (0x00 in hexadecimal);
• optical channel media lane 1 (0x01 in hexadecimal);
• host lane 0 (0x00 in hexadecimal).
Index in hexadecimal: 0x32000100
Transforming it to the ASCII bytes format: 838861056

<config>
<logical-channels>
<channel>

</channel>
</logical-channels>
</terminal-device>
</config>

This validation response provides information on the configuration and runtime for validating OpenZR+ logical
channels.
<logical-channels>
<channel>
<assignment>
<index>1</index>
<state>
<index>1</index>
<allocation>400.000</allocation>
</state>
</assignment>
<config>
<logical-channel-type
opt-types:PROT_OTN</logical-channel-type>
</config>
<state>
opt-types:PROT_OTN</logical-channel-type>
</state>
</channel>
</logical-channels>
</terminal-device>
Logical channel assignment type

The index value in the Openconfig datamodel is shown in ASCII bytes format.
Transforming the index value to the hexadecimal, it is in the format 0xFFSSMMHH, where:
• FF is the fp-port (in hexadecimal format);
• SS is the slot-index, fixed to 0 in case of CMIS modules (in hexadecimal format);
• MM is the optical channel media lane (in hexadecimal format);
• HH is the host lane to which the data-path is assigned (in hexadecimal format).
For example, to calculate the index for an logical channel assignment type:
• fp-port 50 (0x32 in hexadecimal);
• slot-index 0 (0x00 in hexadecimal);
• optical channel media lane 0 (0x00 in hexadecimal);

• host lane 1 (0x01 in hexadecimal).

Index in hexadecimal: 0x32000001
Transforming it to the ASCII bytes format: 838860801

<config>
<logical-channels>
<channel>
</channel>
</logical-channels>
</terminal-device>
</config>

This validation response provides information on the configuration and runtime for validating OpenZR+ logical
channels.
<logical-channels>
<channel>
<assignment>
<index>1</index>
<state>
<assignment-type>LOGICAL_CHANNEL</assignment-type>
<logical-channel>838861056</logical-channel>
<index>1</index>
<allocation>400.000</allocation>
</state>
</assignment>
<config>
opt-types:PROT_ETHERNET</logical-channel-type>
</config>
<state>
opt-types:PROT_ETHERNET</logical-channel-type>
</state>
<ingress>
<state>
<interface>cd50</interface>
</state>
</ingress>
<ethernet>
<state>

<pre-fec-ber>
<min>0.0</min>
<max>0.0</max>
<avg>0.0</avg>
</pre-fec-ber>
<post-fec-ber>
<min>0.0</min>
<max>0.0</max>
<avg>0.0</avg>
</post-fec-ber>
<out-8021q-frames>0</out-8021q-frames>
<fec-uncorrectable-blocks>0</fec-uncorrectable-blocks>
</state>
</ethernet>
<state>
</state>
</channel>
</logical-channels>
</terminal-device>
Configure OpenZR+ port-breakout

Use the commands to configure OpenZR+ port-breakout.
Release

Here is a sample OpenConfig NetConf Payload to configure OpenZR+ port-breakout.
<config>
<component>
<name>PORT-CMIS-MODULE-50</name>
<port>
<breakout-mode xmlns="http://openconfig.net/yang/platform/port">
<groups>
<group>
<index>0</index>
<config>
<index>0</index>
<num-breakouts>1</num-breakouts>
<breakout-speed xmlns="http://openconfig.net/yang/interfaces/
ethernet">SPEED_100GB</breakout-speed>
<num-physical-channels>4</num-physical-channels>
</config>
</group>
</groups>
</breakout-mode>

</port>
<config>
</config>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to configure OpenZR+ port-breakout.
port cd50 breakout 1X100g serdes 25g

Here is a sample OcNOS NetConf Payload to configure OpenZR+ port-breakout.
<port-breakout xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-port-breakout">
<breakouts>
<breakout>
<config>
<mode>1X100g</mode>
<serdes>25g</serdes>
</config>
</breakout>
</breakouts>
</port-breakout>
Unconfiguration
Use these commands to unconfigure OpenZR+ port-breakout.

Here is a sample OpenConfig NetConf Payload to unconfigure OpenZR+ port-breakout.
<config>
<component>
<port>
<groups>
<group operation="delete">
<index>0</index>
<config>
<index>0</index>
</config>

</group>
</groups>
</breakout-mode>
</port>
<config>
</config>
</component>
</components>
</config>
OcNOS CLI Command

The below CLI command is used to unconfigure OpenZR+ port-breakout.
no port cd50 breakout

Here is a sample OcNOS NetConf Payload to unconfigure OpenZR+ port-breakout.
<port-breakout xmlns="http://www.ipinfusion.com/yang/ocnos/ipi-port-breakout">
<breakouts>
<breakout operation="delete">
</breakout>
</breakouts>
</port-breakout>
Validate OpenZR+ port-breakout

Use these commands to validate OpenZR+ port-breakout.
Release

<config>
<component>
<port>
<breakout-mode>
<groups>
<group>
<index>0</index>
<state />
</group>
</groups>

</breakout-mode>
</port>
</component>
</components>
</config>

This validation response provides information on the configuration and runtime for validating OpenZR+ port-breakout.
<config>
<component>
<port>
<groups>
<group>
<index>0</index>
<state>
<index>0</index>
</state>
</group>
</groups>
</breakout-mode>
</port>
</component>
</components>
</config>

PYANG Tree
module: openconfig-acl
+--rw acl
+--rw acl-sets
| +--rw acl-set* [name type]
| +--rw name -> ../config/name
| +--rw type -> ../config/type
| +--rw config
| | +--rw name? string
| | +--rw type? identityref
| | +--rw description? string
| +--ro state
| | +--ro name? string
| | +--ro type? identityref
| | +--ro description? string
| +--rw acl-entries
| +--rw acl-entry* [sequence-id]
| +--rw sequence-id -> ../config/sequence-id
| +--rw config
| | +--rw sequence-id? uint32
| +--ro state
| | +--ro sequence-id? uint32
| +--rw l2
| | +--rw config
| | | +--rw source-mac? openconfig-yang-types:mac-address
| | | +--rw source-mac-mask? openconfig-yang-types:mac-address
| | | +--rw destination-mac? openconfig-yang-types:mac-address
| | | +--rw destination-mac-mask? openconfig-yang-types:mac-address
| | | +--rw ethertype? oc-pkt-match-types:ethertype-type
| | +--ro state
| | +--ro source-mac? openconfig-yang-types:mac-address
| | +--ro source-mac-mask? openconfig-yang-types:mac-address

PYANG Tree
| | +--ro destination-mac? openconfig-yang-types:mac-address

| | +--ro destination-mac-mask? openconfig-yang-types:mac-address
| | +--ro ethertype? oc-pkt-match-types:ethertype-type
| +--rw ipv4
| | +--rw config
| | | +--rw source-address? oc-inet:ipv4-prefix
| | | +--rw destination-address? oc-inet:ipv4-prefix
| | | +--rw dscp? oc-inet:dscp
| | | +--rw protocol? oc-pkt-match-types:ip-protocol-type
| | +--ro state
| | +--ro source-address? oc-inet:ipv4-prefix
| | +--ro destination-address? oc-inet:ipv4-prefix
| | +--ro dscp? oc-inet:dscp
| | +--ro protocol? oc-pkt-match-types:ip-protocol-type
| +--rw ipv6
| | +--rw config
| | | +--rw source-flow-label? oc-inet:ipv6-flow-label
| | | +--rw protocol? oc-pkt-match-types:ip-protocol-type
| | +--ro state
| | +--ro protocol? oc-pkt-match-types:ip-protocol-type
| +--rw transport
| | +--rw config
| | | +--rw source-port? oc-pkt-match-types:port-num-range
| | | +--rw destination-port? oc-pkt-match-types:port-num-range
| | | +--rw detail-mode? enumeration
| | | +--rw explicit-tcp-flags* identityref
| | +--ro state
| | +--ro source-port? oc-pkt-match-types:port-num-range
| | +--ro destination-port? oc-pkt-match-types:port-num-range
| | +--ro detail-mode? enumeration

PYANG Tree
| | +--ro explicit-tcp-flags* identityref

| +--rw actions
| +--rw config
| | +--rw forwarding-action identityref
| | +--rw log-action? identityref
| +--ro state
| +--ro forwarding-action identityref
| +--ro log-action? identityref
+--rw interfaces
+--rw interface* [id]
+--rw id -> ../config/id
+--rw config
| +--rw id? openconfig-interfaces:interface-id
+--ro state
| +--ro id? openconfig-interfaces:interface-id
+--rw interface-ref
| +--rw config
| | +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| | +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
subinterfaces/subinterface/index
| +--ro state
| +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
+--rw ingress-acl-sets
| +--rw ingress-acl-set* [set-name type]
| +--rw set-name -> ../config/set-name
| +--rw type -> ../config/type
| +--rw config
| | +--rw set-name? -> ../../../../../../acl-sets/acl-set/config/name
| | +--rw type? -> ../../../../../../acl-sets/acl-set[name=current()/../set-name]/config/type
| +--ro state
| +--ro set-name? -> ../../../../../../acl-sets/acl-set/config/name
| +--ro type? -> ../../../../../../acl-sets/acl-set[name=current()/../set-name]/config/type
+--rw egress-acl-sets
+--rw egress-acl-set* [set-name type]
+--rw set-name -> ../config/set-name

PYANG Tree
+--rw type -> ../config/type

+--rw config
| +--rw set-name? -> ../../../../../../acl-sets/acl-set/config/name
| +--rw type? -> ../../../../../../acl-sets/acl-set[name=current()/../set-name]/config/type
+--ro state
+--ro set-name? -> ../../../../../../acl-sets/acl-set/config/name
+--ro type? -> ../../../../../../acl-sets/acl-set[name=current()/../set-name]/config/type
module: openconfig-bfd
+--rw bfd
+--rw interfaces
+--rw interface* [id]
+--rw id -> ../config/id
+--rw config
| +--rw id? string
| +--rw enabled? boolean
| +--rw desired-minimum-tx-interval? uint32
| +--rw required-minimum-receive? uint32
| +--rw detection-multiplier? uint8
+--ro state
| +--ro id? string
| +--ro enabled? boolean
| +--ro desired-minimum-tx-interval? uint32
| +--ro required-minimum-receive? uint32
| +--ro detection-multiplier? uint8
| +--ro enable-per-member-link? boolean
+--rw interface-ref
| +--rw config
| +--ro state

PYANG Tree
+--ro micro-bfd-sessions
| +--ro micro-bfd-session* [member-interface]
| +--ro member-interface -> ../state/member-interface
| +--ro state
| +--ro member-interface? -> /openconfig-interfaces:interfaces/interface/config/name
| +--ro session-state? bfd-session-state
| +--ro remote-session-state? bfd-session-state
| +--ro local-discriminator? string
| +--ro remote-discriminator? string
| +--ro local-diagnostic-code? bfd-diagnostic-code
| +--ro remote-diagnostic-code? bfd-diagnostic-code
+--rw peers
+--ro peer* [local-discriminator]
+--ro local-discriminator -> ../state/local-discriminator
+--ro state
+--ro local-address? openconfig-inet-types:ip-address
+--ro remote-address? openconfig-inet-types:ip-address
+--ro subscribed-protocols* identityref
+--ro session-state? bfd-session-state
+--ro remote-session-state? bfd-session-state
+--ro local-discriminator? string
+--ro remote-discriminator? string
+--ro local-diagnostic-code? bfd-diagnostic-code
+--ro remote-minimum-receive-interval? uint32
+--ro demand-mode-requested? boolean
+--ro remote-authentication-enabled? boolean
+--ro echo
| +--ro active? boolean
| +--ro transmitted-packets? uint64
| +--ro up-transitions? uint64
+--ro async
+--ro transmitted-packets? uint64
+--ro received-packets? uint64
+--ro up-transitions? uint64

PYANG Tree
module: openconfig-if-aggregate
augment /oc-if:interfaces/oc-if:interface/oc-eth:ethernet/oc-eth:config:
+--rw aggregate-id? -> /openconfig-interfaces:interfaces/interface/name
augment /oc-if:interfaces/oc-if:interface/oc-eth:ethernet/oc-eth:state:
+--ro aggregate-id? -> /openconfig-interfaces:interfaces/interface/name
module: openconfig-if-ip
augment /oc-if:interfaces/oc-if:interface/oc-vlan:routed-vlan:
+--rw ipv4
+--rw addresses
| +--rw address* [ip]
| +--rw ip -> ../config/ip
| +--rw config
| | +--rw ip? openconfig-inet-types:ipv4-address
| | +--rw prefix-length? uint8
| +--ro state
| | +--ro ip? openconfig-inet-types:ipv4-address
| | +--ro prefix-length? uint8
| | +--ro origin? ip-address-origin
| +--rw vrrp
| +--rw vrrp-group* [virtual-router-id]
| +--rw virtual-router-id -> ../config/virtual-router-id
| +--rw config
| | +--rw virtual-router-id? uint8
| | +--rw virtual-address* openconfig-inet-types:ip-address
| | +--rw priority? uint8
| | +--rw preempt? boolean
| | +--rw preempt-delay? uint16
| | +--rw accept-mode? boolean
| | +--rw advertisement-interval? uint16
| +--ro state

PYANG Tree
| | +--ro virtual-router-id? uint8

| | +--ro virtual-address* openconfig-inet-types:ip-address
| | +--ro priority? uint8
| | +--ro preempt? boolean
| | +--ro preempt-delay? uint16
| | +--ro accept-mode? boolean
| | +--ro advertisement-interval? uint16
| | +--ro current-priority? uint8
| +--rw interface-tracking
| +--rw config
| | +--rw track-interface* -> /openconfig-interfaces:interfaces/interface/name
| | +--rw priority-decrement? uint8
| +--ro state
| +--ro track-interface* -> /openconfig-interfaces:interfaces/interface/name
| +--ro priority-decrement? uint8
+--rw proxy-arp
| +--rw config
| | +--rw mode? enumeration
| +--ro state
| +--ro mode? enumeration
+--rw neighbors
| +--rw neighbor* [ip]
| +--rw config
| | +--rw link-layer-address openconfig-yang-types:phys-address
| +--ro state
| +--ro ip? openconfig-inet-types:ipv4-address
| +--ro link-layer-address openconfig-yang-types:phys-address
| +--ro origin? neighbor-origin
+--rw unnumbered
| +--rw config
| | +--rw enabled? boolean
| +--ro state
| | +--ro enabled? boolean
| +--rw interface-ref

PYANG Tree
| +--rw config
| +--ro state
+--rw config
| +--rw mtu? uint16
| +--rw dhcp-client? boolean
+--ro state
+--ro enabled? boolean
+--ro mtu? uint16
+--ro dhcp-client? boolean
+--ro counters
+--ro in-pkts? openconfig-yang-types:counter64
+--ro in-octets? openconfig-yang-types:counter64
+--ro in-error-pkts? openconfig-yang-types:counter64
+--ro in-forwarded-pkts? openconfig-yang-types:counter64
+--ro in-forwarded-octets? openconfig-yang-types:counter64
+--ro in-discarded-pkts? openconfig-yang-types:counter64
+--ro out-pkts? openconfig-yang-types:counter64
+--ro out-octets? openconfig-yang-types:counter64
+--ro out-error-pkts? openconfig-yang-types:counter64
+--ro out-forwarded-pkts? openconfig-yang-types:counter64
+--ro out-forwarded-octets? openconfig-yang-types:counter64
+--ro out-discarded-pkts? openconfig-yang-types:counter64
augment /oc-if:interfaces/oc-if:interface/oc-vlan:routed-vlan:
+--rw ipv6
+--rw addresses
| +--rw address* [ip]
| +--rw config
| | +--rw prefix-length uint8

PYANG Tree
| | +--rw type? openconfig-inet-types:ipv6-address-type

| +--ro state
| | +--ro ip? openconfig-inet-types:ipv6-address
| | +--ro prefix-length uint8
| | +--ro type? openconfig-inet-types:ipv6-address-type
| | +--ro origin? ip-address-origin
| | +--ro status? enumeration
| +--rw vrrp
| +--rw vrrp-group* [virtual-router-id]
| +--rw virtual-router-id -> ../config/virtual-router-id
| +--rw config
| | +--rw virtual-router-id? uint8
| | +--rw virtual-address* openconfig-inet-types:ip-address
| | +--rw preempt? boolean
| | +--rw preempt-delay? uint16
| | +--rw accept-mode? boolean
| | +--rw advertisement-interval? uint16
| | +--rw virtual-link-local? openconfig-inet-types:ip-address
| +--ro state
| | +--ro virtual-router-id? uint8
| | +--ro virtual-address* openconfig-inet-types:ip-address
| | +--ro preempt? boolean
| | +--ro preempt-delay? uint16
| | +--ro accept-mode? boolean
| | +--ro advertisement-interval? uint16
| | +--ro current-priority? uint8
| | +--ro virtual-link-local? openconfig-inet-types:ip-address
| +--rw interface-tracking
| +--rw config
| | +--rw track-interface* -> /openconfig-interfaces:interfaces/interface/name
| | +--rw priority-decrement? uint8
| +--ro state
| +--ro track-interface* -> /openconfig-interfaces:interfaces/interface/name
| +--ro priority-decrement? uint8

PYANG Tree
+--rw router-advertisement
| +--rw config
| | +--rw interval? uint32
| | +--rw lifetime? uint32
| | +--rw suppress? boolean
| | +--rw managed? boolean
| | +--rw other-config? boolean
| +--ro state
| | +--ro interval? uint32
| | +--ro lifetime? uint32
| | +--ro suppress? boolean
| | +--ro managed? boolean
| | +--ro other-config? boolean
| +--rw prefixes
| +--rw prefix* [prefix]
| +--rw prefix -> ../config/prefix
| +--rw config
| | +--rw prefix? openconfig-inet-types:ipv6-prefix
| | +--rw valid-lifetime? uint32
| | +--rw preferred-lifetime? uint32
| | +--rw disable-advertisement? boolean
| | +--rw disable-autoconfiguration? boolean
| | +--rw enable-onlink? boolean
| +--ro state
| +--ro prefix? openconfig-inet-types:ipv6-prefix
| +--ro valid-lifetime? uint32
| +--ro preferred-lifetime? uint32
| +--ro disable-advertisement? boolean
| +--ro disable-autoconfiguration? boolean
| +--ro enable-onlink? boolean
+--rw neighbors
| +--rw neighbor* [ip]
| +--rw config
| | +--rw link-layer-address openconfig-yang-types:phys-address

PYANG Tree
| +--ro state
| +--ro ip? openconfig-inet-types:ipv6-address
| +--ro link-layer-address openconfig-yang-types:phys-address
| +--ro origin? neighbor-origin
| +--ro is-router? boolean
| +--ro neighbor-state? enumeration
+--rw unnumbered
| +--rw config
| +--ro state
| +--rw config
| +--ro state
+--rw config
| +--rw mtu? uint32
| +--rw dup-addr-detect-transmits? uint32
| +--rw dhcp-client? boolean
+--ro state
+--ro mtu? uint32
+--ro dup-addr-detect-transmits? uint32
+--ro dhcp-client? boolean
+--ro counters
+--ro in-pkts? openconfig-yang-types:counter64
+--ro in-octets? openconfig-yang-types:counter64
+--ro in-error-pkts? openconfig-yang-types:counter64
+--ro in-forwarded-pkts? openconfig-yang-types:counter64
+--ro in-forwarded-octets? openconfig-yang-types:counter64
+--ro in-discarded-pkts? openconfig-yang-types:counter64

PYANG Tree
+--ro out-pkts? openconfig-yang-types:counter64

+--ro out-octets? openconfig-yang-types:counter64
+--ro out-error-pkts? openconfig-yang-types:counter64
+--ro out-forwarded-pkts? openconfig-yang-types:counter64
+--ro out-forwarded-octets? openconfig-yang-types:counter64
+--ro out-discarded-pkts? openconfig-yang-types:counter64
module: openconfig-interfaces
+--rw interfaces
+--rw interface* [name]
+--rw name -> ../config/name
+--rw config
| +--rw name? string
| +--rw type identityref
| +--rw mtu? uint16
| +--rw description? string
| +--rw openconfig-vlan:tpid? identityref
+--ro state
| +--ro name? string
| +--ro type identityref
| +--ro mtu? uint16
| +--ro description? string
| +--ro ifindex? uint32
| +--ro admin-status enumeration
| +--ro oper-status enumeration
| +--ro last-change? openconfig-types:timeticks64
| +--ro logical? boolean
| +--ro counters
| | +--ro in-octets? openconfig-yang-types:counter64
| | +--ro in-pkts? openconfig-yang-types:counter64
| | +--ro in-unicast-pkts? openconfig-yang-types:counter64
| | +--ro in-broadcast-pkts? openconfig-yang-types:counter64
| | +--ro in-multicast-pkts? openconfig-yang-types:counter64

PYANG Tree
| | +--ro in-discards? openconfig-yang-types:counter64

| | +--ro in-errors? openconfig-yang-types:counter64
| | +--ro in-fcs-errors? openconfig-yang-types:counter64
| | +--ro out-octets? openconfig-yang-types:counter64
| | +--ro out-pkts? openconfig-yang-types:counter64
| | +--ro out-unicast-pkts? openconfig-yang-types:counter64
| | +--ro out-broadcast-pkts? openconfig-yang-types:counter64
| | +--ro out-multicast-pkts? openconfig-yang-types:counter64
| | +--ro out-discards? openconfig-yang-types:counter64
| | +--ro out-errors? openconfig-yang-types:counter64
| | +--ro last-clear? openconfig-types:timeticks64
| +--ro openconfig-vlan:tpid? identityref
+--rw subinterfaces
| +--rw subinterface* [index]
| +--rw index -> ../config/index
| +--rw config
| | +--rw index? uint32
| +--ro state
| | +--ro index? uint32
| | +--ro ifindex? uint32
| | +--ro oper-status enumeration
| | +--ro last-change? openconfig-types:timeticks64
| | +--ro logical? boolean
| | +--ro counters
| | +--ro in-octets? openconfig-yang-types:counter64
| | +--ro in-pkts? openconfig-yang-types:counter64
| | +--ro in-unicast-pkts? openconfig-yang-types:counter64
| | +--ro in-broadcast-pkts? openconfig-yang-types:counter64
| | +--ro in-multicast-pkts? openconfig-yang-types:counter64
| | +--ro in-discards? openconfig-yang-types:counter64
| | +--ro in-errors? openconfig-yang-types:counter64

PYANG Tree
| | +--ro in-fcs-errors? openconfig-yang-types:counter64

| | +--ro out-octets? openconfig-yang-types:counter64
| | +--ro out-pkts? openconfig-yang-types:counter64
| | +--ro out-unicast-pkts? openconfig-yang-types:counter64
| | +--ro out-broadcast-pkts? openconfig-yang-types:counter64
| | +--ro out-multicast-pkts? openconfig-yang-types:counter64
| | +--ro out-discards? openconfig-yang-types:counter64
| | +--ro out-errors? openconfig-yang-types:counter64
| | +--ro last-clear? openconfig-types:timeticks64
| +--rw openconfig-vlan:vlan
| | +--rw openconfig-vlan:match
| | | +--rw openconfig-vlan:single-tagged-list
| | | | +--rw openconfig-vlan:config
| | | | | +--rw openconfig-vlan:vlan-ids* openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:state
| | | | +--ro openconfig-vlan:vlan-ids* openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:single-tagged-range
| | | | | +--rw openconfig-vlan:low-vlan-id? openconfig-vlan-types:vlan-id
| | | | | +--rw openconfig-vlan:high-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:low-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:high-vlan-id? openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:double-tagged
| | | | | +--rw openconfig-vlan:inner-vlan-id? openconfig-vlan-types:vlan-id
| | | | | +--rw openconfig-vlan:outer-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:inner-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:outer-vlan-id? openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:double-tagged-outer-list
| | | | | +--rw openconfig-vlan:outer-vlan-ids* openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:outer-vlan-ids* openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:double-tagged-outer-range

PYANG Tree
| | | | | +--rw openconfig-vlan:outer-low-vlan-id? openconfig-vlan-types:vlan-id
| | | | | +--rw openconfig-vlan:outer-high-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:outer-low-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--ro openconfig-vlan:outer-high-vlan-id? openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:double-tagged-inner-outer-range
| | | +--rw openconfig-vlan:config
| | | | +--rw openconfig-vlan:inner-low-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--rw openconfig-vlan:inner-high-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--rw openconfig-vlan:outer-low-vlan-id? openconfig-vlan-types:vlan-id
| | | | +--rw openconfig-vlan:outer-high-vlan-id? openconfig-vlan-types:vlan-id
| | | +--ro openconfig-vlan:state
| | | +--ro openconfig-vlan:inner-low-vlan-id? openconfig-vlan-types:vlan-id
| | | +--ro openconfig-vlan:inner-high-vlan-id? openconfig-vlan-types:vlan-id
| | | +--ro openconfig-vlan:outer-low-vlan-id? openconfig-vlan-types:vlan-id
| | | +--ro openconfig-vlan:outer-high-vlan-id? openconfig-vlan-types:vlan-id
| | +--rw openconfig-vlan:ingress-mapping
| | +--rw openconfig-vlan:config
| | | +--rw openconfig-vlan:vlan-stack-action? openconfig-vlan-types:vlan-stack-action
| | | +--rw openconfig-vlan:vlan-id? openconfig-vlan-types:vlan-id
| | | +--rw openconfig-vlan:tpid? identityref
| | +--ro openconfig-vlan:state
| | +--ro openconfig-vlan:vlan-stack-action? openconfig-vlan-types:vlan-stack-action
| | +--ro openconfig-vlan:vlan-id? openconfig-vlan-types:vlan-id
| | +--ro openconfig-vlan:tpid? identityref
| +--rw openconfig-if-ip:ipv4
| | +--rw openconfig-if-ip:addresses
| | | +--rw openconfig-if-ip:address* [ip]
| | | +--rw openconfig-if-ip:ip -> ../config/ip
| | | +--rw openconfig-if-ip:config
| | | | +--rw openconfig-if-ip:ip? openconfig-inet-types:ipv4-address
| | | | +--rw openconfig-if-ip:prefix-length? uint8
| | | | +--rw ipi-oc-if-deviations:type? ipv4-address-type
| | | +--ro openconfig-if-ip:state
| | | +--ro openconfig-if-ip:ip? openconfig-inet-types:ipv4-address

PYANG Tree
| | | +--ro openconfig-if-ip:prefix-length? uint8

| | | +--ro ipi-oc-if-deviations:type? ipv4-address-type
| | +--rw openconfig-if-ip:config
| | | +--rw openconfig-if-ip:dhcp-client? boolean
| | +--ro openconfig-if-ip:state
| | +--ro openconfig-if-ip:dhcp-client? boolean
| +--rw openconfig-if-ip:ipv6
| +--rw openconfig-if-ip:addresses
| | +--rw openconfig-if-ip:address* [ip]
| | +--rw openconfig-if-ip:ip -> ../config/ip
| | +--rw openconfig-if-ip:config
| | | +--rw openconfig-if-ip:ip? openconfig-inet-types:ipv6-address
| | | +--rw openconfig-if-ip:prefix-length uint8
| | +--ro openconfig-if-ip:state
| | +--ro openconfig-if-ip:ip? openconfig-inet-types:ipv6-address
| | +--ro openconfig-if-ip:prefix-length uint8
| +--rw openconfig-if-ip:config
| | +--rw openconfig-if-ip:dhcp-client? boolean
| +--ro openconfig-if-ip:state
| +--ro openconfig-if-ip:dhcp-client? boolean
+--rw openconfig-if-ethernet:ethernet
| +--rw openconfig-if-ethernet:config
| | +--rw openconfig-if-ethernet:mac-address? openconfig-yang-types:mac-address
| | +--rw openconfig-if-ethernet:auto-negotiate? boolean
| | +--rw openconfig-if-ethernet:duplex-mode? enumeration
| | +--rw openconfig-if-ethernet:port-speed? identityref
| | +--rw openconfig-if-aggregate:aggregate-id? -> /openconfig-interfaces:interfaces/interface/name
| | +--rw ipi-oc-if-deviations:lacp-mode? openconfig-lacp:lacp-activity-type
| | +--rw ipi-oc-if-deviations:load-interval? uint16
| +--ro openconfig-if-ethernet:state
| | +--ro openconfig-if-ethernet:mac-address? openconfig-yang-types:mac-address
| | +--ro openconfig-if-ethernet:auto-negotiate? boolean
| | +--ro openconfig-if-ethernet:duplex-mode? enumeration
| | +--ro openconfig-if-ethernet:port-speed? identityref
| | +--ro openconfig-if-ethernet:hw-mac-address? string
| | +--ro openconfig-if-ethernet:negotiated-duplex-mode? enumeration

PYANG Tree
| | +--ro openconfig-if-ethernet:negotiated-port-speed? identityref

| | +--ro openconfig-if-ethernet:counters
| | | +--ro openconfig-if-ethernet:in-oversize-frames? openconfig-yang-types:counter64
| | | +--ro openconfig-if-ethernet:in-jabber-frames? openconfig-yang-types:counter64
| | | +--ro openconfig-if-ethernet:in-fragment-frames? openconfig-yang-types:counter64
| | | +--ro openconfig-if-ethernet:in-crc-errors? openconfig-yang-types:counter64
| | +--ro openconfig-if-aggregate:aggregate-id? -> /openconfig-interfaces:interfaces/interface/name
| | +--ro ipi-oc-if-deviations:lacp-mode? openconfig-lacp:lacp-activity-type
| | +--ro ipi-oc-if-deviations:load-interval? uint16
| +--rw openconfig-vlan:switched-vlan
| +--rw openconfig-vlan:config
| | +--rw openconfig-vlan:interface-mode? openconfig-vlan-types:vlan-mode-type
| | +--rw openconfig-vlan:native-vlan? openconfig-vlan-types:vlan-id
| | +--rw openconfig-vlan:access-vlan? openconfig-vlan-types:vlan-id
| | +--rw openconfig-vlan:trunk-vlans* union
| +--ro openconfig-vlan:state
| +--ro openconfig-vlan:interface-mode? openconfig-vlan-types:vlan-mode-type
| +--ro openconfig-vlan:native-vlan? openconfig-vlan-types:vlan-id
| +--ro openconfig-vlan:access-vlan? openconfig-vlan-types:vlan-id
| +--ro openconfig-vlan:trunk-vlans* union
+--rw openconfig-if-aggregate:aggregation
| +--rw openconfig-if-aggregate:config
| | +--rw openconfig-if-aggregate:lag-type? aggregation-type
| | +--rw openconfig-if-aggregate:min-links? uint8
| | +--rw ipi-oc-if-deviations:mlag-id? uint16
| +--ro openconfig-if-aggregate:state
| | +--ro openconfig-if-aggregate:lag-type? aggregation-type
| | +--ro openconfig-if-aggregate:min-links? uint16
| | +--ro ipi-oc-if-deviations:mlag-id? uint16
| +--rw openconfig-vlan:switched-vlan
| +--rw openconfig-vlan:config
| | +--rw openconfig-vlan:interface-mode? openconfig-vlan-types:vlan-mode-type
| | +--rw openconfig-vlan:native-vlan? openconfig-vlan-types:vlan-id
| | +--rw openconfig-vlan:access-vlan? openconfig-vlan-types:vlan-id
| | +--rw openconfig-vlan:trunk-vlans* union
| +--ro openconfig-vlan:state

PYANG Tree
| +--ro openconfig-vlan:interface-mode? openconfig-vlan-types:vlan-mode-type

| +--ro openconfig-vlan:native-vlan? openconfig-vlan-types:vlan-id
| +--ro openconfig-vlan:access-vlan? openconfig-vlan-types:vlan-id
| +--ro openconfig-vlan:trunk-vlans* union
+--rw openconfig-if-tunnel:tunnel
+--rw openconfig-if-tunnel:config
| +--rw openconfig-if-tunnel:src? openconfig-inet-types:ip-address
| +--rw openconfig-if-tunnel:dst? openconfig-inet-types:ip-address
| +--rw openconfig-if-tunnel:ttl? uint8
+--ro openconfig-if-tunnel:state
| +--ro openconfig-if-tunnel:src? openconfig-inet-types:ip-address
| +--ro openconfig-if-tunnel:dst? openconfig-inet-types:ip-address
| +--ro openconfig-if-tunnel:ttl? uint8
+--rw openconfig-if-tunnel:ipv4
| +--rw openconfig-if-tunnel:addresses
| | +--rw openconfig-if-tunnel:address* [ip]
| | +--rw openconfig-if-tunnel:ip -> ../config/ip
| | +--rw openconfig-if-tunnel:config
| | | +--rw openconfig-if-tunnel:ip? openconfig-inet-types:ipv4-address
| | | +--rw openconfig-if-tunnel:prefix-length? uint8
| | | +--rw ipi-oc-if-deviations:type? ipv4-address-type
| | +--ro openconfig-if-tunnel:state
| | +--ro openconfig-if-tunnel:ip? openconfig-inet-types:ipv4-address
| | +--ro openconfig-if-tunnel:prefix-length? uint8
| | +--ro ipi-oc-if-deviations:type? ipv4-address-type
| +--rw openconfig-if-tunnel:unnumbered
| +--rw openconfig-if-tunnel:config
| | +--rw openconfig-if-tunnel:enabled? boolean
| +--ro openconfig-if-tunnel:state
| | +--ro openconfig-if-tunnel:enabled? boolean
| +--rw openconfig-if-tunnel:interface-ref
| +--rw openconfig-if-tunnel:config
| | +--rw openconfig-if-tunnel:interface? -> /openconfig-interfaces:interfaces/interface/name
| | +--rw openconfig-if-tunnel:subinterface? -> /openconfig-interfaces:interfaces/interface[oc-
if:name=current()/../interface]/subinterfaces/subinterface/index
| +--ro openconfig-if-tunnel:state
| +--ro openconfig-if-tunnel:interface? -> /openconfig-interfaces:interfaces/interface/name

PYANG Tree
| +--ro openconfig-if-tunnel:subinterface? -> /openconfig-interfaces:interfaces/interface[oc-

if:name=current()/../interface]/subinterfaces/subinterface/index
+--rw openconfig-if-tunnel:ipv6
+--rw openconfig-if-tunnel:addresses
+--rw openconfig-if-tunnel:address* [ip]
+--rw openconfig-if-tunnel:ip -> ../config/ip
+--rw openconfig-if-tunnel:config
| +--rw openconfig-if-tunnel:ip? openconfig-inet-types:ipv6-address
| +--rw openconfig-if-tunnel:prefix-length uint8
+--ro openconfig-if-tunnel:state
+--ro openconfig-if-tunnel:ip? openconfig-inet-types:ipv6-address
+--ro openconfig-if-tunnel:prefix-length uint8
module: openconfig-lacp
+--rw lacp
+--rw config
| +--rw system-priority? uint16
+--ro state
+--ro system-priority? uint16
module: openconfig-lldp
+--rw lldp
+--rw config
| +--rw suppress-tlv-advertisement* identityref
| +--rw system-name? string
| +--rw chassis-id? string
| +--rw chassis-id-type? openconfig-lldp-types:chassis-id-type
+--ro state
| +--ro suppress-tlv-advertisement* identityref
| +--ro system-name? string
| +--ro chassis-id? string

PYANG Tree
| +--ro chassis-id-type? openconfig-lldp-types:chassis-id-type

+--rw interfaces
+--rw interface* [name]
+--rw config
| +--rw name? openconfig-interfaces:base-interface-ref
+--ro state
| +--ro name? openconfig-interfaces:base-interface-ref
| +--ro counters
| +--ro frame-out? ietf-yang-types:counter64
| +--ro last-clear? ietf-yang-types:date-and-time
+--ro neighbors
+--ro neighbor* [id]
+--ro id -> ../state/id
+--ro state
| +--ro system-name? string
| +--ro system-description? string
| +--ro chassis-id? string
| +--ro chassis-id-type? openconfig-lldp-types:chassis-id-type
| +--ro id? string
| +--ro ttl? uint16
| +--ro port-id? string
| +--ro port-id-type? openconfig-lldp-types:port-id-type
| +--ro port-description? string
| +--ro management-address? string
| +--ro management-address-type? string
+--ro custom-tlvs
| +--ro tlv* [type oui oui-subtype]
| +--ro type -> ../state/type
| +--ro oui -> ../state/oui
| +--ro oui-subtype -> ../state/oui-subtype
| +--ro config
| +--ro state
| +--ro type? int32

PYANG Tree
| +--ro oui? string

| +--ro oui-subtype? string
| +--ro value? binary
+--ro capabilities
+--ro capability* [name]
+--ro name -> ../state/name
+--ro config
+--ro state
+--ro name? identityref
module: openconfig-network-instance
+--rw network-instances
+--rw network-instance* [name]
+--rw config
| +--rw type identityref
| +--rw description? string
| +--rw router-id? openconfig-yang-types:dotted-quad
| +--rw route-distinguisher? openconfig-network-instance-types:route-distinguisher
| +--rw fallback-network-instance? network-instance-ref
| +--rw ipi-oc-ni-augments:bridge-protocol? enumeration
+--ro state
| +--ro type identityref
| +--ro router-id? openconfig-yang-types:dotted-quad
| +--ro route-distinguisher? openconfig-network-instance-types:route-distinguisher
| +--ro ipi-oc-ni-augments:bridge-protocol? enumeration
+--rw fdb
| +--rw config
| | +--rw mac-learning? boolean
| | +--rw maximum-entries? uint16
| +--ro state

PYANG Tree
| | +--ro mac-learning? boolean

| | +--ro maximum-entries? uint16
| +--rw mac-table
| | +--rw entries
| | +--rw entry* [mac-address vlan]
| | +--rw mac-address -> ../config/mac-address
| | +--rw vlan -> ../config/vlan
| | +--rw config
| | +--rw mac-address? openconfig-yang-types:mac-address
| | +--rw vlan? -> ../../../../../../vlans/vlan/config/vlan-id
| +--ro l2rib
| +--ro mac-table
| | +--ro entries
| | | +--ro entry* [mac-address]
| | | +--ro mac-address -> ../state/mac-address
| | | +--ro state
| | | | +--ro mac-address? openconfig-yang-types:mac-address
| | | +--ro producers
| | | +--ro producer* [producer]
| | | +--ro producer -> ../state/producer
| | | +--ro state
| | | +--ro producer? enumeration
| | +--ro next-hops
| | +--ro next-hop* [index]
| | +--ro index -> ../state/index
| | +--ro state
| +--ro mac-ip-table
| +--ro entries
| | +--ro entry* [mac-address host-ip]
| | +--ro mac-address -> ../state/mac-address
| | +--ro host-ip -> ../state/host-ip
| | +--ro state
| | | +--ro mac-address? openconfig-yang-types:mac-address
| | | +--ro vlan? -> ../../../../../../../vlans/vlan/config/vlan-id
| | | +--ro evi? oc-evpn-types:evi-id

PYANG Tree
| | | +--ro l2-vni? oc-evpn-types:evi-id

| | | +--ro host-ip? openconfig-inet-types:ip-address
| | | +--ro l3-vni? oc-evpn-types:evi-id
| | +--ro producers
| | +--ro producer* [producer]
| | +--ro producer -> ../state/producer
| | +--ro state
| | +--ro producer? enumeration
| +--ro next-hops
| +--ro next-hop* [index]
| +--ro index -> ../state/index
| +--ro state
| +--ro index? uint64
+--rw evpn
| +--rw evpn-instances
| +--rw evpn-instance* [evi]
| +--rw evi -> ../config/evi
| +--rw config
| | +--rw evi? string
| | +--rw encapsulation-type? identityref
| +--ro state
| +--ro evi? string
| +--ro encapsulation-type? identityref
| +--ro service-type? identityref
| +--ro multicast-group? openconfig-inet-types:ip-address
| +--ro multicast-mask? openconfig-inet-types:ip-address
| +--ro replication-mode? enumeration
| +--ro control-word-enabled? boolean
+--rw encapsulation
| +--rw config
| | +--rw encapsulation-type? identityref
| | +--rw label-allocation-mode? identityref
| +--ro state
| +--ro encapsulation-type? identityref
| +--ro label-allocation-mode? identityref
+--rw inter-instance-policies

PYANG Tree
| +--rw apply-policy
| | +--rw config
| | | +--rw import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/name
| | | +--rw export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/name
| | +--ro state
| | +--ro import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/name
| | +--ro export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/name
| +--rw import-export-policy
| +--rw config
| | +--rw export-route-target* union
| | +--rw import-route-target* union
| +--ro state
| +--ro export-route-target* union
| +--ro import-route-target* union
+--rw table-connections
| +--rw table-connection* [src-protocol dst-protocol address-family]
| +--rw src-protocol -> ../config/src-protocol
| +--rw dst-protocol -> ../config/dst-protocol
| +--rw address-family -> ../config/address-family
| +--rw config
| | +--rw src-protocol? -> ../../../../tables/table/config/protocol
| | +--rw address-family? -> ../../../../tables/table[protocol=current()/../src-protocol]/config/address-
family
| | +--rw dst-protocol? -> ../../../../tables/table/config/protocol
| | +--rw import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | +--rw default-import-policy? default-policy-type
| | +--rw ipi-oc-ni-augments:dst-instance? string
| +--ro state
| +--ro src-protocol? -> ../../../../tables/table/config/protocol
| +--ro address-family? -> ../../../../tables/table[protocol=current()/../src-protocol]/config/address-family
| +--ro dst-protocol? -> ../../../../tables/table/config/protocol
| +--ro disable-metric-propagation? boolean
| +--ro import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| +--ro default-import-policy? default-policy-type
+--rw interfaces

PYANG Tree
| +--rw interface* [id]

| +--rw id -> ../config/id
| +--rw config
| | +--rw id? string
| +--ro state
| +--ro id? string
+--rw tables
| +--rw table* [protocol address-family]
| +--rw protocol -> ../config/protocol
| +--rw address-family -> ../config/address-family
| +--rw config
| | +--rw protocol? -> ../../../../protocols/protocol/config/identifier
| | +--rw address-family? identityref
| +--ro state
| +--ro protocol? -> ../../../../protocols/protocol/config/identifier
| +--ro address-family? identityref
+--rw connection-points
| +--rw connection-point* [connection-point-id]
| +--rw connection-point-id -> ../config/connection-point-id
| +--rw config
| | +--rw connection-point-id? string
| +--ro state
| | +--ro connection-point-id? string
| +--rw endpoints
| +--rw endpoint* [endpoint-id]
| +--rw endpoint-id -> ../config/endpoint-id
| +--rw config
| | +--rw endpoint-id? string
| | +--rw precedence? uint16
| +--ro state

PYANG Tree
| | +--ro endpoint-id? string

| | +--ro precedence? uint16
| +--rw local
| | +--rw config
| | | +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| | | +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| | +--ro state
| | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../
interface]/subinterfaces/subinterface/index
| | +--ro site-id? uint16
| | +--ro site-label-block-offset? uint16
| | +--ro site-label-block-size? uint16
| +--rw remote
| | +--rw config
| | | +--rw remote-system? openconfig-inet-types:ip-address
| | | +--rw virtual-circuit-identifier? uint32
| | +--ro state
| | +--ro remote-system? openconfig-inet-types:ip-address
| | +--ro virtual-circuit-identifier? uint32
| +--rw vxlan
| +--ro endpoint-peers
| | +--ro endpoint-peer* [peer-address]
| | +--ro peer-address -> ../state/peer-address
| | +--ro state
| | +--ro peer-address? openconfig-inet-types:ip-address
| | +--ro peer-state? enumeration
| | +--ro uptime? openconfig-types:timeticks64
| | +--ro control-plane-vnis? string
| | +--ro router-mac? openconfig-yang-types:mac-address
| +--ro endpoint-vnis
| +--ro endpoint-vni* [vni]
| +--ro vni -> ../state/vni
| +--ro state
| +--ro vni? oc-evpn-types:evi-id
| +--ro multidestination-traffic? union

PYANG Tree
| +--ro learning-mode? oc-evpn-types:learning-mode

| +--ro vni-type? enumeration
| +--ro vni-state? enumeration
| +--ro svi-state? enumeration
| +--ro bridge-domain? uint32
| +--ro l3-vrf-name? string
+--rw mpls
| +--rw global
| | +--rw config
| | | +--rw pw-encapsulation? identityref
| | +--ro state
| | | +--ro pw-encapsulation? identityref
| | +--rw interface-attributes
| | | +--rw interface* [interface-id]
| | | +--rw interface-id -> ../config/interface-id
| | | +--rw config
| | | | +--rw interface-id? openconfig-interfaces:interface-id
| | | | +--rw mpls-enabled? boolean
| | | +--rw interface-ref
| | | +--rw config
| | +--rw reserved-label-blocks
| | +--rw reserved-label-block* [local-id]
| | +--rw local-id -> ../config/local-id
| | +--rw config
| | +--rw local-id? string
| +--rw te-global-attributes
| | +--rw srlgs
| | | +--rw srlg* [name]
| | | +--rw name -> ../config/name
| | | +--rw config
| | | | +--rw name? string
| | | +--ro state
| | | +--ro name? string
| | +--rw mpls-admin-groups

PYANG Tree
| | | +--rw admin-group* [admin-group-name]

| | | +--rw admin-group-name -> ../config/admin-group-name
| | | +--rw config
| | | | +--rw admin-group-name? string
| | | | +--rw bit-position? uint32
| | | +--ro state
| | | +--ro admin-group-name? string
| | | +--ro bit-position? uint32
| | +--rw te-lsp-timers
| | +--rw config
| | | +--rw reoptimize-timer? uint16
| | +--ro state
| | +--ro reoptimize-timer? uint16
| +--rw te-interface-attributes
| | +--rw interface* [interface-id]
| | +--rw interface-id -> ../config/interface-id
| | +--rw config
| | | +--rw interface-id? openconfig-interfaces:interface-id
| | | +--rw srlg-membership* -> ../../../../te-global-attributes/srlgs/srlg/name
| | | +--rw admin-group* string
| | +--ro state
| | | +--ro interface-id? openconfig-interfaces:interface-id
| | | +--ro srlg-membership* -> ../../../../te-global-attributes/srlgs/srlg/name
| | | +--ro admin-group* string
| | +--rw interface-ref
| | +--rw config
| | +--ro state
| | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| +--rw signaling-protocols
| | +--rw rsvp-te
| | | +--rw sessions
| | | | +--ro session* [local-index]

PYANG Tree
| | | | +--ro local-index -> ../state/local-index

| | | | +--ro state
| | | | +--ro local-index? uint64
| | | | +--ro source-address? inet:ip-address
| | | | +--ro destination-address? inet:ip-address
| | | | +--ro tunnel-id? uint16
| | | | +--ro lsp-id? uint16
| | | | +--ro session-name? string
| | | | +--ro type? identityref
| | | | +--ro label-in? oc-mplst:mpls-label
| | | | +--ro label-out? oc-mplst:mpls-label
| | | +--rw neighbors
| | | | +--ro neighbor* [address]
| | | | +--ro address -> ../state/address
| | | | +--ro state
| | | | +--ro address? inet:ip-address
| | | | +--ro neighbor-status? enumeration
| | | | +--ro refresh-reduction? boolean
| | | +--rw global
| | | | +--rw graceful-restart
| | | | | +--rw config
| | | | | | +--rw enable? boolean
| | | | | | +--rw restart-time? uint32
| | | | | | +--rw recovery-time? uint32
| | | | | +--ro state
| | | | | +--ro enable? boolean
| | | | | +--ro restart-time? uint32
| | | | | +--ro recovery-time? uint32
| | | | +--rw hellos
| | | | | +--rw config
| | | | | | +--rw hello-interval? uint16
| | | | | +--ro state
| | | | | +--ro hello-interval? uint16
| | | | +--ro state
| | | | +--ro counters
| | | | +--ro in-path-messages? yang:counter64

PYANG Tree
| | | | +--ro in-path-error-messages? yang:counter64

| | | | +--ro in-path-tear-messages? yang:counter64
| | | | +--ro in-reservation-messages? yang:counter64
| | | | +--ro in-reservation-error-messages? yang:counter64
| | | | +--ro in-reservation-tear-messages? yang:counter64
| | | | +--ro in-hello-messages? yang:counter64
| | | | +--ro in-srefresh-messages? yang:counter64
| | | | +--ro in-ack-messages? yang:counter64
| | | | +--ro out-path-messages? yang:counter64
| | | | +--ro out-path-error-messages? yang:counter64
| | | | +--ro out-path-tear-messages? yang:counter64
| | | | +--ro out-reservation-messages? yang:counter64
| | | | +--ro out-reservation-error-messages? yang:counter64
| | | | +--ro out-reservation-tear-messages? yang:counter64
| | | | +--ro out-hello-messages? yang:counter64
| | | | +--ro out-srefresh-messages? yang:counter64
| | | | +--ro out-ack-messages? yang:counter64
| | | +--rw interface-attributes
| | | | +--rw interface* [interface-id]
| | | | +--rw interface-id -> ../config/interface-id
| | | | +--rw config
| | | | | +--rw interface-id? openconfig-interfaces:interface-id
| | | | | +--rw ipi-oc-ni-augments:enabled? boolean
| | | | +--ro state
| | | | | +--ro interface-id? openconfig-interfaces:interface-id
| | | | | +--ro ipi-oc-ni-augments:enabled? boolean
| | | | +--rw interface-ref
| | | | | +--rw config
| | | | | | +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | | | +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| | | | | +--ro state
| | | | | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| | | | +--rw hellos

PYANG Tree
| | | | | +--rw hello-interval? uint16

| | | | +--ro state
| | | | +--ro hello-interval? uint16
| | | +--rw ipi-oc-ni-augments:config
| | | | +--rw ipi-oc-ni-augments:enabled? empty
| | | +--ro ipi-oc-ni-augments:state
| | | +--ro ipi-oc-ni-augments:enabled? empty
| | +--rw ldp
| | +--rw global
| | | +--rw config
| | | | +--rw lsr-id? openconfig-inet-types:ipv4-address
| | | +--ro state
| | | | +--ro lsr-id? openconfig-inet-types:ipv4-address
| | | +--rw graceful-restart
| | | | | +--rw reconnect-time? uint16
| | | | | +--rw recovery-time? uint16
| | | | | +--rw helper-enable? boolean
| | | | +--ro state
| | | | +--ro reconnect-time? uint16
| | | | +--ro recovery-time? uint16
| | | | +--ro helper-enable? boolean
| | | +--rw authentication
| | | +--rw config
| | | | +--rw authentication-key? openconfig-types:routing-password
| | | +--ro state
| | | +--ro authentication-key? openconfig-types:routing-password
| | +--rw interface-attributes
| | | +--rw config
| | | | +--rw hello-holdtime? uint16
| | | | +--rw hello-interval? uint16
| | | +--ro state
| | | | +--ro hello-holdtime? uint16
| | | +--rw interfaces
| | | +--rw interface* [interface-id]

PYANG Tree
| | | +--rw interface-id -> ../config/interface-id

| | | +--rw config
| | | | +--rw interface-id? openconfig-interfaces:interface-id
| | | +--ro state
| | | | +--ro interface-id? openconfig-interfaces:interface-id
| | | +--rw interface-ref
| | | | | +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | | +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| | | | +--ro state
| | | | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
| | | +--rw address-families
| | | +--rw address-family* [afi-name]
| | | +--rw afi-name -> ../config/afi-name
| | | +--rw config
| | | | +--rw afi-name? oc-ldp:mpls-ldp-afi
| | | | +--rw enabled? boolean
| | | +--ro state
| | | +--ro afi-name? oc-ldp:mpls-ldp-afi
| | | +--ro enabled? boolean
| | +--rw targeted
| | | +--rw config
| | | +--ro state
| | | +--rw address-families
| | | +--rw address-family* [afi-name]
| | | +--rw afi-name -> ../config/afi-name

PYANG Tree
| | | +--rw config
| | | | +--rw afi-name? oc-ldp:mpls-ldp-afi
| | | +--ro state
| | | | +--ro afi-name? oc-ldp:mpls-ldp-afi
| | | +--rw targets
| | | +--rw target* [remote-address]
| | | +--rw remote-address openconfig-inet-types:ipv4-address
| | | +--rw config
| | | | +--rw remote-address? openconfig-inet-types:ipv4-address
| | | | +--rw local-address? openconfig-inet-types:ipv4-address
| | | +--ro state
| | | +--ro remote-address? openconfig-inet-types:ipv4-address
| | | +--ro local-address? openconfig-inet-types:ipv4-address
| | | +--ro hello-holdtime? uint16
| | | +--ro hello-interval? uint16
| | +--rw neighbors
| | | +--rw neighbor* [lsr-id label-space-id]
| | | +--rw lsr-id openconfig-inet-types:ipv4-address
| | | +--rw label-space-id -> ../config/label-space-id
| | | +--rw config
| | | | +--rw lsr-id? openconfig-inet-types:ipv4-address
| | | | +--rw label-space-id? uint16
| | | +--ro state
| | | | +--ro lsr-id? openconfig-inet-types:ipv4-address
| | | | +--ro label-space-id? uint16
| | | | +--ro session-state? enumeration
| | | | +--ro negotiated-label-advertisement-mode? label-advertisement-mode
| | | +--ro hello-adjacencies
| | | | +--ro hello-adjacency* [remote-address local-address]
| | | | +--ro remote-address openconfig-inet-types:ipv4-address
| | | | +--ro local-address openconfig-inet-types:ipv4-address
| | | | +--ro state
| | | | | +--ro remote-address? openconfig-inet-types:ipv4-address
| | | | | +--ro local-address? openconfig-inet-types:ipv4-address

PYANG Tree
| | | | | +--ro adjacency-type? oc-ldp:mpls-ldp-adjacency-type

| | | | +--ro interface-ref
| | | | +--ro state
| | | | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../
| | | +--rw authentication
| | | +--rw config
| | | | +--rw authentication-key? openconfig-types:routing-password
| | | +--ro state
| | | +--ro authentication-key? openconfig-types:routing-password
| | +--rw ipi-oc-ni-augments:config
| | | +--rw ipi-oc-ni-augments:enabled? boolean
| | +--ro ipi-oc-ni-augments:state
| | +--ro ipi-oc-ni-augments:enabled? boolean
| +--rw lsps
| +--rw constrained-path
| +--rw named-explicit-paths
| | +--rw named-explicit-path* [name]
| | +--rw name -> ../config/name
| | +--rw config
| | | +--rw name? string
| | +--ro state
| | +--rw explicit-route-objects
| | +--rw explicit-route-object* [index]
| | +--rw index -> ../config/index
| | +--rw config
| | | +--rw address? openconfig-inet-types:ipv4-address
| | | +--rw hop-type? mpls-hop-type
| | | +--rw index? uint8
| | +--ro state
| | +--ro address? openconfig-inet-types:ipv4-address
| | +--ro hop-type? mpls-hop-type
| +--rw tunnels
| +--rw tunnel* [name]

PYANG Tree

| +--rw config
| | +--rw signaling-protocol? identityref
| | +--rw admin-status? identityref
| | +--rw metric-type? identityref
| | +--rw metric? int32
| | +--rw shortcut-eligible? boolean
| | +--rw protection-style-requested? identityref
| | +--rw source? openconfig-inet-types:ipv4-address
| | +--rw ipi-oc-ni-augments:protection-role? identityref
| +--ro state
| | +--ro signaling-protocol? identityref
| | +--ro admin-status? identityref
| | +--ro metric-type? identityref
| | +--ro metric? int32
| | +--ro shortcut-eligible? boolean
| | +--ro protection-style-requested? identityref
| | +--ro source? openconfig-inet-types:ipv4-address
| | +--ro role? identityref
| | +--ro ipi-oc-ni-augments:protection-role? identityref
| +--rw bandwidth
| | +--rw config
| | | +--rw specification-type? te-bandwidth-type
| | | +--rw set-bandwidth? oc-mplst:bandwidth-kbps
| | +--ro state
| | | +--ro specification-type? te-bandwidth-type
| | | +--ro set-bandwidth? oc-mplst:bandwidth-kbps
| | | +--ro signaled-bandwidth? oc-mplst:bandwidth-kbps
| | +--rw auto-bandwidth
| | +--rw config

PYANG Tree
| | | +--rw min-bw? oc-mplst:bandwidth-kbps

| | | +--rw max-bw? oc-mplst:bandwidth-kbps
| | | +--rw adjust-interval? uint32
| | +--ro state
| | | +--ro min-bw? oc-mplst:bandwidth-kbps
| | | +--ro max-bw? oc-mplst:bandwidth-kbps
| | | +--ro adjust-interval? uint32
| | | +--ro interval-high-bw? oc-mplst:bandwidth-kbps
| | +--rw overflow
| | | +--rw config
| | | | +--rw overflow-threshold? openconfig-types:percentage
| | | | +--rw trigger-event-count? uint16
| | | +--ro state
| | | +--ro overflow-threshold? openconfig-types:percentage
| | | +--ro trigger-event-count? uint16
| | +--rw underflow
| | +--rw config
| | | +--rw underflow-threshold? openconfig-types:percentage
| | | +--rw trigger-event-count? uint16
| | +--ro state
| | +--ro underflow-threshold? openconfig-types:percentage
| | +--ro trigger-event-count? uint16
| +--rw p2p-tunnel-attributes
| +--rw config
| | +--rw destination? openconfig-inet-types:ipv4-address
| +--ro state
| | +--ro destination? openconfig-inet-types:ipv4-address
| +--rw p2p-primary-path
| | +--rw p2p-primary-path* [name]
| | +--rw config
| | | +--rw path-computation-method? identityref
| | | +--rw use-cspf? boolean
| | | +--rw explicit-path-name? -> ../../../../../../../named-explicit-paths/named-explicit-path/config/
name
| | | +--rw setup-priority? uint8

PYANG Tree
| | | +--rw hold-priority? uint8

| | | +--rw retry-timer? uint16
| | +--ro state
| | | +--ro path-computation-method? identityref
| | | +--ro use-cspf? boolean
| | | +--ro explicit-path-name? -> ../../../../../../../named-explicit-paths/named-explicit-path/config/
name
| | | +--ro setup-priority? uint8
| | | +--ro hold-priority? uint8
| | | +--ro retry-timer? uint16
| | | +--ro associated-rsvp-sessions* -> ../../../../../../../../../signaling-protocols/rsvp-te/sessions/session/
local-index
| | +--rw path-metric-bound-constraints
| | | +--rw path-metric-bound-constraint* [type]
| | | +--rw type -> ../config/type
| | | +--rw config
| | | | +--rw type? identityref
| | | | +--rw metric-upper-bound? uint16
| | | +--ro state
| | | +--ro type? identityref
| | | +--ro metric-upper-bound? uint16
| | +--rw admin-groups
| | +--rw config
| | | +--rw exclude-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
group/admin-group-name
| | | +--rw include-all-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | | +--rw include-any-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | +--ro state
| | +--ro exclude-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | +--ro include-all-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | +--ro include-any-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| +--rw p2p-secondary-paths
| +--rw p2p-secondary-path* [name]

PYANG Tree

| +--rw config
| | +--rw path-computation-method? identityref
| | +--rw use-cspf? boolean
| | +--rw explicit-path-name? -> ../../../../../../../named-explicit-paths/named-explicit-path/config/
name
| | +--rw setup-priority? uint8
| | +--rw hold-priority? uint8
| | +--rw retry-timer? uint16
| +--ro state
| | +--ro path-computation-method? identityref
| | +--ro use-cspf? boolean
| | +--ro explicit-path-name? -> ../../../../../../../named-explicit-paths/named-explicit-path/config/
name
| | +--ro setup-priority? uint8
| | +--ro hold-priority? uint8
| | +--ro retry-timer? uint16
| | +--ro associated-rsvp-sessions* -> ../../../../../../../../../signaling-protocols/rsvp-te/sessions/session/
local-index
| +--rw path-metric-bound-constraints
| | +--rw path-metric-bound-constraint* [type]
| | +--rw type -> ../config/type
| | +--rw config
| | | +--rw type? identityref
| | | +--rw metric-upper-bound? uint16
| | +--ro state
| | +--ro metric-upper-bound? uint16
| +--rw admin-groups
| +--rw config
| | +--rw exclude-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | +--rw include-all-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| | +--rw include-any-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-

PYANG Tree
| +--ro state
| +--ro exclude-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| +--ro include-all-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
| +--ro include-any-group* -> ../../../../../../../../../../te-global-attributes/mpls-admin-groups/admin-
+--rw vlans
| +--rw vlan* [vlan-id]
| +--rw vlan-id -> ../config/vlan-id
| +--rw config
| | +--rw vlan-id? oc-vlan-types:vlan-id
| | +--rw status? enumeration
| +--ro state
| | +--ro vlan-id? oc-vlan-types:vlan-id
| | +--ro status? enumeration
| +--rw members
| +--ro member* []
| +--ro state
| +--ro interface? base-interface-ref
+--rw protocols
+--rw protocol* [identifier name]
+--rw identifier -> ../config/identifier
+--rw config
| +--rw identifier? identityref
| +--rw default-metric? uint32
+--ro state
| +--ro identifier? identityref
| +--ro default-metric? uint32
+--rw static-routes

PYANG Tree
| +--rw static* [prefix]

| +--rw prefix -> ../config/prefix
| +--rw config
| | +--rw prefix? inet:ip-prefix
| | +--rw set-tag? oc-pt:tag-type
| +--ro state
| | +--ro prefix? inet:ip-prefix
| | +--ro set-tag? oc-pt:tag-type
| +--rw next-hops
| +--rw next-hop* [index]
| +--rw config
| | +--rw index? string
| | +--rw next-hop? union
| | +--rw metric? uint32
| +--ro state
| | +--ro index? string
| | +--ro next-hop? union
| | +--ro recurse? boolean
| | +--ro metric? uint32
| | +--ro preference? uint32
| +--rw enable-bfd
| | +--rw config
| | | +--rw enabled? boolean
| | +--ro state
| +--rw config
| +--ro state

PYANG Tree
+--rw bgp
| +--rw global
| | +--rw config
| | | +--rw as openconfig-inet-types:as-number
| | | +--rw router-id? openconfig-yang-types:dotted-quad
| | +--ro state
| | | +--ro as openconfig-inet-types:as-number
| | | +--ro router-id? openconfig-yang-types:dotted-quad
| | | +--ro total-prefixes? uint32
| | +--rw confederation
| | | +--rw config
| | | | +--rw identifier? openconfig-inet-types:as-number
| | | | +--rw member-as* openconfig-inet-types:as-number
| | | +--ro state
| | | +--ro identifier? openconfig-inet-types:as-number
| | | +--ro member-as* openconfig-inet-types:as-number
| | +--rw graceful-restart
| | | +--rw config
| | | | +--rw restart-time? uint16
| | | | +--rw stale-routes-time? uint16
| | | | +--rw helper-only? boolean
| | | +--ro state
| | | +--ro restart-time? uint16
| | | +--ro stale-routes-time? uint16
| | | +--ro helper-only? boolean
| | +--rw route-selection-options
| | | +--rw config
| | | | +--rw always-compare-med? boolean
| | | | +--rw ignore-as-path-length? boolean
| | | | +--rw external-compare-router-id? boolean
| | | | +--rw enable-aigp? boolean
| | | +--ro state
| | | +--ro always-compare-med? boolean
| | | +--ro ignore-as-path-length? boolean

PYANG Tree
| | | +--ro external-compare-router-id? boolean

| | | +--ro enable-aigp? boolean
| | +--rw afi-safis
| | +--rw afi-safi* [afi-safi-name]
| | +--rw afi-safi-name -> ../config/afi-safi-name
| | +--rw config
| | | +--rw afi-safi-name? identityref
| | +--ro state
| | | +--ro afi-safi-name? identityref
| | | +--ro total-prefixes? uint32
| | +--rw use-multiple-paths
| | | +--rw config
| | | +--rw ebgp
| | | | | +--rw maximum-paths? uint32
| | | | +--ro state
| | | | +--ro maximum-paths? uint32
| | | +--rw ibgp
| | | +--rw config
| | | | +--rw maximum-paths? uint32
| | | +--ro state
| | | +--ro maximum-paths? uint32
| | +--rw add-paths
| | +--rw config
| | | +--rw receive? boolean
| | | +--rw send? boolean
| | | +--rw send-max? uint8
| | +--ro state
| | +--ro receive? boolean
| | +--ro send? boolean
| | +--ro send-max? uint8
| +--rw neighbors
| | +--rw neighbor* [neighbor-address]
| | +--rw neighbor-address -> ../config/neighbor-address
| | +--rw config
| | | +--rw peer-group? -> ../../../../peer-groups/peer-group/peer-group-name

PYANG Tree
| | | +--rw neighbor-address? openconfig-inet-types:ip-address

| | | +--rw peer-as? openconfig-inet-types:as-number
| | | +--rw local-as? openconfig-inet-types:as-number
| | | +--rw auth-password? openconfig-types:routing-password
| | | +--rw remove-private-as? oc-bgp-types:remove-private-as-option
| | | +--rw description? string
| | +--ro state
| | | +--ro peer-group? -> ../../../../peer-groups/peer-group/peer-group-name
| | | +--ro neighbor-address? openconfig-inet-types:ip-address
| | | +--ro peer-as? openconfig-inet-types:as-number
| | | +--ro local-as? openconfig-inet-types:as-number
| | | +--ro auth-password? openconfig-types:routing-password
| | | +--ro remove-private-as? oc-bgp-types:remove-private-as-option
| | | +--ro description? string
| | +--rw timers
| | | +--rw config
| | | | +--rw connect-retry? uint16
| | | | +--rw hold-time? uint16
| | | | +--rw keepalive-interval? uint16
| | | | +--rw minimum-advertisement-interval? uint16
| | | +--ro state
| | | +--ro connect-retry? uint16
| | | +--ro hold-time? uint16
| | | +--ro keepalive-interval? uint16
| | | +--ro minimum-advertisement-interval? uint16
| | +--rw transport
| | | +--rw config
| | | | +--rw passive-mode? boolean
| | | | +--rw local-address? union
| | | +--ro state
| | | +--ro passive-mode? boolean
| | | +--ro local-address? union
| | | +--ro local-port? openconfig-inet-types:port-number
| | | +--ro remote-address? openconfig-inet-types:ip-address

PYANG Tree
| | | +--ro remote-port? openconfig-inet-types:port-number

| | +--rw ebgp-multihop
| | | +--rw config
| | | | +--rw multihop-ttl? uint8
| | | +--ro state
| | | +--ro multihop-ttl? uint8
| | +--rw route-reflector
| | | +--rw config
| | | | +--rw route-reflector-client? boolean
| | | +--ro state
| | | +--ro route-reflector-client? boolean
| | +--rw afi-safis
| | | +--rw afi-safi* [afi-safi-name]
| | | +--rw afi-safi-name -> ../config/afi-safi-name
| | | +--rw config
| | | | +--rw afi-safi-name? identityref
| | | +--ro state
| | | | +--ro afi-safi-name? identityref
| | | | +--ro enabled? boolean
| | | | +--ro prefixes
| | | | +--ro sent? uint32
| | | | +--ro installed? uint32
| | | +--rw graceful-restart
| | | | | +--rw enabled? boolean
| | | | +--ro state
| | | | +--ro received? boolean
| | | | +--ro advertised? boolean
| | | +--rw add-paths
| | | | | +--rw receive? boolean
| | | | | +--rw send? boolean

PYANG Tree
| | | | | +--rw send-max? uint8

| | | | +--ro state
| | | | +--ro receive? boolean
| | | | +--ro send? boolean
| | | | +--ro send-max? uint8
| | | +--rw apply-policy
| | | | | +--rw import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | | +--rw export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | +--ro state
| | | | +--ro import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | +--ro export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | +--rw ipv4-unicast
| | | | +--rw prefix-limit
| | | | | +--rw config
| | | | | | +--rw max-prefixes? uint32
| | | | | | +--rw prevent-teardown? boolean
| | | | | | +--rw warning-threshold-pct? openconfig-types:percentage
| | | | | +--ro state
| | | | | +--ro max-prefixes? uint32
| | | | | +--ro prevent-teardown? boolean
| | | | | +--ro warning-threshold-pct? openconfig-types:percentage
| | | | | +--rw send-default-route? boolean
| | | | +--ro state
| | | | +--ro send-default-route? boolean
| | | | | +--rw config
| | | | | +--ro state

PYANG Tree

| | | | +--ro state
| | | +--rw ipv4-labeled-unicast
| | | | | +--rw max-prefixes? uint32
| | | | | +--rw prevent-teardown? boolean
| | | | | +--rw warning-threshold-pct? openconfig-types:percentage
| | | | +--ro state
| | | | +--ro max-prefixes? uint32
| | | | +--ro prevent-teardown? boolean
| | | | +--ro warning-threshold-pct? openconfig-types:percentage
| | | | +--ro state
| | | +--rw l3vpn-ipv4-unicast
| | | | +--ro state

PYANG Tree
| | | | +--ro state
| | | +--rw l2vpn-vpls
| | | | +--ro state
| | | +--rw l2vpn-evpn
| | | +--rw prefix-limit
| | | +--rw config
| | | | +--rw max-prefixes? uint32
| | | | +--rw prevent-teardown? boolean
| | | | +--rw warning-threshold-pct? openconfig-types:percentage
| | | +--ro state
| | | +--ro max-prefixes? uint32
| | | +--ro prevent-teardown? boolean
| | | +--ro warning-threshold-pct? openconfig-types:percentage
| | +--rw enable-bfd
| | +--rw config
| | +--ro state
| +--rw peer-groups

PYANG Tree
| | +--rw peer-group* [peer-group-name]

| | +--rw peer-group-name -> ../config/peer-group-name
| | +--rw config
| | | +--rw peer-group-name? string
| | | +--rw peer-as? openconfig-inet-types:as-number
| | | +--rw local-as? openconfig-inet-types:as-number
| | | +--rw auth-password? openconfig-types:routing-password
| | | +--rw description? string
| | +--ro state
| | | +--ro peer-group-name? string
| | | +--ro peer-as? openconfig-inet-types:as-number
| | | +--ro local-as? openconfig-inet-types:as-number
| | | +--ro auth-password? openconfig-types:routing-password
| | | +--ro description? string
| | +--rw timers
| | | +--rw config
| | | | +--rw connect-retry? uint16
| | | | +--rw hold-time? uint16
| | | | +--rw keepalive-interval? uint16
| | | | +--rw minimum-advertisement-interval? uint16
| | | +--ro state
| | | +--ro connect-retry? uint16
| | | +--ro hold-time? uint16
| | | +--ro keepalive-interval? uint16
| | | +--ro minimum-advertisement-interval? uint16
| | +--rw transport
| | | +--rw config
| | | | +--rw passive-mode? boolean
| | | | +--rw local-address? union
| | | +--ro state
| | | +--ro passive-mode? boolean
| | | +--ro local-address? union
| | +--rw ebgp-multihop
| | | +--rw config
| | | | +--rw multihop-ttl? uint8

PYANG Tree
| | | +--ro state
| | | +--ro multihop-ttl? uint8
| | +--rw route-reflector
| | | +--rw config
| | | | +--rw route-reflector-client? boolean
| | | +--ro state
| | | +--ro route-reflector-client? boolean
| | +--rw afi-safis
| | | +--rw afi-safi* [afi-safi-name]
| | | +--rw afi-safi-name -> ../config/afi-safi-name
| | | +--rw config
| | | | +--rw afi-safi-name? identityref
| | | +--ro state
| | | | +--ro afi-safi-name? identityref
| | | +--rw apply-policy
| | | | | +--rw import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | | +--rw export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | +--ro state
| | | | +--ro import-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | +--ro export-policy* -> /openconfig-routing-policy:routing-policy/policy-definitions/policy-definition/
name
| | | | | +--rw config
| | | | | +--ro state

PYANG Tree
| | | | +--ro state
| | | | | +--rw config
| | | | | +--ro state
| | | | +--ro state
| | | | +--ro state
| | | | +--ro state

PYANG Tree

| | | | +--ro state
| | | | +--ro state
| | | +--rw l2vpn-vpls
| | | | +--ro state
| | | +--rw l2vpn-evpn
| | | +--rw prefix-limit
| | | +--rw config
| | | | +--rw max-prefixes? uint32

PYANG Tree
| | | | +--rw prevent-teardown? boolean

| | | | +--rw warning-threshold-pct? openconfig-types:percentage
| | | +--ro state
| | | +--ro max-prefixes? uint32
| | | +--ro prevent-teardown? boolean
| | | +--ro warning-threshold-pct? openconfig-types:percentage
| | +--rw config
| | +--ro state
| +--ro rib
| +--ro afi-safis
| +--ro afi-safi* [afi-safi-name]
| +--ro afi-safi-name -> ../state/afi-safi-name
| +--ro state
| | +--ro afi-safi-name? identityref
| +--ro ipv4-unicast
| | +--ro loc-rib
| | | +--ro routes
| | | +--ro route* [prefix origin path-id]
| | | +--ro prefix -> ../state/prefix
| | | +--ro origin -> ../state/origin
| | | +--ro path-id -> ../state/path-id
| | | +--ro state
| | | +--ro prefix? openconfig-inet-types:ipv4-prefix
| | | +--ro origin? union
| | | +--ro path-id? uint32
| | | +--ro last-modified? openconfig-types:timeticks64
| | | +--ro valid-route? boolean
| | +--ro neighbors
| | +--ro neighbor* [neighbor-address]
| | +--ro neighbor-address -> ../state/neighbor-address
| | +--ro state
| | | +--ro neighbor-address? openconfig-inet-types:ip-address
| | +--ro adj-rib-in-post

PYANG Tree
| | | +--ro routes
| | | +--ro route* [prefix path-id]
| | | +--ro path-id -> ../state/path-id
| | | +--ro state
| | | +--ro prefix? openconfig-inet-types:ipv4-prefix
| | | +--ro path-id? uint32
| | | +--ro last-modified? openconfig-types:timeticks64
| | | +--ro valid-route? boolean
| | +--ro adj-rib-out-post
| | +--ro routes
| | +--ro route* [prefix path-id]
| | +--ro prefix -> ../state/prefix
| | +--ro path-id -> ../state/path-id
| | +--ro state
| | +--ro prefix? openconfig-inet-types:ipv4-prefix
| | +--ro path-id? uint32
| | +--ro last-modified? openconfig-types:timeticks64
| | +--ro valid-route? boolean
| +--ro ipv6-unicast
| +--ro loc-rib
| | +--ro routes
| | +--ro route* [prefix origin path-id]
| | +--ro origin -> ../state/origin
| | +--ro state
| | +--ro origin? union
| +--ro neighbors
| +--ro neighbor* [neighbor-address]
| +--ro neighbor-address -> ../state/neighbor-address
| +--ro state

PYANG Tree
| | +--ro neighbor-address? openconfig-inet-types:ip-address

| +--ro adj-rib-in-post
| | +--ro routes
| | +--ro route* [prefix path-id]
| | +--ro state
| +--ro adj-rib-out-post
| +--ro routes
| +--ro route* [prefix path-id]
| +--ro prefix -> ../state/prefix
| +--ro path-id -> ../state/path-id
| +--ro state
| +--ro prefix? openconfig-inet-types:ipv6-prefix
| +--ro path-id? uint32
| +--ro last-modified? openconfig-types:timeticks64
| +--ro valid-route? boolean
+--rw ospfv2
| +--rw global
| | +--rw config
| | | +--rw router-id? yang:dotted-quad
| | | +--rw summary-route-cost-mode? enumeration
| | | +--rw log-adjacency-changes? boolean
| | +--ro state
| | | +--ro router-id? yang:dotted-quad
| | | +--ro summary-route-cost-mode? enumeration
| | | +--ro log-adjacency-changes? boolean
| | +--rw timers
| | | +--rw spf
| | | | | +--rw initial-delay? uint32
| | | | | +--rw maximum-delay? uint32

PYANG Tree
| | | | +--ro state
| | | | +--ro initial-delay? uint32
| | | | +--ro maximum-delay? uint32
| | | | +--ro timer-type? enumeration
| | | +--rw max-metric
| | | | | +--rw set? boolean
| | | | | +--rw include* identityref
| | | | +--ro state
| | | | +--ro set? boolean
| | | | +--ro include* identityref
| | | +--rw lsa-generation
| | | +--rw config
| | | | +--rw initial-delay? uint32
| | | | +--rw maximum-delay? uint32
| | | +--ro state
| | | +--ro initial-delay? uint32
| | | +--ro maximum-delay? uint32
| | | +--ro timer-type? enumeration
| | +--rw graceful-restart
| | | +--rw config
| | | +--ro state
| | +--rw mpls
| | +--rw config
| | | +--rw traffic-engineering-extensions? boolean
| | +--ro state
| | +--ro traffic-engineering-extensions? boolean
| +--rw areas
| +--rw area* [identifier]
| +--rw identifier -> ../config/identifier
| +--rw config
| | +--rw identifier? oc-ospf-types:ospf-area-identifier
| +--ro state
| | +--ro identifier? oc-ospf-types:ospf-area-identifier

PYANG Tree
| +--rw interfaces
| | +--rw interface* [id]
| | +--rw id -> ../config/id
| | +--rw config
| | | +--rw id? string
| | | +--rw network-type? identityref
| | | +--rw priority? uint8
| | | +--rw authentication-type? string
| | | +--rw metric? oc-ospf-types:ospf-metric
| | | +--rw passive? boolean
| | +--ro state
| | | +--ro id? string
| | | +--ro network-type? identityref
| | | +--ro priority? uint8
| | | +--ro authentication-type? string
| | | +--ro metric? oc-ospf-types:ospf-metric
| | | +--ro passive? boolean
| | +--rw interface-ref
| | | +--rw config
| | | | +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| | | | +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../
| | | +--ro state
| | | +--ro interface? -> /openconfig-interfaces:interfaces/interface/name
| | | +--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../
| | +--rw timers
| | | +--rw config
| | | | +--rw dead-interval? uint32
| | | | +--rw retransmission-interval? uint32
| | | +--ro state
| | | +--ro dead-interval? uint32
| | | +--ro hello-interval? uint32
| | | +--ro retransmission-interval? uint32
| | +--rw mpls
| | | +--rw config

PYANG Tree
| | | | +--rw traffic-engineering-metric? uint32

| | | +--ro state
| | | | +--ro traffic-engineering-metric? uint32
| | | +--rw igp-ldp-sync
| | | +--rw config
| | | | +--rw post-session-up-delay? uint32
| | | +--ro state
| | | +--ro post-session-up-delay? uint32
| | +--rw lsa-filter
| | | +--rw config
| | | | +--rw all? boolean
| | | +--ro state
| | | +--ro all? boolean
| | +--rw config
| | +--ro state
| +--rw virtual-links
| +--rw virtual-link* [remote-router-id]
| +--rw remote-router-id -> ../config/remote-router-id
| +--rw config
| | +--rw remote-router-id? inet:ipv4-address-no-zone
| +--ro state
| +--ro remote-router-id? inet:ipv4-address-no-zone
| +--ro adjacency-state? identityref
+--rw isis
+--rw global
| +--rw config
| | +--rw net* oc-isis-types:net
| | +--rw maximum-area-addresses? uint8
| | +--rw level-capability? oc-isis-types:level-type
| +--ro state
| | +--ro net* oc-isis-types:net

PYANG Tree
| | +--ro maximum-area-addresses? uint8

| | +--ro level-capability? oc-isis-types:level-type
| +--rw lsp-bit
| | +--rw overload-bit
| | +--rw config
| | | +--rw set-bit? boolean
| | | +--rw set-bit-on-boot? boolean
| | +--ro state
| | | +--ro set-bit? boolean
| | | +--ro set-bit-on-boot? boolean
| | +--rw reset-triggers
| | +--rw reset-trigger* [reset-trigger]
| | +--rw reset-trigger -> ../config/reset-trigger
| | +--rw config
| | | +--rw reset-trigger? identityref
| | | +--rw delay? uint32
| | +--ro state
| | +--ro reset-trigger? identityref
| | +--ro delay? uint32
| +--rw graceful-restart
| | +--rw config
| | +--ro state
| +--rw timers
| | +--rw config
| | | +--rw lsp-lifetime-interval? uint16
| | | +--rw lsp-refresh-interval? uint16
| | +--ro state
| | | +--ro lsp-lifetime-interval? uint16
| | | +--ro lsp-refresh-interval? uint16
| | +--rw spf
| | | +--rw config
| | | | +--rw spf-first-interval? uint64
| | | | +--rw spf-second-interval? uint64
| | | +--ro state

PYANG Tree
| | | +--ro spf-first-interval? uint64

| | | +--ro spf-second-interval? uint64
| | +--rw lsp-generation
| | +--rw config
| | | +--rw lsp-max-wait-interval? uint64
| | +--ro state
| | +--ro lsp-max-wait-interval? uint64
| +--rw transport
| | +--rw config
| | | +--rw lsp-mtu-size? uint16
| | +--ro state
| | +--ro lsp-mtu-size? uint16
| +--rw afi-safi
| | +--rw af* [afi-name safi-name]
| | +--rw afi-name -> ../config/afi-name
| | +--rw safi-name -> ../config/safi-name
| | +--rw config
| | | +--rw afi-name? identityref
| | | +--rw safi-name? identityref
| | | +--rw metric? uint32
| | +--ro state
| | +--ro afi-name? identityref
| | +--ro safi-name? identityref
| | +--ro metric? uint32
| +--rw inter-level-propagation-policies
| +--rw level1-to-level2
| | +--rw config
| | | +--rw default-import-policy? default-policy-type
| | +--ro state
| | +--ro default-import-policy? default-policy-type
| +--rw level2-to-level1
| +--rw config
| | +--rw default-import-policy? default-policy-type
| +--ro state
| +--ro default-import-policy? default-policy-type
+--rw levels

PYANG Tree
| +--rw level* [level-number]

| +--rw level-number -> ../config/level-number
| +--rw config
| | +--rw level-number? oc-isis-types:level-number
| | +--rw metric-style? oc-isis-types:metric-style
| +--ro state
| | +--ro level-number? oc-isis-types:level-number
| | +--ro metric-style? oc-isis-types:metric-style
| +--rw system-level-counters
| | +--ro state
| | +--ro corrupted-lsps? openconfig-yang-types:counter32
| | +--ro database-overloads? openconfig-yang-types:counter32
| | +--ro manual-address-drop-from-areas? openconfig-yang-types:counter32
| | +--ro exceed-max-seq-nums? openconfig-yang-types:counter32
| | +--ro seq-num-skips? openconfig-yang-types:counter32
| | +--ro own-lsp-purges? openconfig-yang-types:counter32
| | +--ro id-len-mismatch? openconfig-yang-types:counter32
| | +--ro part-changes? openconfig-yang-types:counter32
| | +--ro max-area-address-mismatches? openconfig-yang-types:counter32
| | +--ro auth-fails? openconfig-yang-types:counter32
| | +--ro spf-runs? openconfig-yang-types:counter32
| | +--ro auth-type-fails? openconfig-yang-types:counter32
| +--ro link-state-database
| | +--ro lsp* [lsp-id]
| | +--ro lsp-id -> ../state/lsp-id
| | +--ro state
| | | +--ro lsp-id? oc-isis-types:lsp-id
| | | +--ro remaining-lifetime? uint16
| | | +--ro sequence-number? string
| | | +--ro checksum? string
| | | +--ro pdu-length? uint16
| | | +--ro flags* enumeration
| | +--ro tlvs
| | +--ro tlv* [type]
| | +--ro type -> ../state/type
| | +--ro state

PYANG Tree

| | +--ro area-address
| | | +--ro state
| | | +--ro address* oc-isis-types:area-address
| | +--ro nlpid
| | | +--ro state
| | | +--ro nlpid* enumeration
| | +--ro hostname
| | | +--ro state
| | | +--ro hostname* string
| | +--ro ipv4-interface-addresses
| | | +--ro state
| | | +--ro address* inet:ipv4-address
| | +--ro ipv6-interface-addresses
| | | +--ro state
| | | +--ro address* inet:ipv6-address
| | +--ro ipv4-te-router-id
| | | +--ro state
| | | +--ro router-id* inet:ipv4-address
| | +--ro ipv6-te-router-id
| | | +--ro state
| | | +--ro router-id* inet:ipv6-address
| | +--ro is-reachability
| | | +--ro neighbors
| | | +--ro neighbor* [system-id]
| | | +--ro system-id -> ../state/system-id
| | | +--ro state
| | | | +--ro system-id? oc-isis-types:system-id
| | | +--ro default-metric
| | | +--ro state
| | | +--ro metric? uint8
| | +--ro ipv4-internal-reachability
| | | +--ro prefixes
| | | +--ro prefix* [prefix]
| | | +--ro state

PYANG Tree
| | | | +--ro prefix? inet:ipv4-prefix

| | | +--ro state
| | +--ro ipv4-external-reachability
| | | +--ro state
| | | +--ro state
| | +--ro extended-ipv4-reachability
| | | +--ro state
| | | | +--ro metric? oc-isis-types:wide-metric
| | | +--ro subtlvs
| | | +--ro subtlv* [type]
| | | +--ro type -> ../state/type
| | | +--ro state
| | | | +--ro type? identityref
| | | +--ro tag
| | | | +--ro state
| | | | +--ro tag32* uint32
| | | +--ro prefix-sids
| | | +--ro prefix-sid* [value]
| | | +--ro value -> ../state/value
| | | +--ro state
| | | +--ro value? uint32
| | | +--ro flags* enumeration
| | +--ro ipv6-reachability
| | +--ro prefixes

PYANG Tree
| | +--ro prefix* [prefix]

| | +--ro state
| | | +--ro up-down? boolean
| | | +--ro prefix? inet:ipv6-prefix
| | | +--ro metric? oc-isis-types:wide-metric
| | +--ro subtlvs
| | +--ro subtlv* [type]
| | +--ro type -> ../state/type
| | +--ro state
| | +--ro tag
| | +--ro state
| | +--ro tag32* uint32
| +--rw traffic-engineering
| | +--rw config
| | | +--rw ipv4-router-id? openconfig-inet-types:ipv4-address
| | | +--rw ipv6-router-id? openconfig-inet-types:ipv6-address
| | +--ro state
| | +--ro ipv4-router-id? openconfig-inet-types:ipv4-address
| | +--ro ipv6-router-id? openconfig-inet-types:ipv6-address
| +--rw authentication
| +--rw config
| | +--rw auth-password? openconfig-types:routing-password
| +--ro state
| +--ro auth-password? openconfig-types:routing-password
+--rw interfaces
+--rw interface* [interface-id]
+--rw interface-id -> ../config/interface-id
+--rw config
| +--rw interface-id? openconfig-interfaces:interface-id
| +--rw passive? boolean
| +--rw hello-padding? oc-isis-types:hello-padding-type
| +--rw circuit-type? oc-isis-types:circuit-type

PYANG Tree
+--ro state
| +--ro interface-id? openconfig-interfaces:interface-id
| +--ro passive? boolean
| +--ro hello-padding? oc-isis-types:hello-padding-type
| +--ro circuit-type? oc-isis-types:circuit-type
+--rw circuit-counters
| +--ro state
| +--ro adj-changes? openconfig-yang-types:counter32
| +--ro init-fails? openconfig-yang-types:counter32
| +--ro rejected-adj? openconfig-yang-types:counter32
| +--ro id-field-len-mismatches? openconfig-yang-types:counter32
| +--ro max-area-address-mismatches? openconfig-yang-types:counter32
| +--ro auth-type-fails? openconfig-yang-types:counter32
| +--ro auth-fails? openconfig-yang-types:counter32
| +--ro lan-dis-changes? openconfig-yang-types:counter32
| +--ro adj-number? uint32
+--rw afi-safi
| +--rw af* [afi-name safi-name]
| +--rw afi-name -> ../config/afi-name
| +--rw safi-name -> ../config/safi-name
| +--rw config
| | +--rw afi-name? identityref
| | +--rw safi-name? identityref
| +--ro state
| +--ro afi-name? identityref
| +--ro safi-name? identityref
+--rw levels
| +--rw level* [level-number]
| +--rw level-number -> ../config/level-number
| +--rw config
| | +--rw level-number? oc-isis-types:level-number
| +--ro state
| | +--ro level-number? oc-isis-types:level-number
| +--rw packet-counters

PYANG Tree
| | +--rw lsp
| | | +--ro state
| | | +--ro received? openconfig-yang-types:counter32
| | | +--ro sent? openconfig-yang-types:counter32
| | +--rw ish
| | | +--ro state
| | +--rw psnp
| | | +--ro state
| | +--rw csnp
| | | +--ro state
| | +--rw unknown
| | +--ro state
| | +--ro received? openconfig-yang-types:counter32
| | +--ro sent? openconfig-yang-types:counter32
| +--rw timers
| | +--rw config
| | | +--rw hello-interval? uint32
| | | +--rw hello-multiplier? uint8
| | +--ro state
| | +--ro hello-interval? uint32
| | +--ro hello-multiplier? uint8
| +--rw hello-authentication
| +--rw config
| | +--rw auth-password? openconfig-types:routing-password
| +--ro state
| +--ro auth-password? openconfig-types:routing-password
+--rw enable-bfd
| +--rw config
| +--ro state

PYANG Tree

+--rw mpls
| +--rw igp-ldp-sync
| +--rw config
| +--ro state
+--rw interface-ref
+--rw config
| +--rw interface? -> /openconfig-interfaces:interfaces/interface/name
| +--rw subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
+--ro state
+--ro interface? -> /openconfig-interfaces:interfaces/interface/name
+--ro subinterface? -> /openconfig-interfaces:interfaces/interface[oc-if:name=current()/../interface]/
module: openconfig-platform
+--rw components
+--rw component* [name]
+--rw config
+--ro state
| +--ro type? union
| +--ro id? string
| +--ro location? string
| +--ro mfg-name? string
| +--ro mfg-date? openconfig-yang-types:date
| +--ro hardware-version? string
| +--ro firmware-version? string
| +--ro software-version? string
| +--ro serial-no? string

PYANG Tree
| +--ro part-no? string

| +--ro clei-code? string
| +--ro removable? boolean
| +--ro oper-status? identityref
| +--ro empty? boolean
| +--ro parent? -> ../../../component/config/name
| +--ro temperature
| | +--ro instant? decimal64
| | +--ro avg? decimal64
| | +--ro min? decimal64
| | +--ro max? decimal64
| | +--ro interval? openconfig-types:stat-interval
| | +--ro alarm-status? boolean
| | +--ro alarm-threshold? decimal64
| | +--ro alarm-severity? identityref
| +--ro memory
| | +--ro available? uint64
| | +--ro utilized? uint64
| +--ro allocated-power? decimal64
| +--ro openconfig-alarms:equipment-failure? boolean
+--rw subcomponents
| +--ro subcomponent* [name]
| +--ro name -> ../state/name
| +--ro state
| +--ro name? -> ../../../../../component/config/name
+--rw port
| +--rw openconfig-platform-port:breakout-mode
| | +--rw openconfig-platform-port:groups
| | +--rw openconfig-platform-port:group* [index]
| | +--rw openconfig-platform-port:index -> ../config/index
| | +--rw openconfig-platform-port:config
| | | +--rw openconfig-platform-port:index? uint8
| | | +--rw openconfig-platform-port:num-breakouts? uint8
| | | +--rw openconfig-platform-port:breakout-speed? identityref
| | | +--rw openconfig-platform-port:num-physical-channels? uint8
| | +--ro openconfig-platform-port:state

PYANG Tree
| | +--ro openconfig-platform-port:index? uint8

| | +--ro openconfig-platform-port:num-breakouts? uint8
| | +--ro openconfig-platform-port:breakout-speed? identityref
| | +--ro openconfig-platform-port:num-physical-channels? uint8
| +--rw openconfig-transport-line-common:optical-port
| +--rw openconfig-transport-line-common:config
| | +--rw openconfig-transport-line-common:admin-state? openconfig-transport-types:admin-state-type
| +--ro openconfig-transport-line-common:state
| +--ro openconfig-transport-line-common:admin-state? openconfig-transport-types:admin-state-type
| +--ro openconfig-transport-line-common:optical-port-type? identityref
+--rw power-supply
| +--rw config
| +--ro state
| +--ro openconfig-platform-psu:enabled? boolean
| +--ro openconfig-platform-psu:capacity? decimal64
| +--ro openconfig-platform-psu:input-current? decimal64
| +--ro openconfig-platform-psu:input-voltage? decimal64
| +--ro openconfig-platform-psu:output-current? decimal64
| +--ro openconfig-platform-psu:output-voltage? decimal64
| +--ro openconfig-platform-psu:output-power? decimal64
+--rw fan
| +--ro state
| +--ro openconfig-platform-fan:speed? uint32
+--rw cpu
| +--rw openconfig-platform-cpu:utilization
| +--ro openconfig-platform-cpu:state
| +--ro openconfig-platform-cpu:instant? decimal64
| +--ro openconfig-platform-cpu:avg? decimal64
| +--ro openconfig-platform-cpu:interval? openconfig-types:stat-interval
+--rw openconfig-platform-linecard:linecard
| +--rw openconfig-platform-linecard:config
| | +--rw openconfig-platform-linecard:power-admin-state? oc-platform-types:component-power-type
| +--ro openconfig-platform-linecard:state
| +--ro openconfig-platform-linecard:power-admin-state? oc-platform-types:component-power-type
| +--ro openconfig-platform-linecard:slot-id? string
+--rw openconfig-platform-transceiver:transceiver

PYANG Tree
| +--rw openconfig-platform-transceiver:config
| | +--rw openconfig-platform-transceiver:enabled? boolean
| | +--rw openconfig-platform-transceiver:module-functional-type? identityref
| +--ro openconfig-platform-transceiver:state
| | +--ro openconfig-platform-transceiver:enabled? boolean
| | +--ro openconfig-platform-transceiver:module-functional-type? identityref
| | +--ro openconfig-platform-transceiver:present? enumeration
| | +--ro openconfig-platform-transceiver:form-factor? identityref
| | +--ro openconfig-platform-transceiver:connector-type? identityref
| | +--ro openconfig-platform-transceiver:vendor? string
| | +--ro openconfig-platform-transceiver:vendor-part? string
| | +--ro openconfig-platform-transceiver:vendor-rev? string
| | +--ro openconfig-platform-transceiver:ethernet-pmd? identityref
| | +--ro openconfig-platform-transceiver:sonet-sdh-compliance-code? identityref
| | +--ro openconfig-platform-transceiver:serial-no? string
| | +--ro openconfig-platform-transceiver:date-code? string
| | +--ro openconfig-platform-transceiver:supply-voltage
| | | +--ro openconfig-platform-transceiver:instant? decimal64
| | +--ro openconfig-platform-transceiver:output-power
| | +--ro openconfig-platform-transceiver:input-power
| | +--ro openconfig-platform-transceiver:laser-bias-current
| | +--ro openconfig-platform-transceiver:instant? decimal64
| +--rw openconfig-platform-transceiver:physical-channels
| | +--rw openconfig-platform-transceiver:channel* [index]
| | +--rw openconfig-platform-transceiver:index -> ../config/index
| | +--rw openconfig-platform-transceiver:config
| | | +--rw openconfig-platform-transceiver:index? uint16
| | | +--rw openconfig-platform-transceiver:target-output-power? decimal64
| | +--ro openconfig-platform-transceiver:state
| | +--ro openconfig-platform-transceiver:index? uint16
| | +--ro openconfig-platform-transceiver:target-output-power? decimal64
| | +--ro openconfig-platform-transceiver:laser-age? decimal64
| | +--ro openconfig-platform-transceiver:laser-temperature

PYANG Tree
| | +--ro openconfig-platform-transceiver:target-frequency-deviation
| | +--ro openconfig-platform-transceiver:output-frequency? decimal64
| | +--ro openconfig-platform-transceiver:output-power
| | +--ro openconfig-platform-transceiver:input-power
| | +--ro openconfig-platform-transceiver:laser-bias-current
| | +--ro openconfig-platform-transceiver:instant? decimal64
| +--rw openconfig-platform-transceiver:thresholds
| +--ro openconfig-platform-transceiver:threshold* [severity]
| +--ro openconfig-platform-transceiver:severity -> ../state/severity
| +--ro openconfig-platform-transceiver:state
| +--ro openconfig-platform-transceiver:severity? identityref
| +--ro openconfig-platform-transceiver:input-power-upper? decimal64
| +--ro openconfig-platform-transceiver:input-power-lower? decimal64
+--rw openconfig-terminal-device:optical-channel
+--rw openconfig-terminal-device:config
| +--rw openconfig-terminal-device:frequency? uint64
| +--rw openconfig-terminal-device:target-output-power? decimal64
| +--rw openconfig-terminal-device:operational-mode? uint16
+--ro openconfig-terminal-device:state
+--ro openconfig-terminal-device:frequency? openconfig-transport-types:frequency-type
+--ro openconfig-terminal-device:target-output-power? decimal64
+--ro openconfig-terminal-device:operational-mode? uint16
+--ro openconfig-terminal-device:line-port? -> /openconfig-platform:components/component/name
+--ro openconfig-terminal-device:output-power
| +--ro openconfig-terminal-device:instant? decimal64
+--ro openconfig-terminal-device:input-power
+--ro openconfig-terminal-device:laser-bias-current
+--ro openconfig-terminal-device:chromatic-dispersion
| +--ro openconfig-terminal-device:min? decimal64
| +--ro openconfig-terminal-device:max? decimal64

PYANG Tree
+--ro openconfig-terminal-device:polarization-mode-dispersion
| +--ro openconfig-terminal-device:avg? decimal64
+--ro openconfig-terminal-device:second-order-polarization-mode-dispersion
+--ro openconfig-terminal-device:polarization-dependent-loss
+--ro openconfig-terminal-device:modulator-bias-xi
+--ro openconfig-terminal-device:modulator-bias-xq
+--ro openconfig-terminal-device:modulator-bias-yi
+--ro openconfig-terminal-device:modulator-bias-yq
+--ro openconfig-terminal-device:modulator-bias-x-phase
+--ro openconfig-terminal-device:modulator-bias-y-phase
+--ro openconfig-terminal-device:osnr
+--ro openconfig-terminal-device:carrier-frequency-offset

PYANG Tree

+--ro openconfig-terminal-device:sop-roc
+--ro openconfig-terminal-device:modulation-error-ratio
+--ro openconfig-terminal-device:fec-uncorrectable-blocks? ietf-yang-types:counter64
+--ro openconfig-terminal-device:pre-fec-ber
+--ro openconfig-terminal-device:post-fec-ber
+--ro openconfig-terminal-device:esnr
+--ro openconfig-terminal-device:instant? decimal64
+--ro openconfig-terminal-device:avg? decimal64
+--ro openconfig-terminal-device:min? decimal64
+--ro openconfig-terminal-device:max? decimal64
module: openconfig-qos
+--rw qos
+--rw config
| +--rw ipi-oc-qos-deviations:ipi-qos-enabled? boolean
+--ro state
| +--ro ipi-oc-qos-deviations:ipi-qos-enabled? boolean
+--rw interfaces

PYANG Tree
| +--rw interface* [interface-id]

| +--rw interface-id -> ../config/interface-id
| +--rw config
| | +--rw interface-id? string
| +--ro state
| | +--ro interface-id? string
| | +--rw config
| | | +--rw interface? -> /oc-if:interfaces/interface/name
| | | +--rw subinterface? -> /oc-if:interfaces/interface[oc-if:name=current()/../interface]/subinterfaces/
subinterface/index
| | +--ro state
| | +--ro interface? -> /oc-if:interfaces/interface/name
| | +--ro subinterface? -> /oc-if:interfaces/interface[oc-if:name=current()/../interface]/subinterfaces/
subinterface/index
| +--rw input
| | +--rw classifiers
| | +--rw classifier* [type]
| | +--rw type -> ../config/type
| | +--rw config
| | | +--rw name? -> ../../../../../../../classifiers/classifier/config/name
| | | +--rw type? enumeration
| | +--ro state
| | | +--ro name? -> ../../../../../../../classifiers/classifier/config/name
| | | +--ro type? enumeration
| | +--rw terms
| | +--ro term* [id]
| | +--ro id -> ../state/id
| | +--ro state
| | +--ro id? -> ../../../../../../../../../classifiers/classifier[name=current()/../../../../config/name]/terms/
term/config/id
| | +--ro matched-packets? oc-yang:counter64
| | +--ro matched-octets? oc-yang:counter64
| +--rw output
| +--rw scheduler-policy
| +--rw config
| | +--rw name? -> ../../../../../../scheduler-policies/scheduler-policy/config/name

PYANG Tree
| +--ro state
| | +--ro name? -> ../../../../../../scheduler-policies/scheduler-policy/config/name
| +--ro schedulers
| +--ro scheduler* [sequence]
| +--ro sequence -> ../state/sequence
| +--ro state
| +--ro sequence? -> ../../../../../../../../scheduler-policies/scheduler-policy[name=current()/../../../../
config/name]/schedulers/scheduler/config/sequence
| +--ro conforming-pkts? oc-yang:counter64
| +--ro conforming-octets? oc-yang:counter64
| +--ro exceeding-pkts? oc-yang:counter64
| +--ro exceeding-octets? oc-yang:counter64
+--rw classifiers
| +--rw classifier* [name]
| +--rw config
| | +--rw type? enumeration
| +--ro state
| | +--ro type? enumeration
| +--rw terms
| +--rw term* [id]
| +--rw id -> ../config/id
| +--rw config
| | +--rw id? string
| +--ro state
| | +--ro id? string
| +--rw conditions
| | +--rw ipv4
| | +--rw config
| | +--ro state

PYANG Tree

| +--rw actions
| +--rw config
| | +--rw target-group? -> ../../../../../../../forwarding-groups/forwarding-group/config/name
| +--ro state
| +--ro target-group? -> ../../../../../../../forwarding-groups/forwarding-group/config/name
+--rw forwarding-groups
| +--rw forwarding-group* [name]
| +--rw config
| | +--rw fabric-priority? uint8
| | +--rw output-queue? -> ../../../../queues/queue/config/name
| +--ro state
| +--ro fabric-priority? uint8
| +--ro output-queue? -> ../../../../queues/queue/config/name
+--rw queues
| +--rw queue* [name]
| +--rw config
| | +--rw queue-id? uint8
| +--ro state
| +--ro queue-id? uint8
+--rw scheduler-policies
| +--rw scheduler-policy* [name]
| +--rw config
| +--ro state
| +--rw schedulers
| +--rw scheduler* [sequence]
| +--rw sequence -> ../config/sequence

PYANG Tree
| +--rw config
| | +--rw sequence? uint32
| | +--rw priority? enumeration
| +--ro state
| | +--ro sequence? uint32
| | +--ro priority? enumeration
| +--rw inputs
| | +--rw input* [id]
| | +--rw id -> ../config/id
| | +--rw config
| | | +--rw id? string
| | | +--rw input-type? enumeration
| | | +--rw queue -> ../../../../../../../../queues/queue/name
| | | +--rw weight? uint64
| | +--ro state
| | +--ro id? string
| | +--ro input-type? enumeration
| | +--ro queue? -> ../../../../../../../../queues/queue/name
| | +--ro weight? uint64
| +--rw one-rate-two-color
| +--rw config
| | +--rw cir? uint64
| | +--rw queuing-behavior? oc-qos-types:queue-behavior
| | +--rw max-queue-depth-bytes? uint32
| +--ro state
| +--ro cir? uint64
| +--ro queuing-behavior? oc-qos-types:queue-behavior
| +--ro max-queue-depth-bytes? uint32
+--rw queue-management-profiles
+--rw queue-management-profile* [name]
+--rw config
+--ro state

PYANG Tree

+--rw wred
+--rw uniform
+--rw config
| +--rw min-threshold? uint64
| +--rw max-threshold? uint64
+--ro state
+--ro min-threshold? uint64
+--ro max-threshold? uint64
module: openconfig-routing-policy
+--rw routing-policy
+--rw defined-sets
| +--rw tag-sets
| | +--rw tag-set* [name]
| | +--rw config
| | | +--rw tag-value* openconfig-policy-types:tag-type
| | +--ro state
| | +--ro tag-value* openconfig-policy-types:tag-type
| +--rw openconfig-bgp-policy:bgp-defined-sets
| +--rw openconfig-bgp-policy:ext-community-sets
| +--rw openconfig-bgp-policy:ext-community-set* [ext-community-set-name]
| +--rw openconfig-bgp-policy:ext-community-set-name -> ../config/ext-community-set-name
| +--rw openconfig-bgp-policy:config
| +--rw openconfig-bgp-policy:ext-community-set-name? string
| +--rw openconfig-bgp-policy:ext-community-member* union
| +--rw openconfig-bgp-policy:match-set-options? openconfig-policy-types:match-set-options-type
+--rw policy-definitions
+--rw policy-definition* [name]
+--rw config

PYANG Tree
+--ro state
+--rw statements
+--rw statement* [name]
+--rw config
| +--rw name? uint32
+--ro state
+--rw conditions
| +--rw config
| +--rw match-tag-set
| | +--rw config
| | | +--rw tag-set? -> ../../../../../../../../defined-sets/tag-sets/tag-set/name
| | +--ro state
| | +--ro tag-set? -> ../../../../../../../../defined-sets/tag-sets/tag-set/name
| +--rw openconfig-bgp-policy:bgp-conditions
| +--rw openconfig-bgp-policy:config
| | +--rw openconfig-bgp-policy:ext-community-set? -> /openconfig-routing-policy:routing-policy/defined-
sets/openconfig-bgp-policy:bgp-defined-sets/ext-community-sets/ext-community-set/ext-community-set-name
| +--ro openconfig-bgp-policy:state
| +--ro openconfig-bgp-policy:ext-community-set? -> /openconfig-routing-policy:routing-policy/defined-
sets/openconfig-bgp-policy:bgp-defined-sets/ext-community-sets/ext-community-set/ext-community-set-name
+--rw actions
+--rw config
| +--rw policy-result? policy-result-type
+--ro state
| +--ro policy-result? policy-result-type
+--rw openconfig-bgp-policy:bgp-actions
+--rw openconfig-bgp-policy:config
| +--rw openconfig-bgp-policy:set-route-origin? openconfig-bgp-types:bgp-origin-attr-type
| +--rw openconfig-bgp-policy:set-local-pref? uint32
+--ro openconfig-bgp-policy:state
+--ro openconfig-bgp-policy:set-route-origin? openconfig-bgp-types:bgp-origin-attr-type
+--ro openconfig-bgp-policy:set-local-pref? uint32

PYANG Tree
module: openconfig-system
+--rw system
+--rw config
| +--rw hostname? openconfig-inet-types:domain-name
+--ro state
| +--ro hostname? openconfig-inet-types:domain-name
| +--ro current-datetime? string
| +--ro boot-time? openconfig-types:timeticks64
+--rw clock
| +--rw config
| | +--rw timezone-name? timezone-name-type
| +--ro state
| +--ro timezone-name? timezone-name-type
+--rw logging
| +--rw remote-servers
| +--rw remote-server* [host]
| +--rw host -> ../config/host
| +--rw config
| | +--rw host? openconfig-inet-types:host
| | +--rw network-instance? oc-ni:network-instance-ref
| | +--rw remote-port? openconfig-inet-types:port-number
| +--ro state
| | +--ro host? openconfig-inet-types:host
| | +--ro network-instance? oc-ni:network-instance-ref
| | +--ro remote-port? openconfig-inet-types:port-number
| +--rw selectors
| +--rw selector* [facility severity]
| +--rw facility -> ../config/facility
| +--rw severity -> ../config/severity
| +--rw config
| | +--rw facility? identityref
| | +--rw severity? syslog-severity
| +--ro state
| +--ro facility? identityref
| +--ro severity? syslog-severity

PYANG Tree
+--ro alarms
+--ro alarm* [id]
+--ro id -> ../state/id
+--ro config
+--ro state
+--ro id? string
+--ro resource? string
+--ro text? string
+--ro time-created? openconfig-types:timeticks64
+--ro severity? identityref
+--ro type-id? union
+--ro ipi-oc-sys-deviations:alarm-reported-timestamp? string
module: openconfig-terminal-device
+--rw terminal-device
+--rw config
+--rw logical-channels
| +--rw channel* [index]
| +--rw config
| | +--rw admin-state? openconfig-transport-types:admin-state-type
| | +--rw logical-channel-type? identityref
| | +--rw loopback-mode? openconfig-transport-types:loopback-mode-type
| +--ro state
| | +--ro admin-state? openconfig-transport-types:admin-state-type
| | +--ro rate-class? identityref
| | +--ro trib-protocol? identityref
| | +--ro logical-channel-type? identityref
| | +--ro loopback-mode? openconfig-transport-types:loopback-mode-type
| | +--ro test-signal? boolean
| +--rw otn
| | +--ro state

PYANG Tree
| | +--ro errored-blocks? ietf-yang-types:counter64

| | +--ro fec-uncorrectable-blocks? ietf-yang-types:counter64
| | +--ro pre-fec-ber
| | | +--ro instant? uint64
| | +--ro post-fec-ber
| | | +--ro instant? uint64
| | +--ro q-value
| +--rw ethernet
| | +--ro state
| | +--ro in-block-errors? openconfig-yang-types:counter64
| | +--ro out-8021q-frames? openconfig-yang-types:counter64
| | +--ro in-pcs-bip-errors? openconfig-yang-types:counter64
| | +--ro out-pcs-bip-errors? openconfig-yang-types:counter64
| | +--ro out-block-errors? openconfig-yang-types:counter64
| | +--ro fec-uncorrectable-blocks? ietf-yang-types:counter64
| | +--ro pre-fec-ber
| | | +--ro instant? decimal64
| | | +--ro avg? decimal64
| | | +--ro min? decimal64
| | | +--ro max? decimal64
| | +--ro post-fec-ber
| | | +--ro avg? decimal64
| | | +--ro min? decimal64
| | | +--ro max? decimal64
| | +--ro q-value
| | +--ro esnr
| +--rw ingress
| | +--ro state
| | +--ro transceiver? -> /openconfig-platform:components/component/name
| | +--ro interface? openconfig-interfaces:base-interface-ref
| +--rw logical-channel-assignments
| +--rw assignment* [index]

PYANG Tree

| +--rw config
| +--ro state
| +--ro index? uint32
| +--ro assignment-type? enumeration
| +--ro logical-channel? -> /terminal-device/logical-channels/channel/index
| +--ro optical-channel? -> /openconfig-platform:components/component/name
| +--ro allocation? decimal64
+--rw operational-modes
+--ro mode* [mode-id]
+--ro mode-id -> ../state/mode-id
+--ro state
+--ro mode-id? uint16
+--ro description? string
+--ro vendor-id? string
module: openconfig-terminal-device-properties
+--ro operational-modes
+--ro mode-descriptor* [mode-id]
+--ro mode-id -> ../state/mode-id
+--ro state
| +--ro mode-id? uint16
| +--ro mode-type? identityref
+--ro explicit-mode
+--ro operational-mode-capabilities
| +--ro state
| +--ro modulation-format? union
| +--ro bit-rate? openconfig-terminal-device-property-types:bit-rate
| +--ro baud-rate? decimal64
+--ro optical-channel-config-value-constraints
+--ro state
+--ro min-central-frequency? openconfig-transport-types:frequency-type
+--ro max-central-frequency? openconfig-transport-types:frequency-type
+--ro adjustment-granularity? openconfig-terminal-device-property-types:adjustment-granularity

PYANG Tree
+--ro min-output-power? decimal64

+--ro max-output-power? decimal64
module: ipi-oc-if-deviations
+--rw lacp-mode? openconfig-lacp:lacp-activity-type
+--ro lacp-mode? openconfig-lacp:lacp-activity-type
+--rw load-interval? uint16
+--ro load-interval? uint16

Ocnos Dc Openconfig Cmdref

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Ocnos Dc Openconfig Cmdref

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ocnos Dc Openconfig Cmdref

Uploaded by

Copyright:

Available Formats

OpenConfig Command Reference

IP Infusion Inc. Proprietary

For support, questions, or comments via E-mail, contact:

IP Infusion Inc. Proprietary 2

© 2024 IP Infusion Inc. Proprietary 3

ISIS OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

© 2024 IP Infusion Inc. Proprietary 4

OcNOS NetConf Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

© 2024 IP Infusion Inc. Proprietary 5

OcNOS CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

© 2024 IP Infusion Inc. Proprietary 6

OpenConfig NetConf Payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

BGP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

© 2024 IP Infusion Inc. Proprietary 7

Create BGP Peer-groups with Default VRF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

© 2024 IP Infusion Inc. Proprietary 8

OSPFv2 Openconfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Interface Configuration OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

© 2024 IP Infusion Inc. Proprietary 9

OpenConfig NetConf Payload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

LACP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

© 2024 IP Infusion Inc. Proprietary 10

OcNOS NetConf Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Tunnel Interfaces OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Static Route OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Platform OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

© 2024 IP Infusion Inc. Proprietary 11

Get OpenConfig Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

System OpenConfig Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

© 2024 IP Infusion Inc. Proprietary 12

VLAN OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

© 2024 IP Infusion Inc. Proprietary 13

OcNOS CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

© 2024 IP Infusion Inc. Proprietary 14

© 2024 IP Infusion Inc. Proprietary 15

LLDP OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

© 2024 IP Infusion Inc. Proprietary 16

ACL OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518

© 2024 IP Infusion Inc. Proprietary 17

OcNOS CLI Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

QoS OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

© 2024 IP Infusion Inc. Proprietary 18

OcNOS NetConf Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

© 2024 IP Infusion Inc. Proprietary 19

EVPN Openconfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

OpenZR+ OpenConfig Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

© 2024 IP Infusion Inc. Proprietary 20

Disable configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

© 2024 IP Infusion Inc. Proprietary 21

Get OpenConfig Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

PYANG Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664

© 2024 IP Infusion Inc. Proprietary 22

module: openconfig-if-ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

© 2024 IP Infusion Inc. Proprietary 23

Table 3.1: Conventions

Italics Emphasized terms; titles of books

Note: Special instructions, suggestions, or warnings

© 2024 IP Infusion Inc. Proprietary 24

© 2024 IP Infusion Inc. Proprietary 25