Looking at the following output (show interface status) from one of our 4507s I see gig interfaces 3/2 to 3/6 are all trunked (dot1q). When I look at a show run they do not show as trunked. They should indicate switchport trunk encapsulation dot1q and switchport mode trunk (as does interface gig4/2). I have seven other 4507s all running the same IOS: 12.2(25)EWA8 and they all show the same information in show run and show interface status (as far as trunked goes). This is not a problem as I know the interfaces are trunked and working properly I am just puzzled as to why I see this difference.
Here is the sho int gig3/2 trunk. It looks like you are correct. I did not realize some were set to trunk mode on and others were not. I would think the running config would still show the port using dot1q but I guess not. Thank you for your help! At least now I understand why I see a difference.
My first thought is that the port is left in the default state of "dynamic desirable". This will form a trunk if the other end is either listening for a trunk to be created (dynamic auto) or also wanting to create a trunk (dynamic desirable). The switchport won't show anything under the running config because the default settings haven't been changed for the port. You can also do a "show int g3/2 trunk" to see this.
Can you post the "show int g3/2"?
Your g4/2 has been configured manually to be in trunk mode for dot1q encapsulation.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.