HP 8/40 Brocade Access Gateway Administrator's Guide v6.3.0 (53-1001345-01, Ju - Page 38

Access Gateway policy enforcement matrix, Advanced Device Security policy, How the ADS policy works

Page 38 highlights

3 Advanced Device Security policy Access Gateway policy enforcement matrix The following table shows which combinations of policies can co-exist with each other. TABLE 6 Policy enforcement matrix Policies Auto Port Configuration Port Grouping N_Port Trunking ADS Policy Auto Port Configuration N/A Cannot co-exist Can co-exist Can co-exist N_Port Grouping Mutually exclusive N/A Can co-exist Can co-exist N_Port Trunking Can co-exist Can co-exist N/A Can co-exist ADS Policy Can co-exist Can co-exist Can co-exist N/A Advanced Device Security policy The Advanced Device Security (ADS) is disabled by default for Access Gateway. ADS is a security policy that restricts access to the fabric at the AG level to a set of authorized devices. Unauthorized access is rejected and the system logs a RASLOG message. You can configure the list of allowed devices for each F_Port by specifying their Port WWN (PWWN). The ADS policy secures virtual and physical connections to the SAN. How the ADS policy works When you enable this policy, it applies to all F_ports on the AG-enabled module. By default, all devices have access to the fabric on all ports. You can restrict the fabric connectivity to a particular set of devices where AG maintains a per-port allow list for the set of devices whose PWWN you define to log in through an F_Port. You can view the devices with active connections to an F_Port using the ag --show command. NOTE The ag --show command only displays the Core AGs, such as the AGs that are directly connected to fabric. The agshow --name name command displays the F_Ports of both the Core and Edge AGs. Alternatively, the security policy can be established in the Enterprise fabric using the DCC policy. For information on configuring the DCC policy, see "Enabling the DCC policy on trunk" on page 40. The DCC policy in the Enterprise fabric takes precedence over the ADS policy. It is generally recommended to implement the security policy in the AG module rather than in the main fabric, especially if Failover and Failback policies are enabled. 18 Access Gateway Administrator's Guide 53-1001345-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82

18
Access Gateway Administrator’s Guide
53-1001345-01
Advanced Device Security policy
3
Access Gateway policy enforcement matrix
The following table shows which combinations of policies can co-exist with each other.
Advanced Device Security policy
The Advanced Device Security (ADS) is disabled by default for Access Gateway. ADS is a security
policy that restricts access to the fabric at the AG level to a set of authorized devices. Unauthorized
access is rejected and the system logs a RASLOG message. You can configure the list of allowed
devices for each F_Port by specifying their Port WWN (PWWN). The ADS policy secures virtual and
physical connections to the SAN.
How the ADS policy works
When you enable this policy, it applies to all F_ports on the AG-enabled module. By default, all
devices have access to the fabric on all ports. You can restrict the fabric connectivity to a particular
set of devices where AG maintains a per-port allow list for the set of devices whose PWWN you
define to log in through an F_Port. You can view the devices with active connections to an F_Port
using the
ag --show
command.
NOTE
The
ag
--
show
command only displays the Core AGs, such as the AGs that are directly connected to
fabric. The
agshow
--
name
name
command displays the F_Ports of both the Core and Edge AGs.
Alternatively, the security policy can be established in the Enterprise fabric using the DCC policy.
For information on configuring the DCC policy, see
“Enabling the DCC policy on trunk”
on page 40.
The DCC policy in the Enterprise fabric takes precedence over the ADS policy. It is generally
recommended to implement the security policy in the AG module rather than in the main fabric,
especially if Failover and Failback policies are enabled.
TABLE 6
Policy enforcement matrix
Policies
Auto Port Configuration
Port Grouping
N_Port Trunking
ADS Policy
Auto Port Configuration
N/A
Cannot co-exist
Can co-exist
Can co-exist
N_Port Grouping
Mutually exclusive
N/A
Can co-exist
Can co-exist
N_Port Trunking
Can co-exist
Can co-exist
N/A
Can co-exist
ADS Policy
Can co-exist
Can co-exist
Can co-exist
N/A