06-26-2024 11:33 AM
This post maybe could go to switching, but as the problem is a C1111 router I figure to post it here. I have 2x of these routers at 2 different locations that connect via a fiber network. I am told the switch connecting is "untagged". I have 3 vlans configured, 2 of which I really need to use to communicate. The primary is a default "VLAN 1", the other vlan 100.
In testing I had these routers + some other devices & routers all connected through some basic Netgear 5 port switches, all was good. Now they are remote, all is not good. One of the physical ports was configured as:
interface GigabitEthernet0/1/0
switchport trunk allowed vlan 1-102
switchport mode trunk
The other port is:
interface GigabitEthernet0/1/1
switchport mode access
The VLAN config is pretty basic:
interface Vlan1
ip address 10.5.5.2 255.255.255.240
ip nat inside
!
interface Vlan100
ip address 10.5.6.2 255.255.255.248
I had found some other threads online referencing a 8P model that had "untagged" added to the VLAN configuration, but my options are more limited. Nevertheless I am at a loss to think what I can test next.
The last thing I did was had port 1 with vlan 1 connected directly to a FPR1010 ASA on it's switchport (vlan1) and that too just would not get a ping response. I did have the C1111-4Ps switchport/vlan connected directly to an old router with (Cisco 1721 w/4 port switch). That worked just fine. I am afraid I am either missing something, ignorant of something else, or ??. I did reach out to the other end but am afraid it will come back with "our switch is untagged" response only. Don't know what I can see or do to test further the communication problems.
p.s. I did temporarily test using Gigabit 0/0/1 connected and that of course worked, so this isn't cabling issue but a config issue on my end.
06-26-2024 11:36 AM
Can you draw topolgy
Thanks
MHM
06-27-2024 01:18 AM - edited 06-27-2024 01:18 AM
Hello @TRENT WAITE ,
if the switch is untagged it means the switch has an access port in one VLAN and connecting to its port a port configured as an 802.1Q trunk can provide connectivity only on the native Vlan if the two ends agree on the native VLAN ID.
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide