NRM 41 may actively monitor resources across vBNG instances 57 and 58. NRM 41 may monitor both BNG aspects and system resource aspects of each vBNG instance of vBNG instances 57 and 58. NRM 41 may monitor BNG aspects such as a number of subscribers and services for the subscribers, IPv4/IPv6 address pools, a usage of IPv4/IPv6 address pools, quality of service, queues and schedulers, cache (e.g., L1) resources, business services, and/or calls per second (CPS) at each vBNG instance of vBNG instances 57 and 58. NRM 41 may monitor system resource aspects such as CPU availability, memory, bandwidth, control packet response times, inflight login/logouts (e.g., event rate analyzer), critical management queues, and other system resource aspects. Thus, NRM 41 may be “aware” of not only subscriber related resources but also system resources. NRM 41 may also monitor health of each of vBNG instance of vBNG instances 57 and 58.

NSDB 43 may store a subscriber database for accessing service provider network 20. With the access to each of vBNG of vBNG instances 57 and 58, the entire network subscriber database may be maintained at a centralized place. Subscriber databases of individual vBNG instances may be available at individual vBNG instances. NSDB 43 may have a transaction update mechanism from the individual vBNG subscriber database. NSDB 43 may be in lock-sync with the subscriber database of individual vBNG. For example, NSDB 43 and each vBNG of vBNG instances 57 and 58 may be configured to synchronize a local database (e.g., memory of one of edge routers 30-32) of each respective vBNG with NSDB 43. Service providers may have a subscriber database for the entire network (e.g., service provider network 20) at one single place.