Frame Relay Status and Configuration

Make Calls Outside CUG

This Þeld is only conÞgurable if the port is a CUG member; it speciÞes whether the logical port can make calls to network users outside that CUG.

Encapsulation Method

This Þeld speciÞes whether the trafÞc will be encapsulated by Annex G or RS 1490 for transmission across the frame relay network.

With Annex G, an LAPB frame is encapsulated immediately following the frame relay header (ßag, 2-byte T1.618 header, LAPB address, LAPB control, LAPB I-Þeld, [x.25/x.75]). With RFC 1490, the order is: T1.618 header, Q.922 control byte, Q.933 NLPID, 2-byte level-2 protocol ID, 2-byte level-3 protocol ID, LAPB frame.

¥RFC 1490 Ñ The protocols will be identiÞed on the DLCI based on their NLPIDs and (if applicable) level-2 and level-3 headers (e.g., X.25: ßag, T1.618 2-byte header, 0x03 Q.922 control, 0x08 Q.933 NLPID, T1.617 level-2 LAPB PID 0x51 81, T1.617 level-3 PID 0x67 80, LAPB frame).

¥Annex G Ñ Each protocol must be encapsulated in X.25 for transmission over a single DLCI, because Annex G allows the DLCI to be used only by X.25. Each protocol would require its own X.25 virtual circuit and level-3 window.

Blocked Flag

This value will cause the port to be enabled (if No) or disabled (if Yes) when the device is powered up or re-booted.Whichever state is selected, the port will remain in that state until this value is changed or until an enable or disable action is performed.

Flow Control Negotiation

This Þeld allows for negotiation of ßow control parameters (packet and window sizes for data transmission in either direction) on a per-call basis. If No is selected, the Default Packet Size and Setup Packet Window Size will be used. If Yes is selected, a packet and/or window size included in a call packet will be used. (If a packet and/or window size is not included, the default values will be used.)

Throughput Class Negotiation

This Þeld allows for negotiation of throughput classes for data transmission in either direction on a per-call basis. If No is selected, the Default Throughput Class will be used. If Yes is selected, any throughput class included in a call packet will be used. (If a throughput class is not included, the default value will be used.)

Prevent Local Charge

This Þeld is used to prevent calls from being charged to this port. If Yes is selected, incoming calls from the network with Reverse Charging speciÞed will be rejected and outgoing calls will have Reverse Charging inserted if it is not already in the call packet. If No is selected, then calls can be charged to this port.

Configuring Logical Ports

5-19

Page 107
Image 107
Cabletron Systems 1800 manual Make Calls Outside CUG, Encapsulation Method, Flow Control Negotiation, Prevent Local Charge

1800, FRX4000, FRX6000 specifications

Cabletron Systems, a leading player in network management and telecommunications solutions during the late 20th century, introduced several innovative products that played a crucial role in shaping enterprise networking. Among these were the Cabletron FRX6000, FRX4000, and the FRX1800, which delivered advanced features aimed at enhancing network performance, security, and scalability.

The Cabletron FRX6000 was designed as a robust multi-layer switch, ideal for large-scale enterprise environments. It supported extensive routing capabilities, allowing organizations to manage traffic efficiently even under heavy loads. The FRX6000 boasted high throughput rates and low latency, making it suitable for demanding applications. With support for various network protocols, including IP, IPX, and AppleTalk, its adaptability made it a versatile choice for diverse networking needs. Moreover, security features like VLAN support and Access Control Lists (ACLs) provided enhanced protection against potential threats.

Moving to the FRX4000, this model offered a balance between performance and cost-effectiveness. The FRX4000 maintained many of the essential features of its larger counterpart while catering to medium-sized enterprises. It provided Layer 3 routing and could handle multiple simultaneous connections, ensuring seamless communication across departments. The modular design allowed for easy upgrades, enabling businesses to expand their network infrastructure without significant overhauls. This made the FRX4000 an attractive option for organizations looking to optimize their network investments.

Lastly, the FRX1800, designed for small to medium businesses, focused on simplicity and ease of use while still incorporating powerful network management capabilities. Its user-friendly interface made it accessible for organizations lacking extensive IT resources. The FRX1800 provided essential functionalities such as Integrated Layer 2 switching and routing, network monitoring, and basic security features, ensuring that even smaller companies could maintain efficient, reliable networking without overwhelming complexity.

All three models utilized advanced technologies, including a high bandwidth backbone and state-of-the-art switching architecture, to enable fast and reliable data transfer. They also supported Quality of Service (QoS) mechanisms, allowing businesses to prioritize critical applications and ensure consistent performance across the network.

In summary, the Cabletron FRX6000, FRX4000, and FRX1800 were pivotal in enhancing network capabilities, providing organizations with scalable, secure, and high-performance options tailored to their specific needs.