Abstract: Techniques are disclosed for a user interface for displaying a topology representation of infrastructure of a 5G Radio Access Network (RAN), such as an Open Radio Access Network (O-RAN) 5G infrastructure. For example, a computing system displays, via a user interface, first icons, each icon of the first icons representing first components providing Level-1 functionality for the O-RAN 5G infrastructure, such as non-real-time RAN Intelligent Controllers (RICs). The computing system receives, via the user interface, a selection of a first icon of the first icons. In response to the selection, the computing system displays, via the user interface, second icons, each icon of the second icons representing second components managed by a component of the first components corresponding to the selected first icon. The second components provide Level-2 functionality for the O-RAN 5G infrastructure, such as near-real-time RICs.

Abstract: An example method includes receiving, from a network device, data indicating characterizations of network traffic on a plurality of ports of the network device; determining, by processing circuitry, for each port of the plurality of ports, an indicator of a port type for the port based on the data indicating the characterizations of network traffic on the plurality of ports, wherein the port type indicates a link type of network traffic exchanged by the port; and outputting, by the processing circuitry, the indicator of the port type to an output device.

Abstract: A device may determine that a first link of the device is active. The device may determine whether a Media Access Control Security (MACsec) session is established on the first link. The device may selectively enable or disable a second link of the device based on determining whether the MACsec session is established on the first link.

Abstract: Echo or traceroute functionality is supported in a path spanning multiple autonomous systems (ASes) having segment routing (SR) enabled, the path including an ingress node and an egress node, by: (a) obtaining a return label stack to reach the ingress node from either (A) the egress node, or (B) a transit node in the path; (b) obtaining a label stack to reach, from the ingress node, either (A) the egress node, or (B) the transit node; (c) generating a request message including the return label stack; and (d) sending the request message towards either (A) the egress node, or (B) the transit node using the label stack.

Abstract: A device may receive, from a virtual machine deployed on the device, a request to register for an event associated with a hardware component of the device, and may create a path to a script associated with providing information about the event when the event occurs. The device may provide the script to an event plugin associated with the event and the hardware component, and may register the event plugin with a kernel associated with the device. The device may receive, the kernel, information indicating occurrence of the event associated with the hardware component, and may cause, via the event plugin, execution of the script based on the occurrence of the event associated with the hardware component. The device may provide, based on execution of the script, a notification to the virtual machine, where the notification may indicate the occurrence of the event associated with the hardware component.

Abstract: An example application programming interface (API) server device that distributes configuration data to managed network devices includes one or more processing units implemented in circuitry and configured to receive configuration data to be deployed to at least one of the managed network devices; store the configuration data to a configuration database; and send the configuration data to the at least one of the managed network devices. In this manner, the configuration data can be archived for later retrieval and analysis, e.g., to perform root cause analysis in the event of an error.

Abstract: In some cases, once Fast Reroute (FRR) has taken place (e.g., for MPLS protection), a further FRR is undesirable, and even detrimental. A mechanism to prevent a further FRR, once such a further FRR is determined to be potentially harmful, is described.

Abstract: This disclosure describes techniques for improving speed of network convergence after node failure. In one example, a method includes storing, by SDN controller, an underlay routing table having routes for an underlay network of a data center and an overlay routing table having a set of routes for a virtual network of an overlay network for the data center, wherein the underlay network includes physical network switches, gateway routers, and a set of virtual routers executing on respective compute nodes of the data center; installing, within the underlay routing table, a route to a destination address assigned to a particular one of the virtual routers as an indicator of a reachability status to the particular virtual router in the underlay network. The SDN controller controls, based on presence or absence of the route within the underlay routing table, advertisement of the routes for the virtual network of the overlay network.

Abstract: A controller device manages a plurality of network devices. The controller device includes one or more processing units configured to receive an upgrade request; obtain a redundancy model indicating network device redundancies or service redundancies; determine, based on the upgrade request and the redundancy model, an update graph having nodes each representing one of the network devices or one of the services, the update graph also having at least one edge that connects two of the nodes and that indicates the network redundancy or the service redundancy; determine, based on the update graph including the at least one edge, an update schedule for performing an update of software for the network devices that ensures availability for the first network device or second network device or availability for the service; and update the software of each of the network devices according to the update schedule.

Abstract: Embodiments of the invention describe flexible (i.e., elastic) data center architectures capable of meeting exascale, while maintaining low latency and using reasonable sizes of electronic packet switches, through the use of optical circuit switches such as optical time, wavelength, waveband and space circuit switching technologies. This flexible architecture enables the reconfigurability of the interconnectivity of servers and storage devices within a data center to respond to the number, size, type and duration of the various applications being requested at any given point in time.

Abstract: A device may receive network data associated with a network, and may calculate, based on the network data, key performance indicators (KPIs) for the network. The device may generate a first user interface that depicts one or more of the KPIs, and may receive a selection of a particular KPI from the one or more KPIs displayed by the first user interface. The device may parse a set of rules, utilized to calculate the particular KPI, to generate a parsed set of rules, and may analyze the parsed set of rules to identify particular metrics utilized to calculate the particular KPI. The device may generate a second user interface that depicts one or more timeline views of the particular metrics correlated with the particular KPI, and may provide the second user interface for display.

