Datasheet

Alcatel-Lucent Page 84
OmniSwitch 9000
together to provide the image rollback resiliency feature. Image rollback allows the switch to return to
a prior “last known good” version of software in the event of a system software problem.
The /flash/working directory is intended for software that is still being configured for your network.
Changes made while configuring your switch are saved to the boot.cfg file in the /flash/working
directory. Once the /flash/working directory’s configuration and image files are road-tested and
considered valid and reliable for your network, they can be copied to the /flash/certified directory.
The software in the /flash/certified directory should be treated as the “gold master” for the switch.
When you place configuration and image files in this directory, you are “certifying” them as tested and
reliable. If the switch is running from the /flash/working directory and experiences a software problem,
it will “roll back” to the last known good software in the /flash/certified directory on the next reboot.
Using the WebView OmniSwitch 9000 switches can be configured and monitored using WebView, Alcatel.Lucent’s Web-
based device management tool. WebView software is pre-installed in the switch; you are not required
to load additional software.
Note. Although WebView software is pre-installed, you must first enable HTTP sessions for your
switch before you can log in.
WebView has been tested on the following Web browsers:
• Internet Explorer 6.0 for Windows 2000, Windows NT, and Windows XP
• Netscape 4.79 for Solaris 2.8, and HP-UX 11.0
• Netscape 7.1 for Windows 2000, Windows NT, and Solaris 2.8
Port Disable You can configure a “Port Disable” rule to administratively disable an interface when matching a
policy rule. To make the interface operational again, the port must be unplugged/plugged back or
disabled/enabled using “interfaces s/p admin down” and “interfaces s/p admin up”.
Also, a SNMP trap will be sent when an interface goes down when matching a port disable rule.
SNMP Traps A “pktDrop’ SNMP trap will be sent out to the SNMP station when a port goes down because of a
user-port shutdown profile or a port disable rule.
Ethernet Services OAM Ethernet services can be offered over multiple types of transport using a variety of tunneling
technologies. In all such layered models, it is important to provide basic OAM capabilities in each
layer of the hierarchy. Ethernet Services OAM addresses the OAM functionality in the Ethernet
Service (ETH) layer, which remains independent of the underlying TRAN layer(s), each of which may
have its own OAM capability. The requirements of OAM functions for the ETH layer focus on
monitored parameters e.g. connectivity, delay, delay variation (jitter) and status monitoring. The
Ethernet service interface is considered to be the OAM source and termination of ETH layer OAM. In
particular, the Ethernet service interface on each device is assumed to have a MAC address that can be
used for OAM packet addressing.
Feature to be supported with AOS 6.3.1R01
SFLOW 4.2.17 SFlow is a sampling technology embedded within switches/routers defined in RFC 3176. It provides
the ability to monitor the traffic flows. It requires an sFlow Agent running in the Switch/Router and a
sFlow collector which receives and analyses the monitored data.
SFlow agent running on the OS6850, combines interface counters and traffic flow (packet) samples on
all the configured interfaces into sFlow Datagrams that are sent across the network to an sFlow
collector (3rd Party software). Packet sampling is done in hardware and is non-CPU intensive.
Current release (6.1.3r01) will not support IPv6 as Collector.
The switch sends the first 128 bytes of the sampled packet from which the entire layer 2/3/4
information can be extracted by the receiver. This could include:
- Source/Destination Mac address
- Source IP/ Destination IP
- Source/Destination TCP/UDP/ICMP port
- Source/Destination Physical port (Gigabit Port)
- IPv4/IPv6
- RIP/OSPF/BGP/PIM-SM/DM (OK, but if this information falls within the first 128 Bytes of the
packet)
- VLAN
- QoS 802.1Q, ToS and DiffServ (DSCP)
- Data Payload (OK, but if this information falls within the first 128 Bytes of the packet)
- Others (If this information falls within the first 128 Bytes of the packet)
Given an IP Address the SFLOW sampling information can be sent to a Collector such as the InMon
and/or the Crannog.
SFLOW Back-off Algorithm Since the CPU of switch is involved in the datagram processing, there is a built in back-off algorithm
which will automatically adjust the sampling rate in the case of CPU congestion on switch.
This back-off mechanism is not user-configurable in Release 6.1.3r01. If CPU is congested it
automatically continues to double the sampling rate, and will continue to do so up to a very low rate of
1 sample in 2147483647 (2exp31)-1.
For a 1Gig interface, the bit rate is 1,000,000,000 bits per second. The back-off algorithm is designed
to take effect when the sample rate exceeds 10 samples per second on any interface. Since each sample
is configured by default for 128bytes this is 10x128x8 or 10 samples/sec x 1024 bits/sample or
10x1024 bps
1Gbps / 10x1024 bps = 97656 sampling rate.
Sampling
with all available slot/ports at 10G wire
-
rates on OS9000 and all ports at 1G on the OS6850