Helpful ReplyHot!v6.0 is here

Page: 1234 > Showing page 1 of 4
Author
emnoc
Expert Member
  • Total Posts : 4989
  • Scores: 306
  • Reward points: 0
  • Joined: 2008/03/20 13:30:33
  • Location: AUSTIN TX AREA
  • Status: online
2018/03/29 17:08:32 (permalink) 6.0
0

v6.0 is here

I hope it 's  all good  ;)

PCNSE,  NSE , Forcepoint ,  StrongSwan Specialist
#1
RobertReynolds
Bronze Member
  • Total Posts : 55
  • Scores: 2
  • Reward points: 0
  • Joined: 2016/06/29 21:27:23
  • Location: Sydney, Australia
  • Status: offline
Re: v6.0 is here 2018/03/30 01:53:46 (permalink)
0
https://docs.fortinet.com/uploaded/files/4328/fortios-v6.0.0-release-notes.pdf
 
Beta and interims have been good.
 
Nice Easter surprise.
#2
Kenundrum
Gold Member
  • Total Posts : 131
  • Scores: 15
  • Reward points: 0
  • Joined: 2008/05/15 10:25:50
  • Location: Rhode Island, US
  • Status: offline
Re: v6.0 is here 2018/03/30 06:06:33 (permalink)
0
I'm reading through some of the documentation. I was interested in the fabric changes.
So far- you still cannot have VDOMs enabled and participate in a security fabric which is still ridiculous. Also- the guide appears to be inconsistent for setting up a fabric as far as what is required. The diagrams show that a fortianalyzer is required, but all the text makes it seem like it is optional by referring to it as a recommended item. As I understand it, in 5.4 you only needed fortigates, in 5.6 you need an analyzer to use fabric features. Is that requirement now dropped again? Unfortunately almost all my devices have multiple VDOMs (mixing transparent and NAT modes) so I haven't been able to verify myself.

NSE4
Some FGT500Es, 500Ds, 60Ds at work
FWF60E, FWF80CM at home
#3
rkhair
New Member
  • Total Posts : 20
  • Scores: 0
  • Reward points: 0
  • Joined: 2004/12/02 07:18:50
  • Status: offline
Re: v6.0 is here 2018/03/31 22:29:16 (permalink)
0
did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!
 
Just a warning
#4
neonbit
Expert Member
  • Total Posts : 475
  • Scores: 51
  • Reward points: 0
  • Joined: 2013/07/02 21:39:52
  • Location: Dark side of the moon
  • Status: offline
Re: v6.0 is here 2018/04/01 04:41:38 (permalink)
0
Upgraded 201E from 5.6.3 to 6.0 and working great for me so far. Tested local logging, SSLVPNs with RDP bookmarks and tunnel mode, VLANs,  dialupVPNs, DHCP sever and DNS server and all working fine so far.
 
Registered the FortiClient Linux (beta) to the FGT and it now shows up on the FGT (including my avatar).
 
I like how when you open the policy section it now defaults to the collapse all view instead of the expand all one like it was before.
 
One thing that I noted in the release notes is if you're upgrading from 5.6.3 > 6.0.0 you can't have any VLANs tied to an interface, and then have a zone referencing the interface and the zone. Hope it doesn't burn anyone that didn't read the notes!
 
All up very happy with this build so far, especially for a X.0 GA build.
#5
khj
New Member
  • Total Posts : 6
  • Scores: 0
  • Reward points: 0
  • Joined: 2016/11/17 01:17:09
  • Status: offline
Re: v6.0 is here 2018/04/01 05:32:37 (permalink)
0
Totally agree.
I was excited about the new feature that attempts to make the swithcontroller work with mulitble VDOMs. I have not tried it yet, as the documentation says that some of the bare essentials like STP (and related), QoS, 802.1X etc. are not supported with this feature enabled.
It would be really helpful to know what is on the roadmap for VDOMs in the near future that actually works.
 
 
#6
ede_pfau
Expert Member
  • Total Posts : 5684
  • Scores: 385
  • Reward points: 0
  • Joined: 2004/03/09 01:20:18
  • Location: Heidelberg, Germany
  • Status: offline
Re: v6.0 is here 2018/04/01 06:05:20 (permalink)
0
@neonbit: FOS v5.4.8 fixes the 'policies all-expanded' GUI bug already.

Ede

" Kernel panic: Aiee, killing interrupt handler!"
#7
simonorch
Gold Member
  • Total Posts : 311
  • Scores: 12
  • Reward points: 0
  • Joined: 2009/06/05 00:05:08
  • Location: Norway
  • Status: offline
Re: v6.0 is here 2018/04/01 12:42:15 (permalink)
0
rkhair
did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!
 
Just a warning




Just a thought, that sounds like a certificate issue (if you have redirect to https enabled as well)
Check the 'admin-server-cert' setting under conf sys global.
 
Simon
 

FCNSP V.4, V.5, NSE5
Fortinet platinum partner - Norway
#8
rkhair
New Member
  • Total Posts : 20
  • Scores: 0
  • Reward points: 0
  • Joined: 2004/12/02 07:18:50
  • Status: offline
Re: v6.0 is here 2018/04/01 14:01:50 (permalink)
0
Simon, you are a legend. Thx for pointing me in right direction.

Not sure why it broke but I did this..

1) Changed admin SSL port back to 443
2) the 'admin-server-cert' was showing '' so I assigned the factory one to it.. using... set admin-server-cert "Fortinet_Factory"

Not sure why it lost it on upgrade. Hopefully helps someone else who loses web admin access after v6.0 upgrade.

simonorch
rkhair
did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!
 
Just a warning




Just a thought, that sounds like a certificate issue (if you have redirect to https enabled as well)
Check the 'admin-server-cert' setting under conf sys global.
 
Simon
 
#9
emnoc
Expert Member
  • Total Posts : 4989
  • Scores: 306
  • Reward points: 0
  • Joined: 2008/03/20 13:30:33
  • Location: AUSTIN TX AREA
  • Status: online
Re: v6.0 is here 2018/04/01 19:57:34 (permalink)
0
Will  I bit the bullet , my new  FWF50E  has a fresh  v6.0 installed ;) The upgrade from v5.6.3 went off with zero issues. It did take a few longer minutes for the WebGUI to be present. I will upgrade a FWF60D next and see what a D model does.
 
FWF50E3U17002431 # get system status  |  grep ersion
Version: FortiWiFi-50E v6.0.0,build0076,180329 (GA)
BIOS version: 05000013
Release Version Information: GA
 
Ken
 

PCNSE,  NSE , Forcepoint ,  StrongSwan Specialist
#10
ghorchem
New Member
  • Total Posts : 15
  • Scores: 0
  • Reward points: 0
  • Joined: 2012/07/07 09:09:21
  • Status: offline
Re: v6.0 is here 2018/04/02 20:20:24 (permalink)
0
When I did the upgrade from 5.6.2 SSL VPN host check failed using the latest web browsers on Windows 7 SP1, Windows 10 ver. 1709 and macos. the log file is below:
 
