Sei sulla pagina 1di 94

HP Virtual Connect

Technical Overview
Version 2.3

9/28/2012

Hongjun Ma
ISS Infrastructure Architect CCIE#6820
hongjun.ma@hp.com

http://hongjunma.wordpress.com

Disclaimer
This presentation is created to help customers to understand more about HP Virtual Connect
product besides HP official documentations and white papers.
The presentation is solely my personal view and NOT an official HP reviewed/certified Virtual
Connect doc and best practice white paper. For final answers on Virtual Connect and 3PAR for
features and best practice, please consult with your local HP account team and partners and
check official HP documentations.

Revision History

Version

Date

Description

1.0

10/2011

2.0

9/21/2012

VC3.70 new features, Flex10/10D module, new template, fine tune slides

2.1

9/24/2012

Small contents addition, add disclaimer page

2.2

9/25/2012

One correction for n5k config screen capture

2.3

9/28/2012

Added a page for VC CLI network config and corrected link error for 3par direct attach deck

Initial version

Table of Contents
Why Virtual Connect
HP BladeSystem and Virtual Connect H/W Overview
Cabling
Configuration
HA and Redundancy
Server Profile
Virtual Connect Fibre Channel
Virtual Connect Tunnel Network
3.70 New Features Highlights
Common VC Deployment Missteps

Why Virtual Connect

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Why Virtual Connect


LAN/SAN/Server configuration consolidated in single H/W module using unified management console with
role based access control.
Server Profile empowers server admin with virtualized MAC/WWN and NIC/HBAs. Servers can be easily
added, configured, maintained and moved.

Fully support industry standard LAN/SAN protocols simultaneously such as 802.1q trunk, LACP, LLDP, FC,
FCOE, H/W iSCSI and NFS.
Direct storage attach option to eliminate SAN purchase and operation cost.
Virtual Connect is HP flagship I/O solution/strategy for blade servers and where internal investment goes

Quick Comparison Between VC and Blade Switch


Server Profile Layer

FlexNIC
Virtualized WWN/MAC
NIC BIOS Control
vCenter/System Center
Integration
Server Power Control

Network Layer

Unique
Server
features

Spanning tree
VTP
IP Routing
HSRP/VRRP

Network Layer
Vlan, LACP, LLDP, FCOE+FC

Virtual Connect

Vlan, LACP, CDP/LLDP

Blade Switch

Think about Virtual Connect as a two-layer product.


1st layer is a thin layer of networking which include common networking functions like vlan, trunking, link bundling
7

2nd layer is a Server Profile layer, this is the power and unique value for Virtual Connect. This layer provides unique server features

BladeSystem and Virtual Connect


H/W Overview

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

HP BladeSystem C7000 ---Front

10U
16 half-height blades

HP Insight
Display
9

HP BladeSystem C7000 ---Back


Without Virtual Connect

10

With Virtual Connect Consolidation

Cabling Sample: LAN 40Gb, SAN 40Gb


Flex-10 in Bay1
20Gbps

Flex-10 in Bay2
20Gbps

VC-FC in Bay3

VC-FC in Bay4

16Gbps

16Gbps

Redundant Onboard Administrator


For Management
11

Virtual Connect Family


Ethernet

Flex-10/10D

Flex-10

Converged: Ethernet+FC+FCOE

FlexFabric

1/10-F

FC 8Gb 24-port

(FCOE uplink H/W Ready, future


firmware enabled)

FC 8Gb 20-port
Flex-10/10D

12

Native FC

Which Module to Choose


With the newly released Flex-10/10D, for blade 10G connectivity, you are looking
at mainly two ethernet/converged modules.
10G Ethernet module

10G Ethernet Module + FC Uplinks


+ FCOE downlinks

* Future FCOE uplink+ FCOE downlink

VC-FC

FlexFabric

Flex-10/10D

13

10x10G uplink ethernet ports

8x10G uplink ethernet ports

Note:

Currently pure ethernet module. But H/W


is ready for future FCOE uplink and
downlink function with S/W enablement

