Skip to content

Conversation

@webxia123
Copy link

@webxia123 webxia123 commented Mar 26, 2024

Description

add one flag in the parse to check if enter the vsi line or not

Motivation and Context

input :
Bridge group: NETWORK, bridge-domain: NETWORK_680_1, id: 0, state: up, ShgId: 0, MSTi: 0
Aging: 300 s, MAC limit: 16000, Action: none, Notification: syslog, trap
Filter MAC addresses: 0
ACs: 1 (1 up), VFIs: 1, PWs: 5 (5 up), PBBs: 0 (0 up), VNIs: 0 (0 up)
List of ACs:
Hu0/1/0/1.1, state: up, Static MAC addresses: 0
List of Access PWs:
Neighbor 192.168.201.1 pw-id 1630, state: up, Static MAC addresses: 0
Neighbor 192.168.201.2 pw-id 1630, state: up, Static MAC addresses: 0
List of VFIs:
VFI IBR_NETWORK_680_1 (up)
Neighbor 192.168.201.1 pw-id 1513, state: up, Static MAC addresses: 0
Neighbor 192.168.201.1 pw-id 1514, state: up, Static MAC addresses: 0
Neighbor 192.168.201.1 pw-id 1680, state: up, Static MAC addresses: 0
List of Access VFIs:

error:
genie.metaparser.util.exceptions.SchemaUnsupportedKeyError: bridge_group.NETWORK.bridge_domain.NETWORK_680_1.vfi.neighbor: Unsupported keys: ['192.168.201.2', '192.168.201.1']

Impact (If any)

The all access pw will be included at the section pw

Screenshots:

image

Checklist:

  • I have updated the changelog.
  • I have updated the documentation (If applicable).
  • I have added tests to cover my changes (If applicable).
  • All new and existing tests passed.
  • All new code passed compilation.
@webxia123 webxia123 requested a review from a team as a code owner March 26, 2024 15:01
@webxia123 webxia123 requested review from lsheikal and omehrabi March 26, 2024 15:01
@webxia123 webxia123 changed the title Fix Unsupported keys in show l2vpn bridge-domaine when the bridge in possession of access pw Fix Unsupported keys in show l2vpn bridge-domaine Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant