When deploying APEs or other SW nodes to an NPM installation, if there are firewalls and ACL routers inbetween, it is helpful to KNOW before you TRY whether the network portion has been set up prior.
Utility should:
- Ask what node you are running it on (NPM, MPE, APE, AWS, etc.) (should be run on both MPE (NPM in this case) as well as the outlying SW node (anticipated node to add)
- if on MPE, state MPE, AND the IP/hostname of the remote host
- if APE, AWS, etc., select that type, AND MPE IP/hostname
- Then it should run through the list of ports/protocols to test them to make sure things appear to be correct
- Output should demonstrate what passed and what didn't.
we have deployments that are very complicated, and communicating with the network team what our needs are is very clugy. However, if this utility could make it eaiser: MPE → Node, these ports/protocols, Node → MPE, these ports/protocols it would simplify things before we start up the installation—which can sometimes take up to 30 minutes to fail on a port.
