Please, using Solace SEMP, how can I find which is the current appliance hardware and firmware version?
I tried https://${Solace_IP}/SEMP/v2/config/ and https://${Solace_IP}/SEMP/v2/config/about with no lucky
https://${Solace_IP}/SEMP/v2/config/about/api shows SEMP version, but not Firmware/Hardware versions!
You can use SEMP v2 to retrieve the SolOS version if you have version 10.1.0+.
curl -X GET -u mgmt_username:password 192.168.XXX.XX:PORT/SEMP/v2/monitor and you'll see the version under data.version
SEMP v2 doesn't yet show the hardware details, but you can find them using SEMP v1. More info in the docs, but something like this should do it for you:
<rpc>
<show>
<hardware><details/></hardware>
</show>
</rpc>
Related
I'm surprised there isn't already an answer for this. Maybe it's so obvious no one needs to ask.
This is the issue. I have a web server running on Ubuntu 16.04 on AWS, it takes orders. When an order comes in it has to be printed on a printer located in an office. The printer is a modern enterprise HP printer. So all features are available.
I can set up the printer drivers on a local Ubuntu machine (desktop but tested via ssh command line), then
sudo hp-setup -i
can find the local network printer and configure the drivers. So I can then do
lp some_file.pdf
and it works!!! But...
The remote server on AWS obviously can't find the printer in the office. So plain
sudo hp-setup -i
doesn't work. I've opened up port 9100 on our WAN interface (Draytek), and allowed it to receive connections only from the remote AWS server. But when I try
sudo hp-setup -i my_ip_address
or
sudo hp-setup -i --port=9100 my_ip_address
It returns a stack of errors which scroll off the screen. Starting with
HP Linux Imaging and Printing System (ver. 3.16.3)
Printer/Fax Setup Utility ver. 9.0
Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
(Note: Defaults for each question are maked with a '*'. Press <enter> to accept the default.)
MIB search path: /home/ubuntu/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Cannot find module (SNMPv2-MIB): At line 0 in (none)
Cannot find module (IF-MIB): At line 0 in (none)
Cannot find module (IP-MIB): At line 0 in (none)
Cannot find module (TCP-MIB): At line 0 in (none)
Cannot find module (UDP-MIB): At line 0 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 0 in (none)
and so on.....
I'm pretty sure this is a common issue, but I can't find a similar question with the answer.
Please don't say 'use HP Eprint' or 'Use Google Cloud Print'. We're already using HP Eprint and it's very very unreliable, which is why I'm researching alternatives. Google Cloud Print is not easy to configure to print from a command line or from within a web app.
I need to know how to configure things so the remote AWS server can talk to the office printer.
I have Mirth Connect Version 2.2.3.6825 installed on RHL I want to access my Mirth my Local Machine which have Java 1.8(Java 1.7 it Work fine), I am not able to launch the Administrator tool of Mirth. When I clicked on the administrator button, It opened the window saying starting application after giving User name and Password it give error 'There was an error connecting to the server at the specified address. Please verify that the server is up and running'
http://www.mirthcorp.com/community/wiki/display/mirth/System+Requirements
Java 8 should work with version 2.2.3, but you must be using the Oracle JRE. OpenJDK only recently became supported with version 3.7.
You may also want to try using the new Administrator Launcher available on the mirth downloads page. It comes bundled with a Java 8 JVM so that you don't need to install one separately. It works with all versions of mirth from 2.x and up. See announcement here: https://www.mirthcorp.com/community/forums/showthread.php?t=218662
Is there possibity to migrate data(topic, queues and all other config) from Old Solace VMR to latest Solace pubsub+ version?
Upgrading your VMR to the latest Solace PubSub+ software message broker will preserve all data including messages that are spooled.
If upgrading is not an option, you can capture all message-vpn level data (including topics and queues) with the "show current-config message-vpn *" command. You can use the “>” and “>>” characters to redirect the output to a file and run this file as a script on the new Solace PubSub+ software message broker.
The output is generally backwards compatible but keep in mind that it may not be possible to take the configuration from a newer version of the Solace message broker and apply it on an older version as there may have been new features and commands added.
May I know whether there is any limitations to Solace VMR trial version? I exported CLI commands to setup a VPN from a Solace appliance. I can run the CLI script to create a VPN on appliance but when I tried to run the same script in VMR, it seems to have issues. Similarly, VMR does not seem to allow me to setup SSL. Any advice?
Thank you.
The following Solace appliance features are not currently supported by the Solace VMR:
High-Availability (HA) router redundancy
TLS/SSL client certificates
TLS/SSL bridging
TLS/SSL client connections with Solace Java and JMS messaging API versions less than 7.1.1.169
Compressed traffic
Eliding
HA Config-Sync
Upgrades and downgrades using the ‘boot’ command
Legacy mode SEMP over msg-bus commands
Legacy mode ACL rule enforcement
SNMP
Cut-through guaranteed messaging
This list of feature limitations and other known issues are available in the Solace VMR Release Notes.
The Solace VMR has a lower capacity than the Solace hardware solution, therefore some of the limits on system resources differ. If you have a license for the Solace appliance, you will have access to the SolOS_system_limits_and_alerts_VMR.xlsx spreadsheet in your customer portal which documents all limits of the VMR.
Some examples include:
Client connections - 1000 on VMR, 9000/200,000 on the appliance (depending on the model)
Queues and topic endpoints - 1000 on VMR, 16000 on appliance
Topic subscriptions - 500000 unique and 1000000 non-unique on VMR, 5000000 unique and 10000000 non-unique on appliance
These feature and resource limitations are accurate for the 7.1.1.342 SolOS version of the VMR and appliance. These values may be different for other versions.
Note that these limits apply for both the Evaluation and the Enterprise version of the Solace VMR. The limitation of the Evaluation version, as compared to the Enterprise version, is that it contains only a 30-day trial license and is not supported for production environments.
If your CLI script is returning errors, it could be that it is trying to enable a feature that isn't supported or it has exceeded a limit on the VMR.
I am using Android ICS 4.0.4 source code for enabling the Wi-Fi Direct and run on i.MX6 board with Wi-Fi module which supports marvell 8787 chipset.
I was able to make the wfd0 interface up for wifi direct but the other p2p operations such as device discovery was failing.
I was using WEXT as driver interface .After googling I came to know for the p2p operations nl80211 must be used.
I changed the configurations from WEXT to nl80211. But the wpa_supplicant stopped working.Even though I am starting the wpa_supplicant service from init.rc file the wpa_supplicant does not seems to be running.
Does Android ICS 4.0.4 provide a complete support for Wi-Fi Direct?
Could anyone help me with this issue. ?
The support for Wi-Fi Direct on Android has began for the 4.1 version (source).
Moreover, as you said, the WEXT drivers does not support P2P. So you have to use nl80211 drivers. But are you sure that your device have a valid nl80211 driver?
If you want to known why your wpa_supplicant is crashing, you can start it by hand in a shell without the -B option and with the -dd option and check the log.