- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: HP Storageworks SAN switch 2/32
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО08-12-2010 12:13 PM
тАО08-12-2010 12:13 PM
Set ip addresses.
I cannot access it by it's web page.
http://ip_address
Please help, thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 12:26 PM
тАО08-12-2010 12:26 PM
Re: HP Storageworks SAN switch 2/32
I cannot ping the fibre switch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 12:55 PM
тАО08-12-2010 12:55 PM
Solutionon the serial connection:
ipaddrshow
if you need to change it..
ipaddrset
what version of firmware are you running?
type version
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 03:16 PM
тАО08-12-2010 03:16 PM
Re: HP Storageworks SAN switch 2/32
Kernel: 2.4.19
Fabric OS: v5.1.0d
BootProm 4.5.3
So there is nothing special to configure?
As long as my network connections are correct I should be able to get to it?
What is the Fiber IP address for?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 03:31 PM
тАО08-12-2010 03:31 PM
Re: HP Storageworks SAN switch 2/32
You should only need to set the regular IP, mask and gateway.
You may need to reboot the switch as well.. sometimes the IP does not take right away.
Steven
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 04:42 PM
тАО08-12-2010 04:42 PM
Re: HP Storageworks SAN switch 2/32
Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-12-2010 10:44 PM
тАО08-12-2010 10:44 PM
Re: HP Storageworks SAN switch 2/32
It is used for managing remote switches (FCSW2) whose LAN interface is not directly reachable from the management station. The idea is that the Fibre IP is on a *different* IP network and you add a manual route that points to the LAN connected switch (FCSW1). The transfer to FCSW2 then goes 'in-band' via the Fibre Channel link.
Mgmt(LAN)->FCSW1->FC-LINK->FCSW2
It is *very* important that the Fibre IP is in a different IP subnet or be 'disabled'. Otherwise the switch's IP stack has routing problems, just like any other IP stack.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2010 05:41 AM
тАО08-13-2010 05:41 AM
Re: HP Storageworks SAN switch 2/32
I did have Ethernet and Fiber IP's on the same subnet. Though that being a problem doesn't make sense to me. There's only one RJ-45 port, wouldn't that be a problem when going through a switch? We are vlan'd so I would think a different subnet would have a problem unless you add static routes... which you did mention.
Thank you for helping me get into my switch!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-13-2010 06:03 AM
тАО08-13-2010 06:03 AM
Re: HP Storageworks SAN switch 2/32
Using two different subnets for RJ45(LAN) and FC is not a problem, because then the IP stack then reliably knows where to route the packets.
You 'help' the IP stack in the management station by adding a static route to the IPFC subnet.
Now, FCSW1 receives a packet on its RJ45-port with a destination for the FCSW2 IPFC interface. It knows that it needs to send the packet out its internal IPFC interface and the packet arrives at FCSW2's IPFC interface.
When FCSW2 wants to send data back to the management station, it must understand to use the IPFC interface. So:
1. FCSW2's RJ45(LAN) interface must not be on the same IP subnet that the management station is
2. FCSW2's "default gateway" must be set to FCSW1's IPFC interface IP address.
The packet leaves FCSW2 IPFC interface and arrives at FCSW1 IPFC interface. From the destination address, FCSW1 can infer that it must send the data out of its RJ45(LAN) interface.
The packet finally arrives at the management station.
You can run multiple IP subnets within one VLAN/LAN segment.
Simplified: VLANs just create different LAN segments on 'one cable'.
If you want communication between different VLANs/LAN segments or different IP subnets on one segment, you need a router that has an IP interface in each segment/subnet.