Self-driven and adaptable multi-vBNG management orchestration
摘要
說(shuō)明書(shū)
However, when vBNG 1 457 does not send a heartbeat message in last ‘n’ seconds, NRM 441 outputs a poll vBNG N health message to vBNG 1 457 (406). In response to determining that vBNG 1 457 is not present and/or that there is insufficient health at vBNG 1 457, NRM 441 outputs, to NICM 445, a request to create vBNG N+1 461N (408). Said differently, when health data for vBNG 1 457 is not received within a threshold time, NRM 441 may output, to NICM 445, a request to generate vBNG N+1 461N for recovering BNG subscriber sessions of vBNG 1 457. NICM 445 creates vBNG N+1 461N (410). NRM 441 outputs, to NSDB 443, an instruction to recover vBNG 1 session previously performed by vBNG 1 457 to vBNG N+1 461N (412). Said differently, NRM 441 may modify an entry of NSDB 443 corresponding to vBNG N+1 461N to recover BNG subscriber sessions of vBNG 1 457. NSDB 443 recovers all sessions previously performed by vBNG 1 457 to vBNG N+1 461N (414). For example, a BNG virtual machine manager (e.g., BNG VM manager 59, BNG VM manager 65, etc.) may be configured to generate vBNG N+1 461N to recreate subscribers replayed (e.g., exact, modified, etc.) subscriber information by NSDB 443 that previously corresponded to vBNG 1 457.
