M4250 Datasheet
Loopback interfaces are available as dynamic, stable IP addresses for other devices on the network, and for routing protocols
SupportofRoutingInformationProtocol(RIPv2)as
adistancevectorprotocolspeciedinRFC2453for
IPv4
• Each route is characterized by the number of gateways, or hops, a packet must traverse to reach its intended
destination
• Categorizedasaninteriorgatewayprotocol,RIPoperateswithinthescopeofanautonomoussystem
IPMultinettingallowstoconguremorethanoneIPaddressonanetworkinterface(othervendorsmaycallitIPAliasingorSecondaryAddressing)
ICMPThrottlingfeatureaddscongurationoptions
forthetransmissionofvarioustypesofICMPmes-
sages
• ICMPRedirectscanbeusedbyamalicioussendertoperformman-in-the-middleattacks,ordivert
packetstoamaliciousmonitor,ortocauseDenialofService(DoS)byblackholingthepackets
• ICMPEchoRequestsandothermessagescanbeusedtoprobeforvulnerablehostsorrouters
• RatelimitingICMPerrormessagesprotectsthelocalrouterandthenetworkfromsendingalargenumberof
messagesthattakeCPUandbandwidth
ThePolicyBasedRoutingfeature(PBR)overrides
routing decision taken by the router and makes the
packet to follow different actions based on a policy
• It provides freedom over packet routing/forwarding instead of leaving the control to standard routing proto-
cols based on L3
• For instance, some organizations would like to dictate paths instead of following the paths shown by
routing protocols
• Network Managers/Administrators can set up policies such as:
– My network will not carry traffic from the Engineering department
– Traffic originating within my network with the following characteristics will take path A, while other traffic
will take path B
– When load sharing needs to be done for the incoming traffic across multiple paths based on packet
entities in the incoming traffic
Enterprise security
TrafccontrolMACFilterandPortSecurityhelprestrictthetrafcallowedintoandoutofspeciedportsorinterfacesinthesysteminordertoincreaseoverallsecurity
andblockMACaddressoodingissues
DHCPSnoopingmonitorsDHCPtrafcbetweenDHCPclientsandDHCPserverstolterharmfulDHCPmessageandbuildsabindingsdatabaseof(MACaddress,IP
address,VLANID,port)tuplesthatareconsideredauthorizedinordertopreventDHCPserverspoongattacks
IPsourceguardandDynamicARPInspectionusetheDHCPsnoopingbindingsdatabaseperportandperVLANtodropincomingpacketsthatdonotmatchany
bindingandtoenforcesourceIP/MACaddressesformalicioususerstrafcelimination
Time-basedLayer2/Layer3-v4/Layer3-v6/Layer4AccessControlLists(ACLs)canbebindedtoports,Layer2interfaces,VLANsandLAGs(LinkAggregationGroups
orPortchannel)forfastunauthorizeddatapreventionandrightgranularity
Forin-bandswitchmanagement,managementACLsonCPUinterface(ControlPlaneACLs)areusedtodenetheIP/MACorprotocolthroughwhichmanagement
access is allowed for increased HTTP/HTTPS or Telnet/SSH management security
Out-of-bandmanagementisavailableviadedicatedserviceport(1GRJ45OOB)whenin-bandmanagementcanbeprohibitedviamanagementACLs
Bridgeprotocoldataunit(BPDU)GuardallowsthenetworkadministratortoenforcetheSpanningTree(STP)domainbordersandkeeptheactivetopologyconsistent
and predictable - unauthorized devices or switches behind the edge ports that have BPDU enabled will not be able to influence the overall STP by creating loops
SpanningTreeRootGuard(STRG)enforcestheLayer2networktopologybypreventingroguerootbridgespotentialissueswhenforinstance,unauthorizedor
unexpected new equipment in the network may accidentally become a root bridge for a given VLAN
Dynamic 802.1x VLAN assignment mode, including
Dynamic VLAN creation mode and Guest VLAN / Un-
authenticated VLAN are supported for rigorous user
and equipment RADIUS policy server enforcement
• Upto48clients(802.1x)perportaresupported,includingtheauthenticationoftheusersdomain,inorder
tofacilitateconvergentdeployments.ForinstancewhenIPphonesconnectPCsontheirbridge,IPphones
andPCscanauthenticateonthesameswitchportbutunderdifferentVLANassignmentpolicies(Voice
VLANversusotherProductionVLANs)
802.1xMACAddressAuthenticationBypass(MAB)is
a supplemental authentication mechanism that lets
non-802.1x devices bypass the traditional 802.1x
process altogether, letting them authenticate to
thenetworkusingtheirclientMACaddressasan
identifier
• AlistofauthorizedMACaddressesofclientNICsismaintainedontheRADIUSserverforMABpurpose
• MAB can be configured on a per-port basis on the switch
• MABinitiatesafterunsuccessfuldot1xauthenticationprocess(congurabletimeout),whenclientsdon’t
respond to any of EAPOL packets
• When802.1Xunawareclientstrytoconnect,theswitchsendstheMACaddressofeachclienttotheauthen-
tication server
• TheRADIUSservercheckstheMACaddressoftheclientNICagainstthelistofauthorizedaddresses
• The RADIUS server returns the access policy and VLAN assignment to the switch for each client
PAGE 13 of 57
AV Line Managed Switches
Datasheet | M4250 series
AV Line Managed Switches










