Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

cannot ping the internet from switch

I have something strange happening and I am trying to figure it out. I have a Juniper ex2200 and I cannot ping any other switches in the network or 8.8.8.8. That is why I cannot telnet to this switch from any other switch. However, I can ping other switches and 8.8.8.8 from my PC which is directly connected to this switch. My PC is getting DHCP from a DHCP server. Any tips will be greatly appreciated.
0
leblanc
Asked:
leblanc
1 Solution
 
Craig BeckCommented:
Can you post the config from the switch please?
0
 
Don JohnstonCommented:
Could be a bad IP address or mask.  Could be that this switch is on a different IP network than the other switches and the default-gateway isn't defined. There are many reasons as to why you're seeing this behavior.  

It would help to see the config of the switch and know what IP addresses the other switches have and what IP address the computer has.
0
 
Otto_NCommented:
Don't let the fact that you can communicate properly from a PC connected to the switch fool you - A switch will do proper frame forwarding based on MAC addresses (i.e. LAN switching, required for the connected PC to communicate to the rest of the network) without any IP connectivity from the switch control plane (used when pinging other network devices from the switch itself).  However, it does tell you that the problem is not a physical connectivity issue or a LAN switching problem, but most likely a control plane setting (such as IP address, the interface being used for management, on what VLAN it's connected, default routing sessions, etc.) on the switch itself.

Now, as Craig and Don requested, if we can get an idea of the subnets involved, and the IP config of the switch, we should be able to point out where the fault lies.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
askincakirCommented:
Hi,

running-config ( run show | display set ) would be good for solution. But at this point you have to check below mentioned points:
1- Vlan created ?
  set vlans VLAN-NAME vlan-id XX
2- Check that vlan is passing from any active port ?
 vlan not assigned to port will not work
3- check the L3 naming of the vlan
 set vlans VLAN-NAME l3-address vlan.XX
4- check the ip address and subnet mask of that vlan
 set interfaces vlan unit XX family inet address AA.BB.CC.DD/24

and the last thing. IF there is inter vlan routing, you will need a default gateway. But Juniper products work as a router by default you will need a default route.

5- set routing-options static routing 0/0 next-hop 192.168.0.1 // this is routers ip address.



for trouble shooting:

run show route / you have to see default route in your routing table
run show interface terse / you have to see up up your interfaces.

Br,
0
 
leblancAccountingAuthor Commented:
I will have to schedule to return on site to get what you have requested. I will be probably the end of next week. Thanks
0
 
leblancAccountingAuthor Commented:
I found out that the trunk from the core to this switch has  a different native vlan. It looks like it is a layer  issue. It is working now. Thx
0
 
leblancAccountingAuthor Commented:
The issue was a misconfiguration of the native vlan.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now