US2017346703A1PendingUtilityA1

Monitoring network management activity

Assignee: JUNIPER NETWORKS INCPriority: Dec 27, 2011Filed: Aug 14, 2017Published: Nov 30, 2017
Est. expiryDec 27, 2031(~5.4 yrs left)· nominal 20-yr term from priority
G06F 17/30516H04L 41/22H04L 41/0631G06F 16/24568
43
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A device is configured to receive, from a network device, a first message associated with a network management activity performed by using an application of the network device. The device is further configured to determine whether the first message satisfies a criterion, and to classify the first message based on a type of the application when the first message satisfies the criterion. The device is also configured to receive, from the network device, a second message associated with the network management activity; to correlate the second message with the first message after classifying the first message; and to create a record for the network management activity based on the first message and the second message by using rules associated with the type of the application.

Claims

exact text as granted — not AI-modified
1 - 20 . (canceled) 
     
     
         21 . A method comprising:
 identifying, by a network device, one or more parameters associated with a session,
 the one or more parameters including one or more of:
 first information identifying a type of interface being used by an operator to interact with the network device, or 
 second information identifying a type of process used by the network device for an event; 
 
   generating, by the network device, a message for the event based on the one or more parameters; and   transmitting, by the network device, the message to a logging server,
 the message to be correlated by the logging server with one or more messages associated with the session based on the one or more parameters. 
   
     
     
         22 . The method of  claim 21 ,
 where the event is a log-in event when the network device logs into an application, and   where the message includes a tag that identifies the log-in event.   
     
     
         23 . The method of  claim 21 , further comprising:
 receiving a command;   generating a different message based on receiving the command; and   transmitting the different message to the logging server.   
     
     
         24 . The method of  claim 23 ,
 where the message includes a primary process identifier, and   where the different message includes a secondary process identifier that includes a reference to the primary process identifier.   
     
     
         25 . The method of  claim 23 ,
 where the command is to use an application to configure the network device, and   where the method further comprises:
 performing one or more actions to configure the network device based on the command. 
   
     
     
         26 . The method of  claim 21 , further comprising:
 receiving, from a client device, a request to log-out of an application; and   transmitting, to the logging server, a different message for a log-out event based on receiving the request to log-out.   
     
     
         27 . The method of  claim 21 , further comprising:
 assigning a session identifier that uniquely identifies the session,
 the one or more parameters further including the session identifier; and 
   logging into an application for the operator to use the application to interact with the network device.   
     
     
         28 . A network device comprising:
 one or more processors to:
 identify one or more parameters associated with a session,
 the one or more parameters including information identifying a type of interface being used by an operator to interact with the network device; 
 
 generate a message for an event based on the one or more parameters; and 
 transmit the message to a logging server,
 the message to be correlated by the logging server with one or more messages associated with the session based on the one or more parameters. 
 
   
     
     
         29 . The network device of  claim 28 ,
 where the event is a log-in event when the network device logs into an application, and   where the message includes a tag that identifies the log-in event.   
     
     
         30 . The network device of  claim 28 , where the one or more processors are further to
 receive a command;   generate a different message based on receiving the command; and   transmit the different message to the logging server.   
     
     
         31 . The network device of  claim 30 ,
 where the message includes a primary process identifier, and   where the different message includes a secondary process identifier that includes a reference to the primary process identifier.   
     
     
         32 . The network device of  claim 30 ,
 where the command is to use an application to configure the network device, and   where the one or more processors are further to:
 perform one or more actions to configure the network device based on the command. 
   
     
     
         33 . The network device of  claim 28 , where the one or more processors are further to:
 receive, from a client device, a request to log-out of an application; and   transmit, to the logging server, a different message for a log-out event based on receiving the request to log-out.   
     
     
         34 . The network device of  claim 28 , where the one or more processors are further to:
 assign a session identifier that uniquely identifies the session,
 the one or more parameters further including the session identifier; and 
   log into an application for the operator to use the application to interact with the network device.   
     
     
         35 . A non-transitory computer-readable medium storing instructions, the instructions comprising:
 one or more instructions that, when executed by a network device, cause the network device to:
 identify one or more parameters associated with a session,
 the one or more parameters including information identifying a type of process used by the network device for an event; 
 
 generate a message for the event based on the one or more parameters; and 
 transmit the message to a logging server,
 the message to be correlated by the logging server with one or more messages associated with the session based on the one or more parameters. 
 
   
     
     
         36 . The non-transitory computer-readable medium of  claim 35 , where the instructions further comprise:
 one or more instructions to:
 receive a command to use an application to configure the network device; 
 generate a different message based on receiving the command; and 
 transmit the different message to the logging server. 
   
     
     
         37 . The non-transitory computer-readable medium of  claim 36 , where the instructions further comprise:
 one or more instructions to perform one or more actions to configure the network device based on the command.   
     
     
         38 . The non-transitory computer-readable medium of  claim 35 ,
 where the instructions further comprise:
 one or more instructions to transmit a different message to the logging server, 
   where the message includes a primary process identifier, and   where the different message includes a secondary process identifier that includes a reference to the primary process identifier.   
     
     
         39 . The non-transitory computer-readable medium of  claim 35 , where the instructions further comprise:
 one or more instructions to:
 receive, from a client device, a request to log-out of an application; and 
 transmit, to the logging server, a different message for a log-out event based on receiving the request to log-out. 
   
     
     
         40 . The non-transitory computer-readable medium of  claim 35 , where the instructions further comprise:
 one or more instructions to:
 assign a session identifier that uniquely identifies the session,
 the one or more parameters further including the session identifier; and 
 
 log into an application for an operator to use the application to interact with the network device.

Join the waitlist — get patent alerts

Track US2017346703A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.