depending on how you've deployed prime, you can use the compliance tool. Now, your question was is there any way to see the config. the compliance tool doesn't really do that, but you can set up a template that includes the baseline of how the switches should be set up, and will show any discrepancies when you run the template.   other than that, I don't think there's a way to automate this. I mean you could always view the config archive in prime, but you'd need forever and a day to audit a large number of switches.    chris   ... View more

general rule of thumb that I've used when moving to a new platform is to go with whatever the current recommended version for your platform is. I think 16.6.6 is for the 4331s but that may have changed already.  and as always, read the release notes. ... View more

are you rebooting via the CLI or pulling the plug? There is a field notice on this, and in my experience the couple of times that I have seen this, pulling the plug resolved it. But the condition that we had was both the original software was 15.0.2ex, and the switches had stack mods. if you have not tried that then that's what i would suggest. If you have done that, then disregard. ... View more

as I read this, it's not the chassis fan tray, it is one of the power supply fans. What I have typically seen for this condition is to RMA the power supply. The other thing that I have seen, although only once or twice, is a flaky line feed and you have to call an electrician. But most often this message has been caused by a power supply going bad. Assuming you have two supplies, the replacement would be transparent as long as you are configured for redundant mode and not combined mode.   ... View more

have you run debugs on dhcp on your core device? ... View more

are you getting the unsupported module message in 15.0.2-se11, or in 15.2.2-e9? Last year I took a bunch of 2960S stacks directly from 12.2.53 (or 12.2.58) directly to 15.2.2-e8 and I did not have a problem at all with any of them. If you're going to 15.0.2-se11 and you're seeing that message, did you or can you try going directly to 15.2.2-e9? ... View more

I don't think clearing the protocol will do anything, you would need to be able to clear redistribution, and I don't there's any way to do that other than removing and readding the redistribute line under BGP config. ... View more

yep, your conceptualization is backward. It's all from the perspective of the SVI. Inbound acl on the SVI means traffic sourced from vlan 100 destined for the network, and outbound acl on the SVI means traffic from the network destined for vlan 100. It can be a little counter intuitive at first but once you get it it's easy.  ... View more

your direction is wrong. Looking specifically at the amarinth-in acl, which is applied inbound on the SVI for vlan 100. What that means is that any traffic on vlan 100 coming to the SVI. So your source hosts would have to be 10.0.100.x to see hits on the acl as you are expecting. What you are seeing now is the acl doing exactly what you told it to do. this will sound corny, but to clarify how the direction works, imagine you are standing right at the vlan 100 SVI, facing the LAN for vlan 100. an acl applied inbound would be sourced on vlan 100. an acl applied outbound would be destined for valn 100. ... View more

do you have LLDP enabled? If not, enable it and see if that makes a difference. ... View more