| Scroll ignore |
|---|
| Scroll ignore |
Possible causes and solution(s)
Causes
System overview:
- BVMS 11.0
- VRM 4.00
- Netapp 11.70.R2
Also, the behavior explained below was encountered in:
- BVMS: 10.01
- VRM: 3.82.0057
- Netapp: 11.60.2
Netapp DSA E2800 single controllers are disconnecting for a short period of time.
This is sometimes regular once an hour and even in shorter cycles.
The cameras aren’t recording during the disconnection period.
The ping from the VRM and BVMS server runs without problems on management port and iSCSI.
Solution
Activate the flow control on the management port from the switch.
Useful:
According to the NetApp KB, the default management port IP addresses for each controller is shown below:
Default IP addresses for all platforms except EF600 running 11.60 or earlier:
| Management Port | Controller A | Controller B | Subnet Mask |
| 1 | 192.168.128.101 | 192.168.128.102 | 255.255.255.0 |
| 2 | 192.168.129.101 | 192.168.129.102 |
Note: Default IP addresses are in the form 192.168.XXX.10Y, where:
XXX = 128 is the first port and 129 is the second port on a controller.
Y = 1 is for controller A and 2 is for controller B.
Default IP addresses for all platforms running 11.60.2 and later, or EF600 running 11.60 or later:
| Management Port | Controller A | Controller B | Subnet Mask |
| 1 | 169.254.128.101 | 169.254.128.102 | 255.255.0.0 |
| 2 | 169.254.129.101 | 169.254.129.102 |
Note: Default IP addresses are in the form 169.254.XXX.10Y, where:
XXX = 128 is the first port and 129 is the second port on a controller.
Y = 1 is for controller A and 2 is for controller B.
| Info | ||
|---|---|---|
| ||
Port 2 on the controllers is reserved for Customer Support use only. It should not be used unless explicitly instructed and the default network settings of DHCP enabled should not be changed. | ||
| Scroll ignore | ||
| advancedINLINEgreenINLINEMANDATORY --> after finishing this article, if you wrote advanced content in this section , you must to manually add the "advanced" label This action is required to indicate that this article contains ADVANCED instructions for CTS/ SG or GK . Please contact CTS / SG or GK team to view this section from draft space, if necessaryadINLINE Information below is for CTS, SG, GK reference and must be kept internal only. If you are part of CTS, SG or GK team, please hide this section when you have finished using this article! "Configuring IEEE 802.3x Flow ControlFlow control enables connected Ethernet ports to control traffic rates during congestion by allowing congested nodes to pause link operation at the other end. If one port experiences congestion and cannot receive any more traffic, it notifies the other port by sending a pause frame to stop sending until the condition clears. Upon receipt of a pause frame, the sending device stops sending any data packets, which prevents any loss of data packets during the congestion period." (Source) To configure flow control on an interface, follow these steps beginning in privileged EXEC mode: | Command | Purpose |
Step 1 | configure terminal | Enter global configuration mode |
Step 2 | interface interface-id | Specify the physical interface to be configured, and enter interface configuration mode. |
Step 3 | flowcontrol {receive} {on | off | desired} | Configure the flow control mode for the port. |
Step 4 | end | Return to privileged EXEC mode. |
Step 5 | show interfaces interface-id | Verify the interface flow control settings. |
Step 6 | copy running-config startup-config | (Optional) Save your entries in the configuration file. |