08-12-2025 01:18 AM - edited 08-15-2025 02:07 AM
08-12-2025 01:42 AM
Hello @nrodd69
The serial WAN link between building A and C is down! Since both ends are currently down/down, there’s a possible clocking issue, not just an IP config issue... Double check if only one side provide the clock signal. Only the DCE end needs to provide clocking with the clock rate command.
08-12-2025 01:41 AM
hello @nrodd69 that is a sick lab, i love it/ Alright, It looks like ur WAN link between Admin/Building A and Building C is down because the serial interfaces on both ends (Building A S0/0/1 and Building C S0/0/0) are showing down/down. This usually means there’s either no proper clocking on the DCE side, incorrect encapsulation, or the serial connection isn’t actually linked in Packet Tracer.
I will troubleshoot ur topology after 2 or 3 hours, and will paste here the solution...
Till then, grab some coffee, and enjoy....
-Enes
08-12-2025 02:04 AM
08-12-2025 03:46 AM
Hello again, I already checked the clocking and confirmed that the Building C Serial0/0/0 is DCE and has a clock rate set (I even tried setting clock rate 64000 manually).
Physically, the Serial 0/0/1 on Admin is connected to cloud port 0, and Serial 0/0/0 on SABM is connected to cloud port 1. The cloud device is powered on.
But the interface rotocols on both side still show as down.
Could his be a problem with how im connecting the cloud device? or is there something else I should check?
Thanks in advance for any tips!
08-12-2025 01:42 AM
Hello @nrodd69
The serial WAN link between building A and C is down! Since both ends are currently down/down, there’s a possible clocking issue, not just an IP config issue... Double check if only one side provide the clock signal. Only the DCE end needs to provide clocking with the clock rate command.
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