agant cannot connect to sysdb #25

athos0212 · 2017-05-17T02:06:13Z

veos-log.txt
in veos, example helloWorld can not connect to sysdb, catting log shows:
waiting for connection to Sysdb .............................................................

ruferp · 2017-05-17T05:45:09Z

This most probably means there is no "mount profile" for the HelloWorld application in /usr/lib/SysdbMountProfiles.
Mount profiles are required since release 4.16.x.
A mount profile tells the system what to mount from Sysdb for that application.
Each manager that the application uses requires a corresponding line in the application's profile. The first line of the profile identifies the application the profile is for, the filename itself is irrelevant (just needs to be unique).
There is a brute-force profile that can be used as a guide at /usr/lib/SysdbMountProfiles/EosSdkAll. Its first line needs to be adapted according to the application's binary name: replace the "EosSdk" part of the first line with the basename of your binary. Then optionally remove the lines from the managers your application does not use (for performance reasons).

Here is a copy/paste way to produce that profile on the bash prompt of the EOS switch:
but first change the first line to match your application's executable (see "myApp" below)

bin=/usr/bin/myApp # <<<=== adapt this line
name=$(basename $bin)
dest=/usr/lib/SysdbMountProfiles/$name
source="/usr/lib/SysdbMountProfiles/EosSdkAll"
cat $source | sed "1s/agentName[ ]:./agentName:${name}-%sliceId/" > /tmp/tmp_$name
delta=$(cmp /tmp/tmp_$name $source)
if [ "$?" = "0" ]; then
echo "Error: something is wrong"
else
sudo mv /tmp/tmp_$name $dest
fi

The mount profile will be /usr/lib/SysdbMountProfiles/myApp