Left 4 ports can be configured as Native


FC to split FC/Ethernet traffic with FCOE
traffic down to server CNA

For blade using traditional


FC HBA instead of FCOE
CNA, need to use VC-FC
modules

Which Module to Choose?

14

FlexFabric

Flex-10/10D

Flex-10

1/10-F

8G FC 24-port

8G FC 20-Port

10G Eth Uplink

Yes

Yes

Yes

Yes

No

No

10G Eth Downlink

Yes

Yes

Yes

No

No

No

FCOE Uplink

No

H/W Ready

No

No

No

No

FCOE Downlink

Yes

H/W Ready

No

No

No

No

H/W iSCSI

Yes

Yes

Yes

No

No

No

FC Uplink

Yes

No

No

No

Yes

Yes

FC Downlink

No

No

No

No

Yes

Yes

Virtual Connect FlexFabric Module


Fibre Channel Switches
Native FC

Ethernet Switches
Native 10GE

Port 1-4: Configurable as either FC or 10GE


independently per port

Internal
Downlinks

Ethernet
FCOE
H/W iSCSI

Blade Servers
15

Native 10GE or GE

Port 5-8: Ethernet only, 10GE or GE

Virtual Connect Flex-10/10D Module

16

Use it today as pure 10G ethernet module.


FCOE uplink/downlink is H/W ready and can be enabled by S/W in
the future release.
All 10 ports support 1/10G depending on transceivers plug in.
4 internal dedicated 10G stacking links and no more shared
stacking link on X7/X8 as Flex-10!!
Pretty much same price as original Flex-10 module but with more
uplink ports(10 vs 8 of Flex-10). For new deployment, you should
order this module instead of Flex-10.

Virtual Connect Fibre Channel 8G Module 24 ports

17

8x8G FC uplinks to SAN switches


Standard NPIV on FC ports, FC uplinks as N ports
Need this module if you want to do traditional FC HBA instead of FCOE CNA
from blades and need other ethernet modules like Flex-10/10D in I/O bay 1
and 2 for ethernet connectivity

Cabling

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Common VC FlexFabric Cabling: To non-vPC switches


LAN Switch-1
10G Eth Fibre

LAN Switch-2

SAN Switch-1
8G FC Fibre

10G Eth Fibre

PO1

8G FC Fibre

PO2

I/O Bay 1
I/O Bay 3

I/O Bay 2
X1

X2

X5

X6

X1

X2

X5

X6

I/O Bay 4

I/O Bay 5

I/O Bay 6

I/O Bay 7

I/O Bay 8

1G RJ45 Copper
19

SAN Switch-2

Mgmt Switch-1

1G RJ45 Copper

Mgmt Switch-2

Common VC FlexFabric Cabling: To vPC-like switches


LAN Switch-1
vPC/IRF/VSS like

LAN Switch-2

SAN Switch-1

SAN Switch-2

8G FC Fibre

10G Eth Fibre

8G FC Fibre

10G Eth Fibre

PO1

PO2

I/O Bay 1
I/O Bay 3

I/O Bay 2
X1

X2

X5

X1

X2

X5

X6

I/O Bay 4

I/O Bay 5

I/O Bay 6

I/O Bay 7

I/O Bay 8

1G RJ45 Copper
20

X6

Mgmt Switch-1

1G RJ45 Copper

Mgmt Switch-2

Configuration

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

All You Need to Config: A Trunk and A Profile


Switch (Cisco/HP/Juniper/Extreme)
1. Create a Trunk

Vlan100
Vlan101

LACP

Uplink Ports

Virtual Network Name: Vnet100


Vlan id: 100

10

11

12

13

14

15

16

Virtual Connect

2. Create a Profile

22

Virtual Network Name: Vnet101


Vlan id: 101

Downlink Ports

Untagged

Tagged: vlan100, vlan101

Blade Server: Slot 2

Blade Server: Slot 11

(Windows/Linux)

(Hypervisor)

Network Config: 3 Steps in 1 Page, Done.

Step 1:

Create a Shared Uplink Set(SUS)


SUS == 802.1q Trunk

Step 2:
Assign physical ports to the trunk
LACP automatically enabled

Step 3:
23

Add vlans in the trunk

Server Config: 3 Steps in 1 Page, Done.

Step 1:
Create a Server Profile
A profile mapped to a real server

Step 2:
Assign vlans to server NICs.
Select single vlan for Untagged NIC
Select Multiple Networks for Tagged NIC

24

Trunk and vlans defined


in last page

Step 3:
Assign server profile to real server

Nexus 5K/VC Sample Config and Setup


N5K-1

Eth1/3

VPC

Eth1/4

X1

N5K-2

po1000

vpc peer-link

po1 on N5Ks

po2 on N5Ks

X2

X1

VC-1

d1

Eth1/4

Eth1/3

X2

d1

VC-2

Enclosure Internal Connection


LOM:1

LOM:2

Blade Server in Device Bay 1

25

N5K-1 Configuration
Treat VC ports as host ports.
On switch, configure STP edge
port and BPDU Guard.

Connect with VC-1 X1

Connect with VC-2 X1


26

N5K-2 Configuration
Treat VC ports as host ports.
On switch, configure STP edge
port and BPDU Guard.

Connect with VC-1 X2


27

Connect with VC-2 X2

Virtual Connect/Cisco Terminology Translation

28

Cisco

Virtual Connect

VLAN

Ethernet Network or Virtual Connect Network (Vnet)

Spanning Tree

N/A (VC does not use STP to communicate with network switches)

Access port

Ethernet Network port

Trunk port

Shared Uplink Set(SUS) Port

Port Channel

No need to define a static port channel interface. Ports under one vnet or
SUS will try to negotiate LACP bundle with network switch and generate a
link aggregation group (LAG) ID automatically.

VC-1 Network Config

N5K-1 e1/3

N5K-2 e1/3
You can optionally define
one vlan as native vlan

29

VC-2 Network Config

N5K-1 e1/4

N5K-2 e1/4
You can optionally define
one vlan as native vlan

30

VC-1, VC-2 Network Config in CLI

31

Server Profile Config

vmnic0 ->

Untagged

vmnic1 ->
vmnic2 ->
vmnic3 ->
vmnic4->

Trunk/ Tagged

vmnic5->

Vlans in the trunk

vmhba1 ->
vmhba2->
32

VC SAN Fabrics

HA and Redundancy

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

VC Active/Active Configuration
Switch-1

Switch-2

LACP

LACP

34

Virtual Connect 1

Virtual Connect 2

VC Active/Active Design Redundancy: Normal Condition


Switch-1

Switch-2
Vlan100

VM1

LACP

LACP
Active/Forwarding

Active/Forwarding

Trunk/SUS-1

Trunk/SUS-2

Internal
Cross Link

Virtual Network Name: Vnet100


Vlan id: 100

1
Virtual Connect 2

Only VC internal control


packets will travel
across link

Vlan100

Vlan100

NIC 1
35

Virtual Network Name: Vnet100-2


Vlan id: 100

No vlan100 traffic on
cross link

Virtual Connect 1

VM2

Vlan100

NIC 2

Blade Server: Slot 1

VC Active/Active Design: Failover


Switch-1

Switch-2

LACP

LACP
Active/Forwarding

Trunk/SUS-1

Trunk/SUS-2
Internal
Cross Link

Virtual Network Name: Vnet100


Vlan id: 100

1
Virtual Connect 2

Only VC internal control


packets will travel
across link

Vlan100

Vlan100

NIC 1
36

Virtual Network Name: Vnet100-2


Vlan id: 100

No vlan100 traffic on
cross link

Virtual Connect 1

VM1

Vlan100

VM2

Vlan100

NIC 2

Blade Server: Slot 1

VC Active/Standby Configuration
Switch-1

Switch-2

LACP

LACP

37

Virtual Connect 1

Virtual Connect 2

VC Active/Standby Design Redundancy: Normal Condition


Switch-1

Switch-2

Vlan100

Vlan100

