Is there anyway to reboot the radio the above radio trough snmpset ?
What else can I do with snmpset and where do I get the mibs ?
Thanks
I was able to find the target MIB file for you. You can download it at: http://netmechanica.com/MIBs/SIKLU-MIB.mib
However, according to MIB file definitions the device does not support remote reboot.
I was able to compile the MIB file using NetDecision MIB Manager.
Related
I'm trying to install centos 7.9 on an old HP DL580 using custom cciss driver package loaded during start-up with the DD paramater to get interactive driver update.
that worked well an I see my CCISS drives BUT
if I do a netinstall I can't create a repo because anaconda tries to save the repo on my usbstick .
in /tmp/packaging.log I find:
[Errno 14] curl#37 - "couldn't open file /run/install/DD-1/repodata/repomd.xml"
so curl tries to save it on my usb stick
how do I tell initrd where to store the repo data?
or any other hits?
many thanks
okay, as a workaround don't use USB sticks but specify the repo in the inst.dd
but still I see the issue in using a USB-stick
inst.dd=https://mirror.rackspace.com/elrepo/elrepo/el7/x86_64/RPMS/kmod-cciss-3.6.26-8.el7_8.elrepo.x86_64.rpm
I am using Ubuntu 18.04, woeUsb, 15 GB usb3 Stick, windows 10 64Bit ISO to create bootable device. I found few tutorials how to do it, but I still get error.
Installation failed!
Exit code: 256
Log:
WoeUSB v##WOEUSB_VERSION##
============================== Mounting source filesystem... Wiping all existing partition table and filesystem signatures in /dev/sda...
wipefs: error: /dev/sda: probing initialization failed: No medium
found The command "wipefs --all "${target_device}"" failed with exit
status "1", program is prematurely aborted Unmounting and removing
"/media/woeusb_source_1532252869_8362"... You may now safely detach
the target device
I tried to format my USB several times but nothing worked. I used FAT32 format. Should I first convert it to NTFS?
I have the same issue and found the solution by unmounting USB drive in this way,
Go to the Disks and select your USB drive from the left side menu, and click on the icon shown in the below image to unmount USB.
The command line version of the tool works better in my experience:
woeusb --device Win10_1909_English_x64.iso /dev/sdX --target-filesystem NTFS
/dev/sdX might be different on your system such as sda sdb ..., make sure to check the device path using gparted or fdisk.
Make sure to set the filesystem to NTFS with --target-filesystem NTFS as FAT32 doesn't support large files.
I found that you have to run the software with sudo because it requires the use of gparted. If you don't do this it won't succeed and exit. I suspect this is your problem. I had a similar problem.
I had the same problem but after surfing internet I found something like this: **
sudo woeusb --device image.iso /dev/sdb --tgt-fs NTFS --verbose
**. So in the command image.iso is the OS you downloaded(or the path to it), while the /dev... is the USB device and type of format(NTFS). Just copy the command, change image.iso to the path of your image.iso and change the /dev/sdb to the name of your USB device and make sure you are connected to internet because when I ran the command it seems it communicated with GitHub. Good luck I hope this will help if you haven't found any answer.
There is no need to use any third party tool in the Windows operating system to create a bootable USB. Follow the below commands:
1. Plug your USB drive
2. Open Command Prompt
3. Type: diskpart .
4. Type list volume (this will show your drives)
5. Type sel vol h (h can be replaced with ur usb volume, can be anything g, h, i)
6. Type active
7. It will make your USB active, copy and paste windows files inside it.
I installed net-snmp on centos 7 with yum :
yum install net-snmp
I configured the /etc/snmp/snmpd.conf file to see all the oid tree :
#Make at least snmpwalk -v 1 localhost -c public system fast again.
# name incl/excl subtree mask(optional)
#view systemview included .1.3.6.1.2.1.1
#view systemview included .1.3.6.1.2.1.25.1.1
view all included .1 80
when i tap the snmpwalk command :
snmpwalk -v 1 -c public 127.0.0.1
it works , but i want to search a specefic oid which is :
snmpwalk -v 1 -c public 127.0.0.1 iso.3.6.1.4.1.8711.101.28.1.2.7.20.40.30.10
the snmpwalk doesn't return a result .
how can i add this oid to the oid tree ??
Looking into IANA's PEN registry you see that the private enterprise number 8711 is registered to 'THALES Broadcast & Multimedia'. You installed net-snmpd which doesn't have a subagent registered under this number in it's default configuration.
Since this company seems to be selling IPTV products (I only did a very quick search, no real research) I assume you actually want to query some parameters on the device itself; you don't need a snmp-daemon running on a different machine. Try querying the real target machine instead.
However, if your vendor really provided you with a subagent which shall be installed on your Linux machine, you need to tell net-snmpd to pass all queries to the vendor OID 1.3.6.1.4.1.8711 to this agent. The configuration methodes depends on the type of subagent; if it's AgentX extension configure the master agentx statement and start your subagent after restarting snmpd. If it's just a simple script, you should read up on the EXTENDING AGENT FUNCTIONALITY section in the manual. There are many ways to accomplish this.
Extra-note: The OID you're querying is already deep down the vendor tree. Many subtrees are dynamic and depend on the actual hardware configuration. Try an snmpwalk higher up the tree. I suggest starting directly at 1.3.6.1.4.1.8711. However, it won't work on that certain net-snmp your configured anyway.
I am running xillinux on my microzed board. I need to define a new serial port on the board using vivado. I was able to add this to the IP core and the device is ready. But,how do I make this port visible on ubuntu (xillinux) like ttyPS0. DO I need to add this port to the device tree and generate the dtb file and boot.bin file ? IF so, how do I modify the device tree ?
1.) Now again, instead of vivado if I use ISE, then would I be able to update the device tree source file in the ISE software itself and generate the device tree .dtb file ? If so, where can I find and edit this dts file ?
2.) And for building the new boot.bin file in ISE, I can use http://xillybus.com/downloads/u-boot...ux-1.3.elf.zip for the microzed or can I use the bin file for microzed from xillybus.com/downloads/xillin...rozed-1.3c.zip ?
3.) Even after using the ISE and creating the new .dtb (if possible in ISE), do I have to edit dtc files on the xillinux OS in the micozed board ?
4.) If I need to follow step 3 above to get everything working, based on this link, http://xillybus.com/tutorials/device-tree-zynq-1
I can go only upto to cd /usr/src/kernels/3.12.0-xillinux-1.3/scripts/dtc/
If I type cd /dtc again, it says dtc not a directory.
How do I access the device tree script and add the address mapping to the bus in the peripheral section ?
How do I compile this and make the new device tree start on every boot ?
I can go only upto to cd
/usr/src/kernels/3.12.0-xillinux-1.3/scripts/dtc/
If I type cd /dtc again, it says dtc not a directory.
Sure, /usr/src/kernels/3.12.0-xillinux-1.3/scripts/dtc/dtc is a binary executable. It has been compiled with the Linux kernel. It is the Device Tree Compiler (thus its name) that turns a Device Tree Source foo.dts into a binary Device Tree Blob foo.dtb. The DTS is a text file describing the available hardware and how to access it. The DTB is the same information but in a binary format that the Linux kernel parses at boot time to discover the hardware it is running on and to attach software drivers to the hardware peripherals (among other things).
So, to use the dtc just add /usr/src/kernels/3.12.0-xillinux-1.3/scripts/dtc to your path and use it:
$ export PATH=$PATH:/usr/src/kernels/3.12.0-xillinux-1.3/scripts/dtc
$ dtc -I dts -O dtb -o foo.dtb foo.dts
i did ulimit -c unlimited / some number
proc... core_pattern is core
and my rootfs and the apps are all debugversion [ not the kernel though]
any idea why iam unable to get coredumps on kill -SIGABRT/SEGV pid
thanks
Furion.
Can you try to create the core using gdb as follows?
$ gdb --pid=1234
(gdb) gcore
Saved corefile core.1234
(gdb) detatch
gdb doesn't care about the settings.
If you are wondering what is detach.
Since you have attached the process to gdb, detatch it using gdb control using detatch command
Check to see if core dumps are enabled for your kernel:
CONFIG_ELF_CORE=y
Here's some documentation of the configuration item.
Ensure the current directory (getcwd()) of the process is writable by the process and contains enough space to hold the core dump file.
Maybe the application in question itself changes the core dump size ?
i used prctl in the program to explicitly enable core dump (it sounds like a script is disabling coredumps ) and alls good now