Problem with Vlan Trunk on a HP c-Class GbE2c Switch on Chassi HP C7000

[Compuword]

good evening,

I have an HP C7000 chassis with an HP c-Class GbE2c Switch, but I am having difficulties in trunking the ports for different vlans used

https://imgur.com/gallery/tHyh9v0

my problem is that I can't leave the ports with more than one vlan active, in this case it's just tests, and I created a vm in each vlan

Vlan 1 - vm test 1 with ip 192.168.0.2/24
vlan 10 - vm test 10 with ip 172.16.10.2/24
vlan 20 - with ip 172.16.20.2/24
and vlan 30 - vm test 30 with ip 172.16.30.2/24

the vlans are on ports 2 and 3 simultaneously, I don't have LACP on the active ports, and I don't intend to use it, I will make use of RDMA.
My environment is Windows Server 2022 Datacenter

my router is in vlan 1
my goal is to get the routing between the vlans along with the communication between them, even if I use or create new vms on other ports, they must communicate through the Trunk port

this is a web view of my swicth:

https://imgur.com/gallery/A6gDS8d

Current configuration:
!
version "5.2.23"
switch-type "GbE2c L2/L3 Ethernet Blade Switch for HP c-Class BladeSystem"
!
system timezone 156
! America/Brazil/S-&-SE
!
ssh scp-enable
ssh enable
!
access https enable

no system dhcp
!
interface GigabitEthernet 1
tagging
pvid 10
exit
!
vlan 1
member 1

member 2
member 3
member 4
member 5
member 6
member 7
member 8
member 9
member 10
member 11
member 12
member 13
member 14
member 15
member 16
member 17
member 18
member 20
member 21
member 22
member 23
member 24
!
vlan 10
enable
name "iSCSI"
member 1
!
vlan 20
enable
name "VPN"
member 1
!
vlan 30
enable
name "RR"
member 1
!
spanning-tree stp 1 vlan 1
spanning-tree stp 1 vlan 10
spanning-tree stp 1 vlan 20
spanning-tree stp 1 vlan 30

!

logging host 1 address 192.168.0.3
!
ufd enable
!
interface ip 10
ip address 172.16.10.2 255.255.255.0
enable
vlan 10
exit
!
interface ip 20
ip address 172.16.20.2 255.255.255.0
enable
exit
!
interface ip 30
ip address 172.16.30.2 255.255.255.0
enable
exit
!
interface ip 256
ip address 192.168.0.2 255.255.255.0 

enable
exit
!
ip gateway 4 address 192.168.0.1
ip gateway 4 enable
!
ip routing
!
ip dns primary-server 192.168.0.3
ip dns secondary-server 1.1.1.1
ip dns domain-name cpw.local
!
router ospf
enable
!
area 0 enable
area 0 area-id 0.0.0.0
area 0 type transit
area 0 stub-metric 1
no area 0 authentication-type
area 0 spf-interval 10
! 

router rip
enable
!
end

[Compuword]

Hi, i read my config on my switch and post it:

my Swicth is Enterasys C3g124-48 Gigabit Switch Layer 3.

my blade switch is conecct on ports 39,40,41,42,43 on enterasys, and conecct to portas 1,2,3,4,5 of HP blade switch

This is my Running-config of my Switch:

show running-config
ip igmp
!
ip route 0.0.0.0 0.0.0.0 10.254.254.1
!
interface vlan 1
ip address 1192.168.0.254 255.255.255.0
no shutdown
interface vlan 10
ip address 172.16.10.254 255.255.255.0
no shutdown
interface vlan 20
ip address 172.16.20.254 255.255.255.0
no shutdown
interface vlan 30
ip address 172.16.30.254 255.255.255.0
no shutdown

>show vlan
VLAN: 1 NAME: DEFAULT VLAN
VLAN Type: Default
Egress Ports
ge.1.1, ge.1.3, ge.1.5, ge.1.7-8, ge.1.10, ge.1.13, ge.1.18, ge.1.20, ge.1.23, ge.1.37, ge.1.39-43, ge.1.45-47
Forbidden Egress Ports
None.
Untagged ports
ge.1.1, ge.1.3, ge.1.5, ge.1.7-8, ge.1.10, ge.1.13, ge.1.18, ge.1.20, ge.1.23, ge.1.37, ge.1.39-43, ge.1.45-47

