OPNET 文档
中文
Documentation Home
License and Installation Support
Modeling Concepts
Models
Process Model/Queuing
Process Model/General
Pipeline Stages/Bus Link
Pipeline Stages/Point-to-Point Links
Packet Conversion
Model Support
Applications
Cyber Effects
Cyber Effects
Model Features
Cyber Effects Objects
Cyber Effects Profiles
Cyber Effects Control Flow
Workflow for Modeling Cyber Effects
Defining Effect Scripts
Defining Attack and Remedy Profiles
Configuring Cyber Actions on Nodes
Model Attributes
Cyber Effects Configuration Attributes
Node Attributes
Model Statistics
Model Interfaces
Creating Custom Cyber Effects
Choose a Model
Define the Custom Effect
Update the Cyber Effects Configuration Node
Register the Custom Effect
Adding Cyber Modeling to a Node
Troubleshooting
Cyber Effects API
cyber_effects_cmd_code_is_cyber_effect()
cyber_effects_cmd_process()
cyber_effects_cmd_register()
cyber_effects_mgr_handle_get()
CyberT_Effect_Proc_Ptr
Mainframe
RPG
Server
ATM
Ethernet
FDDI
Frame Relay
ISDN/xDSL
LANE
LAPB
Link Aggregation
SRP
Spanning Tree Bridge
Token Ring
VLAN
X.25
APS
H.323
HAIPE
IP
IP Multicast
IP QoS
IPv6
RSVP
BGP
EIGRP
IGRP
IS-IS
MPLS
OSPF
PNNI
RIP
Software-Defined Networking
TCP
TPAL
LTE
MANET
SMART MAC
Advanced Wireless Package
TDMA
UMTS
WiMAX (802.16e)
Wireless LAN
ZigBee
General Models Reference
Model Library
Modules
Modeler Tutorials
Working with Discrete Event Simulation Models
Notices
Programmers Reference
About ZNetLink
Home
/
Models
/
Troubleshooting
Troubleshooting
You can trace cyber effects activity in ODB by using the command:
ltrace cyber
← Previous
Adding Cyber Modeling to a Node
Next →
Cyber Effects API