GE NETernity CP923RC Datasheet download pdf (Page 3)

• Ratelimiting

The traffic load on specific ports can be limited, to prevent satura-

tion of the network by rogue devices.

• CongestionControl

Extending the PAUSE frame generation further an administrator

can tune the level at which these frames are generated by setting

backpressure and internal buffers per port.

Switch protocol features

SecurityControl

Improved security to manage who can connect to and what traffic

is permitted to flow through the switch can be carried out using

these features. These features also guard against rogue external

devices attempting to disrupt the normal switch operation.

• PortSecurity

This allows an administrator to configure a set of allowed MAC

addresses, or create a limit on the number of allowed connections

on particular ports. If a device attempts to connect where the

MAC address is not configured as permitted, or the port limit is

reached, the device will be denied access to the network through

switch ports.

• PortAuthorization

802.1X Port Authorization is supported, allowing specific control

over who can be connected to which port. Typically, this makes

use of a remote RADIUS server.

– IEEE 802.1X, RFC 2868, 2866

• DenialofServiceProtection

Once enabled, this feature provides protection from certain types

of DoS attacks.

• DHCPSnooping

This allows an OpenWare switch to filter untrusted DHCP

messages and will create an IP-MAC binding table, which can

then be used to check the integrity of other switch messaging.

• DynamicARPProtection

This provides a method of confirming that ARP messages are

being sent to the NETernity switch from known sources, helping

prevent ARP spoofing attacks.

• MACNotification

This provides a log of information as users connect and discon-

nect from switch ports – SNMP traps can be configured to provide

information to a remote Network Management entity.

Multicast

The multicast features provide a method of limiting the forwarding

of multicast traffic by only sending to devices which have indicated

an interest in receiving it. This can be configured dynamically using

IGMP and MLD or by addition of static entries.

• IGMPSnoopingQuerier

– The switch can react to and generate IGMP protocol messages,

which allow an OpenWare switch to dynamically update the

internal multicast forwarding database, only forwarding traffic

on ports which have expressed a wish to receive it. This makes

for efficient use of the overall network bandwidth.

– Both IGMP Snooping and IGMP Snooping Querier functions are

supported.

› RFC 1112, 2236, 3376, 4541

• MLD(MulticastListenerDiscovery)SnoopingQuerier

– MLD provides the same scope of multicast data control as

IGMP Snooping Querier but in IPV6 networks.

– Both MLD Snooping and MLD Snooping Querier functions are

supported.

> RFC 3513, 4541

• StaticMulticastcontrol

OpenWare allows the configuration of static multicast entries,

providing a method of limiting multicast data forwarding for

cases where IGMP or MLD is not available.

• IGMP/MLDAccessGroups&Limits

This feature allows an Administrator the ability to manage access

to configured multicast groups, and also limit the number of

multicast groups which are able to be joined on defined ports.

• GARP,GVRP,GMRP

These protocols handle the exchange of information about

network setup between switches – this can be VLAN information,

Multicast information, etc.

– IEEE 802.1D 802.1Q

• PIM-SM(ProtocolIndependentMulticast–SparseMode)

PIM allows for multicast traffic to be carried over unicast routes. This

is applicable in complex networks with heavy multicast use, typically

with routing controlled by routing protocols like RIP or OSPF.

– RFC 4601

• StaticMulticastRouting

This feature provides a method for a User to add static multicast

routes so defined multicast traffic can be forwarded across VLANs.

Configuration

• DHCPClient/Server/Relay–IPv4andIPv6

The switch can get its configuration information (e.g. IP address)

from another system – or the switch can be configured to give out

configuration information to other systems in the network.

– RFC 951, 1542, 1534, 2131, 2132, 3046, 3315, 3396, 3736, 4242

• DHCPServerPortAware

The switch has a facility that allows allocation of and an IP

address for a requested DHCP Client based on the port on which

the DHCP address request was received on.

• Configurationprofiles

Switches may need different configurations, depending on where

they are positioned in a network. OpenWare provides the ability

for switches to automatically select different configuration files,

dependent on per-defined criteria – for example when the switch

is in a particular slot.

• ConfigurationSnapshot

This provides a mechanism for saving an active configuration,

rolling back to a previously saved configuration, or loading a config-

uration which has been externally downloaded on to the switch.

ManagementProtocol

• SNMP

OpenWare supports SNMP, allowing for OpenWare switches to

be managed and integrated into networks where consolidated

control of heterogeneous networks is required. Appropriate stan-

dard MIBs are supported for most protocol implementations.

– RFC 1155, 1157, 1212, 1215, 1901, 1908, 2571, 2573, 2578,

2579, 3410, 3416, 3584

Provision of SNMP Traps in order to provide indications of events to

SNMP management entities.

Introduction to Ethernet Switch Management with OpenWare

1 2 3 4

Comments to this Manuals

No comments

GE NETernity CP923RC Datasheet Page 3

Comments to this Manuals