Register your Network Actor using the Director

There are two ways to register your Network Actors to the Director:

• Register a Push Mode Actor
• Register a Pull Mode Actor

Register a Push Mode Actor to the Director

Follow one of the sets of steps, depending on how you're registering your Actor: 

Pending Actor

1. Launch the Director and sign in.
2. Select Environment > Actors.
3. Identify the Actor in the Pending Actors table, expand the Actions menu and click Connect to initiate a Director-to-Actor registration.
   

   Actor Action menu and Connect Actor form

4. Enter the Actor's FQDN or IP address.

5. (Optional) Clear the Validate FQDN checkbox.

   Clearing this checkbox allows you to register push Actors when DNS resolution is not possible due to your network setup.

6. Click Connect.
   • The message "Actor 'actor name' is being registered and will update automatically below" displays.
   • Once registration is complete, the Actor moves from the Pending Actors table to the Network Actors list.

Bulk Registration Tokens

1. Launch the Director and sign in.
2. Select Environment > Actors.
3. Identify the Bulk Registration Token you want to use to register the Actor, expand the Actions menu and click Register Push.
4. Populate the Register Push Actor form and then click Submit.
   • Name: The default name of the Actor is the name of the token with a numeral appended.
   • Description: Short description of the Actor
   • Mgmt IP or FQDN: The IP address or fully qualified domain name of the Actor.
   • Actor Time: Select Use System Time or Use NTP Server(s).
   • Optional. Select Enable Network Keepalive.

5. The message "Actor 'actor name' is being registered and will update automatically below" displays.

   Once registration is complete, the Actor moves from the Pending section under the bulk token to the Network Actors list.

Register a Pull Mode Actor by using the command line

1. Connect to the Actor by using SSH.
2. Using an elevated command prompt, navigate to the scripts directory and run vregister.

   sudo /opt/apps/verodin/node/node/scripts/vregister

   When an unexpected response is received, a message is displayed and a response.txt file is created.
   If you need to see Tap Adapters when selecting the interfaces, add the argument --include-tap-adapters when running vregister.
3. Enter the Director's FQDN or IP address.

4. Enter the appropriate code from the Director:

   • registration code in the Pending Actor's table
   • bulk registration token code in the Bulk Registration Tokens table
5. If prompted, specify if you want to verify the Director TLS Certificate [yes|no].

   When set to Yes, it'll verify the certificate during registration and then every time the Actor reaches out to the Director (HTTPS requests).This prompt only appears for Pull Actors.

   Actors can verify TLS certs signed by public CAs, but not private CAs.
6. If desired, add a proxy.
   1. Enter yes.
   2. Enter the Proxy IP and Proxy Port.
   3. If there is an account associated with the proxy, enter the account info.

      The command line states "Successfully validated with Verodin Director" and the Director's Actor listing moves the Actor from the Pending Actors list to the Actors list.

Example of registration steps using vregister

[nodeone@actor ~]$ sudo vregister

 - Verodin Registration Script - 

Enter IP Address or Hostname of Verodin Director: 172.16.39.193

Enter Code from Verodin Director: XXXX-XXXX-XXXX

Use Proxy To Connect To Verodin Director (yes|no): yes

Enter Proxy IP Address: 172.16.71.234

Enter Proxy Port: 443

Enter Proxy Username (blank for none): verodinuser

Enter Proxy Password: