Converting MIBs Using mib2opennms

最新推荐文章于 2021-01-19 16:33:24 发布
最新推荐文章于 2021-01-19 16:33:24 发布
阅读量2.5k 收藏
点赞数
分类专栏： OpenNMS技术应用 文章标签： notifications events variables file opensource import

-----------------------------------------------------------------------------

opennms中两个相当有份量的工具就是mib2opennms和mibparser,mibparser专门用来分析mib文件以形成相应的SNMP采集配置文件XML形式,而mib2opennms负责trap相关Mib的提取以实现opennms中的event和notify,供opennms中的trapd进程来使用.

  From OpenNMS

Contents

[hide]
<script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>

mib2opennms How-To

This little document provides an explanation of how to import SNMP MIBs into OpenNMS, using the opensource tool 'mib2opennms'.

本文描述了使用开源的mibopennms工具将SNMP MIBs文件导入到OpenNMS的方法.

Why import the OIDs using this tool?

OpenNMS has the ability to receive SNMP traps; In order to do that, OpenNMS must know how to treat each event (thus requires a description for each OID that it receives). Normally if you don't do that you will receive anoying messages like the following on your event database:

OpenNMS有接收SNMP traps(陷阱)的能力.因此,OpenNMS必须知道如何去处理每一个发生的时间,也就是说OpenNMS需要每一个接受到的OID都有相应的描述信息.通常来说,在你没有设置描述信息的情况下,你将收到如下的消息,并被存储于你的信息数据库中.

Received unformatted enterprise event (enterprise:.1.3.6.1.4.1.2021.250.10 generic:0 specific:0). 0 args:

Also importing the OIDs by hand is error prone and tedious, so the use of this tool is a must when adding new OIDs.

同样的,当你手工导入错误或冗余时,也回产生上面的信息.不难发现mib2opennms是添加新OIDs的必要工具.

Download the software

There are several alternatives (RPM, source code). Look for it in the contrib directory of OpenNMS.

可以选择RPM和源代码包的形式.从OopenNMS安装目录下的contrib中,可以看到mib2opennms文件夹.

How to use

It is better to get a detailed list of OIDs in the form of XML files; so that you can choose what to cut/paste into your "eventconf.xml," instead of a huge (and useless) list of OIDs.

Here is a Bash script that can do the nasty work for you (take care to define the appropiate variables first): 

# <----- CUT HERE ----->

#!/bin/bash
#
# This program generates a list of XML files to be used with OpenNMS and the 
# "event" section.
# Author: Jose Vicente Nunez Zuleta (josevnz@newbreak.com)
# Requires: mib2openms (http://www.tompa.nu/mib2opennms/)
#

MIBPATH="/usr/share/snmp/mibs:/usr/share/mibs:/home/josevnz/mibs"
MIBDEF=$1
destdir=$2

if [ -z $MIBDEF ] ; then
cat <<EOF;
[ERROR]:
You must supply values for the mib directory. Examples:

/home/josevnz/mibs

/usr/share/snmp/mibs

Then the script will locate all the '*.txt' files present.


EOF
exit 1
fi


mibc="/usr/bin/mib2opennms"
mkdir="/bin/mkdir"
perl="/usr/bin/perl" # sed SUCKS!!! ;)

# Use the user destination dir if present
if [ -z $destdir ] ; then
  destdir="/tmp";
fi

if [ ! -e $destdir ] ; then
  $mkdir -p $destdir
  if [ $? -ne 0 ] ; then
    echo "Error creating destination dir"
  fi
fi

# Get the list of all the MIBs on this system
LIST=`find $MIBDEF -type f -name '*.txt' | /usr/bin/xargs`
if [ $? -ne 0 ] ; then
  echo "Error locating the MIBS"
fi

