Core together to exchange VLAN was 10, access server-side H3C48 mouth switch port access VLAN 10, 16 core vlan10 IP for 172.26.20.1 mask 255.255.255.0, PC, even 16 IP match 172.26.20.244 manual, why not on the net

CodePudding user response:

Can pass 172.26.20.1 no, did you PC gateway Settings

CodePudding user response:

The building Lord, you can have a look at your topology?

CodePudding user response:

You said this is too general, start from the simplest, first check your core, convergence, access, whether have vlan10, then determine the type of interface is correct, and switch to see if there is a routing and configuration is correct, your PC network configuration is also very important, of course, specific circumstances or to see your network topology.

CodePudding user response:

The Internet is a network connected to the Internet through a router, you ping the first switch interface IP address, check whether the road connection, usually pay attention to the gateway host address is 172.26.20.1? Right, then use the route command to view the routing table

CodePudding user response:

First, check whether the IP is the core in the vlan configuration
Then look at attachment, if the normal connection, every level switches have cascading mouth for trunk, increase vlan10, each level can also open the access port, but the attachment must be to a port on the vlan10 links, these two can pass

CodePudding user response:

Very good a praise

CodePudding user response:

The entire issue to topology and configuration scripts, look.

CodePudding user response:

Whether the interface type of problem

CodePudding user response:

Starting from the physical layer, look at the network cable is 4 or 6 core, four core correlates with the 6 core gigabit, second, to see if the STP is normal, trunk whether to allow vlan10 through mouth, the third layer, terminal gateway is properly configured and core routing is normal,

CodePudding user response:

With the method of the trace route where can see first,