VLAN: 10 NAME: Rede iScsi
VLAN Type: Permanent
Egress Ports
ge.1.39-43
Forbidden Egress Ports
None.
Untagged ports
None.

VLAN: 20 NAME: Rede VPN
VLAN Type: Permanent
Egress Ports
ge.1.39-43
Forbidden Egress Ports
None.
Untagged ports
None.

VLAN: 30 NAME: servidores
VLAN Type: Permanent
Egress Ports
None.
Forbidden Egress Ports
None.
Untagged ports
None.

[MV3]

Hello,

Good day!

From the output shared above all the port are enabled and up. 

I suspect this to be a configuration issue, please refer to the below link and recheck the configuration.

Link : https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c00767439

Refer Trunk configuration

Cheers 

[Compuword]

@MV3 

Bom dia, conseguiu chegar a uma comunicação maior através do problema, conseguiu obter mais detalhes e obter detalhes de produto, mas ainda não conseguiu obter uma comunicação entre como v e detalhes de produto, ainda não conseguiu obter uma comunicação grande entre como v.

Antes de mais nada, vou fazer um breve resumo do que fiz até agora:

Mudei o formato de inicialização para bladeos-cli, pois encontrei uma boa documentação usando esta CLI.

HPE_c00767439_HP GbE2c Ethernet Blade Switch para C-Class BladeSystem ISCLI Reference Guide.pdf - Página 13

Switch(config)# boot cli-mode bladeos-cli

Switch# copy run start
Switch# restart

Após a reinicialização, acesse o switch resetei a configuração para fábrica e aplique esta configuração:

324170.pdf - Página 18

=> Configuração pendente
/c/port 17
e em

/c/porta 18
em diante

/c/l2/vlan 1
def 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21 22 23 24

/c/l2/vlan 10
def 0
<= Configuração atual
/c/l2/vlan 10
def 17 18

=> Configuração pendente
/c/l2/vlan 20
def 0
<= Configuração atual
/c/l2/vlan 20
def 17 18

=> Configuração pendente
/c/l2/vlan 30
def 0
/c/l2/mrst/cist/port 21/off
/c/l2/mrst/cist/port 22/off
/c/l2/stp 1/off
<= Configuração atual
/c/l2/vlan 30
def 17 18

=> Configuração pendente
/c/l2/stp 2/off
/c/l2/stp 2/port 1/cost 100
/c/l2/stp 3/off
/c/l2/stp 4/off
/c/l2/stp 5/desligado
/c/l2/stp 6/desligado
/c/l2/stp 7/desligado
/c/l2/stp 8/desligado

/c/l2/trunk 1
rem 17
rem 18
adicionar 20
adicionar 21
adicionar 22
adicionar 23
adicionar 24
/c/l2/trunk 2
e em
adicionar 1
adicionar 2
adicionar 3
adicionar 4
adicionar 5
/c/l2/trunk 3
e
adicionar 17
adicionar 18
/c/l2/tronco 4
e em
adicionar 6
adicionar 7
adicionar 8
adicionar 9
adicionar 10
adicionar 11
/c/l2/tronco 5
e
adicionar 12
adicionar 13
adicionar 14
adicionar 15
adicionar 16

desta forma, você percebe que o trunk foi criado, para conectar uma vm no primeiro blade e colocar a tag na porta vlan como 10 no virtualizador, consigo acessar o ip final do roteador final .1.
Mas nos outros blades, não consigo responder o IP 1 final, apesar de ter marcado a porta com a tag vlan10.

No momento, estou procurando mais informações sobre por que não estou obtendo esse acesso.

>> Main# info/l2/vlan
Nome da VLAN Portas de Status
---- -------------------------------- - ----- -------------------------
1 VLAN padrão ena 1-18 20-24

