1、NetAppxClusteredDataONTAP8.2NetworkManagementGuideNetApp, Inc.495 East Java Drive Sunnyvale, CA 94089 U.S.Part number: 215-07972-A0May 2013Telephone:+1(408)822-60Fax:+1(408)822-4501Supporttelephone:+1(888)463-8277Web:Feedback:doccommentsContentsUnderstandingthenetworkconfiguration7Networkingcomponen
2、tsofacluster7Networkcablingguidelines8Networkconfigurationduringsetup(clusteradministratorsonly)9Networkconfigurationaftersetup11Configuringnetworkports(clusteradministratorsonly)13Typesofnetworkports13Networkportnamingconventions13Rolesfornetworkports14DefaultEthernetportrolesbyplatform15Combiningp
3、hysicalportstocreateinterfacegroups16Whatinterfacegroupsare16Typesofinterfacegroups16Loadbalancinginmultimodeinterfacegroups19Restrictionsoninterfacegroups20Creatinganinterfacegroup21Addingorremovingaportfromaninterfacegroup22Deletinganinterfacegroup22ConfiguringVLANsoverphysicalports23HowVLANswork2
4、3HowswitchesidentifydifferentVLANs24AdvantagesofVLANs25HowtouseVLANsfortaggedanduntaggednetworktraffic26CreatingaVLAN26DeletingaVLAN27Modifyingnetworkportattributes28RemovingaNICfromthenode29ConfiguringIPv6addresses30SupportedandunsupportedfeaturesofIPv630EnablingIPv6onthecluster31ConfiguringLIFs(cl
5、usteradministratorsonly)3232WhatLIFsareRolesforLIFs33CharacteristicsofLlFs35LIFlimits39GuidelinesforcreatingLIFs39GuidelinesforcreatingLIFswithIPv6addresses40CreatingaLIF41ModifyingaLIF43MigratingaLIF44RevertingaLIFtoitshomeport45DeletingaLIF46ConfiguringfailovergroupsforLIFs(clusteradministratorson
6、ly)48ScenariosthatcauseaLIFfailover48Typesoffailovergroups48RelationbetweenLIFrolesandfailovergroups49Creatingoraddingaporttoafailovergroup50Renamingafailovergroup50Removingaportfromordeletingafailovergroup51EnablingordisablingfailoverofaLIF52ManagingroutinginaVserver(clusteradministratorsonly)54Cre
7、atingaroutinggroup54Deletingaroutinggroup55Creatingaroutewithinaroutinggroup56Deletingastaticroute57Configuringhost-nameresolution58Host-nameresolutionfortheadminVserver58Host-nameresolutionforaVserver58Managingthehoststable(clusteradministratorsonly)59CommandsformanagingDNShostnameentries59Managing
8、DNSdomainsforhost-nameresolution59CommandsformanagingDNSdomainconfigurations60Balancingnetworkloadstooptimizeusertraffic(clusteradministratorsonly)61Loadbalancingtypes6lGuidelinesforassigningloadbalancingweights61AssigningaloadbalancingweighttoaLIF62HowDNSloadbalancingworks63CreatingaDNSloadbalancin
9、gzone63AddingorremovingaLIFfromaloadbalancingzone64HowautomaticLIFrebalancingworks66EnablingordisablingautomaticLIFrebalancing66CombiningloadbalancingmethodsinaVserveraccessibleinamultiprotocolenvironment68ManagingSNMPonthecluster(clusteradministratorsonly).70WhatMIBsare70CreatinganSNMPcommunity71Co
10、nfiguringSNMPv3usersinacluster73SNMPv3securityparameters73Examplesfordifferentsecuritylevels74SNMPtraps76Configuringtraphosts76CommandsformanagingSNMP77Viewingnetworkinformation80Displayingnetworkportinformation(clusteradministratorsonly)80DisplayinginformationaboutaVLAN(clusteradministratorsonly)82
11、Displayinginterfacegroupinformation(clusteradministratorsonly)82DisplayingLIFinformation83Displayingroutinginformation85Displayinghostnameentries(clusteradministratorsonly)86DisplayingDNSdomainconfigurations87Displayinginformationaboutfailovergroups(clusteradministratorsonly)87Viewingfailovertargets
12、ofLIFs88ViewingLIFsinaloadbalancingzone90Displayingclusterconnections92Displayingactiveconnectionsbyclient(clusteradministratorsonly)92Displayingactiveconnectionsbyprotocol(clusteradministratorsonly).93Displayingactiveconnectionsbyservice(clusteradministratorsonly)93DisplayingactiveconnectionsbyLlFo
13、nanodeandVserver94Displayingactiveconnectionsinacluster95Displayinglisteningconnectionsinacluster96Commandsfordiagnosingnetworkproblems97UsingCDPtodetectnetworkconnectivity98ConsiderationsforusingCDP98EnablingordisablingCDP99ConfiguringholdtimeforCDPmessages99SettingtheintervalsforsendingCDPadvertis
14、ements100ViewingorclearingCDPstatistics100ViewingneighborinformationbyusingCDP102Copyrightinformation103Trademarkinformation104Howtosendyourcomments105Index106UnderStandingthenetworkCOnfigUratiOnYouneedtounderstandhowtoconfigurenetworkingcomponentsoftheclusterduringandafterthesettingupthecluster.You
15、shouldfollowsomeguidelineswhencablingthenodesandswitchesinyournetwork.AftercablingandinstallingclusteredDataONTAPonthenodes,youneedtosetuptheclusterandconfigureatleastonefunctionalVserver.NetworkingcomponentsofaclusterYoushouldfamiliarizeyourselfwiththenetworkingcomponentsofacluster,beforeorafterset
16、tingupacluster.Abstractingandvirtualizingphysicalnetworkingcomponentsofaclusterintologicalcomponentsprovidestheflexibilityandpotentialmulti-tenancyinDataONTP.Thevariousnetworkingcomponentsinaclusterare:PortsPhysicalports:Networkinterfacecards(NICs)andHBAsprovidephysical(EthernetandFibreChannel)conne
17、ctionstothephysicalnetworks(managementanddatanetworks).Virtualports:VLANsandinterfacegroups(ifgrs)constitutethevirtualports.Whileinterfacegroupstreatseveralphysicalportsasasingleport,VLANssubdivideaphysicalportintomultipleseparateports.1.ogicalinterfacesAlogicalinterface(LIF)isanIPaddressandisassoci
18、atedwithattributessuchasfailoverrulelists,firewallrules.ALIFcommunicatesoverthenetworkthroughtheport(physicalorvirtual)itiscurrentlyboundto.DifferenttypesofLIFsinaclusteraredataLIFs,cluster-managementLIFs,node-managementLIFs,interclusterLIFs,andclusterLIFs.TheownershipoftheLIFsdependsontheVserverwhe
19、retheLIFresides.DataLIFsareownedbydataVserver,node-managementandclusterLIFsareownedbynodeVserver,andcluster-managementLIFsareownedbyadminVserver.RoutinggroupsAroutinggroupisaroutingtable.EachLIFisassociatedwitharoutinggroupandusesonlytheroutesofthatgroup.MultipleLIFscansharearoutinggroup.Eachrouting
20、groupneedsaminimumofoneroutetoaccessclientsoutsidethedefinedsubnet.DNSzonesDNSzonecanbespecifiedduringtheLIFcreation,providinganamefortheLIFtobeexportedthroughtheclustersDNSserver.MultipleLIFscansharethesamename,allowingtheDNSloadbalancingfeaturetodistributeIPaddressesforthenameaccordingtoload.AVser
21、vercanhavemultipleDNSzones.Thefollowingdiagramillustrateshowthedifferentnetworkingcomponentsareassociatedina4-nodecluster:O*red by Data VsecverOned by Adtnin VserverOwned by Node Vserve*FormoreinformationaboutthebasicclusterconceptsandVservers,seetheClusteredDataONTAPSystemAdministrationGuideforClus
22、terAdministrators.NetworkcablingguidelinesYoushouldcableaclustersothattheclustertrafficisonaseparatenetworkfromallothertraffic.Itisoptionalbutarecommendedpracticetohavenetworkmanagementseparatedfromdataandinterclustertraffic.Bymaintainingseparatenetworks,youcanachievebetterperformance,easeofadminist
23、ration,andimprovedsecurityandmanagementaccesstothenodes.Thefollowingdiagramillustratesthenetworkcablingofa4-nodeclusterwithtwodifferentnetworksfordataandmanagement,apartfromtheclusterinterconnect:Operations Manager DataFabric Manager ServerNote:Apartfromthesenetworks,thereisaseparatenetworkforACP(Al
24、ternateControlPath)thatenablesDataONTAPtomanageandcontrolaSASdiskshelfstoragesubsystem.ACPusesaseparatenetwork(alternatepath)fromthedatapath.FormoreinfbnationaboutACP,seetheClusteredDataONTAPPhysicalStorageManagementGuide.Youshouldfollowcertainguidelineswhencablingnetworkconnections:Eachnodeshouldbe
25、connectedtothreedistinctnetworks-oneformanagement,onefordataaccess,andoneforintraclustercommunication.Themanagementanddatanetworkscanbelogicallyseparated.ForsettinguptheclusterinterconnectandthemanagementnetworkbyusingthesupportedCiscoswitches,seetheClusteredDataONTAPSwitchSetupGuideforCiscoSwitches
26、ForsettinguptheclusterinterconnectandthemanagementnetworkbyusingtheNetAppswitches,seetheCN1601andCN1610SwitchSetupandConfigurationGuide.Aclustercanbecreatedwithoutdatanetworkconnections,butmustincludeaclusterinterconnectconnection.Thereshouldalwaysbetwoclusterconnectionstoeachnode,butnodesonFAS22xx
27、systemsmaybeconfiguredwithasingle10-GbEclusterport.Youcanhavemorethanonedatanetworkconnectiontoeachnodeforimprovingtheclient(data)trafficflow.Networkconfigurationduringsetup(clusteradministratorsonly)Youshouldbeawareofsomebasicnetworkconfigurationtobeerfbncdduringtheclustersetup.Basicnetworkconfigur
28、ationincludessettingupthemanagementandclusternetworks,andconfiguringnetworkservicesfortheadminVserver.ForadataVserver,youshouldconfiguredataLIFsandnamingservices.YoucanperformtheinitialnetworkconfigurationoftheclusterandtheVserverbyusingthefollowingwizards: ClusterSetupwizard VserverSetupwizardAtten
29、tion:TheClusterSetupandVserverSetupwizardsdonotsupportIPv6.IfyouwantdataLIFsandmanagementLIFsconfiguredforIPv6,youcanmodifytheLIFsaftertheclusterhasbeenconfiguredandisrunning.Itisnotpossibletoconfigurean!Pv6-onlycluster,becauseclusterLIFsandinterclusterLIFsonlysupportIPv4.Networkingconfigurationduri
30、ngtheClustersetupYoucanperformtheinitialsetupoftheadminVsen,erbyusingtheClusterSetupwizard.Duringthesetup,youcaneitherselectthedefaultvaluesorcustomizeyoursetup.Thedefaultvaluesforsetuparegeneratedbyusingthezeroconfigurationnetworkingmechanism.Forsettingupthe.ClusternetworkTypesofinformationrequired
31、TwoportsfortheprivateclusternetworkMTUsizeof9000forclusterportsIPaddressfortheclusterinterfacesWhenanewnodejoinsacluster,IPaddressesaregeneratedautomatically.However,ifyouwanttoassignIPaddressesmanuallytotheclusterLIFs,youmustensurethatthenewIPaddressesareinthesamesubnetrangeastheexistingclusterLIF
32、s.NetmaskfortheclusterinterfacesAdminVserver Nodeandportforthecluster-managementLIFIPaddressforthecluster-managementLIFNetmaskforthecluster-managementLIFDefaultgatewayforthecluster-managementLIFDNSdomainname DNSnameserversForsettingupthe.Typesofinformationrequired.NodeVserver(foreachnodeinthecluster
33、) Portforthenode-managementLIF IPaddressforthenode-managementLIFNetmaskforthenode-managementLIF Defaultgatewayforthenode-managementLIFNote:Ifyouchoosenottoconfigureanode-managementLIForspecifyadefaultgatewayforthenode-managementLIFwhileusingtheClusterSetupwizard,youmustconfigureanode-managementLIFon
34、eachnodelaterbyusingthecommandlineinterface.Otherwise,someoperationsmightfail.NetworkconfigurationduringtheVserversetupTheVserverSetupwizardguidesyouthroughthefollowingconfiguration:StorageresourcesDataLIFs,NamingservicesFormoreinformationaboutthesetupprocessusingtheClusterSetupandVserverSetupwizard
35、s,seetheClusteredDataONTPSoftwareSetupGuide.RelatedconceptsConfiguringhost-nameresolutiononpage58RelatedreferencesCommandsformanagingDNSdomainconfigurationsonpage60NetworkconfigurationaftersetupYoucanconfigurevariouslogicalnetworkcomponentsaftersettinguptheadminVserverordataVserver.Forexample,afterc
36、reatingtheadminVserveryoucancreateLIFs,routinggroups,failovergroups,andsoon.Ifyouareaclusteradministrator,youcanperfbnthefollowingtasks:Configurenetworkports ConfigureLIFsConfigurefailovergroupsConfigureroutinggroupsConfigurenetworkservicesBalancenetworktrafficIfyouareaVse,cradministrator,youcanperf
37、ormthefollowingtasks: ViewLIFs,Viewroutinggroups,Create,modify,andmanageDNShoststableentriesConfiguringnetworkports(clusteradministratorsonly)Portsarecitherphysicalports(NICs)orvirtualizedports,suchasinterfacegroupsorVLANs.ALIFcommunicatesoverthenetworkthroughtheporttowhichitiscurrentlybound.Typesof
38、networkportsPortsareeitherphysicalports(NICs),orvirtualizedportssuchasinterfacegroupsorVLANs.Interfacegroupstreatseveralphysicalportsasasingleport,whileVLANssubdivideaphysicalportintomultipleseparatevirtualports.InterfaceAportaggregatecontainingtwoormorephysicalportsthatactasasingletnnkport.groupAni
39、nterfacegroupcanbesingle-mode,multimode,ordynamicmultimode.VLANAvirtualportthatreceivesandsendsVLAN-tagged(IEEE802.IQstandard)traffic.VLANportcharacteristicsincludetheVLANIDfortheport.TheunderlyingphysicalportorinterfacegroupportsareconsideredtobeVLANtrunkports,andtheconnectedswitchportsmustbeconfig
40、uredtotrunktheVLANIDs.Note:TheunderlyingphysicalportorinterfacegroupportsforaVLANportcancontinuetohostLIFs,whichtransmitandreceiveuntaggedtraffic.RelatedconceptsCombiningphysicalportstocreateinterfacegroupsonpage16ConfiguringVLANsoverphysicalportsonpage23NetworkportnamingconventionsPortnamesconsisto
41、fthreecharactersthatdescribetheport,stypeandlocation.YoumustbeawareofcertainconventionsofnamingtheEthernetportsonthenetworkinterfaces.InDataONTAPphysicalports,thefirstcharacterdescribestheportstypeandisalwaysetorepresentEthernet.Thesecondcharacterisanumeralidentifyingtheslotinwhichtheportadapterislo
42、cated;thenumeral0(zero)indicatesthattheportisonthenodesmotherboard.Thethirdcharacterindicatestheportspositiononamultiportadapter.Forexample,theportnameebindicatesthesecondEthernetportonthemotherboard,andtheportnamee3aindicatesthefirstEthernetportonanadapterinslot3.Interfacegroupsmustbenamedbyusingth
43、esyntaxa.Forexample,aa,ab,ale,anda2aarevalidinterfacegroupnames.VLANsmustbenamedbyusingthesyntaxport_name-vlan-id,whereport_namespecifiesthephysicalportorinterfacegroupandvlan-idspecifiestheVLANID.Forexample,elc-80isavalidVLANname.RolesfornetworkportsNetworkportscanhaverolesthatdefinetheirpurposeand
44、theirdefaultbehavior.PortroleslimitthetypesofLlFsthatcanbeboundtoaport.Networkportscanhavefourroles:nodemanagement,cluster,data,andintercluster.Eachnetworkporthasadefaultrole.Youcanmodifytherolesforobtainingthebestconfiguration.NodemanagementportsTheportsusedbyadministratorstoconnecttoandmanageanode
45、TheseportscanbeVLAN-taggedvirtualportswheretheunderlyingphysicalportisusedforothertraffic.Thedefaultportfornodemanagementdiffersdependingonhardwareplatform.Someplatformshaveadedicatedmanagementport(eOM).Theroleofsuchaportcannotbechanged,andtheseportscannotbeusedfordatatraffic.ClusterportsTheportsus
46、edforintraclustertrafficonly.Bydefault,eachnodehastwoclusterportsonIO-GbEportsenabledforjumboframes.Note:Insomecases,nodesonFAS22xxsystemswillbeconfiguredwithasingleIO-GbEclusterport.YoucannotcreateVLANsorinterfacegroupsonclusterports.DataportsTheportsusedfordatatraffic.TheseportsareaccessedbyNFS,CI
47、FS5FC,andiSCSIclientsfordatarequests.Eachnodehasaminimumofonedataport.YoucancreateVLANsandinterfacegroupsondataports.VLANsandinterfacegroupshavethedatarolebydefault,andtheportrolecannotbemodified.InterclusterportsTheportsusedforcross-clustercommunication.Aninterclusterportshouldberoutabletoanotherinterclusterportorthedataportofanothercluster.IntercIusterportscanbeonphysicalportsorvirtualports.RelatedconceptsRolesforLIFsonpage33RelatedreferencesDef
