I was working with the Nexus 7K last year and there are some things to consider when working with VPC and layer 3 SVI to consider. Specifically I had a need to be able to do both layer 2 trunks and layer 3 routing. In my previous configuration with VSS this was not and issue because the single active supervisor. VPC is a different animal and cannot route traffic back accross a link so there are some design considerations I got from Cisco's Nexus business unit. Because of you design I thought that I would share my notes, I hope that they are helpful... Layer 3 and vPC Interactions: Unsupported Designs: 1. Peering over a vPC inter-connection 2. Peering over an STP inter-connection using a vPC VLAN 3. Peering over a vPC inter-connection vPC Connect layer-3 routing device - When connect layer-3 routing devices to a vPC domain, do not form routing adjacency with vPC peer devices over the vPC peer-link (unsupported design) - If dynamic routing is required to a vPC domain, L3 routed interfaces should be utilized - If L3 routed interfaces can not be used, connect L3 routing devices to a vPC domain using vPC and implement static routing to FHRP address vPC Design Considerations Do not mix vPC and Layer 3 on the same interface - Different recommendation for Aggregation to Core than with VSS ECMP LInks - Use separate L3 links to hook up Core Switches to a vPC domain - Don’t use L2 port channel to attach routers to a vPC domain unless you statically route to HSRP address - If both, routed and bridged traffic is required, use individual L3 links for routed traffic and L2 port- channel for bridged traffic
... View more
I too am having an issue here and would be content to either have the page redirect to http or successfully take the 3rd party certificate. When I did install the cert the client PC being redirected says it is being redirected to a trusted site and then doesn't go there when you select "yes". Anyone have any progress here?
... View more