Cisco MDS SanOS Troubleshooting Guide -- Configuration Limits for Cisco MDS SAN-OS Release 3.x
From DocWiki
(→Configuration Limits for Cisco MDS SAN-OS Release 3.x) |
(→Configuration Limits for Cisco MDS SAN-OS Release 3.x) |
||
| (5 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
== Configuration Limits for Cisco MDS SAN-OS Release 3.x == | == Configuration Limits for Cisco MDS SAN-OS Release 3.x == | ||
---- | ---- | ||
| - | The features supported by Cisco MDS SAN-OS have maximum configuration limits. For some of the features, we have verified configurations that support limits less | + | The features supported by Cisco MDS SAN-OS have maximum configuration limits. For some of the features, we have verified configurations that support limits less than the maximum. Table C-1 lists the Cisco verified limits and maximum limits for switches running Cisco MDS SAN-OS Release 3.x. |
<div align="left"> | <div align="left"> | ||
{| id="wp1016520table1016514" width="80%" border="1" cellpadding="3" | {| id="wp1016520table1016514" width="80%" border="1" cellpadding="3" | ||
| - | |+ Table C-1 Cisco MDS SAN-OS Release 3.x Configuration Limits | + | |+ '''Table C-1 Cisco MDS SAN-OS Release 3.x Configuration Limits'''| |
| - | | | + | |
! scope="col" | | ! scope="col" | | ||
<div class="pCH1_CellHead1"> Feature </div> | <div class="pCH1_CellHead1"> Feature </div> | ||
! scope="col" | | ! scope="col" | | ||
<div class="pCH1_CellHead1"> Verified Limit </div> | <div class="pCH1_CellHead1"> Verified Limit </div> | ||
| - | ! scope="col" | | + | ! scope="col" |<div class="pCH1_CellHead1"> Maximum Limit </div> |
| - | <div class="pCH1_CellHead1"> Maximum Limit </div> | + | |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
Device alias | Device alias | ||
| | | | ||
| - | + | 8000 per fabric. | |
| | | | ||
| - | + | 20000 per fabric. | |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| Line 41: | Line 39: | ||
100 switches | 100 switches | ||
| | | | ||
| - | 100 switches | + | 100 switches. |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| Line 55: | Line 53: | ||
16 | 16 | ||
| | | | ||
| - | 16 | + | 16. |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
Switches in a single MDS physical fabric or VSAN | Switches in a single MDS physical fabric or VSAN | ||
| | | | ||
| - | 55 switches. | + | 55 switches. |
| | | | ||
239 switches. | 239 switches. | ||
| Line 83: | Line 81: | ||
16,000 zone members per physical fabric (includes all VSANs). | 16,000 zone members per physical fabric (includes all VSANs). | ||
| | | | ||
| - | 20,000 zone members per | + | 20,000 zone members per physical fabric (includes all VSANs). |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| Line 139: | Line 137: | ||
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| - | ISL instances per switch | + | ISL instances per switch |
| | | | ||
Up to 200 ISLs, each with 16 VSANs, for a total of 3200 port-VSAN instances. You can configure more than 200 ISLs with fewer than 16 VSANs, or fewer than 200 ISLs with more than 16 VSANs, within the total ports per VSAN instance limit of 3200. | Up to 200 ISLs, each with 16 VSANs, for a total of 3200 port-VSAN instances. You can configure more than 200 ISLs with fewer than 16 VSANs, or fewer than 200 ISLs with more than 16 VSANs, within the total ports per VSAN instance limit of 3200. | ||
| Line 188: | Line 186: | ||
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| - | SANTap ITLs per DPP (initiator/target/LUN tuple) | + | SANTap ITLs per DPP (initiator/target/LUN tuple) |
| | | | ||
1024 | 1024 | ||
| | | | ||
| - | 1024 | + | 1024. |
|- align="left" valign="top" | |- align="left" valign="top" | ||
| | | | ||
| - | SANTap ITLs per SSM | + | SANTap ITLs per SSM |
| | | | ||
1024 | 1024 | ||
| Line 208: | Line 206: | ||
{| | {| | ||
| | | | ||
| - | <sup>1 </sup>Certain design considerations must be met to reach this limit. We recommend that you have the large | + | <sup>1 </sup>Certain design considerations must be met to reach this limit. We recommend that you have the large fabric design validated by Cisco Advanced Services. |
<sup>2 </sup>This is the number of trunking-enabled ISL ports multiplied by the number of VSANs in the switch. | <sup>2 </sup>This is the number of trunking-enabled ISL ports multiplied by the number of VSANs in the switch. | ||
Latest revision as of 09:03, 4 November 2010
Configuration Limits for Cisco MDS SAN-OS Release 3.x
The features supported by Cisco MDS SAN-OS have maximum configuration limits. For some of the features, we have verified configurations that support limits less than the maximum. Table C-1 lists the Cisco verified limits and maximum limits for switches running Cisco MDS SAN-OS Release 3.x.
|
Feature
|
Verified Limit
| Maximum Limit
|
|---|---|---|
|
Device alias |
8000 per fabric. |
20000 per fabric. |
|
Event Traps - forward via Email |
1 destination. |
Up to 10 destinations. |
|
ISLB VRRP |
20 per switch. |
20 per switch. |
|
NPV switches per NPV core switch |
100 switches |
100 switches. |
|
VSANs |
80 VSANs per physical fabric. |
4000 VSANs per physical fabric. |
|
VSANs per NPV device |
16 |
16. |
|
Switches in a single MDS physical fabric or VSAN |
55 switches. |
239 switches. |
|
Switches in a mixed or open physical fabric or VSAN |
32 switches. |
239 switches. |
|
Domains per VSAN |
40 domains. |
239 domains. |
|
Zone members |
16,000 zone members per physical fabric (includes all VSANs). |
20,000 zone members per physical fabric (includes all VSANs). |
|
Zones |
8000 zones per switch (includes all VSANs). |
8000 zones per switch (includes all VSANs). |
|
Zone sets |
500 zone sets per switch (includes all VSANs). |
1000 zone sets per switch (includes all VSANs). |
|
Supported hops for all major storage, server, and HBA vendors |
7 hops (diameter of the SAN fabric). |
12 hops. |
|
IVR zone members |
4000 IVR zone members per physical fabric. |
20,000 IVR zone members per physical fabric in Cisco SAN-OS Release 3.0(3) and later. 10,000 IVR zone members per physical fabric prior to Cisco SAN-OS Release 3.0(3). |
|
IVR zones |
1500 IVR zones per physical fabric. |
8000 IVR zones per physical fabric in Cisco SAN-OS Release 3.0(3) and later. 2000 IVR zones per physical fabric prior to Cisco SAN-OS Release 3.0(3). |
|
IVR zone sets |
32 IVR zone sets per physical fabric. |
32 IVR zone sets per physical fabric. |
|
IVR service groups |
16 service groups per physical fabric. |
16 service groups per physical fabric. |
|
ISL instances per switch |
Up to 200 ISLs, each with 16 VSANs, for a total of 3200 port-VSAN instances. You can configure more than 200 ISLs with fewer than 16 VSANs, or fewer than 200 ISLs with more than 16 VSANs, within the total ports per VSAN instance limit of 3200. |
Up to 200 ISLs, each with 16 VSANs, for a total of 3200 port-VSAN instances. You can configure more than 200 ISLs with fewer than 16 VSANs, or fewer than 200 ISLs with more than 16 VSANs, within the total ports per VSAN instance limit of 3200. |
|
IP ports per switch |
No limits. |
No limits. |
|
Fibre Channel modules vs. IPS modules per switch |
No limits. |
No limits. |
|
iSCSI and iSLB sessions per IP port |
500 sessions. |
500 sessions. |
|
iSCSI and iSLB sessions per switch |
5000 sessions. |
5000 sessions. |
|
iSCSI and iSLB initiators supported in physical fabric |
2000 initiators. |
2000 initiators. |
|
iSCSI and iSLB targets per physical fabric (virtual and initiator targets) |
6000 targets. |
6000 targets. |
|
SANTap ITLs per DPP (initiator/target/LUN tuple) |
1024 |
1024. |
|
SANTap ITLs per SSM |
1024 |
1024 in Cisco SAN-OS Release 3.0(2j). 2048 in Cisco SAN-OS Release 3.1(2m). 4080 in Cisco SAN-OS Release 3.1(3) and later. |
|
1 Certain design considerations must be met to reach this limit. We recommend that you have the large fabric design validated by Cisco Advanced Services. 2 This is the number of trunking-enabled ISL ports multiplied by the number of VSANs in the switch. 3 SANTap is not supported in SAN-OS Release 3.3(1). |
