Welcome, Guest. Please login or register.

Recent Posts

Pages: [1] 2 3 ... 10
1
Definition Files / Re: Wanted - Juniper ex4300 definition file
« Last post by healy@bnl.gov on August 11, 2017, 08:22:36 PM »
Oh, actually my colleage John did some serious MIB diving this week and now has port vlan index working.  Theres a change needed for vlan names, (the vlan index is appended with a "+") but that'll come. so for now: (i suspect these are the relevant entries in the .def.  we got 95% of the way there using the 4200 as basis for 4300)

VLnams  1.3.6.1.2.1.17.7.1.4.3.1.1
VLnamx
IFvlan  1.3.6.1.2.1.17.7.1.4.5.1.1
IFvlix  1.3.6.1.2.1.17.1.4.1.2

// sample

Vlan   Name
615   N-10.248.121.0-24+615   
616   N-10.248.122.0-24+616
// for some reason via this oid, the vlid tacked on after "+" (above) !  we have another oid to try asap.

                            IF Name     Alias     Port Vlan Index 
Ethernet - Link up/Admin up   ge-1/0/39         139
Ethernet - Link down/Admin up   ge-1/0/33   EMCS   114
Ethernet - Link down/Admin up   ge-1/0/40         139
Ethernet - Link down/Admin up   ge-1/0/42         32
Ethernet - Link up/Admin up   ge-1/0/44         3124
Ethernet - Link up/Admin up   ge-1/0/46   0463-101   615
Ethernet - Link down/Admin up   ge-1/0/45         32
Ethernet - Link up/Admin up   ge-1/0/47   0463-102   615

John will share the full defgen file, that we've concoted with your help, when he's satisfied he has it where he wants it.

2
Definition Files / Re: Wanted - Juniper ex4300 definition file
« Last post by healy@bnl.gov on August 11, 2017, 02:59:18 PM »
thanks for this tip; We'll try leveraging it!
3
Definition Files / Re: Wanted - Juniper ex4300 definition file
« Last post by rickli on August 10, 2017, 03:47:55 PM »
IFvlix is required if the portindexes in the PVID table differ from the actual IF-indexes. It can't be the same OID as for PVIDs...
4
Discovery / Re: Across WAN discoveries
« Last post by rickli on August 10, 2017, 03:45:55 PM »
In general phones should not be contaced though. What version of NeDi and what kind of phones do you have?
5
Discovery / Re: Across WAN discoveries
« Last post by ascii on August 04, 2017, 10:36:05 AM »
you could use a more detailed filter on the 3rd part.
i use this for example
10.80.108.[1-3]$|10.80.110.[6-9][0-9]
depening on who your network looks like it might help.
6
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« Last post by Hannu Liljemark on August 03, 2017, 01:52:31 PM »
Quote
IfAddresses  ------------------------------------------------------------------
IFIP:No useip policy set, always using discovered IPs
SNMP:Connect 172.18.0.222 public v2 Tout:2s MaxMS:1472 Retry:1 NB:0
IFIP:Walking ifaddress table
ERR :ifAddressTable The requested table is empty or does not exist

DisProtocol  ------------------------------------------------------------------
SNMP:Connect 172.18.0.222 public v2 Tout:7s MaxMS:4095 Retry:1 NB:0
ERR :LLDP nbr The requested table is empty or does not exist

Modules      ------------------------------------------------------------------
SNMP:Connect 172.18.0.222 public v2 Tout:2s MaxMS:1472 Retry:1 NB:0
MOD :Walking module description
ERR :Description The requested table is empty or does not exist

In Defgen check the ARP/ND and try the different methods to see which mechanism your switch supports for IfAddresses.

Same for DisProtocol - can you get any data from the switch if you try CDP, FDP or NDP? You may have to investigate the switch CLI or manuals to see if it supports LLDP/CDP even there.

Modules section is near the bottom of Defgen. I guess the defaults are for devices that support ENTITY-MIB. It may be that Raisecom doesn't support that... yet another thing to investigate.

If there's any publicly available MIB file available from Raisecom or in google, you might want to look at that and see if there's anything useful that could be used to pull the data.

Not all devices have support so you may be left without e.g. module or neighbour data.

I guess you can do this also in NEDIO: go to the OS using ssh, find nedi/sysobj directory and do:

grep Modesc * | awk '{print $2}'|grep -v '^$'|sort -u

Here there's currently 38 different OIDs one can use to pull module descriptions depending on device vendor, model and possible even software version. So, either Raisecom supports one of those, or there's something completely new OID which you need to find, or you can just leave the module section empty so Nedi doesn't try to poll the data if it's not available :)

Br,
Hannu
7
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« Last post by pasubio on August 03, 2017, 12:45:52 PM »
Bingo! Thank you Hannu.
Now I'm able to backup the configuration of my Raisecom devices.

If Remo want add the code, I leave it here below:
Code: [Select]
# Raisecom
$cmd{'RaisecomOS'}{'ropr'} = '[\w.-]+>\s?$';
$cmd{'RaisecomOS'}{'enpr'} = '[\w.-]+#\s?$';
$cmd{'RaisecomOS'}{'enab'} = 'enable';
$cmd{'RaisecomOS'}{'shcf'} = 'show running-config';
$cmd{'RaisecomOS'}{'cfst'} = '\sSystem current configuration:';
$cmd{'RaisecomOS'}{'page'} = 'terminal page-break disable';

Do you have any ideas for point 1 on SNMP discovery?
8
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« Last post by Hannu Liljemark on August 03, 2017, 11:49:27 AM »
Okay, in that case I think the regexp should be modified to something like:

$cmd{'RaisecomOS'}{'ropr'} = '[\w.-]+>\s?$';
$cmd{'RaisecomOS'}{'enpr'} = '[\w.-]+#\s?$';

There's the \s removed since there's no whitespace between the hostname and the > or # part in the prompt.

Try that and then run the config backup again.
9
Definition Files / Re: WANTED - .def files for Raisecom Gazelle series
« Last post by pasubio on August 03, 2017, 09:09:02 AM »
Hi Hannu,

The  login/enable sequence on Raisecom device is the following:
  • Login: <username>
  • Password: <password>
  • HOSTNAME>enable
  • Password: <enablepassword>
  • HOSTNAME#show startup-config
10
Discovery / Across WAN discoveries
« Last post by clakomy on August 03, 2017, 01:51:09 AM »
Need some help NeDi community with WAN discoveries. I just got a new instance running and am able to discover local devices and to go across the WAN, I added core devices in the seedlist. Needless to say, everything works like a charm. The only issue that I'm having is that for whatever reason my netfilters are not working as they should and I'm picking up unwanted phones via CDP. This issue is slowing down the discovery process as we have hundreds of phones that NeDi is attempting to connect to. Below is the configuration that I'm using..

The execution is nedi.pl -po

Filters
netfilter       10.130.50|192.168.168|172.30.127|172.30.1|172.30.0|10.130.230
netfilter       ^(?!172.30.130).*$|^(?!172.30.131).*$|^(?!10.130.80).*$

Any insight is highly appreciated! The second filter is my attempt to ignore the phones.

-Casrlos
Pages: [1] 2 3 ... 10