Ridgeline Concepts and Solutions Guide
307
Ridgeline Inventory
Problem: Multiple switches have the same name.
This is because the sysName of those switches is the same. Typically, Extreme Networks switches are
shipped with the sysName set to the type of the switch “Summit48,” “Summit1i,” “Alpine3808,” and so
on, depending on the type of switch.
You can change the way names are displayed through a server property in the Ridgeline
Administration. You can display devices by name or by IP address and name. See “Administering
Ridgeline” in the
Ridgeline Reference Guide
for more information on setting Ridgeline server properties.
Problem: Discovery does not display the MAC address for some devices in discovery results list. In
addition, may not add the device to inventory (primarily happens with workstations).
If the MAC address is not found in the first instance of ifPhysAddress, it is not displayed in the
discovery results table. However, when the device is selected to be added to the Ridgeline inventory,
Ridgeline searches all the ifPhysAddress entries for the device, and will use the MAC address found in
this manner. If no MAC address is found in any ifPhysAddress entry, the device will not be added to
the Ridgeline database.
Problem: Attempted to add a switch to Ridgeline after rebooting the switch, and received an “SNMP
not responding” error.
If a switch has recently been powered on, it may take some time (a number of minutes) before the
device is completely initialized. This will be especially true of chassis devices with many blades, or
devices with a large number of VLANs configured on the device. It the device has not completed its
initialization, Ridgeline may return an error when adding the device. You can simply wait until the
device has finished initializing and adding it again.
Problem: The Device Inventory panel shows incorrect information, and the device image is not
displayed correctly.
This can be caused by a device IP address that is in conflict with another device on the network (a
duplicate IP address). Remove the problem device from the Ridgeline inventory, and add it in again
with the correct IP address.
Printing
Problem: When printing a topology map from the browser client, or a printing report, the browser
can appear to freeze.
Printing a report or a topology map can cause the browser utilization to become very high (approaching
100%) and can spool a very large amount of memory. There is no current solution other than to wait,
and the process will eventually finish.
Summary of Contents for Ridgeline 3.0
Page 14: ...Related Publications Ridgeline Concepts and Solutions Guide 12 ...
Page 26: ...Ridgeline Overview Ridgeline Concepts and Solutions Guide 24 ...
Page 52: ...Getting Started with Ridgeline Ridgeline Concepts and Solutions Guide 50 ...
Page 78: ...Using Map Views Ridgeline Concepts and Solutions Guide 76 ...
Page 88: ...Provisioning Network Resources Ridgeline Concepts and Solutions Guide 86 ...
Page 103: ...6 Ridgeline Concepts and Solutions Guide 101 Figure 63 E Line Service Details Window ...
Page 104: ...Managing Ethernet Services Ridgeline Concepts and Solutions Guide 102 ...
Page 114: ...Importing Services Ridgeline Concepts and Solutions Guide 112 ...
Page 132: ...Managing and Monitoring VPLS Domains Ridgeline Concepts and Solutions Guide 130 ...
Page 146: ...Managing VLANs Ridgeline Concepts and Solutions Guide 144 ...
Page 190: ...Managing Your EAPS Configuration Ridgeline Concepts and Solutions Guide 188 ...
Page 202: ...Managing Network Security Ridgeline Concepts and Solutions Guide 200 ...
Page 350: ...Book Title Ridgeline Concepts and Solutions Guide 348 ...
Page 372: ...Book Title Ridgeline Concepts and Solutions Guide 370 ...