how can I find out what firmware I have? are upgrade cables available (can't find the one that came with it)? new firmware support usb3? I assume this is my problem, as I only have problems with K and M one new computers. Thanks
↧
Forum Post: does a switchview 1000 support usb3?
↧
Forum Post: ACS6000 - Force subsequent sessions on a serial port to only monitor (read-only) the 1st active session
I've enabled multisession (set session=port_access_multiple_session_read|write) on my ACS6000. Now if someone has an established session on a serial port, a 2nd user can establish a session on that same serial port... great. This creates confusion if both users are actively typing in their respective sessions. Is there a way to force subsequent sessions on a serial port to only monitor (read-only) the 1st active session?
↧
↧
Hello Guys, Question: Where to find Activation Token for Avocent DSView Management Software in Avocent Support
Hello Guys, Question: Where to find Activation Token for Avocent DSView Management Software in Avocent Support
↧
Download DSView Management Software Question: Where to find Activation Token? in Avocent Support
Download DSView Management Software Question: Where to find Activation Token? in Avocent Support
↧
Forum Post: Avocent DSView Software Management (Activation Token)
Hi Guys, Im new in Avocent and I'm having trouble downloading the DSView Management software cause I don't know where to find the activation token. Hope someone here can help me thank you.
↧
↧
Forum Post: Permissions to a KVM with a group
Hi All, I have gone to Users > Groups and pre-defined groups. In there I have added 4 KVMs to the predefined group. But they cannot see any of the connections under the KVM device to connect to. Do I have to add every single defice permissions to that group, or is there a way to allow access to everything attached the the KVM itself? Many thanks
↧
plugin to datacenterplaner in Avocent Support
plugin to datacenterplaner in Avocent Support
↧
Forum Post: ACS 6048 sensor error
Hi all, I have eight acs 6048 with firmware 2.0.5.7 ( don't blame me, it's company specification). On six of this i get an error in cli and gui when I want to change the parameters. I cannot change anything. Does somebody also has this behavior or an idea to resolv this issue ? Kind regards, Reinhold.
↧
Forum Post: ACS6000 - ssh_minimum_cipher_and_mac_suite_level to=high drops SSH access
Under /system/security/security_profile you can set the set ssh_minimum_cipher_and_mac_suite_level to "low" or "high". Setting it to "high" drops my SSH session in the Avocent. What does this command look for on the SSH session initiated by the client?
↧
↧
Forum Post: Avocent HMX 2050 and OSX 10.12 Sierra
Just made a new boot drive for Mac Pro with OSX 10.12. HMX 2050 only sends/receives default-1280 resolution. Old boot drive OS 10.6 receives 1920 fine. Manager set up: Dual DVI port EDID setting: Port A&B 1920 x 1200. Latest firmware. Problem with Apple or Avocent?
↧
I would like to seek your assistance for DS View Activation Token. in Avocent Support
I would like to seek your assistance for DS View Activation Token. in Avocent Support
↧
Forum Post: Problem with a Dell rack screen
I inform you that we have a problem at a rack screen is off (it's going off just after its start and it shows nothing)
↧
Forum Post: Déclaration d'un problème toujours sous garantie qui est en panne
Hello, We need your help to report the problem to a rack screen that has a problem and is still under warranty. Thank you for your help, Regards,
↧
↧
can i monitor network switch with KVM switch? in Avocent Support
can i monitor network switch with KVM switch? in Avocent Support
↧
Dear Avocent support, We are in a urgent need for a new power adapter to your SwitchView KVM switch as we have received an adapter with wrong polarity (-9V instead of +9V). Is this wrong polarity issue a known issue to Avocent? We need to have the same adaptor (like the one we have now, re. picture below), but with correct polarity (+9V)! I believe the S/N on the KVM switch is 0321185457 (it is a bit difficult to read from the image below) I believe the S/N on the adapter with wrong polarity is in Avocent Support
Dear Avocent support, We are in a urgent need for a new power adapter to your SwitchView KVM switch as we have received an adapter with wrong polarity (-9V instead of +9V). Is this wrong polarity issue a known issue to Avocent? We need to have the same adaptor (like the one we have now, re. picture below), but with correct polarity (+9V)! I believe the S/N on the KVM switch is 0321185457 (it is a bit difficult to read from the image below) I believe the S/N on the adapter with wrong polarity is in Avocent Support
↧
Forum Post: Our Avocent 8Port KVM Switch 8SV 1000 device not getting ON, Only glowing Red LED's
Our Avocent 8Port KVM Switch 8SV 1000 device not getting ON, Only glowing Red LED's. Request to you all please help me out
↧
Dear Avocent support, We are in a urgent need for a new power adapter to your SwitchView KVM switch as we have received an adapter with wrong polarity (-9V instead of +9V). Is this wrong polarity issue a known issue to Avocent? We need to have the same adaptor (like the one we have now, re. picture below), but with correct polarity (+9V)! I believe the S/N on the KVM switch is 0321185457 (it is a bit difficult to read from the image below) I believe the S/N on the adapter with wrong polarity is in Avocent Support
Dear Avocent support, We are in a urgent need for a new power adapter to your SwitchView KVM switch as we have received an adapter with wrong polarity (-9V instead of +9V). Is this wrong polarity issue a known issue to Avocent? We need to have the same adaptor (like the one we have now, re. picture below), but with correct polarity (+9V)! I believe the S/N on the KVM switch is 0321185457 (it is a bit difficult to read from the image below) I believe the S/N on the adapter with wrong polarity is in Avocent Support
↧
↧
Forum Post: Some HMX KVM compatibility help please
These may be basic questions but I have been struggling to find consistent answers. Here is what I have: HMXMGR Gen1 (older hardware) running v4.0.0.10 firmware multiple HMX 2050 receivers running v4.0.0.18 firmware multiple HMIQDHDD transmitters running v4.0.0.18 firmware Question 1: I read in firmware release notes that HMXMGR v4.0.0.10 is as high as I can go with the old gen1 hardware. If I purchase additional transmitter and receiver devices, do they ship with firmware that is compatible with HMXMGR v4.0.0.10? OR do they ship with firmware that can be downgraded to v4.0.0.18? OR do I have to buy the gen2 HMXMGR as well and upgrade my entire system to v6.x.x.x? Question 2: I'm looking to connect my existing HMIQDHDD transmitters to some VGA-only laptops, but the HMIQDHDD only comes with a dual-DVI cable. Will the VGA+DVI cable (CBL0075) be compatible with my existing HMIQDHDD transmitters, or is CBL0075 only compatible with the HMIQSHDI transmitter? Essentially hoping I can get away with just buying some CBL0075s rather than HMIQSHDI transmitters. Question 3: I understand that the HMXMGR can support up to eight simultaneous user station sessions per a single transmitter per the HMXMGR manual. However, can the HMXMGR support more than eight simultaneous user station sessions if each of the user stations is talking to a different transmitter? Thank you!
↧
Wiki Page: ACS6000 built-in modem configurations for terminal based and PPP logins
The ACS6000 is available with a built-in analog modem which can be used for Out-of-band (OOB) management. The unit supports terminal based logins and PPP logins. The client/caller requires a compatible modem with a standard configuration for dial-out. He can use a terminal program like Hyperterm, Minicom, Picocom or Putty or a PPP client to dial into the ACS6000. Dial-in --------- This is a configuration example for dial-in. On this example PPP is using PAP and the username "dialin" for authentication. 1) Ports -> Auxiliary Ports Status: Enabled Speed: 38400 Init Chat: "" \d\d\d+++\d\d\dATZ OK PPP Address: Local Configuration Local IPv4 Address: 10.10.10.1 Remote IPv4 Address: 10.10.10.2 PPP Authentication: By Appliance Protocol: PAP Save 2) Users -> Local Accounts -> User Names -> Add User Name: dialin Password: Confirm password: Save 3) Ports > Dial-In Profile > Settings Log In To Appliance: Enable PPP Connection: Enable Save Note: On PPP sessions the log message "Cannot determine ethernet address for proxy ARP" is uncritical. Callback ------------ This is a configuration example for callback, a working dial-in configuration is required. On this example the user "cbuser" is used to trigger a callback to the phone number 20. To trigger the callback, dial into the ACS6000 and login as "cbuser". 1) Ports > Dial-In Profile > Settings Log In To Appliance: Callback PPP Connection: Callback Save 2) Ports > Dial-In Profile > Secure Dial-in > Callback Users > Add Callback User: cbuser Callback Number: 20 Save Note: If the callback log /var/log/mgetty.callback shows "dialup: got 'NO DIALTONE'" then the modem is unable to detect the dialtone of the telephone system. To switch off dialtone detection use the following init chat configuration: Ports -> Auxiliary Ports Init Chat: "" \d\d\d+++\d\d\dATZ OK ATX3 OK Save If a callback is triggered then it can take several minutes till the ACS6000 gives up to call the user back. During this time it is not possible to dial-in or trigger another callback. To force a timeout, login as root on the ACS6000 and execute "killall callback". Logging and Troubleshooting ----------------------------------------- This section contains logging and troubleshooting information. They are helpful if something doesn't work as expected. To enable logging edit /etc/mgetty+sendfax/mgetty.config and change debug to 4 (the default is 0 on newer firmware versions). Then execute the command "killall mgetty" to restart mgetty. Do not forget to disable logging when no longer needed. The file /var/log/mgetty.ttyM1 contains the modem log, e.g. the command "tail -f /var/log/mgetty.ttyM1" can be used as root to display the appended data as the file grows. The file /var/log/mgetty.callback contains the callback log. Below are log examples of working connections to help troubleshooting. NOTE: /var/log/mgetty.callback is not used on recent ACS6000 versions. 1) Modem Initialisation -- 02/24 16:20:57 yM1 mgetty: interim release 1.1.33-Apr10 02/24 16:20:57 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in) 02/24 16:20:57 yM1 check for lockfiles 02/24 16:20:57 yM1 locking the line 02/24 16:20:57 ##### failed dev=ttyM1, pid=20853, got signal 15, exiting 02/24 16:20:57 yM1 lowering DTR to reset Modem 02/24 16:20:58 yM1 send: \d\d\d+++\d\d\dATZ[0d] 02/24 16:21:01 yM1 waiting for ``OK'' ** found ** 02/24 16:21:02 yM1 waiting... 2) Dial-in with terminal based login 02/24 16:33:47 yM1 wfr: waiting for ``RING'' 02/24 16:33:47 yM1 send: ATA[0d] 02/24 16:33:47 yM1 waiting for ``CONNECT'' ** found ** 02/24 16:34:35 yM1 send: 02/24 16:34:35 yM1 waiting for ``_'' ** found ** 02/24 16:34:42 ##### data dev=ttyM1, pid=21636, caller='none', conn='38400', name='', cmd='/bin/login', user='ts' 3) Hang up -- 02/24 16:35:13 yM1 mgetty: interim release 1.1.33-Apr10 02/24 16:35:13 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in) 02/24 16:35:13 yM1 check for lockfiles 02/24 16:35:13 yM1 locking the line 02/24 16:35:14 yM1 lowering DTR to reset Modem 02/24 16:35:15 yM1 clean_line: only 500 of 668 bytes logged 02/24 16:35:15 yM1 send: \d\d\d+++\d\d\dATZ[0d] 02/24 16:35:18 yM1 waiting for ``OK'' ** found ** 02/24 16:35:18 yM1 waiting... 4) Dial-in to trigger callback 02/24 17:21:53 yM1 wfr: waiting for ``RING'' 02/24 17:21:53 yM1 send: ATA[0d] 02/24 17:21:53 yM1 waiting for ``CONNECT'' ** found ** 02/24 17:22:13 yM1 send: 02/24 17:22:13 yM1 waiting for ``_'' ** found ** 02/24 17:22:18 ##### data dev=ttyM1, pid=26169, caller='none', conn='38400', name='', cmd='/sbin/callback', user='cbuser' -- 02/24 17:22:19 yM1 mgetty: interim release 1.1.33-Apr10 02/24 17:22:19 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in) 02/24 17:22:19 yM1 check for lockfiles 02/24 17:22:19 yM1 locking the line 02/24 17:22:19 yM1 lowering DTR to reset Modem 02/24 17:22:20 yM1 clean_line: only 500 of 912 bytes logged 02/24 17:22:20 yM1 send: \d\d\d+++\d\d\dATZ[0d] 02/24 17:22:23 yM1 waiting for ``OK'' ** found ** 02/24 17:22:23 yM1 send: ATX3[0d] 02/24 17:22:23 yM1 waiting for ``OK'' ** found ** 02/24 17:22:24 yM1 waiting... 02/24 17:22:43 yM1 lock not made: lock file exists (pid=26388) 5) Callback (/var/log/mgetty.callback) 02/24 17:22:43 PID for mgetty on line ttyM1: 26389 02/24 17:22:43 yM1 no config file found: /etc/mgetty+sendfax/callback.config 02/24 17:22:43 yM1 initializing modem... 02/24 17:22:43 yM1 send: ATQ0V1H0[0d] 02/24 17:22:43 yM1 waiting for ``OK'' ** found ** 02/24 17:22:43 yM1 send: AT+FCLASS=0[0d] 02/24 17:22:43 yM1 waiting for ``OK'' ** found ** 02/24 17:22:43 yM1 dialing 20... 02/24 17:22:43 yM1 mdm_send: 'ATD20' 02/24 17:22:43 yM1 dialup: got 'ATD20' 02/24 17:23:06 yM1 dialup: got 'CONNECT 38400' 02/24 17:23:06 yM1 got CONNECT, success! 02/24 17:23:07 ##### callback: success, device=/dev/ttyM1, mgetty=26389 6) Terminal based login on the callback connection 02/24 17:23:07 yM1 Got callback signal from pid=26388! 02/24 17:23:07 yM1 stealing lock file from pid=26388 02/24 17:23:49 ##### data dev=ttyM1, pid=26389, caller='none', conn='', name='', cmd='/bin/login', user='shell' 7) Hang up the callback connection -- 02/24 17:26:03 yM1 mgetty: interim release 1.1.33-Apr10 02/24 17:26:03 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in) 02/24 17:26:03 yM1 check for lockfiles 02/24 17:26:03 yM1 locking the line 02/24 17:26:04 yM1 lowering DTR to reset Modem 02/24 17:26:05 yM1 clean_line: only 500 of 1503 bytes logged 02/24 17:26:05 yM1 send: \d\d\d+++\d\d\dATZ[0d] 02/24 17:26:08 yM1 waiting for ``OK'' ** found ** 02/24 17:26:08 yM1 send: ATX3[0d] 02/24 17:26:08 yM1 waiting for ``OK'' ** found ** 02/24 17:26:08 yM1 waiting... 8) Dial-in with PPP 02/24 17:34:26 yM1 wfr: waiting for ``RING'' 02/24 17:34:26 yM1 send: ATA[0d] 02/24 17:34:26 yM1 waiting for ``CONNECT'' ** found ** 02/24 17:34:46 yM1 send: 02/24 17:34:46 yM1 waiting for ``_'' ** found ** 02/24 17:34:47 ##### data dev=ttyM1, pid=27094, caller='none', conn='38400', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/' 9) Hang up PPP session -- 02/24 17:36:50 yM1 mgetty: interim release 1.1.33-Apr10 02/24 17:36:50 yM1 WARNING: parent process not init(pid=1), but pid=3251 (/sbin/dial-in) 02/24 17:36:50 yM1 check for lockfiles 02/24 17:36:50 yM1 locking the line 02/24 17:36:51 yM1 lowering DTR to reset Modem 02/24 17:36:51 yM1 send: \d\d\d+++\d\d\dATZ[0d] 02/24 17:36:54 yM1 waiting for ``OK'' ** found ** 02/24 17:36:55 yM1 send: ATX3[0d] 02/24 17:36:55 yM1 waiting for ``OK'' ** found ** 02/24 17:36:55 yM1 waiting...
↧
Wiki Page: ACS6000 Serial Modem Troubleshooting
To troubleshoot the modem, disable the modem port e.g.: Ports > Auxiliary Ports > ttyM1 Status: Disabled Then execute "sptest" as root and choose 1. Single Port Operations -> 1. Port Conversation -> choose your modem port -> enter port number -> enter baud rate Now you are directly connected to the modem and can use the Hayes command set to communicate with the modem. E.g. AT to check if the modem is listening to commands and on external modems to verify if the cabling is correct. Modem will answer with OK. ATA to answer an incoming call (will only work after a RING). Modem will answer with CONNECT once connected or with an error if connection cannot be established. This can take several minutes. The general sequence is: AT the modems answers with OK RING -> someone is calling ATA we get a connection message once connected A CONNECT message is mandatory. Any other answer instead of CONNECT means that the modems are unable to connect. As there is no configuration active at this low level troubleshooting steps there cannot be a configuration issue on the Avocent device. NO CARRIER during synchronization means that the caller did hang up the line during synchronization. It's an issue on the caller side, not on the ACS. Based on customer feedback it is related to bad line quality, incompatible modems or wrong timeout settings on the caller side. The timeout should be at least 180 seconds. No CONNECT message is an environment issue and not under the control of the Avocent device. To quit the test press CTRL+Q, ESC, ESC and do not forget to re-enable the modem port. Note: You cannot test the quality of a phone line for data communication by connecting a telephone to it. Voice needs a much lower frequency spectrum as data. You can only test it by connecting a standard modem with a PC to it, establish a data connection and transfer data over the connection.
↧