I just found the doc on Cisco's site that says that same thing. CLI is misleading when they have the "encapsulation" option but you can't use it, even though there are different images for the 1720 and 1721 in the IOS planner. Guess I've griped enough for today. Thanks for the on and off list replies.
-nmp From: Devin Kinch [mailto:[EMAIL PROTECTED] Sent: Monday, June 23, 2008 2:53 PM To: Max Pierson Cc: [email protected] Subject: Re: [c-nsp] 1720 dot1q Problem Not supported on the 1720 (hardware limitation of the Ethernet chipset). I have one in my lab, and this has always bugged me, especially since the NM-2E2W modules (only 10/half) do support dot1q. On Mon, Jun 23, 2008 at 1:36 PM, Max Pierson <[EMAIL PROTECTED]> wrote: Hi List, I am having some issues with a 1720 and dot1q sub-interfaces. When I try to configure encap dot1q etc on the f0.2 subint, this is what I get.... c1720#conf t c1720(config)#int f0 c1720(config-if)#no shut c1720(config-if)#int f0.2 c1720(config-subif)#encap dot1q 2 ^ % Invalid input detected at '^' marker. c1720(config-subif)#encapsul? encapsulation c1720(config-subif)#encapsulation ? % Unrecognized command I was working on 12.3.20 and noticed CSCsh16540 <http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?metho d=fetchBugDetails&bugId=CSCsh16540&from=summary <http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?metho d=fetchBugDetails&bugId=CSCsh16540&from=summary> > "Router Crashes when encapsulation dot1Q", so I upgraded to 12.3.20a and still have the same issue. Do I need a different image, or am I missing something due to cluebit = 0 J TIA -nmp _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
