cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
633
Views
0
Helpful
0
Replies

891W 'mac-address-table secure sticky' partially missing feature

ian.m.covington
Level 1
Level 1

I'm having trouble configuring secure mac addresses on a Cisco 891W (CISCO891W-AGN-A-K9). Here is the CLI in/out:

(config)#mac-address-table secure sticky f6
Need to enable dynamic port security on the port first before enabling the sticky address
(config)#int f6
(config-if)#switchport ?
  access     Set access mode characteristics of the interface
  mode       Set trunking mode of the interface
  priority   Set 802.1p priorities
  protected  Configure an interface to be a protected port
  trunk      Set trunking characteristics of the interface
  voice      Voice appliance attributes


I've never seen 'Need to enable dynamic port security on the port first before enabling the sticky address' before, and there doesn't appear to be any way to enable the feature in interface config mode, or global config mode.

There are some bugs that affects the 891W: 

'mac-address-table secure sticky' doesn't work - CSCum90577. It doesn't exactly match up with the behavior I am seeing. In the bug, the commands are at least accepted. In my situation, they are rejected. Also, my code version is beyond the fixed code versions

'Dynamic port security feature is missing for C880 platforms' - CSCug19555. In this case, the feature is missing which seems more in line with what I am experiencing. It describes the bug as affecting 'C800' platforms, which means 'hardware platform' in my mind. The difference I see is that this supposedly affects the C800 routers, and mine is a CISCO800 router, so a different hardware generation. It is called 'C890 Software' (C890-UNIVERSALK9-M), so maybe it can be affected, although my code is beyond the fixed code versions.

Is there some obscure CLI that isn't placed logically, a possible bug, or do I need to run the exact code versions that contain the fix? I don't see the code version being the issue, because it doesn't make sense to introduce a fix, and then pull it in later releases.

Thanks for the assist.
Ian

 

0 Replies 0