Table Of Contents
Ethernet Operation
9.1 G1000-4 Card
9.1.1 G1000-4 Application
9.1.2 802.3x Flow Control and Frame Buffering
9.1.3 Ethernet Link Integrity Support
9.1.4 Gigabit EtherChannel/802.3ad Link Aggregation
9.1.5 G1000-4 LEDs
9.1.6 G1000-4 Port Provisioning
9.1.7 G1000-4 Gigabit Interface Converters
9.2 E Series Cards
9.2.1 E100T-12/E100T-G Card
9.2.2 E1000-2/E1000-2-G Card
9.2.3 E Series LEDs
9.2.4 E Series Port Provisioning
9.2.5 E-Series Gigabit Interface Converters
9.3 E Series Multicard and Single-Card EtherSwitch
9.3.1 E Series Multicard EtherSwitch
9.3.2 E Series Single-Card EtherSwitch
9.3.3 ONS 15454 E Series and ONS 15327 EtherSwitch Circuit Combinations
9.4 E Series Circuit Configurations
9.4.1 E-Series Circuit Protection
9.4.2 E Series Point-to-Point Ethernet Circuits
9.4.3 E Series Shared Packet Ring Ethernet Circuits
9.4.4 E Series Hub and Spoke Ethernet Circuit Provisioning
9.4.5 E Series Ethernet Manual Cross-Connects
9.5 G1000-4 Circuit Configurations
9.5.1 G1000-4 Point-to-Point Ethernet Circuits
9.5.2 G1000-4 Manual Cross-Connects
9.6 E Series VLAN Support
9.6.1 E Series Q-Tagging (IEEE 802.1Q)
9.6.2 E Series Priority Queuing (IEEE 802.1Q)
9.6.3 E Series VLAN Membership
9.7 E Series Spanning Tree (IEEE 802.1D)
9.7.1 E Series Multi-Instance Spanning Tree and VLANs
9.7.2 E Series Spanning Tree Parameters
9.7.3 E Series Spanning Tree Configuration
9.7.4 E Series Spanning Tree Map
9.8 G1000-4 Performance and Maintenance Screens
9.8.1 G1000-4 Ethernet Performance Screen
9.8.2 G1000-4 Ethernet Maintenance Screen
9.8.3 E-Series Ethernet Performance Screen
9.8.4 E-Series Ethernet Maintenance Screen
9.9 Remote Monitoring Specification Alarm Thresholds
Ethernet Operation
The Cisco ONS 15454 integrates Ethernet into a SONET time-division multiplexing (TDM) platform. The ONS 15454 supports both E series Ethernet cards and the G series Ethernet card. This chapter describes the Ethernet capabilities of the ONS 15454, including:
•
G Series Card (G1000-4)
–
802.3x flow control and frame buffering
–
End-to-end link integrity and Gigabit EtherChannel
–
GBICs
–
Ethernet circuit provisioning
–
Ethernet performance and maintenance screens
–
Ethernet alarm thresholds (RMON)
•
E Series Cards
–
E100T-12/E100T-G cards
–
E1000-2/E1000-2-G cards
–
GBICs
–
Multicard and Single-card Etherswitch
–
Ethernet circuit combinations, configurations and provisioning
–
VLAN and IEEE 802.1Q support
–
Spanning tree and IEEE 802.1D support
–
Ethernet performance and maintenance screens
–
Ethernet alarm thresholds (RMON)
9.1 G1000-4 Card
The G1000-4 card reliably transports Ethernet and IP data across a SONET backbone. The G1000-4 card maps up to four gigabit Ethernet interfaces onto a SONET transport network. A single card provides scalable and provisionable transport bandwidth at the signal levels up to STS-48c per card. The card provides line rate forwarding for all Ethernet frames (unicast, multicast, and broadcast) and can be configured to support Jumbo frames (defined as a maximum of 10,000 bytes).The G-series card incorporates features optimized for carrier-class applications such as:
•
High Availability (including hitless (< 50 ms) performance under software upgrades and all types of SONET/SDH equipment protection switches)
•
hitless re-provisioning
•
support of Gigabit Ethernet traffic at full line rate
•
full TL1-based provisioning capability. Refer to the Cisco ONS 15454 TL1 Command Guide for G1000-4 TL1 provisioning commands.
The G1000-4 card allows an Ethernet private line service to be provisioned and managed very much like a traditional SONET or SDH line. G1000-4 card applications include providing carrier-grade Transparent LAN Services (TLS), 100 Mbps Ethernet private line services (when combined with an external 100 Mb Ethernet switch with Gigabit uplinks), and high availability transport for applications such as storage over MAN/WANs.
You can map the four ports on the G1000-4 independently to any combination of STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, and STS-48c circuit sizes, provided the sum of the circuit sizes that terminate on a card do not exceed STS-48c.
To support a gigabit Ethernet port at full line rate, an STS circuit with a capacity greater or equal to 1Gbps (bidirectional 2 Gbps) is needed. An STS-24c is the minimum circuit size that can support a gigabit Ethernet port at full line rate.The G1000-4 supports a maximum of two ports at full line rate.
Ethernet cards may be placed in any of the 12 multipurpose card slots. In most configurations, at least two of the 12 slots need to be reserved for optical trunk cards, such as the OC-192 card. The reserved OC-N slots give the ONS 15454 a practical maximum of ten G1000-4 cards. The G1000-4 card requires the XC10G card to operate. The G1000-4 card is not compatible with XC or XCVT cards. For more information about the G1000-4 card specifications, see the Card Reference chapter in the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
The G1000-4 transmits and monitors the SONET J1 Path Trace byte in the same manner as ONS 15454 DS-N cards. For more information, see the "Creating a Path Trace" section.
Note
G-Series encapsulation is standard HDLC framing over SONET/SDH as described in RFC 1622 and RFC 2615 with the PPP protocol field set to the value specified in RFC 1841.
9.1.1 G1000-4 Application
Figure 9-1 shows an example of a G1000-4 application. In this example, data traffic from the Gigabit Ethernet port of a high-end router travels across the ONS 15454 point-to-point circuit to the Gigabit Ethernet port of another high-end router.
Figure 9-1 Data traffic using a G1000-4 point-to-point circuit
The G1000-4 card can carry over a SONET network any layer three protocol that can be encapsulated and transported over Gigabit Ethernet, such as IP or IPX. The data is transmitted on the Gigabit Ethernet fiber into the standard Cisco Gigabit Interface Converter (GBIC) on a G1000-4 card. The G1000-4 card transparently maps Ethernet frames into the SONET payload by multiplexing the payload onto a SONET OC-N card. When the SONET payload reaches the destination node, the process is reversed and the data is transmitted from the standard Cisco GBIC in the destination G1000-4 card onto the Gigabit Ethernet fiber.
The G1000-4 card discards certain types of erroneous Ethernet frames rather than transport them over SONET. Erroneous Ethernet frames include corrupted frames with CRC errors and under-sized frames that do not conform to the minimum 60-byte length Ethernet standard. The G1000-4 card forwards valid frames unmodified over the SONET network. Information in the headers is not affected by the encapsulation and transport. For example, packets with formats that include IEEE 802.1Q information will travel through the process unaffected.
9.1.2 802.3x Flow Control and Frame Buffering
The G1000-4 supports 802.3x flow control and frame buffering to reduce data traffic congestion. To buffer over-subscription, 512 kb of buffer memory is available for the receive and transmit channels on each port. When the buffer memory on the Ethernet port nears capacity, the ONS 15454 uses 802.3x flow control to send back a pause frame to the source at the opposite end of the Gigabit Ethernet connection.
The pause frame instructs that source to stop sending packets for a specific period of time. The sending station waits the requested time before sending more data. Figure 9-1 illustrates pause frames being sent from the ONS 15454s to the sources of the data. The G1000-4 card does not respond to pause frames received from client devices.
This flow-control mechanism matches the sending and receiving device throughput to that of the bandwidth of the STS circuit. For example, a router may transmit to the Gigabit Ethernet port on the G1000-4. This particular data rate may occasionally exceed 622 Mbps, but the ONS 15454 circuit assigned to the G1000-4 port may be only STS-12c (622.08 Mbps). In this example, the ONS 15454 sends out a pause frame and requests that the router delay its transmission for a certain period of time. With a flow control capability combined with the substantial per-port buffering capability, a private line service provisioned at less than full line rate capacity (STS-24c) is nevertheless very efficient because frame loss can be controlled to a large extent.
Some important characteristics of the flow control feature on the G1000-4 include:
•
The G1000-4 card only supports asymmetric flow control. Flow control frames are sent to the external equipment but no response from the external equipment is necessary or acted upon.
•
Received flow control frames are quietly discarded. They are not forwarded onto the SONET path, and the G1000-4 card does not respond to the flow control frames.
•
On the G1000-4 card, you can only enable flow control on a port when auto-negotiation is enabled on the device attached to that port. For more information, see the "G1000-4 Port Provisioning" section.
Because of the above characteristics the link auto-negotiation and flow control capability on the attached Ethernet device must be correctly provisioned for successful link auto-negotiation and flow control on the G1000-4. If link auto-negotiation fails, the G1000-4 does not use flow control (default). Without flow control, traffic loss can occur if the input traffic rate is higher than the bandwidth of the circuit for an extended period of time.
9.1.3 Ethernet Link Integrity Support
The G1000-4 supports end-to-end Ethernet link integrity. This capability is integral to providing an Ethernet private line service and correct operation of layer 2 and layer 3 protocols on the attached Ethernet devices at each end. End-to-end Ethernet link integrity essentially means that if any part of the end-to-end path fails the entire path fails. Failure of the entire path is ensured by turning off the transmit lasers at each end of the path. The attached Ethernet devices recognize the disabled transmit laser as a loss of carrier and consequently an inactive link.
Figure 9-2 End-to-end Ethernet link integrity support
Note
Some network devices can be configured to ignore a loss of carrier condition. If such a device attaches to a G1000-4 card at one end then alternative techniques (such as use of layer 2 or layer 3 protocol keep alive messages) are required to route traffic around failures. The response time of such alternate techniques is typically much longer than techniques that use link state as indications of an error condition.
Note
Enabling or disabling port level flow control on the test set or other Ethernet device attached to the G1000-4 port can affect the transmit (TX) laser. This can result in uni-directional traffic flow, if flow control is not enabled on the attached test set or other Ethernet device.
As shown in Figure 9-2, a failure at any point of the path (A, B, C, D or E) causes the G1000-4 card at each end to disable its TX transmit laser at their ends, which causes the devices at both ends to detect link down. If one of the Ethernet ports is administratively disabled or set in loopback mode, the port is considered a "failure" for the purposes of end-to-end link integrity because the end-to-end Ethernet path is unavailable. The port "failure" also cause both ends of the path to be disabled.
9.1.4 Gigabit EtherChannel/802.3ad Link Aggregation
The end-to-end Ethernet link integrity feature of the G1000-4 can be used in combination with Gigabit Ether Channel capability on attached devices. The combination provide an Ethernet traffic restoration scheme that has a faster response time than alternate techniques such as spanning tree re-routing, yet is more bandwidth efficient because spare bandwidth does not need to be reserved.
The G1000-4 supports all forms of Link Aggregation technologies including Gigabit EtherChannel (GEC) which is a Cisco proprietary standard as well as the IEEE 802.3ad standard. The end-to- end link integrity feature of the G1000-4 allows a circuit to emulate an Ethernet link. This allows all flavors of layer 2 and layer 3 re-routing, as well as technologies such as link aggregation, to work correctly with the G1000-4. The G1000-4 supports Gigabit EtherChannel (GEC), which is a Cisco proprietary standard similar to the IEEE link aggregation standard (IEEE 802.3ad). Figure 9-3 illustrates G1000-4 GEC support.
Figure 9-3 G1000-4 Gigabit EtherChannel (GEC) support
Although the G1000-4 card does not actively run GEC, it supports the end-to-end GEC functionality of attached Ethernet devices. If two Ethernet devices running GEC connect through G1000-4 cards to an ONS 15454 network, the ONS 15454 SONET side network is transparent to the EtherChannel devices. The EtherChannel devices operate as if they are directly connected to each other. Any combination of G1000-4 parallel circuit sizes can be used to support GEC throughput.
GEC provides line-level active redundancy and protection (1:1) for attached Ethernet equipment. It can also bundle parallel G1000-4 data links together to provide more aggregated bandwidth. Spanning Tree (STP) operates as if the bundled links are one link and permits GEC to utilize these multiple parallel paths. Without GEC, STP only permits a single non-blocked path. GEC can also provide G1000-4 card-level protection or redundancy because it can support a group of ports on different cards (or different nodes) so that if one port or card has a failure, then traffic is re-routed over the other port/card.
9.1.5 G1000-4 LEDs
G1000-4 series Ethernet card faceplates have two card-level LEDs and one bicolored LED next to each port.
Figure 9-4 G1000-4 card faceplate LEDs
FAIL LED
|
Red
|
The card's processor is not ready or a catastrophic software failure occurred on the card. The RED LED is normally illuminated while the card boots up and turns off when the software is deemed operational.
|
ACT LED
|
Green
|
The card is active and the software is operational.
|
ACT/LINK LED
|
Off
|
No link exists to the Ethernet port.
|
ACT/LINK LED
|
Solid Amber
|
A link exists to the Ethernet port, but traffic flow is inhibited. For example, a lack of circuit set-up, an error on line, or a disabled port may inhibit traffic flow.
|
ACT/LINK LED
|
Solid Green
|
A link exists to the Ethernet port, but no traffic is carried on the port.
|
ACT/LINK LED
|
Flashing Green
|
A link exists to the Ethernet port and traffic is carried on the port. The LED flash rate reflects the traffic rate for the port.
|
9.1.6 G1000-4 Port Provisioning
This section explains how to provision Ethernet ports on an G1000-4 card. Most provisioning requires filling in two fields: Enabled and Flow Control Negotiation. You can also configure the maximum frame size permitted, either Jumbo or 1548 bytes.
Note
The maximum frame size of 1548 bytes, instead of the common maximum frame size of 1518 bytes, enables the port to accept valid Ethernet frames that use new protocols. New protocols, such as MPLS, add bytes and may cause the frame size to exceed the common 1518 byte maximum.
Media Type indicates the type of GBIC installed. For more information on GBICs for the G1000-4 card, see the "G1000-4 Gigabit Interface Converters" section. The Negotiation Status column displays the result of the most-recent auto-negotiation. The type of flow control that was negotiated will be displayed.
Note
You can only provision flow control on the G1000-4 by enabling auto-negotiation. If the attached device does not support auto-negotiation or is not correctly configured to support the G1000-4's asymmetric flow control, flow control is ignored.
Procedure: Provision G1000-4 Ethernet Ports
Step 1
Click the CTC node view and double-click the G1000-4 card graphic to open the card.
Step 2
Click the Provisioning > Port tabs.
Figure 9-5 shows the Provisioning tab with the Port subtab selected.
Figure 9-5 Provisioning G1000-4 Ethernet ports
Step 3
If you want to label the port, double-click the Port Name heading. Click anywhere else on the screen to save the change.
Step 4
Click the Enabled checkbox(s) to activate the corresponding Ethernet port(s).
Step 5
To disable/enable flow control negotiation, click the Flow Control Neg. checkbox.
Flow control negotiation is enabled by default.
Note
Flow control is enabled only when the attached device is set for auto-negotiation. If auto-negotiation has been provisioned onthe attached device but the negotiation status indicates no flow control, check the auto-negotiation settings on the attached device for interoperation with the asymmetric flow control capability of the G1000-4.
Step 6
To permit the acceptance of jumbo size Ethernet frames, click the Max. Size column to reveal the pull-down menu and select Jumbo.
The maximum accepted frame size is set to Jumbo by default.
Step 7
Click Apply.
Note
Reprovisioning an Ethernet port on the G1000-4 card does not reset the Ethernet statistics for that port. See the "Statistics Window" section for information about clearing the statistics for the G1000-4 port. Reprovisioning an Ethernet port on the E-series Ethernet cards resets the Ethernet statistics for that port.
9.1.7 G1000-4 Gigabit Interface Converters
Gigabit interface converters (GBICs) are hot-swappable input/output devices that plug into a Gigabit Ethernet card to link the port with the fiber-optic network. Figure 9-6 shows a GBIC. The type of GBIC determines the maximum distance that the Ethernet traffic will travel from the card to the next network device.
The G1000-4 card supports three types of standard Cisco GBICs; SX, LX and ZX. Support for the copper-media CX GBIC will be added in a future release.
1000BaseSX operates on multi-mode fiber optic link spans of up to 550 m in length. 1000BaseLX operates on single-mode fiber optic links of up to 10 km in length. 1000BaseZX operates on single-mode fiber optic link spans of up to 70 km in length, and link spans of up to 100 km are possible using premium single mode fiber or dispersion shifted single mode fiber.
Figure 9-6 A gigabit interface converter
Table 9-1 shows the available GBICs for the G1000-4 card.
Table 9-1 G1000-4 Card GBICs
GBIC
|
Span Length
|
Product Number
|
Short wavelength (1000BaseSX)
|
550m
|
15454-GBIC-SX
|
Long wavelength/long haul (1000BaseLX)
|
5km
|
15454-GBIC-LX
|
Extended Distance (1000BaseZX)
|
70km
|
15454-GBIC-ZX
|
Caution 
Use only GBICs certified for use in the ONS 15454 G1000-4 card (Cisco product numbers 15454-GBIC-SX and 15454-GBIC-LX).
For GBIC installation and cabling instructions, see the "Fiber-Optic Cable Installation" section on page 1-52.
9.2 E Series Cards
The E series cards incorporate layer 2 switching, while the G series card is a straight mapper card. The ONS 15454 E series cards include the E100T-12/E100T-G and E1000-2/E1000-2-G. E series cards support VLAN, IEEE 802.1Q, spanning tree, and IEEE 802.1D. An ONS 15454 holds a maximum of ten Ethernet cards, and you can insert Ethernet cards in any multipurpose slot. For card specifications, see the Card Reference chapter in the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
9.2.1 E100T-12/E100T-G Card
E100T-12/E100T-G cards provide twelve switched, IEEE 802.3-compliant 10/100 Base-T Ethernet ports. The ports detect the speed of an attached device by auto-negotiation and automatically connect at the appropriate speed and duplex mode, either half or full duplex, and determine whether to enable or disable flow control. The E100T-G is the functional equivalent of the E100T-12. An ONS 15454 using XC10G cards requires the G versions of the E series Ethernet cards.
9.2.2 E1000-2/E1000-2-G Card
E1000-2/E1000-2-G cards provides two switched, IEEE 802.3-compliant Gigabit Ethernet (1000 Mbps) ports that support full duplex operation. The E1000-2 is the functional equivalent of the E1000-2-G. An ONS 15454 using XC10G cards requires the G versions of the E series Ethernet cards.
9.2.3 E Series LEDs
E series Ethernet card faceplates have three card-level LEDs and a pair of port-level LEDs next to each port. The SF LED is inactive.
Table 9-2 E Series Card-Level LEDS
LED State
|
Description
|
Red FAIL LED
|
The red FAIL LED indicates that the card's processor is not ready or a catastrophic software failure occurred on the Ethernet card. As part of the boot sequence, the FAIL LED is turned on until the software deems the card operational.
|
Green ACT LED
|
A green ACT LED provides the operational status of the card. When the ACT LED is green it indicates that the Ethernet card is active and the software is operational.
|
Table 9-3 E Series Port-Level LEDs
LED State
|
Description
|
Amber
|
Transmitting and Receiving
|
Solid Green
|
Idle and Link Integrity
|
Green Light Off
|
Inactive Connection or Unidirectional Traffic
|
For detailed specifications of the Ethernet cards, refer to the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
9.2.4 E Series Port Provisioning
This section explains how to provision Ethernet ports on an E series Ethernet card. Most provisioning requires filling in two fields: Enabled and Mode. However, you can also map incoming traffic to a low priority or a high priority queue using the Priority column, and you can enable spanning tree with the Stp Enabled column. For more information about spanning tree, see the "E Series Spanning Tree (IEEE 802.1D)" section. The Status column displays information about the port's current operating mode, and the Stp State column provides the current spanning tree status.
Procedure: Provision E Series Ethernet Ports
Step 1
Display CTC and double-click the card graphic to open the Ethernet card.
Step 2
Click the Provisioning > Port tabs.
Figure 9-7 shows the Provisioning tab with the Port function subtab selected.
Figure 9-7 Provisioning E-100 Series Ethernet ports
Step 3
From the Port screen, choose the appropriate mode for each Ethernet port. Valid choices for the E100T-12/E100T-G card are Auto, 10 Half, 10 Full, 100 Half, or 100 Full. Valid choices for the E1000-2/E1000-2-G card are 1000 Full or Auto.
Both 1000 Full and Auto mode set the E1000-2 port to the 1000 Mbps and Full duplex operating mode; however, flow control is disabled when 1000 Full is selected. Choosing Auto mode enables the E1000-2 card to auto-negotiate flow control. Flow control is a mechanism that prevents network congestion by ensuring that transmitting devices do not overwhelm receiving devices with data. The E1000-2 port handshakes with the connected network device to determine if that device supports flow control.
Step 4
Click the Enabled checkbox(s) to activate the corresponding Ethernet port(s).
Step 5
Click Apply.
Your Ethernet ports are now provisioned and ready to be configured for VLAN membership.
Step 6
Repeat this procedure for all other cards that will be in the VLAN.
9.2.5 E-Series Gigabit Interface Converters
Gigabit interface converters (GBICs) are hot-swappable input/output devices that plug into a Gigabit Ethernet card to link the port with the fiber-optic network. The type of GBIC determines the maximum distance that the Ethernet traffic will travel from the card to the next network device.
The E1000-2/E1000-2-G card supports SX and LX GBICs.
1000BaseSX operates on multi-mode fiber optic link spans of up to 550 m in length. 1000BaseLX operates on single-mode fiber optic links of up to 10 km in length.
Table 9-4 shows the available GBICs.
Table 9-4 Available GBICs
GBIC
|
Span Length
|
Product Number
|
Short wavelength (1000BaseSX)
|
550m
|
15454-GBIC-SX
|
Long wavelength/long haul (1000BaseLX)
|
5km
|
15454-GBIC-LX
|
For GBIC installation and cabling instructions, see the "Fiber-Optic Cable Installation" section on page 1-52.
Caution 
Use only GBICs certified for use in the ONS 15454 E1000-2/E1000-2-G card, Cisco product numbers 15454-GBIC-SX and 15454-GBIC-LX.
Caution
E1000-2/E1000-2-G cards lose traffic for approximately 30 seconds when an ONS 15454 database is restored. Traffic is lost during the period of spanning tree reconvergence. The CARLOSS alarm will appear and clear during this period.
9.3 E Series Multicard and Single-Card EtherSwitch
The ONS 15454 enables multicard and single-card EtherSwitch modes for E series cards. At the Ethernet card view in CTC, click the Provisioning > Card tabs to reveal the Card Mode option.
9.3.1 E Series Multicard EtherSwitch
Multicard EtherSwitch provisions two or more Ethernet cards to act as a single layer 2 switch. It supports one STS-6c shared packet ring, two STS-3c shared packet rings, or six STS-1 shared packet rings. The bandwidth of the single switch formed by the Ethernet cards matches the bandwidth of the provisioned Ethernet circuit up to STS-6c worth of bandwidth.
Figure 9-8 A Multicard EtherSwitch configuration
Caution 
Whenever you drop two STS-3c multicard EtherSwitch circuits onto an Ethernet card and delete only the first circuit, you should not provision STS-1 circuits to the card without first deleting the remaining STS-3c circuit. If you attempt to create a STS-1 circuit after deleting the first STS-3c circuit, the STS-1 circuit will not work and no alarms will indicate this condition. To avoid this condition, delete the second STS-3c prior to creating the STS-1 circuit.
9.3.2 E Series Single-Card EtherSwitch
Single-card EtherSwitch allows each Ethernet card to remain a single switching entity within the ONS 15454 shelf. This option allows a full STS-12c worth of bandwidth between two Ethernet circuit points. Figure 9-9 illustrates a single-card EtherSwitch configuration.
Figure 9-9 A Single-card EtherSwitch configuration
Seven scenarios exist for provisioning single-card EtherSwitch bandwidth:
1.
STS 12c
2.
STS 6c + STS 6c
3.
STS 6c + STS 3c + STS 3c
4.
STS 6c + 6 STS-1s
5.
STS 3c + STS 3c +STS 3c +STS 3c
6.
STS 3c +STS 3c + 6 STS-1s
7.
12 STS-1s
Note
When configuring scenario 3, the STS 6c must be provisioned before either of the STS 3c circuits.
9.3.3 ONS 15454 E Series and ONS 15327 EtherSwitch Circuit Combinations
The following table shows the Ethernet circuit combinations available in ONS 15454 E series cards and ONS 15327s.
Table 9-5 ONS 15454 and ONS 15327 Ethernet Circuit Combinations
15327 Single-Card
|
15327 Multicard
|
15454 E Series Single-Card
|
15454 E Series Multicard
|
six STS-1s
|
three STS-1s
|
one STS 12c
|
six STS-1s
|
two STS 3cs
|
one STS 3c
|
two STS 6cs
|
two STS 3cs
|
one STS 6c
|
|
one STS 6c and two STS 3cs
|
one STS 6c
|
one STS 12c
|
|
one STS 6c and six STS-1s
|
|
| |
|
four STS 3cs
|
|
| |
|
two STS 3cs and six STS-1s
|
|
| |
|
twelve STS-1s
|
|
9.4 E Series Circuit Configurations
Ethernet circuits can link ONS nodes through point-to-point, shared packet ring, or hub and spoke configurations. Two nodes usually connect with a point-to-point configuration. More than two nodes usually connect with a shared packet ring configuration or a hub and spoke configuration. This section includes procedures for creating these configurations and also explains how to create Ethernet manual cross-connects. Ethernet manual cross-connects allow you to cross connect individual Ethernet circuits to an STS channel on the ONS 15454 optical interface and also to bridge non-ONS SONET network segments.
9.4.1 E-Series Circuit Protection
Different combinations of E-Series circuit configurations and SONET network topologies offer different levels of E-Series circuit protection. Table 9-6 details the available protection.
Table 9-6 Protection for E-Series Circuit Configurations
Configuration
|
UPSR
|
BLSR
|
1 + 1
|
Point-to-Point Multicard Etherswitch
|
None
|
SONET
|
SONET
|
Point-to-Point Single-Card Etherswitch
|
SONET
|
SONET
|
SONET
|
Shared Packet Ring (multicard only)
|
STP
|
SONET
|
SONET
|
Common Control Card Switch
|
STP
|
STP
|
STP
|
Caution 
Multi-card Etherswitch circuits are not supported on UPSR.
Note
Before making Ethernet connections, choose a STS-1, STS-3c, STS-6c, or STS-12c circuit size.
Note
When making an STS-12c Ethernet circuit, Ethernet cards must be configured as Single-card EtherSwitch. Multicard mode does not support STS-12c Ethernet circuits.
9.4.2 E Series Point-to-Point Ethernet Circuits
The ONS 15454 can set up a point-to-point (straight) Ethernet circuit as Single-card or Multicard. Multicard EtherSwitch limits bandwidth to STS-6c of bandwidth between two Ethernet circuit points, but allows adding nodes and cards and making a shared packet ring. Single-card EtherSwitch allows a full STS-12c of bandwidth between two Ethernet circuit points.
Figure 9-10 A Multicard EtherSwitch point-to-point circuit
Figure 9-11 A Single-card Etherswitch point-to-point circuit
Procedure: Provision an E Series EtherSwitch Point-to-Point Circuit (Multicard or Single-Card)
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoint nodes.
Step 2
Double-click one of the Ethernet cards that will carry the circuit.
Step 3
Click the Provisioning > Card tabs.
Step 4
If you are building a Multicard Etherswitch point-to-point circuit:
a.
Under Card Mode, verify that Multi-card EtherSwitch Group is checked.
b.
If Multi-card EtherSwitch Group is not checked, check it and click Apply.
c.
Repeat Steps 2 - 4 for all other Ethernet cards in the ONS 15454 that will carry the circuit.
If you are building a Single-card Etherswitch circuit:
d.
Under Card Mode, verify that Single-card EtherSwitch is checked.
e.
If Single-card EtherSwitch is not checked, check it and click Apply.
Step 5
Navigate to the other ONS 15454 Ethernet circuit endpoint.
Step 6
Repeat Steps 2 - 5.
Step 7
Click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens.
Step 8
In the Name field, type a name for the circuit.
Step 9
From the Type pull-down menu, choose STS.
Note
The VT and VT Tunnel types do not apply to Ethernet circuits.
Step 10
Choose the size of the circuit from the Size pull-down menu.
The valid circuit sizes for an Ethernet Multicard circuit are STS-1, STS-3c and STS-6c.
The valid circuit sizes for an Ethernet Single-card circuit are STS-1, STS-3c, STS-6c and STS-12c.
Step 11
Verify that the Bidirectional checkbox is checked and click Next.
The Circuit Creation (Circuit Source) dialog box opens ( Figure 9-12).
Figure 9-12 Choosing a circuit source
Step 12
Choose the circuit source from the Node menu. Either end node can be the circuit source.
Step 13
If you are building a Multicard EtherSwitch circuit, choose Ethergroup from the Slot menu and click Next.
Step 14
If you are building a Single-card EtherSwitch circuit, from the Slot menu choose the Ethernet card where you enabled the Single-card Etherswitch and click Next.
The Circuit Creation (Destination) dialog box opens.
Step 15
Choose the circuit destination from the Node menu, (in this example, Node 2). Choose the node that is not the source.
Step 16
If you are building a Multicard EtherSwitch circuit choose Ethergroup from the Slot menu and click Next.
Step 17
If you are building a Single-card EtherSwitch circuit, from the Slot menu choose the Ethernet card for which you enabled the Single-card Etherswitch and click Next.
The Circuit Creation (Circuit VLAN Selection) dialog box opens.
Step 18
Create the VLAN:
a.
Click the New VLAN tab.
b.
Assign an easily-identifiable name to your VLAN.
c.
Assign a VLAN ID.
Note
The VLAN ID should be the next available number between 2 and 4093 that is not already assigned to an existing VLAN. Each ONS 15454 network supports a maximum of 509 user-provisionable VLANs.
d.
Click OK.
e.
Highlight the VLAN name and click the >> tab to move the available VLAN(s) to the Circuit VLANs column.
Step 19
Click Next.
The Circuit Creation (Circuit Routing Preferences) dialog box opens.
Step 20
Confirm that the following information about the point-to-point circuit is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
VLANs on the circuit
•
ONS 15454 nodes included in the circuit
Step 21
Click Finish.
Step 22
You now need to provision the Ethernet ports and assign ports to VLANs. For port provisioning instructions, see the "Provision E Series Ethernet Ports" procedure. For assigning ports to VLANs, see the "Provision Ethernet Ports for VLAN Membership" procedure. For information about manually provisioning circuits, see the "E Series Ethernet Manual Cross-Connects" procedure.
9.4.3 E Series Shared Packet Ring Ethernet Circuits
This section provides steps for creating a shared packet ring ( Figure 9-13). Your network architecture may differ from the example.
Figure 9-13 A shared packet ring Ethernet circuit
Procedure: Provision an E Series Shared Packet Ring
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoints.
Step 2
Double-click one of the Ethernet cards that will carry the circuit.
Step 3
Click the Provisioning > Card tabs.
Step 4
Under Card Mode, verify that Multi-card EtherSwitch Group is checked.
Step 5
If Multi-card EtherSwitch Group is not checked, check it and click Apply.
Step 6
Display the node view.
Step 7
Repeat Steps 2 - 6 for all other Ethernet cards in the ONS 15454 that will carry the shared packet ring.
Step 8
Navigate to the other ONS 15454 endpoint.
Step 9
Repeat Steps 2 - 7.
Step 10
Click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens.
Step 11
In the Name field, type a name for the circuit.
Step 12
From the Type pull-down menu, choose STS.
Note
The VT and VT Tunnel types do not apply to Ethernet circuits.
Step 13
From the Size pull-down menu, choose the size of the circuit.
For shared packet ring Ethernet, valid circuit sizes are STS-1, STS-3c, and STS-6c.
Step 14
Verify that the Bidirectional checkbox is checked.
Note
If you are building a shared packet ring configuration, you must manually provision the circuits.
Step 15
Click Next.
The Circuit Creation (Circuit Source) dialog box opens.
Step 16
From the Node menu, choose the circuit source.
Any shared packet ring node can serve as the circuit source.
Step 17
Choose Ethergroup from the Slot menu and click Next.
The Circuit Creation (Circuit Destination) dialog box opens.
Step 18
Choose the circuit destination from the Node menu.
Step 19
Except for the source node, any shared packet ring node can serve as the circuit destination.
Step 20
Choose Ethergroup from the Slot menu and click Next.
The Circuit Creation (Circuit VLAN Selection) dialog box opens.
Step 21
Create the VLAN:
a.
Click the New VLAN tab.
The Circuit Creation (Define New VLAN) dialog box opens ( Figure 9-14).
Figure 9-14 Choosing a VLAN name and ID
b.
Assign an easily-identifiable name to your VLAN.
c.
Assign a VLAN ID.
This VLAN ID number must be unique. It is usually the next available number not already assigned to an existing VLAN (between 2 and 4093). Each ONS 15454 network supports a maximum of 509 user-provisionable VLANs.
d.
Click OK.
Figure 9-15 Selecting VLANs
e.
Highlight the VLAN name and click the >> tab to move the VLAN(s) from the Available VLANs column to the Circuit VLANs column ( Figure 9-15).
By moving the VLAN from the Available VLANs column to the Circuit VLANs column, all the VLAN traffic is forced to use the shared packet ring circuit you created.
Step 22
Click Next.
Step 23
Uncheck the Route Automatically checkbox and click Next.
Figure 9-16 Adding a span
Step 24
Click either span (green arrow) leading from the source node. ( Figure 9-16)
The span turns white.
Step 25
Click Add Span.
The span turns blue and adds the span to the Included Spans field.
Step 26
Click the node at the end of the blue span.
Step 27
Click the green span leading to the next node.
The span turns white.
Step 28
Click Add Span.
The span turns blue.
Step 29
Repeat Steps 24 - 27 for every node remaining in the ring. Figure 9-17 shows the Circuit Path Selection dialog box with all the spans selected.
Figure 9-17 Viewing a span
Step 30
Verify that the new circuit is correctly configured.
Note
If the circuit information is not correct, click the Back button and repeat the procedure with the correct information. You can also click Finish, delete the completed circuit, and begin the procedure again.
Step 31
Click Finish.
Step 32
You now need to provision the Ethernet ports and assign ports to VLANs. For port provisioning instructions, see the "Provision E Series Ethernet Ports" procedure. For assigning ports to VLANs, see the "Provision Ethernet Ports for VLAN Membership" procedure.
9.4.4 E Series Hub and Spoke Ethernet Circuit Provisioning
This section provides steps for creating a hub and spoke Ethernet circuit configuration. The hub and spoke configuration connects point-to-point circuits (the spokes) to an aggregation point (the hub). In many cases, the hub links to a high-speed connection and the spokes are Ethernet cards. Figure 9-18 illustrates a sample hub and spoke ring. Your network architecture may differ from the example.
Figure 9-18 A Hub and Spoke Ethernet circuit
Procedure: Provision an E Series Hub and Spoke Ethernet Circuit
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoints.
Step 2
Double-click the Ethernet card that will create the circuit.
Step 3
Click the Provisioning > Card tabs.
Step 4
Under Card Mode, check the Single-card EtherSwitch checkbox.
If Single-card EtherSwitch is not checked, check it and click Apply.
Step 5
Navigate to the other ONS 15454 endpoint and repeat Steps 2 - 4.
Step 6
Display the node view or network view.
Step 7
Click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens.
Step 8
In the Name field, type a name for the circuit.
Step 9
From the Type pull-down menu, choose STS.
Note
The types VT and VT Tunnel do not apply to Ethernet circuits.
Step 10
Choose the size of the circuit from the Size pull-down menu.
Step 11
Verify that the Bidirectional checkbox is checked and click Next.
The Circuit Creation (Circuit Source) dialog box opens.
Step 12
From the Node menu, choose the circuit source.
Either end node can be the circuit source.
Step 13
From the Slot menu, choose the Ethernet card where you enabled the single-card EtherSwitch and click Next.
The Circuit Creation (Circuit Destination) dialog box opens.
Step 14
Choose the circuit destination from the Node menu.
Choose the node that is not the source.
Step 15
From the Slot menu, choose the Ethernet card where you enabled the single-card EtherSwitch and click Next.
The Circuit Creation (Circuit VLAN Selection) dialog box opens ( Figure 9-12).
Step 16
Create the VLAN:
a.
Click the New VLAN tab.
The Circuit Creation (Define New VLAN) dialog box opens ( Figure 9-14).
b.
Assign an easily-identifiable name to your VLAN.
c.
Assign a VLAN ID.
This should be the next available number (between 2 and 4093) not already assigned to an existing VLAN. Each ONS 15454 network supports a maximum of 509 user-provisionable VLANs.
d.
Click OK.
e.
Highlight the VLAN name and click the >> tab to move the VLAN(s) from the Available VLANs column to the Circuit VLANs column ( Figure 9-15).
Step 17
Click Next.
The Circuit Creation (Circuit Routing Preferences) dialog box opens.
Step 18
Confirm that the following information about the point-to-point circuit is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
VLANs that will be transported across this circuit
•
ONS 15454 nodes included in this circuit
Note
If the circuit information is not correct, click the Back button and repeat the procedure with the correct information. You can also click Finish, delete the completed circuit, and start the procedure from the beginning.
Step 19
Click Finish.You must now provision the second circuit and attach it to the already-created VLAN.
Step 20
Log into the ONS 15454 Ethernet circuit endpoint for the second circuit.
Step 21
Double-click the Ethernet card that will create the circuit. The CTC card view displays.
Step 22
Click the Provisioning > Card tabs.
Step 23
Under Card Mode, check Single-card EtherSwitch.
If the Single-card EtherSwitch checkbox is not checked, check it and click Apply.
Step 24
Log into the other ONS 15454 endpoint for the second circuit and repeat Steps 21 - 23.
Step 25
Display the CTC node view.
Step 26
Click the Circuits tab and click Create.
Step 27
Choose STS from the Type pull-down menu.
Note
The types VT and VT Tunnel do not apply to Ethernet circuits.
Step 28
Choose the size of the circuit from the Size pull-down menu.
Step 29
Verify that the Bidirectional checkbox is checked and click Next.
Step 30
Choose the circuit source from the Node menu and click Next.
Either end node can be the circuit source.
Step 31
Choose the circuit destination from the Node menu.
Choose the node that is not the source.
Step 32
From the Slot menu, choose the Ethernet card where you enabled the single-card EtherSwitch and click Next.
The Circuit Creation (Circuit VLAN Selection) dialog box is displayed.
Step 33
Highlight the VLAN that you created for the first circuit and click the >> tab to move the VLAN(s) from the Available VLANs column to the Selected VLANs column.
Step 34
Click Next and click Finish.
Step 35
You now need to provision the Ethernet ports and assign ports to VLANs. For port provisioning instructions, see the "Provision E Series Ethernet Ports" procedure. For assigning ports to VLANs, see the "Provision Ethernet Ports for VLAN Membership" procedure.
9.4.5 E Series Ethernet Manual Cross-Connects
ONS 15454s require end-to-end CTC visibility between nodes for normal provisioning of Ethernet circuits. When other vendors' equipment sits between ONS 15454s, OSI/TARP- based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent this lack of continuous DCC, the Ethernet circuit must be manually cross connected to an STS channel riding through the non-ONS network. This allows an Ethernet circuit to run from ONS node to ONS node utilizing the non-ONS network.
Note
Provisioning manual cross-connects for Multicard Etherswitch circuits is a separate procedure from provisioning manual cross-connects for Single-card Etherswitch circuits. Both procedures are listed below.
Figure 9-19 Ethernet manual cross-connects
Procedure: Provision an E Series Single-card EtherSwitch Manual Cross-Connect
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoints.
Step 2
Double-click one of the Ethernet cards that will carry the circuit.
Step 3
Click the Provisioning > Card tabs.
Step 4
Under Card Mode, verify that Single-card EtherSwitch is checked.
If the Single-card EtherSwitch is not checked, check it and click Apply.
Step 5
Display the node view.
Step 6
Click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens ( Figure 9-20).
Figure 9-20 Creating an Ethernet circuit
Step 7
In the Name field, type a name for the circuit.
Step 8
From the Type pull-down menu, choose STS.
Note
The types VT and VT Tunnel do not apply to Ethernet circuits.
Step 9
Choose the size of the circuit from the Size pull-down menu.
The valid circuit sizes for an Ethernet Multicard circuit are STS-1, STS-3c and STS-6c.
Step 10
Verify that the Bidirectional checkbox is checked and click Next.
The Circuit Creation (Circuit Source) dialog box opens.
Step 11
From the Node menu, choose the current node as the circuit source.
Step 12
From the Slot menu, choose the Ethernet card that will carry the circuit and click Next.
The Circuit Creation (Circuit Destination) dialog box opens.
Step 13
From the Node menu, choose the current node as the circuit destination.
Step 14
From the Slot menu, choose the optical card that will carry the circuit.
Step 15
Choose the STS that will carry the circuit from the STS menu and click Next.
Note
For Ethernet manual cross-connects, the same node serves as both source and destination.
The Circuit Creation (Circuit VLAN Selection) dialog box opens ( Figure 9-15).
Step 16
Create the VLAN:
a.
Click the New VLAN tab.
The Circuit Creation (Define New VLAN) dialog box opens ( Figure 9-14).
b.
Assign an easily-identifiable name to your VLAN.
c.
Assign a VLAN ID.
The VLAN ID should be the next available number (between 2 and 4093) that is not already assigned to an existing VLAN. Each ONS 15454 network supports a maximum of 509 user-provisionable VLANs.
d.
Click OK.
Figure 9-21 Selecting VLANs
e.
Highlight the VLAN name and click the arrow >> tab to move the VLAN(s) from the Available VLANs column to the Circuit VLANs column ( Figure 9-21).
Step 17
Click Next.
The Circuit Creation (Circuit Routing Preferences) dialog box opens.
Step 18
Confirm that the following information is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
VLANs on this circuit
•
ONS 15454 nodes included in this circuit
Note
If the circuit information is not correct use the Back button, then redo the procedure with the correct information. Alternately, you can click Finish, then delete the completed circuit and start the procedure from the beginning.
Step 19
Click Finish.
Step 20
You now need to provision the Ethernet ports and assign ports to VLANs. For port provisioning instructions, see the "Provision E Series Ethernet Ports" procedure. For assigning ports to VLANs, see the "Provision Ethernet Ports for VLAN Membership" procedure.
Step 21
After assigning the ports to the VLANs, repeat Steps 1 - 19 at the second ONS 15454 Ethernet manual cross-connect endpoint.
Note
The appropriate STS circuit must exist in the non-ONS 15454 equipment to connect the two STSs from the ONS 15454 Ethernet manual cross-connect endpoints.
Caution 
If a CARLOSS alarm repeatedly appears and clears on an Ethernet manual cross connect,
the two Ethernet circuits may have a circuit-size mismatch. For example, a circuit size of STS-3c was configured on the first ONS 15454 and circuit size of STS-12c was configured on the second ONS 15454. To troubleshoot this occurrence of the CARLOSS alarm, refer to Step 9 of the CARLOSS alarm troubleshooting procedure in the Alarm Troubleshooting chapter of the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
Procedure: Provision an E Series Multicard EtherSwitch Manual Cross-Connect
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoints.
Step 2
Double-click one of the Ethernet cards that will carry the circuit.
Step 3
Click the Provisioning > Card tabs.
Step 4
Under Card Mode, verify that Multi-card EtherSwitch Group is checked.
If the Multicard-card EtherSwitch Group is not checked, check it and click Apply.
Step 5
Display the node view.
Step 6
Repeat Steps 2 - 5 for any other Ethernet cards in the ONS 15454 that will carry the circuit.
Step 7
Click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens ( Figure 9-22).
Figure 9-22 Creating an Ethernet circuit
Step 8
In the Name field, type a name for the circuit.
Step 9
From the Type pull-down menu, choose STS.
Note
The types VT and VT Tunnel do not apply to Ethernet circuits.
Step 10
Choose the size of the circuit from the Size pull-down menu.
The valid circuit sizes for an Ethernet Multicard circuit are STS-1, STS-3c and STS-6c.
Step 11
Verify that the Bidirectional checkbox is checked and click Next.
The Circuit Creation (Circuit Source) dialog box opens.
Step 12
From the Node menu, choose the current node as the circuit source.
Step 13
Choose Ethergroup from the Slot menu and click Next.
The Circuit Creation (Circuit Destination) dialog box opens.
Step 14
From the Node menu, choose the current node as the circuit destination.
Step 15
Choose Ethergroup from the Slot menu and click Next.
Note
For the Ethernet manual cross-connect, the destination and source should be the same node.
The Circuit Creation (Circuit VLAN Selection) dialog box opens ( Figure 9-15).
Step 16
Create the VLAN:
a.
Click the New VLAN tab.
The Circuit Creation (Define New VLAN) dialog box opens ( Figure 9-14).
b.
Assign an easily-identifiable name to your VLAN.
c.
Assign a VLAN ID.
The VLAN ID should be the next available number (between 2 and 4093) that is not already assigned to an existing VLAN. Each ONS 15454 network supports a maximum of 509 user-provisionable VLANs.
d.
Click OK.
Figure 9-23 Selecting VLANs
e.
Highlight the VLAN name and click the arrow >> tab to move the VLAN(s) from the Available VLANs column to the Circuit VLANs column ( Figure 9-23).
Step 17
Click Next.
The Circuit Creation (Circuit Routing Preferences) dialog box opens.
Step 18
Confirm that the following information is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
VLANs on this circuit
•
ONS 15454 nodes included in this circuit
Note
If the circuit information is not correct use the Back button, then redo the procedure with the correct information. Alternately, you can click Finish, then delete the completed circuit and start the procedure from the beginning.
Step 19
Click Finish.
You now need to provision the Ethernet ports and assign ports to VLANs. For port provisioning instructions, see the "Provision E Series Ethernet Ports" procedure. For assigning ports to VLANs, see the "Provision Ethernet Ports for VLAN Membership" procedure. Return to the following step after assigning the ports to VLANs.
Step 20
Highlight the circuit and click Edit.
The Edit Circuit dialog box opens.
Step 21
Click Drops and click Create.
The Define New Drop dialog box opens.
Step 22
From the Slot menu, choose the optical card that links the ONS 15454 to the non-ONS 15454 equipment.
Step 23
From the Port menu, choose the appropriate port.
Step 24
From the STS menu, choose the STS that matches the STS of the connecting non-ONS 15454 equipment.
Step 25
Click OK.
The Edit Circuit dialog box opens.
Step 26
Confirm the circuit information that displays in the Circuit Information dialog box and click Close.
Step 27
Repeat Steps 1 - 26 at the second ONS 15454 Ethernet manual cross-connect endpoint.
Note
The appropriate STS circuit must exist in the non-ONS 15454 equipment to connect the two ONS 15454 Ethernet manual cross-connect endpoints.
Caution 
If a CARLOSS alarm repeatedly appears and clears on an Ethernet manual cross connect,
the two Ethernet circuits may have a circuit-size mismatch. For example, a circuit size of STS-3c was configured on the first ONS 15454 and circuit size of STS-12c was configured on the second ONS 15454. To troubleshoot this occurrence of the CARLOSS alarm, refer to Step 9 of the CARLOSS alarm troubleshooting procedure in the Alarm Troubleshooting chapter of the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
9.5 G1000-4 Circuit Configurations
This section explains how to provision G1000-4 point-to-point circuits and Ethernet manual cross-connects. Ethernet manual cross-connects allow you to cross connect individual Ethernet circuits to an STS channel on the ONS 15454 optical interface and also to bridge non-ONS SONET network segments.
9.5.1 G1000-4 Point-to-Point Ethernet Circuits
G1000-4 cards support point-to-point circuit configuration. Provisionable circuit sizes are STS 1, STS 3c, STS 6c, STS 9c, STS 12c, STS 24c and STS 48c. Each Ethernet port maps to a unique STS circuit on the SONET side of the G1000-4.
Figure 9-24 A G1000-4 point-to-point circuit
The G1000-4 supports any combination of up to four circuits from the list of valid circuit sizes, however the circuit sizes can add up to no more than 48 STSs. Due to hardware constraints, the initial release of this card (software release 3.2) imposes additional restrictions on the combinations of circuits that can be dropped onto a G1000-4 card. These restrictions are transparently enforced by the ONS 15454, and you do not need to keep track of restricted circuit combinations.
The restriction occurs when a single STS-24c is dropped on a card. In this instance, the remaining circuits on that card can be another single STS-24c or any combination of circuits of STS-12c size or less that add up to no more than 12 STSs (i.e. a total of 36 STSs on the card).
No circuit restrictions are present, if STS-24c circuits are not being dropped on the card. The full 48 STSs bandwidth can be used (for example using either a single STS-48c or 4 STS-12c circuits).
Note
Since the restrictions only apply when STS-24cs are involved but do not apply to two STS-24c circuits on a card, you can easily minimize the impact of these restrictions. Group the STS-24c circuits together on a card separate from circuits of other sizes. The grouped circuits can be dropped on other G1000-4 cards on the ONS 15454.
Note
The G1000-4 uses STS cross-connects only. No VT level cross-connects are used.
Note
All SONET side STS circuits must be contiguous.
Caution 
G1000-4 circuits connect with OC-N cards or other G1000-4 cards. G1000-4 cards do not connect with E-series Ethernet cards.
Caution 
The G1000-4 card requires the XC10G card to operate. The G1000-4 card is not compatible with XC or XCVT cards.
Procedure: Provision a G1000-4 Point-to-Point Circuit
Step 1
Log into an ONS 15454 that you will use as on of the Ethernet circuit endpoint.
Step 2
In CTC node view, click the Circuits tab and click Create.
The Circuit Creation (Circuit Attributes) dialog box opens. ( Figure 9-25)
Figure 9-25 Creating a G1000-4 circuit
Step 3
In the Name field, type a name for the circuit.
Step 4
From the Type pull-down menu, choose STS.
The VT and VT Tunnel types do not apply to Ethernet circuits.
Step 5
Choose the size of the circuit from the Size pull-down menu.
The valid circuit sizes for a G1000-4 circuit are STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, and STS-48c.
Step 6
Verify that the Bidirectional checkbox is checked and click Next.
Note
Users can ignore the Number of Circuits box and the Protected Drops box.
Caution 
If you are provisioning a G1000-4 circuit on a UPSR do not check the
Switch on PDI-P box. Checking the
Switch on PDI-P box may cause unnecessary UPSR protection switches.
The Circuit Creation (Circuit Source) dialog box opens ( Figure 9-26).
Figure 9-26 Circuit Creation dialog box
Step 7
Choose the circuit source node from the Node menu. Either end node can be the circuit source.
Step 8
From the Slot menu choose the slot containing the G1000-4 card that you will use for one end of the point-to-point circuit.
Step 9
From the Port menu choose a port.
Step 10
Click Next.
The Circuit Creation (Destination) dialog box opens.
Step 11
Choose the circuit destination from the Node menu.
Step 12
From the Slot menu choose the slot that holds the G1000-4 card that you will use for the other end of the point-to-point circuit.
Step 13
From the Port menu choose a port.
Step 14
Click Next.
The Circuit Creation (Circuit Routing Preferences) dialog box opens.
Step 15
Confirm that the following information about the point-to-point circuit is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
ONS 15454 nodes included in the circuit
Step 16
Click Finish.
Step 17
If you have not already provisioned the Ethernet card, follow the "Provision G1000-4 Ethernet Ports" procedure.
Note
To change the capacity of a G1000-4 point-to-point circuit, you must delete the original circuit and reprovision a new larger circuit.
9.5.2 G1000-4 Manual Cross-Connects
ONS 15454s require end-to-end CTC visibility between nodes for normal provisioning of Ethernet circuits. When other vendors' equipment sits between ONS 15454s, OSI/TARP-based equipment does not allow tunneling of the ONS 15454 TCP/IP-based DCC. To circumvent a lack of continuous DCC, the Ethernet circuit must be manually cross connected to an STS channel riding through the non-ONS network. This allows an Ethernet circuit to run from ONS node to ONS node while utilizing the non-ONS network.
Note
In this chapter, "cross-connect" and "circuit" have the following meanings: Cross-connect refers to the connections that occur within a single ONS 15454 to allow a circuit to enter and exit an ONS 15454. Circuit refers to the series of connections from a traffic source (where traffic enters the ONS 15454 network) to the drop or destination (where traffic exits an ONS 15454 network).
Figure 9-27 G1000-4 manual cross-connects
Procedure: Provision a G1000-4 Manual Cross-Connect
Step 1
Display CTC for one of the ONS 15454 Ethernet circuit endpoint nodes.
Step 2
Click the Circuits tab and click Create.
Step 3
The Circuit Creation (Circuit Attributes) dialog box opens.
Step 4
In the Name field, type a name for the circuit.
Step 5
From the Type pull-down menu, choose STS.
The VT and VT Tunnel types do not apply to Ethernet circuits.
Step 6
Choose the size of the circuit from the Size pull-down menu.
The valid circuit sizes for a G1000-4 circuit are STS-1, STS-3c, STS-6c, STS-9c, STS-12c, STS-24c, and STS-48c.
Step 7
Verify that the Bidirectional checkbox is checked and click Next.
The Circuit Creation (Circuit Source) dialog box opens ( Figure 9-28).
Figure 9-28 Circuit Creation (Circuit Source) dialog box
Step 8
Choose the circuit source node from the Node menu.
Step 9
From the Slot menu choose the slot containing the Ethernet card.
Step 10
From the Port menu choose a port.
Step 11
Click Next.
The Circuit Creation (Destination) dialog box opens.
Step 12
From the Node menu, choose the current node as the circuit destination.
Step 13
From the Slot menu, choose the optical card that will carry the circuit.
Step 14
Choose the STS that will carry the circuit from the STS menu and click Next.
Note
For Ethernet manual cross-connects, the same ONS 15454 serves as both source and destination.
Step 15
Confirm that the following information is correct:
•
Circuit name
•
Circuit type
•
Circuit size
•
ONS 15454 nodes included in this circuit
Note
If the circuit information is not correct use the Back button, then redo the procedure with the correct information. Alternately, you can click Finish, then delete the completed circuit and start the procedure from the beginning.
Step 16
Click Finish.
Step 17
You now need to provision the Ethernet ports. For port provisioning instructions, see the "Provision G1000-4 Ethernet Ports" procedure.
Step 18
To complete the procedure, repeat Steps 1 - 16 at the second ONS 15454.
Note
The appropriate STS circuit must exist in the non-ONS 15454 equipment to connect the two STSs from the ONS 15454 Ethernet manual cross-connect endpoints.
Caution 
If a CARLOSS alarm repeatedly appears and clears on an Ethernet manual cross-connect,
the two Ethernet circuits may have a circuit-size mismatch. For example, a circuit size of STS-3c was configured on the first ONS 15454 and circuit size of STS-12c was configured on the second ONS 15454. To troubleshoot this cause of the CARLOSS alarm, refer to the Alarm Troubleshooting Chapter of the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
9.6 E Series VLAN Support
Users can provision up to 509 VLANs with the CTC software. Specific sets of ports define the broadcast domain for the ONS 15454. The definition of VLAN ports includes all Ethernet and packet-switched SONET port types. All VLAN IP address discovery, flooding, and forwarding is limited to these ports.
The ONS 15454 802.1Q-based VLAN mechanism provides logical isolation of subscriber LAN traffic over a common SONET transport infrastructure. Each subscriber has an Ethernet port at each site, and each subscriber is assigned to a VLAN. Although the subscriber's VLAN data flows over shared circuits, the service appears to the subscriber as a private data transport.
9.6.1 E Series Q-Tagging (IEEE 802.1Q)
IEEE 802.1Q allows the same physical port to host multiple 802.1Q VLANs. Each 802.1Q VLAN represents a different logical network.
The ONS 15454 works with Ethernet devices that support IEEE 802.1Q and those that do not support IEEE 802.1Q. If a device attached to an ONS 15454 Ethernet port does not support IEEE 802.1Q, the ONS 15454 only uses Q-tags internally. The ONS 15454 associates these Q-tags with specific ports.
With Ethernet devices that do not support IEEE 802.1Q, the ONS 15454 takes non-tagged Ethernet frames that enter the ONS network and uses a Q-tag to assign the packet to the VLAN associated with the ONS network's ingress port. The receiving ONS node removes the Q-tag when the frame leaves the ONS network (to prevent older Ethernet equipment from incorrectly identifying the 8021.Q packet as an illegal frame). The ingress and egress ports on the ONS network must be set to Untag for the process to occur. Untag is the default setting for ONS ports. Example #1 in Figure 9-29 illustrates Q-tag use only within an ONS network.
With Ethernet devices that support IEEE 802.1Q, the ONS 15454 uses the Q-tag attached by the external Ethernet devices. Packets enter the ONS network with an existing Q-tag; the ONS 15454 uses this same Q-tag to forward the packet within the ONS network and leaves the Q-tag attached when the packet leaves the ONS network. Set both entry and egress ports on the ONS network to Tagged for this process to occur. Example #2 in Figure 9-29 illustrates the handling of packets that both enter and exit the ONS network with a Q-tag.
For more information about setting ports to Tagged and Untag, see the "Provision Ethernet Ports for VLAN Membership" procedure.
Figure 9-29 A Q-tag moving through a VLAN
9.6.2 E Series Priority Queuing (IEEE 802.1Q)
Note
IEEE 802.1Q was formerly IEEE 802.1P.
Networks without priority queuing handle all packets on a first-in-first-out basis. Priority queuing reduces the impact of network congestion by mapping Ethernet traffic to different priority levels. The ONS 15454 supports priority queuing. The ONS 15454 takes the eight priorities specified in IEEE 802.1Q and maps them to two queues ( Table 9-7). Q-tags carry priority queuing information through the network.
The ONS 15454 uses a "leaky bucket" algorithm to establish a weighted priority (not a strict priority). A weighted priority gives high-priority packets greater access to bandwidth, but does not totally preempt low-priority packets. During periods of network congestion, roughly 70% of bandwidth goes to the high-priority queue and the remaining 30% goes to the low-priority queue. A network that is too congested will drop packets.
Table 9-7 Priority Queuing
User Priority
|
Queue
|
Allocated Bandwidth
|
0,1,2,3
|
Low
|
30%
|
4,5,6,7
|
High
|
70%
|
Figure 9-30 The priority queuing process
9.6.3 E Series VLAN Membership
This section explains how to provision Ethernet ports for VLAN membership. For initial port provisioning (prior to provisioning VLAN membership) see the "E Series Port Provisioning" section.
Caution 
ONS 15454s propagate VLANs whenever a node appears on the same network view of another node regardless of whether the nodes connect through DCC. For example, if two ONS 15454s without DCC connectivity belong to the same Login Node Group, then whenever CTC gets launched from within this login node group, VLANs propagate from one to another. This happens even though the ONS 15454s do not belong to the same SONET ring.
Procedure: Provision Ethernet Ports for VLAN Membership
The ONS 15454 allows you to configure the VLAN membership and Q-tag handling of individual Ethernet ports.
Step 1
Display the CTC card view for the Ethernet card.
Step 2
Click the Provisioning > VLAN tabs ( Figure 9-31).
Figure 9-31 Configuring VLAN membership for individual Ethernet ports
Step 3
To put a port in a VLAN, click the port and choose either Tagged or Untag. Figure 9-31 shows Port 1 in the red VLAN and Port 2 through Port 12 in the default VLAN. Table 9-8 shows valid port settings.
If a port is a member of only one VLAN, go to that VLAN's row and choose Untag from the Port column. Choose -- for all the other VLAN rows in that Port column. The VLAN with Untag selected can connect to the port, but other VLANs cannot access that port.
If a port is a trunk port, it connects multiple VLANs to an external device, such as a switch, which also supports trunking. A trunk port must have tagging (802.1Q) enabled for all the VLANs that connect to that external device. Choose Tagged at all VLAN rows that need to be trunked. Choose Untag at one or more VLAN rows in the trunk port's column that do not need to be trunked, for example, the default VLAN. Each Ethernet port must attached to at least one untagged VLAN.
Step 4
After each port is in the appropriate VLAN, click Apply.
Table 9-8 Port Settings
Setting
|
Description
|
--
|
A port marked with this symbol does not belong to the VLAN.
|
Untag
|
The ONS 15454 will tag ingress frames and strip tags from egress frames.
|
Tagged
|
The ONS 15454 will handle ingress frames according to VLAN ID; egress frames will not have their tags removed.
|
Note
If Tagged is chosen, the attached external devices must recognize IEEE 802.1Q VLANs.
Note
Both ports on individual E1000-2/E1000-2-G cards cannot be members of the same VLAN.
9.7 E Series Spanning Tree (IEEE 802.1D)
The Cisco ONS 15454 operates spanning tree protocol (STP) according to IEEE 802.1D when an Ethernet card is installed. STP operates over all packet-switched ports including Ethernet and SONET ports. On Ethernet ports, STP is disabled by default but may be enabled with a check box under the Provisioning > Port tabs at the card-level view. On SONET interface ports, STP activates by default and cannot be disabled.
The Ethernet card can enable STP on the Ethernet ports to allow redundant paths to the attached Ethernet equipment. STP spans cards so that both equipment and facilities are protected against failure.
STP detects and eliminates network loops. When STP detects multiple paths between any two network hosts, STP blocks ports until only one path exists between any two network hosts ( Figure 9-32). The single path eliminates possible bridge loops. This is crucial for shared packet rings, which naturally include a loop.
Figure 9-32 An STP blocked path
To remove loops, STP defines a tree that spans all the switches in an extended network. STP forces certain redundant data paths into a standby (blocked) state. If one network segment in the STP becomes unreachable, the spanning-tree algorithm reconfigures the spanning-tree topology and reactivates the blocked path to reestablish the link. STP operation is transparent to end stations, which do not discriminate between connections to a single LAN segment or to a switched LAN with multiple segments. The ONS 15454 supports one STP instance per circuit and a maximum of eight STP instances per ONS 15454.
9.7.1 E Series Multi-Instance Spanning Tree and VLANs
The ONS 15454 can operate multiple instances of STP to support VLANs in a looped topology. You can dedicate separate circuits across the SONET ring for different VLAN groups (i.e., one for private TLS services and one for Internet access). Each circuit runs its own STP to maintain VLAN connectivity in a multi-ring environment.
Procedure: Enable E Series Spanning Tree on Ethernet Ports
Step 1
Display the CTC card view.
Step 2
Click the Provisioning > Port tabs.
Step 3
In the left-hand column, find the applicable port number and check the Stp Enabled checkbox to enable STP for that port.
Step 4
Click Apply.
9.7.2 E Series Spanning Tree Parameters
Default spanning tree parameters are appropriate for most situations. Contact the Cisco Technical Assistance Center (TAC) at 1-877-323-7368 before you change the default STP parameters.
At the node view, click the Maintenance > Etherbridge > Spanning Trees tabs to view spanning tree parameters.
Table 9-9 Spanning Tree Parameters
BridgeID
|
ONS 15454 unique identifier that transmits the configuration bridge protocol data unit (BPDU); the bridge ID is a combination of the bridge priority and the ONS 15454 MAC address
|
TopoAge
|
Amount of time in seconds since the last topology change
|
TopoChanges
|
Number of times the spanning tree topology has been changed since the node booted up
|
DesignatedRoot
|
Identifies the spanning tree's designated root for a particular spanning tree instance
|
RootCost
|
Identifies the total path cost to the designated root
|
RootPort
|
Port used to reach the root
|
MaxAge
|
Maximum time that received-protocol information is retained before it is discarded
|
HelloTime
|
Time interval, in seconds, between the transmission of configuration BPDUs by a bridge that is the spanning tree root or is attempting to become the spanning tree root
|
HoldTime
|
Minimum time period, in seconds, that elapses during the transmission of configuration information on a given port
|
ForwardDelay
|
Time spent by a port in the listening state and the learning state
|
9.7.3 E Series Spanning Tree Configuration
To view the spanning tree configuration, at the node view click the Provisioning tab and Etherbridge subtab.
Table 9-10 Spanning Tree Configuration
Column
|
Default Value
|
Value Range
|
Priority
|
32768
|
0 - 65535
|
Bridge max age
|
20 seconds
|
6 - 40 seconds
|
Bridge Hello Time
|
2 seconds
|
1 - 10 seconds
|
Bridge Forward Delay
|
15 seconds
|
4 - 30 seconds
|
9.7.4 E Series Spanning Tree Map
The Circuit screen shows forwarding spans and blocked spans on the spanning tree map.
Procedure: View the E Series Spanning Tree Map
Step 1
On the circuit screen ( Figure 9-33), double-click an Ethernet circuit.
Figure 9-33 The spanning tree map on the circuit screen
Note
Green represents forwarding spans and purple represents blocked (protect) spans. If you have a packet ring configuration, at least one span should be purple.
9.8 G1000-4 Performance and Maintenance Screens
CTC provides Ethernet performance information, including line-level parameters, the amount of port bandwidth used, and historical Ethernet statistics. CTC also includes spanning tree information, MAC address information, and the amount of circuit bandwidth used. To view spanning tree information, see the "E Series Spanning Tree Parameters" section.
9.8.1 G1000-4 Ethernet Performance Screen
CTC provides Ethernet performance information that include line-level parameters, the amount of port bandwidth used, and historical Ethernet statistics.
9.8.1.1 Statistics Window
The Ethernet statistics screen lists Ethernet parameters at the line level. Display the CTC card view for the Ethernet card and click the Performance > Statistics tabs to display the screen.
Figure 9-34 G1000-4 Statistics window
Table 9-11 G1000-4 Statistics Values
Baseline
|
Clicking Baseline resets the software counters (in that particular CTC client only) temporarily to zero without affecting the actual statistics on the card. From that point on, only the delta in counters are displayed by this CTC. These new base lined counters display only as long as the user displays the Performance pane. If the user navigates to another pane and comes back to the Performance pane, the true actual statistics retained by the card display.
|
Refresh
|
Manually refreshes the statistics
|
Auto-Refresh
|
Sets a time interval for the automatic refresh of statistics
|
Clear
|
Resets the actual counters on the card to zero; this change is recognized by all management clients.
|
Note
The CTC automatically refreshes the counter values once right after a Baseline operation, so if traffic is flowing during a baseline operation, some traffic counts may immediately be observed instead of zero counts.
Note
The Clear button will not cause the G1000-4 card to reset. Provisioning, enabling, or disabling a G1000-4 port will not reset the statistics.
Note
You can apply both the Baseline and the Clear functions to a single port or all ports on the card. To apply Baseline or Clear to a single port, click the port column to highlight the port and click the Baseline or Clear button.
Table 9-12 Ethernet Parameters
Parameter
|
Meaning
|
Link Status
|
Indicates whether the Ethernet link is receiving a valid Ethernet signal (carrier) from the attached Ethernet device; up means present, and down means not present
|
Rx Packets
|
Number of packets received since the last counter reset
|
Rx Bytes
|
Number of bytes received since the last counter reset
|
Tx Packets
|
Number of packets transmitted since the last counter reset
|
Tx Bytes
|
Number of bytes transmitted since the last counter reset
|
Rx Total Errors
|
Total number of receive errors
|
Rx FCS
|
Number of packets with a Frame Check Sequence (FCS) error. FCS errors indicate Frame corruption during transmission
|
Rx Alignment
|
Number of packets with alignment errors; alignment errors are received incomplete frames
|
Rx Runts
|
The total number of frames received that are less than 64 bytes in length and have a CRC error.
|
Rx Giants
|
Number of packets received that are greater than 1548 bytes in length
|
Rx Pause Frames (G series only)
|
Number of received Ethernet 802.3x pause frames
|
Tx Pause Frames (G series only)
|
Number of transmitted 802.3x pause frames
|
Rx Pkts Dropped Internal Congestion (G series only)
|
Number of received packets dropped due to overflow in G1000-4 frame buffer.
|
Tx Pkts Dropped Internal Congestion (G series only)
|
Number of transmit queue drops due to drops in the G1000-4 frame buffer
|
HDLC errors (G series only)
|
HDLC errors received from SONET/SDH (See note)
|

Note
The HDLC errors counter should not be used to count the number of frames dropped due to HDLC errors as each frame can get fragmented into several smaller frames during HDLC error conditions and spurious HDLC frames can also generate. If these counters are incrementing at a time when there should be no SONET path problems that may indicate a problem with the quality of the SONET path. For example, a SONET protection switch causes a set of HLDC errors to generate. The actual values of these counters is less relevant than the fact they are changing.
9.8.1.2 Utilization Window
The Utilization subtab shows the percentage of current and past line bandwidth used by the Ethernet ports. Display the CTC card view and click the Performance and Utilization tabs to display the screen. From the Interval menu, choose a time segment interval. Valid intervals are 1 minute, 15 minutes, 1 hour, and 1 day. Press Refresh to update the data.
Note
The G Series card does not display statistics on the Trunk Utilization screen, since the G Series card is not a layer two device or switch. The E Series cards is a layer two device or switch and supports the Trunk Utilization screen. The Trunk Utilization screen is similar to the Line Utilization screen, but Trunk Utilization shows the percentage of circuit bandwidth used rather than the percentage of line bandwidth.
9.8.1.3 G Series Utilization Formula
The utilization screen numbers may differ from the numbers encountered on an Ethernet test set. The G series line utilization numbers express the average of ingress and egress traffic as a percentage of the total capacity. Line utilization is calculated with the following formula: (InOctets + OutOctets)*8*100/ (intervals*maxRate). The interval is defined in seconds. maxRate is defined by raw bits/second in one direction for the Ethernet port (i.e. 1 Gbps). maxRate is multiplied by 2 in the denominator to determine the raw bit rate in both directions.
9.8.1.4 History Window
The Ethernet History subtab lists past Ethernet statistics. At the CTC card view, click the Performance tab and History subtab to view the screen. Choose the appropriate port from the Line menu and the appropriate interval from the Interval menu. Press Refresh to update the data.
9.8.2 G1000-4 Ethernet Maintenance Screen
When a G1000-4 card is installed in the ONS 15454, the Maintenance tab under CTC card view reveals a Maintenance screen with two tabs Loopback and Bandwidth. The Loopback screen allows you put an individual G1000-4 port into a Terminal (inward) loopback. The Bandwidth screen displays the amount of current STS bandwidth the card is using.
Figure 9-35 The G1000-4 Maintenance tab, including loopback and bandwidth information
Table 9-13 G1000-4 Maintenance Screen Values
Loopback
|
Displays the Loopback status of the G1000-4 port
|
#
|
Specifies the specific port number on the G1000-4 card
|
Loopback Type
|
Allows you to configure a port for a Terminal (Inward) loopback or clear the current loopback (none)
|
Apply
|
Enables the Loopback configuration on the port
|
Bandwidth
|
Displays the amount of STS bandwidth provisioned for the G1000-4 card.
|
Caution 
Use Loopback only for the initial test and turn-up of the card and SONET network tests. Do not put the card in Loopback when the G1000-4 ports are in service and attached to a data network. Loopbacks can corrupt the forwarding tables used in data networking.
Note
For more information about using loopbacks with the ONS 15454, see the "Network Tests" section of the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
9.8.3 E-Series Ethernet Performance Screen
CTC provides Ethernet performance information that includes line-level parameters, the amount of port bandwidth used, and historical Ethernet statistics.
9.8.3.1 Statistics Window
The Ethernet statistics screen lists Ethernet parameters at the line level. Table 9-14 defines the parameters. Display the CTC card view for the Ethernet card and click the Performance > Statistics tabs to display the screen.
The Baseline button resets the statistics values on the Statistics screen to zero. The Refresh button manually refreshes statistics. Auto-Refresh sets a time interval for automatic refresh of statistics to occur.
The G1000-4 Statistics screen also has a Clear button. The Clear button sets the values on the card to zero. Using the Clear button will not cause the G1000-4 to reset.
Table 9-14 Ethernet Parameters
Parameter
|
Meaning
|
Link Status
|
Indicates whether link integrity is present; up means present, and down means not present
|
Rx Packets
|
Number of packets received since the last counter reset
|
Rx Bytes
|
Number of bytes received since the last counter reset
|
Tx Packets
|
Number of packets transmitted since the last counter reset
|
Tx Bytes
|
Number of bytes transmitted since the last counter reset
|
Rx Total Errors
|
Total number of receive errors
|
Rx FCS
|
Number of packets with a Frame Check Sequence (FCS) error. FCS errors indicate Frame corruption during transmission
|
Rx Alignment
|
Number of packets with alignment errors; alignment errors are received incomplete frames
|
Rx Runts
|
Number of packets received that are less than 64 bytes in length
|
Rx Giants
|
Number of packets received that are greater than 1518 bytes in length for untagged interfaces and 1522 bytes for tagged interfaces
|
Tx Collisions (E series only)
|
Number of transmit packets that are collisions; the port and the attached device transmitting at the same time caused collisions
|
Tx Excessive (E series only)
|
Number of consecutive collisions
|
Tx Deferred (E series only)
|
Number of packets deferred
|
Rx Pause Frames (G series only)
|
Number of received Ethernet 802.3x pause frames.
|
Tx Pause Frames (G series only)
|
Number of transmitted 802.3x pause frames.
|
Rx Pkts Dropped Internal Congestion (G series only)
|
Number of received packets dropped due to overflow in G1000-4 frame buffer.
|
Tx Pkts Dropped Internal Congestion (G series only)
|
Number of transmit que drops due to drops in G1000-4 frame buffer.
|
9.8.3.2 Line Utilization Window
The Line Utilization window shows the percentage of line, or port, bandwidth used and the percentage used in the past. Display the CTC card view and click the Performance and Utilization tabs to display the screen. From the Interval menu, choose a time segment interval. Valid intervals are 1 minute, 15 minutes, 1 hour, and 1 day. Press Refresh to update the data.
9.8.3.3 E Series Utilization Formula
The utilization screen numbers may differ from the numbers encountered on an Ethernet test set. The line utilization numbers express the average of ingress and egress traffic as a percentage of the total capacity. Line utilization is calculated with the following formula: (InOctets + OutOctets)*8 bits/octets/100/ intervals*(maxRate*2). Intervals is defined in seconds. maxRate is defined by raw bits/second in one direction for the circuit. maxRate is multiplied by 2 in the denominator to get the raw bit rate in both directions.
Table 9-15 maxRate for STS circuits
STS-1
|
51840000
|
STS-3c
|
155000000
|
STS-6c
|
311000000
|
STS-12c
|
622000000
|
This formula does not take into account the HDLC headers, SONET header and inter-frame gap. This means that the line utilization numbers will not reach 100%. It also means that smaller packet sizes will result in lower utilization figures.
Note
Line utilization numbers express the average of ingress and egress traffic as a percentage of capacity.
9.8.3.4 History Window
The Ethernet History screen lists past Ethernet statistics. At the CTC card view, click the Performance tab and History subtab to view the screen. Choose the appropriate port from the Line menu and the appropriate interval from the Interval menu. Press Refresh to update the data. Table 9-14 defines the listed parameters.
9.8.4 E-Series Ethernet Maintenance Screen
Display an E-series Ethernet card in CTC card view and choose the Maintenance tab to display MAC address and bandwidth information.
9.8.4.1 MAC Table Window
A MAC address is a hardware address that physically identifies a network device. The ONS 15454 MAC table, also known as the MAC forwarding table, will allow you to see all the MAC addresses attached to the enabled ports of an E series Ethernet card or an E series Ethernet Group. This includes the MAC address of the network device attached directly to the port and any MAC addresses on the network linked to the port. The MAC addresses table lists the MAC addresses stored by the ONS 15454 and the VLAN, Slot/Port/STS, and circuit that links the ONS 15454 to each MAC address ( Figure 9-36).
Figure 9-36 MAC addresses recorded in the MAC table
Procedure: Retrieve the MAC Table Information
Step 1
Click the Maintenance > EtherBridge > MAC Table tabs.
Step 2
Select the appropriate Ethernet card or Ethergroup from the Layer 2 Domain pull-down menu.
Step 3
Click Retrieve for the ONS 15454 to retrieve and display the current MAC IDs.
Note
Click Clear to clear the highlighted rows and click Clear All to clear all displayed rows.
9.8.4.2 Trunk Utilization Window
The Trunk Utilization screen is similar to the Line Utilization screen, but Trunk Utilization shows the percentage of circuit bandwidth used rather than the percentage of line bandwidth used. Click the Maintenance > Ether Bridge > Trunk Utilization tabs to view the screen. Choose a time segment interval from the Interval menu.
Note
The percentage shown is the average of ingress and egress traffic.
9.9 Remote Monitoring Specification Alarm Thresholds
The ONS 15454 features Remote Monitoring (RMON) that allows network operators to monitor the health of the network with a Network Management System (NMS). For a detailed description of the ONS SNMP implementation, see the Chapter 11, "SNMP."
One of the ONS 15454's RMON MIBs is the Alarm group. The alarm group consists of the alarmTable. An NMS uses the alarmTable to find the alarm-causing thresholds for network performance. The thresholds apply to the current 15-minute interval and the current 24-hour interval. RMON monitors several variables, such as Ethernet collisions, and triggers an event when the variable crosses a threshold during that time interval. For example, if a threshold is set at 1000 collisions and 1001 collisions occur during the 15-minute interval, an event triggers. CTC allows you to provision these thresholds for Ethernet statistics.
Note
You can find performance monitoring specifications for all other cards in the Cisco ONS 15454 Troubleshooting and Maintenance Guide.
Note
The following tables define the variables you can provision in CTC. For example, to set the collision threshold, choose etherStatsCollisions from the Variable menu.
Table 9-16 Ethernet Threshold Variables (MIBs)
Variable
|
Definition
|
iflnOctets
|
Total number of octets received on the interface, including framing octets
|
iflnUcastPkts
|
Total number of unicast packets delivered to an appropriate protocol
|
ifInMulticastPkts
|
Number of multicast frames received error free
|
ifInBroadcastPkts
|
The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer.
|
ifInDiscards
|
The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.
|
iflnErrors
|
Number of inbound packets discarded because they contain errors
|
ifOutOctets
|
Total number of transmitted octets, including framing packets
|
ifOutUcastPkts
|
Total number of unicast packets requested to transmit to a single address
|
ifOutMulticastPkts
|
Number of multicast frames transmitted error free
|
ifOutBroadcastPkts
|
The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent
|
ifOutDiscards
|
The number of outbound packets which were chosen to be discarded even though no errors had been detectedto prevent their being transmitted.
|
dot3statsAlignmentErrors
|
Number of frames with an alignment error, i.e., the length is not an integral number of octets and the frame cannot pass the Frame Check Sequence (FCS) test
|
dot3StatsFCSErrors
|
Number of frames with framecheck errors, i.e., there is an integral number of octets, but an incorrect Frame Check Sequence (FCS)
|
dot3StatsSingleCollisionFrames
|
Number of successfully transmitted frames that had exactly one collision
|
dot3StatsMutlipleCollisionFrame
|
Number of successfully transmitted frames that had multiple collisions
|
dot3StatsDeferredTransmissions
|
Number of times the first transmission was delayed because the medium was busy
|
dot3StatsLateCollision
|
Number of times that a collision was detected later than 64 octets into the transmission (also added into collision count)
|
dot3StatsExcessiveCollision
|
Number of frames where transmissions failed because of excessive collisions
|
dot3StatsCarrierSenseErrors
|
The number of transmission errors on a particular interface that are not otherwise counted.
|
dot3StatsSQETestErrors
|
A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface.
|
etherStatsJabbers
|
Total number of Octets of data (including bad packets) received on the network
|
etherStatsUndersizePkts
|
Number of packets received with a length less than 64 octets
|
etherStatsFragments
|
Total number of packets that are not an integral number of octets or have a bad FCS, and that are less than 64 octets long
|
etherStatsPkts64Octets
|
Total number of packets received (including error packets) that were 64 octets in length
|
etherStatsPkts65to127Octets
|
Total number of packets received (including error packets) that were 65 - 172 octets in length
|
etherStatsPkts128to255Octets
|
Total number of packets received (including error packets) that were 128 - 255 octets in length
|
etherStatsPkts256to511Octets
|
Total number of packets received (including error packets) that were 256 - 511 octets in length
|
etherStatsPkts512to1023Octets
|
Total number of packets received (including error packets) that were 512 - 1023 octets in length
|
etherStatsPkts1024to1518Octets
|
Total number of packets received (including error packets) that were 1024 - 1518 octets in length
|
etherStatsJabbers
|
Total number of packets longer than 1518 octets that were not an integral number of octets or had a bad FCS
|
etherStatsCollisions
|
Best estimate of the total number of collisions on this segment
|
etherStatsCollisionFrames
|
Best estimate of the total number of frame collisions on this segment
|
etherStatsCRCAlignErrors
|
Total number of packets with a length between 64 and 1518 octets, inclusive, that had a bad FCS or were not an integral number of octets in length
|
receivePauseFrames (G series only)
|
The number of received 802.x pause frames
|
transmitPauseFrames(G series only)
|
The number of transmitted 802.x pause frames
|
receivePktsDroppedInternalCongestion(G series only)
|
The number of received framed dropped due to frame buffer overflow as well as other reasons.
|
transmitPktsDroppedInternalCongestion(G series only)
|
The number of frames dropped in the transmit direction due to frame buffer overflow as well as other reasons.
|
txTotalPkts
|
Total number of transmit packets.
|
rxTotalPkts
|
Total number of receive packets
|
Procedure: Creating Ethernet RMON Alarm Thresholds
Step 1
Display the CTC node view.
Step 2
Click the Provisioning > Etherbridge > Thresholds tabs.
Step 3
Click Create.
The Create Ether Threshold dialog box opens.
Figure 9-37 Creating RMON thresholds
Step 4
From the Slot menu, choose the appropriate Ethernet card.
Step 5
From the Port menu, choose the Port on the Ethernet card.
Step 6
From the Variable menu, choose the variable. Table 9-16 lists and defines the Ethernet Threshold Variables available in this field.
Step 7
From Alarm Type, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.
Step 8
From the Sample Type pull-down menu, choose either Relative or Absolute. Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of any time period.
Step 9
Type in an appropriate number of seconds for the Sample Period.
Step 10
Type in the appropriate number of occurrences for the Rising Threshold.
Note
For a rising type of alarm to fire, the measured value must shoot from below the falling threshold to above the rising threshold. For example, if a network is running below a falling threshold of 400 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, these occurrences fire an alarm.
Step 11
Type in the appropriate number of occurrences for the Falling Threshold. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 minutes subsides and creates only 799 collisions in 15 minutes, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15 minute period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12
Click the OK button to complete the procedure.