Just need to ask a few questions about my packet tracer assignment
Got all green lights but some packet loss/connection issues :)
Mitch might know a bit and I'm sure he will see this thread.
Just to let you know I've seen it and will respond properly in the morning before I head to work when I can think straight.
I'm off to get some grub and sleep.
You see, I told you he would!!
:)
cool
Quote from: Lance on Nov 08, 2010, 22:50:38
You see, I told you he would!!
;D
We're good at the prediction lark aren't we. ;)
Ok later than intended but here goes.
What type of connection are you experiencing loss over? (one of the local LAN links or a serial WAN connection)?
Have you ensured both ends are in the up state (no shutdown issued on both ports)
If using RIP or RIP v2 as your routing protocol make sure your timers are in sync.
If using OSPF make sure the AS number is the same on both ends to ensure they achieve adjacency.
Hopefully thats enough to prompt you but if you can give me a little more info I maybe able to help a little more.
Well it seems I can ping from one pc on a vlan to other pcs on the equivalent vlan
I can ping from router to router over the serial connection
Switch to switch seems to have problems
Switch to PC seems to have problems
Switch to router seems to have problems
Using OSPF and Dot1q trunking
I'll post up my packet tracer layout in a bit - is there anything that springs to mind?
Just stumbled across this as I currently have no Internet, have you setup a native vlan on the swtich and assigned an IP address to it?
Yes
Assigned native to 1 and gave it ip 172.16.1.2 / .3 for each switch
Does any one have packet tracer?
If so I can post up the file
If not ill post up my setup and any relevant config files worth looking at
...Tomorrow that is :)
nn
I have packet tracer I should be able to have a look tomorrow.
:welc: :karma: nfx_
Welcome to our happy place, nfx_. :welc: :karma:
Welcome to the forums :karma:
:welc: :karma: nfx_
Attached Packet tracer
I dont necessarily want a direct answer, more what I should check as its been racking my brain, just need to figure it out :evil:
Thanks and welcome to idnetters !
Is it there...I attached it but couldnt see it before :blush:
Ahh yes
Attached below :laugh:
I've had a look, it looked as you hadn't setup the native vlan correctly on switches and router, below I have shown the config you had originally and what I have changed it to.
Switch1
interface FastEthernet0/1
switchport trunk allowed vlan 1,10,20
switchport mode trunk
!
interface FastEthernet0/2
switchport trunk allowed vlan 1,10,20
switchport mode trunk
New Config
interface FastEthernet0/1
switchport mode trunk
switchport trunk native vlan 1
!
interface FastEthernet0/2
switchport mode trunk
switchport trunk native vlan 1
!
Switch 2
interface FastEthernet0/1
switchport trunk allowed vlan 1-1001
switchport mode trunk
!
New Config
interface FastEthernet0/1
switchport mode trunk
switchport trunk native vlan 1
!
On the router you had used the native command but it was on the wrong interface so I just switched to the correct interface and everything appears to be working correctly now.
StaffordRouter
interface FastEthernet0/0.1
encapsulation dot1Q 1
ip address 172.16.1.1 255.255.255.0
!
interface FastEthernet0/0.10
encapsulation dot1Q 10
ip address 172.16.10.1 255.255.255.0
!
interface FastEthernet0/0.20
encapsulation dot1Q 20 native
ip address 172.16.20.1 255.255.255.0
!
New Config
interface FastEthernet0/0.1
encapsulation dot1Q 1 native
ip address 172.16.1.1 255.255.255.0
!
interface FastEthernet0/0.10
encapsulation dot1Q 10
ip address 172.16.10.1 255.255.255.0
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 172.16.20.1 255.255.255.0
!
The thing to remember is that the native vlan needs to be consistent across all switches and routers, hope this helps and hasn't just confused you further.
Well it looks impressive, I hope it works :karma:
I'm by no means an expert I only completed my CCNA at the start of this year, there are probably people here that will be able to explain it better than I have.
Looking at it at work at the moment. Thanks for taking a look :) ever grateful :) i'l have a pop tonight but that does make sense. Quite proud thats all i had wrong lol :) karma for you when i get hmme
Ah i understand the router native cmd now. Had to set it native on the 0.01 as that was vlan 1 the native id !
I have to say I had to back out of the CCNA due to work commitments before I got to VLANs so can't really give you an answer I'm afraid.
I cant seem to be able to ping a switch from a connected device
Is this normal?
Remember a switch is a Layer 2 device.
So to check functionality I should be able to:
- Ping from Router to Router
- Ping from Either Router to any Workstation
- Ping from workstation to workstation on same vlan
- STP packet from switch to switch
Any more?
I think you can ping from switch to switch but you won't get a response from the switch when pinging it from a connected PC.
As I say, I took a step back before we got to VLANs and switch programming but am sure someone will be along who can help with this.
Thanks tho :)
Am currently just pinging from workstation to workstation and to router
all good so far :)
Should I be able to access workstations/vice versa from stock router?
Attached image of setup
If they are on the same VLAN I believe so yes.
*stoke router
Its just on the worksheet it doesnt say anything about configuring stoke vlans
hmm
Might be advisable to have a chat with your instructor/course helpline.
indeed - i'll ask tomorrow
just strange it doesnt say about touching the stoke router other than setting up a loopback
surely I need to configure something to allow vlans to it
???
I'm guessing that the stoke router probably has nothing to do really with this task and is just there as a reminder in how to setup a router and serial links. I presume that you will probably be covering inter-vlan routing soon which will enable you to contact workstations on other vlans, its basically just adding the networks on the sub interfaces to the routing protocol that you are using.
Got it working now :)
Just had to double check ospf entries and voilá 8-)