LINUXOR.SK ... open source notes ...

NetApp - ATTO FibreBridge 7500N settings

category: solutionz · date: 2019-12-31 · updated: 2026-10-02 · author: LALA

NetApp Solution · Config document · referenced from Physical design and cabling

noteThe bridge is managed here over plain HTTP on an Ethernet port, with SNMP enabled and one local account. That was all the device offered at the time; it is not how a bridge should be managed today.

The settings of one FC-to-SAS bridge, taken from the configuration dump the bridge produces itself. A bridge presents the disks of the SAS shelf stacks behind it to both Fibre Channel fabrics; it has no notion of aggregates, pools or owners.

ItemValue
DeviceATTO FibreBridge 7500N, firmware 2.85
Shown hereDC1-A-BNAS001, the first bridge of datacenter A at site 1
Also applies toDC1-A-BNAS002, DC1-B-BNAS001, DC1-B-BNAS002; see the differences below
Produced withThe command dumpconfiguration of the bridge
Changed throughThe web interface on a management port, over HTTP, with the one local account
What the dump isAbout 620 lines: an event log, the answers to two dozen commands, and two lists of every disk behind the bridge
What is shownThe settings only

The file

ini
# dumpconfiguration of DC1-A-BNAS001.
# Settings only. Left out of the dump: the event log at its start, the
# FC and SAS world wide names, the SFP and cable serial numbers, the FC
# error counters, the list of 136 disks and 6 shelf enclosure devices
# behind the bridge, and the IPv6 addresses, which the bridge builds from
# its MAC addresses. The line counts and the "Ready." prompts that the
# bridge prints around every answer are left out as well.
# Lines starting with ";" are the bridge's own table headers.

# --- Fibre Channel: both ports up, point-to-point, 16 Gb --------------------
FCPortList
; Port    Status
;===============
   1      Up
   2      Up

get FCConnMode all
; Port    Conn Mode
;==================
   1      ptp
   2      ptp

get FCDataRate all
; Port    Data Rate
;==================
   1      16Gb
   2      16Gb

# --- Ethernet management ports: static addresses, no DHCP, no DNS -----------
get IPAddress all
; Port      Address
;=======================================================================
   MP1      10.11.15.47
   MP2      10.11.15.48

get IPSubnetMask all
; Port      SubnetMask
;=================================
   MP1      255.255.255.0
   MP2      255.255.255.0

get IPGateway all
; Port      Gateway
;=================================
   MP1      10.11.15.254
   MP2      10.11.15.254

get IPV6Gateway
IPV6Gateway =

get EthernetSpeed all
; Port      Speed
;==========================
   MP1      1000
   MP2      auto (1000)

get IPDHCP all
; Port      DHCP
;==========================
   MP1      disabled
   MP2      disabled

get IPDNSServer
Server not configured

# --- SAS: connectors A, B and C carry one shelf stack each, D is off --------
# The fifth column of the original, the SAS address, is removed.
SASPortList
;Connector      PHY     Link            Speed
;=============================================
Device  A       1       Up              12Gb
Device  A       2       Up              12Gb
Device  A       3       Up              12Gb
Device  A       4       Up              12Gb
Device  B       1       Up              12Gb
Device  B       2       Up              12Gb
Device  B       3       Up              12Gb
Device  B       4       Up              12Gb
Device  C       1       Up              12Gb
Device  C       2       Up              12Gb
Device  C       3       Up              12Gb
Device  C       4       Up              12Gb
Device  D       1       Disabled        12Gb
Device  D       2       Disabled        12Gb
Device  D       3       Disabled        12Gb
Device  D       4       Disabled        12Gb

