Hi,
Remember that VLAN ID is a Layer 2 (Ethernet) feature. Because you need
to connect to an IP address (Layer 3) on the switch to manage it, you
must connect from an IP address (i.e. your laptop's IP address) in the
same IP network block. In other words, you can't expect to manage from
an IP address *outside* of 192.168.20.x (in your case). You *could*
assign a different management IP address on the switch if you really
need management to be in a different IP network.
Hope this helps,
Frank
On 2022/11/25 10:18, ITEM via Aruba Instant On Community wrote:
> (thanking you for your availability) rewind...
> 1930 8P, I have to use one port as "uplink".
> By convention I use the 8, but any is fine (as long as it works hahahaha).
> Fully understood what you tell me about "trunk", mine was one of the many attempts made.
> I have not assigned ports to TRK1. Trk1, 2, and, 4 are disabled.
> I configured port 8 only (included vlan2, vlan20 and alternating between included and excluded). I see the vlan20 addresses placed elsewhere (192.168.20.205,206,207,208), I don't reach "itself", 192.168.20.211 ... only by putting the laptop on class 192.168.20.x can I go to the switch (192.168.20.211)
> it seems to me such a trivial thing that I just don't understand how it doesn't work (but I have completely lost my lucidity)
>
> ------------------------------
> IT EM
> ------------------------------
> -------------------------------------------
> Original Message:
> Sent: 11-23-2022 08:49 AM
> From: Frank Myhr
> Subject: Copper uplinks 1930
>
> If interface 8 is part of TRK1, then you need to check the VLAN
> configuration of TRK1 -- which overrides that of port 8 as long as it's
> a member of TRK1.
>
> It looks odd to me that your Port Vlanid 2 is different than your
> Untagged Vlan 1 membership... but if you're sending frames tagged with
> vlan 20 (or whatever your management vlan is) then don't think it matters.
>
> Glad your port security is disabled, which as you note is default.
> Another case of poor terminology, imo it should be called "port
> isolation". So that's not the source of your trouble.
>
> ~
>
> My complaint about ambiguous term "trunk" goes to HPE / Aruba, not to
> you. Maddening that they changed its meaning between the 1920 and 1930
> without even noting it.
>
>
> On 2022/11/23 08:20, ITEM via Aruba Instant On Community wrote:
>> Frank, ;) I know I used the term "trunk" improperly.
>> I replicated the setup I usually did for the fiber uplink, on an RJ45 port.
>> I "managed" the port both as an independent port and as a "grouped" port (TRK1 with port 8 as element).
>> I repeat what I consider a strange thing... the switch has a static ip 192.168.20.211, but the management vlan is 20 (v20m).
>> (Vlan Interface Configuration: interface 8 - Port Vlanid 2 - Tagged only - Untagged Vlan 1 - Tagged VLANs 2,20)
>> I reach 192.168.20.205,206,207,208 (the other switches) on ping and on web.
>> I do not resolve and do not ping 192.168.20.211.
>>
>> When he told me about "Security" I imagined that I could have put something "blocking"... I was wrong, all identical to the other configurations (all default).
>>
>> ------------------------------
>> IT EM
>> ------------------------------
>> -------------------------------------------
>> Original Message:
>> Sent: 11-23-2022 07:18 AM
>> From: Frank Myhr
>> Subject: Copper uplinks 1930
>>
>> I think maybe (?) you're having the same confusion I did about Aruba's
>> use of the term "trunk" in the 1930 vs. 1920 switch. AFAICT "trunk" means:
>>
>> 1920: carries more than one vlan (may or may not be a single port or
>> aggregated ports)
>>
>> 1930: aggregates multiple ports (may or may not carry multiple VLANs)
>>
>> When you say "copper upload" I guess you are connecting to and
>> attempting to manage from a 1G RJ45 port. This is the way I manage mine.
>> It works. You have to set up the port's VLANs properly:
>> In VLAN: VLAN Configuration, the row for the "Interface" (port or trunk)
>> you are trying to manage from must have your management VLAN (30) listed
>> in its "Tagged VLANs" column.
>>
>> Another thing to check is Security: Port Security. It must be disabled
>> for the port (or trunk) you are trying to manage from.
>>
>>
>>
>> On 2022/11/23 06:52, ITEM via Aruba Instant On Community wrote:
>>> For the Aruba Instant On 1930 24G/48G switches connected by fiber to each other, I had no problems. I managed the separate management VLAN.
>>> The problem occurs if I want to do the copper upload, without using the SFP port.
>>> Whether with or without "trunk" I don't reach the switch via the web.
>>> I navigate to another vlan, manage the Aruba APs on other VLANs, reach the other switches on the management VLAN... but I can't get to the switch address anymore (obviously with a defined, static IP and belonging to the same class as the other switches)
>>>
>>> ------------------------------
>>> IT EM
>>> ------------------------------
>>> -------------------------------------------
>>> Original Message:
>>> Sent: 11-23-2022 06:32 AM
>>> From: Frank Myhr
>>> Subject: Copper uplinks 1930
>>>
>>> Hi,
>>>
>>> I'm not sure if you're using a 10GBASE-T (or 1000BASE-T) transceiver or
>>> a DAC cable in a SFP+ port? (DAC cable worth a try if possible.)
>>>
>>> I can't answer your exact question, but it is possible to locally manage
>>> a 1930 24G on a VLAN other than 1 from a copper RJ45 port -- that's how
>>> I configured mine.
>>>
>>> I don't think I've tried managing via a SFP+ port. But you've already
>>> confirmed that you can via fiber. I don't see why a DAC cable would be
>>> any different.
>>>
>>> I'd also expect the VLAN setup with copper to be the same as you've
>>> successfully used with fiber.
>>>
>>> Best regards,
>>> Frank
>>>
>>>
>>>
>>> On 2022/11/23 03:10, ITEM via Aruba Instant On Community wrote:
>>>> I apologize in advance if there is already some topic with the same question. I've been going crazy for a few days.
>>>> I have Aruba Instant On 1930 24G/48G connected by fiber and it was not a problem to change management to a different VLAN than 1.
>>>> (no cloud management) The problem comes when I can't do it in fiber but I have to do it as a copper uplink.
>>>> After several attempts (aside from my low skill) I'm "suspecting" that the SFP ports have different handling.
>>>> In the configuration I'm going to do (after putting the swtich on a different network class from the initial one and the same as that of the other switches), I reach the management of the other switches, I don't ping the ip of the just configured switch and I don't I reach the web interface
>>>> For example, if I have 3 vlan (1, 20, 30) and i want to put the management on 30, how should I manage the uplink port (trunk-portgroup, which I do with the fiber connection).
>>>>
>>>> ------------------------------
>>>> IT EM
>>>> ------------------------------
>>>>
>>>>
>>>> Reply to Sender :
https://community.arubainstanton.com/eGroups/PostReply/?GroupId=7&MID=5179&SenderKey=db0aff1a-5371-4b3f-8011-018489ce813a <https: community.arubainstanton.com/egroups/postreply/?groupid="7&MID=5179&SenderKey=db0aff1a-5371-4b3f-8011-018489ce813a">
>
> Reply to Sender :
https://community.arubainstanton.com/eGroups/PostReply/?GroupId=7&MID=5215&SenderKey=db0aff1a-5371-4b3f-8011-018489ce813a>
> Reply to Discussion :
https://community.arubainstanton.com/eGroups/PostReply/?GroupId=7&MID=5215>
>
>
> You are subscribed to "Instant On - Wired" as
fmyhr@fhmtech.com. To change your subscriptions, go to
http://community.arubainstanton.com/preferences?section=Subscriptions. To unsubscribe from this community discussion, go to
http://community.arubainstanton.com/HigherLogic/eGroups/Unsubscribe.aspx?UserKey=47c634a8-152f-490d-a7ba-75ef496c9e34&sKey=KeyRemoved&GroupKey=b8887e96-ceee-4f41-97c2-3e4d2d07e42a.
Original Message:
Sent: 11/25/2022 10:18:00 AM
From: ITEM
Subject: RE: Copper uplinks 1930
(thanking you for your availability) rewind...
1930 8P, I have to use one port as "uplink".
By convention I use the 8, but any is fine (as long as it works hahahaha).
Fully understood what you tell me about "trunk", mine was one of the many attempts made.
I have not assigned ports to TRK1. Trk1, 2, and, 4 are disabled.
I configured port 8 only (included vlan2, vlan20 and alternating between included and excluded). I see the vlan20 addresses placed elsewhere (192.168.20.205,206,207,208), I don't reach "itself", 192.168.20.211 ... only by putting the laptop on class 192.168.20.x can I go to the switch (192.168.20.211)
it seems to me such a trivial thing that I just don't understand how it doesn't work (but I have completely lost my lucidity)
------------------------------
IT EM
------------------------------
Original Message:
Sent: 11-23-2022 08:49 AM
From: Frank Myhr
Subject: Copper uplinks 1930
If interface 8 is part of TRK1, then you need to check the VLAN
configuration of TRK1 -- which overrides that of port 8 as long as it's
a member of TRK1.
It looks odd to me that your Port Vlanid 2 is different than your
Untagged Vlan 1 membership... but if you're sending frames tagged with
vlan 20 (or whatever your management vlan is) then don't think it matters.
Glad your port security is disabled, which as you note is default.
Another case of poor terminology, imo it should be called "port
isolation". So that's not the source of your trouble.
~
My complaint about ambiguous term "trunk" goes to HPE / Aruba, not to
you. Maddening that they changed its meaning between the 1920 and 1930
without even noting it.
On 2022/11/23 08:20, ITEM via Aruba Instant On Community wrote:
> Frank, ;) I know I used the term "trunk" improperly.
> I replicated the setup I usually did for the fiber uplink, on an RJ45 port.
> I "managed" the port both as an independent port and as a "grouped" port (TRK1 with port 8 as element).
> I repeat what I consider a strange thing... the switch has a static ip 192.168.20.211, but the management vlan is 20 (v20m).
> (Vlan Interface Configuration: interface 8 - Port Vlanid 2 - Tagged only - Untagged Vlan 1 - Tagged VLANs 2,20)
> I reach 192.168.20.205,206,207,208 (the other switches) on ping and on web.
> I do not resolve and do not ping 192.168.20.211.
>
> When he told me about "Security" I imagined that I could have put something "blocking"... I was wrong, all identical to the other configurations (all default).
>
> ------------------------------
> IT EM
> ------------------------------
> -------------------------------------------
> Original Message:
> Sent: 11-23-2022 07:18 AM
> From: Frank Myhr
> Subject: Copper uplinks 1930
>
> I think maybe (?) you're having the same confusion I did about Aruba's
> use of the term "trunk" in the 1930 vs. 1920 switch. AFAICT "trunk" means:
>
> 1920: carries more than one vlan (may or may not be a single port or
> aggregated ports)
>
> 1930: aggregates multiple ports (may or may not carry multiple VLANs)
>
> When you say "copper upload" I guess you are connecting to and
> attempting to manage from a 1G RJ45 port. This is the way I manage mine.
> It works. You have to set up the port's VLANs properly:
> In VLAN: VLAN Configuration, the row for the "Interface" (port or trunk)
> you are trying to manage from must have your management VLAN (30) listed
> in its "Tagged VLANs" column.
>
> Another thing to check is Security: Port Security. It must be disabled
> for the port (or trunk) you are trying to manage from.
>
>
>
> On 2022/11/23 06:52, ITEM via Aruba Instant On Community wrote:
>> For the Aruba Instant On 1930 24G/48G switches connected by fiber to each other, I had no problems. I managed the separate management VLAN.
>> The problem occurs if I want to do the copper upload, without using the SFP port.
>> Whether with or without "trunk" I don't reach the switch via the web.
>> I navigate to another vlan, manage the Aruba APs on other VLANs, reach the other switches on the management VLAN... but I can't get to the switch address anymore (obviously with a defined, static IP and belonging to the same class as the other switches)
>>
>> ------------------------------
>> IT EM
>> ------------------------------
>> -------------------------------------------
>> Original Message:
>> Sent: 11-23-2022 06:32 AM
>> From: Frank Myhr
>> Subject: Copper uplinks 1930
>>
>> Hi,
>>
>> I'm not sure if you're using a 10GBASE-T (or 1000BASE-T) transceiver or
>> a DAC cable in a SFP+ port? (DAC cable worth a try if possible.)
>>
>> I can't answer your exact question, but it is possible to locally manage
>> a 1930 24G on a VLAN other than 1 from a copper RJ45 port -- that's how
>> I configured mine.
>>
>> I don't think I've tried managing via a SFP+ port. But you've already
>> confirmed that you can via fiber. I don't see why a DAC cable would be
>> any different.
>>
>> I'd also expect the VLAN setup with copper to be the same as you've
>> successfully used with fiber.
>>
>> Best regards,
>> Frank
>>
>>
>>
>> On 2022/11/23 03:10, ITEM via Aruba Instant On Community wrote:
>>> I apologize in advance if there is already some topic with the same question. I've been going crazy for a few days.
>>> I have Aruba Instant On 1930 24G/48G connected by fiber and it was not a problem to change management to a different VLAN than 1.
>>> (no cloud management) The problem comes when I can't do it in fiber but I have to do it as a copper uplink.
>>> After several attempts (aside from my low skill) I'm "suspecting" that the SFP ports have different handling.
>>> In the configuration I'm going to do (after putting the swtich on a different network class from the initial one and the same as that of the other switches), I reach the management of the other switches, I don't ping the ip of the just configured switch and I don't I reach the web interface
>>> For example, if I have 3 vlan (1, 20, 30) and i want to put the management on 30, how should I manage the uplink port (trunk-portgroup, which I do with the fiber connection).
>>>
>>> ------------------------------
>>> IT EM
>>> ------------------------------
>>>
>>>
>>> Reply to Sender : https://community.arubainstanton.com/eGroups/PostReply/?GroupId=7&MID=5179&SenderKey=db0aff1a-5371-4b3f-8011-018489ce813a</https:>