Abstract: In an example, a method comprises obtaining, by a policy controller from a first SDN architecture system, flow metadata for packet flows exchanged among workloads of a distributed application deployed to the first SDN architecture system; identifying, using flow metadata for a packet flow of the packet flows, a source endpoint workload and a destination endpoint workload of the packet flow; generating a network policy rule to allow packet flows from the source endpoint workload to the destination endpoint workload of the packet flow; and adding the network policy rule to a configuration repository as configuration data for a second SDN architecture system to cause a deployment system to configure the second SDN architecture system with the network policy rule to allow packet flows from the source endpoint workload to the destination endpoint workload when the distributed application is deployed to the second SDN architecture system.

Abstract: A device may receive an input associated with deploying a virtual firewall on a computing device. The device may determine a first set of characteristics associated with the virtual firewall and a second set of characteristics associated with a hypervisor associated with the computing device. The device may automatically tune the virtual firewall based on the first set of characteristics and the second set of characteristics. The device may deploy the virtual firewall after tuning the virtual firewall.

Abstract: A network device may receive a request for a service from an endpoint device located in a first region, and may determine whether destination addresses are identified for the service and the first region. The network device may determine whether the service and the first region are identified in a lookup table, and may receive performance metrics associated with multiple paths in the first region to the destination addresses, based on the service and the first region not being identified in the lookup table. The network device may generate a performance metrics matrix based on the performance metrics, and may identify a best destination and a best path for the service in the first region based on the performance metrics matrix, and may cause, for the endpoint device, a connection to the service to be established via the best destination and the best path for the first region.

Abstract: A network node may receive an indication of a range of network address prefixes and a corresponding range of sequential identifiers. The network node may generate a policy for mapping respective network address prefixes, having ordered positions within the range of network address prefixes, to respective identifiers having corresponding ordered positions within the corresponding range of sequential identifiers. The network node may discover a device associated with a network address having a network address prefix at an ordered position within the range of network address prefixes. The network node may map, based on the policy, the network address prefix to an identifier having an ordered position within the corresponding range of sequential identifiers, wherein the ordered position within the corresponding range of sequential identifiers corresponds to the ordered position within the range of network address prefixes. The network node may advertise the mapping to one or more neighbor nodes.

Abstract: An example computing device is configured to receive an instance of a customer service model representative of a plurality of customer services. Each of the plurality of customer services associated with a corresponding at least one requirement and a corresponding at least one constraint. The computing device is configured to receive an instance of a resource model representative of a plurality of resources and map the instance of the customer service model and the instance of the resource model to an internal placement model. The computing device is configured to allocate the plurality of resources to the plurality of customer services such that the at least one requirement and the at least one constraint for each of the plurality of customer services are satisfied and inverse map data indicating how the plurality of resources are allocated to a format consumable by the customer device and output the inverse mapped data.

Abstract: An autonomous system border router (ASBR) provided in a domain in which routers share an anycast address, may perform a method comprising: (a) receiving, from an exterior Border Gateway Protocol (eBGP) peer, first reachability information for a first prefix, the first reachability information including a first next hop (NH) address; (b) communicating first link state information about the first prefix to another router in the domain, the first link state information associating the first prefix with the anycast address; (c) receiving, from an eBGP peer, second reachability information for a second prefix, the second reachability information including a second next hop (NH) address; and (d) communicating second link state information about the second prefix to the other router in the domain, the second link state information associating the second prefix with the anycast address. This effectively reduces the number of next hops related to a prefix learned by two or more ASBRs (e.g.

Abstract: A network device can automatically select an execution plan from a set of possible execution plans that cause a first set of traffic assignments in a network to be changed to a second set of traffic assignments. A traffic assignment indicates assignments of the traffic to one or more tunnels, internal routes and/or peer links to be utilized for routing traffic received at provider edge routers through a network to prefixes. A traffic assignment can have various parameters such as bandwidth, transmission costs etc. Each execution plan has one or more steps, and each step has one or more traffic assignment changes progressing from the first set of traffic assignments to the second set of traffic assignments. The network device can automatically select an execution plan based on an evaluation metric determined for each execution plan. The evaluation metric can be a cost based metric or a quality based metric.

Abstract: Techniques are described that detect areas with insufficient radio frequency (RF) coverage in a wireless network. A network management system (NMS) determines one or more service level expectation (SLE) metrics for each client device in a wireless network. The SLE metrics are aggregated to each access point (AP) in the wireless network, and each AP is assigned an AP score based on the aggregated SLE metrics. To identify potential coverage holes, the NMS groups APs having poor AP scores. If a root cause of the poor AP scores cannot be automatically resolved and if the poor AP scores persist for a predetermined period of time, the group of APs is determined to represent a true coverage hole. The NMS may generate a notification regarding recommended corrective actions to the customer and/or IT personnel.

Abstract: Techniques are disclosed for disseminating network service-specific mapping information across administrative domains. In one example, a network device receives an indication of a route target and one or more underlay tunnels configured to support a service route. The service route is configured to transport network traffic associated with a first network service of a plurality of network services. The network device defines, based on the indication, a first transport class of a plurality of transport classes. The network device receives a service route for the first network service and stores a correspondence between the service route and the first transport class. The network device receives network traffic associated with the first network service and forwards, based on the correspondence, the network traffic along the underlay tunnels specified by the first transport class.