You will need to re-install that file to /usr/libSysdbMountProfiles after a reboot. This can be done via a "on-boot" script, or by packaging that profile into an RPM and configure EOS to boot with it (that's the best route if your application is already installed via an RPM).

The on-boot script route looks like this:

switch(config)# event-handler
switch(config-handler)# trigger on-boot
switch(config-handler)# action bash /mnt/flash/.sh

where /mnt/flash/.sh is a script that copies (installs) the profile from /mnt/flash to /usr/lib/SysdbMountProfiles.

The RPM route looks like this (after scp-ing the RPM to /tmp on the switch):

switch(config)# copy file:/tmp/myApp.i686.rpm extension:
switch(config)# extension myApp.i686.rpm
switch(config)# copy installed-extensions boot-extensions

The second line installs the RPM, the third one makes sure it will get re-installed after a reboot.

athos0212 · 2017-05-17T06:36:14Z

It works. Thank you for the quick response.

ruferp · 2017-05-17T07:53:36Z

slight correction, the stars did not survive the copy/paste into this wiki, added them as STAR below:

cat $source | sed "1s/agentName[ ]STAR:.STAR/agentName:${name}-%sliceId/" > /tmp/tmp_$name

N.B. this would work too, but would not detect any errors in case the template file is not as expected:

cat $source | sed "1s/.STAR/agentName:${name}-%sliceId/" > /tmp/tmp_$name

chency · 2017-10-09T11:41:22Z

@ruferp It seems not work on my VM(vEOS-lab-4.18.1F.vmdk).Is there anything missing?
binary file:/mnt/flash/HelloWorld.py
(copy from EosSdk/examples/HelloWorld.py)

The mount profile:/mnt/flash/HelloWorld

bin=/mnt/flash/HelloWorld.py
name=$(basename $bin)
dest=/usr/lib/SysdbMountProfiles/$name
source="/usr/lib/SysdbMountProfiles/EosSdkAll"
cat $source | sed "1s/agentName[ ]*:.*/agentName:${name}-%sliceId/" > /tmp/tmp_$name
delta=$(cmp /tmp/tmp_$name $source)
if [ "$?" = "0" ]; then
  echo "Error: something is wrong"
else
  sudo mv /tmp/tmp_$name $dest
fi

The on-boot script:/mnt/flash/HelloWorld-install.sh

#!/bin/bash
echo "Start HelloWorld-install bash"
sudo cp /mnt/flash/HelloWorld /usr/lib/SysdbMountProfiles/HelloWorld.py

ruferp · 2017-10-09T21:56:14Z

don't use extensions like .py, just call you binary HelloWorld.
The .py will mess up stuff at multiple levels in our code!

And the .py is quite irrelevant: binaries usually don't have extensions, although I do see a few in linux, but that's really an exception:

prufer@ubuntu:~/cross/gcc/gcc-4.9.2$ ls /usr/bin  | grep ".*\.[^0-9]" | sed 's/.*\.//' | sort | uniq -c | sort -n -r | head
      6 py
      4 pl
      2 sh
      2 gold
      2 bfd
      1 yacc
      1 x11
      1 wrapper
      1 ul
      1 tiny
prufer@ubuntu:~/cross/gcc/gcc-4.9.2$ ls /usr/bin/*.py
/usr/bin/miniterm.py    /usr/bin/pildriver.py  /usr/bin/pilfont.py
/usr/bin/pilconvert.py  /usr/bin/pilfile.py    /usr/bin/pilprint.py
prufer@ubuntu:~/cross/gcc/gcc-4.9.2$ 
prufer@ubuntu:~/cross/gcc/gcc-4.9.2$ ls /usr/bin | wc
   1496    1496   15691
prufer@ubuntu:~/cross/gcc/gcc-4.9.2$

chency · 2017-10-10T02:07:32Z

Ah~~~! It isn't a binary file. A python file copy from EosSdk/examples/HelloWorld.py!
Even if I change the file to HelloWorld,it still in waitting for connet sysdb.....
Only work for binary file?

ruferp · 2017-10-10T02:23:02Z

binary or py makes no difference, as far as mount profile is concerned.
Have you re-generated the mount profile after the name change, or at least edited the old one to remove the .py in the first line?

chency · 2017-10-10T02:38:04Z

I have done it both,but it still no work.

chency · 2017-10-10T02:50:04Z

The log file:
HelloWorld-HelloWorldAgent-2858.zip

ruferp · 2017-10-10T03:04:33Z

This:

bin=/mnt/flash/HelloWorld.py
name=$(basename $bin)
dest=/usr/lib/SysdbMountProfiles/$name
source="/usr/lib/SysdbMountProfiles/EosSdkAll"
cat $source | sed "1s/agentName[ ]*:.*/agentName:${name}-%sliceId/" > /tmp/tmp_$name
delta=$(cmp /tmp/tmp_$name $source)
if [ "$?" = "0" ]; then
  echo "Error: something is wrong"
else
  sudo mv /tmp/tmp_$name $dest
fi

is not supposed to be the mount profile itself, but how to create it!
Try:
bash
sudo su
source /usr/lib/libSysdbMountProfiles/HelloWord
exit
(I guess the bash script can overwrite itself since that's the last thing it does)

chency · 2017-10-10T03:54:42Z

Still not word, maybe the Sysdb not running!
After I reboot the vm(have added source cmd in my on-boot script), the HelloWorld mount file in /usr/lib/SysdbMountProfiles/ changed to

agentName:HelloWorld-%sliceId

Include: EosSdk_acl.include
Include: EosSdk_agent.include
Include: EosSdk_class_map.include
Include: EosSdk_decap_group.include
Include: EosSdk_directflow.include
Include: EosSdk_eth_intf.include
Include: EosSdk_eth_lag_intf.include
Include: EosSdk_eth_phy_intf.include
Include: EosSdk_fib.include
Include: EosSdk_hardware_table.include
Include: EosSdk_intf.include
Include: EosSdk_IntfMgrHelper.include
Include: EosSdk_ip_intf.include
Include: EosSdk_ip_route.include
Include: EosSdk_lldp.include
Include: EosSdk_mac_table.include
Include: EosSdk_mlag.include
Include: EosSdk_mpls_route.include
Include: EosSdk_neighbor_table.include
Include: EosSdk_nexthop_group.include
Include: EosSdk_policy_map.include
Include: EosSdk_subintf.include
Include: EosSdk_system.include
Include: EosSdk_vrf.include
Include: EosSdk_GOpenFlow.include
Include: EosSdk_bfd_session.include

Email: [email protected]

ruferp · 2017-10-10T04:21:14Z

I did not see any EOS switch window there

chency · 2017-10-10T04:52:29Z

I tested it on the VMware Workstation named Fedora 4_18(baseed on vEOS-lab-4.18.1F.vmdk).
Only work on real EOS switch?

ruferp · 2017-10-10T05:42:01Z

It looks like it is working now.

chency · 2017-10-10T07:58:26Z

@ruferp Thank you for the quick response and the remote assistance.

Run the HelloWorld.py on VM

Copy python file (EosSdk/examples/HelloWorld.py) to /mnt/flash.
Rename with HelloWorld(/mnt/flash/HelloWorld)
Create mount file(/mnt/flash/HelloWorld.profile)

bin=/mnt/flash/HelloWorld
name=$(basename $bin)
dest=/usr/lib/SysdbMountProfiles/$name
source="/usr/lib/SysdbMountProfiles/EosSdkAll"
cat $source | sed "1s/agentName[ ]*:.*/agentName:${name}-%sliceId/" > /tmp/tmp_$name
delta=$(cmp /tmp/tmp_$name $source)
if [ "$?" = "0" ]; then
  echo "Error: something is wrong"
else
  sudo mv /tmp/tmp_$name $dest
fi

Create on-boot script(/mnt/flash/HelloWorld-install.sh)

#!/bin/bash
echo "Start HelloWorld-install bash"
sudo /mnt/flash/HelloWorld.profile

Persist your Agent

v-EOS#conf
v-EOS(config)#event-handler HelloWorld-install 
v-EOS(config-handler-HelloWorld-install)#trigger on-boot
v-EOS(config-handler-HelloWorld-install)#action bash /mnt/flash/HelloWorld-install.sh
v-EOS(config-handler-HelloWorld-install)#end
v-EOS#write
Copy completed successfully.
v-EOS#

A litter problem comes out after I reboot the VM.
It seems the HelloWorldAgent is started before the on-boot script has been excuted.
After the VM is successed reboot, the HelloWorldAgent auto-run...but waitting for connet Sysdb....
Then I shut it down, and restart it,it work again.

    v-EOS>en
    v-EOS#conf
    v-EOS(config)#daemon HelloWorldAgent 
    v-EOS(config-daemon-HelloWorldAgent)#show daemon 
    Process: HelloWorldAgent (running)
    No configuration options stored.

    No status data stored.

    v-EOS(config-daemon-HelloWorldAgent)#shutdown
    v-EOS(config-daemon-HelloWorldAgent)#exec /mnt/flash/HelloWorld
    v-EOS(config-daemon-HelloWorldAgent)#no shutdown
    This is an EosSdk application
    Full agent name is 'HelloWorld-HelloWorldAgent'
    v-EOS(config-daemon-HelloWorldAgent)#show daemon
    Agent: HelloWorldAgent (running)
    No configuration options stored.

    Status:
    Data           Value                       
    -------------- --------------------------- 
    greeting       Welcome! What is your name?

ruferp · 2017-10-10T08:16:29Z

Yes, that's a known problem with the on-boot triggers: indeed, your agent may get started before the on-boot script runs. After 10 minutes the agent will give up looking for sysdb and restart, at which point it will find a mount-profile and thus can talk to sysdb.
That's why it is better to create an 'extension' that contains your agent and its profiles (and other files it may need), because those get installed before any agent gets started (EventMgr is the agent that will react to the on-boot configuration, and if he does this after your agent has started, then you are toast). I think there is also an rc file that can be put into /mnt/flash that get executed right after the EOS.swi got extracted, but I'm not sure about that (and/or how it has to be named).

ruferp · 2017-10-11T01:22:59Z

You can use an rc script that gets run after the EOS.swi image was extracted and before the agents run (instead of the on-boot script that runs too late to create a mount-profile for your agent that is configured in the startup-config).

Here is an example/illustration (where you see how to call the script, namely rc.eos):

$ ssh [email protected]
Password:
vEOS1>en
vEOS1#bash

Arista Networks EOS shell

[admin@vEOS1 ~]$ cat /mnt/flash/rc.eos
#!/bin/bash
outf=/tmp/rc.eos.out
whoami > $outf
ls /usr/bin/Aaa.sh >> $outf
ps -ef | grep Sysdb >> $outf
[admin@vEOS1 ~]$ cat /tmp/rc.eos.out
root
/usr/bin/Aaa.sh  <=== EOS.swi was extracted, but Sysdb is not yet running
[admin@vEOS1 ~]$

ruferp · 2017-10-11T04:56:40Z

by the way, to set the root password (so you can ssh into the vm as root), don't use the "username secret " command, use this command instead:

aaa root secret 0 <password>

That will give you a bash shell inside the VM when you ssh; to get a Cli, just run "Cli -A" from bash.
Any user created through the username command will give you a Cli shell if you ssh in as them.
The username 'admin' is created without password, so if you want to be able to ssh in as admin without needed a password, then run this command first:

aaa authentication policy local allow-nopassword-remote-login

If somebody uses VMware fusion: this is how to have the vm get an ip address: dhclient ma1 (from bash), then use ifconfig to find the ip address.

tsuna assigned daltonb-arista May 17, 2017

athos0212 closed this as completed May 17, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

agant cannot connect to sysdb #25

agant cannot connect to sysdb #25

athos0212 commented May 17, 2017 •

edited

Loading

ruferp commented May 17, 2017

athos0212 commented May 17, 2017

ruferp commented May 17, 2017

chency commented Oct 9, 2017 •

edited

Loading

ruferp commented Oct 9, 2017 •

edited by tsuna

Loading

chency commented Oct 10, 2017

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017

chency commented Oct 10, 2017

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017 •

edited

Loading

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017 •

edited

Loading

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017

ruferp commented Oct 10, 2017

ruferp commented Oct 11, 2017 •

edited

Loading

ruferp commented Oct 11, 2017 •

edited

Loading

agant cannot connect to sysdb #25

agant cannot connect to sysdb #25

Comments

athos0212 commented May 17, 2017 • edited Loading

ruferp commented May 17, 2017

athos0212 commented May 17, 2017

ruferp commented May 17, 2017

chency commented Oct 9, 2017 • edited Loading

ruferp commented Oct 9, 2017 • edited by tsuna Loading

chency commented Oct 10, 2017

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017

chency commented Oct 10, 2017

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017 • edited Loading

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017 • edited Loading

ruferp commented Oct 10, 2017

chency commented Oct 10, 2017

Run the HelloWorld.py on VM

ruferp commented Oct 10, 2017

ruferp commented Oct 11, 2017 • edited Loading

ruferp commented Oct 11, 2017 • edited Loading

athos0212 commented May 17, 2017 •

edited

Loading

chency commented Oct 9, 2017 •

edited

Loading

ruferp commented Oct 9, 2017 •

edited by tsuna

Loading

chency commented Oct 10, 2017 •

edited

Loading

chency commented Oct 10, 2017 •

edited

Loading

ruferp commented Oct 11, 2017 •

edited

Loading

ruferp commented Oct 11, 2017 •

edited

Loading