Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

Cisco 3020 Blade Switch for HP Blade Server

What is the best practice for managing these switches?

1) Give the fa0 interface an IP address


2) Give VLAN 1 an IP Address

What are the advantages / disadvantages of doing one over the other?


Re: Cisco 3020 Blade Switch for HP Blade Server

For management interfaces, it is important that they are always up and reachable. A physical interface goes down when it's link goes down, a vlan goes down only when the last interface (including trunks) in the vlan goes down.

Therefore, you should not want to configure a physical interface, when it goes down, the whole device becomes unreachable for network management.

Using a vlan for this will give you a higher availability and the option to use redundant paths to your NMS.



New Member

Re: Cisco 3020 Blade Switch for HP Blade Server


Thanks. But if the inband network has a problem (for example broadcast storm) then getting to the 3020 switch via inband may be a problem. But via the OA module in the blade server to the interface fa0 may be more reliable under this circumstance for troublesooting the broadcast storm for example.

Re: Cisco 3020 Blade Switch for HP Blade Server

How often do you really expect to experience a broadcast storm?

In a modern and well designed network, chances for this are minimal so you might be planning for something that will never occur.


CreatePlease to create content