Just tried with live Linux, same problem. Strange thing is that speed doubled, now it is 10MB/sec, but still much slower than other access points. No fluctuation on speed, pretty much constant 10MB/sec. Also again client and OC20 shows that live client is connected with 5Ghz and 802.11 AC
↧
Re: HPE OC20 802.11ac (RW) Access Point performance issues
↧
Re: HPE OC20 802.11ac (RW) Access Point performance issues
Pretty interesting, considering that doubling the 5 MBps value to 10 MBps means a gain of 100%...not the result you expect but still remarkable considering there is somewhere an problem (also consideri that you can try a large amount of iwlwifi related optimizations using Linux...just as example, think about the WiFi/Bluetooth operations coexistence).
Probably there is something related to IEEE 802.11ac Channel Bandwidth settings on the OC20 (as example a Channel width of 20 MHz - with just one Spatial Stream SS involved - seems to provide, depending on MCS Index 0-9, bit rates ranging from 7.2 to 96.3 Mbps at 5 GHz...pretty compatible with a throughput of only 10 MBps).
Would be interesting to deep dive into Linux CLI [*] to grab all information about iwlwifi and your Intel 7265 AC adapter [*]...but, probably, also HPE should give you some troubleshooting support on OC20 side.
[*] starting with a:
$ dmesg |grep iwlwifi
and going on checking microcode:
$ ls -ltr /lib/firmware/|grep 7265
up to showing with iw the connection status:
$ iw dev wirelessinterfacename link
where wirelessinterfacename should be changed with the actual Wireless NIC name given by Linux on your test host (you should see a line on the output of the first dmesg command about a "wirelessinterfacename: renamed from wlan0", that's the actual Wireless interface name...the wlan0 was the old name provided by the previous NIC naming system).
↧
↧
Re: OC20 Management & Features
Thanks for the Release Notes.
I will try to get my hands on two or three OC20 from our distributor and will provide more information then.
But I don't have much faith in 802.1X support, to be honest.
↧
Re: HP 1920 - extreme slow VLAN routing
Hi Folks
I had the same problem in just a small environment, just 40 VM’s and 25 workstations. I did not came across your blog about this issue, so I have struggled over a week on this.
Reading always helps a lot!
I just changed the switch to old Cisco 3750 and everything works fine. On all workstation I got file transfer throughput of more than 30 Mbyte/s between routed Vlans.
So what is this HP 1920 actually for? It says it is layer 3, but partially it is not!
We are going to give back the switch to the supplier.
Thanks & Regards,
Boris
↧
PANDUAN CARA BERMAIN BLACKJACK ONLINE UNTUK PEMULA
1xidr - Panduan Cara Bermain Blackjack Online Untuk Pemula. Para pemain yang baru bermain blackjack di mana permainan ini mengunakan jenis kartu poker atau biasanya di sebut kartu remi oleh para pemain judi online. Untuk para pemain yang ingin bermain Blackjack Online di mana jenis permainan ini sangat terkenal di Indonesia dengan sebutan Blackjack 21 oleh para pemain Judi Online.
Panduan Bermain Blackjack Online ini bukan permainan untuk melawan Dealer Casino Online atau member online lainnya. Permainan in merupakan salah satu permainan strategi di mana kita berusaha untuk mencapai nominal 21 atau biasnya di sebut "BLACKJACK". Maka dari itu kami akan menguras cara bermain Blackjack Online di 1XBET.
↧
↧
Cryptic error message HP V1810-48G
Every few months I receive error messages through syslog from one of our three switches (firmware PK 1.34) like this:
[-2131330512]: hal_misc.c(96) 1523 %% Jump to NULL! Interrupt: 0x00000000 vector: 0x00000098 cause: 0x00000000 status: 0x00000000
So far I see not a real impact..
Can anyone say anything more about these errors?
↧
Dental Web Design in Australia
Dental Web Design in Australia
"Looking for quality dental web design? Consult with We Are Web. We are a digital agency in Melbourne that provides premium web solutions, content marketing and more. Call today."
30-40 Flockhart St Abbotsford 3067 VIC
1300 774 825
jeremy@weareweb.com.au
Monday to Friday: 8AM to 6PM,Saturday: 10AM to 2PM
CONTACT US WEB SOLUTIONS IN SYDNEY AND PERTH
↧
Switch HPE OfficeConnect série 1920
I have an HP OfficeConnect 1920 Series Switch but forgot the ip address of the same as I do to restore factory default if it does not have reset button?
↧
Re: Switch HPE OfficeConnect série 1920
You should just connect thorugh Console cable (using the PuTTY client, as example <-- check HPE OfficeConnect 1920 Switch Series latest documentation - User Guide - on how to do that) and then, once logged into the Switch Console, execute the ipsetup CLI Command (which assign an IP address to Default VLAN Id 1) once again or, if you really want to re-initialize, execute the initialize CLI Command (which delete the Startup Configuration file and reboot the switch into the factory default state).
↧
↧
Re: HPE OC20 802.11ac (RW) Access Point performance issues
If you still have the issue with performance, getting a look at the output of this command in Windows command line may help:
> netsh wlan show interfaces
It will give you details on the channel used and the connection rates.
↧
Re: HPE OC20 802.11ac (RW) Access Point performance issues
Yes, we still have issues with every OC20 devices. I have been using netsh and normal Windows 10 Settings to check WLAN properties. Those usually shows 802.11 AC 5GHz, channel is usually 52, but still no more than about 5MB/s speeds on data transfer from servers. Even if I go as far as I can with test laptop the signal usually drops to 802.11n, but data transfer speeds is the same even if there are about 30meters and few walls between laptop and OC20.
↧
Re: 10GB Fibre Module on 1920 48G
I've successfully used any SFP module for J4858C, Brute Networks, Axiom & Bocade manufacture.
Hope that helps!
↧
HPE OfficeConnect 1920, 24G
Is the static routing of the RIP (Routing Information Protocol) used in this model?
↧
↧
Re: HPE OfficeConnect 1920, 24G
RIP (routing table formed dynamically) is different from Static Routing (routing table formed statically and manually): AFAIK HPE OfficeConnect 1920 Switch series supports IPv4/IPv6 Static Routing only (Neither RIP nor OSPF, up to 32 IPv4 and 32 IPv6 Static Routes admitted).
↧
Pregnancy maternity and tummy belt for women
Pregnancy maternity and tummy belt for women
Maternity Belt helps you by ensuring that your tummy is supported properly after the pregnancy. The post-pregnancy belt protects the fetus thereby preventing any chances of miscarriage for women. Tummy belt aims at making your pregnancy easier as being pregnancy support belt.
http://farlin.co.in/farlin-maternity-belt
Maternity Belt,
Pregnancy Belt,
Tummy Belt,
Women,
post pregnancy belt
↧
Re: Cannot log into new switch. Followed directions to a tee. Its not my first rodeo either.
Why do you think that Switch should have the Telnet server service enabled (if any at all)?
From what HPE OfficeConnect 1820 Switch Series Installation and Getting Started Guide (March 2017), it should fall back on default 192.168.1.1/24 IP Address if it doesn't found a valid DHCP Server releasing to it an alternative (or the same IP Address) in 120 seconds...so a question: do you have a device in the same LAN Segment and for the same Default VLAN that is acting as DHCP Server? if so...what is the IP Address released to the HPE OfficeConnect 1820 Switch (you should be able to verify that reading the DHCP Server Logs looking for the HPE Switch MAC Address).
I ask because you must be sure that the IP Address you're pinging and on which you believe there is the HPE Switch Web GUI is really that address (so DHCP presence matters).
If not, no DHCP Server is available, the Default 192.168.1.1/24 IP Address is valid (wait at least two minutes before connecting from Power On).
↧
IP Phone not working on HP 1920 switch
Hello
We have HP 1920 (JG924A) switch at remote location. Having only 1 VLAN (Default VLAN - 1). All ports are access ports. Switch HP 1920 is connected with another uplink switch HP E-3800 that too has only 1 VLAN (Default VLAN-1) all ports are untagged in VLAN 1. That switch HP e-3800 is uplink with Cisco router.
There are PC / workstations , printers, IP Phones. All of them working fine on HP-E3800.
But IP Phones are not working on HP-1920. Able to ping the IP phone but service is not working. When shifting IP Phone to HP E-3800 it works fine.
Help needed.
↧
↧
Re: IP Phone not working on HP 1920 switch
Can you share port(s) configurations used at both ends (HPE OfficeConnect 1920 and HPE 3800) to form the uplink?
↧
Re: IP Phone not working on HP 1920 switch
Switch HPE-3800
Running configuration:
; J9585A Configuration Editor; Created on release #KA.15.03.3015
; Ver #01:00:01
hostname "HP-E3800"
module 1 type J9585x
interface 25
name "Uplink_to_HP-1920"
exit
interface 26
name "UPLINK_TO_ROUTER"
exit
ip default-gateway x.x.x.x
vlan 1
name "DEFAULT_VLAN"
untagged 1-26
ip address x.x.x.x y.y.y.y
exit
telnet-server listen data
web-management listen data
ip ssh listen data
snmp-server community "abc123" operator
snmp-server listen data
spanning-tree
oobm
disable
no ip address
exit
tftp server listen data
no autorun
no dhcp config-file-update
no dhcp image-file-update
password manager
password operator
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
***************************************************************
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Switch HP-1920
#
version 5.20.99, Release 1108
#
sysname HP1920
#
domain default enable system
#
ipv6
#
telnet server enable
#
password-recovery enable
#
vlan 1
#
domain system
access-limit disable
state active
idle-cut disable
self-service-url disable
#
user-group system
group-attribute allow-guest
#
local-user abc123
password cipher
authorization-attribute level 3
service-type ssh telnet terminal
service-type web
#
stp mode rstp
stp enable
#
interface NULL0
#
interface Vlan-interface1
ip address x.x.x.x y.y.y.y
#
interface GigabitEthernet1/0/1
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/2
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/3
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/4
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/5
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/6
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/7
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/8
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/9
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/10
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/11
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/12
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/13
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/14
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/15
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/16
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/17
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/18
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/19
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/20
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/21
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/22
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/23
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/24
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/25
stp edged-port enable
#
interface GigabitEthernet1/0/26
stp edged-port enable
#
interface GigabitEthernet1/0/27
stp edged-port enable
#
interface GigabitEthernet1/0/28
stp edged-port enable
#
ip route-static 0.0.0.0 0.0.0.0 x.x.x.x
#
undo info-center logfile enable
#
snmp-agent
snmp-agent local-engineid ?????
snmp-agent community read abc123
snmp-agent sys-info location
snmp-agent sys-info version v3
snmp-agent target-host trap address udp-domain x.x.x.x params securityname abc123 v2c
snmp-agent trap enable default-route
#
load xml-configuration
#
user-interface aux 0
authentication-mode scheme
user-interface vty 0 15
authentication-mode scheme
#
return
↧
Re: IP Phone not working on HP 1920 switch
Mmmm...from configuration file the HPE 3800-24G-2SFP+ Switch (J9585A) physical port 25 (it's the first 10GbE port of two, is it right?) is used as uplink port to the HPE OfficeConnect 1920-24G switch...but on this latter one what port was used as uplink terminating port?
I ask because HPE OfficeConnect 1920 Switch Series hasn't 10GbE Ports (Ports and Slots are for 1GbE at maximum) so you were forced to use, on both ends, physical ports running at Gigabit Ethernet speed only at best (that's mandatory on the HPE 1920 side). Is that right?
Question: 10GbE Port 25 and 26 on HPE 3800 can go at 1GbE? in other terms do those ports admit 1GbE/10GbE operation or only 10GbE?
Have you set both uplink end ports with "Port Type" of type "Trunk" instead of type "Access" permitting VLAN Id 1 to pass? I ask because HPE 3800 Port 25 and HPE 1920 Port x are uplinked so Port Type should be set of type "Trunk" (at least this is the nomenclature and port settings that is recommended on HPE 1920 side, since it is a Comware 5.20 operating system based Switch).
On HPE 1920 consult User Guide to see how to set the port used as uplink to HPE 3800 of type "Trunk" permitting VLAN Id 1 (VLAN Id 1 is default untagged on all ports so it should be very simple as changing type "Access" to type "Trunk" for the "Port Type" on the port considered for the uplink).
The HPE 3800 is ProVision operating system based and uses another type of nomenclature to define an uplink port to another switch, generally it is sufficient to configure the VLAN Id 1 to be untagged on the physical port you will use to uplink to another switch (eventually specifiying other tagged VLAN Ids that uplink port would let to flow):
HPE3800(config)#vlan 1 HPE3800(config-vlan)#untagged 25
Then consider to update both Firmware images (R1108 of HPE 1920 is quite old, latest is R1117 or eventually R1116 | KA.15.03.3015 ...what? is that correct? looking here no KA.15.03.3015 was listed so, probably, it is older than the oldest liste which is KA.15.09.0009...by the way latest software release for 16.04 Software Branch of KA Product Line is actually the recent KA.16.04.0008...so, if I were you, I would pay a close attention to my Switch(es) firmware(es) before trying or doing other configurations).
You should configure your uplink between HPE 3800 and HPE 1920 as described here
↧