03-07-2023 09:01 AM - edited 03-08-2023 05:24 AM
The pinging works if it's between the PCs however when doing the following, it doesnt work:
*********************************************************************************
UPDATE:
Thanks so much everyone for helping! I've now got full connectivity everywhere.
How connectivity to VLAN got fixed =
Some small changes I made to the ip addresses in my VLAN. Also the ISP router wasn't announcing the network 11.0.0.0 properly so i managed to sort that out by setting the Aimee router's Serial port to the network 11.0.0.0 first. Then because the cloud server Fa-port was set down, I fixed it by just re-wiring the copper-cross-over wire again and it worked.
How connectivity to wireless LAN C got fixed =
A simple change I did to the Aimee router. After coding the following, the IP addresses was set correctly by the DHCP and this enabled the full connectivity to work:
(config) ip dhcp excluded-address 10.87.255.254
Updated image:
Solved! Go to Solution.
03-07-2023
09:07 AM
- last edited on
03-28-2023
11:14 PM
by
Translator
Couple of the things you need to check here on the switch.
- is the switch acting as Layer 2 ? or Layer 3?
- what is the PC gateway ? is this point to 0.1 or 63.254 ?
- how is your config switch port config - connected to router
- can you post
show run
(from switch and Router) (if possible all the device show run)
03-07-2023 10:30 AM - edited 03-07-2023 10:31 AM
Pinging to PCs also worked but only 4/5 success. - if you do one more time you get success 5/5 (you see normally intial packet los for the first time).
If you running RIP as IGP, ISP router not anouncing the network 11.1.1.1/30 - so add this network anouncement on ISP router.
Cloud server configured 88.44.22.2/30 ? where is the gateway configured for this ?
ISP router you need to replace 11.1.1.1/30 with 88.44.22.1/30 or reconfigure Cloud server with IP 11.1.1.2/32 gateway 11.1.1.1 to work.
The other destinations did not work at all from the router. - give example which was failed ?
03-07-2023
01:31 PM
- last edited on
03-28-2023
11:21 PM
by
Translator
RIP when you issue a command network that might have already taken in to routing table
you can check on Aimee router
show IP route
(you should see 11.0.0.0 supernet there)
cloud router - try rebooting after the IP change. see not sure what image you using as cloud router.
When pinging from Aimee router it fails in the following:
When trying to ping from switch then it fails in following:
03-08-2023 02:36 AM
I am not familiar with PT, how the AP configuration to be done on PT
high level you have routing issue and make sure you have right DHCP Scope and right default gateway for the pool for the devices to work.
check this video :
03-08-2023 03:31 AM
169.254.0.0/16 (169.254.0.0 – 169.254.255.255)
These addresses are “link local,” which means packets with these addresses are sent out to the network, but should never be forwarded to other parts of the network. You’ll often see addresses from this range if a device is unable to get an address using DHCP. Then it simply takes an address from this range and uses it to try to at least communicate locally.
use Private Ip range for your DHCP and set Gateway according to that network
03-07-2023
09:07 AM
- last edited on
03-28-2023
11:14 PM
by
Translator
Couple of the things you need to check here on the switch.
- is the switch acting as Layer 2 ? or Layer 3?
- what is the PC gateway ? is this point to 0.1 or 63.254 ?
- how is your config switch port config - connected to router
- can you post
show run
(from switch and Router) (if possible all the device show run)
03-07-2023
09:28 AM
- last edited on
03-28-2023
11:16 PM
by
Translator
03-07-2023
09:41 AM
- last edited on
03-28-2023
11:17 PM
by
Translator
All the routerr configure ip routing
config t
!
ip routing
!
Once this enabled, from Ainee router, try to ping all the destination before you try from PC - is that working ?
and post from all routers :
show ip route
show ip interface brief
show ip arp
show cdp neighbour.
also from PC traceroute to 11.1.1.1
03-07-2023 10:21 AM
i enabled ip routing on all the routers.
Then i tried the ping to all destination from the Aimee router. It worked 5/5 success only on the DNS server. Pinging to PCs also worked but only 4/5 success.
The other destinations did not work at all from the router.
The traceroute from switch to 11.1.1.1 printed the below:
I also attached a document showing the information from the all the routers as requested.
03-07-2023 10:30 AM - edited 03-07-2023 10:31 AM
Pinging to PCs also worked but only 4/5 success. - if you do one more time you get success 5/5 (you see normally intial packet los for the first time).
If you running RIP as IGP, ISP router not anouncing the network 11.1.1.1/30 - so add this network anouncement on ISP router.
Cloud server configured 88.44.22.2/30 ? where is the gateway configured for this ?
ISP router you need to replace 11.1.1.1/30 with 88.44.22.1/30 or reconfigure Cloud server with IP 11.1.1.2/32 gateway 11.1.1.1 to work.
The other destinations did not work at all from the router. - give example which was failed ?
03-07-2023 01:02 PM
Pinging to the PCs from Aimee router now works and also pinging to the DNS server works too, thank you.
About the ISP router, i'm not sure how to make it announce the network 11.1.1.1/30. I tried writing the below but didn't work.
I have reconfigured the cloud server's default gateway and ip address but i noticed the below says link is down? Do you know how to make the link go up?
When pinging from Aimee router it fails in the following:
Also when trying to ping from PC to DNS server, laptop, smartphone, ISP, and cloud server then it says request timed out.
When trying to ping from switch then it fails in following:
03-07-2023
01:31 PM
- last edited on
03-28-2023
11:21 PM
by
Translator
RIP when you issue a command network that might have already taken in to routing table
you can check on Aimee router
show IP route
(you should see 11.0.0.0 supernet there)
cloud router - try rebooting after the IP change. see not sure what image you using as cloud router.
When pinging from Aimee router it fails in the following:
When trying to ping from switch then it fails in following:
03-07-2023
02:49 PM
- last edited on
03-28-2023
11:22 PM
by
Translator
Thank you so much, the pinging now seems to work everywhere except the laptop and smartphone.
For the laptop/smartphone it says 'host not reachable'. I tried to create dhcp server on the Aimee router and tried to bind the laptop/smartphone ip network but when i use the command
show ip dhcp binding
then its not showing anything.
How can I fix this?
03-07-2023 02:54 PM
Good progress, nice pickup like it the way its going
as I mentioned 169.X is Link Local IP address? not sure where this device get IP address from DHCP ? do you have DHCP Server any where ?
are you able to ping AP IP address 10.187.192.1 ?
03-08-2023
02:13 AM
- last edited on
03-28-2023
11:27 PM
by
Translator
The smartphone and laptop are allocated ip addresses by the DHCP.
I have DHCP server in the Aimee router as below:
show ip dhcp pool
show ip dhcp binding
show run
I'm able to ping from switch to router aimee port gig0/2 10.87.255.254 with 5/5 success but I get 0/5 success if trying to ping to the laptop/smartphone.
03-08-2023 02:36 AM
I am not familiar with PT, how the AP configuration to be done on PT
high level you have routing issue and make sure you have right DHCP Scope and right default gateway for the pool for the devices to work.
check this video :
03-08-2023 03:31 AM
169.254.0.0/16 (169.254.0.0 – 169.254.255.255)
These addresses are “link local,” which means packets with these addresses are sent out to the network, but should never be forwarded to other parts of the network. You’ll often see addresses from this range if a device is unable to get an address using DHCP. Then it simply takes an address from this range and uses it to try to at least communicate locally.
use Private Ip range for your DHCP and set Gateway according to that network
03-07-2023 10:01 AM
Hello,
All of your problems involve router Aimee. Show output from commands mentioned by balaji.bandi and show running-config from Aimee router.
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