cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
658
Views
0
Helpful
10
Replies
ibrahim.menem
Beginner

Onep session termination

Hi,

Sometimes after deletion or a try to delete a policy, and after program termination the session in the router keep established for some time, the deletion operation doesn't return failure message in "rc" and all I get from onePK Log is "Failed to withdraw end-point. operation failed."
what is the meaning of this error and how can I overcome it?

Thank you,

Ibrahim

10 REPLIES 10
scadora
Cisco Employee

I'm not familiar with the error.  Does it happen reproducibly?  Can you post code snippet that causes it?

Thanks,

Shelly

yes it is reproducible, I create a policymap, attach it to an interface and save the handler to be able to remove it later from another function, this is the psuedo code:

main:

     getHandler(ifacename, &policyHandler);

     removeHandler(ifacename, policyHandler);

the error happens when i call removeHandler.

getHandler:

     get_datapath_table

     onep_element_get_interface_by_name

     onep_policy_pmap_op_list_new

     onep_policy_op_add_network_element

     onep_policy_pmap_op_create

     onep_policy_op_update

     apply_on_interface

removeHandler:   

     onep_policy_pmap_op_list_new

     onep_policy_pmap_op_delete

     onep_policy_op_add_network_element

     onep_policy_op_update

I also tried to to use onep_policy_target_op_deactivate before deleting policy map but I got the same behavior!

Thank you,

Ibrahim

Joe Clarke
Hall of Fame Cisco Employee

This can happen if the IDL used to tear down the DPSS session fails.  On what platform and code rev are you seeing this?

I'm using csr1000v with sdk-c64-1.2.1.194, I also can try it on ASRk1

Joe Clarke
Hall of Fame Cisco Employee

There seems to be some bugs mentioning this error, but nothing matches it exactly.  I'll see if I can get one of the DPSS developers to look at this.

that would be great, thank you

I also confirm the same behavior on the ASR1001

Can you check/turn on the logs on the CSR1kv?

"debug onep server datapath"

"debug onep server policy"

See if any Error level logs come out when you get "Failed to withdraw end-point. operation failed." on the application.

"show logg | inc error"

From the app nav team, please also check at IOS CLI:

You can use the following commands. The first one will tell you if a dpss

context has been created/destroyed. With the 2nd one, you can see the

service node config and with the 3rd one, you can see the health probes

exchanges.

show service-insertion type dpss service-context

show service-insertion type dpss service-node-group

show service-insertion type dpss statis service-node-group

Hi Alan,

this is the error message I get:

[error][tid: 3] [session id: 431] [ONEP][DATAPATH]: Subblock is NULL [onep_datapath_session_exit:283]

it appears when the session is actually terminated (timeouted some time after program temination)

the other datapath commands are rather cryptic for me, would you recommend any documentation about the datapath architecture?

I attach the output down here:

CSR-IBRA#show service-insertion type dpss service-context

Service Context                             : dpss/1

Cluster protocol VPATH version              : 1

Time service context was enabled            : Thu Jul 10 08:11:52 2014

Current FSM state                           : Converging

Time FSM entered current state              : Thu Jul 10 08:11:52 2014

Last FSM state                              : Initializing

Time FSM entered last state                 : Thu Jul 10 08:11:52 2014

Cluster operational state                   : Operational

Stable AppNav controller View:

Stable SN View:

Current AppNav Controller View:

    192.168.4.60

Current SN View:

CSR-IBRA#show service-insertion type dpss service-node-group

Service Node Group name         : dpss_sng_1

    Service Context             : dpss/1

    Member Service Node count   : 1

Service Node (SN)                   : 192.168.4.170

Auto discovered                     : No

SN belongs to SNG                   : dpss_sng_1

Current status of SN                : Dead

Time current status was reached               : Thu Jul 10 09:02:16 2014

Cluster protocol VPATH version                : 0

Cluster protocol incarnation number           : 0

Cluster protocol last sent sequence number    : 1404987556

Cluster protocol last received sequence number: 0

Cluster protocol last received ack number     : 0

CSR-IBRA#show service-insertion type dpss statis service-node-group

Service Node Group: dpss_sng_1

Number of Service Node(s): 1

Member Service Nodes:

     IP Address

192.168.4.170

Aggregate of statistics from all SNs of the SNG:

------------------------------------------------

Time since statistics were last reset/cleared:

Aggregate number of probe requests sent to SN       : 3

Aggregate number of probe responses received from SN: 0

Aggregate number of invalid probe responses received

        Total                                       : 0

        Incompatible version                        : 0

        Authentication failed                       : 0

        Stale response                              : 0

        Malformed response                          : 0

        Unknown response                            : 0

Aggregate number of times liveliness was lost with the SN :   0

Aggregate number of times liveliness was regained with the SN:0

Aggregare number of version probes sent to SN:                3

Aggregate number of version probes received from SN:          0

Aggregate number of healthprobes sent to SN:                  0

         

CSR-IBRA#show service-insertion type dpss statis service-node-group

Service Node Group: dpss_sng_1

Number of Service Node(s): 1

Member Service Nodes:

     IP Address

192.168.4.170

Aggregate of statistics from all SNs of the SNG:

------------------------------------------------

Time since statistics were last reset/cleared:

Aggregate number of probe requests sent to SN       : 17

Aggregate number of probe responses received from SN: 0

Aggregate number of invalid probe responses received

        Total                                       : 0

        Incompatible version                        : 0

        Authentication failed                       : 0

        Stale response                              : 0

        Malformed response                          : 0

        Unknown response                            : 0

Aggregate number of times liveliness was lost with the SN :   0

Aggregate number of times liveliness was regained with the SN:0

Aggregare number of version probes sent to SN:                17

Aggregate number of version probes received from SN:          0

Aggregate number of healthprobes sent to SN:                  0

Aggregate number of healthprobes received from SN:            0

         

         

Aggregate traffic distribution statistics

-----------------------------------------

Packet and byte counts-

----------------------

Redirected Bytes    : 0                  

Redirected Packets  : 0                  

Received Bytes      : 0                  

Received Packets    : 0     

thank youo

ibrahim.menem
Beginner

Could someone confirm that the removal procedure is correct? do I need to call deactivate before deleting the pmap?

any pseudo code for the removal procedure?

Regards

Content for Community-Ad

This widget could not be displayed.