VM2

VM1

LACP

LACP
Active/Forwarding

Trunk/SUS-1

Trunk/SUS-1
Internal
Cross Link

Virtual Network Name: Vnet100


Vlan id: 100

NIC 1

1
Virtual Connect 2

VC internal control
packets will travel cross
link as well

Vlan100

Virtual Network Name: Vnet100


Vlan id: 100

Vlan100 traffic can use


cross link if needed to
reach destination.

Virtual Connect 1

38

Standby/blocking

VM2

Vlan100

NIC 2

Blade Server: Slot 1

VC Active/Standby Design Failover


Switch-1

Switch-2

Vlan100

Vlan100

Active/Forwarding

VM1

Trunk/SUS-1

Internal
Cross Link

Virtual Network Name: Vnet100


Vlan id: 100

NIC 1

1
Virtual Connect 2

VC internal control
packets will travel cross
link as well

Vlan100

Virtual Network Name: Vnet100


Vlan id: 100

Vlan100 traffic can use


cross link if needed to
reach destination.

Virtual Connect 1

39

Trunk/SUS-1

VM1

LACP

VM2

LACP

Vlan100

NIC 2

Blade Server: Slot 1

Server Profile

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Sample VMware Host Configuration

41

Same Windows Server Configuration

42

How to add extra NICs in Server Profile

Right click the area


and choose Add
Connection

43

Flex NIC

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

FlexNIC and NIC Mapping (One Port Example)


Virtual Connect 1

Virtual Connect 2

Port: d1

Port: d1

1a 1b

1c

1d

2a 2b

2c

2d

Motherboard 10G port: 1

Motherboard 10G port: 2

Blade
1
45

3
0

5
2

7
4

2
6

4
1

6
3

8
5

The Power of FlexNIC (The View of Whole module)


1

Virtual Connect (Interconnect Bay 1)


1

1a 1b 1c 1d

1a 1b 1c 1d

Blade Server
Slot 1

Blade Server
Slot 2

15

16

1a 1b 1c 1d

1a 1b 1c 1d

Blade Server
Slot 15

Blade Server
Slot 16

One Flex-10 or FlexFabric offers up to 64 downlinks ports to 16 blade servers


A pair of Flex-10 or FlexFabric offers up to 128 downlinks ports to 16 blade servers
46

Whats Shown on Host OS

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Virtual Connect FlexHBA: VMware ESX 4.0 U2

48

Virtual Connect FlexNIC: VMware ESX 4.0 U2


OS drivers and tools reflect
speeds assigned to FlexNICs
and iSCSI or FCoE FlexHBAs by
VC Manager

49

FlexNIC and FlexHBA in Windows Server 2008

50

FlexNIC in Windows Server 2008

51

VMware vCenter Integration

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

From vCenter, Server Connection View through VC to


Access Switch

Access Switch Layer

Host vSwitch Layer


53

Virtual Connect Layer

Virtual Connect Fibre Channel

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Virtual Connect Fibre Channel


Standard NPIV on FC ports. FC uplink ports are N_Port.
Does not consume a SAN Fabric Domain ID.
Maximum of 255 physical or virtual server HBA ports through each of
the modules uplink ports.
VC 3.70 introduces 3PAR storage direct attach, please see 3.70 new
feature section

55

VC Fibre Channel Configuration

56

Fabric A Configuration

57

Fabric B Configuration

58

Assign HBA1 to Fabric A

59

Assign HBA2 to Fabric B

60

Virtual Connect Tunnel Network

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

A Tunnel VNET is like a Pass-through Cable


LAN Switch
Vlan100
Vlan101

LACP

Virtual Network Name: Vnet-Tunnel-All-Vlans

Tagged: vlan100
vlan101

62

10

11

Virtual Connect

( Its doing 802.1Q-in-Q Vlan TAG internally)

12

13

14

15

16

Tagged: vlan100
vlan101

Blade Server: Slot 2

Blade Server: Slot 11

(Windows/Linux)

(Hypervisor)

Virtual Connect

