11-12-2004 02:42 PM - edited 03-02-2019 07:56 PM
Hello, I have vlan1 on FA/1, and vlan2 on FA/3. vlan1 has the IP of 192.168.100.1/27 , vlan 2 is 192.168.100.33/27. I have a PC connected to FA/3 that can ping 100.33 but not over to 100.1 on vlan1.
Both ports are in trunking mode with dot1q encapsulation. Here are some shows ... Any ideas or help would be appreciated, I know I am just missing something simple here. Thanks!
router#sh int fa 1 tru
Port Mode Encapsulation Status Native vlan
Fa1 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa1 1-1005
Port Vlans allowed and active in management domain
Fa1 1-2
Port Vlans in spanning tree forwarding state and not pruned
Fa1 1-2
router#sh int fa 3 tru
Port Mode Encapsulation Status Native vlan
Fa3 on 802.1q trunking 2
Port Vlans allowed on trunk
Fa3 1-1005
Port Vlans allowed and active in management domain
Fa3 1-2
Port Vlans in spanning tree forwarding state and not pruned
Fa3 1-2
#sh int fa 1 switchport
Name: Fa1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1-2
Priority for untagged frames: 0
Override vlan tag priority: FALSE
Voice VLAN: none
Appliance trust: none
#sh int fa 3 switchport
Name: Fa3
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 2 (test_vlan)
Trunking VLANs Enabled: ALL
Trunking VLANs Active: 1-2
Priority for untagged frames: 0
Override vlan tag priority: FALSE
Voice VLAN: none
Appliance trust: none
11-12-2004 03:03 PM
Are both vlans showing up and up in show ip int br? Can you source a ping on the switch from vlan 1 to vlan 2 and vice versa? Does the ip network show up as directly connected in a show ip route? I'm not sure why you are trunking to an end pc but the configuration will work because your native vlans are set appropriately to match the untagged packets sent by the pc.
11-12-2004 03:16 PM
Thanks for the response, Yes both vlans are up and up, Pings between the two are successful, and the interfaces are directly connected in sh ip route. I am only using a PC because I dont have another switch to use to test connectivity through the 1721 and across vlans...
#ping
Protocol [ip]:
Target IP address: 192.168.100.33
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.100.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.33, timeout is 2 seconds:
Packet sent with a source address of 192.168.100.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
C 192.168.100.0 is directly connected, Vlan1
C 192.168.100.32 is directly connected, Vlan2
11-12-2004 03:18 PM
Thanks for the response, Yes both vlans are up and up, Pings between the two are successful, and the interfaces are directly connected in sh ip route. I am only using a PC because I dont have another switch to use to test connectivity through the 1721 and across vlans...
#ping
Protocol [ip]:
Target IP address: 192.168.100.33
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.100.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.33, timeout is 2 seconds:
Packet sent with a source address of 192.168.100.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
C 192.168.100.0 is directly connected, Vlan1
C 192.168.100.32 is directly connected, Vlan2
11-12-2004 03:50 PM
Looks good! Dumb question but is the subnet mask and default gateway set correctly on the pc?
11-12-2004 04:00 PM
There are no dumb questions in networking :)) .. Yes it is, its being handed out by the 1721 .. its gw is 100.33 the ip of vlan2 mask is /27. Unless this is incorrect?
Would a routing protocol help at all? I had turned up ospf but it didnt seem to help ...
01-03-2005 01:07 PM
The problem was one of the fa ports were not trunking. I just had turn on trunking on the port and give it its native vlan.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: