Skip to content

Add support for connection point status #1532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arun-arista wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add support for connection point status #1532

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 64 additions & 1 deletion release/models/network-instance/openconfig-network-instance-types.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,13 @@ module openconfig-network-instance-types {
description
"Types associated with a network instance";

oc-ext:openconfig-version "0.9.3";
oc-ext:openconfig-version "0.10.0";

revision "2026-08-04" {
description
"Add connection point operational status.";
reference "0.10.0";
}

revision "2021-07-14" {
description
Expand Down Expand Up @@ -196,6 +202,63 @@ module openconfig-network-instance-types {
endpoint";
}

identity CONNECTION_POINT_OPER_STATUS {
description
"Base identity for the operational status of a connection point.";
}

identity ADMIN_DOWN {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point is administratively down.";
}

identity CONFIG_CONFLICT {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point is down due to a configuration conflict.
Examples are: - Multiple endpoints configured with the same local
MPLS label. - A static endpoint configured with both a tunnel interface
and a nexthop-group transport.";
}

identity DOWN {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point is operationally down due to a forwarding plane
or transport failure. This is distinct from ADMIN_DOWN, UNPROGRAMMED
and CONFIG_CONFLICT. Typical causes include a failed transport tunnel,
loss of the remote signaling session, or the local interface being down.";
}

identity UNPROGRAMMED {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point configuration has been resolved and validated,
but the hardware programming has not completed or has failed.";
}

identity UP {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point is fully operational.";
}

identity PARTIALLY_UP {
base CONNECTION_POINT_OPER_STATUS;
description
"At least one endpoint is up and programmed while at least one other
endpoint is not fully up or programmed.";
}

identity STANDBY {
base CONNECTION_POINT_OPER_STATUS;
description
"The connection point is configured as a backup and is not actively forwarding
traffic. It will transition to UP upon failure of the primary
connection point.";
}
Comment on lines +210 to +260

@gemini-code-assist gemini-code-assist Bot Aug 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Defining generic identity names like UP, DOWN, ADMIN_DOWN, and STANDBY directly in openconfig-network-instance-types.yang can lead to namespace conflicts in the future. Since YANG identity names must be unique within a module, defining these generic names for connection points prevents any other operational status (e.g., for endpoints, pseudowires, or other network instance components) from using the same names in this types module.

To ensure future extensibility and avoid namespace pollution, it is highly recommended to prefix these identities with CONNECTION_POINT_ (or CP_).

  identity CONNECTION_POINT_ADMIN_DOWN {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point is administratively down.";
  }

  identity CONNECTION_POINT_CONFIG_CONFLICT {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point is down due to a configuration conflict.
      Examples are: - Multiple endpoints configured with the same local
      MPLS label. - A static endpoint configured with both a tunnel interface
      and a nexthop-group transport.";
  }

  identity CONNECTION_POINT_DOWN {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point is operationally down due to a forwarding plane
      or transport failure. This is distinct from ADMIN_DOWN, UNPROGRAMMED
      and CONFIG_CONFLICT. Typical causes include a failed transport tunnel,
      loss of the remote signaling session, or the local interface being down.";
  }

  identity CONNECTION_POINT_UNPROGRAMMED {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point configuration has been resolved and validated,
      but the hardware programming has not completed or has failed.";
  }

  identity CONNECTION_POINT_UP {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point is fully operational.";
  }

  identity CONNECTION_POINT_PARTIALLY_UP {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "At least one endpoint is up and programmed while at least one other
      endpoint is not fully up or programmed.";
  }

  identity CONNECTION_POINT_STANDBY {
    base CONNECTION_POINT_OPER_STATUS;
    description
      "The connection point is configured as a backup and is not actively forwarding
      traffic. It will transition to UP upon failure of the primary
      connection point.";
  }


identity LABEL_ALLOCATION_MODE {
description
"Base identity to be used to express types of label allocation
Expand Down
16 changes: 15 additions & 1 deletion release/models/network-instance/openconfig-network-instance.yang
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,13 @@ module openconfig-network-instance {
virtual switch instance (VSI). Mixed Layer 2 and Layer 3
instances are also supported.";

oc-ext:openconfig-version "4.7.0";
oc-ext:openconfig-version "4.8.0";

revision "2026-08-04" {
description
"Add connection point operational status.";
reference "4.8.0";
}

revision "2026-03-17" {
description
Expand Down Expand Up @@ -1146,6 +1152,14 @@ module openconfig-network-instance {
description
"Operational state data relating to a forwarding-instance
connection point";

leaf oper-status {
type identityref {
base oc-ni-types:CONNECTION_POINT_OPER_STATUS;
}
description
"Operational status of the connection point.";
}
}

grouping table-config {
Expand Down
Loading