EXOS v21 - SOAP/XML API
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-11-2017 07:02 AM
Hi, we've long been users of the XOS SOAP/XML API for provisioning tasks, but it seems to have changed in v21, since the CherryPy update of the web framework. The API endpoint used to be http(s):///xmlService, but this now just gives a 404. The WSDL and XSD files all seem to still be there. Can't find anything in the documentation, apart from the release notes acknowledge that the SOAP/XML functionality should still be there. Anyone know what the API endpoint is now?
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-11-2017 03:29 PM
For anyone following this thread, it was confirmed as a bug and a fix is scheduled for release with 22.3.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-11-2017 12:16 PM
Yeah, I'll get one opened with TAC, thanks for confirming what I'm seeing.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-11-2017 12:00 PM
It seems you are right, strange. I think opening a case for that would be best.
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 hello emertxe "show ver"SOAP-ENV:Client Not a valid user
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 oscar emertxe "show ver"
Slot-1 : 800550-00-08 1626N-41812 Rev 8.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-2 : 800554-00-07 1636N-41581 Rev 7.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-3 :
Slot-4 :
Slot-5 :
Slot-6 :
Slot-7 :
Slot-8 :
X460-G2-VIM-2Q-B-1: 800555-00-03 1521N-40658 Rev 3.0
Image : ExtremeXOS version 22.2.1.5 by release-manager
on Mon Feb 27 11:03:54 EST 2017
BootROM : 1.0.2.1
Diagnostics : 5.11
Certified Version : EXOS Linux 3.18.24, FIPS fips-ecp-2.0.12
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 oscar emertxe "show account"
User Name Access LoginOK Failed State
-------------------------------- ------ ------- ------ --------
admin R/W 15 0 Enabled
user RO 0 0 Enabled
hello R/W 0 0 Enabled
oscar R/W 2 0 Enabled
okoot@bigbird:~/work/EXOS-XML$
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 hello emertxe "show ver"SOAP-ENV:Client Not a valid user
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 oscar emertxe "show ver"
Slot-1 : 800550-00-08 1626N-41812 Rev 8.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-2 : 800554-00-07 1636N-41581 Rev 7.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-3 :
Slot-4 :
Slot-5 :
Slot-6 :
Slot-7 :
Slot-8 :
X460-G2-VIM-2Q-B-1: 800555-00-03 1521N-40658 Rev 3.0
Image : ExtremeXOS version 22.2.1.5 by release-manager
on Mon Feb 27 11:03:54 EST 2017
BootROM : 1.0.2.1
Diagnostics : 5.11
Certified Version : EXOS Linux 3.18.24, FIPS fips-ecp-2.0.12
okoot@bigbird:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 oscar emertxe "show account"
User Name Access LoginOK Failed State
-------------------------------- ------ ------- ------ --------
admin R/W 15 0 Enabled
user RO 0 0 Enabled
hello R/W 0 0 Enabled
oscar R/W 2 0 Enabled
okoot@bigbird:~/work/EXOS-XML$
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎04-11-2017 11:43 AM
After some further testing, we may have stumbled on one of the strangest bugs I've come across. It seems that the XOS APIs aren't working for usernames that start with the letters h,i,j,k,q,r or s. Starting with any other letter is fine, but not those ones. Would appreciate if you could test this out on your switch Oscar and see if you are getting the same behaviour?
