Gbe2c layer 2 3 ethernet blade switch настройка web
© 2004, 2006 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation. SunOS™ and Solaris™ are trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
Third edition: December 2006
Рекомендую
Additional references
• HP GbE2c Ethernet Blade Switch for c-Class BladeSystem User Guide
• HP GbE2c Ethernet Blade Switch for c-Class BladeSystem ISCLI Reference Guide
• HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Guide
• HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Browser-based Interface Reference Guide
• HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Quick Setup Instructions
Популярные посты за все время
Хе хе. Я тут овладел новым джедайством (Денис, спасибо за наводку). Посмотрите на эту картинку: На первый взгляд скриншо.
Intel купил McAfee. по рассказам знающих тему все было вот так: - Так. Нам нужен антивирус. Купите кто-нибудь McAfee. Вечером: .
В двойку лидеров по известности среди продуктов VMware входит программа VMware Workstation. Это весьма эффективное средство создания вир.
В vSphere 5 появилась такая штука как Web Client – по сути, старый добрый web-интерфейс, но слегка в новом обличии. Если в тройке и четве.
Последние комментарии
Contents
Command line interface
Connecting to the switch .
Establishing a console connection .
Setting an IP address .
Establishing a Telnet connection.
Establishing an SSH connection .
Accessing the switch .
Command line history and editing.
Command line interface shortcuts.
Configuring Simple Network Management Protocol support .
Changing the default administrator password .
Changing the default user password.
Changing the default operator password .
System Information Menu .
SNMPv3 Information Menu .
SNMPv3 USM User Table information .
SNMPv3 View Table information .
SNMPv3 Access Table information.
SNMPv3 Group Table information .
SNMPv3 Community Table information.
SNMPv3 Target Address Table information .
SNMPv3 Target Parameters Table information .
SNMPv3 Notify Table information.
Show last 100 syslog messages.
System user information .
Layer 2 information .
FDB information menu .
Show all FDB information.
Link Aggregation Control Protocol information .
Spanning Tree information .
Command line interface 3
Rapid Spanning Tree and Multiple Spanning Tree information
Common Internal Spanning Tree information .
Trunk group information.
Layer 2 general information .
Layer 3 information .
Show all IP Route information .
Show all ARP entry information .
ARP address list information .
OSPF general information .
OSPF interface information.
OSPF Database information menu.
OSPF route codes information .
Routing Information Protocol information .
RIP Routes information .
RIP user configuration .
IGMP multicast group information .
IGMP multicast router port information .
RMON Information Menu .
RMON history information .
RMON alarm information .
RMON event information .
Link status information .
Logical Port to GEA Port mapping .
Uplink Failure Detection information .
Port Statistics Menu .
Internet Protocol (IP) statistics .
Port RMON statistics.
Layer 2 statistics.
Layer 3 statistics.
GEA Layer 3 statistics menu .
GEA Layer 3 statistics .
Command line interface 4
IGMP Multicast Group statistics.
OSPF statistics menu.
OSPF global statistics .
Management Processor statistics .
Access Control List (ACL) statistics menu .
Uplink Failure Detection statistics.
Viewing, applying, reverting, and saving changes .
Viewing pending changes.
Applying pending changes .
Saving the configuration .
System host log configuration .
Secure Shell Server configuration .
RADIUS server configuration.
TACACS+ server configuration .
NTP server configuration.
System SNMP configuration .
User Security Model configuration.
SNMPv3 View configuration .
View-based Access Control Model configuration.
SNMPv3 Group configuration .
SNMPv3 Community Table configuration .
SNMPv3 Target Address Table configuration.
SNMPv3 Target Parameters Table configuration.
SNMPv3 Notify Table configuration .
System Access configuration.
Management Networks configuration .
User Access Control configuration.
User ID configuration.
Temporarily disabling a port .
Port link configuration.
Port ACL/QoS configuration.
Layer 2 configuration .
802.1x Global configuration.
Command line interface 5
802.1x Port configuration .
Rapid Spanning Tree Protocol / Multiple Spanning Tree Protocol configuration.
Common Internal Spanning Tree configuration.
CIST bridge configuration .
CIST port configuration .
Spanning Tree configuration.
Bridge Spanning Tree configuration .
Spanning Tree port configuration .
Forwarding Database configuration .
Static FDB configuration.
IP Trunk Hash configuration .
Layer 2 IP Trunk Hash configuration .
Link Aggregation Control Protocol configuration.
LACP Port configuration .
Layer 3 configuration .
IP interface configuration .
Default Gateway configuration .
IP Static Route configuration .
Address Resolution Protocol configuration .
IP Forwarding configuration .
Network Filter configuration .
Route Map configuration.
IP Access List configuration.
Autonomous System Path configuration .
Routing Information Protocol configuration .
RIP Interface configuration.
RIP Route Redistribution configuration .
Open Shortest Path First configuration .
OSFP Area Index configuration.
OSPF Summary Range configuration .
OSPF Interface configuration .
OSPF Virtual Link configuration .
OSPF Host Entry configuration .
OSPF Route Redistribution configuration.
OSPF MD5 Key configuration.
IGMP snooping configuration .
IGMP static multicast router configuration.
IGMP filtering configuration.
IGMP filter definition .
IGMP filtering port configuration .
Domain Name System configuration.
Bootstrap Protocol Relay configuration .
Virtual Router Redundancy Protocol configuration.
VRRP Virtual Router configuration .
VRRP Virtual Router Priority Tracking configuration .
VRRP Virtual Router Group configuration .
VRRP Virtual Router Group Priority Tracking configuration .
VRRP Interface configuration.
VRRP Tracking configuration.
Quality of Service configuration.
QoS 802.1p configuration.
Access Control configuration .
Access Control List configuration.
ACL Ethernet Filter configuration .
Command line interface 6
ACL IP Version 4 Filter configuration.
ACL TCP/UDP Filter configuration .
ACL Meter configuration .
ACL Re-mark configuration .
ACL Re-mark In-Profile configuration .
ACL Re-mark In-Profile Update User Priority configuration .
ACL Re-mark Out-of-Profile configuration .
ACL Packet Format configuration.
ACL Group configuration .
Remote Monitoring configuration .
RMON history configuration.
RMON event configuration .
RMON alarm configuration.
Port-based port mirroring .
Uplink Failure Detection configuration.
Failure Detection Pair configuration .
Link to Monitor configuration .
Link to Disable configuration.
Saving the active switch configuration .
Restoring the active switch configuration .
Operations-level port options .
Operations-level port 802.1x options .
Operations-level VRRP options .
Boot Options Menu
Updating the switch software image .
Downloading new software to the switch .
Selecting a software image to run .
Uploading a software image from the switch .
Selecting a configuration block.
Resetting the switch .
Accessing the ISCLI .
System maintenance options.
Forwarding Database options.
ARP cache options .
IP Route Manipulation options.
IGMP Multicast Group options.
IGMP Snooping options.
IGMP Mrouter options .
Uuencode flash dump.
FTP/TFTP system dump put .
Clearing dump information.
Unscheduled system dumps .
Command line interface 7
Command line interface 8
Like this:
Command line interface
воскресенье, 28 ноября 2010 г.
Подпишись на комментарии
Комментарии
Комментарии
One Response to HP Blade – c3000 – GbE2c interconnection module: configuration Notes – part 3
Hi Marco!
Thanks for your notes! Good help. But I am still puzzled about one problem. Can I ask some further questions ?
Assume you haven’t configured an interconnect GbE2c switch (or in my case a GbE2c L2/3 switch), for example
the switch is brand new and you just plugged it in into the blade enclosure. All downlink and uplink ports are at VLAN 1
and enabled, according to manuals/quick specs.
Assume further that 4 cables are connected from uplink ports 21 – 24 to external switch/switches, which has
it’s (or their) ports as well at VLAN 1 and are enabled (no-shutdown in Cisco terms). And that the blade enclosure is
equipped with a total of 16 blades (G6 or G7, for example), running fine. No mezzanine cards, just the LOM
NIC’s. Assume further that there is no other obstacle(s), or in other words the blades are communicating with
the external switch(es).
(The interconnect GbE2c switch is at interconnect bay 1 in the enclosure.)
So, what I have been puzzled by (and I cannot test), what will I see at the 4 uplink ports towards the external
switches ? Traffic flows, from all blades that for the moment communicate, on all 4 uplink ports/cables, according to
some rule or schema ? If that is the case, what is the rule by which a blade (or interconnect switch) selects on
which uplink port/cable, it will send ? Load balancing ? Round robin ? Random ?
Or will just one uplink port/cable be used for traffic from all 16 blades, even if the other three uplink ports would
also be working ?
Best regards,
Mikael
Популярные посты за месяц
Хе хе. Я тут овладел новым джедайством (Денис, спасибо за наводку). Посмотрите на эту картинку: На первый взгляд скриншо.
Intel купил McAfee. по рассказам знающих тему все было вот так: - Так. Нам нужен антивирус. Купите кто-нибудь McAfee. Вечером: .
Как многие уже слышали, VMware объявила об относительно скором релизе пятой вСферы - в третьем квартале этого года. Уже стали известны по.
С радостью я констатирую тот факт, что практически каждый день мне пишут про мою книгу. В основном - "Где ее можно купить?" С о.
Accessing the switch
• User—User interaction with the switch is completely passive; nothing can be changed on the switch. Users may display information that has no security or privacy implications, such as switch statistics and current operational state information.
• Operator—Operators can only effect temporary changes on the switch. These changes will be lost when the switch is rebooted/reset. Operators have access to the switch management features used for daily switch operations. Because any changes an operator makes are undone by a reset of the switch, operators cannot severely impact switch operation, but do have access to the Maintenance menu.
• Administrator—Only administrators can make permanent changes to the switch configuration, changes that are persistent across a reboot/reset of the switch. Administrators can access switch functions to configure and troubleshoot problems on the switch. Because administrators can also make temporary (operator-level) changes as well, they must be aware of the interactions between temporary and permanent changes.
Access to switch functions is controlled through the use of unique usernames and passwords. Once you are connected to the switch via the local console, Telnet, or SSH, you are prompted to enter a password. The password entered determines the access level. The default user names/password for each access level is listed in the following table.
NOTE: It is recommended that you change default switch passwords after initial configuration and as regularly as required under your network security policies. For more information, see the “Setting passwords” section in the “First-time configuration” chapter.
Hello , I buy an second hand Gbe2c Layer 2-3 Blade switch for my HP C7000 but I cannot login into the configuration because the default admin password is changed.
So simple question , how can I do an factory reset for this switch for getting back the admin default connection ?
- Mark as New
- Bookmark
- Subscribe
- Mute
Do you have the null modem cable with mini adapter to console into the switch?
During startup you can shift-T into the boot menu (it may take a couple of tries to catch it perseverance is key)
Use a password of admin
Look for a conf f option to apply factory default configuration
Issue a reset and allow to restart.
The manuals are still out there if you do some digging from the product pages.
Related links - Tech support / manuals - manuals - have a dig around.
Please make use of the kudos and solved buttons to let others know when posts are helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
Yessss ! It works ! A little bit old school style (TTY lol) but it's working. After couple of try and strange menus (low level menu switch I suppose lol) I can have an access to CLi and doing an factory reset.
Thanks a lot and for information I use this for connexion :
- an USB to RS232 converter (Trendnet TU-S9) with Null modem cable
- COM parameters : 9600bps, 8 Bits, 1 stop, no parity, flow control set to XON/XOFF
- software used : Putty on win seven x64
Direction to use (from other post) :
Reset the switch, while it is performing the memory test (while it is doing the dots) do a T .
The switch will end up in diagnostic mode and prompt you for a password.
Enter "admin" as the password. ("" are not used when entering the password)
From the main menu select boot.
From the boot menu enter "conf f".
You will see the following "Next boot will use switch FACTORY (f) config block".
logical port (known as a dynamic trunk group or Link Aggregation group) with any device that supports the standard.
The 802.3ad standard allows standard Ethernet links to form a single Layer 2 link using the Link Aggregation Control
Protocol (LACP). Link aggregation is a method of grouping physical link segments of the same media type and speed
in full duplex, and treating them as if they were part of a single, logical link segment. If a link in a LACP trunk group
port is operable within a bounded time period between the actor and the partner. Only the Market Responder
A port's Link Aggregation Identifier (LAG ID) determines how the port can be aggregated. The Link Aggregation ID
Admin key—A port's Admin key is an integer value (1-65535) that you can configure in the CLI. Each GbE2c
port that participates in the same LACP trunk group must have the same admin key value. The Admin key is
For example, consider two switches, an Actor (the GbE2c) and a Partner (another switch), as shown in the following
In the configuration shown in the table above, Actor switch ports 20 and 21 aggregate to form an LACP trunk group
with Partner switch ports 1 and 2. At the same time, Actor switch ports 22 and 23 form a different LACP trunk group
LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the
active—The port is capable of forming an LACP trunk. This port sends LACPDU packets to partner system ports.
passive—The port is capable of forming an LACP trunk. This port only responds to the LACPDU packets sent
Each active LACP port transmits LACP data units (LACPDUs), while each passive LACP port listens for LACPDUs.
During LACP negotiation, the admin key is exchanged. The LACP trunk group is enabled as long as the information
matches at both ends of the link. If the admin key value changes for a port at either end of the link, that port's
When the system is initialized, all ports by default are in LACP off mode and are assigned unique admin keys. To
make a group of ports aggregatable, you assign them all the same admin key. You must set the port's LACP mode to
active to activate LACP negotiation. You can set other port's LACP mode to passive, to reduce the amount of LACPDU
Тут собираю интересное по интересующей меня теме виртуализации.
- Главная страница
- Книга по vSphere
- Performance - как правильно мониторить
- VMware Certification
- Курсы VMware
- Подборка важных материалов
Посты по email
VLAN + vSphere Distributed Switch + HP GbE2c Layer 2/3
Мне приходится вести довольно обширную переписку. Угадайте по какой теме :)
Слово “приходится” не означает, что я недоволен – мне нравится такое положение вещей.
Может быть, не всегда есть возможность ответить развернуто, а иногда ответ я и не знаю, но без внимания я не оставляю ни одного письма.
Что меня радует, иногда обращающиеся ко мне специалисты склонны и делиться знаниями. Вот как раз такой случай:
Настройка VLAN на vSphere Distributed Switch и блейд-свитче HP GbE2c Layer 2/3.
Давайте рассмотрим задачу организации сети с несколькими vlan на распределенном свитче.
Когда и кому это может понадобиться?
Представим себе следующий классический вариант – сервер с 2-мя сетевыми адаптерами. Один физический адаптер необходимо зарезервировать под служебные нужды VMWare, такие как Service Console и VMkernel. На базе же второго адаптера мы можем создать только один виртуальный свитч для проброса сети для виртуальных машин. А что делать, если виртуальным машинам необходимо пробросить как минимум две изолированных сети, а то и 3-4.
Ну или другой вариант – пусть мы озаботились заранее и купили сервер с четырьмя сетевыми интерфейсам. Но при постройке среды виртуализации сделали все правильно и один физический адаптер отвели под ServiceConsole, а другой под VMkernel Port. Остается два адаптера для проброса сетей виртуальным машинам. В большинстве случаев этого достаточно. Но вот появляется срочная задача прокинуть еще одну изолированную сеть в виртуальную среду.
Что делать? Пожалуй, самый очевидный и простой вариант – купить сетевую карту и на ее базе создать очередной виртуальный свитч. Но бывают ситуации, когда нет времени на долгий процесс закупки, или нет слотов в сервере под дополнительную сетевую карту и т.п. Вот тут на помощь нам приходят vlan. Именно настройка vlan на виртуальном и физическом свитче позволит вам через один физический интерфейс прокинуть несколько разных сетей виртуальным машинам.
Рассмотрим конкретную практическую задачу.
Есть хост ESX(блейд-лезвие), с четырьмя сетевыми интерфейсам подключенный в блейд-свитч HP GbE2c Layer 2/3. Один интерфейс ESX хоста, как описывалось выше, отведен под Service Console, а второй VMkernel Port для vMotion. Двум оставшимся интерфейсам соответствуют два распределенных свитча Distributed Switch 1&2, позволяющие вывести две группы виртуальных машины в две изолированных сети. Появляется третья группа виртуальных машин, которым необходима третья изолированная сеть. Решено настроить vlan`ы на одном из двух существующих распределенных свитчей.
Дополнительная сеть – это дополнительный трафик. После мониторинга становится понятно, что виртуальный свитч Distributed Switch2 менее нагружен и легко перенесет добавочный трафик, поэтому через него будут проброшены две сети. Distributed Switch 1 конфигурироваться не будет.
*При использовании большого количества vlan, рекомендую мониторить текущую и планировать будущую нагрузку. Можно пробросить несколько сетей с малой нагрузкой через один виртуальный свитч, а второй оставить под сеть с основным трафиком. Если же виртуальные машины генерируют примерно одинаковый трафик в каждую сеть, то следует размазывать нагрузку и конфигурировать по несколько vlan на каждый виртуальный свитч. Всегда помним, что каждый виртуальный свитч опирается на физический интерфейс с ограниченной пропускной способностью.
Теперь о прикладной задаче. При пробросе трех сетей для виртуальных машин это выглядит так:
Настройка очень проста. Каждая группа портов виртуального распределенного свитча, соответствующая отдельной изолированной сети, должна находиться в отдельном vlan`е. Порты-аплинки между свитчами, должны быть сконфигурированы как tagged порты (т.е. могут пропускать через себя трафик разных vlan`ов).
Для распределенного коммутатора Distributed Switch 2 необходимо сделать следующие настройки:
1. Создаем 2-е группы портов на одном распределенном коммутаторе.
2. В настройках 1-й группы портов в пункте VLAN указать VLAN Type = VLAN и задать VLAN ID (для текущего примера VID=6).
3. В настройках 2-й группы портов в пункте VLAN указать VLAN Type = VLAN и задать VLAN ID (для текущего примера VID=5).
4. В настройках Uplink-группы в пункте VLAN указать VLAN Type = VLAN Trunking. В поле VLAN trunk range указать VLAN ID, для vlan, созданных выше.
На этом вся конфигурации виртуальной среды завершена. Остается настроить физический блейд-свитч.
Ниже приведена настройка для свитча HP GbE2c Layer 2/3. Хосты ESX подключены к внутренним портам 1,2,9,10. Порт 21, 23 внешние аплинки в разные сети.
Включаем тегирование и задаем default vlan внутренних портов.
/cfg/port 1
tag e
pvid 5
/cfg/port 2
tag e
pvid 5
/cfg/port 9
tag e
pvid 5
/cfg/port 10
tag e
pvid 5
Создаем Vlan, включаем их, задаем имя и порты
/cfg/l2/vlan 5
ena
name “…”
def 1 2 9 10 21
/cfg/l2/vlan 6
Ena
name “…”
def 1 2 9 10 23
You can configure your module connecting a serial cable, telnetting to it IP address, or accessing the web based management console. I think that the first time you use the module the web gui is the best choiche, and that you’ll prefer the telnet access as soon as you acquire more knowledge on it.
Accessing the Web Management module is really easy: simply select (in my example the module is installed in interconnect bay 1)
HP BladeSystem Onboard Administrator / Enclosure Information / Interconnect Bays / 1. GbE2c Layer 2/3 Ethernet Blade / Management Console
The first thing is certainly having a look to all the ports: click HP c-Class GbE2c Switch / Switch Ports
Notice that port 19 has assigned the management VLAN (4095).
In our example we have some access based VLAN (VLAN 2, 3, 4) assigned to Physical Gbit uplink ports (21,22,34). Each physical port is connected to a separate physical network. As you can see, we have switchport 1 configured with VLAN Tagging enabled – this is mandatory to have it assigned to more than a VLAN: in our example we have a blade on Device bay 1, that must access on its first downlink port VLAN 2,3,4. The only way to accomplish this task is to assign VLAN 2,3,4 to the switchport.
Подпишись на обновления по RSS
Connecting to the switch
You can access the command line interface in one of the following ways:
• Using a console connection via the console port
• Using a Telnet connection over the network
• Using a Secure Shell (SSH) connection to securely log in over a network
Establishing a console connection
To establish a console connection with the switch, you need:
• A null modem cable with a female DB-9 connector (See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem User Guide for more information.)
• An ASCII terminal or a computer running terminal emulation software set to the parameters shown in the table below
Table 1 Console configuration parameters
Command line interface 9
To establish a console connection with the switch:
1. Connect the terminal to the console port using the null modem cable.
2. Power on the terminal.
3. Press the Enter key a few times on the terminal to establish the connection.
4. You will be required to enter a password for access to the switch. (For more information, see the “Setting passwords” section in the “First-time configuration” chapter.)
Setting an IP address
To access the switch via a Telnet or an SSH connection, you need to have an Internet Protocol (IP) address set for the switch. The switch can get its IP address in one of the following ways:
• Management port access:
• Using a Dynamic Host Control Protocol (DHCP) server—When the /cfg/sys/dhcp command is enabled , the management interface (interface 256) requests its IP address from a DHCP server. The default value for the /cfg/sys/dhcp command is enabled .
• Configuring manually—If the network does not support DHCP, you must configure the management interface (interface 256) with an IP address. If you want to access the switch from a remote network, you also must configure the management gateway (gateway 4).
• Uplink port access:
• Using a Bootstrap Protocol (BOOTP) server—By default, the management interface is set up to request its IP address from a BOOTP server. If you have a BOOTP server on the network, add the Media Access Control (MAC) address of the switch to the BOOTP configuration file located on the BOOTP server. The MAC address can be found in the System Information menu (See the “System information” section in the “Information Menu” chapter.) If you are using a DHCP server that also does BOOTP, you do not have to configure the MAC address.
• Configuring manually—If the network does not support BOOTP, you must configure the management port with an IP address.
Establishing a Telnet connection
A Telnet connection offers the convenience of accessing the switch from any workstation connected to the network. Telnet provides the same options for user, operator, and administrator access as those available through the console port. By default, Telnet is enabled on the switch. The switch supports four concurrent Telnet connections.
Once the IP parameters are configured, you can access the CLI using a Telnet connection. To establish a Telnet connection with the switch, run the Telnet program on the workstation and enter the telnet command, followed by the switch IP address:
You will then be prompted to enter a password. The password entered determines the access level: administrator, operator, or user. See the “Accessing the switch” section later in this chapter for description of default passwords.
Establishing an SSH connection
Although a remote network administrator can manage the configuration of a switch via Telnet, this method does not provide a secure connection. The Secure Shell (SSH) protocol enables you to securely log into the switch over the network.
As a secure alternative to using Telnet to manage switch configuration, SSH ensures that all data sent over the network is encrypted and secure. In order to use SSH, you must first configure it on the switch. See the “Secure Shell Server configuration” section in the “Configuration Menu” chapter for information on how to configure SSH.
The switch can perform only one session of key/cipher generation at a time. Therefore, an SSH/Secure Copy (SCP) client will not be able to log in if the switch is performing key generation at that time or if another client has just logged in before this client. Similarly, the system will fail to perform the key generation if an SSH/SCP client is logging in at that time.
Command line interface 10
The supported SSH encryption and authentication methods are listed below.
• Server Host Authentication—Client RSA authenticates the switch in the beginning of every connection
• User Authentication—Local password authentication; Remote Authentication Dial-in User Service (RADIUS) The following SSH clients are supported:
• SSH 3.0.1 for Linux (freeware)
• SecureCRT® 4.1.8 (VanDyke Technologies, Inc.)
• OpenSSH_3.9 for Linux (FC 3)
• FedoraCore 3 for SCP commands
• PuTTY Release 0.58 (Simon Tatham) for Windows
NOTE: The switch implementation of SSH is based on versions 1.5 and 2.0, and supports SSH clients from version 1.0 through version 2.0. SSH clients of other versions are not supported. You may configure the client software to use protocol SSH version 1 or version 2.
By default, SSH service is not enabled on the switch. Once the IP parameters are configured, you can access the command line interface to enable SSH.
To establish an SSH connection with the switch, run the SSH program on the workstation by issuing the ssh command, followed by the user account name and the switch IP address:
You will then be prompted to enter your password.
NOTE: The first time you run SSH from the workstation, a warning message might appear. At the prompt, enter yes to continue.
Обо мне
Все высказанное здесь представлено “как есть” и не предоставляет каких-либо гарантий и прав. Позиция автора может не совпадать с позицией работодателя. Просмотреть профиль
Share this:
Архив блога
Introduction
The HP GbE2c switch is ready to perform basic switching functions right out of the box. Some of the more advanced features, however, require some administrative configuration before they can be used effectively. This guide provides a command reference for the HP GbE2c Ethernet Blade Switch and the HP GbE2c Layer 2/3 Ethernet Blade Switch.
The extensive switching software included in the switch provides a variety of options for accessing and configuring the switch:
• Built-in, text-based command line interfaces (AOS CLI and ISCLI) for access via a local terminal or remote Telnet/Secure Shell (SSH) session
• Simple Network Management Protocol (SNMP) support for access through network management software such as HP Systems Insight Manager
• A browser-based management interface for interactive network access through the Web browser
The command line interface provides a direct method for collecting switch information and performing switch configuration. Using a basic terminal, you can view information and statistics about the switch, and perform any necessary configuration.
This chapter explains how to access the AOS CLI to the switch.
Ярлыки
Читайте также: