Radius with SSHv2, RIP MIBs, Trunk Traffic

BLADE OS 5.1 Release Notes

RADIUS with SSHv2

With RADIUS turned on, users might see a duplicate login prompt for SSHv2 clients, if the RADIUS server is too slow to respond or if the RADIUS server is not available. In this case, users must re-type the username and password to login.

RIP MIBs

Due to backward-compatibility issues, two Routing Information Protocol (RIP) MIBs are available in BLADEOS: ripCfg and rip2Cfg. Use the rip2Cfg MIB to configure RIPv1 and RIPv2 through SNMP.

BLADEOS does not support the standard RIPv2 MIB, as described in RFC 1724. Use the rip2Cfg MIB to configure RIPv1 and RIPv2 through SNMP.

Trunk and Link Loop

When you create a trunk or link loop between the GbESM and another switch, packets might loop infinitely at line rate within the related links. When this problem occurs, the GbESM continuously displays the following messages at the console:

WARNING: packet_sent u: 0, dv_active: tx ring full

packet_sent dcnt=114, public1=110, vcnt=1025

Solution: Remove the loop to resolve this misconfiguration.

Trunk Traffic

Multicast, broadcast and DLF (Destination Lookup Failure, which are unknown destination MAC packets) traffic is sent to the lowest numbered port in the trunk. If this port is down, then the traffic is sent to the next lowest-numbered port. If the port that was down comes up again, the traffic is not re-hashed back to the recovered port.

Browser Based Interface

Some versions of Microsoft Internet Explorer version 6.x do not perform HTTP download efficiently. If you have one of these versions, HTTP software download might take much longer than expected (up to several minutes).

Web-browsers from different vendors may vary in their support of standard features. If you encounter problems using the BBI in a particular browser, a different browser may resolve the issue.

BMD00098, December 2009