IP Control Module Diagnostics. Alcatel-Lucent iP2000, IP2100
Pubblicità
Pubblicità
IP Control Module Diagnostics
A
Multicast-capable high-bandwidth LIM diagnostics . . . . . . . . . . . . . . . . . . . . . A-27
SNMP MIB for GMAC and VLAN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-29
This appendix describes the gmac , igmp , and pim system-level commands. Information provided by the gmac command is also accessible to an external management utility through the ip2kstats.mib
management information base (MIB). Information displayed by the pim command can also be accessed through the PIMv2 MIB
(currently defined in draft-ietf-pim-mib-v2-01.
txt) under experimental 61 .
In addition, this appendix describes the following debug-level commands, which are not documented in the Stinger Reference and are not supported.
■ diag igmpsp
■
■ diag igmp brtbls
■
■
■
■ ifmgr diag brtbl sar info np
Caution Debug-level commands can be used to display low-level details about IP
DSLAM operations. However, they are introduced into the system for development purposes, and are not part of the supported software environment. Use debug-level commands with caution!
Stinger® IP Control Module Configuration Guide A-1
IP Control Module Diagnostics
Enabling the debug environment
Enabling the debug environment
To access the debug environment, log in using the default super (super-user) profile.
For example: admin> auth super
Password:
The default password for this account is Ascend . If the password has not been changed, you should change it now to prevent unauthorized super-user access to the system.
The debug environment contains many hidden commands and parameters that are not intended for general use. The debug environment is not supported, and the documentation provided here is not comprehensive.
Caution Under most circumstances, debug commands are not required for monitoring Stinger IP DSLAM operations, and under some circumstances, these commands might produce undesirable results. Use the information with caution.
Contact Alcatel-Lucent OnLine Customer Support at http://www.lucent.com/support with questions or concerns.
Gigabit Ethernet diagnostics
The gmac command provides diagnostic output about the Gigabit Ethernet media access controller (GMAC) driver.
gmac
Description Provide diagnostics on the Gigabit Ethernet (GigE) driver.
Permission level system
Usage gmac [options]
Command element
-v
-i [-u/d]
-n
-s
Description
Show gmac version.
With no additional option, initialize/reset the
GigE port.
-i -u Force GigE link up.
-i -d Force GigE link down.
Set up network processor to communicate with
GMAC.
Set up a SAR channel for communicating with
GMAC.
A-2 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics gmac
Command element
-l [-i/e/d/p]
-p
-r
-w
-d [-c/a/e]
-t
-?
Description
Loopback.
-l -i Set port for internal loopback.
-l -e Set port for external loopback.
-l -d Set port for no loopback
-l -p Run loopback test for Ethernet poweron self test (POST).
Ping test.
Read a PHY register.
Write to a PHY register.
With no additional option, display all statistics.
-d -c Clear GMAC statistics.
-d -a Display ATM statistics.
-d -e Display Ethernet statistics.
Set debug level (0 through 3).
Display a summary of commands.
Example The gmac -n command sets up the network processor for communication with the GMAC port: super> gmac -n
NP setup for gmac done.
Example The gmac -s command sets up a SAR channel for communicating with the
GMAC port: super> gmac -s
GMAC: SAR conn. open with vpi = 0, vci = 200
Example The gmac -v command displays the GMAC version: super> gmac -v
GMAC version : 0x0b
Example The gmac -i command resets the Gigabit Ethernet port: super> gmac -i gigE port reset.
Example The gmac -d command displays the total transmit and receive statistics for the GigE interface of the IP control module. For details about the gmac -d output
fields, see the descriptions of MIB objects in “Total transmit statistics” on page A-30
and “Total receive statistics” on page A-32. For example, the following command
displays the current GMAC statistics: super> gmac -d
Gigabit Ethernet port statistics : txOctetsLow = 1040 txOctetsHigh = 0 txGoodPackets = 4
Stinger® IP Control Module Configuration Guide A-3
IP Control Module Diagnostics
IGMP diagnostics txPkt64 = 0 txPkt65127 = 0 txPkt128255 = 0 txPkt256511 = 4 txPkt5121023 = 0 txPkt1024Max = 0 txPktDefer = 0 txPktUndSz = 0 txUnderFlow = 0 txPfcf = 0 txPfcc = 0 txRfcf = 0 txRfcc = 0 txOverFlow = 0 txAlmostFull = 0 rxOctetsLow = 1646718 rxOctetsHigh = 0 rxGoodPackets = 2059 rxPkt64 = 766 rxPkt65127 = 0 rx128255 = 0 rx256511 = 160 rx5121023 = 0 rx1024Max = 1133 rxMacType = 0 rxCrcErrors = 0 rxUnderSize = 0 rxOverSize = 0 rxAlmostFull = 0 rxOverRun = 0 rxMulticastPackets = 1896 rxBroadcastPackets = 46 rxJabber = 0 rxPfc = 0 rxRfc = 0
IGMP diagnostics
The igmp command provides information about IGMP multicast operations. The profile argument has been added to support MCAST-SERVICE profiles.
The diag igmpsp and diag igmp commands are available only in the debug
environment. See “Enabling the debug environment” on page A-2 for related
information.
igmp
Description Displays or clears multicast information about IGMP groups and clients.
Permission level system
A-4 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics igmp
The system-level igmp command supports new set of arguments for displaying information obtained by IGMP snooping. The igmp command is supported both on the shelf and the individual LIM slots. Following is the new usage statement, which shows both the existing and new arguments: admin> igmp
Igmp Commands Usage:
igmp <mbone | groups | clients | slots | vc >
<profile [mcast-profile] | delete [grp_addr][if_num]>
Igmp Snooping Commands Usage:
igmp <smbone | sgroups [bridgeNum] | sclients [bridgeNum]>
<sslots | sdelete [bridgeNum][grp_addr][if_num]>
Command element mbone groups clients slots vc profile [mcastprofile]
Description
Display multicast backbones. For example: admin> igmp mbone
Mbone is currently:
Slot 1:8 ifNum = 1
Display currently registered multicast group addresses and interfaces.
Display multicast clients.
Display multicast enable slots.
Check the multicast VCs that are configured and active at any point of time. For example: admin> igmp vc
Current VCs:
Profile Name IfNum Active
-----------------------------------------------oc3-multi 17 yes oc3-multi2 25 yes oc3-multi1 24 yes
Display multicast profiles. If you specify an MCAST-
SERVICE profile name, the command also displays the
CONNECTION profiles associated with that profile. This option is available only on the system control module.
For example, the following command displays information about an MCAST-SERVICE profile named test : admin> igmp profile test
Mcast Service : test
Filter Type : MCAST_FILTER_INCLUSIVE
Filter List :
239.10.10.10 - 239.10.10.10 ( Count = 1 )
Connection Profiles :
1) stg61
2) stg63
Stinger® IP Control Module Configuration Guide A-5
IP Control Module Diagnostics igmp
Command element delete [grp_addr
[if_num]]
Description
With the delete option alone, delete all currently registered multicast groups and their members. If a group address is specified, delete all members of that group. If a group address and interface number are specified, delete that member of the specified group. For example: admin> igmp delete 226.1.1.2 12
LOG notice, Shelf 1, Controller-1, Time: 10:25:53--
Multicast client 226.1.1.2 link DOWN interface number 12
When executed from the shelf controller prompt, only groups that have been joined from the trunk side can be deleted. You must open a session to the LIM to delete groups that have been joined from the LIM side.
sdelete [bridgeNum]
[grp_addr] sdelete [bridgeNum]
[grp_addr][if_num]
Delete all the members of this group, for this bridge on this slot.
Delete a unique instance.
Example The igmp client command shows local MBONE and IGMP client interfaces. For example: super> igmp client
IGMP Clients
Client Version RecvCount CLU ALU
2(Mbone) 2 0 0 0
4(Mbone) 2 0 0 0
1(Mbone) 2 3370 0 0
5 2 0 0 0
6 2 0 0 0
The output contains the following fields:
Field Description
Client
Version
In igmp client command output, the Client field displays the interface ID (the ifIndex value) on which the client resides.
The 1 value represents the Gigabit Ethernet interface. Other numbers are WAN interfaces, numbered according to when they became active. The interfaces labeled (Mbone) receive multicast data from multicast routers.
IGMP version.
RecvCount
CLU/ALU
Number of IGMP messages received on that interface.
CLU is current line utilization, and ALU is average line utilization. Both indicate the percentage of bandwidth used across this interface. If bandwidth utilization is high, some
IGMP packet types are not forwarded.
A-6 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics igmp
Example The igmp groups command displays information about MBONE interfaces.
Details about client member interfaces are maintained on the LIM itself. For example, the following command is invoked on the IP control module of a Stinger system with multicast clients on a DSL interface in slot 6 and an MBONE configured on a Gigabit
Ethernet interface: super> igmp groups
IGMP Group address Routing Table
Up Time: 0d 1:25:05
Group Address MemberIf Expire time Counts
239.100.100.5 * (Mbone) 0::0 S2
Slot 1:6
The next commands open a session with the DSL LIM and invoke igmp groups on the
LIM: super> open 1 6 dadsl-atm-24-1/6> igmp groups
IGMP Group address Routing Table
Up Time: 0d 1:23:46
Group Address MemberIf Expire time Counts
239.100.100.5 6 00:04:07 0::0 S2
When the command is executed on the LIM, the output displays details about the corresponding client member interface. The output contains the following fields:
Field Description
Group address
MemberIf
Expire time
Counts
Multicast address used for the group. An asterisk indicates the IP multicast address being monitored. If a group has no members, the system forwards multicast traffic for the group to the MBONE interface (the default route).
Interface ID of multicast group members.
When this membership expires. The system sends out
IGMP queries every 60 seconds, so the expiration time is usually renewed. If the expiration time is reached, the system removes the entry from the table. If the field contains periods, this membership never expires. A string of periods means that the default route never times out.
Number of packets forwarded to the client, the number of packets dropped due to lack of resources, and the state of the membership.
Example The igmp slot command displays information about slots supporting
IGMP clients: super> igmp slot
IGMP Client Slots
Shelf:Slot Group SendCount
1:8 230.0.0.9 0
1:5 230.0.0.9 0
1:2 230.0.0.9 0
Stinger® IP Control Module Configuration Guide A-7
IP Control Module Diagnostics igmp hosts
The output contains the following fields:
Field Description
Shelf:Slot
Group
SendCount
Shelf and slot card the MBONE connection is on.
Interface number of connection.
Number of packets sent across the interface.
Example The igmp profile command displays information about MCAST-SERVICE profiles. If you execute the command on the control module and specify a profile name, the command will also display the CONNECTION profiles assocated with it.
super> igmp profile
IGMP Service Profiles
Service Name : gold-service
Filter Type : MCAST_FILTER_INCLUSIVE
Filter List :
224.255.129.120
224.225.129.119
Service Name : bronze-service
Filter Type : MCAST_FILTER_INCLUSIVE
Filter List :
224.255.129.119
The output contains the following fields:
Field Description
Service Name Name of the multicast service profile.
Filter Type Inclusive multicast group filtering in the named profile.
Filter List Multicast group addresses to be filtered.
igmp hosts
Description Displays host addresses per member interface for fast-leave purposes.
This command is not available on the controller. To use it, you must open a session to the module on which the member interfaces are established.
Permission level system
Usage igmp hosts
Example The following commands can be used to verify the hosts that have joined a multicast group on an ADSL module in slot 6: admin> open 1 6 dadsl-atm-24-1/6> igmp hosts
Group Address MemberIf Host Address
230.1.1.1 1 10.10.10.2
10.10.10.3
A-8 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics diag igmpsp
diag igmpsp
Description Enable low-level diagnostics on IGMP services profiles.
Permission level debug
Usage diag igmpsp
Example This example first uses a system-level command to view IGMP multicast service profile characteristics. It then uses the debug environment to display low-level diagnostic information.
super> igmp profile
IGMP Service Profiles
Service Name : gold-service
Filter Type : MCAST_FILTER_INCLUSIVE
Filter List :
239.100.100.4
The profile named gold-service has been applied to a connection on the second port of that LIM. The following commands open a session with the ADSL LIM and display diagnostics on the service profiles: super> open 1 6 dadsl-atm-24-1/6> diag igmpsp mcastJoinFilterVerify: Received CLASS D address 239.100.100.4 in report
_profileNameCompare: Compare ( gold-ser with gold-ser ) mcastJoinFilterVerify: [ gold-ser ] is multicast service profile for [ term-
6-2 ] connection
The next output indicates that the system accepted the message received from a client on the second LIM interface: mcastJoinFilterVerify: Received CLASS D address 239.100.100.4 in report
_profileNameCompare: Compare ( gold-ser with gold-ser ) mcastJoinFilterVerify: [ gold-ser ] is multicast service profile for [ term-
6-2 ] connection
diag igmp
In the command output, 230.1.1.1 is the group address and two hosts, 10.10.10.2 and 10.10.10.3, have joined the group on interface 1.
Description Enable low-level diagnostics on IGMP protocol messages.
Permission level debug
Usage diag igmp
Example This example displays IGMP join messages from a client. The following output shows a group message to a client on LIM slot 6, port 6 and the client’s response requesting to join multicast group 230.0.0.9: super> diag igmp igmp debug is ON igmpParseMsg: IGMP packet to 230.0.0.9 type 6 on interface 6 port 6
Stinger® IP Control Module Configuration Guide A-9
IP Control Module Diagnostics
PIM-SM diagnostics
Receiving Version 2 Response from 6
Joining Group 230.0.0.9
IGMP: Joining new group 230.0.0.9
_sendIGMPTableUpdateMsg: sending IGMP_TAB_ADD to 1:8
_sendUpdateMsgToShelf : client 6 join group 230.0.0.9 vRouterID 0 igmpParseMsg: IGMP packet to 230.0.0.9 type 6 on interface 6 port 6
Receiving Version 2 Response from 6
IGMP: Refreshing group 230.0.0.9 input ifNum 6
PIM-SM diagnostics
The pim command provides information about PIM-SM v2 operations.
pim
Description Displays PIM-related information.
Permission level system
Usage pim [ group | rp | nbr | if ifnum | bsr | hash group-addr ]
Command element groups rp nbr if ifnum bsr hash group-addr
Description
Displays information about multicast groups.
Displays group-RP mappings.
Displays information about PIM neighbor routers.
Displays PIM interface statistics.
Displays information about candidate BSRs or the elected BSR.
Displays the best RP for a group or group range.
Example The pim groups command displays information about all multicast groups.
For example: super> pim groups
Group Addr RP/Source Addr upJPTimer Tree(Rpt/Spt)
223.1.1.1 192.168.101.1 40 RPT
224.4.4.4 10.10.10.10 70 RPT
Output field ( pim groups ) Description
Group Addr
RP/SourceAddr upJPTimer
Tree(Rpt/Spt)
Multicast group address for the entry
With the current software version, the RP/Source address is the RP’s IP address.
The interval in seconds following which the Stinger IP
DSLAM sends another PIM join/prune message.
With the current software version, the value of this field is always RPT (RP tree).
Example The pim rp command displays PIM information for candidate Rendezvous
Points (C-RPs) for IP multicast groups. When the local router is the BSR, this
A-10 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics pim information is obtained from received C-RP-Advertisements. When the local router is not the BSR, this information is obtained from received RP-Set messages. For example: super> pim rp
Group RP-Address RPF neighbor Priority holdtime
224.0.0.0/8 1.1.1.3 1.1.1.3 40 75:62
234.0.0.0/8 1.1.1.3 1.1.1.3 40 75:62
234.3.0.0/16 1.1.1.3 1.1.1.3 40 75:62
234.4.0.0/16 1.1.1.3 1.1.1.3 40 75:62
234.5.0.0/16 1.1.1.3 1.1.1.3 40 75:62
234.6.0.0/16 1.1.1.3 1.1.1.3 40 75:62
Static entries (if any) appear following a Static Entries label at the end of the list.
Static entries represent the PIM-GROUP-RP-MAPPING profile entries. Fields in the command output have the following meaning:
Output field (
Group
RP-Address
RPF neighbor
Priority holdtime pim rp ) Description
The IP multicast group address and group mask for which this entry contains information about the C-RP.
IP address of the C-RP.
IP address of the Reverse Path Forwarding (RPF) neighbor-router to which a join message for this group would be directed to under certain circumstances. The
RPF neighbor for an RP is calculated when the Stinger
IP DSLAM receives an IGMP join message for a group range that uses the RP.
Priority of this mapping, to be used in selecting a C-RP if multiple mappings are found for a group range.
Holdtime of the C-RP. If the Stinger is the BSR, the first value in this field represents the holdtime received in the C-RP message for this RP and the second value shows the time left before this C-RP will be removed. If the Stinger is not the elected BSR, the first value in this field represents the holdtime received in BSR messages and second value will be zero.
Example The pim nbr command displays information about PIM neighbors on active
PIM interfaces in the Stinger IP DSLAM. For example: super> pim nbr
Neighbor Interface Priority Holdtime DR
1.1.101.2 2 2 100 YES
Fields in the command output have the following meaning:
Output field ( pim nbr )
Neighbor
Interface
Description
The IP address of the PIM neighbor.
The value of ifIndex for the interface used to reach this
PIM neighbor.
Stinger® IP Control Module Configuration Guide A-11
IP Control Module Diagnostics pim
A-12
Output field (
Priority
Holdtime
DR pim nbr ) Description
Hello priority of the neighbor. The 0 value indicates that the neighbor does not support the priority option, or the neighbor supports the priority option but has an assigned hello priority of 0.
Interval in seconds before the Stinger times out the neighbor if no hello message is received.
Whether the neighbor is DR on the interface.
Example The pim if command displays information and statistics about the specified PIM interface. For example: super> pim if 1 pimHelloIntvl 30 pimHelloHoldtime 105 pimHelloPriority 1 pimJpIntvl 60 pimJpHoldtime 210 pimLanPruneDelay 5000 pimOdDelay 2500 pimDR FALSE genId 22305411
PIM Statistics
4 packets received
0 bad checksum packets received
0 bad version packets received
3 hello packet received
0 join/prune packets received
0 Boot strap packets received
1 C-RP Adv packets received
5 packets transmitted
4 hello packets sent
0 join/prune packets sent
1 boot strap packets sent
The statistics list the number of various packet types sent or received on this interface. They reach a maximum value and are then reset to zero. The pimDR field indicates whether the Stinger IP DSLAM is DR on the interface. The other fields in pim if command output correspond to the pim-options configuration for the
interface, as described in “PIM options in the IP-INTERFACE and CONNECTION profiles” on page 10-7.
Example The pim bsr command shows information about candidate BSRs within the domain if the Stinger is acting as candidate BSR, otherwise it shows information about the elected BSR. For example, the following output occurs when the Stinger IP
DSLAM has been elected BSR: super> pim bsr
Stinger BSR State : ELECTED_BSR
Details of CURRENT BSR:
BSR IP Address : 1.1.1.101
BSR Interface : 1
BSR Priority : 255
Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
VLAN-related diagnostics
BSR holdtime : 57
BSR Current Frag Tag : 717
BSR HASH masklen : 30
Fields in the command output have the following meaning:
Output field ( pim bsr )
Stinger BSR State
BSR IP Address
BSR Interface
BSR Priority
BSR holdtime
BSR Current Frag Tag
BSR HASH masklen
Description
State of the system relevant to BSR election. If C-BSR is not enabled in the IP-GLOBAL profile, this field displays
Stinger is not a C-BSR.
The IP address of the bootstrap router (BSR) for the local PIM region.
The value of ifIndex for the interface used to reach the
BSR.
Priority of the current BSR, from 0 to 255.
The bootstrap holdtime when the BSR is a C-RP in the local domain. If Stinger is elected BSR, holdtime represents the interval after which next BSM will be sent.
The value used in the current BSM to identify fragmented BSMs.
A value (30 by default) used to calculated the hash value for a group range when two RPs have the same priority
Example The pim hash command displays the IP address of the best RP for a group or group range. For example: super> pim hash 234.1.1.1
Best RP for group 234.1.1.1 is 1.1.1.10
To determine the best RP for a particular group, the system searches the dynamic list of RPs first. If the system does not find an RP in the dynamic list, the Stinger system looks into the static RP list. For dynamic entries, the system selects the best RP on the basis of the longest prefix match, RP priority, and the RP IP address. For static entries, the selection of best RP is based on longest prefix match.
VLAN-related diagnostics
The brtbls (bridge tables), ifmgr , diag brtbls , and vlanstats commands are
brtbls
Description The brtbls command supports diagnostics related to VLAN bridge circuits.
Permission level debug
Stinger® IP Control Module Configuration Guide A-13
IP Control Module Diagnostics ifmgr
Usage brtbls [-c] |[-i n][-p ifnum] [-s n][-r]
Command element
-c
-i n
-p ifnum
-s n
Description
Show all bridge circuits.
Show interfaces on bridge circuit n, or within bridgegroup n.
Show partner information on ifnum.
Show stack user VLANs on bridge circuit n.
Example This example displays bridge table information for VLAN bridge circuits.
super> brtbls -c
bridgeGroup bridgeType circuit interfaceList items on list
10 VLAN_CKT 0x84019f30 8400f040 1
1000 VLAN_STACK 0x84016300 82c4d830 3
2 circuits.
Example The next command displays interfaces on bridge circuit 11: super> brtbls -i 11
ifNum ifType ifName
11 135 vlan11
13 49 wan13
The next command lists the interfaces in bridge group 1000: super> brtbls -i 1000
ifNum ifType ifName
23 49 wan23
22 49 wan22
20 135 vlan1000
Example The next command shows paired bridge-circuit interface information for interface 13: super> brtbls -p 13
[ifNum 13 iff 80c4aa88] <----> [ifNum 11 iff 80c4a678]
Example The brtbls -r command shows the “router” interface (the default uplink path) for a bridge group. For a bridge group on STP-enabled ports, it displays two
“router” interfaces. For example: super> brtbls -r 10
IF-NUM PhyAddr
------ -------
24 {1 8 3}
23 {1 8 2}
ifmgr
Description The ifmgr command displays interface-table entries, toggles the debug display, and marks an interface as enabled or disabled. To see the VLAN interface related information, this command should only be entered from the Control Module.
Permission level debug
A-14 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics ifmgr
Usage ifmgr [options]
Command element
[-r vrouter]
[-r vrouter] -k ifNum
Description
Display routing entries. If a virtual router name is specified on the command line, the command displays only the table of the virtual router. If no virtual router name is specified, the command displays the tables for all virtual routers.
Enables manual deletion of a virtual interface on a BIR connection. If ifNum is the interface number of a virtual interface on a BIR connection, the command deletes that virtual interface.
If ifNum is the interface number of the main configured
BIR connection, the command deletes all virtual interfaces associated with that interface. (The main BIR connection interface is never deleted through the use of this command.)
If ifNum is neither the interface number of a virtual interface or a main BIR interface, the command displays an error message.
Displays interface table entries.
-d [ifname | ifnum]
-n conn-profile name Display slot and interface number of the connection.
[up|down] [ifnum|ifname] Enables or disables the specified interface.
Example The ifmgr -d command displays the interface table: super> ifmgr -d bif slot sif u m p ifname host-name remote-addr local-addr
---------------------------------------------------------------------------
000 1:08 000 * ie0 - 0.0.0.0/32 9.9.9.55/32
001 1:08 001 * ie1 - 0.0.0.0/32 0.0.0.0/32
002 1:08 002 * ie2 - 0.0.0.0/32 10.10.10.2/32
032 1:08 007 * ie-stp-1-21- 0.0.0.0/32 0.0.0.0/32
033 1:08 008 * ie1-2111 - 0.0.0.0/32 31.31.31.2/32
034 1:08 009 * ie2-2111 - 0.0.0.0/32 31.31.31.2/32
008 1:08 008 * lo0 - 0.0.0.0/32 127.0.0.1/32
009 0:00 000 * rj0 - 0.0.0.0/32 127.0.0.2/32
010 0:00 000 * bh0 - 0.0.0.0/32 127.0.0.3/32
011 1:08 000 * wanabe - 0.0.0.0/32 127.0.0.3/32
012 0:00 000 * local - 0.0.0.0/32 127.0.0.1/32
013 0:00 000 * mcast - 0.0.0.0/32 224.0.0.0/32
014 0:00 000 - tunnel0 - 0.0.0.0/32 127.0.0.5/32
015 0:00 000 * vr0_main - 0.0.0.0/32 127.0.0.4/32
017 0:00 000 * sar1-61-17 - 0.0.0.0/32 0.0.0.0/32
018 0:00 000 * sar1-62-18 - 0.0.0.0/32 0.0.0.0/32
019 0:00 000 * sar1-9-19 - 0.0.0.0/32 0.0.0.0/32
020 0:00 000 * sar1-8-20 - 0.0.0.0/32 0.0.0.0/32
021 0:00 000 * sar1-9-21 - 0.0.0.0/32 0.0.0.0/32
022 0:00 000 - sip0 - 0.0.0.0/32 0.0.0.0/32
023 1:03 001 * p wan23 mpoa-102 5.5.5.5/32 5.5.5.1/32
Stinger® IP Control Module Configuration Guide A-15
IP Control Module Diagnostics ifmgr
024 0:00 000 * wan24 - 0.0.0.0/32 0.0.0.0/32
025 0:00 000 * wan25 - 0.0.0.0/32 0.0.0.0/32
026 1:08 007 * ie-lag-1 - 0.0.0.0/32 10.10.1.83/32
027 1:08 008 * ie-lag-1-1 - 0.0.0.0/32 10.10.7.83/32
<end>
The ifmgr -d command now indicates a virtual STP interface. For example, in the following output, virtual interface 32 is designated ie-stp-1-2111 and the real interface 33 (a routed VLAN) is designated ie1-2111.
super> ifmgr -d bif slot sif u m p ifname host-name remote-addr local-addr
---------------------------------------------------------------------------
000 1:08 000 * ie0 - 0.0.0.0/32 9.9.9.55/32
001 1:08 001 * ie1 - 0.0.0.0/32 0.0.0.0/32
002 1:08 002 * ie2 - 0.0.0.0/32 10.10.10.2/32
032 1:08 007 * ie-stp-1-21- 0.0.0.0/32 0.0.0.0/32
033 1:08 008 * ie1-2111 - 0.0.0.0/32 31.31.31.2/32
034 1:08 009 * ie2-2111 - 0.0.0.0/32 31.31.31.2/32 u m slot sif p
Command element bif
Description
Bundle interface number. There is one interface number per bundle, including Multilink Protocol (MP) connections. This number is the global interface-table number.
Shelf and slot to which the interface is assigned.
Slot interface.
Whether the interface is enabled (*) or disabled (-).
The interface is part of an MP bundle.
Whether the interface is permanent. A p indicates a permanent interface. A hyphen (-) or a blank indicates that the interface is not permanent. A permanent interface is an interface that is configured in the command-line interface and stored in Stinger NVRAM.
All the Ethernet interfaces and the interfaces based on
CONNECTION profiles are permanent. Transient interfaces are those the Stinger unit builds from
RADIUS. These interfaces have no interface entry when the connection is not active.
A-16 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics ifmgr
Command element ifname host-name remote-addr local-addr
Description
Interface name. Many of the interface names are
described in “Displaying the interface table” on page 4-3.
The names ie1 and ie2 represent GigE interfaces.
The names sar<shelf>-<slot>-<ifnum> represent SAR interfaces.
The names ie-lag-<grp> represent LAG main interfaces, where <grp> is the index of the ETHER-
GROUP profile. LAG virtual interfaces are shown the following name: ie-lag-<grp>-<num> where <grp> is the index of the ETHER-GROUP profile and <num> is the last number of the IP-INTERFACE profile corresponding to the virtual interface.
Hostname of remote device.
Remote address of device as configured in a
CONNECTION profile.
Address of the local interface.
Example The next command displays information about the Gigabit Ethernet interface: super> ifmgr -d 1 iff 0x82ec86cc inUse: Yes hostName: dialoutName:
Authentication Source: In: local Out: local
ExternFilters: No
ExternRoutes @ 0 miscInfo @ 0 reDirectDest: 0.0.0.0
DLCI routeId: 0
MP(P) id: 0 rtIf: 1:08:1 virtual id: 0, virtual next @ -1, virtual main @ -1 minor device: 1 device status: 0x221 output func: 0x801b5f18 input func: 0x801b61a0 mtu: 1500 ip_addr: 201.168.53.123
dstip_addr: 0.0.0.0
netmask: 255.255.255.0
net: 201.168.53.0
subnet: 201.168.53.0
bcast: 201.168.53.255
nbcast: 201.168.53.255
Stinger® IP Control Module Configuration Guide A-17
IP Control Module Diagnostics diag brtbls
diag brtbls
Description Enable diagnostic printf input for bridge tables.
Permission level debug
Usage diag brtbls
Example The next commands enable and disable bridge table diagnostics.
super> diag brtbls brtbls ( Bridge Tables diagnostic ) brtbls debug is ON super> diag brtbls brtbls ( Bridge Tables diagnostic ) brtbls debug is OFF
vlanstats
directed-bcast: yes management only: no macaddr: 00c07b65d579 inp_qcnt: 0 out_qcnt: 0 nexthop: 0.0.0.0
proxy_arp_mode: 0 proxy_arp_head: 0 vRouterID: 0 if_redirServer: 0.0.0.0
if_redirPort: 0 if_redirPort: 0
ATMP tunnel: DISABLED
No associated connection profile
SNMP ifType: 6 multicastServiceProfile : multicastMaxGroups : 0
Description Display or clear VLAN statistics. For details about the vlanstats output
fields, see the descriptions of MIB objects in “VLAN statistics tables” on page A-34.
Permission level debug
Usage vlanstats [-c] {shelf slot item} vlan-id
Command element
-c
Description
Clear statistics for the specified VLAN.
Example The following command displays statistics about VLAN 1 on the first controller’s GigE interface: super> vlanstats { 1 8 2 } 1 rxOctetsHigh : 0 rxOctetsLow : 0 rxFrames : 0
A-18 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
SAR-related diagnostics rxUnicastFrames : 0 rxMulticastFrames : 0 rxBroadcastFrames : 0 txOctetsHigh : 0 txOctetsLow : 0 txFrames : 0 txUnicastFrames : 0 txMulticastFrames : 0 txBroadcastFrames : 0
Example The following command clears the statistics for VLAN 1: super> vlanstats -c { 1 8 2 } 1
Statistics for VLAN 1 cleared
SAR-related diagnostics
The sar
sar
Description Display the Segmentation and Reassembly (SAR) interface and routing tables, protocol statistics, and active sockets.
Permission level debug
Usage sar [options]
-l
-p
-q
-m
Command element
-b
-c
-i
-r
-s
-t
-v
-w
-x
-y
-z [-d|-o|-i|-c|-a]
Description
Show free transmission buffer list.
Clear SAR statistics.
Reset the SAR (destructive).
List open channels.
Configure transmission packet display.
Configure receive packet display.
Show SAR control memory information.
Read shaper.
Show SAR statistics.
Execute SAR PHY test (control module).
Show SAR virtual circuit table.
Write shaper.
List open connections.
Loopback cell statistics (shelf).
List open WAN connections (Stinger control module).
Stinger® IP Control Module Configuration Guide A-19
IP Control Module Diagnostics
Network processor-related diagnostics
Network processor-related diagnostics
The info np
info np
Example The following command analyzes contents of a frame on Gigabit Ethernet to check the VLAN ID: super> sar -p -a -100
SAR: now dumping the contents of all transmitted packets super> ping -c 1 20.1.2.10
PING 20.1.2.10 (20.1.2.10): 56 data bytes tx 1/61(d) @ a1d46b00 packet len 102
TX packet: (task "_brouterPacketTask" at 0x81697c40, time: 8907.26) 102 octets @ 0xa1d46b00
[0000]: 01 20 01 02 03 04 00 d0 52 01 02 04 81 00 00 64 . ......
R......d
[0010]: 08 00 45 00 00 54 c9 2a 00 00 ff 01 c6 6e 14 01 ..E..T.*
.....n..
[0020]: 02 04 14 01 02 0a 08 00 8a 47 23 a5 00 00 60 00 ........
.G#...`.
[0030]: ea 12 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........
........
[0040]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........
........
[0050]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........
........
[0060]: 00 00 00 00 ....
Description Display hardware, protocol, and connection information.
Permission level debug
Usage info np option
Option Description addr arp [vrouter] bridge option conn [slot] [ifnum] did [didnum] ipqos [ifnum]
Display PayloadPlus addr information
Display ARP entries. If a virtual router name is specified on the command line, the command displays only the table of the virtual router. If no virtual router name is specified, the command displays the tables for all virtual routers.
group group-num Display bridging group details.
table group-num ifnum
Display bridging table details.
Display connections.
Display destination ID (DID) table contents.
Display IP QoS details.
A-20 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics info np
Option Description lacp lns mbl mgrp mpm pm bwdist pm rates psl lport [cnt]
[rspslot]
Display link aggregation group (LAG) details.
Display LNS entries
Display Mobile entries
Display multicast groups.
Display the VLAN-MAC to port mapping table in the network processor.
Display IP2100 port-manager bandwidth distribution.
Display IP2100 port-manager bandwidth rates.
Display lport-scheduler information qid qidnum [rspslot] rsc route [vrouter] sed didnum [cnt] sid sidnum [rspslot] spoof [ifnum]
Display Queue information
Display the resources collection list.
Display routing entries. If a virtual router name is specified on the command line, the command displays only the table of the virtual router. If no virtual router name is specified, the command displays the tables for all virtual routers.
Display SED parameters indexed by DID
Display scheduler information
Display spoof details.
Example Without arguments, the info np conn command displays all connection handles. For example: super> info np conn
Connection Handles if slot act cPort dPort type uctl udata qos dctl ddata qos
19 2 Y 000001 000001 LIM 0/124 0/123 default 0/124 0/123 default
1 8 Y 000000 000000 GE 0/864 0/864 default 0/864 0/864 default
6 8 Y 000000 000000 GE 0/864 0/864 default 0/864 0/864 default
7 8 Y 000000 000000 GE 0/864 0/864 default 0/864 0/864 default
24 8 Y 000000 000000 GE 0/864 0/864 default 0/864 0/864 default
To dump all the connection handles for a given slot, or for a given port on a slot, specify the slot/port numbers on the command line. For example: super> info np conn 1 2 22
Connection Handles if sh/sl act cPort dPort type uctl udata dctl ddata
22 1/2 Y 000000 000001 ATM 0/124 0/60 0/60 0/124
Encaps: AAL5-LLC - MTU=1560 (50)
Control & Data Service Queues:
------------------------------
ControlQID 354 Lport 0001
Scheduler UBR CosQueue 1
DataQID 352 Lport 0010
Stinger® IP Control Module Configuration Guide A-21
IP Control Module Diagnostics info np
Scheduler UBR CosQueue 1
PDU Ids:
---------
PduID port vpi/vci Tree
000156 0x0401 0/124 3098
000157 0x0200 0/60 3098
000158 0x0401 2/124 3098
000159 0x0200 0/60 3098
VLAN Configuration : Vlan is not enabled
Packet Flow configuration: No Packet Flow is attached
Multicast Configuration : Multicast is not enabled
Bridge Configuration : Bridging is not enabled
Filter Configuration : No Filters applied
QOS Configuration :
Downstream : default
Upstream : default
DID List:
Did Type QId cosId
572252 UNICAST 353 1
572253 UNICAST 355 1
OAM DID List:
Did Type
572254 UNICAST
572255 UNICAST
572256 UNICAST
572257 UNICAST
If the connection is a LAG interface, the command shows an additional “cloned” data service queue below the Control & Data Service Queues section of the output. This represents a duplicate queue for the second Gigabit Ethernet port, which is used in the distribution of frames.
For example: super> info np conn 1 8 29
Connection Handles if sh/sl act cPort dPort type uctl udata dctl ddata
29 1/8 Y 000000 000000 LAG 0/0 0/0 0/0 0/0
Encaps: ETH/ATM - MTU=1500 (50)
Control & Data Service Queues:
------------------------------
DataQID 320 Lport 0x0020
DataQID (clone) 324 Lport 0x0021
A-22 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics info np
Scheduler UBR CosQueue 3
PDU Ids:
---------
None.
VLAN Configuration : Vlan-Id 7
Packet Flow configuration: No Packet Flow is attached
Multicast Configuration : Multicast is not enabled
Bridge Configuration : Bridge Group 20 Transparent Bridging enabled
Filter Configuration : No Filters applied
QOS Configuration :
Downstream : default
Upstream : default
VLAN CONNECTION: next DIDs are for vlan-id 7
Principal DID List:
Did Type QId cosId Cloned
---------- --------------- ---------- ----- ------
50512 MULTICAST 322 2 No
50513 MULTICAST 326 2 Yes
1048558 UNICAST 323 3 Yes
Layer 2 DID List: Empty
Example The info np mpm command displays the VLAN-MAC to port mapping table in the network processor. For example: super> info np mpm
MAC Address VlanID IfNum Did CnHdl
----------- ------ ----- --- -----
00:00:E2:19:BD:16 2111 33 572243 8894a240
The first column of the output displays the MAC address of the gateway. The second column displays the VLAN ID associated with the MAC address in the first column.
The third column displays the interface number of the Gigabit Ethernet port on which the MAC frame was received. The last two columns display the DID used to send a frame to the gateway and its associated connection handle.
Example To display all routes on the network processor, use the info np route command. For example: super> info np route
Local If Routes for vrouter:main
Destination Gateway IF DID needArp
Stinger® IP Control Module Configuration Guide A-23
IP Control Module Diagnostics info np
1.1.1.3/32 - local 000000 N
9.0.0.0/8 - ie1-1 000000 N
9.9.9.91/32 - local 000000 N
9.9.9.92/32 - local 000000 N
12.0.0.0/8 - ie1 000000 N
12.12.12.12/32 - local 000000 N
127.0.0.0/8 - bh0 000000 N
127.0.0.1/32 - local 000000 N
127.0.0.2/32 - rj0 000000 N
135.254.196.0/24 210.210.210.1 ie0 000000 N
210.0.0.0/8 - ie0 000000 N
210.210.210.75/32 - local 000000 N
224.0.0.0/4 - mcast 000000 N
224.0.0.1/32 - local 000000 N
224.0.0.2/32 - local 000000 N
224.0.0.9/32 - local 000000 N
224.0.0.13/32 - local 000000 N
255.255.255.255/32 - ie0 000000 N
Route Table for vrouter:main
Destination Gateway IF DID needArp
1.1.1.0/24 1.1.1.12 wan19 000000 Y
1.1.1.12/32 1.1.1.12 wan19 000000 Y
Total 20 routes <end>
Example The info np lacp command displays LAG information, such as whether the constituent ports are distributing or not. For example: super> info np lacp
802.3ad Link Aggregation status on NP:
-------------------------------------o LAG 1:
- Ge port 1: distributing
- Ge port 2: distributing
* Ge port 1: group=1, LAG-IfNum=32
* Ge port 2: group=1, LAG-IfNum=32
Example The info np mgrp displays multicast group information. For example: super> info np mgrp
IP Address MaxMtu Member FirstDid LastDid LstInList NdDrain
224.1.1.1 1610 1 12855 12855 12855 No
Example To display IP QoS details, IP QoS monitoring must be enabled on the
info np ipqos command displays information being monitored on the specified interface. For example: super> info np ipqos 19
IP QOS monitoring information for IF 19
IP QOS profile: Pav-Pbit
Number of priority :4 Lowest priority :1
Default classification :provided Total Mcast Rules :0
Classified DIDs :3 Classification rules :4
A-24 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics info np
Mapping priority/COS
P[0]=x P[1]=5 P[2]=x P[3]=x P[4]=4 P[5]=3 P[6]=2 P[7]=x
Main DID list
-------------
DID Qid COS Type
43514 285 5 ucast
Classified DID list
-------------------
DID Qid COS Type
43516 282 2 ucast
43518 283 3 ucast
43520 284 4 ucast
Example To display the IP2100 NP port-manager fixed-rate (guaranteed) rate allocation based on NP-PORT profile settings, use the info np pm bwdist command.
For example: super> info np pm bwdist
NP Port Manager Rates
NP PM Bandwidth Distribution
System Aggregate Allocated BW : 432581
Aggregate User Requested BW : 433416
Available system BW : 3486580
Port Requested Allocated Status
{1 1 0} 36805 36805 BW SERVICED
{1 2 0} 9359 9393 BW SERVICED
{1 3 0} 36805 36805 BW SERVICED
{1 4 0} 9359 9393 BW SERVICED
{1 5 0} 36805 36805 BW SERVICED
{1 6 0} 9359 9393 BW SERVICED
{1 7 0} 9359 9393 BW SERVICED
{1 10 0} 9359 9393 BW SERVICED
{1 11 0} 9359 9393 BW SERVICED
{1 12 0} 36805 36805 BW SERVICED
{1 13 0} 9359 9393 BW SERVICED
{1 14 0} 9359 9393 BW SERVICED
{1 15 0} 36805 36805 BW SERVICED
{1 16 0} 9359 9393 BW SERVICED
{1 17 1} 2540 2555 BW SERVICED
{1 17 2} 2540 2555 BW SERVICED
{1 18 1} 2540 2555 BW SERVICED
{1 18 2} 2540 2555 BW SERVICED
{1 0 2} 62500 62654 BW SERVICED
{1 0 3} 62500 62654 BW SERVICED
Example To display the IP2100 NP port-manager nonfixed-rate (nonguaranteed) rate allocation, use the info np pm rates command. For example: super> info np pm rates
NP Port Manager Rates
Stinger® IP Control Module Configuration Guide A-25
IP Control Module Diagnostics info np
Port{1 1 0} NonFixedRate :552083
Port{1 2 0} NonFixedRate :140896
Port{1 3 0} NonFixedRate :552083
Port{1 4 0} NonFixedRate :140896
Port{1 5 0} NonFixedRate :552083
Port{1 6 0} NonFixedRate :140896
Port{1 7 0} NonFixedRate :140896
CM#8 NonFixedRate :10004
CM#9 NonFixedRate :10004
Port{1 10 0} NonFixedRate :140896
Port{1 11 0} NonFixedRate :140896
Port{1 12 0} NonFixedRate :552083
Port{1 13 0} NonFixedRate :140896
Port{1 14 0} NonFixedRate :140896
Port{1 15 0} NonFixedRate :552083
Port{1 16 0} NonFixedRate :140896
Port{1 17 1} NonFixedRate :38339
Port{1 17 2} NonFixedRate :38339
Port{1 18 1} NonFixedRate :38339
Port{1 18 2} NonFixedRate :38339
Port{1 0 2} NonFixedRate :939814
Port{1 0 3} NonFixedRate :939814
PCI NonFixedRate :8483
Example To display detailed information about a bridge group, use the info np brig command. Its argument is the internal bridge group number. For exampe: super> info np brig 1
Number of interfaces in bridge group #50 : 3
Internal bridge group number : 1
Time left to Mac Aging Timer expiry : 30 rif type bport UDID FDID host-name
----------------------------------------------
0020 wan 0001 43526 12600 minal-3.28
0021 wan 0002 43528 12601 minal-13.4
0022 vlan 0003 43530 12602 vlan22
Flood list pattern :
Type Learn Tree Act Value Pattern
BRI Y 3120 4 00303138 16 48 00000001 00000000
Flood list Information : list size num first last lastinlist Not-drained
------------------------------------------------------
0 255 3 12600 12602 12602 0
Multicast Groups :
GrpIp Msize Maxmtu Member First Last LstInList nDrain
225.1.1.1 255 0 1 13110 13110 13110 0
Type Learn Tree Act Value Pattern
BMP Y 3123 0 00103336 48 0 00000001 E1010101
235.1.1.1 255 0 1 12855 12855 12855 0
A-26 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
Multicast-capable high-bandwidth LIM diagnostics
Group PortBlock if Did Destination
----------------------------------------------------
00050 ROUTER 0022 43530 00:00:00:00:00:09
00050 ROUTER 0022 43530 00:00:00:00:00:0a
00050 ROUTER 0022 43530 00:00:00:00:00:0b
00050 ROUTER 0022 43530 00:00:00:00:00:0c
00050 ROUTER 0022 43530 00:00:00:00:00:0d
Table has 5 entries.
Multicast-capable high-bandwidth LIM diagnostics
The info command is available only in the debug environment, and only in the LIM
interface. See “Enabling the debug environment” on page A-2 for related
information.
To use this command, you must first open an administrative session to the module.
For example, the following commands open a session to a module in slot 15, and then exit the session: super> open 1 15 ep-hs-gs-48-1/15> quit
info
Type Learn Tree Act Value Pattern
BMP Y 3123 0 00103237 48 0 00000001 EB010101
Example The i nfo np bridge command displays bridge table entries. Its arguments are the bridge group number and (optionally) an interface number. For example: super> info np bridge 50
Description On multicast-capable HB LIMs, the info command displays information relevant to distributed multicast operations on the LIM. This section describes its use only in the context of multicast-capable high-bandwidth (HB) LIMs.
For background information, see “Distributed multicast with HB LIMs (IP2100 only)” on page 9-25.
Permission level debug
Usage info <info-type> [port/conn-id/slot] [ifnum]
<info-type> : ffwbridge mcast
Option Description ffwbridge -e Display all entries in the internal AAL5 bridge. For
details about the internal bridge, see “Downstream traffic processing” on page 9-28.
ffwbridge -e [<port> vpi Display the bridge entry for the specified connection.
vci]
<port> vpi
The DSL line (starting at 1)
The VPI on the DSL side.
Stinger® IP Control Module Configuration Guide A-27
IP Control Module Diagnostics info
A-28
Option Description ffwbridge -f mcast -p -g mcast -s -g vci The VCI on the DSL side.
Display the FFW interface. For details about FFW
interfaces, see “Conceptual overview” on page 9-26.
Display all multicast groups in IGMP proxy (routing) mode.
Display all multicast groups in IGMP snooping
(bridging) mode.
mcast -p -g <ip-address> Display properties of the specified group in IGMP proxy
(routing) mode.
mcast -s -g <ip-address> Display properties of the specified group in IGMP snooping (bridging) mode.
mcast -p -m <ip-address> Display the member list of the specified group in IGMP proxy (routing) mode.
mcast -s -m <ip-address> Display the member list of the specified group in IGMP snooping (bridging) mode.
Example For example, the following command displays all bridge entries (all terminated, routed connections) on the HB LIM: ep-hs-gs-48-1/15> info ffwBridge -e
DSL port VPI VCI Bridged to Sonet port VPI VCI
4 0 35 0 0 150
Example The following command displays more detailed information about a connection on port 4 using VPI 0 and VCI 25: ep-hs-gs-48-1/15> info ffwBridge -e 4 0 35
DSL side
Port : 4
VPI : 0
VCI : 35
IW port tag : 15
IW Rx channel tag : 16
IW Tx channel tag : 17
IW Tx flow aggregation tag : 18
Sonet side
Port : 0
VPI : 0
VCI : 150
IW port tag : 19
IW Rx channel tag : 20
IW Tx channel tag : 21
IW Tx flow aggregation tag : 22
Example The following command displays information related to the FFW interface
(the interface on which multicast traffic is sourced on the HB LIM).
ep-hs-gs-48-1/15> info ffwBridge -f
FFW System
Host IW Rx channel tag : 0
Host IW Tx channel tag : 0
Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics
Host Tx aggregation tag : 1
FFW interface
IW port tag : 6
IW Rx channel tag : 7
IW Tx channel tag : 8
Example The following command displays information about all multicast groups in proxy mode: ep-hs-gs-48-1/15> info mcast -p -g
GROUP address Aggr Tag Nb members
224.1.1.2 25 1
SNMP MIB for GMAC and VLAN statistics
The ip2kstats.mib
MIB gathers statistics about the GMAC interface of the IP control module, and also collects statistics on a per-VLAN basis. It is implemented as the following proprietary Alcatel-Lucent enterprise MIB: ip2kStatsGroup OBJECT IDENTIFIER ::= { ascend 51 }
The transmit and receive statistics represented in this MIB are also accessible in the command-line interface by using the gmac -d command. The VLAN statistics are also accessible in the command-line interface by using the debug-level vlanstats command.
History maintained at 15-minute intervals
The system maintains a history of the following fields by averaging them at fixed
15-minute intervals for the last 24 hours (96 intervals):
■
■
Tx and Rx octets (transmit and receive traffic streams)
Multicast traffic (receive side only)
■
■
■
Unicast traffic (transmit and receive traffic streams)
Broadcast traffic (receive side only)
Cyclic redundancy check (CRC) errors (receive side only)
Gigabit Ethernet (GigE) statistics tables
Gigabit Ethernet statistics are represented in five MIB tables:
■ GigE configuration
■
■
GigE interval transmit statistics
GigE interval receive statistics
■
■
GigE total transmit statistics
GigE total receive statistics
Stinger® IP Control Module Configuration Guide A-29
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics
Gigabit Ethernet configuration
The gigEConfigTable is a configuration table for an IP control module GigE interface.
It is indexed by the interface index. This MIB table contains the objects shown in
Table A-1. GigEConfigTable MIB objects
MIB object gigEValidIntervals gigELastInitTime
Description
The number of previous intervals for which data was collected. The value will be 96 unless the interface was brought online within the last
24 hours, in which case the value will be the number of complete 15-minute near-end intervals since the interface has been online.
System time when the GigE port was last initialized. The time is represented in text format.
Interval transmit statistics
The gigETxIntervalTable is a table containing transmit statistics for the GigE interface in a 15-minute interval. It is indexed by the interface index and the interval number (contained in the gigETXIntervalNumber variable). This MIB table contains
the objects shown in Table A-2:
Table A-2. GigETxIntervalTable MIB objects
MIB object gigETxIntervalNumber gigETxIntervalOctetsLow gigETxIntervalOctetsHigh gigETxIntervalUnicastPackets
Description
A number between 1 and 96, where 1 is the most recently completed 15-minute interval and 96 is the 15-minute interval completed 23 hours and 45 minutes prior to interval 1.
The lower 32 bits and upper 32 bits of the 64bit interval transmit packet byte counter, which contains a count of how many bytes were transmitted in error-free packets during the interval.
Total number of Unicast packets transmitted during the interval.
Total transmit statistics
The gigETxTotalTable is a table containing the total transmit statistics for the GigE interface. It is indexed by the interface index. The transmit counters in this table are
A-30 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics also displayed in the output of the gmac -d
command. See “” on page A-33. This MIB
table contains the objects shown in Table A-3:
Table A-3. GigETxTotalTable MIB objects
MIB object gigETxTotalOctetsLow gigETxTotalOctetsHigh gigETxTotalGoodPackets gigETxTotalPkt64 gigETxTotalPkt65To127 gigETxTotalPkt128To255 gigETxTotalPkt256To511 gigETxTotalPkt512To1023 gigETxTotalPkt1024ToMax gigETxTotalPktDefer gigETxTotalPktUndSz gigETxTotalUnderFlow gigETxTotalPfcf gigETxTotalPfcc gigETxTotalRfcf
Description
The lower 32 bits and upper 32 bits of the
64-bit transmit packet byte counter, which contains a total count of how many bytes have been transmitted in error-free packets.
Total count of packets transmitted without error.
Total count of transmitted 64-byte packets.
Total count of transmitted packets from 65 to
127 bytes in length.
Total count of transmitted packets from 128 to
255 bytes in length.
Total count of transmitted packets from 256 to
511 bytes in length.
Total count of transmitted packets from 512 to
1023 bytes in length.
Total count of transmitted packets from 1024 bytes up to the MAX bytes in length (1536 for non-jumbo packets and 9728 for jumbo packets).
1
Total count of packets that were deferred because the interframe gap was in excess of 96 bits when a packet was available for transmission. The IFG is a delay between code division multiple access/carrier detect
(CDMA/CD) packets, intended to provide interframe recovery time for other CSMA/CD sublayers and for the physical medium.
Total count of packets less than 64 bytes in length.
Total count of packets that were truncated because of an empty FIFO.
Total count of Pause Flow Control packets that were sent because the receive FIFO exceeded its highwater mark. The Pause function is a mechanism for full duplex flow control.
Total count of Pause Flow Control packets that were sent because the client requested them.
Total count of Reset Flow Control packets that were sent because the receive FIFO went below its lowwater mark.
Stinger® IP Control Module Configuration Guide A-31
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics
Table A-3. GigETxTotalTable MIB objects (Continued)
MIB object gigETxTotalRfcc gigETxTotalOverFlow gigETxTotalAlmostFull
Description
Total count of Reset Flow Control packets that were sent because the client requested them.
Total number of packets in which a write from the physical signaling interface was attempted to a full transmit FIFO.
Total number of packets in which the transmit
FIFO Almost Full flag was set.
1. Jumbo packets are not currently supported on the Gigabit Ethernet interface of the IP control modules.
Interval receive statistics
The gigERxIntervalTable is a table containing receive statistics for the GigE interface in a 15 minute interval. It is indexed by the interface index and the interval number
(contained in the gigERXIntervalNumber variable). This MIB table contains the
Table A-4. GigERxIntervalTable MIB objects
MIB object Description gigERxIntervalNumber gigERxIntervalOctetsLow gigERxIntervalOctetsHigh
A number between 1 and 96, where 1 is the most recently completed 15 minute interval and 96 is the 15 minutes interval completed 23 hours and 45 minutes prior to interval 1.
The lower 32 bits and upper 32 bits of the 64bit interval receive packet byte counter, which contains a count of how many bytes were received in error free packets during the interval.
gigERxIntervalUnicastPackets Count of packets of the Unicast Type received during the interval.
gigERxIntervalMulticastPackets Count of packets of the Multicast Type received during the interval.
gigERxIntervalBroadcastPackets Count of packets of the Broadcast Type received during the interval.
gigERxIntervalCrcErrors Count of packets that failed CRC received during the interval.
Total receive statistics
The gigERxTotalTable is a table containing the total receive statistics for the GigE interface. It is indexed by the interface index. The receive counters in this table are also displayed in the output of the gmac -d
command. See “” on page A-33. This MIB table contains the objects shown in Table A-5:
A-32 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics
Table A-5. GigERxTotalTable MIB objects
MIB object gigERxTotalOctetsLow gigERxTotalOctetsHigh gigERxTotalGoodPackets gigERxTotalPkt64 gigERxTotalPkt65To127 gigERxTotalPkt128To255 gigERxTotalPkt256To511 gigERxTotalPkt512To1023 gigERxTotalPkt1024ToMax gigERxTotalMacType gigERxTotalCrcErrors gigERxTotalUnderSize gigERxTotalOverSize gigERxTotalAlmostFull gigERxTotalOverRun gigERxTotalMulticastPackets gigERxTotalBroadcastPackets gigERxTotalJabber gigERxTotalPfc
Description
The lower 32 bits and upper 32 bits of the 64bit receive packet byte counter, which contains a total count of how many bytes have been received in error free packets.
Total count of packets received without error.
Total count of received 64-byte packets.
Total count of received packets from 65 to 127 bytes in length.
Total count of received packets from 128 to 255 bytes in length.
Total count of received packets from 256 to 511 bytes in length.
Total count of received packets from 512 to
1023 bytes in length.
Total count of received packets from 1024 bytes up to the MAX bytes in length (1536 for nonjumbo packets and 9728 for jumbo packets).
1
Total count of MAC Type packets received
Total count of packets received that failed CRC.
Total count of packets that were less than 64 bytes in length.
Total count of packets received that were greater than the MAX bytes in length (1536 for non-jumbo packets and 9728 for jumbo packets).
Total number of packets in which the receive
FIFO exceeded its highwater mark.
Total number of receive packets in which a write to a full receive FIFO was attempted.
Total number of receive packets that were of the Multicast Type.
Total number of receive packets that were of the Broadcast Type.
Total count of receive packets that were classified as Jabber. Jabber is the condition of abnormally long transmissions, usually due to a fault condition.
Total count of Pause Flow Control packets that were received. The Pause function is a mechanism for full duplex flow control.
Stinger® IP Control Module Configuration Guide A-33
IP Control Module Diagnostics
SNMP MIB for GMAC and VLAN statistics
Table A-5. GigERxTotalTable MIB objects (Continued)
MIB object gigERxTotalRfc
Description
Total count of Reset Flow Control packets that were received.
1. Jumbo packets are not currently supported on the Gigabit Ethernet interface of the IP control modules.
VLAN statistics tables
To capture and clear VLAN statistics, the following MIB tables are supported:
■ GigE VLAN statistics
■ GigE VLAN clear statistics
VLAN statistics
The GigEVlanStatTable is the VLAN statistics table for an IP control module GigE interface. It is indexed by the interface index and by VLAN ID (contained in the gigEVlanId variable). The counters in this table are also displayed in the output of the vlanstats
debug-level command. See “vlanstats” on page A-18.
This MIB table contains the objects shown in Table A-6:
Table A-6. GigEVlanStatTable MIB objects
MIB object gigEVlanId gigEVlanRxOctetsLow gigEVlanRxOctetsHigh gigEVlanRxGoodFrames gigEVlanRxUnicastFrames gigEVlanRxMulticastFrames gigEVlanRxBroadcastFrames gigEVlanTxOctetsLow gigEVlanTxOctetsHigh
Description
VLAN ID. Identifies a specific VLAN on the GigE interface of the IP control module.
Receive Frame Byte Counter Low Double
Word.
Receive Frame Byte Counter High Double
Word.
Receive frame counter. Indicates the total number of frames received on the GigE interface for this VLAN.
Receive Unicast frame counter. Indicates the total number of unicast frames received for this
VLAN.
Receive Multicast frame counter. Indicates the total number of multicast frames received for this VLAN.
Receive Broadcast frame counter. Indicates the total number of broadcast frames received for this VLAN.
Transmit frame byte counter Low Double word.
Transmit Frame Byte Counter High Double word.
A-34 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
PIMv2 MIB support
Table A-6. GigEVlanStatTable MIB objects (Continued)
MIB object gigEVlanTxGoodFrames gigEVlanTxUnicastFrames gigEVlanTxMulticastFrames gigEVlanTxBroadcastFrames
Description
Transmit frame counter. Indicates the total number of Ethernet frames transmitted on the
GigE interface for this VLAN.
Unicast transmit frame counter. Indicates the total number of unicast frames transmitted for this VLAN.
Multicast transmit frame counter. Indicates the total number of multicast frames transmitted for this VLAN.
Broadcast transmit frame counter. Indicates the total number of broadcast frames transmitted for this VLAN.
VLAN clear statistics
The GigEVlanClearStatTable is the table for clearing statistics for a given VLAN on the IP control module GigE interface. It is indexed by the interface index and by
VLAN ID (contained in the gigEVlanId variable). This table contains the objects
Table A-7. GigEVlanClearStatTable MIB objects
MIB object gigEVlanClearStatCmd
Description
Command to clear statistics for a particular
VLAN. Values are: none(1) –No action. clearAllStats(1) –Clear all statistics.
A GET operation on this object will always return none(1) .
PIMv2 MIB support
The system provides SNMP MIB support for the PIM protocol as defined in draft-ietf-pim-mib-v2-01.txt (the PIMv2 MIB). The PIMv2 MIB is placed in the
MIB tree under experimental 61 . The current software supports PIMv2 MIB tables as
Table A-8. Current level of support for PIMv2 MIB tables
PIMv2 MIB table pimInterfaceTable pimNeighborTable pimIpMRouteTable NO pimNextHopGroup NO
Support in this software version
YES
YES
Stinger® IP Control Module Configuration Guide A-35
IP Control Module Diagnostics
PIMv2 MIB support
Table A-8. Current level of support for PIMv2 MIB tables (Continued)
PIMv2 MIB table pimRPTable pimRPSetTable pimCandidateRPTable pimComponentTable
Support in this software version
NO
YES
NO
YES
The snmpwalk , get , and getnext routines are supported for objects in the supported tables . Because Stinger IP DSLAMs operate within a single PIM domain, the component index in pimComponentTable is always set to 1 . For example, the following snmpwalk from an SNMP manager displays information from the pimInterfaceTable :
$ snmpwalk -m all -O 50.50.50.5 public experimental.pimMIB.pimMIBObjects.pim.pimInterfaceTable
pimInterfaceAddress.2 = IpAddress: 1.1.1.2
pimInterfaceNetMask.2 = IpAddress: 255.0.0.0
pimInterfaceMode.2 = sparse(2) pimInterfaceDR.2 = IpAddress: 1.1.1.2
pimInterfaceHelloInterval.2 = 60 seconds pimInterfaceStatus.2 = active(1) pimInterfaceJoinPruneInterval.2 = 60 seconds pimInterfaceTrigHelloInterval.2 = 5 seconds pimInterfaceHelloHoldtime.2 = 105 seconds pimInterfaceLanPruneDelay.2 = on(1) pimInterfacePropagationDelay.2 = 7500 milliseconds pimInterfaceOverrideInterval.2 = 2500 pimInterfaceGenerationID.2 = on(1) pimInterfaceJoinPruneHoldtime.2 = 210 seconds
The following snmpwalk command displays information from the pimNeighborTable :
$ snmpwalk -m all -O 50.50.50.5 public experimental.pimMIB.pimMIBObjects.pim.pimNeighborTable
pimNeighborIfIndex.167837953 = 1 pimNeighborExpiryTime.167837953 = Timeticks: (98) 0:00:00.98
pimNeighborMode.167837953 = sparse(2) pimNeighborLanPruneDelay.167837953 = 0 pimNeighborOverrideInterval.167837953 = 0 pimNeighborTBit.167837953 = off(0) pimNeighborDRPresent.167837953 = true(1)
The following command from an SNMP manager displays information from the pimRPSetTable :
$ snmpwalk -m all -O s 50.50.50.5 public experimental.pimMIB.pimMIBObjects.pim.pimRPSetTable
pimRPSetHoldTime.1.224.255.50397441 = 75 pimRPSetHoldTime.1.234.255.50397441 = 75 pimRPSetHoldTime.1.1002.65535.50397441 = 75 pimRPSetHoldTime.1.1258.65535.50397441 = 75 pimRPSetHoldTime.1.1514.65535.50397441 = 75 pimRPSetHoldTime.1.1770.65535.50397441 = 75 pimRPSetExpiryTime.1.224.255.50397441 = Timeticks: (56) 0:00:00.56
A-36 Stinger® IP Control Module Configuration Guide
IP Control Module Diagnostics
PIMv2 MIB support pimRPSetExpiryTime.1.234.255.50397441 = Timeticks: (56) 0:00:00.56
pimRPSetExpiryTime.1.1002.65535.50397441 = Timeticks: (56) 0:00:00.56
pimRPSetExpiryTime.1.1258.65535.50397441 = Timeticks: (56) 0:00:00.56
pimRPSetExpiryTime.1.1514.65535.50397441 = Timeticks: (56) 0:00:00.56
pimRPSetExpiryTime.1.1770.65535.50397441 = Timeticks: (56) 0:00:00.56
Following is sample output of an snmpwalk on pimComponentTable :
$ snmpwalk -m all -O s 50.50.50.5 public experimental.pimMIB.pimMIBObjects.pim.pimComponentTable
pimComponentBSRAddress.1 = IpAddress: 1.1.1.101
pimComponentBSRExpiryTime.1 = Timeticks: (45) 0:00:00.45
pimComponentCRPHoldTime.1 = 0 seconds pimComponentStatus.1 = active(1)
Stinger® IP Control Module Configuration Guide A-37
Scarica
Pubblicità