Quantcast
Channel: Web and Unmanaged topics
Viewing all 1308 articles
Browse latest View live

HPE 1920S JL386A | VLAN, Trunks, DHCP Relay

$
0
0

Hello,

I'm facing a major issue with the new 1920S models.

I'm usually building vSphere hosts connected over trunk with vlan tagging.

The switches also have one trunk for the router/firewall with vlan tagging.

Sometimes it is necessary to connect another trunk port to a poe switch for Access Points or sth like, this trunk is also with vlan tagging.

So I upgraded the device to 2.08 and began to build my config.

I startet with the connectivity, the switch is configured with static ip inside my untagged mgmt vlan.
Gateway is the router/firewall with its interface ip.

After that I started to configure the VLANs, the the port port memberships for each port and trunk.

It seems to work, but it's not...sth. is with the dhcp relay wrong...

On the router/firewall there is a relay for the vlans set, that is pointing to the corporate dhcp server, on that there are the scopes, but no packet is arriving there.

So I started to get deeper inside the switch config, under the routing section I found dhcp relay.
No matter what I'm setting there, it is not relaying the requests.
At first I tried to set the global setting, I enabled the Admin Mode (?) - and added the corporate dhcp server IP.

After that I tried to setup the vlan/interface configuration inside the DHCP Relay section.
I'm trying to add the corporate dhcp server ip for the VLAN-XXX - once in the dropdown for the vlan-interface I could select all vlans i got, by now I can select only one and this is not the one which is not workling.

The routing section itself is a little bit confusing as well, since it is a layer 3 switch, I get the point, but this is some which I don't want to use, since I have a router in my network.
But here I needed to configure the function, that I can connect to the switch from another VLAN, than the MGMT? VLAN/Interface Configuration in Routing\Configuration section...

In the IPv4 Routing it gets more confusing, I configured the gateway in step one and did not configure any other route for the switch, but in the route table the switch has one route for one of the vlan-subnets which is pointing to the switch internal ip of this subnet as next hop and not the gateway ip address...so where is this route comming from?

I hope you can help me with the exact configuration of this device.

Thanks

Lukas


HPE 1920-48G-PoE+ (370W) QOS BEHAVIOR dot1p and DSCP not available

$
0
0

Hello

I'am sorry for my english...

I have 1920 series hp switch. With 24 ports i can chose dot1p and dscp for the behavior of qos policy but i can't with the 48 ports. I've tried in web and in command line. Options are noe available. How can i do ?

It is to video traffic optimization.

Thanks

V1920 switches and changed default vlan

$
0
0

Hi all,

have two procuve V1920-48G switches, have done this simple setup.

VLAN 1 Default VLAN

VLAN 2 LAN

VLAN 200 PRIVATE LAN

Have made the ports connecting the two hybrid, with vlan 2 untagged and vlan 200 tagged.

I have selected so VLAN 1 has NO member on both switches.

But the result is that ports tagged/untagged with vlan 200 works on both sides, but the vlan2 which is ONLY untagged on all ports, does not go from switch 1 to switch 2

When using vlan 1 and deselecting all vlan 2, it works ?!

Odd or just me :-)

 

best regards

Martin  

IRF TRAFFIC VERY SLOW

$
0
0

HI all I have 6 switches connected to irf & two uplink.

Network performance through this stack is very poor.

Regards,

Salim

3COM 3CDSG8/hp v1900 8g

$
0
0

The switch being used lost the image on a power outage.  I have changed the boot area and it appears all areas have lost the image.  I can connect via console but cant seem to get the switch to accept the image I believe to be correct oc801_00_05A.bin 

I am looking for detailed instructions on how to do this.  I realize this is legacy equipment, but the environment I'm in, it is unfortunately necessary.  Thanks in advance.

JE009A ABA vs ABB

$
0
0
Hi, what's the difference between the JE009A switch's ABA and ABB 'tag'?

I've found a similar question on a non-HP forum for another switch, the best guess there was for supported languages, which didn't explain the price difference.

Also, is there a way to find out this ABA/ABB param for a switch (on the web gui or in cli)?

HP1950 broken web interface

$
0
0

I have a stack of 4 HP1950s, two JG962A and two JG963A working together in an IRF stack. All of a sudden the management interface is broken. I can login but after that the menu remains empty only an error window opens with "The data error". (see here)

Looking at all the web requests I see a request to "/wnm/get.j?sessionid=abc" which gets answers with

"rpc-error":
{"/rpc-reply":

and then everythings ends.

I'm quite stuck with this since these things are completely useless without a web interface since CLI is abcent. The only thing I tried so far is cycling the power. Network switching is performing without any issues. From what I can tell these all seem to run firmware version r3115p03.

I'm in the blind here. I'm looking for insights on how to analyze this and what steps to take to get this back to life.
Any insight/advice is apreciated

advanced ACLs example 1920S

$
0
0

Someone can give an example of an ACL that denies IP traffic between two VLANs VLAN 110 and VLAN 130. I have tried to do it using advanced ACL and it has been impossible.
Please help


problems with intervlans communication

$
0
0

hi and sorry for my bad english,

i have some problems of configuration on my new installation.

i have 2 switch (2530 and 1920s) behind a stormshield appliance.

on the old installation we haven't vlan yet, and the old ip configuration is reused in the new configuration for the vlan 1.

i have 3 vlan (1 data, 20 management, 90 visitor), and here is my 1920s configuration :

!Current Configuration:
!
!System Description "HPE OfficeConnect Switch 1920S 48G 4SFP PPoE+ (370W) JL386A, PD.02.06, Linux 3.6.5-a07f8920, U-Boot 2012.10-00118-g3773021 (Oct 11 2016 - 15:39:54)"
!System Software Version "PD.02.06"
!System Up Time "0 days 23 hrs 21 mins 8 secs"
!Additional Packages HPE QOS,HPE IPv6 Management,HPE Routing
!Current SNTP Synchronized Time: SNTP Client Mode Is Disabled
!
network protocol none
network parms 192.168.20.253 255.255.255.0 0.0.0.0
vlan database
vlan 20,90,100
vlan name 20 "MANAGEMENT"
vlan name 90 "INVITE"
vlan name 100 "VOIP"
vlan routing 1 1
vlan routing 20 2
vlan routing 90 3
exit

network mgmt_vlan 20
ip ssh server enable
ip ssh protocol 2
sshcon timeout 30
configure
sntp server "37.187.5.167"
!clock timezone 1 minutes 0
clock timezone id 38
time-range Schedule-1
exit
time-range Schedule-2
exit
ip routing
ip helper enable
ip helper-address 192.168.1.11 dhcp
username "admin" password xxxxxxxxxxxxxxxxxxxxx level 15 encrypted override-complexity-check
no username guest
voice vlan
line console
exit

line telnet
exit

line ssh
exit

port-channel name TRK 1 pont-HP-1920-N1
interface 46
addport TRK 1
exit
port-channel name TRK 2 ROC1
interface 47
addport TRK 2
exit
snmp-server sysname "HP-1920S-N1"
snmp-server location "N1"
snmp-server contact "administrateur"
!
ip access-list DATA
permit ip any any
exit

ip access-list INVITE
permit ip any any
exit

ip access-list MGMT
permit ip any any
exit

ip access-group DATA vlan 1 in 1
ip access-group MGMT vlan 20 in 1
ip access-group INVITE vlan 90 in 1

interface 1
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 2
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 3
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 4
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 5
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 6
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 7
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 8
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 9
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 10
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 11
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 12
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 13
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 14
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 15
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 16
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 17
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 18
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 19
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 20
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 21
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 22
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 23
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 24
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 25
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 26
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 27
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 28
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 29
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 30
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 31
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 32
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 33
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 34
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 35
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 36
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 37
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 38
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 39
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 40
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 41
vlan pvid 100
vlan participation exclude 1,20
vlan participation include 100
exit

 

interface 42
vlan pvid 100
vlan participation exclude 1,20
vlan participation include 100
exit

 

interface 43
vlan pvid 100
vlan participation exclude 1,20
vlan participation include 100
exit

 

interface 44
vlan participation exclude 20
vlan participation include 100
vlan tagging 100
exit

 

interface 45
vlan pvid 90
vlan participation exclude 1
vlan participation include 90
exit

 

interface 48
vlan pvid 20
vlan participation exclude 1
vlan participation include 20
exit

 

interface TRK 1
vlan participation include 20,90,100
vlan tagging 1,20,90,100
exit

 

interface TRK 2
vlan participation include 20,90,100
vlan tagging 1,20,90,100
exit

 

interface vlan 1
bandwidth 10000
routing
ip address 192.168.1.253 255.255.255.0
ip mtu 1500
no ip unreachables
no ip redirects
exit

 

interface vlan 20
bandwidth 10000
routing
ip mtu 1500
no ip unreachables
no ip redirects
exit

 

interface vlan 90
bandwidth 10000
routing
ip address 192.168.90.253 255.255.255.0
ip helper-address 192.168.1.11 dhcp
ip mtu 1500
no ip unreachables
no ip redirects
exit


ip route 0.0.0.0 0.0.0.0 192.168.1.254 10

exit

the ping between vlan1 and 90 work fine but vlan90 won't going out on the web. 

does anyone have some ideas of what i have done wrong?

thanks in advance.

HP 1950 JG961A IP-HELPER

$
0
0

i have a  HP 1950 JG961A and i wish to add a DHCP helper to a vlan.  i can't find an option in the GUI and i can find even less in "xtd-cli-mode".

Infact in xtd, i can display settings but i can't seem to conf t or en .... (i'm no wizard)

 

