Does anyone have a working link to the Prime Infrastructure 3.0 Administrator guide? All the ones I have found either give a 404 error or redirect to the 2.2 version of the guide.
... View more
Is there a rackmount kit for the ASA-5545-X devices? It came with a cabinet rail kit but we plan on installing in a traditional 19" Telco rack.
... View more
You can't do exactly as you wish with just an ASA firewall. You could get a reverse proxy and/or webapplication firewall to handle this for you. However you should note that if these webservers use SSL or not as there are complications with using SNI.
... View more
For my authorization profile result in ISE for PI, I use the following: Access Type = ACCESS_ACCEPT cisco-av-pair = NCS:virtual-domain0=ROOT-DOMAIN cisco-av-pair = NCS:role0=Root Now you would obviously need to change this if you have multiple virtual domains in PI. It looks similar to what you are using. My successful login is shown below (however I don't see the Virtual port type): Source Timestamp 2015-03-03 10:23:56.123 Received Timestamp 2015-03-03 10:23:56.123 Policy Server MYISESERVER Event 5200 Authentication succeeded Failure Reason Resolution Root cause Username mycoolusername User Type Endpoint Id Endpoint Profile IP Address Identity Store MYADIDENTITYSTORE Identity Group Audit Session Id Authentication Method PAP_ASCII Authentication Protocol PAP_ASCII Service Type Network Device PISERVERNAME Device Type Network Management Location Corporate Office NAS IP Address PI-IP-ADDRESS NAS Port Id NAS Port Type Authorization Profile Cisco-Prime-Infrastructure Posture Status NotApplicable Security Group Response Time 19 Try taking out the port type=virtual in your authorization profile config. I only see the port type=virtual in the authentication.
... View more
A DOS attack to a layer 2 port is when a rogue host floods the interface with mac addresses. The switch will learn as many as it can until it fills it's mac address table. Once the mac address table is full, the switch will essentially turn into a hub and will begin flooding packets to all ports as it cannot do it's normal forwarding based on the mac address table. Different switches have different capacities, but in general every host port should be protected from this flood attack by limiting the amount of mac addresses it will learn on each port. http://en.wikipedia.org/wiki/MAC_flooding
... View more
You can protect against DOS by using port security. This should be done on every non trunk port. interface gig0/1 switchport port-security maximum 3 switchport port-security switchport port-security violation restrict This will allow only 3 active mac addresses on port gig0/1. In order to protect against MAC spoofing you would need either dot1x security or dynamic arp inspection (which requires DHCP snooping and you are using static ips).
... View more
From my experiences, a single T1 line for 8 users is insufficient bandwidth with any video content beyond an office user type workload. I would check the pool settings as well as the teradici pcoip group policy settings for your pool in question. Maybe you have build-to-lossless turned off or something. From the network side I would check MTU first from the branch side. Make sure you can ping your connection servers with the do not fragment bit enabled and be sure the MTU you are using is correct. As far as the QOS is concerned, you really should just have UDP 4172 matched and not all the HTTP and HTTPS and other ports you have. You could be congesting your queue as you've cast a pretty wide net there. Can you post show policy-map interface ser1/0 on your 7206? Also do similar for the branch interfaces on their routers. Here is some nice reading material from VMware's documentation (link)
... View more
What you're asking is possible to do on each SVI with an access-list. As you've noticed the full features of IOS aren't available in their switches so it will be a little tedious to manage.
... View more
I won't show my exact config file, but I will post the details below. Basically what I did was modified the "Host *" template uncommenting what configuration items I wanted to change. You can leave the other sections commented out and openssh will continue to use default for things you have not specified. So step one is to uncomment Host *. Uncomment Ciphers and MAC lines. Change any order you prefer for the Ciphers and MAC lines. Save the file an reboot the linux OS. I exited the shell and typed reload in the CLI to reboot the linux OS. My system took around 5 minutes to fully reboot and load PI into it's usable state.
... View more
Thanks Marvin, modified the /etc/ssh/ssh_config file making the necessary changes. Now PI uses SHA1. Hopefully no future patches get clobber because of this! haha
... View more
Is there any way to change the SSH2 encryption and hash settings PI 2.1 uses to connect to it's managed devices? Right now it is using AES-128 and MD5, but I would like to change it to AES-256 and SHA1.
... View more