Hi all,

i would like to ask about HP Officeconnect 1920s. i did VLan and Trunk in 1920s Switch but it is not working. I have over 20 VLans.. Please point to me step by step about Trunk and VLan. 

The HP Office Connect is a product of Hewlett-Packard Inc.

This community is for customers and friends of Hewlett Packard Enterprise, which is an independent company. For HP products, please see www.hp.com or the HP Support Forums: https://h30434.www3.hp.com/.

Hi , the OP is correct: the HPE OfficeConnect 1920S (as the superseded 1920) is an entry level Switch series - web managed only - of HPE...there is also a dedicated Support Portal about the entire HPE OfficeConnect Switch (and Wireless AP) series.

Edit, for the OP I add here the reference about HPE OfficeConnect 1920S Switch series:

Landing page of HPE OfficeConnect Support portal says it all.

Specific page of HPE OfficeConnect 1920S Switch series (with Manuals and Firmwares) can easily be found by selecting 1920S on the drop-down menu: Pay attention to what was discussed here regarding the latest proposed OfficeConnect's Firmwares (HPE OfficeConnect Support Portal's switch series specific pages don't seem to having been kept up-to-date lately with latest published Firmwares available as of today, that has been verified with regard to 1920S, 1950 and 1820 switch series and the thread above is about that).

My apologies, and thanks for verifiying.

Hello Everyone,

can someone please point me to the firmware download page for the 1920-8G switch.

Unfortunatly this can't be found aymore via the support page nor via the OfficeConnect portal.

I wish HPE changes back to the old support pages, most software/firmware were easier to find then.

Cheers, Ole

---

OleJo wrote: Hello Everyone,can someone please point me to the firmware download page for the 1920-8G switch.

Here we go:

• go here.
• enter the product name (Switch series), model or - better - the SKU (in you case the SKU is exactly JG920A)
• press "Search"
• go to the link provided to see all released Firmwares and related Release Notes (that's your case).

OleJo wrote: Unfortunatly this can't be found aymore via the support page nor via the OfficeConnect portal.

I wish HPE changes back to the old support pages, most software/firmware were easier to find then.

Cheers, Ole

---

I agree with you. Luckily there are other paths to reach Networking firmware related downloads, as the one provided above; the new HPE Support Portal is far from being effective (at least speaking about Networking firmware related downloads, Server related searches are still suffering a little bit too).

Another strange thing is that HPE OfficeConnect 1920 Switch Series, despite being part of OfficeConnect, is not listed on HPE OfficeConnect Support portal...maybe because it was superseded by 1920S...who knows?

Thanks Parnassus,

this helps me a lot. I wasn't aware of this path, as I'm more used to server support.

I'm just stopping my comments about the new support pages, our HPE key account manager is more suitable for the rant ;).

Anyhow, at least there are kind people here in the community.

Cheers Ole 

Glad you find the info useful!

OleJo wrote:I'm just stopping my comments about the new support pages, our HPE key account manager is more suitable for the rant ;).

Yeah, I know what you mean.

We (HPE Community active and returning users), after initial moments during which we felt lost (I speak for myself here), are trying to be positive and constructive providing all required feedbacks directly and indirectly...things are necessarily moving on and some improvements were already implemented (some not)...it still lacks some of the nice things the past portal had or still it has flaws and all were discussed on this hot thread here...if you have some spare time give it a read you would find it quite interesting...undoubtly your HPE Key Account Manager will help the cause but you can provide some feedback too.

Hi,

When my switch boots up in some point it shows the following output on the screen.

rv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(8,25)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(7,25,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(8,26)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(7,26,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(8,27)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(7,27,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,0)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,0,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,1)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,1,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,2)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,2,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,3)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,3,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,4)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,4,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,5)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,5,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,6)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,6,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,7)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,7,1)fail! Drv_InternalSetStpPort: call Hal_GetStpPortState fail! Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(9,16)fail! Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(8,16,1)fail! Drv_

I'd like to know which could be the reason for this out put and what could i do about it.

Tks...

I have 3 clients all running Watchguard Fireboxes, Watchguard APs, and HP switches. 2 of the clients have 1920s, one has a 5130. The two 1920 clients have VLAN1 default corp lan and VLAN20 for guest wifi. The 5130 client has 6 VLANs...1corp/lan, 20guest, 30 production network, 40 redundant ISP from remote site 1, 50 voip, 60 remote site 1-fiber, 70 remote site 2-fiber.

