npm not working?

Question

npm

npm and all other commands do not work, such an error:
The name "npm" is not recognized as a cmdlet name

WHAT TO DO

Answer 1

WHAT TO DO

Install nodejs.

Answer 2

What a creative... a ring, yes, on L3...
Your task (as you formulated it) has no solution, because all reservation of routes on L3 is carried out using dynamic routing (well, that's why it's dynamic). Changing the route with static routing is nonsense.
You may be interested in one of the dynamic routing protocols, for example, OSPF - it reacts quite quickly to network topology changes and is easy to start under Linux and can start under Windows.

Answer 3

Tell me which way to dig? Metrics?

Yes, metrics are larger for backup routes.
Example for windows machine, main routes:

route add 192.168.102.0 mask 255.255.255.0 192.168.3.2 metric 1
route add 192.168.103.0 mask 255.255.255.0 192.168.3.2 metric 1

backup routes:

route add 192.168.102.0 mask 255.255.255.0 192.168.1.1 metric 100
route add 192.168.103.0 mask 255.255.255.0 192.168.1.1 metric 100

For other cars it's the same. The point is that when the link on the interface disappears, the corresponding route, as a rule, is deleted from the routing table (I just checked it on win7). Keep in mind that if two links out of three fail, you will get a routing loop (but these are trifles compared to the unavailability of part of the network). Well, other disadvantages of static routing will also appear (the inability to track the inoperability of the next hop except through the state of the interface, etc.)

Packets addressed "out" must go through the GW.

Here you can do so. On the linux server (in the center of the picture), raise the loopback interface. On the other two machines, set the default routes through it. They also have two routes directly to it (main and reserve). On the main linux server, set the default route to the Internet.

Answer 4

maybe you need STP?

Answer 5

If you want to sort it out with statics - read thoughtfully habrahabr.ru/post/140552 only there statics are like a saddle for a cow, they don’t climb, you can still conjure with metrics or write multiple routing tables, there are many options, but in a real network your eyes will be stretched on your ass for such a crutch , because a person who came to your network to rake tons of routes with handles then, oh, how he won’t like it, schA router 3, imagine it will be 5 or 10, how will you scale this horror? So the choice is OSPF / IS-IS / RIP and do not rivet bicycles.