Fortinetgateway # [191:root:2b]allocSSLConn:280 sconn 0x561cb400 (0:root)
[190:root:2c]allocSSLConn:280 sconn 0x560e9400 (0:root)
[191:root:2b][192:root:2b]SSL state:before SSL initialization (172.168.1.3)
allocSSLConn:280 sconn 0x561cb400 (0:root)
[191:root:2b]SSL state:before SSL initialization (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS read client hello (172.168.1.3)
[192:root:2b][191:root:2b]SSL state:before SSL initialization (172.168.1.3)
[192:root:2b]SSL state:before SSL initialization (172.168.1.3)
SSL state:SSLv3/TLS write server hello (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS read client hello (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write server hello (172.168.1.3)
[190:root:2c]SSL state:before SSL initialization (172.168.1.3)
[190:root:2c]SSL state:before SSL initialization (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS read client hello (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write server hello (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write certificate (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write certificate (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write certificate (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write key exchange (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write server done (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write server done:system lib(172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write key exchange (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write server done (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write server done:system lib(172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write key exchange (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write server done (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write server done:system lib(172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write server done (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write server done (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write server done (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS read client key exchange (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS read change cipher spec (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS read finished (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS read client key exchange (172.168.1.3)
[192:root:2b]SSL state:SSLv3/TLS write session ticket (172.168.1.3)
[192:root:2b][191:root:2b]SSL state:SSLv3/TLS write change cipher spec (172.168.1.3)
SSL state:SSLv3/TLS read change cipher spec (172.168.1.3)
[191:root:2b][192:root:2b]SSL state:SSLv3/TLS read finished (172.168.1.3)
SSL state:SSLv3/TLS write finished (172.168.1.3)
[190:root:2c]SSL state:SSL negotiation finished successfully (172.168.1.3)
SSL state:SSLv3/TLS read client key exchange (172.168.1.3)
[192:root:2b]SSL established: TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
[191:root:2b]SSL state:SSLv3/TLS write session ticket (172.168.1.3)
[190:root:2c][192:root:2b][191:root:2b]SSL state:SSLv3/TLS read change cipher spec (172.168.1.3)
SSL state:SSLv3/TLS write change cipher spec (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS read finished (172.168.1.3)
[191:root:2b]SSL state:SSLv3/TLS write finished (172.168.1.3)
[190:root:2c]SSL state:SSLv3/TLS write session ticket (172.168.1.3)
[190:root:2c]SSL state:SSL negotiation finished successfully (172.168.1.3)
SSL state:SSLv3/TLS write change cipher spec (172.168.1.3)
[191:root:2b]SSL established: TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
[190:root:2c]SSL state:SSLv3/TLS write finished (172.168.1.3)
[190:root:2c]SSL state:SSL negotiation finished successfully (172.168.1.3)
[190:root:2c]SSL established: TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
[192:root:2b]req: /remote/login?lang=en
[192:root:2b]rmt_web_auth_info_parser_common:439 no session id in auth info
[192:root:2b]rmt_web_get_access_cache:760 invalid cache, ret=4103
[192:root:2b]req: /css/main-blue.css
[192:root:2b]mza: 0x134c7d8 /css/main-blue.css
[191:root:2b]req: /sslvpn/js/login.js?q=717f435f6e4f169b34
req: /remote/fgt_lang?lang=en
[191:root:2b]mza: 0x134c7b0 /sslvpn/js/login.js
[192:root:2b]req: /fonts/lato-regular.woff
[192:root:2b]def: 0x134c748 /fonts/lato-regular.woff
[191:root:2b]req: /fonts/lato-bold.woff
[191:root:2b]def: 0x134c748 /fonts/lato-bold.woff
[192:root:2b]req: /fonts/ftnt-icons.woff
[192:root:2b]def: 0x134c748 /fonts/ftnt-icons.woff
[191:root:2c]allocSSLConn:280 sconn 0x561cbd00 (0:root)
[191:root:2c]SSL state:before SSL initialization (172.168.1.3)
[191:root:2c]SSL state:before SSL initialization (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS read client hello (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS write server hello (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS write change cipher spec (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS write finished (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS write finished:system lib(172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS write finished (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS read change cipher spec (172.168.1.3)
[191:root:2c]SSL state:SSLv3/TLS read finished (172.168.1.3)
[191:root:2c]SSL state:SSL negotiation finished successfully (172.168.1.3)
[191:root:2c]SSL established: TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
[190:root:2c]req: /remote/logincheck
[190:root:2c]rmt_web_auth_info_parser_common:439 no session id in auth info
[190:root:2c]rmt_web_access_check:686 access failed, uri=[/remote/logincheck],ret=4103,
[190:root:2c]rmt_logincheck_cb_handler:900 user 'horchemg' has a matched local entry.
[190:root:2c]sslvpn_auth_check_usrgroup:1770 forming user/group list from policy.
[190:root:2c]sslvpn_auth_check_usrgroup:1812 got user (0) group (2:0).
[190:root:2c]sslvpn_validate_user_group_list:1440 validating with SSL VPN authentication rules (1), realm ().
[190:root:2c]sslvpn_validate_user_group_list:1488 checking rule 1 cipher.
[190:root:2c]sslvpn_validate_user_group_list:1496 checking rule 1 realm.
[190:root:2c]sslvpn_validate_user_group_list:1507 checking rule 1 source intf.
[190:root:2c]sslvpn_validate_user_group_list:1546 checking rule 1 vd source intf.
[190:root:2c]sslvpn_validate_user_group_list:1618 rule 1 done, got user (0) group (1:0).
[190:root:2c]sslvpn_validate_user_group_list:1706 got user (0), group (2:0).
[190:root:2c]two factor check for horchemg: off
[190:root:2c]sslvpn_authenticate_user:167 authenticate user: [horchemg]
[190:root:2c]sslvpn_authenticate_user:174 create fam state
[190:root:2c]fam_auth_send_req:577 with server blacklist:
[190:root:2c]fam_auth_send_req_internal:449 fnbam_auth return: 4
[190:root:2c]Auth successful for group Users_W_and_I
[190:root:2c]fam_do_cb:479 fnbamd return auth success.
[190:root:2c]SSL VPN login matched rule (0).
[190:root:2c]rmt_web_session_create:764 create web session, idx[0]
[192:root:2b]Timeout for connection 0x561cb400.
[192:root:2b]Destroy sconn 0x561cb400, connSize=0. (root)
[191:root:2b]Timeout for connection 0x561cb400.
[191:root:2b]Destroy sconn 0x561cb400, connSize=1. (root)
[191:root:2c]Timeout for connection 0x561cbd00.
[191:root:2c]Destroy sconn 0x561cbd00, connSize=0. (root)
[190:root:2c]req: /remote/hostcheck_install?auth_type=16&u
[190:root:2c]rmt_hcinstall_cb_handler:450 remote check failed
[190:root:0]sslvpn_internal_remove_one_web_session:2681 web session (root:horchemg:Users_W_and_I:172.168.1.3:0 0) removed for Server terminated session normally
[190:root:2c]req: /sslvpn/css/ssl_style.css
[190:root:2c]mza: 0x134c7e0 /sslvpn/css/ssl_style.css
[192:root:2c]allocSSLConn:280 sconn 0x561cb400 (0:root)
[192:root:2c]SSL state:before SSL initialization (172.168.1.3)
[192:root:2c]SSL state:before SSL initialization (172.168.1.3)
[192:root:2c][190:root:2c]SSL state:SSLv3/TLS read client hello (172.168.1.3)
req: /remote/fgt_lang?lang=en
[192:root:2c]SSL state:SSLv3/TLS write server hello (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write certificate (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write key exchange (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write server done (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write server done:system lib(172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write server done (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS read client key exchange (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS read change cipher spec (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS read finished (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write session ticket (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write change cipher spec (172.168.1.3)
[192:root:2c]SSL state:SSLv3/TLS write finished (172.168.1.3)
[192:root:2c]SSL state:SSL negotiation finished successfully (172.168.1.3)
[192:root:2c]SSL established: TLSv1.2 ECDHE-ECDSA-AES256-GCM-SHA384
[190:root:2c]rmt_check_conn_session:1975 delete connection 0x560e9400 w/ web session 0
[190:root:2c]Destroy sconn 0x560e9400, connSize=0. (root)
[192:root:2c]epollFdHandler,569, sconn=0x561cb400[12,-1,-1,-1,-1], fd=12, event=25.
[192:root:2c]epollFdHandler:639 s: 0x561cb400 event: 0x19
[192:root:2c]Destroy sconn 0x561cb400, connSize=0. (root)
#11
btp
Bronze Member
  • Total Posts : 35
  • Scores: 2
  • Reward points: 0
  • Joined: 2007/09/26 02:02:57
  • Status: offline
Re: v6.0 is here 2018/04/03 03:58:18 (permalink)
0
Just upgraded - and notice that a subinterface (VLAN) that I created under wan1 in GUI, and then popped over to another VDOM, lost the reference to the main interface (wan1). I had to enter it manually afterwards.
 
config system interface
edit "TUBA"
set vdom "GET"
set vlanid 10
next
end


Attached Image(s)

#12
emnoc
Expert Member
  • Total Posts : 4989
  • Scores: 306
  • Reward points: 0
  • Joined: 2008/03/20 13:30:33
  • Location: AUSTIN TX AREA
  • Status: online
Re: v6.0 is here 2018/04/03 06:12:27 (permalink)
0

[191:root:2c]Destroy sconn 0x561cbd00, connSize=0. (root)
[190:root:2c]req: /remote/hostcheck_install?auth_type=16&u
[190:root:2c]rmt_hcinstall_cb_handler:450 remote check failed

 
So did you find a reason why? I just found out my sslvpn authentication rule didn't cary over when I push my FWF50E from v5.6.3 to v6.0.0.
 
Ken
 

PCNSE,  NSE , Forcepoint ,  StrongSwan Specialist
#13
rkhair
New Member
  • Total Posts : 20
  • Scores: 0
  • Reward points: 0
  • Joined: 2004/12/02 07:18:50
  • Status: offline
Re: v6.0 is here 2018/04/03 07:04:11 (permalink)
0
anyone notice that there 'web rating overrides' don't work? non of mine have worked since the upgrade to v6 tried to recreate them etc, but they seem to be just ignored.
#14
Andy Bailey
Bronze Member
  • Total Posts : 38
  • Scores: 2
  • Reward points: 0
  • Joined: 2016/06/27 11:21:22
  • Status: offline
Re: v6.0 is here 2018/04/04 07:43:25 (permalink)
0
Hello everyone,
 
The 6.0 update looks good- seems a bit faster on my Fortigate 60E (direct upgrade from 5.6.3).
 
But has anyone had any issues with modifying policies?
 
I've getting a "Failed to save some changes: Input value is invalid" message (showing in the attachment) when I try and modify a policy (for example add an anti-spam to an existing policy).
 
Has anyone else seen this? There are no "red" indications around any fields in the policy or hints that I can see and it seems to happen on every policy I have tried to modify. I know there is a new UUID for policies- perhaps somehow related to that?
 
Any ideas anyone?
 
Kind Regards,
 
 
Andy.
post edited by Andy Bailey - 2018/04/04 07:47:44

Attached Image(s)

#15
romanr
Platinum Member
  • Total Posts : 903
  • Scores: 30
  • Reward points: 0
  • Joined: 2004/06/08 08:29:56
  • Location: Vienna/Austria
  • Status: offline
Re: v6.0 is here 2018/04/04 08:20:16 (permalink) ☄ Helpfulby Andy Bailey 2018/04/04 12:54:16
0
Andy Bailey
I've getting a "Failed to save some changes: Input value is invalid" message (showing in the attachment) when I try and modify a policy (for example add an anti-spam to an existing policy).



Hey,
 
I don't have that problem - works fine for me since Beta 3.
 
Can you run the following on a Command Line, while you try to modify a policy:
 
diag deb reset
diag deb ena
diag deb cli 8
 
... and post the output
 
Br,
Roman
#16
Jordan_Thompson_FTNT
optimizzz
  • Total Posts : 459
  • Scores: 16
  • Reward points: 0
  • Joined: 2011/10/17 21:30:20
  • Location: Canada
  • Status: offline
Re: v6.0 is here 2018/04/04 08:29:25 (permalink) ☄ Helpfulby Andy Bailey 2018/04/04 12:34:55
0
romanr
Andy Bailey
I've getting a "Failed to save some changes: Input value is invalid" message (showing in the attachment) when I try and modify a policy (for example add an anti-spam to an existing policy).

 
Can you run the following on a Command Line, while you try to modify a policy:
 
diag deb reset
diag deb ena
diag deb cli 8
 
... and post the output

 
In addition, please enable "diag debug app httpsd -1" and include that output.
#17
ghorchem
New Member
  • Total Posts : 15
  • Scores: 0
  • Reward points: 0
  • Joined: 2012/07/07 09:09:21
  • Status: offline
Re: v6.0 is here 2018/04/04 09:43:08 (permalink)
0
you still cant use ecc ssl certfifcates to secure the admin web login page.
#18
Andy Bailey
Bronze Member
  • Total Posts : 38
  • Scores: 2
  • Reward points: 0
  • Joined: 2016/06/27 11:21:22
  • Status: offline
Re: v6.0 is here 2018/04/04 12:53:23 (permalink)
0
I've attached the output your requested Roman and Jordan. Thanks for your help.
 
Nothing really obvious for me. I tried opening the policy and then clicking ok (no changes) and again (no changes) same result both times. I tried Edge instread of Firefox too- no changes there either.
 
The key lines seem to be:-
 
[httpsd 9510 - 1522869450    error] cmdb_commit_from_json[1426] -- error saving request object to CLI (-651)
[httpsd 9510 - 1522869450    error] _api_cmdb_v2_config[1137] -- error editing object (nret=-651)
[httpsd 9510 - 1522869450    error] api_return_http_result[516] -- API error -651 raised


Interestingly I can delete policies- I just tried deleting a couple of unused policies and that worked fine (highlighted from the "IPv4 Policy" list and then just delete.
 
Any other ideas?
 
 
 
post edited by Andy Bailey - 2018/04/04 12:54:45
#19
Jordan_Thompson_FTNT
optimizzz
  • Total Posts : 459
  • Scores: 16
  • Reward points: 0
  • Joined: 2011/10/17 21:30:20
  • Location: Canada
  • Status: offline
Re: v6.0 is here 2018/04/04 17:59:37 (permalink)
0
Andy Bailey
I've attached the output your requested Roman and Jordan. Thanks for your help.
 
Any other ideas?

 
Thanks. This is helpful. We'l troubleshoot on our end.
#20
Page: 1234 > Showing page 1 of 4
Jump to:
© 2018 APG vNext Commercial Version 5.5