Replies: 3 comments 1 reply
-
A small update and progress on this. I did some manual reading and enabled Napalm logs. The result is this:
So it seems that the napalm driver name I have set in Peering Manager is not right. But the driver name I use in Python is 'sros' so I need to work out why this is not working. |
Beta Was this translation helpful? Give feedback.
-
What is odd is that in the napalm-sros install README, it says the driver is called 'sros' - and this driver name works fine in Python:
|
Beta Was this translation helpful? Give feedback.
-
Are you sure that the |
Beta Was this translation helpful? Give feedback.
-
Sorry if this isnt the right place to ask for help, but I thought this would be worth a try:
I have two routers configured in Peering Manager - one is Junos, the other is Nokia SROS. I can successfully connect to the Junos device when I click ping in the devices screen, but cannot connect to the SROS device.
I have followed the instructions here for installing the Napalm driver for SROS, and I can successfully connect to the Nokia device from Python.
I have Peering Manager installed, checked out to release v1.7.4.
I have added the routers under Devices | Routers - one has platform = junos, the other has platform = sros.
In configuration.py I have a Napalm user, password and the following args set:
NAPALM_ARGS = {'port':22}
. This is necessary because our management firewall only permits port 22.I have created an 'sros' platform in the GUI, but the password algorithm field only presents Juniper or Cisco options. So in the device, I have unchecked the 'encrypt passwords' field.
From the underlying linux host where Peering Manager is installed, I can ssh to both devices ok. I can also ssh with '-s netconf' and I get a netconf response from both devices. So I am confident there is no firewall issue between the Peering Manager host and the device.
However, when I click the ping button on the SROS device in Peering Manager, I get 'unable to connect to the router'.
If I run tcpdump -i eth0 host I see no packets going out to the SROS device at all. If I do the same for the Junos device, tcpdump captures packets destined to port 22. So it seems as though Napalm can connect in native python, but Peering Manager cannot - it doesn't even send any packets out.
What is the best way to debug this? The logs directory does not seem to show any information other than a PeeringDB log file.
Any help would be much appreciated!
Andy
Beta Was this translation helpful? Give feedback.
All reactions