I promise this is the last time I respond to myself :) Hopefully it will provide some insight.
I believe I found the reason the Cat5k was not being routed when connected to a certain port on the default gateway-- I noticed the encapsulation for the interface was set to 802.1q...which I definitely DIDN'T do-- in fact I had created a subif with ISL encapsulation. It turns out there were some subif's created quite a while ago. The encapsulation of these subifs were all set to 802.1q. Despite the fact that all these 802.1q subinterfaces were administratively shut down, the physical interface still reflected this and listed its encapsulation as 802.1q as well. To resolve, I went to each subif on the problem interface and took off any and all encapsulation via "no encap". I shut down each interface (again) just for good measure. After doing this, the physical interface displayed ARPA encapsulation and everything works fine-- connected the Cat5k to the to the problem port, and everything was routed fine. Whew! What a pain to track down. Even when entering "no interface ", the subinterfaces remained persistent. Weird. I'll close this thread and open a new one regarding this persistent subif behavior. :) Thanks to Dave and everyone helped/offered help. - Sean -----Original Message----- From: Sean Knox [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 1:34 PM To: [EMAIL PROTECTED] Subject: RE: Catalyst 5000 not being routed [7:34566] Well, strangely the Cat5k is being routed now... Due to another situation, I was forced to move the interface the Cat5 connected to on the default gateway... Originally the Cat5k connected to FastEthernet 1/0/7 on a Cat8510, but now its connected to Fa1/0/4 on the Cat8510. I configured the new connection with the same IP as the other, and it works fine. For the record, I don't have any VLAN encapsulation set on the new port. I think I have a bad port, because I'm having problems connecting another device to the original port. I'm seeing a lot of "%AAL5-3-NOBUFFER: No reassembly buffers to receive pkt , vpi 0, vci 35" errors when I connect the port in question to another device (an older Extreme Summit48 switch). - Sean Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34800&t=34800 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
