Hi,
Thank you for taking time to answer my question. But I don't understand what you are trying to say...
You copied a piece from a manual?
Can you clarify this more please?
thank you.
Arno
Hi,
Thank you for taking time to answer my question. But I don't understand what you are trying to say...
You copied a piece from a manual?
Can you clarify this more please?
thank you.
Arno
Update to PT.02.05 FW helps. Now it's OK.
cheers
It is my understanding you only enable loop protection on your "access" ports, not your uplinks. It's meant to keep the end user from creating a loop if they plug up a switch and create a loop. We do not enable loop protect on our uplink ports, only end user device ports.
Hi, i was looking to download the latest firmware for my PS1810 switch and i did manage to find all the neccesary documentation, i just could not find the downloadable software needed.
Can someone help me finding the PS.2.10 firmware (latest) for my PS1810-8G?
In the default IP address statement 192.168.1.1
I can not connect on this IP, on ping it does not respond. This address in my network is free. Reset switch did it didn't help
It turns out that if you connect it to a network that has DHCP server, it will get the address from it, the manufacturer should have displayed it in the documentation.
I've going at it for 4 hours now and have not been able to get SNMPv3 working on these type of switches.
Not able to do an SNMP walk or get traps.
Has anyone been able to get this working?
Hi,
Yes SNMP v3 is supported on some of HPE Office Conenct 1920s.
Can you share your Product number?
Have you tried to enable trap?
Thanks!
AKG
i will try to switch to mstp by the way commnet industrial has only rstp protocol or some proprietary ring protocols
Hello, my first post here!
I have come around a weird bug while provisionning a HPE 1920S PoE+ switch.
I have two identical 1920S switch brand new out of the box, which I upgraded from the PD.01.05 software version to the latest version PD.02.05. On the first switch I had no issues at at and my Aruba IAP-207 worked perfectly. On the other switch I realized that not a single AP was coming up, but my non-PoE wired devices had a link and connectivity.
Upon starting the troubleshooting steps, I saw the logs showed the following error message on all switchports: <12> Dec 31 19:19:00 Auberge-SW-2-1 POE[poe_monitor]: hpc_poe_brcm.c(9473) 3325 %% Unable to get the PortStaus for port 24 of unit 1
I then reverted back to the original code version on the switch and saw other PoE related messages and still nothing was working:
3 Jan 1 00:04:52 Error POE Unable to Download Firmware to PoE Unit 1, Card 0
4 Jan 1 00:04:52 Warning POE Code downloaded onto the PoE chip is bad. Need new Code
I then went on and tried another 1920S firmware version (PD.01.08) which seemed to fix the firmware issues, as my APs were finally getting power to them. I noticed also some logs related to PoE.
Hi, I have 6 HP 1950 switches that I am deploying.
I was thinking of having 1 stack of 4 and 1 stack of 2, the stack of 2 will have edge connections and servers etc and the stack of 4 is all client PC's and Phones/Printers etc. They are side by side in our racks so close to each other.
I am confused about how best to uplink from the stack of 4 into the stack of 2.
I will be utilising the 2 SFP ports on each switch for the uplinks.
So on my 4 stack I will have 8 SFP ports to use and on the stack of 2 I will have 4 available.
I am trying to use as little cabling as possible for the uplinks while still having some redundancy.
Hi, since you want to use (that's reasonable!) SFP Interfaces on both IRFs (the four members one and the other two members one) you're thus limited by the grand total of 4 SFP Interfaces provided by the two members IRF.
If I were you I will create a 4 links LACP LAG on both, say BAGG1 and BAGG1, with 4 member links distributed on all four - so using 1 SFP per Member - IRF Members on one side - your Stack 1 - and with the peer 4 member links distributed on all other two - so using 2 SFP per Member - IRF Members on the other side - your Stack 2) and then interconnect them via that LAG...in this way you will have enough redundancy/resiliency.
Hi,
I am having issues with PS1810-8G locking up. The network setup is this:
Router -> PS1810 -> Microserver Gen8 with Windows Server 2016
The same PS1810 switch has QNAP 453A connected to it.
PS1810 crashes every single time I do the following after starting Microserver:
1) Turn on the switch
2) Turn on Microserver
3) Login into Windows Server 2016 user account
4) Connect to QNAP share
5) Go into a second level directory on QNAP share
6) The switch stops working and all other devices coming of the switch loose connectivity
When I don't have the Microserver turned on other devices can browse through QNAP shares and there are no problems. I don't know if the issue is PS1810 or Microserver. This has been a problem ever since I purchased the switch but I previously 'solved' it by connecting a second switch to PS1810 and connecting Microserver to that. Today I moved around my equipment and regardless of where the Microserver is connected (directly to PS180 or to a second switch that connects to PS1810) the switch crashes.
Has anyone experienced anything similar? Any idea as to what I could do?
Thanks.
Hi, it's unusual a Switch crashes due to a bug...especially if it "crashes" only when a very specific host is connected to it.
It's also unclear what do you mean with "crash" (does it reboot automatically? is the network just hanging? all of your connected hosts lose - ping as example - interconnectivity?).
Not knowing exactly your network topology/mapping neither your networked hosts IP assignments nor your Switch ports configuration...do (a) an update your HPE 1810-8G to PS.2.10 (see here), double-check IP addressing (and port/VLAN settings) of all of your connected hosts to verify no overlapping/conflicts are present and then try to understand (Switch side and Host side) why connecting a specific Host to your network segment/switch causes the Switch to hang/crash/reboot (or whatever).
What happens if you DO NOT connect your HPE ProLiant Microserver G10? can you still browse your QNAP's shared folders?
Hi,
I've attached a network diagram that should be sufficient to describe the current network setup. Devices attached to the switch get their IP addresses from the router. Some of the devices have reserved IP addresses and some are random.
PS1810 is running PS.2.10 with PS.2.8 as a backup image. All the ports on the switch are on the same VLAN as VLANs are not enabled.
The PS1810 is configured like this:
When I write crash I mean the following occurs:
If I do not start up the Microserver G8 the PS1810 works and other devices continue to have access to each other. Other devices on the other ports of the router continue to have ping access to PS1810 connected devices, and have access to QNAP shares.
I have tried connecting NIC 1 and NIC 2 of the Microserver to the PS1810 and seeing if it made any difference. No difference having either NIC connected. I have not tried having only ILO connected to the PS1810.
I have not tried disconnecting QNAP and trying to mount Windows 10 shares on Windows Server 2016 (Microserver Gen 8). That may be worth doing but issue will still remain that a specific host (HP Microserver Gen8) causes the HP PS1810 switch to crash. Its even more odd to me as the two are designed to work in unison.
The only solution that I have found so changing the network layout. If you look at my attached diagram and on it disconnect the Microserver Gen8 and QNAP from PS1810, then connect them to the unmanaged switch. In that scenario, where the layer 2 connection between Microserver Gen8 and QNAP is across another switch (a switch that is connected to PS1810) there is no crashing of PS1810.
Hi all:
I want to config 1920S hybrid port.
Since 1920S didn't support cli config.
If I want to config port with below config (It's HPE 1920 configuration)
How can I do via WebGUI?
port link-type hybrid undo port hybrid vlan 1 port hybrid vlan 100 200 tagged port hybrid pvid vlan 100
Thanks,
Hey guys,
Thank you in advance for help on this one. I have 2 aruba 2530 switches connected by Fiber on port 52 on both switches. The root swith work perfect but my 2nd switch will not route traffice on my "guest" or "Mgmt" vlan. The internal (defuatl vlan1) works on both ends so that vlan is working but the other 2 are not. Im sure this is something simple but I am not seeing it. Can any one give me a hand? I will attach the running configs of both switches. Thank you in advance.
Root switch
Running configuration:
; J9772A Configuration Editor; Created on release #YA.16.06.0006
; Ver #13:44.00.04.19.02.13.98.82.34.61.18.28.f3.84.9c.63.ff.37.27:43
hostname "2530-48G-MUDO SIDE A"
ip default-gateway 192.168.1.1
interface 3
name "X0"
exit
interface 5
name "X2_Guest"
exit
interface 7
name "X3_MGMT"
exit
interface 14
name "AP1_MUDO_Office"
exit
interface 16
name "AP2_Kitchen_Hallway"
exit
interface 18
name "AP3_Oak_Rooom"
exit
interface 20
name "AP4_Bar_Area"
exit
interface 26
name "AP5_2nd_Floor_Right_of_stairs"
exit
interface 28
name "AP6_2nd_Floor_Elevator"
exit
interface 30
name "AP7_2nd_Floor_right_Side_banquet_hall"
exit
interface 32
name "AP8_]2nd_Floor_Banquet_Hall_Middle"
exit
interface 38
name "AP9_2nd_Floor_Banquet_Hall_Left_Side"
exit
interface 40
name "AP10_2nd_Floor_Bar_area"
exit
interface 52
name "Tie_To_Proshop"
exit
snmp-server community "public" unrestricted
snmp-server location "MUDO office side"
vlan 1
name "DEFAULT_VLAN"
no untagged 5,7
untagged 1-4,6,8-13,15,17,19,21-25,27,29,31,33-37,39,41-51
tagged 14,16,18,20,26,28,30,32,38,40,52
ip address 192.168.1.240 255.255.255.0
exit
vlan 200
name "Guest"
untagged 5
tagged 14,16,18,20,26,28,30,32,38,40,52
no ip address
exit
vlan 300
name "MGMT"
untagged 7,14,16,18,20,26,28,30,32,38,40
tagged 52
ip address 10.10.101.240 255.255.255.0
exit
no tftp server
no dhcp config-file-update
no dhcp image-file-update
password manager
----
2nd switch - that is the switch that is getting the internal (x0) vlan but not the other 2 (x2 guest) (x3 mgmt)
Running configuration:
; J9772A Configuration Editor; Created on release #YA.16.06.0006
; Ver #13:44.00.04.19.02.13.98.82.34.61.18.28.f3.84.9c.63.ff.37.27:43
hostname "2530-48G-Pro Shop Side B"
ip default-gateway 192.168.1.1
interface 14
name "AP11_Proshop_closest_to_bathroom"
exit
interface 16
name "AP12_Next_to_Managers_office"
exit
interface 52
name "Tie_From_Mudo_Side_A"
exit
snmp-server community "public" unrestricted
snmp-server location "Pro Shop side B"
vlan 1
name "DEFAULT_VLAN"
untagged 1-13,15,17-51
tagged 14,16,52
ip address 192.168.1.241 255.255.255.0
exit
vlan 200
name "Guest"
tagged 14,16,52
no ip address
exit
vlan 300
name "MGMT"
untagged 14,16
tagged 52
ip address 10.10.101.241 255.255.255.0
exit
You need to decide if you want your switches to switch or to route. Why does switch #2 have an IP address in VLAN1?
You have all 3 VLANs spanned between the two switches, so you don't have a VLAN problem.
Your problem is most likely to lie in what your hosts are using as their "default gateway", and what the configuration at 192.168.1.1 is. I suspect you don't have routes for the subnet 10.10.101.0 on the device that has 192.168.1.1. You don't seem to have any routing in place for VLAN200.