Please advise how i can complete this task.

 

oc20 config via console port

$
0
0

Hi, i need to turn off the 2.4ghz radio signal in my oc20, i have connected via the console port, but have no options to turn off the 2.4ghz, does anyone know if this is possible or how to do it?

HP 445010-001 | 4 / 16Q Fibre Channel Switch | AG308A

$
0
0

Hi

Is it possible to get hold of the firmware for this switch?

Thanks

HP 1950 JG961A - ACL to vLAN

$
0
0

I have a HP 1950 JG961A and I have created an ACL (v4) in the GUI but I can't see how you append this ACL to a vLAN ??

 

Please advise.

Odd STP related problem in V1910 with a stacked switch

$
0
0
I have a very straightforward network to deal with, a central switch made up of two stacked Edgecore ecs4510-28F switches feeding 11 V1910-48G switches.
The feeds are dynamic, LACP controlled, LAGs of 4*1G fibre SFPs
At the V1910 end the LAGs are made up of ports 49-52.
At the Edgecore end the LAGs are made up of two ports each from each stack half, e g port1+2 in switch1 + port1+2 in switch2.
The topology is a simple and straightforward star, the 4*1G LAGs connect each V1910 directly to the 4510 stack, and there are no other links between switches. The V1910 rj45 ports connect to individual flats, and the risk of a loop to appear between two flats seems minute, even with Apple style ethernet bridges and wifi leakage.

Now to the problem:
If I enable STP on the MSTP global configuration page in more than one V1910, all but one V1910 will eventually be cut off from the 4510stack.
All I do is enable globally, and all else is default.
What could possibly cause this?
There are no superfluous links, and the topology will never change, but I'm still uneasy about turning STP off, which would, I suppose, solve the problem.
What would be your first thought in a situation like mine?

HPE OfficeConnect Switch 1920S JL384A ARP Proxy

$
0
0

Hello, I am new to HP (networking too) and trying setup 1920S switch so pardon me if I ask what I supposed to know.

We own ancient Siemens PLCs with no option of setting gateway. The network setup consists of Kerio Control and one 1920S. I need to access the PLC from VPN client connected to Kerio Control.

I believe that 1920s is supposed to be able to use ARP proxy. But what I read about 1920s seems to be able to ARP proxy only in betwen subnets set directly on the unit. Is that right or is there a chance to make my configuration work?

I must access IP 10.10.10.1 from IP 192.168.124.10. Thanks much for sending me the right direction.

Configuration:
- Kerio Control VPN Client 192.168.124.10
- Kerio Control VPN server 192.168.124.1
- Kerio Control LAN VLAN10 10.10.10.224
- unit 1920s
      routing->configuration->global routing enabled
      routing for VLAN10 enabled and set IP 10.10.10.10, ARP proxy enabled
     default fateway set to 10.10.10.224
PLC 10.10.10.1 (no gateway)


How to create two separate VLANs in HP 1920s POE Switch

$
0
0

Hi,

I have an hpe 1920s poe switch.

My ISP has given me a public IP. ... say- 202.56.230.52  sub : 255.255.255.252 , g/w -202.56.230.51

I want to create two separate vlan ..... say vlan 5 & vlan 6

vlan 5 will assign for lan connection 

vlan 6 will be assign for wi-fi connection. 

So I want to create two separate private ip pool. 192.168.1.0 network 

So tell me how is it possilble . would I have to a trunk port or jus IP route .

 

Tel me

 

P.S. :Mod: Moved as a new topic from following post

Intermittent Latency Issues

$
0
0

Hi Guys,

I am experiencing high latency intermittently in our internal LAN: Please help to resolve:::::

I have configured two 5940 switches in stack. 4*40Gbps ports are used for irf. Stacking is working fine. Three  "HPE OEM ProLiant BL460c Gen9"blade server are integrated with these switch. Six BAGG interfaces are created to integrate the server. Each BAGG interface contains two 40Gbps port(One from switch1 & another from Switch2). All gateways are defined in this switch. When I pinging Server IP from switch getting high latency intermittently for some server IP. If I shut switch-1' port(used in BAGG) getting latency for all server IP. But when shutting switch-2' port(used in BAGG) no latency for all IP.