get SASConnectorInfo all
SAS connector information for connector A:
Vendor:        Amphenol
Part Number:   112-00437+A0
Cable Type:    Passive Copper 2m ID:00
SAS connector information for connector B:
Vendor:        Amphenol
Part Number:   112-00437+A0
Cable Type:    Passive Copper 2m ID:00
SAS connector information for connector C:
Vendor:        Amphenol
Part Number:   112-00437+A0
Cable Type:    Passive Copper 2m ID:00
SAS connector D is currently disabled.
Vendor:        N/A
Part Number:   N/A
Cable Type:    N/A

# --- SNMP: agent on, no trap destination, traps off -------------------------
get SNMP
SNMP = enabled

get SNMPTrapAddress
;             Index IP Address                               Trap Level
SNMPTrapAddress   1 0.0.0.0                                  none
SNMPTrapAddress   2 0.0.0.0                                  none
SNMPTrapAddress   3 0.0.0.0                                  none
SNMPTrapAddress   4 0.0.0.0                                  none
SNMPTrapAddress   5 0.0.0.0                                  none
SNMPTrapAddress   6 0.0.0.0                                  none

get SNMPTraps
SNMPTraps = disabled

# --- Diagnostics -------------------------------------------------------------
CoreDumpInfo
No core dump found.

What changes on the other three bridges

SettingDC1-A-BNAS001DC1-A-BNAS002DC1-B-BNAS001DC1-B-BNAS002
IPAddress of MP110.11.15.4710.11.15.4910.11.23.4710.11.23.49
IPAddress of MP210.11.15.4810.11.15.5010.11.23.4810.11.23.50
IPGateway10.11.15.25410.11.15.25410.11.23.25410.11.23.254
EthernetSpeed of MP1100010001000auto (1000)
SNMPTrapsdisabledenabledenabledenabled
CoreDumpInfoNo core dumpNo core dumpOne core dump, dated 09/06/2017No core dump
Cable type ID of connectors A, B, C00, 00, 0000, 00, 0000, 00, 0101, 00, 01
Shelves behind it10 to 3110 to 3150 to 7150 to 71

Everything else is identical on all four: both FC ports up, point-to-point at 16 Gb; SAS connectors A to C up at 12 Gb and D disabled; DHCP off; no DNS server; SNMP enabled with no trap destination; 136 disks and six shelf enclosure devices visible.

Three of the differences do not look like design. The fixed speed of MP1 on three bridges and the disabled traps on one are not explained anywhere in the notes; with no trap destination configured, the trap setting has no effect either way. The core dump on DC1-B-BNAS001 is from 2017, the year of the installation, and the notes do not mention it. The file kept for DC1-B-BNAS002 contains two dumps one after the other, with the same settings.

The event log that the dump starts with, and that is left out here, holds little more than periodic checkpoints, SCSI reservation conflicts between the controllers, and the logins to the web interface from the admin VPN.

Checked against ONTAP 9.19.1

As builtToday
FibreBridge 7500N, firmware 2.85NetApp states that the 6500N and 7500N are at end of hardware support and therefore also end of software support. The successor is the 7600N, and replacing a 7500N by a 7600N in a running configuration is a documented procedure
Managed over Ethernet: web interface over HTTP, SNMP enabledIn-band management over the FC ports exists from ONTAP 9.5 and is the default from 9.8. NetApp recommends in-band management with IP access disabled; from ONTAP 9.5 the command securebridge switches off Telnet and the other IP services of the bridge
ONTAP monitors the bridges by SNMP, storage bridge showOut-of-band management of the bridges by SNMP is deprecated. The command family is system bridge since ONTAP 9.8
No HTTPS, no SSH, no directory loginNetApp's bridge procedures still name only the web interface, serial, Telnet, FTP, SNMP and ICMP as services of the bridge. ATTO's own current documentation was not checked for this write-up
Three stacks on connectors A to CA pair of 7500N or 7600N bridges supports up to four stacks

The device that had to be written into the design as a constraint, because it could do neither HTTPS nor central authentication, no longer needs an address at all: with in-band management ONTAP reaches the bridge through the same FC ports the disks use.

← solutionz