Unable to add Juniper Switch to Aria Operations for Networks
search cancel

Unable to add Juniper Switch to Aria Operations for Networks

book

Article ID: 400560

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

When trying to add newer Juniper switch with OS version higher than 20.2, immediately fails with an unknown error to add. 

You may see similar logs in Collector

2025-04-25T18:04:50.733Z ERROR common.utils.CommonUtils collector-process-msg-exec-11 logException:2680 Connection not alive for: JUNIPERSWITCH
java.lang.Exception: null
2025-04-25T18:04:50.733Z ERROR dataprovider.utils.ResultCodeUtils collector-process-msg-exec-11 getDPResultCode:734 Could not determine exact error code for: JUNIPERSWITCH, java.lang.Exception
2025-04-25T18:04:50.733Z INFO dataprovider.southbound.AbstractDPNetconfConnectionEntity_NetconfConnectionWrapper collector-process-msg-exec-11 closeInternalConnectionsExplicitly:168 Closing netconf session explicitly
2025-04-25T18:04:50.733Z INFO dataprovider.southbound.AbstractDPNetconfConnectionEntity_NetconfConnectionWrapper collector-process-msg-exec-11 closeInternalConnectionsExplicitly:178 Closing ssh channel explicitly


You may see similar logs in your Juniper switch 

Apr 25 12:04:50  N1A mgd[58885]: PVIDB: Attribute 'mgd.is_modular_chassis' not present in Db
Apr 25 12:04:50  N1A kernel: match_inp_rtbl_index:, none criteria match for the connection, returning FALSE, local port =514, foreign port = 0
Apr 25 12:04:50  N1A kernel: match_inp_rtbl_index:, none criteria match for the connection, returning FALSE, local port =514, foreign port = 0

Environment

VMware Aria Operations for Networks 6.12
VMware Aria Operations for Networks 6.12.1
VMware Aria Operations for Networks 6.13
VMware Aria Operations for Networks 6.14

Cause

Juniper OS version higher than 20.2, uses higher netconf juniper library that is incompatible with our netconf juniper library for parsing data. 

Resolution

A patch will be delivered later this year with the new library. Alternatively, you can open a Broadcom Support case and we will work with engineering for a workaround.