for file in $LIST; do
  # Get the mib name from the file
  mib=`echo $file |$perl -e' while(<STDIN>) { 
-----------------------------------------------------------------------------


opennms中两个相当有份量的工具就是mib2opennms和mibparser,mibparser专门用来分析mib文件以形成相应的SNMP采集配置文件XML形式,而mib2opennms负责trap相关Mib的提取以实现opennms中的event和notify,供opennms中的trapd进程来使用.


  From OpenNMS 


  
  


   
   


   
   

   
   

       
       
 
        
Contents
 
        [hide] 
       

       
       

<script type="text/javascript">___FCKsi___0</script>

   
   

   
   
mib2opennms How-To 


   
   
This little document provides an explanation of how to import SNMP MIBs into OpenNMS, using the opensource tool 'mib2opennms'. 


   
   
本文描述了使用开源的mibopennms工具将SNMP MIBs文件导入到OpenNMS的方法.


   
   

   
   
Why import the OIDs using this tool? 


   
   
OpenNMS has the ability to receive SNMP traps; In order to do that, OpenNMS must know how to treat each event (thus requires a description for each OID that it receives). Normally if you don't do that you will receive anoying messages like the following on your event database: 


   
   
OpenNMS有接收SNMP traps(陷阱)的能力.因此,OpenNMS必须知道如何去处理每一个发生的时间,也就是说OpenNMS需要每一个接受到的OID都有相应的描述信息.通常来说,在你没有设置描述信息的情况下,你将收到如下的消息,并被存储于你的信息数据库中.


   
   
Received unformatted enterprise event (enterprise:.1.3.6.1.4.1.2021.250.10 generic:0 specific:0). 0 args:


   
   
Also importing the OIDs by hand is error prone and tedious, so the use of this tool is a must when adding new OIDs. 


   
   
同样的,当你手工导入错误或冗余时,也回产生上面的信息.不难发现mib2opennms是添加新OIDs的必要工具.


   
   

   
   
Download the software 


   
   
There are several alternatives (RPM, source code). Look for it in the contrib directory of OpenNMS. 


   
   
可以选择RPM和源代码包的形式.从OopenNMS安装目录下的contrib中,可以看到mib2opennms文件夹.


   
   

   
   
How to use 


   
   
It is better to get a detailed list of OIDs in the form of XML files; so that you can choose what to cut/paste into your "eventconf.xml," instead of a huge (and useless) list of OIDs. 


   
   
Here is a Bash script that can do the nasty work for you (take care to define the appropiate variables first): 


   
   
___FCKpd___1


   
   
Then you can call it like this: 


   
   
 ./generate_mibs.bsh /home/josevnz/mibs 1> output.txt 2> errors.txt



   
   

   
   
Resources 


   
   
List of extracted (and ready to use) MIBs: 


   
   

   
   

   
   
More on mib2opennms 


   
   
This came up on the discussion list, so I thought it should go here. 


   
   
Q: I am trying to get the Juniper MIBs into OpenNMS, but I can't get mib2opennms to work. I only get segmentation faults: 


   
   
# mib2opennms mib-jnx-ipv6.txt
mib2opennms version 0.2.2
Segmentation fault



   
   
A: This usually means that there is a problem with the ASN.1 notation in your mibs. 


   
   
I don't get a seg fault on that mib, but since: 


   
   
grep NOTIF mib-jnx-ipv6.txt


   
   
and 


   
   
grep TRAP mib-jnx-ipv6.txt


   
   
return nothing, there are no events defined in that MIB. 


   
   
A quick search shows the following files support NOTIFICATION-TYPE objects: 


   
   
Stormbringer:~/Desktop/JuniperMibs tarus$ grep -l NOTIF *
mib-jnx-bgpmib2.txt
mib-jnx-cfgmgmt.txt
mib-jnx-chassis.txt
mib-jnx-coll.txt
mib-jnx-ldp.txt
mib-jnx-mpls.txt
mib-jnx-ping.txt
mib-jnx-pmon.txt
mib-jnx-rmon.txt
mib-jnx-sonet.txt
mib-jnx-sonetaps.txt
mib-jnx-vpn.txt



   
   
Let's check out the first one. if I run: 


   
   
/usr/local/bin/mib2opennms mib-jnx-bgpmib2.txt


   
   
I get: 


   
   
        <mask>
                <maskelement>
                        <mename>id</mename>
                        <mevalue>.0.1.1</mevalue>
                </maskelement>
                <maskelement>
                        <mename>generic</mename>
                        <mevalue>0</mevalue>
                </maskelement>
                <maskelement>
                        <mename>specific</mename>
                        <mevalue>1</mevalue>
                </maskelement>
        </mask>



   
   
Note that the id looks wrong. It should be something like .1.3.6.1.4.1.x 


   
   
This usually means that there is a broken import somewhere, so we should include the MIB files in the current directory: 


   
   
/usr/local/bin/mib2opennms -m. mib-jnx-bgpmib2.txt
        <mask>
                <maskelement>
                        <mename>id</mename>
                        <mevalue>.0.1.1</mevalue>
                </maskelement>
                <maskelement>
                        <mename>generic</mename>
                        <mevalue>0</mevalue>
                </maskelement>
                <maskelement>
                        <mename>specific</mename>
                        <mevalue>1</mevalue>
                </maskelement>
        </mask>



   
   
Hrm, not much better, and adding the path to the default MIBs doesn't help either: 


   
   
/usr/local/bin/mib2opennms -m/usr/share/snmp/mibs:. mib-jnx-bgpmib2.txt


   
   
So, it's time to look into the mib file. The first NOTIFICATION-TYPE object is: 


   
   
jnxBgpM2Established NOTIFICATION-TYPE
    ::= { jnxBgpM2BaseNotifications 1 }



   
   
So let's work backwards. 


   
   
jnxBgpM2BaseNotifications
    OBJECT IDENTIFIER ::= { jnxBgpM2BaseScalars 0 }

jnxBgpM2BaseScalars
    OBJECT IDENTIFIER ::= { jnxBgpM2 1 }

jnxBgpM2 MODULE-IDENTITY
     ::= { jnxBgpM2Experiment 1 }



   
   
Now, jnxBgpM2Experiment comes from: 


   
   
jnxBgpM2Experiment
    FROM JUNIPER-EXPERIMENT-MIB



   
   
Therein lies the problem. As mentioned in the README: 


   
   
If mib2opennms complains about a missing MIB, be sure that there is a file
in your "-m" MIB path that has the *exact* name as the MIB it is complaining
about.



   
   
For example, if it complains "Can't find RFC-1213" and you have a file in your path called "RFC1213", you must rename it or copy it to "RFC-1213". 


   
   
The extensions .txt, .my and I believe .mib are acceptable, so in the above example, RFC-1213.txt should work." 


   
   
Well, there is no file called JUNIPER-EXPERIMENT-MIB. So: 


   
   
cp mib-jnx-exp.txt JUNIPER-EXPERIMENT-MIB


   
   
and rerun: 


   
   
/usr/local/bin/mib2opennms -m/usr/share/snmp/mibs:.  mib-jnx-bgpmib2.txt
        <mask>
                <maskelement>
                        <mename>id</mename>
                        <mevalue>.0.5.1.1.1</mevalue>
                </maskelement>
                <maskelement>
                        <mename>generic</mename>
                        <mevalue>0</mevalue>
                </maskelement>
                <maskelement>
                        <mename>specific</mename>
                        <mevalue>1</mevalue>
                </maskelement>
        </mask>



   
   
Better. More research shows that the JUNIPER-SMI MIB is referenced by JUNIPER-EXPERIMENT-MIB: 


   
   
cp mib-jnx-smi.txt JUNIPER-SMI
/usr/local/bin/mib2opennms -m/usr/share/snmp/mibs:.  mib-jnx-bgpmib2.txt
        <mask>
                <maskelement>
                        <mename>id</mename>
                        <mevalue>.1.3.6.1.4.1.2636.5.1.1.1</mevalue>
                </maskelement>
                <maskelement>
                        <mename>generic</mename>
                        <mevalue>0</mevalue>
                </maskelement>
                <maskelement>
                        <mename>specific</mename>
                        <mevalue>1</mevalue>
                </maskelement>
        </mask>



   
   
Success! The only problem is that "generic" is set to zero, so add the -6 option: 


   
   
/usr/local/bin/mib2opennms -6 -m/usr/share/snmp/mibs:.  mib-jnx-bgpmib2.txt
        <mask>
                <maskelement>
                        <mename>id</mename>
                        <mevalue>.1.3.6.1.4.1.2636.5.1.1.1</mevalue>
                </maskelement>
                <maskelement>
                        <mename>generic</mename>
                        <mevalue>6</mevalue>
                </maskelement>
                <maskelement>
                        <mename>specific</mename>
                        <mevalue>1</mevalue>
                </maskelement>
        </mask>



   
   
The final steps are to take the new file and make it contain "events" by adding an <events> tag at the very top and an </events> tag at the bottom. The file can now be added to eventconf.xml via an include. Restart OpenNMS and the events are ready to go. 


   
   
This is just an example of how mib2opennms should work. I don't understand the seg faults - could be an issue with the build. We don't support stuff in contrib, so anyone with come C++ experience might want to check it out for us. WORKSFORME on my Mac (built using libsmi from fink). 


   
   



   
   

   
   
Varbinds --- Nasty ..... until recently ...


   
   
Recently the behavior of OpenNMS, at least regarding the current SVN trunk, has been changed in conformance with RFC2089. This change takes care of all the problems mentioned below. 


   
   



   
   
--- obsolete --- mib2opennms also converts the varbinds from the MIB as puts them into the event message. Because of the fact that SNMPv1 traps are different in data layout from SNMPv2 notifications might be things to correct before using the converted mib. 


   
   
SNMPv2 notifications contain the originator OID of the trap and also a timestap as first two variables in the packet being send. Because of this the varbinds of converted MIBs with NOTIFICATIONs are always shifted by two. 


   
   
This means that parm[#1] does not contain the fist variable that the agent sent, but more the OID of the NOTIFICATION originator. 


   
   
The only thing you need to do (until mib2opennms might be changed) is to always add "2" to any parm# that is in the xml file created. 


   
   
 


  
  

= m#.*/(.*)/.txt#; print $1 }'`
echo "Processing: $mib"
# Generate a OpenNMS MIB xml file for each located mib
COMMAND="$mibc -f "$destdir/$mib.xml" -m $MIBPATH $file"
echo $COMMAND
$COMMAND
if [ $? -ne 0 ]; then
echo "MIB conv failed"
fi
done
# <----- CUT HERE ----->

Then you can call it like this: 

___FCKpd___2

Resources

List of extracted (and ready to use) MIBs:

More on mib2opennms

This came up on the discussion list, so I thought it should go here.

Q: I am trying to get the Juniper MIBs into OpenNMS, but I can't get mib2opennms to work. I only get segmentation faults: 

___FCKpd___3

A: This usually means that there is a problem with the ASN.1 notation in your mibs.

I don't get a seg fault on that mib, but since: 

___FCKpd___4

and 

___FCKpd___5

return nothing, there are no events defined in that MIB.

A quick search shows the following files support NOTIFICATION-TYPE objects: 

___FCKpd___6

Let's check out the first one. if I run: 

___FCKpd___7

I get: 

___FCKpd___8

Note that the id looks wrong. It should be something like .1.3.6.1.4.1.x

This usually means that there is a broken import somewhere, so we should include the MIB files in the current directory: 

___FCKpd___9

Hrm, not much better, and adding the path to the default MIBs doesn't help either: 

___FCKpd___10

So, it's time to look into the mib file. The first NOTIFICATION-TYPE object is: 

___FCKpd___11

So let's work backwards. 

___FCKpd___12

Now, jnxBgpM2Experiment comes from: 

___FCKpd___13

Therein lies the problem. As mentioned in the README: 

___FCKpd___14

For example, if it complains "Can't find RFC-1213" and you have a file in your path called "RFC1213", you must rename it or copy it to "RFC-1213".

The extensions .txt, .my and I believe .mib are acceptable, so in the above example, RFC-1213.txt should work."

Well, there is no file called JUNIPER-EXPERIMENT-MIB. So: 

___FCKpd___15

and rerun: 

___FCKpd___16

Better. More research shows that the JUNIPER-SMI MIB is referenced by JUNIPER-EXPERIMENT-MIB: 

___FCKpd___17

Success! The only problem is that "generic" is set to zero, so add the -6 option: 

___FCKpd___18

The final steps are to take the new file and make it contain "events" by adding an <events> tag at the very top and an </events> tag at the bottom. The file can now be added to eventconf.xml via an include. Restart OpenNMS and the events are ready to go.

This is just an example of how mib2opennms should work. I don't understand the seg faults - could be an issue with the build. We don't support stuff in contrib, so anyone with come C++ experience might want to check it out for us. WORKSFORME on my Mac (built using libsmi from fink).


Varbinds --- Nasty ..... until recently ...

Recently the behavior of OpenNMS, at least regarding the current SVN trunk, has been changed in conformance with RFC2089. This change takes care of all the problems mentioned below.


--- obsolete --- mib2opennms also converts the varbinds from the MIB as puts them into the event message. Because of the fact that SNMPv1 traps are different in data layout from SNMPv2 notifications might be things to correct before using the converted mib.

SNMPv2 notifications contain the originator OID of the trap and also a timestap as first two variables in the packet being send. Because of this the varbinds of converted MIBs with NOTIFICATIONs are always shifted by two.

This means that parm[#1] does not contain the fist variable that the agent sent, but more the OID of the NOTIFICATION originator.

The only thing you need to do (until mib2opennms might be changed) is to always add "2" to any parm# that is in the xml file created.

 

cnhome
关注
专栏目录
tpm2-tools源码分析之tpm2_load.c（4）
phmatthaus的专栏
03-27 412
tpm2-tools源码分析之tpm2_load.c（4）
OpenNMS扩展–基于JoeSNMP/MIB数据访问实现
两粒种子，一片森林
04-24 3298
JoeSNMP是OpenNMS采用的SNMP API，已独立成为一个Open Source Framework，基于JoeSNMP可以对MIB网络数据进行相应的操作。JoeSNMP封装了多个对SNMP Get,Set等操作的处理。
opennms 监控mysql_使用opennms监控设备性能
weixin_31972679的博客
01-19 507
使用opennms网管软件监控设备cpu、内存性能一、windows系统的cpu、内存性能数据采集在Windows系统里面安装informant-std采集代理，在http://www.snmp-informant.com/downloads.htm下载，安装后重启snmp服务，然后再opennms里面即可看到cpu、内存等数据。二、交换机、防火墙等的cpu、内存性能数据采集以h3c交换机为例：1...
OpenNMS安装与配置笔记
te_amo蘑菇
07-22 1194
OpenNMS安装与配置笔记 [color=red]一.从GIT获取源码，建立eclipse工程[/color] 1.mkdir ~/rcs; cd ~/rcs 2. git clone git://opennms.git.sourceforge.net/gitroot/opennms/opennmss 3. git branch -a (查看所有的分支) 4. git c...
OpenNMS扩展 – SNMP报表配置
fang8187的博客
04-24 322
OpenNMS扩展 – SNMP报表配置 SNMP报表的显示主要由两个文件，datacollection-config.xml与snmp-graph.properties。 定制SNMP图形报表主要步骤如下： 1. 通过SNMP获取数据(datacollection-config.xml) 在datacollection-config.xml文件中定义OID捕获数据，在此例中将捕获系统...
SNMP协议以及著名的MIB详解
weixin_34346099的博客
04-20 2942
为什么80%的码农都做不了架构师？>>> ...
converting_rgb2gray.zip_scale
07-15
code for converting gray scale image into color image by using template
Converting_to_mp3_files_using_ffmpeg.pdf
01-08
2. **指定音频编解码器进行转换** ```bash ffmpeg -i source.wav -acodec libmp3lame output.mp3 ``` 此命令明确指定了使用libmp3lame编解码器来进行MP3编码。 3. **指定恒定比特率（CBR）进行转换** ```...
sid.zip_Converting_SID_between_binary
09-21
2. 二进制到字符串：相反的过程，需要读取二进制SID的头部信息，获取版本号、权威主体标识数量，然后读取每个子权威值，最后构建出相应的字符串表示。 三、编程实现 在提供的压缩包文件中，SidFunc.cpp和SidFunc.h...
net-snmp中载入第三方mib库
12-17 809
一般我们下载回来的mib文件可能后缀名为.mib，为了清晰起见，可能需要改名。一般改成 MIB_NAME.txt 这样的形式。 例如/usr/share/snmp/mibs/IP-MIB.txt 中包含如下一行 IP-MIB DEFINITIONS ::= BEGIN 这个MIB_NAME具体的定义是在mib文件中第一个包含 DEFINITIONS 的行，在DEFINITIONS之前的...
[OpenNMS] 当妳有特殊的资料收集需求时，几种客制化的方法
帝国反抗君 - PowerOp
07-14 663
之前这篇 [免费服务]001:L君试用OSE (CentOS 5.4 + OpenNMS 1.6.10) 文章，最后面提到的客制化需求，简单的说，就是要把一些用指令可以查询到的数据，画成图表。很多网管系统的应对方法，都是在自己这端 fork 一个 telnet 或 ssh ，远端登入到被监控的机器，执行查询的指令，然后从回传的结果抓出需要的资讯(parsing)但是 OpenNMS 不推荐这样的方式（！）我之前就有注意到 opennms 有一些设计理念，很重视 scale/scalability；他们应该是
使用java 的两个mibble-mibs-2.9.3.jar 和 mibble-2.9.3.jar解析MIB文件
ljh_learn_from_base的博客
05-30 4139
参考：https://blog.csdn.net/qq_37694421/article/details/83894870 今天有幸使用java帮同学解决解析MIB(Management Infomation Base)文件 在线下载链接，两个jar 都要导入 mibble-2.9.3.jar 和mibble-mibs-2.9.3.jar 如果是maven 项目可以用 maven 仓库 ...
LeetCode 最小覆盖子串（双指针窗口滑动）
热门推荐
hestyle的博客
02-15 5万+
给定一个字符串 S 和一个字符串 T，请在 S 中找出包含 T 所有字母的最小子串。 示例： 输入: S = &quot;ADOBECODEBANC&quot;, T = &quot;ABC&quot; 输出: &quot;BANC&quot; 说明： 如果 S 中不存这样的子串，则返回空字符串 &quot;&quot;。 如果 S 中存在这样的子串，我们保证它是唯一的答案。 思路分析：题目的要求是在s串中找出一段字符串各个字符出现的次数刚
opennms监听windows SNMP
liuwei063608的专栏
09-09 2230
opennms监听windows 1 步骤 1.1 为设备开启SNMP协议 控制面板—>程序和功能—>打开或关闭windows功能—>选中SNMP协议。 图1-1 1.2 添加SNMP身份验证 服务—>SNMP Service—>安全—>添加社区名称和接受SNMP的主机信息。 图1-2 1.3 开启防火墙 控制面板—>windows防火墙—>打开或关闭windows防火墙
添加自定义MIB的三种方法
梦
01-22 1万+
我所知道的添加自定义MIB的方法有三种 1.静态加载，将生成的.c和.h文件加入到相应的位置，重新编译snmp库，优点是不需要修改配置文件，缺点是每次添加都得重新编译； 2.动态加载，将生成的.c和.h文件再编译成.so库，修改snmpd.conf配置文件。优点是每次添加不需要重新编译，缺点是必须支持dlmod命令； 3.子代理扩展，将生成的.c和.h文件编译成可执行程序，运行该程序
snmp mib 数据类型
twinkle_star1314的博客
04-20 8650
SNMP Overview SNMP Overview What Is an Agent? Who Is a Manager? Manager and Agent Relationship What Is a MIB? What are MIB Groups? MIB Datatypes Available MIB
考虑P2G和碳捕集设备的热电联供综合能源系统优化调度模型（Matlab代码实现）.rar
最新发布
10-09
1.版本：matlab2014/2019a/2024a 2.附赠案例数据可直接运行matlab程序。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
可提高超声成像系统在时间延迟多普勒参数方面的分辨率 matlab代码.rar
10-09
1.版本：matlab2014/2019a/2024a 2.附赠案例数据可直接运行matlab程序。 3.代码特点：参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象：计算机，电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
Struts2 Convention Plugin实战指南
3. Converting a Codebehind-based application to Convention 将原有的基于Codebehind的Struts2应用转换为使用Convention模式，主要工作是按照约定调整包结构和类名，删除或简化XML配置。 4. Helloworld 创建一...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值