4/19/2023 0 Comments Ping console command![]() usr/bin/ntpq: write to localhost failed: No route to run show system uptime ![]() usr/bin/ntpq: configured source-address in ntp.conf 1.1.1.1 invalid. System Uptime shows that it is currently using the Local Clock as it's time source. However, the log messages show that it was able to pull NTP from the specified server, but the NTP status is still shows that it failed and "no route to host". I have done as you suggested but it still doesn't appear to work. Safesys-vr.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Safesys-vr.inet.0: 12 destinations, 12 routes (12 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both Inet.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden) Route 0.0.0.0/0 next-table show routing-options ![]() I can only ping my gateway if I include the "bypass-routing" option to skip the routing show routing-instances I still cannot ping from the SRX console to anything on the web. So I decided to test by removing the public interface out of the routing instance and back into the default instance. With the routing instance I found some oddities such as ntp or dns not working on the box. So I guess I am not completely out of the woods yet. Node Priority Status Preempt Manual Monitor-failures ![]() LB Loopback monitoring MB Mbuf monitoringĬF Config Sync monitoring RE Relinquish monitoring GR GRES monitoring HW Hardware monitoring Ge-7/0/2 weight show chassis cluster statusĬS Cold Sync monitoring FL Fabric Connection monitoring System-services run show configuration chassis cluster Route 0.0.0.0/0 next-hop show configuration show configuration security zones security-zone untrust If I issue the command "ping bypass-routing interface reth0.0 address" I can ping the gatewayĭescription "WAN Uplink pair 1 of 2 - partner ge-7/0/0" ĭescription "Trust Interfaces Uplink pair 1 of 2 - partner xe-7/0/17" ĭescription "WAN Uplink pair 2 of 2 - partner ge-0/0/0" ĭescription "Trust Interfaces Uplink pair 2 of 2 - partner xe-0/0/17" ĭescription "WAN Uplink - ge-0/0/0 & ge-7/0/0" ĭescription "Trust Interfaces - xe-0/0/17 & xe-7/0/17" Īddress show configuration routing-instances If I just issue the ping command to my gateway, it says "ping: sendto: No route to host" There is a virtual routing instance to split up mgmt interface routing and everything else because the mgmt interface is configured in the same subnet as a sub interface in another zone. Any traffic from the trust zone to untrust works as intended. I am able to ping,ssh to the ip address assigned to my untrust interface. From the console I cannot ping anything through my public interface such as 8.8.8.8. I have weird communication issue on an SRX1500 cluster running Junos 18.1R2.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |