Patent application number | Description | Published |
20090034533 | SYSTEM AND METHOD FOR PROVIDING LINK, NODE AND PG POLICY BASED ROUTING IN PNNI BASED ATM NETWORKS - A system and method for providing link, node, and PG policy based routing in PNNI based ATM networks is disclosed. A computer implemented method signals and routes a call in the network. Upon detecting the call's arrival, its service request is accessed. Upon determining that the service request relates to an attribute of a link, a routing path is sought that conforms to the service request, as by accessing information relating to the routing path and comparing the information to the service request. A conforming routing path is selected, and the call is routed via that path. A computer implemented method advertises an attribute of links, nodes, policies, etc. Data relating to the route's attribute can be provided to a node as a GAT IE component of a PNNI signaling setup message for multi-peer group networks, and advertised using PTSEs within a peer group. | 02-05-2009 |
20090135728 | USER DATAGRAM PROTOCOL TRACEROUTE PROBE EXTENSION - The embodiments described herein provide methods and apparatuses for implementing a User Datagram Protocol traceroute probe extension. In an example embodiment, a request to transmit a User Datagram Protocol (UDP) packet to a remote destination is received. A probe header and a probe data element is then stored in a data field of the UDP packet. The UDP packet is then transmitted toward the remote destination. In an example embodiment, a User Datagram Protocol (UDP) packet is received and it is determined whether the UDP packet includes a probe data structure. When the determination is affirmative, the probe data structure is processed. | 05-28-2009 |
20100238812 | Operating MPLS label switched paths and MPLS pseudowire in loopback mode - In one embodiment, an initiating maintenance end point (MEP) may transmit a lock message to lock a circuit traversing one or more maintenance intermediate points (MIPs) between the initiating MEP and an end MEP. The initiating MEP may then transmit an in-band packet containing a loopback request to a particular MIP along the circuit using a particular time-to-live (TTL) value in the packet to reach the particular MIP. Upon receiving the packet at the particular MIP, and in response to determining that the TTL has expired, the particular MIP inspects the packet to discover the loopback request, and correspondingly operates in a loopback mode. | 09-23-2010 |
20110013520 | DYNAMIC PROBE ARCHITECTURE - Systems, methods and other embodiments associated with dynamic probe generation are described. In one embodiment, an apparatus includes generation logic to dynamically generate a probe configured to identify a status associated with an event occurring in a network device, a path between network devices, and/or a location in an encapsulation stack. Additionally, the apparatus comprises reception logic to receive the status. | 01-20-2011 |
20110055637 | ADAPTIVELY COLLECTING NETWORK EVENT FORENSIC DATA - In an embodiment, a data processing system comprises a repository configured to store a plurality of event message definitions for error messages, syslog messages, or other notification messages that may be emitted by one or more managed network elements; event annotation logic coupled to the data repository and configured to receive and store one or more annotations to each of the event message definitions, wherein each of the annotations specifies event context information to be collected in the managed network elements when an associated event message occurs; event forensics definitions generator logic coupled to the event annotation logic and configured to generate an event forensics definitions file capable of interpretation by one or more managed network elements and comprising event type identifiers and context information identifiers for context information to be collected, and configured to cause distributing the event forensics definitions file to the one or more managed network elements. | 03-03-2011 |
20120033663 | Discovery of Services Provided by Application Nodes in a Network - An application node advertises service(s), using a routing protocol, that it offers to other network nodes. For example, the routing protocol used to advertise service(s) in a Service Provider Network is typically an link-state, Interior Gateway Protocol (IGP), such as, but not limited to, Intermediate System to Intermediate System (IS-IS) or Open Shortest Path First (OSPF). Packets are encapsulated and sent from a service node (e.g., packet switching device) using one or more advertised services applied to a packet by an application node (e.g., a packet switching device and/or computing platform such as a Cisco ASR 1000). | 02-09-2012 |
20120033664 | Label Distribution Protocol Advertisement of Services Provided by Application Nodes - An application node advertises service(s), using a label distribution protocol, that it offers to other network nodes and a corresponding label to use to identify these services(s). For example, a Targeted Label Distribution Protocol (tLDP) session may be established between a packet switching device and the application node providing these services to communicate the advertisement. Packets are encapsulated and sent from a service node (e.g., packet switching device) with the corresponding label to have one or more advertised services applied to the packet by an application node (e.g., a packet switching device and/or computing platform such as a Cisco ASR 1000). | 02-09-2012 |
20120063314 | UNIVERSAL LOAD-BALANCING TUNNEL ENCAPSULATION - In one embodiment, packets received at head-end nodes in a computer network may have a payload and protocol ID of an original protocol of the packet. To allow load balancing across the network, the head-end node may convert the protocol ID to indicate a UDP packet, and may insert a UDP shim header into the packet having a load balance ID, at least one port ID of a destination tail-end node of the packet, and an indication of the original protocol ID. The head-end node may transmit the converted UDP packet toward the tail-end node as part of a load-balanced UDP flow based on the load balance ID. Tail-end nodes may receive UDP packets, and determine whether they are converted UDP packets. If so, the original protocol of the packet may be determined, the UDP header may be removed, and the packet may be processed according to the original protocol. | 03-15-2012 |
20120063450 | Data Path Processing Information included in the Pseudowire Layer of Packets - Data path processing information is included in the pseudowire layer of pseudowire packets in order to provide information for use in the data path processing of data (e.g., a packet), typically, but not always, included in the payload of the pseudowire packet itself. The pseudowire packet typically includes in corresponding fields: a pseudowire label for identifying a pseudowire type; a pseudowire control word; and payload data. The pseudowire type identifies the structure of the pseudowire control word field and the payload field, including the location of data path meta data, such as in the pseudowire control word field or payload field. This data path meta data identifies one or more attributes for use in processing the payload data. | 03-15-2012 |
20120203892 | IDENTIFYING OPERATING HYBRID SOLUTIONS - A method and apparatus for identifying operating hybrid solutions is provided. An operating hybrid solution includes a combination of hardware and software components operating together for a particular purpose, such as to provide particular functionality. In various embodiments, mappings are stored to associate operating hybrid solutions with operating criteria that describe devices when the devices are operating according to the operating hybrid solutions. During operation of a device, a monitoring process uses the mappings to determine whether the device is operating as part of an operating hybrid solution. The monitoring process stores an indication of whether the device is operating as part of the operating hybrid solution, and the indication may be provided in response to a request for operating hybrid solution information associated with the device. | 08-09-2012 |
20120327954 | Packet Meta-Tagging Using Excess Payload - Packet meta-tagging using excess payload is described. In an implementation, a total packet length value specified in packet received at a network element is adjusted while preserving a data length value associated with a data portion of the packet to generate additional space in the packet to accommodate packet transmission meta-data. Packet-transmission meta-data can be inserted into the additional space created in the packet by the network element. In some implementations, the meta-data describes packet transmission characteristics of the packet. For example, the meta-data can be a timestamp corresponding to the time at which the packet was received by the network element. The meta-data can be an identifier corresponding to the network element that received the packet. | 12-27-2012 |
20130103739 | Obtaining Dynamic Connected-Network Topology Via any Node in Network - A method, an apparatus and computer readable storage media facilitate obtaining of a current network topology within a network by requesting this topology from any node within the network, where the topology can be provided in any manner that is suitable to the requester. In an example embodiment, a connection is established between a computing device and a network including a plurality of nodes, each node connected with at least one other neighboring node within the network, each node further including a network element configured to receive and transmit data to and from other nodes. A request is sent for current network topology information from the computing device to any selected node within the network, where the selected node has current network topology information. A graphical image of the current network topology is provided at the computing device that is based upon the current network topology information. | 04-25-2013 |
20130114462 | Sub-Topology Discovery for Operating Hybrid Solutions - Network topology information may be determined for a plurality of network devices on a network. System identifier information may then be determined for each of the plurality of network devices on the network. The system identifier information may be a list of network solutions that each network device actually or potentially belongs to. The system may then flag the system identifier information to indicate whether each solution is an actual or a potential solution. | 05-09-2013 |
20130155877 | OPERATING MPLS LABEL SWITCHED PATHS AND MPLS PSEUDOWIRE IN LOOPBACK MODE - In one embodiment, a circuit that extends between a head-end label switching router (LSR) and a tail-end LSR and traverses one or more intermediate LSRs is locked to data plane traffic. The head-end LSR transmits a packet along the circuit that includes a particular time-to-live (TTL) value configured to expire at a particular intermediate LSR at which loopback is to occur. The circuit is used in a loopback mode. The head-end LSR transmits along the circuit a packet that includes a cease loopback request. The circuit ceases to be used in the loopback mode. The circuit is unlocked to permit the circuit to pass data plane traffic. | 06-20-2013 |
20130262461 | Method and System for Centralized Issue Tracking - In one embodiment, a method for facilitating centralized issue tracking. The method includes receiving information on a case from an issue tracking system (case information). The method facilitates executing a tagging method stored in a memory device that reads the case information, determines whether a part of the case information is desired information, and then tags the desired information. Finally, the method facilitates communicating the tagged information to a centralized database, where the centralized database stores the tagged information, and where the tagged information is accessible to the issue tracking system and at least one other issue tracking system. | 10-03-2013 |
20140096197 | INSTANT MESSAGING VIRTUAL PRIVATE NETWORKS - According to one embodiment, an apparatus may receive a virtual private network (VPN) establishment request communicated over an instant messenger protocol. The apparatus may negotiate a communication tunnel in response to receiving the VPN establishment request and receive a datagram through the communication tunnel. | 04-03-2014 |
20140173073 | Proactive M2M Framework Using Device-Level vCard for Inventory, Identity, and Network Management - A network device may connect to a smart-enabled network. Once connected, the network device may receive a network address for a network management server (NMS). Having the network address for the NMS, the network device may generate a vCard comprising the attributes necessary for registering with the NMS. The network device may then communicate the vCard to the NMS. The NMS may then be configured to identify, register, and add the network device to a directory. | 06-19-2014 |
20140198634 | DETECTING FAILURES OF BACKUP LABEL SWITCHED PATHS IN A NETWORK ENVIRONMENT - A method is provided in one example and includes communicating a first request message to a first network element functioning as a point of local repair for a backup label switched path. The first request message includes a first network address having a predetermined value and an indication of a forwarding equivalence class associated with the backup label switched path. The method further includes receiving a first reply message from the first network element. The first reply message includes at least one backup path parameter associated with the backup label switched path. | 07-17-2014 |
20140269699 | SEAMLESS SEGMENT ROUTING - In one embodiment, a packet and a segment ID stack is received at a node. The segment ID stack includes a plurality of segment IDs, one or which is a first area-segment ID that identifies a first area of a subdivided network. One of a plurality of forwarding tables at the node is selected based on the first area-segment ID. Thereafter, the packet is forwarded based on information contained in the selected forwarding table. | 09-18-2014 |
20140289243 | METHOD AND SYSTEM FOR CENTRALIZED ISSUE TRACKING - In one example, a method for facilitating centralized issue tracking. The method includes receiving information on a case from an issue tracking system (case information). The method facilitates executing a tagging method stored in a memory device that reads the case information, determines whether a part of the case information is desired information, and then tags the desired information. Finally, the method facilitates communicating the tagged information to a centralized database, where the centralized database stores the tagged information, and where the tagged information is accessible to the issue tracking system and at least one other issue tracking system. | 09-25-2014 |
20140310358 | Adaptive Publish/Subscribe System - A context-driven publication option is received over a network at an adaptive publish subscribe broker from a publishing network device. The context driven publication options are presented over the network to a subscribing network device. A selection of a context-driven subscription is received over the network at the adaptive publish/subscribe broker from the subscribing network device. A publication configured for network management and operations is received at the adaptive publish/subscribe broker. Publications are filtered at the adaptive publish/subscribe broker for the subscribing network device according to the selection of the context-driven subscription. | 10-16-2014 |
20140362682 | Determining the Operations Performed Along a Service Path/Service Chain - Presented herein are techniques performed in a network comprising a plurality of network nodes each configured to apply one or more service functions to traffic that passes the respective network nodes in a service path. At a network node, an indication is received of a failure or degradation of one or more service functions or applications applied to traffic at the network node. Data descriptive of the failure or degradation is generated. A previous service hop network node at which a service function or application was applied to traffic in the service path is determined. The data descriptive of the failure or degradation is communicated to the previous service hop network node. | 12-11-2014 |
20150029872 | PATH-PING AND ECMP-TRACEROUTE FOR IPV6 OVERLAY VIRTUALIZED NETWORKS - In one embodiment, an ingress network virtualization edge (NVE) in a computer network generates an echo packet, and sets an indication in the echo packet that the echo packet is for overlay path validation. In addition, the ingress NVE sets a message type of the echo packet to a generic echo request, and includes virtualization network (VN) context information within the echo packet. Once setting a destination address of the echo packet as an egress NVE address and including an indication to the egress NVE that the echo packet is an operations, administration, and management (OAM) message, the ingress NVE may then send the echo packet toward the egress NVE (e.g., to validate the VN context information and/or to reveal multipath traces). | 01-29-2015 |
20150030026 | MPLS LSP Connectivity Test When the Initiator Address is Unknown - The present disclosure provides for carrying reachability information in an echo request message and/or an echo reply message, which can be used to reach an initiator when the initiator's address is unknown. An echo request message includes an FEC (forwarding equivalence class) stack that identifies a label switched path (LSP). The echo request message is received by a label switching routing element (LSR) on the LSP, and the echo request is originated by an initiator. In response to a detection that the FEC stack changes at the LSR, a segment reachability (SR) sub-TLV (type-length-value) element can be generated, where the SR sub-TLV includes reachability information that can be used to reach the initiator, and the reachability information includes an incoming label allocated by the LSR to reach the initiator. | 01-29-2015 |