Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello Team,
1. How to fetch easily all alarms generated on SMC from the last 24 hours ?
Looking at:
https://developer.cisco.com/docs/stealthwatch/#!reporting-api-version-1
It looks like i need to do multiple different queries including tags like: ext...
Hello Team,I am using API to get some details about my env.I got orgid and networks successfully:[
{
"id": "N_595038100766352700",
"organizationId": "620490",
"name": "Wireless",
"timeZone": "America/Los_Angeles",
...
Hello Team,
Do we have any plans to have ISE being ready for multi-tenancy (supporting many separate orgs / customers) ?
It looks like we have already most components ready for this (including AD, IP-SGT mapping per VRF), but one very important is ...
Hello Team,
CSR1k 16.9.1.
I have enabled rest:
aaa authentication login HTTP local
username rest privilege 15 password 0 Krakow123
ip http server
ip http authentication aaa login-authentication HTTP
ip http secure-server
restconf
(i have also tes...
Hello Team,
NSO 4.6.2 with FMC registred, i am using restconf API to manage my FMC via NSO. I am able to read the objects, example in CLI:
#show devices device FMC01 | display xpath
.....
/devices/device[name='FMC01']/cisco-fmc-meta:ciscofmc-id-...
Hi Paul,
Yep, that is correct, no authentication, it looks perfectly fine, i have the same and it's working fine:
I do believe you might be using too old version of ISE (2.1) where that API was not yet really there, i remember to have some cha...
OK, i've just found a solution for authentication failure (not for 411 error!)
I had exactly same issue with netconf:
To get restconf or netconf working we need to be sure the user is not only in priv15 lvl but also exec mode authorization is enabled...
Hi Viktor, Team
Thank you for the help here.
I have opened TAC case 685381128.
ncs --reload did not help but....
After we rebooted whole VM the problem is gone. We can see process listening on tcp/8080.
Certainly some problem here.
Will keep in monit...
Hi Jan,
Yes - this is default 4.6.2 install, no changes to nso.conf, very default install. And i can confirm no process listening on tcp/8080. ncs --reload did no help.
I will open a TAC case for this and update you here on the results.
Thanks !
Hi Jan,
Thanks for the help here.
It looks like we have no process listening on 8080.
the same also with lsof:
telnet gives the same result as curl.
Should it work out of the box ? Or maybe there is something i should configure after deploying NSO ...