When to Use a Tunnel vNET


Most of VC deployment uses Mapped mode, which is the default mode. Tunnel mode can
be a good option if you have the following scenario

Many(usually over hundreds) vlans need to be passed to server NICs

All servers in the enclosure want to receive all of these vlans

Tunnel mode uses 802.1q Tunneling method internally. It behaves like a pass-through
module with the benefit of port aggregation.
Note: A Tunnel vNET needs dedicated uplink so its mutually exclusive with Shard Uplink
Set concept.
63

Combine Tunnel vNET with Share Uplink Set(SUS)


Option 1

Option 2

Physical Switch
Trunk 2
Vlan 200-300

Trunk 1
Vlan100
Vlan101
Vlan102

Trunk 2
Vlan 200-300

Trunk 1
Vlan100
Vlan101
Vlan102

SUS1
vnet100

Physical Switch

SUS1

vnet102

vnet100

vnet102

vnet-tunnel
vnet101

vnet-tunnel
vnet101

Virtual Connect

Vnet100
(vlan100)
untagged
NIC 1

Vnet101
(vlan101)
untagged
NIC 2

Vnet102
(vlan102)
untagged

NIC 3

Vnet-tunnel(Vlan200-300)
tagged
NIC 4

Blade Server 1
64

Virtual Connect

Vnet100(vlan100) untagged
Vnet101(vlan101) tagged
Vnet102(vlan102) tagged
NIC 1

Vnet-tunnel(Vlan200-300)
tagged
NIC 2

Blade Server 1

Define a Tunnel vNET

65

3.70 New Features Highlights

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Virtual Connect Recent Releases


09/2011

01/2012

3.30

3.51

Monitoring CLI Enhancement


NAG(Network Access Group)

BL 460 Gen8 support

06/2012

3.60
Bl420Gen8, BL465Gen8
support

09/2012

3.70
3PAR Storage Direct Attach
Flex-10/10D support

Merge Mapped/Tunnel mode

Manageability enhancement

Increased Vlan capacity

BL660Gen8, WS460Gen8 support

TACACS+/Radius support

Feature Release
Bug Fix Release

67

FlexFabric Direct Attach to HP 3PAR


Storage Array

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Virtual Connect Direct Attach to 3PAR Storage


VC FlexFabric module can directly attach 3PAR storage without SAN switches to save SAN H/W and
management cost.
FlexFabric module implements simplified SAN fabric services like automatic zoning and name
services.
You can still connect FlexFabric uplinks to SAN switch for traditional SAN fabric service. It can coexist with the new direct attach connection.
Requirements:
The feature is only available for VC FlexFabric module with VC3.70 and later.
It only supports HP 3PAR(V,T and F-series) storage with Inform OS 3.1.1 MU1 and later.
Other storage arrays support may be planned in the future
Recommended Links For Virtual Connect Direct Attach Implementation:
Virtual Connect Fibre Channel Cookbook
Virtual Connect 3.70 User Guide
3PAR VMware Implementation Guide
69

3PAR vSphere 5 Best Practice

Virtual Connect Fibre Channel Connectivity Supported


Before 3.70: Option 1
After 3.70: Option 1 OR Option 2 OR Option1+Option2
Option 2: Direct Attach

Option 1: Fabric Attach

With 8:1
oversubscription

3PAR V800 supports up to 192 FC host ports. This means that 48 enclosures
70

can be connected to a single 3PAR when using 4 FC uplinks per enclosure

Direct Attach Fabric Demo Topology


Port 1/2/3 PWWN
21230002AC00159E
Port 0/2/3 PWWN
20230002AC00159E

Port 0/2/2 PWWN


20220002AC00159E

1
2

Controller
Node 0

3PAR V400 NWWN


2FF70002AC00159E

Controller
Node 1

Port 1/2/2 PWWN


21220002AC00159E

X1 X2

X1 X2

IO Bay 1

IO Bay 2
Fabric A

Fabric B

d3
71

vmhba1 pwwn
50060B0000C26600

d3
FCOE

FCOE

