Cisco Technology, Inc.

Masum Z Hasan

Petre Dini

Monique Jeanne Morrow

Cosmin Nicu Dini

Manuela Ionelia Popescu

Michael P Hammer

Andrew George Harvey

L Alexander Clemm

Lewis Wiley Tucker

Leo Pereira

Kui Zhang

Kenneth John Roberts

Elaine Cheong

Kurella Murty

A representation of network resources and relationships among the network resources is established. The network resources include network resources of a tenant and network resources of a plurality of clouds. Input specifying at least one network resource of the tenant, at least one network resource of each of two of the plurality of clouds, and an action directed to the specified network resources is received in the representation. A multi-cloud extension is configured in accordance with the input. The multi-cloud extension extends to network resources of the tenant and the plurality of clouds, and is isolated from network resources of other tenants.

Cloud framework for multi-cloud extension

Establishing an MCEE logical structure relating tenant resources of a tenant site, first non-tenant cloud resources at a first non-tenant cloud site, and second non-tenant cloud resources at a second non-tenant site. Mapping the MCEE logical structure nodes to a segmented end-to-end virtual network structure (E2E-VNS) such that the resources at each node of the MCEE logical structure is in a separate virtual network of the E2E-VNS. Establishing an extension and isolation (EXI) domain in the MCEE logical structure associating at least one node of the tenant resources with at least one node of the first non-tenant cloud and at least one node of the second non-tenant cloud. Connecting for network communications, the E2E-VNS virtual networks of the nodes of the EXI domain for isolation of the resources of the nodes of the EXI domain from the other resources of the MCEE logical structure in an EXI virtual network.

Framework for network technology agnostic multi-cloud elastic extension and isolation

Techniques are described for fulfilling a request for services in a federated peering environment. Embodiments receive an advertisement of offered services from each of a plurality of service providers. Such an advertisement may specify a list of offered services and pricing information for the services. A request for one or more services is received from a client at a first service provider. Embodiments determine a second service provider from the plurality of service providers to peer with to dynamically create a federation of peers for fulfilling the service request, based on the received advertisements of offered services and the requested services. Embodiments then peer with at least the determined second service provider to dynamically create a peered federation and fulfill the service request through the created federation of peers.

Real time service advertisement for billing and revenue settlement in a federated model

A computer apparatus comprises first Border Gateway Protocol (BGP) logic comprising BGP route table data; a network interface to communicatively couple to a first autonomous system; data collection logic in computer-readable storage media when executed operable to perform discovering an address prefix of a data collector that is communicatively coupled to second BGP logic of a router within a second autonomous system that is coupled to the first autonomous system, wherein the second autonomous system is independent of the first autonomous system; determining a path through the first autonomous system, the one or more networks or internetworks, and the second autonomous system to the data collector based on the BGP route table; requesting the data collector to provide one or more data values relating to performance of network elements of the second autonomous system; receiving and storing the one or more data values.

Collecting network performance data from multiple autonomous systems

An approach is provided for characterizing the dynamic availability behavior of network elements using metrics that indicate patterns of availability of a network element over time. The metrics provide an indication of stability and instability of a network element and include one stability metric and three instability metrics. The stability metric is a stability order that indicates how long an operational state holds with respect to a prior operational state. The instability metrics include an instability order, a repeatability order and a multiplicity order. The instability order indicates how quickly a network element changes operational states. The repeatability order indicates short-term instability within a vicinity of a change in operational state. The multiplicity order indicates long-term instability. The metrics may be used alone, or in various combinations, by network management applications to better manage network elements.

Approach for characterizing the dynamic availability behavior of network elements

A uniquely configured data structure is used to store event information for each network entity, where logical and physical dependency relationships among entities are captured in the data structure. For each entity, the data structure is configured to store (a) a 'genuine event set', which includes a list of events that originated in association with the entity; and (b) a 'derived event set', which includes a list of records in which each record is associated with an event that originated in association with an entity that has a dependency relationship (e.g., layering or topological) with the entity. The derived event set may simply comprise references to the genuine event sets for entities that have a dependency relationship with the entity.

Method and apparatus for correlating events in a network

A method of managing performance data and accounting data that are generated in a computer network comprises collecting performance data from the network using one or more collector blades that are installed into a data collection manager at a time when the data collection manager is executed; determining whether the performance data satisfies one or more thresholding rules, and if so, generating and sending one or more performance messages; filtering the performance data using one or more filters; aggregating the performance data; and correlating the performance data with other data received from one or more network management subsystems.

Method and apparatus for collecting network performance data

Systems and methods are provided for generating an Internetworking Operating System (IOS) Command Line Interface (CLI) configuration model and a logical topology from an IOS CLI configuration base. The method includes representing structure and cross-CLI dependencies in a formal specification format, such as Extended Backus-Naur Form (EBNF), and translating the representation into a machine-processable structure and code referred to as the IOS CLI Dependency Tree (ICDT). The ICDT is the configuration model. The ICDT optionally may be manipulated to generate configuration models in other formats, such as Java classes or XSD (eXtensible markup language Schema Definition). The method further includes generating the logical topology from the ICDT.

Auto-generation of configuration and topology models

Approaches are described for capturing illegal and undesired behavior for network components and for interactions between components. One approach comprise specifying one or more states and state transitions for one or more components or interactions between components, wherein at least one composite state transition is specified, and generating a notification corresponding to a specified state or state transition when the state or state transition occurs. These approaches provide a holistic view of the entire state space of a network or component or component interactions, and allow undesired or illegal states to be captured in a timely manner.

Approaches for capturing illegal and undesired behavior in network components and component interactions

A method for correlating output of distributed processes includes receiving certain information at a first process of multiple distributed processes that perform one computer application. The information includes a unique identifier for a particular instance of the application that is different from any other identifier for any other instance of the application. The unique identifier is included in data written by the first process to a first data structure. Based on the unique identifier, the data in the first data structure is correlated with data in a different, second data structure written by a different, second process.

Growing community of inventors

San Jose, CA, United States of America

Masum Z Hasan