The VLANs are created on the Watchguard Fireboxes except for clientwith 5130...it only has 1, 20, and 30 configured...40, 50, 60, 70 are not created on their Firebox yet.   Corp and Guest VLANS at all three clients have DHCP enabled on them in the Fireboxes.

Both 1920 switches have all ports untagged VLAN1. Port 24 of each switch goes to Firebox and is set for 1T/10U/PVID1/Trunk. Each switch port that has an AP plugged in to it is set as 1T/10U/PVID1/Trunk. If I log in to guest wireless I do not get an IP from the DHCP Server on VLAN20.  I have webGUI access to these switches via a remote machine at these sites, but have not tried configuring SSH/Telnet in webGUI to see if I can putty in to them from those remote machines.

The 5130 site has witch port 24 to Firebox set as Trunk/PVID1/Permit1,20,30,50,60,70 and everything else default...clients on VLAN1 can't get out to internet or ping router so I had to plug router in to another temporary port(default pvid1/access) to get them online and talking to the router. Switch port 23 to AP is Trunk/PVID1/Permit20 and everything else default...guest wireless clients not getting DHCP.  Switch fiber port 25 is remote site 1 and is Trunk/PVID1/Permit-1,20,50,60. Switch fiber port 26 is remote site 2 and is Trunk/PVID1/Permit-1,20,40,70.  Both those sites have internet connectivity.  The goal for those sites is separate VLANs from everything, but connectivity to the shared domain controller/fileserver on VLAN1.  The fact these two seem to work, yet their VLANs aren't yet configured in the Firebox, is odd and perhaps a hint at what might be wrong?  I have webGUI access via a remote machine at this site, enabled SSH and telnet to use putty from that remote machine, but ssh unexpectedly closes after login and telnet connects and immediately says failed login and I can't figure out why.

I do not have physical access to the sites with 1920 switches.  I have limited access to the site with the 5130 and major changes needed to be performed after hours and scheduled in advance.

Could an admin please move this post to the appropriate section?  For some reason it ended up under Legacy and these are currently offered products.  Thanks.

Is your HPE OfficeConnect 1920 Switch (JG920A) able to run correctly or not? it's not clear if those messages are boot warnings only or a signal that something worst happened...do you have access to it via Console? do you reach its Boot Menù? what do you see exactly since you power it on? are you able to manage it through its Web GUI or what? which firmware version was/is it running on?

I'm not sure if I understand this:
1T/10U/PVID1/Trunk

Does that mean you have PVID set to 1 but you have VLAN 10 set as untagged? I'm not even sure the switch would allow you to configure it that way...

You talk about your VLAN configs but your question is about IP connectivity.

You need to explain where each VLANs default gateway is configured in the network and confirm that devices on each VLAN can ping their default gateway.

Once each VLAN has devices on it that can ping their default gateway you can look at your routing - how do the devices get to subnets beyond their own segment - the device that has the default gateway address would need IP forwarding config if the DHCP server is in a different segment, default route to the device that has the internet access, and that device in turn may need a route back to the internal subnet if it isn't on the same segment.

It may be best to break down your question into smaller, simple chunks - for example, let's not talk about 3 networks all at once. Let's just talk about 1 device on one network, the full ip configuration of it and its network infrastructure, DHCP server details and router details. You get that working then you will have a model to follow for the rest.

Hi Parnassus,

Answer your first question, not it isn't able to boot correctly. Yes, I can access to it via console cable and i'm able to access to the boot menu. At the begining i thought it was some kind of issue related with the firmware and i tried changing it for other versions (older and later) but i had no good result. 

Bellow you can see the full output i got. 

I hope you could help me.

Press Ctrl+D to access BASIC-BOOTWARE MENU
Booting Normal Extend BootWare
The Extend BootWare is self-decompressing..........................Done!

****************************************************************************
* *
* HPE 1920-24G Switch JG924A BootWare, Version 1.22 *
* *
****************************************************************************
Copyright (c) 2010-2017 Hewlett Packard Enterprise Development LP