Blade 3(ESXi5.0)

vmhba2 pwwn
50060B0000C26602

All You Need for Redundant SAN Fabric Configuration!

Fabric A

Fabric B

72

How to Config and Monitor Direct Attach Storage


Please check this Presentation:

Virtual Connect 3PAR Direct Attach Config Walkthrough

73

3.70 Other Features


Note:

Not all new features are listed, please check VC3.70 Release Notes and User Guide for complete list.

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

GUI Interface Throughput Display

75

Port Channel Statistics

76

FlexNIC Statistics(GUI and CLI)

77

LLDP Display Enhancement


VC Before 3.70

VC after 3.70

Change module
name for lldp
display

78

Show MAC in GUI and CLI Enhancement

79

IGMP Multicast Group in GUI

80

FC Port Stats on FlexFabric Module

Interface TX/RX rate

81

FC/FCOE Downlink SAN Uplink Port Field

82

Shown which uplink port in


SAN fabric is used for login

Factory Default MAC/WWN Display

Now can show burn-in MAC/WWN

83

GUI/CLI Activity Status

Activity Indicator supported for these operations:

84

Enclosure Import
Enclosure Recovery
Server Profile Operations
Module Recovery
Persist Configuration

Nexus5000/5500 FlexFabric 8G FC Connection


Support
Now you can connect VC FlexFabric module with Nexus5000/5500 with 8G FC connection
Before 3.70, only 4G FC Connection is supported.
Best Place to check details is this PDF file on HP SPOCK( Single Point of Connectivity Knowledge for HP Storage Products) page

85

Cisco Twinax Cables Supported as of 3.70

86

Description

Cisco Part Number

Cisco 3-m 10G SFP+ Twinax cable assembly

SFP-H10GB-CU3M

Cisco 5-m 10G SFP+ Twinax cable assembly

SFP-H10GB-CU5M

Cisco 7-m 10G SFP+ Twinax cable assembly

SFP-H10GB-ACU7M

Cisco 10-m 10G SFP+ Twinax cable assembly

SFP-H10GB-ACU10M

Common VC Deployment Missteps

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Not All Uplinks Are Active

If you want to have all uplinks active across VC modules, define two
trunks(SUS) , one for each VC module. See Sample Config
88

FlexFabric X1-X4 Port LED Amber Flashing with FC Cables

By default, FlexFabric module X1-X4 are


configured as ethernet ports. With FC
cables/transceivers connected, the port status
will show amber flashing due to incompatibility.
Users should define a SAN fabric in VC Manager
and assign the port to the fabric, the port will
come up green.
For details, please check VC Setup and
Installation Guide.
89

Trying to use FlexFabric X1-X4 as FCOE uplink


FCOE Switch

FlexFabric port X1-X4 can be configured as native FC ports but NOT FCOE ports. FlexFabric implements
FCOE in its downlink to blade CNA adapters.

90

Getting Stacking Error Alarm in VC Manager


LAN Switch

For FlexFabric and Flex-10: Do NOT plug any transceivers in X7 and X8 at the same time. X7/X8 are VC
internal horizontal stacking links. You can use either X7 or X8, just dont use both of them at the same
time(unless you use other ports and connect horizontal modules externally).

91

For Flex-10/10D: No such restriction, you can use all 10 uplink ports at the same time. Flex-10/10D has
dedication internal stacking link.

Getting Stacking Error Alarm in VC Manager

If you have multiple VC Ethernet


modules(Flex10/10D, FlexFabric, Flex10, 1/10F)
in one enclosure, you need to vertically stack
them together.
This is required for VC internal control/synching.
Not following this rule is not a HP supported
config.
For details, please check VC Setup and
Installation Guide and search stacking.

92

Stacking VC in Multi-enclosures, Is It Dual-Ring Topology?

Do you know for VC stacking in multi-enclosure,


HP recommends dual-ring topology like red
lines in this diagram for best redundancy.

For details, please check VC Fibre Channel


Cookbook and VC Setup and Installation Guide.

93

Thank you

Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Potrebbero piacerti anche