Context configuration example, Network requirements – H3C Technologies H3C SecPath F5020 User Manual
Page 79

70
Task Command
Display contexts.
display context [ name context-name ]
Display interfaces assigned to
contexts.
display context [ name context-name ] interface
Display CPU, disk space, and
memory usage of contexts.
•
Centralized IRF devices/distributed devices in standalone mode:
display context [ name context-name ] resource [ cpu | disk |
memory ] [ slot slot-number cpu cpu-number ]
•
Distributed devices in IRF mode:
display context [ name context-name ] resource [ cpu | disk |
memory ] [ chassis chassis-number slot slot-number cpu cpu-number ]
Display VLANs for contexts.
display context [ name context-name ] vlan
Clear information for an absent
security engine in a security
engine group.
reset blade-controller-team team-id member slot slot-number cpu
cpu-number
Context configuration example
Network requirements
As shown in
, configure three contexts on the firewall and assign them to three LANs. To meet
secure access requirements of the three LANs, configure the contexts as follows:
•
Assign larger amounts of disk space to context cnt1 and configure a large CPU weight for it.
•
Configure context cnt2 to use the default disk space.
•
Configure a small CPU weight for context cnt3.
Figure 23 Network diagram