Means when packet is coming via second switch, getting latency.

I checked by interchanging the cable but still latency is there. Same issue is observed for all six BAGG interface.

IP 10.60.205.1/24 is configured in this switch on interface vlan600. ping response for 10.60.205.16 ::

56 bytes from 10.60.205.16: icmp_seq=16 ttl=64 time=1.516 ms
56 bytes from 10.60.205.16: icmp_seq=17 ttl=64 time=1.464 ms
56 bytes from 10.60.205.16: icmp_seq=18 ttl=64 time=72.630 ms
56 bytes from 10.60.205.16: icmp_seq=19 ttl=64 time=19.773 ms
56 bytes from 10.60.205.16: icmp_seq=20 ttl=64 time=62.238 ms
56 bytes from 10.60.205.16: icmp_seq=21 ttl=64 time=2.343 ms
56 bytes from 10.60.205.16: icmp_seq=22 ttl=64 time=1.600 ms
56 bytes from 10.60.205.16: icmp_seq=23 ttl=64 time=2.292 ms
56 bytes from 10.60.205.16: icmp_seq=24 ttl=64 time=1.522 ms
56 bytes from 10.60.205.16: icmp_seq=25 ttl=64 time=20.496 ms
56 bytes from 10.60.205.16: icmp_seq=26 ttl=64 time=44.124 ms
56 bytes from 10.60.205.16: icmp_seq=27 ttl=64 time=2.002 ms

No latency from 10.60.205.13

56 bytes from 10.60.205.13: icmp_seq=0 ttl=64 time=1.468 ms
56 bytes from 10.60.205.15: icmp_seq=1 ttl=64 time=1.359 ms
56 bytes from 10.60.205.13: icmp_seq=2 ttl=64 time=1.493 ms
56 bytes from 10.60.205.13: icmp_seq=3 ttl=64 time=1.185 ms
56 bytes from 10.60.205.13: icmp_seq=4 ttl=64 time=1.156 ms
56 bytes from 10.60.205.13: icmp_seq=5 ttl=64 time=1.166 ms
56 bytes from 10.60.205.13: icmp_seq=6 ttl=64 time=1.266 ms
56 bytes from 10.60.205.13: icmp_seq=7 ttl=64 time=1.309 ms
56 bytes from 10.60.205.13: icmp_seq=8 ttl=64 time=1.226 ms
56 bytes from 10.60.205.13: icmp_seq=9 ttl=64 time=1.096 ms

<TOR01>display version

HPE Comware Software, Version 7.1.070, Release 2612P02

Copyright (c) 2010-2018 Hewlett Packard Enterprise Development LP

HPE FF 5940 32QSFP+ Switch uptime is 0 weeks, 0 days, 5 hours, 49 minutes

BAG Config::

========

interface Bridge-Aggregation24

description To_Enc_2_VC1_Q1_Q2_External

port link-type trunk

undo port trunk permit vlan 1

port trunk permit vlan 600 to 699

link-aggregation mode dynamic

TEST CASE::

In BAGG 24 port 1/0/19 & 2/0/19 is there. If shut 1/0/9 then latency for all IP. If shut 2/0/9 no latency for all IP. If plug out the cable from 2/0/9 and connect to 1/0/9 no latency is there.

Switch reboot and upgradation is also done but no luck.

HPE 1950 48G 2SFP+ intervlan routing

$
0
0

Hi, 

I have got a network of 9(1950) switches connected in a ring topology. I want the core switch (48 Port 1950 Switch) to do intervlan routing.  I have made vlan interfaces on core swtiches for all vlan and set a static route to the firewall with a priority of 1, but it is not working can some please confirm can 1950 provide intervlan routing ? 

 

I have also set all the edge switches with a static route pointng to the core management vlan interface.

