cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1438
Views
15
Helpful
7
Replies

I have a problem in packet tracer

Salehchroma
Level 1
Level 1

 Hello every one , i have a problem in my topology, when i want to send packets from PC to another PC i got failed so, can you help me with my problem

and please explain the problem after solving.

3 Accepted Solutions

Accepted Solutions

Hello,

 

the DHCP pools on  the MLS switches dish out the wrong default gateways. Change the '60' to '1', which matches the actual IP address of the Vlan interfaces.

 

ip dhcp pool vlan10
network 78.69.0.0 255.255.255.0
default-router 78.69.0.60
ip dhcp pool vlan20
network 78.79.0.0 255.255.255.0
default-router 78.79.0.60
ip dhcp pool vlan30
network 78.89.0.0 255.255.255.0
default-router 78.89.0.60
ip dhcp pool vlan40
network 78.99.0.0 255.255.255.0
default-router 78.99.0.60
ip dhcp pool Staff
network 78.69.0.0 255.255.255.0
default-router 78.69.0.60
ip dhcp pool Student_1
network 78.79.0.0 255.255.192.0
default-router 78.79.0.60
ip dhcp pool Student_2
network 78.89.0.0 255.255.192.0
default-router 78.89.0.60
ip dhcp pool Student_3
network 78.99.0.0 255.255.192.0
default-router 78.99.0.60

View solution in original post

Martin L
VIP
VIP

Same switch mentioned above complains about Native Vlan ID mismatch; Native vlan should match (same id) per each of links. aka per pair of switches. 

Core routers complain about ospf getting incorrect ospf area id from neighbors. I think you just made several typos under router ospf network x area y.  alternative to network x area y command under ospf, you can use ip ospf 1 area x under each interface. 

 

Regards, ML
**Please Rate All Helpful Responses **

View solution in original post

fix for Router 2 is to change  network 59.0.0.32 0.0.0.3 area 0 into  network 59.0.0.32 0.0.0.3 area 59,

fix for Router 3 is following network 59.0.0.60 0.0.0.3 area 59,  network 59.0.0.28 0.0.0.3 area 59

basically, those 2 routers have interfaces in area 59, not 0

 

Regards, ML
**Please Rate All Helpful Responses **

View solution in original post

7 Replies 7

Hello,

 

the DHCP pools on  the MLS switches dish out the wrong default gateways. Change the '60' to '1', which matches the actual IP address of the Vlan interfaces.

 

ip dhcp pool vlan10
network 78.69.0.0 255.255.255.0
default-router 78.69.0.60
ip dhcp pool vlan20
network 78.79.0.0 255.255.255.0
default-router 78.79.0.60
ip dhcp pool vlan30
network 78.89.0.0 255.255.255.0
default-router 78.89.0.60
ip dhcp pool vlan40
network 78.99.0.0 255.255.255.0
default-router 78.99.0.60
ip dhcp pool Staff
network 78.69.0.0 255.255.255.0
default-router 78.69.0.60
ip dhcp pool Student_1
network 78.79.0.0 255.255.192.0
default-router 78.79.0.60
ip dhcp pool Student_2
network 78.89.0.0 255.255.192.0
default-router 78.89.0.60
ip dhcp pool Student_3
network 78.99.0.0 255.255.192.0
default-router 78.99.0.60

Salehchroma
Level 1
Level 1

thanks, but i still have a problem when i send packets between PC to PC from another VLANs and Between servers and the PCs.

 

Thanks again ....

Martin L
VIP
VIP

Same switch mentioned above complains about Native Vlan ID mismatch; Native vlan should match (same id) per each of links. aka per pair of switches. 

Core routers complain about ospf getting incorrect ospf area id from neighbors. I think you just made several typos under router ospf network x area y.  alternative to network x area y command under ospf, you can use ip ospf 1 area x under each interface. 

 

Regards, ML
**Please Rate All Helpful Responses **

fix for Router 2 is to change  network 59.0.0.32 0.0.0.3 area 0 into  network 59.0.0.32 0.0.0.3 area 59,

fix for Router 3 is following network 59.0.0.60 0.0.0.3 area 59,  network 59.0.0.28 0.0.0.3 area 59

basically, those 2 routers have interfaces in area 59, not 0

 

Regards, ML
**Please Rate All Helpful Responses **

Thank you so match,

but there is a last problem is that: the all MLSs does not allowed the PCs or servers to send any packets to another PCs out of that MLS's Switches, so what is the problem with this.

and thanks again for you and i appreciate your help....

Hello,

 

post the project file again with all the changes you have made so far.

Focusing on Green network, CS dept. we have 2 issues: 1. different DHCP pools on MLS2 vs MLS3 for vlan 10,20,30,40; and MLS 2 has same network range for vlan 10 and for pool Staff,  vlan 20 as pool Student_1, and etc.Not a issue here but when you compare 2 MLS switches, then we have different network ranges for vla 10 -40.   Which one is correct?

issue 2. L2 switches should not have same IPs as L3 for vla 10 and 20.  L2 switches are not doing routing so IPs are just for management purpose; those L2 switches should have its own network separate from data/users networks.  

following does not match what you have written in text box in green area : 

ip dhcp pool vlan10

network 78.70.0.0 255.255.255.0

default-router 78.70.0.10

ip dhcp pool vlan20

network 78.80.0.0 255.255.255.0

default-router 78.80.0.10

 

comparing to MLS 2

ip dhcp pool vlan10

network 78.69.0.0 255.255.255.0

default-router 78.69.0.60

ip dhcp pool vlan20

network 78.79.0.0 255.255.255.0

default-router 78.79.0.60

 

Update: forgot to mention MLS 2 does not have ospf turn ON and once you have DHCP fixed, don't forget to re-new IPs on PCs.