Lembrete: A porta 17 precisa ser habilitada.

Lembrete: A porta 18 precisa ser habilitada.
10 iSCSI ena 17 18
20 VPN ena 17 18
30 RR ena 17 18
4095 Mgmt VLAN ena 19

Altere o ip que era usado para facilitar o teste para 10.254.254.0/24 vlan 1 10.100.100.0/24 - vlan 10 10.200.200.0/24 - vlan 20 
vlan 30 sem ip definido

Outras informações importantes mas não relevantes para o caso:
Descobri que em blades g9 preciso atualizar o driver qlogic em modo de segurança para poder virtualizar o adaptador e assim não causar uma tela azul (BSOD), ao tentar ativar RDMA ou até mesmo a placa no hyper-v, após uma atualização do driver, o problema foi resolvido após uma atualização do driver.

Google translated: 

Good morning, managed to get more communication through the issue, managed to get more details and get product details, but still couldn't get a communication between like v and product details, still couldn't get big communication between like v.

First of all, I'll give you a brief summary of what I've done so far:

I changed the boot format to bladeos-cli as I found good documentation using this CLI.

HPE_c00767439_HP GbE2c Ethernet Blade Switch for C-Class BladeSystem ISCLI Reference Guide.pdf - Page 13

Switch(config)# boot cli-mode bladeos-cli

Switch# copy run start
Switch# restart

After the reboot, access the switch and reset the configuration to factory and apply this configuration:

324170.pdf - Page 18

=> Pending configuration
/c/port 17
is at

/c/port 18
on

/c/l2/vlan 1
def 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21 22 23 24

/c/l2/vlan 10
def 0
<= Current configuration
/c/l2/vlan 10
def 17 18

=> Pending configuration
/c/l2/vlan 20
def 0
<= Current configuration
/c/l2/vlan 20
def 17 18

=> Pending configuration
/c/l2/vlan 30
def 0
/c/l2/mrst/cist/port 21/off
/c/l2/mrst/cist/port 22/off
/c/l2/stp 1/off
<= Current configuration
/c/l2/vlan 30
def 17 18

=> Pending configuration
/c/l2/stp 2/off
/c/l2/stp 2/port 1/cost 100
/c/l2/stp 3/off
/c/l2/stp 4/off
/c/l2/stp 5/off
/c/l2/stp 6/off
/c/l2/stp 7/off
/c/l2/stp 8/off

/c/l2/trunk 1
rem 17
rem 18
add 20
add 21
add 22
add 23
add 24
/c/l2/trunk 2
is at
add 1
add 2
add 3
add 4
add 5
/c/l2/trunk 3
and
add 17
add 18
/c/l2/trunk 4
is at
add 6
add 7
add 8
add 9
add 10
add 11
/c/l2/trunk 5
and
add 12
add 13
add 14
add 15
add 16

this way, you can see that the trunk was created, to connect a vm on the first blade and put the tag on the vlan port as 10 on the virtualizer, I can access the final ip of the final router .1.
But on the other blades, I can't answer the final IP 1, despite having tagged the port with the vlan10 tag.

I'm currently looking for more information on why I'm not getting this access.

>> Main# info/l2/vlan
VLAN Name Status Ports
---- -------------------------------- ----- -------- -----------------
1 standard VLAN ena 1-18 20-24

Reminder: Port 17 needs to be enabled.

Reminder: Port 18 needs to be enabled.
10 iSCSI ena 17 18
20 VPN ena 17 18
30 RR ena 17 18
4095 Mgmt VLAN ena 19

Change the ip that was used for easy testing to 10,254,254.0/24 vlan 1 10,100,100.0/24 - vlan 10 10,200.200.0/24 - vlan 20
vlan 30 no ip defined
Other important but not relevant information:
I found that on g9 blades I need to update the qlogic driver in safe mode to be able to virtualize the adapter and thus not cause a blue screen (BSOD), when trying to activate RDMA or even the card in hyper-v, after a driver update, the issue was resolved after a driver update.