DHCP Snooping basics not work with HPE switches (JG920A,

$
0
0

I use dhcp-server and the output is configured to permanent IP based on  mac-addresses.
dhcp snooping is configured on HPE. one port is trusted and all others are untrusted. This option 82 is turned off completely.
I write down the traffic coming from HPE back to dhcp server with capture tool (Mikrotik) to a file only from this port and with the condition 'port 68'
and see the following picture:
dhcp request as if you are duplicated. I see two packets in a row.
one with the original mac, the second with the HPE mac.

The switch-uplink in this case gives information messages about the need to take action.
Firmware fully updated to Version Release 1120 (2018). DHCP option 82 is not used. DHCP relay is not used.
Behavior on a larger scale is noticeable on the switch HPE 1920 48 ports, 24 ports , etc.

what's happening?
how to configure dhcp snooping simply?

must HPE duplicate DHCP replies ? 

 

I have some text config but it very simple :

 

===============display version===============
===================================================
HPE Comware Platform Software
Comware Software, Version 5.20.99, Release 1120
Copyright (c) 2010-2018 Hewlett Packard Enterprise Development LP
HPE 1920-8G Switch uptime is 0 week, 0 day, 2 hours, 43 minutes

HPE 1920-8G Switch
128M bytes DRAM
32M bytes Flash Memory
Config Register points to Flash

Hardware Version is Ver.A
Bootrom Version is 122
[SubSlot 0] 8GE+2SFP Hardware Version is Ver.A

==========================================================
===============display device verbose===============
==========================================================
Slot 1
SubSNo PortNum PCBVer FPGAVer CPLDVer BootRomVer AddrLM Type State
0 10 Ver.A NULL 000 122 IVL SMBS10 Normal
Slot 1 info:
Status : Normal
Type : SMBS10
Software Ver : Release 1120
PCB Ver : Ver.A
FPGA Ver : NULL
BootRom Ver : 122
CPLD Ver : 000
PortNum : 10
Chip : 0
Learning Mode: IVL
=================================================================
===============display current-configuration===============
=================================================================
#
version 5.20.99, Release 1120
#
sysname HP 1920G Switch
#
clock timezone Moscow add 03:00:00
#
domain default enable system
#
ipv6
#
telnet server enable
#
web idle-timeout 30
#
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 admin
password cipher $c$3$2XXXXXXXXXXXXXXXXXXXXXXXXXX
authorization-attribute level 3
service-type telnet terminal
service-type web
#
stp mode rstp
stp enable
#
interface NULL0
#
interface Vlan-interface1
ip address 192.168.24.4 255.255.252.0
#
interface GigabitEthernet1/0/1
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/2
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/3
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/4
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/5
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/6
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/7
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/8
loopback-detection enable
port auto-power-down
stp edged-port enable
undo lldp enable
dhcp-snooping trust
#
interface GigabitEthernet1/0/9
loopback-detection enable
stp edged-port enable
#
interface GigabitEthernet1/0/10
loopback-detection enable
stp edged-port enable
#
dhcp-snooping
#
ip route-static 0.0.0.0 0.0.0.0 Vlan-interface1 192.168.24.1
#
info-center loghost 192.168.4.104
undo info-center logfile enable
#
ntp-service source-interface Vlan-interface1
ntp-service unicast-server 192.168.4.4
#
ssh server enable
#
load xml-configuration
#
user-interface aux 0
authentication-mode scheme
user-interface vty 0 15
authentication-mode scheme
#
return
===============================================================
===============display saved-configuration===============
===============================================================
#
version 5.20.99, Release 1120
#
sysname HP 1920G Switch
#
clock timezone Moscow add 03:00:00
#
domain default enable system
#
ipv6
#
telnet server enable
#
web idle-timeout 30
#
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 admin
password cipher $c$3$XXXXXXXXXXx
authorization-attribute level 3
service-type telnet terminal
service-type web
#
stp mode rstp
stp enable
#
interface NULL0
#
interface Vlan-interface1
ip address 192.168.24.4 255.255.252.0
#
interface GigabitEthernet1/0/1
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/2
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/3
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/4
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/5
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/6
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/7
loopback-detection enable
port auto-power-down
stp edged-port enable
#
interface GigabitEthernet1/0/8
loopback-detection enable
port auto-power-down
stp edged-port enable
undo lldp enable
dhcp-snooping trust
#
interface GigabitEthernet1/0/9
loopback-detection enable
stp edged-port enable
#
interface GigabitEthernet1/0/10
loopback-detection enable
stp edged-port enable
#
dhcp-snooping
#
ip route-static 0.0.0.0 0.0.0.0 Vlan-interface1 192.168.24.1
#
info-center loghost 192.168.4.104
undo info-center logfile enable
#
ntp-service source-interface Vlan-interface1
ntp-service unicast-server 192.168.4.4
#
ssh server enable
#
load xml-configuration
#
user-interface aux 0
authentication-mode scheme
user-interface vty 0 15
authentication-mode scheme
#
return
=====================================================

OfficeConnect 1950 (JH295A) no web access after firmware upgrade

$
0
0

Hi,

I've updated the firmware of JH295A, now when I try to log in I'm seeing the following message and I can't log in:

Login in failed, please check your network, or the HTTPS service is enable

 

I'm not sure what's wrong and sometimes I can connect to 443 and sometimes I can't, thanks!

Viewing all 1308 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>