Compiled Date : Apr 14 2017 15:05:19
CPU Type : MIPS4kec
CPU L1 Cache : 16KB
CPU Clock Speed : 500MHz
Memory Type : DDR3 SDRAM
Memory Size : 128MB
Memory Speed : 300MHz
BootWare Size : 3MB
Flash Size : 32MB

BootWare Validating...
Press Ctrl+B to enter extended boot menu...
Starting to get the main application file--flash:/JG924A-CMW520-R1107.bin!.
...........................................................................
.................
The main application file is self-decompressing.............................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
..................................Done!
System application is starting...
System application is starting...RTK API error = 3, file hal/switch/realtek/rtk_drv_acl_839x.c, line = 3934
Hal_SetAclInit failed rv = 193!
RTK API error = 3, file hal/switch/realtek/rtk_drv_mac.c, line = 561
Hal_SetMacInit failed rv = 193!
Hal_SetIPMCInit failed rv = 193!
RTK API error = 3, file hal/switch/realtek/rtk_drv_vlan.c, line = 146
Hal_SetVlanInit failed rv = 386!
Hal_Dot1xInit failed rv = 386!
RTK API error = 3, file hal/switch/realtek/rtk_drv_ratelimit.c, line = 177
Hal_SetRatelimitInit failed rv = 579!
RTK API error = 3, file hal/switch/realtek/rtk_drv_qos.c, line = 155
Hal_SetQosInit failed rv = 772!
Hal_StpInit failed rv = 772!
Hal_I2cFiberInit failed rv = 772!
Hal_GetBoardIdByGpio failed rv = 772!
Hal_PhyRegInit failed rv = 772!
Hal_StormCtl_Init failed rv = 772!
Hal_SetTrapInit failed rv = 772!
Hal_AggrInit failed rv = 772!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1918
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 396
) fail!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651

RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_stp.c, line = 662
Drv_InternalSetStpPort: call Hal_GetStpPortState fail!
Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(1,5)fail!
Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(0,5,3)fail!RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_vlan.c, line = 691
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_stp.c, line = 662
Drv_InternalSetStpPort: call Hal_GetStpPortState fail!
Drv_PortSetStpStateInAllInstances: call Drv_InternalSetStpPort(1,5,0) fail!
Drv_STP_BlockPort: call Drv_PortSetStpStateInAllInstances fail!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
System is starting...
Press Ctrl+D to access BASIC-BOOTWARE MENU
Booting Normal Extend BootWare
The Extend BootWare is self-decompressing..........................Done!

Thanks..!

Hi Parnassus,

Answer your first question, not it isn't able to boot correctly. Yes, I can access to it via console cable and i'm able to access to the boot menu. At the begining i thought it was some kind of issue related with the firmware and i tried changing it for other versions (older and later) but i had no good result. 

Bellow you can see the full output i got. 

I hope you could help me.

Press Ctrl+D to access BASIC-BOOTWARE MENU
Booting Normal Extend BootWare
The Extend BootWare is self-decompressing..........................Done!

****************************************************************************
* *
* HPE 1920-24G Switch JG924A BootWare, Version 1.22 *
* *
****************************************************************************
Copyright (c) 2010-2017 Hewlett Packard Enterprise Development LP

Compiled Date : Apr 14 2017 15:05:19
CPU Type : MIPS4kec
CPU L1 Cache : 16KB
CPU Clock Speed : 500MHz
Memory Type : DDR3 SDRAM
Memory Size : 128MB
Memory Speed : 300MHz
BootWare Size : 3MB
Flash Size : 32MB

