Hey Brian,   This is not working like this, I made sure both FlowCollectors and SMC can resolve the local FQDN of the servers, through the configured DNS server in SMC, even tested it on the SMC configuration page to make sure cache is corect, but in WebGUI the resolution does not happen, that is in my opinion wrong. SMC should try to resolve by itself the FQDN of the IPs, specially for the Server Host Groups. Or we should have an option in Host Group configuration where to mention if we ask SMC to do FQDN resolution or not for those host groups. ... View more

Hey Carlos, I presume you're using Stealthwatch 7.0 from the picture, go to Stealthwatch Management Console, then to Central Management, choose SMC -> from Actions choose Edit Appliance Configuration for SMC -> within Appliance Configuration switch to Network Services -> then add on the right, manually the FQDNs of the host you want resolved in Local Resolution tab. I added 2 snapshots for ease. Then you'll have the names resolved in Dashboard, specially in Host dashboard. ... View more

Hello Adrian, Please have a look in a guide how to configure SSM in promiscuous mode, it should work as you expect. http://www.cisco.com/en/US/docs/security/ips/6.1/configuration/guide/cli/cli_ssm.html thanks ... View more

Hello guys, I noticed the issue, I noticed the discussion but I haven't noticed an working response for IOS IPS 15.; I followed Dustin Ralich's guide and I had to do the followings : use the link "ida-client server url https://www.cisco.com/cgi-bin/front.x/ida/locator/locator.pl " created the trustpoint root imported the certificate for www.cisco.com created the trustpoint for L3 from Verising imported the certificate from verisign; entered the autoupdate menu #ip ips auto-update set the "cisco" auto-update path; set the occurence set the username and password verified the update with "debug ip ips auto-update" and "debug ida-client" update successful ... View more

Hello, you could try to remove the "domain clientless" extension defined in your webvpn context : #gateway ISR2801-RM domain tunnel I had the same issue and I believe that the domain is somehow linked to the trustpoint, so while the domain declared is not part of the selfsigned certificate defined in trustpoint, there is no need for the option domain tunnel; ... View more