- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- Problem to access 2nd GbE2 Interconnect Switch
ProLiant Servers - Netservers
1753412
Members
7343
Online
108793
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2005 04:02 AM
09-16-2005 04:02 AM
Problem to access 2nd GbE2 Interconnect Switch
Configuration :
HP ProLiant BL p-Class with 2 internal GbE2 Interconnect Switch (Copper); code V2.2.0
ports 17 and 18 on both internal switch are up;
The 1st switch is the only one connected to the outside network thru its port 19;
The 2nd switch is not directly connected at all to the outside network (all its ports 19,20,21,22,23,24 are unplugged) ;
Problem :
There is no way to ping this 2nd switch from the 1st switch or from any PC in the outside network;
The 2 switches have an IP interface (IF1) defined in VLAN1, and this VLAN 1 is supported on ports 17 to 24 of both switches
The same problem exist on out 2 Blades servers;
the only way to bypass this problem is to connect to the 2nd switch via its console port and do a Ping from it to the outside network;
then, after, this 2nd switch will be available from the outside network , at least for a while
Question :
is this a known problem or a normal situation du to the fact that this 2nd switch is not directly connected to the outside network ?
thanks in advance
is there any
HP ProLiant BL p-Class with 2 internal GbE2 Interconnect Switch (Copper); code V2.2.0
ports 17 and 18 on both internal switch are up;
The 1st switch is the only one connected to the outside network thru its port 19;
The 2nd switch is not directly connected at all to the outside network (all its ports 19,20,21,22,23,24 are unplugged) ;
Problem :
There is no way to ping this 2nd switch from the 1st switch or from any PC in the outside network;
The 2 switches have an IP interface (IF1) defined in VLAN1, and this VLAN 1 is supported on ports 17 to 24 of both switches
The same problem exist on out 2 Blades servers;
the only way to bypass this problem is to connect to the 2nd switch via its console port and do a Ping from it to the outside network;
then, after, this 2nd switch will be available from the outside network , at least for a while
Question :
is this a known problem or a normal situation du to the fact that this 2nd switch is not directly connected to the outside network ?
thanks in advance
is there any
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2005 06:48 PM
09-17-2005 06:48 PM
Re: Problem to access 2nd GbE2 Interconnect Switch
Probably all what you described is default settings, along my understanding crosslinks should permit communication between the switches for additional management capability, fault tolerance, and cable reduction. Without changes in Console you should ping NIC from switch B, unless you really have to open some kind membership?
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00429271/c00429271.pdf
From Page 13
More
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00291271/c00291271.pdf
See attachment, Pretend that image is your set up, where NIC 1(or2) and NIC 3 joined as a TEAM for Fault tolerant, suggested to connected Switch B out.
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00429271/c00429271.pdf
From Page 13
More
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00291271/c00291271.pdf
See attachment, Pretend that image is your set up, where NIC 1(or2) and NIC 3 joined as a TEAM for Fault tolerant, suggested to connected Switch B out.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP