rfc1987.txt
来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 1,398 行 · 第 1/5 页
TXT
1,398 行
Newman, et. al. Informational [Page 20] RFC 1987 GSMP Protocol Specification August 1996 may be indicated for each VC using the Flags field. The VC Activity message is: Message Type = 48 The VC Activity request and success response messages have the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Type | Result | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of Records | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ VC Activity Records ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Number of Records Field specifies the number of VC Activity records to follow. The maximum number of VC Activity records permitted in a single VC Activity message is 120. Reserved Field is not used. It is set to zero by the sender and ignored by the receiver. Each VC Activity Record has the following format: +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags | Input VPI | Input VCI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + VC Traffic Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Input Port Identifies the port number of the input port on which the VC of interest arrives in order to identify the VC (regardless of whether the traffic count for the VC is maintained on the input port or the output port).Newman, et. al. Informational [Page 21] RFC 1987 GSMP Protocol Specification August 1996 Input VPI Input VCI Fields identify the specific virtual channel for which statistics are being requested. Flags In the request message this field is unused, it should be set to zero by the sender and ignored by the receiver. In the success response message bit 0 (msb) of the Flags field is used to indicate an invalid VC Activity record. This bit must be zero if any of the fields in this VC Activity record are invalid, if the input port specified by the Input Port field does not exist, or if the specified connection does not exist. If this bit is zero in a success response message bits 1 and 2 of the Flags field and the VC Traffic Count field are undefined. If bit 0 of the flags field is set, the VC Activity record is valid, and bits 1 and 2 of the Flags field in the VC Activity record are used as follows: Bit 1 of the Flags field: if set, indicates that the value in bit 2 of the Flags field is valid; if zero, indicates that the value in the VC Traffic Count field is valid. If bit 1 of the Flags field is set, bit 2 of the Flags field, if set, indicates that there has been some activity on this virtual channel since the last VC Activity message for this virtual channel. If bit 1 of the Flags field is set, bit 2 of the Flags field, if zero, indicates that there has been no activity on this virtual channel since the last VC Activity message for this virtual channel. Bit 3 of the Flags field is not used, it should be set to zero by the sender and ignored by the receiver. VC Traffic Count Field is unused in the request message, it should be set to zero by the sender and ignored by the receiver. In the success response message, if the switch supports per-VC traffic counting, the VC Traffic Count field must be set to the value of a free running, VC specific, 64 bit traffic counter counting traffic flowing across the specified virtual channel. The value of the traffic counter is not modified by reading it. If per-VC traffic counting is supported, the switch must report the VC Activity resultNewman, et. al. Informational [Page 22] RFC 1987 GSMP Protocol Specification August 1996 using the traffic count rather than using bit 2 of the Flags field. The format of the failure response is the same as the request message with the Number of Records field set to zero and no VC Activity records returned in the message. If the switch is incapable of detecting per-VC activity, a failure response must be returned indicating, "The specified request is not implemented on this switch."5.2 Port and VC Statistics Messages The Port and VC Statistics messages are used to query the various port and VC specific traffic and error counters. The Port and VC Statistics request messages have the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Type | Result | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | zero | VPI | VCI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Port Identifies the port number of the port for which statistics are being requested. VPI VCI Fields identify the specific virtual channel for which statistics are being requested. For requests that do not require a virtual channel to be specified these fields should be set to zero in the request and ignored by the receiver. The success response messages for the port and VC statistics group have the following format:Newman, et. al. Informational [Page 23] RFC 1987 GSMP Protocol Specification August 1996 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version | Message Type | Result | Code | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Transaction Identifier | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | zero | VPI | VCI | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input Cell Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input Frame Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input Cell Discard Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input Frame Discard Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input HEC Error Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Input Invalid VPI/VCI Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Output Cell Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Output Frame Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Output Cell Discard Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |Newman, et. al. Informational [Page 24] RFC 1987 GSMP Protocol Specification August 1996 + Output Frame Discard Count + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Port VPI/VCI Fields are the same as those of the request message. Input Cell Count Output Cell Count Each gives the value of a free running 64 bit counter counting cells arriving at the input or departing from the output respectively. In response to a Port Statistics message the count will be on a per port basis and in response to a VC Statistics message the count will be on a per VC basis. Input Frame Count Output Frame Count Each gives the value of a free running 64 bit counter counting frames (packets) arriving at the input or departing from the output respectively. In response to a Port Statistics message the count will be on a per port basis and in response to a VC Statistics message the count will be on a per VC basis. Input Cell Discard Count Output Cell Discard Count Each gives the value of a free running 64 bit counter counting cells discarded due to queue overflow on an input port or on an output port respectively. In response to a Port Statistics message the count will be on a per port basis and in response to a VC Statistics message the count will be on a per VC basis. Input Frame Discard Count Output Frame Discard Count Each gives the value of a free running 64 bit counter counting frames discarded due to queue overflow on an input port or on an output port respectively. In response to a Port Statistics message the count will be on a per port basis and in response to a VC Statistics message the count will be on a per VC basis. HEC Error Count Gives the value of a free running 64 bit counter counting cells discarded due to header checksum errors on arrival at an input po⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?