BootWare Validating...
Press Ctrl+B to enter extended boot menu...
Starting to get the main application file--flash:/JG924A-CMW520-R1107.bin!.
...........................................................................
.................
The main application file is self-decompressing.............................
............................................................................
............................................................................
............................................................................
............................................................................
............................................................................
..................................Done!
System application is starting...
System application is starting...RTK API error = 3, file hal/switch/realtek/rtk_drv_acl_839x.c, line = 3934
Hal_SetAclInit failed rv = 193!
RTK API error = 3, file hal/switch/realtek/rtk_drv_mac.c, line = 561
Hal_SetMacInit failed rv = 193!
Hal_SetIPMCInit failed rv = 193!
RTK API error = 3, file hal/switch/realtek/rtk_drv_vlan.c, line = 146
Hal_SetVlanInit failed rv = 386!
Hal_Dot1xInit failed rv = 386!
RTK API error = 3, file hal/switch/realtek/rtk_drv_ratelimit.c, line = 177
Hal_SetRatelimitInit failed rv = 579!
RTK API error = 3, file hal/switch/realtek/rtk_drv_qos.c, line = 155
Hal_SetQosInit failed rv = 772!
Hal_StpInit failed rv = 772!
Hal_I2cFiberInit failed rv = 772!
Hal_GetBoardIdByGpio failed rv = 772!
Hal_PhyRegInit failed rv = 772!
Hal_StormCtl_Init failed rv = 772!
Hal_SetTrapInit failed rv = 772!
Hal_AggrInit failed rv = 772!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1918
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 396
) fail!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651

RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_stp.c, line = 662
Drv_InternalSetStpPort: call Hal_GetStpPortState fail!
Drv_Port_SetMstpStateByInstance: call Drv_InternalSetStpPort(1,5)fail!
Drv_Set_MstpPortState: call Drv_Port_SetMstpStateByInstance(0,5,3)fail!RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_vlan.c, line = 691
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1651
RTK API error = 3, file hal/switch/realtek/rtk_drv_stp.c, line = 662
Drv_InternalSetStpPort: call Hal_GetStpPortState fail!
Drv_PortSetStpStateInAllInstances: call Drv_InternalSetStpPort(1,5,0) fail!
Drv_STP_BlockPort: call Drv_PortSetStpStateInAllInstances fail!
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
RTK API error = 3, file hal/switch/realtek/rtk_drv_port.c, line = 1702
System is starting...
Press Ctrl+D to access BASIC-BOOTWARE MENU
Booting Normal Extend BootWare
The Extend BootWare is self-decompressing..........................Done!

Thanks..!

Sorry, that was a typo, meant to say 1U/10T/PVID1.

The VLANs are created and assigned an IP in their respective subnets on the Watchguard, so I assume those IPs are the VLAN gateways?  In these VLAN configs on the Watchguard, each VLAN has it's own DHCP server enabled for their respective subnets.  Example - VLAN20 has an interface IP of 192.168.20.5 with DHCP Server enabled with a scope of 192.168.20.100-200.  VLAN20 is added to switch with an interface IP of 192.168.20.10.  Most VLANs will need to communicate with a domain controller/fileserver on the main corporate network/VLAN1 which is 192.168.1.x(main gateway/router/firewall is 192.168.1.1, server is 192.168.1.10, etc).  Guest wireless, or VLAN20, only goes out to the internet and should have no connectivity to anything else in any other VLAN/network.

On Saturday I went on site with the 5180 client and I tried setting an unused switch port as 20U/PVID20/Access and plugged my laptop in to it to see if any VLAN20 traffic was passing and it did not work.  Through a bunch of troublshooting and tests I somehow got everything working, no idea how, I've gone over the conifg numerous times and it doesn't look like I did anything different than before.  Router is plugged in to trunk port 24 of switch, all tagged VLANs appear to be passing traffic, accessing the server on VLAN1, etc.  Need to make sure my inter-vlan traffic/firewall policies are configured correctly, especially to make sure VLAN20/guest wireless is segrated out to the internet, but so far so good.

On the two 1920 clients I still couldn't get VLAN20(tagged) working to get the guest wireles segrated and sent out straight to the internet.  Other than default/cop VLAN1 that is the only VLAN, so the simplest configuration, but it doesn't work for whatever reason.  They're located on the other side of the country so it's not a easy to untag an unsused port for VLAN20 to plug a device in to see traffic and if DHCP works.

Hi,

i'm currently testing a HP 1920S switch and snmp.  Firmware PD.01.07.  I'm using Paessler SNMP tester 5.2.3.

When using the default snmp on the switch (private, public) i can query for example the uptime.  If i however add an extra community with a random name (let's say testro) i can no longer query the switch (i'm getting no response).  The community entry would then be :

community : testro

security : testro

Groupname : defaultread

IP Address : 0.0.0.0.  

Is this expected behaviour?

Ah, i noticed i posted this in the wrong community.  Apologies. 

Still need help on this one