Dial-out telemetry for network management
Dial-out telemetry for network management includes a tunnel client configured to form a tunnel service for telemetry inside a dialed-out tunnel from the tunnel client to a tunnel server, wherein the tunnel service is between a network element, communicatively coupled to the tunnel client, and a network management system communicatively coupled to the tunnel server, and preserve the tunnel service via keepalives including during a software upgrade associated with any of the network management system and the network element and with the tunnel service itself.
1 . A tunnel client implemented by circuitry configured to:
form a tunnel service for telemetry inside a dialed-out tunnel from the tunnel client to a tunnel server, wherein the tunnel service is between a network element, communicatively coupled to the tunnel client, and a network management system communicatively coupled to the tunnel server, wherein the dialed-out tunnel comprises a remote procedure call (gRPC) tunnel that transports a transparent, bi-directional transmission control protocol (TCP)-over-gRPC channel initiated by the network element toward the tunnel server, and wherein forming the tunnel service includes establishing a long-lived bi-directional Register remote procedure call (RPC) between the tunnel client and the tunnel server that remains open while both the tunnel client and the tunnel server are alive, and
preserve the tunnel service via keepalives including during a software upgrade associated with any of the network management system and the network element and with the tunnel service itself, wherein preserving comprises (i) overriding default gRPC keepalive parameters using tunnel-stack keepalive attributes, and (ii) exchanging tunnel-control messages indicating upgrade-start and upgrade-finished states for an in-service software upgrade (ISSU) of the tunnel client or the tunnel server or for an in-service tunnel software upgrade (ISTSU) of the tunnel service, such that the established dialed-out tunnel and the tunnel service remain connected without teardown during the software upgrade.
2 . The tunnel client of claim 1 , wherein the circuitry is further configured to
signal a beginning and an end of any software update.
3 . The tunnel client of claim 1 , wherein the circuitry is further configured to
detect an upgraded ability of the tunnel server and perform an upgrade of the tunnel service based thereon, wherein detecting comprises receiving, during tunnel registration or during a life of an established tunnel session, bidirectional capability information identifying (i) a set of tunnel ser es supported by the tunnel server and (ii) service-type capabilities for at least one tunnel service, and wherein performing the upgrade comprises dynamically enabling, disabling, or updating operation of the tunnel service in-line with the established tunnel session based on the received capability information without disconnecting the tunnel session.
4 . The tunnel client of claim 1 , wherein the tunnel service is a gRPC Network Management Interface (gNMI) service.
5 . The tunnel client of claim 4 , wherein the circuitry is further configured to
implement a tunnel-based Authentication, Authorization, and Accounting (AAA) framework utilizing gRPC.
6 . The tunnel client of claim 5 , wherein the AAA framework utilizes existing security in the gRPC along with remote Authentication, service Authorization and Accounting provided as tunnel-service(s).
7 . The tunnel client of claim 4 , wherein the circuitry is further configured to
implement Remote Authentication Dial-in User Service (RADIUS) over gRPC.
8 . A tunnel server implemented by circuitry configured to:
form a tunnel service for telemetry inside a dialed-out tunnel from a tunnel client to the tunnel server, wherein the tunnel service is between a network management system, communicatively coupled to the tunnel server, and a network element communicatively coupled to the tunnel client, wherein the dialed out tunnel comprises a gRPC tunnel that transports a transparent, bi-directional TCP-over-gRPC channel initiated by the network element toward the tunnel server, and wherein forming the tunnel service includes establishing a long-lived bi-directional Register RPC between the tunnel client and the tunnel server that remains open while both the tunnel client and the tunnel server are alive, and
preserve the tunnel service via keepalives including during a software upgrade associated with any of the network management system and the network element and with the tunnel service itself, wherein preserving comprises (i) overriding default gRPC keepalive parameters using tunnel-stack keepalive attributes, and (ii) exchanging tunnel-control messages indicating upgrade-start and upgrade-finished states for an ISSU of the tunnel client or the tunnel server or for an ISTSU of the tunnel service, such that the established dialed-out tunnel and the tunnel service remain connected without teardown during the software upgrade.
9 . The tunnel server of claim 8 , wherein the circuitry is further configured to
signal a beginning and an end of any software update.
10 . The tunnel server of claim 8 , wherein the circuitry is further configured to
provide an upgraded ability of the tunnel server to the tunnel client which performs an upgrade of the tunnel service based thereon.
11 . The tunnel server of claim 8 , wherein the tunnel service is a gRPC Network Management Interface (gNMI) service.
12 . The tunnel server of claim 11 , wherein the circuitry is further configured to
implement a tunnel-based Authentication, Authorization, and Accounting (AAA) framework utilizing gRPC.
13 . The tunnel server of claim 12 , wherein the AAA framework utilizes existing security in the gRPC.
14 . The tunnel server of claim 11 , wherein the circuitry is further configured to
implement Remote Authentication Dial-in User Service (RADIUS) over gRPC.
15 . A method comprising steps of:
forming a tunnel service for telemetry inside a dialed-out tunnel from a tunnel client to a tunnel server, wherein the tunnel service is between a network element, communicatively coupled to the tunnel client, and a network management system communicatively coupled to the tunnel server, wherein the dialed-out tunnel comprises a gRPC tunnel that transports a transparent, bi-directional TCP-over-QRPC channel initiated by the network element toward the tunnel server, and wherein forming the tunnel service includes establishing a long-lived bi-directional Register RPC between the tunnel client and the tunnel server that remains open while both the tunnel client and the tunnel server are alive; and
preserving the tunnel service via keepalives including during a software upgrade associated with any of the network management system and the network element and with the tunnel service itself, wherein preserving comprises (D) overriding default gRPC keepalive parameters using tunnel-stack keepalive attributes, and (ii) exchanging tunnel-control messages indicating upgrade-start and upgrade-finished states for an ISSU of the tunnel client or the tunnel server or for an ISTSU of the tunnel service, such that the established dialed-out tunnel and the tunnel service remain connected without teardown during the software upgrade.
16 . The method of claim 15 , wherein the steps further include
signaling a beginning and an end of any software update.
17 . The method of claim 15 , wherein the steps further include
detecting an upgraded ability of the tunnel service at either the tunnel server or the tunnel client and performing an upgrade of the tunnel service based thereon.
18 . The method of claim 15 , wherein the tunnel service is a gRPC Network Management Interface (gNMI) service.
19 . The method of claim 15 , wherein the steps further include
implementing a tunnel-based Authentication, Authorization, and Accounting (AAA) framework utilizing gRPC.
20 . The method of claim 15 , wherein the steps further include
implementing Remote Authentication Dial-in User Service (RADIUS) over gRPC.