Page 2
WITCH PERATING YSTEM V Disclaimer RuggedCom Inc. makes no warranty of any kind with regard to this material. RuggedCom shall not be liable for errors contained herein or for consequential damages in connection with the furnishing, performance, or use of this material.
BOUT THIS UIDE This guide is concerned with aiding the user in the configuration and operation of the RuggedSwitch™ using the RuggedCom User Interface. Specifically, this guide details aspects of: • Accessing the User Interface • Security (passwords) • Configuring the switch •...
3. Configure the switch’s IP address (Administration, Configure IP Services, IP Address) and Subnet Mask (Administration, Configure IP Services, Subnet). If instead you wish the switch to load the address via DHCP, set the address type to dynamic (Administration, Configure IP Services, IP Address Type). See Chapter 1 for more details.
8. By default the switch has VLAN 1 configured on all ports (VLAN 1 is always present for management purposes). IGMP is disabled for VLAN 1 by default and can be enabled by the Virtual LANs, Configure Static VLANs, IGMP command.
Quick Start Recommendations... ii For Users Migrating From Revisions ROS 1.2 and Earlier..iii Table Of Contents ... iv Chapter 1– Setting Up And Administering The Switch ...1 Introduction...1 The RuggedSwitch™ User Interface ...1 Using the RS232 Port to Access the User Interface ...1 The Structure of the User Interface...3...
VLAN Applications ...34 Traffic Domain Isolation...34 Administrative Convenience...35 Reduced Hardware...35 Service Differentiation...36 VLAN Configuration ...36 VLAN Parameter Ranges & Default Settings...36 Virtual LANs Menu ...37 Static VLANs Menu...37 Port VLAN Parameters Menu...39 VLAN Summary Menu ...42 Troubleshooting ...43 RuggedCom Table Of Contents...
Page 8
Introduction to Multicast Filtering...75 IGMP Features ...75 IGMP Concepts And Issues ...77 Router IGMP Operation...77 Switch IGMP Active and Passive Operation ...78 Combined Router And Switch IGMP Operation ...79 Multicast Filtering Configuration ...82 Multicast Filtering Parameter Ranges & Default Settings...82 Multicast Filtering Menu ...82...
Page 9
Upgrading Firmware Using A TFTP Client On Your Workstation...122 Upgrading Firmware Using The TFTP Client On Your RuggedSwitch™ ...124 Capturing Configurations...125 Capturing Configurations With XModem ...125 Capturing Configurations With TFTP ...125 Using SQL Commands ...127 Getting Started ...127 RuggedCom Table Of Contents...
Page 10
Changing Values In A Table...129 Defaulting A Table...130 Using RSH And SQL...130 Appendix A - Menu Tree ...131 Appendix B - SNMP MIB Support...132 Appendix C – SNMP Trap Summary ...132 Appendix D – RMON Acceptable MIB Parameters...133 Index...137 RuggedCom...
Page 11
Figure 21: Static VLANs Menu ...37 Figure 22: Port VLAN Parameters Menu ...39 Figure 23: VLAN Summary Menu ...42 Figure 24: Determining The CoS Of A Received Frame ...45 Figure 25: Use of CoS When Forwarding Frames ...46 Figure 26: Classes Of Service Menu...46 RuggedCom...
Page 12
Figure 47: Diagnostics Menu Showing Alarm Commands ...89 Figure 48: Alarms Menu ...91 Figure 49: CPU Diagnostics Menu ...93 Figure 50: Viewing the System Log ...95 Figure 51: Ethernet Statistics Menu...97 Figure 52: Ethernet Statistics Menu...98 Figure 53: Port Statistics Menu...98 RuggedCom...
Page 13
Figure 73 Selecting rows in a table based upon parameter values...129 Figure 74 Selecting rows in a table based upon multiple parameter values ...129 Figure 75 Changing Values In A Table ...129 Figure 76 Defaulting A Table ...130 Figure 77 Bulk Inspections Using RSH and SQL ...130 RuggedCom...
Chapter 1– Setting Up And Administering The Switch Introduction This chapter familiarizes the user with the RuggedCom user interface as well as describes the following procedures: • Configuring the IP Address and Subnet Mask • Configuring the Gateway Address • Configuring for DHCP Operation •...
The Structure of the User Interface The user interface is organized as a series of menus with an escape to a command line interface (CLI) shell. Each menu screen presents the switch name (as proved by the System Identification parameter), Menu Title, Access Level, Alarms indicator, Sub-Menus and Command Bar.
The user interface provides a shell for operations that are more easily performed at the command line. You may switch back and forth from the menu system and shell by pressing <CTRL> S. For more information on the capabilities of the shell consult Chapter 10 - Using The CLI Shell.
These values will be loaded via Dynamic Host Configuration Protocol (DHCP) and may be viewed using the “ipconfig” shell command. IP Address This parameter specifies the IP address of the switch. Administration Configure IP Services Configure System Identification...
This parameter specifies the gateway IP address. This is the address to use when forwarding packets to a network other than the one the switch belongs to. It is only required if you intend to manage the switch from a management station that is separated from the switch by a router.
Configure Passwords The guest, operator and admin passwords provide differing levels of access to the switch. Guest users can view most settings but may not change settings or run commands. Operators cannot change settings but can reset alarms, statistics and logs.
NTP Update Period This parameter determines how frequently the time is updated from the NTP server. If the update attempt fails the switch will make two more attempts (at one- minute intervals) after which an alarm is generated. The programmed update rate will then be resumed.
This command identifies management stations that may configure the switch through SNMP and receive Traps from the switch. At shipping time and after factory reloads the switch is configured not to allow remote management or raise Traps. Identify a management station to the switch by executing the Configure SNMP Management Stations command and pressing CTRL-I to create a management record, as shown below.
Programming a gateway of 10.0.0.1 will cause the switch to forward un-resolvable frames to the router. This problem will also occur if the gateway address is not configured and the switch tries to raise an SNMP trap to a host that is not on the local subnet RuggedCom Router RuggedSwitch 10.0.0.1...
MAC Address management provides you with the following features: • The ability to configure static MAC addresses. • The ability to set the switch MAC address aging time MAC Address Management Configuration MAC Address Management Parameter Ranges & Default Settings...
The port the MAC address was learned upon. Type Either “Static” or “Dynamic”, this parameter describes how the switch has learned the MAC address. Dynamic addresses are learned from received frames. Static addresses are learned from configured entries in the Static MAC Address Table.
Prioritized MAC addresses are configured when traffic to or from a specific device on a LAN segment is to be assigned a higher CoS priority than other devices on MAC Address Learning Options Aging Time 300 s Static MAC Address Table Port Normal Learn High Admin Access Admin Access RuggedCom...
Page 27
CoS (Class of Service) Set this parameter to normal if you want the prioritized address to have a normal CoS priority or to high if you want the prioritized address to have a high CoS priority RuggedCom Chapter 2 - Configuring MAC Management...
• Single-mode fiber (1310nm) optical ports on 9µm cable, 15km distances • Multi-mode Uses MTRJ Connector, Single-mode Uses LC Connector • Support Far End Fault Indication Through FEFI signal All Interfaces • Port security • Broadcast Rate Filtering • Link based Alarms and Traps RuggedCom...
Note: Port security is applied at the edge of the network in order to restrict admission to specific devices. Do not apply port security on core switch connections or where traffic types such as RSTP or IGMP are active. Broadcast Rate Limiting Broadcast rate filtering provides a means to limit the rate of broadcast frames accepted by each port.
When FEFI is enabled the switch bases generation of link signal upon its reception of link signal. If switch A fails to receive a link signal from the controller it will stop generating a link signal. The controller will detect the link failure and switch to the backup port.
VLAN port, all tags in frames copied from the source port will be removed before transmission on the target port. A further limitation of port mirroring is that traffic originated by the switch, such as ping requests, may not be mirrored.
Ultimately, as traffic load approaches 100% the link will become entirely unusable. These problems can be avoided by always configuring ports to the appropriate fixed values. RuggedCom Chapter 3 – Configuring the Ports Port Parameters...
Z-Help S-Shell Figure 14: Port Rate Limiting Menu Broadcasts The switch will limit the number of accepted broadcast frames on this port to this value each second, discarding the excess. Broadcast storm filtering may be disabled for the port. Port Security Menu...
The port security mode, either on or off. Autolearn This may be either “off” or set to the number of addresses the switch is allowed to self-learn. A setting of “off” will cause the switch to match the source MAC addresses of incoming frames against addresses already entered in the Static MAC Address table.
Figure 16: Port Mirroring Menu Port Mirroring Enable or disable port mirroring with this command. Note: Port mirroring will be disabled upon the next reset of the switch. Source Port Select the source port with this command. Target Port Select the target port with this command.
Resetting Ports Performs a reset of one or all Ethernet ports. This action is useful for forcing re- negotiation of speed and duplex or in situations where the link partner has latched into an inappropriate state. RuggedCom Port Status Port Name Link Speed Duplex Maint.
The command “ping 192.168.0.1 500 2” can be used to issue 500 pings each separated by 2 milliseconds to the next switch. If the link used is of high quality then no pings should be lost and the average round trip time should be small.
• Viewing VLAN status and statistics • Troubleshooting VLANs VLAN Features RuggedCom VLANs provide you with the following features: • Per Port : • Native VLAN is configurable. • Modes of operation tailored to edge devices (such as a PC or IED) and to network switch interconnections.
The switch can be configured to transmit frames on the native VLAN tagged. Management VLAN Management traffic, like all traffic on the network, must belong to a specific VLAN. RuggedCom switch management is always part of VLAN 1. This VLAN is the native VLAN by default. RuggedCom...
The Internet Group Management Protocol (IGMP) provides the ability for IP hosts and workstations to report their multicast group memberships to routers. The switch can “snoop” or monitor these messages in order to restrict multicast traffic streams to only the necessary parts of the network. IGMP snooping is activated on a per-VLAN basis.
These hosts may be replaced by a single multihomed host supporting each network on a its own VLAN. This host can perform routing between VLANs. Switch 1 VLAN 3 Switch 3 VLAN 4 RuggedCom...
For each parameter the parameter name, recommended setting and possible range are included. Configuration Items (All Ports) Configured VLANs Port VLAN Type Port native VLAN (PVID) Port native VLAN format RuggedCom Chapter 4 – Configuring VLANs Switch Default Value Supported Values 1 (Management VLAN) 1-1000...
Figure 21: Static VLANs Menu Valid VLAN numbers lie in the range of 1 to 1000. Note: The switch reserves the first VLAN (VLAN 1) for management purposes. VLAN Name Entering a meaningful name will associate this VLAN with its users.
Tagged or Trunk except those Untagged in Forbidden list The factory default sets the port type to “edge“. RuggedCom all members of the VLAN will . For more information on IGMP see Chapter 7 – Port VLAN Parameters Port Type PVID...
Page 46
Trunk ports are automatically members of all VLANs and implement switch-to- switch connections. The switch can “pass through” traffic, forwarding frames received on one trunk port out another trunk port. The trunk ports must be members of all the VLANs the “pass through”...
If the VLAN configured as the PVID does not exist in the “Configure VLANs” menu, the switch will automatically create and use it. IGMP will automatically be disabled for that VLAN. If it is desirable for IGMP to be used on that VLAN, it can be created in the “Configure VLANs”...
• I don’t need VLANs at all. How do I turn them off? Simply leave all ports set to type “Edge” and leave the native VLAN set to 1. This is the default configuration for the switch. Problem Two • I have added two VLANs 2 and 3. I made a number of ports members of these VLANS.
CoS provides the ability to expedite the transmission of certain frames and port traffic over others. The CoS of a frame can take on one of two values, either normal or high. The default policies of the switch enforce a normal CoS for all traffic.
Use Normal CoS Port Frame Weighting tagged ? tagged ? Selector High Cos? To CoS Queues Use High CoS of other Ports Leave CoS As Is Srip Tag Transmitted Frame Leave Tag As Is Use High Tag Use Normal Tag RuggedCom...
Figure 27: Global CoS Parameters Menu CoS Weighting During traffic bursts, frames queued in the switch pending transmission on a port may have both high and normal priorities. This parameter specifies the weighting algorithm for transmitting high priority CoS and normal priority CoS frames.
This menu maps the priority field in an 801.1P or 802.1Q tag to a CoS. Port CoS Parameters Port Default CoS Inspect TOS Normal Normal Normal Normal Normal Normal Normal Normal Priority to CoS Mapping Priority Normal Normal Normal Normal High High High High Admin Access Admin Access RuggedCom...
Normal Access Priority When frames that were originally received untagged are transmitted from a tagged port the switch will insert an 802.1Q VLAN tag priority field based upon the frame’s CoS. The port will insert this parameters value when the frame is configured for normal priority CoS.
• SNMP manageable including newRoot and topologyChange traps. Historically, a device implementing STP on its ports has been referred to as a bridge. RuggedCom uses the term bridge and switch synonymously. and port status provide a rich set of tools for performance...
The RSTP role basically describes whether the port is facing the center or edges of the network and whether it can currently be used or not. State RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
Or Active RSTP Handshake has Occurred Learning BPDUS indicate Forwarding Timer Expires port should not Or Active RSTP Handshake be active Discarding RSTP Enabled ™ introduces two more states, Disabled and Link Down. Introduced Link rises or falls Link Down RuggedCom...
Edge ports that receive configuration messages immediately lose their edge port status and become normal spanning tree ports. A loop created on an improperly connected edge port is thus quickly repaired. RuggedCom Chapter 6 – Configuring Rapid Spanning Tree Root...
Page 58
If RSTP detects this circumstance (based upon the port’s half duplex state after link up) it will switch off Proposing-Agreeing. The port must transition through the learning and forwarding states spending the forward delay in each. There are circumstances where RSTP will make an incorrect decision about the point-to-point state of the link simply by examining the half duplex status, namely: •...
Page 59
There is a relationship between the bridge diameter and the maximum age parameter . To achieve extended ring sizes, RuggedCom RSTP uses an age increment of ¼ of a second. The value of the maximum bridge diameter is thus four times the configured maximum age parameter.
Ports with half duplex/shared media restrictions require special attention in order to guarantee that they do not cause extended failover/recovery times. RuggedCom...
Design Considerations For RSTP in Ring Backbone Configurations 1. Select the design parameters for the network. What are the requirements for robustness and network failover/recovery times? Typically, ring backbones are chosen to provide cost effective but robust network designs. RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
LAN. For example if port 3 is designated to carry the network traffic of LAN A, port 4 will block. Should an interface failure occur on port 3, port 4 would assume control of the LAN. Figure 36: Port Redundancy RuggedCom...
Configuration Item Enabled Priority STP Cost RSTP Cost Edge Port Point to Point RuggedCom Chapter 6 – Configuring Rapid Spanning Tree Supported Values Disabled, Enabled STP, STP and RSTP 1 to 10 seconds 6 to 40 seconds 3 to 10...
Mbps and 2,000,000 for 10 Mbps). Note that RSTP link costs are used only when the bridge version support is set to allow RSTP and the port does not migrate to STP. RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
Edge Port Point to Point Auto Auto False Auto Auto False Auto Auto False Auto Auto False Auto Auto False Auto Auto False Auto Auto False Auto Auto False Admin Access Auto Auto Auto Auto Auto Auto Auto Auto RuggedCom...
Page 67
Force the parameter false when the port operates the link full duplex, but is still not point to point (e.g. a full duplex link to an unmanaged bridge that concentrates two other STP bridges). RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
Configured Hello Time The configured Hello time from the Bridge RSTP Parameters menu. Bridge RSTP Statistics Not Designated For Any LAN 32768 / 00-0A-DC-00-50-00 32768 / 00-0A-DC-00-10-00 2.0 s 2.0 s 15.0 s 15.0 s 20.0 s 20.0 s Admin Access RuggedCom...
Page 69
Total Topology Changes A count of topology changes in the network, as detected on this bridge through link failures or as signaled from other bridges. Excessively high or rapidly increasing counts signal network problems. RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
The port is designated for (i.e. carries traffic towards the root for) its LAN. Root The port on the bridge providing connectivity towards the root bridge. Port RSTP Statistics Role Cost RX RSTs Admin Access TX RSTs RX Configs RuggedCom...
Page 71
TX Tcns The count of configuration messages transmitted on this port. Designated Root ID Provided on the root ports of designated bridges, the Bridge Identifier of the bridge this port is connected to. RuggedCom Chapter 6 – Configuring Rapid Spanning Tree...
Problem Two • My PC/IED/Device is on your switch. After I reset the switch, it takes a long time before it comes up. Is it possible that the RSTP edge setting for this port is set to false? If edge is set false the bridge will make the port go through two forward delay times before the port can send or receive frames.
Page 73
Point setting to true. Either will allow the Proposing-Agreeing protocol to be used. Problem Three • When I test your switch by deliberately breaking a link, it takes a long time before I can poll devices past the switch. I thought RSTP was supposed to be fast. What is happening? Is it possible that ports participating in the topology have been configured to STP mode or that the port’s Point to Point parameter is set false? STP and multipoint...
Page 74
Examine the RSTP port statistics to determine the port from which the TCNs are arriving. Sign-on to the switch at the other end of the link attached to that port. Repeat this step until the switch generating the TCNs is found (i.e. the switch that is itself not receiving a large number of TCNs).
This may introduce significant traffic onto ports that do not require it and receive no benefit from it. RuggedCom switches with IGMP Snooping enabled will act upon IGMP messages sent from the router and the host, restricting traffic streams to the appropriate LAN segments.
After the last consumer of a group has un-subscribed, the router will prune the multicast stream from the given segment. Multicast Membership Query Router M1 Membership Report RuggedCom...
Active Mode When such a switch is used without a multicast router, it is able to function as if it is a multicast router. The switch acts as a multicast router, sending general/specific queries, processing leaves/joins and actively pruning the network.
In this example we will assume that the two routers agree that router 1 is the querier for VLAN 2 and router 2 is simply a non-querier. In this case, the switch will periodically receive queries from router 1 and, thus, maintain the information which port links the multicast router.
Page 79
When host C1 decides to leave a multicast group it will issue a leave request to the switch. If the switch is in active mode it will specific poll the port to determine if C1 is the last member of the group on that port. If C1 is the last (or only) member, the switch will issue a leave to the router and the group will immediately be pruned from the port.
Mode This parameter sets the IGMP mode to active or passive. In active mode the switch generates IGMP queries, if and when queries from a multicast router are not detected. In passive mode the switch passively snoops IGMP traffic and never sends IGMP queries.
Use passive mode only with routers that have problems identifying IGMP enabled switches. A switch running in passive mode requires the presence of a multicast router or it will not be able to forward multicast streams at all! Query Interval In active mode, this is the time interval between IGMP queries sent by the switch.
If a detected multicast traffic source “moves” to a different port (or another source of the same group becomes active) the switch will re-detect it after multicast source port information is aged out (about two query intervals later).
VLAN unless IGMP is enabled. Problem Two • Computers on my switch receive the multicast traffic just fine, but I can’t get the stream through a connected router. Is the port used to connect the router included in the Router Ports parameter of...
Page 84
The flooding will stop when the “false” router ports are aged out (about 2 switch query intervals). Note that the same behaviour will be observed when the switch resets or when IGMP Snooping is being enabled for the VLAN (in the latter case flooding will only be observed within the VLAN being configured).
Using The Alarm System Alarm Concepts And Issues Alarms are the occurrence of events of interest that are logged by the switch. If alarms have occurred the switch will indicate the number of alarms in the top right corner of all menu screens.
6 17:40 Port 12 was down WARN 6 23:02 Port 6 is down <CTRL> Z-Help S-Shell D-PgDn U-PgUp Figure 48: Alarms Menu Clearing Alarms The Diagnostics menu Clear Alarms command will clear all alarms. RuggedCom Alarms Description Chapter 8 – Diagnostics 6 ALARMS!
Product Identification CPU Usage This parameter presents the CPU usage. RAM Total This parameter presents the total amount of memory available to the switch’s processor. RAM Available This parameter presents the amount of memory available to be consumed by the switch’s processor.
• The version of the Boot code that has been loaded onto the product. • The version of the Main Application code that has been loaded onto the product. • The hardware revision of the RuggedSwitch™ Management CPU. RuggedCom Chapter 8 – Diagnostics syslog.txt Admin Access...
The Load Factory Default Configuration command will re-load all configuration parameters to factory default values. Configuration parameters that affect the connection to the switch (as provided by the Configure IP Services menu) will not be modified. A prompt will be displayed requesting confirmation of this action.
The Ethernet Statistics menu is accessible from the main menu Ethernet Statistics command. My Switch <CTRL> Z-Help S-Shell Figure 51: Ethernet Statistics Menu RuggedCom Chapter 9 - Using Ethernet And RMON Statistics Ethernet Statistics View Ethernet Statistics View Ethernet Port Statistics Clear Ethernet Port Statistics...
The number of Broadcast frames sent. DropEvents This counter is incremented once for every received packet that must be dropped due to insufficient switch resources. Cumulative Error Statistics CRCAlignErrors This counter is incremented for every received packet with an invalid CRC.
Page 94
• RMON Alarms Table – Monitors a specific management information base (MIB) object for a specified interval, generates an alarm at a specified value (rising threshold or falling threshold). Alarms are logged in the switch alarm menu and can be used to triggers RMON events.
Many records can be constructed, each detailing specific ports and capture intervals. If enough records are constructed the switch may not be able to allocate enough buckets and will reduce the depth of the last entered record.
The number of seconds (1 to 3600) between samples. The default value is 1800. Owner A field describing the person who configured this record and any applicable contact information. The RMON specification recommends that the string always start with the word “monitor”. RMON History Control Table 3000 Admin Access Monitor Monitor Monitor RuggedCom...
The remaining fields provide the counts for each statistic as measured in the sample period. Statistics collection begins whenever the History Control record is created and when the switch is initialized. As new samples are added, the window is automatically updated. My Switch...
The RMON Alarm record points to a particular RMON Event Record, which can generate an SNMP trap, an entry in the switch’s event log or both. The RMON Event Record can “steer” alarms towards different communities of trap receivers.
It may be desirable to alarm when the total, or absolute, number of events crosses a threshold. In this case, set the measurement period type to “absolute”. RuggedCom Chapter 9 - Using Ethernet And RMON Statistics Upper = Lower...
The method of sampling the selected variable and calculating the value to be compared against the thresholds. Interval The time interval in seconds over which the data is sampled and compared with the rising and falling thresholds. RMON Alarms Rising Thr 10000 10000 Admin Access Falling Thr 100000 100000 RuggedCom...
Page 101
Events Table, then no alarm will be generated. Owner A field describing the person who configured this record and any applicable contact information. The RMON specification recommends that the string always start with the word “monitor”. RuggedCom Chapter 9 - Using Ethernet And RMON Statistics...
A field describing the person who configured this record and any applicable contact information. The RMON specification recommends that the string always start with the word “monitor”. RMON Events Last Time Sent 0 days, 00:00:00 0 days, 00:00:00 Admin Access RuggedCom...
Log Time The elapsed time from the reboot when this log was created. Log Description The description of the event that activated this log entry. RuggedCom Chapter 9 - Using Ethernet And RMON Statistics RMON Event 1 Logs Table LogDescription...
(a period of 60 seconds and a threshold of 60,000 frames will measure the same rate). Finally, note that generating both transitions of an alarm (rising and falling) provides for discovery of the event duration from the SNMP logs. RuggedCom...
<CTRL> S. Any menu operation in progress (such as changing a configuration parameter) will be terminated. You may return to the menu system by pressing <CTRL> S or entering “exit<CR>” at the shell prompt. RuggedCom Chapter 10 - Using The CLI Shell...
Telnet to the server with specified IP address. TFTP client. Displays the contents of a text file. Prints software versions. Upload or download a file to the switch. Clears all alarms. Clears the system and crash logs. Starts a loopback test on the desired port(s).
The crashlog.txt file will contain debugging information relating to problems that have resulted in unplanned restarts of the switch. A file size of 0 bytes indicates that no untoward events have occurred. The syslog.txt file contains a record of significant events including startups, configuration modifications, firmware upgrades and database re-initializations due to feature additions.
Care should be taken not to start a loop test from a telnet session on the port used to connect to the switch. The test can be programmed to stop after a number of passes, to continue until an error occurs or to continue indefinitely.
192.168.0.1 500 2” can be used to issue 500 pings each separated by 2 milliseconds to the next switch. If the link used is of high quality then no pings should be lost and the average round trip time should be small.
Notes: Tracing has been designed to provide detailed information to expert users. Note that all tracing is disabled upon switch startup. In order to display the current trace settings and discover the systems that be traced, enter the CLI command “trace ?”.
Note: The trace package includes the “forward” subsystem, a remote reporting facility intended to be used only under the direction of RuggedCom service personnel. Viewing DHCP Learned Information Using Ipconfig The CLI command “ipconfig” will provide the current IP address, subnet mask and default gateway.
Commands that start interactive dialogs (such as trace or loop) cannot be used. Resetting The Switch The CLI command “reset” can be used to reset the switch. where ipadd = The address or resolved name of the product password = The password for the access level you wish to...
Your RuggedSwitch™ has two firmware components, the boot binary and the main application binary. In normal practice only the main application will have to be upgraded. Your RuggedCom representative will provide you with this file. It will be of the form RuggedSwitch_Main_v1.x.y.bin.
The switch must be reset in order for the new software to take effect. If you want to reset the switch immediately enter “reset<CR>”. The switch will begin its reboot within a few seconds.
(e.g. RuggedSwitch_Main_v1.4.1.bin) is present there. Telnet to or connect to the console of the switch. Enter the CLI shell and run the command “tftp host_addr get main.bin RuggedSwitch_Main_v1.4.1.bin”. Check the status of the download by running the version command.
The RuggedSwitch™ provides a means to capture the configuration of the switch in an ASCII formatted text file. The same file can be downloaded to the switch at a later date in order to restore the switch to its previous configuration.
Saves the database to non-volatile memory storage. SELECT Queries the database and displays selected records. UPDATE Allows for existing records in a table to be updated. Figure 69 The sql command and SQL help RuggedCom Chapter 11 – Upgrading Firmware And Managing Configurations...
>sql select “ip address” from ipcfg IP Address 10.9.0.2 Figure 72 Select a parameter with a table Description Alarms CPU Diagnostics Port Parameters Ethernet Statistics Port Status IP Services Subnet Gateway 255.0.0.0 10.0.0.254 Enabled public Inactivity Timeo Disabled RuggedCom...
The “where” clause can be used to select rows in a table to modify. As an example, suppose that it desirable to identify all ports on the switch operating in 100 Mbps full duplex with flow control disabled, and to enable flow control on these ports.
Auto Select Disabled Status Media Type Flow Control FEFI Enabled Auto Select Disabled Enabled Auto Select Disabled Enabled Auto Select Disabled Enabled Auto Select Disabled Link Alarms Disabled Enabled Link Alarms Disabled Enabled Disabled Enabled Disabled Enabled Disabled Enabled RuggedCom...
Ethernet Statistics Main Menu Spanning Tree Virtual LANs Classes of Service MAC Address Tables Multicast Filtering Diagnostics RuggedCom Appendices Configure IP Services Configure System Identification Configure Passwords Configure Time and Date Configure SNMP Management Stations Configure Ports Parameters Configure Port Rate Limiting...
Page 122
The switch also generates the proprietary traps summarized in the following table. These traps are described in the RC-TRAPS-MIB. SNMP Trap Name GenericTrap (String “Stack overflow”) GenericTrap (String “Heap error”) GenericTrap (String “PowerSupplyFailure”) GenericTrap (String “Broadcast Storm Filtering activated on port”) GenericTrap (String “Received frame on interface it was sent on, potential hardware loop”)
RuggedCom MIB P CCEPTABLE ARAMETERS The total number of bytes received on the interface, including framing characters. The total number of bytes of all the data bytes received on the line, including bytes from bad packets and framing octets.
Page 124
The total number of received packets that where between 128 and 255 bytes long. The total number of received packets that where between 256 and 511 bytes long. The total number of received packets that where between 512 and 1023 bytes long. and 1518 bytes long. RuggedCom...
Page 125
RuggedCom The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
Page 126
The number of frames discarded by this port due to an excessive size. The number of frames that have been received by this port from its segment. The number of frames that have been transmitted by this port to its segment. RuggedCom...
Need help?
Do you have a question about the RuggedSwitch RS1600 and is the answer not in the manual?
Questions and answers