First step towards
configuring the Management IP Interface is to configure a VirtualPortGroup
interface. You can also configure secondary IP addresses on the
VirutalPortGroup interface, similar to a gigabit Ethernet interface IP address
configuration.
To configure the
VirtualPortGroup interface, complete the following procedure:
Verifying the
VirtualPortGroup Interface Configuration
To verify the
VirtualPortGroup interface configuration, use the
show run interface
VirtualPortGroup command as shown in the example below:
show run interface VirtualPortGroup 0
Building configuration...
Current configuration : 145 bytes
!
interface VirtualPortGroup0
ip address 1.22.3.1 255.255.255.0 secondary
ip address 1.22.2.1 255.255.255.0
no mop enabled
no mop sysid
end
The
VirtualPortGroup interface is in a down state. The interface comes up after the
cable video management interface is configured.
Verifying the
VirtualPortGroup Interface State
To verify the
VirtualPortGroup interface state, use the
show interfaces
VirtualPortGroup command as shown in the example below:
show interfaces VirtualPortGroup 0
VirtualPortGroup0 is up, line protocol is up
Hardware is Virtual Port Group, address is badb.ad09.7077 (bia badb.ad09.7077)
Internet address is 1.22.2.1/24
MTU 1500 bytes, BW 2500000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:24:14, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out