Information on command result [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    en:dpi:dpi_components:platform:subscriber_management:subsman_res:start [2018/04/12 19:36] – kvazikraven:dpi:dpi_components:platform:subscriber_management:subsman_res:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
    Line 1: Line 1:
    -====== 5 Information on command result ====== 
    -{{indexmenu_n>5}} 
    -**For all parameters except of 'list' and 'profile'** 
      
    - Result processing ... a/b/c/d/e 
    -   The symbolic names are indicated in parenthesis: 
    -     a - total records 
    -     b - records successfully processed 
    -     c - some server's error occurred 
    -     d - the attribute(s) was set already 
    -     e - the attribute was not set (meaningful on removal) 
    -    
    - Example (the first run): 
    -   fdpi_ctrl load --service 1,2,3 --cidr 192.168.0.0/19 
    -   Autodetected fastdpi params : dev='lo', port=29001 
    -   connecting 127.0.0.1:29001 ... 
    -   --------------------------------- 
    -   Result processing CIDR=192.168.0.0/19 : 8192/8192/0/0/0 
    -Example (the second run: the attribute already set): 
    -   fdpi_ctrl load --service 1,2,3 --cidr 192.168.0.0/19 
    -   Autodetected fastdpi params : dev='lo', port=29001 
    -   connecting 127.0.0.1:29001 ... 
    -   --------------------------------- 
    -   Result processing CIDR=192.168.0.0/19 : 8192/0/0/8192/0 
    -    
    -**For 'list' parameter** 
    - 
    - Result processing ... a/b/c 
    -   The symbolic names are indicated in parenthesis: 
    -     a - total records 
    -     b - the attribute was set (in this case it is a service) 
    -     c - the attribute was not set 
    -      
    - Example: 
    -   fdpi_ctrl list --service --cidr 192.168.0.0/19 
    -    A lot of output lines. The last lines are: 
    -   192.168.31.249 1,2,3 (0x7) 
    -   192.168.31.250 1,2,3 (0x7) 
    -   192.168.31.251 1,2,3 (0x7) 
    -   192.168.31.252 1,2,3 (0x7) 
    -   192.168.31.253 1,2,3 (0x7) 
    -   192.168.31.254 1,2,3 (0x7) 
    -   192.168.31.255 1,2,3 (0x7) 
    -   --------------------------------- 
    -   Result processing CIDR=192.168.0.0/19 : 8192/8192/0 
    -    
    -**For 'profile' parameter** 
    - 
    - Profile creation\\ 
    - Result processing ... a/b/c/d 
    -   Symbolic notations are given in parentheses: 
    -     a - in total 
    -     b - succeeded 
    -     c - internal error ( look through fastdpi_alert.log ) 
    -     d - profile already exists ( in this case there is a41 profile with corresponding characteristics for the  service 4) 
    - 
    -Example (the first run): 
    -   fdpi_ctrl load profile --service 4  --profile.name a41 --profile.json '{ "url_list" : "http://mysite.ru/myfile.bin" , "redirect" : "http://mysite.ru/block", "federal" : true }' 
    -    Autodetected fastdpi params : dev='em1', port=29000 
    -    connecting 5.200.43.18:29000 ... 
    -    ================================ 
    -    ------------------ 
    -    1/1/0/0 
    - 
    -Example (the second run): 
    -    fdpi_ctrl load profile --service 4  --profile.name a41 --profile.json '{ "url_list" : "http://mysite.ru/myfile.bin" , "redirect" : "http://mysite.ru/block", "federal" : true }' 
    -    Autodetected fastdpi params : dev='em1', port=29000 
    -    connecting 5.200.43.18:29000 ... 
    -    ================================ 
    -    ------------------ 
    -    1/0/0/1 
    -     
    - Example (if a profile can not be specified for the service): 
    -    fdpi_ctrl load profile --service 3  --profile.name a31 --profile.json '{ "url_list" : "http://mysite.ru/myfile.bin" , "redirect" : "http://mysite.ru/block", "federal" : true }' 
    -    Autodetected fastdpi params : dev='em1', port=29000 
    -    connecting 5.200.43.18:29000 ... 
    -    ================================ 
    -    hvers=0x3, hcmd=16 : bad profile (name or parameters), error code ecode=4 
    -        ierr_code=1 (service can't have profile) 
    -         
    - Profile deletion\\ 
    - Result processing ... a/b/c/d/e 
    -    a - in total 
    -    b - succeeded 
    -    c - profile not found 
    -    d - profile is being used ( i.e. there are subscribers with specified service and corresponding profile ) 
    -    e - internal error ( look through fastdpi_alert.log ) 
    -     
    - Example (profile deletion): 
    -    fdpi_ctrl  del profile --service 4  --profile.name a41 
    -    Autodetected fastdpi params : dev='em1', port=29000 
    -    connecting 5.200.43.18:29000 ... 
    -    ================================ 
    -    ------------------ 
    -    1/1/0/0/0 
    -     
    - Example (profile deletion command repetition ): 
    -    fdpi_ctrl  del profile --service 4  --profile.name a41 
    -    Autodetected fastdpi params : dev='em1', port=29000 
    -    connecting 5.200.43.18:29000 ... 
    -    ================================ 
    -    ------------------ 
    -    1/0/1/0/0