All, Checking in with a request for feedback regarding use of the spanning-tree link-type point-to-point command and its uses.  For configuration samples, when and where is the command used and is it possible to see it only at one end of a switch to switch link without issue?   Example config - two switches Switch 02 Int Gi1/0/26 Description - Link to CORE Building 1 Complex A  Sw01 P1/0/26 switchport access vlan 126 switchport trunk allowed vlan 2,101,126 switchport mode trunk switchport nonegotiate spanning-tree portfast  (*not in play due to trunk port*) spanning-tree link-type point-to-point (Full duplex direct link assumption)   Switch 01 Int Gi1/0/26 Description - Link to CORE Bld2 Complex B xxxx Sw02 P1/0/26 switchport access vlan 126 switchport trunk allowed vlan 2,101,126 switchport mode trunk switchport nonegotiate spanning-tree portfast  (*not in play due to trunk port*) REM spanning-tree link-type point-to-point (Full duplex direct link assumption)   Example config question - What if this side of the link did not have 'Spanning-tree link-type point-to-point' - what symptoms or risks would be visible or if the link is designated as full duplex, no anomalies would be seen? Thanks in advance for the reviews and comments   ... View more

To all, We have seen an interesting anomaly over the past three months where Storm Control triggers a shutdown of an interface as configured.  The Storm Control configuration looks like the following; storm-control broadcast level pps 2k 300 storm-control multicast level pps 4k 3k storm-control action shutdown   Our interfaces constantly run around 2.82k and to 2.85k pps Issue - we encounter 7 or 8 pairs of switches executing the shutdown command out of 18 pairs of switches on the same subnet.   Possible Resolution? What parameters have others used for storm-control and what are the risks to increasing pps to 5k and 4k? storm-control broadcast level pps 2k 300 storm-control multicast level pps 5k 4k storm-control action shutdown Thoughts and comments requested.  The team is reviewing applications and other aspects that could trigger these events.  Any comments or suggestions are welcome ... View more

We are having an issue with the following setup; Cisco 2504 Controller -  Software Version 8.1.102.0   Cisco 3702I - two AP's - regulatory domains are unprimed, need to prime them - flashing green, red, black confirms (visual), and the controller notes unprimed AP's Regulatory Domains Country Code Universal Prime Status Cisco Discovery Protocol      We have connected to CCO via smartphone, logged in, and are having issues acquiring an IP address.  The following steps have been completed to prep the controller and AP's for 'priming' - We of course cannot login via smartphone to SSID called Universal AP (for priming).  It seems the smartphone is not acquiring an IP address after login ENTER WIFI PASSWORD screen on smartphone - notes WiFi is not connecting; Preparing a 2500 Series Controller for Manual Priming Step 1  Open the WLC graphical user interface (GUI) Step 2  Choose WLANs to open the WLANs page. This page lists all of the WLANs currently configured on the controller. For each WLAN, you can see its WLAN ID, profile name, type, SSID, status, and security policies. Step 3  Click the WLAN ID of the WLAN to which the universal AP is to associate. The SSID of this WLAN is the same SSID which the smartphone will need to connect to later, when priming the universal AP. Step 4  Go to Security tab > Layer 2 tab. a.  Choose Layer 2 Security as ‘WPA+WPA2’ b.  Under WPA+WPA2 Parameters check the WPA2-Policy AES check box. c.  Under Authentication Key Management enable 802.1x or PSK, based on your requirements.  (WE chose PSK since we have no radius server) Step 5  Go to the Advanced tab. Enable Universal Admin Support by checking the Universal AP Admin check box. Step 6  On the General tab, select the Status check box to enable this WLAN. Alternatively, to enable the WLAN at a later stage: a.  Choose WLANs to open the WLANs page. b.  Enable or disable a WLAN from the WLANs page by selecting the check box to the left of that WLAN. c.  Choose Enable Selected from the drop-down list d.  Click Go. e.  Click Apply. Step 7  Click Apply to commit your changes. Step 8  Click Save Configuration to save your changes. During manual priming, using Cisco AirProvision, ensure that all non-universal APs on this WLAN are disabled. This ensures that the smartphone connects to only the universal AP awaiting priming. Once your configuration settings are committed, proceed with Step 3, in the Overall Workflow for Priming a Universal AP. Any comments or tips to have the smartphone connect and acquire an ip address from the priming SSID network?             ... View more