Votos - 3, Puntuación media: 3.7
(
)
)
|
Resumen del manual
PIM is “protocol-independent” because it does not rely on any particular unicast routing protocol. Sparse mode PIM (PIM-SM) contrasts with flood-and-prune dense mode multicast protocols, such as DVMRP and PIM Dense Mode (PIM-DM) in that multicast forwarding in PIM-SM is initiated only via specific requests, referred to as Join messages. PIM-DM for IPv4 is now supported with the 6.1.3.R01 release. PIM-DM packets are transmitted on the same socket as PIM-SM packets, as both use the same protocol and message format. Unlike PIM-SM, in PIM-DM there are no periodic joins transmitted; only explicitly triggered prunes and grafts. In addition, there is no Rendezvous Point (RP) in PIM-DM. Protocol Independent Multicast Source-Specific Multicast (PIM-SSM) is a highly-efficient extension of PIM. SSM, using an explicit channel subscription model, allows receivers to receive multicast traffic directly from the source; an RP tree model is not used. In other words, a Shortest Path Tree (SPT) between the receiver and the source is created without the use of a Rendezvous Point (RP). Multinetting This feature allows IP traffic from multiple subnets to coexist on the same VLAN. A network is said to be multinetted when multiple IP subnets are brought together within a single broadcast domain (VLAN). It is possible to assign up to eight different IP interfaces per VLAN. NTP Client The Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver. It provides client time accuracies within half a second on LANs and WANs relative to a primary server synchronized to Universal Coordinated Time (UTC) (via a Global Positioning Service receiver, for example). OSPFv2/OSPFv3 Open Shortest Path First version 3 (OSPFv3) is now available with the 6.1.3.R01 release on the OmniSwitch 6850 Series and OmniSwitch 9000 Series. OSPFv3 is an extension of OSPF version 2 (OSPFv2) that provides support for networks using the IPv6 protocol. OSPFv2 is for IPv4 networks. Both versions of OSPF are shortest path first (SPF), or link-state, protocols for IP networks. Also considered interior gateway protocols (IGP), both versions distribute routing information between routers in a single Autonomous System (AS). OSPF chooses the least-cost path as the best path. OSPF is suitable for complex networks with a large number of routers by providing faster convergence, loop free routing, and equal-cost multi-path routing where packets to a single destination can be sent to more than one interface simultaneously. The following features are also supported by both versions of OSPF: • Graceful (Hitless) Support During Failover, which is the time period between the restart and the reestablishment of adjacencies after a planned (e.g., the users performs the takeover) or unplanned (e.g., the primary management module unexpectedly fails) failover. • OSPF adjacencies over non broadcast links. OmniSwitch 6800/6850/9000—Release 6.1.3.R01 page 27 Software Supported Partitioned Switch Management A user account includes a login name, password, and user privileges. The privileges determine whether the user has read or write access to the switch, and which command domains and command families the user is authorized to execute on the switch. The privileges are sometimes referred to as authorization; the designation of particular command families or domains for user access is sometimes referred to as partitioned management. Available command domains and families are listed in the following table: Domain Corresponding Families domain-admin file telnet dshell debug domain-system system aip snmp rmon web config domain-physical chassis module interface pmm health domain-network ip rip ospf vrrp ip-routing ipx ipmr ipms domain-layer2 802.1q vlan bridge stp linkagg ip-helper domain-service dns domain-policy qos policy slb domain-security session avlan aaa Per-VLAN DHCP Relay The OmniSwitch 9000 allows you to configure multiple DHCP relay (ip helper) addresses on a per-vlan basis. For the Per-VLAN service, identify the number of the VLAN that makes the relay request. You may identify one or more server IP addresses to which DHCP packets will be sent from the specified VLAN. Both standard and per VLAN modes are supported. Policy Server Management Policy servers use Lightweight Directory Access Protocol (LDAP) to store policies that are configured through Alcatel-Lucent’s PolicyView network management application. PolicyView is an OmniVista application that runs on an attached workstation. The Lightweight Directory Access Protocol (LDAP) is a standard directory server protocol. The LDAP policy server client in the switch is based on RFC 2251. Currently, PolicyView is supported for policy management. Policy Based Routing (Permanent Mode) Policy Based Routing may be used to redirect traffic to a particular gateway based on source or destination IP address, source or destination network...
Otros modelos de este manual:Equipo de red - 6850 (422.93 kb)
Equipo de red - 6800 (422.93 kb)